A couple of weeks ago on my copter’s maiden flight, I stupidly managed to let it get hung up in a tree. After it was retrieved I plugged in the battery and tried to fly it again but it would not arm. Eventually I noticed that the safety switch was flashing with four quick flashes followed by a pause and then repeating. Per the documentation this means that the FMU armed, but the IO did not. After attempting further troubleshooting I noticed that the power connector had ripped off the power module so the Pixhawk must have been getting its power from the ESCs. So, I replaced the power module but I continue to get the error code indicating that the IO board did not arm. Also the amber and blue lights on the IO side are alternating; the documentation says that this indicates a memory allocation error for developers and shouldn’t be seen by end-users.
Did I damage the Pixhawk when I tried to arm it when it wasn’t connected to the power module? The collision with the tree didn’t seem violent enough to cause major problems. Any advice on what to do would be appreciated. Thanks
Hi Alan.I had something similar happen with the same IO leds flashing as per your description. It happened after multiple tries getting my RC to connect to pixhawk (I was running AC 3.4.4).
Eventually, I uploaded rover firmware … then reuploaded the AC 3.4.4 firmware. Seemed to do the trick for me. May or may not solve your issue.
Cheers
Jason
Thanks for the suggestion Jason. Unfortunately it didn’t work. I’m still getting the same errors.