- OvmsDev - Open Vehicles

Server V3 topic prefix, stability and encryption
by Jakob Löw 04 Jul '18

04 Jul '18

Hey, I've seen some changes pushed to the repo regarding the v3 server. I did some development on that too and found it to be very unstable, often crashing after start (when transmitting all metrics) or when the NetUp was called before any interface was up. Both issues were connected to race conditions. I opened two pull requests to fix them [0], [1]. The first one also introduces a new configuration option to set a custom prefix for the MQTT topic. OVMS metric names seem to use a sort of namespacing using dots, like m.freeram or v.e.on. Replacing dots in metric names by slashes in MQTT topics, makes the OVMS follow MQTT namespacing rules (m/freeram and v/e/on). One thing currently missing with the Server V3 is encryption. Mongoose supports SSL so enabling it would be easy, but the problem is the certificate management. We could allow users to load certs onto the module, however this is something unexperienced users wouldnt do. Another option is to ship the OVMS with a list of common root certs, like many browsers do. The certs shipped with firefox are ~500KB and can be easily obtained e.g. from the debian repos [2]. This could then also be used by the server v2 to replace the outdated RC4 encryption. - Jakob [0] https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pu ll/137 [1] https://github.com/openvehicles/mongoose/pull/1 [2] https://packages.debian.org/stretch/ca-certificates

2 2

Alerts (or, the lack thereof)
by Greg D. 03 Jul '18

03 Jul '18

Hi folks, A couple of postings on TMC from Roadster owners who have received a single alert, and never got any more. I've not had this problem, and wonder what guidance we can give them. https://teslamotorsclub.com/tmc/posts/2845522/ (starting with his "next question"...) I'm on version 3.1.006; the two recent posts are from versions .006 and .007, so this isn't a version issue. Is there something they need to configure? I don't know, for example, what app they are running, but presume the issue is upstream of that. Thanks, Greg

2 3

OVMS v3 v3.1.008 Over-the-Air firmware update
by Mark Webb-Johnson 03 Jul '18

03 Jul '18

https://www.openvehicles.com/node/2058 <https://www.openvehicles.com/node/2058> Today, we are pleased to release v3.1.008. Over 60 bug fixes and enhancements have gone into this release since the last public release (v3.1.006), and a summary of the major changes is here: Firmware: 3.1.008 3.1.008 OTA release - Vehicle theft alert if vehicle moved more than 500m when parked - New 'location radius' command to set location radius - Only issue 'location.enter' and 'location.leave' events if vehicle is ON - Fix issue with OTA updates in 3.1.007 3.1.007 OTA release - Logging: auto expire log archive New config: log [file.keepdays] = 30 0 = disable New command: log expire [days] Manual expire Note: auto expire is done within hour 0 of day - Web UI: simplified time zone region selection (vehicle config) - Web UI: locations editor - Prefer SPI RAM (on 3.1 hardware) for improved on-chip memory availability For full detail on all changes, check the GitHub revision history. Please note the firmware v3.1.007 was never fully released (beyond testing release levels) as it had an issue with OTA updates. If you are running v3.1.007 you will most likely have to manually update to v3.1.008, using these instructions (only for those running v3.1.007): 1. Firstly, go back to factory firmware: ota boot factory module reset 2. After reset, connect to wifi and do a manual ota update: ota flash http api.openvehicles.com/firmware/ota/v3.1/main/3.1.008.ovms3.bin module reset 3. After that is done, check the version with: ota status You should be running 3.1.008 from an ota partition. Alternatively, you can download 3.1.008 from http://api.openvehicles.com/firmware/ota/v3.1/main/3.1.008.ovms3.bin <http://api.openvehicles.com/firmware/ota/v3.1/main/3.1.008.ovms3.bin> directly and put as ovms3.bin on SD CARD to update from that. 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'. Thank you for your support of the project. Open Vehicles

1 0

Fwd: [openvehicles/Open-Vehicle-Monitoring-System-3] 29e333: Issue #36: Add support for ota/tag in config
by Mark Webb-Johnson 30 Jun '18

30 Jun '18

