Honeywell RC500 SCONTRL RTU Users Guide

Honeywell Process Solutions

RC500 RC-SCONTRL RTU User's Guide

RC-DCX211 R200

November 2011

Release 200 Honeywell

ii RC500 RC-SCONTRL RTU User's Guide R200 Honeywell November 2011

Notices and Trademarks

Copyright 2011 by Honeywell International Srl. Release 200 November 2011

While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its customers.

In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The information and specifications in this document are subject to change without notice.

Honeywell, PlantScape, Experion PKS, and TotalPlant are registered trademarks of Honeywell International Inc.

Other brand or product names are trademarks of their respective owners.

Honeywell Process Solutions

1860 W. Rose Garden Lane

Phoenix, AZ 85027 USA

1-800 822-7673

R200 RC500 RC-SCONTRL RTU User's Guide iii November 2011 Honeywell

About This Document This document describes how to configure RC500 SCONTRL Remote Terminal Unit (RTU).

This documentation is intended for the following audience:

System engineers who would configure the RC500 RTU modules, create associated applications, and operate the run-time RC500 RTU modules.

Field engineers who would install and maintain RC500 RTU modules.

Knowledge of Experion control system and exposure to Microsoft Windows environment is necessary for configuring the RTUs.

Release Information

Document Name Document ID Release Number

Publication Date

RC500 RC-SCONTRL RTU User's Guide RC-DCX211 200 November 2011

Support and Other Contacts

iv RC500 RC-SCONTRL RTU User's Guide R200 Honeywell November 2011


United States and Canada Contact:

Phone: Facsimile: Mail:

Honeywell Solution Support Center 1-800-822-7673 (outside Arizona) 602-313-5558 (in Arizona) Calls are answered by dispatcher between 6:00 am and 4:00 pm Mountain Standard Time. Emergency calls outside normal working hours are received by an answering service and returned within one hour. 602-313-3293 Honeywell TAC, MS P13 2500 West Union Hills Drive Phoenix, AZ, 85027

Europe Contact:

Phone: Facsimile: Mail:

Honeywell TAC-EMEA +32-2-728-2732 +32-2-728-2696 TAC-BE02 Hermes Plaza Hermeslaan, 1H B-1831 Diegem, Belgium

Pacific Contact:

Phone: Fascimile: Mail: Email:

Honeywell Global TAC Pacific 1300-300-4822 (toll free within Australia) +61-8-9362-9559 (outside Australia) +61-8-9362-9564 Honeywell Limited Australia 5 Kitchener Way Burswood 6100, Western Australia [email protected]

India Contact:


Honeywell Global TAC India +91-20- 6603-9400 +91-20- 6603-9800 Honeywell Automation India Ltd 56 and 57, Hadapsar Industrial Estate Hadapsar, Pune 411 013, India [email protected]


R200 RC500 RC-SCONTRL RTU User's Guide v November 2011 Honeywell

Korea Contact:


Honeywell Global TAC Korea +82-80-782-2255 (toll free within Korea) +82-2-792-9015 Honeywell Co., Ltd 4F, Sangam IT Tower B4-4 Block 1590, DMC Sangam-dong, Mapo-gu, Seoul, 121-835, Korea [email protected]

Peoples Republic of China Contact:

Phone: Mail: Email:

Honeywell Global TAC China +86- 21-5257-4568 Honeywell (China) Co., Ltd 33/F, Tower A, City Center, 100 Zunyi Rd. Shanghai 200051, Peoples Republic of China [email protected]

Singapore Contact:


Honeywell Global TAC South East Asia +65-6580-3500 +65-6580-3501 +65-6445-3033 Honeywell Private Limited Honeywell Building 17, Changi Business Park Central 1 Singapore 486073 [email protected]

Taiwan Contact:


Honeywell Global TAC Taiwan +886-7-536-2567 +886-7-536-2039 Honeywell Taiwan Ltd. 17F-1, No. 260, Jhongshan 2nd Road. Cianjhen District Kaohsiung, Taiwan, ROC [email protected]


vi RC500 RC-SCONTRL RTU User's Guide R200 Honeywell November 2011

Japan Contact:


Honeywell Global TAC Japan +81-3-6730-7160 +81-3-6730-7228 Honeywell Japan Inc. New Pier Takeshiba, South Tower Building, 20th Floor, 1-16-1 Kaigan, Minato-ku, Tokyo 105-0022, Japan [email protected]

Elsewhere

Call your nearest Honeywell office.

World Wide Web Honeywell Solution Support Online:

http://www.honeywell.com/ps

Training Classes Honeywell Automation College:

http://www.automationcollege.com

Symbol Definitions

R200 RC500 RC-SCONTRL RTU User's Guide vii November 2011 Honeywell

Symbol Definitions The following table lists those symbols used in this document to denote certain conditions.

Symbol Definition

ATTENTION: Identifies information that requires special consideration.

TIP: Identifies advice or hints for the user, often in terms of performing a task.

REFERENCE -EXTERNAL: Identifies an additional source of information outside of the bookset.

REFERENCE - INTERNAL: Identifies an additional source of information within the bookset.

CAUTION

Indicates a situation which, if not avoided, may result in equipment or work (data) on the system being damaged or lost, or may result in the inability to properly operate the process.

CAUTION: Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury. It may also be used to alert against unsafe practices.

CAUTION symbol on the equipment refers the user to the product manual for additional information. The symbol appears next to required information in the manual.

WARNING: Indicates a potentially hazardous situation, which, if not avoided, could result in serious injury or death.

WARNING symbol on the equipment refers the user to the product manual for additional information. The symbol appears next to required information in the manual.

WARNING, Risk of electrical shock: Potential shock hazard where HAZARDOUS LIVE voltages greater than 30 Vrms, 42.4 Vpeak, or 60 VDC may be accessible.

Symbol Definitions

viii RC500 RC-SCONTRL RTU User's Guide R200 Honeywell November 2011

Symbol Definition

ESD HAZARD: Danger of an electro-static discharge to which equipment may be sensitive. Observe precautions for handling electrostatic sensitive devices.

Protective Earth (PE) terminal: Provided for connection of the protective earth (green or green/yellow) supply system conductor.

Functional earth terminal: Used for non-safety purposes such as noise immunity improvement. NOTE: This connection shall be bonded to Protective Earth at the source of supply in accordance with national local electrical code requirements.

Earth Ground: Functional earth connection. NOTE: This connection shall be bonded to Protective Earth at the source of supply in accordance with national and local electrical code requirements.

Chassis Ground: Identifies a connection to the chassis or frame of the equipment shall be bonded to Protective Earth at the source of supply in accordance with national and local electrical code requirements.

R200 RC500 RC-SCONTRL RTU User's Guide ix November 2011 Honeywell

Contents

1. RC-SCONTRL RTU INTRODUCTION .......................................... 13 1.1 Overview ....................................................................................................... 13

2. RC-SCONTRL RTU CONFIGURATION ........................................ 15 2.1 Overview ....................................................................................................... 15

2.2 Adding an RC-SCONTRL RTU .................................................................... 17 2.3 Configuring RC-SCONTRL RTU communication ports ............................ 18

Configure Ethernet ports .......................................................................................... 18 Configure serial ports ............................................................................................... 22

2.4 Redundant RTUs .......................................................................................... 24 Overview .................................................................................................................. 24 Redundant RTU switch over conditions ................................................................... 24 Station Status Module variables ............................................................................... 25 Configure a redundant RTU ..................................................................................... 27 Create and load ISaGRAF program for redundancy ................................................ 32 Configure synchronization ........................................................................................ 34 Add an I/O module to a redundant RTU ................................................................... 36

2.5 Configuring peer-to-peer communication ................................................. 37 Configure I/O transfer ............................................................................................... 37 Configure conditional transfer ................................................................................... 41

2.6 Assigning I/O module to RTU ..................................................................... 45 Add virtual I/O modules ............................................................................................ 46 I/O tag names and restrictions .................................................................................. 48

