Barra Recovery - Debug Logs

Debug Log Reasons

Updated at November 7th, 2025

Table of Contents

Barra Recovery General and Debug Logs On-Demand Tracking What's the Digital Input? Beacon Mode Standby & Moving Modes, Check-ins Magnet Other Log Reasons Further Debugging Information What's Next?

Barra Recovery General and Debug Logs

The Barra Recovery includes helpful debug logs to confirm the device actions and status:

On-Demand Tracking

Successful initiation of the ODT mode.

Debug[GEN][Info]: On Demand Tracking enabled, expires 17/06/2025 06:00:00

Successful cessation of ODT mode.

Debug[GEN][Info]: On Demand Tracking disabled

Incorrect initiation of ODT mode.

Debug[GEN][Info]: On Demand Tracking expiry set in the past

Successful expiry of ODT mode.

Debug[GEN][Info]: On Demand Tracking expired

Moving period initiated - When in ODT, returns selected acquisition results.

StartofTrip[....<chosen acquisition strategy results, i.e. cell tower or WI-FI MAC IDs and Digital and Analog values>

Locationless update while in ODT mode.

ElapsedTime[...

Moving period ended - When in ODT, returns selected acquisition results.

EndofTrip[...<chosen acquisition strategy results, i.e. cell tower or WI-FI MAC IDs and Digital and Analog values>

What's the Digital Input?

If you see a digital input value in the payload, it's because within the Standby Mode system parameter tab, the below field has been enabled. This activates a digital input value for use within an end-system (i.e. Telematics Guru) to determine the current mode of operation.

On-Demand Tracking Active Digital Input

Input X

Beacon Mode

Successful initiation of beaconing.

Debug[GEN][Sevr]: BEACON: ON exp 2942881792 (23,11796500,1000,5000)

Successful cessation of beaconing.

Debug[GEN][Sevr]: BEACON: off command given, turning beacon off

Successful expiry of beaconing.

Debug[GEN][Sevr]: BEACON: expired, turning off

Incorrect initiation (invalid expiry).

Debug[GEN][Sevr]: BEACON: poor expiry given, turning beacon off

Standby & Moving Modes, Check-ins

Device exits Standby Mode.

Debug[CON][Servr]: Exiting Standby Mode

Start-of-Moving (SoM) settings expired.

Debug[CON][Warn]: SoM settings expired

End-of-Moving (EoM) settings expired.

Debug[CON][Warn]: EoM settings expired

Start-of-Moving (SoM) check-in (configured via Digital Input).

StartofTrip[... <cell tower ID payload if enabled> ]

Check-in (periodic while in motion, locationless)

CheckIn[... <cell tower ID payload if enabled> ]

Standby Movement Digital Input (state change).

StandbyMovementDigitalInput[... <input index / value> ]

Trip end (returns selected acquisition results).

EndofTrip[... <Cell ID / GNSS / Wi-Fi MACs and analog/digital values> ]

Magnet

Activation mode enabled.

Debug[GEN][Sevr]: Activation mode enabled

Device enters Standby Mode.

Debug[CON][Sevr]: Entering Standby Mode

Magnet status flag updated.

Debug[GEN][Info]: Status flag MagnetAbsent=1, 0

Tamper mapped to digital input (state change).

DigitalInputChanged[... <Tamper input index / value> ]

Other Log Reasons

Trip-end with full acquisition results

EndOfTrip[... <Cell ID / GNSS / Wi-Fi MACs and analog/digital values> ]

Further Debugging Information

GPL (Get Primary Location).

The number next to the GPL or CheckIn represents the reason for getting a location and/or checking in. For GPL:

Bit 0 = end of trip
Bit 1 = on demand
Bit 2 = on demand once
Bit 3 = emergency

For CheckIn:

Bit 0 = Start of Trip
Bit 1 = End of Trip
Bit 2 = On Demand
Bit 3 = On Demand Once
Bit 4 = Check-In in Standby Mode (period elapsed) = Heartbeat.
Bit 5 = emergency

What's Next?

Read more about the Barra Recovery:

The following documents are withheld for security purposes. Contact your Digital Matter representative for further information.

Barra Recovery Asynchronous Message Commands
How to use a transceiver for last-metre device recovery
Complete downloadable user guide

Contact Us