experion mx vio - balibago platform - experion mx/6510020405.pdf · experion mx vio user manual...

Experion MX VIO

User Manual 6510020405

Experion MX VIO User Manual

March, 2012

Confidentiality Statement

This manual is a product of Honeywell. It is intended for use only by Honeywell and customer personnel in connection with Honeywell products. It is strictly prohibited to copy this manual or any part thereof or to transfer this manual or any part thereof to any non-Honeywell person or entity, except customer personnel for use in connection with Honeywell products. Persons employed by a third-party service company shall not have access to this manual.

Notice

All information and specifications contained in this manual have been carefully researched and prepared according to the best efforts of Honeywell, and are believed to be true and correct as of the time of this printing. However, due to continued efforts in product improvement, we reserve the right to make changes at any time without notice.

Trademarks

All trademarks and registered trademarks are the properties of their respective holders.

Copyright

© 2012 Honeywell

All rights reserved. No part of this publication may be reproduced or translated, stored in a database or retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of Honeywell.

P/N: 6510020405 3/29/12 i

Contents

Introduction .............................................................................................................................................. iii Audience ................................................................................................................................................ iii About This Manual ................................................................................................................................ iii Conventions ........................................................................................................................................... iv

1. Overview ............................................................................................................................................ 1-1 1.1. Link-Level Interface ................................................................................................................. 1-2 1.2. Object Groups ........................................................................................................................... 1-2

1.2.1. Controller Object Interface ........................................................................................... 1-3 1.2.2. Analog and Digital Input Objects Interface .................................................................. 1-3 1.2.3. Object Grouping Example ............................................................................................ 1-3

1.3. Straight-Through Data .............................................................................................................. 1-5 1.4. Initialization Issues ................................................................................................................... 1-5 1.5. OPC Server Specifics ................................................................................................................ 1-5

2. Data Transfer .................................................................................................................................... 2-1 2.1. Reading Data from the Server ................................................................................................... 2-1 2.2. Writing Data to the Server ........................................................................................................ 2-1

2.2.1. Object Group Configuration ......................................................................................... 2-2 2.2.2. Data Fresh Flag ............................................................................................................. 2-2 2.2.3. Recommended Object Group Configuration ................................................................ 2-2

2.3. Object Variable Transfer Names............................................................................................... 2-3

3. Object Variable Transfer ................................................................................................................. 3-1 3.1. Object Variable Lists ................................................................................................................ 3-1

3.1.1. Analog Input Object ...................................................................................................... 3-1 3.1.2. Controller Object .......................................................................................................... 3-2 3.1.3. Digital Input Object ...................................................................................................... 3-2 3.1.4. Link Level ..................................................................................................................... 3-3

Experion MX VIO User Manual Contents

3/29/12 P/N: 6510020405 ii

3.1.5. Object Group Level ...................................................................................................... 3-3 3.2. Interface Variables .................................................................................................................... 3-3

3.2.1. Variable Description ..................................................................................................... 3-3 3.2.2. Control Mode Definition .............................................................................................. 3-6

4. Controller Interface Scenarios ......................................................................................................... 4-1 4.1. Scenario 1, Remote/Local Concept with Bidirectional Control ............................................... 4-1 4.2. Scenario 2, Man/Auto/Cascade Concept with Bidirectional Control ....................................... 4-3

List of Figures Figure 1-1 Shows the platform of the RAE600 system server ................................................................ 1-1

List of Tables Table 3-1 Analog Input Objects .............................................................................................................. 3-1Table 3-2 Controller Objects ................................................................................................................... 3-2Table 3-3 Digital Input Object ................................................................................................................. 3-2Table 3-4 Link Level ............................................................................................................................... 3-3Table 3-5 Object Group Level ................................................................................................................. 3-3Table 3-6 Control Modes ......................................................................................................................... 3-6Table 4-1 Remote/Local Concept with Bidirectional Control ................................................................. 4-1Table 4-2 Man/Auto/Cascade Concept with Bidirectional Control ........................................................ 4-3

P/N: 6510020405 3/29/12 iii

Introduction

The purpose of this manual is to define the communication interface between the Experion MX and DCS vendors for virtual control of inputs and controllers.

Audience This manual is intended for use by DCS vendors and technical personnel involved in using the Experion MX product as the server for the communication interface between 2 systems.