2.7 Configuring I/O modules ............................................................................. 49

2.8 Configuring system information module ................................................... 52 2.9 Configuring RC500 RTU as DNP3 slave ..................................................... 53

DNP3 slave points mapping the RTU ....................................................................... 54 Configure DNP3 slave driver .................................................................................... 55 Map I/O types to DNP class ..................................................................................... 62

2.10 Configuring RTU as Modbus Master .......................................................... 70

2.11 Configuring RTU as Modbus Slave ............................................................ 71

2.12 Configuring datalogging .............................................................................. 73 Configure Host transfer ............................................................................................ 73

Contents

x RC500 RC-SCONTRL RTU User's Guide R200 Honeywell November 2011

Execute Host transfer .............................................................................................. 78 Configure Client transfer .......................................................................................... 78 Configure Datalog Server for specific stations ......................................................... 82 Configure Datalog Server for any station ................................................................. 83 Copy datalog configuration ...................................................................................... 85

2.13 Configuring alarms in RTU .......................................................................... 86 Add discrete alarms ................................................................................................. 86 Add analog alarms ................................................................................................... 87 Add periodic alarms ................................................................................................. 89 Add a recipient ......................................................................................................... 90

3. LOAD RC-SCONTRL RTU CONFIGURATION ............................ 91 3.1 Overview ........................................................................................................ 91

3.2 Startup operations ........................................................................................ 91 Start an RTU ............................................................................................................ 91 Establish communication between Honeywell RC500 I/O Tool Kit and RTU ........... 92

3.3 Load options ................................................................................................. 93

3.4 Loading basic configuration to RTU ........................................................... 93

3.5 Loading DNP3 protocol configuration to RTU ........................................... 95 Load DNP3 protocol configuration to secondary RTU ............................................. 95

3.6 Loading all configuration files ..................................................................... 96 3.7 Loading an ISaGRAF program to RTU........................................................ 97

4. COMMUNICATION BETWEEN EXPERION AND RTU................ 99 4.1 Establishing communication between Experion and RTU using DNP3 .. 99

Prerequisite ............................................................................................................. 99 Enable components in Quick Builder ..................................................................... 101 Add a DNP3 Protocol channel ............................................................................... 102 Add a DNP3 Protocol controller ............................................................................. 103 Configure Experion Points ..................................................................................... 104 Configure an Experion Analog Point ...................................................................... 104 Configure an Experion Status Point ....................................................................... 105

1. RC-SCONTRL RTU introduction 1.1. Overview

R200 RC500 RC-SCONTRL RTU User's Guide xi November 2011 Honeywell

4.2 Establishing communication between Experion and RTU using Modbus ...................................................................................................................... 106

Enable components in Quick Builder ...................................................................... 106 Add a Modbus Protocol channel ............................................................................. 108 Add a Modbus Protocol controller .......................................................................... 109 Configure Experion Points ...................................................................................... 109 Configure an Experion Analog Point ...................................................................... 109 Configure an Experion Status Point ....................................................................... 111

4.3 RC500 diagnostic display configuration .................................................. 112 Prerequisites ............................................................................................................. 112 RC500 diagnostic parameters mapping to Quick Builder points ............................. 113 Configure detail display for DNP3 controller ........................................................... 118 Configure detail display for Modbus ....................................................................... 120 Navigating detail display ......................................................................................... 122

5. RC-SCONTRL RTU OPERATIONS ............................................ 125 5.1 Overview ..................................................................................................... 125

5.2 Replacing/upgrading redundant RTUs .................................................... 125

5.3 Verifying the loaded configuration data .................................................. 126

5.4 Retrieving the configuration data ............................................................. 126

5.5 Monitoring RC-SCONTRL RTU ................................................................. 127 Monitor I/O modules ............................................................................................... 127 Change I/O values using Test I/O .......................................................................... 128 Monitor the communication between I/O modules and RTU .................................. 129 Monitor the heartbeat register ................................................................................ 129 Monitor redundancy ................................................................................................ 130

5.6 Monitoring the ring switch status ............................................................. 131 Monitor the ring switch status using RTUs ............................................................. 131 Monitor RTU Status ................................................................................................ 135

5.7 Resetting the RTU ...................................................................................... 136

5.8 Set the real-time clock for an RTU ............................................................ 136

6. MAINTENANCE AND TROUBLESHOOTING ............................ 137

Contents

xii RC500 RC-SCONTRL RTU User's Guide R200 Honeywell November 2011

6.1 Upgrading firmware .................................................................................... 137 Considerations ....................................................................................................... 137

6.2 Resetting System Com Port ...................................................................... 140

6.3 Formatting battery backed RAM ............................................................... 141 6.4 LED status ................................................................................................... 143

6.5 Diagnostics and troubleshooting .............................................................. 144

R200 RC500 RC-SCONTRL RTU User's Guide 13 November 2011 Honeywell

1. RC-SCONTRL RTU introduction

1.1 Overview RC-SCONTRL RTU is a modular and scalable controller capable of remote automation and control applications. The module, combined with Honeywells powerful and feature-rich SCADA products, provides an integrated solution that solves remote automation requirements.

You can install RC-SCONTRL RTU either in a non-redundant configuration or in a redundant configuration.

Figure 1: RC-SCONTRL RTU

1. RC-SCONTRL RTU introduction 1.1. Overview

14 RC500 RC-SCONTRL RTU User's Guide R200 Honeywell November 2011


2. RC-SCONTRL RTU configuration

2.1 Overview The Honeywell RC500 I/O Tool Kit is a Windows software, and it is used to configure and maintain RTUs and I/O modules. Before you begin with RTU configuration, ensure that the Honeywell RC500 I/O Tool Kit is already installed and registered.

REFERENCE - INTERNAL

Refer to the Honeywell RC500 SIUG for more information regarding Honeywell RC500 I/O Tool Kit installation and registration.

ATTENTION

In the Honeywell RC500 I/O Tool Kit, RTUs and I/O modules are known as station.

RC-SCONTRL RTU configuration involves the following tasks.

Basic RTU configuration

Creating an RC-SCONTRL RTU

Configuring Ethernet ports

Configuring serial ports

Configuring a redundant RC-SCONTRL RTU

Creating and loading ISaGRAF program for redundancy

Configuring synchronization

I/O configuration

Configuring I/O transfer

Configuring conditional transfer

Assigning I/O modules to RTUs

Adding virtual I/O modules

Configuring I/O modules

Configuring system information module

2. RC-SCONTRL RTU configuration 2.2. Adding an RC-SCONTRL RTU


Protocol configuration

Configuring DNP3 slave driver

Mapping I/O types to DNP points

Enabling components in Quick Builder

Adding a DNP3 Protocol channel

Adding a DNP3 Protocol controller

Configuring Modbus Protocol

Adding Modbus Protocol channel

Configuring an Experion Analog Point

Configuring an Experion Status Point

Configuring RTU as Modbus Master

Configuring RTU as Modbus slave

Datalog configuration

Configuring Host transfer

Configuring Client transfer

Configuring Datalog Server for specific stations

Configuring Datalog Server for any station

Copying datalog configuration

Alarm configuration

Adding discrete alarms

Adding analog alarms

Adding periodic alarms

Adding recipient

2. RC-SCONTRL RTU configuration 2.2. Adding an RC-SCONTRL RTU


2.2 Adding an RC-SCONTRL RTU To add an RTU, you must create a configuration project in the Honeywell RC500 I/O Tool Kit. The file extension of the project is .6pj. It stores the configuration details of the RTUs and the I/O modules.

Perform the following steps to create a new project and to add an RC-SCONTRL RTU in the Honeywell RC500 I/O Tool Kit.

Step Action

1 Choose Start > Programs > Honeywell Tools > Honeywell Tool Kit.

The Honeywell RC500 I/O Tool Kit appears.

