13.1 Behavior of PGM during fault scenarios
This section provides information on the behavior of the PGM under various scenarios such as power off,
communication loss with the devices, communication loss with the C300 Controller and so on.
Related topics
“Loss of communication between PGM and C300” on page 250
“Loss of communication between PGM and slave device ” on page 250
“Loss of communication between the PGM and control strategies” on page 251
“CEEC300 state is changed to Idle ” on page 251
“Inactivation of PIOMB” on page 251
“Deletion of PIOMB” on page 251
“PGM power failure” on page 252
“Removal of PGM from IOTA” on page 252
“Mismatch of the slave device and the master addresses” on page 252
“Experion server switchover” on page 252
13.1.1 Loss of communication between PGM and C300
This communication loss can occur when both the FTE cables are removed from the non-redundant PGM.
Attention
Even if one of the FTE cables are removed or is faulty, the PGM can still communicate with the devices on network.
The following table illustrates the behavior of the DSB and the PIOMB blocks when there is a communication
loss between the PGM and the C300 Controller.
DSB
PIOMB
Input side behavior
•
The DSB is informed of the communication
loss.
•
The connections are removed.
•
The PGM stops data updates to the associated
PDCs.
Input channels
•
Input Channels will be set to fail-safe values (NaN and OFF for
analog and digital values respectively).
•
Channel value status is set to "Bad."
•
The associated function blocks react to the fail-safe data.
Output side behavior
•
The fail-safe value of the device is set on the
DSB block.
Output channels
Output Channel will request the upstream blocks to go into
initialization (INITMAN parameter should be set to "ON" for the
PID and DEVCTL blocks).
13.1.2 Loss of communication between PGM and slave device
This communication loss between the PGM and the slave devices can occur in the following scenarios.
• The PROFIBUS cable is removed from the PGM.
• The slave devices are not configured properly.
• The slave devices are broken.
The following table illustrates the behavior of the DSB and PIOMB blocks in the event of a communication loss
between the PGM and the slave device.
13 PROFIBUS GATEWAY MODULE (PGM) TROUBLESHOOTING
250
www.honeywell.com
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 ...