About This Manual This manual contains 4 chapters.

Chapter 1, Overview, provides a general overall description of the communication interface between a vendor’s client system and the Experion MX system.

Chapter 2, Data Transfer, describes the basic requirements of data transfer from the client system to the Experion MX system.

Chapter 3, Variable Transfer List, provides tables listing the variables needed for the different types of objects supported in the interface. A functional description is also provided for each variable found in the interface.

Chapter 4, Controller Interface Scenarios, describes 2 different control interface scenarios based on 2 different control strategies.

Experion MX VIO User Manual Introduction

3/29/12 P/N: 6510020405 iv

Conventions The following conventions are used in this manual:

Text may appear in uppercase or lowercase except as specified in these conventions. Boldface Boldface characters in this special type indicate your input. Special Type Characters in this special type that are not boldfaced indicate system

prompts, responses, messages, or characters that appear on displays, keypads, or as menu selections.

Italics In a command line or error message, words and numbers shown in italics represent filenames, words, or numbers that can vary; for example, filename represents any filename. In text, words shown in italics are manual titles, key terms, notes, cautions, or warnings.

Boldface Boldface characters in this special type indicate button names, button menus, fields on a display, parameters, or commands that must be entered exactly as they appear.

lowercase In an error message, words in lowercase are filenames or words that can vary. In a command line, words in lowercase indicate variable input.

Type Type means to type the text on a keypad or keyboard. Press Press means to press a key or a button. [ENTER] or [RETURN]

[ENTER] is the key you press to enter characters or commands into the system, or to accept a default option. In a command line, square brackets are included; for example: SXDEF 1 [ENTER]

[CTRL] [CTRL] is the key you press simultaneously with another key. This key is called different names on different systems; for example, [CONTROL], or [CTL].

[KEY-1]-KEY-2 Connected keys indicate that you must press the keys simultaneously; for example, [CTRL]-C.

Click Click means to position the mouse pointer on an item, then quickly depress and release the mouse button. This action highlights or “selects,” the item clicked.

Double-click Double-click means to position the mouse pointer on an item, and then click the item twice in rapid succession. This action selects the item “double-clicked.”

Drag X Drag X means to move the mouse pointer to X, then press the mouse button and hold it down, while keeping the button down, move the mouse pointer.

Press X Press X means to move the mouse pointer to the X button, then press the mouse button and hold it down.

Introduction Conventions

P/N: 6510020405 3/29/12 v

The attention icon appears beside a note box containing information that is important.

The caution icon appears beside a note box containing information that cautions you about potential equipment or material damage.

The warning icon appears beside a note box containing information that warns you about potential bodily harm or catastrophic equipment damage.

P/N: 6510020405 3/29/12 1-1

1. Overview

The RAE600 system can be used as the server in a server/client communication network. The system can handle client controllers and process inputs. This document defines the interface to the client controllers and inputs. Using these definitions, the client system can create an application to transfer needed information to and from the RAE600 system. Once in the RAE600 system, this data is used in complex supervisory control and to display data on a single window operator interface.

The platform of the RAE600 system server can be simplified into the figure below.

Figure 1-1 Shows the platform of the RAE600 system server

Reads

Writes Client System

Da Vinci Platform

Real-Time Data Repository

Inputs, Status Outputs, Setpoints, Mode, Limits, Alarms

Outputs, Setpoints, Mode

Supervisory Control

Operator Interface

Server

Experion MX VIO User Manual Overview

3/29/12 P/N: 6510020405 1-2

1.1. Link-Level Interface To check on the health of the link, there are 2 variables:

• A heartbeat signal used in the RAE600 system to monitor the health of each link. Each configured client link is required to have one of these variables.

• A flag set every 2 seconds by the RAE600 systems, letting the client system know when the application is up and running normally. Each client link will have configured groups of objects associated with it.

1.2. Object Groups The Object Groups are used to group a collection of objects that have their required data available to the RAE600 system at the same time. These objects include:

• Controllers

• Analog Inputs

• Digital Inputs

The client system controls the update time through a flag (data fresh) assigned to each Object Group. The flag is set by the client system each time all of the required data for that group is available at the RAE600 system. After reading the data, the RAE600 system will reset the flag. As stated in Section 3.2.3, “Recommended Object Group Configuration,” all of the objects within a particular link may be in one Object Group.