2 Choose File > New Project.

The Wizard Selection dialog box appears.

3 Click Add a new station to the project option and click OK.

The Select New Station Type dialog box appears.

Note: If you want to add a station to an existing project, on the left-pane, in the Tree views right-click All Stations and choose New Station under By Type tab.

4 In the list, click RC500 RTU and click OK.

The Save As dialog box appears.

5 Enter a project name and click Save.

The RC500 RTU Station Configuration page appears.

6 Under Define General Properties, enter details in the Station Name box, the Station number box, and the Serial number box.

ATTENTION

Station name should not exceed 20 characters, and in special characters, only the underscore is allowed.

Value for the station number should be between 0 and 15999.

The serial number can be found at the base of the RTU.

7 In the Station Type list, click RC-SCONTRL.

8 Click Configure Later.

A new station is added.

2. RC-SCONTRL RTU configuration 2.3. Configuring RC-SCONTRL RTU communication ports


2.3 Configuring RC-SCONTRL RTU communication ports Configure Ethernet ports All RC-SCONTRL RTU models have two independent Ethernet ports. Each Ethernet port (Ethernet port 1 and Ethernet port 2) has its own MAC address.

The two Ethernet ports should be assigned IP addresses and subnet masks such that they operate on independent Ethernet networks. If the two Ethernet ports are configured to reside on the same Ethernet network, the RTUs operating system may disable one of the two Ethernet ports and might result in undesired behavior.



The following table provides information about the protocols supported by the RTU.

Protocol Recommended port number

Use

RC500 UDP 1594 Used for communication between

ISaGRAF and RTU

Honeywell RC500 I/O Tool Kit and RTU

The communication port used is 1594.

RC500 UDP / TCP

1594 Used for communication between

I/O module and RTU

Peer-to-peer RTU

Modbus UDP / TCP Master


RTU and I/O Modules

RTU and third-party Modbus slave devices

The RTU acts as the Modbus Master.

Modbus UDP / TCP Slave


RTU and SCADA

RTU and third-party Modbus Masters

The RTU acts as Modbus Slave.

DNP3 UDP / TCP 20000 Used for communication between RTU and SCADA.



Perform the following steps to configure Ethernet ports in the RTU.

Step Action

1 Right-click the station and choose Configure.

The RC500 RTU Station Configuration dialog box appears.

2 Click Ports tab.

3 Under Define Communication Port Properties, click Ethernet1, and then click Configure Selected Port.

The Ethernet Port Configuration dialog box appears.

4 Under IP address, click any one of the options provided.

Automatically assign IP address based on station number Select this option to automatically assign IP address based on station number. In this case, if the station number is changed, the IP address also changes automatically.

Use DHCP Select this option to allow DHCP server to assign the IP addresses to the stations.

Manually assign IP address Select this option to assign IP address manually.

5 Click Advanced.

The Advanced Ethernet/IP Security dialog box appears.

6 In the Subnet mask box, enter the subnet mask of the network.

7 In the TCP/IP timeout list, either click an existing value or enter a value in seconds and click OK.

8 In the TCP/IP gateways box, enter the IP address.



Step Action

ATTENTION

Subnet Mask

Assign an IP address for the subnet mask to associate the station to the required subnet.

TCP/IP Timeout

This setting determines the amount of time that a TCP/IP session can be inactive before it can be terminated by the station. An inactive TCP/IP session is terminated only if the stations maximum allowable number of TCP/IP sessions is in use and a new TCP/IP session request is received from another Ethernet device.

TCP/IP gateway

This feature allows the station to communicate with devices on other networks. If you specify TCP/IP gateway address, then the TCP/IP gateway routes messages to the other networks.

9 Click Ethernet2 and then click Configure Selected Port.


10 Perform the steps from step 4 to step 8.

11 In the Ethernet Port Configuration dialog box, click OK.

The Ethernet ports are configured.



Configure serial ports RC-SCONTRL RTU supports RS232 and RS485 serial ports. The following table provides information about various protocols supported by serial ports and their uses.

Protocol Use

RC500 Serial protocol Used for communication between

RC500 and I/O module

Peer-to-peer communication between RTUs

Modbus RTU Master protocol Used for communication between

RC500 and I/O Modules

RC500 and third-party Modbus slave devices

The RC500 acts as the Modbus Master.

Modbus ASCII Master protocol Used for communication between

RC500 and third-party Modbus slave devices

The RC500 acts as the Modbus Master.

Modbus RTU Slave protocol Used for communication between

RC500 and SCADA

RC500 and third-party Modbus Masters.

The RC500 acts as the Modbus Slave.

DNP3 Slave Used for communication between RTU and SCADA.

The RC500 acts as DNP3 Slave.

ATTENTION

RS232 A and RS232 B ports are not redundant.



Perform the following steps to configure serial ports in the RTU.

Step Action



2 Click the Ports tab.

3 Under Define Communication Port Properties, click a serial port and then click Configure Selected Port.

The Serial Port Configuration dialog box appears.

4 In Port protocol list, click the required communication protocol.

ATTENTION

RC500, Modbus RTU Master, Modbus ASCII Master, Modbus RTU Slave, Modbus ASCII Slave, and DNP3 Slave are the protocols that are supported currently.

5 Select appropriate values in the Baud rate, Parity, Data bits, and Stop bits list.

6 In the Flow control list, click the required flow control method.

ATTENTION

For RS485 port, the only value available is 2-Wire Parity Line.

7 In the Lead time box and in the Lag time box, enter appropriate values.

ATTENTION

The Lead time and Lag time boxes are enabled only if the Half Duplex Modem or the Full Duplex Modem is selected as flow control method.

8 In the Passthru to list, click the required COM port through which the data should be passed.

ATTENTION

The Passthru to list is enabled only for RC500 protocol.

2. RC-SCONTRL RTU configuration 2.4. Redundant RTUs


Step Action

9 If you want to connect a modem to the port, select Set modem check box, and enter the Modem Initialization string in the Set modem box.

Most RC500 RTUs can be configured to send an initialization string to a modem upon power-up. The string typically contains Hayes-compatible modem commands. A common use of this feature is to place the modem in auto-answer mode upon station power-up.

10 Click OK.

2.4 Redundant RTUs Overview A redundant (secondary) RTU is configured along with the primary RTU as a backup option.

Using Honeywell RC500 I/O Tool Kit, you can automatically create and maintain the configuration of a second RC-SCONTRL RTU to ensure that redundant RTUs, used as a pair, would always have the same configuration loaded into them. When a configuration change is made to one RTU, the same changes are reflected in the secondary RTU as well. By default, configuration loaded into the primary RTU is simultaneously loaded into the secondary RTU.

The operation of redundant RTUs require Ethernet connectivity between the two RTUs, and Ethernet connectivity between the RTUs and the computer in which running Honeywell RC500 I/O Tool Kit.

Redundant RTU switch over conditions In redundant RTUs, there are two RTUsA primary RTU and a secondary RTU. When the primary RTU fails, the secondary RTU takes over the place of the primary RTU and continues the operation.

Typically, the switch-over between RTUs take place under the following conditions.

Software failure or program maintenance in RTU

RTU hardware failure

Power supply failure

Ethernet connection failure



The RTUs use built-in redundancy features to identify the failure and to switch-over between the RTUs.

The conditions in which the redundancy are supported or not supported are provided in the following list.

Supported:

Serial port redundancy is supported. Redundant RTUs communicates to third-party serial devices through Modbus. Here, the RTU acts as Modbus master. If there is RTU to third-party communication over serial, and if switch over happens, then the redundancy is achieved.

RTU-SCADA redundancy over TCP/IP for single LAN (Ethernet) is supported. RTU redundancy to SCADA is achieved through Modbus and DNP3 slave over TCP/IP. Here, RC500 acts as slave.

I/O Module communication redundancy is achieved through ring configuration using the ring switches.

Not Supported:

