February 2019 - OvmsDev - Open Vehicles

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

BUG? in v3.2.0-1 in vehicle_mitsubishi - flood of BMS-error msg
by Michael Eric Menk 11 Jul '19

11 Jul '19

There is a bug in MIEV code, that bombs the web GUI and phone APP with BMS errors. I suspect that this is because the Peugeot and Citroen branded MIEVs have a 80 cell battery pack vs MIEVs 88cells. Sample of a message: > Voltage: SD=1mV OK > Temperature: SD=1.4C !6:+3.1C !16:+3.1C !18:+3.1C The missing cells could also be used to set the voltage gauge. There are two LEV50-4 missing in the 80 cell pack, number 06 and 12. If a flagg is set while looping the CAN massages, then the flag can be used inside OvmsVehicleMitsubishi::GetDashboardConfig to set correct voltage. The float charge voltage of the 80 cell pack is 328.4 volt

3 15

3G network
by Stein Arne Sordal 02 Jul '19

02 Jul '19

Hi I guess this question is basically for Mark, In Norway the telecom providers have decided to turn off almost all of the 3G network soon and focus on 4G only. Any plan for 4G modem? Kind regards, Stein Arne Sordal

6 12

Can buses stop after some time
by Tom Parker 01 Jun '19

01 Jun '19

Hi all, I synced up with master about a week ago and since then I've seen both can busses stop working. I still see the 12v battery metric changing, but everything that comes from the car stops. Rebooting the module with "module reset" does not seem to fix it, while make app-flash monitor does fix it. I haven't tried make monitor on it's own. Is anyone else seeing behavior like this? Sorry for the vague bug report. I'll spend some time later this weekend to try to gather more information.

7 45

Garbage in /store
by Stephen Casner 27 May '19

27 May '19

When I do "vfs ls /store" I get 128 lines like the following: -2146205 01-Jan-1970 00:00 ????????.??? After that comes valid content: [DIR] 01-Jan-1980 00:00 ovms_config/ 83 01-Jan-1980 00:00 .htpasswd The config facility appears to be intact. Does the garbage indicate that the /store filesystem is scrogged and needs to be rebuilt? -- Steve

3 11

Android App v3.12.2 in Play Store
by Michael Balzer 07 Apr '19

07 Apr '19

Whoa. Our first public App update since …drumroll… June 2014 :) I didn't get any bug reports for my 3.12.2 beta release, so I just finished some last details and uploaded it. May take some hours to appear in the Play Store. As change history has grown a bit beyond the allowed 500 chars for the release info, I've added a history page to the Wiki: https://github.com/openvehicles/Open-Vehicle-Android/wiki/History I'm afraid it's just the condensed gitlog though. I hope users won't get confused, sure could need some refinement. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

10 47

Callout for JDM Nissan Leaf VINs
by Anko Hanse 03 Mar '19

03 Mar '19

This is related to feature requests #180 and #181 (automatic detection of model-year and battery size). For USA and EU style VINs we might have a method of deriving the year and battery size. Unfortunately cars made for the Japanese Domestic Market and frequently imported 2nd hand into Australia and New Zealand do not use a VIN but instead have some sort of serial number in the form of ZE0-123456 or AZE0-123456. I have posted a request on a NZ forum (www.geekzone.co.nz<http://www.geekzone.co.nz/>) for people to email me their JDM style VIN combined with year (and possibly month) and battery size. Note that LeafSpy-Pro also toggles with another VIN-like number, I'm interested in that too if people can get it. If not then just the ZE0- or AZE0- number is fine... Possibly any NZ OVMS users seeing this post can do the same and also email me those details or reply here. For privacy reasons I would suggest to mask the lowest digits of your VINs, i.e: AZE0-2003xx, Dec 2015, 30kwh, 230JT11122000xxx Hopefully that will give us some new insights... I very much hope our collective powers can confirm that ZE0-1xxxxx and AZE0-1xxxxx is 24kwh, AZE0-2xxxxx is 30kwh, AZE1-1xxxxx is 40kwh and possibly AZE1-2xxxxx will be 62kwh :-)

3 14

Power states clarification
by Greg D. 02 Mar '19

02 Mar '19

