January 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

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

Collecting information on the Fiat 500e
by Jason Perkins 14 Feb '19

14 Feb '19

OVMS team, As an owner of a Fiat 500e I was very interested when I stumbled across this project on the TMC forums. The Fiat factory telematics system deactivates 3 years from the original vehicle sale and is non renewable. I think FCA wants to kill the whole system at this point (it's been replaced with the corporate UConnect system) 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. I believe the actual control unit was adapted from some kind of remote-disablement system used in europe (the Fiat literature calls this the Vehicle Tracking Module). The Fiat has a normal J1962 plug, but does not have OBDII protocol support. Like the Kia Soul the powertrain CAN on pin 6 / 14 and the body CAN on 1 / 9. There's no telling how long the telematics will keep working on our roommates '14, so doing a capture sooner than later would be good. I'm open to any suggestions on how best to do this. The car related diag tools I have on hand are: ELM327 Bluetooth, Ross-Tech VCDS (For VW / Audi Products), and AlfaOBD (which can talk to most of the modules in the 500e - but not the VTM :( ), and an adapter to swap the CAN wires so a standard interface can get to the Body CAN. Thanks! -J

5 28

OVMS v3 v3.2.001 Over-the-Air firmware update
by Mark Webb-Johnson 04 Feb '19

04 Feb '19

https://www.openvehicles.com/node/2123 <https://www.openvehicles.com/node/2123> Today, we are pleased to release v3.2.0-1 to Early Access Program (EAP) participants. This is the first public v3.2 version, and introduces an entirely new scripting framework based on an embedded javascript engine. Now, custom javascript modules and functions can be written to respond to system events. In addition, a host of other UI changes enhancements have been made. A summary of the major changes is here: 2019-01-19 MWJ 3.2.001 OTA release - v3.2 first public release - New JavaScript modular framework allowing for dynamic scripting and object model - New vehicle: Smart ED (adaption by Martin Graml ) - Mitsubishi i-MiEV re-write for OVMS v3 - Web UI: text / script editor - Web UI: user plugin support (pages & hooks) - Web UI: night mode by URI parameter, e.g. "…/#/dashboard?nm=1" - Web UI: dashboard accessible w/o login - Web UI: added config backup & restore tool - Web UI: file selector added for firmware flashing from SD - Web UI: text notifications (info/error/alert) displayed as dialogs - Twizy web UI: drivemode buttons secured & added to dashboard - Twizy web UI: added file dialog for virtual dyno recording - Twizy: SEVCON monitoring & recording New commands: xrt mon start [] xrt mon stop xrt mon reset New metrics: xrt.i.* = operational inverter data xrt.s.* = power & torque by speed (virtual dyno) - Twizy: experimental powermap calculation including region 3 / breakdown torque New config: xrt [motor_trq_breakdown] = 0 Breakdown torque in Nm, e.g. 210.375 xrt [motor_rpm_rated] = 0 Rated speed in rpm, e.g. 2100 See docs/Renault-Twizy/Twizy-Powermap-Calculator-Tbrk.ods for details. - Add inactivity watchdog timers to CAN buses - NissanLeaf: Fix for 0% SOH on 30KWh models with Nissan BMS update - Introduction of support for DBC CAN bus configuration files For full detail on all changes, check the GitHub revision history. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. You can choose the release level by setting 'config ota tag edge|eap|main', as one of: edge: Bleeding edge developer nightly-builds eap: Early Access Program (full releases, but with little public testing) main: Publicly tested full releases (the most stable) We expect to release the 3.2.001 firmware to 'main' (all users) after EAP testing (most likely within a week or so). Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project. Open Vehicles

3 7

HUD
by Geir Øyvind Vælidalo 02 Feb '19

02 Feb '19

I’m thinking about maybe buying a HUD to connect to OVMS. Do you have any recommendations? Greg, which one do you have? Best regards, Geir

2 5