|Subject:||Re: [Paparazzi-devel] Hand testing, GCS for Lisa M2|
|Date:||Wed, 14 Nov 2012 23:46:27 +0100|
Thank you for replying, here is the additional information you requested.
We are using a transparent telemetry.
We are not using XBees quite yet, we are only directly connecting the Lisa to the PC via USB (baud rate 57600).
We aren't attaching any other peripherals to the Lisa at this point. It did however come with an Asperin 2.1 built in.
We know our USB port is working at some point because we are able to upload to the Lisa. The 1Hz Red indicator blinks post-upload.
When we hit this Execute the following commands are executed and a blank GCS is displayed:
Run '/home/uav/paparazzi/sw/ground_segment/tmtc/link -d /dev/ttyS0 -s 57600'
Run '/home/uav/paparazzi/sw/ground_segment/tmtc/server '
Run '/home/uav/paparazzi/sw/ground_segment/cockpit/gcs '
There are no other errors or commands that are executed now. (The only one we had before was about /dev/ttyUSB0, and our usb port is /dev/ttyS0 so we switched those in the config files).
I have attached the airframe, flight plan, settings, radio, and telemetry files we are using. Also attached are is the config file and the control panel file. Our A/C is called MYAC.
Here is the hardware we are working towards implementing:
* Spektrum DSM2 Remote Receiver [SPM9545]
* (2) XBee 18468-XBee Pro 2 wireless modules attached to sparkfund breakout boards.
* u-Blox GS407
* Lisa M/2.0 with Asperin 2.1 IMU.
Thanks again for the help so far. Please let us know if there is anything else you need.
~DanOn Mon, Nov 12, 2012 at 11:28 PM, Stephen Dwyer <address@hidden> wrote:
Could you clarify a few more things about your setup?
What telemetry subsystem type are you using? (XBee API or transparent?
Should be transparent with the above session datalink setting,
assuming it hasn't been modified.)
Are you using XBees during this test or connecting directly to the
computer with a serial line?
Do you have more details on your hardware setup? Are you sure the
tx/rx lines are not reversed anywhere?
What baud rates to you have set on the modems (if any) and the
autopilot? (Do they match the the session datalink setting i.e.
Does the link agent fail at startup with an error? Or appear to be
Some good checks include:
If you are using XBees or another radio modem, hook the usb-serial
adapter directly to the autopilot serial port (be aware of voltage
level limitations) and see if it works without radio modems. Verify
the tx-rx lines are connected correctly.
If you have a usb-serial adapter or radio modem board with rx and tx
indicator lights, make sure you see some activity on these.
If you are confident serial data is getting to the computer, you can
perhaps try opening the serial port with the correct settings in a
terminal program of some sort (screen, coolterm, etc etc) and see if
anything comes through (you should see a bunch of binary i.e. junk
data coming through at a fairly high rate).
It is always helpful to attach relevant configuration files (i.e.
airframe file) and note which paparazzi version you are using. (Run
./paparazzi_version from the paparazzi main directory, or check the
first part of the output after building an airframe in Paparazzi
Hope that helps.
On Mon, Nov 12, 2012 at 4:44 PM, ustuav <address@hidden> wrote:
> Hey everyone,
> We are currently trying to setup a hand test for the first time on our Lisa
> M/2. We have configured the A/C and airframe files for our equipment.
> Here are the steps we are taking:
> * Select Target > ap
> * Clean, Build, then Upload.
> * Select Session > Flight address@hidden
> * Execute
> Our GCS pops up with no flight controls (we are using fixedwing_basic.xml
> settings file).
> We are unable to launch or receive any data from our autopilot.
> Can anyone outline the steps that need to be taken in order to receive data
> from the Lisa? Is there any additional configurations that need to be done
> for us to setup a hand test?
> Dan & the UST-UAV dev team
> Paparazzi-devel mailing list
Paparazzi-devel mailing list
Paparazzi-devel mailing list
|[Prev in Thread]||Current Thread||[Next in Thread]|