March 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

Firmware release 3.3.004
by Michael Balzer 28 Jun '24

28 Jun '24

Everyone, I've just tagged version 3.3.004 and released the build to EAP on ovms.dexters-web.de -- Mark, please follow up. As usual, we will release this to MAIN in about a week. This release has been long overdue, it includes numerous new features, new vehicles and of course lots of bug fixes. A huge thank you to everyone involved in this collaborative effort! Changes since 3.3.003: - MG EV Added support for MG5 (2020 - 2023) Short Range - MG EV Added support for MG ZS EV (2023 - ) and MG5 (2020 - 2023) Long Range - OVMS Server v3 metrics filtering New configs: [server.v3] metrics.include -- Comma-separated list of metric names (with possible wildcard) matching metrics to send [server.v3] metrics.exclude -- Comma-separated list of metric names (with possible wildcard) matching metrics to not send - Renault Zoe Phase 2: Initial support - Improved output of bms shell command for narrow windows. New commands: bms volt -- Output only voltage info if available bms temp -- Output only temperature info if available - Hyundai Ioniq 5: Initial support - Support for specifying units in scripts New commands: metrics units -- Display available unit identifiers metrics get -- Get at a particular metric value (with a specified unit) Extended commands: metrics set -- Support setting with a specified unit Extend functions OvmsMetrics.Value -- Optionally specify a unit (and make 'decode' work) and to get values with units. OvmsMetrics.GetValues -- Optionally specify a unit to get values with units. OvmsMetrics.AsFloat -- Optionally specify a unit New DukTape function OvmsMetrics.HasValue -- Returns true if the metric has a valid value. - Added power consumptions units: kWhP100K,KPkWh,MPkWh - Consolidate custom trip power consumption metrics to single value (kWhP100K) in Kia Niro and Kia Soul - VFS: sorted directory listings & recursive directory listings New commands: vfs rls <path> -- List <path> and all subdirectory contents - Vehicle: emit standard events on charge/generator connection type changes New events: vehicle.charge.type -- Vehicle charge connection type has changed (e.g. ccs/type2/…) vehicle.gen.type -- Vehicle generator connection type has changed - CAN logging: add possibility to log events (name) and metrics (JSON object with name, value, unit) New configs: [can] log.events_filters -- comma-separated list of filters (with possible wildcard) matching an event name [can] log.metrics_filters -- comma-separated list of filters (with possible wildcard) matching a metric name - Add units Bar, Permille - Add user configuration for groups of metrics Adds the 'ToUser' unit that converts to the user specified unit. Add -u to 'metrics list' to view metrics as user units. - Add completion for metrics set/get as well as units - Mini Cooper SE: Initial support - Hyundai Ioniq vFL: trip metrics, range estimations, TPMS, web configuration, charge type detection, charge speed & time estimation New configs: [xhi] ctp.maxpower -- Default charge power limit [kW] for charge time estimations, default 0 = unlimited [xhi] ctp.soclimit -- SOC level [%] for secondary charge time estimation (sufficient SOC), default 80 [xhi] notify.charge.delay.ccs -- Wait time [sec] for DC charge power to ramp up before sending the notification, default 15 [xhi] notify.charge.delay.type2 -- … same for AC charging, default 3 [xhi] range.ideal -- ideal new car range [km], default 200 [xhi] range.user -- typical current user range [km], default 200 [xhi] range.smoothing -- Number of SOC samples, default 10 = ~ 5% SOC [xhi] tpms.pressure.warn -- default 230 [kPa] [xhi] tpms.pressure.alert -- default 220 [kPa] [xhi] tpms.temp.warn -- default 90 [°C] [xhi] tpms.temp.alert -- default 100 [°C] New metrics: xhi.b.range.user -- actual current user range [km] xhi.e.state -- General/ignition state flags - Module: support deep sleep schedules New commands: module sleep -- Shutdown all components and enter deep sleep for a time span or until a specific time. - Add support for user-configured metrics in the web interface and plugins: Adds an extra 'units' stream from the websocket containing sub-streams: - metrics (for the current user unit/label for each metric) (subscribe to units/metrics) - prefs (for any user preferences for unit groups/types) (subscribe to units/prefs) Adds proxy arrays metrics_user[] , metrics_label[] available to plugin pages. Adds various browser javascript functions and methods for plugins related to displaying user configurations Auto-converts metric display to user units in plugins that use attributes - Cellular: add GPS/GNSS state control commands (for power management) New commands: cellular gps [status] -- output current modem GPS/GNSS subsystem status cellular gps start -- start modem GPS/GNSS subsystem cellular gps stop -- stop modem GPS/GNSS subsystem - CAN framework: add bus reset command New commands: can [can1…4] reset -- reset the CAN interface - Vehicle: add support for custom command handlers, see… https://docs.openvehicles.com/en/latest/userguide/scripting.html#ovmsvehicl… - Renault Twizy: read battery energy available from BMS (thanks to Martin Bitz) New metrics: xrt.b.energy.avail -- Current battery energy available [kWh] (aged) xrt.b.energy.full -- Maximum battery energy capacity [kWh] (aged, needs full charge) - Add button on web file editor to reload obd2ECU (when obd2ECU is enabled). - Vehicle: add support for a geofence for valet mode similar to parking/flatbed warnings. New Configs: [vehicle] valet.alarmdistance -- How far away from the original position before raising an alert (in metres) [vehicle] valet.alarminterval -- How often the alarm can be raised in minumtes - Add metric and events related to obd2ecu process: New metric: m.obdc2ecu.on -- Is the OBD2ECU process currently on. New events: obd2ecu.start -- Called after the OBD2ECU process is started. obd2ecu.stop -- Called before the OBD2ECU process is stopped. - Web UI: Add configuration for Valet and Flatbed geofence to the Locations config page. - Network: New 'network ping' command to ping (ICMP) hostname or IP address. (ESP-IDFv4+ only / needs to be enabled in menuconfig - Developer Options) - Vehicle: add automatic module shutdown/reboot based on 12V battery voltage level New configs: [vehicle] 12v.shutdown -- Shutdown voltage level (default: disabled) [vehicle] 12v.wakeup -- Reboot minimum voltage level after shutdown (default: any) [vehicle] 12v.wakeup_interval -- Reboot test interval in seconds (default: 60) New events: vehicle.alert.12v.shutdown -- 12V shutdown threshold reached, entering deep sleep - BYD Atto 3 initial support - Vehicle: add 12V shutdown delay & notification New configs: [vehicle] 12v.shutdown_delay -- Shutdown delay in minutes (default: 2) New events: vehicle.alert.12v.low -- 12V shutdown voltage level detected vehicle.alert.12v.operational -- 12V recovered above shutdown level New notifications: [alert] batt.12v.shutdown -- Alert about imminent 12V shutdown - VFS toolkit: add recursive options to mkdir (-p) & rmdir (-r) commands - Renault-Zoe-Ph1: add Cabin Pre-heat/cool Control Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

