Table of Contents
Advertisement
Chapter 3 Deployment
Structure of the
353-1DP01
diagnostic data
Byte 0 ... Byte 5 Standard diagnostic
data
x ... x+4
Identifier-related
diagnostic
x ... x+11
Module state
max. 9⋅(x ... x+2) Channel-related
diagnostic
x ... x+19
Interrupt
Standard
diagnostic data
3-24
The diagnostic messages that are created by the PROFIBUS slave have,
depending on the parameterization, a length of 58Byte.
As soon as the PROFIBUS slave sends a diagnostic to the master, the
max. of 58Byte diagnostic data are prepended by 6Byte standard
diagnostic data:
At the transfer of a diagnostic to the master the slave standard diagnostic
data are prepended to the diagnostic bytes. More detailed information to
the structure of the slave standard diagnostic data is to find in the standard
papers of the PROFIBUS User Organization.
The slave standard diagnostic data have the following structure:
Standard diagnostic
Byte
Bit 7 ... Bit 0
0
Bit 0: Bit is always at 0
Bit 1: slave is not yet ready for exchange data
Bit 2: Configuration data does not correspond to
actual configuration
Bit 3: External slave diagnostic available
Bit 4: Request function is not supported by slave
Bit 5: 0 (fix)
Bit 6: Wrong parameterization
Bit 7: 0 (fix)
1
Bit 0: New parameters have to be assigned to slave
Bit 1: Statistic Diagnostic
Bit 2: 1 (fix)
Bit 3: Response monitoring has been enabled
Bit 4: "FREEZE" control command received
Bit 5: "SYNC" control command received
Bit 6: reserved
Bit 7: 0 (fix)
2
Bit 6 ... 0: reserved
Bit 7: Diagnostic data overflow
3
Master address after parameterizing
FFh: Slave has not been parameterized
4
Ident number High Byte
5
Ident number Low Byte
Is only prepended at transfer to the
master via PROFIBUS
Internal stored diagnostic
HB140E - IM - RE_353-1DP01 - Rev. 14/47
Manual VIPA System 300S
Can be enabled
or disabled via
paramete-
rization
Advertisement
Table of Contents
