New Events page: describe situations in your vehicle data as event definitions with start and end conditions written in a small expression language, with calculated signals, extra signals to summarise, a minimum duration and a capture window. Expressions are checked as you type, with signal completion from the configuration’s dictionaries.
Cloud runs: evaluate a definition over the recorded trips of a vehicle, configuration or time range. A preview shows how many trips and how much data a run covers before it starts.
Run results: every occurrence with its trip, start, duration and trip time, a summary of the involved signals, and CSV and JSON downloads.
The trip files dialog has one Format picker; export a single file from its row or select several and export them together, with a count of successes.
New BLF export of the CAN traffic, and OBD Snapshot exports as HTML and JSON.
Built-in OBD snapshot viewer: view the diagnostic report of one file or of the whole trip in the application, filter it, and download it.
Exported MF4 files carry the trip, device, vehicle, configuration and the vehicle’s attributes such as the VIN in their metadata.
Exclude GPS from MDF in a configuration keeps position data out of the files recorded on the device; Remove GPS location strips it from a converted download.
Data Dictionaries
Every dictionary has a Source, the measurement its signals are stored under. Set it per file or for several files at once with Set source, for example to keep the buses of two vehicles apart in Grafana.
Trips
Filter the trip list by Status (Error, Warning, OK, Unknown).
Configurations
XCP .lab import offers Import (Replace) and Import (Append).
Import and export of configurations report success and failure clearly, and exported files can be imported again as they are.
Signal catalogs are built per channel when a configuration is saved, which makes the event editor’s completion fast even for large A2L files.
Devices
Recording can be started, stopped and split into a new trip locally through the device web manager’s API, without the cloud.
Base-image updates over the air, with automatic rollback if the new image does not boot.
A failing bus or ECU no longer stops the rest of the recording: each XCP and CCP channel reconnects on its own, and a protocol that cannot start is skipped instead of aborting the trip.
API and CLI
The vds command-line client now covers the whole API: event definitions, expression checks and cloud runs (vds events), the device status log (vds devices status-log), users (vds users), the trip status filter, signal catalogs (vds configs catalog) and the datasource server (vds dss). Every command explains itself with --help, and the project connection is set up with vds tenants add-url. See the new Command-line Tools page.
New API endpoints for event definitions and runs, signal catalogs, user management, the device status log, and the trip status filter. The API reference now describes every operation and field; the DSS API has its own reference page.
Important Changes:
Event definitions and signal catalogs. The signal catalog of a configuration now contains only the signals the configuration selects. An event definition that referenced a dictionary signal outside the selection is rejected until the signal is added to the configuration. A configuration saved before this release must be saved once more before its catalog is available to the event editor.
Dictionary sources. A changed source takes effect when the configurations using the file are saved again; earlier data stays under the old measurement in Grafana.
Configuration export format. Exported JSON wraps the settings under a spec key. Tools that read exported files need to expect it.
Event summaries now include the sample that started the event, so counts, minimum, mean and maximum of runs differ slightly from runs made with earlier releases.
Device status is stored in a new status log; the trip log of trips recorded before the upgrade is still available.
Bug Fixes:
Fixed a reprocessed or redelivered trip file being listed twice in the trip files of a trip
Fixed a cloud run reporting success when some of its trips could not be evaluated; the run now names how many trips failed and the most common reason, and is marked failed when no trip was analysed
Fixed run start, completion and modification times shown shifted by the server’s time zone
Fixed the event editor failing to open configurations with a very large A2L or DBC (the signal catalog exceeded the response size limit)
Fixed the last column of every table running into the table edge
Fixed device health (collectd and rcuinfo) missing from the monitoring dashboard
Fixed delay() and filter() with a non-literal argument crashing the expression check instead of reporting an error
Fixed delay() failing for signals whose names contain a dot
Fixed the reason of a failed trip file conversion not reaching the browser
Fixed a failing bus or protocol stopping the rest of the recording on the device
Fixed a device staying awake, with XCP, OBD, UDS and DTC collection stopped, for the rest of its uptime after an aborted shutdown
Fixed downloaded MF4 files having an empty metadata block