Scenario
Cause of loss/prerequisites
Effect of communication loss
Loss of communication
between C300 and PGM
Loss of communication between the C300
and the PGM can occur if both FTE cables
are disconnected. In such a case, a
notification that the PGM went OFFNET
is reported. The PDA sets the appropriate
status of the data passed to the PIOMBs.
Input type PIOMB
•
PIOMB receives communication
failure status.
•
Channel data is set to fail-safe values.
•
Strategies react to the fail-safe values.
Output type PIOMB
•
PIOMB receives communication
failure status.
•
Channel blocks request upstream
blocks to go into initialization.
•
Device output values is set to
configured fail-safe values by the DSB.
Loss of communication
between PGM and the device
Loss of communication between the PGM
and the device can occur under the
following scenarios.
•
Cable on the PROFIBUS network
breaks.
•
Device fails.
•
Device power is disconnected.
Input type PIOMB
•
PIOMB receives communication
failure status.
•
Channel data is set to fail-safe values.
•
Strategies react to the fail-safe values.
Output type PIOMB
•
PIOMB receives communication
failure status.
•
Channel blocks request upstream
blocks to go into initialization.
•
Device output values are set to
configured fail-safe values by the DSB.
A Device OFFNET notification is also
reported.
Loss of PGM power
When a PGM loses power such that the
secondary cannot take over, the devices
must put themselves in a safe state, if such
an operation is supported by the device.
If the devices do not go into a safe state,
the following changes occur.
Input type PIOMB
•
PIOMB receives communication
failure status.
•
Channel data is set to fail-safe values.
•
Strategies react to the fail-safe values.
Output type PIOMB
•
PIOMB receives communication
failure status.
•
Channel blocks request upstream
blocks to go into initialization.
•
Device output values will be set to
configured fail-safe values by the DSB.
C300 Switchover
(with connection between the
C300 and the PGM re-
established within the specified
period of time)
•
PIOMB and CM1 are active.
•
CEE is in the Run state.
•
C300 and PGM are communicating.
PIOMB
•
Output values are held.
•
Input values and control loops maintain
their current values.
•
Switchover does not cause strategies to
set to fail-safe values.
9 PROFIBUS I/O MODULE (PIOMB) FUNCTION BLOCK
219
Summary of Contents for Experion PKS
Page 1: ...Experion PKS PROFIBUS Gateway Module User s Guide EPDOC XX88 en 431E June 2018 Release 431 ...
Page 8: ...CONTENTS 8 www honeywell com ...
Page 10: ...1 ABOUT THIS GUIDE 10 www honeywell com ...
Page 32: ...4 PROFIBUS GATEWAY MODULE PGM INSTALLATION 32 www honeywell com ...
Page 58: ...5 PROFIBUS GATEWAY MODULE PGM BLOCK 58 www honeywell com ...
Page 69: ...6 PROTOCOL BLOCK 69 ...
Page 103: ...5 Click OK 6 PROTOCOL BLOCK 103 ...
Page 110: ...6 PROTOCOL BLOCK 110 www honeywell com ...
Page 183: ...PDC Details tab Figure 6 Detail Display of PDC Details tab 7 DEVICE SUPPORT BLOCK DSB 183 ...
Page 186: ...7 DEVICE SUPPORT BLOCK DSB 186 www honeywell com ...
Page 231: ...9 PROFIBUS I O MODULE PIOMB FUNCTION BLOCK 231 ...
Page 232: ...9 PROFIBUS I O MODULE PIOMB FUNCTION BLOCK 232 www honeywell com ...
Page 236: ...10 PROFIBUS GATEWAY MODULE PGM CONFIGURATION EXAMPLE 236 www honeywell com ...
Page 264: ...13 PROFIBUS GATEWAY MODULE PGM TROUBLESHOOTING 264 www honeywell com ...