Overview Object Groups

P/N: 6510020405 3/29/12 1-3

1.2.1. Controller Object Interface In this interface, the RAE600 system receives the setpoint, process value, and output from the client controller. Statuses such as the state of the process value and wind-up conditions are also received so the RAE600 system can display the state of the controller. The system can also control the controller’s mode, setpoint, and output through variables that the client system can read periodically. By receiving the minimum and maximum values for setpoint, process value, and output, the RAE600 system can also perform limit checking, scale the display variables, and send limit alarms to the operator.

1.2.2. Analog and Digital Input Objects Interface For the input interface, the RAE600 system needs to receive the process value from the client system. The status of the input is received so the RAE600 system can show the state of the input. In the case of the analog input, the minimum and maximum limits are also sent to the RAE600 system for use in limit checking and alarms.

1.2.3. Object Grouping Example Two different types of grouping are defined for this interface:

• Link transfer grouping

• Application interface grouping

The link transfer grouping is the transfer groups of the communications link, such as OPC read/write groups or ODX read/write groups.

The application interface grouping is the interface structure used within the RAE600 system, and its use is defined in this manual.

Although the main focus of this document is the application interface, both groupings are shown in the example on the following page.


3/29/12 P/N: 6510020405 1-4

Link Transfer Groupings Application Interface Groupings Read transfer group 1

Control1.setpoint req Control1.output req Control1.auto req Control1.cascade req Control2.setpoint req Control2.output req Control2.auto req Control2.cascade req Control3.output req Control3.setpoint req Control3.auto req Control3.cascade req Client1.serverapplok

Write transfer group 1 Control1.setpoint Control1.output Control1.auto Control1.cascade Control1.status Control2.setpoint Control2.output Control2.auto Control2.cascade Control2.status Control3.setpoint Control3.output Control3.auto Control3.cascade Control3.status Client1.data fresh1

Write transfer group 2 Input1.value Input1.status Input2.value Input2.status Client1.data fresh2

Write transfer group 3 Client1.DCSCommOK Client1.serverapplok

Client1 Client1.DCSCommOK Object Group 1

Control1.setpoint req Control1.setpoint Control1.output req Control1.output Control1.auto req Control1.cascade req Control1.auto Control1.cascade Control1.status Control2.setpoint req Control2.setpoint Control2.output req Control2.output Control2.auto req Control2.cascade req Control2.auto Control2.cascade Control2.status Control3.setpoint req Control3.setpoint Control3.output req Control3.output Control3.mode req Control3.auto req Control3.cascade req Control3.auto Control3.cascade Control3.status Client1.data fresh1

Object Group 2 Input1.value Input1.status Input2.value Input2.status Client1.data fresh2

Overview Straight-Through Data

P/N: 6510020405 3/29/12 1-5

The preceding example is only provided to demonstrate the concept for the project teams. The link transfer groupings should be set up in a way that best fits the link’s specific characteristics and system topology, and that follows the guidelines of the server interface defined in this document. The application interface groupings may also be set up in other configurations, depending on the requirements of the system.

1.3. Straight-Through Data Standard OPC (or ODX) data transfers can be used to directly exchange data not requiring the object grouping and the specific handshaking defined in this document. MIS data, grade data, and sheet break signals are examples that would need to be determined and agreed upon on a project requirement basis.

1.4. Initialization Issues The RAE600 server expects all of the required data in all of the Object Groups to be refreshed before ServerApplOK is updated in the RAE600 system. Also, the data read from the server should not be used until the ServerApplOK variable changes value. This is to ensure that the setpoint, mode, and output tracking are completed before the controllers are put under supervisory control. This means that any time the client system sees the link status change to “link up,” the client should force a transfer of all of the read/write data.

1.5. OPC Server Specifics The communication interface of choice is OPC. The RAE600 OPC Server is based on the v1.0A specification dated September 11, 1997. In addition to the required interfaces, the server also supports the optional IOPCServerBrowseServerAddressSpace interface with a hierarchical namespace. This allows the RAE600 database to be browsed by OPC clients.

The server can be referenced by the Program ID (PROGID) Hmx.RaeServer_O. OPC servers are addressed by a combination of PROGID and machine name unless the client is on the same machine as the server, in which case only the PROGID is required. Since OPC is based on Microsoft’s DCOM, all remote connections are subject to NT security.