RTU-SCADA redundancy over serial is not supported. RTU redundancy to SCADA is not achieved through Modbus and DNP3 over serial, and over terminal server configurations. If the RTU communicates to SCADA over serial, and if there is a switch over, then the redundancy is not achieved.

I/O Module redundancy is not supported.

Station Status Module variables Each RTU has a set of key variables called Station Status Module variables. These variables are monitored by the redundancy code to ensure that the RTUs determine which RTU is in control and whether the logic code is running. There are two types of variablesSelf and Other. The RTU uses the Self as its own variables and the Other as the other RTUs variables. The built-in redundancy configuration automatically sets a write transfer of the Self-bits to the other stations Other-bits.



The following table provides more information about the Station Status Module variables.

Variable Description

Self_Heartbeat This bit is the Discrete Output variable that is toggled continuously by the ISaGRAF program. This variable is used by the built-in redundancy code to determine whether the station should be in Active mode or Back-up mode.

Self_Active This bit is the status-bit generated by the built-in redundancy feature. When the bit is ON, the RTU is in Active mode. The built-in redundancy sets this bit when all the active criteria are met.

Self_Backup This bit is the status-bit generated by the built-in redundancy feature. When this bit is ON, the station is in Back-up mode.

Other_Heartbeat This bit is the toggling heartbeat Discrete Output of the other station, which is generated by the ISaGRAF program of the other station.

Other_Active This bit is the Self_Active bit from the other station. This is used by the built-in redundancy feature to determine whether the RTU should be in Active mode or in Back-up mode.

Other_Status This bit is the Self_Back-up bit of the other station. It is used by the built-in redundancy feature to determine whether the station should be in Active mode or in Back-up mode.

Self_Status This bit is used to determine whether the station is in Active mode or Back-up mode.

The ON message indicates Active mode and the OFF message indicates Back-up mode.



Configure a redundant RTU When you need high-availability system, redundant RTUs can be configured.

Perform the following steps to configure the RTU with redundancy option.

Step Action

1 Choose Start > Programs > Honeywell Tools > Honeywell Tool Kit.


2 Choose File > New Project.

The Wizard Selection dialog box appears.

3 Click Add a new station to the project option and click OK.

The Select New Station Type dialog box appears.

ATTENTION

If you want to add a station to an existing project, right-click All Stations and choose New Station under By Type tab in the tree views.

4 In the list, click RC500 RTU and click OK.

The Save As dialog box appears.

5 Enter a project name and click Save.

The RC500 RTU Station Configuration page appears.

6 Under Define General Properties, enter details in the Station Name box, the Station number box, and the Serial number box.

7 In the Station Type list, select RC-SCONTRL.

8 Select Automatically configure a secondary controller check box.

The secondary station name is displayed.

9 Select Enable built-in redundancy check box.



Step Action

ATTENTION

If you want to enable the secondary RTU to an existing station, perform the following steps.

1. Right-click the station and choose Configure. The RC500 RTU Station Configuration dialog box appears.

2. In the General tab, select the Automatically configure a secondary controller check box and the Enable built-in redundancy check box.

10 Click Next.

The Ports page appears.

11 Perform the following steps to configure Ethernet ports.

a) Under Define Communication Port Properties, click Ethernet1 and then click Configure Selected Port.


b) Under IP address, click any one of the options given.

Automatically assign IP address based on station number Select this option to automatically assign IP address based on station number. In this case, if the station number is changed, the IP address also changes automatically.

Use DHCP Select this option to allow DHCP server to assign the IP addresses to the stations.

Manually assign IP address Select this option to assign IP address manually.

c) Click OK.

d) Click Ethernet2 and then click Configure Selected Port.


e) Under IP address, click any one of the options given.

f) Click Advanced.

The Advanced Ethernet/IP Security dialog box appears.

g) In the Advanced Ethernet tab, in Port list, click Ethernet2 and click OK.



Step Action

h) In the Ethernet Port Configuration dialog box, click OK.

ATTENTION

Subnet Mask

Assign an IP subnet mask for the RTU, if the RTU communicates through a TCP/IP gateway device (typically the computer) to a device on another network.

TCP/IP Timeout

This setting determines the period of time that a TCP/IP session can be inactive before it can be terminated by the station. An inactive TCP/IP session is terminated only if the stations maximum allowable number of TCP/IP sessions is in use and a new TCP/IP session request has been received from another Ethernet device.

12 Click Next.

The I/O Modules page appears.

13 Click Next.

The Advanced page appears.

14 Click Next.

The I/O Transfers page appears.

15 Click Next.

The Redundant Controller Options page appears.

16 In the Serial number box, enter the serial number of the secondary RTU.

17 Under Station number options,

If you want to use the same station number for the secondary RTU and the primary RTU, click Use the primary controller station number.

Or

If you want to use different station numbers for secondary RTU station and primary RTU station, click Use a unique station number and enter a station number in the box.



Step Action

ATTENTION

If the communication between SCADA and RTU is through Modbus, then use the same station number for the primary RTU and the secondary RTU.

If the communication between SCADA and RTU is through DNP3, then you can either use same station number for both primary RTU and the secondary RTU or you can use unique station number for both RTUs.

18 In the IP Address box and in the 2nd IP Address box, enter the IP addresses for the secondary RTU.

ATTENTION

Ensure that both the IP addresses are in different subnet mask.

19 Under Built-in redundancy options, click the General tab.

20 Select Enable built-in redundancy and select Enable common IP.

The Common IP box and the Subnet mask box are available for editing.

ATTENTION

The Enable common IP option is enabled only if the Enable built-in redundancy check box is selected.

21 Enter an IP address in the Common IP box.

ATTENTION

Common IP address should be a unique IP address in LAN2. The Experion server uses this IP address to communicate with the RTU. The common IP address is bound to the RTU that is currently acting as primary.

For example, if the IP Address under Secondary controller options is 10.1.0.7, then the Common IP should be 10.1.0.x, where x is a unique number in the network.

22 Click Heartbeat tab and enter time in seconds in Allowable loss period box. The default value is 5 seconds.



Step Action

ATTENTION

If the primary RTU fails, then the secondary RTU waits for the allowable loss period and changes the status to primary.

The default synchronization period is 50 mS. You can change the synchronization period by performing the following steps.

a) Click I/O Transfers tab.

b) Click _StaStatWire_ transfer and click Edit Selected Transfer. The I/O Transfer Configuration page appears.

c) Click Action Definition tab.

d) Under Scan time/ trigger,

In the Scan option list, click Use the Specified Interval Time.

In the Scan interval time list, click the period of your choice. This interval is the synchronization period.

e) To add an alert about the synchronization failure, in the Scan enable flag list, click Self_Active.

23 Click Virtual I/O Synch.

24 Enter the number of registers required in Num Regs and the starting register number in Start Addr for different I/O types.

These are used to create the range for all output types and to synchronize outputs between the two RTUs.

ATTENTION

Do not change the Redundancy bits (Digital Output) starting address. The default starting address is zero.

Do not synchronize the first seven Digital Output registers as they are used by the RTUs for redundancy operations.



Step Action

25 Click Finish.

ATTENTION

To enable redundancy, you have to create an ISaGRAF program and load it in the RTU. To know more about creating and loading ISaGRAF program, refer to Creating and loading ISaGRAF program for redundancy.

ATTENTION

Add Dual LAN supports for non-redundant RTU.

Create and load ISaGRAF program for redundancy Perform the following steps to create and load the ISaGRAF program to RTU.

Step Action

1 Open the ISaGRAF tool.

2 Create a new ISaGRAF project.

3 Add a new program and add a functional block diagram to the program.

4 In the Honeywell RC500 I/O Tool Kit, choose File > Export > I/O Definitions to > ISaGRAF.

The ISaGRAF Export dialog box appears.

5 In the ISaGRAF version list, click the ISaGRAF version that is used and click Next.

