[Ovmsdev] Reset Standard Metrics on vehicle change
mark at webb-johnson.net
Fri Sep 11 14:22:18 HKT 2020
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).
> On 11 Sep 2020, at 2:15 PM, Soko <ovms at soko.cc> wrote:
> 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.
> 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?
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
More information about the OvmsDev