TS odometer or trip meter not working correctly

[dsmcrzy]

I have been fighting this for sometime now. I don't believe its an error in my settings, but who knows really. Attached are my current settings for both the data logging fields and my VSS settings. Per the OEM manual, 4000 pulses = 1 mile. My speedometer in TS works perfectly, which makes no sense that my odometer doesn't work correctly.

This is in a 420a powered eclipse running an MS3x.
Current TS version is MS Ultra v3.0.10
MS firmware is v1.4.1

Basically the odometer and the trip meter count up roughly twice as fast as it should. I have double and triple checked my gauges to ensure that I am not running kilometers rather than miles. This morning I actually made 2 trip gauges, one in Km, one in Miles. Neither matched what I actually traveled to work. Any idea what can be going on? I would think since my speedometer is spot on, that my odometer should be as well. I would like to get this resolved before the car goes away for winter, and I begin installing my raspberry pi dash.

Thank you,
Kyle

[LT401Vette]

If the VSS is reading right, the inputs don't matter, it is just looking at the end result.

Can you post your msq so I can try your set up here and see.

[dsmcrzy]

Sorry Phil, I should have just added it last night. Here it is. Thank you!

[LT401Vette]

Set a gauge to use the OutputChannel: tsVehicleSpeedMph

See if that agrees with your VSS1 speedometer.

[dsmcrzy]

Hey Phil,

Sorry for the delay. I created that gauge per your instructions and it does show speed spot on with my VSS1 speed. I took a data log but it doesn't look like it logs it separately.

[LT401Vette]

Then I'm at a loss...
tsVehicleSpeedMph is the normalized channel TS bases the odometer on. I've run for hours and it is working spot on.

There must be something missing here.

[dsmcrzy]

TS uses speed and time to run the odometer right? Is it possible something is going on with the time?

I'm at a loss too. it doesn't make sense.

[LT401Vette]

It does use time of course... But I assume if your PC's clock was off by that much you would notice.

If it is roughly twice as fast, maybe somehow it is getting double counted/added on each read.
Maybe some combination of channels causes this.

Perhaps send my a project backup and I can try it with your project.

[dsmcrzy]

Phil,

I sent you a PM with a link to my TS project. Thanks for you're help with this.

I did follow this thread to add a distance traveled to my megalogviewer HD
http://www.msextra.com/forums/viewtopic ... 00&t=52204
When I do this and then add a log it shows I traveled 7.833 miles where my stock odometer is showing 7.5 miles on my ride home. Maybe there is something you can find in my project that I'm missing. The log of my trip home is in the same location as my project.

[dsmcrzy]

Trip to work this morning
Actual via OEM odo and google maps - 7.7 miles
TS trip odometer - 15.1 miles
MLV TripMiles - 8.052

[dsmcrzy]

Phil, did you ever get a chance to look into this? Were you able to download the files from the link I sent?

[LT401Vette]

Phil, did you ever get a chance to look into this? Were you able to download the files from the link I sent?

I have looked into this exhaustively...
I did find another bug with it where when you started a data log it would go wacky, that is fixed in the latest version.

But as for accuracy, even using your project it still was reading accurately.

The latest beta 3.0.11 addresses the data log bug.
http://www.tunerstudio.com/index.php/do ... ngelogmenu


If it is a consistent error %, then we can create a custom channel, that scales the odometer then point your odometer at that channel.

use a channel formula of:

Code: Select all

   odometerScaleValue  = { 0.5 }
   tsDistanceTraveledMilesStored = { persistentAccumulate( odometerScaleValue * (tsInputSpeedMPH / 3600) * (deltatime) ) }, "Miles"

Use the value 0.5 as a starting point for odometerScaleValue as it is about double, then raise it or lower it until it is accumulating accurately.

I considered adding a trim factor in this manor right to the dialog, but didn't want to do this unless significant drift proves to be common.

[dsmcrzy]

Thank you Phil. I'll work with that channel on my end and take a few more trip samples, but on my end it does seem like halfing it would yield pretty accurate results.

Thanks again!

[LT401Vette]

One clarification to the above...

if using tsDistanceTraveledMilesStored as the channel name as in the above, your odometer will already be pointing at the odometer channel. That is the name TS is already using, so in a custom.ini your new definition will over-ride the underlying.

For the trip meter, use:
tsDistanceTraveledMiles = { accumulate( odometerScaleValue * (tsInputSpeedMPH / 3600) * (deltatime) ) }, "Miles"