This page starts from what you see and works back to the cause. Two tools do most of the work:
- The status LEDs on the logger (table on the Hardware page).
- The trip log of the trip on the Trip Data page, which lists what the logger reported; the Trip Log Messages page explains each message.
When the logger is not reachable from the cloud at all, the Device Web Manager over the Ethernet port shows the same information locally. Support is reached at vds.support@us.bosch.com; include the device’s IMEI and, where possible, a debug snapshot from the web manager’s Logs tab.
The device stays Offline
The Assignments page shows Offline and the green LED is not solid.
| Check | What it tells you |
|---|---|
| Power: is the supply between 9 and 36 V and the harness seated? | No LED at all means no power. After power-up the LEDs take a moment to start. |
| Green LED blinking for more than a few minutes | The logger is running but cannot reach the backend: usually no cellular connection. |
| Red LED blinking | A temporary error the logger keeps retrying, typically the cellular link. |
| Red LED solid | A permanent error; contact support with the IMEI. |
| SIM and SD card seated (under the cover) | A loose SIM shows as Unlock Required or Registration failing on the web manager’s modem card. |
| Antenna connectors | With a two-connector antenna, CELL1 goes to the bottom socket on the owa5X (top on the owa4X). A swapped antenna gives a weak or no signal. |
On the web manager, the Networks tab’s modem card shows Registration, Packet Service, Signal Quality, Operator and Failed Reason. “Registration: denied” or a missing operator points to the SIM or coverage; a good registration with no packet service points to the APN, which you can set with New Profile in the cellular section.
The device is Online but records no trips
| Check | What it tells you |
|---|---|
| Configuration column on the Assignments page | “No Configuration” means the logger has nothing to record. Assign one. |
Trip log message Measurement not started: no configuration set |
Same cause, seen from the device. |
| Device Details: are the buses of the configuration mapped to interfaces? | An unmapped bus shows a yellow Update button; the channels on that bus record nothing. |
| Is the vehicle awake? | The logger starts a trip when it sees CAN traffic or ignition, depending on the power settings. With the ignition off and a quiet bus there is no trip. |
A trip exists but one protocol has no data
Open the trip log and look for the channel in brackets, for example [CAN 1] or [XCP 1]:
| Message | Cause |
|---|---|
Interface is not available |
The bus is mapped to an interface that is not up, or wired to the wrong connector. Check the mapping in Device Details and the interface state on the web manager’s CAN tab. |
Missing bus configuration / Unable to find network for vehicle |
The channel’s bus is not mapped on this device. |
XCP connect failed ... or CCP connect failed ... |
The ECU did not answer: wrong instance or transport in the A2L, wrong bus, or the ECU is off. Since 1.7.0 a failing XCP or CCP channel keeps retrying on its own and no longer stops the other channels. |
A2L EPK mismatch |
The A2L does not match the software on the ECU; measurements may be read from wrong addresses. Upload the matching A2L. |
UDS: Connection error / UDS DTC: Connection error |
The ECU did not answer the Tx ID; check Tx and Rx IDs and the bus. |
OBD messages with Interface is not available |
The OBD bus is mapped to the wrong interface, or the vehicle’s diagnostic connector is not wired to it. |
Check the bit rate too: the web manager’s CAN tab shows error counters per interface, and its Detect Baudrate tool finds the rate of a live bus.
GPS is missing or wrong
- GPS must be switched on in the configuration’s OBD/GPS tab; the rate there gates collection.
- Positions need sky view; a logger inside a building reports nothing.
- On the web manager’s Device Configuration tab, the GPS CAN Interface should stay
vcan0unless the vehicle is meant to receive GPS frames. - Exclude GPS from MDF in the configuration, or Remove GPS location on export, deliberately leave GPS out of files while telemetry still carries it.
Data arrives late
Uploads share the cellular link with telemetry. Large MF4 recordings, a high telemetry rate, or a weak signal delay the trip files; the trip stays Active until the logger finishes. The Data Ingest view on the General Configuration page shows how much the vehicle sends. Reduce rates or the number of signals if the link cannot keep up.
Times look wrong
Timestamps are recorded in UTC and shown in the browser’s time zone. Set the vehicle’s Timezone attribute on the Vehicles page so exported files carry the local zone. A logger with no GPS fix and no network for a long time can drift; it resynchronises as soon as it connects.
The device sleeps or wakes unexpectedly
Wake and sleep follow the power settings of the logger: CAN activity and ignition (T-15) as sleep and wake triggers, a check duration and a sleep delay. The trip log records Device going to sleep due to power settings (No CAN / No T-15) and the restart messages. The settings are on the web manager’s Power Management tab. If the ignition plug of the harness is not connected, T-15 cannot wake the device; leave the ignition trigger off in that case.