paparazzi-devel
[Top][All Lists]
Advanced

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

Re: [Paparazzi-devel] Viewing BMP085 messages and fusion with GPS altitu


From: Felix Ruess
Subject: Re: [Paparazzi-devel] Viewing BMP085 messages and fusion with GPS altitude
Date: Wed, 2 May 2012 12:54:26 +0200

As a hack to use the baro on lisa/m for fixedwings right now, you
could use conf/modules/baro_board.xml and add what is needed for fw
baro in sw/airborne/boards/lisa_m/baro_board.[ch]

On Wed, May 2, 2012 at 10:32 AM, Felix Ruess <address@hidden> wrote:
> Hi,
>
> There is no I2C0 on Lisa/M, use I2C1 or I2C2, see
> http://paparazzi.enac.fr/wiki/Lisa/M#Pinout
>
> These sensor modules were only meant as payloads (to log data, etc.).
> And currently it's more the proper code that's missing and not
> documentation... we should get rid of estimator.c, make a proper baro
> interface, etc...
> Pull requests always welcome ;-)
>
> Cheers, Felix
>
> On Tue, May 1, 2012 at 5:15 AM, Chris Wozny <address@hidden> wrote:
>> All,
>>
>> I'm having trouble showing messages for the BMP085 on the latest pull of
>> dev. When I try and compile, I get the following error:
>>
>> mcu_periph/i2c.c: In function 'i2c0_init':
>> mcu_periph/i2c.c:9: warning: implicit declaration of function 'i2c0_hw_init'
>> mcu_periph/i2c.c:9: warning: nested extern declaration of 'i2c0_hw_init'
>> ...
>> CC /home/woz/paparazzi/var/MV2_LisaM_2/ap/modules/sensors/baro_bmp.o
>> LD /home/woz/paparazzi/var/MV2_LisaM_2/ap/ap.elf
>> /home/woz/paparazzi/var/MV2_LisaM_2/ap/mcu_periph/i2c.o: In function
>> `i2c0_init':
>> /home/woz/paparazzi/sw/airborne/mcu_periph/i2c.c:9: undefined reference to
>> `i2c0_hw_init'
>> collect2: ld returned 1 exit status
>> make[1]: *** [/home/woz/paparazzi/var/MV2_LisaM_2/ap/ap.elf] Error 1
>> make[1]: Leaving directory `/home/woz/paparazzi/sw/airborne'
>> make: *** [ap.compile] Error 2
>> make: Leaving directory `/home/woz/paparazzi'
>>
>>
>> I've got the following configuration:
>>
>> <firmware name="fixedwing">
>>   ...
>>   <target name="ap" board="lisa_m_2.0">
>>      <define name="USE_I2C0"/>
>>      <define name="BMP_I2C_DEV" value="i2c0"/>
>>      <define name="SENSOR_SYNC_SEND"/>
>>   </target>
>>   ...
>>   <subsystem name="i2c"/>
>> </firmware>
>> <modules>
>>   <load name="baro_bmp.xml"/>
>> </modules>
>>
>>
>> I've seen that in the past there have been issues with i2c0, is this a
>> continuation of that? Also, when I try and add the BARO_BMP85 messages to my
>> telemetry configuration, I get the following error:
>>
>> firmwares/fixedwing/main_ap.c: In function 'reporting_task':
>> firmwares/fixedwing/main_ap.c:404: warning: implicit declaration of function
>> 'PERIODIC_SEND_BARO_BMP85'
>> firmwares/fixedwing/main_ap.c:404: warning: nested extern declaration of
>> 'PERIODIC_SEND_BARO_BMP85'
>> firmwares/fixedwing/main_ap.c:404: error: 'PprzTransport' undeclared (first
>> use in this function)
>> firmwares/fixedwing/main_ap.c:404: error: (Each undeclared identifier is
>> reported only once
>> firmwares/fixedwing/main_ap.c:404: error: for each function it appears in.)
>> firmwares/fixedwing/main_ap.c:404: error: 'UART2' undeclared (first use in
>> this function)
>> make[1]: ***
>> [/home/woz/paparazzi/var/MV2_LisaM_2/ap/firmwares/fixedwing/main_ap.o] Error
>> 1
>> make[1]: Leaving directory `/home/woz/paparazzi/sw/airborne'
>> make: *** [ap.compile] Error 2
>> make: Leaving directory `/home/woz/paparazzi'
>>
>> I think there needs to be a little more documentation as to the use of
>> BMP085 and/or barometers for fusion with GPS altitude (why are there two
>> separate defines?) as the only airframe which uses it on the repository is
>> Martin's funjetmm.xml. I'd love to update the wiki with the info I will
>> receive for replies from this thread.
>>
>> Best,
>> Chris
>>
>> _______________________________________________
>> 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]