Commonly Seen Device Logs/Errors

Updated at April 30th, 2025

Table of Contents

Debug[COM] Logs Debug[GEN] Logs Debug[GSM] Logs Debug[ACC] Logs Debug[GPS] Logs Commonly Seen Reset Logs Reset Reasons Watchdog Reset Reasons Watchdog Reset Reasons - Manually Initiated Resets Battery-Powered Watchdog Reset Reasons Powered Watchdog Reset Reasons Device Caused Resets - Watchdog Reasons

This article shows a list of commonly seen debug log messages sent by devices. They can be viewed here - View Device Logs. By default, "Severe" logs are recorded by the device and uploaded to the server.

Not every log indicates a problem, sometimes it is just an event that we feel is useful to record. An example would be a few logs showing connection errors that are worth logging, but might just indicate the device was out of coverage for a little bit, and not an error/issue.

Deciphering some logs can be complex - and is best left to the Digital Matter Support team.

Some logs might point to a problem. The logging level can be changed like so - Turn on Debug Logging - to provide more detailed logging information.

Debug[COM] Logs

Log Reason	Explanation	Solution
Debug[COM][Sevr]: Invalid command received	Issue communicating with Bluetooth module, Bluetooth® module shuts down, no other effect on device operation	Try upgrading your Bluetooth® firmware and device firmware to the latest versions for compatibility
Debug[COM][Crit]: Unsupported BLE version 0001024E. Turning off.	The Bluetooth® firmware is not compatible with the current device firmware	Try upgrading your Bluetooth firmware and device firmware to the latest versions for compatibility

Debug[GEN] Logs

Log Reason	Explanation	Solution
Debug[GEN][Crit]: VBat = 6124 mV, Reset = 0X4, Watchdog = 0X1	This is the Battery voltage and if there's a Reset reason the code is detailed here	For Common reset reasons, see below If you are seeing RESET = 0x14, change batteries as soon as possible.
Debug[GEN][Sevr]: JAMW	GPS Jamming or Interference detected	See GPS Jamming and Interference Detection : Digital Matter Support

Debug[GSM] Logs