A few changes to OTA this morning: The ‘ota status’ command used to check available server version only if a WIFI network was up. It now does that if ANY network is up (including modem). I’ve added a config instance ‘tag’ to parameter ‘ota’. This can be used to override the ota tag (default: main) at run-time. I’ve added a config instance ‘server’ to parameter ‘ota’. This can be used to override the ota server URL (default: api.openvehicles.com/firmware/ota <http://api.openvehicles.com/firmware/ota>). From now on, I’m going to be maintaining two tags for the production ota server api.openvehicles.com <http://api.openvehicles.com/>. These are: main: for stable releases edge: for bleeding edge developer releases You can, for example, now set your module to bleeding-edge by ‘config set ota tag edge’. Regards, Mark. > Begin forwarded message: > > From: GitHub <noreply(a)github.com> > Subject: [openvehicles/Open-Vehicle-Monitoring-System-3] 29e333: Issue #36: Add support for ota/tag in config > Date: 16 April 2018 at 8:37:46 AM HKT > To: mark(a)webb-johnson.net > Reply-To: GitHub <noreply(a)github.com> > > Branch: refs/heads/master > Home: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3 > Commit: 29e33348f6dff949fd22567083de1d9db04b05e3 > https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/commit/29e… > Author: Mark Webb-Johnson <mark(a)webb-johnson.net> > Date: 2018-04-16 (Mon, 16 Apr 2018) > > Changed paths: > M vehicle/OVMS.V3/components/ovms_ota/src/ovms_ota.cpp > M vehicle/OVMS.V3/main/ovms_version.cpp > > Log Message: > ----------- > Issue #36: Add support for ota/tag in config > Issue #37: Add support for ota/server in config > Issue #38: ota status should show available server version for modem as > well as wifi > >

4 9

A Car Hacking Experiment: When Connectivity Meets Vulnerability
by Mark Webb-Johnson 29 Jun '18

29 Jun '18

FYI: https://www.researchgate.net/publication/286931560_A_Car_Hacking_Experiment… <https://www.researchgate.net/publication/286931560_A_Car_Hacking_Experiment…> Interconnected vehicles are a growing commodity providing remote access to on-board sys- tems for monitoring and controlling the state of the ve- hicle. Such features are built to facilitate and strengthen the owner’s knowledge about its car but at the same time they impact its safety and security. Vehicles are not ready to be fully connected as various attacks are currently possible against their control systems. In this paper, we analyse possible attack scenarios on a recently released all-electric car and investigate their impact on real life driving scenarios. We leverage our findings to change the behaviour of safety critical com- ponents of the vehicle in order to achieve autonomous driving using an Open Vehicle Monitoring System. Furthermore, to demonstrate the potential of our setup, we developed a novel mobile application able to control such vehicle systems remotely through the Internet. We challenge the current state-of-the-art technology in today’s vehicles and provide a vulnerability analysis on modern embedded systems.

3 5

Vehicle Info in User Guides
by Mark Webb-Johnson 29 Jun '18

29 Jun '18

We’ve got quite a few (hundreds, as we are about half way sold through the second batch) using OVMS v3 now, and I’m getting questions about specific functionality in specific vehicles. We need better documentation on this. As an example, I’ve updated the User Guide, Tesla Roadster section. I’ve covered: A short introduction about level of vehicle support. Should describe exactly what model years and variants are supported, and overall how good the support is. Hardware requirements. A list of components (on fasttech, or elsewhere) for what is required (most importantly cables, antennas, etc). Module installation in the vehicle. Where we recommend putting it. Antenna installation. Where we recommend placing the antenna(s). Vehicle-specific configuration options. Vehicle-specific commands. Notes. Concentrate on limitations, or vehicle-specific stuff. Thanks. A space to thank the developers (yourself) and anybody else who has contributed to that vehicle module support. It would be good if the other vehicles followed the same format (or something similar). I see that Kia Soul is pretty complete, but Nissan Leaf and Renault Twizy need some work (I guess the RT document is somewhere else?). It would be good to get this all in one place, so we can simply refer questions to that. Could you guys fill in / copy over the text, and I’ll help with proof-reading and formatting? Thanks, Mark.

1 0

Compiler warning
by Mark Webb-Johnson 28 Jun '18

28 Jun '18

I’m seeing this: CXX build/ovms_webserver/src/ovms_webserver.o /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3.1/vehicle/OVMS.V3/components/ovms_webserver/src/ovms_webserver.cpp: In member function 'user_session* OvmsWebServer::CreateSession(const http_message*)': /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3.1/vehicle/OVMS.V3/components/ovms_webserver/src/ovms_webserver.cpp:665:32: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] s->id = *((uint64_t *) digest); ^ Michael: Can you have a look? Thanks, Mark.

