paparazzi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] Modem communication


From: Felix Ruess
Subject: Re: [Paparazzi-devel] Modem communication
Date: Thu, 14 Oct 2010 21:44:07 +0200

Roman,

The configuration looks good except for the
  <arg flag="-uplink" constant=""/>
I don't exactly know for what that would be needed, but you should not
need it for a standard setup like yours.

The device /dev/ttyUSB0 is also the standard device, so you can leave
that parameter out if you want.
Also you don't have to specify the modem baud rate if you are using
the default 57600 baud anyway (but it doesn't hurt either).

You don't have to manually edit your control_panel.xml, you can just
start a Data Link (and whatever else you want to run in your session)
from the tools menu, adapt the parameters in the textbox (add -s
57600) and then save that session as a new session.

Make sure your modems are configured correctly and they work outside
of paparazzi (e.g. you can see some messages in a terminal).
Your usb device should be correct if the link does not fail. (that
device should come up if you plug in the modem, check with dmesg)

Cheers, Felix

On Thu, Oct 14, 2010 at 7:55 PM, Roman Nikitin <address@hidden> wrote:
>
> Felix,
>
> thank you for the answer. I changed the code in control_panel.xml to
>
> <session name="XBee 2.4GHz">
>        <program name ="Data Link">
>                <arg flag="-d" constant="/dev/ttyUSB0"/>
>                <arg flag="-uplink" constant=""/>
>                <arg flag="-s" constant="57600"/>
>        <program/>
>        <program name ="Server">
>        <program name ="GCS">
> <session/>
>
> I have no error message any more in GCS window, but the modem are not 
> speaking to each other either. In message window don´t appear any messages.
>
> My codes in airframe file look still like this
>
> !--Communication -->
>  <subsystem name="telemetry"  type="transparent">
>  <param name="MODEM_BAUD"   value="B57600">
>  </subsystem>
>
> With baud rate of 57600. I suppose it is right. Please correct me, if I am 
> wrong.
>
> Guys, I hope you have more ideas for the problem solving. Please let me know 
> them.
>
> I am not sure that all my usb ports are active. Logically it should be the 
> case, because it is possible to flash the ap board using usb connection.
>
> It would be nice, if any could send me your own working files, including 
> control_panel and conf files. So the settings could be proved.
>
> The problem is not solved, so I am still looking for more ideas.
>
> Thank you.
>
> Regards,
>
> Roman
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: address@hidden [mailto:address@hidden Im Auftrag von Felix Ruess
> Gesendet: Montag, 11. Oktober 2010 18:11
> An: address@hidden
> Betreff: Re: [Paparazzi-devel] launchsitl, simstil, Paparazzi Center
>
> Hi Roman,
>
> you started a session, probably "Flight address@hidden".
> As you can see the link is looking for the modem under /dev/paparazzi/xbee
> And your modem is not available under that device. You can make your
> specific modem available under that name by creating an appropriate
> udev rule if you want.
> Also you started the link with "-transport xbee", but I guess you use
> transparent mode...
>
> So just make a new session for yourself with the appropriate
> parameters, I'm guessing
> .../paparazzi3/sw/ground_segment/tmtc/link  -d /dev/ttyUSB -s 57600
>
> Cheers, Felix
>
> On Mon, Oct 11, 2010 at 6:09 PM, Roman Nikitin <address@hidden> wrote:
>> Hi all,
>>
>> I am back and continue the work on my final year project. As I did stop to 
>> work on my autopilot the old system was used and all my stuff worked just 
>> perfect.
>>
>> Yesterday I did update and now I am using the current system based on 
>> subsystems. The problem I have now is that I does not have communication 
>> between the modems. I have Xbee pro (series 1) modem. The error I can see in 
>> GCS window is
>>
>> Run '/home/uav/paparazzi3/sw/ground_segment/tmtc/link  -d 
>> /dev/paparazzi/xbee -transport xbee -s 57600'
>> Run '/home/uav/paparazzi3/sw/ground_segment/tmtc/server '
>> Run '/home/uav/paparazzi3/sw/ground_segment/cockpit/gcs '
>> Failure("Error opening modem serial device : fd < 0 (/dev/paparazzi/xbee)")
>> Broadcasting on network 127.255.255.255, port 2010
>>
>> DONE (exec /home/uav/paparazzi3/sw/ground_segment/tmtc/link  -d 
>> /dev/paparazzi/xbee -transport xbee -s 57600 2>&1
>>
>> I suppose it is something wrong in the codes, but the issue can't be found. 
>> My modems are set up with baud 57600.They worked just fine with old system, 
>> I am pretty sure that no farther changes are required for new subsystem. I 
>> am using
>>
>> <!--Communication -->
>> <subsystem name="telemetry"  type="transparent">
>>  <param name="MODEM_BAUD"   value="B57600">
>> </subsystem>
>>
>> code in my airframe file.
>>
>> Any ideas what should I change to avoid the error message?
>>
>> Thank you.
>>
>> Regards,
>>
>> Roman
>>
>>
>> Roman Nikitin
>>
>> Bristol Institute of Technology
>> University of the West of England
>> Aerospace Systems Engineering
>> email: address@hidden
>> Mob.: +44 (0) 7760806643
>>
>>  please consider the environment before printing emails.
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Paparazzi-devel mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]