August 2020 - OvmsDev - Open Vehicles

3G / 2G fallback on SIM5360 Europe?
by Chris van der Meijden 15 Aug '20

15 Aug '20

Hi all I'm trying to understand some principals of the SIM connection methods of OVMS. Reason is that I recently moved from "the big city" Munich to the very much rural village Thalham. In Thalham we have so called "lite" mobile transmitters. These transmitters are installed, as far as I understood, to safe money and to prepare the transition of the providers to 4g / 5g. They are forcing the frequencies towards the 4g band with those. So these transmitters seem to offer only 2g and 4g, but no more 3g (really ???). I don't have any network connection with the SIM in my OVMS here in Thalham. In the next village Zolling I have connection. In Zolling they don't have the "lite" transmitters, but still have full 3g support. The antenna of my OVMS is working well (-100 dBm to -70 dBm). Now my questions ... Does OVMS have a fallback on SIM5360 Europe to 2g (EDGE) if 3g is not available? I also did some reading in the modem documentation and tried to send some AT commands. Goal is to try to force the SIM into 2g mode. I tried i.e. simcom muxtx 2 AT+COPS? to get some information from the SIM, but I don't get an answer on that command at all. No matter what channel I try. Am I missing something there? Thanx for input. Regards Chris

3 15

dirty mongoose submodule
by Derek Caudwell 15 Aug '20

15 Aug '20

Hi all, I am still struggling to resolve GitHub Desktop reporting the mongoose submodule as "-dirty" which then prevents popping stashed changes. I have tried the git commands below without success and can only assume it is because I am using WSL2 as my build environment. Is anyone else using WSL2, having the same issue? - fetch all submodules (needed if submodules were added in context of a pull) git submodule update --recursive --init - pull all submodules git pull --recurse-submodules git submodule update --recursive --remote - retract all the local changes in all submodules git submodule foreach --recursive git reset --hard - in all submodules, delete all files that are not part of the repository git submodule foreach --recursive git clean -fdx

2 1

Re: [Ovmsdev] V2H mode
by Derek Caudwell 14 Aug '20

14 Aug '20

Hi all, How about the following framework: V2G framework - used to set mode, set current/charge limits and query status with commands such as, V2G mode - used to set mode either V2G, G2V, REM (default - mode remotely set by charger/V2G/V2H unit) V2G limit - used to set limits such as charge/discharge current limit and SOC min/max limits V2G status - used to report mode, limits set and power/current flow V2G start - used to start powerflow in a given mode V2G stop - used to stop powerflow The basic wrappers could be defined in vehicle.h/cpp and the feature confirmed as supported in the specific vehicle and coded to implement the specific command features. Views? Cheers Derek

2 1

Re: [Ovmsdev] Frequent Crashes
by Derek Caudwell 12 Aug '20

12 Aug '20

Hi Michael, The following is the content of my "dummy" script, so it shouldn't cause any looping issues: var history = { "test": [], "v.p.odometer": [], "v.p.altitude": [], "v.b.energy.used": [], "v.b.energy.recd": [], }; var lastOdo = 0; var saveOdo = 0; print(Duktape.enc('jc', history)); I deleted the script and folder before seeing your suggestion on task priority, but I could reinstate and try at some point. Since deleting the script and the events folder the module has been stable for over 10 hours. I see there is garbage collection every 60s which seems to match the crash timings to within a second or so, could this be the cause?? Kind regards Derek

2 3

V2H mode
by Derek Caudwell 12 Aug '20

12 Aug '20

Hi all, I have a V2H unit for the Leaf which I intend to CAN log with a view to being able to start/stop and see powerflow from the car to appliances. Is this best handled by addition of subcommands to charge framework or simply addition of a "V2H" mode to the existing framework, or some other approach? Cheers Derek

3 2

Frequent Crashes
by Derek Caudwell 11 Aug '20

11 Aug '20

Hi all, Firstly, thank you Michael for your patience and help in getting the static ip changes/framework to a point they could be incorporated into the master. With the edge build I appear to be getting frequent crashes, am I correct in interpreting from the crash logs that these are caused by DukTape? I currently have a simple js in /store/events/system.wifi.sta.disconnected/10-test.js to see how js/events engine works. 2020-08-11 22:02:37 NZST I (178142) ovms-server-v2: Send MP-0 h1,-166,*-OVM-DebugCrash,0,2592000,3.2.014-42-g6c884ce/ota_0/edge (build idf v3.3.2-881-g22d636b Aug 10 2020 00:01:35),23,Crash,12,12,23,0,abort(),0,,0x4008e627 0x4008e8c1 0x400e6edc 0x40083f6a ,6,Task watchdog,ticker.1,EventScript,59,OVMS DukTape 2020-08-11 22:07:06 NZST I (21202) ovms-server-v2: Send MP-0 h1,-10,*-OVM-DebugCrash,0,2592000,3.2.014-42-g6c884ce/ota_0/edge (build idf v3.3.2-881-g22d636b Aug 10 2020 00:01:35),25,Crash,12,12,25,0,abort(),0,,0x4008e627 0x4008e8c1 0x400e6edc 0x40083f6a ,6,Task watchdog,ticker.10,EventScript,60,IDLE1|OVMS DukTape Kind regards Derek

