[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Paparazzi-devel] No serial communication between PC & XBee?
From: |
Alston Pike |
Subject: |
Re: [Paparazzi-devel] No serial communication between PC & XBee? |
Date: |
Thu, 18 Jun 2009 12:16:30 -0500 |
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
>
>
- Re: [Paparazzi-devel] No serial communication between PC & XBee?, Bernard Davison, 2009/06/17
- Re: [Paparazzi-devel] No serial communication between PC & XBee?,
Alston Pike <=
- Re: [Paparazzi-devel] No serial communication between PC & XBee?, Bernard Davison, 2009/06/19
- [Paparazzi-devel] Possible Solution: No serial communication between PC & XBee?, David Conger, 2009/06/19
- Re: [Paparazzi-devel] No serial communication between PC & XBee?, Bernard Davison, 2009/06/20
- Re: [Paparazzi-devel] No serial communication between PC & XBee?, Alston Pike, 2009/06/21
- Re: [Paparazzi-devel] No serial communication between PC & XBee?, Bernard Davison, 2009/06/22
- Re: [Paparazzi-devel] No serial communication between PC & XBee?, Alston Pike, 2009/06/22
- Re: [Paparazzi-devel] No serial communication between PC & XBee?, Alston Pike, 2009/06/22