3/29/12 P/N: 6510020405 1-6

Data types in OPC are polymorphic. A server returns a canonical data type for each item (for example, VT_I2). The client can choose to accept this and use it for all read/write operations. Alternatively, a client can request that a specific item be treated as a requested data type. In this case, the server will perform all necessary data conversions if the requested type is convertible to the canonical type.

P/N: 6510020405 3/29/12 2-1

2. Data Transfer

This chapter deals with the interface data transfer of both reads and writes. It describes the concept of Object Groups and the data fresh flag.

2.1. Reading Data from the Server When reading data, the client should typically request the data at a 1-second rate, either through a periodic read or when data has been changed. Data that is changed by the RAE600 system is outputs, setpoints, and modes. If the client system does not require the data at a rate of 1 second, a slower rate may be configured for slower-executing controllers. During initialization, the client system should not use any data read from the server until it detects a change in the ServerApplOK value.

2.2. Writing Data to the Server The client must inform the RAE600 server when updated data is available at the server. This is done through the use of Object Groups. Object Groups are a collection of object references, such as controllers, containing data transferred to the RAE600 server. Each client link will have at least one of these groups configured. Within each group is a flag (data fresh) used to notify of data availability at the server system.

Experion MX VIO User Manual Data Transfer

3/29/12 P/N: 6510020405 2-2

2.2.1. Object Group Configuration Each client has a number of controllers and/or input devices that interface with the RAE600 server. Each one of these controllers and input devices is referred to as an object in the RAE600 platform. Every object must contain a reference in an Object Group configured in the RAE600 system. Each of these Object Groups has a data fresh flag, which is set by the client when all of the required data for all of the objects in that group is available. This does not mean that all data must be updated before this flag is set, but only that required data that has changed since the last update is refreshed.

2.2.2. Data Fresh Flag The data fresh flag is set by the client application after all of the latest data for the associated Object Group has been updated. The update should occur when the data within a given group has changed, but not faster than a 1-second rate. If there is no change in the data, the RAE600 system requires a periodic validation of the data freshness. Typically, RAE600 expects fresh data every 2 seconds. Again, this is done by setting the data fresh flag.

2.2.3. Recommended Object Group Configuration It is up to the project team to determine the best way to set up the Object Groups. In this section, the following suggestions are made to help with that determination.

It is perfectly acceptable to have all of the objects in one Object Group with one data fresh flag, which is used for client write synchronization.

Client1

Client1.DCSCommOK Object Group 1

Controller 1 Controller 2 Input 1 Data fresh

The topology of the total system, rate of object updates, and link limitations may suggest that more than one Object Group is in order.

Client2

Data Transfer Object Variable Transfer Names

P/N: 6510020405 3/29/12 2-3


Controller 1 Controller 2 Data fresh 1

Object Group 2 Input 1 Input 2 Data fresh 2

Another system may warrant multiple Object Groups of controllers and input objects.

Client3


Controller 1 Controller 2 Data fresh 1

Object Group 2 Controller 3 Controller 4 Controller 5 Data fresh 2

Object Group 3 Input 1 Input 2 Data fresh 3

Object Group 4 Input 3 Input 4 Input 5 Data fresh 4

2.3. Object Variable Transfer Names It is recommended that the client system use the following naming convention for the variables to be transferred. The convention is object name, separator character, and RAE600 field name. For example, the name for the setpoint written into the RAE600 system for the stockflow controller would be stockflow.setpoint. The name for an analog input object’s process value might be dye1234.value.

Experion MX VIO User Manual Data Transfer

3/29/12 P/N: 6510020405 2-4

P/N: 6510020405 3/29/12 3-1

3. Object Variable Transfer

Following are lists of variable field names used in the RAE600 Server to display and supervise a controller or simple input object. The client system must provide these variables on variable change and/or at a periodic rate defined for each Object Group (typically every 2 seconds).

3.1. Object Variable Lists The lists of objects in the following sections show the RAE600 field name, the RAE600 field type, the direction of transfer, and the OPC canonical type for each variable. The OPC canonical type is provided here to define the variable type as seen in the OPC environment, and as a reference for uses with other communication protocols. A later section will go into a more detailed definition of the meaning and function of each variable.