5 15

OBD poller module shell proposal
by Michael Geddes 26 Apr '24

26 Apr '24

Hi all, I know some of this (especially for the status) functionality is predicated on code that's not gone up yet - however this is allowing 'pause' and 'resume' of the poller (which has been merged). My question is not so much about the functionality and status information, but about the location of the *poller* subcommand. (See below). Should 'vehicle' be exclusively for switching the vehicle type? Should the 'poller' command be top-level? Under obdii? Thoughts welcome. If you do vehicle poller pause then the last line reads 'Vehicle OBD Polling is paused' //. -------8<---------------------------------------- *OVMS# vehicle ?* Usage: vehicle [list|module|poller|status] list Show list of available vehicle modules module Set (or clear) vehicle module poller OBD polling status status Show vehicle module status *OVMS# vehicle poller ?* Usage: vehicle poller [pause|resume] pause Pause OBD Polling resume Resume OBD Polling *OVMS# vehicle poller* OBD Polling running on bus 1 with an active list Time between polling ticks is 1000ms with 1 secondary sub-ticks Last poll command received 1s (ticks) ago. Vehicle OBD Polling is running.

4 18

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 02 Apr '24

02 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

OVMS on Transport Evolved
by Chris van der Meijden 25 Mar '24

25 Mar '24

Nikki Gordon-Bloomfield, a well known journalist and the ev youtube entrepeneur, has mentioned OVMS in her latest youtube "Transport Evolved" episode, entitled "Does Your Electric Car REALLY Need Telematics?": https://youtu.be/pucL1h_G8bg "Transport Evolved" has 151k subscribers, this is some nice advertisement for OVMS :-) Her call to support OVMS starts at minute 19. Regards Chris

2 1

V2 server not starting
by Derek Caudwell 24 Mar '24

24 Mar '24

Hi all, My ovms unit is regularly disconnecting from the V2 server with the message: State: Waiting for network connectivity Server is ready to start I'm on 3.3.003-696-g562479ea, I suspect it is happening when I either leave home or return (simple script turns on/off modem to use wifi). The V3 server does not have the same issue. Any ideas on debugging appreciated, as the network/wifi connection is up and stable? Also I finally got to the bottom of my issue with the 7600 modem, the daughter board's RX pin was not long enough causing intermittent connection to the main board. Cheers Derek

2 1

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

Support for Kia EV6?
by Douglas Urner 15 Mar '24

15 Mar '24

Is the Ioniq code close enough to the EV6 to allow reading the battery condition? I have a friend with an EV6 that won’t charge to full capacity. We’re suspicious that there is one or more bad cells, but so far the Kia dealer hasn’t been willing / able to tell her anything more than “we don’t find any problems”… Other suggestions for how to read the battery pack would also be most welcome. Thanks, Doug

2 1

Forum Notifications
by Mark Webb-Johnson 05 Mar '24

05 Mar '24

I’ve had to turn off email notifications for forum (and other such) posts. It was a useful feature, but despite running new user verification emails, captchas, and stopforumspam lookups, we keep getting spammers polluting the forums and that gets us repeatedly blacklisted by the over-zealous Spamhaus. So, email notifications are off for the foreseeable future. The forums see little traffic anyway, and we need a better approach (perhaps also for this mailing list). Discord? Google groups? Any ideas of something open and friendly? Regards, Mark.

3 2