Pending DTC Info

The PENDING_DTC_INFO event is generated when the OBD-II system detects pending Diagnostic Trouble Codes (DTCs) in a vehicle. Pending DTCs are early indicators of potential issues that have been detected but not yet confirmed as permanent faults. This event helps monitor vehicle health, identify repeated issues, and perform proactive maintenance.

Event Type: PENDING_DTC_INFO

Enablement Package: NA

Trigger Condition

  • The PENDING_DTC_INFO event must be subscribed by the customer.
  • The event will be triggered whenever the vehicle’s ECU (Electronic Control Unit / Engine Control Unit) identifies a pending Diagnostic Trouble Code.

Example Payload

{
"inputBit7": 0,
"partialUpdate": false,
"inputBit4": 0,
"voiceCallActive": 0,
"inputBit3": 0,
"inputBit6": 0,
"inputBit5": 0,
"type": "PENDING_DTC_INFO",
"deviceId": "7b9ec524-8059-11ec-91e8-c1b4ab6f81d2",
"networkService": 0,
"commStateConnected": 0,
"messageType": "PENDING_DTC_INFO",
"messageIndex": "16078646",
"dimentionFix": 0,
"lastKnownLon": -90.5253357,
"inputBit0": 0,
"inputBit2": 0,
"id": "1c006e23-1101-46ce-8260-f7add74896a4",
"state": null,
"inputBit1": 0,
"commStatusAvaliable": 0,
"locality": null,
"eventIndex": 0,
"assetNo": "",
"fixStatusCorrected": 0,
"deviceSerial": "1062505290",
"groupName": "Azuga Northeast",
"lastKnownTime": 1663891316000,
"jmsType": "",
"vehicleName": "Zia's Vehicle",
"deviceTypeId": 1,
"destinationQueues": null,
"city": null,
"latitude": 38.6210808,
"unitStatus": 0,
"invalidFix": 0,
"dataService": 0,
"noOfAccums": 0,
"customerId": 1059,
"beaconMacAddress": null,
"tripNumber": 711,
"spare": 0,
"address": null,
"roaming": 0,
"messageEventType": null,
"stateId": 0,
"updateTime": null,
"userId": "8a9388a8-7dd7-5b7e-017e-c0a7a85c5e35",
"batteryPercentage": 0,
"currentState": 0,
"deviceProtocolMessageId": null,
"messageEventTypeId": 0,
"zipCode": null,
"country": null,
"deviceAssociatedVIN": "1G1PF5SC0C7208921",
"beaconType": null,
"groupId": "bb443197-af0f-11ea-87f7-712f0c9121d3",
"vendorTypeId": 1,
"firmwareVersion": null,
"fixStatuslastKnown": 0,
"fixStatusHistoric": 0,
"longitude": -90.5249991,
"satellites": null,
"locationTime": 1663891337000,
"odometer": 209870,
"offset": -300,
"virtualTripEnd": false,
"imei_meid": "352602114115360",
"insideHOO": true,
"timeOfFix": null,
"sensorNames": null,
"tripPolyline": null,
"lastKnownLat": 38.6207052,
"fixQuality": 0,
"unitStatusBit0": 0,
"unitStatusBit2": 0,
"unitStatusBit1": 0,
"unitStatusBit3": 0,
"storedLocation": false,
"protocolVersionIdChange": true,
"accumesList": null,
"accumulators": null,
"fixStatusPredict": 0,
"network3G": 0,
"lastKnownAddress": "14442 Clayton Rd, Ballwin, MO 63011, USA",
"privacyModeEnable": false,
"fixStatus": 0,
"vehicleId": "7b9ec523-8059-11ec-91e8-79d8a6a932aa",
"lastKnownFixQuality": 0,
"dtcMessageRecords": [
{
"dtcType": 0,
"failureMode": 0,
"subType": "DTC_MESSAGE_RECORD_OBD",
"dtcMessage": "0171"
},
{
"dtcType": 0,
"failureMode": 0,
"subType": "DTC_MESSAGE_RECORD_OBD",
"dtcMessage": "0299"
}
],
"dtcCount": 2,
"userName": "Bruce Driver",
"tripState": "ACTIVE",
"messageTypeId": 51,
"obdSpeed": null,
"location": {
"latitude": 38.6210808,
"longitude": -90.5249991
},
"commonState": 0,
"carrierId": null
}

