Control Edge

ControlEdge
Builder User's Guide
RTDOC-X283-en-130A
September 2016
Release 130
Document Release Issue Date
RTDOC-X283- 130 0 September 2016
en-130A
Disclaimer
This document contains Honeywell proprietary information. Information contained
herein is to be used solely for the purpose submitted, and no part of this document or its
contents shall be reproduced, published, or disclosed to a third party without the express
permission of Honeywell International Sàrl.
While this information is presented in good faith and believed to be accurate, Honeywell
disclaims the implied warranties of merchantability and fitness for a purpose and makes
no express warranties except as may be stated in its written agreement with and for its
customer.
In no event is Honeywell liable to anyone for any direct, special, or consequential
damages. The information and specifications in this document are subject to change
without notice.
Copyright 2016 - Honeywell International Sàrl
2 www.honeywell.com
Contents
1 About this guide ....................................................................................................................... 7

2 Getting started with ControlEdge Builder .............................................................................. 9
2.1 Before you start ................................................................................................................................. 10
2.2 Launching ControlEdge Builder ....................................................................................................... 12
2.3 Working with projects ....................................................................................................................... 13
2.3.1 Creating a project ............................................................................................................... 13
2.3.2 Opening an existing project ............................................................................................... 15
2.4 Connecting a Controller .................................................................................................................... 16
2.5 Configuring controller redundancy ................................................................................................... 17
2.6 Selecting operating modes ................................................................................................................ 18
3 Configuring communication .................................................................................................. 21
3.1 Configuring Ethernet Ports ............................................................................................................... 22
3.1.1 Configuring ETH1 and ETH2 ............................................................................................ 22
3.1.2 Configuring ETH3 and ETH4 ............................................................................................ 23
3.2 Configuring Protocols ....................................................................................................................... 26
3.2.1 Configuring a Modbus Slave ............................................................................................. 26
3.2.2 Configuring an OPC UA client .......................................................................................... 26
3.2.3 Configuring an OPC UA server ......................................................................................... 27
3.3 Configuring SCADA Mapping ......................................................................................................... 31
3.3.1 Adding a Modbus Slave mapping table ............................................................................. 31
3.3.2 Renaming a mapping table ................................................................................................. 32
3.3.3 Deleting a mapping table ................................................................................................... 32
3.3.4 Exporting a mapping table ................................................................................................. 32
3.3.5 Importing a mapping table ................................................................................................. 32
4 Configuring I/O Modules and channels ................................................................................ 33
4.1 Managing an I/O module .................................................................................................................. 34
4.2 Configuring UIO ............................................................................................................................... 36
4.3 Binding I/O Channels to I/O Variables ............................................................................................. 41
4.3.1 Creating an I/O Variable ..................................................................................................... 41
4.3.2 Binding an I/O Variable to an I/O Channel ........................................................................ 42
4.3.3 I/O Channel Data ............................................................................................................... 42
4.4 Importing I/O configuration .............................................................................................................. 46
4.5 Exporting I/O configuration .............................................................................................................. 50
3
CONTENTS
5 Programming with IEC 61131-3 ............................................................................................. 51

6 Downloading a project to the controller ............................................................................... 55
7 Debugging the Program ......................................................................................................... 59
8 Administration of the system ................................................................................................ 61
8.1 Configuring Date/Time ..................................................................................................................... 62
8.1.1 Setting Time Source ........................................................................................................... 62
8.1.2 Setting Time Zone .............................................................................................................. 62
8.2 User Privileges .................................................................................................................................. 63
8.2.1 Changing the Password ...................................................................................................... 63
8.3 Managing a project ............................................................................................................................ 65
9 Maintenance ............................................................................................................................ 67
9.1 Upgrading firmware .......................................................................................................................... 68
9.1.1 Upgrading firmware for a non-redundant controller .......................................................... 68
9.1.2 Upgrading firmware for a redundant controller ................................................................. 70
9.1.3 Upgrading EPM firmware .................................................................................................. 71
9.1.4 Upgrading I/O module firmware ........................................................................................ 73
9.2 Rebooting a controller ....................................................................................................................... 77
9.3 Resetting to factory defaults ............................................................................................................. 78
9.3.1 Resetting a connected controller directly ........................................................................... 78
9.3.2 Resetting via SD card ......................................................................................................... 78
10 Diagnostics ........................................................................................................................... 79
10.1 Viewing system diagnostics ............................................................................................................ 80
10.2 Viewing I/O diagnostics .................................................................................................................. 81
10.3 Uploading and Viewing System Event Log .................................................................................... 84
10.3.1 Uploading System Event Log .......................................................................................... 84
10.3.2 Viewing System Event Log .............................................................................................. 84
10.4 Uploading Dump File ...................................................................................................................... 85
10.5 Capturing project diagnostic information ....................................................................................... 86
11 Appendix A error code reference ........................................................................................ 87
12 Appendix B Modbus Master Configuration ........................................................................ 93
12.1 Modbus TCP Master ....................................................................................................................... 94
12.1.1 Configuring Modbus TCP Master .................................................................................... 94
12.1.2 Programming Modbus TCP Master ................................................................................. 94
12.2 Description of Modbus Function Block .......................................................................................... 98
12.2.1 Read Single Coil .............................................................................................................. 99
12.2.2 Read Multiple Coils ....................................................................................................... 101
12.2.3 Read Single Discrete Input ............................................................................................ 103
12.2.4 Read Multiple Discrete Inputs ....................................................................................... 105
12.2.5 Read Single Input Register ............................................................................................ 107
4 www.honeywell.com
CONTENTS
12.2.6 Read Multiple Input Registers ....................................................................................... 109

12.2.7 Read Single Holding Register ........................................................................................ 111
12.2.8 Read Multiple Holding Registers ................................................................................... 113
12.2.9 Write Single Coil ............................................................................................................ 116
12.2.10 Write Single Holding Register ..................................................................................... 117
12.2.11 Write Multiple Coils ..................................................................................................... 119
12.2.12 Write Multiple Holding Registers ................................................................................ 121
12.2.13 Description of CONFIG_INFO ................................................................................... 123
12.2.14 Description of Input and Output Data Type ................................................................. 125
12.3 Modbus Protocol Error Codes ....................................................................................................... 126
12.4 Endian Mode ................................................................................................................................. 128
13 Notices ................................................................................................................................. 129
5
CONTENTS
6 www.honeywell.com
1 About this guide
Revision history
Revision Date Description

A September 2016 Initial release of this document
Intended audience
This documentation is intended for the following audience: Users who plan, install,
configure, operate, or maintain the ControlEdge 900 Controller and I\O modules running
the eCLR (IEC 61131-3) execution environment.
Prerequisite skills
Knowledge of SCADA systems and experience of working in a Microsoft Windows
environment are required.
Special terms
The following table describes some commonly used industry-wide and Honeywell-
specific terminology:
Terminology Description
SCADA Supervisory Control and Data Acquisition
Experion® PKS Experion® Process Knowledge System
AI Analog Input
AO Analog Output
DI Digital Input
DO Digital Output
7
1 ABOUT THIS GUIDE
Terminology Description
POU Programming Organization Unit
CPM Control Processor Module
EPM Expansion Processor Module
Local I/O rack I/O rack with CPM installed (non-redundant)
Expansion I/O rack I/O rack with EPM installed
Related documents
The following list identifies publications that may contain information relevant to the
information in this document.
Document name Document number

ControlEdge Builder Software Installation User’s Guide RTDOC-X285-en-130A
ControlEdge 900 Controller Hardware Planning and HWDOC-X430-en-A
Installation Guide
ControlEdge Builder Software Change Notice RTDOC-X166-en-1301A
8 www.honeywell.com
2 Getting started with ControlEdge Builder
Related topics
“Before you start” on page 10
“Launching ControlEdge Builder” on page 12
“Working with projects” on page 13
“Connecting a Controller” on page 16
“Configuring controller redundancy” on page 17
“Selecting operating modes” on page 18
9
2 GETTING STARTED WITH CONTROLEDGE BUILDER
2.1 Before you start

Before you begin with the configuration, ensure that ControlEdge Builder has been
correctly installed.
See ControlEdge Builder Software Installation User’s Guide for more information
regarding the ControlEdge Builder installation.
See ControlEdge 900 Controller Hardware Planning and Installation Guide for more
information regarding ControlEdge 900 Controller installation and configuration.
The following table lists the commonly used tasks:
If you want to... Then, see this topic...

Configure the controller and 1. Open ControlEdge Builder, see “Launching ControlEdge
program the project for the Builder” on page 12.
first time 2. Create a Project, see “Creating a project” on page 13.
3. Configure IP address, see “Configuring ETH1 and ETH2” on
page 22.
Tip
The configurations from the second row to the end
are optional which should be completed before
programming with IEC61131-3.
4. Configure I/O network topology, see “Configuring ETH3 and
ETH4” on page 23.
5. Program with IEC 61131-3 optionally, see “Programming
with IEC 61131-3” on page 51.
6. Connect to a controller, see “Connecting a Controller” on
page 16.
7. Download the configuration, see “Downloading a project to
the controller”.
8. Monitor and debug the program optionally, see “Debugging
the Program” on page 59.
Configure redundancy “Configuring controller redundancy” on page 17
Select operating modes “Selecting operating modes” on page 18
Configure Modbus slave 1. Assign Modbus slave protocol to an Ethernet port, see
“Configuring ETH1 and ETH2” on page 22.
2. Add a mapping table, see “Adding a Modbus Slave mapping
table” on page 31.
3. Configure Modbus slave settings, see “Configuring a
Modbus Slave” on page 26.
10 www.honeywell.com
If you want to... Then, see this topic...

Configure Modbus master “Appendix B Modbus Master Configuration” on page 93
Configure OPC UA client “Configuring an OPC UA client” on page 26
Configure OPC UA server “Configuring an OPC UA server” on page 27
Configure I/O Module “Configuring Input and Output”
Upgrade firmware “Upgrading firmware” on page 68
Reboot the controller “Rebooting a controller” on page 77
Reset the controller to the “Resetting to factory defaults” on page 78
factory defaults
Configure Date/Time “Configuring Date/Time” on page 62
Change the password “Changing the Password” on page 63
Capture controller dump files Install an SD card in the CPM.
of future system errors
If an incident occurs, see “Uploading Dump File” on page 85.
Attention
A dump file is ONLY generated automatically if the
controller has an SD card installed. Installing an SD card
after an event is too late.
11
2.2 Launching ControlEdge Builder

Click Start > All Programs > Honeywell > ControlEdge Builder > ControlEdge
Builder to launch ControlEdge Builder and the Start Page appears. Start Page is outside
any project context, and enables the user to select an action to start. It provides several
actions:
• Create Project: click the icon to create a new project with default ControlEdge 900
Controller configuration.
• Open Project: click the icon to open an existing project.
• Connect: click the icon to connect to a controller.
Figure 1: Start Page
2.3 Working with projects

You can create a new project or open an existing project in ControlEdge Builder.
Related topics
“Creating a project” on page 13
“Opening an existing project” on page 15
2.3.1 Creating a project

The configuration and programming details are stored in a project.
To create a new project

1 From the Start Page, click Create Project.
2 In the Create New Project from Template window, click General and select
900cp1 from the Available Templates list.
3 Click Next. The Save As window appears.
4 Select an appropriate directory to save the project and enter a name for the project in
the File name field.
Attention
• The project name must not exceed 24 characters.
• The directory path length must not exceed 171 characters.
5 Click Save. A project is created, and the Home Page appears. You can click Set
Controller Name under Controller and Communications and enter the desired
name for the controller.
Figure 2: Home Page
13
Item Description
1 Open Project: open an existing project.
2 Connect/Disconnect: connect/disconnect with a controller.
3 Project Name: display the project name.
4 After connecting with a controller, the connection status, name, IP address, role
and operating mode of the connected controller are displayed.
5 FW: select and display the target firmware version used for the project upgrade.
6 Controller HW: select and display the target hardware version used for the
project upgrade.
7 Download: download the configuration to the connected controller.
8 More > Back To Start Page: return back to the Start Page.
9 Toolbar. See the table below for each item.
The following table lists the commonly used toolbar icons which are highlighted in
callout 9 of the picture above.
Icon Name Description

ControlEdge Click it to move to the Home Page.
Configuration
Workspace
IEC Programming Click it to move to the IEC Programming Workspace.
Workspace
Make Click it to compile the changed worksheets.
Rebuild Project Click it to compile all worksheets. The command Rebuild
Project should only be used if 'Make' generates compiling
errors or you have unzipped your project without the
frontend code.
Project Control The control dialog Resource_name is used to control the
Dialog communication with one single PLC or simulation - in
contrast to the project control dialog that is able to control
several PLCs. Thus, the control dialog 'Resource name' is
also known as resource control dialog.
Debug on/off Click it to switch all worksheets between offline and online
mode.
• Online: monitor the online values of the project.
• Offline: configure the project.
2.3.2 Opening an existing project

1 From the Start Page, click Open Project.The default folder of all the available
projects in the system appears.
2 Select the target project and click Open.The project is opened, and the Home Page
appears.
15
2.4 Connecting a Controller

