[Top][All Lists]

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

How does this relate to infrared.c?? Re: [Paparazzi-devel] paparazzi HW

From: gwen hastings
Subject: How does this relate to infrared.c?? Re: [Paparazzi-devel] paparazzi HW
Date: Sat, 20 Oct 2007 10:44:51 -0700

Subject stands .. as list etiquette please dont reply to other subjects by way of starting a totally new subject, instead start a new thread instead of replying to others.. this way it just gets too confusing, Thanx

ps how much on your HW and how does this relate to tiny or classix?

address@hidden wrote:
Hi, i will produce the following items (on pick/place machines, 603 only)

lpc213x/4x with XBEE module, connector for other radio modules and external GPS, 
micro-SD card holder, 4Mbit Flash memory, PPM input (isolated), PS2 Controller 
input, optional pressure sensor (uses 2xadc & dac), inputs for external ADC 
(IR-Sensor as example), isolated connector for servo board, FSK output for APRS, 
and of course, USB on the 4x versions. As example, i want use the LPC2142 for the 
base station offering
USB to GPS/MODEM/rc-receiver/gamepad connection and eventually encryption
of the modem link (without SD card fitted). On the UAV, a higher lpc213x
CPU (4x is possible) can do the job. The reason to divide servos, rc-receiver, 
gps from the main cpu and RF-module is to minimize interferencing.

Servo board.

Further, one board having a 8051 processor with 8x 24bit ADC and
3D magnetometer + 2x pressure sensors.

Finally the IMU board with gyros and accel sensors.
I donĀ“t have decided, if using the IDG300 and one ADXRS or three
ADXRS because there are far superior on bias correction.
The advantage of the IDG300, apart of beeing 15$ cheaper, is that
only one board is needed compared to the not so easy mounting of the
ADRX gyros.

If someone would discuss offlist on this HW project, please contact me.

Building a tiny board with the same schematic is possible with the exception of 
the dc/dc converter, using oem modules.
-------- Original-Nachricht --------
Datum: Sat, 20 Oct 2007 00:15:42 +0200
Von: address@hidden
An: address@hidden
Betreff: [Paparazzi-devel] Code cleaning

Good evening ladies and gentlemen

Looking at the code and especialy the infrared.c file, it appears that
over the
years, we have accumulated some not so used features.
For example, we have 4 differents ways of dealing with infared
 -without vertical sensor using ground calibration
 -without vertical sensor using the famous LLS filter
 -with vertical sensor using a linear function
 -with vertical sensor using the IR360 method ( atan2 )

This leads to 340 lines of not so easy to read code and dozains of not so
to understand parameters. What about removing all that and leaving only
IR360 method which seems the most efficient ?

If anybody has a strong oposition to this, please let us know


Paparazzi-devel mailing list

  "Arguing with an engineer is like wrestling with a pig in the mud;
   after a while you realize you are muddy and the pig is enjoying it."

reply via email to

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