Log Reason	Explanation	Solution
Debug[GSM][Sevr]: Aborting oneshot reg	Device can't register onto the cellular network If the unit has been connecting before it generally just indicates a coverage issue at the time of the log. Or you have set your registration timeout too short in the Upload Parameters	In most cases no action is required. The device will report these logs when it's been out of coverage and unable to register.
Debug[GSM][Sevr]: Aborting oneshot data	Device could register on the network, but the upload failed.	Generally coverage related and intermittent. Could be a server issue if on a 3rd party server (server closing connection during upload)
Debug[GSM][Sevr]: Aborting oneshot APN	Device could not register onto the network due to an incorrect APN defined	A correct APN needs to be set using a DM Link. (A DM Link is needed as the device would not be able to go online to download the APN from a server)
Debug[GSM][Sevr]: Hard Error: `AT` (0/3), LastRx: ``	Modem is not responding after initial startup. The device resets the modem. This can happen on devices which use the SARA Modem intermittently.	Part of normal device operation. No action required. If there are many of these logs consistently, it may point to a signal/device issue
Debug[GSM][Sevr]: Hard reset	The device has hard reset the modem. Can occur after the Hard Error above (to recover from the modem error)	Update your device to the latest firmware. Modem error recovery is better handled in the latest versions. Underlying issues may be poor reception, too tight system parameters for modem
Debug[GSM][Sevr]: Modem turn off failed	The device was unable to shut down its modem because the modem was busy/mid-operation	Update devices to latest firmware. Modem shutdown is better handled in the latest versions.
Debug[GSM][Sevr]: Hard Power Down	The modem was not responding, so the firmware reset it to recover back to normal operation.	No action is required. Points to an issue occurring during data upload. If there are many of these logs occurring regularly, it may point to a signal/device issue
Debug[GSM][Sevr]: Socket leak detected	The modem did not close the connection properly	Generally intermittent and no action required. This is fixed by either a soft reset or a hard reset and is generated from a modem bug in the uBlox module
Debug[GSM][Sevr]: Doing EMERG_OFF	When the unit shuts down, it instructs the modem to turn off before removing the power. If the Modem module takes too long to shut down, it gets forced off.	No issue, regular operation.
Debug[GSM][Sevr]: HTTP fail online-live2.services.u-blox.com:80 0/0	The device has not been able to download GPS Aiding data from uBlox Generally due to a connectivity issue	See 4G connectivity troubleshooting article here
Debug[GSM][Info]: APN xyz,, Debug[GSM][Info]: Exhausted APNs xyz,,	The device has an APN set to connect to the network. The modem has tried to use this APN and could not get online	Generally - no issue, this is the correct operation, it shows that the modem has been prevented from joining the 'wrong' network - particularly with roaming SIMS which may try to join the wrong one.
Debug[GSM][Warn] Soft Error: `AT+CPIN?` (9/9), LastRx: ` ERROR `	The device SIM pin command to the SIM failed. This is usually due to the SIM not being inserted properly, but can also occur if a SIM has a unique user set pin.	Checking the SIM installation will usually fix this issue. Ensure the SIM is oriented the right way, and that the holder is properly closed for micro form factor SIMs.
Debug [GSM][Info] CEREG = 90	This means the SIM is not being registered due to UICC (Universal Integrated Circuit Card) failure. Potential issue with the SIM making contact with the contacts on the device.	Try and remove and reinsert the SIM in case it is just an insertion problem,try a new SIM card, try cleaning contacts with isopropyl alcohol (if it looks like there is residue built up on them), contact support if these do not resolve the issue.
Debug[GSM][Sevr]: SMS APN=M2M	The device received the SMS APN command. APN was set to “M2M”	No issue, regular operation. SMS Commands
Debug[GSM][Sevr]: Modem Freeze Reason	Seen on devices using Nordic Modem	Occurs when the device is in certain locations with poor coverage. Device will recover when it gets back to coverage. Update to latest device firmware and modem firmware.
Debug[GSM][Sevr]: GPS Error Hold Off!	Occurs on devices with the Sony GNSS - when the firmware is waiting for the module to turn off, but it continues to send sentences. The firmware simply shuts off the GNSS and logs this message	No action required - logs should be sporadic and device will recover. If they are occuring constantly there may be a device issue requiring it to be changed over.
Debug[GSM][Sevr]: Timeout Waiting for CTS	The cellular modem is not responding These logs will not appear in OEM, since if the modem can't respond, the device can't upload data. It indicates a fault with the modem. These faults would be seen if you are reading the logs via the Wired Provisioning Tool	Replace the device if it is not connecting.
Debug[GSM][Sevr]: ?URC=+ESMCAUSE:33	This error is a network error that usually arises from the modem attempting to connect to the server outside of the network session.	We have seen this on the Global devices particularly, but it shouldn't be a concern if it happens intermittently.However, if it's happening a lot, it could be a symptom of a bad network configuration. See Configuring Network Settings.

Debug[ACC] Logs

Log Reason	Explanation	Solution
Debug[ACC][Crit]: Tumbler triggered cos^2<0	Accident detected - see Accident Detection	This happens when the device has a sudden change in velocity or change in angle. This is common when provisioning - as a device not secured to a vehicle can easily be ‘thrown’ about (comparitively) in one's hand.
Debug[ACC][Crit]: Accel error in State_Cfg	The device cannot talk to the accelerometer module	If there are continous error logs, this suggests a hardware fault. Replace device.
Debug[ACC][Crit]: Roll detected cos^2<383553884,id=358737579,log=0,detail=0	The vehicle has rolled over.	This is very common if you flip the device over when it is not installed in a vehicle. Accident Detection and Reconstruction + Accident Data Exports
Debug[ACC][Crit]: Roll reset	The vehicle has returned to its upright position after having rolled over.	As above.
Debug[ACC][Crit]: Accident detected mag^2=6028,id=358673786,log=0,detail=0	The device has detected significant impact, suggesting that an accident has occurred.	As above - very common if the device is moved/bumped when not installed - during provisioning or installation. Otherwise can just indicate a harsh jolt when driving if the threshold is set too low - or the device is not properly secured.

