Need help with VSS setup - reading about 3x too high

[shauer]

I have been trying to figure out a minor issue with my VSS setup. My MPH reading appears to be roughly 3 times higher than it should be. For example, my log file shows approximately 220 MPH with I'm really doing 70MPH.

I have two magnets mounted on my drive shaft 180 degrees apart. I'm using a coil pickup (VR sensor). I condition the VR signal through one of Jean's VR conditioner boards and then run the signal to the table switch input.

Below is a screen shot of my VSS setup and I have attached my msq.

Just one thought, the screen tells me to enter my wheel diameter in meters and I did, but that sounds a little odd as it is the only metric input. Should this be feet instead (a difference of a little over 3....)

Any ideas would be greatly appreciated.

Thanks!

[charged3800z24]

I also have TS showing 3 times the speed. It was working fine then a made a change and have no idea what happened, lol. How are you running the gage in the dash, I didn't see any output configured?

[shauer]

I am only using VSS for closed loop idle control enable and fan control enable for the moment. I can only see the MPH1 value via the log files in MLV. It is not configured as an output.

I actually installed the drive shaft sensor as part of my new cruise control. While I was at it, I added the signal to MS.

Interesting that someone else is also getting 3x the correct speed.

[charged3800z24]

I am only using VSS for closed loop idle control enable and fan control enable for the moment. I can only see the MPH1 value via the log files in MLV. It is not configured as an output.

I actually installed the drive shaft sensor as part of my new cruise control. While I was at it, I added the signal to MS.

Interesting that someone else is also getting 3x the correct speed.

OK, I miss understood. I'm currently using the CAM-In and will be switching to the Dual VR baord this weekend.

[jsmcortina]

Confirmed.
There's a trivial one line bug in the code causing "driveline" to apply the wrong final drive ratio. Will be fixed for the next beta.

James

[shauer]

Thanks for the information James. In the mean time I will just make my wheel diameter 3 times smaller.

[charged3800z24]

Confirmed.
There's a trivial one line bug in the code causing "driveline" to apply the wrong final drive ratio. Will be fixed for the next beta.

James

Is it only in drive line? Could we use wheel instead?

Edit: nevermind, Wheel seems to work just fine.