Hi,
modules.h is included in nav, so you can access any module function
with the flight plan.
Gautier
Le 03/09/2010 10:00, address@hidden a écrit :
Hi
Christophe,
Bomb
is a navigation routine and is not in main_ap.c. Not sure
if it could be a module; I will look into it.
Yes,
there are a few sensors that should be moved from main_ap.c
to modules (such as srf08, airspeed_ets, baro_ets, baro_scp,
baro_MS5534A, humid_sht,
max11040, micromag_fw, osam_imu_ugear etc). As a developer, I will
certainly help
to move them into modules in due course. We will then have a more
improved code
structure.
Cheers,
Mark
From:
address@hidden
[mailto:address@hidden] On
Behalf
Of Christophe De Wagter
Sent: Thursday, 2 September 2010 3:15 PM
To: paparazzi-devel
Subject: Re: [Paparazzi-devel] Subsystems, airframe files.
Dear Mark,
Thanks for all the updates. The splitting of
eagletree into
the baro and airspeed subsystems sound like very good options as there
are
several other baro's and airspeed sensors.
For the bomb part: do you see any option to make
it into a
module instead (and be able to remove all bomb related stuff from the
main_ap.c)? It's not part of the essential fixedwing firmware
(sensor-control-nav-actuator) and can be run at the end of the periodic
loop
(->module).
Christophe
On Wed, Sep 1, 2010 at 9:10 AM, <address@hidden>
wrote:
Just to let you all know that I successfully
converted my
"fixed wing" airframe files to the new structure.
In order to do this for my particular setup, I had to enhance the SVN
as
follows:
- create a new subsystem to support bomb.c <subsystem
name="navigation" type="bomb"/>
- separate the Eagletree airspeed sensor from the altitude sensor (I'm
only
using the airspeed sensor). To do this, I split the former subsystem
into two
parts:
<subsystem name="airspeed"
type="ets"/> and <subsystem name="baro"
type="ets"/>
These modifications were committed to the SVN.
I also updated the Wiki to reflect these changes.
FYI, Mark
-----Original Message-----
From: paparazzi-devel-bounces+mark.griffin=itu.int@nongnu.org
[mailto:paparazzi-devel-bounces+mark.griffin=itu.int@nongnu.org]
On Behalf Of Felix Ruess
Sent: Thursday, 26 August 2010 11:13 PM
To: address@hidden
Subject: Re: [Paparazzi-devel] Subsystems, airframe files.
Hi Helge,
I meant to follow up on my earlier email.
Just after I wrote the mail we implemented an automatic selection for
the actuators depending on the board (4017 for tiny2 and twog, 4015
for tiny1).
So you don't have to worry about that anymore since it is fixed in
hardware for a board anyway.
We took the definition of the control loops to use out of the general
makefile and made it a "subsystem" because not everyone is using the
standard control.
So to get the standard control loops you have to specify that
subsystem without type as you indicated below.
Cheers, Felix
On Thu, Aug 26, 2010 at 10:36 PM, Helge Walle <address@hidden>
wrote:
> Hi,
>
> I am rewriting my airframe file, and wonder about the following:
>
> Is the line
>
> <subsystem name="control"/>
>
> a replacement for
>
> <subsystem name="actuators"
type="4017"/>
>
> Thanks,
>
> Helge.
>
> _______________________________________________
> 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
|