<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">@Chris: Thanks for the reminder - I am aware of it and that was the area of code I fixed for 3.2.012. The issue was a simple typo - missing the comma between the left rear tyre temperature and the stale indicator.<div class=""><br class=""></div><div class="">@Greg:</div><div class=""><br class=""></div><div class="">The approach Chris mentioned indeed differentiated between a metric NEVER being defined (by a car module) and the value merely being stale (not currently updated). It should not affect the roadster.</div><div class=""><br class=""></div><div class="">There are four types of sensor (in the roadster modules at least):</div><div class=""><br class=""></div><div class=""><ol class="MailOutline"><li class="">One that transmit continuously, and always, no matter the state of the car (e.g. SOC%).</li><li class="">One that transmits only while the car is awake (e.g. PEM temperature).</li><li class="">One that transmits only when the car is doing something (e.g. TPMS).</li><li class="">One that transmits only on specific request (e.g. CAC).</li></ol></div><div class=""><br class=""></div><div class="">We typically can’t control those (although in the case of #2 we can in some circumstances wake up the car to force it to update the sensor, but that has other consequences).</div><div class=""><br class=""></div><div class="">In the case of TPMS in the roadster, when the module resets we don’t have any record of the TPMS value. We also have no known way to request the car to transmit it. There is also a limitation of the TPMS (W) message in OVMS protocol v2 in that the stale indicator is at the end of the message so we can’t update that indicator without also transmitting the TPMS values. So, we are faced with three choices:</div><div class=""><br class=""></div><div class=""><ol class="MailOutline"><li class="">Don’t transmit any TPMS (W) message at all. The App will then get the old stored value from the server, but the stale sensor maybe incorrect. Not good.</li><li class="">Transmit a TPMS (W) message, using zeros for temperatures and pressures. Terrible for a car like the roadster that supports TPMS.</li><li class="">Transmit a TPMS (W) message, with a ’stale' indicator to show that the TPMS values are not defined / valid at all.</li></ol></div><div class=""><br class=""></div><div class="">We chose #3, as it seems the best we can do.</div><div class=""><br class=""></div><div class="">The current behaviour (with 3.2.012) should be that if you drive the car, the TPMS should be shown in bright white. If you then park, after some time the values will go stale and show as gray in the App. That should continue, so long as you don’t reboot the module. If you reboot the module, the TPMS will be lost and the App won’t show the values until you next drive the car. That is the best we can do with v2 protocol, imho.</div><div class=""><br class=""></div><div class="">Please try it for a few days, without rebooting the module, and make sure that works for you as above.</div><div class=""><br class=""></div><div class="">Regards, Mark.</div><div class=""><br class=""></div><div class="">P.S. <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">From a metric point of view, I am convinced that the approach we currently have of a metric recording meta data on whether it has ever been set (defined), if it has not been updated for a while (stale), as well as the value itself (with units) is the correct one. We need to think about protocol v3 and the future - in particular how the stale and defined meta data can be indicated to apps.</span></div><div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><br class=""></span></div><div class=""><div><blockquote type="cite" class=""><div class="">On 23 Apr 2020, at 2:46 AM, Greg D. <<a href="mailto:gregd2350@gmail.com" class="">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="">
So, this is affecting ALL cars? Not what I would want to see. <br class="">
<br class="">
Fundamentally, there is a difference between a metric being
undefined for a vehicle, and one which the car supports but which
has not yet been populated. Did this fix take too broad a swipe at
the TPMS metric? That approach could get confusing over time, as
some cars support some metrics and not others.<br class="">
<br class="">
Greg<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Chris van der Meijden wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:1587580472.3727.12.camel@arachnon.de" class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
<div class="">Hi all</div>
<div class=""><br class="">
</div>
<div class="">I would like to point to this thread:</div>
<div class=""><br class="">
</div>
<div class=""><a href="http://lists.openvehicles.com/pipermail/ovmsdev/2020-March/006730.html" moz-do-not-send="true" class="">http://lists.openvehicles.com/pipermail/ovmsdev/2020-March/006730.html</a></div>
<div class=""><br class="">
</div>
<div class="">The code for TMPS has been changed for vehicles that don't
support TPMS</div>
<div class=""><br class="">
</div>
<div class="">Regards</div>
<div class=""><br class="">
</div>
<div class="">Chris</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Am Mittwoch, den 22.04.2020, 11:23 -0700 schrieb Greg D.:</div>
<blockquote type="cite" class=""> Ok... So the module updated to EAP last
night, as expected. The display (screen shot) shows zeros for
Ambient, Charger/PEM, Motor, and battery; 12v is live, as is the
odometer. TPMS is missing. Is there a reason that the bulk of
the metrics aren't read? Are they not present on the CAN bus,
or is the module explicitly not watching for them until the car
wakes up?<br class="">
<br class="">
If I wake the car up, Ambient, Charger/PEM, motor, and battery
are immediately updated, but TPMS is still missing. <br class="">
<br class="">
For consistency and less confusion, I would like for the TPMS to
be populated in both screen shots, and showing zeros until the
car is driven. And by "consistency" I do NOT mean "remove the
other metrics too". I'm trying to be careful what I wish for...<br class="">
<br class="">
When I put it in Drive for a few minutes, the TPMS icons do
appear with live data. I'll let the car sit for a few days, and
see what happens to the display. What I expect is that they
will remain present, even if not live.<br class="">
<br class="">
Greg<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Greg D wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:D18AA4AA-203B-4435-8D9C-3832D3AA2EFA@gmail.com" class="">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8" class="">
Ok, EAP is set. Let's see what happens at 2am...<br class="">
<br class="">
Greg<br class="">
<br class="">
<br class="">
<div class="gmail_quote">On April 21, 2020 11:05:01 PM PDT,
Mark Webb-Johnson <a class="moz-txt-link-rfc2396E" href="mailto:mark@webb-johnson.net" moz-do-not-send="true"><mark@webb-johnson.net></a>
wrote:
<blockquote type="cite" class=""> I think best to move to EAP and see
if that improves the situation. On ‘edge’, you will be
getting an update (and reboot) once every night or two.
<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 12:58 PM, 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,<br class="">
<br class="">
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 class="">
<br class="">
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 class="">
<br class="">
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 class="">
<br class="">
Greg<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Mark Webb-Johnson
wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:93BA45A0-4637-4B13-B1A9-24F5EDEDC3CB@webb-johnson.net" class="">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" class="">
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 class=""><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" 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" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
<br class="">
</blockquote>
</div>
<br class="">
-- <br class="">
This space for rent... </blockquote>
<br class="">
<pre class="">_______________________________________________
OvmsDev mailing list
<a href="mailto:OvmsDev@lists.openvehicles.com" moz-do-not-send="true" class="">OvmsDev@lists.openvehicles.com</a>
<a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" moz-do-not-send="true" class="">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre wrap="" class="">_______________________________________________
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 class="">
</div>
_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.openvehicles.com" class="">OvmsDev@lists.openvehicles.com</a><br class="">http://lists.openvehicles.com/mailman/listinfo/ovmsdev<br class=""></div></blockquote></div><br class=""></div></body></html>