SST-PB3-REM
User Reference Guide
System Diagnostics
173
©2014 Molex Inc.
Document Edition: 1.1.4.0, Document #: 715-0106, Template Edition: 1.1, Template #: QMS-06-045
Use, duplication or disclosure of this document or any of the information contained herein is subject to the restrictions on page ii of this document.
Table 7.1-7: PfbLiveList and PfbDiagList Definition
PfbLiveList
PfbDiagList
Meaning
0
0
This state is reported in the three following cases:
-
system init state (temporary state)
-
for not configured devices, as a definitive state
-
for configured devices, when the Profibus stack is not
in OPERATE or CLEAR state
0
1
Communication with the device is failed
1
0
Communication with the device is OK and there is no diagnostic asked
by the device
1
1
Communication with the device is OK but there is a diagnostic asked by
the device
In addition, if the status of all slaves is acceptable, then bit 0 of location PfbMasSts is set to 1. If
this bit is 0, one or more slaves are in error.
7.1.3 Reading the Slave Diagnostics
Refer to section 10, Explicit Messaging on how Slave Diagnostics are retrieved.
The first 6 slave Diagnostic bytes are common to all DP slaves, as follows:
Table 7.1-8: Response to Slave Diagnostic CIP Message
Location byte offset
Meaning/Description
1
Station status byte 1
2
Station status byte 2
3
Station status byte 3
4
Master Station Address (Master that configured the slave.
OxFF means that no master has configured this slave
5 – 6
Slave ID
The bits in station status byte 1are defined in the table below.
Table 7.1-9: Bits in Station Status Byte 1
Bit AOP Tag Name
Meaning/Description
7
Master Lock
DP slave has been parameterized by another master
6
Parameter_Fault
Slave received an invalid parameter frame, wrong Ident, wrong length, invalid parameters,
and so on
5
Invalid_Slave_Repsonse
Invalid response from the slave
4
Function_Not_Supportedt
Master requested a function that the slave does not support
3
ExtDiagnosticData
An entry exists in the slave-specific diagnostic area.
2
CfgDataFalt
Configuration check data for the slave was incorrect
