July 2019 - OvmsDev - Open Vehicles

Locations and scripts
by ovms 03 Dec '19

03 Dec '19

Hi I would like to run scripts based on location. The scripts work fine, but the location service stops working. I guess the location service requires CAN1 to be working? Since CAN1 stops receiving after a short period of time, the location service also stops. Is there a way to bypass this so the location service does not depend on CAN1 working? Kind regards, Stein Arne Sordal

7 61

Added Pushover and SSL client support
by Marko Juhanne 26 Oct '19

26 Oct '19

Hello all, I've been wanting to have a bit more configurable notification system on my mobile phone compared to the OVMS mobile app (quiet hours, different message priority levels, override quiet hours with emergency priority, custom sounds, persistent notifications demanding acknowledgment etc). I already use Pushover as notification platform for my home automation system and it has worked nicely for these two past years so I decided to port Pushover client to OVMS as well. For those who don't know, Pushover is a notification platform that has apps for iOS and Android. They also have a desktop (actually web) application as well. You create an account and then register your application. There's a 5 USD per platform one-time fee, which I find quite reasonable. Message limit is 7500 messages / month / application. So if you have multiple cars, you could register them as individual applications. I'm not affiliated with the company, just a happy customer. There are now commits for Pushover support on my fork ( https://github.com/mjuhanne/Open-Vehicle-Monitoring-System-3) It's up to date with the main branch, and has the SWCAN commits as well. I would appreciate if others could test it before making a pull request, since there are now quite many changes. I didn't want to add another http client, so I used Mongoose. But then after enabling SSL support using mbedssl I found out that there's this client space "struct mg_connect_opts" that will be too small (and causes crash) if MG_ENABLE_SSL is not enabled also in every component that uses Mongoose. To configure Pushover, there's a new Config/Notifications page on OVMS. You can filter which notifications and events will be relayed and select their priority levels accordingly. I thought about using web config pluging, but maybe we could integrate this page to configure notifications for OVMS mobile apps as well? Best regards, Marko Juhanne

3 9

SWCAN and enhanced Ampera/Volt support
by Marko Juhanne 18 Oct '19

18 Oct '19

Hi all, I've been tinkering with OVMS and Opel Ampera these few past months, and the I've made some progress with the SWCAN support. As you know, the SN65 transceiver cannot do High-Voltage Wake Up, so many of the nice-to-have polling and remote controlling functions are not available on those cars that rely on it, such as Volt/Ampera. So I've created an add-on SWCAN board that attaches to the internal OVMS extension header. The board uses TH8056 transceiver, which is specifically designed for SWCAN bus. As for the controller, same MCP2515 is used as in OVMS. Here's the link to the boards GitHub page: https://github.com/mjuhanne/OVMS-SWCAN For the firmware patches, here's my OVMS branch: https://github.com/mjuhanne/Open-Vehicle-Monitoring-System-3 There are a lot of changes, especially MCP2515 code add-ons and refactoring, of which some are specific to the new swcan-bus, but some could be beneficial otherwise as well. Then there's the support for the new board and TH8056. On the other hand, if a car can be woken up without HV WakeUp, the board is not really needed and the SN65 can be used with 33.3 kbps speed to communicate on SWCAN bus. Since ESP32 supports only 3 hardware CS on one SPI bus and all the CS lines are now already used, there's also patches for software CS (that's what the additional MCP2515 is using). With my OBD cable I wire SWCAN to use CAN2 lines and put the 2nd MCP2515 on OVMS to sleep, but there's no reason why all the 4 CAN controllers couldn't work independently at the same time (untested at this time). There's also patches to the Ampera/Volt module code base to include SWCAN support, add handling of several new CAN messages (still work in progress, more to come!), as well as VoltStar-like capabilities (locking/unlocking doors, remote preheat) similar to Brian Batista's MyVolStar app/OBDLink MX-combo. Sadly, I haven't been able to get the VoltStar-specific functionality to work on my 2014 Ampera, but other non-Voltstar SWCAN messages do work (waking up the car, controlling windows etc.). This is is similar to other reports of MyVolStar on 2014 Volt/Ampera, so maybe something has changed in the ECU behaviour between MY13 and MY14. It would be really nice to get other OVMS developers with SWCAN/GMLAN enabled cars to test these. SWCAN specific patches can be tested also without the board, but naturally the HV Wakeup functionality is not available. Let me know if you're interested so I can send a PCB or two for testing (I have bunch of leftovers). Best regards, Marko

4 4

Dexter'web API
by Tim Jackson 28 Sep '19

28 Sep '19

Hi there all, I have 2 of the latest units, and I am running a Nissan Leaf and e-NV200.. I have 2 questions 1. Is there an API for dexter-web.de <http://dexter-web.de/> site? 2. Is there any updated documentation on the current API on TMC? Thanks Tim

2 2

Roadster cooldown again
by Stephen Casner 23 Aug '19

23 Aug '19

Today my coolant pump was running continuously even though the charge level was only 55% and the ambient temperature was only 77F, although the battery was at 89F (32C) left over from a drive last evening. So, I decided to try cooldown again. The log is below. This time the charge current was properly managed at 12A and Range mode. The A/C fans came on soon after starting and the battery temp was reduced from 32C to 30C in 3 minutes. However, after that the temperature did not drop further, even though the templimit is currently set to 25C, except for a brief period at 29C for 3 minutes about halfway through the hour time limit before returning to 30C. I didn't monitor the whole time, but I didn't notice the A/C fans on any more. Does the Roadster not try to cool below 30C? Yet when we were testing last winter while the ambient temperature was cooler, I was able to set the templimit to 19C and the car did cool the battery from 20C to 19C in the test. Perhaps the car's goal temperature is based on some delta from the ambient temperature. This time the session correctly did not turn into a regular charging session after the cooldown time limit was reached, and the coolant pump did stop running. -- Steve Welcome to the Open Vehicle Monitoring System (OVMS) - SSH Console Firmware: 3.2.001-18-gac0ae29b-dirty/ota_1/main Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1 OVMS# config list xtr xtr (readable writeable) cooldown.templimit: 25 OVMS# log file /sd/cooldown Logging to file: /sd/cooldown OVMS# log mon Monitoring log messages enabled I (466541) ovms-server-v2: Incoming Msg: MP-0 Z0 I (493591) ovms-server-v2: Send MP-0 PAStandard - Charge Stopped|SOC: 54.0%|Ideal range: 124M|Est. range: 115M|ODO: 55912.4M OVMS# charge cooldown Cooldown has been started I (540471) v-teslaroadster: Cooldown: 0 cycles 32C/25C 12A (with 60 minute(s) remaining) I (580461) ovms-server-v2: Incoming Msg: MP-0 Z1 I (580521) ovms-server-v2: One or more peers have connected I (581471) ovms-server-v2: Send MP-0 S54.0,M,245,12,charging,range,153,142,12,0,0,0,5,1,3,0,0,0,178.49,858,0,0,0,0,0,0,0,0,0,0,0,-1.16,0.00,79 I (581541) ovms-server-v2: Send MP-0 D92,0,5,31,28,31,466,559124,0,581,23,2,1,1,12.75,0,12.6,128,31,0,0 I (581601) ovms-server-v2: Send MP-0 L37.346279,-122.037292,336,30,1,1,0,0,1.2,0,0 I (581661) ovms-server-v2: Send MP-0 W0,0,0,0,0,0,0,0,0 I (581711) ovms-server-v2: Send MP-0 F3.2.001-18-gac0ae29b-dirty/ota_1/main (build idf v3.1-dev-2835-g151269458-dirty May 23 2019 17:16:23),5YJRE11B181000033,25,1,TR1N,Revelstoke I (599471) ovms-server-v2: Send MP-0 PIRange - Charging|242.0V/12.0A|Full: 858 mins|SOC: 54.0%|Ideal range: 153M|Est. range: 142M|ODO: 55912.4M|CAC: 178.5Ah|SOH: 80% I (600471) v-teslaroadster: Cooldown: 0 cycles 31C/25C 12A (with 59 minute(s) remaining) I (600551) housekeeping: 2019-07-30 19:07:05 GMT (RAM: 8b=113788-127376 32b=10312) I (638391) ovms-server-v2: Incoming Msg: MP-0 Z0 I (660471) v-teslaroadster: Cooldown: 0 cycles 31C/25C 12A (with 58 minute(s) remaining) I (720471) v-teslaroadster: Cooldown: 0 cycles 30C/25C 12A (with 57 minute(s) remaining) I (780471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 56 minute(s) remaining) I (793471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (803471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (840471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 55 minute(s) remaining) I (853471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (863471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (900471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 54 minute(s) remaining) I (900541) housekeeping: 2019-07-30 19:12:05 GMT (RAM: 8b=113788-127084 32b=10312) I (913471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (923471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (960471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 53 minute(s) remaining) I (973471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (983471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1020471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 52 minute(s) remaining) I (1033471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1043471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1080471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 51 minute(s) remaining) I (1093471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1103471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1140471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 50 minute(s) remaining) I (1153471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1163471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1182471) ovms-server-v2: Send MP-0 S54.0,M,243,12,charging,range,155,143,12,10,0,100,5,1,3,0,0,0,178.49,875,0,0,0,0,0,0,0,0,0,0,0,-2.32,0.00,79 I (1182551) ovms-server-v2: Send MP-0 D92,0,5,35,33,30,466,559124,0,1182,25,2,1,1,12.79,0,12.6,0,35,0,0 I (1182611) ovms-server-v2: Send MP-0 L37.346329,-122.037262,336,57,1,1,0,0,2.3,0,0 I (1182661) ovms-server-v2: Send MP-0 F3.2.001-18-gac0ae29b-dirty/ota_1/main (build idf v3.1-dev-2835-g151269458-dirty May 23 2019 17:16:23),5YJRE11B181000033,25,1,TR1N,Revelstoke I (1200471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 49 minute(s) remaining) I (1200601) housekeeping: 2019-07-30 19:17:05 GMT (RAM: 8b=113788-127376 32b=10312) I (1213471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1223471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1260471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 48 minute(s) remaining) I (1273471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1283471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1320471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 47 minute(s) remaining) I (1333471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1343471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1380471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 46 minute(s) remaining) I (1393471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1403471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1440471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 45 minute(s) remaining) I (1453471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1463471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1500471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 44 minute(s) remaining) I (1500541) housekeeping: 2019-07-30 19:22:05 GMT (RAM: 8b=113788-127084 32b=10312) I (1513471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1523471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1560471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 43 minute(s) remaining) I (1573471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1583471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1603141) ovms-server-v2: Incoming Msg: MP-0 Z1 I (1603191) ovms-server-v2: One or more peers have connected I (1603471) ovms-server-v2: Send MP-0 S54.0,M,245,12,charging,range,156,144,12,17,0,100,5,1,3,0,0,0,178.49,864,0,0,0,0,0,0,0,0,0,0,0,-2.32,0.00,79 I (1603551) ovms-server-v2: Send MP-0 D92,0,5,35,36,30,466,559124,0,1603,25,2,1,1,12.79,0,12.6,0,35,0,0 I (1603621) ovms-server-v2: Send MP-0 L37.346302,-122.037346,336,65,1,1,0,0,2.3,0,0 I (1603681) ovms-server-v2: Send MP-0 W0,0,0,0,0,0,0,0,0 I (1603741) ovms-server-v2: Send MP-0 F3.2.001-18-gac0ae29b-dirty/ota_1/main (build idf v3.1-dev-2835-g151269458-dirty May 23 2019 17:16:23),5YJRE11B181000033,25,1,TR1N,Revelstoke I (1620471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 42 minute(s) remaining) I (1631391) ovms-server-v2: Incoming Msg: MP-0 Z0 I (1633471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1643471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1680471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 41 minute(s) remaining) I (1693471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1703471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1740471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 40 minute(s) remaining) I (1753471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1763471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1800471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 39 minute(s) remaining) I (1800541) housekeeping: 2019-07-30 19:27:05 GMT (RAM: 8b=113788-127084 32b=10312) I (1813471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1823471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1860471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 38 minute(s) remaining) I (1873471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1883471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1920471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 37 minute(s) remaining) I (1933471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (1943471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (1980471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 36 minute(s) remaining) I (1993471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (2003471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (2040471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 35 minute(s) remaining) I (2053471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (2063471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (2100471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 34 minute(s) remaining) I (2100541) housekeeping: 2019-07-30 19:32:05 GMT (RAM: 8b=113788-127084 32b=10312) I (2113471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (2123471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (2141341) ovms-server-v2: Incoming Msg: MP-0 Z1 I (2141401) ovms-server-v2: One or more peers have connected I (2141471) ovms-server-v2: Send MP-0 S55.0,M,244,12,charging,range,157,146,12,26,0,100,5,1,3,0,0,0,178.49,853,0,0,0,0,0,0,0,0,0,0,0,-2.32,0.00,79 I (2141531) ovms-server-v2: Send MP-0 D92,0,5,35,40,30,466,559124,0,2141,25,2,1,1,12.78,0,12.6,0,35,0,0 I (2141591) ovms-server-v2: Send MP-0 L37.346249,-122.037209,336,42,1,1,0,0,2.3,0,0 I (2141641) ovms-server-v2: Send MP-0 W0,0,0,0,0,0,0,0,0 I (2141721) ovms-server-v2: Send MP-0 F3.2.001-18-gac0ae29b-dirty/ota_1/main (build idf v3.1-dev-2835-g151269458-dirty May 23 2019 17:16:23),5YJRE11B181000033,25,1,TR1N,Revelstoke I (2160471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 33 minute(s) remaining) I (2173471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (2174471) ovms-server-v2: Send MP-0 S55.0,M,245,12,charging,performance,158,146,12,27,0,100,5,1,4,0,0,0,178.49,857,0,0,0,0,0,0,0,0,0,0,0,-2.32,0.00,79 I (2177381) ovms-server-v2: Incoming Msg: MP-0 Z0 I (2183471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (2220471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 32 minute(s) remaining) I (2233471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (2243471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (2280471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 31 minute(s) remaining) I (2293471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (2303471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (2340471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 30 minute(s) remaining) I (2353471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (2363471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (2400471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 29 minute(s) remaining) I (2400531) housekeeping: 2019-07-30 19:37:06 GMT (RAM: 8b=113788-127084 32b=10312) I (2413471) v-teslaroadster: Cooldown: Cycle 1 PERFORMANCE mode I (2423471) v-teslaroadster: Cooldown: Cycle 1 RANGE mode I (2460471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 28 minute(s) remaining) I (2520471) v-teslaroadster: Cooldown: 1 cycles 30C/25C 12A (with 27 minute(s) remaining) I (2580471) v-teslaroadster: Cooldown: 2 cycles 29C/25C 12A (with 26 minute(s) remaining) I (2607471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (2617471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (2640471) v-teslaroadster: Cooldown: 2 cycles 29C/25C 12A (with 25 minute(s) remaining) I (2667471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (2677471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (2700471) v-teslaroadster: Cooldown: 2 cycles 29C/25C 12A (with 24 minute(s) remaining) I (2700541) housekeeping: 2019-07-30 19:42:06 GMT (RAM: 8b=113788-127084 32b=10312) I (2727471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (2737471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (2742471) ovms-server-v2: Send MP-0 S56.0,M,244,12,charging,range,159,147,12,36,0,200,5,1,3,0,0,0,178.49,842,0,0,0,0,0,0,0,0,0,0,0,-2.32,0.00,79 I (2742531) ovms-server-v2: Send MP-0 D92,0,5,35,44,30,466,559124,0,2742,25,2,1,1,12.78,0,12.6,0,35,0,0 I (2742581) ovms-server-v2: Send MP-0 L37.346329,-122.037308,336,55,1,1,0,0,2.3,0,0 I (2742651) ovms-server-v2: Send MP-0 F3.2.001-18-gac0ae29b-dirty/ota_1/main (build idf v3.1-dev-2835-g151269458-dirty May 23 2019 17:16:23),5YJRE11B181000033,26,1,TR1N,Revelstoke I (2760471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 23 minute(s) remaining) I (2787471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (2797471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (2820471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 22 minute(s) remaining) I (2847471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (2857471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (2880471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 21 minute(s) remaining) I (2907471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (2917471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (2940471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 20 minute(s) remaining) I (2967471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (2977471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3000471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 19 minute(s) remaining) I (3000541) housekeeping: 2019-07-30 19:47:06 GMT (RAM: 8b=113788-127084 32b=10312) I (3027471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3037471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3060471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 18 minute(s) remaining) I (3087471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3097471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3120471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 17 minute(s) remaining) I (3147471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3157471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3180471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 16 minute(s) remaining) I (3207471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3217471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3240471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 15 minute(s) remaining) I (3267471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3277471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3300471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 14 minute(s) remaining) I (3300551) housekeeping: 2019-07-30 19:52:06 GMT (RAM: 8b=113788-127084 32b=10312) I (3327471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3337471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3343471) ovms-server-v2: Send MP-0 S56.0,M,243,12,charging,range,161,149,12,46,0,200,5,1,3,0,0,0,178.49,827,0,0,0,0,0,0,0,0,0,0,0,-2.32,0.00,79 I (3343531) ovms-server-v2: Send MP-0 D92,0,5,36,47,30,466,559124,0,3343,25,2,1,1,12.78,0,12.6,0,36,0,0 I (3343611) ovms-server-v2: Send MP-0 L37.346321,-122.037262,336,59,1,1,0,0,2.3,0,0 I (3343671) ovms-server-v2: Send MP-0 F3.2.001-18-gac0ae29b-dirty/ota_1/main (build idf v3.1-dev-2835-g151269458-dirty May 23 2019 17:16:23),5YJRE11B181000033,25,1,TR1N,Revelstoke I (3360471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 13 minute(s) remaining) I (3387471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3397471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3420471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 12 minute(s) remaining) I (3447471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3457471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3480471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 11 minute(s) remaining) I (3507471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3517471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3540471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 10 minute(s) remaining) I (3567471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3577471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3600471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 9 minute(s) remaining) I (3600551) housekeeping: 2019-07-30 19:57:06 GMT (RAM: 8b=113788-127084 32b=10312) I (3627471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3637471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3649701) simcom: PPP Connection disconnected I (3649751) simcom: PPP Connection disconnected I (3650471) simcom: Lost network connection (+PPP disconnect in NetMode) I (3650521) simcom: State: Enter NetLoss state I (3650571) gsm-ppp: Shutting down (hard)... I (3650631) gsm-ppp: PPP is shutdown I (3650711) netmanager: MODEM down (with WIFI client up): staying with WIFI client priority I (3655491) gsm-ppp: StatusCallBack: User Interrupt I (3655541) gsm-ppp: PPP connection has been closed I (3659471) simcom: State timeout, transition to 5 I (3659521) simcom: State: Enter NetWait state I (3660471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 8 minute(s) remaining) I (3663471) simcom: State: Enter NetStart state I (3664561) simcom: PPP Connection is ready to start I (3665471) simcom: State: Enter NetMode state I (3665521) gsm-ppp: Initialising... I (3668241) gsm-ppp: StatusCallBack: None I (3668291) gsm-ppp: status_cb: Connected I (3668351) gsm-ppp: our_ipaddr = 10.170.41.247 I (3668401) gsm-ppp: his_ipaddr = 10.64.64.64 I (3668451) gsm-ppp: netmask = 255.255.255.255 I (3668501) gsm-ppp: our6_ipaddr = :: I (3668611) netmanager: MODEM up (with WIFI client up): staying with WIFI client priority I (3687471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3697471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3720471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 7 minute(s) remaining) I (3747471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3757471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3780471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 6 minute(s) remaining) I (3807471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3817471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3840471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 5 minute(s) remaining) I (3867471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3877471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3900471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 4 minute(s) remaining) I (3900541) housekeeping: 2019-07-30 20:02:06 GMT (RAM: 8b=113788-127084 32b=10312) I (3927471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3937471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (3944471) ovms-server-v2: Send MP-0 S57.0,M,244,12,charging,range,163,151,12,56,0,300,5,1,3,0,0,0,178.49,820,0,0,0,0,0,0,0,0,0,0,0,-2.32,0.00,79 I (3944531) ovms-server-v2: Send MP-0 D92,0,5,36,50,30,466,559124,0,3944,25,2,1,1,12.79,0,12.6,0,36,0,0 I (3944601) ovms-server-v2: Send MP-0 L37.346325,-122.037338,336,55,1,1,0,0,2.3,0,0 I (3944661) ovms-server-v2: Send MP-0 F3.2.001-18-gac0ae29b-dirty/ota_1/main (build idf v3.1-dev-2835-g151269458-dirty May 23 2019 17:16:23),5YJRE11B181000033,25,1,TR1N,Revelstoke I (3960471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 3 minute(s) remaining) I (3987471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (3997471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (4020471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 2 minute(s) remaining) I (4047471) v-teslaroadster: Cooldown: Cycle 2 PERFORMANCE mode I (4057471) v-teslaroadster: Cooldown: Cycle 2 RANGE mode I (4080471) v-teslaroadster: Cooldown: 2 cycles 30C/25C 12A (with 1 minute(s) remaining) I (4080521) v-teslaroadster: Cooldown: Cycle 2 cooldown completed I (4080701) ovms-server-v2: Send MP-0 PARange - Charge Stopped|SOC: 57.0%|Ideal range: 163M|Est. range: 151M|ODO: 55912.4M|CAC: 178.5Ah|SOH: 80% I (4126971) ovms-server-v2: Incoming Msg: MP-0 Z1 I (4127031) ovms-server-v2: One or more peers have connected I (4127471) ovms-server-v2: Send MP-0 S58.0,M,65535,127,stopped,standard,133,124,32,0,0,300,3,21,0,0,0,0,178.49,812,0,0,0,-1,0,0,0,0,0,0,0,0.00,0.00,79 I (4127541) ovms-server-v2: Send MP-0 D68,0,5,36,51,30,466,559124,0,4127,25,0,1,1,11.47,0,12.6,0,36,0,0 I (4127621) ovms-server-v2: Send MP-0 L37.346321,-122.037346,336,65,1,1,0,0,0.0,0,0 I (4127681) ovms-server-v2: Send MP-0 W0,0,0,0,0,0,0,0,0 I (4127751) ovms-server-v2: Send MP-0 F3.2.001-18-gac0ae29b-dirty/ota_1/main (build idf v3.1-dev-2835-g151269458-dirty May 23 2019 17:16:23),5YJRE11B181000033,25,1,TR1N,Revelstoke I (4142331) ovms-server-v2: Incoming Msg: MP-0 Z0 I (4200481) housekeeping: 2019-07-30 20:07:06 GMT (RAM: 8b=113788-127248 32b=10312) I (4420551) ovms-server-v2: Incoming Msg: MP-0 Z1 I (4420601) ovms-server-v2: One or more peers have connected I (4421471) ovms-server-v2: Send MP-0 S58.0,M,1,0,stopped,standard,133,124,32,0,0,300,2,21,0,0,0,0,178.49,812,0,0,0,0,0,0,0,0,0,0,0,0.00,0.00,79 I (4421531) ovms-server-v2: Send MP-0 D76,0,5,34,49,30,466,559124,0,4421,25,2,1,1,12.94,0,12.6,0,34,0,0 I (4421591) ovms-server-v2: Send MP-0 L37.346359,-122.037308,336,65,1,1,0,0,0.4,0,0 I (4421661) ovms-server-v2: Send MP-0 W0,0,0,0,0,0,0,0,0 I (4421721) ovms-server-v2: Send MP-0 F3.2.001-18-gac0ae29b-dirty/ota_1/main (build idf v3.1-dev-2835-g151269458-dirty May 23 2019 17:16:23),5YJRE11B181000033,25,1,TR1N,Revelstoke I (4424641) ovms-server-v2: Incoming Msg: MP-0 Z0 OVMS# log close Closed log file I (4491401) command: SetLogfile: file logging stopped I (4500481) housekeeping: 2019-07-30 20:12:06 GMT (RAM: 8b=113788-127496 32b=10312) OVMS# exit

2 4

JTAG debugging
by Marko Juhanne 03 Aug '19

03 Aug '19

Hi, has anyone tried JTAG debugging with OVMS? Mainly interested in having settable breakpoints (a feature which doesn't seem to be possible with UART gdb stub in ESP32, but seems to work with ESP8266. See https://visualgdb.com/tutorials/esp8266/gdbstub/ ). There's no JTAG header on OVMS, but I'm willing to solder a JTAG connector directly to ESP32 pins. But those pins are already connected to the SD-card reader.. Is not having a sd-card in the slot enough, or does the initialization mess with the debugger connection, thus needing to disable the sd card module on firmware? Or do I have to desolder the reader? (last resort) Br, Marko

2 1

Crashes while flashing
by Craig Leres 30 Jul '19

30 Jul '19

I think there might be a new problem with the code. The most common way for me to load new firmware is via the "Flash from web" from my system at home. Several times this weekend I've gotten "Request error, please retry" when starting the flash. Just now I got one half way through the flash. I haven't been able to get a useful stack trace because my build/ovms3.elf has already been overwritten with a new image when this happens and xtensa-esp32-elf-addr2line just prints a bunch of "??:0" lines. I've had this multiple times on two different modules today and so far 3 times in a row. I finally resorted to booting from the factory partition (which I try to keep loaded with the current public release). That resulted in it completely losing its config and firing up the OVMS ssid instead of joining my network. I've attached some frame grabs. Craig

3 3

New can logging
by Michael Balzer 29 Jul '19

29 Jul '19

Mark, is there a bug in the new can monitoring or am I doing something wrong? monitor mode: OVMS# can log start monitor crtd CAN logging to MONITOR active: Type:monitor Format:crtd Filter:off Vehicle:RT Note: info logging is at debug log level, frame logging is at verbose, and errors as usual I (83919) canlog-monitor: Now logging CAN messages to monitor D (83919) canlog-monitor: 1564312407.926444 CXX OVMS CRTD OVMS# can can1 tx standard 080 010203 ets Jun 8 2016 00:22:57 rst:0x8 (TG1WDT_SYS_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0018,len:4 load:0x3fff001c,len:4952 load:0x40078000,len:7416 load:0x40080000,len:8344 entry 0x4008037c W (86) boot: PRO CPU has been reset by WDT. W (86) boot: WDT reset info: PRO CPU PC=0x4008aab8 W (86) boot: WDT reset info: APP CPU PC=0x4009621a vfs mode: OVMS# can log start vfs crtd /sd/logs/can.crtd ets Jun 8 2016 00:22:57 rst:0x8 (TG1WDT_SYS_RESET),boot:0x3b (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0018,len:4 load:0x3fff001c,len:4952 load:0x40078000,len:7416 load:0x40080000,len:8344 entry 0x4008037c W (86) boot: PRO CPU has been reset by WDT. W (86) boot: WDT reset info: PRO CPU PC=0x4008aab8 W (86) boot: WDT reset info: APP CPU PC=0x400838cc Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

3 5

Can message flow reproduce
by Tamás Kovács 28 Jul '19

28 Jul '19

hi, Now i get a Lexia for Peugeot iOn and I get some useful data on can network, such as SOH and another metrics. if Lexia connected and I create a OVMS can log. I see the following data: 167913.526 1R11 761 2 21 1 FF FF FF FF FF 167913.536 1R11 762 10 2E 61 1 90 8F 1 79 167913.546 1R11 761 30 8 0A FF FF FF FF FF 167913.576 1R11 762 22 0A 4C 3 1 5E 1 5D 167913.596 1R11 762 23 1 2C 0 FA 0 FB 0 167913.606 1R11 762 24 0F 0F 1 5A 0 E8 A5 167913.636 1R11 762 26 64 0 0 0 0 0 0 167914.026 1R11 762 24 0F 0F 1 5A 0 E8 A5 167914.046 1R11 762 25 FE 0 0 1 78 75 7B 167914.056 1R11 762 26 64 0 0 0 0 0 0 167914.436 1R11 761 30 8 0A FF FF FF FF FF 167914.446 1R11 762 21 0 1 78 33 0D B3 4E 167914.476 1R11 762 23 1 2C 0 F9 0 FB 0 167914.496 1R11 762 24 0F 0F 1 5A 0 E8 A5 167914.876 1R11 761 2 21 1 FF FF FF FF FF 167914.876 1R11 762 10 2E 61 1 90 8F 1 79 167914.896 1R11 761 30 8 0A FF FF FF FF FF 167914.906 1R11 762 21 0 1 79 0 0D B3 4E 167914.926 1R11 762 22 0A 4C 3 1 5E 1 5D 167914.966 1R11 762 25 FE 0 0 1 79 75 7B 167914.986 1R11 762 26 64 0 0 0 0 0 0 167915.316 1R11 761 2 21 1 FF FF FF FF FF I searching on google and find the following things the Mitsubishi Outlander PHEV ( http://www.myoutlanderphev.com/forum/viewtopic.php?f=10&t=1796) use the same PID-s. And many more useable metrics if I can resolve this communication with ECU-s

1 1

esp-idf v3.3
by Michael Balzer 27 Jul '19

27 Jul '19

FYI: I've merged the current v3.3 status and am now running the new build (toolchain still 1.22.0-93-gf6c4cdf) on my modules. I though it would be easier to merge v3.2 first, but that didn't work out. The current v3.2 status seems to have a bug, it wouldn't link due to too many segments. The segments have been introduced by a wifi blob update to support a new wifi IRAM optimization, but that needs a linker script & esptool update as well, that seems to be available only in the v3.3 branch. So I merged v3.3 directly afterwards, and that builds without issues. So far I haven't noticed any relevant problems running the new build. On stopping the wifi module, two event errors get logged, and the AP network interface remains configured as up: OVMS# wifi mode off Stopping wifi station... I (1307252) esp32wifi: Stopping WIFI station I (1307252) netmanager: Interface priority is pp3 (10.170.195.13/255.255.255.255 gateway 10.64.64.64) I (1307252) netmanager: Set DNS#2 0.0.0.0 I (1307252) netmanager: WIFI client down (with MODEM up): reconfigured for MODEM priority I (1307252) wifi: state: run -> init (0) I (1307262) wifi: pm stop, total sleep time: 1100678913 us / 1301859253 us I (1307262) wifi: new:<1,0>, old:<1,1>, ap:<1,1>, sta:<1,0>, prof:1 E (1307262) event: system_event_sta_disconnected_handle_default 294 esp_wifi_internal_reg_rxcb ret=0x3014 E (1307262) event: system_event_ap_stop_handle_default 223 esp_wifi_internal_reg_rxcb ret=0x3014 W (1307262) netmanager: CleanupConnections: can't get AP station list I (1307272) wifi: flush txq I (1307272) wifi: stop sw txq I (1307272) wifi: lmac stop hw txq I (1307292) time: Network was reconfigured: restarting SNTP client I (1307322) netmanager: Set DNS#2 0.0.0.0 I (1307322) esp32wifi: STA disconnected with reason 8 I (1307352) netmanager: Set DNS#2 0.0.0.0 I (1307392) netmanager: Set DNS#2 0.0.0.0 I (1307392) netmanager: WIFI access point is down I (1307392) esp32wifi: AP stopped OVMS# net status Interface#3: pp3 (ifup=1 linkup=1) IPv4: 10.170.195.13/255.255.255.255 gateway 10.64.64.64 Interface#2: ap2 (ifup=1 linkup=1) IPv4: 192.168.4.1/255.255.255.0 gateway 192.168.4.1 DNS: 192.168.2.1 192.168.2.1 Default Interface: pp3 (10.170.195.13/255.255.255.255 gateway 10.64.64.64) OVMS# But wifi is off, and after starting the wifi network again, everything works, so that's a minor issue. I'll do some more tests tomorrow, then push the update. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

4 15