<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Mark,<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
Greg<br>
<br>
<br>
<div class="moz-cite-prefix">Mark Webb-Johnson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:93BA45A0-4637-4B13-B1A9-24F5EDEDC3CB@webb-johnson.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Greg,
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">Those metrics won’t come back until the car has been
driven.</div>
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark.<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 22 Apr 2020, at 11:07 AM, Greg D. <<a
href="mailto:gregd2350@gmail.com" class=""
moz-do-not-send="true">gregd2350@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""> Hi Mark,
Michael,<br class="">
<br class="">
I am on Edge, and it updated 2am local on the 20th (2
days ago).
<meta http-equiv="content-type" content="text/html;
charset=UTF-8" class="">
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).<br class="">
<br class="">
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. <br
class="">
<br class="">
Greg<br class="">
<br class="">
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!<br class="">
<br class="">
<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Mark Webb-Johnson wrote:<br
class="">
</div>
<blockquote type="cite"
cite="mid:05748430-9C2F-4120-9140-6B79632B7B45@webb-johnson.net"
class="">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" class="">
Greg,
<div class=""><br class="">
</div>
<div class="">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.</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark.<br class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">On 22 Apr 2020, at 4:09 AM, Greg
D. <<a href="mailto:gregd2350@gmail.com"
class="" moz-do-not-send="true">gregd2350@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="content-type"
content="text/html; charset=UTF-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
Hi folks,<br class="">
<br class="">
So, I seem to be going backwards with OVMS
and my Tesla Roadster...<br class="">
<br class="">
I'm looking at the OVMS app on my Android
phone. <br class="">
<br class="">
Used to be that I'd see the TPMS data -
pressure and temperature - as it was the
last time the car was driven. <br class="">
<br class="">
Then it turned into zeros.<br class="">
<br class="">
Today I see it's gone altogether. This is
not progress.<br class="">
<br class="">
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 <b class="">no use</b> for the
OVMS, as the data is sitting right there on
the car's display.<br class="">
<br class="">
Is there any way to get the old
functionality back?<br class="">
<br class="">
Greg<br class="">
</div>
_______________________________________________<br class="">
OvmsDev mailing list<br class="">
<a
href="mailto:OvmsDev@lists.openvehicles.com"
class="" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br
class="">
<a class="moz-txt-link-freetext"
href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev"
moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre class="" wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br
class="">
OvmsDev mailing list<br class="">
<a href="mailto:OvmsDev@lists.openvehicles.com" class=""
moz-do-not-send="true">OvmsDev@lists.openvehicles.com</a><br
class="">
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a>
<a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
</body>
</html>