April 2021 - 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

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

16 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

TLS CA question
by Stephen Casner 29 Jan '22

29 Jan '22

I find that I need to enable the following option in my testing of the possible replacement of MEDTLS with WolfSSL, otherwise I get an "ASN no signer to confirm" error: WOLFSSL_ALT_CERT_CHAIN allows CA's to be presented by peer, but not part of a valid chain. Default wolfSSL behavior is to require validation of all presented peer certificates. This also allows loading intermediate CA's as trusted and ignoring no signer failures for CA's up the chain to root. The alternate certificate chain mode only requires that the peer certificate validate to a trusted CA. Is that expected for the trust arrangements we are using? A possibly related question: do we expect the server to validate clients, or only the clients to validate the server? -- Steve

4 60

Open issues blocking release 3.2.016
by Michael Balzer 21 Jun '21

21 Jun '21

As the other thread got off-topic: I'd still like to get forward regarding release 3.2.016. We identified three open issues: 1. VW e-Up sometimes stays awake for 4-5 hours. 2. Wifi AP connection is unstable with some devices. 3. More frequent location flatbed theft false alerts. My current status on these is: 1. …is probably not a bug on the OVMS but rather a real behaviour of the e-Up performing an extended 12V trickle charge. 2. …has only been reported by Steve Davies and seems (?) to have been solved by the default scan timings – Steve? 3. …seems to be a Heisenbug, i.e. hasn't had any reports since we added extended logging. Is my status correct? If so, I think these should no longer stop us from releasing 3.2.016. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

6 12

Bolt / Amperae support
by Edwin ten Haaf 25 Apr '21

25 Apr '21

short update. When waking up the car with volt.ampera template I get lot's of data. The solution to get data was, wake up the car :-) (sorry) So the good news is that it can communicate. It reads out the charge status. Range does not match but that's understandable. [image: image.png] [image: image.png] Switching to my new template I get [image: image.png] In verbose level the module crashes because of to much data. How can I port the volt/ampera readings to the new templates. Must be something with the connectivity(can) I gues ? Thanks in advance, Edwin

1 0

Bolt Ampera-e support
by Edwin ten Haaf 24 Apr '21

24 Apr '21

Goodmorning all, I made little progress but now I'm stuck and could need some help/advice. Made a new vehicle template from the hyundayionic as advised. Changed the pids but it's not working very well. Sometimes the app seems to come alive and shows it's charging but it's not reproducable. Same happens when picking Volt/Ampera module for my ampera-e. I don't know how to investigate this further. I have some logs attached and my work in progress on Github <https://github.com/Edwintenhaaf/Open-Vehicle-Monitoring-System-3/tree/bolt-…> . Thanks in advance, Edwin I (37857379) v-bae: Chevrolet Bolt / Opel Ampera-e vehicle module D (37857379) events: Signal(power.can1.on) D (37857379) max7317: egpio.output.2.low D (37857379) events: Signal(egpio.output.2.low) D (37857389) metrics: pmetrics_register: 'xbae.c.state' => slot=68, used 78/100 D (37857389) metrics: pmetrics_register: 'xbae.b.soc.bms' => slot=69, used 78/100 D (37857389) events: Signal(vehicle.type.set) D (37857759) events: Signal(config.changed) D (37857759) webserver: ConfigChanged: config.changed auto I (37858279) webserver: HTTP GET /menu I (37858299) location: UpdateParkPosition: vehicle is driving I (37858299) v-bae: PollerStateTicker: [online] charge_state=00 => PollState 0->1 D (37858299) vehicle: PollerSend(1): send [bus=0, type=22, pid=8334], expecting 7e4/7ec-7ec E (37858299) can: can1: intr=1 rxpkt=0 txpkt=0 errflags=0x8000d9 rxerr=0 txerr=8 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (37858309) can: can1: intr=3 rxpkt=0 txpkt=0 errflags=0x8000d9 rxerr=0 txerr=24 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (37858309) can: can1: intr=5 rxpkt=0 txpkt=0 errflags=0x8000d9 rxerr=0 txerr=40 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (37858309) can: can1: intr=7 rxpkt=0 txpkt=0 errflags=0x8000d9 rxerr=0 txerr=56 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (37858309) can: can1: intr=9 rxpkt=0 txpkt=0 errflags=0x8000d9 rxerr=0 txerr=72 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (37858309) can: can1: intr=10 rxpkt=0 txpkt=0 errflags=0x8000d9 rxerr=0 txerr=80 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (37858309) can: can1: intr=13 rxpkt=0 txpkt=0 errflags=0x8040d9 rxerr=0 txerr=104 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (37858309) can: can1: intr=19 rxpkt=0 txpkt=0 errflags=0x8040a4 rxerr=5 txerr=112 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (37858309) can: can1: intr=24 rxpkt=0 txpkt=0 errflags=0x8040a4 rxerr=12 txerr=112 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (37858309) can: can1: intr=27 rxpkt=0 txpkt=0 errflags=0xa040d9 rxerr=13 txerr=128 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (37858319) can: can1: intr=28 rxpkt=0 txpkt=0 errflags=0x804cd9 rxerr=13 txerr=128 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 E (37858319) can: can1: intr=28 rxpkt=0 txpkt=0 errflags=0x804cd9 rxerr=13 txerr=128 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=1 wdgreset=0 errreset=0 D (37858309) events: Signal(vehicle.aux.12v.on) D (37858319) events: Signal(vehicle.charge.12v.start) D (37858319) events: Signal(vehicle.awake) D (37858329) events: Signal(vehicle.on) D (37858329) events: Signal(vehicle.charge.state) I (37859289) powermgmt: Charging 12V battery..

1 0

OVMS going comatose
by Stephen Casner 24 Apr '21

24 Apr '21

Since updating my in-car OVMS with a build from the master branch after my WolfSSL update I've experienced a couple of instances where connectivity from app was lost. The first time I needed a quick resolution so I just reset OVMS. It happened again during the night while charging, and this time I connected to the console to check conditions before resetting. What I found was that the async console was not responding at all. Since I have OVMS configured to drop into gdb on a crash, I should have seen something. I've turned on logging to file to see if that sheds any light. -- Steve

3 16

Tesla Roadster VDS custom message
by Mark Webb-Johnson 21 Apr '21

21 Apr '21

Great things are afoot for Tesla Roadster and OVMS. Mark

3 3

upload error
by Edwin ten Haaf 21 Apr '21

21 Apr '21

[image: image.png] [image: image.png] Hello All, Been trying to get Amperae support working. Did some work in the config and tried to upload this to the module but it failed. I do not know what went wrong. Followed the developers guide. Any advice welcome. Edwin

3 2

Willing to help adding Ampera-e/Bolt support
by Edwin ten Haaf 16 Apr '21

16 Apr '21

Hello All, I'm currently driving a 2018 Opel Ampera-e and since Opel pulled out the plug from OnStar as they moved to PSA group (peugeot) my car is offline. Recently I noticed the OVMS project and bought myself a kit. It's hooked up and connected but only location data is available at the moment. The pids needed are available from this location https://allev.info/boltpids/ Jason_ABRP wrote some tips in the forum thread https://www.openvehicles.com/node/2345 As I am not a developer but a eager to learn system engineer in IT i'm lost from this point. In the bolt/ampera pid sheet there are these pids but how do I translate these into a new car template? My son is a software developer student and can also help me in making this template. Any help would be appreciated. Thanks, Edwin

3 2