- OvmsDev - Open Vehicles

SSL error?
by Michael Stegen 04 Jan '24

04 Jan '24

With TLS enabled, the ovms v3 module can not connect to the openvehicles.com server anymore. When i disable TLS from the Server v2 configuration tab, the module successfully connects.. firmware is 3.3.003 Am i doing something wrong or is there a certificate issue? I (4103952) ovms-server-v2: Connection is api.openvehicles.com:6870 I (4103952) ovms-server-v2: Status: Connecting... I (4103982) webserver: HTTP GET /shell I (4104062) webserver: HTTP POST /api/execute I (4104072) webcommand: HttpCommandStream[0x3f8bfaf8]: 3484084 bytes free, executing: server v2 status E (4105182) mongoose: mg_ssl_if_mbed_err 0x3f8c3f54 SSL error: -9984 W (4105182) ovms-server-v2: Connection failed E (4105192) ovms-server-v2: Status: Error: Connection failed E (4107502) mongoose: mg_ssl_if_mbed_err 0x3f8c3f54 SSL error: -29312 W (4107502) ovms-server-v2: Connection failed E (4107502) ovms-server-v2: Status: Error: Connection failed I (4107512) ovms-server-v2: Status: Disconnected I (4151302) webserver: HTTP GET /cfg/server/v2 I (4157072) webserver: HTTP POST /cfg/server/v2 I (4162122) webserver: HTTP GET /shell I (4166952) ovms-server-v2: Connection is api.openvehicles.com:6867 I (4166952) ovms-server-v2: Status: Connecting... I (4167202) ovms-server-v2: Connection successful I (4167202) ovms-server-v2: Status: Logging in...

3 3

CAN2 turning off without reason
by Christos Oscar Kambiselis 11 Dec '23

11 Dec '23

Good afternoon, I've been trying to log CAN data using CAN2 in listen mode and connected to a different bus in the car ,I stopped the logging to the SD card yesterday and was going to test network streaming the data directly today, since I was having problems downloading the file, but I noticed that it goes to "Off" after an unspecified time. Yesterday I made sure it was on "Listen", after failing with the SD card file. And there is no mention of a timer, in the dev docs. Oscar

1 0

VWEUP module service interval?
by Michael Geddes 03 Dec '23

03 Dec '23

Hey All, I've been paving the way for 64 bit time_t that's apparently in the newer esp32 releases. I'm keen to know how that update to the newer sdk is going too? For persistence, I am registering the high 32bits as a second metric with "_hi" suffix (Similar to how the arrays work). One thing I've noticed is that there's a standard metric: OvmsMetricInt* ms_v_env_service_time; // Time to next scheduled maintenance/service [Seconds] cf the doc v.e.serv.time 1572590910Sec Time of next scheduled maintenance/service [Seconds] So it's a bit ambiguous but vweup (the only one who sets this metric) implementation treats this as a time_t. I think I will convert it to a 64 bit 'DateLocal' metric. Thoughts? //.ichael

3 2

Hologram
by Mark Webb-Johnson 27 Nov '23

27 Nov '23

I’m having a weird issue with Hologram. For years we’ve been buying SIMs from them and including with every OVMS device shipped. No issues, no complaints, and all smooth sailing. Now, a month or so ago I tried to buy a new batch of SIMs, the Hologram shop no longer offers shipping to Hong Kong. I wrote to them using their website contact feature, but no reply. I wrote to their sales contact, but no reply. I wrote to all my contacts there, but no reply. I wrote using both my open vehicles email address and gmail, but no reply. Ghosted. No idea if they are restructuring, or something broken with their email contact system, but it is very frustrating. Anyway, it now looks like the upcoming batch of OVMS won’t be able to include Hologram SIMs as standard. An inconvenience for our users, but not much I can do about it. If anyone has any contacts there, or any way of contacting them, perhaps you would try and ask. I’ve given up. There are plenty of alternatives, but perhaps that given that only a fraction of our users actually use the included Hologram SIM, it is time to stop including it. Regards, Mark.

