Replies to This Discussion

DeveloperPermalink Reply by Adam Rivera on February 19, 2012 at 10:28am

I just had an AHA!! moment. It occurred to me that the bottom of the Xbee is just the interface board that the modem sits on top of. Just take your xbee off the interface that connects to the APM and use your USB interface board to re-program the modem from your copter. I am in the process of flashing it right now, but I am pretty confident that this will work.

Thanks,

Adam

• ▶ Reply

Permalink Reply by Don Brooks on February 19, 2012 at 10:29am

It's more likely that your copter side xbee is the one that's bricked. You'd have to pull it off the serial adapter and switch it with the ground side.

• ▶ Reply

Permalink Reply by Don Brooks on February 19, 2012 at 10:30am

seems you beat me to it. Good luck!

• ▶ Reply

DeveloperPermalink Reply by Adam Rivera on February 19, 2012 at 10:34am

Thanks for replying Don! Appreciate the help.

• ▶ Reply

Permalink Reply by Tomas Soedergren on February 19, 2012 at 10:32am

Adam,

When you first noticed telemetry stopped, did that happen during an ongoing session, or did you experience it during bootup of copter?

I have frequent boot issues where sometimes I have to do multiple restarts of the copter before booting correctly.

I think this only occurs when I have had the XBee link active. At some occations I unplugged the AC side XBee, restarted and it would boot fine. Then reconnect XBee, start AC and the link would be restored. I am not 100% about the relation between boot problems and XBee but there seems to be a correlation. I use APM2 and usually the latest firmware / MP.

• ▶ Reply

DeveloperPermalink Reply by Adam Rivera on February 19, 2012 at 10:35am

I did try to restart the APM several times... I think it was totally bricked. Testing shortly.

• ▶ Reply

Permalink Reply by Mattia Parise on March 14, 2012 at 8:29am

Adam, did you get it working? I have the same issue. I unbricked them, but the problem is that the test with the print("Serial 3") works, but APM does not work. I think the problem is that the copter's xbee does not receive anything.
Do you have any news?

• ▶ Reply

DeveloperPermalink Reply by Adam Rivera on March 14, 2012 at 8:41am

I did get them working. I had to run through the unbrick process on both modules and then make sure to set the default baud rate on each device to 54600. Once I did that I was back in business.

• ▶ Reply

Permalink Reply by Jan Schermer on March 14, 2012 at 8:42am

In newer versions of code, CLI can be activated by pressing ENTER 3x at boot. I guess whatever is getting from your XBee is triggering it? I'm not sure if this is true for all Serial ports or only the first one, but if you are able to compile your firmware then try commenting this section out (it's in GCS_Mavlink.pde if I remember correctly).

• ▶ Reply

Permalink Reply by Mattia Parise on March 14, 2012 at 9:15am

Hi Jan. It is avoiding it of course, but I can't connect to the terminal (i see only rubbish words in terminal through xbee). Another thing: if I upload the test code it is working in one way, but if I change the Xbees it does not work. I am able to compile my firmware... But what section do I have to comment?What is the purpose in doing that? Thanks.

Also I can see that the RSSI Led is working only in one XBEE...

• ▶ Reply