- OvmsDev - Open Vehicles

Leaf AZE1 (2018+) Integrations
by Wayne Love 18 Mar '25

18 Mar '25

Greetings all, I'm new here and with OVMS but have a fair amount of experience messing around with OVMS. I've been working on extending the Leaf code to support the AZE1 model (production year 2018 onwards) and have it mostly working. If anyone is interested, I've forked the code and created a branch here wayne-love/Open-Vehicle-Monitoring-System-3 at Leaf-AZE1 My first question, are there any considerations / checks that I need to do before submitting a pull request? Thanks Wayne

2 1

Simple Auth for api
by Chris van der Meijden 18 Mar '25

18 Mar '25

I'm trying to connect our e-UP to EVCC using the http api. This fails, because I don't have a Drupal server installed. I only found AuhDrupal and AuthNone as modules for the the server. I don't want to install a Drupal instance for only one user, so I'm now trying to write a AuthSimple module for only one user with the username and password included in the code (I know, unsecure), so that the authentication for that user goes through and I get the variables I need for EVCC. Before I reinvent the wheel, does a code snippet perhaps exists, that does the trick? Regards Chris

3 4

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 24 Feb '25

24 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

New to OVMS development
by Info Zeitnitz 24 Jan '25

24 Jan '25

Hi everyone, my name is Christian and I started some time ago to adapt the OVMS firmware to my hardware. The hardware is a Lilygo T-Call A7670E V1.0 board (ESP32 Wrover-E, 4G modem Simcom 7670E, 4MB Flash, 8MB PSRAM) mounted on a custom PCB providing power, two CAN bus transceivers and 1 MCP2515. No extension chip is implemented. I use this to connect to my Smart EQ, which actually needs only a single CAN bus. I got the firmware going, including the 4G modem and its running reasonably stable, even though the Lilygo board has only 4MB of Flash (had to disable OTA and some other components). It works with both server versions. This firmware is based on the Version 3.3-004 tagged in the Github repo. I had to modify the code to get it working without the extension and with the Simcom 7670 module. In addition I added some changes from the master branch, especially for the Smart EQ. I would be willing to share some of the mods I did to the code and contribute to the further development. Especially the cellular code, which is still utilizing PPP, could benefit from an update to TCP/IP. I actually had quite a hard time to get the modem going with PPP, since the Simcom 7670 does not understand all the used AT-commands. So, I hope for a productive collaboration. Best regards Christian

4 3

Re: [Ovmsdev] OVMS Poller module/singleton
by Developer From Jokela 23 Jan '25

23 Jan '25

Hi. Tested with MCP_CAN lib settings, same thing as with SAE recommendation. // cnf1=0x00; cnf2=0xf0; cnf3=0x86; original code // SAE/CiA recommendation // PROP=5, PS1=8, PS2=2, SJW=2, Sample 1x @87.5% //cnf1=0x40; cnf2=0xbc; cnf3=0x81; // Arduino MCP_CAN lib // PROP=6, PS1=5, PS2=4, SJW=2, Sample 3x @75% cnf1=0x40; cnf2=0xe5; cnf3=0x83; E (445282) can: can2: intr=240803 rxpkt=242887 txpkt=6 errflags=0x22401c02 rxerr=0 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (446202) can: can2: intr=242315 rxpkt=244423 txpkt=6 errflags=0x23401c01 rxerr=0 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (448472) can: can2: intr=246089 rxpkt=248236 txpkt=6 errflags=0x22401c02 rxerr=0 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (448472) can: can2: intr=246089 rxpkt=248237 txpkt=6 errflags=0x23401c01 rxerr=0 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 OVMS# can can1 status CAN: can1 Mode: Active Speed: 500000 DBC: none Interrupts: 112548 Rx pkt: 112559 Rx ovrflw: 0 Tx pkt: 18 Tx delays: 0 Tx ovrflw: 0 Tx fails: 0 Err flags: 0x00000000 Rx err: 0 Tx err: 0 Rx invalid: 0 Wdg Resets: 0 Wdg Timer: 1 sec(s) Err Resets: 0 OVMS# can can2 status CAN: can2 Mode: Active Speed: 500000 DBC: none Interrupts: 291197 Rx pkt: 293642 Rx ovrflw: 0 Tx pkt: 6 Tx delays: 0 Tx ovrflw: 0 Tx fails: 0 Err flags: 0x01000001 Rx err: 0 Tx err: 0 Rx invalid: 0 Wdg Resets: 0 Wdg Timer: 9 sec(s) Err Resets: 0 Values from can2 are not present in leaf metrics.

3 5

Re: [Ovmsdev] OVMS Poller module/singleton
by Developer From Jokela 20 Jan '25

20 Jan '25

Hi. Tried setting Remember, the SAE/CiA recommendation is SJW=2, Sample 1x @87.5%. That >> would translate to: >> PROP=5, PS1=8, PS2=2, SJW=2, Sample 1x @87.5% = cnf1=0x40; cnf2=0xbc; cnf3=0x81; on leaf and it works fine. But, queue gets full and no data from can2 gets through. CAN1 no errors, CAN2: E (186415) can: can2: intr=294497 rxpkt=296913 txpkt=0 errflags=0x22401c02 rxerr=0 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (186425) can: can2: intr=294498 rxpkt=296914 txpkt=0 errflags=0x23401c01 rxerr=0 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 After this change poller now sends tx commands, compared to before when it did not. - DFJ > ovmsdev-request(a)lists.openvehicles.com kirjoitti 19.1.2025 kello 21.47: > > Am 19.01.25 um 12:48 schrieb Michael Balzer via OvmsDev: >> Maybe we should give that a try? I.e. >> >> ? MODULE_ESP32CAN->BTR1.B.SAM = (MyESP32can->m_speed < >> CAN_SPEED_125KBPS) ? 1 : 0; >> > > This change works flawlessly on my UpMiiGo (running can1 at 500 kbit/s). > > Regards, > Michael > > -- > Michael Balzer * Am Rahmen 5 * D-58313 Herdecke > Fon 02330 9104094 * Handy 0176 20698926 > >

2 1

Handling pilot signal interruption
by Chris B 14 Jan '25

14 Jan '25

Hi everyone First, thank you for working to build OVMS. It's an amazing achievement. I only started using it late last year. I've encountered just two issues, and fixed the first of those in PR#1081. I'd like to ask for your opinion on how to fix issue #1086 [1]. There's a shortcoming in Nissan hardware that means that timed climate control start can cause the charging pilot signal to disappear for a tenth of a second. This makes the car think it has just been plugged in, and it commences charging. OVMS then notices it is charging beyond the target SOC and commands the car to stop. This is fine, except it also ends the climate control before it has even had a chance to get going. My first idea for a workaround is to implement a configurable time period during which SOC limit isn't applied. Another idea is to implement detection for pilot interruption, and inhibit SOC limit for 30 minutes after that occurs. What do you think should be done here? Thanks, Chris Links: ------ [1] https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/1086

3 2

Crashing on restart
by Tamás Kovács 08 Jan '25

08 Jan '25

Now i change the sd card to a smaller, and formatted to fat32 (16Gb), but on reboot is crashing. Now connect a computer to the usb port, and create a log in verbose, attached to the email. -- Üdvözlettel: Kovács Tamás

3 5