Hey all, so I have a pair of APM2s that aren't working and I can't figure out why or how to fix them. I'll call them Alpha and Beta.

Alpha will seemingly function when connected to a battery: lights flash, GPS locks, RTF light comes on, etc.  However, neither the USB nor the telemetry port work completely.  The telemetry powers the radio but doesn't send or accept traffic, but that's not as important as USB.  When I connect the USB, the APM powers up, the computer recognizes it as an APM, and I have the option of connecting to it in APM Planner. If I try, it says Getting Params as usual, and the Tx light flashes but not as much as my other APMs. After about 7 seconds it flashes a lot faster and the Planner says Timeout on read: Your serial link isn't fast enough.  The Tx light then becomes solid on and stays that way even if you reset.  If I connect in the terminal, all of the usual "GROUND START...Demo Servos!...Warming up ADC...Demo Servos!... Ready to FLY" shows up fine, so clearly the baud rate is in fact correct. I wrote a python MAVLink dissector, and all of the packets the APM is sending are completely correct.  So basically with Alpha it comes down to everything is working perfectly, all my tests are showing that it's working and sending legitimate data, but the telemetry port isn't working and Planner can't successfully connect. I have used multiple USB cables and computers. Any thoughts?

Beta also does the correct boot sequence with the LEDs, but again the telemetry port and USB port do not work, this time at all.  When I attempt to connect with the Planner, the Rx light flashes once as it should, but the APM never transmits, same with the terminal.  So basically with Beta, it won't communicate at all and there's nothing I can really think of to test with.  As much as I love my APM1s, I'd like to not have to go back to using them because these 2s are broken, and I haven't even done anything out of the ordinary with them.  Any help would be appreciated.

Tags: APM2, USB, bricked

Views: 140

Reply to This

Replies to This Discussion

With Alpha, have you tried reloading the firmware and erasing the eeprom (CLI setup/erase)?

Yeah it can't detect the version and says to check the cabling.

Assuming you've also tried on another computer with another USB cable, and they're still not working, I'd contact customer support from the store you got them from and request a RMA.

Well here's the conclusion I'm coming to based on more tests I've done...

With Alpha, if I hook up the 3DRs and go to the Terminal, I get a response from the APM if I spam it with Setup Radio, Tests, or Show Settings clicks, but to me it seems that the baud rate might be slightly off. For instance:

Spamming Setup Radio:

?ou?usutup  (setup)
?exitMsetip-*|W?wymo?[t  (exit setup)
wetutk?h5sa?5n7
rc?sotu?itmxit
ww?WH77adio  (radio)
}vuq?uxZ5{e|it  (exit)

itMsetuztupMJradio-wh5|??5Vu[5wetoO??{tsgk?z}cW5)?w]O?exmtsutup  (setup radio exit setup)

Spamming Tests:
tesv*e|m?m?oz5|m{t  (test)
?exi?_oYm  (exit)
e?[5tew~O?ez
=~/?e?coMo?}}wo?uWG}?{75j?testk?-uS->??e}mw?/?extKr?  (test exit)

Spamming Show Settings
?/?extKr?m|=~omtM?e}7w75shows  (shows)
Wu?otsutup{??uw}WW=u  (setup)
{euun?}mu=?sutups?mxmt  (setup)
weux}[=?Yuwo?|5???
s?kwowk^CWo?|i_?exit-sutupsho?eyiu  (exit setup show)
se7n?exo7?exi|sewMe|mt  (exit)

So say the oscillator responsible for the internal clock of the APM is damaged, and instead of 57600 baud rate, it's 56000 or something, so every few bits will be off and we can see this in the ascii text.  So my thought is that for at least Alpha, maybe also Beta, there was some sort of surge or something that damaged the board such that the oscillator is off.

One time my apm2 was bricked. It begin the initialization and then freeze. To solve this issues I do the following:

In arducopter code, function init_ardupilot (file sytem.pde), just after the Serial port initialization "Serial.begin(SERIAL0_BAUD, 128, 256);"
I add the following instruction
"run_cli();"
which force the start of the cli before all others initializations. I compile and sent it to the apm. Then connect with serial usb, erase the eeprom and does a reset with cli command.

After this I resent the correct code to the apm, reconfigure it and everything where working fine.

It would be cool, if in next version of "mission planner" there is a possibility to send a small program that clean everything and in particular the eeprom.

RSS

Social Networking

Contests

Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.

A list of all T3 contests is here

Groups

Advertisement

© 2013   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service