<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hi Chris and Mark,<br>
thanks for your positive responses.<br>
<br>
The Simcom modem is already supported by my last PR, so no extra
configuration required. This is independent from the hardware
selection.<br>
<br>
The currently used single config <span
style="white-space: pre-wrap">CONFIG_OVMS_HW_BASE_LILYGO_1_0 takes care of 2 things:
- Change the pin assignment of the ESP32 to match the Lilygo module and the motherboard
- Reassign required signals of the GPIO extender chip max7317 to ESP32 IO pins. This is only related to the powering of the modem.
Thats all.
The latter can easily be handled by an alternative config, if the max7317 is disabled.
But there is the need to handle an alternative IO mapping in ovms_peripherals.h and this is very specific for the Lilygo/motherboard combination. I do not care, whether this is handled as a separate HW version, or is achieved by just an additional optional config to rearrange pins.
To keep it completely flexible, a free pin mapping could be available via menuconfig or an extra file, but that might be too error prone.
Concerning the availability of the hardware: at this stage, I will not be able to provide kits for this hardware option. Probably someone else is interested doing this?
Chris, if you are interested to test it, I could provide you with a partially assembled motherboard (most passive components and the DC/DC converter).
As far as I see, you are located in Germany as well, so shipment would be no problem.
Best regards
Christian
</span><br>
<br>
<br>
Am 27.04.2025 um 14:44 schrieb Mark Webb-Johnson via OvmsDev:<br>
</div>
<blockquote type="cite"
cite="mid:C1356E2F-A196-4CC4-9310-7EAF8EC24F95@webb-johnson.net">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Chris,</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">I guess if somebody wanted to, it could be
available as an unsoldered kit of Pcb and parts. The problem
with assembled kits is CE (and ROHS) certification for sale in
EU, but unsoldered kits are generally considered exempted from
that (although the radio / antenna part of it is a gray area).</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Regards, Mark</div>
<div dir="ltr"><br>
<blockquote type="cite">On Apr 27, 2025, at 3:03 PM, Chris van
der Meijden via OvmsDev <a class="moz-txt-link-rfc2396E" href="mailto:ovmsdev@lists.openvehicles.com"><ovmsdev@lists.openvehicles.com></a>
wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi Christian,</div>
<div><br>
</div>
<div>very impressive. You did a great job on the development
and on the documentation.</div>
<div><br>
</div>
<div>It is good to have an alternative hardware option.</div>
<div><br>
</div>
<div>As you mentioned, it is a disadvantage that OTA is not
possible, but that seems to be the price for a cheaper
hardware. Other obstacles I see, is that the hardware seems
only available directly from China and that we need to build
our own motherboard. That is for me the greatest hurdle,
alltough you did a great documentation with the Eagle
schematics.</div>
<div><br>
</div>
<div>I would like to test your hardware approach, if the
hardware would be available as a "ready to go" kit. Are you
planning on providing such a kit?</div>
<div><br>
</div>
<div>I could definitly see this as part of the OVMS
repository. Lets see what the other opinions on that are :-)</div>
<div><br>
</div>
<div>Regards</div>
<div><br>
</div>
<div>Chris</div>
<div><br>
</div>
<div>Am Samstag, dem 26.04.2025 um 17:40 +0200 schrieb Info
via OvmsDev:</div>
<blockquote type="cite"
style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">
<div>Hi,<br>
</div>
<div>I finished the implementation and documentation of the
OVMS module based <br>
</div>
<div>on the Lilygo T-Call A7670E board (ESP32 WROVER E and a
Simcom A7670E).<br>
</div>
<div>The module is in operation since more than a month in
my Smart EQ.<br>
</div>
<div><br>
</div>
<div>The hardware details can be found here: <br>
</div>
<div><a
href="https://github.com/zbchristian/OVMS-Lilygo-based-Module"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/zbchristian/OVMS-Lilygo-based-Module</a><br>
</div>
<div><br>
</div>
<div>There are some limitations wrt the standard module:<br>
</div>
<div>- only 4MB Flash -> no OTA update<br>
</div>
<div>- no GPIO extender -> only 2 CAN buses<br>
</div>
<div>- no SD-card support<br>
</div>
<div><br>
</div>
<div>The required modification in the firmware:<br>
</div>
<div>- remapping of the ESP32 pins in ovms_peripherals<br>
</div>
<div>- replace some of the GPIO extender pins by standard
ESP32 pins<br>
</div>
<div>- new hardware option in menuconfig (set
CONFIG_OVMS_HW_BASE_LILYGO_1_0=y)<br>
</div>
<div>- Simcom 7670 modem support (already available in the
OVMS repo)<br>
</div>
<div><br>
</div>
<div>All this is available in the branch lilygo-support of <br>
</div>
<div><a
href="https://github.com/zbchristian/Open-Vehicle-Monitoring-System-3-Lilygo-Support"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/zbchristian/Open-Vehicle-Monitoring-System-3-Lilygo-Support</a><br>
</div>
<div><br>
</div>
<div>My question to the main developers: Is there interest
to incorporate <br>
</div>
<div>this into the official OVMS repository?<br>
</div>
<div><br>
</div>
<div>Best regards<br>
</div>
<div> Christian<br>
</div>
<div><br>
</div>
<div>_______________________________________________<br>
</div>
<div>OvmsDev mailing list<br>
</div>
<div><a href="mailto:OvmsDev@lists.openvehicles.com"
moz-do-not-send="true" class="moz-txt-link-freetext">OvmsDev@lists.openvehicles.com</a><br>
</div>
<div><a
href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev"
moz-do-not-send="true" class="moz-txt-link-freetext">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a><br>
</div>
</blockquote>
<div><br>
</div>
<div><span></span></div>
<span>_______________________________________________</span><br>
<span>OvmsDev mailing list</span><br>
<span><a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.openvehicles.com">OvmsDev@lists.openvehicles.com</a></span><br>
<span><a class="moz-txt-link-freetext" href="http://lists.openvehicles.com/mailman/listinfo/ovmsdev">http://lists.openvehicles.com/mailman/listinfo/ovmsdev</a></span><br>
</div>
</blockquote>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
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>
</body>
</html>