I have a trouble with Xbee, it happen after the last update.

On hexa, the xbee module have blue and red light switched on, trying to connect with mission planner (57K), I see the following errors:

 in ArdupilotMega.MAVLink.readPacket() (:0) [ProgressReporterDialogue Background thread]
2012-07-11 22:44:48,062  INFO ArdupilotMega.MAVLink - Mavlink Bad Packet (crc fail) len 0 crc 65535 pkno -1 (:0) [ProgressReporterDialogue Background thread]
2012-07-11 22:44:49,264  INFO ArdupilotMega.MAVLink - MAVLINK: S wait time out btr 0 len 0 (:0) [ProgressReporterDialogue Background thread]
2012-07-11 22:44:49,264  INFO ArdupilotMega.MAVLink - MAVLink readpacket read error: System.Exception: Timeout
   in ArdupilotMega.MAVLink.readPacket() (:0) [ProgressReporterDialogue Background thread]
2012-07-11 22:44:49,264  INFO ArdupilotMega.MAVLink - Mavlink Bad Packet (crc fail) len 0 crc 65535 pkno -1 (:0) [ProgressReporterDialogue Background thread]
2012-07-11 22:44:50,480  INFO ArdupilotMega.MAVLink - MAVLINK: S wait time out btr 0 len 0 (:0) [ProgressReporterDialogue Background thread]
2012-07-11 22:44:50,480  INFO ArdupilotMega.MAVLink - MAVLink readpacket read error: System.Exception: Timeout
   in ArdupilotMega.MAVLink.readPacket() (:0) [ProgressReporterDialogue Background thread]
2012-07-11 22:44:50,480  INFO ArdupilotMega.MAVLink - Mavlink Bad Packet (crc fail) len 0 crc 65535 pkno -1 (:0) [ProgressReporterDialogue Background thread]
2012-07-11 22:44:51,682  INFO ArdupilotMega.MAVLink - MAVLINK: S wait time out btr 0 len 0 (:0) [ProgressReporterDialogue Background thread]
2012-07-11 22:44:51,682  INFO ArdupilotMega.MAVLink - MAVLink readpacket read error: System.Exception: Timeout
   in ArdupilotMega.MAVLink.readPacket() (:0) [ProgressReporterDialogue Background thread]
2012-07-11 22:44:51,682  INFO ArdupilotMega.MAVLink - Mavlink Bad Packet (crc fail) len 0 crc 65535 pkno -1 (:0) [ProgressReporterDialogue Background thread]
2012-07-11 22:44:51,682 DEBUG ArdupilotMega.MAVLink - MAv Data: len 0 btr 0 (:0) [ProgressReporterDialogue Background thread]
2012-07-11 22:44:51,682  INFO ArdupilotMega.MAVLink - 682 Start connect loop  (:0) [ProgressReporterDialogue Background thread]
2012-07-11 22:45:33,600  INFO ArdupilotMega.MainV2 - myview width 0 height 0 (:0) [Base Thread]
2012-07-11 22:45:33,600  INFO ArdupilotMega.MainV2 - this   width 160 height 27 (:0) [Base Thread]

Any idea...got lost...it was working fine...

Thanks

Marco

Views: 569

Replies to This Discussion

I did find issues like this on some updates under Windoze 7 

I resolved them by resetting permissions in the Mission Planner directory.

Now, whenever there is an update I say no, quit Mission Planner, then run it as Administrator and do the update.

No more problems.

Worth a try.

to me it looks like your xbee's ant talking to each other. ie no data

Hi Mike, in fact I have a Window7 64bit...I will try your suggestion, hope it could work.
One question: in the xbee module on the hexa, both blue and red light are on, I remeber the blue one but not the red one? do you know what the red led means?

Thanks

@Micheal, thanks for your answer...do you know what the red led means?

I believe the red LED is an RSSI indicator. It comes on whenever I open a connection to the copter.

So in Mission Planner, when connect is selected, the Red LED comes on.

So you have 2 modules.  Lets call them the Air, which is on the Hexa, and the ground module.  On the ground module do you have a green light when you power them both up?  If not they wont communicate, at least not in my experience.  When the green light goes on the ground module (RSSI) then they will talk.  If they don't talk connect them both to your computer with either USB or FTDI and use X-CTU which is a diagnostic tool from Digi.  Any module you cant query is bricked if it was working once before.  You need to un-brick it.  I am in the process of doing this right now.  I hope this helps.

Rick

@Mike: the red light in the Air module (hexa) is always on as I connect the batteries...
@Rick: the Air module does not have the usb connector....i guess i will need a special cable in order to use the tool X-CTU....
In what does consist the 'unbrick' procedure? reinstalling the firmware?

Thanks
Marco

I just did this 2 minutes ago so I thought I would write this while the process is somewhat fresh.

The un-bricking process is pretty simple, but it only works if you have 1 working xbee.

1.  Open X-CTU.

2. Load the config from the working xbee at the modem configuration tab.  Click "Read"

3. From the PC Settings tab, change the com port and baud settings to those of the "bricked" xbee

4. Check "Always Update Firmware", and click the "Write" button. 

5. What happens some time is the xbee switches back to 9600 baud.  You can test if this occurs by clicking the "Test / Query" button.  It should reply with the firmware and serial number.

6. Go back to "Modem Configuration" and change the baud rate and the "Modem VID" to match the working xbee.

If you have problems reading the configuration from the working xbee, check the "Com Port Setup" and click Test.

I hope this helps,

Rick

Hi Rick, thanks to your reply.
I will do all the tests tomorrow (and some repair work as well.....).
I will follow the procedure...Hope the xbee module could work again!

Thanks again for your time!
Let you know

Marco
Hi Rick, I've tried your procedure in order to unbrick the air module, but no success.
I can read the configuration of the 'ground' one but looks like I cannot write it in the air one, or better I can write it, then I have to switch back to 9600 baud in order to read it but the parameters look different and it is not working...
Is there any place where i could find the right firmware to upload to the air module?

Thanks
marco

Just reading through your problem, I couldn't spot the obvious so I am going to ask.

Have you unplugged the "Air" module from it's board on the Hexa and plugged it into the USB board connected to your computer to configure it with X-CTU?

You won't be able to configure it while it is in the Hexa.

Hi Mike, yes I've done it...if not no way ;-)

But it may be I've loaded the wrong firmware...?

I've read the firmware of the 'ground' module and written it to the air one...

is sending the AT commands and looks working..

I will do again tomorrow and attach the screenshots.

If you keep having issues with it, if you install Team Viewer, I can give you a hand.  Cheers,

Rick

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