Reference

Field

Description

type
String

Type of event.
Example: PENDING_DTC_INFO

deviceId
String,UUID

Unique identifier of the device.
Example: 7b9ec524-8059-11ec-91e8-c1b4ab6f81d2

messageType
String

Type of message.
Example: PENDING_DTC_INFO

lastKnownLon
Double

Last known longitude of vehicle in degrees.
Example: `-90.5253357

id
String,UUID

Unique identifier of the message.
Example: 1c006e23-1101-46ce-8260-f7add74896a4

deviceSerial
String

Serial number of the device.
Example: 1062505290

groupName
String

Name of the assigned group.
Example: Azuga Northeast

lastKnownTime
TimeStamp

Last known time in milliseconds.
Example: 1663891316000

vehicleName
String

Name of the vehicle.
Example: Zia's Vehicle

deviceTypeId
Integer

Type ID of the device, 1-Datalogger
Example: 1

customerId
Integer

Unique Azuga ID of the customer.
Example: 1059

tripNumber
Integer

Represents a unique ID assigned to a specific trip, allowing the system to track and reference that particular journey or route.
Example: 711

userId
String,UUID

Unique ID of the user.
Example: 8a9388a8-7dd7-5b7e-017e-c0a7a85c5e35

deviceAssociatedVIN
String

VIN associated with the device..
Example: 1G1PF5SC0C7208921

groupId
String,UUID

Unique Identifier of the Group.
Example: bb443197-af0f-11ea-87f7-712f0c9121d3

vendorTypeId
Integer

Vendor type ID.
Example: 1(1= Danlaw)

locationTime
Time Stamp

Time the location was recorded in milliseconds.
Example: 1663891337000

odometer
Integer

Odometer reading in kilometers.
Example: 209870

offset
Integer

Time zone offset.
Example: -300

virtualTripEnd
Boolean

Indicates whether the trip ended virtually.
Example: false

imei_meid
String

IMEI/MEID of the device.
Example: 352602114115360

insideHOO
Boolean

Indicates if inside hours of operation.
Example: true

lastKnownLat
Double

Last known latitude of vehicle in degrees.
Example: 38.6207052

lastKnownAddress
String

Indicates last known Address.
Example: 14442 Clayton Rd, Ballwin, MO 63011, USA

vehicleId
String,UUID

Unique ID for the vehicle.
Example: 7b9ec523-8059-11ec-91e8-79d8a6a932aa

dtcCount
Integer

Count of DTC records in the message.
Example: 2

userName
String

Name of the user.
Example: Bruce Driver

tripState
String

State of the trip.
Example: ACTIVE

latitude
Double

Latitude co-ordinate value in degrees Example: 38.6210808

longitude
Double

Longitude co-ordinate value in degrees Example: -90.5249991

dtcMessageRecords
dtcType: 0, failureMode: 0 subType: DTC_MESSAGE_RECORD_OBD,
dtcMessage: 0171

Object list of DTC records:

dtcType
Integer

Represents the type or category of the Diagnostic Trouble Code (DTC). Values typically indicate whether the fault is active, historical, pending, or system-specific.
Example: 0

failureMode
Integer

Indicates the nature or severity of the fault detected. The values generally follow the J1939 standard: 0 – No fault detected (OK) 1 – Data valid but above normal operational range (Warning) 2 – Data valid but below normal operational range 3–7 – Reserved for future use or custom definitions 8 – Severe fault detected 9 – Critical fault requiring immediate action (e.g., shutdown) These codes describe how serious the fault is and what type of intervention may be required..
Example: 0

subType
String

Specifies the format or schema used to interpret the DTC record. This value helps identify the standard (e.g., J1939) under which the DTC is reported. Example: "DTC_MESSAGE_RECORD_OBD"

dtcMessage
Integer

The actual DTC code.
Example: 0171