Re: [Paparazzi-devel] No serial communication between PC & XBee?

[Alston Pike]

Right now, I've got the document hosted on my account on our college's
linux server.  You can find it at

http://www.unix.eng.ua.edu/~apike/files/Blackbird.pdf

It's pretty comprehensive of the entire project, since I was trying to
create a doc that would let people who pick up the autopilot system
after me be up and running with as little trouble as possible.  I've
left the airframe configuration to the page on the wiki, and only
covered the details of XBee configuration using the transparent
protocols.

Maybe there is something in there that will be helpful.

Alston Pike
BSME 2009
The University of Alabama
address@hidden
(706) 594-2812



2009/6/20 Bernard Davison <address@hidden>:
> Thanks Alston,
>
> At the moment I'm thinking that I have a modem configuration problem.
>
> My current setup is (Since I've burnt out one modem with the 5 volt supply
> issue and stuffed up one with a re-flash issue...)
> Aircraft: XBP24-Z7WIT-004 - Configured as endpoint AT 9600 Baud
> Ground: XBP24-BSIT-004 - Configured as coordinator AT (Not ZNet) 9600 Baud
>
> I can get serial communications working fine using the default transparent
> communications (PPRZ) when connection the FTDI cable directly to the Tiny
> v2.11.
> I have then tried to replace the cable connection with the XBees and use the
> same configuration without success.
>
> I look forward reading your doc.
>
> Cheers,
> Bernie.
>
> On 20/06/2009, at 5:21 AM, Alston Pike wrote:
>
>> I'll post a PDF file to my website later this weekend and get the link
>> posted.
>>
>> As far as power is concerned, I think the XBee modems are 3.3V, but
>> are 5V tolerant (that is, if I remember correctly).  The cables
>> included with the PPZUAV kits drive the modems off the 5V bus to keep
>> radio interference off the 3.3V line shared with the processor.  That
>> said, according the specs on Digi's website, the XBee Pro only draws
>> 294mA and the LM317 should be good for 1.5A.
>>
>> Which FTDI cable are you using?
>>
>> Alston Pike
>> BSME 2009
>> The University of Alabama
>> address@hidden
>> (706) 594-2812
>>
>>
>>
>> 2009/6/18 Bernard Davison <address@hidden>:
>>>
>>> I think I've been having similar problems combined with power supply
>>> issues... :-(
>>> First I fried one XBee unit by plugging it into the FTDI cable which I
>>> though was 3.3 volt because of the details of the item when connected to
>>> USB
>>> port. (came up as ...FTDI... 3.3v)
>>> Next I've made a power supply from the 5 volts using an LM317 power
>>> regulator but I think under load the power supply is unstable so will try
>>> again with a low drop out regulator.
>>> I think this has resulted in partial flashing of another XBee that I
>>> bought
>>> as a replacement. I hope there's a power up sequence that can be used to
>>> re-flash it. Must read the docs more thoroughly first...
>>>
>>> I'd love a copy of your config docs is you wouldn't mind.
>>>
>>> Thanks,
>>> Bernie.
>>>
>>> On 19/06/2009, at 3:16 AM, Alston Pike wrote:
>>>
>>> Initially, I found that I had a bad modem that wouldn't let me flash
>>>
>>> the firmware.  The biggest thing, however, is getting all the settings
>>>
>>> right and flashed to the modems via X-CTU.
>>>
>>> If you need anything, I've got a fairly detailed paper that I wrote to
>>>
>>> detail the installation and (some of) the configuration of the
>>>
>>> autopilot system which I can post online.
>>>
>>> Alston Pike
>>>
>>> BSME 2009
>>>
>>> The University of Alabama
>>>
>>> address@hidden
>>>
>>> (706) 594-2812
>>>
>>>
>>>
>>> 2009/6/17 Bernard Davison <address@hidden>:
>>>
>>> Hi Alston,
>>>
>>> I'm experiencing similar issues to what you have described earlier.
>>>
>>> Are you able to remember any details of what caused the problem and the
>>>
>>> solution or what I've missed and post them here?
>>>
>>> Thanks,
>>>
>>> Bernie.
>>>
>>> On 03/04/2009, at 3:10 PM, Alston Pike wrote:
>>>
>>> It will most likely be some time next week before I get a chance to get
>>> on
>>>
>>> IRC.  We're hosting an ASME conference here in Tuscaloosa this weekend
>>> and
>>>
>>> I'll be busy with that.
>>>
>>> That said, I'll be presenting what work I have completed with my plane
>>> and
>>>
>>> the amazingness of Paparazzi.
>>>
>>> AP
>>>
>>>
>>> On 4/2/09, David Buzz Carlson <address@hidden> wrote:
>>>
>>> Alston,
>>>
>>> If you have time, I can troubleshoot this with you on the IRC.
>>>
>>> Buzz
>>>
>>> Alston Pike wrote:
>>>
>>> FTDI cable works fine. I have the Flight USB setting for transparent
>>>
>>> operation using the PPRZ protocol.
>>>
>>> Interesting note... when I use the Flight - Maxstream @ 57600 option,
>>>
>>> I get some activity on the transmit & receive lights on the adapter
>>>
>>> board but when I use the transparent options, I get nothing.
>>>
>>> Alston Pike
>>>
>>> BSME 2009
>>>
>>> The University of Alabama
>>>
>>> address@hidden <mailto:address@hidden>
>>>
>>> (706) 594-2812
>>>
>>>
>>> 2009/4/2 C.KUO <address@hidden
>>>
>>> <mailto:address@hidden>>
>>>
>>>  Hi there
>>>
>>>  Have you try to use FTDI cable instead of mdoem to check if the
>>>
>>>  GCS has some reaction?
>>>
>>>  2nd thing, you use the Xbee or PPRZ for the modem? because if you
>>>
>>>  use PPRZ (which should work with you Xbee, but just no multiple
>>>
>>>  aircraft operation), then you need to use option"flight by usb
>>>
>>>  9600", and in this option, you need to change the rate to 57600
>>>
>>>  (same as your modem).
>>>
>>>  I hope this will hleps.
>>>
>>>
>>>  good luck
>>>
>>>  Chen
>>>
>>>
>>>  引述 Alston Pike <address@hidden
>>>
>>>  <mailto:address@hidden>>:
>>>
>>>
>>>     So, in the process of configuring my modems, I came to realize
>>>
>>>     that the
>>>
>>>     modem in the plane was bad and that it was part of my problems
>>>
>>>     I've been
>>>
>>>     having getting the GCS to populate. I've got a new one now,
>>>
>>>     and I'm able to
>>>
>>>     work with that modem in X-CTU.
>>>
>>>     Now that I've got the plane reassembled with the new modem in
>>>
>>>     place, I try
>>>
>>>     launching a new flight. The activity lights on the FTDI
>>>
>>>     adapter never come
>>>
>>>     on. The power LED is on, and I checked dmesg and *something* is
>>>
>>> on
>>>
>>>     ttyUSB0. My GCS still will not populate.
>>>
>>>     Here's everything I know:
>>>
>>>     Ground station modem:
>>>
>>>     XBee Pro Series 2.
>>>
>>>     Configured with ZNet 2.5 Configurator AT function set
>>>
>>>     (Firmware 1047)
>>>
>>>     PAN ID: 1337
>>>
>>>     Destination (DH) : 13A200
>>>
>>>     Destination (DL) : 402C135B
>>>
>>>     Serial (SH) : 13A200
>>>
>>>     Serial (SL) : 404BA6E6
>>>
>>>     Baud : 57600
>>>
>>>     Plane modem:
>>>
>>>     XBee Pro Series 2
>>>
>>>     Configured with ZNet 2.5 Router/End Device AT function set
>>>
>>>     (Firmware 1247)
>>>
>>>     PAN ID : 1337
>>>
>>>     Destination (DH) : 13A200
>>>
>>>     Destination (DL) : 404BA6E6
>>>
>>>     Serial (SH) : 13A200
>>>
>>>     Serial (SL) : 402C135B
>>>
>>>     Baud : 57600
>>>
>>>     dmesg:
>>>
>>>     [ 552.804394] usb 1-2: new full speed USB device using
>>>
>>>     uhci_hcd and address
>>>
>>>     2
>>>
>>>     [ 550.733249] usb 1-2: configuration #1 chosen from 1 choice
>>>
>>>     [ 550.735160] ftdi_sio 1-2:1.0: FTDI USB Serial Device
>>>
>>>     converter detected
>>>
>>>     [ 550.735202]
>>>
>>>     /build/buildd/linux-2.6.24/drivers/usb/serial/ftdi_sio.c:
>>>
>>>     Detected FT232RL
>>>
>>>     [ 550.735314] usb 1-2: FTDI USB Serial Device converter now
>>>
>>>     attached to
>>>
>>>     ttyUSB0
>>>
>>>     ivyprobe:
>>>
>>>     Broadcasting on network 127.255.255.255, port 2010
>>>
>>>     Paparazzi server connected from localhost
>>>
>>>     Paparazzi server subscribes to '^(.*) ALIVE'
>>>
>>>     Paparazzi server subscribes to '^(.*) PPRZ_MODE'
>>>
>>>     Paparazzi server subscribes to '^([^ ]*) +(MOVE_WAYPOINT(
>>>
>>> .*|$))'
>>>
>>>     Paparazzi server subscribes to '^([^ ]*) +(DL_SETTING( .*|$))'
>>>
>>>     Paparazzi server subscribes to '^([^ ]*) +(JUMP_TO_BLOCK(
>>>
>>> .*|$))'
>>>
>>>     Paparazzi server subscribes to '^([^ ]*) +(RAW_DATALINK( .*|$))'
>>>
>>>     Paparazzi server subscribes to '^([^ ]*) +([^ ]*)
>>>
>>>     +(AIRCRAFTS_REQ.*)'
>>>
>>>     Paparazzi server subscribes to '^([^ ]*) +([^ ]*)
>>>
>>> +(CONFIG_REQ.*)'
>>>
>>>     Link connected from localhost
>>>
>>>     Link subscribes to '^([^ ]*) +(DGPS_RAW( .*|$))'
>>>
>>>     Link subscribes to '^([^ ]*) +(ACINFO( .*|$))'
>>>
>>>     Link subscribes to '^([^ ]*) +(MOVE_WP( .*|$))'
>>>
>>>     Link subscribes to '^([^ ]*) +(WIND_INFO( .*|$))'
>>>
>>>     Link subscribes to '^([^ ]*) +(SETTING( .*|$))'
>>>
>>>     Link subscribes to '^([^ ]*) +(BLOCK( .*|$))'
>>>
>>>     Link subscribes to '^([^ ]*) +(BOOZ2_FMS_COMMAND( .*|$))'
>>>
>>>     Link subscribes to '^([^ ]*) +(HITL_UBX( .*|$))'
>>>
>>>     Link subscribes to '^([^ ]*) +(HITL_INFRARED( .*|$))'
>>>
>>>     Link subscribes to '^([^ ]*) +(FORMATION_SLOT( .*|$))'
>>>
>>>     Link subscribes to '^([^ ]*) +(FORMATION_STATUS( .*|$))'
>>>
>>>     Link subscribes to '^([^ ]*) +(JOYSTICK_RAW( .*|$))'
>>>
>>>     Link subscribes to '^([^ ]*) +(COMMANDS_RAW( .*|$))'
>>>
>>>     And finally, my control_panel.xml:
>>>
>>>     <control_panel name="paparazzi control panel">
>>>
>>>     <section name="variables">
>>>
>>>     <variable name="downlink_serial_port" value="/dev/ttyUSB0"/>
>>>
>>>     <variable name="fbw_serial_port" value="/dev/ttyS1"/>
>>>
>>>     <variable name="ap_serial_port" value="/dev/ttyS0"/>
>>>
>>>     <variable name="ivy_bus" value="127:2010"/>
>>>
>>>     <variable name="map" value="muret_UTM.xml"/>
>>>
>>>     <variable name="flight_plan" value="flight_plans/muret1.xml"/>
>>>
>>>     </section>
>>>
>>>     <section name="programs">
>>>
>>>     <program name="Server" command="sw/ground_segment/tmtc/server">
>>>
>>>     <arg flag="-b" variable="ivy_bus"/>
>>>
>>>     </program>
>>>
>>>     <program name="Data Link" command="sw/ground_segment/tmtc/link">
>>>
>>>     <arg flag="-b" variable="ivy_bus"/>
>>>
>>>     </program>
>>>
>>>     <program name="GCS" command="sw/ground_segment/cockpit/gcs">
>>>
>>>     <arg flag="-b" variable="ivy_bus"/>
>>>
>>>     </program>
>>>
>>>     <program name="Flight Plan Editor"
>>>
>>>     command="sw/ground_segment/cockpit/gcs -edit">
>>>
>>>     </program>
>>>
>>>     <program name="Messages"
>>>
>>>     command="sw/ground_segment/tmtc/messages">
>>>
>>>     <arg flag="-b" variable="ivy_bus"/>
>>>
>>>     </program>
>>>
>>>     <program name="Settings"
>>>
>>>     command="sw/ground_segment/tmtc/settings">
>>>
>>>     <arg flag="-b" variable="ivy_bus"/>
>>>
>>>     </program>
>>>
>>>     <program name="Log Plotter" command ="sw/logalizer/plot"/>
>>>
>>>     <program name="Real-time Plotter" command
>>>
>>>     ="sw/logalizer/plotter"/>
>>>
>>>     <program name="Log File Player" command="sw/logalizer/play">
>>>
>>>     <arg flag="-b" variable="ivy_bus"/>
>>>
>>>     </program>
>>>
>>>     <program name="Simulator" command="sw/simulator/launchsitl">
>>>
>>>     <arg flag="-b" variable="ivy_bus"/>
>>>
>>>     </program>
>>>
>>>     <program name="Hardware in the Loop"
>>>
>>>     command="sw/simulator/simhitl">
>>>
>>>     <arg flag="-fbw" variable="fbw_serial_port"/>
>>>
>>>     <arg flag="-ap" variable="ap_serial_port"/>
>>>
>>>     </program>
>>>
>>>     <program name="Environment Simulator"
>>>
>>> command="sw/simulator/gaia">
>>>
>>>     <arg flag="-b" variable="ivy_bus"/>
>>>
>>>     </program>
>>>
>>>     <program name="Http Server"
>>>
>>> command="sw/ground_segment/tmtc/boa"/>
>>>
>>>     </section>
>>>
>>>     <section name="sessions">
>>>
>>>     <session name="Flight address@hidden">
>>>
>>>     <program name="Data Link">
>>>
>>>     <arg flag="-d" constant="/dev/ttyUSB0"/>
>>>
>>>     </program>
>>>
>>>     <program name="Server"/>
>>>
>>>     <program name="GCS"/>
>>>
>>>     </session>
>>>
>>>     <session name="Flight address@hidden">
>>>
>>>     <program name="Data Link">
>>>
>>>     <arg flag="-d" constant="/dev/ttyUSB0"/>
>>>
>>>     <arg flag="-transport" constant="xbee"/>
>>>
>>>     <arg flag="-s" constant="57600"/>
>>>
>>>     </program>
>>>
>>>     <program name="Server"/>
>>>
>>>     <program name="GCS"/>
>>>
>>>     </session>
>>>
>>>     <session name="Flight USB">
>>>
>>>     <program name="Data Link">
>>>
>>>     <arg flag="-d" constant="/dev/ttyUSB0"/>
>>>
>>>     <arg flag="-transport" constant="pprz"/>
>>>
>>>     <arg flag="-uplink" constant=""/>
>>>
>>>     <arg flag="-s" constant="57600"/>
>>>
>>>     </program>
>>>
>>>     <program name="Server"/>
>>>
>>>     <program name="GCS"/>
>>>
>>>     </session>
>>>
>>>     ... the rest is as-is from when I downloaded the CVS.
>>>
>>>     I can send my airframe config file later if it would help.
>>>
>>>     Confused,
>>>
>>>     Alston Pike
>>>
>>>     BSME 2009
>>>
>>>     The University of Alabama
>>>
>>>     address@hidden <mailto:address@hidden>
>>>
>>>     (706) 594-2812
>>>
>>>
>>>
>>>
>>>  Dr C.KUO
>>>
>>>  Aerospace Engineering, MEng
>>>
>>>  Mechanical Engineering, PhD
>>>
>>>  Research Associate
>>>
>>>  Department of Materials Science and Engineering
>>>
>>>  Saarland University
>>>
>>>  Campus Dudweiler, Beethovenstrasse
>>>
>>>  66125 Saarbr?ken
>>>
>>>
>>>
>>>  _______________________________________________
>>>
>>>  Paparazzi-devel mailing list
>>>
>>>  address@hidden <mailto: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
>>>
>>>
>>>
>>> --
>>>
>>> Alston Pike
>>>
>>> BSME 2009
>>>
>>> The University of Alabama
>>>
>>> address@hidden
>>>
>>> (706) 594-2812 _______________________________________________
>>>
>>> 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
>>>
>>>
>>> _______________________________________________
>>> 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
>