Hi,
I've been using 12 bit resolution. Need it since I'm also operating with a
control force loading system and autopilot. If you go to 12 bits suggest you
get some high res, multi-turn pots or some other systems (like magnetic) to
give you the precision that warrants 12 bits. If you're using low cost single
270 degree turn pots, might as well stick with a lower bit resolution.
Incidentially, those same 12 bits boards are used to fly the Global Observer
UAV built by AeroVironment, so I guess they're good enough ;-)
Think of it this way, determine the angular travel of your control stick; for
8bits divide by 256; for 12 bits divide by 4096. That defines the resoluion.,
i.e. degrees per bit. So then you have to decide how good is your sensor in
defining the control stick location. If you can't sense 4096 discrete positions
your wasting time and money using 12 bits.
Regards
John
----- Original Message -----
From: "Roberto Inzerillo" <rob...@gmx.net>
To: flightgear-devel@lists.sourceforge.net
Sent: Wednesday, March 7, 2012 10:14:44 AM
Subject: [Flightgear-devel] Double Input Resolution?
Hi everybody,
it's a few weeks I'm dealing with a few analog to digital converters, I'm using
them to convert external analog signals and use them as inputs to FlightGear
controls.
I'm wondering which resolution is best when dealing with properties of type
double. My analog values get converted to digital ones before being fed to
FGFS. I see FGFS likes doubles, that's ok, I am converting those digital inputs
to appropriate double values.
I'm talking about stuff like /controls/flight/aileron or
/controls/engines/enigne/throttle.
I'll try and be as precise as possible with my hardware so that I get
reliable/stable/consistent readings to feed to FGFS, I'm getting closer to make
rid of any unwanted highres noise, still I am going to deal with 8, 10 or
12-bit resolution digital values. That may be too much and useless. I'd like to
crop them down to more reasonable resolution if possible/usefull.
I see FGFS keyboard/mouse interface uses 7/8bit resolution. I'd like to know if
someone can help me figuring out what input resolution should I use for:
/controls/flight/aileron
/controls/flight/aileron-trim
/controls/flight/elevator
/controls/flight/elevator-trim
/controls/flight/rudder
/controls/flight/rudder-trim
/controls/gear/brake-parking
/controls/engines/enigne/throttle
/controls/engines/engine/cowl-flaps-norm
/controls/engines/engine/propeller-pitch
I'd prefer keep using 8bit resolution (cheap and reliable solution). I'm open
to use 10bit resolution if usefull. I'm willing to go with a 12bit resolution
input only if _really_ needed. That's how I see it now.
I don't want to discard usefull information, nor I want to use useless
over-precise values. I'm looking for a reasonable compromise here, but I don't
know the internals of FGFS.
Cheers,
Roberto
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