3 5

A query on vehicle type switch (and failure)
by Michael Geddes 27 Nov '23

27 Nov '23

This code is from OvmsVehicleFactor::SetVehicle m_currentvehicle = NewVehicle(type); if (m_currentvehicle) { m_currentvehicle->m_ready = true; } m_currentvehicletype = std::string(type); StandardMetrics.ms_v_type->SetValue(m_currentvehicle ? type : ""); MyEvents.SignalEvent("vehicle.type.set", (void*)type, strlen(type)+1); My question is about what happens when NewVehicle() returns NULL. Should m_currecntvehicletype, v.type and the SignalEvent all be set as blank? Any particular reason why only the v.type is set as blank? //.ichael

2 5

Tesla Roadster Diagnostics
by Mark Webb-Johnson 22 Nov '23

22 Nov '23

Just got told about this… Tesla releases DBC and diagnostic tools for Tesla Roadster: https://github.com/teslamotors/roadster Can you imagine a world where every vehicle manufacturer did this for all their models (both past and current)? Regards, Mark.

1 0

Ongoing Poll system factoring
by Michael Geddes 17 Nov '23

17 Nov '23

Hi all , I have a whole bunch of commits that I'm quite keen to get put forward that are aimed at defining a better interface between the vehicle implementations and the base ISOTP/VWtp polling implementations. Next up is this one: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/914 There's no real functional change with this, but it is moving Vehicle implementations away from using the member variables and working with passed-in state information. I'm really hoping I can get this one moved forward and I want to be able to address any concerns people have with this code.. either as responses or as changes to the code. //.ichael

1 0

Implementing time printing/parsing and 32bit time_t values!
by Michael Geddes 05 Nov '23

05 Nov '23

I've added a p/r that implements a 'date+time' metric https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/946 I've also added a comment that reads as follows: One discovery I made while implementing this was that time_t is a 32bit number. It seems when we move to the 5.0+ framework this will be fixed in the esp32 libraries, but we will still need to implement a separate metric class for 64 bit time_t values. I'm thinking that an easy way to do it, since the underlying persist mechanism is 32bit, would be to have "_high" suffix a store the high bit as a "separate" metric. Should I do it with this patchset? I can implement the separate metric class and put in #ifdefs for when the time_t value is 64bit. Thoughts on this?? It also highlights the importance of pushing forwards with the new frameworks and filling in the gaps for that. //.

1 0

Time units and functions
by Michael Geddes 21 Oct '23

21 Oct '23

Hi all, firstly, it seems we are using a bunch of time functions that are not thread-safe (localtime gmtime and asctime) (See recommendation here: https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/s…) - so I'll push up a p/r for that. Next is the couple of Metrics that are using the unit 'Seconds' but which are really time_t values.. I'm looking to add a new Group of metrics for time with units UnixEpoch, UTCDate & LocalDate. This is what I have at the moment with the default metrics for m.time.utc as UTCDate and v.p.gpstime as LocalDate. (I can make them the same) m.time.utc 2023-10-19 11:22:28 UTC v.p.gpstime 2023-10-19 19:22:26 AWST Currently I've changed these in the JSON to be exported as "%FT%T.000Z" which is a semi standard for JSON. The 'conversion' for the date values doesn't do anything - these really only effect the output. I've also been looking at v.g.timerstart which is UTCTime & LocalTime units. I've fixed up conversions both way.. v.g.timerstart 18:00:00local Thoughts on these? Cautions? //.ichael

2 2

GSM + GPS combined antenna working!
by Michael Geddes 06 Oct '23

06 Oct '23

I believe I have finally resolved the issue with the GSM daughter board and/or antenna interfering with my GPS. I replaced both and it seems to be all good now. Interestingly, I found this nice Antenna that has GSM and GPS (with 2 well-labeled tails that are compatible with the OVMS connections). https://www.amazon.com.au/dp/B07V9HRF65 It seems to be working well and is much neater to replace (I snaked it up through to the speaker+air cover on the front dash area). //.ichael

2 2