<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Yeah – I’ve got a patch to fix the comments/documentation on that and the other changes already up that changed the default format for m.time.utc and v.p.gpstime as well as now v.e.serv.time.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>I’ll do a p/r separately for this<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>//.ichael<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> OvmsDev <ovmsdev-bounces@lists.openvehicles.com> <b>On Behalf Of </b>Michael Balzer<br><b>Sent:</b> Sunday, December 3, 2023 3:33 PM<br><b>To:</b> ovmsdev@lists.openvehicles.com<br><b>Subject:</b> Re: [Ovmsdev] VWEUP module service interval?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Michael,<br><br>yes, v.e.serv.time is local time. Please also fix the comment "Time to", I think that remained from the initial draft.<br><br>IDF5 migration probably could use some help:<br><a href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/752#issuecomment-1791558855">https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/752#issuecomment-1791558855</a><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Segoe UI",sans-serif;color:#1F2328;background:white'>sorry to have been silent such a long time - I unfortunately have been busy on other subjects, and I didn't have the time (and still don't) to make significant progresses on the ESPv5+ front</span><o:p></o:p></p></blockquote><p class=MsoNormal style='margin-bottom:12.0pt'><br>Regards,<br>Michael<br><br><o:p></o:p></p><div><p class=MsoNormal>Am 03.12.23 um 03:13 schrieb Michael Geddes:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>Hey All,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I've been paving the way for 64 bit time_t that's apparently in the newer esp32 releases. I'm keen to know how that update to the newer sdk is going too?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>For persistence, I am registering the high 32bits as a second metric with "_hi" suffix (Similar to how the arrays work).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>One thing I've noticed is that there's a standard metric:<o:p></o:p></p></div><div><p class=MsoNormal> OvmsMetricInt* ms_v_env_service_time; // Time to next scheduled maintenance/service [Seconds]<o:p></o:p></p></div><div><p class=MsoNormal>cf the doc<o:p></o:p></p></div><div><p class=MsoNormal> v.e.serv.time 1572590910Sec Time of next scheduled maintenance/service [Seconds]<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>So it's a bit ambiguous but vweup (the only one who sets this metric) implementation treats this as a time_t.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I think I will convert it to a 64 bit 'DateLocal' metric. Thoughts?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>//.ichael<o:p></o:p></p></div></div><p class=MsoNormal><br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>OvmsDev mailing list<o:p></o:p></pre><pre><a href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a><o:p></o:p></pre><pre><a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><o:p></o:p></pre></blockquote><p class=MsoNormal><br><br><o:p></o:p></p><pre>-- <o:p></o:p></pre><pre>Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal<o:p></o:p></pre><pre>Fon 02333 / 833 5735 * Handy 0176 / 206 989 26<o:p></o:p></pre></div></body></html>