experion r410 and later - honeywell · 2014-11-03 · prior to r410, opc integrator and opc gateway...

Honeywell

Honeywell Process Solutions – Global TAC

Honeywell Confidential & Proprietary This work contains valuable confidential and proprietary information and is subject to any confidentiality or non-disclosure agreements between

Honeywell and its affiliates and subsidiaries (“Honeywell Group”). This work is provided by Honeywell on a without prejudice basis and shall not be relied upon in any legal, arbitration or other dispute resolution proceedings.

Disclosure, use or reproduction of Honeywell material is prohibited except as authorized in writing by Honeywell.

© Honeywell, 2012

Owner: Category:

Global TAC

Peer-to-peer CEE to non-CEE communication

File Name: GTAC_R410_and later _P2P_CEE_non_CEE_comm s

Revision: 7 Document Name: Peer responder functionality. Considerations and usage

Date: October 29, 2014 Page: 1 of 15

Experion R410 and later

PEER RESPONDER FUNCTIONALTY. CONSIDERATIONS AND USAGE

Signature

……………………………………….. Reviewer

Name

Strezimir Dukovski, Marin Ruskov Position TAC Engineers Server-Client

Date

October 29, 2014

Honeywell


Owner: Category:

Global TAC





REVISION DETAILS

7 October 29, 2014 Added gudance for limiting write rate for TPS systems

6 October 12, 2014 Added R430

5 January 22, 2014 Added CAB blocks for handling Failsafe scenarios

4 January 14, 2014 Ready for release

3 December 18, 2013

2 August 29, 2012

1 August 28, 2012

0 Auguts 23, 2012

Rev. Date Details

CONTENTS

1 INTRODUCTION: ................................................................................................................................... 3

2 PERFORMANCE CONSIDERATIONS ................................................................................................... 3

2.1 Reading ............................................................................................................................................ 3

2.2 Writing .............................................................................................................................................. 3

2.3 OPC Integrator .................................................................................................................................. 5

2.4 TPS ................................................................................................................................................... 5

2.5 SCADA ............................................................................................................................................. 6

2.6 DSA .................................................................................................................................................. 6

3 FEATURE DESCRIPTION ..................................................................................................................... 6

3.1 CEE Controller Points ....................................................................................................................... 6

3.2 Guidelines for configuring peer-to-peer communication between CEE and non-CEE points ............. 6

3.3 Configuration Example ...................................................................................................................... 8

3.4 Designing the control strategy for Failsafe control ............................................................................. 9

3.5 Experion Server Peer Responder Performance .............................................................................. 13

3.6 Experion Server Peer Responder Display ....................................................................................... 14

3.7 Advanced Peer to Peer Functionality .............................................................................................. 14

4 TAC CONTACTS ................................................................................................................................. 15

Honeywell


Owner: Category:

Global TAC





1 INTRODUCTION:

The purpose of this document is to describe a new functionality, available in Experion R410 and later, for peer-to-peer communication between CEE and Non-CEE points. Prior to R410, OPC Integrator and OPC Gateway were used to transfer data from the Experion Server points such as SCADA Points and OPC Advance Points to the CEE controllers such as C300/C200E. In addition, peer-to-peer communication between the C300 Controller and the Safety Manager was achieved using PCDI. Peer-to-peer communication between the ACE and TPS points was supported through OPC Gateway and direct peer references from CEE to Experion Server Points was not supported. Moreover, the peer-to-peer communication was not redundant, and peer-to-peer communication between C300/C200E and TPS points was not supported. With R410 and later, native peer-to-peer communication is supported between CEE-controllers such as C300, C200E, ACE, SIM-C300, SIMC200E and SIM-ACE and non-CEE controllers such as PMD and Safety Manager. In addition, peer-to-peer communication is also supported between the CEE-controllers and Experion Server points such as OPC point, OPC-Advanced point, DSA, Point Servers, SCADA, and TPS, through Experion Server. Attention:

Writes from SIM-C300, SIM-C200E and SIM-ACE are not supported.

For critical communications consider PCDI, because this new functionality depends on the server availability.

ACE-T is to be used for TPN communications in the following cases: - Cascade connection between CEE and HPM controllers - LCN Prefetch

If only peer read from TPN controllers / non cascade writes to TPN controllers is desired, the CEE-nonCEE p2p could be used, not using ACE-T node.