The ISaGRAF version Export dialog box appears.

6 In the ISaGRAF project box, browse to the ISaGRAF project folder and select the project.

7 Click Next.

The ISaGRAF Export Tag Selection dialog appears.

8 Under Tags to export, click Tags from one station only and click the particular station in the list.

9 Click Next.



Step Action

The ISaGRAF Export Summary dialog appears.

10 Click Finish.

The ISaGRAF Export Progress dialog box appears.

11 Once the tags are exported, click Close.

12 Open the ISaGRAF tool and open the functional block diagram.

13 Create a functional block diagram for redundancy similar to the diagram shown below.

14 In the Honeywell RC500 I/O Tool Kit, load the ISaGRAF program to the RTU.

REFERENCE INTERNAL

For more information about loading an ISaGRAF program to the RTU, refer to Loading an ISaGRAF program to RTU.



Configure synchronization While adding secondary RTU, it is essential to synchronize the output of the primary RTU with the secondary RTU.

ATTENTION

Heart beat messages are exchanged through Ethernet1 port.

Ethernet1 port of Primary RTU and Secondary RTU should be connected through a switch and should not be connected directly. If connected directly and if the cable between both the Ethernet1 ports fails, then both the RTUs go to backup state, which results in a single point failure.

Perform the following steps to synchronize outputs between the primary RTU and the secondary RTU.

Step Action

1 Right-click the station (primary RTU) and choose Configure.


2 Click I/O Modules tab and click Add Virtual I/O.

The Auto-Create Virtual Modules dialog box appears.

3 In Discrete Output row, click the cell under Starting Register Number and enter the value from which the register number must start.

4 Click the respective cell under Number of Registers and enter the number of registers required.

The maximum value allowed is 1024.

5 In Analog Output row, click the cell under Starting Register Number and enter the value from which the register number must start.

6 Click the respective cell under Number of Registers and enter the number of registers required. Click OK.

Maximum value allowed is 1024.

ATTENTION

Only outputs can be synchronized.

7 Click Redundant Controller Options tab.

8 Under Built-in redundancy options, click Virtual I/O Synch tab.



Step Action

9 In Discrete Output row, click the cell under Start Addr and enter the value from which the register number must start.

ATTENTION

Ensure to enter the same value entered for Starting Register Number in Auto-Create Virtual Modules dialog box.

10 In Discrete Output row, click the cell under Num Regs and enter the number of registers required.

ATTENTION

Ensure to enter the same value entered for Number of Registers in Auto-Create Virtual Modules dialog box.

11 In Analog Output row, click the cell under Start Addr and enter the value from which the register number must start.

ATTENTION

Ensure to enter the same value entered for Starting Register Number in Auto-Create Virtual Modules dialog box.

12 In Analog Output row, click the cell under Num Regs and enter the number of registers required.

ATTENTION

Ensure to enter the same value entered for Number of Registers in Auto-Create Virtual Modules dialog box.

13 Click OK.



Add an I/O module to a redundant RTU Perform the following steps to add an I/O module to a redundant RTU.

Step Action

1 Right-click the station (primary RTU) and choose Configure.


2 Click Redundant Controller Options tab.

3 Under Built-in redundancy options, click I/O Transfers tab.

4 Click Add Remote I/O.

The Add Redundant Remote I/O Module dialog box appears.

5 In the Select a module type list, click the type of the I/O module that is added.

6 In the Module name box, enter a name for the I/O module.

7 In the Station number box, enter a station number for the I/O module.

8 In the IP Address box, enter the IP address of the I/O module.

9 Select Create a Remote I/O Link module and I/O Transfers check box.

10 Click OK.

2. RC-SCONTRL RTU configuration 2.5. Configuring peer-to-peer communication


2.5 Configuring peer-to-peer communication An I/O transfer is used to copy input or output values from one device to another. The RTU that is performing the transfer is called as the Local Station. I/O data can be transferred to/from an external device (I/O module or RTU) or within the local station itself. These transfers can be normal transfers or conditional transfers. A transfer made within the local station itself is referred to as Internal Block Move.

Configure I/O transfer Perform the following steps to configure I/O transfer.

Step Action



2 Click the I/O Transfers tab.

3 Click Wizard Add New Transfer.

The Select Remote Station page appears.

4 If the remote station is part of the project file, then

a) Clear the Specify by station number check box.

b) In the Remote station name list, click the station to which you want transfer I/O.

c) Click Next. The Select Transfer Name page appears.

Or

If the remote station is not part of the project file or if it is a product of a different manufacturer (For example serial device, PLC, and so on), then

a) Select the Specify by station number check box.

b) Enter the remote station number in the Remote station number box.


5 In the Name box, enter a name for the transfer.

The name should not exceed 40 characters.



Step Action

6 Click Next.

The Select Transfer Type page appears.

7 In the Transfer type list, click the type of I/O transfer.

Select Read RC500 I/O to have this station read I/O in a Block I/O Move or from a remote station configured for RC500 protocol.

Select Write RC500 I/O to have this station write I/O in a Block I/O Move or to a remote station configured for RC500 protocol.

Select Read Modbus I/O to have this station read I/O from a remote Modbus device or a module configured for Modbus protocol.

Select Write Modbus I/O to have this station write I/O to a remote Modbus device or a module configured for Modbus protocol.

ATTENTION

Using I/O transfers, you can either read data from the remote station or write data to the remote station.

8 Click Next.

The Select Port page appears.

9 In the Communications port list, click the port that is used for communication.

ATTENTION

Peer-to-peer communication is possible through the serial ports and the Ethernet ports.

10 Check the Current port settings.

Serial ports

a) Click Advanced.

b) In the Data format list, click either Binary or Hex, depending on the type of data transfer. Select Binary if 8-bit data format is required and select ASCII (Hex) if 7-bit data format is required.

c) In the Messaging sequence list, click either Rapid Fire or Wait for Reply. Normally, whenever there is heavy network traffic, 'Wait for Reply' is used. Whenever there is high network bandwidth, 'Rapid fire' is used.



Step Action

d) In the Message timeout box, enter the time in milliseconds. The default communication timeout is three seconds. This is displayed as a "3000" in the Message timeout box. Enter a longer timeout to compensate for transmission delays or data errors. Enter a shorter timeout to communicate over direct wiring and to perform quicker retries if there is any communication error.

e) In the Message attempts, enter the number of times the station would send messages to remote station or I/O module before moving to the next station or I/O module. Whenever the network traffic is high, the number of message attempts is also high. Whenever the traffic is low, then the number of message attempts is also low.

f) Select Most significant word (MSW) first check box. Select this parameter only if the station communicates with a third-party Modbus slave device that swaps the word order when reading or writing 32-bit long integer values. By default, RC500 products that support Modbus communication do not swap the word order. If this parameter is selected, the master station reverses the order of the two analog registers in each 32-bit long integer value when sending or replying to third-party Modbus commands for long integer I/O. This parameter has no effect on floating point values or when using Daniel Extensions to read or write long integer values.

ATTENTION

If there is any mismatch between the Serial port type selected in the Current port settings, and the protocol type selected in the Ports tab, then a protocol error message appears.

If the error occurs, click Yes and update the port settings in Select Transfer Type page to match the protocol.

Ethernet ports

If the Destination IP address is same as the remote stations IP address, then

a) Click Advanced.

b) In the Messaging sequence list, click either Rapid Fire or Wait for Reply.

c) In the Message timeout box, enter the time in milliseconds.

d) In the Message attempts, enter the number of times the station would send messages to remote station or I/O module before moving to the next station or I/O module.



Step Action

e) Click Next. The Scan Options page appears.

Or

If the Destination Address is different from the remote stations IP address, then

a) Select Use this destination IP address check box. The Use this destination IP address box is enabled for editing.

b) Enter the remote stations IP address.

c) Click Advanced.

d) In the Messaging sequence list, click either Rapid Fire or Wait for Reply.

