<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
EU server now also has 3.2.018 released in "main".<br>
<br>
<a class="moz-txt-link-freetext" href="https://dexters-web.de/firmware-release-3.2.018-text_101.en.htm">https://dexters-web.de/firmware-release-3.2.018-text_101.en.htm</a><br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 07.12.21 um 01:36 schrieb Mark
Webb-Johnson:<br>
</div>
<blockquote type="cite"
cite="mid:755BC7B7-99FA-4BF4-A600-58CA7BFB9654@webb-johnson.net">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
I have released 3.2.018 to main OTA now, and announced it.
@Michael please follow with your EU server. Thanks to everyone
that contributed to this.
<div class=""><br class="">
</div>
<div class="">
<div class="">The certification for our upcoming 3.3 hardware
has been fully completed, and results published. You can see
the FCC stuff by:</div>
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;" class="">
<div class=""><a href="https://www.fcc.gov/oet/ea/fccid"
class="" moz-do-not-send="true">https://www.fcc.gov/oet/ea/fccid</a></div>
<div class=""><br class="">
</div>
<div class="">Grantee Code: 2ATDM</div>
<div class="">Product Code: OVMS-33-7 </div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">Hardware is in production and should be generally
available later this month. We have been affected by some
component chip shortages, but I am told those have been
resolved. We need to release the 3.3 firmware to the factory
later this week (or first thing next).</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark</div>
<div class=""><br class="">
</div>
<div class="">On 18 Nov 2021, at 3:06 PM, Mark Webb-Johnson <<a
href="mailto:mark@webb-johnson.net" class=""
moz-do-not-send="true">mark@webb-johnson.net</a>> wrote:<br
class="">
<div>
<blockquote type="cite" class=""><br
class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
<div class="">We need to get the v3.3 release ready
for release now, as the new v3.3 hardware is about
to enter production and the factory needs the
firmware.</div>
<div class=""><br class="">
</div>
<div class="">Accordingly, I suggest:</div>
<div class=""><br class="">
</div>
<div class="">
<ol class="MailOutline">
<li class="">I have already updated the for-v3.3
branch with all the recent changes from v3.2.<br
class="">
<br class="">
</li>
<li class="">We now (today/tomorrow) release the
current v3.2 branch as tag 3.2.018, OTA release.
This would be the (hopefully) last v3.2 release.<br
class="">
<br class="">
</li>
<li class="">After release of that, we branch off
master to a v3.2 branch, for historical purposes
(and if we need it for anything).<br class="">
<br class="">
</li>
<li class="">We then merge back for-v3.3 into the
master branch and start working through the
usual daily builds for that to get it ready for
production. I think there is still some work to
do on pouring the plugins, but the core code
(and in particular new modem support) should be
ok now.</li>
</ol>
</div>
<div class=""><br class="">
</div>
<div class="">I think we will need to investigate an
approach for dual builds for v3.3-or-later and
pre-v3.3 hardware, to take advantage of the new
ESP32 rev3 chips. I think those will require a
different sdkconfig. We can do that automatically in
the OTA system, by building the URL based on the
ESP32 platform revision. Should we do that with the
v3.3 release (even if the builds are for the moment
the same), or at a later date?</div>
<div class=""><br class="">
</div>
<div class="">Regards, Mark.</div>
<div class=""><br class="">
</div>
</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">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br
class="">
</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>
<pre class="moz-signature" cols="72">--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26</pre>
</body>
</html>