ICG (Intercluster gateway) is to be used in cases when cascade connection between ACE (ACE-T) controllers in different clusters is required. If only peer read / non cascade write is required then CEE to DSA p2p is possible. Note:

When using peer responder functionality, GTAC recommends running Experion systems at latest available patch level

2 PERFORMANCE CONSIDERATIONS

2.1 Reading

Reads occur at the CEE peer subscription period. This is independent of the Control Module execution period. Note: Reading lots of point parameter values from TPS at default rate can put a significant load on the LCN.

2.2 Writing

Control strategies that take advantage of peer responder functionality must be designed to minimize the number of writes to the control system. By default, PUSH blocks writes at the Control Module execution period. If the execution period is one second, peer responder will do a single write for the configured blocks every second. If there are multiple Control Modules performing writes through peer responder and the execution period of these Control Modules is increased, peer responder may still write once per second if each Control Module has a different execution phase.

On the PUSH blocks there is a "Store on change Enable" option which determines whether or not an input value is to be stored to destination only when it changes. It is recommended that all the PUSH blocks writing to point parameters have the "Store on change Enable" option enabled. This will mean that Peer Responder will only write to the point parameter when the value changes rather than writing to it continuously even though the value is not changing.

Honeywell


Owner: Category:

Global TAC





Important: PUSH block’s "Store on change” feature generally doesn’t take effect with real numbers since their value typically changes every execution cycle. Additional techniques should be applied to reduce the number of real value writes. Examples of such techniques are given below.

To reduce the write rate it is possible to implement dead band functionality for floating point values in control strategies. Preferably this could be done using CAB blocks for projects with C300 controllers. Projects, not running C300 could use control strategy logic to implement a dead band for writing values.

Dead band implementation examples are show below:

CAB implementation (preferred for C300)

Note that CAB runtime should be enabled in CEE before loading control modules with CAB blocks in controller. This could be done while controller is running and on control from Control Builder Monitoring Tab as shown below:

Control logic implementation (could be used for both, C200 and C300 controllers)

Note that in this control strategy the value that configures the dead band should never be negative. The execution order of the blocks is important. See the attached export of the control module.

Replace the NUMERIC block with the value that is writing to peer responder.

CAB block Dead band value

Insert a param connector with the point parameter that is being written to through peer responder.

Honeywell


Owner: Category:

Global TAC





Note: Peer responder will write to points using the Program access level. The mode of the point may need to be changed to allow writes from the Program access level. It is possible to change the security level that peer responder will use to write to TPS points by using the System Management Display to configure the TPN server and change the Default Access Level.

In R410.6 (and later) and R430.2 (and later) it is possible to configure the fastest rate that Peer Responder will perform writes. By default Peer Responder can write every second. When using Peer Responder to write to TPS point parameters, suggest changing the fastest rate that Peer Responder will perform writes to be 2000ms. Be careful not to make the value too high as this can cause delays in the Control Module processing.

To adjust Peer responder write rate perform these steps on both the primary and backup Experion server machines:

1. Open regedit.exe and expand the following tree: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Honeywell\TPS50\CDA\CDASp

2. Double click RegRespSweepPeriod to edit the value. This value is the fastest rate that Peer Responder will perform writes in milliseconds.

3. Change the value to 2000 (Decimal).

2.3 OPC Integrator

Customers typically configure OPC groups at different group rates (e.g. 1 second, 2 seconds, 5 seconds, and 30 seconds). Because peer responder reads are always done at the CEE peer subscription period, peer responder is not a direct replacement for OPC Integrator. It can only replace groups that were previously at the 1 second rate.

OPC Integrator is designed to have one write outstanding per group rate at any one time. Peer responder can have multiple writes outstanding.

2.4 TPS

Use of peer responder with TPS points requires careful consideration. Reads & writes at the one second rate can cause slow down of the ESVT impacting flex stations & DSA connections & OPC applications.

Insert a param connector with the point parameter that is being written to through peer responder.

This is the deadband configuration value.

Replace the NUMERIC block with the value that is writing to peer responder.

Honeywell


Owner: Category:

Global TAC





2.5 SCADA

Use of peer responder with SCADA points also requires careful consideration. SCADA channels can typically support one point parameter write per second. Peer responder reads do not place additional load on the SCADA network.

2.6 DSA

DSA adds additional latency to reads and writes. This needs to be taken into consideration when designing the control strategy.

Attention:

