[Top][All Lists]

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

Re: [Paparazzi-devel] Telemetry Over WiFi, through Panda Board

From: Gautier Hattenberger
Subject: Re: [Paparazzi-devel] Telemetry Over WiFi, through Panda Board
Date: Mon, 17 Jun 2013 10:13:11 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12

Hello Cameron,

Le 17/06/2013 09:07, Cameron Lee a écrit :

I'm looking into sending telemetry over WiFi using an embedded system on the aircraft such as the Panda Board, Beagle Board, a Gumstick Overo, or something similar. Specifically, I have a a Panda Board that listen's to the TWOG's UART output and want to send this data to the GCS over WiFi. Right now I only care about the one direction (downlink, aka telemetry, aka plane to ground). 

I'm looking at some code that I think does something similar in both software/airborne/fms and software/airborne/firmwares/beth. I've got a few questions though:

1. What does FMS stand for?
Flight Management System -> a really stupid name for this, we should change it if you want my opinion
2. What's the difference between overo_gcs_com.c and fms_gs_com.c? They seem like they do similar things. In particular, what's the difference between stuff in the fms folder and the stuff in the beth folder?
My colleague was working on this at the time of the Lisa/L. I forgot what the difference is. Probably not that much as you said.  You should search the makefiles in conf/firmwares, but you'll find which one are supposed to be compiled together.
3. I see GCS mentioned in many places in the code. For example: GCS_PORT. Is this for the telemetry, where data is sent to the ground segment including the GCS, but possibly also the messages agent and others? Or is this for datalink where data is sent from the GCS to control the plane? Or maybe both.
It was bi-directional telemetry/datalink over UDP if I recall correctly.
4. Does the existing code talk to the autopilot over UART? I don't see where to define which tty port this would be done on, so I'm wondering if maybe this isn't how it works.
No it was mainly using SPI link between MCU (stm32f1) and Overo board. Opening an UART should be easier...




Paparazzi-devel mailing list

reply via email to

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