e) In the Message timeout box, enter the time in milliseconds.

f) In the Message attempts, enter the number of times the station would send messages to remote station or I/O module before moving to the next station or I/O module.

g) Click Next. The Scan Options page appears

11 In the Update interval box, enter the I/O transfer interval of your choice and click Next.

The I/O Options page appears.

12 a) In the I/O type list, click the type of the I/O to be transferred.

b) In the Register count box, enter the number of registers to be used.

c) Enter the details required in Local registers and Read from remote registers.

ATTENTION

Local registers - Virtual I/O module address of RTU that requests data.

Remote from remote registers - Virtual I/O module address of RTU that provides data.



Step Action

13 Click Next.

The Complete! page appears.

14 Click Finish.

The summary of the I/O transfer appears and if you click any of the parameter, the corresponding configuration page of the I/O transfer appears.

Configure conditional transfer While transferring data between RTUs, a certain condition can be set, depending on which the I/O transfers would take place. Generally, this condition would be the status of any particular discrete I/O tag or virtual I/O tag. Depending upon the status of the I/O tag, the I/O transfer is initiated.

Perform the following steps to configure conditional transfer.

Step Action



2 Add a Virtual I/O module.

For more information about how to add a virtual I/O module, refer to Adding Virtual I/O modules section.

3 Click the I/O Transfers tab.

4 Click Wizard Add New Transfer.

The Select Remote Station page appears.

5 If the remote station is part of the project file, then

a) Clear the Specify by station number check box.

b) In the Remote station name list, click the station to which you want transfer I/O.


Or



Step Action

If the remote station is not part of the project file or if it is a product of a different manufacturer, then

a) Select the Specify by station number check box.

b) In the Remote station number box, enter the remote station number.


6 In the Name box, enter a name for the transfer.

The name should not exceed 40 characters.

7 Click Next.

The Select Transfer Type page appears.

8 In the Transfer type list, click the type of I/O transfer.

Select Read RC500 I/O to have this station read I/O in a Block I/O Move or from a remote station configured for RC500 protocol.

Select Write RC500 I/O to have this station write I/O in a Block I/O Move or to a remote station configured for RC500 protocol.

Select Read Modbus I/O to have this station read I/O from a remote Modbus device or a module configured for Modbus protocol.

Select Write Modbus I/O to have this station write I/O to a remote Modbus device or a module configured for Modbus protocol.

ATTENTION

Using I/O transfers, you can either read data from the remote station or write data to the remote station.

9 Click Next.

The Select Port page appears.

10 In the Communications port list, click the port that is used for communication.

ATTENTION

Peer-to-peer communication is possible through the serial ports and the Ethernet ports.

11 Check the Current port settings.



Step Action

Serial ports

a) Click Advanced.

b) In the Data format list, click either Binary or Hex, depending on the type of data transfer.

c) In the Messaging sequence list, click either Rapid Fire or Wait for Reply. Normally, whenever there is heavy network traffic, 'Wait for reply' is used. Whenever there is high network bandwidth, 'Rapid fire' is used.

d) In the Message timeout box, enter the time in milliseconds. The default communication timeout is three seconds. This is displayed as a "3000" in the Message timeout box. Enter a longer timeout to compensate for transmission delays or data errors. Enter a shorter timeout to communicate over direct wiring and to perform quicker retries if there is any communication error.

e) In the Message attempts, enter the number of times the station would send messages to remote station or I/O module before moving to the next station or I/O module. Whenever the network traffic is high, the number of message attempts is also high. Whenever the traffic is low, then the number of message attempts is also low.

f) Select the Most significant word (MSW) first check box. Select this parameter only if the station communicates with a third-party Modbus slave device that swaps the word order when reading or writing 32-bit long integer values. By default, RC500 products that support Modbus communication do not swap the word order. If this parameter is selected, the master station reverses the order of the two analog registers in each 32-bit long integer value when sending or replying to third-party Modbus commands for long integer I/O. This parameter has no effect on floating point values or when using Daniel Extensions to read or write long integer values.

g) Click Next. The Scan Options page appears.

ATTENTION

If there is any mismatch between the Serial port type selected in the Current port settings, and the protocol type selected in the Ports tab, then a protocol error message appears. If the error occurs, click Yes and update the port settings in Select Transfer Type page to match the protocol.



Step Action

Ethernet ports

If the Destination IP address is same as the remote stations IP address, then

a) Click Advanced.

b) In the Messaging sequence list, click either Rapid Fire or Wait for Reply.

c) In the Message timeout box, enter the time in milliseconds.

d) In the Message attempts, enter the number of times the station would send messages to remote station or I/O module before moving to the next station or I/O module.

e) Click Next. The Scan Options page appears.

Or

If the Destination Address is different from the remote stations IP address, then

a) Select Use this destination IP address check box. The Use this destination IP address box is enabled for editing.

b) Enter the remote stations IP address.

c) Click Advanced.

d) In the Messaging sequence list, click either Rapid Fire or Wait for Reply.

e) In the Message timeout box, enter the time in milliseconds.

f) In the Message attempts, enter the number of times the station would send messages to remote station or I/O module before moving to the next station or I/O module.

g) Click Next. The Scan Options page appears.

12 In the Update interval list, click the I/O transfer interval of your choice.

13 Click Advanced.

In Scan Enable Flag list, click the discrete tag name that would act as a conditional signal for I/O transfer.

Or

2. RC-SCONTRL RTU configuration 2.6. Assigning I/O module to RTU


Step Action

Select the Use a Trigger Name box and enter the trigger name that is assigned for this I/O transfer.

14 Click Next.

The I/O options page appears.

15 In the I/O type list, click the type of the I/O to be transferred.

16 In the Register count box, enter the number of registers to be used.

17 Enter the details required in Local registers and Read from remote registers.

18 Click Next.

The Complete! Page appears.

19 Click Finish.

2.6 Assigning I/O module to RTU Once I/O modules are physically connected to the RTU, they have to be added and configured in the Honeywell RC500 I/O Tool Kit as well.

Perform the following steps to assign an I/O module to the station.

Step Action

1 Choose Configure > New I/O Module.

The Module Configuration dialog box appears.

2 In the Module type list, click Remote I/O Link.

3 In the Part number list, select an I/O module.

4 In the Module tag name box, enter a name for the module and click OK.

The General page appears.

5 Click Configure Later.

The I/O module is assigned to the RTU.



Add virtual I/O modules Virtual I/O modules are imaginary modules that can be added to the Honeywell RC500 I/O Tool Kit configuration. The registers in a virtual I/O module are separate from the registers associated with the physical I/O modules that are connected to the RTU.

By default, a RTU has many I/O registers of each type. The lowest numbered registers are assigned to the physical I/O connected to the RTU. The remaining registers can be read / written by Windows programs (Test I/O functionality of the Honeywell RC500 I/O Tool Kit) and by application programs running in the RTU itself.

Virtual I/O modules are commonly used for the following purposes.

To pass set points and other data to an ISaGRAF program running in the RTU.

To hold I/O data transferred from another station through an I/O transfer, by a Modbus I/O transfer (or) RC500 I/O Transfer.

To monitor I/O module and/or remote station status from within Windows applications.

You can configure up to 1024 registers in each type of virtual I/O module. The following are the types of virtual I/O modules that can be added to the RTU.

Discrete Inputs

Discrete Outputs

Analog Inputs

Analog Outputs

Floating Point Inputs

Floating Point Outputs

Long Integer Inputs

Long Integer Outputs



Perform the following steps to add a virtual I/O module.

Step Action



2 Click I/O Modules tab and Click Add Virtual I/O.

The Auto-Create Virtual Modules dialog box appears.

3 Select Auto-create I/O tag names check box.

ATTENTION

The types of Input/Output available are provided in a tabular format. By default, the value of the starting register number and the number of registers is set to None. You can change these values as per requirement.

