Replies to This Discussion

DeveloperPermalink Reply by Andrew Tridgell on April 26, 2012 at 5:12pm

Hi Richard,

The red LED being on solid just means it is in bootloader mode. That LED being lit just means it is ready to receive a new firmware from your PC.

Try uploading the firmware again. The current planner versions should detect that the radio is in bootloader mode and load a new firmware. Make sure you use the latest mission planner.

Cheers, Tridge

• ▶ Reply

Permalink Reply by Richard C. on April 26, 2012 at 5:16pm

I tried multiple times & with the latest mission planner. On a whim, I changed baud to 4800 and it successfully programmed. It failed on 56k and higher. So, problem solved!

• ▶ Reply

DeveloperPermalink Reply by Andrew Tridgell on April 26, 2012 at 5:19pm

That's very strange!

Is it now working at 57600?

Cheers, Tridge

• ▶ Reply

Permalink Reply by Richard C. on April 26, 2012 at 5:58pm

Sadly, no. The firmware upgrade on ground module was successful from 1.3->1.5, but still never able to connect in APM to plane (that was the original reason I tried f/w upgrade). I'm going to keep tinkering, but starting to think I got some bum hardware

• ▶ Reply

DeveloperPermalink Reply by Andrew Tridgell on April 26, 2012 at 6:03pm

when you have it connected to your laptop, get the settings and show them here. It may be just bad eeprom settings.

Cheers, Tridge

• ▶ Reply

DeveloperPermalink Reply by Andrew Tridgell on April 26, 2012 at 6:05pm

another thing to watch out for is the tx/rx order of the cable to the APM. Try swapping the tx and rx if the red light doesn't blink when you use it on the APM.

Also, if its an APM2, then the radio will only work when the USB cable is unplugged (there is only one UART being shared between the two ports)

Cheers, Tridge

• ▶ Reply

Permalink Reply by Richard C. on April 26, 2012 at 7:35pm

I'm getting flashing green LEDs on both air and ground now, so obviously no connection. Attached are ground radio settings, unable to pull air module. Ground f/w is 1.5, last I saw, air was 1.3. Docs note f/w versions must match, though I'm not seeing a way to upgrade air unit. Is there a way to view/edit air settings over USB (since wireless isn't working) to verify it's a match? Pretty frustrated at this point, so open to try anything.

BTW, I do have the APM2.0

Attachments:

• Capture.PNG, 33 KB

• ▶ Reply

Permalink Reply by Richard C. on April 26, 2012 at 7:43pm

Also, APM 1.1.75 & ArduPlane 2.33. I verified the TX/RX cabling. RX goes to TX, TX connects to RX

• ▶ Reply

Permalink Reply by Gabriel on April 27, 2012 at 5:12pm

you need to upgrade your firmware on the Air version, means you need to buy/borrow a FTDI cable. and plug the air version into your computer and click upgrade firmware. 

• ▶ Reply

DeveloperPermalink Reply by Andrew Tridgell on April 29, 2012 at 4:32pm

Hi Richard,

As Gabriel noted, you need a FTDI cable in order to upgrade the firmware on your air module so the firmware versions match. Unfortunately there is no way to get the air module parameters without either a FTDI cable or a working link between the two radios.

Can you borrow a FTDI cable from someone?

Cheers, Tridge

• ▶ Reply