November 2018 - 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

3G network
by Stein Arne Sordal 03 Jul '19

03 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 02 Jun '19

02 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

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 15 Feb '19

15 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

How can I help
by Robert Sharpe (Electric Vehicle Consultant) 26 Jan '19

26 Jan '19

Hi All, I like where OVMS project is going and would like to help if I can. Where I can possibly add value is make things easy for people to use (eg documentation, etc) experienced on UI/UX design, etc. as an ex developer, good at testing and finding problems. Some initial thoughts on activities are to make it easier for non technical people to use OVMS, help doc author pull out user only specific content to a user manual and make it non-technical (renaming current user manual to developers manual) to help people see roadmap, provide a mechanism to see who wants what and who is working on it. to allow developers and users to display problems with their vehicle only, add Labels to the github issues list or group by project (I am not an expert on GITHUB so please be patient) update GITHUB readmes to better direct people that find GITHUB first. Please let me know if anyone is dealing with any of these areas add and/or vote for what things you think I can help with by putting a comment next to the activity above. Regards, Robert Sharpe Electric Vehicle Consultant 07711 252971 Your Plugged-in Partner Evergreen Consulting is the trading name of Sharpe Consultants Ltd

5 18

Attention: esp-idf upgrade still breaks configuration
by Michael Balzer 25 Jan '19

25 Jan '19

See https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/165 I'll reset both master branches now. If you're about to pull, please wait until I've reverted the branches. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

3 18

Poor wifi performance
by Stephen Casner 09 Jan '19

09 Jan '19

I find the wifi performance of OVMS v3 to be poor, and I'm wondering how it might be improved. I have a mix of thoughts here. For both my own unit and that of Timothy Rodgers, wifi reception in our garages was unusable. You can blame that on too much distance from the access point, but my iPhone and MacBook both access the wifi just fine from my garage. The wifi antenna in the OVMS is probably smaller and its location within the metal framework around the car's firewall may impede radio transmission. Perhaps it would be feasible to switch to an ESP32-WROVER-I with an external antenna to improve performance, but that would be a big deal. If there is a transmit power adjustment, perhaps that could be increased? When Timothy parks his car next to his house, which is about 50 feet closer than the garage, then the wifi reception was good enough for the update to 3.1.008 to succeed. But when he tries to connect with the browser, page updates often time out, so it is close to unusable. Perhaps we could improve usability by increasing the timeout in our javascript to allow more time for TCP to retransmit? For my own unit, I switched from AP+client to just client mode and at first it seemed that had improved the client performance. But still the next day I had no access from the iPhone app. When I connected to the console to find out why I saw that server v2 was repeatedly trying to connect and failing. I'm presuming that the cause was poor wifi connectivity since I was also not able to reach the web server on the client address, although I have not proven that. But since the client wifi was associated with the home AP and had an address, the OVMS network routing preferred the wifi and did not try to use the modem. For now I have resorted to turning off wifi. I suggest that the network routing algorithm be enhanced to back off to use the modem if some number of attempts to connect to the server over wifi have failed. The iPhone will do this for itself (there is a setting to enable this called Wi-Fi Assist). The behavior of repeated connection attempts and failures by server v2 seems to induce a more serious failure after a while, perhaps due to some resource starvation. At that point there is a failure message "mg_connect(api.openvehicles.com:6867) failed: cannot parse address" every time server v2 tries to connect. I expect that is a bug that could be fixed. Lastly, since we may encounter situations where network communication is not working, we should facilitate access to the console. When I was trying to help Timothy change a location radius setting remotely by phone and the web browser was timing out, I suggested that he find a micro-USB cable so he could connect to the console. But then I realized he would not have any application on his laptop that would allow him to connect to the console. Developers use "make monitor" in the software development cycle, but users won't have that tool. I have my own program on the MacBook that I use as an alternative when I don't want to induce a reset when I connect. But is there a simple program for Windows suitable for non-developer users that can connect to the OVMS console? -- Steve

4 46

Javascript
by Mark Webb-Johnson 23 Dec '18

23 Dec '18