4 For a particular I/O type, click the respective cell under Starting Register Number.

5 Enter the value from which the particular I/O type register number must start.



Step Action

6 For a particular I/O type, click the respective cell under Number of Registers and enter the number of registers required.

Maximum value allowed is 1024.

7 Click OK.

I/O tag names and restrictions I/O registers names can be automatically created or customized as per the requirement.

Perform the following steps to customize I/O tag names.

Step Action

1 Choose Operations > Advanced Operations > Tag Restrictions.

The I/O Tag Name Restrictions dialog box appears.

2 Under Restriction Types, click Custom Restrictions.

The choices under Restrictions are enabled.

ATTENTION

To follow IEC 1131-3 tag name standard, under Restriction Types, click IEC 1131-3 Tags.

3 Select the options given under Restrictions as per requirement.

Once you select the options, if any tag name does not follow the restriction, then in the Honeywell RC500 I/O Tool Kit the particular tag name is highlighted in yellow color.

The following list provides the options that are available for selection.

Spaces Not Allowed in Tag Names

Begin with an Alpha Character

Upper/Lower Case are Equivalent

Limit Tag Names to ____ Characters

Limit Prefix Names to ____ Characters

Limit Prefix+Tag Names to ____ Characters

2. RC-SCONTRL RTU configuration 2.7. Configuring I/O modules


Step Action

4 Click Options.

The Error Checking Options dialog box appears.

5 Select the options given as per requirement.

These options are used to check the duplicate tag names, IP addresses, station numbers, and so on. Once you select the options, and if any duplicate item is found, then the Status field displays ERROR message.

6 Click OK and again click OK.

2.7 Configuring I/O modules Perform the following steps to configure the I/O modules that are added to the station.

Step Action



2 Click I/O Modules tab.

3 Click the I/O module to be configured and click Configure Module. The Module Configuration dialog box appears.

4 Click Remote I/O Links Options tab.

5 Under Communication port, click a port in the Port list.

Note: The current port settings vary depending on the port that is selected.

a) In the Data format list, click Binary or Hex, depending on the type of data transfer.

b) In the Messaging sequence list, click either Rapid Fire or Wait for Reply. Normally, whenever there is heavy network traffic, 'Wait for reply' is used and whenever high network bandwidth is used, 'Rapid fire' is used.

c) In the Message timeout box, enter the time in milliseconds. The default communication timeout is three seconds. This is displayed as a "3000" in the Message timeout box. Enter a longer timeout to compensate for transmission delays or data errors. Enter a shorter timeout to communicate over direct wiring and to perform quicker retries if there is any communication error.

2. RC-SCONTRL RTU configuration 2.7. Configuring I/O modules


Step Action

d) In the Message attempts, enter the number of times the station would send messages to remote station or I/O module before moving to the next station or I/O module. Whenever the traffic is high, then the number of message attempts is also high. Whenever the traffic is low, then the number of message attempts is also low.

6 Under Scan time/trigger, perform the following tasks.

In the Scan option list,

a) Click Use a Trigger Name, and enter the name of the trigger in the Trigger name box.

b) Click Use a Default Scan Time and enter the time interval for scan in the Default time (for all actions) box.

c) Click Use the Specified Interval Time and enter the time interval for scan in Scan interval time box.

ATTENTION

To configure an I/O module for a redundant RTU, perform the following:

1. Under I/O scan options, select Use built-in redundancy options check box.

2. In the Read output enable list, click Self_Backup and select Read DO and Read AO check boxes. Selecting the Read DO and Read AO check boxes ensures that the outputs are read by the redundant RTU.

3. In the Write output enable list, click Self_Active and select Write DO and Write AO check boxes. Selecting the Write DO and Write AO check boxes ensures that the outputs are set by the primary RTU. Both the RTUs read the input parameters.

7 Click Discrete Options tab.

8 Under Discrete input options, enter a value in First DI register box.

ATTENTION

The I/O address of the Discrete input starts from the value entered in the First DI register box. For example, if you enter 2 in the First DI register box, the discrete input I/O address starts from X2.

2. RC-SCONTRL RTU configuration 2.8. Configuring system information module


Step Action

9 Select Retain values on power loss check box.

The RTU retains the current values of the module if power is lost or cycled.

10 Click Discrete Tags tab.

11 Perform the following steps in the Discrete Tags page.

a) In the I/O Tag Name column, enter the name for the particular I/O register.

b) In the OFF Message column, enter the message to be displayed if the specific register is in OFF state.

c) In the ON Message column, enter the message to be displayed if the specific register is in ON state.

12 Click Analog Options tab.

13 Under Analog input options, enter a value in First AI register box.

ATTENTION

The I/O address of the Analog input starts from the value entered in the First AI register box. For example, if you enter 2 in the First AI register box, the Analog Input I/O Address starts from AX2.

14 Select Retain values on power loss check box.

The RTU retains the current values of the module if power is lost or cycled.

15 Click Analog Tags tab.

16 In the I/O Tag Name column, enter the name for the particular I/O register.

17 Click OK.

ATTENTION

To know about the I/O module that a particular station is configured to, click Address Map in the I/O Modules tab and check the details in the Station I/O Address Map dialog box.

2. RC-SCONTRL RTU configuration 2.8. Configuring system information module


2.8 Configuring system information module Perform the following steps to configure the system information module.

Step Action



2 Click I/O Modules tab.

3 Click Add New Module. The Module Configuration dialog box appears.

4 In the Module type list, click Diagnostic/Monitoring.

or

In the Module type list, click Virtual Module.

5 In the Part number list, click System Information if you have selected Module type as Virtual Module.

6 In the Module tag name box, enter a name for the module.

7 In the Refresh Cycle box, enter the interval (number of seconds) at which the system information module refresh its dynamic parameters.

8 Select Enable station reset feature and in the Reset Magic box enter the reset magic number.

The reset magic number is used in the Experion detail display to restart the RTU.

9 Click OK.

The General page appears.

10 Click Next.

The I/O Options page appears.

11 In the First Register box, enter the first register values to be used for I/O options.

12 In the Number of Registers box, enter the number of registers to be used for I/O options.

2. RC-SCONTRL RTU configuration 2.9. Configuring RC500 RTU as DNP3 slave


Step Action

ATTENTION

In the Long Integer Inputs (LX) box, enter number of registers as 18 for DNP3 run-time parameter.

13 Click Next.

The I/O Tags page appears.

14 Click Finish.

ATTENTION

To get the system information parameters value from an RTU you must map these points as DNP3 points, by configuring DNP3 slave driver. For more information about configuring DNP3 slave driver, refer to the section Configuring RC500 RTU as DNP3 slave.

While configuring DNP3 slave driver, do not map the system information parameters to any DNP3 classes.

2.9 Configuring RC500 RTU as DNP3 slave RC500 RTU is a DNP3 slave. DNP3 slave driver in RC500 is fully complaint to Level 2 of DNP3.0 standard and implements some of the Level 3 functions. Experion can read/write data from / to RC500 RTUs through DNP3 protocol. Experion is the DNP3 master.

ATTENTION

For redundant RTU Configuration, DNP3 Configuration must be performed in both the stations.

Repeat the exact DNP3 configuration of the primary RTU to the secondary RTU as it involves manual configuration.



DNP3 slave points mapping the RTU The following table provides the DNP3 slave points mapping the RTU.

I/O Type

Address Range in Toolkit Address Range in DNP slave

Starting Address

Number of Registers

DNP Start Address

Number of Registers

Discrete Inputs 0 8192 0 8192

Discrete Outputs 0 8192 0 8192

Analog Inputs 0 8192 0 8192

Analog Outputs 0 8192 0 8192

Floating Point Inputs 0 1024 8192 1024

Floating Point Outputs

0 1024 8192 1024

Long Integer Inputs 0 512 This maps to Binary Counter address 0 in DNP3 slave.

512

Long Integer Inputs 512 512 9216 512

