It is cause by a loose connection, I believe that the USB connector of your FC is loose. So waiting will not fix it moving the cable a bit will.
Pay attention to the noise your windows does when you connect or disconnect the cable.
Disconnection noises are bad if you did not explicitly disconnected the board.
No issue at all with any other app.
Only with AMC.
It did that twice since yesterday and it was on the last version.
In an older version this didn’t happen, at least for 15 or so days that I used it.
I noticed in your motor test videos the GPS wire is hanging free - make sure that is secured before you fly. It’s very good at enhancing vibrations and transferring them to the flight controller.
The same goes for other wiring.
Thank you very much for your advice, although I already have it in mind.
And I had it tied up, I just took it off because some cables from the camera were disconnected and I had to undo the whole drone.
MAVFTP is not working and the board is falling back to simple param download.
AMC warns you about it when connecting (MAVFTP not available) but it somehow does not correctly fall back to simple param download correctly.
MP sees the same issue, but manages to fallback.
Yes, this is a bug, triggered by the board not not supporting MAVFTP.
AMC should fallback, but it does not.
So if I understand it correctly.
I changed some params and then it triggered this error message.
I guess it has something to do with the params that I last changed, as I have this error from yesterday only.
Is there anything that I can do to fix it?
Changing the flight controller at this time isn’t an option for me.
Thanks again!
And also I took a screenshot of every step in the param files.
Can I then go on Mission Planner and change these params to my preferances, and do what AMC does, without AMC?
I suggest that Speedybee become a Corporate Sponser and contribute some $$$ as their hardware consumes considerable action on the forum.
Edit-they are a partner. I wasn’t aware of that, that’s great.
During my test flights yesterday, everything worked perfectly! From Loiter and Alt Hold to RTL and Auto Mode, all flight modes performed as expected.
I suspect that the issue was caused by overload, so we disabled logging by setting LOG_BACKEND_TYPE = 0 for good measure. Now, I’m wondering if I should continue configuring parameters using the ArduPilot Methodic Configurator (AMC). To be honest, I’m a bit concerned that changing something might affect my progress.
I also have a few questions:
First set of questions:
How can I make my drone automatically arm itself when I switch to Auto Mode and start its predefined flight(because in the stage that Im in, I need to arm the drone, give a little throttle and then switch to auto mode)?
How can I make the camera start recording when the drone is armed(esp32 cam)?
Second set (further development):
How can I arm the drone without a transmitter, using an external signal, and have it follow the same behavior as in my first question?
In general, does the drone require a connection to the transmitter while flying in Auto Mode? I ask because I want to know the distance limitations for my mission. For example, can I set a flight path of around one kilometer or even several kilometers?
Any guidance on these would be greatly appreciated!