I have a Matek F405-miniTE that was previously working in a small quad, I think running the first AC FW for that board, probably 4.2.0. Someone tried to load 4.2.2 on it, and now the board won’t boot, streaming a continuous string of errors. Here is a capture from the message window in MissionPlanner:
I have been able to load the latest FW using MissionPlanner, both Plane and Copter. However, when I attempt to load the 4.2.0 hex file, it asks if it is a Linux board - I say no, then it asks if it is APM 2+ - I say yes, then it reads the hex, and then indicates that there was a communication failure.
I have a PC with an older version of MissionPlanner, and it is still showing AC4.2.1 as the latest, but when I load it and then reconnect, MP indicates that it is 4.2.2.
Am I doing something wrong, or is there a better approach to load older FW?
EDIT: I just tried using the “All Options” feature, selecting stable 4.2.0, and I get this error
Well shoot. I was just getting ready to submit a trouble ticket to Matek, and they wanted high rez photos of both sides. I had already pulled it out of the quad and removed all the peripheral components for debugging, but for the photos I unsoldered all the pigtails. In intern had soldered them on, and the solder job looked really good. However, now it works. There must have been a solder bridge that I couldn’t see. That was a lot of work for nothing.
I’m glad it’s working but feel sad that I once again filled these pages with something that turned out to be user error.
Looks like I’m not quite out of the woods yet. The autopilot boots, and I’ve got it detecting the GPS and Compass, and reading the RC signals, but when I try to set flight modes - there aren’t any. On the Flightmodes page, there are no options in the drop-down menus, and the current flight mode is listed as unknown. In the full parameter list, I can enter numbers in the flightmode entries, but it isn’t showing me any options. I’m guessing there is still something wrong with the FW I have on it. It’s currently running AC4.2.2.
I’m working on tuning this quad, and having some new experiences. It flies well in Acro and Stab, hovering just a bit below mid stick. When I switch to Alt-hold or Pos-hold mode, I have to give it very high throttle to keep it from immediately landing, probably 75 to 80%. I ran hover_learn, and it set hover at about 0.148, which seems low. Z-vibrations seem high (around 60 to 80), but x and y are reasonable, and there is no clipping, Nevertheless, on the last hop I got an Err: FAILSAFE_VIBE-1 message. It happened almost exactly as I switched to alt-hold mode, , and it’s followed almost immediately be a Vibration compensation ON message. I didn’t see anything that looked like a failsafe, but about 15 seconds later it shot into the air very abruptly. I tried to change to Stab mode in a panic, but accidentally went to Pos-hold. then i switched to Stab and recovered it. Looking at the logs, it seems that the climb ended when I switched to Pos-hold. The current meter isn’t calibrated well, but it was reporting a 1A draw in hover, and shot to 16 amps during the climb.
Another issue. Sitting on the ground, the displayed heading always seems to drift to about a 90 degree error over time, but in flight, it seems to correct itself and holds position well.
I’m used to getting clipping when vibes are crazy high. i was surprised that there weren’t any. It’s a featherweight 5" quad with 20mm stack. Both the ESC and FC are isolated with grommets. But maybe they are over compressed. In alt-hold, it seemed like it was oscillating vertically a bit. It looks like there is a P-gain for alt-hold. Default value seems to be 1. Should I try a lower value?
I wouldn’t do that. There are likely other parameters that need attention before changing that. I have a sub 250g 5" and it’s at default for sure. Post a link to a flight log.
