Reset Standard Metrics on vehicle change
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
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
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
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
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
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
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
On 2020-09-10 04:33, Soko wrote:
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?
Since persistent metrics are reset on a cold boot I'm curious about a "hot" vehicle change happens. Is it a matter of leaving the ovms module plugged into and powered by a laptop and then moving it between obd-ii ports on two different cars? Craig
Heya, We have now two vehicle-implementations for the same vehicle: VW eUp via T26A or via OBD. So this is kinda valid now... And I'm not sure what you mean by cold boot, but persistent metrics are stored in RTC memory so they survive any reboot afaik. Soko On 10.09.2020 21:59, Craig Leres wrote:
On 2020-09-10 04:33, Soko wrote:
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?
Since persistent metrics are reset on a cold boot I'm curious about a "hot" vehicle change happens. Is it a matter of leaving the ovms module plugged into and powered by a laptop and then moving it between obd-ii ports on two different cars?
Craig
By cold reboot I suppose he means unplugging from one car and plugging into the other. Powering down the module for some time. I think this is a pretty rare occurrence and can probably be handler easier by telling people to clear the persistent metrics and reboot if they are switching from T26A to OBD (or the other way). Regards, Mark
On 11 Sep 2020, at 2:15 PM, Soko <ovms@soko.cc> wrote:
Heya,
We have now two vehicle-implementations for the same vehicle: VW eUp via T26A or via OBD. So this is kinda valid now...
And I'm not sure what you mean by cold boot, but persistent metrics are stored in RTC memory so they survive any reboot afaik.
Soko
On 10.09.2020 21:59, Craig Leres wrote:
On 2020-09-10 04:33, Soko wrote:
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?
Since persistent metrics are reset on a cold boot I'm curious about a "hot" vehicle change happens. Is it a matter of leaving the ovms module plugged into and powered by a laptop and then moving it between obd-ii ports on two different cars?
Craig
OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
participants (4)
-
Craig Leres -
Mark Webb-Johnson -
Michael Balzer -
Soko