Diagnostic Trouble Codes

This article was written for version 2.3.1 of Core. Click here for the most recent version of the help center.

Diagnostic Trouble Codes (DTC) are used to indicate a specific diagnostic status for a node.

The meaning of a DTC is dependent on the node context. Always check the documentation for the specific application to determine what the DTC means.

For example this C++ function will return DTC_CONFIG if the function was unable to open the serial device handle.

DTC Code Description
0 No error - DTC_NONE
20 Usage error - DTC_USAGE
40 System design file not accessible - DTC_NOSDF
41 System design file corrupt - DTC_BADSDF
42 System design file key invalid - DTC_SDFKEY
50 Data model configuration error - DTC_PDMCONFIG
51 Data model ‘core’ module version is not supported by the API version - DTC_PDMCORE_VERSION
52 Data model shared library file missing error - DTC_NOPDM
53 Failed to create PolySync Core Logfile/RnR wall clock - DTC_LOGFILE_REPLAY_CLOCK
70 Interrupted system call error - DTC_INTR
75 Operation in progress error - DTC_INPROGRESS
100 Data format error - DTC_DATAERR
102 Cannot open input - DTC_NOINPUT
103 Addressee unknown - DTC_NOUSER
104 Host name unknown - DTC_NOHOST
105 Service unavailable - DTC_UNAVAILABLE
106 System error - DTC_OSERR
107 Memory error - DTC_MEMERR
108 Critical OS file missing - DTC_OSFILE
109 Cant create output file - DTC_CANTCREAT
110 Input/output error - DTC_IOERR
111 Error in protocol - DTC_PROTOCOL
112 Permission denied - DTC_NOPERM
113 Configuration error - DTC_CONFIG
114 Runtime environment error - DTC_ENVERR
115 License error - DTC_LICERR
116 Message/resource type is not supported - DTC_TYPESUPPORT
117 Failed to create message queue - DTC_MESSAGE_QUEUE
118 Failed to create shared memory queue - DTC_SHAREDMEM_QUEUE
119 Failed to create thread - DTC_THREAD
120 Failed to create PolySync Core Logfile API reader thread - DTC_LOGFILE_READER_THREAD
121 Failed to create PolySync Core Logfile API writer thread - DTC_LOGFILE_WRITER_THREAD
123 Failed to create message publisher - DTC_MESSAGE_PUBLISHER
124 Failed to create message subscriber - DTC_MESSAGE_SUBSCRIBER
125 Failed to read data - DTC_BAD_READ
126 Failed to write data - DTC_BAD_WRITE
300 Bad device initialization - DTC_BADDEVICEINIT
301 No device initialization - DTC_NODEVICEINIT
302 Device not powered - DTC_NODEVICEPWR
303 Device damaged - DTC_DEVICEDAMAGED
304 Interface not connected - DTC_NOINTERFACE
305 Interface protocol violated - DTC_INTERFACEPROTOCOL
306 Interface saturated - DTC_INTERFACESATURATED
307 Interface in use - DTC_INTERFACEINUSE
308 Native bus not connected - DTC_NONATIVEBUS
309 Native bus protocol violated - DTC_NATIVEBUSPROTOCOL
310 Native bus saturated - DTC_NATIVEBUSSATURATED
311 Native bus in use - DTC_NATIVEBUSINUSE
312 Failed to locate PolySync Core CAN support module/library - DTC_CAN_MODULE
313 Failed to locate specified CAN channel on the host - DTC_NO_CAN_CHANNEL
314 Failed to apply configuration to the CAN channel - DTC_CAN_CHANNEL_CONFIG
315 No valid CAN channel data seen - DTC_NO_CAN_DATA
316 Failed to locate PolySync Core Socket support module/library - DTC_SOCKET_MODULE
317 Failed to create socket with specified address/port - DTC_NO_SOCKET
318 Failed to apply configuration to the socket - DTC_SOCKET_CONFIG
319 No valid socket data seen - DTC_NO_SOCKET_DATA
320 Failed to locate PolySync Core Serial support module/library - DTC_SERIAL_MODULE
321 Failed to create serial device interface - DTC_NO_SERIAL
322 Failed to apply configuration to the serial device interface - DTC_SERIAL_CONFIG
323 No valid serial data seen - DTC_NO_SERIAL_DATA
324 Failed to locate PolySync Core Shared Memory support module/library - DTC_SHAREDMEM_MODULE
325 Failed to create shared memory interface - DTC_NO_SHAREDMEM
326 Failed to apply configuration to the shared memory segment - DTC_SHAREDMEM_CONFIG
327 No valid shared memory data seen - DTC_NO_SHAREDMEM_DATA
328 Failed to locate PolySync Core Video support module/library - DTC_VIDEO_DEVICE_MODULE
329 Failed to create video device with specified device path - DTC_NO_VIDEO_DEVICE
330 Failed to apply configuration to the video device - DTC_VIDEO_DEVICE_CONFIG
331 No valid video device data seen - DTC_NO_VIDEO_DEVICE_DATA
332 Failed to apply configuration to the video encoder - DTC_VIDEO_ENCODER_CONFIG
333 Failed to apply configuration to the video decoder - DTC_VIDEO_DECODER_CONFIG
800 Logfile contains no message data - DTC_LOGFILE_EMPTY
801 Specified replay session identifier does not exist on the host - DTC_INVALID_REPLAY_SESSION
900 Process is not responding - DTC_PROCESS_NOT_RESPONSIVE
901 PolySync Core Manager daemon is not responding - DTC_MANAGER_NOT_RESPONSIVE
902 PolySync Core PTP service is not responding - DTC_PTP_NOT_RESPONSIVE
1000 Command is not available or not supported - DTC_COMMAND_NOT_AVAILABLE
1001 Command is missing required data elements - DTC_COMMAND_NO_DATA
1002 Command has invalid data elements - DTC_COMMAND_BAD_DATA
1100 Request for position index in sequence outside of valid range - DTC_SEQUENCE_INDEX_OUT_OF_RANGE
1101 Request for position index in sequence collides with another request - DTC_SEQUENCE_INDEX_COLLISION