December 2020 - OvmsDev - Open Vehicles

Re: [Ovmsdev] Changing Existing Functionalities
by Derek Caudwell 14 Dec '20

14 Dec '20

I envisage following a robust testing process outside of the main repo being a bit more difficult with the Leaf because of the quite substantial changes in the can bus framework/messages over the years. A change that works for more recent years but not for prior years is not always easy to spot, also improvements/additions of metrics may only work on a particular year unless another dev with a prior year implements and tests them. Without a group of Leaf devs or testers across the various years that can be called upon to test prior to putting through a PR to main I expect future changes will stay in Leaf devs repos untested for other MYs, as there is no particular reason for others to jump in and test the code to confirm compatibility. PR487 will be a good test case to see if the approach proposed can work in practice.

2 1

Re: [Ovmsdev] Changing Existing Functionalities
by Derek Caudwell 13 Dec '20

13 Dec '20

Hi Michael, Thanks for clarifying, until then I had been using "edge" on the basis that is where other devs would pick up on any issues with other models, so that issues got resolved before "eap" where they go out to a wider test community. Jaunius (@mjkapkan), and other Leaf devs I suggest circulating the repo that can be pulled from for testing on this mailing list before it goes to the master PR, or is there a way to notify others through github? Kind regards Derek (@drc38)

2 1

Changing Existing Functionalities
by jaunius＠gmx.com 12 Dec '20

12 Dec '20

Hi, Already several times there have been instances where functionalities or existing metrics are changed and merged without reviews from previous developers. This leads to additional time of rolling back the changes when often the changes brake something for different model year cars. In turn this leads to more time spent on rolling back the changes and etc. Do we have some kind of guidlines to avoid this? Kind regards, Jaunius Sent using the GMX mail app

2 1

More AddTrust/UserTrust CA certificate trouble
by Stephen Casner 12 Dec '20

12 Dec '20

I've just moved to a different laptop which caused me to look at some things I have not looked at for a while. One of them was the perl script Tom Saxton gave me to query the openvehicles server to gather the log entries for my car. That script references: https://www.openvehicles.com:6869 This is now failing to log in. Testing manually with curl gives: auge14> curl -X GET -c ovms-cookie "https:/www.openvehicles.com:6869/api/cookie?username=xxxx&password=xxxx" curl: (60) SSL certificate problem: certificate has expired More details here: https://curl.haxx.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. This looks like it could be related to the AddTrust CA cert expiration that occurred back in May. I check the macOS keychain and I see that the new USERTrust RSA CA certificate is already there and matches the one that Mark included with his email to this list about the problem. Looking on the web for guidance I found the following suggested command which appear to indicate that the server is still using a certificate referencing the old CA cert? auge15> openssl s_client -showcerts -servername www.openvehicles.com -connect www.openvehicles.com:443 > cacert.pem depth=3 C = SE, O = AddTrust AB, OU = AddTrust External TTP Network, CN = AddTrust External CA Root verify error:num=10:certificate has expired notAfter=May 30 10:48:38 2020 GMT Is this something that needs to be fixed on the server, or is there something I need to change in my query? -- Steve

2 3

VFS rm
by Tamás Kovács 11 Dec '20

11 Dec '20

Hi! Any idea how to remove these files? "OVMS# vfs ls /store/usr 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? 64 12-Sep-1965 06:34 ????????.??? ..." [image: Screenshot 2020-12-06 at 16.07.57.png]

6 7

Charging Monitor Plugin
by jaunius＠gmx.com 09 Dec '20

09 Dec '20

Hi, I created this Plugin as I was not getting the necessary details in one screen from the app. Maybe something to look in to for the joint iOS/Android app. https://github.com/mjkapkan/OVMS-Plugins/tree/master/chargemon See print-screens attached. It is still in beta but fairly usable. Will finalise and add all my plugins soon to the main repo. Stay safe, Jaunius Sent using the GMX mail app

1 0

Do I have to flash "entire chip" with esptool if I already have the code on my OVMS box?
by Steve Davies 05 Dec '20

05 Dec '20

Hi Mark et-al, I've installed the esp32 and the esp-idf environments on my Mac and successfully build the OVMS firmware. In the developer guide it then covers how to flash the box with esptool. But: do I need to do that? - my OVMS box is up and running already - I'm guessing I can use OTA update to update with steve@maximus OVMS.V3 % ls -l build/ovms3.bin -rw-r--r-- 1 steve staff 2986336 Dec 5 12:24 build/ovms3.bin ? Since the "flash from web" and and "flash from file" are looking for an ovms.bin. Nervous to brick my box since it was expensive to get it to Cape Town. By the way, my build prints 'App "ovms3" version: 3.2.015-162-g10232c58-dirty' I recognise the git commit hash, but what is the "-dirty"? (I build a "bmwi3" branch of a fork of the original project - maybe that answers my own question?) My OVMS box currently says it's running "3.2.015/ota_0/main (build idf v3.3.2-881-g22d636b7b Sep 2 2020 08:32:35)" Thanks, Steve

2 4

Hello from a new subscriber
by Steve Davies 01 Dec '20

01 Dec '20

Hi, I'm Stephen Davies. Mark suggested that I say hello on the list, so: "Hi!". I own a 2019 BMW I3S BEV and I'm keen to try to add support into OVMS. (I live in Cape Town in South Africa - the i3 is the one very few EVs sold here) I've done a fair amount of work reverse-engineering messages from a couple of apps that can already talk to the I3 on OBD2 port. So I have a fair list of PIDs from that. My OVMS box arrived the other day. I built an ovms-server and I've got my OVMS box talking to my server and through to the IOS OVMS app. So the next step will be to set up to be able to build the firmware from source and then to start adding the i3... Can I ask one question in conclusion: how do I get the OVMS IOS app to do a TLS connection? I told it to use port 6870 but it does not do a TLS handshake. Do OVMS devs hang out in an IRC room, Slack or some such? Thanks, Steve

2 1