paparazzi-devel
[Top][All Lists]
Advanced

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

Re: [Paparazzi-devel] Altitude estimation


From: Felix Ruess
Subject: Re: [Paparazzi-devel] Altitude estimation
Date: Wed, 8 Oct 2014 21:50:52 +0200

Hi again,

Should work now in v5.2 and master. Would be great if you could test/check again...

By default there were only 8 sys_time timers available and we used them all up... upped the default available sys_time software timers to 16.

Also fixed the baro dt for ins_alt float when using an onboard baro with https://github.com/paparazzi/paparazzi/pull/848

We'll probably make a v5.2.1 maintenance release soonish, so that people not tracking the v5.2 stable branch (instead e.g. using the tarball) will also get the fixes.


Cheers, Felix

On Wed, Oct 8, 2014 at 6:23 PM, Felix Ruess <address@hidden> wrote:
Hm.. that is very very strange that does not appear to work.
I can test on my lisa_mx later tonight, but I don't have a lisa_m 2 around at the moment.

You need(ed) to define the BARO_PERIODIC_FREQUENCY, configure simply creates a makefile variable.
But to make this consistent I just pushed a commit that will add it to the commandline defines if it exists as a makefile variable so you can also use configure just like for the other frequencies.

On Wed, Oct 8, 2014 at 6:09 PM, afishindouban <address@hidden> wrote:

and if I use

    <target name="ap"   board="lisa_m_2.0">
      <configure name="LISA_M_BARO" value="BARO_MS5611_SPI"/>
      <configure name="BARO_PERIODIC_FREQUENCY" value="60"/>
      <configure name="PERIODIC_FREQUENCY" value="120"/>
      <configure name="AHRS_PROPAGATE_FREQUENCY" value="100"/>
      <configure name="AHRS_CORRECT_FREQUENCY" value="100"/>
      <define name="DEBUG"/>
    </target>

the output of complier shows BARO_PERIODIC_FREQUENCY is not set to 60, still
in 50, strange:

 PRINT_CONFIG_MSG_VALUE("USE_BARO_BOARD is TRUE, reading onboard baro: ",
BARO_BOARD)
 ^
firmwares/fixedwing/main_ap.c:110:1: note: #pragma message: Config:
PERIODIC_FREQUENCY = 120
 PRINT_CONFIG_VAR(PERIODIC_FREQUENCY)
 ^
firmwares/fixedwing/main_ap.c:111:1: note: #pragma message: Config:
NAVIGATION_FREQUENCY = 4
 PRINT_CONFIG_VAR(NAVIGATION_FREQUENCY)
 ^
firmwares/fixedwing/main_ap.c:112:1: note: #pragma message: Config:
CONTROL_FREQUENCY = 60
 PRINT_CONFIG_VAR(CONTROL_FREQUENCY)
 ^
firmwares/fixedwing/main_ap.c:117:1: note: #pragma message: Config:
TELEMETRY_FREQUENCY = 120
 PRINT_CONFIG_VAR(TELEMETRY_FREQUENCY)
 ^
firmwares/fixedwing/main_ap.c:122:1: note: #pragma message: Config:
MODULES_FREQUENCY = 120
 PRINT_CONFIG_VAR(MODULES_FREQUENCY)
 ^
firmwares/fixedwing/main_ap.c:128:1: note: #pragma message: Config:
BARO_PERIODIC_FREQUENCY = 50
 PRINT_CONFIG_VAR(BARO_PERIODIC_FREQUENCY)
 ^
firmwares/fixedwing/main_ap.c:136:1: note: #pragma message: Config:
AHRS_PROPAGATE_FREQUENCY = 100
 PRINT_CONFIG_VAR(AHRS_PROPAGATE_FREQUENCY)
 ^
firmwares/fixedwing/main_ap.c:140:1: note: #pragma message: Config:
AHRS_CORRECT_FREQUENCY = 100
 PRINT_CONFIG_VAR(AHRS_CORRECT_FREQUENCY)



--
View this message in context: http://lists.paparazziuav.org/Lisa-M-v2-Aspirin-IMU-loss-tp16142p16235.html
Sent from the paparazzi-devel mailing list archive at Nabble.com.

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel



reply via email to

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