Trip Summary - Incorrect Values

Here you can ask technical questions about UTCOMP-3 / UTCOMP-PRO compatibility and features.
Post Reply
DArtagnon
Posts: 21
Joined: Thu Jan 17, 2019 3:49 am
Has thanked: 1 time

Trip Summary - Incorrect Values

Post by DArtagnon »

I've noticed on the trip summary page during power off has incorrect values, the Vavg and Vmax are entirely wrong. Any thoughts on how to correct? The speedometer function works...
20200616_124423.jpg
20200616_124423.jpg (668.85 KiB) Viewed 15047 times
Matthew

PS - Oddly the MPG value is correct... but I don't have a fuel flow sensor! So I'm not even sure how it is calculating that.... but I've not paid close attention to see if it is always right.
ArT
Posts: 1602
Joined: Wed Mar 25, 2015 8:54 am
Location: Warsaw, Poland
Has thanked: 61 times
Been thanked: 171 times

Re: Trip Summary - Incorrect Values

Post by ArT »

Trip is calculated from 2 fuels. Have you updated utcomp last time? (-256 vmax is after update). Please restart trip statistics and let me know how it looks like after some trip.
DArtagnon
Posts: 21
Joined: Thu Jan 17, 2019 3:49 am
Has thanked: 1 time

Re: Trip Summary - Incorrect Values

Post by DArtagnon »

ArT wrote:Trip is calculated from 2 fuels. Have you updated utcomp last time? (-256 vmax is after update). Please restart trip statistics and let me know how it looks like after some trip.

I don't understand "trip is calculated from 2 fuels".. what does that mean.
I am running 3.7
I'll have to figure out how to reset the trip statistics. Is that some button presses or do I have to use the program?
ArT
Posts: 1602
Joined: Wed Mar 25, 2015 8:54 am
Location: Warsaw, Poland
Has thanked: 61 times
Been thanked: 171 times

Re: Trip Summary - Incorrect Values

Post by ArT »

Long press SW3 to reset trip.
Trip is calculated from 2 fuel signals connected to pins A10 and A11 (second is optional).
DArtagnon
Posts: 21
Joined: Thu Jan 17, 2019 3:49 am
Has thanked: 1 time

Re: Trip Summary - Incorrect Values

Post by DArtagnon »

Thanks Art! That fixed it.
Post Reply