|Subject:||Re: [Paparazzi-devel] GCS problem|
|Date:||Wed, 6 Jul 2011 16:17:59 +0000|
I am using the Xbee in xbee_api mode.
In annex follows my airframe file.
> Date: Wed, 6 Jul 2011 09:26:55 +0200
> From: address@hidden
> To: address@hidden
> Subject: Re: [Paparazzi-devel] GCS problem
> Hi Pedro,
> I'm also guessing you are using the XBee modems in transparent serial
> mode (using the telemetry_transparent subsystem in your airframe
> This means you should NOT be using the "Flight address@hidden"
> session, but the "Flight address@hidden" session! The former one is
> for using the XBees in API mode as the name already suggests.
> The "Flight address@hidden" also already defaults to /dev/ttyUSB0 as
> device, which is the correct one most of the time (plugged first) as
> Chris already said.
> Cheers, Felix
> P.S. I think sending one message in such a short time should normally
> be enough ;-)
> On Wed, Jul 6, 2011 at 2:45 AM, Chris Gough
> <address@hidden> wrote:
> > Hi Pedro,
> > The GCS is black until it starts receiving messages. Usually this is
> > only a brief moment as it boots up, but if there is a problem with the
> > data link it stays black. You can use the "messages" tool to see what
> > (if anything) is coming down the data link. I expect the messages tool
> > will confirm that you are not getting any messages.
> > The error you mentioned is a good hint why you haven't received any
> > messages: because the system is trying to use a modem that isn't there
> > (at /dev/paparazzi/xbee). You have two ways to fix it: either put the
> > modem where the system is looking, or tell it to look where the modem
> > actually is. Either approach should work, but you should probably try
> > first "looking where the modem is".
> > Mounting the modem at specific place (such as /dev/paparazzi/xbee)
> > involves editing udev rules (as described by Felix last month, edit
> > 10-paparazzi.rules and install it in /etc/udev/rules.d/, etc.). This
> > is a good solution because it protects your configuration from random
> > changes (e.g. caused by plugging different serial devices into your
> > computer, or plugging things in a different order, etc). But you
> > should try the quick and dirty solution first to check everything's
> > working.
> > If you plug your modem in and then run dmesg, you will see a line
> > telling you where the modem was mounted by default (e.g.
> > /dev/ttyUSB0). It might mount it differently next time (for example,
> > if you plugged in something like an ftdi cable first, that may be on
> > /dev/ttyUSB0 already so your modem may get mounted on /dev/ttyUSB1...
> > or if you change your udev configuration by adding a rule about where
> > that device should be mounted). Whatever, see where it is mounted
> > right now and then tell your system to use that modem (instead of
> > /dev/paparazzi/xbee). This is easy, just start your session in the
> > paparazzi center, then change the data link to use "-d /dev/ttyUSB0"
> > (or wherever your modem is) instead of "-d /dev/paparazzi/xbee".
> > Restart the data link and everything should work! (check out the GCS).
> > If that fixed it, save the session so it starts with "-d /dev/ttyUSB0"
> > next time. Make a note to come back and fix your udev rules later,
> > first have a play with your system and check everything isn working as
> > you expected.
> > Chris Gough
> > On Wed, Jul 6, 2011 at 4:48 AM, Pedro Andrade <address@hidden> wrote:
> >> Hi world,
> >> I'm with one problem at the GCS and datalink. I use the autopilot Lisa/L
> >> with IMU aspirin and modem XBee Pro S2 (B57600).
> >> Firstly I would like to know which session I will use, "Flighit
> >> address@hidden" or "Flighit address@hidden".
> >> When I use "Flighit address@hidden" then the error happens:
> >> Failure("Error opening modem serial device : fd < 0 (/dev/paparazzi/xbee)")
> >> and then, the GCS opens, but don't opens the intruments of the navegation.
> >> At annex follows a picture of the GCS wiht the problem.
> >> Cheers.
> >> _______________________________________________
> >> Paparazzi-devel mailing list
> >> address@hidden
> >> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
> > --
> > .
> > _______________________________________________
> > Paparazzi-devel mailing list
> > address@hidden
> > https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
> Paparazzi-devel mailing list
Description: Text Data
|[Prev in Thread]||Current Thread||[Next in Thread]|