- OvmsDev - Open Vehicles

3.2.013
by Mark Webb-Johnson 10 Jun '20

10 Jun '20

Getting ready to release 3.2.013. I’ve tagged it, and built for api.openvehicles.com <http://api.openvehicles.com/> edge. The main changes here are: TPMS subsystem (including Tesla Roadster support with new optional K-line expansion board) Change to config for server.v2 For #2, I moved the server password from server.v2/password to password/server.v2, and made the server.v2 config parameter read-write. That better matches how server.v3 does it. The change is done via a config migration, so should be transparent. Absent any issues, I plan to move to EAP early in the coming week. Regards, Mark

3 10

What happened to TPMS?
by Greg D. 06 Jun '20

06 Jun '20

6 13

UserTrust/AddTrust/Comodo root CA expiration
by Mark Webb-Johnson 04 Jun '20

04 Jun '20

The AddTrust root CA certificate that our api.openvehicles.com <http://api.openvehicles.com/> is signed by has expired (last night). This will impact TLS connections to api.openvehicles.com <http://api.openvehicles.com/>. Our certificate itself is fine (and doesn’t expire until Feb 2022), but the root cert is was signed by (via intermediaries) has expired. Pretty irresponsible for AddTrust/UserTrust/Comodo to sign a certificate with a later expiration date than their own CA, imho. Also irresponsible for them not to inform the customers. Everybody can be expected to monitor their own certificate expiration date, but not that of their certificate authority. I’ve been up most of the night dealing with fallout from this (in other work and customer related systems), so not happy. Anyway, I’ve updated the trusted root certificate in edge now, and released that. AddTrust has become UserTrust. To connect via tls to api.openvehicles.com <http://api.openvehicles.com/> now, you will either need to firmware update, or manually add the trusted ca to /store/trustedca/usertrust.crt (I have attached it here, for convenience). I have also taken this opportunity to change the server v2 and v3 backoff retry times to 60 seconds (was 20 or 30). Regards, Mark.

4 3

Save Status
by Tamás Kovács 04 Jun '20

04 Jun '20

I would like to implement Save status to save / load value when module crash. I copy kia_common.h/cpp and remove all code not relevant, added code to vehicle_mitsubishi.h/cpp same as kia, but not restore the soc value. If i check the saved file at web interface / editor has size 4, and if i open it is empty. Last time i saw the Trip power plugin do the same at my module, if module restart no data in web interface. I think Trip power chart plugin overwrite the datafile after reboot. Save data to SD card. Any idea?

2 2

J1850 support research
by Craig Leres 25 May '20

25 May '20

I've been doing some research on a possible J1850 expansion board; I've looked at the (nice!) work that Mark and Marko have done on TPMS and SWCAN expansion boards. It looks like the TPMS expansion adds the k-line (LIN bus) to the previously unused pin 1 of the DB9. I think I can also use pin 1 for the J1850 bus. The J1850 protocol chip I'm using (HIP7010) uses SPI as does the SWCAN board. The ESP32 docs say there are four SPI devices. Two are used for flash tasks leaving HSPI and VSPI. I believe ovms uses HSPI for SPI ram access and VSPI is used to run the can buses (and SWCAN when present). The problem I see is that the HIP7010 must be SPI master; unlike I2C I don't think you can have more than one SPI bus master. I think this means my best approach is to build a J1850 to canbus protocol bridge and just encapsulate J1850 frames in can frames? I think I could still feed the J1850 bus on pin 1 of the DB9. This way the protocol bridge would only need the HD25 connector to do everything: J1850, 5V, vehicle 12V (needed by the J1850 transceiver), and can bus lines. Am I correct in talking myself out of an expansion board? Craig

2 3

HttpApi fixed & deployed
by Sébastien Darveau 19 May '20

19 May '20

Hi all, I’ve contributed for the first time to the OVMS project by fixing a few things in the server code related to the REST Api. That was not easy since I’m not familiar with Perl but I want my soc on my Garmin watch! I’m an experienced software consultant from Montreal. I’ve been working in the mobile game and broadcast industries but I’m now into Xamarin so maybe I could give my help to the unified mobile app development. Let me know if this is still planned. I also have a Leaf 2015 with OVMS and it’s an awesome project! Best, Sebastien Darveau

2 1

Locations (actions, etc)
by Mark Webb-Johnson 05 May '20

05 May '20

Steve, What is the current status of the changes you have been making to the locations system? I have a user asking why: >location set Likini >location action enter Likini notiffy entered >****: location action enter Likini notify entered Unregconised command Usage: location action enter <location> acc <profile> Usage: location action enter <location> homelink 1|2|3 Usage: location action enter <location> notify <text> Was this ever completed? Regards, Mark