DSA point name has to be unique across clusters. The DSA point with the same name in another cluster cannot be configured for peer-to-peer communication.

3 FEATURE DESCRIPTION

3.1 CEE Controller Points

The peer-to-peer communication with non-CEE points is possible in the control strategies assigned to the CEE points using the following functions.

Parameter connector

SCM expression

SCM Alias Table

CAB parameter references

PHASE block parameter reference using Formula Parameter and Report Parameters

Expressions in the AUXCALC, ENHAUXCALC, REGCALC, and ENHREGCALC blocks

Attention

Peer-to-peer communication is not supported between the non-CEE points and the following:

C300-20ms CEE

Fieldbus blocks

PMIO and Series C I/O blocks

Control cascade.

3.2 Guidelines for configuring peer-to-peer communication between CEE and non-CEE points

Before configuring the peer-to-peer communication between CEE and non-CEE points, you must adhere to the following common guidelines.

Data type of non-CEE point’s parameters and CEE parameters must be identical.

Note: If you try to configure different data type parameters for peer-to-peer communication, Data Type mismatch error appears.

Honeywell


Owner: Category:

Global TAC





The format in which you need to reference non-CEE peer-to-peer parameters except for TPS points must be as follows:

<point name>.<parameter name>[<array index1>,<array index2>] Note: Use Square bracket [] instead of braces ().

The format for configuring the TPS points must be as follows:

<point name>.<parameter name>(<array index1>,<array index2>)

For TPS points, only alphanumeric characters and the following special characters can be used while configuring the expressions.

Underscore (_)

At sign (@)

Dollar sign ($)

Attention

Whole array peer-to-peer communication is not supported between CEE and non-CEE points.

CAB on ACE dynamic re-referencing is not supported for non-CEE peer-to-peer references.

You cannot configure non-CEE points in the Server History and Trend configuration of CM in Control Builder

Non-CEE points are not listed in the Point Picker. Therefore, you must remember the correct non-CEE point names to configure in the control strategies.

The following parameters of the SCM-STEP block cannot be configured for peer-to-peer communication with the non-CEE points.

o OP[].INSTRUCTTYPE

o OP[].CURRVALREF

o OP[].ENTRYVALREF

o OP[].MONTASKREF

o OP[].TARGETVALREF

o OP[].TARGETDESCREF

o OP[].TARGETMAXREF

o OP[].TARGETMINREF

o OP[].TARGETEUDESCREF

o OP[].CURRDESCREF

o OP[].CURREUDESCREF

o OP[].ENTRYDESCREF

o OP[].ENTRYMAXREF

Honeywell


Owner: Category:

Global TAC





o OP[].ENTRYMINREF

o OP[].ENTRYEUDESCREF

Before configuring a peer-to-peer reference in the Control Builder to an Experion Server point, you must ensure the following:

The point to which the peer-to-peer communication is being configured must exist in the Experion Server database.

Performing the Experion Server peer-to-peer configuration when both servers are running and are in synchronization is recommended. If you perform peer-to-peer configuration when only one server running as primary, ensure that the System Repository is in synchronized state after the other server is started as backup server.

Ensure that you do not perform Experion server peer-to-peer configuration and load when the servers are in dual primary state. If you attempt to do so, the peer-to-peer communication between the Experion server points would be lost once the servers recover from the dual primary state.

TPS points must be primed before referencing them for peer-to-peer communication.

Array parameter of the TPS point must be configured before configuring the peer-to-peer configuration to the array parameter of the TPS point in the Experion Controllers (Example: C300, C200E or ACE). If you want to reconfigure the array parameter of the TPS point, you must reload the control strategy. To reload the control strategy, follow the below procedure:

When an Experion Server point is deleted, the function block running in one of the CEE controllers and reading the Experion point.parameter receives “FAILSAFE” value. However, if the deleted Experion Server point is recreated with the same name and reloaded, the function blocks continues to receive the “FAILSAFE” value. To avoid this issue, perform the following steps.

Delete the control modules referring to the Experion Server point.parameter completely from the Monitoring view. Note: You can use Configuration Studio Search Tool to find the Experion Server point.parameter references in

control modules (Search is performed on project configuration and assumption is that project and monitor configuration is almost the same)

Wait for 20 seconds and reload the control modules from the Project to the Monitoring view. Note: Even, if one of the control modules referring to the Experion Server point.parameter is not deleted from

