I am hoping someone can help me with this...
I have my APM board hooked up to the GPS, magnetometer, XBee and groundstation software. I have connected using my XBee com port at 57600 and everything seems to be working ok, I get what seems to be very good IMU feedback on the HUD and GPS position updates... and I always say "don't fix what ain't broke"
However.... when I look at the console part of the Mission Planner application, there are a bunch of messages about Mavlink Bad Packets being displayed as follows :
Mavlink Bad Packet (crc fail) len 45 crc 61283 pkno 32
Olost 16 pkts 81
20/01/2012 00:04:33 action received:
Request stream MAV_DATA_STREAM_POSITION at 3 hz : currently 0
Ylost 60 pkts 83
Mavlink Bad Packet (crc fail) len 109 crc 25766 pkno 27
qMavlink Bad Packet (crc fail) len 45 crc 10082 pkno 32
ZZlost 65 pkts 88
Mavlink Bad Packet (crc fail) len 45 crc 37560 pkno 32
]lost 107 pkts 91
Mavlink Bad Packet (crc fail) len 45 crc 21200 pkno 32
Elost 149 pkts 94
'`lost 191 pkts 96
Mavlink Bad Packet (crc fail) len 109 crc 36964 pkno 27
BNMavlink Bad Packet (not addressed to this MAV) got 227 45 vs 1 1
BCI?Wlost 196 pkts 101
Mavlink Bad Packet (crc fail) len 45 crc 42789 pkno 32
lost 238 pkts 104
Mavlink Bad Packet (crc fail) len 45 crc 59556 pkno 32
I am now wondering whether this is normal behavior of if I am missing messages and it is affecting the efficiency of my telemetry feedback... perhaps this can be sorted out by a firware update or something else I am missing.
The XBee modules themselves work 100% when wired in loopback and also fine when running the com port test scetch, I have also used then to transmit large amounts of data without using the APM and had no problems so I doubt it is that.
Has anyone else noticed these messages.
I can post the actual HEX data of the messages or even the logic timings from my osciloscope/logic analyser if that would help...
Thanks in Advance for any help...