<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr">Just had a thought.</div><div dir="ltr"><br></div><div dir="ltr">Events used to be synchronous, but we switched to deliver in a different task. Maybe the startup sequence relies on that in some way.</div><div dir="ltr"><br><blockquote type="cite">On 30 Jan 2020, at 6:32 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div dir="ltr">Seems identical. The changes don’t seem to affect the dispatch of the system.start event.</div><div dir="ltr"><br></div><div dir="ltr">I think it must be a race condition.</div><div dir="ltr"><br></div><div dir="ltr">Mark</div><div dir="ltr"><br><blockquote type="cite">On 30 Jan 2020, at 5:56 PM, Michael Balzer <dexter@expeedo.de> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr">
  
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  
  
    <div class="moz-cite-prefix">Mark,<br>
      <br>
      a similar issue was happening on some Smart ED and fixed by
      Dimitrie later on:<br>
      <br>
<a class="moz-txt-link-freetext" 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:<br>
    </div>
    <blockquote type="cite" cite="mid:B8E1DC41-A780-43CC-B5FA-5D7C0E6BA7B1@webb-johnson.net">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      Still stumped…
      <div class=""><br class="">
      </div>
      <div class="">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.</div>
      <div class=""><br class="">
      </div>
      <div class="">But why is StandardMetrics.ms_m_version empty (as is
        the hardware value as well).</div>
      <div class=""><br class="">
      </div>
      <div class="">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.</div>
      <div class=""><br class="">
      </div>
      <div class="">MDNS outputs “Starting MDNS” when it sees that. The
        ovms_time sets the environment variable TZ. Your car is showing:</div>
      <div class=""><br class="">
      </div>
      <blockquote style="margin: 0 0 0 40px; border: none; padding:
        0px;" class="">
        <div class="">
          <div class="">ovms> time status</div>
          <div class="">...</div>
          <div class="">Vehicle Response:</div>
          <div class="">  Time Zone:  Not defined</div>
          <div class="">  UTC Time:   2020-01-30 05:00:53 UTC</div>
          <div class="">  Local Time: 2020-01-30 05:00:53 GMT</div>
          <div class="">  Provider:   None</div>
        </div>
      </blockquote>
      <div class="">
        <div class="">
          <div><br class="">
          </div>
          <div>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.</div>
          <div><br class="">
          </div>
          <div>So, tried a hacky test:</div>
          <div><br class="">
          </div>
        </div>
      </div>
      <blockquote style="margin: 0 0 0 40px; border: none; padding:
        0px;" class="">
        <div class="">
          <div class="">
            <div>
              <div>ovms> metric list version</div>
              <div>...</div>
              <div>Vehicle Response:</div>
              <div>  m.version</div>
              <div><br class="">
              </div>
              <div>
                <div>ovms> event raise system.start</div>
                <div>...</div>
                <div>Vehicle Response:</div>
                <div>  Raising event: system.start</div>
                <div><br class="">
                </div>
                <div>
                  <div>ovms> metric list version</div>
                  <div>...</div>
                  <div>Vehicle Response:</div>
                  <div>  m.version                              
                     3.2.008-121-g4c6c9fe/ota_0/edge (build idf
                    v3.3-beta3-775-gdc1ca69 Jan 29 2020 00:00:52)</div>
                  <div><br class="">
                  </div>
                  <div>
                    <div>ovms> ota status</div>
                    <div>...</div>
                    <div>Vehicle Response:</div>
                    <div>  Firmware:        
                       3.2.008-121-g4c6c9fe/ota_0/edge (build idf
                      v3.3-beta3-775-gdc1ca69 Jan 29 2020 00:00:52)</div>
                    <div>  Running partition: ota_0</div>
                    <div>  Boot partition:    ota_0</div>
                    <div>  Factory image:     3.1.001</div>
                    <div>  OTA_O image:       3.2.008-121-g4c6c9fe</div>
                    <div>  OTA_1 image:       3.2.008-121-g4c6c9fe</div>
                    <div>  Server Available:  3.2.008-121-g4c6c9fe (no
                      update required)</div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </blockquote>
      <div class="">
        <div class="">
          <div><br class="">
          </div>
          <div>🤢</div>
          <div><br class="">
          </div>
          <div>Can you try to boot from USB (module reset) and provide
            the serial boot log? Particularly around the lines ’Starting
            USB console’.</div>
          <div><br class="">
          </div>
          <div>Maybe a race condition at startup, or some other issue
            delivering events early on?</div>
          <div><br class="">
          </div>
          <div>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.</div>
          <div><br class="">
          </div>
          <div>Regards, Mark.</div>
          <div><br class="">
            <blockquote type="cite" class="">
              <div class="">On 30 Jan 2020, at 11:55 AM, Mark
                Webb-Johnson <<a href="mailto:mark@webb-johnson.net" class="" moz-do-not-send="true">mark@webb-johnson.net</a>>
                wrote:</div>
              <br class="Apple-interchange-newline">
              <div class="">
                <meta http-equiv="Content-Type" content="text/html;
                  charset=UTF-8" class="">
                <div style="word-wrap: break-word; -webkit-nbsp-mode:
                  space; line-break: after-white-space;" class="">Greg,
                  <div class=""><br class="">
                  </div>
                  <div class="">It seems your car can’t pickup currently
                    running firmware version:</div>
                  <div class=""><br class="">
                  </div>
                  <blockquote style="margin: 0 0 0 40px; border: none;
                    padding: 0px;" class="">
                    <div class="">ovms> open ROADSTER834B</div>
                    <div class="">Connected and logged in to
                      ROADSTER834B</div>
                    <div class="">
                      <div class="">ovms> metric list version</div>
                      <div class="">...</div>
                      <div class="">Vehicle Response:</div>
                      <div class="">  m.version</div>
                    </div>
                  </blockquote>
                  <div class="">
                    <div class=""><br class="">
                    </div>
                    <div class="">By comparison, here’s mine:</div>
                    <div class=""><br class="">
                    </div>
                  </div>
                  <blockquote style="margin: 0 0 0 40px; border: none;
                    padding: 0px;" class="">
                    <div class="">
                      <div class="">
                        <div class="">ovms> metric list version</div>
                        <div class="">...</div>
                        <div class="">Vehicle Response:</div>
                        <div class="">  m.version                      
                                   3.2.008-121-g4c6c9fe/ota_1/edge
                          (build idf v3.3-beta3-775-gdc1ca69 Jan 29 2020
                          00:00:52)</div>
                        <div class="">ovms> ota status</div>
                        <div class="">...</div>
                        <div class="">Vehicle Response:</div>
                        <div class="">  Firmware:        
                           3.2.008-121-g4c6c9fe/ota_1/edge (build idf
                          v3.3-beta3-775-gdc1ca69 Jan 29 2020 00:00:52)</div>
                        <div class="">  Running partition: ota_1</div>
                        <div class="">  Boot partition:    ota_1</div>
                        <div class="">  Factory image:     3.2.002</div>
                        <div class="">  OTA_O image:      
                          3.2.008-120-gcfb7864</div>
                        <div class="">  OTA_1 image:      
                          3.2.008-121-g4c6c9fe</div>
                      </div>
                    </div>
                  </blockquote>
                  <div class="">
                    <div class=""><br class="">
                    </div>
                    <div class="">Your m.hardware metric is also blank.</div>
                    <div class=""><br class="">
                    </div>
                    <div class="">I’ll keep looking, but at the moment
                      this seems bizarre.</div>
                    <div class=""><br class="">
                    </div>
                    <div class="">Regards, Mark.</div>
                    <div class=""><br class="">
                      <blockquote type="cite" class="">
                        <div class="">On 30 Jan 2020, at 11:21 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="">
                          <div class="">Hi Mark, Michael,<br class="">
                            <br class="">
                            Seems like what is happening is that the
                            module keeps thinking a new<br class="">
                            update is available.  Today was especially
                            active for some reason. <br class="">
                            Screenshot of the Android application's log
                            screen, attached.  All<br class="">
                            versions appear to be the same.  The car has
                            simply been sitting in the<br class="">
                            garage on WiFi; no transitions of network
                            access.<br class="">
                            <br class="">
                            Output of 'ota status' attached as well.<br class="">
                            <br class="">
                            Sorry, but I don't appear to have logging
                            enabled. What specifically<br class="">
                            would you like logged?<br class="">
                            <br class="">
                            Greg<br class="">
                            <br class="">
                            <br class="">
                            Mark Webb-Johnson wrote:<br class="">
                            <blockquote type="cite" class="">Not normal.
                              Can you send us the logs. Also the output
                              of ‘ota status’ would be helpful.<br class="">
                              <br class="">
                              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 class="">
                              <br class="">
                              Regards, Mark.<br class="">
                              <br class="">
                              <blockquote type="cite" class="">On 25 Jan
                                2020, at 11:35 AM, Greg D. <<a href="mailto:gregd2350@gmail.com" class="" moz-do-not-send="true">gregd2350@gmail.com</a>>
                                wrote:<br class="">
                                <br class="">
                                Hi folks,<br class="">
                                <br class="">
                                I moved my car's OVMSv3 to the Edge
                                firmware a bit ago, and notice that<br class="">
                                every update seems to be doubled.
                                 Besides being a bit annoying, it ends<br class="">
                                up without a previous version to fall
                                back to since both partitions end<br class="">
                                up being the same.<br class="">
                                <br class="">
                                Is this behavior normal?  Can it be
                                prevented?<br class="">
                                <br class="">
                                I'm only on Edge because of the bug in
                                obd2ecu, and will probably move<br class="">
                                to EAP after we get an EAP build with
                                the fix in it.  Is the behavior<br class="">
                                the same there?<br class="">
                                <br class="">
                                I used to be on Main, and all seemed
                                fine there.<br class="">
                                <br class="">
                                Thanks,<br class="">
                                <br class="">
                                Greg<br class="">
                                <br class="">
_______________________________________________<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 href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
                              </blockquote>
_______________________________________________<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 href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
                            </blockquote>
                            <br class="">
                            <span id="cid:F04A596F-9B1F-4F12-850B-D3A1AF5B2E80" class=""><Repeated updates.png></span><span id="cid:524D6E91-8B2C-41EF-854C-07B316B2D57D" class=""><Repeated
                              updates ota status output.txt></span>_______________________________________________<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 href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev" class="" moz-do-not-send="true">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br class="">
                          </div>
                        </div>
                      </blockquote>
                    </div>
                    <br class="">
                  </div>
                </div>
              </div>
            </blockquote>
          </div>
          <br class="">
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-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>
    <br>
    <pre class="moz-signature" cols="144">-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
</pre>
  

<span>_______________________________________________</span><br><span>OvmsDev mailing list</span><br><span>OvmsDev@lists.openvehicles.com</span><br><span>http://lists.openvehicles.com/mailman/listinfo/ovmsdev</span><br></div></blockquote><span>_______________________________________________</span><br><span>OvmsDev mailing list</span><br><span>OvmsDev@lists.openvehicles.com</span><br><span>http://lists.openvehicles.com/mailman/listinfo/ovmsdev</span><br></div></blockquote></body></html>