ProSoft Technology 5205-104S-PDPS - Manual (Page 71)

Diagnostics and Troubleshooting 4205/5205-TS-104S-PDPS ♦ ProLinx Standalone
IEC-60870-5-104 to PDPS Communication Module with Time Stamp
ProSoft Technology, Inc. Page 71 of 128
July 12, 2007
3 Diagnostics and Troubleshooting
In This Chapter
Definition of Module's Extended Diagnostics Data................. 71
The module provides information on diagnostics and troubleshooting in the
following forms:
Status data values are transferred from the module to the processor.
Data contained in the module can be viewed through the
Configuration/Debug port attached to a terminal emulator.
LED status indicators on the front of the module provide information on the
module's status.
3.1 Definition of Module's Extended Diagnostics Data
The Extended Diagnostic Data is reported during startup and initialization
sequence when the master requests diagnostic data from the module. The
Extended Diagnostics is "Device Related" type providing status data (the
extended diagnostic bit 3 in standard diagnostic byte 1 is set = 0). The data
length is normally 14 (0E) bytes displayed in the following format:
Byte(s) Description (HEX)
0 Extended Diagnostics length (normally 14 bytes (0E))
1 to 6 ASCII data for Product Version
7 to 10 ASCII data for Product Name
11 Value of Status Register [0] (see Section 2)
12 Value of Status Register [1] (see Section 2)
13 Module State (see Section 2)
Bytes 7 through 10 Data – Specific Product Code Value
Each ProLinx application has its own, unique product code. You can determine
the product code from the Version screen in the Configuration/Debug menu.
The following table lists the product codes for some ProLinx modules that
support the PDPS protocol.
Example Product Example Product Code
5105-ASCII-PDPS ASPS
5105-DFCM-PDPS DFPS
5105-DH485-PDPS D4PS
5105-DNPM-PDPS DMPS
5105-DNPS-PDPS D3PS
5105-I101S-PDPS ISPS
5105-I103M-PDPS PSI3
5105-MCM-PDPS PDSM