2 2

Feedback regarding web dashboard
by Mark Webb-Johnson 28 Jun '18

28 Jun '18

I received the following feedback regarding the web dashboard: Can you please revert the two ranges in the OVMS dashboard so that they appear in the same order as in the app (see pictures above: 297 - 307 v. 307 - 298)? This would make reading the numbers much easier for us! Can we make this change? Regards, Mark.

2 1

Default values and fields...
by Greg D. 27 Jun '18

27 Jun '18

Hi folks, One thing I've noticed in setting up the OVMS module is that my experience with the term "default" is a bit different than what we have implemented. In the past, I have come to expect "default" to mean "if you don't do anything, you will get this". Instead, we seem to be using it to mean "unless you need to use something else, use this value". In the former case, one properly leaves the entry empty or otherwise unchanged. In the later case, we show the value, but it is up to the user to actually configure it. Leaving the entry in its default state is not correct. Where this most recently affected things was the automatic update to version .006, which did not occur on time. Investigating, there were a couple of fields labeled with the default phrasing (e.g. the server address) that were, as I thought instructed, left blank. Filling them in with the default contents and pressing save worked. Next morning, I awoke to .006 running on the module. Yea! Oh, almost... My timezone was also wrong. It was set to -7 like I do everywhere else, instead of PST8PDT. Where did that come from? My only clue to this was that the new boot status display of time at last boot said GMT instead of PDT. Is this just my own weird view of the world? Is it worth changing either the on-screen instructions to clarify what action needs to be taken, or should we actually implement (pre-configure) the defaults so that no further action needs to be taken by the user? My recollection is that this is not just with the webserver UI; the command line setup is equally in need of active management, for example to get the v2 server to connect. There are lots of defaults all over the place, but none of them are implemented by default. At least we are consistent... Greg

6 24

Fwd: OVMS 3.1.007
by Mark Webb-Johnson 26 Jun '18

26 Jun '18

FYI: I’ve put v3.1.008 up on edge, but not live yet. Users of the problematic v3.1.007 can download and update from there. I plan to release v3.1.008 to all edge users this weekend. Regards, Mark. > Begin forwarded message: > > From: Mark Webb-Johnson <mark(a)openvehicles.com> > Subject: OVMS 3.1.007 > Date: 26 June 2018 at 10:21:16 PM HKT > To: undisclosed-recipients:; > > > You vehicle connected to the api.openvehicles.com <http://api.openvehicles.com/> is running firmware v3.1.007. That version of firmware was released to ‘edge’ a week or so ago, but was not released to ‘main’ as we’ve seen issues with that firmware sometimes being unable to update over Wifi OTA (depending on flash image size and speed of flash access). > > As we are about to release v3.1.008 (to address this issue, as well as a few other small enhancements), it would be helpful if you could manually update to that new firmware first (as the automatic OTA update from v3.1.007 to v3.1.008 will most likely fail for you). You can do that with: > > Firstly, go back to factory firmware: > > ota boot factory > module reset > > After reset, connect to wifi and do a manual ota update: > > ota flash http api.openvehicles.com/firmware/ota/v3.1/edge/3.1.008.ovms3.bin <http://api.openvehicles.com/firmware/ota/v3.1/edge/3.1.008.ovms3.bin> > module reset > > After that is done, check the version with: > > ota status > > (You should be running 3.1.008 from an ota partition) > > Alternatively, you can download 3.1.008 from http://api.openvehicles.com/firmware/ota/v3.1/edge/3.1.008.ovms3.bin <http://api.openvehicles.com/firmware/ota/v3.1/edge/3.1.008.ovms3.bin> directly and put as ovms3.bin on SD CARD to update from that. > > We will release v3.1.008 to edge this weekend, and we suggest you do this manual upgrade before then. > > Apologies for the inconvenience. > Regards, Mark.

1 0