Debug[GPS] Logs

Log Reason	Explanation	Solution
Debug[GPS][Info]: Bad length: NMEA/PMTK: SGNRMC, 031855.40$PMTK011,MTKGPS08 .000,A,D57 7	This log occurs when the device is switching between the binary and NMEA formats as there is often no assurance of sentence completion during the switchover process.	This log should not prevent the device from obtaining a GPS fix, however it's advisable to update the device to the latest firmware version.
Debug[GPS][Crit] Error - off	The device has failed to get a response from the GNSS module. This could be due to damage to the module from static discharge or higher than recommended voltage, or could be a temporary error that resolves itself.	Ensure your installation is not applying too much voltage device. If the issue does not resolve itself, contact support.
Debug[GPS][Crit]: CheckAwake fail	GPS module is failing to start.	Replace the device.
Debug[GPS][Sevr]: Error -22 in CEPW	This log occurs when there has been a failure in sending aiding data to the GPS.	No action required. The GPS may believe the aiding data that has been downloaded is corrupt in some way. Wait a day or two to allow the device to re-download the next set of GPS aiding data from the server. The GPS aiding data slot version may be used as a reference to see when the next set of aiding data has been downloaded.
Debug[GPS][Sevr]: ?URC =	This means the modem sent a message but the message didn't have a handler so it is getting logged.	Can occur sporadically No actions are required.

Commonly Seen Reset Logs

When a device resets, you will typically see a log such as the one below:

Debug[GEN][Crit]: VBat = 4888 mV, Reset = 0X4, Watchdog = 0x1

There are two values that are of interest here - the reset and watchdog reset reasons. The reset reasons tell you what kind of reset occurred - typically either a power on, brownout, or a firmware-initiated reset. If the firmware initiated the reset, then the watchdog reason will tell you why.

Reset Reasons

The following are the most common reset reasons:

Reset Reason	Explanation	Applicable Devices
0x1	Power on reset. This mainly occurs when power is first supplied. It can also occur during severe brownouts.	All DM devices.
0x2	Brown out reset. The voltage dipped below the brown out threshold. Typically seen when batteries are depleted. Battery insertions can also appear as brownouts occasionally.	All DM devices.
0x4	Watchdog reset. The firmware reset the device. The reason it did so is detailed by the watchdog reset reason.	All DM devices
0x10/0x14	Under voltage lockout reset. The voltage dipped below the minimum voltage threshold. Typically seen when batteries are getting low.	Battery powered devices.
Reset=2/Reset=6	Under voltage lockout (UVLO) reset. Seen on devices using Nordic modem. The voltage dipped below the minimum operating voltage threshold.	Battery powered devices
0xA	Reset from Provisioning Tool	All DM devices
0xC	Brown out reset	All DM devices
0x8	Power on reset & brown out	All DM devices
0x110/0x101	Indicative of flash issues. 0x101 being an issue reading the flash, and 0x110 being an issue powering the flash.	All DM devices

Watchdog Reset Reasons

Watchdog reasons less than 0x100 are manually initiated resets, whilst watchdog resets greater than or equal to 0x100 are caused by the device resetting itself to try and rectify an error state. The watchdog reasons greater than 0x100 tend to be device-specific and are far less frequent so are not included here for brevity.

Remora3 4G, Oyster3 4G, Yabby3 4G, Hawk Cellular