Hi folks (mostly Mark, probably), I just noticed that there is a power command for OBD2ECU as well as ext12v. I understand (or thought I did) what controlling the ext12v power does, but how is "power" related to OBD2ECU? Is this related to firing up the opened CAN bus, or is there some tie to the ext12v power? I have manually created scripts for vehicle.on and vehicle.off to explicitly control ext12v, so that an attached HUD will follow the key. We talked about having this sort of thing done automatically, but I didn't think it was ever implemented, nor what the particulars would be regarding some of the device corner cases. Is that what is happening here? Related, what do the other states do? (Sleep, deepsleep, etc.) Thanks, Greg

3 3

RETOOLS web
by Mark Webb-Johnson 25 Feb '19

25 Feb '19

Michael, this is probably for you - but if anybody else can help please do… I am trying to see how hard it would be to do a web based interface to the RETOOLS system. Presumably this would appear in the menu as Tools / Reverse Engineering (or some such abbreviation if that is too long). The basic screen would look something like this: +----------------------------------------------------------------------------------------------------+ | | | +----------+ +------+-------+------------------------------------+------+ +--------------------+ | | | | | hdr1 | hdr2 | hdr3 | hdr4 | | | | | | | +------+-------+------------------------------------+------+ | | | | | Controls | | | | | | | Info | | | | | | col1 | col2 | col3 | col4 | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +----------+ | | | | | +--------------------+ | | | | | | | | | +----------+ | | | | | +--------------------+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Status | | | | | | | | | | | | | | | TABLE | | | | | | | | | | | | | | Extra | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +----------+ | | | | | +--------------------+ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | +------+-------+------------------------------------+------+ | | | +----------------------------------------------------------------------------------------------------+ The controls are just a set of controls - things that bring up dialogs for more information or perform actions. Like start/stop RE, switch modes, manipulate DBC files, etc. Left justified in the frame, and perhaps 10% of the width. Height can dynamically adjust with the text content. The Status, Info, and Extra panes are just a dynamically updated text panes. Main code needs to be able to send text here and have it shown in the appropriate pane. Right justified in the frame and perhaps 30% of the width. Height can dynamically adjust with the text content. The TABLE is a table. Probably 5 columns by many rows (anywhere from 20 to 200 or so). Either paged, scrolling, or just very tall. Paged is probably preferable. Would need a simple mechanism to dynamically add/update a row (identified by ‘key’ column and in sorted order), presumably using the web socket. Also need something to be able to dynamically clear the entire table. The RETOOLS code would use this to update the table in realtime (presumably over a web socket). It would be good if the table could do things like search filtering of displayed rows, column sorting, etc (all client side - something like datatables.net) For example, look at this output: OVMS# re dbc list key records ms last can1/100:0081 2 22000 01 02 03 04 05 | ..... can1/101 1 44000 01 02 03 04 | .... dbc/DI_Signal1: 129 km dbc/DI_Signal2: 1 km dbc/DI_Signal3: 130 kWh dbc/DI_Signal4: 122 Degrees The idea is to be able to show the key, records, ms, last, and ascii dump in the main table. Then, clicking on a row would show the statistics for that message in the Info pane, and DBC signals in the Extra pane. I can handle the RETOOLS side, but the javascript is beyond me. I also had a look at the ovms web server framework, but it doesn’t seem to be able to do the table part (yet)? Any idea how complex this is? Regards, Mark.

4 11

Leaf charge time estimates
by Robin O'Leary 24 Feb '19

24 Feb '19

https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/207 This adds support for 6 metrics ("xnl.v.c.duration....") reporting the Leaf BMS's time estimates in minutes for various hypothetical charging conditions: * to 100% charge (".full") * to 80% charge (".range") * with power ~1.6kW (".l0") * with power ~3.3kW (".l1") * with power ~6.7kW (".l2") I find them useful, although they don't seem to fit in the existing OVMS charge reporting framework, which expects an on-going charge before it calculates any estimate. They may also help us reverse-engineer whether the BMS expects temperature, cell state, tapering near full, etc. to affect the duration, if we want to make our own time estimation algotithm, On my Leaf (which has the 6.6kW charger), the dash display normally shows two charge time estimates: at 3.3kW power ("xnl.v.c.duration.full.l1") and at 6.6kW power ("xnl.v.c.duration.full.l2"). My model has the option for "Long life battery mode"; when this is enabled, it instead shows the values to 80% ("xnl.v.c.duration.range.l1", "xnl.v.c.duration.range.l2").

2 1