the Monitoring view, the function blocks reading the Experion Server point.parameter continues to receive the “FAILSAFE” value. This is applicable though the corresponding control module is deleted/reloaded in the Monitoring view.

Data type of the OPC advanced point is always configured as FLOAT64 parameter. Hence, peer-to-peer configuration has to be done for FLOAT64 parameter only in the Control Builder. For data type conversion (example, converting a data type from FLOAT64 to INT16), use TYPECONVERT block for peer-to-peer communication.

Variant data types published by point servers cannot be added to peer-to-peer Attention: Minimum Subscription rate is 1sec.

3.3 Configuration Example

On the below screen shot is shown example control module making use of the above described CEE to non-CEE point peer to peer connection.

Honeywell


Owner: Category:

Global TAC





3.4 Designing the control strategy for Failsafe control

Projects utilizing peer responder to read non-CEE values in their C300 control strategies must consider handling of communication disconnection scenarios. There are two main reasons which could cause a transfer of bad value to C300

Server Failover The failover from the primary Experion server to the backup Experion server may take between 30-70 seconds (depending upon the size of the system). When Experion fails over to the backup server, values from non-CEE points that are being read by the CEE through Peer Responder will not be available.

Point becoming bad at its native interface The non-CEE point being transferred through peer responder may become bad because of sensor failure or communication loss with controller where this point resides.

Normally the control failsafe value should not be transferred directly to the process, since this could cause setting incorrect setpoints or inadequate logic results, generating process bumps or trips. The control failsafe value can be handled in number of ways including:

- Hold the previous good value until the non-CEE point parameter returns from control failsafe to good values again - Hold the previous good value for a defined period (e.g. 70 seconds) and then write a specific value to the process to

indicate that the input is bad The control strategy logic below can be used to detect the control failsafe value for each data type. The table also lists the values that the CEE will see for non-CEE points during disconnection event.

Data Type Example Point

Parameter Control Failsafe

value Detecting Failsafe value

SCADA

Floating point

(FLOAT64)

ANA01.PV NaN

Two different Function blocks could be used , depending on control strategy needs as shown below

1. Using CHECKBAD Function block

2. Using DATA ACQUISITION Function block

Honeywell


Owner: Category:

Global TAC





TPS

Floating Point

(FLOAT32)

TPS_REG001.PV NaN

SCADA/TPS

Enumeration

(ENUM)

ANA01.MODE

STA01.PV

TPS_ALM.MODE

Enum0

TPS

Boolean

(BOOLEAN)

Enum0

SCADA/TPS

Integer

(INT16)

ANA01.INALM

STA01.NumberOfInputStates

TPS_ALM.NOPINPTS

0

Additional logic could be built to implement the appropriate behaviour for the process. Instructions on the usage of the example CAB blocks provided with this document are described below. Step 1: Choose the failsafe handling CAB block appropriate for the input data type:

Data Type CAB Block

FLOAT FAILFLOAT_01S

ENUM

INT

FAILINT_01S

BOOLEAN FAILBOOL_01S

Step 2: Reference the input parameter in the CAB block:

Honeywell


Owner: Category:

Global TAC





Step 3: Decide on the way the failsafe value should be handled:

a) Option 1 - Hold the previous good value until the non-CEE point parameter returns from control failsafe to good values again. Set HOLDTIME to NaN.

The following table provides some examples of what the CAB blocks will output when input values become bad.

Data Type CAB Block Results

FLOAT FAILFLOAT_01S

ENUM FAILINT_01S


Honeywell


Owner: Category:

Global TAC





INT FAILINT_01S

b) Option 2 - Hold the previous good value for a defined period and then write a specific value to the process to indicate that the input is bad. Set HOLDTIME to the desired hold period and BADOUT to the specific value you want to write when input is bad. For example to configure the CAB block to output the value NaN for a FLOAT after a timeout of 70 seconds, set HOLDTIME to 70 and BADOUT to NaN.

The following table shows what the CAB blocks will output when input values become bad, both during and after the hold period.

Data Type CAB Block Results

During the HOLDTIME period

Results

After the HOLDTIME period

FLOAT FAILFLOAT_01S

ENUM FAILINT_01S


Honeywell


Owner: Category:

Global TAC





INT FAILINT_01S

3.5 Experion Server Peer Responder Performance

The following table describes the Performance and Capacity limits for these new Server Peer-Peer connections.

Experion Server Peer Responder Communications Performance

