Let's say with the two VWUP it's the first time this use case even makes sense ;-) But I will forward him the command, thanks Soko On 10.09.2020 14:18, Michael Balzer wrote:
So you've got a user who switches between two different vehicles without taking the module offline?
Well… that's not actually a common use case, is it? ;-)
I'd expect a user doing this to know how to do a "metrics persist -r" if needed…
Regards, Michael
Am 10.09.20 um 14:10 schrieb Soko:
Heya,
In this particular case:
The user changes between VWUP.T26 and VWUP.OBD and was wondering about the weird range metrics...
The issue is that OBD doesn't set the range... or T26 doesn't set the voltage. So he is left with values in the metrics although those are not set by the current/active vehicle.
Soko
On 10.09.2020 14:06, Michael Balzer wrote:
Soko,
what do you mean by vehicle change?
Regards, Michael
Am 10.09.20 um 13:33 schrieb Soko:
Hi again,
Another issue reported is about (persistent) metrics who keep there value after vehicle change. First I thought the vehicles need to address this. But wouldn't it be better that all standard metrics get a reset on every vehicle change?
Soko
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev