Protocol Block Icons; Protocol Block Notifications - Honeywell Experion PKS User Manual

6.10.5 Protocol Block icons

The following table summarizes the various appearances that a Protocol Block icon can assume based on view
and current Protocol Blockstate.
If Icon is...
Project view
gray
Monitoring view
green
red

6.10.6 Protocol Block notifications

When the Protocol Block is active, it generates the following notifications.
Notification
Field Network
Failure
Field Network
Configuration
Failure
Field Network Tag
Table Failure
Input Data Base
Cycle Changed
Then it indicates...
Protocol Block a is associated with configured PGM.
Protocol Block is active.
Protocol Block is in a failed state.
Description
This notification is generated when the master has lost connection to all PROFIBUS slave devices.
After the Protocol Block is downloaded, the CRC sum of the parameter NETCONFBIN is calculated.
It is then compared to the NETCONCRCSUM parameter which was calculated by the tools. In there
is a mismatch in this comparison, this notification is generated.
You must modify and reload the field network configuration for this notification to return to normal.
After the Protocol Block downloaded, the CRC sum of the parameter NETTAGTABLEBIN is
calculated. It is then compared to the value that was loaded along the NETTAGTABLEBIN parameter.
If there is a mismatch in this comparison, this notification is generated.
You must modify and reload the field network configuration for this notification to return to normal.
The input data is sampled on every Process Data Access (PDA) base cycle, which is the smallest raw
data cycle seen in PDA opens. The data delivery time which is the time consumed between process
data read from the PROFIBUS network to the end of triggering PDA transport is measured on every
cycle.
The new data sample time is calculated based on the data delivery time and the start time of the earlier
sample. If the data delivery time is longer than minimum cycle (5 ms), the next sample will be
delayed so that there is always a minimum of 5 ms time from the end of data delivery to the start of
the next sample.
If the data delivery takes more than the minimum cycle (5 ms) on three consecutive cycles, this
notification is generated. This notification returns to normal when the data delivery time has been
below minimum cycle (5ms) on three consecutive cycles.
To recover from this, you must reduce either the number of PIOMB connections or the input data read
cycle defined in the PIOMB block.
6 PROTOCOL BLOCK
93