December 2017 - OvmsDev - Open Vehicles

ppp problem on disconnect
by Michael Balzer 11 Dec '17

11 Dec '17

Just had this after letting the module idle for a while: … I (11249582) simcom: CREG Network Registration: RegisteredRoaming I (11253822) ovms-server-v2: Send MP-0 D0,0,5,0,0,-40,0,0,0,11251,0,0,1,0,0.373626,0,0,0,0,0 I (11273832) ovms-server-v2: Send MP-0 D0,0,5,0,0,-40,0,0,0,11271,0,0,1,0,0.401099,0,0,0,0,0 I (11279582) simcom: CREG Network Registration: RegisteredRoaming I (11282842) ovms-server-v2: Send MP-0 D0,0,5,0,0,-40,0,0,0,11280,0,0,1,0,0.362637,0,0,0,0,0 I (11286902) simcom: PPP Connection disconnected I (11286902) simcom: PPP Connection disconnected I (11287562) simcom: Lost network connection (+PPP disconnect in NetMode) I (11287562) gsm-ppp: Shutting down (hard)... I (11287562) simcom: State: Enter NetStart state I (11287562) gsm-nmea: Startup I (11292662) gsm-ppp: StatusCallBack: User Interrupt E (11292662) gsm-ppp: status_cb: User interrupt| I (11292662) gsm-ppp: Shutdown (via status callback) I (11292662) events: Signal(system.modem.down) I (11292662) events: Signal(network.modem.down) I (11292852) ovms-server-v2: Send MP-0 D0,0,5,0,0,-40,0,0,0,11290,0,0,1,0,0.417582,0,0,0,0,0 I (11292902) simcom: PPP Connection disconnected I (11292902) simcom: PPP Connection disconnected I (11292902) simcom: PPP Connection disconnected I (11299592) simcom: PPP Connection is ready to start I (11300562) simcom: State: Enter NetMode state I (11300562) gsm-ppp: Initialising... OVMS > Task watchdog got triggered. The following tasks did not feed the watchdog in time: - IDLE (CPU 0) Tasks currently running: CPU 0: tiT CPU 1: ipc1 Task watchdog got triggered. The following tasks did not feed the watchdog in time: - IDLE (CPU 0) Tasks currently running: CPU 0: tiT CPU 1: ipc1 Task watchdog got triggered. The following tasks did not feed the watchdog in time: - IDLE (CPU 0) Tasks currently running: CPU 0: tiT CPU 1: ipc1 … … and so on, no more input reaction from the shell here, had to do a reset. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

4 8

scp is implemented
by Stephen Casner 10 Dec '17

10 Dec '17

I have extended the SSH server in console_ssh to support SSH session type "exec" in addition to the original "shell" session type. This allows the client ssh command to be followed by a command to the executed on OVMS: auge1221> ssh ovms vfs ls /store ovms_config scripts events testdir auge1222> It also allows use of the client's scp command to transfer files to or from OVMS. The clients scp command starts an ssh session and passes along an scp command to be executed on the server's end. On a Unix-like system the server would execute the scp command as a separate process, but on OVMS I have implemented the scp protocol within console_ssh. So, for example, I can use scp to fetch my startup script so I can edit it to remove the extra command I added to set the logging level for ssh while I was debugging and then write back the updated script: auge1224> scp -r ovms:/store/events . startmeup 100% 72 0.1KB/s 00:00 auge1225> scp events/system.start/startmeup ovms:/store/events/system.start/ startmeup 100% 56 0.1KB/s 00:00 auge1226> In these examples you see that I am using public key authentication so I don't have to enter a password. Secure and very convenient! The SSH implementation is a bit slow doing the public key calculations so there is a pause of a few seconds as each command begins, but then the files are transmitted expediously. I have not attempted yet to do tuning of build options for wolfssh for speed and memory usage. I have also not figured out yet how to perform the rekeying procedure with this wolfssh library. Because the rekeying is not implemented properly some data may be lost when it occurs. However, rekeying will be triggered after about 1GB of data transfer, so it seems unlikely that we will hit that trigger right away. For those who have been wondering when this would be completed, sorry for the delay. The scp protocol is somewhat crude and there is no document to specify it which meant I had to do experiments to figure out the right actions at each step. Finally I found the OpenSSH implementation on github so I could RTSL. After that testing all the corner cases took a while. I'm sure you all will let me know if you find problems! -- Steve

2 3

Fix to esp-idf for adjusting logging levels
by Stephen Casner 10 Dec '17

10 Dec '17

If you have observed that sometimes when you try to adjust logging levels using the OVMS command "level" that the change is not effective, the explanation is that the logging code in esp-idf uses a cache to speed the level lookup but the call to set the level did not update the cache. I've fixed that in openvehicles/esp-idf just now. -- Steve

1 0

Notifications concept draft
by Michael Balzer 10 Dec '17

10 Dec '17

Some thoughts about how to implement vehicle notifications and data logging. Please check & comment. Concept: - handle all unsolicited transmissions from vehicles by commands - vehicle module signals event if a transmission is due - … with event data = command line to generate output - listeners retrieve the transmission content by executing the command - queueing for async delivery is done by the listeners (i.e. through BufferedShell) → any shell command can be used for transmissions → all transmissions can also be generated on the shell / by script → all transmission output can be sent to any channel → data logging on SD can be done transparently by the system Interactive consoles can output unsolicited transmissions by event type according to the current log level. Events: "send.info" → send text notification "send.alert" → send text alert "send.data" → send data record (CSV, content part of v2 MP) Scheme: MyEvents.SignalEvent("send.<type>", "command [args]"); Examples: MyEvents.SignalEvent("send.info", "stat"); MyEvents.SignalEvent("send.alert", "xrt batt status"); MyEvents.SignalEvent("send.data", "xrt log RT-BAT-C"); → command output: H,RT-BAT-C,4,86400,1,1,4025,3675,4045,5,14,14,19,1 Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

