Hi
Mark,
Yes, I understand that. Not expecting such a
dramatic change as saving data in NV RAM. The end
user presumably won't have their module rebooting
very often, so this isn't worth trying to save stuff
across reboots.
I'm trying think back to when the behavior started
to change. It might have been when I moved off the
Main branch to Edge because of the bug with OBD2ECU
CAN initialization, so module reboots are far more
frequent. I'm tempted to get back on Main, or at
least EAP, but I'm also vaguely remembering that
there was a change related specifically to "stale"
data that put a lot of data out of reach for a day.
This latest UI behavior change was the straw that
caused me to write.
It seems like populating data takes a lot longer now
than, say, 6 months ago. Did something change a
while back that has led to this? Part of the
puzzle, perhaps, is that we have two moving pieces,
the Module and the App. I'm on Android, if that
matters.
Greg
Mark Webb-Johnson
wrote:
Greg,
I think the issue you have is that
after a firmware update the module will reboot.
That will mean it will lose the metrics for
TPMS.
Those metrics won’t come back until
the car has been driven.
I don’t see a simple solution. We
could address it in v2 protocol by not sending
the tpms message unless the metrics are defined,
but that might still mess up the stale
indicator. That wouldn’t affect the individual
metrics and v3 protocol we are trying to move to
for the future.
There is a small amount of RTC ram
that is retained through a reboot. Perhaps we
could have a mechanism to save+restore certain
metrics there? But not at all simple.
Regards, Mark.
Hi Mark, Michael,
I am on Edge, and it updated 2am local
on the 20th (2 days ago).
Firmware: 3.2.011-13-g7d83320/ota_0/edge
(build idf v3.3-beta3-775-gdc1ca69 Apr
20 2020 15:10:37). The app is 3.16.1
(2020031801).
I just put the car in Drive for a few
minutes, and all the stats got
populated. The car is off and sleeping
now, so I'll check it again in the
morning.
Greg
p.s. Just saw your EAP announcement.
With the 3.2.012 code coming, it will be
interesting to see what happens after
the reset. I'll let you know!
Mark
Webb-Johnson wrote:
Greg,
What firmware version
are you running in the module? If
EAP/MAIN 3.2.011, can you try
updating to the edge release? I
suspect you are seeing the bug with
3.2.011 and the TPMS protocol v2
message.
Regards, Mark.
Hi folks,
So, I seem to be going
backwards with OVMS and my
Tesla Roadster...
I'm looking at the OVMS app
on my Android phone.
Used to be that I'd see the
TPMS data - pressure and
temperature - as it was the
last time the car was
driven.
Then it turned into zeros.
Today I see it's gone
altogether. This is not
progress.
What I want to see is the
data from the car, as last
it was read. I do not care
that it is not live. In
fact, if it were live, that
would mean that the car is
in Drive, which (hopefully)
means that I am in my car.
If so, I have no
use for the OVMS, as
the data is sitting right
there on the car's display.
Is there any way to get the
old functionality back?
Greg
_______________________________________________
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
_______________________________________________
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