Definitions: PPS = Average Parameters Per Second PPM = Average Parameters Per Minute

Experion Server

(CDAsp)

Peer-to-Peer Performance Total Maximum Target Publish Rate to Pull/Get Subscriptions from all initiator nodes. (outgoing data)1,2,3

1200 PPS

Maximum Target Publish Rate for TPS points to Pull/Get Subscriptions from all initiator nodes. (outgoing data) 1,2,3,6,7

(Included as part of the total rate above)

400 PPS

Peer-to-Peer Subscription Update Rate Fastest Server Peer publication period to controllers

(Subscriptions at slower rates are allowed as long as the slower rate is supported by the initiator) 1 sec

Push/Store Request Performance Total Maximum Response Rate to Push/Store Requests from all initiator nodes3,5 350 PPS

Maximum Response Rate for TPS points to Push/Store Requests from all initiator nodes5,6,7

(Included as part of the total rate above)

150 PPS

Peer-to-Peer Capacity

Maximum Total Subscribed Parameters per Server Cluster (Includes all CDA Peer subscription from CEE Controllers)

2500 parameters

Maximum Total simultaneous Request/Response capacity of Experion Server4 1000 parameters

Peer Connection Units (PCUs)

(Number of Controllers that the Experion Server can respond to a remote peer connection request with)1

30

(Includes total of ACEs, SIM- ACEs, C200Es, SIM-C200Es,

C300s, SIM-C300s)

Redundant Server Failover

Maximum Time for CDA on the Server to re-establish Peer-Peer connections to controllers after a Backup Server becomes Primary Server following failover

1 minute

Honeywell


Owner: Category:

Global TAC





Notes:

1 – Experion Server as a Peer to CDA Controllers is only a CDA Data Responder Node. No Peer-Peer transactions can be initiated from the Experion Server.

2 – Outgoing peer data capacity is defined/measured before the RBE (Report by Exception) comparisons are done, so all parameters requested as peer data contribute to the outgoing PPS load, whether they are changing or not and sent over the network or not.

3 – Includes all Server Point types, e.g. TPS, SCADA, DSA, OPC, Point Servers, although the TPS points are further restricted by the next row.

4 – Includes writes from controllers

5 – Ability to deliver write data rate depends upon throughput of underlying process control network. As per the specifications for the underlying subsystems the number of write transactions per second is limited in addition to the maximum throughput. It is recommended that as few list writes are done as possible in as large lists as possible.

6 - Assumes the parameters are already primed.

7 – Reads and writes for TPS point parameters must comply with the LCN connected Experion server restrictions which take into account all reads and writes to TPS point parameters happening on the ESVT. Please see Experion server technote 343 (LCN connected Experion server performance and capacity).

3.6 Experion Server Peer Responder Display

This display give information about the below described parameters.

Property Description

Total parameters subscribed The total number of parameters subscribed to on the server.

Total parameters output The total number of parameter values returned to the subscribing peer.

Average parameter output The average number of parameters reported per second (maximum 5-second average).

Maximum average parameter output

The highest value of the average number of parameters reported per second.

Total one shot writes The total number of writes.

Transaction count Increments by one each time a request is made to the server.

Reset statistics Resets all counters to zero.

Last reset The last date and time that the counters were reset to zero.

To invoke this display in the station go: View > System Status > Experion Server Responder

3.7 Advanced Peer to Peer Functionality

Non CEE P2P does not support back initialization (cascade) or pre-fetch, so for applications requiring advanced P2P, an ACE-T or inter cluster gateway would be used:

ACE-T is required to support the following functionalities (these features are not available in CEE to non CEE p2p communication via the ESVT).

a. Cascade connection between Experion Controllers and HPM b. LCN Prefetch

ICG supports Cascade connection between controllers that are part of different Experion Clusters (using the REEOUT block). Such a cascade connection is not supported in DSA & CEE-NonCEE p2p combination.

If only peer read from controllers / non-cascade writes to controllers is desired, then CEE to non CEE p2p communication shall be used for achieving this without the use of ACET or ICG.:

Honeywell


Owner: Category:

Global TAC





4 TAC CONTACTS

Marin Ruskov – [email protected]

Strezimir Dukovski – [email protected]

mailto:[email protected]

mailto:[email protected]

experion r410 and later - honeywell · 2014-11-03 · prior to r410, opc integrator and opc gateway...

Documents