Some communication interfaces, such as OPC, provide for data-type conversion. Therefore, the data types indicated below need not be the types of the corresponding variables on the client system.

3.1.1. Analog Input Object Table 3-1 Analog Input Objects

RAE600 Field Name Field Type Transfer Direction OPC Canonical Type

Value Double ← VT_R8 Status Byte ← VT_I2 Value max * Double ← VT_R8 Value min * Double ← VT_R8

Experion MX VIO User Manual Object Variable Transfer

3/29/12 P/N: 6510020405 3-2

Alarm status * Byte array ← VT_ARRAY (VT_I2) * Field is optional; not required in the object data freshness update.

3.1.2. Controller Object Table 3-2 Controller Objects


Value Double ← VT_R8 Status Byte ← VT_I2 Windup Status * Long ← VT_I4 Setpoint Double ← VT_R8 Output Double ← VT_R8 Auto mode Byte ← VT_I2 Cascade mode Byte ← VT_I2 Setpoint req Double → VT_R8 Output req Double → VT_R8 Auto req Byte → VT_I2 Cascade req Byte → VT_I2 Value max * Double ← VT_R8 Value min * Double ← VT_R8 Setpoint max * Double ← VT_R8 Setpoint min * Double ← VT_R8 Output max * Double ← VT_R8 Output min * Double ← VT_R8 Alarm status * Byte array ← VT_ARRAY (VT_I2) * Field is optional; not required in the object data freshness update.

3.1.3. Digital Input Object Table 3-3 Digital Input Object


Value Byte ← VT_I2

Status Byte ← VT_I2

Alarm status * Byte array ← VT_ARRAY (VT_I2)

* Field is optional; not required in the object data freshness update.

Object Variable Transfer Interface Variables

P/N: 6510020405 3/29/12 3-3

3.1.4. Link Level Table 3-4 Link Level


DCSCommOK Byte ← VT_I2

ServerApplOK Long → VT_I4

3.1.5. Object Group Level Table 3-5 Object Group Level


Data fresh Byte ← VT_I2

3.2. Interface Variables The following section describes the variables within the RAE600 system.

3.2.1. Variable Description Alarm status – (optional) This byte array is used to transfer any alarm

information to the RAE600 system. (Format TBD)

Auto mode – This is the actual state of the controller at the client system. This variable should be set whenever the controller is in Auto or Cascade mode. In the case of Cascade, the Cascade Mode variable must also be set. A value of 0 means that the controller is in Manual mode. This variable works in conjunction with the Cascade mode and Status to display the correct mode and status. (For more details, see Section 4.2.2, “Control Mode Definition.”)

Auto req – This is the request from the RAE600 system to set the client controller to Auto mode. Reading a value of 1 is the server’s request for the client controller to go into Auto mode. A transition in Auto mode or a mode change request at the RAE600 system will affect the value of this


3/29/12 P/N: 6510020405 3-4

variable. Because of the tracking property of this variable, the client should consider acting only on a transition of this variable, or block the action of this variable when the client mode changes until the request reflects that change.

Cascade mode – This is the actual state of the controller. A value of 1 denotes that the controller is in Cascade mode at the client system. A value of 0 means that the controller is in Auto or Manual mode. This variable works in conjunction with the Auto mode and Status to display the correct mode and status. (For more details, see Section 4.2.2, “Control Mode Definition.”)

Cascade req – This is the request from the RAE600 system to set the controller to Cascade mode. Reading a value of 1 is the server’s request for the client controller to go into Cascade mode. A transition in Cascade mode or a mode change request at the RAE600 system will affect the value of this variable. Because of the tracking property of this variable, the client should consider acting only on a transition of this variable, or block the action of this variable when the client mode changes until the request reflects that change. If the client does not support the concept of a Cascade mode, the Cascade req variable should be fed back into the Cascade mode variable directly.

Data fresh – This is the flag used by the client system to indicate that the data in an Object Group is ready for use in the RAE600 system. The client sets this variable after all data in the Object Group associated with it has been updated to the latest values. The RAE600 system will zero (0) the variable after the data is consumed.

