April 2022 - OvmsDev - Open Vehicles

Netmanager priority issue solved
by Michael Balzer 05 Jul '23

05 Jul '23

TL;DR: you need to pull my latest esp-idf changes. I've finally found & solved the strange priority changes for our netmanager task (i.e. being raised suddenly from origin 5 to 18/22): the bug was in the esp-idf posix threads mutex implementation. I had suspected the mutex priority inheritance for a while, so added a way to retrieve the internal mutex hold count for our task list. Using this I noticed the hold count would always & only raise by 2 whenever any kind of mongoose connection was closed. That lead me to checking the thread concurrency protection for mongoose mbufs, because every mongoose connection has two mbufs associated (rx & tx), each having a posix mutex. The bug was: posix mutexes were deleted after locking (taking) them. FreeRTOS mutexes must not be deleted while being taken, that breaks the priority inheritance (more precisely the disinheritance), with the visible effect being the mutex hold count not returning to zero. As a side effect, this may also solve the strange event task starvations (hope so…). I was investigating this as I suspected some busy loop in the netmanager context. With the netman running at prio 22, that would effectively block almost all other processing including the timer service. I've found & fixed one potential busy loop trigger in the netman that would have been caused by the netman task still running while all interfaces had been lost -- not sure if that could happen, but it would explain the effects. So please watch your crash debug info & report if the issue still turns up. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

5 19

Fiat500e Quirks
by William Reading 19 Nov '22

19 Nov '22

Howdy there, I recently got an OVMS set up with my Fiat 500e and was happy to see that it works, but I noticed noticed a few oddities. The first one is that it uses Valet Mode (CommandActivateValet) for preconditioning instead of CommandClimateControl: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/bd192… <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/bd192…> Is there a downside to changing the code to where it uses Climate Control instead? It seems like that would fit better with the intended functionality. The other is that it seems to rapidly generate spurious charging / not charging events, which en masse seems to make the websocket connection on the web server time out. I can put together a pull request to try to fix these issues, but was wondering if there are any thoughts on these two things before getting started. There's also no pictures of the Fiat on the iOS App, but I assume that's because the last release of the iOS App predates support. Thanks, William Reading

2 3

IOS app reported GSM signal strength
by Craig Leres 17 Oct '22

17 Oct '22

I've noticed for awhile but never asked the question; why does the IOS app report wifi signal strength when I'm connected to wifi as gsm signal strength? I would expect gsm to always be gsm and maybe wifi would also be shown (and identified as such) when present. Note that I run my modules in wifi client-only mode. Craig

2 2

Not processing canbus frames anymore
by Craig Leres 24 Sep '22

24 Sep '22

I have a v3.3 module in my Corvette and recently got it back on the road but I find that following the sim7600 modem testing I did a few weeks ago, it doesn't seem to be processing canbus frames. When the car is running, the module does not appear to update soc or vin although this used to work. Comparing "module sum" between it and my Cadillac turned up something extra in the [vehicle] section: [vehicle] 12v.alert: 12v.ref: - id: RF059 + id: 768V name: timezone: PST8PDT,M3.2.0,M11.1.0 timezone_region: America/Los_Angeles - type: CHEVROLET_C6_CORVETTE units.distance: M While the [auto] section only has expected differences: [auto] @@ -38,9 +44,9 @@ scripting: yes server.v2: yes server.v3: yes - vehicle.type: C6CORVETTE + vehicle.type: C2CTS wifi.mode: client - wifi.ssid.ap: RF059 + wifi.ssid.ap: 768V wifi.ssid.client: Team America I don't really remember/know how to quickly monitor the canbus but with the car running it *seems* to be seeing canbus frames: OVMS# can log start monitor crtd CAN logging to MONITOR active: Type:monitor Format:crtd(discard) Vehicle:C6CORVETTE Note: info logging is at debug log level, frame logging is at verbose, and errors as usual OVMS# can log status #1: open Type:monitor Format:crtd(discard) Vehicle:C6CORVETTE Messages:7240 Dropped:0 Filtered:0 Rate:0.0% MONITOR: running Messages:7240 Discarded:0 Dropped:0 Filtered:0 Rate:0.0% OVMS# can log status #1: open Type:monitor Format:crtd(discard) Vehicle:C6CORVETTE Messages:11447 Dropped:0 Filtered:0 Rate:0.0% MONITOR: running Messages:11447 Discarded:0 Dropped:0 Filtered:0 Rate:0.0% OVMS# can list can1: Active/500000 dbc none can2: Off/1000000 dbc none can3: Off/1000000 dbc none Any suggestions on how to figure out what I'm doing wrong? Craig

