c300 communications and batch presentation
TRANSCRIPT
Return on Imagination
Honeywell Users Group 2009
Marc Schuilwerve – Saudi AramcoCommunications between controllers belonging to different server clusters
PD
F processed w
ith CuteP
DF
evaluation editionw
ww
.CuteP
DF
.com
2
Introduction to Peer to Peer passes
• Communicating between controllers in the same Server Cluster.– Peer to peer passes between controllers are referenced by
the tagname.parameter, no special configuration required.
• Controllers communicating to controllers in another Server Cluster in the same FTE Community.– Peer to peer passes need to make use of exchange blocks.
3
Server Clusters
Level 1 Switches
Cluster #1
Level 1 Switches
Cluster #2
Level 2 Switches Level 2 Switches
4
Exchange Blocks
• Send and Receive concept
– One has to configure both a sending (source) Control Module (CM)
as well as a Receiving (responding) CM.
• Need to establish a Nomenclature convention
– Sending or source CM: controller_name_SRC, for example:
2C200_5_SRC
• File name in Target Device: destination_controller_name_x
– Receiving or responding CM: controller_name_RSP, for example:
C300_5_RSP.
• Exchange block name: RSP_NUM_Controller_name_x
5
Typical Source CM
6
How to configure a Source CM
• Create a new CM and follow your nomenclature rule.
• Add a RequestNumArray or a RequestFlagArray block to the CM.
– Configure the array block Main tab. Make sure that you configure the
Command type as CIPWrite and estimate how many numerics or
flags you are going to pass, leave some room for the future.
7
Source block configuration cont.
• Configure the Communication Tab.
• Make sure you have the IP address of the C200/C300 that is going to
receive the information, or the destination node. The “File Name in Target
Device” is very important since it will be used in the response array block
in the destination controller.
• Please note the format: 1,0,2, IP address,1,1, or in this example
1,0,2,10.0.2.27,1,1
8
Source block configuration cont.
• Now you will have to configure the connections to the array block, and you
need to connect the READYFL of the REQNUMARRAY/FLG block to its
SENDFL. After this task the source CM should be ready, and it will be time
to configure the corresponding destination CM
9
Source Block CM example
10
How to configure a Responding CM
– Create a new CM and follow your nomenclature rule.
– Add a ResponseNumArray or an ResponseFlagArray block to the
CM.
– Configure the array block Main tab. Configure the CIP Tag Name
identical to the “File Name in Target Device” that you entered when
you configured the Source CM.
– Once this has been done one can configure numerics/flags as place
holders for the peer to peer passed information, or one can directly
access the array point from other CM’s in that controller
11
Responding Block CM example
12
Practical Example
The example depicted below shows a compensated flow input coming from another Experion system. This flow is being summed and past as an analog output to the utility supplier (non Experion user). Notice that one of the inputs comes from a so called response CM; C200_5_RSP.
13
Conclusion
• A solution for large sites– Large sites like refineries should pay close attention
during the FTE network design to make sure the design allows nodes on different Server Clusters to communicate directly to each other using the TCP/IP protocol. Honeywell network experts should be able to help in the proper design of the network.
– Assuming you have designed the network correctly, then you are also automatically setup to take full advantage of DSA technology, which by itself is absolutely amazing and warrants another presentation!
14
Marc Schuilwerve – Saudi AramcoSome SCM tips, including SCM Alias Tables, Level1 Devices and more.
Return on Imagination
Honeywell Users Group 2009
15
Agenda
• Overview of some Batch Terminology
• Alias Tables
• Level 1 Devices
• Multiple SCM commanding to a single device
16
Batch Terminology
• Level1 Device
– A Level 1 Device is a Control Module that is bound to a SCM.
Typically the CM will have a RegCtl or DevCtl block configured in it.
The MODATTR and other parameters of the RegCtl or DevCtl block
will track predefined configuration defined in the SCM and CM based
on the SCM status.
• Common SCM
– This is a SCM that manipulates devices that maybe common to
multiple units. A typical example is a charge loop of an ingredient into
a reactor. Often there will be multiple reactors, but the charge pump,
flow meters and some valves will be common to all reactors, thus a
Common or Shared SCM is utilized. This feature is useful when
doing arbitration of shared devices by a higher level like a RCM or
Total Plant Batch.
17
Common SCM
Shared or Common
Devices
Dedicated Devices
A single Common SCM would control all these Devices
Alias Table Application
18
Alias Tables – what are they?
• In many plants certain equipment is shared between multiple units and operated in a batch mode. The most common examples are the charging of ingredients into reactors. Often multiple batch reactors are deployed that are charged with similar ingredients.
19
Alias Tables
– A programmer has a choice of writing a SCM with
multiple branches for each reactor, or make use of an
Alias Table.
• The above depiction is simplified, in reality the amount of steps and transitions avoided would be typically on the order of 30 steps and 30 transitions for a three reactor example
SCM with Alias Table SCM without Alias Table
Maximum number of
Transitions and Steps in a
SCM is 400
20
Alias Table – screen shot
Instances – number of reactors.
Instance selected.
Number of alias is 31
X 3 = 93.
Either TotalPlant Batch or an RCM/SCM can set the
required instance. An Operator can also select the
instance.
TBP users need to make sure that at the top of the SCM they add some code to select the correct instance, a sample of a step output code is listed below.SCM.INSTSELECT : = (SCM.auxunit)=211 ?1 : ( (SCM.auxunit)=221 ?2 : ( (SCM.auxunit)=222 ?3: SCM.INSTSELECT))
Alias Tables are
not just for
devices, you can
specify recipe
parameters and
other items too!
21
Alias Table – Advantages and Drawbacks
• Advantages:
– Considerably less code required.
– Easy to add another reactor, just fill in the new alias instance.
• Drawback– Cross references on the CM’s to alias addresses are not depicted.
This makes it difficult to realize the impact if you modify or delete a
CM that is used in a SCM alias table. This omission has been
submitted to the UIS (UIS R16 Item # 2950).
– Level1 device declaration should not be done if the CM is used in an
Alias Table. Basically the drawback is that the device cannot use
Level 1 tracking features, so some extra coding must be done in the
SCM to make sure that the device is in the proper mode and state.
22
Level1 Device – What is it?
• A Control Module can have a Function Block
parameter such as MODATTR change modes based
on the state of the SCM that it is linked to. This linked
tracking functionality requires that the one configures
parameters both in the CM that has the desired
Function Block that needs manipulation, as well as in
the SCM that does the manipulation.
23
Level 1 Configuration in the Control Module
The screenshot depicts a
CM Function Block that
has a SCM relationship
with a SCM named
EVAP_CHG. This is
referred to as “Binding”
the CM to the SCM.
Name of the linked SCM
24
Level 1 Configuration in the Control Module
On another tab one can
configure the state you
want to device to take when
a SCM Abnormal Handler
is invoked. This can be a
useful tool to do some
interlocking based on the
state of the SCM.
25
SCM modifications for Level 1 devices.
• If one does link a CM to a SCM, than the
coding in the SCM is also slightly different
in the STEP configurations for those
devices. One has to select the stored
option in the STEP output pull down
button; this is done by selecting the SET
option.
• In addition the SCM STEP display will also
depict an “S” at the beginning of each
output that is linked to a CM.
26
Level 1 Tracking feature
The Device Control or
Reg Control block can
be automatically
placed into Program
mode by selecting the
appropriate tracking
mode.
27
Level 1 Tracking feature
The Reg Control
block can respond to
abnormal handlers.
The Device Control
Block has just two
options, SAFEOP or
NONE.
28
R201 → R301 versus ≥R310
• Starting in Experion R310, the following three action qualifiers, as defined
in IEC 61131-3, are provided for STEP output sequences in addition to the
original qualifiers of Set (S) and NotStored (N) for legacy Level 1 devices
through Control Modules that are still supported.
1. N_IEC - not set (or also known as not stored, NS) , ON while step is active
2. S_IEC - set , ON until R
3. R_IEC - reset ( reset to OFF from previous S )
Please refer to Honeywell documentation in regards to these new features.The other IEC 61131-3 action qualifiers (L, D, P, SD, DS, SL) are not provided
29
Multiple SCM commands to a CM Function Block
In some batch applications
it may be necessary for
multiple SCM’s to
command a single device.
A typical application is that
of a valve on a common
charge header. In such an
example you may have
five different SCM’s
charging ingredients into a
common header which has
one isolation valve on top
of the reactor. How does
one assure that the valve
behaves as intended?
Valve getting
commands from
multiple SCM’s
30
Multiple SCM’s commanding a DevCtl block.
In the depicted CM there are
7 SCM’s that send
commands to this particular
valve; in addition there is
one interlock connection to
override any SCM
command. In this case the
NMP SCM is commanding
an OPEN command, while
the other 6 SCM’s are
commanding a closed
command. Since a MAX
block is used, the logic will
take the NMP_CMD value
and command the valve to
open
This setup also allows for concurrent charging through the
common header.
