For some reason when I move out of CLI mode and hit the reset, the LED A (green) does not blink nor turn solid. What have I done wrong? When I am in CLI mode, it is solid.
I have tried using the mission planner as well as uploading the code manually.
The planner cannot communicate with the APM either for some reason...the count down (timeout) reaches zero, maybe this could indicate something else is wrong as well? I tried adding #define GCS_PROTOCOL GCS_PROTOCOL_MAVLINK, but still no luck.
Not beeing an expert, by what you describe, seems to me the IMU is not comunicating with APM. That happened to me some days ago after a somehow violent flight. Seems that some of my weldings were not 100% even if they looked like.I would advise you to recheck all the weldings, and if any of them is in short circuit. Even if they look ok, re weld some of them (the ones from the connectors).
Between last night and today I don't believe I did anything differently, but for some reason it is working now.
LED A still would not come on unless the motor signals were plugged in after the APM was booted. Is this the standard? I could not find this in the manual and I do not remember reading it. I read 'If you've kept the four-wire connector from APM to the power disconnected for safety, now is the time to connect it.' Is this referencing the signal wires?
First few flights have been a new success! It looks like I have a new leaf blower as tree droppings were flying everywhere.
Thanks for the help!
Yes, its the four wire signal cable to the ESCs that's soldered to the Power Distribution Board on a standard AC2, and plugs into the four lowest numbered outputs of the APM board (nearest the edge of the R/A connectors)
Hello again. As I told you before, same happened to me and I rebuild the weldings thinking it could be that (since my problem solved with that), well, yesterday it happened again after a crash against a kitchen stool where 2 motors got stalled. The APM went crazy again with the symptoms described here (not booting properlly, leds not going thru the sequence, etc.), so I went recheking the weldings and everything ok, I pressed the boards together but still nothing, so I was loosing my faith, I unplugged everything, left the building to cool off, and after a couple of hours, plugged everything again and it was working again. I believe now that it has nothing to do with bad contacts or weldings (since it was working fine). Maybe after a surcharge or current feedback from the motors the IMU seems to go crazy, and maybe 1 component stays charged or with reverse polaryzation (I'm not an electronics expert) and it needs to loose the charge. This happend to me the first time when my quad flipped over and damaged a motor, and the second time now when it crashed againt the stool. So, something to do with motors getting stopped suddendly by force, I believe.
The four-wire connector can be left attached the entire time correct?
"If you've kept the four-wire connector from APM to the power disconnected for safety..." The "If" got me because I did not keep it disconnected for safety, I had the batteries removed instead.
The yellow safety advice boxes that are scattered around the manual use beautifully ambiguous English, but their intention is to say leave the 4-wire cable disconnected at all times except when you need it connected.
The danger time is when the APM is rebooting, which is for example immediately after you plug in the USB cable, even if the board is already powered.