I’ve enabled the javascript support in the ovms_scripts module. You can now write script files using the javascript language, and they will be run by the duktape engine. Any script file ending with “.js” extension will be treated as javascript. I’ve also added OvmsCommand and OvmsPrint extension commands. Two examples: OVMS# vfs cat /store/scripts/helloworld.js OvmsPrint("Hello world!\n”); OVMS# . helloworld.js Hello world! OVMS# vfs cat /store/scripts/ota.js OvmsPrint(OvmsCommand("ota status")); OVMS# . ota.js Running partition: factory Boot partition: factory Firmware: 3.1.008-40-g9254170-dirty/factory/edge (build idf v3.1-dev-1583-g0fb2019f Jul 9 2018 08:49:48) Server Available: 3.1.008-37-g939416c (no update required) Sat Jul 7 16:00:45 UTC 2018 Automated build (markhk8) ... A useful example would be to have a script that runs on location.leave, and checks the v.e.gear metric for vehicle in Drive, before firing off the homelink to close the garage door. Like all good things, the opportunity for evil is forever prevalent (and truly scary): OVMS# vfs cat /store/scripts/bruteforce.js for (var pin = 1000; pin < 10000; pin++) { OvmsCommand("unlock " + pin); } OVMS# . bruteforce.js V (1421374) canlog: TX can1 id 102 len 8: 0b 03 00 00 e8 03 00 40 | .......@ V (1421374) canlog: TX can1 id 102 len 8: 0b 03 00 00 e9 03 00 40 | .......@ V (1421374) canlog: TX can1 id 102 len 8: 0b 03 00 00 ea 03 00 40 | .......@ V (1421384) canlog: TX can1 id 102 len 8: 0b 03 00 00 eb 03 00 40 | .......@ V (1421384) canlog: TX can1 id 102 len 8: 0b 03 00 00 ec 03 00 40 | .......@ V (1421384) canlog: TX can1 id 102 len 8: 0b 03 00 00 ed 03 00 40 | .......@ V (1421384) canlog: TX can1 id 102 len 8: 0b 03 00 00 ee 03 00 40 | .......@ V (1421384) canlog: TX can1 id 102 len 8: 0b 03 00 00 ef 03 00 40 | .......@ V (1421384) canlog: TX can1 id 102 len 8: 0b 03 00 00 f0 03 00 40 | .......@ V (1421394) canlog: TX can1 id 102 len 8: 0b 03 00 00 f1 03 00 40 | .......@ ... I’ll leave it up to an exercise to the reader to change that script to use DukOvmsMetricValue() to monitor the v.e.locked metric to record success. Note that this is very hacky and experimental at the moment. A better approach seems to be to have a javascript task running, initialised at boot with a user’s javascript program. That can have timers, and whatever else it needs, to do it’s stuff. Then, scripts executed are run in the context of that task. The current implementation is really just a proof of concept. The OvmsPrint is particularly kludgy (a better implementation would be to hook to the duktape I/O system). Duktape is also currently running in internal RAM, although changing it to use SPI RAM should not be hard. Regards, Mark. > Begin forwarded message: > > From: GitHub > > Branch: refs/heads/master > Home: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3 > Commit: f1736f927df582c5ff374ef5d8c3a565e8f67295 > https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/f17… > Author: Mark Webb-Johnson <mark(a)webb-johnson.net> > Date: 2018-07-09 (Mon, 09 Jul 2018) > > Changed paths: > M vehicle/OVMS.V3/main/ovms_command.cpp > > Log Message: > ----------- > Javascript: Add a OvmsCommand function to execute an OVMS command > > > Commit: 69427f4ac0cf68dc462b05752936befe4be22256 > https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/694… > Author: Mark Webb-Johnson <mark(a)webb-johnson.net> > Date: 2018-07-09 (Mon, 09 Jul 2018) > > Changed paths: > M vehicle/OVMS.V3/main/ovms_script.cpp > > Log Message: > ----------- > Javascript: Add a OvmsPrint function to be able to print a string > JavaScript: Support .js script files (executed with javascript engine) > > > Compare: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/compare/92… > **NOTE:** This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ > > Functionality will be removed from GitHub.com on January 31st, 2019.

3 14