xbee with Mavlink 1.0

Posted by x-air71 on July 11, 2012 at 1:08pm

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

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –
Follow

Replies

  • x-air71 July 17, 2012 at 10:44pm
    Hi Rick, i will try again, hopefully this evening.
    I have teamviewer installed, so no problem for this.In case I will face the same problem it could be a solution, thanks for your availability. In case I'm not able to make the air module work again could be a good solution.
    Where do you live, in order to see if it is possible to find an appropriate timing in case of need ;-)
    I'm living in Istanbul, let's say European hour + 1

    Thanks
    Marco
    this.in
    This domain may be for sale!
  • Mike Boland July 17, 2012 at 12:22pm

    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.

  • x-air71 July 16, 2012 at 10:15pm
    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
  • x-air71 July 13, 2012 at 12:04am
    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
  • x-air71 July 12, 2012 at 10:53pm
    @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
  • Rick Stewart July 12, 2012 at 3:29pm

    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 Boland July 12, 2012 at 3:23pm

    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.

  • x-air71 July 11, 2012 at 10:25pm
    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?
  • Developer
    Michael Oborne July 11, 2012 at 3:57pm

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

  • Mike Boland July 11, 2012 at 2:21pm

    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.

This reply was deleted.