Incorrect RANGE in dashboard
Answered
Hey - just signed up for the trial and linked to ABRP. Most functions seems to work right away but I have a challenge with the range.
I'm in the UK so displaying in MILES but the calculated figure is incorrect. When I switch to KM the absolute number is correct @203 but is equal to the distance in MILES shown in the vehicle. Ie. the TRONITY Dashboard displays 203 KM while the car shows 203 MILES. If I switch to MILES in the TRONITY Dashboard it changes to 126 Miles.
Clearly it's just a calculation in the coding but it's incorrect - how can I fix this so the data transferred out to ABRP is correct.
(Vehicle: 2022 Porsche Taycan)
-
It indeed sounds a bit like a bug with unit conversion.
I am not sure, whether the Tronity support monitors this forum all the time. Maybe its better you directly contact them with your bug report using the request form linked on upper right of this page.
0 -
I will certainly do as you suggest….
0 -
Mark Graves please send an example to support@tronity.io
0 -
The issue has now corrected and mileage/range is accurate. Apparently a charge resolved this and it’s working great.
Next issue is the GPS is way off! This must be a vehicle issue I guess.
0 -
Hi Mark, for some areas, there is currently an issue with the GPS mapping which we could correct for you in our backend. The OEM is on the issue to solve it to overcome manuel adjustments in the future.
Best
Nils
1 -
Ok great - do I need to send a request in to fix that issue?
I really like the functionality of the system so will be setting up the full subscription when the trial ends.
0 -
Hi Mark Graves OEM is working on a fix - expected by end of this week. After this is validated we would take care of the trips that are corrupted. I would ask you to please file a case via support@tronity.io
Best, Nils
0 -
I have the wrong range too, in the vehicle tab, but is not subordinated to mi km conversion
0 -
Another occurrence, but the other way around. On the insights tab, the range is displayed as 513 km, which should instead be 319. The number is displayed correctly on the website, but in app seems to be assumed than 319 is miles and therfore the displayed number in km is wrong.
0
Please sign in to leave a comment.
Comments
9 comments