February 2024 - OvmsDev - Open Vehicles

Warning in Duktape
by Michael Geddes 09 Aug '24

09 Aug '24

There's an unused variable 'dcc' warning in the below code. It seems that the 'Perform the callback' is not being 'performed! Is this deliberate? //.ichael void DukOvmsCommandRegisterRun(int verbosity, OvmsWriter* writer, OvmsCommand* cmd, int argc, const char* const* argv) { ESP_LOGD(TAG, "DukOvmsCommandRegisterRun(%s)",cmd->GetName()); auto it = MyDuktape.m_cmdmap.find(cmd); if (it == MyDuktape.m_cmdmap.end()) { ESP_LOGE(TAG, "Command '%s' cannot be found in registry",cmd->GetName ()); return; } else { DuktapeConsoleCommand* dcc = it->second; // Perform the callback } }

3 6

Upgrading Mongoose ?
by Michael Geddes 26 Apr '24

26 Apr '24

I've been looking at the work of Ludovic in updating OVMS to the new framework. I've even put up a few pull-requests where this work has uncovered bugs due to improvements in the compiler. Ludovic did a great job in also updating the Mongoose library. For those unaware, the big issue is that there was a massive reworking of the library just after the point where ovms forked the library. I suspect some/many? of the changes that were made in our fork are no longer required. There was a lot done in moving some of the work that had to be done in the callers (ovms) code into the mongoose code which is great - and Ludovic has done that conversion - there are just a few more things that needed to be done on top of that. One of the things they did was remove mg_locals.h which allowed us to configure mongoose from our own custom include. The other really annoying thing they did was to remove the use of MG_ALLOC, MG_CALLOC in place of malloc( calloc( etc. The problem with this is for freertos they define #define calloc(a, b) mg_calloc(a, b) #define free(a) vPortFree(a) #define malloc(a) pvPortMalloc(a) without any further condition. Tihs means we don't have a way of defining these to our own versions which is what we originally did... well not without forking the mongoose (which maybe we do anyway). It also means that any of our files that include mongoose.h will have these redefined away from our own versions of these. Fortunately it seems we don't use those much. I also noticed that even the latest Mongoose MQTT doesn't appear to support aliases (and therefore optimising the amount of data used by a v3 server).. but it appears that wolfmqtt does - so should we be using that instead as a mqtt client?? Does anybody else have some further input on this?? //.

2 2

FIAT e-Doblo (same as Peugeot Rifter, Opel Combo, Citroen Berlingo?)
by Raphael Mack 03 Apr '24

03 Apr '24

Hi, I own a eDoblo from Fiat and recently bought an OVMS. Very cool.project, thanks for all.the effort you all have put in it! Beside trouble to permanently plug in the generic ODB2 connector due to space below the cover I face the fact that it is not supported by OVMS. So I created https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/976 and would like to contribute. In my former life I worked in automotive industry but I already recognized that it is much easier to read a CAN trace if you have a DBC and the well known Vector tools at hand 😃. In case anyone has some hints where I can get more info about the frames and signals, even from other cars in the same family (EMP2, Peugeot e208, e2008, Opel mokka-e) from the Stellantis brands or former PSA it could be a great help to sort at least some ID into the 'interesting' or 'boring' boxes. Last but not least any idea where I could get an overall bus architecture for the car from would be cool, as I would like to install the the OVMS in a permanent place different from the ODB2 connector. Looking forward to a great journey here. BTW: initially I had trouble receiving mails from the list, as the sending servers IP was on some blacklist and therefore blocked on my incoming mailserver. So if you could put me personally on CC on an answer I'd be happy, just in case this is not yet sorted out. Regards, Rapha

2 2

Firmware release 3.3.004
by Michael Balzer 17 Mar '24

17 Mar '24

Mark & everyone, there are new feature extensions in the pull request queue, i.e. poller timing control by Michael Geddes & a new MG5 model variant by Peter Grey. I'd rather close 3.3.003 now and release the current state as main 3.3.004 before merging new features that again would need testing. A new main release is overdue, and the latest fixes by Michael Geddes did improve stability significantly. I haven't had a single crash with 3.3.003-621 yet. Objections? Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

5 9

Maxus eDeliver 9
by Mark Webb-Johnson 01 Mar '24

01 Mar '24

Has anyone looked at the Maxus eDeliver 9 vehicle support? Seeing these IDs on the CAN bus, which doesn’t seem to match either the eDeliver3 or eUniq56 expectations: 0F1, 1D8, 1F5, 210, 220, 223, 261, 266, 269, 281, 290, 293, 2F6, 300, 310, 319, 329, 355, 362, 363, 373, 375, 379, 37A, 3D7, 410, 501, 503, 509, 510, 511, 512, 558, 55F, 598, 5A5, 5A6, 5B0, 5E0, 698, 6F0, 6F1, 6F2, 795, 7C8 There is a commercial operation in Germany that is looking for help with this. Regards, Mark.

3 2

wolfssl has been converted to a git submodule
by Ludovic LANGE 19 Feb '24

19 Feb '24

Dear all, The PR https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/887 which converts wolfssl to a git submodule has been merged to master. For those that build / sync their trees manually, please ensure that you do `git submodule update --init --recursive` after the git pull, so that you can properly retrieve the submodule. You can confirm that everything is OK by doing: $ git submodule status 7b953e7ebb440ce9461ee469159c3759450e7c98 components/mongoose/mongoose (6.2-882-g7b953e7) c05f6c7530a8670e3d0ffdf04ee4cecb2d3b0496 components/wolfssh/wolfssh (v1.4.10-stable) 2d5a0ccae50a2ea32fc933d707b465520cc90011 components/wolfssl/wolfssl (v4.7.0-stable-5-g2d5a0ccae) 7c3878f8302c0e84578a67473e49e60bc6b3ada7 components/zip/libzip (rel-1-5-1-60-g7c3878f) d6bcf4ca4d02479f058fff44cfd171f928148179 components/zip/zlib (v1.2.11-65-gd6bcf4c) It should print (3rd line) a version of v4.7.0-stable-5-g2d5a0ccae. If instead you see: $ git submodule status 7b953e7ebb440ce9461ee469159c3759450e7c98 components/mongoose/mongoose (6.2-882-g7b953e7) c05f6c7530a8670e3d0ffdf04ee4cecb2d3b0496 components/wolfssh/wolfssh (v1.4.10-stable) -2d5a0ccae50a2ea32fc933d707b465520cc90011 components/wolfssl/wolfssl 7c3878f8302c0e84578a67473e49e60bc6b3ada7 components/zip/libzip (rel-1-5-1-60-g7c3878f) d6bcf4ca4d02479f058fff44cfd171f928148179 components/zip/zlib (v1.2.11-65-gd6bcf4c) then you need to use `git submodule update --init --recursive` Let me know if it's not working according to the plan. Regards,

3 3

SSL Certificates for Open Vehicles
by Mark Webb-Johnson 13 Feb '24

13 Feb '24

FYI: I’ve updated the SSL certificates for Open Vehicles (www.openvehicles.com <http://www.openvehicles.com/>, api.openvehicles.com <http://api.openvehicles.com/>, etc) - all services including website, MQTT and v2 server. CA’s are: C = LV, L = Riga, O = GoGetSSL, CN = GoGetSSL RSA DV CA C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority That should be the same as the components/ovms_tls/trustedca/usertrust.crt we already have trusted in OVMS v3 by default, so hopefully no impact. Regards, Mark

2 1

Auxiliary Battery Monitor (Kia Niro EV)
by Douglas Urner 09 Feb '24

09 Feb '24

The 12V auxiliary battery in our Niro has died twice, so I decided to dig back into OVMS to see if it could shed any light on what is going on with the battery. I’ve installed the AuxBatMon <https://docs.openvehicles.com/en/latest/plugin/auxbatmon/README.html> plugin to log battery parameters and I have questions… The module is running: 3.3.003/ota_1/main (build idf v3.3.4-848-g1ff5e24b1b Sep 3 2022 11:32:12) — is this really the latest stable version? Here’s what I’m seeing: My questions: What is the source of the current value? Is it being reported by the vehicle? I’m puzzled by it remaining at a high constant value even after the charger appears to have shut down. Similarly with the charger and environmental temperature values — it seems add that they are mostly constant. If there is anyone out there with a Niro / Kona, I’d be curious to know what the behavior of your auxiliary battery looks like. Many thanks, Doug

2 1