DCSCommOK – This variable is the heartbeat for the communication link between the RAE600 and client system. The client system sets this variable to a 1 (no slower than 2 seconds and no faster than 1 second). The RAE600 system will reset the value every 2 seconds after reading it. If the RAE600 system sees that the value of DCSCommOK is not set for 6 seconds, it will declare the link down and set the controllers associated with the link to a suspended mode. The suspend status will be removed when this flag is set again. There is one of these variables for each client link.

Output – This is the actual output value of the controller, and it is the value displayed on the RAE600 operator interface.

Output max – (optional) This variable is used for limit checking and scaling of the display output. If this variable is never sent from the client system, the values must be configured in the RAE600 system at system build time.

Object Variable Transfer Interface Variables

P/N: 6510020405 3/29/12 3-5

Output min – (optional) This variable is used for limit checking and scaling of the display output. If this variable is never sent from the client system, the values must be configured in the RAE600 system at system build time.

Output req – This variable requests an output value from the RAE600 system when the controller is in Manual mode.

ServerApplOK – This variable is available to the client system, and it indicates that the server application is up and running. The RAE600 system increments this variable every 2 seconds between a range of 0 and 100. The client system should read this variable for initialization purposes and as verification that the application in the server is running normally. When this variable changes, the RAE600 system is ready to accept control for the client objects. If this variable does not change for longer than 10 seconds at the client, the client system should set all of the objects to a local control state and refresh all data, then continue to update the data at the normal rate until ServerApplOK starts incrementing again.

Setpoint – This is the actual setpoint value for the controller, and it is the value displayed on the RAE600 operator interface.

Setpoint max – (optional) this variable is used for limit checking and scaling of the display setpoint. If this variable is never sent from the client system, the values must be configured in the RAE600 system at system build time.

Setpoint min – (optional) this variable is used for limit checking and scaling of the display setpoint. If this variable is never sent from the client system, the values must be configured in the RAE600 system at system build time.

Setpoint req – This variable requests setpoints from the RAE600 system.

Status – This variable is used to mark the Value variable bad. Conditions such as hardware failures and interlock conditions on the client system should set this to a 0. A value of 1 indicates that the controller is ready for control. This variable works in conjunction with the Auto mode and Cascade mode to display the correct controller mode and status. (For more details, see Section 4.2.2, “Control Mode Definition.”)

Value – This variable is the process value from the client system. This is the value displayed on the RAE600 operator interface.

Value max – (optional) this variable is used for limit checking and scaling of the display value variable. If this variable is never sent from the client system, the values must be configured in the RAE600 system at system build time.


3/29/12 P/N: 6510020405 3-6

Value min – (optional) this variable is used for limit checking and scaling of the display value variable. If this variable is never sent from the client system, the values must be configured in the RAE600 system at system build time.

Windup status – (optional) This is used to flag the controller as to when and when not to accept new controller output changes while in Auto or Cascade mode. The values of this variable are as follows:

1 - normal mode; all outputs accepted

2 - high limit; only negative change outputs are accepted

3 - low limit; only positive change outputs are accepted

4 – high low limit; no outputs are accepted

If this variable is not sent to the RAE600 system, the default will be to accept all outputs.

3.2.2. Control Mode Definition There are 3 variables that work in conjunction to define the mode and status of a controller: Auto mode, Cascade mode, and Status. The table below defines their interaction and the resulting mode, color, and status displayed on the RAE600 operator interface.

Table 3-6 Control Modes

Cascade Mode

Auto Mode

Status

Mode

Color

Status

0 0 0 Manual Red Not Ready 0 0 1 Manual Green Ready 0 1 0 Auto Red Suspend 0 1 1 Auto Green Computer 1 0 0 Cascade Red Suspend 1 0 1 Cascade Red Suspend 1 1 0 Cascade Red Suspend 1 1 1 Cascade Yellow Cascade

P/N: 6510020405 3/29/12 4-1

4. Controller Interface Scenarios

Two examples of interface scenarios are provided here to help client application designers visualize how the interface might be implemented for their specific controller objects.

4.1. Scenario 1, Remote/Local Concept with Bidirectional Control

This scenario assumes that the client system has the concept of local and remote, and accepts setpoints and (optionally) outputs from the RAE600 server system when in remote.

Table 4-1 Remote/Local Concept with Bidirectional Control

Da Vinci Field Name

Transfer Direction

Description

Value ← Process value from the client controller. Written to the server at the appropriate rate for the application.