5 28

Enclosure for OVMS v3
by Mark Webb-Johnson 04 Dec '17

04 Dec '17

Injection moulding samples are in. Clean and simple. And oh so black. Regards, Mark

3 6

Tracking lists
by mr23＠comcast.net 04 Dec '17

04 Dec '17

Are there any lists of issues/actions/milestones remaining before- approving the factory to begin more/volume production- per car model issues ? Looking forward to being able to order hw for a LEAF, and integrate OVMS ! -Chris

2 1

Problems ms_v_charge_mode
by Geir Øyvind Vælidalo 03 Dec '17

03 Dec '17

I’m having problems setting ms_v_charge_mode. I do it this way, but it fails at runtime: StdMetrics.ms_v_charge_mode->SetValue( chademo ? "performance" : "standard"); This is the trace I get, so it seems to fail somewhere else: I (6451) events: Signal(vehicle.charge.mGuru Meditation Error of type LoadProhibited occurred on core 0. Exception was unhandled. Register dump: PC : 0x400883c3 PS : 0x00060633 A0 : 0x8008708a A1 : 0x3ffc6b30 0x400883c3: vListInsertEnd at /Users/goev/esp/esp-idf/components/freertos/./list.c:130 A2 : 0x3ffc6384 A3 : 0x3ffc6c78 A4 : 0x00060620 A5 : 0x00000000 A6 : 0x00000000 A7 : 0x00000000 A8 : 0x00000038 A9 : 0x3ffb33b8 A10 : 0x3ffb131c A11 : 0x00060623 A12 : 0x00060623 A13 : 0x3ffce1ec A14 : 0x3ffce1ec A15 : 0x3ffc6a70 SAR : 0x00000010 EXCCAUSE: 0x0000001c EXCVADDR: 0x00000040 LBEG : 0x400014fd LEND : 0x4000150d LCOUNT : 0xfffffffa Backtrace: 0x400883c3:0x3ffc6b30 0x40087087:0x3ffc6b50 0x400860f1:0x3ffc6b70 0x4008771b:0x3ffc6b90 0x40087818:0x3ffc6bc0 0x400883c3: vListInsertEnd at /Users/goev/esp/esp-idf/components/freertos/./list.c:130 0x40087087: vTaskPlaceOnEventListRestricted at /Users/goev/esp/esp-idf/components/freertos/./tasks.c:4446 0x400860f1: vQueueWaitForMessageRestricted at /Users/goev/esp/esp-idf/components/freertos/./queue.c:2392 0x4008771b: prvProcessTimerOrBlockTask at /Users/goev/esp/esp-idf/components/freertos/./timers.c:839 0x40087818: prvTimerTask at /Users/goev/esp/esp-idf/components/freertos/./timers.c:839 It looks like it has something to do with the Signal event, but I ‘m still not that good using gbd to find out what actually makes this fail. Any one got a clue? Regards, Geir

3 7

Leaf Updates
by Tom Parker 02 Dec '17

02 Dec '17

Hi, I ported over support for Gen 2 Chargers and polling for the battery Ah capacity and the "Hx" value in https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/9 3 Questions: In v2 we checked whether transmit mode was enabled, I'm not seeing similar logic in the Telsa Roadster module. I've commented out the checks in the leaf code for the time being. In v2 I abstracted the hardware interactions necesary to write to the canbus into a function void vehicle_nissanleaf_send_can_message(short id, unsigned char length, unsigned char *data). In v3 we call canbus::Write(const CAN_frame_t* p_frame). Do we want to add a similar simpler "send to this buffer with this can id" method to the canbus object? The Leaf doesn't use any of the extended can features so a simple interface for the simple case seems to make sense. For the moment I've implemented it within the leaf codebase, see void OvmsVehicleNissanLeaf::SendCanMessage(uint16_t id, uint8_t length, uint8_t *data) in the pull request. I've also porting over the remote command features, I like the interface presented to the car modules to implement these. I need to wait until tomorrow to test these on a real car so haven't sent a pull request yet. I'm very close to finished on porting the leaf support!

2 4

Fwd: Fiat 500e Support?
by Mark Webb-Johnson 01 Dec '17

01 Dec '17

Anybody using Fiat 500e, or interested? I can’t find much online. This might be a good test case for what we can do with RE-TOOLS on OVMS v3. Regards, Mark > Begin forwarded message: > > Subject: Fiat 500e Support? > Date: 30 November 2017 at 11:24:52 PM HKT > To: support(a)openvehicles.com > > Hello > > I'm curious if there is any plan for OVMS to support the Fiat 500e? The Fiat factory telematics system deactivates 3 years from the original vehicle sale and is non renewable, so another solution would be ideal. > > I have a 2013 500e with deactivated telematics, and our roommate has a 2014 with working telematics. If any data could be captured from the car with working telematics (branded as Fiat Access) to assist integrating OVMS I'd love to help. > > The Fiat Access telematics provides vehicle location, battery level, tire pressure, setting the charge schedules, locking / unlocking the car, and starting the climate control.

1 0