June 2021 - OvmsDev - Open Vehicles

new member interested in Kia Soul EV preheating
by EV Eh? 28 Jun '21

28 Jun '21

Hello! I'm new. I have an OVMS installed now, and working pretty well on my 2018 Kia EV Soul. I can now use the previously useless "third button" on the remote to open the charging door, and remote lock and unlock the car. I can even show a nearly useless (but fun) second speedometer using the web interface and my iPad while driving by connecting to the OVMS AP. I have the antennas connected and the cell phone modem working. Win! I have SavvyCAN installed and working over wifi too. I have spare SD Cards I can use if network streaming isn't enough. I'm interested in trying to get some sort of pre-heating going in the Soul. The story coming to mind: - As a driver, I'd like to be able to tell my Soul to start warming itself up while connected to an EVSE, so that when I leave the house in ~30 minutes I'll have a warm car and won't have to spend my precious 180km of range (who are we kidding, 150 in winter) on that. It'd be nice to do this in the OVMS Android app somehow, but that's negotiable. >From stalking this forum and Kia SOUL EV forums, people have figured out lots of things about the Soul but not this yet somehow? I have a background in software dev and *nix systems administration, and I'm a tinkerer at heart. How do I get started? Naively, it seems like I would just ... what, start SaavyCAN, sit in the car and ... turn the heat on? That can't possibly work. Maybe ... have the scheduled cabin preheater start while SavvyCAN is listening? I mean, surely someone tried that already? (I'll likely start here if there's no alternative advice out there..) Cheers, Kyle aka Longbranchflyer, EVEhCanada

1 0

Simcom 7000G
by Derek Caudwell 27 Jun '21

27 Jun '21

Hi Mark, Craig I have connected up a simcom 7000G module with the v3.3 branch. It required a few tweaks to the power cycling to turn it on/off reliably and now I have realised that it does not appear to support multiplexing of the uart. Any suggestions on the best way to proceed? Will it require a rewrite of the ovms_cellular routines in the simcom_7000 code? Cheers Derek

2 1

New plugin: VW e-Up ECU Library & Toolkit
by Michael Balzer 27 Jun '21

27 Jun '21

https://docs.openvehicles.com/en/latest/plugin/v-vweup/ecutoolkit/README.ht… Probably already the largest plugin I've written so far, although it's only version 0.5 yet… Help & feedback is appreciated. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

1 0

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

DTC code reading
by Tamás Kovács 21 Jun '21

21 Jun '21

Hi! I would like to create a dtc reading on i-miEV/ Peugeot iOn. But if is send the following command: OVMS# obd can1 request device 761 762 19020f 761[762] 19020f: request failed with response error code 80 I now use hobdrive app to read dtc code with OBDlink LX

2 5

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

Re: [Ovmsdev] MCP2515 driver bug?
by Derek Caudwell 04 Jun '21

04 Jun '21

Hi Mark, If you need code improvements tested on a real vehicle let me know, as it would be great to get the issue resolved. I suspect it is the main cause of the module crashes on the Leaf. Michael, the ovms archives can be searched from Google by explicitly specifying the site eg mcp2515 site:http://lists.openvehicles.com/pipermail/ovmsdev/ Kind regards Derek

4 3