Status ← Status is set when the RAE600 system is able to take control of the controller. This would be when the controller is not in an alarm condition and the mode of the controller, at the client system, is in remote.

Setpoint ← Setpoint from the client controller. Written to the server at the appropriate rate for the application. This is used for setpoint tracking.

Output ← Output from the client controller. Written to the server at the appropriate rate for the application. This is used for output tracking.

Experion MX VIO User Manual Controller Interface Scenarios

3/29/12 P/N: 6510020405 4-2

Auto mode ← For client systems that allow manual outputs, this variable is set when the controller is not in Manual mode at the client system. For clients that do not allow manual outputs from the server, this variable should be set when the controller is in remote mode and not in Manual mode.

Cascade mode ← The client will feed back the value of the Cascade req to this variable.

Setpoint req → Setpoint req is used by the client system for the controller setpoint whenever the controller is in remote mode.

Output req → Output req is used by the client system for the controller output whenever the controller is in the remote Manual mode. The client does not use this variable if the client does not support the remote Manual mode.

Auto req → Auto req is set by the RAE600 system when the RAE600 system wants the controller in remote Auto mode. Once the remote mode is requested by the RAE600 system, the controller should remain in remote until requested to change to local at the client system. This would allow the RAE600 system to request remote Manual mode (if supported) by resetting the Auto req. Also, if remote Manual mode is not supported, when the Auto req is reset the client system should return to a local state. Whether the controller mode returns to local Auto or Manual is up to the client application.

Cascade req → The client will read this variable and feed the value back into the Cascade mode variable.

Controller Interface Scenarios Scenario 2, Man/Auto/Cascade Concept with Bidirectional Control

P/N: 6510020405 3/29/12 4-3

Cascade Mode

Auto Mode

Status

Cascade Req

Client Mode

Transition Cause

0 0 0 0 Local Manual Client requests local and Manual. 0 0 1 0 Remote Manual

(only applicable if supported)

Client requests remote and Manual mode, or the RAE600 system removes the Auto req and Cascade req.

0 1 0 0 Local Auto Client requests local and Auto. 0 1 1 0 Remote Auto Client requests remote and Auto

mode, or the RAE600 system asserts the Auto req.

1 1 1 1 Remote Auto RAE600 system asserts the Cascade req and Auto req.

4.2. Scenario 2, Man/Auto/Cascade Concept with Bidirectional Control

This scenario assumes that the client system has the concept of Manual, Auto, and Cascade from a client or server system (without a specific remote permissive state required to accept remote setpoints and outputs).

Table 4-2 Man/Auto/Cascade Concept with Bidirectional Control

Da Vinci Field Name

Transfer Direction

Description

Value ← Process value from the client controller. Written to the server at the appropriate rate for the application.

Status ← Status is set when the RAE600 system is able to take control of the controller. This would be when the controller is not in an alarm condition at the client system.

Setpoint ← Setpoint from the client controller. Written to the server at the appropriate rate for the application. This is used for setpoint tracking.

Output ← Output from the client controller. Written to the server at the appropriate

rate for the application. This is used for output tracking. Auto mode ← This is set when the controller is not in Manual mode at the client system. Cascade mode

← This is set when the controller is in Cascade mode at the client system.

Setpoint req → Setpoint req is the requested setpoint from the RAE600 system. The client should use this value for the controller setpoint whenever the requested setpoint changes.

Experion MX VIO User Manual Controller Interface Scenarios

3/29/12 P/N: 6510020405 4-4

Output req → Output req is the requested output from the RAE600 system. The client should use this value for the controller output whenever the output requested changes and the controller is in Manual mode.

Auto req → Auto req is set by the RAE600 system when the RAE600 system wants the controller in Auto mode.

Cascade req → Cascade req is set by the RAE600 system when the RAE600 system wants the controller in Cascade mode.

Cascade Mode

Auto Mode

Status

Cascade Req

Client Mode

Transition Cause

0 0 1 0 Manual Client requests Manual mode, or RAE600 system removes the Auto req and the Cascade req.

0 1 1 0 Auto Client requests Auto mode, or RAE600 system asserts the Auto req.

1 1 1 1 Cascade Client requests Cascade mode, or RAE600 system asserts the Cascade req.

experion mx vio - balibago platform - experion mx/6510020405.pdf · experion mx vio user manual...

Documents