paparazzi-devel
[Top][All Lists]
Advanced

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

Re: [Paparazzi-devel] What setting I should to use?


From: Luiz Flavio Felizardo
Subject: Re: [Paparazzi-devel] What setting I should to use?
Date: Fri, 19 Aug 2011 17:55:06 -0300

Sending this message just to make it clear that thanks to Felix I was able to identify the problem and get my telemetry and gcs working....
After hours of chatting on IRC, and heaps of attempts we finally discovered that the problem was:

The wires connecting the XBee modem to the Lisa Board were connected wrong...

The right settings should be the UART data out from XBEE connected to the Rx of the LISA and vice versa! (they were switched and it took us about a month to finally realize that) I hope this will help someone in the future with the same problem ^^

I know rookie mistake, but believe me, it was the engineers fault...

2011/8/19 Felix Ruess <address@hidden>
Hi Helge,

Mostly a subsystem is a part offering a specific functionality with a
defined interface and can have multiple different implementations.
On the technical side subsystems are basically just a convenient way
to pack certain parts of the code into makefiles and add a few
configuration options to them. (See conf/autopilot/subsystems/...)
So these replaced the old raw makefile section in the airframe file.
This makes it easier to put an airframe file together and also allows
us to change the code and move/rename files behind the scenes without
breaking everyones airframe files.

About modules: http://paparazzi.enac.fr/wiki/Modules
The modules allow to add new code in a flexible way with
initialization, periodic and event functions without modifying the
main AP loop.
Ha, I guess the first sentence I wrote could equally be applied to
some of the modules.

So the difference is that with subsystems you "package" some of the
"normal" code and you have to explicitly call the functions (e.g.
control loops) from the main ap loop. This gives you tighter control
over what gets called when.
The event and periodic functions of the modules get called at the end
of event_task_ap and periodic_task_ap respectively.

This means that modules are perfect to add stuff like extra sensors,
but not so much for e.g. estimation and control where you want to
exactly control when and in what order things happen.

But you can also wrap some subsystem code as a modules (e.g.
infrared), or the other way round (e.g. imu_ppzuav).
As you can see with the imu_ppzuav module it also still expects a
direct ImuEvent call from main_ap, so you could say it's not a "pure"
module.

Hope this sheds some light on the differences and similarities.

Cheers, Felix

