5101 Mod6 R3 ECB
5101 Mod6 R3 ECB
Table of Contents
Introduction ........................................................................................... 2
Introduction
This module explains the function of the Equipment Control Block. The ECB is responsible for retrieving
and sending data and status to and from the FBM's. This topic will discuss how the FBM's convert a field
signal into a digital signal and then make this data available to the ECB. The "failsafe strategy" for
output channels will be discussed, as well as, how to configure the ECB parameters to achieve the
desired failsafe configuration.
Module Objective:
Utilizing all available documentation, the student will configure Equipment Control Blocks (ECB's) for
normal and failsafe operation.
Enabling Objectives:
The enabling objectives that support this module objective are as follows:
• Describe the significance of the Station and ECB compounds for a Control Processor.
• Describe the functions that the Equipment Control Blocks (ECBs) perform with
regard to the Control Processor (CP) and the Fieldbus Modules (FBM).
• Configure and test the Manual Failsafe (MANFS) parameter of the PID block.
These compounds are automatically added to the Control Database when the station is defined
and downloaded from IDE or Initialized . The naming convention for the Station Compound will
be the letterbug followed by the characters "_STA". Within the Station Compound is a block
named STATION and is a type STA block. The naming convention for the ECB Compound is the
station letterbug followed by the characters "_ECB". Within the ECB Compound is the Primary
ECB, which is named PRIMARY_ECB(2-4), and it is of type ECBP.
The following rules apply to Station and ECB Compounds:
• When the user edits a control station, the Station and ECB Compound parameters may not
be modified. They are displayed for viewing only. Within the Station Compound, only one
block, the STATION block, may exist. No other blocks may be inserted into the Station
Compound. In addition, the Station block may not be deleted. The parameters of the Station
Block may be modified.
• Similarly, the ECB Compound parameters may not be modified and the ECB Compound
and Primary ECB may not be deleted. The parameters of the Primary ECB may be
modified. No blocks may be inserted in front of the Primary ECB. Other ECB's, however,
may be added after the Primary ECB within the ECB Compound. These are handled as
normal blocks - they can be added, modified, and deleted.
• The Station and ECB Compounds are only recognizable by their unique names. It is not
possible for the user to create a Station or ECB Compound from scratch.
• Station and ECB Compounds can be imported and exported with the Control Database.
Fieldbus Scanning
Control Processor scan of a Fieldbus Module is performed on a per-FBM basis.
The ECB parameter, PERIOD, determines the period at which an FBM is scanned.
The Analog-type FBMs perform their own scanning of Analog inputs independent of CP/Fieldbus
scan intervals.
Power Up
When the FBM is first powered up, the FBM firmware writes zeroes to the gate array registers
and places the FBM in its Failsafe State. Since all of the hold/fallback bits equal 0 (Fallback) and
each fallback value equals 0, each output is at its de-energized value of 0 - waiting for the FBM to
go on-line.
FBM reboot
The FBM goes to the Failsafe State and the FBM outputs assume the Failsafe configuration until
the FBM is back on-line and the application software resumes control.
Comm Fail
Fieldbus Communications Failure or CP Failure. Two ECB parameters determine the if and when
of a communications failure between the CP and the FBM configured by that ECB.
FSENAB
Failsafe Enable is a Boolean that, when True, enables the FSDLAY timer. If communications fail
with FSENAB False, there is no failsafe activity: the FBM continues to drive the
outputs using the current values, which is equivalent to holding the outputs.
Note: Failsafe Enable (FSENAB) does not affect the Failsafe configuration. Setting FSENAB
False DOES prevent the FBM from going to the Failsafe State because of a CP-to-FBM
communications failure, but it CANNOT prevent the FBM from going to Failsafe for
any other reason.
FSDLAY
Failsafe Delay (FSDLAY), is a timer that, when enabled by FSENAB, specifies (in units
of .01 seconds) the length of time the FBM waits for a communication from the CP
before entering a Comm Fail (or software) Failsafe state. This state asserts the output
values specified by the failsafe configuration.
Example: The default value of 1000 causes the FBM to wait 10 seconds between CP
communications before going to the Failsafe state, if FSENAB is set True.
EEPROM Update
The FBM goes to the Failsafe State and the FBM outputs assume the Failsafe configuration
defined by the gate array registers prior to the EEPROM update. The FBM maintains this
definition until the EEPROM update is completed and the application software resumes control.
Power fail
When the main power fails, FBM outputs are de-energized since it is the main power that drives
them. The FBM goes to battery-backup, where the battery maintains the failsafe configuration in
the gate array registers.
If main power returns while the FBM is still battery-backed, the FBM assumes the failsafe
configuration. If main power returns after the backup battery discharges, the failsafe
configuration is gone, and the FBM reverts to a Day 0 Cold Start.
Bits 15 - 8 7
9 10 11 12 13 14 15 16
7
Bits 15 - 8
9 10 11 12 13 14 15 16
Note:
In a Ladder Logic application, the following rung must be added in order for the logic to go to
failsafe upon loss of Fieldbus communications:
COMMF FAILSF
( )
FBM O
1
O
Conditioned Conditioned 2
Output Output O
FBK BCALCI INITI INITO BCALCO 3
Failsafe Output
Read Back Counts Read Back Counts O
Value Value 4
MEAS OUT MEAS ECB
PID AOUT 5
O
FBM & ECB FBM Status O
Status 6
O
7
PID AOUT 8
O
PARAMETERS PARAMETERS
MANFS MANFS 4 - 20 mA
PRIBLK PRIBLK
ECB Operations
ECB Configuration
ECB's may now be configured in a manner similar to control blocks using the standard IDE
software. In addition, ECB's can be contained within any compound, not just the ECB Compound.
As discussed previously, ECB's can appear in the Block List of a compound just as any other block.
ECB's can now be manipulated in a manner similar to that used for normal blocks. An ECB is
automatically added when a new FBM is added to the CP in the network tab in the IDE. The ECB
will automatically be listed in the Station ECB Compound. By double clicking on the ECB
compound, you can access and modify ECB parameters, and configure a Failsafe pattern or values
if required. An ECB can reside in the ECB Compound or, it can be moved to any other compound
in the same CP. When the ECB editing is done, it can be deployed to your station.
You can edit an FBM extension parameters in the same manner as the Main FBM module.
The ECB parameters may be recalled for modification. However, a number of ECB parameters will
be protected from further modification. The parameter names and values being drawn with a dark
gray background color indicate such protection. Whenever an ECB is modified, a Deploy to the CP
must follow.
Certain FBMs are capable of running more than one type of ECB. FBM 241 is an example. In this
FBM, we could load ladder logic ECB or DIN/DOUT ECB. To load different software package in
an FBM, you must do the following:
• Select the Network tab.
• In the Network tab, expand the galaxy and then the active CP.
To edit the ECB parameters, click the Deployment tab and then double click the ECB compound.
Select ECBs tab from the ensuing window and then the desired ECB to edit
Lab
Introduction
This laboratory exercise consists of two parts. In the first part, the CP will be Undeployed and Rebooted
"Initialized" so that the student may observe the effect on the CP, FBM's, and the process. In part two,
an Analog and a Digital FBM will be configured and tested for failsafe conditions.
CP Initialization
In this lab exercise, you will Undeploy and Reboot (Initialize) the CP. The Initialize procedure,
which includes a CP reboot, deletes all compounds and Equipment Control Blocks (ECB's) CP
Lab Setup
1. Access the BlockSelect display and refresh CP2801 or CP2701.
2. Expand Control Processor.
3. Write down the names of the compounds in this CP___________________________
____________________________ __________________________________
____________________________ __________________________________
____________________________ __________________________________
____________________________ __________________________________
____________________________ __________________________________
4. Expand CPNAME_ECB compound. How many ECBs are present? Write down the names
____________________________ ________________________ __________
____________________________ __________________________________
Undeploying the CP
1. Call up the IDE control database configurator.
2. In the Deployment window, expand your working Control Processor.
3. Right click Control Processor and select Undeploy from the ensuing menu. The Undeploy
window is called up.
Note: When you Undeploy the CP, you are deleting the compounds from the Checkpoint file at
the same time. By rebooting the CP after Undeploy, the checkpoint file which is empty, is
reloaded into the Cp.
Review Questions
None!