Click Connect from the Home Page, and the Connect controller page appears.
Select one of the following two methods to connect a controller:
• Scan the network to connect a controller
1. Click the Scan and Select tab to view the detailed information about the
discovered controllers in the system.
2. Select the target controller. Then, select the user name and type in the password.
For the initial password of each user type, see “User Privileges” on page 63.
3. Click Connect.
• Manually type in IP address to connect a controller
1. Click IP Address tab, enter the IP address of the target controller.
Attention
– For the non-redundant controller, if the DHCP client is not enabled on ETH2,
the default static IP address of ETH2 is 192.168.1.50.
– For the redundant controller, if DHCP clients are not enabled on ETH1 and
ETH2, the default static IP address of the primary controller (CPM1) on ETH2 is
192.168.1.50, and the secondary controller (CPM2) is 192.168.1.51.
2. Select the user name and type in the password. For the default password of each
user type, see “User Privileges” on page 63.
3. Click Connect.
Tip
ControlEdge Builder will disconnect with the controller automatically if there is no
communication between them including displaying the diagnostic view, uploading the
datalog, downloading the configuration, and upgrading the firmware for over ten
minutes.
2.5 Configuring controller redundancy
To disable redundancy
1 Under Communication, select Configure Redundancy.
2 Select Disable Redundancy to disable the redundancy function.
3 Click OK. Redundancy has been disabled. The IP address configured for the
secondary controller will be disabled.
To enable redundancy
1 Under Controller and Communications, select Configure Controller
Redundancy.
2 Select Enable Controller Redundancy, and then click OK.
The configuration of I/O modules in the rack local to the controller will be removed
and a static IP address must be configured for the secondary controller.
3 Configure the IP address of the controllers.
• If the Obtain an IP Address Automatically options of ETH1 and ETH2 were
enabled, this option will be disabled automatically. Configure Primary
Controller IP Address and Secondary Controller IP Address manually.
• If the Obtain an IP Address Automatically options of ETH1 and ETH2 were
disabled, configure the Secondary Controller IP Address manually.
17
2.6 Selecting operating modes

The operating modes for the CPM are:
• Stop Locked: All tasks are inactive and ready to be executed, therefore the I/O
images are not updated and no output signals are transmitted to the I/Os.
• Run Locked: CPM performs all control and communication tasks and on-line
configuration editing and configuration changes are inhibited.
• Running: CPM performs all control and communication tasks and on-line
configuration editing are permitted.
• Stopped: All tasks are inactive and ready to be executed, therefore the I/O images
are not updated and no output signals are transmitted to the I/Os.
See the following table as a reference when determining your CPM operating mode:
Table 1: Privilege of operating modes
Mode Switch position

STOP RUN REMOTE
on CPM
Operating mode Stop Locked Run Locked Running Stopped
Switchover command Yes Yes Yes Yes
Enabling sync Yes Yes Yes Yes
Disabling sync Yes Yes Yes Yes
Becoming primary Yes Yes Yes Yes
Resetting statistics Yes Yes Yes Yes
Configuration
Yes No Yes1 Yes
download
Firmware download Yes No Yes2 Yes
Forcing outputs Yes3 Yes Yes Yes3
Warn/Cold reboot Yes No No Yes
Factory reset Yes No No Yes
Warn/Cold start
No N/A N/A Yes
command
Stop Command N/A No Yes N/A
Mode Switch position

STOP RUN REMOTE
on CPM
Note:
1. Two types of configuration download: download changes and download all. Download all is
only available when the system is in Stopped or Stop Locked operating mode.
2. Only on-process firmware upgrade is allowed in the Running operating mode.
3. When forcing outputs are in the Stopped state, the forced values are pending until it transits
to the Running mode. When forcing outputs are in the Stopped or Stop Locked operating
mode, the forced values are pending until it transits to the Running or Run Locked operating
mode.
To change the operating modes, turn the mode switch on CPM or configure from the
configuration tool when the mode switch is in Remote position.
To change the operating mode

1 From the Home Page, click the Project Control Dialog icon from the toolbar.
2 Click Warm or Cold to change the operating mode to Running. Click Stop to
change the operating mode to Stopped. For more information about Warm, Cold and
Stop, see the table “Parameter description of eclrRes window” in “Downloading a
project to the controller” on page 55.
19
3 Configuring communication
Related topics
“Configuring Ethernet Ports” on page 22
“Configuring Protocols” on page 26
“Configuring SCADA Mapping” on page 31
21
3 CONFIGURING COMMUNICATION
3.1 Configuring Ethernet Ports

There are four Ethernet ports, ETH1, ETH2, ETH3 and ETH4, on the controller. ETH1
and ETH2 are used for communicating with PC application and/or other controllers, or
other devices. ETH3 and ETH4 are used for communicating with EPMs on the I/O
network.
Related topics
“Configuring ETH1 and ETH2” on page 22
“Configuring ETH3 and ETH4” on page 23
3.1.1 Configuring ETH1 and ETH2
Configuring Ethernet ports for the non-redundancy

1 Click the arrow beside Configure Ethernet Ports from Home Page, and select
ETH1 or ETH2.
2 Under Network Setting, perform one of the following methods to configure the IP
Address of the Ethernet port:
• Click Obtain an IP address automatically to acquire an IP address dynamically.
If DHCP client is enabled on any Ethernet port, and DHCP server is not
available, that port is assigned an IPv4LL address which is in the 169.254.x.x
subnet.
• Select Use the following IP address to specify a static IP address, and type in the
IP Address, Subnet Mask and Gateway.
3 Under the Protocol Binding, select the protocol which you want to bind to the port.
You are provided with three options, Modbus TCP Slave, Modbus TCP Master,
and OPC UA Server.
See the following table for details about supported protocols :
Table 2: Protocol Supported by ETH1 and ETH2
Protocol Description
Modbus TCP Slave Used for communication between the controller and a Modbus TCP
master such as a SCADA system like Experion.
The controller acts as the Modbus TCP slave.
The TCP port number is configurable and the default value is 502.
Protocol Description
Modbus TCP Master Used for communication between the controller and third-party
Modbus slave devices.
The controller acts as the Modbus TCP Master.
For how to configure the Modbus TCP Master, see “Appendix B
Modbus Master Configuration” on page 93.
OPC UA Server Used for communication between the controller and an OPC UA
client such as a SCADA system like Experion or other controllers.
The controller acts as the OPC UA Server.
The TCP port number is configurable and the default value is 4840.
4 Click Save to complete the Ethernet port configuration.

5 Click Back to return to the Home Page.
Configuring Ethernet ports for the redundancy

ETH1 or ETH2.
2 Under Network Setting, Select Use the following IP address to specify a static IP
address, and type in the Primary Controller IP Address, Secondary Controller IP
Address, Subnet Mask and Gateway.
Tip
The Secondary Controller IP Address is unavailable if the redundancy function is
disabled. See “Configuring controller redundancy” on page 17 for instructions to
configure redundancy.
3 Under the Protocol Binding, select the protocol which you want to bind to the port.
You are provided with three options, Modbus TCP Slave, Modbus TCP Master,
and OPC UA Server.
See “Table 2: Protocol Supported by ETH1 and ETH2” for the information about
supported protocols.
3.1.2 Configuring ETH3 and ETH4

ETH4 has the same configuration as ETH3, so only ETH3 should be configured
manually.
23
Configuring Ethernet ports for the non-redundancy

ETH3 or ETH4.
2 Under Network Setting, enter the IP Address and the Subnet Mask of the Ethernet
port.
Attention
• The default IP address is 172.168.0.101.
• The range of the IP address is from 101 to 254.
• The IP address cannot be in the same network subnet as ETH1 and ETH2.
3 Select Ring Topology or Star Topology under I/O Network Topology.

This configuration should match the position of 100X switch on the EPM hardware.
For more information about the switch, see “Assembling I/O racks” in the
ControlEdge 900 Controller Hardware Planning and Installation Guide.
Configuring Ethernet ports for the redundancy

ETH3 or ETH4.
2 Under Network Setting, configure the IP addresses. Type in the CPM A IP
Address, CPM B IP Address and the Subnet Mask of the Ethernet port.
• If redundancy is enabled: type the CPM A IP Address, and CPM B IP Address
is automatically incremented by 1. Type the Subnet Mask for the Ethernet port.
For example: CPM A IP Address is configured as 172.168.0.101, and CPM B
IP Address will be 172.168.0.102.
• If redundancy is disabled: type the CPM A IP Address, and CPM B IP Address
is disabled. Type the Subnet Mask for the Ethernet port.
Attention
• The default IP address is 172.168.0.101.
• The range of the IP address is from 101 to 254.
• The IP address cannot be in the same network subnet as ETH1 and ETH2.
3 Select Ring Topology or Star Topology under I/O Network Topology.

This configuration should match the position of 100X switch on the EPM hardware.
For more information about the switch, see “Assembling I/O racks” in the
ControlEdge 900 Controller Hardware Planning and Installation Guide.
25
3.2 Configuring Protocols

You can configure protocols including Modbus Slave, OPC UA Client and OPC UA
Server. You can then select the protocol to bind to the Ethernet ports.
Related topics
“Configuring a Modbus Slave” on page 26
“Configuring an OPC UA client” on page 26
“Configuring an OPC UA server” on page 27
3.2.1 Configuring a Modbus Slave

1 Click Configure Protocols > Modbus Slave and select the target communication
ports.
2 Select Slave ID.
3 Select the required mapping table from the Mapping drop-down list. See “Adding a
Modbus Slave mapping table” on page 31 for more information.
Tip
The same mapping table may be selected for use on multiple ports. For example, this
could be used when a SCADA system communicates through 2 ports in for
redundancy.
3.2.2 Configuring an OPC UA client

OPC UA client maintains sessions in response to each execution of the UaConnect
function block. One execution of the UaConnect function block contains that one
corresponding session will be created by the OPC UA client on the controller and
correspondingly one session will be created on the target OPC UA server.
Attention
Make sure that the OPC UA Server’s time is synchronized to the controller’s time.
To configure an OPC UA client

1 Click Configure Protocols > OPC UA Client. The OPC UA Client page appears.
2 Select the values for the Max Session Count and Max Subscription Per Session
parameters.
See the following table for the parameter description.
Table 3: OPC UA Client parameter description
Parameter Description
Max Session Count The maximum number of concurrent sessions allowed by the client
If you enter a value of 0, the number of sessions allowed is unlimited.
The default value is 100.
Max Subscriptions The maximum number of subscriptions allowed by the client for one
Per Session session
If you enter a value of 0, the number of subscriptions allowed is
unlimited.
Attention
For R130, this parameter cannot be configured.
3 Click Save.
3.2.3 Configuring an OPC UA server

Attention
• Make sure that the OPC UA client’s time is synchronized to the controller’s time.
• It is recommended to use the default values for the parameters of OPC UA Server.
To configure an OPC UA server

1 Click Configure Protocols > OPC UA Server. The OPC UA Server page appears.
2 Configure the following parameters if required:
Table 4: OPC UA Server parameter description
Port The port that clients will use to connect. For example: opc.tcp://
192.168.0.15:4840
Max Request Age The maximum age of a request (in milliseconds) the server allows.
Zero value is defined as unlimited.
The default value, which is 0, indicating that the request age allowed
is unlimited.
27
Max Session Count The maximum number of concurrent sessions the server allows.
If you enter a value of 0, the number of sessions allowed is unlimited.
Max Subscription The maximum number of subscriptions allowed by the server for one
Per Session session.
If you enter a value of 0, the number of subscription allowed is
unlimited.
Attention
Max Session Per The maximum number of concurrent sessions the server allows per
Client client.
The default value, which is 0, indicating that the number of sessions
allowed is unlimited.
Min Session The minimum timeout for a session (in milliseconds).
Timeout
If you enter a value of 0, the minimum timeout is unlimited.
Max Session The maximum timeout for a session (in milliseconds).
Timeout
If you enter a value of 0, the maximum timeout is unlimited.
Max Browse The maximum number of browse continuation points managed by a
Continuation Points session.
Max Browse Results The maximum number of browse results for one browse operation.
The default value, which is 0, indicating that the number of browse
results is unlimited.
Max Nodes To The maximum number of nodes to browse.
Browse
The default value, which is 0, indicating that the number of nodes
Min Publishing The minimum cycle rate of the Subscription.
Interval
The default value is 50 milliseconds.
Max Publishing The maximum cycle rate of the Subscription.
Interval
The default value, which is 0, indicating that the publishing interval
Min Keep Alive The minimum interval after which the subscription sends a
Interval notification to the client. This notification ensures the subscription is
maintained.
Min Subscription Provides assurance to the client that the server is still alive.
Lifetime
The minimum period after which the subscription will be deleted if no
publish request is received.
If you enter a value of 0, the subscription lifetime allowed is
unlimited.
Max Subscription Provides assurance to the server that the client is still alive.
Lifetime
The maximum period after which the subscription will be deleted if
no publish request is received.
The default value, which is 0 milliseconds, indicating that the
subscription lifetime allowed is unlimited.
Max Retransmission The maximum number of messages allowed per Subscription in the
Queue Size republish queue.
Max Notifications The maximum number of notifications allowed per Publish.
Per Publish
The default value, which is 0, indicating that the number of
notifications allowed is unlimited.
Max Data Queue The maximum size of data monitored item queues.
Size
Max Event Queue The maximum size of event monitored item queues.
Size
Attention
Max Subscription The maximum number of subscriptions that can be created.

Count
The default value, which is 0, indicating that the number of
subscriptions allowed is unlimited.
Max Monitored Item The maximum number of items that can be monitored.
Count
The default value, which is 0, indicating that the number of items
29
Max Monitored Item The maximum number of items that can be monitored for each
Per Subscription subscription.
Count
Max Monitored Item The maximum number of items that can be monitored for each
Per Session Count session.
For more information about the parameter descriptions, see the specification in the https://
opcfoundation.org/.
3 Click Save.
3.3 Configuring SCADA Mapping

