<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""></div></blockquote><div class=""><br class=""></div><div class="">Existing developer OVMS v3 boards (with WROOM-32 module) will continue to be called v3.0. New production OVMS v3 boards (with WROVER module) will be called v3.1. We have conditional compilation in the firmware, to switch the pin assignments and whatever else is required.</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><span style="font-family: Menlo-Regular; font-size: 14px;" class=""> Branch: refs/heads/for-v3.0</span><br style="font-family: Menlo-Regular; font-size: 14px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px;" class=""> Home: </span><a href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3" style="font-family: Menlo-Regular; font-size: 14px;" class="">https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3</a><br style="font-family: Menlo-Regular; font-size: 14px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px;" class=""> Commit: 9504df70be78b6626970ec0ea53d2c2470e90afa</span><br style="font-family: Menlo-Regular; font-size: 14px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px;" class=""> </span><a href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/9504df70be78b6626970ec0ea53d2c2470e90afa" style="font-family: Menlo-Regular; font-size: 14px;" class="">https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/9504df70be78b6626970ec0ea53d2c2470e90afa</a><br style="font-family: Menlo-Regular; font-size: 14px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px;" class=""> Author: Mark Webb-Johnson <</span><a href="mailto:mark@webb-johnson.net" style="font-family: Menlo-Regular; font-size: 14px;" class="">mark@webb-johnson.net</a><span style="font-family: Menlo-Regular; font-size: 14px;" class="">></span><br style="font-family: Menlo-Regular; font-size: 14px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px;" class=""> Date: 2018-01-10 (Wed, 10 Jan 2018)</span><br style="font-family: Menlo-Regular; font-size: 14px;" class=""><br style="font-family: Menlo-Regular; font-size: 14px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px;" class=""> Changed paths:</span><br style="font-family: Menlo-Regular; font-size: 14px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px;" class=""> M vehicle/OVMS.V3/main/Kconfig</span><br style="font-family: Menlo-Regular; font-size: 14px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px;" class=""> M vehicle/OVMS.V3/main/ovms_peripherals.h</span><br style="font-family: Menlo-Regular; font-size: 14px;" class=""><br style="font-family: Menlo-Regular; font-size: 14px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px;" class=""> Log Message:</span><br style="font-family: Menlo-Regular; font-size: 14px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px;" class=""> -----------</span><br style="font-family: Menlo-Regular; font-size: 14px;" class=""><span style="font-family: Menlo-Regular; font-size: 14px;" class=""> Support for OVMS hardware v3.1</span></div></blockquote><div class=""><br class=""></div><div class=""><div class="">Converting developer v3.0 boards to v3.1 is not really feasible (a skilled solderer could probably use a 16MB Analog Lamb WROOM-32+PSRAM module; that would be a relatively simple de-solder + re-solder of the module, a not-so-simple re-arrange of the traces for IO16->IO4 and IO17->IO13, and disabling of external 16MB flash). Anyway, those existing developer modules should be fine to continue to use (just without the extra PSRAM).</div></div><div class=""><br class=""></div><div class="">We are today finalising the circuit schematic and board layout for the above, and building a couple of test boards (with WROVER modules). I should have one in about a week’s time (assuming all the components are available). In that time, we’ll finish the ESP IDF v3.0 support, and test late next week / over next weekend (20th/21st Jan). Assuming no problems, we should be able to give factory the go-ahead to produce early the week after.</div><div class=""><br class=""></div><div class="">Given that timing, I doubt if we are going to be able to get these boards made before the Chinese New Year holidays. Even if we can get them made, FastTech distribution may not be able to get them out during the holidays. Manufacturing in China starts to close down around the end of January / early February this year. New Year itself is mid-February. Anyway, we’ll get this all finalised, payment and instruction to start manufacturing in place, then do the best we can and get these out available during February. A big warning is going to go with them that this is for early adopters only, and firmware is changing on a daily basis. Updating firmware via wifi / sd card should be fine.</div><div class=""><br class=""></div><div class="">I’m seeing a light at the end of a long dark tunnel.</div><div class=""><br class=""></div><div class="">Regards, Mark.</div><div class=""><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>