5 20

GPS flatbed alerts from military jamming/spoofing?
by Michael Balzer 29 Apr '22

29 Apr '22

I've had no GPS false alerts since Craig added the NMEA checksum validation and I fixed the VW e-Up state detection. That is, until war on Ukraine began. Since then, I've had multiple alerts, mostly late night. I wouldn't have thought military GPS jamming or spoofing would have an effect with that range, the next war region is ~ 1.200 km from here. I've added some more logging to see if we can detect and filter this. Reduced log from the latest event below. HDOP jumps from 1.8 (good) to 5.6 (bad), but only after the alert has been triggered. Should we generally scale the alarm threshold by HDOP (if available)? Regards, Michael 01:31:35 vehicle dist=15 smoothed=13 alarm=500 gpsmode=AA satcount=6 hdop=2.0 gpsspeed=0.0 01:48:30 vehicle dist=15 smoothed=15 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 02:04:10 vehicle dist=15 smoothed=15 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 02:20:50 vehicle dist=14 smoothed=16 alarm=500 gpsmode=AA satcount=3 hdop=500.0 gpsspeed=0.0 04:15:15 vehicle dist=260 smoothed=60 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:15:15 vehicle dist=297 smoothed=107 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:15:20 vehicle dist=216 smoothed=129 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=8.5 04:15:20 vehicle dist=184 smoothed=140 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=8.5 04:16:00 vehicle dist=1162 smoothed=344 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:16:00 vehicle dist=1322 smoothed=540 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:16:00 CEST W flatbed.moved gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:16:05 vehicle dist=1419 smoothed=716 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 04:16:05 vehicle dist=1426 smoothed=858 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 04:17:25 vehicle dist=710 smoothed=828 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=5.2 04:17:25 vehicle dist=303 smoothed=723 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=5.2 04:17:30 vehicle dist=245 smoothed=627 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:30 vehicle dist=233 smoothed=549 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:35 vehicle dist=161 smoothed=471 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=13.7 04:17:35 vehicle dist=143 smoothed=405 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=13.7 04:17:40 vehicle dist=100 smoothed=344 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:40 vehicle dist=87 smoothed=293 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:45 vehicle dist=50 smoothed=244 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:45 vehicle dist=36 smoothed=203 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:50 vehicle dist=127 smoothed=187 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:50 vehicle dist=136 smoothed=177 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:55 vehicle dist=110 smoothed=164 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:17:55 vehicle dist=104 smoothed=152 alarm=500 gpsmode=AA satcount=5 hdop=5.6 gpsspeed=0.0 04:18:00 vehicle dist=107 smoothed=135 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=0.0 04:18:05 vehicle dist=57 smoothed=119 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=9.4 04:18:05 vehicle dist=44 smoothed=104 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=9.4 04:18:10 vehicle dist=34 smoothed=90 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=7.2 04:18:15 vehicle dist=17 smoothed=66 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=7.8 04:18:15 vehicle dist=6 smoothed=54 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=7.8 04:18:25 vehicle dist=25 smoothed=35 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=1.7 04:18:25 vehicle dist=29 smoothed=34 alarm=500 gpsmode=AA satcount=6 hdop=1.8 gpsspeed=1.7 04:18:35 vehicle dist=25 smoothed=30 alarm=500 gpsmode=AA satcount=5 hdop=1.8 gpsspeed=0.0 04:32:25 vehicle dist=15 smoothed=15 alarm=500 gpsmode=AA satcount=4 hdop=1.9 gpsspeed=0.0 04:48:15 vehicle dist=15 smoothed=14 alarm=500 gpsmode=AA satcount=5 hdop=3.1 gpsspeed=0.0 04:48:20 vehicle dist=15 smoothed=14 alarm=500 gpsmode=AA satcount=5 hdop=3.1 gpsspeed=0.0 04:48:25 vehicle dist=18 smoothed=15 alarm=500 gpsmode=AA satcount=4 hdop=3.1 gpsspeed=1.5 04:48:30 vehicle dist=14 smoothed=16 alarm=500 gpsmode=AA satcount=4 hdop=6.2 gpsspeed=0.0 -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

