February 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

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

UI redesign in Android App - Needs beta testing
by Developer From Jokela 08 Mar '25

08 Mar '25

Hi Android users. I’ve recently redesigned UI for Android and it would need some testing. Here is the latest build available for UI redesign: https://github.com/openvehicles/Open-Vehicle-Android/tree/test-dfj-ui/latest Please report any issues, improvement suggestions, etc. Thank you! Br, DFJ

5 25

Levels of poller states
by Chris Box 25 Feb '25

25 Feb '25

Hi everyone While trying to resolve the Leaf's poll state management, I find myself needing to understand the different levels of poller state that exist in the main (non-vehicle-specific) code. What is the semantic difference between these? OvmsVehicle::m_poll_state OvmsPollers::m_poll_state OvmsPoller::m_poll_state To me it appears the first two duplicate each other, and I'm not sure why. The third one is a little different as it's per poller (i.e. per bus). If I follow how changes are propagated to these for my car, I see: OvmsVehicle::PollSetState(state) This immediately sets OvmsVehicle::m_poll_state = state, and calls: OvmsPollers::PollSetState(state) This immediately sets OvmsPollers::m_poll_state = state, and queues a request to set the lowest level states. When the request is processed, it loops through the buses. For each it calls: OvmsPoller::Do_PollSetState(state) This sets this instance's OvmsPoller::m_poll_state = state, and updates some associated variables. What is the logic behind having so many poll states? Chris

2 2

Re: [Ovmsdev] OVMS Poller module/singleton
by Michael Balzer 08 Feb '25

08 Feb '25

