<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="">Craig,<div class=""><br class=""></div><div class=""><blockquote type="cite" class="">What's the status of the "for-v3.3" branch?</blockquote><div class=""><br class=""></div>That’s on me. I’ve been ill for the last month (not COVID, thankfully), and master has diverged from for-v3.3 causing conflicts. I hope to resolve this week.</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class="">Another question I had is what is the difference between:</blockquote></div><div class=""><br class=""></div><div class="">The v3.0 / v3.1 / v3.2 in the URL path refers to the _hardware_ version, not firmware. For all current hardware we should be using:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><a href="http://api.openvehicles.com/firmware/ota/v3.1/" class="">http://api.openvehicles.com/firmware/ota/v3.1/</a>...</div></blockquote><div class=""><div class=""><div><br class=""></div><div>The v3.2 path is not currently used. I’ve renamed it as ‘v3.2.obsolete’ in <a href="http://api.openvehicles.com" class="">api.openvehicles.com</a> to try to avoid confusion.</div><div><br class=""></div><div>Regards, Mark</div><div><br class=""><blockquote type="cite" class=""><div class="">On 8 Feb 2021, at 10:11 AM, Craig Leres <<a href="mailto:leres@xse.com" class="">leres@xse.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class="">What's the status of the "for-v3.3" branch? Last weekend after I upgraded the esp32-wroom module in my dev ovms box I tried updating and I couldn't get it to run. It would be nice to get the simcom refactoring into master (or at least catch for-v3.3 up with things like the persistent metrics update, etc). I'm not advocating this for 3.2.016, just expressing an interest in it happening in the near term.<br class=""><br class="">Another question I had is what is the difference between:<br class=""><br class=""> <a href="http://api.openvehicles.com/firmware/ota/v3.1/main/ovms3.bin" class="">http://api.openvehicles.com/firmware/ota/v3.1/main/ovms3.bin</a><br class=""> <a href="http://api.openvehicles.com/firmware/ota/v3.1/main/ovms3.ver" class="">http://api.openvehicles.com/firmware/ota/v3.1/main/ovms3.ver</a><br class=""><br class="">and:<br class=""><br class=""> <a href="http://api.openvehicles.com/firmware/ota/v3.2/main/ovms3.bin" class="">http://api.openvehicles.com/firmware/ota/v3.2/main/ovms3.bin</a><br class=""> <a href="http://api.openvehicles.com/firmware/ota/v3.2/main/ovms3.ver" class="">http://api.openvehicles.com/firmware/ota/v3.2/main/ovms3.ver</a><br class=""><br class="">The v3.1 version currently points to 3.2.15 and the v3.2 version points to 3.2.008 which wasn't what I was expecting when I was looking for a 3.2.008 image to flash in the factory partition of my modules.<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>Craig<br class="">_______________________________________________<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></div></blockquote></div><br class=""></div></div></body></html>