May 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 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

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

Tesla Powered RAV4 EV support
by Michael Iimura 04 Jul '21

04 Jul '21

I am planning to work on support for the Tesla Powered 2012-2014 Toyota RAV4 EV. I don't see any evidence of earlier work on Github. I have done some preliminary recon and determined that only the main Toyota CAN and Tesla CAN are needed for the desired information. Maybe K-Line for TPMS would be nice since the car won't display pressures, but the Toyota Techstream diagnostic software does. The most valuable information is on the Tesla CAN and should be similar or exactly the same as other Tesla models. I am just starting to gather hardware and software at this moment, but suggestions are welcomed. - Mike

4 6

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

22 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

Poller support for VW TP 2.0
by Michael Balzer 11 Jun '21

11 Jun '21

Everyone interested in VW/VAG vehicles: I've added a first implementation of the VW TP 2.0 protocol in the vehicle poller. I've pushed this to a new branch for testing: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/tree/vwtp20 This includes refactoring the ISO TP engine into a separate module, so may introduce bugs with that. Please do not introduce larger changes in the master poller code until we've tested and merged this change. The VW TP 2.0 engine is based on the explanation by Jared Wiltshire (https://jazdw.net/tp20) plus some observations & tests I've made with my Seat Mii. I've added a text version of Jared's page in the vehicle docs folder: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/vwtp2… VW TP 2.0 polls integrate seamlessly into an existing poller list and can also be sent as single OBD requests. Quoting from vehicle.h: // VWTP_20: this protocol implements the VW (VAG) specific "TP 2.0", which establishes // OSI layer 5 communication channels to devices (ECU modules) via a CAN gateway. // On VWTP_20 poll entries, simply set the TXID to the gateway base ID (normally 0x200) // and the RXID to the logical 8 bit ECU ID you want to address. // TP 2.0 transports standard OBD/UDS requests, so everything else works the same way // as with ISO-TP. // // VW TP 2.0 poll entry examples: // // TXID, RXID, TYPE, PID, TIMES, BUS, PROT // { 0x200, 0x1f, 0x10, 0x89, {…times…}, 0, VWTP_20 } // { 0x200, 0x1f, 0x22, 0x04a1, {…times…}, 0 , VWTP_20 } // // VW gateways currently do not support multiple open channels. To minimize connection // overhead for successive polls to an ECU, the VWTP_20 engine keeps an idle connection open // until the keepalive timeout occurs. So you should try to arrange your polls in interval // blocks/sequences to the same devices if possible. // // To explicitly close a VWTP_20 channel, send a poll (any type) to RXID 0, that just // closes the channel (ECU ID 0 is an invalid destination): // { 0x200, 0, 0, 0, {…times…}, 0 , VWTP_20 } To manually send a request, use the "-v" option on the OBD request command to select VW TP 2.0, e.g.: OVMS# obd can1 req dev -v 200 1f 22f197 200[1f] 22f197: Response: 47 57 2d 4b 2d 43 41 4e 20 54 50 32 30 | GW-K-CAN TP20 To manually close a channel from the shell, issue: OVMS# obd can1 req dev -v 200 00 0000 Feedback, code audits & tests are welcome. If you encounter errors or misbehaviour, please send me a debug log including the CAN range 200-3ff: OVMS# log level debug vehicle-vwtp OVMS# can log start monitor crtd 200-3ff Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

1 1

Server HTTP API: vehicle connect & disconnect
by Michael Balzer 28 May '21

28 May '21

By request of a user implementing an OVMS plugin for the EVCC framework (https://github.com/andig/evcc) I've extended the server HTTP API by calls to connect to and disconnect from a vehicle: https://docs.openvehicles.com/en/latest/protocol_httpapi/requests.html#get-… I've also added the message timestamps & ages to the other responses along with this, so an API client can tell if the data is fresh. @Mark: please verify my code (I'm no perl monk) & consider updating the api.openvehicles.com server so the plugin can be used with that server as well. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

1 2

Generator / V2G metrics
by Derek Caudwell 24 May '21

24 May '21

Hi all, In case it is helpful to others here is a sample output of the V2G metrics populated for the Leaf from a recent session. Note I've opted for presenting the Chademo voltage, current and power output (as the grid voltage and inverter efficiency is not known -external to car- but nominal grid voltage could be set with a parameter and then calculated). v.g.climit 19.8939A v.g.current 7.5A v.g.duration.empty 533Min v.g.duration.range v.g.duration.soc v.g.efficiency v.g.generating yes v.g.kwh 0.0562549kWh v.g.kwh.grid v.g.kwh.grid.total v.g.limit.range v.g.limit.soc v.g.mode standard v.g.pilot yes v.g.power 2.8275kW v.g.state exporting v.g.substate onrequest v.g.temp v.g.time 104Sec v.g.timermode v.g.timerstart v.g.type chademo v.g.voltage 377V Michael, is it possible to have v.g metrics added to the V2 server message format for incorporating into the ovms app? Is it worth having a parameter to indicate car support for V2G functionality? Cheers Derek

2 1

Beta V2X for Nissan Leaf
by Derek Caudwell 19 May '21

19 May '21

Hi all, I have added basic Vehicle to Grid/Home metrics for the Leaf. If anyone else has a V2X unit and is able to test it that would be great. It is available here: https://github.com/drc38/Open-Vehicle-Monitoring-System-3 Cheers Derek

1 0

4G Simcom board
by Derek Caudwell 10 May '21

10 May '21

Hi, To connect to 4G can anyone foresee an issue connecting up a SimCom 7000g such as this to the OVMS mainboard: https://a.aliexpress.com/_mNyRKTn I assume it may need the level shifter added (TXS0104EPWR) if not already on the board. Are all the SimCom commands generic or require modifying? Cheers Derek

3 3