Michael, (taking this back to the list, as other developers may have helpful ideas or suggestions) from a first check, your new patch (PR #1008) won't help for vehicles that don't use the poller, like the generic DBC vehicle or the Fiat 500 (plus possibly non-public third party vehicles). As the poller is normally compiled in, these would need a run time switch to re-enable the vehicle task, or more suitably default into that configuration and switch to the poller task only when the poller gets initialized. How about moving the task back into the vehicle class, but keeping your task message extensions while doing so, and adding a way for the poller to hook into the task? The dedicated vehicle task is an essential part of the vehicle framework, but I do remember some occasions where a general way to pass custom messages to the vehicle task would have been helpful to use the task for more than CAN processing. If the poller shall become avaible as a separate service that can be used without any vehicle instance (currently not a defined use case), the construct of a CAN processor task that can be extended for custom messages (or a message processor task that can subscribe to CAN frames) could be factored out into a dedicated class or template. The poller could then create his own instance of that class, if it cannot hook into an existing one. Btw, in case you're not aware of this, FreeRTOS also provides queue sets (https://www.freertos.org/RTOS-queue-sets.html) We haven't used them in the OVMS yet, but they could be useful, especially if message unions become large or tasks shall be able to dynamically subscribe to different message sources. Regards, Michael Am 30.04.24 um 01:20 schrieb Michael Geddes: > It might be worth reverting, but, I've got a patch suggestion that > I'll push up which will let me know if I understand everything and > which might provide a solution. > > If this isn't going to work then revert. (P/R coming) > > While the poller was still a part of the vehicle class it was probably > still all ok. The poller had taken over what I assume you are > talking about as the vehicle task. A call-back fromthe poller was > calling IncomingPollRxFrame which was then coming from the (now) > poller task (is that correct?) > > While we have OVMS_COMP_POLLER config defined, we could just use the > poller task to provide the IncomingPollRxFrame call-back from the > poller (was vehicle?) task. > > The problem is when OVMS_COMP_POLLER is undefined, we need an > alternate (maybe we could use the 'Event' loop then) which is when I > hacked that bad solution. > > > //.ichael > > > I was thinking though that because everything is being queued we could > divert some calls into the car > > On Mon, 29 Apr 2024, 18:58 Michael Balzer, <dexter(a)expeedo.de> wrote: > > Michael, > > I've found a severe design flaw with your poller change. Sorry, I > should have seen that before, and shouldn't have merged this. > > You have moved the standard CAN frame processing from the vehicle > task into the CAN task by changing the vehicle from a CAN listener > to a CAN callback processor. That will break all kind of things, > vehicles like the Twizy, Smart and many others rely on frame > processing being done in the dedicated vehicle task. > > This especially induces issues regarding CAN processing capacity, > as the vehicles rely on having a separate context and not needing > to decouple complex processing of incoming frames. So this will > degrade the CAN processing performance seriously in many cases, > where additional steps involving file or network I/O need to be done. > > So this needs to be changed back. > > I assumed you introduced a new dedicated poller task but kept the > vehicle task intact. From your naming > (OvmsVehicle::IncomingPollRxFrame), it seems you misinterpreted > the vehicle task's purpose as only being used for polling. > > I assume this isn't a small change…? If so we should revert the > poller merge, to avoid having a defunctional edge build state > until the fix. > > > Secondly: logging is generally expensive regardless of the log > level control and log channels enabled. Any log message needs to > be queued to the log system, so involves a lock and a potential > wait state (for the queue) & resulting context switch (= minimum > delay of 10 ms). Therefore, logging must be avoided as far as > possible in any time critical context, and is forbidden under some > circumstances, e.g. in a timer callback (see FreeRTOS docs on > this). The log system load multiplies with connected web clients > or enabled file logging and enabled debug / verbose level logging > -- that quickly becomes too much, usually triggering the task > watchdog. > > Your logging of nearly all bus events passing to/from the poller > (especially the log entry in Queue_PollerFrame) becomes an issue > on any vehicle that has high frequency running process data frames > on the bus, like the Twizy or Smart. As a counter measure, I've > just added a runtime control for all the poller's verbose logging > (by default now off), and changed some debug level logs to > verbose. Not sure if I've catched all that may need to be silenced > by default. Please check all your log calls and place them under > the new "trace" control flag wherever appropriate. > > This won't help avoiding issues with process data frame buses though. > > > Shall I revert the poller merge for now? > > Regards, > Michael > > > > Am 29.04.24 um 06:18 schrieb Michael Geddes: >> Btw I included the log changes in the p/r which is a few small >> commits for the poller. >> >> //. >> >> On Mon, 29 Apr 2024, 07:20 Michael Geddes, >> <frog(a)bunyip.wheelycreek.net> wrote: >> >> Hey Michael, >> I've got to work now (it's Monday), but I suspect those >> 'giving up' are from unsolicited messages on the bus. >> I can re-order things so that the message will likely be >> 'dropped (no poll entry)' rather than the time-out message. >> And make it a verbose log. >> >> //.ichael >> >> On Mon, 29 Apr 2024 at 00:25, Michael Balzer >> <dexter(a)expeedo.de> wrote: >> >> Michael, >> >> forwarding the Twizy logs to you directly, as they >> contain the user location. >> >> He has just verified it's the new version, he says the >> module stops responding as soon as he turns on the Twizy. >> >> His description of his actions is a bit ambiguous, and it >> seems he didn't enable logging to the file persistently. >> >> According to the server, these were the version boot times: >> >> 2024-04-28 15:30:56 0 3.3.004-32-g125e0841/ota_0/edge >> (build idf v3.3.4-849-g6e214dc335 Apr 26 2024 19:16:50) >> 2024-04-28 16:21:08 0 3.3.004-32-g125e0841/ota_0/edge >> (build idf v3.3.4-849-g6e214dc335 Apr 26 2024 19:16:50) >> 2024-04-28 16:38:33 0 3.3.004-63-gf3595561/ota_1/edge >> (build idf v3.3.4-849-g6e214dc335 Apr 27 2024 07:44:50) >> 2024-04-28 16:40:57 0 3.3.004-63-gf3595561/ota_1/edge >> (build idf v3.3.4-849-g6e214dc335 Apr 27 2024 07:44:50) >> 2024-04-28 16:43:14 0 3.3.004-63-gf3595561/ota_1/edge >> (build idf v3.3.4-849-g6e214dc335 Apr 27 2024 07:44:50) >> 2024-04-28 16:46:39 0 3.3.004-63-gf3595561/ota_1/edge >> (build idf v3.3.4-849-g6e214dc335 Apr 27 2024 07:44:50) >> 2024-04-28 16:54:44 0 3.3.004-32-g125e0841/ota_0/edge >> (build idf v3.3.4-849-g6e214dc335 Apr 26 2024 19:16:50) >> >> Attached is also his crash debug log -- a2ll doesn't tell >> much about what happened, but maybe you get an idea from >> this. >> >> After the boot at 16:46, there are immediately lots of >> these messages: >> >> 2024-04-28 16:46:33.792 CEST D (39042) vehicle-poll: >> Poller: Queue PollerFrame() >> 2024-04-28 16:46:33.792 CEST D (39042) vehicle-poll: >> [1]Poller: Incoming - giving up >> >> Regards, >> Michael >> >> >> Am 28.04.24 um 16:44 schrieb Michael Geddes: >>> Ah. OK. >>> >>> I could try to fix the vin thing using the new way of >>> doing it and get rid of a semaphore? >>> It would at least identify the problem possibly? >>> >>> Michael >>> >>> >>> On Sun, 28 Apr 2024, 22:32 Michael Balzer via OvmsDev, >>> <ovmsdev(a)lists.openvehicles.com> wrote: >>> >>> Not sure if that's the problem, but I've found a >>> different behaviour with the new PollSetState() >>> implementation. >>> >>> The old version only did anything if the new state >>> actually was different from the previous one. The >>> Twizy relies on this behaviour, calling >>> PollSetState() from the per second ticker (see >>> OvmsVehicleRenaultTwizy::ObdTicker1). >>> >>> The new implementation apparently always sends the >>> PollState command to the task, and that in turn >>> always at least locks the poller mutex. Not sure >>> if/how that could cause the observed issues, but it >>> definitely adds quite some (unnecessary?) >>> lock/unlock operations. >>> >>> >>> >>> Am 28.04.24 um 16:05 schrieb Michael Balzer via OvmsDev: >>>> The Twizy uses the poller to query the VIN (once) >>>> and DTCs (every 10 seconds while driving), see >>>> rt_obd2.cpp. >>>> >>>> It also has its own version of the OBD single >>>> request (OvmsVehicleRenaultTwizy::ObdRequest), >>>> which was the precursor for the generalized >>>> version. This is used by custom/user Twizy plugins >>>> and scripts to access ECU internals. >>>> >>>> The Twizy doesn't use IncomingPollRxFrame, but the >>>> Twizy's IncomingPollReply handler will log any poll >>>> responses it doesn't know about, so that could lead >>>> to a lot of log output if something goes wrong there. >>>> >>>> >>>> Am 28.04.24 um 15:49 schrieb Michael Geddes via >>>> OvmsDev: >>>>> AFAICT the twizzy doesn't use the poller list at >>>>> all. So is it missing a call-back or something?? >>>>> >>>>> I can see a potential problem with >>>>> IncomingPollRxFrame being called twice as much as >>>>> it should be but only when there is a poll list. >>>>> Maybe commenting out this would do it. (I can >>>>> find another away to get this called on the thread >>>>> I want). This might be the problem with the smarted >>>>> >>>>> void >>>>> OvmsVehicle::OvmsVehicleSignal::IncomingPollRxFrame(canbus* >>>>> bus, CAN_frame_t *frame, bool success) >>>>> { >>>>> //if (Ready()) >>>>> // m_parent->IncomingPollRxFrame(frame, success); >>>>> } >>>>> >>>>> //. >>>>> >>>>> >>>>> On Sun, 28 Apr 2024 at 21:10, Michael Balzer via >>>>> OvmsDev <ovmsdev(a)lists.openvehicles.com> wrote: >>>>> >>>>> There may also be an issue with the Renault >>>>> Twizy, I've received a report of a user who is >>>>> using the edge builds, that the latest build >>>>> wouldn't work. >>>>> >>>>> He reports all kinds of errors and warnings >>>>> signaled by the car during driving, and >>>>> switching back to the previous build fixed the >>>>> issues. >>>>> >>>>> I've asked him to provide a debug log excerpt >>>>> if possible. >>>>> >>>>> Regards, >>>>> Michael >>>>> >>>>> >>>>> Am 28.04.24 um 14:29 schrieb Michael Geddes >>>>> via OvmsDev: >>>>>> OK. That's bad. >>>>>> >>>>>> Does the reading work in general? >>>>>> >>>>>> Is it just the writing commands? >>>>>> >>>>>> Raise a ticket on github and tag me in and we >>>>>> can address it that way. >>>>>> >>>>>> Michael >>>>>> >>>>>> On Sun, 28 Apr 2024, 19:49 Thomas Heuer via >>>>>> OvmsDev, <ovmsdev(a)lists.openvehicles.com> wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>> The new poller code doesn't seem to work >>>>>> properly with the smarted. >>>>>> >>>>>> D (218831) vehicle-poll: >>>>>> [1]PollerNextTick(PRI): cycle complete >>>>>> for ticker=215 >>>>>> >>>>>> V (218831) vehicle-poll: Standard Poll >>>>>> Series: List reset >>>>>> >>>>>> D (218831) vehicle-poll: >>>>>> PollSeriesList::NextPollEntry[!v.standard]: >>>>>> ReachedEnd >>>>>> >>>>>> V (218831) vehicle-poll: [1]PollerSend: >>>>>> Poller Reached End >>>>>> >>>>>> D (219691) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> D (219691) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> V (219691) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219691) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> V (219691) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> V (219691) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219691) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> *OVMS#*unlock 22 >>>>>> Vehicle unlocked >>>>>> >>>>>> V (219691) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219691) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> V (219691) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219701) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> V (219701) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219701) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> V (219701) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219701) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> V (219701) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219701) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> V (219701) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219701) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> V (219701) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219701) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> V (219701) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219701) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> V (219701) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219701) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> V (219701) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219701) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> V (219701) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219701) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> V (219701) vehicle-poll: Pollers: >>>>>> FrameRx(bus=2) >>>>>> >>>>>> D (219701) vehicle-poll: Poller: Queue >>>>>> PollerFrame() >>>>>> >>>>>> *Von:*OvmsDev >>>>>> <ovmsdev-bounces(a)lists.openvehicles.com> >>>>>> *Im Auftrag von *Michael Geddes via OvmsDev >>>>>> *Gesendet:* Sonntag, 28. April 2024 12:27 >>>>>> *An:* OVMS Developers >>>>>> <ovmsdev(a)lists.openvehicles.com> >>>>>> *Cc:* Michael Geddes >>>>>> <frog(a)bunyip.wheelycreek.net> >>>>>> *Betreff:* [Ovmsdev] OVMS Poller >>>>>> module/singleton >>>>>> >>>>>> Hey all, >>>>>> >>>>>> The poller singleton code that I've been >>>>>> working on for over a year now is merged >>>>>> in. (Thanks Michael for expediting the >>>>>> final step). >>>>>> >>>>>> This includes separate multi-frame states >>>>>> per bus and multiple poll lists as well >>>>>> as non-blocking one off queries. As well >>>>>> as more 'states'. >>>>>> >>>>>> I have included some programming >>>>>> documentation in the change but am happy >>>>>> to supply more if needed. >>>>>> >>>>>> The ioniq 5 code has some examples of how >>>>>> it can be used. Some examples are: >>>>>> >>>>>> * grabbing the vin as a one shot without >>>>>> blocking >>>>>> >>>>>> * having a short list of queries that are >>>>>> polled quickly for obd2ecu (this also >>>>>> demonstrates using a shorter frame break >>>>>> value and then a break after successful a >>>>>> response) >>>>>> >>>>>> Have a play please! >>>>>> >>>>>> Also interested in hearing what user >>>>>> tools might be worth looking at next for >>>>>> the poller object. >>>>>> >>>>>> //.ichael G. >>>>>> >>>>>> _______________________________________________ >>>>>> OvmsDev mailing list >>>>>> OvmsDev(a)lists.openvehicles.com >>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> OvmsDev mailing list >>>>>> OvmsDev(a)lists.openvehicles.com >>>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev >>>>> >>>>> -- >>>>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal >>>>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 >>>>> >>>>> _______________________________________________ >>>>> OvmsDev mailing list >>>>> OvmsDev(a)lists.openvehicles.com >>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev >>>>> >>>>> >>>>> _______________________________________________ >>>>> OvmsDev mailing list >>>>> OvmsDev(a)lists.openvehicles.com >>>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev >>>> >>>> -- >>>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal >>>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 >>>> >>>> _______________________________________________ >>>> OvmsDev mailing list >>>> OvmsDev(a)lists.openvehicles.com >>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev >>> >>> -- >>> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal >>> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 >>> >>> _______________________________________________ >>> OvmsDev mailing list >>> OvmsDev(a)lists.openvehicles.com >>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev >>> >> >> -- >> Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal >> Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 >> > > -- > Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal > Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 > -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

7 117