3 3

3.2.012 EAP OTA
by Mark Webb-Johnson 01 May '20

01 May '20

I think the tpms bug is serious enough to require a release. So, I’ve built a 3.2.012 and released to EAP at api.openvehicles.com <http://api.openvehicles.com/>. 2020-04-22 MWJ 3.2.012 OTA release - #357 tpms rear left temperature incorrect in v2 protocol - #354 Flush UART buffer when power cycling modem - General stability improvements to CAN logging and playback As usual, for full changelog see: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/maste… <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/maste…> This will also allow us to get more feedback on the uart reset approach, and if it makes any difference to those modules that can’t seem to recover from loss of cellular connection. Regards, Mark.

3 5

can polling
by Tamás Kovács 01 May '20

01 May '20

Can anybody help me understanding can polling? I use the following code in 3.0.12 and older version. i send every 60s when the car is on a following code: CAN_frame_t frame; memset(&frame,0,sizeof(frame)); frame.origin = m_can1; frame.FIR.U = 0; frame.FIR.B.DLC = 3; frame.FIR.B.FF = CAN_frame_std; frame.MsgID = 0x761; frame.data.u8[0] = 0x02; frame.data.u8[1] = 0x21; frame.data.u8[2] = 0x01; m_can1->Write(&frame); At IncomingFrameCan1 i catch the response message at 0x762 and send a flow control message (this values from can logging during genuine diagnostic use on car) if (d[0] == 16) { // Request CAC... CAN_frame_t frame; memset(&frame,0,sizeof(frame)); frame.origin = m_can1; frame.FIR.U = 0; frame.FIR.B.DLC = 3; frame.FIR.B.FF = CAN_frame_std; frame.MsgID = 0x761; frame.data.u8[0] = 0x30; frame.data.u8[1] = 0x08; frame.data.u8[2] = 0x0A; m_can1->Write(&frame); } And with this is get some data (CAC) But if i use polling with the following values static const OvmsVehicle::poll_pid_t vehicle_mitsubishi_polls[] = { { 0x761, 0x762, VEHICLE_POLL_TYPE_OBDIIGROUP, 0x02, { 0, 10, 10 } }, // cac { 0, 0, 0, 0, { 0, 0, 0 } } }; i get the following in void OvmsVehicleMitsubishi::IncomingPollReply.... I (178194) v-mitsubishi: 762 TYPE:21 PID:02 7 01 7e 01 7e 01 7f 01 00 I (178224) v-mitsubishi: 762 TYPE:21 PID:02 7 7e 01 7e 01 7e 01 7e 00 I (178284) v-mitsubishi: 762 TYPE:21 PID:02 7 01 7e 01 7e 01 7e 01 00 I (178284) v-mitsubishi: 762 TYPE:21 PID:02 7 7e 01 7e 01 7e 01 7e 00 I (178314) v-mitsubishi: 762 TYPE:21 PID:02 7 01 7e 01 7e 01 7e 01 00 I (178344) v-mitsubishi: 762 TYPE:21 PID:02 7 7e 01 7e 01 7e 01 7e 00 I (178374) v-mitsubishi: 762 TYPE:21 PID:02 7 01 7e 01 7e 01 7e 01 00 I (178404) v-mitsubishi: 762 TYPE:21 PID:02 7 7e 01 7e 01 7e 01 7e 00 I (178434) v-mitsubishi: 762 TYPE:21 PID:02 7 01 7e 01 7e 01 7e 01 00 I (178464) v-mitsubishi: 762 TYPE:21 PID:02 7 7e 01 7e 01 7e 01 7e 00 I (178494) v-mitsubishi: 762 TYPE:21 PID:02 7 01 7e 01 7e 00 00 00 00 i run a can logging with this session and i only see the same data (incomping poll reply) only the d[0] is changed. What do i do wrong?

1 1

3.2.012 test
by Michael Eric Menk 28 Apr '20

28 Apr '20

I have downloaded and tested 3.2.012 The C-zero (MiEV clone) charge bug was not included. On 25.04.2020 20:24, Tamás Kovács wrote: > Thanks the log, now i modified the AC charge detection code. > > If you want to try add the following to config / firmware / flash from > web : kommykt-nas.ddns.net:22289/ovms3.bin > <http://kommykt-nas.ddns.net:22289/ovms3.bin> > This is my NAS, the internet speed is not very high. > The changes that Tamás did worked. It tould have been nice that this would be included in 3.2.012 before it goes in prod. As far as I can see, the code is not committed into master yet. A better range_est while fastcharing can worked on later.

2 1