Diagnostics and error handling
BK3xx0
65
Version: 4.3.0
DP standard 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 paramétrisation 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 diagnosis / DPV1 slave application not yet ready for data
exchange
0x01.2
PROFIBUS DP slave
0x01.3
WdOn: DP watchdog 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
Device-specific diagnostic data (extended DiagData)
Device-specific diagnostic data (DPV1 status message)
The meaning of the first 4 bytes of the DPV1 status message is specified by the DPV1 standard, while the
bytes that follow are manufacturer-specific.