Issue with Sensor Monitor

[sbarton]

For some reason Analog 1 (pin 14) is showing values and changes with fuel level (plugged into Analog 2, pin 13) even though nothing is plugged it into Pin 14. Other analog inputs are showing some weird stuff even though nothing is plugged into them.

Just updated to RA 1.13.

http://www.youtube.com/watch?v=InBYfCfVVkw

-Scott

[sbarton]

I have the following hooked up:
Pin 1: Ground
Pin 2: 12v Power
Pin 9 (Analog 6): Coolant
Pin 13 (Analog 2): Fuel

Pin 15 (GPIO3): Brake switch (not actually connected)
Pin 20 (Pulse1): RPM (not actually connected)





I enabled all of the analog channels, set them to 1Hz, set the precision to 2, set them to simple linear scaling 0.004900 (default).

Then using Sensor Monitor, I read the values with the fuel level sender at 0% (out of tank), 100% (flipped over), and 50% (in tank with half tank of gas).

Analog5
0.10 = 0%
0.00 = 100%
0.02 = 50%

Analog4
0.14 = 0%
0.00 = 100%
0.02 = 50%

Fuel
5.01 = 0%
3.14 = 100%
5.01 = 50%

Battery
14.10 = 0%
13.80 = 00%
13.8 = 50%

Coolant
0.10 = 0%
0.00 = 100%
0.02 = 50%

Analog 3
0.14 = 0%
0.00 = 100%
0.02 =50%

Analog 1
5.0v = 0% (first time)
4.50 = 0% (second time)
0.0v = 100%
0.53 = 48%

Analog7
0.10 = 0%
0.00 = 100%
0.02 = 50%

[sbarton]

It looks like all of the analog channels vary a little bit when the fuel level changes, but Analog1 REALLY changes a lot, even though nothing is plugged into it. In fact it changes more then the Analog 2, which is where the fuel wire is plugged into.

-Scott

[gizmodo]

I noticed this same thing when I had my brake switch hooked up to analog inputs.

[brentp]

We've released an updated version of RaceAnalyzer (1.1.14) and firmware (1.2.6) that helps with the sensor monitor. The firmware was periodically omitting channels from the samples, and we hopefully fixed crashing issues with the sensor monitor on some windows platforms.

Let us