4 10

Vehicle support for VW MEB platform
by ovmsdev 24 Apr '22

24 Apr '22

Hi all, I'm new to OVMS, just ordered my kit. Sinc e I own an VW ID.4, I'd like to add support for the VW MEB platform, which includes the Skoda Enyaq, Volkswagen ID.x, Audi Q4 etron, Cupra Born. Anyone else interesting in helping out? I have found some resources that will help us get started: VW ID3 support for the evDash: https://github.com/nickn17/evDash/blob/master/src/CarVWID3.cpp ID.3 support for the UDS Decoder tool: https://www.goingelectric.de/forum/viewtopic.php?p=1758362&sid=f3168951a5a6… https://github.com/TUMFTM/uds-decoder/blob/master/python_can_recorder/ids.t… Quickest way would be to create an EBC description for it... but I guess for full feature support we'll need an additional vehicle to the source code. Which of the existing vehicles would be best suited as a starting point: vweup? This uses two CAN connectors though. Kind regards, Wessel

3 2

Re: [Ovmsdev] MG5 - I'd like to help
by Martin Klefas-Stennett 05 Apr '22

05 Apr '22

I just got an MG5 LR and while any actual development work is completely beyond me, I’m happy to help with collecting data and such if that’s useful? I noticed in the Docs that it mentions the MG5 Specifically as “not yet supported in this build” though, so perhaps you’re all past the stage where someone unskilled could be useful? Thanks in advance. Regards, Martin Klefas-Stennett. ________________________________ From: Martin Klefas-Stennett Sent: 13 February 2022 22:22 To: ovmsdev(a)lists.openvehicles.com <ovmsdev(a)lists.openvehicles.com> Subject: MG5 - I'd like to help I just got an MG5 LR and while any actual development work is completely beyond me, I’m happy to help with collecting data and such if that’s useful? I noticed in the Docs that it mentions the MG5 Specifically as “not yet supported in this build” though, so perhaps you’re all past the stage where someone unskilled could be useful? Thanks in advance.

1 0

Update zlib to version 1.2.12
by Michael Balzer 02 Apr '22

02 Apr '22

Everyone, I've just updated our zlib clone (https://github.com/openvehicles/zlib) to version 1.2.12, fixing a serious security issue (out of bounds access by extracting malicious ZIP data). To follow you need to do… git submodule update --recursive …after your next pull/fetch. From https://www.zlib.net/: > > Version 1.2.12 has these key improvements over 1.2.11: > > * Fix a deflate bug when using theZ_FIXEDstrategy that can result in > out-of-bound accesses. > * Fix a deflate bug when the window is full indeflate_stored(). > * Speed up CRC-32 computations by a factor of 1.5 to 3. > * Use the hardware CRC-32 instruction on ARMv8 processors. > * Speed upcrc32_combine()with powers of/x/tables. > * Addcrc32_combine_gen()andcrc32_combine_op()for fast combines. > > /Due to the bug fixes, any installations of 1.2.11 should be replaced > with 1.2.12./ I suggest also checking your other projects for inclusions of zlib. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

1 0