<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)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle20
{mso-style-type:personal-reply;
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:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:121583563;
mso-list-template-ids:964483734;}
@list l1
{mso-list-id:529297100;
mso-list-template-ids:964483734;}
@list l2
{mso-list-id:1159922307;
mso-list-template-ids:420238602;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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=EN-IN link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Hello Mark,<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'> Thanks for the comments. Please find the attached responses inline in green.<o:p></o:p></span></p><ol start=1 type=1><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l0 level1 lfo1'>Please don’t call this "OVMS v4", as that would cause confusion. Our ‘v’ naming is based on processor architecture:<br><br>v1 - original prototype hand-built (PIC18F2680)<br>v2 - first production version (PCI18F2685)<br>v3 - refined production version (ESP32 WROVER, 16MB flash 4MB SPIRAM)<br><br>Within that we have a .x naming scheme for subversions. The current version is v3.2 and the upcoming 4G module will be v3.3.<br><br>It sounds like you are trying to make a different layout of the upcoming version, so perhaps a fork of v3.3?<br><br>My concern here is to avoid confusion. <span style='background:lime;mso-highlight:lime'>Yes this is kind of fork of v3.3 with some additions on v3.2. </span><o:p></o:p></li><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l0 level1 lfo1'>SIM7600 sounds ok. That is the direction we are heading as well. <span style='background:lime;mso-highlight:lime'>If we adopt the version SIM7600G-H then this is global with all regions supported. However all modules on this series are pin to pin so doesn’t matter if we go for region specific.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l0 level1 lfo1'>For ESP32 are you using WROVER module with 16MB flash and 4MB/8MB SPIRAM? <span style='background:lime;mso-highlight:lime'>Noop. I am planning to use wroom only. Should I switch to wrover instead?<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l0 level1 lfo1'>For things like ACC detection, full power control, RGB LED, which GPIO / extended-IO pins are you using? <span style='background:lime;mso-highlight:lime'>I have used extender i.e MAX7317AEE+. Attached is the reference for esp32 connections.</span><span style='color:windowtext'> </span><span style='background:lime;mso-highlight:lime'><o:p></o:p></span></li></ol><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt;margin-left:36.0pt'><img width=1144 height=470 style='width:11.9166in;height:4.9in' id="Picture_x0020_1" src="cid:image002.jpg@01D78D2B.5F91A690"><span style='color:black;background:lime;mso-highlight:lime'><o:p></o:p></span></p><ol start=5 type=1><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l0 level1 lfo1'>It doesn’t look like you support the current expansion board option? <span style='background:lime;mso-highlight:lime'>Noop. I am not using any expansion thing here. Any particular requirement for that?<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l0 level1 lfo1'>It seems that you are using a different vehicle connector, so this will be hardwired for Indian MG ZS EV? <span style='background:lime;mso-highlight:lime'>Noop. Since we can use this for many other vehicles also by changing the connector. In current version the PCB has exposed pads where we need to solder wires to connector.</span> <o:p></o:p></li><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l0 level1 lfo1'>Note that we removed the LED in v3 (it was in v2) due to power consumption issues with that. <span style='background:lime;mso-highlight:lime'>There is power control option from hardware side. Only esp32 and accelero module are always on. For other things, power control is done from GPIO of esp32.</span><o:p></o:p></li><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>How are you intending to handle firmware? A fork of the current code, or kconfig flags to support your hardware differences? <span style='background:lime;mso-highlight:lime'>Unfortunately I am not that good on software side . Can modify it slightly by not much. Would require some support on this .</span><o:p></o:p></li></ol><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='color:black;background:lime;mso-highlight:lime'>One more thing, I was not able to find the CAN ic in stock so using TCAN334 from TI. Will this work with MCP2515-E_ML?</span><span style='color:black'><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'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Rohit Soni<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><span lang=EN-US>From:</span></b><span lang=EN-US> OvmsDev <ovmsdev-bounces@lists.openvehicles.com> <b>On Behalf Of </b>Mark Webb-Johnson<br><b>Sent:</b> 09 August 2021 01:51 PM<br><b>To:</b> OVMS Developers <ovmsdev@lists.openvehicles.com><br><b>Subject:</b> Re: [Ovmsdev] OVMS Hardware 4.0<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:black'>Looks interesting. A few comments:</span><o:p></o:p></p><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><div><ol start=1 type=1><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l1 level1 lfo3'>Please don’t call this "OVMS v4", as that would cause confusion. Our ‘v’ naming is based on processor architecture:<br><br>v1 - origjnal prototype hand-built (PIC18F2680)<br>v2 - first production version (PCI18F2685)<br>v3 - refined production version (ESP32 WROVER, 16MB flash 4MB SPIRAM)<br><br>Within that we have a .x naming scheme for subversions. The current version is v3.2 and the upcoming 4G module will be v3.3.<br><br>It sounds like you are trying to make a different layout of the upcoming version, so perhaps a fork of v3.3?<br><br>My concern here is to avoid confusion.<o:p></o:p></li><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l1 level1 lfo3'>SIM7600 sounds ok. That is the direction we are heading as well.<o:p></o:p></li><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l1 level1 lfo3'>For ESP32 are you using WROVER module with 16MB flash and 4MB/8MB SPIRAM?<o:p></o:p></li><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l1 level1 lfo3'>For things like ACC detection, full power control, RGB LED, which GPIO / extended-IO pins are you using?<o:p></o:p></li><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l1 level1 lfo3'>It doesn’t look like you support the current expansion board option?<o:p></o:p></li><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l1 level1 lfo3'>It seems that you are using a different vehicle connector, so this will be hardwired for Indian MG ZS EV?<o:p></o:p></li><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l1 level1 lfo3'>Note that we removed the LED in v3 (it was in v2) due to power consumption issues with that.<o:p></o:p></li><li class=MsoNormal style='color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo3'>How are you intending to handle firmware? A fork of the current code, or kconfig flags to support your hardware differences?<o:p></o:p></li></ol><div><p class=MsoNormal><span style='color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>Regards, Mark,<o:p></o:p></span></p></div></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 9 Aug 2021, at 3:18 PM, <<a href="mailto:rohit@ekraft.asia">rohit@ekraft.asia</a>> <<a href="mailto:rohit@ekraft.asia">rohit@ekraft.asia</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Hello OVMS dev’s,<o:p></o:p></p></div><div><p class=MsoNormal> I am basically hardware designer planning to use the OVMS on my MG ZS EV ( Indian version ). For this I designed the hardware containing 4g module as well as all the components on single PCB.<o:p></o:p></p></div><div><p class=MsoNormal>Have a look on below:<o:p></o:p></p></div><div><p class=MsoNormal><image002.jpg><image004.jpg><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal> Top Side Bottom side<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>The hardware features are as follows:<o:p></o:p></p></div><ol style='margin-top:0cm' start=1 type=1><li class=MsoListParagraph style='margin-top:0cm;margin-bottom:0cm;mso-list:l2 level1 lfo2'>4G module with active GPS antenna support ( sim7600 )<o:p></o:p></li><li class=MsoListParagraph style='margin-top:0cm;margin-bottom:0cm;mso-list:l2 level1 lfo2'>ESP32 as main processor ( similar to ovms rev 3)<o:p></o:p></li><li class=MsoListParagraph style='margin-top:0cm;margin-bottom:0cm;mso-list:l2 level1 lfo2'>Sim and sd card in stacked single slot to save space<o:p></o:p></li><li class=MsoListParagraph style='margin-top:0cm;margin-bottom:0cm;mso-list:l2 level1 lfo2'>3 can bus ports<o:p></o:p></li><li class=MsoListParagraph style='margin-top:0cm;margin-bottom:0cm;mso-list:l2 level1 lfo2'>Battery backup in case need to use this device as security. On board charging<o:p></o:p></li><li class=MsoListParagraph style='margin-top:0cm;margin-bottom:0cm;mso-list:l2 level1 lfo2'>Accelero/ gyro combined low power device<o:p></o:p></li><li class=MsoListParagraph style='margin-top:0cm;margin-bottom:0cm;mso-list:l2 level1 lfo2'>ACC detection in case of supported from vehicle from OBD port<o:p></o:p></li><li class=MsoListParagraph style='margin-top:0cm;margin-bottom:0cm;mso-list:l2 level1 lfo2'>Fully power control of each and every component and low power sleep mode<o:p></o:p></li><li class=MsoListParagraph style='margin-top:0cm;margin-bottom:0cm;mso-list:l2 level1 lfo2'>Input power supply up-to 60 V<o:p></o:p></li><li class=MsoListParagraph style='margin-top:0cm;margin-bottom:0cm;mso-list:l2 level1 lfo2'>RGB led for status indication<o:p></o:p></li></ol><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>The device case would be as below in which OBD connector would be there.<o:p></o:p></p></div><div><p class=MsoNormal><image007.jpg><image008.jpg><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Do let me know if we need to add something so hardware is future ready.<span class=apple-converted-space> </span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Regards,<o:p></o:p></p></div><div><p class=MsoNormal>Rohit Soni<o:p></o:p></p></div><div><p class=MsoNormal>+91-9660770212<o:p></o:p></p></div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>_______________________________________________<br>OvmsDev mailing list<br></span><a href="mailto:OvmsDev@lists.openvehicles.com"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>OvmsDev@lists.openvehicles.com</span></a><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><br></span><a href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>http://lists.openvehicles.com/mailman/listinfo/ovmsdev</span></a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></body></html>