[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Paparazzi-devel] datalink problem
From: |
Dirk-Willem van Gulik |
Subject: |
Re: [Paparazzi-devel] datalink problem |
Date: |
Wed, 6 Oct 2010 14:25:25 +0100 |
On 4 Oct 2010, at 16:06, Ana García Álvarez wrote:
> Dear community, I have a problem with my autopilot(tiny v2.11), and don't
> know how to solve it.
> I have the XBee Pro 2.5 modems(2.4GHz). I have configured them with the X-CTU
> sofware(baud rate to 57600, firmware: coordinator AT and end device AT, and
> finally the two have the same Pan ID).
> I use the transparent protocol(paparazzi).
> The "downlink" is perfect. I can see the movement of my aircraft in the GCS,
> the battery message, GPS info, throttle, all the messages look ok....but I
> have no "datalink", or that's what I think.
> Once I've launched a modem session, I get GPS fixed and stay in
> "holding"...but I can't launch the aircraft, or change the mode via GCS. I
> have launched the "datalink messages" and can see a "WIND" message sending
> each 10seconds, but when I try to launch, a "BLOCK" appears in the "datalink
> messages", but it isn't sent(I've been waiting for more than
> 180seconds)...and there is no activity in the console of the GCS or in the
> main paparazzi center one(nothing written like an error or so).
> Does anybody know what may happen?May I miss anything related to my
> configuration settings, the software or so on?
A quick think to try is to short Tx & Rx on the airplane side; connect 'tip',
'Hyperterm' or a similar terminal app to the station side - and then check if
characters roundtrip - i.e. echo back - or if there is sporadic corruption.
Thanks,
Dw