The trip log of a trip (the health icon on the Trip Data page) lists the messages the logger reported while recording. This page explains them. Messages are quoted exactly as the logger writes them, so you can search for them.
Reading a message
- Messages about one channel of the configuration start with the channel in brackets:
[CAN 1],[XCP 1],[UDS 1],[RMBA 1], numbered in the order of the configuration, or[OBD <bus name>]for OBD. Messages without a prefix concern the whole device. - Severity: Error means the channel or the device could not do what the configuration asked; Warn is something to look at; Info is normal operation.
- A message that repeats is shown once with a repeat count.
Device and recording
| Message | Meaning | What to do | Severity |
|---|---|---|---|
Measurement not started: no configuration set |
The device has no configuration assigned. | Assign one on the Assignments page. | Warn |
Starting MF4 recording for assigned configuration |
The configuration has Create MDF on; files are being written. | Nothing. | Info |
No MF4 recording enabled for assigned configuration |
Create MDF is off; only telemetry is sent. | Enable it in the configuration if you want files. | Info |
Starting can monitor for the following CAN interfaces: ... |
The device watches these interfaces for bus activity (wake and sleep). | Nothing. | Info |
Stopping data collection due to Wake/Sleep settings, configuration update or watchdog timeout |
The trip ended: the device goes to sleep, received a new configuration, or restarted its measurement service. | Nothing, unless it repeats without a reason you know. | Info |
Device going to sleep due to power settings (No CAN / No T-15) |
Sleep triggers fired: no bus activity and no ignition. | Nothing. Adjust the power settings on the web manager if the device should stay awake. | Info |
data collection restarted due to sleep timer being reset (T-15 / Wake_on_CAN input) |
A wake trigger cancelled the countdown to sleep. | Nothing. | Info |
data collection failed to restart due to sleep timer being reset (T-15 / Wake_on_CAN input) |
The restart after a cancelled sleep failed. | Check the following messages; contact support if it repeats. | Error |
RCU awake |
The device woke up. | Nothing. | Info |
CAN
| Message | Meaning | What to do | Severity |
|---|---|---|---|
Missing bus configuration |
The channel has no bus selected. | Select a bus on the channel’s tab. | Error |
Error in bus configuration |
The channel’s bus or dictionary could not be loaded. | Re-save the configuration; check the dictionary parsed without errors. | Error |
CAN: Unable to find network for vehicle, check configuration |
The bus of the channel is not mapped to an interface on this device. | Map it in Device Details. | Error |
Interface is not available |
The mapped interface is down or does not exist. | Check the mapping and the interface state on the web manager’s CAN tab. | Error |
Interface creating failed, check Bus/Interface settings |
The interface could not be opened. | Same as above; check the bit rate. | Error |
Device socket error, check device CAN configuration / connection error |
The CAN socket failed while recording. | Check the wiring and the bus; contact support if it repeats. | Error |
unable to set filters |
The message filters for the selected signals could not be applied. | Re-save the configuration; contact support if it repeats. | Error |
OBD
| Message | Meaning | What to do | Severity |
|---|---|---|---|
Starting OBD data collection |
OBD polling started on the configured bus. | Nothing. | Info |
Interface is not available (with the [OBD ...] prefix) |
The OBD bus is mapped to an interface that is down. | Check the mapping and wiring of the diagnostic connector. | Error |
Missing bus configuration (with the [OBD ...] prefix) |
OBD is enabled without a bus. | Select a bus on the OBD/GPS tab. | Error |
OBD polling adapts itself: if the vehicle answers slowly, the interval is stretched so that OBD never takes more than 80 percent of the bus time. That is reported as an informational message and is not an error.
XCP
| Message | Meaning | What to do | Severity |
|---|---|---|---|
Missing A2L file configuration / Invalid A2L file / Error in A2L file / Error loading configuration from A2L file, check that A2L is correct |
The A2L is missing or could not be parsed. | Choose or re-upload the A2L. | Error |
XCP: Unable to find network for vehicle, check configuration / Missing interface for XCP on CAN |
The channel’s bus is not mapped on this device. | Map it in Device Details. | Error |
Network interface [...] not found, check configuration |
The mapped interface does not exist on the device. | Fix the mapping. | Error |
XCP: Selected transport is not supported, check XCP instance in configuration |
The instance’s transport is not one the logger can use. | Pick another instance in the A2L. | Error |
XCP connect failed, verify configuration and interface are correct, verify ECU is online and connected |
The ECU did not answer the connect request. | Check bus, instance and that the ECU is powered. The channel keeps retrying by itself. | Error |
XCP session start failed, check physical interface settings / ECU and bus status |
Connected, but the measurement session could not start. | Check the bit rate and the ECU state. | Error |
XCP DAQ capabilities failed, check ECU and bus status |
The ECU did not report its DAQ capabilities. | Check the ECU; try again. | Error |
XCP: ECU memory overflow, too many DAQ lists, reduce configuration size |
The selection does not fit into the ECU’s DAQ memory. | Remove measurements or move them to fewer rasters. | Error |
XCP unlock failed, check .so file, attemping to continue anyways... |
The Seed and Key library did not unlock the ECU. | Upload the right .so for this ECU. |
Error |
A2L EPK mismatch: ECU=... A2L=... |
The A2L’s software identifier differs from the ECU’s. | Upload the A2L that matches the ECU software. | Warn |
A2L EPK match: ... |
The A2L matches the ECU software. | Nothing. | Info |
no DAQ data received from ECU for 10 seconds, restarting XCP data collection loop / DAQ read cycle timeout, no response from ECU after 10 seconds, restarting XCP data collection loop |
The ECU stopped sending; the channel reconnects. | Nothing unless it repeats; then check the bus load and the rasters. | Info |
maintain connection is active, will keep ecu on countdown |
The channel keeps the ECU awake while the device counts down to sleep. | Nothing. | Info |
Failed to extract signal from daq sample / Failed to write signal into MF4 from daq sample: ... |
One sample could not be decoded or written. | Nothing unless frequent; then check the A2L. | Info |
XCP: Configuration error |
The channel’s settings are inconsistent. | Re-save the configuration. | Error |
XCP over Ethernet (xETK)
| Message | Meaning | What to do | Severity |
|---|---|---|---|
XETK device discovered with MAC address [...] and IP [...] |
The xETK was found on the Ethernet port. | Nothing. | Info |
Error attempting to discover XETK device on [...], check for mismatch between target IP and device IP |
No xETK answered. | Check the cable, the xETK power and the IP in the A2L instance. | Error |
Invalid XETK remote IP [...], check configuration / Target IP [...] does not match any local network on [...], check configuration |
The IP in the A2L does not fit the device’s Ethernet network. | Correct the IP in the A2L instance. | Error |
Reassigning XETK IP address from [...] to [...] |
The logger moved the xETK to a usable address. | Nothing. | Info |
Error attempting to reassign IP address / Error attempting to setup XETK IP management for [...], please contact support. |
The address change failed. | Contact support. | Error |
CCP
| Message | Meaning | What to do | Severity |
|---|---|---|---|
CCP: Error loading configuration, verify configuration is setup properly / CCP: Interface not specificed |
The channel’s settings or bus are incomplete. | Select a bus; re-save the configuration. | Error |
CCP plugin creation failed, verify configuration and interface are correct |
The channel could not be set up. | Check the A2L and the bus. | Error |
CCP connect failed, verify configuration and interface are correct, verify ECU is online and connected |
The ECU did not answer. | Check bus and ECU power. The channel keeps retrying by itself. | Error |
Error exchanging id: ... |
The ECU rejected the station address. | Check the CCP instance in the A2L. | Error |
seed and key unlock failed, check .so file |
The Seed and Key library did not unlock the ECU. | Upload the right .so. |
Error |
CCP session start failed, check physical interface settings / ECU and bus status |
Connected, but the measurement could not start. | Check the bit rate and the ECU state. | Error |
CCP daq failed to to be created, check configuration |
The DAQ lists could not be set up. | Reduce the selection; check the rasters. | Error |
CCP collector failed, make sure connection to ECU is sound and verify A2L / configuration |
The channel stopped after repeated errors. | Check wiring, A2L and configuration. | Error |
CCP measurement succesfully setup, started measurement cycle |
Measurement is running. | Nothing. | Info |
DAQ read cycle timeout, no response from ECU after 10 seconds, restarting XCP data collection loop |
The ECU stopped sending; the channel reconnects (the message says XCP for CCP too). | Nothing unless it repeats. | Info |
maintain connection is active, will keep ecu on countdown |
The channel keeps the ECU awake while the device counts down to sleep. | Nothing. | Info |
Failed to extract signal from daq sample: ... |
One sample could not be decoded. | Nothing unless frequent. | Warn |
UDS and UDS - RMBA
| Message | Meaning | What to do | Severity |
|---|---|---|---|
UDS: Error in bus configuration / Missing bus configuration and dtc disabled |
The channel has no usable bus, and nothing to do. | Select a bus; enable Collect DTCs or select identifiers. | Error |
Error in Txid string / Error in Rxid string |
The Tx or Rx ID is not valid hexadecimal. | Enter them as 0x.... |
Error |
UDS plugin creation failed, verify configuration and interface are correct / RMBA plugin creation failed, verify configuration and interface are correct |
The channel could not be set up. | Check the definition file, the A2L and the bus. | Error |
UDS: Connection error |
The ECU did not answer a request. | Check Tx and Rx IDs, the bus and that the ECU is awake. | Error |
UDS DTC: Connection error |
The DTC request got no answer. | Same as above. | Error |
Errors you cannot fix from the configuration
If a message says to contact support, or an error repeats on every trip after the configuration and the mapping have been checked, contact vds.support@us.bosch.com with the IMEI, the trip start time and the trip log (Download in the Trip Logs dialog).
The Log Across Trips
Since release 1.7.0 the logger’s messages are stored in a status log that spans trips. The web application shows the log per trip; the REST API and the vds command-line client also read it per device for the last 90 days (GET /devices/{id}/status-log, vds devices status-log <device-id>), which shows what happened between trips, for example while a device was trying to connect. The log of a trip recorded before the upgrade is still available per trip. The Command-line Tools page shows the commands.