Replies to This Discussion

Permalink Reply by Vincent Mees on April 13, 2012 at 8:54am

I've reloaded the code, samething.

I split the power supply so that apm gets power from seperate supply. So hooked it up with usb and teh outputs standard with the ESC.

Same thing, until I connected with MP. Then it booted up???

So redid everything as previous, placed jumper and connected battery.

No go. Then I did a reset of the APMwith the switch and presto, it booted.

Is there something wrong with the code??

Its not very ideal to do a reset after battery connection with props and all........

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on April 13, 2012 at 9:00am

Yes, this is a known issue that we're looking at. I know it's a little annoying, but just make a habit of pressing the reset button after you plug in your LiPo. It's probably a good idea anyway, since it ensures you'll be calibrating on level ground, but it won't be necessary for much longer. 

• ▶ Reply

Permalink Reply by Vincent Mees on April 13, 2012 at 10:15am

Thx Chris for the heads up

• ▶ Reply

Permalink Reply by Temeraire on April 18, 2012 at 1:06pm

I've got a similar problem over here. Flashed the APM via USB, calibrated compass etc. If I reset the APM connected to my laptop via usb the C LED is flashing 6 times before it's solid. Resetting it with ESC and LiPo, the B LED is lit a few seconds and turns off, like its low powered. C is on and I can't connect via USB. Something about CRC Errors (MavLink Bad Packet). He connects until the giro calibration and terminates it with a "timeout on read - getParamList 0 5 - Your serial link isn't fast enough" and so on. Serial connection via putty is okay, but I think it can't connect to the shield. GPS has no fix, too. Reflashing the APM works fine, but with no improvement of the usb-link.

May I have to "unplug" the shield? I've no idea...

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on April 18, 2012 at 5:06pm

Telmeraire: make sure you're not using a USB hub.

• ▶ Reply

Permalink Reply by Temeraire on April 19, 2012 at 12:38am

It's directly plugged in on USB Port in my laptop. I will check, if i get a gps lock later today.

• ▶ Reply

Permalink Reply by James on April 19, 2012 at 1:42am

try different ports on the laptop.  on the netbook i use at the field only the ports on the left work, those on the right power the board, show up as a com port in the system, but are unable to connect.

 

not all usb ports are created equally :-/ 

• ▶ Reply

Permalink Reply by Temeraire on April 19, 2012 at 4:01am

I've tried the powered usb port and all the others. Seems, that i can't get a gps fix.

• ▶ Reply

Permalink Reply by Vernon Barry on April 19, 2012 at 4:36am

You have to be outside with clear sky, nothing and I mean nothing above the gps module. GPS signal is pretty weak these days.

Permalink Reply by Temeraire on April 19, 2012 at 2:00pm

Now I have flashed several times different firmware versions, and also tested the GPS again in a field. I still get no gps fix, and now the rx/tx-leds blink continuously and it is locking directly after the "Init gyro". Even if I run the board only on the battery, the blinking rx/tx-led.

• ▶ Reply

Permalink Reply by Vernon Barry on April 20, 2012 at 4:51am

APM 2.0 must hit the reset button when powered from battery. (known bug right now)

TX RX will always blink-your sending telemetry data via mavlink packets constantly

GPS is a standalone device meaning it has its own firmware so if you give it power, the blue LED on the gps blinks slow until it aquires the satelites and then goes solid on. When it's solid on, it's then sending it's coordinates via (I think binary) serial connection to the 2560.

SO no matter what firmware is on the ardupilot, the GPS works completely standalone based on it's LED. Determine if it's working from a LED standpoint and then worry about the rest of this.

 

• ▶ Reply

Permalink Reply by Darrell Burkey on February 23, 2013 at 10:15pm

I'm assuming the bug described in this thread has been dealt with given that the thread is a bit old now?

I have two APM boards here ver 2.5.1 and 2.5.2 that refuse to boot up. When I plug them in to my computer via USB the computer indicates that the port is connected with it's usual windows beep but only the C blue led comes on and stays lit. Resetting the board a few times worked a couple of times but now it's 'no go' all the time.

I think I probably damaged them when I was working out how to power servos on my camera gimbal from  UBEC rather than the APM. One of the servos was damaged by connecting to the wrong voltage and I think maybe somehow some voltage ended up on the signal line or something.

Is there some voodoo or magic that can be done to save these APMs? It's a bit expensive to replace them although I have ordered one just in case.

• ▶ Reply