by DarrenR on Fri Feb 27, 2009 10:18 am
Hi Martin,
Unfortualtly the PDM is a simple device and doesn't deal with negitive numbers. You need to offset the calibration of the G sensor in the ECU. So for example, in the G force custom calibration, set 10 for 0G, 5 for -5G and 15 for +5G. Recieve the value in the PDM as 16bit and set a divisor of 100. In the PDM this will give you a value of 100 for 0G, 50 for -5G and 150 for +5G.
if you need better resolution than 0.1G you can divide by say 10 to give 0.01G resolution but you will have to calibrate the G sensor in ECU manager with an offset of 1.28G. This would give a range of -1.28G (value of 0) to + 1.27G (value of 255) 0G would have a value of 128 in the PDM.
Since the G force logged value will have an offset, just minus the offset away in i2 to make it back to the correct numbers. I know it is not ideal so we are looking to make improvements in this area.
If sending the G force from a dash, the channel values in the dash can remain correct but the values in the PDM still come out the same.
Darren Reynolds
MoTeC Research Centre - Melbourne, Australia.