April 2025 - OvmsDev - Open Vehicles

Firmware release 3.3.005
by Michael Balzer 26 Jul '25

26 Jul '25

Everyone, I'd say release 3.3.005 is due. 3.3.004 was 03/2024, we've since collected quite some fixes and new features, including extensions for Smart EQ & the new MG4 support. There are lots of new Smart users now, as Mercedes have stopped support for the official Smart EQ App (see https://www.smart-emotion.de/article/415-mercedes-discontinues-smart-eq-app…) The current state is also very stable, I had no issue reports. Any objections / open fixes or additions that should be included in 3.3.005? Regards, Michael -- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926

4 10

How I got sphinx working on ubuntu 23.1 + WSL
by Michael Geddes 26 May '25

26 May '25

Firstly, thanks to Michael Balzer for fixing my errors in the rst files I checked in. (Also, apparently I can't spell Auxiliary - doh). I _had_ tried to get sphinx working recently and failed miserably, so I tried again this morning. The problem is that ubuntu: * Doesn't provide a package for m2r2 or sphinx-mdinclude (a fork of m2r2) * No longer allows you to pip install into the main python library path So first I got rid of the installed sphinx-doc sudo apt remove sphinx-doc Then I set up a sphinx virtual environment pipx install sphinx pipx inject sphinx sphinx_rtd_theme docutils mistune requests sphinx-mdinclude For some reason I was getting run-time python errors with m2r2 which is why I tried switching to mdinclude. In docs/source/conf.py I changed extensions = [ 'm2r2' ] to be 'sphinx_mdinclude' instead of 'm2r2' The pipx command creates a virtual execution environment for sphinx and puts a shim for sphinx in your local path that runs it in the virtual environment. //.ichael

9 31

Re: [Ovmsdev] System diagram?
by Dave Pawson 28 Apr '25

28 Apr '25

On Mon, 28 Apr 2025 at 03:35, Mark Webb-Johnson < mark.johnson(a)network-box.com> wrote: > Dave, > > We have: > > https://www.openvehicles.com/developers > > > as a starting point, > which provides a basic system hardware diagram, though it's rather heavy on acronyms! Are all parts used? A-D & D-A, encryption, touch sensor - I'm guessing this diagram is from the makers literature? > and the developer’s guide: > > > https://docs.google.com/document/d/1q5M9Lb5jzQhJzPMnkMKwy4Es5YK12ACQejX_NWE… > > > has detailed information on each hardware component. > > But I’m not aware of any system / software architecture diagrams. > I had hoped for a modular structure to see how the sw interfaced, perhaps to pick up on some lesser parts to get into it. I worked with low level stuff 40 years ago, asm and C. More recently Python and scripting on my Fedora box. What sort of development environment do you use please? Are there data sets available for different cars for testing? regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ.

2 5

System diagram?
by Dave Pawson 28 Apr '25

28 Apr '25

New to this project. Are there any system / software architecture diagrams around please, to let a newbie get his/her head round the software and hw interfaces? Thanks -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ.

2 2

Nissan Leaf ZE1 - Total loss of power
by Wayne Love 12 Apr '25

12 Apr '25

Just want to report another incident with a Leaf. My wife was driving to work this morning, according to her the Leaf started to display warning messages and then did a full HV power shutdown with a "Service EV System" "No Power" error. When I was able to get to her there were a number of DTC's being reported, I was not able to clear these with LeafSpy even with the OVMS module unplugged and had to disconnect the 12v battery. This behavior is consistent with the symptoms that I saw when the OVMS was crashing with a buffer overrun. I'll have a look at the logs when she gets home tonight to see if there are any indicators as to what is going on. Let me know if there are any specific investigative steps that I should be following. Thanks Wayne

4 6

Integration of Simcom 7670 and changes to Simcom Powering
by Info Zeitnitz 07 Apr '25

07 Apr '25

Dear all, I finished to integrate the Simcom 7670 modem into the OVMS code. See https://github.com/zbchristian/Open-Vehicle-Monitoring-System-3.git branch update_cellular. Modem Powering =============== I had problems to get the 7670 working with the current code. The modem was stuck in a power cycle loop. I checked the Simcom documentation for the 4 models 5360, 7000 series, 7600, 7670 and the powering procedure via the PWRKEY pin is the same, but with different on/off timing. Depending on the hardware, the PWRKEY can be inverted as well. This is the case for my Lilygo TCall board, but I think not for the OVMS HW versions. At least version 3.1 connects the corresponding MAX7317 pin directly to the modem. Assuming, that all hardware versions use the PWRKEY procedure for powering, I streamlined the code and moved the corresponding functions into separate files (simcom_powering.cpp and simcom_powering.h). This avoids the duplication of the code. All this leads to substantial changes in ovms_cellular and ovms_cellular_modem_driver as well. The code works now perfectly for the 7670, but testing is required for all other models. If my assumptions about the OVMS HW versions are not correct, or the modems do not work as documented, some modifications might be needed. GNSS Location ============ The 7670 no longer accepts the currently used AT commands to obtain the location as a GRMC sentence. So, I added code to the new 7670 class to request the location via the AT+CGNSSINFO command. Since this has to be send explicitly again and again, I implemented a corresponding call in the StatusPoller of the 7670. All the NMEA related code has been adapted to handle the corresponding CGNSSINFO response. In conclusion, before doing a pull request, it would make sense that the code is tested with the other hardware and modem models. So, tell me what you think and if the general strategy of the mods make sense to you. Best regards Christian

3 12

Duktape support for polling lists - p/r submitted.
by Michael Geddes 06 Apr '25

06 Apr '25

Hi All, This is the P/R here: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/1126 This is really where I was heading with the Poller implementation, in that it allows user-space additions to the polling infrastructure. The complexity of the specification means that it's really more appropriate to Duktape than to a cli script. It is definitely "a lot", and I suspect/suggest that it would be deferred until a release is made. I'm quite pleased with this implementation which has already been very much improved by people's observations and suggestions: * The Once-Off command call is the only one that calls back to duktape * The Decoding re-uses the DBC internals to achieve programmatic decoding. * It extends the various Duktape functions to control/interact with various aspects of the vehicle and poller (while giving necessary isolation). For anybody interested in the idea of being able to make a vehicle implementation in Duktape, this is worth having a look at! I do have some DBC Duktape commands ready to go as well. There is still some bits to do with the battery v/temp arrays that I've not quite covered. I have some ideas but they are not quite there yet. In the implementation I have already abstracted the destination 'Metric' and this is where this would fit in - ie the ability to populate the v/t array separately and then have some way of triggering the storing of those values. The internals are the BmsRestartCellTemperatures() and BmsSetCellTemperature( ) and other related functions which would need to be somehow called. //.ichael G.

1 0

Another incident
by Chris Box 05 Apr '25

05 Apr '25

Hi, It's happened again. Yesterday while driving the Leaf lost drive mode, forcing pulling over. I couldn't reengage gear until I had disconnected the 12v battery. Looking at the evidence today, the incident can't be explained by writing random bytes in CommandWakeup(), nor by having the wrong timing. It actually suggests that OVMS locked up ten minutes before the car was impacted. Here's what happened. 13:15 to 13:17 I drove off from home, but forgot an item so quickly returned back there. The sd log records this activity just fine, and the last entries before the suspected hang were these: 2025-02-07 13:19:59.174 GMT D (93751944) events: Signal(vehicle.asleep) 2025-02-07 13:22:29.184 GMT I (93901954) housekeeping: 2025-02-07 13:22:28 GMT (RAM: 8b=79028-81980 32b=12560 SPI=3262992-3285432) There should have been the next housekeeping message at 13:27:29 but none was recorded on the sd. Log flushes are configured to occur after 30 seconds. The last MQTT metric update my server received was around 13:27:50. This showed it was connected to home wifi. At 13:28 I unlocked the car, started it and drove off without noticing anything unusual. None of this activity appears in the log. During the drive there should have been a connection via Hologram to my server, but none was received. Ten minutes later at 13:38 I was driving when a yellow warning light came on and the car moved to neutral. Essentially the same symptoms as in January: turning off and on would not clear the fault; it couldn't detect brake status meaning it told me to press brake pedal when I already was. Also showed I-key system error. As I was stranded I used the only option I knew of to clear the fault, and I disconnected the 12v battery. On restoring power and dismissing the fault notice, it was happy to drive. The log shows this cold start SNTP was at 13:44. On returning home, unfortunately 'boot status' says nothing about a crash, presumably because any information was lost when I pulled power. So it seems there is some mechanism by which OVMS can lock up, without watchdog oversight. And that ten minutes later it can do something that becomes a critical issue for the car systems. Chris Relevant log entries below, all part of the same file. 1970 follows immediately after 13:22:29.184. 2025-02-07 13:17:50.184 GMT D (93622984) vehicle-poll: Pollers: Queue SetState() 2025-02-07 13:17:50.184 GMT D (93622984) vehicle-poll: Pollers: PollState(0) 2025-02-07 13:17:50.184 GMT D (93622984) events: Signal(vehicle.off) 2025-02-07 13:17:51.144 GMT D (93623944) events: Signal(vehicle.aux.12v.charging.dip) 2025-02-07 13:17:53.144 GMT D (93625944) events: Signal(vehicle.aux.12v.dip) 2025-02-07 13:17:54.824 GMT E (93627624) can: can2: intr=15711227 rxpkt=15730955 txpkt=100 errflags=0x22401c02 rxerr=0 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 txqueue=0 2025-02-07 13:17:56.754 GMT D (93629554) events: Signal(vehicle.locked) 2025-02-07 13:17:59.744 GMT E (93632544) can: can2: intr=15716706 rxpkt=15736447 txpkt=100 errflags=0x23401c01 rxerr=0 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 txqueue=0 2025-02-07 13:18:09.144 GMT D (93641944) events: Signal(vehicle.charge.12v.stop) 2025-02-07 13:18:10.144 GMT I (93642944) powermgmt: No longer charging 12V battery.. 2025-02-07 13:18:33.174 GMT D (93665944) events: Signal(vehicle.aux.12v.normal) 2025-02-07 13:18:33.764 GMT E (93666534) can: can2: intr=15754521 rxpkt=15774368 txpkt=100 errflags=0x22401c02 rxerr=0 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 txqueue=0 2025-02-07 13:18:45.174 GMT I (93677944) ovms-server-v3: Connection is <redacted> 2025-02-07 13:18:45.174 GMT I (93677944) ovms-server-v3: Status: Connecting... 2025-02-07 13:18:45.224 GMT D (93677994) events: Signal(server.v3.connecting) 2025-02-07 13:18:48.624 GMT I (93681394) ovms-server-v3: Connection successful 2025-02-07 13:18:48.644 GMT I (93681414) ovms-server-v3: Status: OVMS V3 MQTT login successful 2025-02-07 13:18:48.644 GMT D (93681414) events: Signal(server.v3.connected) 2025-02-07 13:18:49.174 GMT I (93681944) ovms-server-v3: Subscribe to MQTT topics 2025-02-07 13:18:49.174 GMT I (93681944) ovms-server-v3: Transmit all metrics 2025-02-07 13:18:49.464 GMT I (93682234) ovms-server-v3: Subscription acknowledged 2025-02-07 13:19:59.174 GMT D (93751944) events: Signal(vehicle.asleep) 2025-02-07 13:22:29.184 GMT I (93901954) housekeeping: 2025-02-07 13:22:28 GMT (RAM: 8b=79028-81980 32b=12560 SPI=3262992-3285432) 1970-01-01 00:00:08.424 GMT I (7994) command: OpenLogfile: now logging to file '/sd/logs/log' 1970-01-01 00:00:13.474 GMT D (13034) events: Signal(system.event) 1970-01-01 00:00:13.474 GMT D (13034) events: Signal(system.wifi.scan.done) 1970-01-01 00:00:19.424 GMT I (18984) cellular: State: Enter Identify state 1970-01-01 00:00:19.434 GMT I (18994) cellular: Identified cellular modem: SIM7600/Experimental support for SIMCOM SIM7600 1970-01-01 00:00:19.434 GMT I (18994) cellular: Set modem driver to 'SIM7600' 1970-01-01 00:00:19.434 GMT I (18994) cellular: State: Enter PoweredOn state 1970-01-01 00:00:19.424 GMT D (18994) events: Signal(system.modem.installed) 1970-01-01 00:00:19.434 GMT D (19004) events: Signal(system.modem.poweredon) 1970-01-01 00:00:23.474 GMT D (23034) events: Signal(system.event) 1970-01-01 00:00:23.474 GMT D (23034) events: Signal(system.wifi.scan.done) 1970-01-01 00:00:33.474 GMT D (33034) events: Signal(system.event) 1970-01-01 00:00:33.474 GMT D (33034) events: Signal(system.wifi.scan.done) 1970-01-01 00:00:39.434 GMT I (38994) cellular: State: Enter MuxStart state 1970-01-01 00:00:39.444 GMT I (39004) gsm-mux: Start MUX 1970-01-01 00:00:39.444 GMT D (39004) events: Signal(system.modem.muxstart) 1970-01-01 00:00:39.444 GMT I (39014) gsm-mux: Channel #0 is open 1970-01-01 00:00:39.464 GMT I (39024) gsm-mux: Channel #1 is open 1970-01-01 00:00:39.464 GMT I (39024) gsm-mux: Channel #2 is open 1970-01-01 00:00:39.474 GMT I (39034) gsm-mux: Channel #3 is open 1970-01-01 00:00:39.484 GMT I (39044) gsm-mux: Channel #4 is open 1970-01-01 00:00:40.414 GMT I (39984) cellular: State: Enter NetWait state 1970-01-01 00:00:40.414 GMT D (39984) events: Signal(system.modem.netwait) 1970-01-01 00:00:43.474 GMT D (43034) events: Signal(system.event) 1970-01-01 00:00:43.474 GMT D (43034) events: Signal(system.wifi.scan.done) 1970-01-01 00:00:46.054 GMT D (45624) events: Signal(vehicle.awake) 1970-01-01 00:00:50.444 GMT I (50014) cellular: Network Registration status: RegisteredRoaming 1970-01-01 00:00:51.414 GMT I (50984) cellular: State: Enter NetStart state 1970-01-01 00:00:51.434 GMT D (50994) events: Signal(vehicle.aux.12v.blip) 1970-01-01 00:00:51.434 GMT D (50994) events: Signal(system.modem.netstart) 1970-01-01 00:00:51.444 GMT D (51004) events: Signal(vehicle.charge.12v.start) 1970-01-01 00:00:51.434 GMT I (51004) cellular: Network Mode: LTE,Online 1970-01-01 00:00:52.414 GMT I (51984) powermgmt: Charging 12V battery.. 1970-01-01 00:00:52.464 GMT I (52034) cellular: PPP Connection is ready to start 1970-01-01 00:00:53.424 GMT I (52984) cellular: State: Enter NetMode state 1970-01-01 00:00:53.424 GMT I (52984) gsm-ppp: Initialising... 1970-01-01 00:00:53.434 GMT D (52994) events: Signal(system.modem.netmode) 1970-01-01 00:00:53.484 GMT D (53044) events: Signal(system.event) 1970-01-01 00:00:53.484 GMT D (53044) events: Signal(system.wifi.scan.done) 1970-01-01 00:00:53.594 GMT I (53154) gsm-ppp: StatusCallBack: None 1970-01-01 00:00:53.594 GMT I (53154) gsm-ppp: status_cb: Connected 1970-01-01 00:00:53.594 GMT I (53154) gsm-ppp: our_ipaddr = 100.83.212.151 1970-01-01 00:00:53.594 GMT I (53154) gsm-ppp: his_ipaddr = 10.64.64.64 1970-01-01 00:00:53.594 GMT I (53154) gsm-ppp: netmask = 255.255.255.255 1970-01-01 00:00:53.594 GMT I (53154) gsm-ppp: DNS#0 = 8.8.8.8 1970-01-01 00:00:53.584 GMT I (53154) gsm-ppp: DNS#1 = 8.8.4.4 1970-01-01 00:00:53.594 GMT I (53154) gsm-ppp: our6_ipaddr = :: 1970-01-01 00:00:53.594 GMT D (53154) events: Signal(network.interface.up) 1970-01-01 00:00:53.604 GMT D (53164) events: Signal(system.modem.gotip) 1970-01-01 00:00:53.604 GMT I (53164) netmanager: Interface priority is pp2 (100.83.212.151/255.255.255.255 gateway 10.64.64.64) 1970-01-01 00:00:53.604 GMT I (53164) netmanager: Set DNS#2 0.0.0.0 1970-01-01 00:00:53.594 GMT I (53164) netmanager: MODEM up (with WIFI client down): starting network with MODEM 1970-01-01 00:00:53.594 GMT D (53164) events: Signal(network.modem.up) 1970-01-01 00:00:53.594 GMT D (53164) events: Signal(network.up) 1970-01-01 00:00:53.604 GMT I (53174) time: Starting SNTP client 1970-01-01 00:00:53.604 GMT D (53174) events: Signal(network.interface.change) 1970-01-01 00:00:53.614 GMT D (53174) events: Signal(network.mgr.init) 1970-01-01 00:00:53.614 GMT I (53174) webserver: Launching Web Server 2025-02-07 13:44:08.584 GMT I (53184) webserver: Binding to port 80 (http) 2025-02-07 13:44:08.584 GMT I (53184) ssh: Launching SSH Server

4 12