2 1

Time for 3.2.014?
by Mark Webb-Johnson 11 Aug '20

11 Aug '20

I would like to build a 3.2.014 for EAP (and after a few days -> MAIN). Any objections? Anything last minute to go in? Once that is out, I can start to bring in my plugin framework extensions (and also changes to command/script for command extensions in javascript) - I think we can call that 3.3.001. Regards, Mark.

3 7

Rolls Royce conversion - Tesla insights?
by Greg D. 09 Aug '20

09 Aug '20

Hi Mark, For entertainment value, if nothing else... This conversion took a Model S and melded it with a classic Rolls Royce, and kept the main Tesla components working. Rather amazing accomplishment. Why I bring this up here is that they made a custom interface board to talk to the Tesla Model S CAN bus, feeding it with information from some decidedly non-Tesla stuff. They say it's been open sourced, so perhaps there might be some clues in there as to additional things one can do with the OVMS Model S integration? https://www.youtube.com/watch?v=5A9xnbcGXso Enjoy, Greg

1 0

OBD2ECU use with latest Roadster cable?
by Greg D. 06 Aug '20

06 Aug '20

Hi Mark, So, following the "OVMS issue: obdii on can3 crashes VMS" thread on TMC led me to an "oops!", I think... Did I miss something? With the updated OVMS cable to the Diag port on the Roadster, the report is that all 3 CAN busses are connected to the car. If so, doesn't that make the obd2ecu process impossible to run, since there's no CAN bus available on the 26 pin port to connect a HUD to? And, if one were to hook up a HUD to the 26 pin port, wouldn't its polls be sent on (at 500 kb/s) through the OVMS wiring to the car, confusing the car? Is the older (single CAN bus) cable still available? That, I would think, would fix the problem. I have the original cable, so haven't noticed anything wrong. The OP on that thread also claimed the original cable, which doesn't make sense. Where is the Oops? Greg

2 6

App notification help
by Derek Caudwell 06 Aug '20

06 Aug '20

Any help appreciated to understand why App alerts are being sent with different information to that in the MP-0 message. I assume it is being triggered earlier and then delayed for some reason? 2020-08-05 18:25:08 NZST I (325841) ovms-server-v3: Tx event vehicle.charge.start 2020-08-05 18:25:08 NZST I (325861) ovms-server-v3: Tx event vehicle.charge.state 2020-08-05 18:25:08 NZST I (325891) ovms-server-v3: Tx event vehicle.charge.mode 2020-08-05 18:25:08 NZST I (326031) webserver: HTTP POST /api/execute 2020-08-05 18:25:08 NZST I (326051) webserver: HTTP POST /api/execute 2020-08-05 18:25:08 NZST I (326071) webserver: HTTP POST /api/execute 2020-08-05 18:25:08 NZST I (326091) webcommand: HttpCommandStream[0x3f89a4bc]: 3601112 bytes free, executing: stat*2020-08-05 18:25:08 NZST I (326101) ovms-server-v2: Send MP-0 S62.0,K,371,0,charging,standard,132,101,16,1,0,0,3,1,0,0,0,0,65.44,0,0,0,80,-1,0,0,0,0,0,164,0,-0.51,511.50,82* 2020-08-05 18:25:08 NZST I (326131) ovms-server-v2: Send MP-0 D80,8,4,12.5,0,16,0,447560,0,325,12.5,1,1,1,12.17,0,12.5,0,0,0,16 2020-08-05 18:25:08 NZST I (326091) webcommand: HttpCommandStream[0x3f895bf4]: 3598540 bytes free, executing: stat 2020-08-05 18:25:08 NZST I (326091) webcommand: HttpCommandStream[0x3f89a3f4]: 3600896 bytes free, executing: stat*2020-08-05 18:25:10 NZST I (328121) ovms-server-v2: Send MP-0 PINot charging|SOC: 62.0%|Ideal range: 132km|Est. range: 102km|ODO: 44756.0km|CAC: 65.4Ah|SOH: 82%* 2020-08-05 18:25:10 NZST I (328131) ovms-server-v3: Tx notify ovms/nismo/notify/info/charge.started=Not charging|SOC: 62.0%|Ideal range: 132km|Est. range: 102km|ODO: 44756.0km|CAC: 65.4Ah|SOH: 82% 2020-08-05 18:25:10 NZST I (328191) ovms-server-v3: Tx event notify.info.charge.started 2020-08-05 18:25:11 NZST I (328301) ovms-server-v3: Message publishing acknowledged (msg_id: 216) 2020-08-05 18:25:11 NZST I (329151) ovms-server-v3: Tx event vehicle.charge.pilot.on 2020-08-05 18:25:11 NZST I (329171) ovms-server-v3: Tx event vehicle.charge.prepare

2 1