When a controller acts as a slave to a master, such as in a SCADA system, mapping
tables are used to map controller variables to protocol addresses.
Related topics
“Adding a Modbus Slave mapping table” on page 31
“Renaming a mapping table” on page 32
“Deleting a mapping table” on page 32
“Exporting a mapping table” on page 32
“Importing a mapping table” on page 32
3.3.1 Adding a Modbus Slave mapping table

1 From the Home Page, under Programming and I/O, select Configure SCADA
Mapping > Modbus Slave.
2 Click Add Mapping, and enter the mapping table name in the Name field. Then,
click OK.
3 Configure address mapping for each of the data types Discrete Inputs, Coil,
Holding Register, and Input Register as required.
4 In the Discrete Inputs tab, click Add to add more addresses as required. The
maximum quantity of registers that can be added is 8000.
5 For each address:
Tip
For efficient communications, Modbus addresses should be sequential in the mapping
table.
a Modify the Modbus Address if required.

b Click the browse button under the Variable Name field and select the relevant
variable.
c Click OK.
6 Repeat steps 4 and 5 for each data type.
7 Click Save.
31
3.3.2 Renaming a mapping table

Attention
If the mapping table has been bound to communication ports, renaming the mapping table
will unbind it from the ports automatically.
1 Select the target mapping table, and click the edit icon .
2 Enter the new name for this mapping table and click OK.
3.3.3 Deleting a mapping table

1 Select the target mapping table, and click .
2 Click Yes to delete the table.
3.3.4 Exporting a mapping table
To export mapping addresses to a .csv file:

1 Select the target mapping table, and click the export icon .
2 Enter the file name in the dialog provided and then click Save.
Tip
The exported .csv file with global variables is not editable. If you want to edit it, first
right-click the column with variable name and select Format Cells. In the Number
tab, select Text and click OK.
3.3.5 Importing a mapping table

Before being imported , the variables should be created in IEC Programming
Workspace.
To import mapping addresses:

1 Select the target mapping table, and click the import icon .
2 Select the target .csv file and click Open, a warning message appears indicating that
the imported variables will overwrite all the existing variables in the project.
3 Click Yes to import the mapping table.
4 Configuring I/O Modules and channels
The I/O module has 16 channels, and each channel can be configured as:
• Digital input (with line monitoring)
• Digital output (with short circuit protection)
• Analog input (0-20mA or 4-20mA active)
• Analog output (4-20mA active)
Related topics
“Managing an I/O module” on page 34
“Configuring UIO” on page 36
“Binding I/O Channels to I/O Variables” on page 41
“Importing I/O configuration” on page 46
“Exporting I/O configuration” on page 50
33
4 CONFIGURING I/O MODULES AND CHANNELS
4.1 Managing an I/O module
Adding an I/O module

1 From the Home Page, under Programming and I/O and click Configure I/O.
2 Click Add I/O Module, the Add I/O Module dialog appears.
3 Select the Type, assign the Rack and Slot, and set the IOM Scan Time for the
Module.
See the following table for the parameter descriptions:
Type I/O module type
Rack Rack address:
• If controller redundancy is enabled, the rack address range is
from 1 to 99.
• If controller redundancy is disabled, the rack address range is
from 0 to 99. 0 is only for the local I/O rack.
• For an expansion I/O rack, the address must be the same with
the EPM address configured on 1x and 10x rotary switches.
For details about the rotary switches, see “Assembling I/O
racks” in the ControlEdge 900 Controller Hardware Planning
and Installation Guide.
Slot Slot number: the location of the I/O module mounted in the rack
• If the I/O module is installed in a 4-slot rack, the slot number is
ranging from 1 to 4.
• If the I/O module is installed in an 8-slot rack, the slot number
is ranging from 1 to 8.
• If the I/O module is installed in a 12-slot rack, the slot number
is ranging from 1 to 12.
IOM Scan Time IOM scan time: the time interval for refreshing the I/O data.
It is recommended to be equal or an integral multiple of the
Interval in the Task settings. To check the Interval, right-click a
Task in IEC Programming Workspace, and select Settings.
For example: if the Interval in Task Settings is 10ms, then set the
IOM Scan Time as 10ms, 20ms or 30ms and so on.
4 Click OK to complete the configuration.
Removing an I/O module

1 From the Home Page, click Configure I/O under Programming and I/O, and select
the target I/O module.
2 Click the Delete icon. A warning message appears to confirm the deletion.
3 Click Yes to delete the I/O module.
After deleting the I/O module, the channels in this I/O module are unbound with the
variables. However, the variables are still existing in the program.
Editing an I/O module

1 From the Home Page, click Configure I/O under Programming and I/O, and select
the target I/O module.
2 Click the Edit icon. The Edit I/O Module page appears.
3 Modify the rack address, slot number or IOM scan time as required, and click Yes.
35
4.2 Configuring UIO

From the Home Page, under the Programming and I/O, click Configure I/O. Select
the target UIO module, and double-click the field under Type for the target channel to
configure the channel type. There are four types can be selected: AI, AO, DI, and DO.
Configuring Analog Input channels

1 Select an AI channel. The AI configuration parameters appear.
2 Configure the parameters as required. See the following table for a description of
each parameter:
Table 5: Analog Input channel parameter
Sensor Type There are two options:
• 0-20mA
• 4-20mA
Open Wire Detection Select the checkbox to enable Open Wire Detection. It is only
available when the sensor type is 4-20mA.
For more information about Open Wire Detection, see “UIO module
wiring” in the ControlEdge 900 Controller Hardware Planning and
Installation Guide.
EU Low1 EU Low default value is 0.
EU High1 EU High default value is 100.
EU Ex Low1 EU Ex Low default value is -10.
EU Ex High1 EU Ex High default value is 110.
EU Description (Optional) Enter Engineering Unit description if it is required.
Note: Use the following algorithm to configure EU Low, EU High, EU EX Low and EU EX
High values to avoid warning messages.
• EU_EX _Low <= Fault Value <= EU_EX_High
• EU_EX _Low = EU_Low – (EU_High – EU_Low ) * 10%
• EU_EX_High = EU_High + (EU_High – EU_Low ) * 10%
• EU_EX _Low <= EU_Low < EU_High <= EU_EX_High
3 Bind I/O variables to physical I/O channels as follows:

a For the target channel, click Bind.
The Select I/O Variable dialog appears. The available I/O variables with data
types compatible to the selected I/O channel type are displayed automatically.
b If the required I/O variable exists in the list, select it and click Bind. If the
required I/O variable is not existing in the list, click Add New Variable to create
a new I/O variable. The Select I/O Variable dialog appears.
You can also create I/O variables from IEC Programming Workspace. See
“Creating an I/O Variable” on page 41 for more details.
c Type the Name and Description, and then click Add.
The I/O variable is created and bound to the I/O channel successfully.
d Click Save.
e Program the I/O variable optionally. See “Programming with IEC 61131-3” on
page 51 for detailed configuration.
Configuring Analog Output channels

1 Select an AO channel. The AO configuration parameters appear.
each parameter:
Table 6: Analog Output channel parameter
Sensor Type 4-20mA
Fail Safe Output There are two options:
Mode
• Hold Last Output
• User Configured Output
User Config Output An appropriate value is needed for User Config Output if the Fail
Safe Output Mode is selected as User Configured Output.
EU Low1 EU Low default value is 0.
EU High1 EU High default value is 100.
EU Ex Low1 EU Ex Low default value is -10.
EU Ex High1 EU Ex Low default value is 110.
Note: Use the following algorithm to configure EU Low, EU High, EU EX Low and EU EX
High values to avoid warning messages.
• EU_EX _Low <= Fault Value <= EU_EX_High
• EU_EX _Low = EU_Low – (EU_High – EU_Low ) * 10%
• EU_EX_High = EU_High + (EU_High – EU_Low ) * 10%
• EU_EX _Low <= EU_Low < EU_High <= EU_EX_High
37

d Click Save.
Configuring Digital Input channels

1 Select a DI channel. The DI configuration parameters appear.
each parameter:
Table 7: Digital Input channel parameter
Direction There are two options:
• Direct: when a high level input is given to a DI channel, the
BOOL type DI value is TRUE; for a low level input, it is
FALSE.
• Reversed: when a high level input is given to a DI channel, the
BOOL type DI value is FALSE; for a low level input, it is
TRUE.
De-bounce Time For Channels that are configured with a de-bounce, the UIO will
declare that the channel has changed state if all the consecutive
samples are in the new state for the configured de-bounce time
period.
It ranges from 0 to 50 and its default value is 0.
For example, if a DI has been 0 and transitions (without noise) to a 1
then the UIO detects that transition and needs the input to stay in the
new state for the configured de-bounce time to declare the new state
as 1. If the signal is noisy, then the counting process starts anew each
time the DI leaves the 0 state until it achieves the new state for
consecutive samples.
State 0 Description (Optional) Enter description if it is required.
Open Wire Detection Select the checkbox to enable Open Wire Detection.
Installation Guide.
Short Circuit Select the checkbox to enable Short Circuit Detection.
Detection
3 Bind I/O variables to physical I/O channels as follows.

d Click Save.
Configuring Digital Output channels

1 Select a DO channel. The DO configuration parameters appear.
each parameter:
39
Table 8: Digital Output channel parameter
Direction There are two options:
• Direct: when a high level input is given to a DI channel, the
BOOL type DI value is TRUE; for a low level input, it is
FALSE.
• Reversed: when a high level input is given to a DI channel, the
BOOL type DI value is FALSE; for a low level input, it is
TRUE.
Fail Safe Output There are two options:
Mode
• Hold Last Output
• User Configured Output
User Config Output An appropriate value is needed for User Config Output if the Fail
Safe Output Mode is selected as User Configured Output.
Open Wire Detection Select the checkbox to enable Open Wire Detection.
Installation Guide.
Short Circuit Select the checkbox to enable Short Circuit Detection.
Detection

d Click Save.
4.3 Binding I/O Channels to I/O Variables

This feature enables the user to program I/O variables and map them to channels of I/O
devices.
Related topics
“Creating an I/O Variable” on page 41
“Binding an I/O Variable to an I/O Channel” on page 42
“I/O Channel Data” on page 42
4.3.1 Creating an I/O Variable

1 Click IEC Programming Workspace from the toolbar.
2 Double-click IO_Data Types under Data Types of Project Tree Window, the
available I/O data structure is displayed.
I/O Type Structure Type

AI ANALOG_INPUT_TYPE
AO ANALOG_OUTPUT_TYPE
ANALOG_OUTPUT_READBACK_TYPE
DI DIGITAL_INPUT_TYPE
DO DIGITAL_OUTPUT_TYPE
DIGITAL_OUTPUT_READBACK_TYPE
3 Double-click Global_Variables under Physical Hardware, the global variable sheet

appears.
4 Right-click under the corresponding group, and select Insert variable to add a new
I/O variable.
For output channel variables, you must add corresponding read back variables with
suffix “_READBACK” in the Input IO Variables group.
5 Double-click the Name and Description fields to modify, and select Type and Usage
from the drop-down lists.
Tip
IEC address of the I/O variable is generated automatically after you bind it with an
I/O channel and click Make. If you add a new I/O variable by copying an existing
bound one in a compiled project, you should delete the IEC address of the new
variable manually and click Make to generate it automatically.
41
6 Program the I/O variables optionally. See “Programming with IEC 61131-3” on
7 Click Make from the toolbar.
4.3.2 Binding an I/O Variable to an I/O Channel

1 From the Home Page, select Configure I/O to bind an I/O channel.
2 For the target I/O channel, click Bind. The Select I/O Variable dialog appears. The
available I/O variables with data types compatible to the selected I/O channel type
are scanned and displayed automatically.
3 Select the target I/O variable and click Bind.
4 Click Save.
Attention
• All I/O variables must be created within the ‘Input I/O Variable’ or ‘Output I/O
Variable’ group of the Global Variables in IEC Programming Workspace.
• To ensure the minimum I/O latency, the task with the fastest interval should also
have the highest priority. It is recommended to use priority of ‘0’ for this task.
• If you change the name and type of an I/O variable, which is bound to a channel,
you must rebind them.
• If an I/O variable is not bound to a channel, its Status (STS) and Process Variable
(PV) will not be updated.
4.3.3 I/O Channel Data
I/O channel structures

Each I/O Channel has one or two structures. All of the related information for this
channel is grouped together in the structures as shown below. You can use this
information as reference for I/O channel configuration and programming.
I/O Type Structure Description

Type
AI ANALOG TYPE
_INPUT_
ANALOG_INPUT_TYPE:
TYPE
STRUCT
STS : USINT;
PV : REAL;
EUHI : REAL;
EULO : REAL;
EUHIEX : REAL;
EULOEX : REAL;
END_STRUCT;
END_TYPE
AO ANALOG TYPE
_OUTPUT
ANALOG_OUTPUT_TYPE:
_TYPE
STRUCT
OP: REAL;
END_STRUCT;
END_TYPE
ANALOG TYPE
_OUTPUT
ANALOG_OUTPUT_READBACK_TYPE :
_READB
ACK_TY STRUCT
PE STS : USINT;
OP_READBACK : REAL;
EUHI : REAL;
EULO : REAL;
EUHIEX : REAL;
EULOEX : REAL;
END_STRUCT;
END_TYPE
43
I/O Type Structure Description

Type
DI DIGITAL_ TYPE
INPUT_T
DIGITAL_INPUT_TYPE:
YPE
STRUCT
STS : USINT;
PV : BOOL;
END_STRUCT;
END_TYPE
DO DIGITAL_ TYPE
OUTPUT_
DIGITAL_OUTPUT_TYPE:
TYPE
STRUCT
OP : BOOL;
END_STRUCT;
END_TYPE
DIGITAL_ TYPE
OUTPUT_
DIGITAL_OUTPUT_READBACK_TYPE:
READBA
CK_TYPE STRUCT
STS : USINT;
OP_READBACK : BOOL;
END_STRUCT;
END_TYPE
I/O channel status

