Datalogging & Video Solutions for C5
#21
Pro
For water temp, Ben provided some data and I fit a curve to it. Below about 120 degF, it gives an incorrect reading. The temp circuit seems to change around this temp.
If you prefer a function, it is this:
Temp (degF) = 0.0365477458944952*V^6 - 1.37691779802641*V^5 + 14.3256285124391*V^4 - 69.4597440685648*V^3 + 179.707756800085*V^2 - 287.449559849111*V + 414.418077041844
Where V it voltage and the output is the temperature in degF.
I'd give this a try.
Voltage Temp degF
0.00000 414.41808
0.15625 373.63492
0.31250 340.15248
0.46875 312.66939
0.62500 290.05928
0.78125 271.35632
0.93750 255.74118
1.09375 242.52739
1.25000 231.14801
1.40625 221.14279
1.56250 212.14558
1.71875 203.87227
1.87500 196.10900
2.03125 188.70080
2.18750 181.54059
2.34375 174.55861
2.50000 167.71218
2.65625 160.97587
2.81250 154.33205
2.96875 147.76180
3.12500 141.23626
3.28125 134.70828
3.43750 128.10455
3.59375 121.31801
3.75000 114.20074
3.90625 106.55716
4.06250 98.13764
4.21875 88.63252
4.37500 77.66644
4.53125 64.79315
4.68750 49.49063
4.84375 31.15659
5.00000 9.10442
0.00000 414.41808
0.15625 373.63492
0.31250 340.15248
0.46875 312.66939
0.62500 290.05928
0.78125 271.35632
0.93750 255.74118
1.09375 242.52739
1.25000 231.14801
1.40625 221.14279
1.56250 212.14558
1.71875 203.87227
1.87500 196.10900
2.03125 188.70080
2.18750 181.54059
2.34375 174.55861
2.50000 167.71218
2.65625 160.97587
2.81250 154.33205
2.96875 147.76180
3.12500 141.23626
3.28125 134.70828
3.43750 128.10455
3.59375 121.31801
3.75000 114.20074
3.90625 106.55716
4.06250 98.13764
4.21875 88.63252
4.37500 77.66644
4.53125 64.79315
4.68750 49.49063
4.84375 31.15659
5.00000 9.10442
Temp (degF) = 0.0365477458944952*V^6 - 1.37691779802641*V^5 + 14.3256285124391*V^4 - 69.4597440685648*V^3 + 179.707756800085*V^2 - 287.449559849111*V + 414.418077041844
Where V it voltage and the output is the temperature in degF.
I'd give this a try.
Last edited by MySR71; 04-16-2017 at 09:38 PM.
The following users liked this post:
Hi Volts Z06 (04-17-2017)
#22
Burning Brakes
That should be all I need. I actually used only two data points to calculate oil temp and other than reading 3 degrees F when temps are below 144, it seems to be pretty accurate.
Thank you!
Thank you!
#23
A while ago I was going to try to add-on the F45 shock position sensors but just ditched it for traditional linear pots as the OEM setup is pretty bulky. If you wanted to, you could tap into the individual wheel speed sensors (and create custom channels to show how the diff is working and rear tire slip), but you'll need to convert the signals to something the DL-1/a logger's digital inputs can use (Race Tech sells a converter). Could obviously log the trans temp if you have a Z06. I can't think of anything else, in terms of OEM sensors, that would be useful for driving analysis.
I just got my RaceCapture Pro Mk3, and I think this will be a pretty good option for tapping into the factory sensors on a C5. Max sampling rates of each analog channel is 1kHz, and it's configurable for each channel.
My plans are to use the gyros in the RCP rather than the yaw gyro on the car, but I'm going to tap steering angle (and derive the channel for steering rate), throttle position, brake pressure, shock position (F55 sensors), and wheel speeds. This is primarily for autocross, where we're allowed to run 2 drivers in the same car, and I'm really curious to see what the difference is between drivers for brake pressure and steering input.
#24
Pro
#25
Burning Brakes
Another question for those of you that are tapping into stock sensors. Are using a pull up resistor or allowing the PCM's pull up resistor to provide voltage? I'm running into some issues and think my problem is that I'm using a pull up resistor bridged between the MXG's 5v output and the return (or pins 1-4 for those of you who are familiar).
#26
Pro
I am not using a pull up resistor. I'm only splicing into the sensor's output wire and connecting that to the break out box in my data system. I am telling the software not to use a pull up resistor. Sometimes, I also splice into the sensor's ground wire and also connect that the break out box. I let the car supply the sensor's 5 volts as it did when stock.
I do, however, have to turn on the data system before turning the car's key. Otherwise, the car will set codes. Similarly, I turn off the car, then the data system. So the data system is first on, last off.
If you are still talking about the water temp, note that it will read a very wrong number until the temp gets over around 120 degF.
I do, however, have to turn on the data system before turning the car's key. Otherwise, the car will set codes. Similarly, I turn off the car, then the data system. So the data system is first on, last off.
If you are still talking about the water temp, note that it will read a very wrong number until the temp gets over around 120 degF.
Last edited by MySR71; 05-29-2017 at 10:53 AM.
#27
Burning Brakes
Thanks for the reply. What system are you using? I find my Aim MXG automatically reboots if I turn it on before starting. I also think my problem is that I'm trying to use the pull up resistor and I might have the polarity reversed. It was working correctly when the ignition was off and then when I started the car leading me to belive what you said is true....all I have to do is read the output voltage of the sensor.
#28
Pro
I have a Racepak G2X Pro. For power, it is hardwired in to a power source that does not turn off during engine start. Yup, just look at the output voltage of the sensor and use a calibration to convert it to relevant units.
PS It MIGHT work ok if you turn on the data system immediately after starting the car. Don't wait more than a second or two.
PS It MIGHT work ok if you turn on the data system immediately after starting the car. Don't wait more than a second or two.
Last edited by MySR71; 05-29-2017 at 01:36 PM.
The following users liked this post:
Hi Volts Z06 (05-29-2017)
#29
Safety Car
Right, if you are using the OEM temp sensor(s) - the PCM provides a pull-up resistor so you can just tap into the wire - you do not want to introduce a 2nd pull-up.
The following users liked this post:
Hi Volts Z06 (05-29-2017)
#30
Burning Brakes
Ben, when you picked up sensors on Mark's car, did you use the ground connection or simply tap only one wire since the logger already has a ground connection?
The following users liked this post:
Hi Volts Z06 (05-29-2017)
#33
Burning Brakes
This seems to be the right thread for my problem so here it goes:
Anyone every had a problem when tapping into the TPS sensor on a C5? I tapped into that with my MXG and everything was fine. After the second session on track, I lost my throttle pedal and the engine ran at idle until I disconnected the MXG from the sensor. Everything was fine after. While I didn't pull any codes (since the problem was fixed) I'm guessing that the slight bit of resistance from the MXG caused the TPS1 and TPS2 sensors (and possibly APP1 sensor) to have a slight imbalance triggering a code.
Anyone every had a problem when tapping into the TPS sensor on a C5? I tapped into that with my MXG and everything was fine. After the second session on track, I lost my throttle pedal and the engine ran at idle until I disconnected the MXG from the sensor. Everything was fine after. While I didn't pull any codes (since the problem was fixed) I'm guessing that the slight bit of resistance from the MXG caused the TPS1 and TPS2 sensors (and possibly APP1 sensor) to have a slight imbalance triggering a code.
#34
Pro
The only time I've every had trouble on my 2002 was when I turned on the ignition prior to turning on the data system. Then fault codes are generated after a very short time (seconds) although I'm not sure if it is because the APP, steering wheel sensor, or brake pressure sensor. The APP channel that I'm recording is the one which goes from a low voltage at zero throttle and increases in voltage at WOT. I haven't tried the other one.
PS I've spliced into the sensor's wiring under the dash.
PS I've spliced into the sensor's wiring under the dash.
Last edited by MySR71; 07-28-2017 at 09:16 PM.
#35
Burning Brakes
The only time I've every had trouble on my 2002 was when I turned on the ignition prior to turning on the data system. Then fault codes are generated after a very short time (seconds) although I'm not sure if it is because the APP, steering wheel sensor, or brake pressure sensor. The APP channel that I'm recording is the one which goes from a low voltage at zero throttle and increases in voltage at WOT. I haven't tried the other one.
PS I've spliced into the sensor's wiring under the dash.
PS I've spliced into the sensor's wiring under the dash.
#36
Racer
I have an MXG as well and want to do the same thing.
#37
Burning Brakes
No....I had an engine fire later that day due to a bad o-ring on my dry sump system so I'm still rebuilding the car. Was hoping to get some input here before trying again.
#38
Racer
How exactly did you connect the MXG? which connector to adapt to a AIM 719 connector did you use? what pullup sensor if any?
#39
Pro
#40
Burning Brakes
I purchased patch cords from Binder directly and just used a multimeter to figure out the pinouts. From there you only are hooking directly to the sensor output and reading the 0 to 5v signal. There is no pull-up resistor required. Again, I ended up in limp mode after tying into TPS2 so I'm trying to see how others have done it.