FC310x - PCI Cards for PROFIBUS

Diagnostic Data - DiagData

There follows a description of the DP diagnostic data

Offset
Meaning
0x00.0
StationNonExistent: slave did not reply to the last telegram
0x00.1
StationNotReady: slave still processing the Set_Prm / Chk_Cfg telegram
0x00.2
CfgFault: slave signaling a configuration error
0x00.3
ExtDiag: extended DiagData available and valid
0x00.4
NotSupported: slave does not support a feature requested via Set_Prm or Global_Control
0x00.5
InvalidSlaveResponse: slave response not DP-compatible
0x00.6
PrmFault: slave reports a parameterization error
0x00.7
MasterLock: slave currently exchanging data with another master
0x01.0
PrmReq: re-parameterize and reconfigure slave
0x01.1
StatDiag: slave signaling static diagnostics / DPV1 slave application not yet ready for data exchange
0x01.2
PROFIBUS-DP-Slave
0x01.3
WdOn: DP watchdog switched on
0x01.4
FreezeMode: DP slave in freeze mode
0x01.5
SyncMode: DP slave in sync mode
0x01.6
reserved
0x01.7
Deactivated: DP slave has been deactivated
0x02.0
reserved
0x02.1
reserved
0x02.2
reserved
0x02.3
reserved
0x02.4
reserved
0x02.5
reserved
0x02.6
reserved
0x02.7
ExtDiagOverflow: too much extended data present
0x03
MasterAdd: station address of master with which slave is exchanging data
0x04,0x05
IdentNumber
from 0x06
Extended DiagData
 

Extended DiagData

A distinction is made in the Extended DiagData between identification diagnosis, channel diagnosis and manufacturer-specific diagnosis. The first byte indicates the type of the diagnosis and the length of the associated data. In the Extended DiagData several diagnostic types can be entered consecutively.

 
 

Header Byte

Bit
Meaning
0-5
Length of the associated diagnostic data, including header byte
6-7
0 = manufacturer-specific diagnostics (DPV1 is not supported) or DPV1 diagnostics (DPV1 is supported (DPV1_Enable = 1) in associated GSD file)
Module diagnostics
Channel diagnostics
Revision number
 
 

Manufacturer-specific diagnostics

The structure of the manufacturer-specific diagnostics may be found in the documentation for the DP slave.

 
 

DPV1 diagnostics

In the case of DP slaves that also support DPV1, the DPV1 diagnostics, in which a distinction is made between status messages and alarms, is sent instead of the manufacturer-specific diagnostics.

Byte
Meaning
0
Header-Byte (bits 6,7 = 0, bits 0-5 = 4..63)
1
Bits 0-6: Alarm type
Bit 7: always 0
2
Slot number (0-254)
3
Bits 0-1: Alarm specifier
Bit 2: Additional acknowledge
Bits 3-7: Sequence number
4-63
Manufacturer specific (see the documentation for the DP slave)

Alarm type

Value
Meaning
0
reserved
Diagnostic alarm
2
Process alarm
3
Withdrawal alarm
4
Insertion alarm
5
Status alarm
6
Update alarm
7-31
reserved
20-126
Manufacturer specific (see the documentation for the DP slave)
127
reserved
 
 

Module diagnostics

The module diagnostics contain one bit for each DP module. The bit indicates whether a diagnosis for the corresponding DP module is present.

Byte
Meaning
0
Header byte (bits 6,7 = 1, bits 0-5 = 2..32)
1
Bit 0: 1st DP module has diagnostics
Bit 1: 2nd DP module has diagnostics
...
Bit 7: 8th DP module has diagnostics
...
...
31
Bit 0: 241th DP module has diagnostics
Bit 1: 242th DP module has diagnostics
Bit 2: 243th DP module has diagnostics
Bit 3: 244th DP module has diagnostics (a maximum of 244 DP modules is possible)
 
 

Channel diagnostics

The channel diagnostics provide a closer description of the cause of the diagnosis of a DP module.

Byte
Meaning
0
Header byte = 0x83 (3 bytes including header, bits 6,7 = 2)
1
Bits 0-5: Channel number
Bits 6-7: 0 = reserved, 1 = input, 2 = output, 3 = input/output
2
Bits 0-4: Error type
Bits 5-7: Channel type

Error type

Value
Meaning
0
reserved
Short circuit
2
Undervoltage
3
Overvoltage
4
Overload
5
Overtemperature
6
Wire breakage
7
Upper limit value exceeded
8
Value below lower limit
9
Error
10-15
reserved
16-31
Manufacturer specific (see the documentation for the DP slave)

Channel type

Value
Meaning
0
Any type
Bit
2
2 bit
3
4 bit
4
Byte
5
Word
6
2 words
7
reserved
 
 

Revision number

The structure of the revision number may be found in the documentation for the DP slave.

 
Additional information
DPV1 Error Codes