The STS value defines the I/O channel status. See the following table for a definition of
each STS value.
STS Value Description

0 Channel is good.
1 Channel is offline. This could be caused if IOM communication is lost.
11 The value is higher than the extended high range value.
12 The value is higher than the high range value but lower than the extended high
range value.
STS Value Description

13 The value is lower than the low range value but higher than the extended low range
value.
14 The value is lower than the extended low range value.
15 No calibration on the channel, it is for AI and AO only.
16 The channel is open wired, and it is currently for AO only.
18 The field cable has a short circuit. It is applicable for DI and DO.
19 Internal hardware error
20 Read Back Test Fail: Analog/Digital output channel is unable to drive the desired
output current on the terminals. This could happen due to high load resistance or a
broken wire.
45
4.4 Importing I/O configuration

You can configure all I/O in a .csv file and import it in ControlEdge Builder.
A template of the .csv file is provided in “C:\Users\Public\Public Documents
\ControlEdge Builder\IOConfigTemplates” with the following parameters.
Parameter Rule for I/O configuration import

Rack Address Valid value ranges from 0 to 99.
Rack address for each channel of assigned module shall not be empty.
Rack quantity must not be more than 12.
For the redundant controller, the IO configuration in Rack 0 is not
applicable.
Slot Number For 4-slot rack, the slot number ranges from 1 to 4.
For 8-slot rack, the slot number ranges from 1 to 8.
For 12-slot rack, the slot number ranges from 1 to 12.
The quantity of slots assigned to one rack must not be more than 12.
Each channel of the assigned module must be assigned a slot number.
No duplicate slot numbers are allowed in a rack.
Module Type I/O module type
Currently, only UIO16 is supported.
Channel Enabled Indicates whether a channel is enabled for this I/O.
Enter one of the following two values:
• False
• True
False is the default value.
Channel Number The channel number, which can be between 1 and 16, must be aligned
with the module type. All channels must have a number assigned.
Channel Type The type of channel for this module
Valid values are:
• AI
• AO
• DI
• DO

I/O Variable Optional
The variable to which this channel is to be bound.
Tip
Variable names cannot be duplicated, and must comply with
the IEC naming conventions:
• If the variable specified exists in the Variable table in the
IEC Programming Workspace, you must specify a
channel of the same type as that contained defined in the
table. When the I/O configuration file is imported, the
variable is automatically bound to the channel.
• If the variable specified does not exist in the IEC
Programming Workspace, it will be created
automatically after importing the I/O configuration file.
Description The description of I/O variable

EU Description Description of engineering unit
Sensor Type The sensor type depends on the selected module type.
UIO module supports:
• For AI channel: 4-20mA or 0-20mA
• For AO channel: 4-20mA
EU Low Low range of engineering unit
It shall be smaller than EU High
EU High High range of engineering unit
EU Ex Low Optional
Extended low should be lower than EU Low. For details of the
algorithm, see the Note in the table “Analog Input channel
parameter” in “Configuring UIO” on page 36.
(EU Low) - (EU High - EU Low)*10% is the default value.
EU Ex High Optional
Extended high should be higher than EU High. For details of the
algorithm, see the Note in the table “Analog Input channel
parameter” in “Configuring UIO” on page 36.
(EU High) + (EU High - EU Low)*10% is the default value.
OpenWireDetection Open Wire Detection: True or False
Only DI and DO channel of UIO module support Open Wire
Detection.
47

ShortCircuitDetection Short Circuit Detection: True or False
Only DI and DO channesl of UIO module support Short Circuit
Detection.
State 0 Description Optional
Description of State 0
Only DI and DO channels of UIO module support State 0
Description.
State 1 Description Optional
Description of State 1
Only DI and DO channels of UIO module support State 1
Description.
Direction Optional
The given signal of a DI or DO channel. There are two options:
Reverse or Direct.
Direction is direct by default.
Fail Safe Output Mode Optional
Determines the output behavior for AO and DO channel when
failsafe. There are two options: Hold Last Output or User Cfg Output
Hold Last Output is the default value.
AO User Configured Optional
Output
To assign the user configured output.
EU Ex Low <= User configured output <= EU Ex High
EU Ex Low is assumed if the assigned value is smaller than EU Ex
Low;
EU Ex High is assumed if the assigned value is beyond EU Ex High.
0 is the default value.
DO User Configured Optional
Output
Assigns the user configured output. There are two options: 0 or 1.
0 is the default value.
To import I/O configuration

1 From the Home Page, under Programming and I/O, click Configure I/O.
2 Click Import icon, a warning message appears indicating that the imported data may
overwrite current I/O configuration.
3 Click Yes to continue to import.

4 Browse to the location the target file stored and select the .csv file, then click Open
to import the I/O configuration.
49
4.5 Exporting I/O configuration

The I/O configuration can be exported to a .csv file.
To export I/O configuration

1 From the Home Page, under Programming and I/O, click Configure I/O.
2 Click Export icon, the Save As window appears.
3 Browse to the location you want to store the file and click Save to export the I/O
configuration.
5 Programming with IEC 61131-3
This chapter introduces general information about programming with IEC 61131-3.
Each project consists of Libraries, Data Types, POUs and the set of configuration
elements that are contained in the Physical Hardware folder.
The following table describes these terms.
Term Description
Libraries The libraries that are included in your project. These are either user-defined
libraries or firmware libraries:
• User Library: contains programs, function blocks, functions and user-
defined data types, and can be reused across projects. Honeywell
provides user libraries and user can create their own. The file extensions
for user library are *.mwt and *.mwe.
• Firmware Library: contains function blocks and functions prepared by
Honeywell for specific hardware. The file extension for firmware library
is *.fwl.
User-defined Declare user-defined data types such as ARRAYs, STRUCTs and STRINGs.
Data Types Currently, Honeywell provides the following read-only user-defined data
types:
• IO_DataTypes
• MbMaster_DataTypes
• Hart_dataTypes
• Aga_DataTypes
51
5 PROGRAMMING WITH IEC 61131-3
Term Description
Logical POUs Logical Program Organization Units (POUs) are the language elements of a
program. They are small, independent software units containing the program
code. The name of a POU must be unique within the project.
There are three different POU types:
• Program: contains a logical combination of function or function block
calls. Programs have input and output parameters and they can have an
internal memory.
• Function: POUs with multiple input parameters and exactly one output
parameter.
• Function Block: POUs with multiple input/output parameters and
internal memory.
Physical Reflects the structure of configuration elements determined by the controller
Hardware according to the IEC 61131. Honeywell-provided default projects come pre-
configured with the hardware attributes.
Global variables can be declared and programs can be associated to tasks.
Tasks Program POUs must be associated to a task (in the form of program
instances) in order to be executed.
Tasks of different types can be inserted.
• DEFAULT: Each resource can contain one default task. It is the task with
the lowest priority (lower than cyclic tasks) and is not time scheduled.
• CYCLIC: executes their associated programs in fixed time intervals.
• EVENT: executes their associated programs each time a particular event
occurs.
• SYSTEM: executes its associated programs each time a particular system
event occurs.
Tip
Task name and Instance name must start with a letter or an
underscore. The rest of the characters can be letters, numbers or
underscores. The maximum quantity of characters which a task name
can have is seven and that of a program instance is twenty four.
Term Description
Global Variables Declare the variables of the following types to diagnose and monitor the
system:
• System Variables
• Common Variables
• Input IO Variables
• Output IO Variables
• Controller
• Redundancy Local
• Redundancy Partner
• MODBUS MASTER
• MODBUS SLAVE
• IO Diagnostics
See the embedded online help for details about programming. Select Help > Contents
from the toolbar. In the pop-up help, navigate to 7 minutes for an easier startup. For
detailed tutorial, click the video clip at the bottom of each phase.
To program with IEC 61131-3

1 Click the IEC Programming Workspace button from the toolbar. Right-click
Logical POUs and select Insert > Program.
2 In the Insert dialog, type the Name and click OK.
3 To add library, right-click Libraries and click Insert. Select User Library or
Firmware Library.
• For User Library, select .mwt file.
• For Firmware Library, click the corresponding folder and select the target .fwl
file.
Tip
For more information about libraries, see the online help embedded in the
ControlEdge Builder.
4 Right-click Data Type and select Insert > Datatypes and name the target data type.
5 Add global variables as follows:
a Double-click Global_Variables under Physical Hardware, the global variable
sheet appears.
b Right-click under the corresponding group, and select Insert variable to add a
new global variable.
c Double-click Name and Description fields to modify and select Type and Usage
from the drop-down lists.
53
6 Right-click eclrRes : ARM_LE_GCC3* and select Settings. Verify that the

Parameter in the Communication group box is the same as the IP address of the
connected controller.
7 Add a Task as follows:
a Under Physical Hardware, right-click Task and select Insert > Task.
b Enter the name. Select the task type then click OK.
c Configure the parameters as required in the Task settings dialog.
d Click OK.
8 Right-click the task you have inserted and select Insert > Program instance.
9 Enter the name in Program instance and select corresponding Program type. Click
OK.
10 Under Logical POUs, double-click of the program that you have inserted. In the
workplace, drag the target function or function block from the Edit Wizard pane, and
the function or function block is displayed.
11 Double-click the pin-outs of the function or function block, the Variable Properties
dialog appears.
12 Select the Name, Data Type and Usage from the drop-down list, assign the initial
value and I/O address.
13 It is optional to select the target group from Global Variable Groups. Click OK and
the new variables are added to the selected groups. If you do not select a Global
Variable Group, the variables are added to the Common Variables group by
default.
14 Click Make from the toolbar.
6 Downloading a project to the controller
After completing the configuration and programming, you should download your project
to the controller.
Before downloading the project to the controller, you have to ensure:
• The project is opened in ControlEdge Builder.
• The project is compiled without any error.
• The controller is connected.
To download a project
1 From the Home Page, click Download. A eclrRes window appears:
See the following table for the parameter description of the eclrRes window.
55
6 DOWNLOADING A PROJECT TO THE CONTROLLER
Table 9: Parameter description of eclrRes window
State • On: The controller is running and accessible via online
communication, but no application is loaded.
• Loading: The state 'Loading' is only visible while installing a
controller application (e.g. while loading a bootproject).
• Stop: The controller application is loaded and ready to execute
(by pressing one of the start buttons).
• Starting: All necessary initializations are performed including
loading the drivers depending on the start up modes (cold/warm/
hot).
• Running: The controller application is executed.
• state [DEBUG]: The appendix [DEBUG] after the actual state
can appear in conjunction with the states RUN, STOP or HALT.
[DEBUG] indicates, that the debug mode is active, i.e. either
variables are forced or breakpoints are set (if a breakpoint is
reached, the state changes to HALT [DEBUG]).
• HALT: The program execution is halted at a breakpoint which
has been set using the 'Debug' dialog. In this state all user tasks
are inactive and the I/O images are not updated. The program
execution can be resumed with one of the control dialog buttons
'Go', 'Step' or 'Trace'.
• HaltRequested: Intermediate state: During program execution, a
set breakpoint has been reached. All necessary actions to halt the
execution of the controller application are performed.
• Stopping: All necessary actions to stop the execution of the
controller application are performed including unloading the
drivers.
• Resetting: Unloads the controller application and clears the eCLR
application.
• TIMEOUT: This state which is also displayed in the control
dialog 'Resource_name' indicates that the connection between the
programming system and the controller was not established within
the given time interval. The corresponding time interval is set in
the dialog 'Resource settings...' (field 'Timeout'). During this
interval, the system tries to connect the controller. If the interval
has elapsed without a successful connection, the online part of the
programming tool enters the TIMEOUT state.
Stop Stop the program execution on the controller.
Cold Executes a cold start:
• all data are initialized.
• the open functions of all I/O drivers are executed.
• system event 'Cold start' is called.
• all user tasks are activated (ready to be scheduled and executed).
Warm Executes a warm start:
• only non-retentive data are initialized.
• the open functions of all I/O drivers are executed.
• system event 'Warm start' is called.
• all user tasks are activated (ready to be scheduled and executed).
Reset Reset the controller.
Download Download the current project to the controller.
For details, see the embedded online help. Select Help > Contents, and search for
PLC state machine to display the corresponding content.
2 Click OK after the project configuration is downloaded to the controller successfully.
57
7 Debugging the Program
After the project has been downloaded to the controller, and you have performed a cold
or warm start, you can switch the worksheet to online mode to verify and debug the
program.
To debug the program, click from the toolbar under the IEC Programming
Workspace.
For more information about debugging and online mode, see the embedded online help.
Select Help > Contents, and search for Phase 5: Debugging the project in online
mode to display the corresponding content.
59
7 DEBUGGING THE PROGRAM
8 Administration of the system
Related topics
“Configuring Date/Time” on page 62
“User Privileges” on page 63
“Managing a project” on page 65
61
8 ADMINISTRATION OF THE SYSTEM
8.1 Configuring Date/Time
Related topics
“Setting Time Source” on page 62
“Setting Time Zone” on page 62
8.1.1 Setting Time Source

1 From the Home Page, click Configure Date/Time Options under Miscellaneous.
2 Select Enable and enter the IP addresses of SNTP servers in the Primary Server
and Secondary Server fields.
3 Adjust the Poll Interval to synchronize current controller time to the SNTP server.
The SNTP message poll interval is Poll Interval power of 2 (2(Poll Interval)) in unit of
second.
The maximum poll interval is 17 (approx. 36 hours) and the minimum is 6 (64
seconds).
It is recommended to set Poll Interval as 16 (approx. 18 hours). To avoid the
communication storm, the controller will pick a random poll interval time in the
range [2(Poll Interval), 2(Poll Interval+1)], not exactly what is configured.
8.1.2 Setting Time Zone

