[Ovmsdev] Support for Lilygo T-Call based module

Sat May 3 21:09:35 HKT 2025

Hi Chris and Casten,
ok, very good.

Carsten, if you experience any problems, please get in touch with me.

Best regards.
     Christian

Am 29. April 2025 07:10:22 schrieb Chris van der Meijden via OvmsDev 
<ovmsdev at lists.openvehicles.com>:
> Hi Christian
>
> Thank you for your generous offer.
>
> I'm deep into other projects at the moment, so I woukd not feel comfortable 
> when your hardware would be laying around at my place and I would not be 
> spending the time with it it deserves.
>
> And as Carsten now jumped in, there will be some good team testing.
>
> So thank you again. I will be following the development with great interest 
> and surely will step into this hardware somewhere in the future.
>
> Success
>
> Chris
>
> Am Montag, dem 28.04.2025 um 15:16 +0000 schrieb Carsten Schmiemann via 
> OvmsDev:
>>
>> Hi Christian,
>>
>>
>>
>>
>> really nice work, thanks.
>>
>>
>>
>>
>>
>> I immediately ordered 5 PCBs and will test it on my electric scooter from 
>> NIU which has a CAN bus and I did some reverse engineering already. Only 
>> the high price of an OVMS 3.3 module was holding me back :-)
>>
>>
>>
>>
>> Greetings from Germany
>>
>> Carsten
>>
>> Von: OvmsDev <ovmsdev-bounces at lists.openvehicles.com> im Auftrag von Info 
>> Zeitnitz via OvmsDev <ovmsdev at lists.openvehicles.com>
>> Gesendet: Montag, 28. April 2025 14:24:32
>> An: ovmsdev at lists.openvehicles.com
>> Cc: Info Zeitnitz
>> Betreff: Re: [Ovmsdev] Support for Lilygo T-Call based module
>> Hi Chris and Mark,
>> thanks for your positive responses.
>>
>> The Simcom modem is already supported by my last PR, so no extra 
>> configuration required. This is independent from the hardware selection.
>>
>> The currently used single config 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
>>
>>
>>
>> Am 27.04.2025 um 14:44 schrieb Mark Webb-Johnson via OvmsDev:
>>> Chris,
>>>
>>> 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).
>>>
>>> Regards, Mark
>>>
>>>> On Apr 27, 2025, at 3:03 PM, Chris van der Meijden via 
>>>> OvmsDev<ovmsdev at lists.openvehicles.com> wrote:
>>>> Hi Christian,
>>>>
>>>> very impressive. You did a great job on the development and on the 
>>>> documentation.
>>>>
>>>> It is good to have an alternative hardware option.
>>>>
>>>> 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.
>>>>
>>>> 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?
>>>>
>>>> I could definitly see this as part of the OVMS repository. Lets see what 
>>>> the other opinions on that are :-)
>>>>
>>>> Regards
>>>>
>>>> Chris
>>>>
>>>> Am Samstag, dem 26.04.2025 um 17:40 +0200 schrieb Info via OvmsDev:
>>>>> Hi,
>>>>>
>>>>> I finished the implementation and documentation of the OVMS module based
>>>>>
>>>>> on the Lilygo T-Call A7670E board (ESP32 WROVER E and a Simcom A7670E).
>>>>>
>>>>> The module is in operation since more than a month in my Smart EQ.
>>>>>
>>>>>
>>>>> The hardware details can be found here:
>>>>>
>>>>> https://github.com/zbchristian/OVMS-Lilygo-based-Module
>>>>>
>>>>>
>>>>> There are some limitations wrt the standard module:
>>>>>
>>>>> - only 4MB Flash -> no OTA update
>>>>>
>>>>> - no GPIO extender -> only 2 CAN buses
>>>>>
>>>>> - no SD-card support
>>>>>
>>>>>
>>>>> The required modification in the firmware:
>>>>>
>>>>> - remapping of the ESP32 pins in ovms_peripherals
>>>>>
>>>>> - replace some of the GPIO extender pins by standard ESP32 pins
>>>>>
>>>>> - new hardware option in menuconfig (set CONFIG_OVMS_HW_BASE_LILYGO_1_0=y)
>>>>>
>>>>> - Simcom 7670 modem support (already available in the OVMS repo)
>>>>>
>>>>>
>>>>> All this is available in the branch lilygo-support of
>>>>>
>>>>> https://github.com/zbchristian/Open-Vehicle-Monitoring-System-3-Lilygo-Support
>>>>>
>>>>>
>>>>> My question to the main developers: Is there interest to incorporate
>>>>>
>>>>> this into the official OVMS repository?
>>>>>
>>>>>
>>>>> Best regards
>>>>>
>>>>>    Christian
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>>
>>>>> OvmsDev mailing list
>>>>>
>>>>> OvmsDev at lists.openvehicles.com
>>>>>
>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>>>
>>>>
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.openvehicles.com
>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>>
>>>
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.openvehicles.com
>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20250503/df4ffb17/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5285 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20250503/df4ffb17/attachment.p7s>