Long Integer Outputs 0 1024 9216 1024



Configure DNP3 slave driver Perform the following steps to configure DNP3 Slave driver in Honeywell RC500 I/O Tool Kit.

Step Action

1 Choose Start > All Programs > Honeywell Tools > Honeywell Tool Kit.


2 Click .

The DNP3 Slave Driver Configuration dialog box appears.

3 Under Stations, the list of configured station is displayed. Select the station to be configured for DNP3.

4 Click Configure Selected Station.

The Station dialog box appears.

Defining general properties

5 In General tab, under Compatibility Mode, click Level 2+ option button.

It supports binary, analog, and binary-counter DNP3 points.

ATTENTION

If you click Level 2 option button, it does not support frozen analog input, frozen analog event, and frozen counter change.

6 If you select Enable Unsolicited Responses, then the RTU sends event data to SCADA without any request from SCADA. You need to configure the following details.

DNP Address to Send Unsolicited Message to Enter the address of the station to which DNP3 slave will send unsolicited messages.

Event Report Queue Timeout Enter the time in milliseconds for any events allowed to remain in the event queue before being reported. Minimum value: 1,000 ms (1 second) and maximum value: 3,600,000 ms (1 hour).

Event Report Queue Threshold Enter the minimum number of events in the event queue required to trigger the generation of an unsolicited event report message.



Step Action

Max. number of events to send in an unsolicited response Enter the maximum number of events to send in every unsolicited message.

Unsolicited Timeout Enter the time in milliseconds the DNP3 driver waits for confirmation for the sent unsolicited application fragment. Minimum value: 0 ms and maximum value: 3,600,000 ms.

Unsolicited Retry count Enter the number of times the DNP3 driver attempts to send the unsolicited application fragment upon not receiving confirmation. The value can be 0 to 255.

7 If you select Enable Initial Unsolicited Responses, then the DNP3 driver sends an initial unsolicited message upon startup.

Event detection rate Enter time in milliseconds for which the DNP3 driver detect for events.

Max events in queue after disconnect (TCP server only) Enter time in seconds for which the events are retained for a master even after disconnected. Once server reconnects within that time all the events will be reported to that master.

8 Select Enable Real Time Data Traces to log all the DNP3 traces in the specified path mentioned in Device box.

9 Select Time Synchronization to request time synchronization from the DNP3 master. Requests can be made at intervals of once per minute, once per hour, once per day, or never.

10 Under On new event when Event Queue is full,

Click Discard Newest Event - in case the DNP3 event buffer is full, then any new event is discarded. or

Click Discard Oldest Event - in case the DNP3 event buffer is full, then any new event overwrites the oldest event.

Defining physical link layer properties

11 In Physical Link Layer tab, under Mode of Operation, click the necessary option.

If you want to establish serial communication, click Serial option under Serial. Select the port from the Serial Port drop-down list. By default, Port A is selected.



Step Action

.

ATTENTION

For RS485 communication, these two options are enabled.

Select Enable Collision Avoidance to prevent any data collision on the link.

Type any value in the Max. Random Delay box. Maximum allowed value is 5000 mS.

SCADA Master monitors the data from many DNP3 Slaves through RS-485 network (multi-drop links). However, RS-485 network supports only simplex (one-way communication at a time) and if unsolicited response is enabled, then multiple RTUs try to transmit data at the same time. In this scenario, RTU supports a collision avoidance algorithm

Or

If you want to establish Ethernet TCP communication from RC500 RTU, click TCP option button and perform the following.

a) Click Server.

b) Type the TCP port in the TCP/UDP Port box that is used for communication between RC500 and DNP3 master.

ATTENTION

Typically, DNP3 slave acts as a TCP server which means accepts DNP3 master connection requests.

If DNP3 slave is to act as a TCP Client, then perform the following.

a) Click Client and type the IP address of the host (DNP3 Master).

b) Type the TCP port that is used for communication between RC500 and DNP3 master in TCP/UDP Port box.

Or

If you want to establish Ethernet UDP communication from RC500 RTU, click UDP option and type the UDP Port that is used for communication between RC500 and DNP3 Master in TCP/UDP Port box.



Step Action

ATTENTION

If you want to enable DNP3 Multi-Master capability, then refer to the section Defining Multi-Master properties.

Defining data link layer properties

12 In the Data Link Layer tab, if Same as RC500 Station Number is not selected, then type the DNP address of the selected controller in This Station DNP Address box.

ATTENTION

If Same as RC500 Station Number is selected, then the DNP address is same as the station number.

13 Type the time delay before sending the response from the slave in Min Response Delay box. Maximum allowed value is 255 mS.

14 Select Enable Data Link Confirmations to configure retry and timeout for the data link frames that are not confirmed.

ATTENTION

Enable Data Link Confirmations is not selected by default.

Ensure to set the Data Link Timeout and Retries as it might load the network.

15 Type the value in Data Link Retries and Retry Timeout boxes.

Maximum allowed value for retries is 255.

Maximum allowed value for retry timeout is 3600000 mS.

ATTENTION

The DNP3 Slave Driver can be configured to send its own DNP Address when a DNP Master requests for it. When Enable Self Address is selected, if a message is sent with the "Self Address" (65532) in the destination address field, RC500 responds with its unique individual address. This feature simplifies the commissioning, troubleshooting, and maintenance of devices with an unknown address. If this feature is not enabled, the station ignores the messages sent to the "Self Address.



Step Action

Defining application layer properties

16 In the Application Layer tab, Select Enable Application Layer Confirm to request confirmation from DNP3 master for all the application fragments sent by RC500.

If you select Use different SEQ numbers for confirm and response, the DNP3 master requests confirmation for all the application fragments sent by RC500. Then the DNP3 driver responds with the sequence number in an increment method.

17 Type the timeout for which RC500 would wait for the confirmation from the DNP3 master in Application Confirmation TimeOut box.

Maximum allowed value for timeout is 3600000 mS.

Defining DNP objects mapping

In the Object Mapping tab, you can map the RC500 I/O as DNP3 points. It displays a list with all existing I/O types.

18 Double-click the required I/O type or select the I/O type and click Map I/O.

The Station dialog box appears.

19 In the General tab, clear Auto Detect and then type the register address in the Highest Register Address box.

ATTENTION

If Auto Detect is selected, then the detected last register address of that particular IO type is showed in the Highest Register Address box automatically and No DNP3 Points is unavailable.

If you do not want to map the RC500 I/O points to DNP3 points, select No DNP3 Points.



Step Action

In the Object 1-Binary Inputs tab, you can map each of the Binary inputs configured in the station to a respective DNP class.

The available classes are Class 1, Class 2, and Class 3.

Similarly, you can also map the following I/O types that are configured in the station to a respective DNP class.

Analog Inputs

Floating Point Inputs

Long Inputs

Binary Counters

ATTENTION

Output points, are also mapped as DNP3 points but will not have any class associations.

For more information about how to map all I/O types to DNP class, refer to the section Map I/O types to DNP class.

Defining default variation configuration 20 Under Default Variation tab, you can configure default variation for each type of

DNP3 point. Default variation defines the data format that is used by the RC500 to send data to DNP3 Master, when the Master does not specifically ask for a specific data variation.

21 Default values are selected for each DNP3 point. If you want to change the value, select the required value from the drop-down list for each DNP3 point.

ATTENTION

Default variation of the Binary Input Change has to be 2: with time, when binary input points are configured as SOE (sequence of events) points in Experion.

Defining Multi-Master properties 22 In Physical Link Layer tab, Click TCP and select Enable Multi-Master.

23 In Multi-Master tab, under Mode, click any one of the following as per requirement.

IP Based: To allow Multiple DNP3 masters to fetch data from RC500 through the configured IP addresses.



Step Action

Port Based: To allow Multiple DNP3 masters to fetch data from RC500 through the confi

Documents

Honeywell RC500 SCONTRL RTU Users Guide