1 Click Configure Date/Time Options under Miscellaneous.
2 Select Set Time Zone tab, and select the target time zone from the Time Zone drop-
down list.
3 Select Automatically Switch to Daylight Saving Time if it is applicable.
8.2 User Privileges

ControlEdge Builder supports three user types namely Operator, Engineer and
Administrator. Privileges for the various user types are listed as following:
Action Description Operator Engineer Administrator

Change own password √ √ √
Change other’s password √
View diagnostics √ √
Reset diagnostics √ √
Upload datalog (upload only) √ √ √
Upload datalog (upload and delete) √ √
View and control datalog status √ √ √
Upload bulk datalog √ √ √
Upload system event log √ √
Download configuration and program √ √
Upgrade firmware √
Reboot the controller √ √
Reset the connected controller to factory √ √
defaults
The default password of each user type is listed as follows:
User Name Password

Operator Oper@123
Engineer Engr@123
Administrator Admin@123
8.2.1 Changing the Password

You must connect to the controller to change the password. You must change the default
password after you login for the first time.
To change a user’s password

1 To change a user’s password, select Change Password under Miscellaneous. The
Change Password dialog appears.
63
2 Select the target User Name, type in the relevant information in the Original
password, New password and Confirm password fields and click OK.
Attention
The password must have at least one capital letter, one lowercase letter, one number and
one non-alpha numeric character ( E.g. !@#$%^&;*()) and the length must be minimum
eight characters.
8.3 Managing a project

In ControlEdge Builder, a project can be archived as a zipped file and saved as a
template. A previously archived project can be unzipped and then used. It is
recommended to zip your files regularly to back up your work.
You can also print parts of a project or the whole project.
To save the opened project as a template

1 Click File > Save As Template. The Save As Template dialog box appears.
2 Enter the Template Name and select Group.
3 Click OK.
The project will be saved as a template and it is displayed in the Available
Templates.
To save the opened project to a zipped file

1 Click File > Save Project As / Zip Project As. The Save/Zip project as dialog box
appears.
2 From the Save as type drop-down list, select Zipped Project Files (*zwt).
3 Select the required folder and enter a file name for the archive.
4 If user libraries are required in the zipped project, in the Zip Options, select both
Zip User-Libraries and Zip Frontend-Code.
Tip
If Zip Frontend-Code is not selected, when the project is unzipped, the user libraries
might become unusable.
5 Click Zip.
To extract a zipped project

1 Click File > Open Project / Unzip Project from the toolbar. The Open/Unzip
project dialog box appears.
2 From the Files of type drop-down list, select Zipped Project Files (*zwt).
3 Select the target zipped file, and then click Unzip.
4 Click Yes to accept the folder specified, or click No to navigate to another folder.
5 Click Save to extract the zipped project.
65
To print a project
1 Open the target project and click File > Print Project. The Print Project dialog
appears.
2 For the Range, select either:
• All to print the whole project; or,
• Selected to print the selected parts of the project.
3 For the Page Range, select either:
• All to print all pages; or,
• Enter the page numbers you want to print in the Pages field.
4 For the Print, select the following worksheets to be printed:
• Data Type Worksheet
• Description Worksheet
• Variable Worksheet
• Code Worksheet
• Task and Resource Information
• Local Cross Reference
• Global Cross Reference
• OEM specific data
• Table of Contents
5 Click Print. The Save As dialog appears.
6 Select the target directory and click Save.
9 Maintenance
Related topics
“Upgrading firmware” on page 68
“Rebooting a controller” on page 77
“Resetting to factory defaults” on page 78
67
9 MAINTENANCE
9.1 Upgrading firmware

The firmware of CPM, EPM and I/O module can be upgraded using the Upgrade
Firmware option under Maintenance.
Before upgrading the firmware, it is recommended to:
• Log in as the Administrator to connect the target controller.
• Install the latest ControlEdge Builder on your computer. See the ControlEdge
Builder Software Installation User’s Guide for details.
Related topics
“Upgrading firmware for a non-redundant controller” on page 68
“Upgrading firmware for a redundant controller” on page 70
“Upgrading EPM firmware” on page 71
“Upgrading I/O module firmware” on page 73
9.1.1 Upgrading firmware for a non-redundant controller

There are two ways to connect to a controller, and then upgrade the firmware.
• Connect to the controller from the Start Page and upgrade the firmware.
• Open a project from the Start Page, connect to the controller and upgrade the
firmware.
Attention
The firmware upgrade is only allowed in Stop Locked or Stopped operating modes.
To get more information about the connected controller:

1. From the Home Page, click Upgrade Firmware under Maintenance.
2. Select CPM to view the following information about the controller.
Table 10: CPM information
Module Name The configured controller name
Model Number Model number of the connected controller
9 MAINTENANCE
States • Running: The program execution is activated and the inputs and
outputs of the I/O image are updating according to the I/O
configuration.
• Stopped: A program is loaded in the controller but all user tasks are
inactive, therefore the I/O images are not updated and no output signals
are being transmitted to the I/O.
• On: No program is loaded in the controller.
• FW Upgrading: Controller is in firmware upgrade process.
Redundancy Role • Non-Redundant: Indicates a non-redundant controller system.
• Primary: Indicates a redundant controller system.
Rack Address Address of the rack in which the controller is installed
Slot Number The position of the slot on which the controller is installed:
• A
• B(only applicable for a redundant controller)
HW Version Controller hardware version
Boot Version1 Boot firmware version
The controller runs the boot firmware if the application firmware is not
available or corrupt. The boot version has a colored icon to differentiate it
from application firmware version.
Application Application firmware version
Version1 User configuration settings can only be downloaded if the controller is
running application firmware.
Transferred The version of the firmware image which has been transferred to the
Version controller. The version has a colored icon.
• : Indicates the transferred image is the boot firmware image
• : Indicates the transferred image is the application firmware image
The transferred firmware image will be deleted from the controller after
reboot.
Status • Completed: Indicates firmware upgrade has completed successfully.
• In Progress (x%): Indicates firmware upgrade is in process.
Note1: If either of the Boot firmware or Application firmware is invalid, only the invalid one can
be upgraded.
To upgrade firmware
1. From the Upgrade Firmware page, click Transfer, the Transferring firmware
dialog appears.
69
9 MAINTENANCE
2. Click Browse, and select the target firmware file in .pkg format. The target firmware
version number is displayed in Firmware version.
3. Do either of the following to download the target firmware to the controller.
• It is recommended to click Transfer, so only the difference between the target
firmware and the current version is downloaded.
• If the target firmware is the same with the current firmware, but still you want to
overwrite the current firmware. Select Full Transfer and click Transfer.
The updated firmware version is displayed in Transferred Version after it is
downloaded to the controller successfully.
4. Click Upgrade. The Upgrade firmware dialog appears.
5. Click OK. A warning message appears to remind you that the controller will restart
after the upgrade.
6. Click Yes. You can check the upgrade progress under Status. During the upgrade
progress, a warning message appears reminding you that the controller is
disconnected with ControlEdge Builder.
7. The Connect Controller dialog appears after the upgrade is completed. Reconnect
the controller.
8. Check the corresponding firmware version (Boot version or Application version) to
confirm the firmware has upgraded successfully.
9.1.2 Upgrading firmware for a redundant controller

For R130, only Off-process firmware upgrades are allowed for a redundant controller.
Attention
Firmware upgrades are only allowed in Stopped or Stop Locked operating modes for a
redundant controller.
Prerequisites
• Assume the primary controller is at slot A and the secondary controller is at slot B.
• The primary controller (slot A) should be connected with ControlEdge Builder.
• Pull out the secondary controller before upgrading the primary controller.
To upgrade the firmware, Off-process

1 From the Start Page, click Connect to connect the target controller. You can also
click Open Project to open a project and click Connect from the Home Page to
connect the primary controller.
2 Click Upgrade Firmware under Maintenance and select CPM. The CPM status
information appears as shown in the table “CPM information” in “Upgrading
firmware for a non-redundant controller” on page 68.
9 MAINTENANCE
3 Click Transfer. Select the target firmware file in .pkg format. The target firmware
version number is displayed in Firmware version under the Transferring firmware
dialog.
4 Perform either of the following methods to download the target firmware to the
controller.
• If the target firmware is the same with the current firmware, but you still want to
downloaded to the controller successfully.
5 Click Upgrade. The Upgrade firmware dialog appears.
6 Click OK. A warning message appears to remind you the controller will restart after
the upgrade.
7 Click Yes. A progress bar appears indicating the upgrade progress. During the
upgrade progress, a warning message appears reminding you that the controller is
disconnected with ControlEdge Builder.
8 The Connect Controller dialog appears after the upgrade is completed. Reconnect
the primary controller.
9 Pull out the primary controller from the slot A, and inset the secondary controller
into the slot B.
10 Connect to the secondary controller.
11 From the Home Page, click View System Diagnostics under Diagnostics.
12 Right-click System and select Become Primary to set the secondary controller to be
the primary one.
13 Repeat steps 1 to 8 to upgrade the firmware on the secondary controller.
14 After the firmware upgrade is completed, insert the primary controller into the slot A.
9.1.3 Upgrading EPM firmware

Attention
• EPM firmware upgrade is only allowed in Stop Locked, Running or Stopped operating
modes.
• If the EPM is being upgraded, all I/O modules in the same rack will keep in failsafe state
until the firmware upgrade is completed.
1 Perform either of the following to connect the controller.

• From the Start Page, click Connect to connect the target controller.
71
9 MAINTENANCE
• From the Start Page, click Open Project. And then click Connect to connect the
target controller from the Home Page.
2 Click Upgrade Firmware under Maintenance. The Upgrade Firmware dialog
appears.
3 Click EPM tab, all available EPMs are displayed with the following information.
Attention
At least one I/O module, which is in the same rack with the target EPM, must be added
in the Configure I/O page, then the target EPM will be displayed here. See “Configuring
I/O Modules and channels” on page 33 for details.
Table 11: EPM information
Module Name The configured EPM module type
Model Number Model number of EPM
States • OK: EPM is working normally.
• Error: Error exists in EPM.
• Not Configured: Indicates the detected EPM is not configured.
• FW Upgrading: Indicates EPM is in firmware upgrade process.
• Offline: It is failed to detect the EPM in an expected time after
firmware upgrade is started.
Redundancy Role Non-redundant: Indicates redundant EPMs.
Rack Address Rack address configured from 1x and 10x rotary switches on EPM
hardware, ranging from 1 to 99.
Slot Number The position of the slot on which EPM is installed.
A
HW Version EPM hardware version
Boot Version1 Boot firmware version.
EPM runs the boot firmware if the application firmware is not available
or corrupt. The boot version has a colored icon to differentiate it from
application firmware version.
Application Application firmware version. User configuration settings can only be
Version1 downloaded if the EPM is running application firmware.
9 MAINTENANCE
Version target module. The version has a colored icon.
• : Indicates the transferred image is the application firmware
image
The transferred firmware image will be deleted after reboot.
Status • Completed: Indicates firmware upgrade is completed successfully.
• Failed: Indicates firmware upgrade is failed.
Note1: If either of the Boot firmware or Application firmware is invalid, only the invalid one
can be upgraded.
4 Select the target EPM and click Transfer, the Transferring firmware dialog
appears.
5 Click Browse, and select the target firmware file in .pkg format. The target firmware
6 Perform either of the following methods to download the target firmware to the
EPM.
• If the target firmware is same as the current firmware, but you still want to
downloaded to the EPM successfully.
8 Click OK, the upgrade progress is shown in the column Status.
9.1.4 Upgrading I/O module firmware

Attention
I/O module firmware upgrade is only allowed in Stopped, Running or Stop Locked
operating modes.
Prerequisites
The target I/O module must be added in the Configure I/O page. See “Configuring I/O
Modules and channels” on page 33 for more information.
73
9 MAINTENANCE
1 Perform either of the following methods to connect the controller.

• From the Start Page, click Connect to connect the target controller.
• From the Start Page, click Open Project. And then click Connect to connect the
target controller from the Home Page.
2 Click Upgrade Firmware under Maintenance. The Upgrade Firmware dialog
appears.
3 Click UIO 16 tab, all available I/O modules are displayed with the following
information..
Table 12: I/O module information
Module Name The configured I/O module type
Model Number Model number of the I/O module
States • OK: The module is working normally.
• Error: Error exists in the module.
• Not Configured: Indicates the detected module is not configured.
• FW Upgrading: Indicates the module is in firmware upgrade
process.
• Offline: It is failed to detect the module in an expected time within
which upgrade process is expected to be completed.
Redundancy Role N/A: Not applicable to I/O module
Rack Address Rack address, 0 or ranging from 1 to 99
• If the I/O module is mounted in the local I/O rack, the rack address
is 0.
• If the I/O module is mounted in the expansion I/O rack, the rack
address is ranging from 1 to 99.
Slot Number The position of the slot on which the I/O module is mounted, ranging
from 1 to 12.
• If the I/O module is mounted in the 4-slot rack, the slot number is
HW Version I/O module hardware version
9 MAINTENANCE
Boot Version1 Boot firmware version.
The I/O module runs the boot firmware if the application firmware is not
available or corrupt. The boot version has a colored icon to differentiate
it from application firmware version.
Attention
For R130, boot firmware upgrade is not supported.
Application Application firmware version.

Version1 User configuration settings can only be downloaded if the I/O module is
running application firmware.
Version target module. The version has a colored icon.
• : Indicates the transferred image is the application firmware
image
Transferred firmware image will be deleted after reboot.
Status • Completed: Indicates firmware upgrade has completed successfully.
• Failed: Indicates firmware upgrade is failed.
Note1: If either of the Boot firmware or Application firmware is invalid, only the invalid one
can be upgraded.
4 Select the target I/O modules and click Transfer, the Transferring firmware dialog
appears.
5 Click Browse, and select the target firmware file in .pkg format. The target firmware
6 Perform either of the following methods to download the target firmware to the I/O
module:
• It is recommended to click Transfer, wherein only the difference between the
target firmware and the current version is downloaded.
• If the target firmware is same as the current firmware, you may want to overwrite
the current firmware. Select Full Transfer and click Transfer.
downloaded to the I/O module successfully.
8 Click OK, a warning message appears indicating the module will be offline once in
firmware upgrade process.
75
9 MAINTENANCE
9 Click Yes, the upgrade progress is shown in the column Status.
9 MAINTENANCE
9.2 Rebooting a controller

You can use ControlEdge Builder to remotely reboot a controller.
Prerequisites
• Before rebooting the controller, you must log in as the Administrator or Engineer to
connect the target controller.
• Controller reboot is only allowed in Stopped or Stop Locked operating mode.
To remotely reboot the controller

1 Click Reboot Controller under Maintenance. In the pop-up window, select Warm
Reboot or Cold Reboot and click Reboot. See the following table for details on the
effect of warm reboot and cold reboot:
Items Warm Reboot Cold Reboot

Program Program is stopped and then given a Program is stopped and then given a
Warm start; Only non-retentive are Cold start; All variables are
initialized. initialized.
I/O AO/DO goes to Fail Safe Output Mode AO/DO goes to Fail Safe Output
setting. Mode setting.
Firmware Transferred firmware is cleared. Transferred firmware is cleared.
Upgrade
2 A warning message prompts the user that ControlEdge Builder will disconnect with
the controller during the reboot. Click Yes to continue.
3 In the pop-up message which prompts the user to check the reboot result after 30
seconds, click OK.
77
9 MAINTENANCE
9.3 Resetting to factory defaults

The ControlEdge 900 Controller can be reset to factory default settings. For redundant
controllers, if the primary controller has been reset, the secondary one will be reset
automatically.
The controller can be reset to factory settings in the following two ways:
• Reset Connected Controller Directly.
• Reset via SD Card.
Attention
Factory reset is only allowed in Stopped or Stop Locked operating mode.
9.3.1 Resetting a connected controller directly

1 Under Maintenance, click Reset to Factory Defaults > Reset Connected
Controller Directly.
2 A warning message prompts you that the controller will be reset to the default
factory settings and all configurations in the controller will be lost. During the reset,
the controller will be rebooted automatically and disconnected. Click OK to
continue.
3 A pop-up message prompts you to check the reset status after 180 seconds. Click
OK.
9.3.2 Resetting via SD card

1 Insert SD card into the computer in which ControlEdge Builder is installed.
2 Under Maintenance, click Reset to Factory Defaults > Reset via SD Card.
3 Type in the Serial Number of the target controller in the pop-up window, and click
Save. The serial number can be found on the label of the controller. Or click
Platform under View Diagnostic to find the Platform.SerialNumber.
4 In the pop-up window, select the root directory of SD card to save the resetfile.rst
file.
Attention
Do not rename the factory reset file.
5 Insert the SD card into the controller, and reboot the controller. The controller will
scan the factory reset file and will be reset to factory defaults automatically.
10 Diagnostics
User can view diagnostics of Platform, Redundancy, Modbus Slave and Modbus Master
from ControlEdge Builder. The System Event Log and the Dump File can also be
uploaded from the controller.
Related topics
“Viewing system diagnostics” on page 80
“Viewing I/O diagnostics” on page 81
“Uploading and Viewing System Event Log” on page 84
“Uploading Dump File” on page 85
“Capturing project diagnostic information” on page 86
79
10 DIAGNOSTICS
10.1 Viewing system diagnostics

Connect to the controller, and perform the following steps to view basic diagnostics
information.
1 Click View System Diagnostics under Diagnostics. The diagnostics window
appears.
2 Click Refresh to update the information. The Platform, Redundancy, Modbus Slave
and Modbus Master information will be retrieved from the controller and displayed.
You can also use the Refresh Automatically option by setting a refresh rate.
3 Right-click System and there are five options can be selected. See the following
table for the description of these options.
Name Description
Reset Statistics Reset the statistic values of Modbus Master and Modbus Slave
to the default values.
Disable Synchronization (Only for redundancy) Disable synchronization between the
primary controller and the secondary controller.
Enable Synchronization (Only for redundancy) Enable synchronization between the
primary controller and the secondary controller.
Switchover (Only for redundancy) Exchange the roles of the primary and
secondary controllers. After that, ControlEdge Builder and the
controller will be disconnected.
Become Primary (Only for redundancy) When the primary controller is
disconnected, first connect the secondary controller and click
this option to set it to be the primary one.
10 DIAGNOSTICS
10.2 Viewing I/O diagnostics

See “Appendix A error code reference” on page 87 for more information about error
codes.
1 From the Home Page, click View I/O Diagnostics under Diagnostics. The I/O
Diagnostics page appears.
2 Click the down arrow on the right of the I/O tab to expand the rack list. The
overview of the racks which are running in the controller appears on the right panel.
See the following table for the configuration parameters:
Rack Address The system gets the assigned Rack Address number from the
I/O configuration in the running controller and populates these
addresses in Rack Overview table.
Rack Type Based on the Rack Address, the system detects physically
installed racks with specific addresses and populates them along
with their respective types and working status in the Rack
overview table.
Status Status of rack:
• OK: All the modules installed on the rack are running
without error.
• Error: Error exists in one or more of the modules
installed on the rack.
• Offline: A configured Rack address is not detected, it
may be caused by a communication error between controller
and EPM, or the EPM with related address is not physically
existed.
Click Refresh to update the rack information, or you can select the Refresh
Automatically Every checkbox and set a refresh rate.
3 Click a rack name in the rack list panel to view the module list for that rack. All the
slots of the rack are listed with or without module type according to the configuration
and the rack type detected.
The naming format used is:
• Slot XX - Module Type: the slot is assigned to an IOM.
• Slot XX - Empty: the slot is not assigned to an IOM.
On the rightmost page, the detailed information of the rack appears including the
following parameters.
81
10 DIAGNOSTICS
Module Number Module number of CPM or EPM
Tip
If the I/O module is mounted in a local I/O rack, the
information of CPM is displayed.
If the I/O module is mounted in an expansion I/O rack,
the information of EPM is displayed.
Hardware Version Hardware version of CPM or EPM

Firmware Version Firmware version of CPM or EPM
Status Status of CPM or EPM:
• OK
• Error
Holding the mouse cursor over the shown error code, the
description of the error appears.
• Offline
Power Supply Power supply status:
• OK
• Error
Slot Number Slot number mounted in the rack, ranging from 1 to 12.
Module type The type of I/O module
Status Status of I/O module:
• OK: No Module level error exits and all the channels of
the module are running without error.
• Error: Module level error exists, or a module channel is
with an error.
• Offline: Configured module is not detected.
4 Click a module in the Module List to view its diagnostic information.

See the following table for the detailed diagnostic information.
Module Number Module number of I/O module
Hardware Version Hardware version of I/O module
Firmware Version Firmware version of I/O module
10 DIAGNOSTICS
Status Status of I/O module:
• OK: No Module level error exits and all the channels of the
module are running without error.
• Error: Module level error exists, or a module channel is with
an error.
Tip
Hold the mouse cursor over the shown error code of
a faulty I/O module to see a description of the error.
• Offline: Configured module is not detected.
Channel Defined channel of the assigned module type
Status Status of channel:
• OK
• Error
Tip
Hold the mouse cursor over the shown error code of
a faulty channel to see a description of the error.
The channel status will not be displayed if the type of the

physically installed module does not match the configured one.
Description Description of the channel
83
10 DIAGNOSTICS
10.3 Uploading and Viewing System Event Log

The controller logs operational and diagnostic events in the System Event Log. Follow
these procedures to upload and then view the events.
Related topics
“Uploading System Event Log” on page 84
“Viewing System Event Log” on page 84
10.3.1 Uploading System Event Log

1 Click View System Event Log > Upload System Event Log under Diagnostics.
The current system event log destination path and filename is displayed under
Upload System Event Log.
2 Click browse button under Upload System Event Log to change the destination
filename.
3 Click Upload button to retrieve the system event log from the controller and store it
to the destination file. The system event log is now ready for viewing. See “Viewing
System Event Log” on page 84 for instructions.
10.3.2 Viewing System Event Log

To view system events, you must upload the system event log from the controller to a
file on the computer first. See “Uploading System Event Log” on page 84 for
instructions.
To view the system events

1 Click View System Event Log > View System Event Log under Diagnostics.
2 Click View to select the relevant file you have uploaded, click Open. The system
events contained in the file will be displayed.
3 You can filter the events by selecting from the various filters for the Application,
Category, From and To fields. Then click Apply.
10 DIAGNOSTICS
10.4 Uploading Dump File

The controller dump file contains additional information for Honeywell technical
support. It does not contain any user actionable information. If Honeywell technical
support requests the controller dump file, follow these procedures to upload the file
before sending it to Honeywell.
Attention
For the controller to generate a dump file, an SD card must be installed in the controller
before an incident occurs. Without an SD card, a dump file cannot be generated. After
uploading a dump file, if the file appears to be empty, then an SD card may not have been
inserted in the controller at the time of the incident or the SD card may be full.
1 Click View System Event Log > Upload System Event Log under Diagnostics.
The current dump file destination path and filename is displayed under Unload
Dump File.
2 Click browse button under Unload Dump File to change the destination path and
filename.
3 Click Upload button to retrieve the dump file from the controller and store it to the
destination file. The dump file is now ready for sending to Honeywell technical
support.
85
10 DIAGNOSTICS
10.5 Capturing project diagnostic information

A diagnostic capture enables you to save the log files for the project, and send it back to
Honeywell technical support if ControlEdge Builder has an exception.
1 From Home Page, select Save Diagnostic Capture under Diagnostics. The Save
Diagnostic Capture dialog box appears.
2 Click the browser icon to select a directory and enter a file name. Click Save.
3 Click Save.
11 Appendix A error code reference
See the following tables for the error codes in ControlEdge Builder:
System error code
Error Description Cause Action

Code
0 SUCCESS Success N/A
1 FAILURE Operation failure. Generic failure Upload System Event Logs
for debugging.
4 INVALID_OBJ_ Invalid Object Id Upload System Event Logs
ID for debugging.
12 INVALID_VAL Value not acceptable for other Upload System Event Logs
UE reason (too large/too small/invalid for debugging.
eng. units code)
14 INVALID_SIZE Size not valid (may be too big/too Upload System Event Logs
small) for debugging.
27 INSUFFICIENT Insufficient device resources e.g. Upload System Event Logs
_DEVICE_RES queue full, buffers/memory for debugging.
OURCES unavailable
40 INVALID_DAT Invalid data received from the Send the controller error log
A builder. and builder log to
Honeywell.
129 TIMEOUT Usually the connection between the Check the status of the
controller and the builder is broken. controller.
501 INVALID_APP_ Application ID in the request is Upload System Event Logs
ID invalid. for debugging.
502 INVALID_ATT Attribute ID in the request is Upload System Event Logs
R_ID invalid. for debugging.
87
11 APPENDIX A ERROR CODE REFERENCE

Code
503 INVALID_ATT Attribute index in the request is Upload System Event Logs
R_IDX invalid. for debugging.
504 INVALID_FC Function code in the request is Upload System Event Logs
invalid. for debugging.
505 READ_ONLY Attribute write request failed Upload System Event Logs
because attribute is read-only. for debugging.
506 INAPPROPRIA Request cannot be executed in the Wait for current operation to
TE_PROCESS_ current state. For example: complete or cancel current
MODE operation (if possible and
Controller load request fails
appropriate) and retry.
because the controller is either in
the process of upgrade, reboot or
shutdown.
Controller reboot request fails
because a reboot is already in
progress.
Controller upgrade request fails
because the controller startup is not
completed, or it is in the process of
reboot, load, upgrade or shutdown.
507 UNSUPPORTE N/A N/A
D
508 INVALID_FILE File ID specified in the request is Upload System Event Logs
_ID invalid for debugging.
509 INVALID_CON Config file is corrupted or not Upload System Event Logs
FIG_ENTITY compatible with existing release. for debugging.
510 CONFIGFILE_ Config file does not exist. Upload System Event Logs
NOTEXIST Controller database might be for debugging.
corrupted.
511 UPLOADDATA Archiving backup files is having Try multiple times. If it is
_NOTEXIST issue due to memory limitations. still not working, upload
System Event Logs for
debugging.
513 IP_ADDRESS_ Requested static IP address cannot Assign a different static IP
NOT_AVAILAB be assigned to the interface because address or remove the node
LE another node with the same IP with the same IP address
address already exists on the from the network and retry.
network.

Code
514 INVALID_AUT The user doesn’t have Builder pops up an error
HORIZATION_I corresponding authorization to message.
D perform the operations. For
example, the operator does not have
the privilege to change password
for other users, administrators or
engineers.
515 INVALID_DAT Data type in the request is invalid. Upload System Event Logs
A_TYPE for debugging.
518 SESSION_EXPI No communication between the Reconnect to the controller.
RED controller and the builder for over
ten minutes.
EPM diagnostics
The system provides 4 BYTE long variable (32 bit) to indicate the working state of the
module. Each bit represents one state, "1" means the state defined is active. Multiple
states can be detected at the same time.
Bit State Cause Action

0 Offline EPM is not installed or the Check if EPM have been installed or
communication between communication line have been
controller and EPM is error. connected.
UIO diagnostics
The system provides 4 BYTE long variable (32 bit) to indicate the working state of the
module. Each bit represents one state, "1" means the state defined is active. Multiple
states can be detected at the same time.

0 Offline Communication error or Check the physical installation and the
module doesn't physically configuration.
exist or module is not powered
on.
1 IOM Type Configured IOM is different Check the installed IOM on the rack
Mismatch from the one physically and the configuration. Then replace the
installed. IO module if the type of the installed
module is not expected or Change the
IO Module type in the configuration if
the configured type is not correct.
89

2 Hardware Internal hardware error. Power recycle the field power for the
Error affected module. Replace module
hardware if error persists.
3 Factory Module does not contain the Replace IO module hardware.
DataErr correct factory data or factory
data is corrupted.
6 WDTErr Module encountered a Restart the IO module by powering it
watchdog reset. off and powering back ON. Replace IO
module if error persists.
7 ExternalPow The external 24V supply is not Check the 24V connections, check the
erErr connected/has lost power/has 24V external power supply and ensure
an overvoltage. that it is powered on and connected.
Check if the 24 V power supply does
not have an undervoltage/overvoltage.
8 InternalPowe Bad power supply module on Check that the power supply and UIO
rErr the rack or hardware failure on modules are correctly inserted in the
the UIO. rack and the mounting screws are tight.
Replace rack power supply if the power
supply error is still seen on this module
or other modules. Replace UIO
hardware if error persists.
9 Over The UIO module detected that Check if there is sufficient ventilation
temperature the board temperature is between the racks. Check if the current
higher than the threshold. drawn from the UIO module to the DO
and AO channels do not exceed the
specification limits of 4.2 A. If the error
persists, replace module hardware.
11 Not factory Module is not factory Replace IO module hardware.
calibrated calibrated or calibration data
corrupted.
Channel diagnostic
Error State Cause Action

Code
0 Good N/A N/A
1 Bad Channel The module is offline, or; Check the module status
The module is with errors.
11 OverRangeHigh When input value is larger than (EU Check the input signal
Extended High) + (EU High - EU Low)*10%
Error State Cause Action

Code
12 OverRangeHigh When input value is in the range Check the input signal
from EU High to (EU High) + (EU
High - EU Low)*10%
13 OverRangeLow When input value is in the range Check the input signal
from (EU Low) - (EU High - EU
Low)*10% to EU Low
14 OverRangeLow When iInput value is smaller than Check the input signal
Extended (EU Low) - (EU High - EU
Low)*10%
15 NoCalibration No AI/AO calibration data found in Calibrate the module
IOM
16 OpenWired1 Field cable broken or not connected Check field cable
to the terminals of the module connections and ensure that
the sensor or actuator is
connected to the IO module.
In case of DI, the correct
values of external resistors
have to be used to detect
open wire
18 ShortCircuit2 Field cable has a short circuit Check field cable for short
circuit and ensure that the
sensor or actuator is
connected to the IO module.
In case of DI, the correct
values of external resistors
have to be used to detect
short circuit. In case of DO,
the short circuit protection
prevents the output to be
driven.
19 IO HardwareErr Internal hardware error Power recycle the field
power for the affected
module or Replace module
hardware if error persists
20 Read Back Test Analog/Digital output channel is Check field cable
Fail unable to drive the desired output connections and ensure that
current on the terminals. This could the actuator is connected to
happen due to high load resistance the IO module
or a broken wire.
Note 1: Open wire detection is applicable for AI, DI and DO.
Note 2: Short circuit detection is applicable for DI and DO.
91
12 Appendix B Modbus Master Configuration
Related topics
“Modbus TCP Master” on page 94
“Description of Modbus Function Block” on page 98
“Modbus Protocol Error Codes” on page 126
“Endian Mode” on page 128
93
12 APPENDIX B MODBUS MASTER CONFIGURATION
12.1 Modbus TCP Master
Related topics
“Configuring Modbus TCP Master” on page 94
“Programming Modbus TCP Master” on page 94
12.1.1 Configuring Modbus TCP Master

Modbus TCP Master is used for communication between the controller and third-party
Modbus slave devices over Ethernet.
Prerequisites
A new project is created and an controller is added to the project opened in ControlEdge
Builder. See “Creating a project” on page 13 and “Connecting a Controller” on page 16
for more details.
To set a controller as the Modbus TCP Master

1 From the Home Page, click Configure Ethernet Ports and select ETH1 or ETH2 to
configure.
2 Under Network Setting, select Use the following IP address to type in the details in
IP Address, Subnet Mask and Gateway manually.
3 Under Protocol Binding, select Modbus TCP Master to bind Modbus TCP Master
to the Ethernet port.
4 Click Save to save the configuration, or click Back to return to the Home Page.
5 Click Connect from the Home Page to connect a controller. For the user name and
password, see “User Privileges” on page 63.
6 Click Download from the Home Page to load the configuration of Modbus TCP
Master to the controller.
12.1.2 Programming Modbus TCP Master

After downloading the configuration, you need to program Modbus TCP Master for the
project in IEC Programming Workspace.
To program the Modbus TCP Master

1 Right-click Logical POUs and select Insert > Program. Then type in the name, and
click OK. For the following steps, FBD language is taken as an example.
2 Add a Taskas follows:

a Under Physical Hardware, right-click Task and select Insert > Task.
b In the pop-up window, type in the name. Select the task type as CYCLIC, and
click OK.
c In the pop-up window of Task settings, configure the corresponding parameters.
d Click OK.
3 Right-click the task you have inserted and select Insert > Program instance.
4 In the pop-up window, type in the name in Program instance and select
corresponding Program type. Click OK.
5 Right-click Libraries and select Insert > Firmware Library, select
MODBUS.FWL. Then click Include.
6 Right-click Data Types and select Insert > Datatypes. In the pop-up window, type
in the name in Name and click OK.
7 Double-click the data type you have inserted and define an array in worksheet shown
as below, then click Save button from the toolbar. Click Make.
Figure 3: Modbus Data Array

8 Under Logical POUs, double-click of the program that you have inserted, in the
workplace, drag the target function or function block of modbus from the Edit
Wizard pane; the function or function block is displayed. There are twelve function
blocks available for Modbus master programming. For more details, see “Description
of Modbus Function Block” on page 98. For the following steps, the function block
MB_RD_MHR is taken as an example.
9 Double-click the pin-outs of the function or function block to assign variables. In the
pop-up Variable Properties window, select the Name, Data Type and Usage from
the drop-down list, and assign Initial value and I/O address. Then click OK.
95
Tip
To assign initial values to CONFIG_INFO:
CONFIG_INFO, a predefined data structure for Modbus configuration information, is
the crucial input for Modbus master function blocks and contains key Modbus
communication parameters such as IP address of slave, slave ID, port number of the
controller to be used, etc. This data structure is read-only and cannot be viewed and
edited in ControlEdge Builder. See “Description of CONFIG_INFO” on page 123 for
more details. Slave1 is the variable name assigned by the user of CONFIG_INFO.
Figure 4: CONFIG_INFO for Modbus TCP Master
10 Assign the data returned by the function block to variables to monitor.
Figure 5: Output Data
Tip
DATA1 is the variable name assigned by the user of OUTPUT pin of MB_RD_MHR
and it is an array.
After the basic programming steps as described, the workplace will appear as shown
below.
Figure 6: Programming Completion

11 Click Make from the toolbar to compile the programs.
12 Click Download from the toolbar to download the compiled programs of Modbus
TCP Master to the controller.
97
12.2 Description of Modbus Function Block

With these function blocks, you can read and write single coil, multiple coils, single
discrete input, multiple discrete inputs, single input register, multiple input registers,
single holding register, etc., as per Modbus protocol.
Related topics
“Read Single Coil” on page 99
“Read Multiple Coils” on page 101
“Read Single Discrete Input” on page 103
“Read Multiple Discrete Inputs” on page 105
“Read Single Input Register” on page 107
“Read Multiple Input Registers” on page 109
“Read Single Holding Register” on page 111
“Read Multiple Holding Registers” on page 113
“Write Single Coil” on page 116
“Write Single Holding Register” on page 117
“Write Multiple Coils” on page 119
“Write Multiple Holding Registers” on page 121
“Description of CONFIG_INFO” on page 123
“Description of Input and Output Data Type” on page 125
12.2.1 Read Single Coil
Figure 7: MB_RD_C
Description
It is used to read a single coil.
Input
Table 13: MB_RD_C Input Parameter
Parameter Data type Description

ENABLE BOOL Enable: If TRUE, the FB is enabled and workable.
CONFIG_INFO User defined data This is a structure provided by Honeywell. Modbus
type related information is included. For more details, see
“Description of CONFIG_INFO” on page 123.
START_ADDR UINT The first Modbus register address to read. Function
code is not included in the address.
SEND_FLAG BOOL If SEND_FLAG is true and RDY_FLAG is true,
function blocks will send the request. RDY_FLAG
is TRUE means last communication is finished.
Before the last communication is finished, even if
the SEND_FLAG is true, the request won’t be sent.
99
Output
Table 14: MB_RD_C Output Parameter

RDY_FLAG BOOL True: last communication is finished. FB is ready for
the next communication.
False: command request is being sent or received.
OUTPUT BOOL Output: 1: true, 0: OFF
DONE BOOL Indicates that the response is received from slave
device.
ERR_FLG BOOL Will be set to TRUE if there is either a general error
or a protocol error.
PROTOCOL_ER USINT Error numbers defined by Modbus protocol. See
R “Modbus Protocol Error Codes” on page 126 for
details.
GEN_ERR USINT General error code:
0: Communication succeeded.
1: The input parameter is invalid.
2: Response timeout
3: Controller internal time out (IPC timeout).
4: Invalid request
12.2.2 Read Multiple Coils
Figure 8: MB_RD_MC
Description
It is used to read multiple coils.
Input
Table 15: MB_RD_MC Input Parameter

LENGTH UINT The number of registers to read.
101

is TRUE means the last communication finished.
SEND_FLAG is true, the request won’t be sent.
Output
Table 16: MB_RD_MC Output Parameter

OUTPUT Array of BOOL User defined data type: array of bool. The size of the
array should be equal to the number of the registers
to read. Define a data type as shown below:
TYPE
Variable Name:
array[1..LENGTH] of BOOL;
END_TYPE
DONE BOOL Indicates that the response is received from a slave

device.
details.
2: Response timeout
4: Invalid request
12.2.3 Read Single Discrete Input
Figure 9: MB_RD_DI
Description
It is used to read single discrete input.
Input
Table 17: MB_RD_DI Input Parameter

is TRUE means last communication is finished.
Before last communication is finished, even if
SEND_FLAG is true the request won’t be sent.
103
Output
Table 18: MB_RD_DI Output Parameter

OUTPUT Array of BOOL User defined data type: array of BOOL. The size of
the array should be equal to the number of the
registers to read.
OUTPUT BOOL Output: 1: true, 0: OFF
device.
details.
2: Response timeout
4: Invalid request
12.2.4 Read Multiple Discrete Inputs
Figure 10: MB_RD_MDI
Description
It is used to read multiple discrete inputs.
Input
Table 19: MB_RD_MDI Input Parameter

105

is TRUE means the last communication is finished.
Output
Table 20: MB_RD_MDI Output Parameter

OUTPUT Array of BOOL User defined data type: array of bool. The size of the
to read. Define a data type as shown here:
TYPE
Variable Name:
END_TYPE

device.
details.
2: Response timeout
4: Invalid request
12.2.5 Read Single Input Register
Figure 11: MB_RD_IR
Description
It is used to read single input register.
Input
Table 21: MB_RD_IR Input Parameter

START_ADDR UINT The Modbus register address to read. Function code
is not included in the address.
function blocks would send the request.
RDY_FLAG is TRUE means the last
communication is finished. Before last
communication is finished, even if SEND_FLAG is
true, the request won’t be sent.
107
Output
Table 22: MB_RD_IR Output Parameter

OUTPUT BOOL 16bit Data read from the START_ADDR
device.
details.
2: Response timeout
3: Controller internal time out(IPC timeout).
4: Invalid request
12.2.6 Read Multiple Input Registers
Figure 12: MB_RD_MIR
Description
It is used to read multiple input registers.
Input
Table 23: MB_RD_MIR Input Parameter

109

communication is finished. Before the last
communication is finished, even if the
Output
Table 24: MB_RD_MIR Output Parameter

OUTPUT INT, UINT, DINT, User defined data type. The size of the array should
UDINT, LINT, be equal to the number of the registers to read. The
REAL or LREAL; end user should define a data type as shown here:
TYPE
Variable Name:
array[1..LENGTH] of INT, UINT, DINT,
UDINT, LINT, REAL or LREAL;
END_TYPE
The end user can read the data of a specific register

by using the suffix.
ENDIAN_MODE USINT Endian mode is required for reading/writing 32bit
and 64 bit variables. As Modbus always use big
Endian to transceive data, there is no need to set the
Endian mode for 16-bit data.
1: little Endian mode for 32 bit data
2: byte-swapped little Endian mode for 32 bit data
3: big Endian mode for 32 bit data
4: byte-swapped big Endian mode for 32 bit data
Please see “Endian Mode” on page 128 for details.

device.
details.
2: Response timeout
4: Invalid request
12.2.7 Read Single Holding Register
Figure 13: MB_RD_HR
Description
It is used to read a single holding register.
111
Input
Table 25: MB_RD_HR Input Parameter

SEND_FLAG is true the request won’t be sent.
Output
Table 26: MB_RD_HR Output Parameter

OUTPUT BOOL 16 bit data read from the START_ADDR
device.
ERR_FLG BOOL Will be set true if there is either a general error or a
protocol error.
details.

2: Response timeout
4: Invalid request
12.2.8 Read Multiple Holding Registers
Figure 14: MB_RD_MHR
Description
It is used to read multiple holding registers.
Input
Table 27: MB_RD_MHR Input Parameter

113

Output
Table 28: MB_RD_MHR Output Parameter

OUTPUT Array of INT, UINT, User defined data type. The size of the array should
DINT, UDINT, be equal to the number of the registers to read. The
LINT, REAL or end user should define a data type as shown here:
LREAL;
TYPE
Variable Name:
array[1..LENGTH] of INT/UINT/DINT/
UDINT/LINT/REAL/LREAL;
END_TYPE
The end user can read the data of a specific register

by using the suffix.

device.
details.
2: Response timeout
4: Invalid request
115
12.2.9 Write Single Coil
Figure 15: MB_WR_C
Description
It is used to write a single coil.
Input
Table 29: MB_WR_C Input Parameter

INPUT BOOL Input data: 1: ON, 0: OFF
Output
Table 30: MB_WR_C Output Parameter

device.
details.
2: Response timeout
4: Invalid request
12.2.10 Write Single Holding Register
Figure 16: MB_WR_HR
117
Description
It is used to write single holding register.
Input
Table 31: MB_WR_HR Input Parameter

function blocks would send the request. RDY_FLAG
is TRUE means the last communication is finished.
the SEND_FLAG is true, the request won’t be sent.
INPUT UINT 16 bit input data of START_ADDR register
Output
Table 32: MB_WR_HR Output Parameter

device.
details.

2: Response timeout
4: Invalid request
12.2.11 Write Multiple Coils
Figure 17: MB_WR_MC
Description
It is used to write multiple coils.
Input
Table 33: MB_WR_MC Input Parameter

119

LENGTH UINT The number of registers to write.
SEND_FLAG BOOL If SEND_FLAG is TRUE and RDY_FLAG is true,
INPUT Array of BOOL User defined data type: array of bool. The size of the
to read. The end user should define a data type as
shown here:
TYPE
Variable Name:
END_TYPE
Use the suffix to set the status of a specific register.
Output
Table 34: MB_WR_MC Output Parameter

device.
details.

2: Response timeout
4: Invalid request
12.2.12 Write Multiple Holding Registers
Figure 18: MB_WR_MHR
Description
It is used to write multiple holding registers.
Input
Table 35: MB_WR_MHR Input Parameter

121

LENGTH UINT The number of registers to write.
INPUT Array of INT, UINT, User defined data type. The size of the array
DINT, UDINT, depends on the number of the registers to write:
LINT, REAL, or
Size of (array) * size of (element of array) / size of
LREAL
(UINT) = LENGTH.
The end user should define a data type as shown
here:
TYPE
Variable Name:
array[1..LENGTH] of INT, UINT, DINT,
UDINT, LINT, REAL or LREAL;
END_TYPE
Use the suffix to read the data of a specific register.
Output
Table 36: MB_WR_MHR Output Parameter


device.
details.
2: Response timeout
4: Invalid request
12.2.13 Description of CONFIG_INFO

The CONFIG_INFO pin defined in the function blocks is to input all the configuration
information for the Modbus master.
123
There are two types of communication between Modbus master and Modbus slave:
serial communication using RS232 or RS485, and Ethernet communication. Accordingly
two types of data structures are defined for CONFIG_INFO.
• For serial communication, the data structure is defined as:
TYPE
MB_CONFIG_INFO_COM:
STRUCT
MB_SLAVE_ID: USINT;
PORT_NUM: USINT;
RETRIES: USINT;
TIMEOUT: UDINT;
END_STRUCT;
END_TYPE
• For Ethernet communication, the data structure is defined as:
TYPE
MB_CONFIG_INFO_ETH:
STRUCT
MB_SLAVE_ID: USINT;
PORT_NUM: USINT;
RETRIES: USINT;
TIMEOUT: UDINT;
TCP_PORT_NUM: UINT;
IP_ADDR: STRING;
END_STRUCT;
END_TYPE
Attention
You are not permitted to make any change to the data structure as the configuration would
be parsed incorrectly.
See the following table for the parameter descriptions.
Table 37: CONFIG_INFO Parameter

MB_SLAVE_ID USINT Modbus slave ID: valid arrange: 1~247.

PORT_NUM USINT • The physical interface of serial port:
1. RS232 port 1
2. RS232 port 2
3. RS485 port 1
4. RS485 port 2
5. reserved
6. reserved
• The physical interface of Ethernet port:
1. Ethernet port 1
2. Ethernet port 2
3. reserved
4. reserved
RETRIES USINT Retry times before it is failed.
TIMEOUT UDINT Timeout unit: millisecond.
The minimal timeout is 500ms. If the end-user
gives a number less than 500, the FB would
send the default timeout value instead.
12.2.14 Description of Input and Output Data Type

Modbus supports reading and writing multiple consecutive registers. In these cases, the
input or output is defined as an array.
• For reading and writing coils and discrete inputs, array of BOOL is defined.
Set or retrieve the data value by using the suffix. For example: there are 10 coils to
read, the output array COIL_OUT can be defined as array [1...10] of BOOL, reading
the status of the fifth register could be COIL_OUT [5].
• For reading and writing input registers and holding registers, multiple array types can
be defined: INT, UINT, DINT, UDINT, REAL, LREAL or LINT.
Set or retrieve the data value by using the suffix. For example: there are 3 LREAL
variables , or in other words, 12 holding registers to read, the output array
LREAL_OUT can be defined as array[1..3] of LREAL, reading the value of the
second register could be LREAL_OUT[2]. In this case, the Endian mode is involved.
Tip
Reading or writing a single DINT/UDINT/LINT/REAL/LREAL type data: You need not
define an “array[1..1] of xxx ”; you can simply assign a DINT, UDINT, LINT, REAL or
LREAL type variable to the INPUT/OUTPUT pin of the function block.
125
12.3 Modbus Protocol Error Codes

Refer to the following table for Modbus Protocol Error Codes:
Table 38: Modbus Protocol Error Codes
Error Item Description

Code
0 success N/A
69 Connection broken Signals that the TCP/IP connection is closed by the remote peer
or broken.
129 checksum error N/A
130 invalid frame error Signals that a received frame does not correspond either by
structure or content to the specification or does not match a
previously sent query frame. A poor data link typically causes
this error.
131 Invalid reply error Signals that a received reply does not correspond to the
specification
132 reply timeout error Signals that a fieldbus data transfer timed out. This can occur if
the slave device does not reply in time or does not reply at all.
A wrong unit address will also cause this error. On some
occasions, this exception is also produced if the characters
received don't constitute a complete frame.
133 send timeout error Signals that a fieldbus data send timed out. This can only occur
if the handshake lines are not properly set.
161 illegal function Signals that an illegal Function exception response was
response received. This exception response is sent by a slave device
instead of a normal response message if a master sent a Modbus
function not supported by the slave device.
162 illegal address Signals that an illegal Data Address exception response was
response received. This exception response is sent by a slave device
instead of a normal response message if a master queried an
invalid or non-existing data address.
163 illegal value Signals that an illegal Value exception response was received.
response This exception response is sent by a slave device instead of a
normal response message if a master sent a data value that is not
an allowed value for the slave device.
Error Item Description

Code
164 failure response Signals that a Slave Device Failure exception response (code
04) was received. This exception response is sent by a slave
device instead of a normal response message if an
unrecoverable error occurred while processing the requested
action. This response is also sent if the request would generate a
response whose size exceeds the allowable data size.
127
12.4 Endian Mode

Modbus protocol supports 16bit data only. If there are 32bit or 64bit variables, 2 or 4
consecutive registers should be used to read the data value. In these cases, the Endian
mode may be involved due to the different Endian modes in Modbus slave devices.
See the following table for the concept of Endian modes used in Modbus function
blocks:
Table 39: Modbus Function Block Endian Mode
Endian mode Description

Little endian Lower registers contain lower bits and higher registers contain higher bits. The
order is on a register basis. Inside each register, the more significant byte is
always at the first place as defined by the Modbus protocol.
Big endian Lower registers contain higher bits and higher registers contain lower bits. The
order is on a register basis. Inside each register, the more significant byte is
always at the first place as defined by the Modbus protocol.
Byte-swapped The two bytes inside each register would be swapped.
See the following table for the valid Endian modes:
Table 40: Modbus Function Block Valid Endian Mode
Valid Endian Description

mode
1 little Endian mode for 32 bit data
2 byte-swapped little Endian mode for 32 bit data
3 big Endian mode for 32 bit data
4 byte-swapped big Endian mode for 32 bit data
5 little Endian mode for 64 bit data
6 byte-swapped little Endian mode for 64 bit data
7 big Endian mode for 64 bit data
8 byte-swapped big Endian mode for 64 bit data
13 Notices
Trademarks
Experion® is a registered trademark of Honeywell International, Inc.
ControlEdge™ is a trademark of Honeywell International, Inc.
Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.
Trademarks that appear in this document are used only to the benefit of the trademark
owner, with no intention of trademark infringement.
Third-party licenses
This product may contain or be derived from materials, including software, of third
parties. The third party materials may be subject to licenses, notices, restrictions and
obligations imposed by the licensor. The licenses, notices, restrictions and obligations, if
any, may be found in the materials accompanying the product, in the documents or files
accompanying such third party materials, in a file named third_party_licenses on the
media containing the product, or at http://www.honeywell.com/ps/thirdpartylicenses.
Documentation feedback
You can find the most up-to-date documents on the Honeywell Process Solutions
support website at:
http://www.honeywellprocess.com/support
If you have comments about Honeywell Process Solutions documentation, send your
feedback to:
hpsdocs@honeywell.com
129
13 NOTICES
Use this email address to provide feedback, or to report errors and omissions in the
documentation. For immediate help with a technical problem, contact your local
Honeywell Technical Assistance Center (TAC).
How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software defect or
weakness that can be exploited to reduce the operational or security capabilities of the
software.
Honeywell investigates all reports of security vulnerabilities affecting Honeywell
products and services.
To report a potential security vulnerability against any Honeywell product, please follow
the instructions at:
https://honeywell.com/pages/vulnerabilityreporting.aspx
Submit the requested information to Honeywell using one of the following methods:
• Send an email to security@honeywell.com.
or
• Contact your local Honeywell Technical Assistance Center (TAC) listed in the
“Support” section of this document.
Support
For support, contact your local Honeywell Process Solutions Customer Contact Center
(CCC). To find your local CCC visit the website, https://
www.honeywellprocess.com/en-US/contact-us/customer-support-contacts/Pages/
default.aspx.
Training classes
Honeywell holds technical training classes that are taught by process control systems
experts. For more information about these classes, contact your Honeywell
representative, or see http://www.automationcollege.com.

Control Edge

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Control Edge

Uploaded by

Copyright:

Available Formats

ControlEdge

Builder User's Guide

1 About this guide ....................................................................................................................... 7

5 Programming with IEC 61131-3 ............................................................................................. 51

12.2.6 Read Multiple Input Registers ....................................................................................... 109

Revision Date Description

Document name Document number

2.1 Before you start

If you want to... Then, see this topic...

If you want to... Then, see this topic...

2.2 Launching ControlEdge Builder

Figure 1: Start Page

2.3 Working with projects

2.3.1 Creating a project

To create a new project

Figure 2: Home Page

Icon Name Description

2.3.2 Opening an existing project

2.4 Connecting a Controller

2.5 Configuring controller redundancy

2.6 Selecting operating modes

Table 1: Privilege of operating modes

Mode Switch position

Mode Switch position

To change the operating mode

3.1 Configuring Ethernet Ports

3.1.1 Configuring ETH1 and ETH2

Configuring Ethernet ports for the non-redundancy

Table 2: Protocol Supported by ETH1 and ETH2

4 Click Save to complete the Ethernet port configuration.

Configuring Ethernet ports for the redundancy

3.1.2 Configuring ETH3 and ETH4

Configuring Ethernet ports for the non-redundancy

3 Select Ring Topology or Star Topology under I/O Network Topology.

Configuring Ethernet ports for the redundancy

3 Select Ring Topology or Star Topology under I/O Network Topology.

5 Click Back to return to the Home Page.

3.2 Configuring Protocols

3.2.1 Configuring a Modbus Slave

3.2.2 Configuring an OPC UA client

To configure an OPC UA client

Table 3: OPC UA Client parameter description

3.2.3 Configuring an OPC UA server

To configure an OPC UA server

Table 4: OPC UA Server parameter description

Max Subscription The maximum number of subscriptions that can be created.

3.3 Configuring SCADA Mapping

3.3.1 Adding a Modbus Slave mapping table

a Modify the Modbus Address if required.

3.3.2 Renaming a mapping table

3.3.3 Deleting a mapping table

3.3.4 Exporting a mapping table

To export mapping addresses to a .csv file:

3.3.5 Importing a mapping table

To import mapping addresses:

4.1 Managing an I/O module

Adding an I/O module

4 Click OK to complete the configuration.

Removing an I/O module

Editing an I/O module

4.2 Configuring UIO

Configuring Analog Input channels

Table 5: Analog Input channel parameter