On Thu, Aug 18, 2011 at 10:32 AM, Helge Walle <address@hidden> wrote:
> Hi Felix,
>
> Please forgive me for breaking into this thread. In your explanation, could
> you please also write a few words about the basic difference between
> subsystems and modules?  For the sensors, are subsystems using the same code
> as modules?
>
> Thanks,
> Helge.
>
>
> 2011/8/18 Felix Ruess <address@hidden>
>>
>> Hi Blake,
>>
>> The most important file is the airframe file. It describes what
>> firmware, sensors, algorithms, etc. you want to use and also holds
>> your configuration parameters for these subsystems.
>>
>> The settings file describes which settings you will be able to tune
>> while the autopilot is running. (With the settings tool or the
>> settings tab in the GCS). As changes only occur in RAM, you can save
>> the settings to you airframe file (or use the new permanent settings
>> feature).
>> So you basically could have an empty settings file, but wouldn't be
>> able to e.g. tune the control loops in flight.
>>
>> I'm not sure what you are referring to with ahrs file...
>>
>> So it looks like you are still on some older version and you didn't
>> add a ahrs subsystem to the airframe file, e.g. dcm:
>>  <firmware name="fixedwing">
>>    <target name="ap" board="your_board">
>>    ...
>>    <subsystem name="ahrs" type="dcm"/>
>>  </firmware>
>>
>> Probably easiest if you just post your airframe file if you still have
>> troubles...
>>
>> Cheers, Felix
>>
>>
>> On Mon, Aug 15, 2011 at 9:43 PM, Blake Chambers <address@hidden> wrote:
>> > Felix,
>> > I was originally getting both sets of errors.  I commented out
>> > the imu_overrun, imu_health, renorm_sqrt_count lines.  I have attached a
>> > .jpg of what I have now.
>> > I don't understand what needs to be in the settings file, or some conf
>> > file,
>> > or the ahrs file that allows this all to work.  Can you explain this
>> > architecture a bit?
>> >
>> > Respectfully,
>> > Blake J. W. Chambers
>> > MIT '13 Aero/Astro Department
>> > Phi Kappa Theta
>> > Phone: (617) 819-4021
>> >
>> >
>> >
>> > On Mon, Aug 15, 2011 at 2:02 PM, Felix Ruess <address@hidden>
>> > wrote:
>> >>
>> >> Blake,
>> >> You have to be a bit more specific about your setup and errors... are
>> >> you using the imu_ppzuav module or subsystem? Which ahrs subsystem are
>> >> you using?
>> >>
>> >> So when using the current settings file, what errors do you get?
>> >>
>> >> If you are getting errors about imu_overrun, imu_health,
>> >> renorm_sqrt_count then please update from master or simply delete them
>> >> from your settings file.
>> >> If you get errors about ins_[pitch|roll]_neutral, then you are missing
>> >> an ahrs subsystem (or using one that doesn't have this defined).
>> >> The imu subsystem/module just grabs the sensor data and you have to
>> >> choose an ahrs subsystem to actually compute the attitude from that.
>> >>
>> >> Felix
>> >>
>> >> On Mon, Aug 15, 2011 at 7:24 PM, Blake Chambers <address@hidden>
>> >> wrote:
>> >> > Felix,
>> >> > I am using a imu_ppzuav that is modified to use the l3g4200
>> >> > gyroscopes.
>> >> > Respectfully,
>> >> > Blake J. W. Chambers
>> >> > MIT '13 Aero/Astro Department
>> >> > Phi Kappa Theta
>> >> > Phone: (617) 819-4021
>> >> >
>> >> >
>> >> >
>> >> > On Mon, Aug 15, 2011 at 12:55 PM, Felix Ruess <address@hidden>
>> >> > wrote:
>> >> >>
>> >> >> Blake,
>> >> >> what I wrote still applies to imu_health and renorm_sqrt_count as
>> >> >> well, these are just used in the ahrs_dcm subsystem.
>> >> >> There are only ins_roll_neutral and ins_pitch_neutral in the ins
>> >> >> section of your settings file if you are using a current version.
>> >> >>
>> >> >> So this settings file is for fixedwing firmware with an IMU. What
>> >> >> imu/ahrs/ins subsystem or module are you using?
>> >> >>
>> >> >> Cheers, Felix
>> >> >>
>> >> >> On Mon, Aug 15, 2011 at 6:42 PM, Blake Chambers <address@hidden>
>> >> >> wrote:
>> >> >> > Felix,
>> >> >> > Actually, it is not just the imu_overrun setting.  I am using the
>> >> >> > tuning_ins.xml, and everything in the ins section is causing the
>> >> >> > "not
>> >> >> > declared" error.
>> >> >> > Respectfully,
>> >> >> > Blake J. W. Chambers
>> >> >> > MIT '13 Aero/Astro Department
>> >> >> > Phi Kappa Theta
>> >> >> > Phone: (617) 819-4021
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On Mon, Aug 15, 2011 at 11:55 AM, Felix Ruess
>> >> >> > <address@hidden>
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> Hi Blake,
>> >> >> >>
>> >> >> >> if you still get the same error (imu_overrun not declared), you
>> >> >> >> are
>> >> >> >> not using the current tuning_ins.xml settings file from the
>> >> >> >> master
>> >> >> >> branch.
>> >> >> >> Current version of the master branch does not contain this
>> >> >> >> setting:
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> https://github.com/paparazzi/paparazzi/blob/master/conf/settings/tuning_ins.xml
>> >> >> >>
>> >> >> >> So the entries in your settings.xml file(s) basically just let
>> >> >> >> you
>> >> >> >> set
>> >> >> >> parameters, etc. by directly modifying variables (or call
>> >> >> >> handlers).
>> >> >> >> You are getting this error because you settings file still
>> >> >> >> contains
>> >> >> >> imu_overrun, but you don't have an imu subsystem that has that
>> >> >> >> variable.
>> >> >> >>
>> >> >> >> Cheers, Felix
>> >> >> >>
>> >> >> >>
>> >> >> >> On Mon, Aug 15, 2011 at 1:39 AM, Blake Chambers
>> >> >> >> <address@hidden>
>> >> >> >> wrote:
>> >> >> >> > I am still having the same compiling problem.  I am using
>> >> >> >> > tuning_ins.xml; I
>> >> >> >> > have updated the version.
>> >> >> >> > Do you have any other advice that might help?
>> >> >> >> > Respectfully,
>> >> >> >> > Blake J. W. Chambers
>> >> >> >> > MIT '13 Aero/Astro Department
>> >> >> >> > Phi Kappa Theta
>> >> >> >> > Phone: (617) 819-4021
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > On Fri, Aug 12, 2011 at 8:02 PM, Felix Ruess
>> >> >> >> > <address@hidden>
>> >> >> >> > wrote:
>> >> >> >> >>
>> >> >> >> >> You have an outdated version... please update to the latest
>> >> >> >> >> git
>> >> >> >> >> master.
>> >> >> >> >>
>> >> >> >> >> On Fri, Aug 12, 2011 at 8:52 PM, Pedro Andrade
>> >> >> >> >> <address@hidden>
>> >> >> >> >> wrote:
>> >> >> >> >> > Hi Felix,
>> >> >> >> >> > I tryed set the " setting" with tunning_ins.xml file,
>> >> >> >> >> > however
>> >> >> >> >> >  the
>> >> >> >> >> > following
>> >> >> >> >> > error happens:
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > ...........................................................................................................................................................................................
>> >> >> >> >> > Run 'make -C /home/lmi/paparazzi -f Makefile.ac
>> >> >> >> >> > AIRCRAFT=AVIAO
>> >> >> >> >> > ap.compile '
>> >> >> >> >> > make: Entrando no diretório `/home/lmi/paparazzi'
>> >> >> >> >> > AVIAO
>> >> >> >> >> > BUILD AVIAO, TARGET ap
>> >> >> >> >> > make[1]: Entrando no diretório `/home/lmi/paparazzi'
>> >> >> >> >> > BUILD /home/lmi/paparazzi/var/AVIAO/generated/airframe.h
>> >> >> >> >> > ##################################################
>> >> >> >> >> >  AIRFRAME MODEL: AVIAO
>> >> >> >> >> > ##################################################
>> >> >> >> >> > BUILD /home/lmi/paparazzi/var/AVIAO/generated/modules.h
>> >> >> >> >> > BUILD /home/lmi/paparazzi/var/AVIAO/generated/settings.h
>> >> >> >> >> > BUILD /home/lmi/paparazzi/var/AVIAO/generated/tuning.h
>> >> >> >> >> > BUILD /home/lmi/paparazzi/var/AVIAO/generated/periodic.h
>> >> >> >> >> > make[1]: Saindo do diretório `/home/lmi/paparazzi'
>> >> >> >> >> > make[1]: Entrando no diretório `/home/lmi/paparazzi'
>> >> >> >> >> > BUILD /home/lmi/paparazzi/var/AVIAO/generated/radio.h
>> >> >> >> >> > ##################################################
>> >> >> >> >> >  RADIO MODEL: cockpitSX (easy)
>> >> >> >> >> > ##################################################
>> >> >> >> >> > make[1]: Saindo do diretório `/home/lmi/paparazzi'
>> >> >> >> >> > make[1]: Entrando no diretório `/home/lmi/paparazzi'
>> >> >> >> >> > BUILD /home/lmi/paparazzi/var/AVIAO/generated/flight_plan.h
>> >> >> >> >> > ##################################################
>> >> >> >> >> >  FLIGHT PLAN: Basic
>> >> >> >> >> > ##################################################
>> >> >> >> >> > Warning: low altitude (0<0+25) in <waypoint NAME="TD"
>> >> >> >> >> > Y="57.0"
>> >> >> >> >> > X="28.8"
>> >> >> >> >> > ALT="0.0"/>
>> >> >> >> >> > BUILD /home/lmi/paparazzi/var/AVIAO/flight_plan.xml
>> >> >> >> >> > make[1]: Saindo do diretório `/home/lmi/paparazzi'
>> >> >> >> >> > cd sw/airborne; make PAPARAZZI_SRC=/home/lmi/paparazzi
>> >> >> >> >> > PAPARAZZI_HOME=/home/lmi/paparazzi TARGET=ap all
>> >> >> >> >> > make[1]: Entrando no diretório
>> >> >> >> >> > `/home/lmi/paparazzi/sw/airborne'
>> >> >> >> >> > DEPEND /home/lmi/paparazzi/var/AVIAO/ap/.depend
>> >> >> >> >> > make[1]: Saindo do diretório
>> >> >> >> >> > `/home/lmi/paparazzi/sw/airborne'
>> >> >> >> >> > make[1]: Entrando no diretório
>> >> >> >> >> > `/home/lmi/paparazzi/sw/airborne'
>> >> >> >> >> > Using CC   = /opt/paparazzi/stm32/bin/arm-none-eabi-gcc
>> >> >> >> >> > Using LD   = /opt/paparazzi/stm32/bin/arm-none-eabi-gcc
>> >> >> >> >> > Using CP   = /opt/paparazzi/stm32/bin/arm-none-eabi-objcopy
>> >> >> >> >> > Using DMP  = /opt/paparazzi/stm32/bin/arm-none-eabi-objdump
>> >> >> >> >> > Using NM   = /opt/paparazzi/stm32/bin/arm-none-eabi-nm
>> >> >> >> >> > Using SIZE = /opt/paparazzi/stm32/bin/arm-none-eabi-size
>> >> >> >> >> > Using OOCD = /opt/paparazzi/stm32/bin/openocd
>> >> >> >> >> > GCC version:
>> >> >> >> >> > arm-none-eabi-gcc (GCC) 4.4.3
>> >> >> >> >> > Copyright (C) 2010 Free Software Foundation, Inc.
>> >> >> >> >> > This is free software; see the source for copying
>> >> >> >> >> > conditions.
>> >> >> >> >> >  There
>> >> >> >> >> > is
>> >> >> >> >> > NO
>> >> >> >> >> > warranty; not even for MERCHANTABILITY or FITNESS FOR A
>> >> >> >> >> > PARTICULAR
>> >> >> >> >> > PURPOSE.
>> >> >> >> >> > OOCD version:
>> >> >> >> >> > Open On-Chip Debugger 0.5.0-dev-00789-g59a6380
>> >> >> >> >> > (2011-03-15-11:50)
>> >> >> >> >> > Licensed under GNU GPL v2
>> >> >> >> >> > For bug reports, read
>> >> >> >> >> > http://openocd.berlios.de/doc/doxygen/bugs.html
>> >> >> >> >> > *** NOT using multilib ***
>> >> >> >> >> > CC /home/lmi/paparazzi/var/AVIAO/ap/mcu.o
>> >> >> >> >> > CC /home/lmi/paparazzi/var/AVIAO/ap/sys_time.o
>> >> >> >> >> > CC /home/lmi/paparazzi/var/AVIAO/ap/actuators.o
>> >> >> >> >> > CC /home/lmi/paparazzi/var/AVIAO/ap/arch/stm32/mcu_arch.o
>> >> >> >> >> > arch/stm32/mcu_arch.c:46:2: warning: #warning Info: Using
>> >> >> >> >> > external
>> >> >> >> >> > clock
>> >> >> >> >> > CC /home/lmi/paparazzi/var/AVIAO/ap/arch/stm32/led_hw.o
>> >> >> >> >> > CC /home/lmi/paparazzi/var/AVIAO/ap/./inter_mcu.o
>> >> >> >> >> > CC /home/lmi/paparazzi/var/AVIAO/ap/math/pprz_geodetic_int.o
>> >> >> >> >> > CC
>> >> >> >> >> > /home/lmi/paparazzi/var/AVIAO/ap/math/pprz_geodetic_float.o
>> >> >> >> >> > CC
>> >> >> >> >> > /home/lmi/paparazzi/var/AVIAO/ap/math/pprz_geodetic_double.o
>> >> >> >> >> > CC /home/lmi/paparazzi/var/AVIAO/ap/math/pprz_trig_int.o
>> >> >> >> >> > CC
>> >> >> >> >> >
>> >> >> >> >> > /home/lmi/paparazzi/var/AVIAO/ap/firmwares/fixedwing/main_fbw.o
>> >> >> >> >> > CC /home/lmi/paparazzi/var/AVIAO/ap/subsystems/electrical.o
>> >> >> >> >> > CC /home/lmi/paparazzi/var/AVIAO/ap/./commands.o
>> >> >> >> >> > CC
>> >> >> >> >> >
>> >> >> >> >> > /home/lmi/paparazzi/var/AVIAO/ap/firmwares/fixedwing/main_ap.o
>> >> >> >> >> > In file included from firmwares/fixedwing/main_ap.c:50:
>> >> >> >> >> > /home/lmi/paparazzi/var/AVIAO/generated/settings.h: In
>> >> >> >> >> > function
>> >> >> >> >> > 'settings_get_value':
>> >> >> >> >> > /home/lmi/paparazzi/var/AVIAO/generated/settings.h:153:
>> >> >> >> >> > error:
>> >> >> >> >> > 'imu_overrun'
>> >> >> >> >> > undeclared (first use in this function)
>> >> >> >> >> > /home/lmi/paparazzi/var/AVIAO/generated/settings.h:153:
>> >> >> >> >> > error:
>> >> >> >> >> > (Each
>> >> >> >> >> > undeclared identifier is reported only once
>> >> >> >> >> > /home/lmi/paparazzi/var/AVIAO/generated/settings.h:153:
>> >> >> >> >> > error:
>> >> >> >> >> > for
>> >> >> >> >> > each
>> >> >> >> >> > function it appears in.)
>> >> >> >> >> > firmwares/fixedwing/main_ap.c: In function 'reporting_task':
>> >> >> >> >> > firmwares/fixedwing/main_ap.c:199: error: 'imu_overrun'
>> >> >> >> >> > undeclared
>> >> >> >> >> > (first
>> >> >> >> >> > use in this function)
>> >> >> >> >> > make[1]: **
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > [/home/lmi/paparazzi/var/AVIAO/ap/firmwares/fixedwing/main_ap.o]
>> >> >> >> >> > Erro 1
>> >> >> >> >> > make[1]: Saindo do diretório
>> >> >> >> >> > `/home/lmi/paparazzi/sw/airborne'
>> >> >> >> >> > make: ** [ap.compile] Erro 2
>> >> >> >> >> > make: Saindo do diretório `/home/lmi/paparazzi'
>> >> >> >> >> > DONE (exec make -C /home/lmi/paparazzi -f Makefile.ac
>> >> >> >> >> > AIRCRAFT=AVIAO
>> >> >> >> >> > ap.compile  2>&1)
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > ................................................................................................................................................................................................................................
>> >> >> >> >> > Cheers
>> >> >> >> >> > Pedro Andrade
>> >> >> >> >> >> Date: Tue, 9 Aug 2011 22:18:15 +0200
>> >> >> >> >> >> From: address@hidden
>> >> >> >> >> >> To: address@hidden
>> >> >> >> >> >> Subject: Re: [Paparazzi-devel] What setting I should to
>> >> >> >> >> >> use?
>> >> >> >> >> >>
>> >> >> >> >> >> Please use tuning_ins.xml
>> >> >> >> >> >>
>> >> >> >> >> >> (There never was a tuning_basic_imu.xml, I guess you meant
>> >> >> >> >> >> tuning_basic_ins.xml which is now just tuning_ins.xml
>> >> >> >> >> >> without
>> >> >> >> >> >> any
>> >> >> >> >> >> ahrs/dcm specific stuff).
>> >> >> >> >> >>
>> >> >> >> >> >> Cheers, Felix
>> >> >> >> >> >>
>> >> >> >> >> >> On Tue, Aug 9, 2011 at 9:57 PM, Christophe De Wagter
>> >> >> >> >> >> <address@hidden>
>> >> >> >> >> >> wrote:
>> >> >> >> >> >> > Oh, I should have mentioned that:
>> >> >> >> >> >> > telemetry: default_fixedwing_imu.xml
>> >> >> >> >> >> > settings: tuning_basic_imu.xml
>> >> >> >> >> >> > (disclaimer: if names have not changed)
>> >> >> >> >> >> > Sincerely
>> >> >> >> >> >> > -Christophe
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > On Tue, Aug 9, 2011 at 8:06 PM, Pedro Andrade
>> >> >> >> >> >> > <address@hidden>
>> >> >> >> >> >> > wrote:
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> Hi Christophe,
>> >> >> >> >> >> >> can you tell me, what is the telemetry configuration
>> >> >> >> >> >> >> file
>> >> >> >> >> >> >> do
>> >> >> >> >> >> >> you
>> >> >> >> >> >> >> use?
>> >> >> >> >> >> >> (i.e. default, xbee868)
>> >> >> >> >> >> >> Cheers
>> >> >> >> >> >> >> ________________________________
>> >> >> >> >> >> >> Date: Tue, 12 Jul 2011 12:41:20 +0200
>> >> >> >> >> >> >> From: address@hidden
>> >> >> >> >> >> >> To: address@hidden
>> >> >> >> >> >> >> Subject: Re: [Paparazzi-devel] What setting I should to
>> >> >> >> >> >> >> use?
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> make a copy of
>> >> >> >> >> >> >> ./conf/airframes/ppzuav/fixedwing/tiny_ppzuav.xml
>> >> >> >> >> >> >> change to board="lisa_l_1.1"
>> >> >> >> >> >> >> change telemetry to type="xbee_api" and set your
>> >> >> >> >> >> >> baudrate
>> >> >> >> >> >> >> change imu to type="aspirin"
>> >> >> >> >> >> >> -Christophe
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> On Tue, Jul 12, 2011 at 3:26 AM, Pedro Andrade
>> >> >> >> >> >> >> <address@hidden>
>> >> >> >> >> >> >> wrote:
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> Hi,
>> >> >> >> >> >> >> I'm making a fixedwing.
>> >> >> >> >> >> >> Cheers.
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> ________________________________
>> >> >> >> >> >> >> Date: Wed, 6 Jul 2011 23:12:33 +0200
>> >> >> >> >> >> >> From: address@hidden
>> >> >> >> >> >> >> To: address@hidden
>> >> >> >> >> >> >> Subject: Re: [Paparazzi-devel] What setting I should to
>> >> >> >> >> >> >> use?
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> Are you making a rotorcraft or a fixedwing?
>> >> >> >> >> >> >> On Jul 6, 2011 1:28 AM, "Pedro Andrade"
>> >> >> >> >> >> >> <address@hidden>
>> >> >> >> >> >> >> wrote:
>> >> >> >> >> >> >> >
>> >> >> >> >> >> >> > Hi all,
>> >> >> >> >> >> >> > What setting I should to use for the Lisa/L, Aspirin
>> >> >> >> >> >> >> > and
>> >> >> >> >> >> >> > XBee
>> >> >> >> >> >> >> > modem.Cheers
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> _______________________________________________
>> >> >> >> >> >> >> Paparazzi-devel
>> >> >> >> >> >> >> mailing
>> >> >> >> >> >> >> list address@hidden
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >> >> >> >> >> >> _______________________________________________
>> >> >> >> >> >> >> Paparazzi-devel mailing list
>> >> >> >> >> >> >> address@hidden
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> _______________________________________________
>> >> >> >> >> >> >> Paparazzi-devel
>> >> >> >> >> >> >> mailing
>> >> >> >> >> >> >> list address@hidden
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >> >> >> >> >> >> _______________________________________________
>> >> >> >> >> >> >> Paparazzi-devel mailing list
>> >> >> >> >> >> >> address@hidden
>> >> >> >> >> >> >>
>> >> >> >> >> >> >> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >> >> >> >> >> >>
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >> > _______________________________________________
>> >> >> >> >> >> > Paparazzi-devel mailing list
>> >> >> >> >> >> > address@hidden
>> >> >> >> >> >> > https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >>
>> >> >> >> >> >> _______________________________________________
>> >> >> >> >> >> Paparazzi-devel mailing list
>> >> >> >> >> >> address@hidden
>> >> >> >> >> >> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >> >> >> >> >
>> >> >> >> >> > _______________________________________________
>> >> >> >> >> > Paparazzi-devel mailing list
>> >> >> >> >> > address@hidden
>> >> >> >> >> > https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >>
>> >> >> >> >> _______________________________________________
>> >> >> >> >> Paparazzi-devel mailing list
>> >> >> >> >> address@hidden
>> >> >> >> >> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > _______________________________________________
>> >> >> >> > Paparazzi-devel mailing list
>> >> >> >> > address@hidden
>> >> >> >> > https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >> >> _______________________________________________
>> >> >> >> Paparazzi-devel mailing list
>> >> >> >> address@hidden
>> >> >> >> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >> >> >
>> >> >> >
>> >> >> > _______________________________________________
>> >> >> > Paparazzi-devel mailing list
>> >> >> > address@hidden
>> >> >> > https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> _______________________________________________
>> >> >> Paparazzi-devel mailing list
>> >> >> address@hidden
>> >> >> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > Paparazzi-devel mailing list
>> >> > address@hidden
>> >> > https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >> >
>> >> >
>> >>
>> >> _______________________________________________
>> >> Paparazzi-devel mailing list
>> >> address@hidden
>> >> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >
>> >
>> > _______________________________________________
>> > Paparazzi-devel mailing list
>> > address@hidden
>> > https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>> >
>> >
>>
>> _______________________________________________
>> Paparazzi-devel mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>
>

_______________________________________________
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]