<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:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
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 Vorformatiert Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLVorformatiertZchn
{mso-style-name:"HTML Vorformatiert Zchn";
mso-style-priority:99;
mso-style-link:"HTML Vorformatiert";
font-family:"Consolas",serif;}
span.E-MailFormatvorlage22
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
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=DE link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>The issue was on boot, the events: SignalEvent: queue overflow, event 'system.start' dropped in some case.<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'>the problem was the egpio settings in OvmsVehicleSmartED::ConfigChanged(OvmsConfigParam* param)<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'><a href="https://github.com/Dimitrie78/Open-Vehicle-Monitoring-System-3/commit/21e1a0339c029adf5c746dfd6fecddbc9455a947#diff-9106f33dff1f6160884b2e78d145607fL155-L160">https://github.com/Dimitrie78/Open-Vehicle-Monitoring-System-3/commit/21e1a0339c029adf5c746dfd6fecddbc9455a947#diff-9106f33dff1f6160884b2e78d145607fL155-L160</a><o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>line 155 – 160<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>Von:</b> OvmsDev <ovmsdev-bounces@lists.openvehicles.com> <b>Im Auftrag von </b>Mark Webb-Johnson<br><b>Gesendet:</b> Donnerstag, 30. Januar 2020 11:35<br><b>An:</b> OVMS Developers <ovmsdev@lists.openvehicles.com><br><b>Betreff:</b> Re: [Ovmsdev] Double updates - Normal?<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Just had a thought.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Events used to be synchronous, but we switched to deliver in a different task. Maybe the startup sequence relies on that in some way.<o:p></o:p></p></div><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-bottom:12.0pt'>On 30 Jan 2020, at 6:32 PM, Mark Webb-Johnson <<a href="mailto:mark@webb-johnson.net">mark@webb-johnson.net</a>> wrote:<o:p></o:p></p></blockquote></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal><o:p></o:p></p><div><p class=MsoNormal>Seems identical. The changes don’t seem to affect the dispatch of the system.start event.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I think it must be a race condition.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Mark<o:p></o:p></p></div><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-bottom:12.0pt'>On 30 Jan 2020, at 5:56 PM, Michael Balzer <<a href="mailto:dexter@expeedo.de">dexter@expeedo.de</a>> wrote:<o:p></o:p></p></blockquote></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal> <o:p></o:p></p><div><p class=MsoNormal>Mark,<br><br>a similar issue was happening on some Smart ED and fixed by Dimitrie later on:<br><br><a href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/293">https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/293</a><br><br>I thought that was a Smart specific issue, maybe I was wrong.<br><br>Regards,<br>Michael<br><br><br>Am 30.01.20 um 06:17 schrieb Mark Webb-Johnson:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>Still stumped… <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The OTA code doesn’t call GetOVMSVersion(), but instead just looks at StandardMetrics.ms_m_version (which we know is blank). That is why this is happening.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>But why is StandardMetrics.ms_m_version empty (as is the hardware value as well).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The ovms_version code hooks into ’system.start’ event, and sets the version and hardware metrics. So, obviously that is not being called. That event is raised just after ’Starting USB console…”. The event is also listened to be ovms_time, ovms_mdns, and swcan.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>MDNS outputs “Starting MDNS” when it sees that. The ovms_time sets the environment variable TZ. Your car is showing:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><blockquote style='margin-left:30.0pt;margin-right:0cm'><div><div><p class=MsoNormal>ovms> time status<o:p></o:p></p></div><div><p class=MsoNormal>...<o:p></o:p></p></div><div><p class=MsoNormal>Vehicle Response:<o:p></o:p></p></div><div><p class=MsoNormal> Time Zone: Not defined<o:p></o:p></p></div><div><p class=MsoNormal> UTC Time: 2020-01-30 05:00:53 UTC<o:p></o:p></p></div><div><p class=MsoNormal> Local Time: 2020-01-30 05:00:53 GMT<o:p></o:p></p></div><div><p class=MsoNormal> Provider: None<o:p></o:p></p></div></div></blockquote><div><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>So looks like TZ is not being set. Presumably that means the call is not happening. I had a look at the ovms_events code, but can’t find anything obvious.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>So, tried a hacky test:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div><blockquote style='margin-left:30.0pt;margin-right:0cm'><div><div><div><div><p class=MsoNormal>ovms> metric list version<o:p></o:p></p></div><div><p class=MsoNormal>...<o:p></o:p></p></div><div><p class=MsoNormal>Vehicle Response:<o:p></o:p></p></div><div><p class=MsoNormal> m.version<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>ovms> event raise system.start<o:p></o:p></p></div><div><p class=MsoNormal>...<o:p></o:p></p></div><div><p class=MsoNormal>Vehicle Response:<o:p></o:p></p></div><div><p class=MsoNormal> Raising event: system.start<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>ovms> metric list version<o:p></o:p></p></div><div><p class=MsoNormal>...<o:p></o:p></p></div><div><p class=MsoNormal>Vehicle Response:<o:p></o:p></p></div><div><p class=MsoNormal> m.version 3.2.008-121-g4c6c9fe/ota_0/edge (build idf v3.3-beta3-775-gdc1ca69 Jan 29 2020 00:00:52)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>ovms> ota status<o:p></o:p></p></div><div><p class=MsoNormal>...<o:p></o:p></p></div><div><p class=MsoNormal>Vehicle Response:<o:p></o:p></p></div><div><p class=MsoNormal> Firmware: 3.2.008-121-g4c6c9fe/ota_0/edge (build idf v3.3-beta3-775-gdc1ca69 Jan 29 2020 00:00:52)<o:p></o:p></p></div><div><p class=MsoNormal> Running partition: ota_0<o:p></o:p></p></div><div><p class=MsoNormal> Boot partition: ota_0<o:p></o:p></p></div><div><p class=MsoNormal> Factory image: 3.1.001<o:p></o:p></p></div><div><p class=MsoNormal> OTA_O image: 3.2.008-121-g4c6c9fe<o:p></o:p></p></div><div><p class=MsoNormal> OTA_1 image: 3.2.008-121-g4c6c9fe<o:p></o:p></p></div><div><p class=MsoNormal> Server Available: 3.2.008-121-g4c6c9fe (no update required)<o:p></o:p></p></div></div></div></div></div></div></div></blockquote><div><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Segoe UI Emoji",sans-serif'>🤢</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Can you try to boot from USB (module reset) and provide the serial boot log? Particularly around the lines ’Starting USB console’.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Maybe a race condition at startup, or some other issue delivering events early on?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Only other thing I see are some scripts on /store/events regarding vehicle on/off - perhaps you can try disabling those to see if they trigger the issue? I tried recreating them on my box, but couldn’t repeat your problem.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards, Mark.<o:p></o:p></p></div><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On 30 Jan 2020, at 11:55 AM, Mark Webb-Johnson <<a href="mailto:mark@webb-johnson.net">mark@webb-johnson.net</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Greg, <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>It seems your car can’t pickup currently running firmware version:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><blockquote style='margin-left:30.0pt;margin-right:0cm'><div><p class=MsoNormal>ovms> open ROADSTER834B<o:p></o:p></p></div><div><p class=MsoNormal>Connected and logged in to ROADSTER834B<o:p></o:p></p></div><div><div><p class=MsoNormal>ovms> metric list version<o:p></o:p></p></div><div><p class=MsoNormal>...<o:p></o:p></p></div><div><p class=MsoNormal>Vehicle Response:<o:p></o:p></p></div><div><p class=MsoNormal> m.version<o:p></o:p></p></div></div></blockquote><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>By comparison, here’s mine:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><blockquote style='margin-left:30.0pt;margin-right:0cm'><div><div><div><p class=MsoNormal>ovms> metric list version<o:p></o:p></p></div><div><p class=MsoNormal>...<o:p></o:p></p></div><div><p class=MsoNormal>Vehicle Response:<o:p></o:p></p></div><div><p class=MsoNormal> m.version 3.2.008-121-g4c6c9fe/ota_1/edge (build idf v3.3-beta3-775-gdc1ca69 Jan 29 2020 00:00:52)<o:p></o:p></p></div><div><p class=MsoNormal>ovms> ota status<o:p></o:p></p></div><div><p class=MsoNormal>...<o:p></o:p></p></div><div><p class=MsoNormal>Vehicle Response:<o:p></o:p></p></div><div><p class=MsoNormal> Firmware: 3.2.008-121-g4c6c9fe/ota_1/edge (build idf v3.3-beta3-775-gdc1ca69 Jan 29 2020 00:00:52)<o:p></o:p></p></div><div><p class=MsoNormal> Running partition: ota_1<o:p></o:p></p></div><div><p class=MsoNormal> Boot partition: ota_1<o:p></o:p></p></div><div><p class=MsoNormal> Factory image: 3.2.002<o:p></o:p></p></div><div><p class=MsoNormal> OTA_O image: 3.2.008-120-gcfb7864<o:p></o:p></p></div><div><p class=MsoNormal> OTA_1 image: 3.2.008-121-g4c6c9fe<o:p></o:p></p></div></div></div></blockquote><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Your m.hardware metric is also blank.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I’ll keep looking, but at the moment this seems bizarre.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards, Mark.<o:p></o:p></p></div><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On 30 Jan 2020, at 11:21 AM, Greg D. <<a href="mailto:gregd2350@gmail.com">gregd2350@gmail.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Hi Mark, Michael,<br><br>Seems like what is happening is that the module keeps thinking a new<br>update is available. Today was especially active for some reason. <br>Screenshot of the Android application's log screen, attached. All<br>versions appear to be the same. The car has simply been sitting in the<br>garage on WiFi; no transitions of network access.<br><br>Output of 'ota status' attached as well.<br><br>Sorry, but I don't appear to have logging enabled. What specifically<br>would you like logged?<br><br>Greg<br><br><br>Mark Webb-Johnson wrote:<br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>Not normal. Can you send us the logs. Also the output of ‘ota status’ would be helpful.<br><br>Are you sure this isn't just a notification of the update, and is the update itself? Perhaps a screenshot of the double notifications you receive?<br><br>Regards, Mark.<br><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>On 25 Jan 2020, at 11:35 AM, Greg D. <<a href="mailto:gregd2350@gmail.com">gregd2350@gmail.com</a>> wrote:<br><br>Hi folks,<br><br>I moved my car's OVMSv3 to the Edge firmware a bit ago, and notice that<br>every update seems to be doubled. Besides being a bit annoying, it ends<br>up without a previous version to fall back to since both partitions end<br>up being the same.<br><br>Is this behavior normal? Can it be prevented?<br><br>I'm only on Edge because of the bug in obd2ecu, and will probably move<br>to EAP after we get an EAP build with the fix in it. Is the behavior<br>the same there?<br><br>I used to be on Main, and all seemed fine there.<br><br>Thanks,<br><br>Greg<br><br>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a><br><a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><o:p></o:p></p></blockquote><p class=MsoNormal>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a><br><a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><o:p></o:p></p></blockquote><p class=MsoNormal><br><Repeated updates.png><Repeated updates ota status output.txt>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a><br><a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><o:p></o:p></p></div></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></blockquote></div><p class=MsoNormal><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><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><p class=MsoNormal>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a><br><a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><o:p></o:p></p></div></blockquote><p class=MsoNormal>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a><br><a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><o:p></o:p></p></div></blockquote></div></body></html>