Watchdog Reset Reason	Explanation
0x0	Either not a watchdog reset, or an unknown error occurred.
0x1	App reset. This occurs when the device resets itself due to changed conditions. Typical reasons include: The parameters were updated Firmware was downloaded The device must switch to recovery mode/back to normal operation A reset async message was received
0x2	No comms. The device could not communicate with the server for 3 days or more. The device resets itself to retry an upload with loose upload restrictions. This also triggers the use of backup admin params when applicable.
0x100	GPS module failed to power on
0x101	GPS module failed to power off
0x102	Modem failed to power on
0x103	Modem failed to power off

Barra Core, Edge, GPS

Watchdog Reset Reason	Explanation
0x123	Modem Fault Lockup Occurs when cellular modem is not responding, which is indicated by logs such as “Timeout Waiting for CTS”. This signifies a fault with the modem - if the modem cannot respond, the device cannot upload data.
0x124	Modem Fault Recursion This can occur in certain locations with poor coverage. The device will typically recover once it moves to a location with better coverage. Updating to the latest device and modem firmware versions can help resolve this issue.
0x125	Flash bad access This error indicates an issue related to the device's flash memory.
0x126	Flash unaligned write This error occurs when there is an attempt to write data to the flash memory in an unaligned manner. Ensure that the device firmware is up-to-date.
0x127	Activation going dormant This error occurs when the device's activation process enters a dormant state, triggering a watchdog reset. Ensure that the device is in an area with adequate network coverage and verify that the device firmware is up-to-date.
0x128	Activation awakening This error occurs when the device's activation process is transitioning from a dormant state to an active state, triggering a watchdog reset.
0x129	Flash chip erase in flash This indicates that the device encountered a problem while attempting to erase data on the flash memory chip, and the watchdog timer responded by resetting the device.
0x130	Flash Unaligned Erase This error occurs when there is an attempt to erase data from the flash memory in an unaligned manner, triggering a watchdog reset.

Watchdog Reset Reasons - Manually Initiated Resets

Watchdog Reset Reason	Explanation	Applicable Devices
0x0	Either not a watchdog reset, or an unknown error occurred.	All DM devices.
0x1	App reset. This occurs when the device resets itself due to changed conditions. Typical reasons include: The parameters were updated Firmware was downloaded The device must switch to recovery mode/back to normal operation A reset async message was received	All DM devices.
0x2	No comms. The device could not communicate with the server for 3 days or more. The device resets itself to retry an upload with loose upload restrictions. This also triggers the use of backup admin params when applicable.	All DM devices.
0x3	SMS reset. The device received an SMS command to reset. On some devices, the app reset (0x1) is used instead.	Mainly powered devices.
0x4	Async message reset. The device recieved an async message command to reset. On some devices, the app reset (0x1) is used instead.	Mainly powered devices.
0x7	Modem brownout. The device has received insufficient voltage and thus the modem is unable to power up properly to connect.	Mainly powered devices.

Battery-Powered Watchdog Reset Reasons

Watchdog Reset Reason	Explanation	Applicable Devices
0x5	Backup admin parameters expired. The device was testing the backup admin parameters and is now reverting back to the standard admin parameters.	Battery powered devices.
0x106	Occurs when the device fails to verify what it has written to the flash.	Battery powered devices.

Powered Watchdog Reset Reasons

Watchdog Reset Reason	Explanation	Applicable Devices
0x5	Under Voltage Vockout (UVLO) reset. The UVLO was triggered. This is typically seen when the external voltage is too low and the backup battery is depleted.	Powered devices.
0x6	Backup admin parameters expired. The device was testing the backup admin parameters and is now reverting back to the standard admin parameters.	Powered Devices.

Device Caused Resets - Watchdog Reasons

Watchdog Reset Reason	Explanation	Applicable Devices
0x100	Flash verification failed	Powered devices.
0x102	Bad Header Pointer	Older Generation Devices, e.g. Oyster2
0x114	Modem Freeze	Can occur in isolated areas. Device will typically recover once it moves location. Update to the latest device and modem firmware versions to resolve.

Contact Us