MC-IoT

System Tools Suite User

Guide
System Release 35.0

MARCH 2024 *6802979C10*

© 2024 Motorola Solutions, Inc. All Rights Reserved. 6802979C10-BA
6802979C10-BA
Intellectual Property and Regulatory Notices

Intellectual Property and Regulatory

Notices
Copyrights
The Motorola Solutions products described in this document may include copyrighted Motorola Solutions
computer programs. Laws in the United States and other countries preserve for Motorola Solutions
certain exclusive rights for copyrighted computer programs. Accordingly, any copyrighted Motorola Solutions
computer programs contained in the Motorola Solutions products described in this document may not be
copied or reproduced in any manner without the express written permission of Motorola Solutions.
No part of this document may be reproduced, transmitted, stored in a retrieval system, or translated into
any language or computer language, in any form or by any means, without the prior written permission of
Motorola Solutions, Inc.

Trademarks
MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered
trademarks of Motorola Trademark Holdings, LLC and are used under license. All other trademarks are the
property of their respective owners.

License Rights
The purchase of Motorola Solutions products shall not be deemed to grant either directly or by implication,
estoppel or otherwise, any license under the copyrights, patents or patent applications of Motorola Solutions,
except for the normal nonexclusive, royalty-free license to use that arises by operation of law in the sale of a
product.

Open Source Content

This product may contain Open Source software used under license. Refer to the product installation media
for full Open Source Legal Notices and Attribution content.

European Union (EU) and United Kingdom (UK) Waste of Electrical and Electronic
Equipment (WEEE) Directive

The European Union's WEEE directive and the UK's WEEE regulation require that products sold into
EU countries and the UK must have the crossed-out wheelie bin label on the product (or the package in some
cases). As defined by the WEEE directive, this crossed-out wheelie bin label means that customers and end
users in EU and UK countries should not dispose of electronic and electrical equipment or accessories in
household waste.
Customers or end users in EU and UK countries should contact their local equipment supplier representative
or service center for information about the waste collection system in their country.

Disclaimer
Please note that certain features, facilities, and capabilities described in this document may not be applicable
to or licensed for use on a specific system, or may be dependent upon the characteristics of a specific mobile
subscriber unit or configuration of certain parameters. Please refer to your Motorola Solutions contact for
further information.
© 2024 Motorola Solutions, Inc. All Rights Reserved

2
 6802979C10-BA
Contact Us

Contact Us
The Centralized Managed Support Operations (CMSO) is the primary contact for technical support included
in your organization's service agreement with Motorola Solutions. To enable faster response time to customer
issues, Motorola Solutions provides support from multiple countries around the world.
Service agreement customers should be sure to call the CMSO in all situations listed under Customer
Responsibilities in their agreement, such as:
● To confirm troubleshooting results and analysis before taking action
Your organization received support phone numbers and other contact information appropriate for your
geographic region and service agreement. Use that contact information for the most efficient response.
However, if needed, you can also find general support contact information on the Motorola Solutions website,
by following these steps:
1. Enter motorolasolutions.com in your browser.
2. Ensure that your organization's country or region is displayed on the page. Clicking or tapping the name
of the region provides a way to change it.
3. Select "Support" on the motorolasolutions.com page.

Comments
Send questions and comments regarding user documentation to documentation@motorolasolutions.com.
Provide the following information when reporting a documentation error:
● The document title and part number
● The page number or title of the section with the error
● A description of the error
Motorola Solutions offers various courses designed to assist in learning about the system. For information, go
to https://learning.motorolasolutions.com to view the current course offerings and technology paths.

3
6802979C10-BA
Document History

Document History
Version Description Date
6802979C10-AA Revised version of the MC-IoT STS User Guide manual. October 2019
6802979C10-AB Minor updates. December 2019
6802979C10-AC MC-IoT 4.5 updates. June 2020
6802979C10-AD Updates: September 2020
● IL-7710
○ Customizing the Site Configuration on page 109
○ Advanced Link Parameters for SI1 Port on page
408
○ LoRa Port Configurations on page 449
○ MC-EDGE LoRa on page 651
○ Enabling LoRaWAN on page 651
○ LoRaWAN Configuration on page 651
○ Configuring LoRaWAN Devices on page 651
○ Considerations for Sending and Receiving Device
Data on page 652
○ Adding Elements from the Inventory on page 311
○ RTU Add-On File Types on page 182
○ Encrypting MC-EDGE Add-On Files (Secured STS
Only) on page 185
● IL-8124
○ ACE1000/MC-EDGE Data Register Location
○ ACE1000 MODBUS Data Types

6802979C10-AE Updates: November 2020

● IL-8213
○ ACE1000/MC-EDGE SI1 Port Configurations on
page 399
○ SI1 Port Parameters on page 396
○ Port Protocols for ETH1/ETH2/ETH3 on page 436
○ MC-EDGE/ACE1000 MODBUS Configuration on
page 635
○ MC-EDGE/ACE1000 MODBUS Client (Master) on
page 635
○ MC-EDGE/ACE1000 MODBUS Server (Slave) on
page 639
○ MC-EDGE/ACE1000 as MODBUS Client (Master)
on page 646

4
 6802979C10-BA
Document History

Version Description Date

○ ACE1000 as MODBUS Client (Master) on page

647
○ MC-EDGE as MODBUS Client (Master) on page
646
○ LoRaWAN Advanced Parameters on page 449
○ Defining MQTT Topics on page 481
○ SCADA Polling and Comm Status of ACE1000
RTUs on page 644
○ LoRaWAN Configuration on page 651
● IL-8377
○ RTU Add-On File Types on page 182
○ SI2 Port Configurations on page 418
○ SI2/SI3 Ports (MC-EDGE T3) on page 420
○ USB and USB1/USB2 Port Configurations on page
440
○ USB and USB1/USB2 Port Parameters on page
440
○ Advanced Link Parameters for USB and USB1/
USB2 Ports on page 440
○ LoRa Port Parameters on page 448
Removed:
○ ACE1000/MC-EDGE MODBUS Support in a Mixed
System
○ ACE1000/MC-EDGE MODBUS Support in an
ACE1000/MC-EDGE System
○ MODBUS Address
○ ACE1000/MC-EDGE Data Register Location
○ ACE1000 MODBUS Data Types

6802979C10-AF ● IL-8658 March 2021

○ MC-EDGE Site Download Options on page 146
○ MC-EDGE LoRaWAN Backup and Restore on
page 653
○ DNS Service Parameters (MC-EDGE) on page 459
○ NTP Service Parameters (MC-EDGE) on page 487
○ MDLC GW API Parameter (MC-EDGE) on page
479
○ SNMP Agent Parameters (MC-EDGE) on page
495
○ ACE1000/MC-EDGE SI1 Port Configurations on
page 399

5
6802979C10-BA
Document History

Version Description Date

○ Adding Elements from the Inventory on page 311

● IL-8695 Added IRRInet-EDGE

6802979C10-AG Minor changes.

6802979C10-AH Minor changes.
6802979C10-AJ ● IL-9184 July 2021
○ Converting ACE3600 Application Databases to
MC-EDGE Format on page 388

6802979C10-AK ● IL-9288 October 2021

○ Customizing the Site Configuration on page 109
○ ACE1000/MC-EDGE SI1 Port Configurations on
page 399
○ Port Protocols for LTE on page 443

6802979C10-AL The following sections were updated: December 2021

● LoRa Port Configurations on page 449
● LoRaWAN Advanced Parameters on page 449
● LoRa Gateway Advanced Parameters on page 450
● Monitoring Database Tables on page 377

6802979C10-AM Minor updates. March 2022

6802979C10-AN Minor updates. June 2022
6802979C10-AP The following sections were updated: September 2022
● ETH1/ETH2/ETH3 Port Configurations on page 431
● ETH1/ETH2/ETH3 Port Parameters on page 430
● USB and USB1/USB2 Port Parameters on page 440
● Advanced Physical Parameters for LTE Port on page
442
● Monitoring Database Tables in RTUs on page 258

6802979C10-AR The following sections were updated: December 2022

● Downloading System Firmware to MC-EDGE Sites on
page 151
● Customizing the Site Configuration on page 109
● Customizing I/O Configuration for ACE1000 and MC-
EDGE Sites on page 121
● Retrieving Error Logger Information from Sites on page
226
● Moving Sites to Areas on page 250
● Adding Elements from the Inventory on page 311
● STS Inventory Elements on page 318

6
 6802979C10-BA
Document History

Version Description Date

● RADIUS Service (MC-EDGE) on page 493

● SNMP Agent Parameters (MC-EDGE) on page 495
The following sections were added:
● Customizing NFM Devices for NFM-EDGE Sites on
page 127
● Setting Login Banner (MC-EDGE) on page 213
● Generating SSH Authentication Keys (MC-EDGE) on
page 213
● Configuring RFDS in STS on page 130
● Creating an RFDS Configuration from a Predefined
Template on page 131
● Manually Creating New RFDS Configuration Files on
page 133
● NFM on page 219
● Exporting UEM Configuration Data for NFM on page
219
● Generating the NFM Site List Report on page 219

6802979C10-AT The following sections were updated: March 2023

● Acronyms and Abbreviations on page 54
● Downloading on page 67
● STS Tools Reference on page 81
● Uploads from Sites on page 159
● Exporting UEM Configuration Data for NFM on page
219
● Retrieving Software Diagnostics from Sites on page
230
● SNMP Agent Parameters (MC-EDGE) on page 495
The following sections were added:
● LEDs Management Parameters (MC-EDGE) on page
479
● PKI Files Management on page 220
● Creating PKI Configuration on page 220
● PKI Configuration Editor Parameters on page 222

6802979C10-AU The change of the title from MC-IoT STS User Guide to May 2023
System Tools Suite User Guide.
The following sections were updated:
● Downloads to Sites on page 145
● Downloading System Firmware to MC-EDGE Sites on
page 151

7
6802979C10-BA
Document History

Version Description Date

● MC-EDGE RTU Version Change on page 163

● Downloading to All Sites on page 206
● Generating SSH Authentication Keys (MC-EDGE) on
page 213
● Creating PKI Configuration on page 220
● PKI Configuration Editor Parameters on page 222
● STS Table Monitor on page 253
● Table Monitor Screens on page 262
● MC-EDGE Advanced IPsec Parameters on page 432
● LoRa Port Parameters on page 448
● SNMP Agent Parameters (MC-EDGE) on page 495
● Syslog Service (MC-EDGE) on page 499
The new sections were added:
● Changing Linux Passwords Manually in Secured STS
on page 216
● Changing SNMP User Credentials (MC-EDGE) on
page 218
● Resetting SNMP User Definitions on page 219
● Static Route (MC-EDGE) on page 499
● MC-EDGE Upgrade Tables on page 654
● MC-EDGE NFM Number of Objects Limitation on page
657

6802979C10-AV The following sections were updated: June 2023

● ACE1000/MC-EDGE DI Parameters on page 452
● ACE1000/MC-EDGE DO Parameters on page 453
● ACE1000/MC-EDGE AI Parameters on page 454
● Customizing the Site Configuration on page 109
● ACE1000/MC-EDGE DI Parameters on page 452
● ACE1000/MC-EDGE AI Parameters on page 454
The new section was added:
● Customization of ASTRO Parameters of NFM-EDGE
and AuxIO-EDGE Sites on page 125

6802979C10-AW The following sections were updated: September 2023

● STS Table View on page 90
● Viewing the System in Table View on page 91
● Customization of ASTRO Parameters of NFM-EDGE
and AuxIO-EDGE Sites on page 125
● Downloads to Sites on page 145

8
 6802979C10-BA
Document History

Version Description Date

● Defining Areas in the STS System on page 99

● Moving Sites to Areas on page 250
● RTU Add-On File Types on page 182
● Changing Linux Passwords Manually in Secured STS
on page 216
● MC-EDGE Advanced IPsec Parameters on page 432
● Advanced Physical Parameters for LTE Port on page
442
● LoRaWAN Advanced Parameters on page 449
● LoRa Gateway Advanced Parameters on page 450
The following sections were added:
● Ports and Files Columns on page 92
● Select Columns Context Menu on page 93
● Adding or Removing Files from Areas on page 100
● Changing Linux Passwords on page 215
● Changing Default Linux Passwords in Secured and
Unsecured STS on page 217

6802979C10-AY The following sections were updated: December 2023

● MC-EDGE LoRaWAN Backup and Restore on page
653
● Customizing the Site Configuration on page 109
● MDLC Communication Driver Configuration on page
138
● Advanced Physical Parameters for LTE Port on page
442
● LoRa Gateway Advanced Parameters on page 450
The following sections were added:
● SSH Known Hosts List (MC-EDGE) on page 215
● Setting up Communications in the Static Mode on page
138
● Dynamic Mode on page 142

6802979C10-BA The following sections were updated: March 2024

● Creating Projects in STS on page 97
● Site Download Reset and Erase Options on page 159
● RTU Add-On File Types on page 182
● LoRaWAN Advanced Parameters on page 449
● LoRa Gateway Advanced Parameters on page 450

9
6802979C10-BA
Contents

Contents
Intellectual Property and Regulatory Notices................................................................... 2
Contact Us............................................................................................................................3
Document History................................................................................................................4
List of Figures.................................................................................................................... 28
List of Tables......................................................................................................................37
List of Processes............................................................................................................... 43
List of Procedures............................................................................................................. 44
About MC-EDGE® Maintenance Manual...........................................................................50
Helpful Background Information.............................................................................................................50
Related Information................................................................................................................................50
Icon Conventions...............................................................................................................51
Style Conventions............................................................................................................. 52
Model Complements..........................................................................................................53
Acronyms and Abbreviations...........................................................................................54
Definitions, Terms, and Conventions.............................................................................. 58
Chapter 1: MC-IoT System Tools Suite – Overview........................................................ 59
1.1 MOSCAD System............................................................................................................................ 60
1.2 Control Center..................................................................................................................................60
1.2.1 Remote Terminal Unit (RTU).............................................................................................. 60
1.2.2 ACE IP Gateway................................................................................................................ 61
1.3 STS for ACE3600 RTUs.................................................................................................................. 62
1.3.1 Features and Functions..................................................................................................... 62
1.3.2 ACE1000, MC-EDGE®, and IRRInet-EDGE RTUs............................................................ 63
1.3.3 Legacy RTUs......................................................................................................................63
1.3.4 RTU Programming Concept...............................................................................................64
1.3.5 Programming Sequence.................................................................................................... 64
1.3.6 RTU Definition....................................................................................................................64
1.3.6.1 Site Configuration.................................................................................................65
1.3.6.2 Network Configuration..........................................................................................65
1.3.7 RTU Application................................................................................................................. 66
1.3.7.1 Downloading.........................................................................................................67
1.4 Communication Network..................................................................................................................67
1.4.1 RTUs and Network.............................................................................................................68
1.4.2 Communication Links.........................................................................................................68

10
 6802979C10-BA
Contents

1.4.3 Communication Types........................................................................................................69

1.5 Network Configurations....................................................................................................................70
1.5.1 Simple System................................................................................................................... 70
1.5.2 Two-Link and Multi-Link Systems.......................................................................................70
1.5.3 Two-Zone System.............................................................................................................. 71
1.5.4 Multiple Zone Systems.......................................................................................................72
1.5.5 Standard Modem................................................................................................................73
1.6 RTU Software...................................................................................................................................73
Chapter 2: MC-IoT STS...................................................................................................... 74
2.1 Hardware and Software Requirements............................................................................................74
2.2 Installing MC-IoT STS......................................................................................................................74
2.3 STS to RTU Connection...................................................................................................................74
2.4 STS and RTU...................................................................................................................................75
2.4.1 RTU....................................................................................................................................75
2.4.2 Database Principles........................................................................................................... 75
2.4.3 Programming Philosophy................................................................................................... 78
2.5 System Tool Suite Overview............................................................................................................ 78
2.6 STS Tools Reference....................................................................................................................... 81
Chapter 3: MC-IoT STS Operation.................................................................................... 83
3.1 MC-IoT STS Operation Overview.................................................................................................... 83
3.2 Graphical User Interface Description............................................................................................... 83
3.2.1 STS Icons...........................................................................................................................85
3.2.2 Menus................................................................................................................................ 86
3.2.3 STS Diagram View.............................................................................................................87
3.2.3.1 Viewing the System in Diagram View...................................................................88
3.2.4 STS Table View..................................................................................................................90
3.2.4.1 Viewing the System in Table View........................................................................91
3.2.4.2 Ports and Files Columns...................................................................................... 92
3.2.4.3 Select Columns Context Menu.............................................................................93
3.2.5 Navigating the System....................................................................................................... 94
3.2.5.1 Navigating via the System Tree............................................................................94
3.2.5.2 Navigating via the System Path Bar.....................................................................95
3.2.5.3 Navigating via the Diagram View..........................................................................95
3.2.5.4 Navigating via the Table View...............................................................................96
3.3 Building a MOSCAD System........................................................................................................... 96
3.3.1 Starting the STS.................................................................................................................97
3.3.2 Creating Projects in STS....................................................................................................97
3.3.3 Setting the System Address...............................................................................................98
3.3.4 Setting the PRIS System Address..................................................................................... 99

11
6802979C10-BA
Contents

3.3.5 Defining Areas in the STS System.....................................................................................99

3.3.5.1 Adding or Removing Files from Areas................................................................100
3.3.6 Defining Sites in the STS System.................................................................................... 101
3.3.6.1 Defining an ACE3600 Site..................................................................................102
3.3.6.2 Defining an IRRInet Site in the STS System...................................................... 104
3.3.6.3 Defining an ACE1000, AuxIO-EDGE or MC-EDGE Site.................................... 106
3.3.6.4 Defining an ACE IP Gateway Site...................................................................... 107
3.3.7 Customizing the Site Configuration..................................................................................109
3.3.7.1 Customizing Site Port Configuration...................................................................110
3.3.7.2 Customizing I/O Configuration for ACE3600 Sites............................................. 114
3.3.7.3 Customizing I/O Configuration for ACE1000 and MC-EDGE Sites....................121
3.3.7.4 Customizing I/O Configuration for IRRInet-M Sites............................................125
3.3.7.5 Customization of ASTRO Parameters of NFM-EDGE and AuxIO-EDGE Sites. 125
3.3.7.6 Customizing NFM Devices for NFM-EDGE Sites...............................................127
3.3.7.7 Customizing Advanced Site Parameters............................................................128
3.3.7.8 Customizing Add-On Options for Existing Sites................................................. 130
3.3.7.9 Configuring RFDS in STS.................................................................................. 130
3.3.7.10 Creating an RFDS Configuration from a Predefined Template........................ 131
3.3.7.11 Manually Creating New RFDS Configuration Files...........................................133
3.3.8 Defining Site Communication Links................................................................................. 135
3.3.9 Defining I/Os in Sites........................................................................................................136
3.3.10 Importing Legacy RTU Site Configurations.................................................................... 137
3.3.11 MDLC Communication Driver Configuration.................................................................. 138
3.3.11.1 Setting up Communications in the Static Mode................................................ 138
3.3.11.2 Dynamic Mode..................................................................................................142
3.3.11.3 MDLC Driver Console.......................................................................................143
3.3.12 APX CPS Mode (MC-EDGE v15.00 or Lower).............................................................. 144
3.3.13 Downloads to Sites........................................................................................................ 145
3.3.13.1 Download Restrictions......................................................................................146
3.3.13.2 MC-EDGE Site Download Options...................................................................146
3.3.13.3 Downloading System Firmware to ACE3600 and IRRInet-M Sites..................147
3.3.13.4 Downloading System Firmware to MC-EDGE Sites.........................................151
3.3.13.5 Downloading Other Files to Sites..................................................................... 153
3.3.13.6 Site Download Reset and Erase Options......................................................... 159
3.3.14 Uploads from Sites.........................................................................................................159
3.3.14.1 Uploading Files from Sites............................................................................... 160
3.3.15 Upgrading ACE3600 System Firmware......................................................................... 161
3.3.16 MC-EDGE RTU Version Change................................................................................... 163
3.3.17 Closing STS Projects..................................................................................................... 164

12
 6802979C10-BA
Contents

3.4 Administering the System.............................................................................................................. 164

3.4.1 Opening Existing Projects................................................................................................ 164
3.4.2 Managing Applications..................................................................................................... 166
3.4.3 Editing Link Type Costs....................................................................................................169
3.4.4 Network Tables.................................................................................................................169
3.4.4.1 Managing Network Tables.................................................................................. 170
3.4.4.2 Editing Network Tables.......................................................................................172
3.4.5 Configuring MDLC Links.................................................................................................. 173
3.4.6 IP Conversion Tables....................................................................................................... 175
3.4.6.1 Managing IP Conversion Tables.........................................................................175
3.4.6.2 Editing IP Conversion Table Files.......................................................................177
3.4.6.3 IP Conversion Table Editor Functions................................................................ 179
3.4.7 Managing Dynamic IP Access Tables.............................................................................. 180
3.4.8 Managing Add-On Files................................................................................................... 180
3.4.8.1 RTU Add-On File Types..................................................................................... 182
3.4.9 Encrypting MC-EDGE Add-On Files (Secured STS Only)............................................... 185
3.4.10 Site Tables......................................................................................................................186
3.4.10.1 Managing Site Tables....................................................................................... 188
3.4.10.2 Site Table Editor............................................................................................... 190
3.4.11 Managing DNP Client (Master) Configuration Files........................................................198
3.4.12 Field View.......................................................................................................................200
3.4.12.1 Retrieving the Field View..................................................................................201
3.4.13 Uploading New Sites to STS..........................................................................................202
3.4.14 Downloading to All Sites................................................................................................ 206
3.4.15 MDLC Password Change...............................................................................................208
3.4.15.1 Changing the MDLC Password in Project Only................................................209
3.4.15.2 Changing the MDLC Password in Sites........................................................... 209
3.4.15.3 Overriding the MDLC Password....................................................................... 211
3.4.16 Adding Comments..........................................................................................................212
3.4.17 Backing Up the Database.............................................................................................. 213
3.4.18 Setting Login Banner (MC-EDGE)................................................................................. 213
3.4.19 Generating SSH Authentication Keys (MC-EDGE)........................................................213
3.4.20 SSH Known Hosts List (MC-EDGE)...............................................................................215
3.4.21 Changing Linux Passwords............................................................................................215
3.4.21.1 Changing Linux Passwords Manually in Secured STS.................................... 216
3.4.21.2 Changing Default Linux Passwords in Secured and Unsecured STS..............217
3.4.22 Changing SNMP User Credentials (MC-EDGE)............................................................ 218
3.4.22.1 Resetting SNMP User Definitions.................................................................... 219
3.4.23 NFM............................................................................................................................... 219

13
6802979C10-BA
Contents

3.4.23.1 Exporting UEM Configuration Data for NFM.................................................... 219

3.4.23.2 Generating the NFM Site List Report............................................................... 219
3.4.24 Printing the System........................................................................................................ 220
3.4.25 PKI Files Management...................................................................................................220
3.4.25.1 Creating PKI Configuration...............................................................................220
3.4.25.2 PKI Configuration Editor Parameters............................................................... 222
3.5 Administering Sites (Basic)............................................................................................................ 224
3.5.1 Customizing Site Configurations...................................................................................... 224
3.5.2 Renaming Sites................................................................................................................224
3.5.3 Changing the Site ID of Sites........................................................................................... 225
3.5.4 Site Error Logging............................................................................................................ 226
3.5.4.1 Retrieving Error Logger Information from Sites..................................................226
3.5.5 Site Diagnostics............................................................................................................... 229
3.5.5.1 Retrieving Software Diagnostics from Sites....................................................... 230
3.5.6 Time Tagged Event Logging.............................................................................................232
3.5.6.1 Retrieving Time-Tagged Event Logs from Sites................................................. 233
3.5.7 Setting and Retrieving Site Date and Time...................................................................... 235
3.5.8 Synchronizing Sites..........................................................................................................236
3.5.9 Editing Network Tables in Individual Sites........................................................................237
3.5.10 Editing Site Tables in Individual Sites.............................................................................237
3.5.11 Phonebook Files and Modems.......................................................................................237
3.5.11.1 Modem Connections.........................................................................................238
3.5.11.2 Setting Dial-Up Parameters.............................................................................. 239
3.5.11.3 Dial-Up Parameters.......................................................................................... 239
3.5.11.4 Editing Phonebook Files...................................................................................241
3.5.11.5 Dialing Site-Attached Modem Numbers............................................................242
3.5.12 Editing IP Conversion Tables in Individual Sites............................................................ 243
3.5.13 Uploading Site Definitions.............................................................................................. 243
3.5.13.1 Results of Site Definition Upload......................................................................244
3.5.14 Application Programming............................................................................................... 245
3.5.15 Opening Site Applications.............................................................................................. 245
3.5.16 Copying Sites................................................................................................................. 246
3.5.17 Copying Sites with CPU Redundancy............................................................................247
3.5.18 Moving Sites to Areas.................................................................................................... 250
3.5.19 Toggling the FEP Status.................................................................................................251
3.5.20 Deleting Sites................................................................................................................. 252
3.6 Application Monitoring (ACE3600 and MC-EDGE)........................................................................252
3.7 STS Table Monitor......................................................................................................................... 253
3.7.1 Monitoring Database Tables in RTUs...............................................................................258

14
 6802979C10-BA
Contents

3.7.2 Refreshing Values in the Table Monitor............................................................................261

3.7.3 Updating RTUs via the Table Monitor...............................................................................261
3.7.4 Copying Information in the Table Monitor.........................................................................262
3.7.5 Printing Screens in the Table Monitor.............................................................................. 262
3.7.6 Table Monitor Screens..................................................................................................... 262
3.8 Administering Sites (Advanced).....................................................................................................267
3.8.1 STS Hardware Testing..................................................................................................... 267
3.8.2 Performing Hardware Tests..............................................................................................267
3.8.2.1 Starting the STS Hardware Test Utility............................................................... 268
3.8.2.2 Testing Expansion Modules................................................................................269
3.8.2.3 Testing the CPU................................................................................................. 289
3.8.2.4 Testing LEDs...................................................................................................... 294
3.8.2.5 Testing the Power Supply...................................................................................299
3.8.2.6 Testing the ACE3600 Plug-In Communication Port............................................306
3.8.2.7 Testing the IRRInet-M Port 3.............................................................................. 307
3.8.2.8 Power Management Test....................................................................................308
3.8.2.9 Upgrading Expansion Loader Firmware.............................................................310
3.8.3 Configuring the Advanced Parameters.............................................................................311
3.8.4 Analyzing MDLC Protocol.................................................................................................311
3.8.5 Defining and Activating Encrypted MDLC Communication.............................................. 311
3.9 Using the Inventory........................................................................................................................ 311
3.9.1 Adding Elements from the Inventory................................................................................ 311
3.9.2 Storing Elements in the Gallery........................................................................................314
3.9.3 Modifying Folders in the Gallery.......................................................................................316
3.9.4 Importing the Gallery from Another STS.......................................................................... 316
3.9.5 STS Inventory Elements.................................................................................................. 318
3.10 Viewing the Online Help and STS Version...................................................................................321
3.11 Exporting and Importing Site Properties.......................................................................................322
Exporting Site Properties to a .csv File................................................................................... 322
Importing Site Properties Tables to Sites.................................................................................. 323
Chapter 4: Application Programmer...............................................................................324
4.1 Application Programmer Overview................................................................................................ 324
4.2 Application Programming...............................................................................................................325
4.3 Starting the Application Programmer............................................................................................. 326
4.4 Creating New Applications.............................................................................................................326
4.5 Opening Existing Applications....................................................................................................... 327
4.6 Navigating the Application Programmer Window...........................................................................328
4.7 Building a Database.......................................................................................................................328
4.7.1 User Tables...................................................................................................................... 329

15
6802979C10-BA
Contents

4.7.2 System Tables..................................................................................................................329

4.7.3 Constant Tables (ACE3600 Only).................................................................................... 330
4.7.4 Single-Column Tables...................................................................................................... 331
4.7.5 Multiple-Column Tables....................................................................................................331
4.7.6 Data Types....................................................................................................................... 332
4.7.7 Creating Database Tables................................................................................................333
4.7.8 Opening Existing Tables...................................................................................................333
4.7.9 Editing Tables...................................................................................................................334
4.7.9.1 Editing Single-Column Tables............................................................................ 334
4.7.9.2 Editing Multiple-Column Tables.......................................................................... 336
4.7.9.3 Toggling the Attribute Page................................................................................ 339
4.7.10 Searching for Variables or Duplicated Columns.............................................................339
4.7.11 Copying (or Cutting) and Pasting Tables........................................................................340
4.7.12 Deleting Tables...............................................................................................................341
4.7.13 Renaming Tables........................................................................................................... 341
4.7.14 Printing Tables................................................................................................................341
4.7.15 Batch Printing Tables..................................................................................................... 342
4.7.16 Monitoring Tables........................................................................................................... 342
4.7.17 Database Building Examples......................................................................................... 342
4.8 Process Programming (ACE3600 Only)........................................................................................ 344
4.8.1 Process Tree.................................................................................................................... 345
4.8.1.1 Creating Processes............................................................................................ 345
4.8.1.2 Creating Rungs.................................................................................................. 346
4.8.2 Editing Rungs...................................................................................................................346
4.8.2.1 Adding Elements to Rungs Manually................................................................. 347
4.8.2.2 Adding Elements to Rungs Automatically.......................................................... 348
4.8.2.3 Linking Elements in Rungs.................................................................................350
4.8.2.4 Normalizing Rungs............................................................................................. 351
4.8.2.5 Creating Branches Manually.............................................................................. 351
4.8.2.6 Creating Branches Automatically....................................................................... 351
4.8.2.7 Closing Branches............................................................................................... 352
4.8.2.8 Selecting Elements in Rungs............................................................................. 352
4.8.2.9 Copying (or Cutting) and Pasting Elements in Rungs........................................ 353
4.8.2.10 Duplicating Elements in Rungs........................................................................ 353
4.8.2.11 Deleting Elements in Rungs............................................................................. 353
4.8.2.12 Adding Comments to the Rung Workspace..................................................... 353
4.8.3 Rung Element Parameters...............................................................................................353
4.8.3.1 Rung Element Parameter Examples.................................................................. 354
4.8.3.2 Defining Rung Element Parameters...................................................................355

16
 6802979C10-BA
Contents

4.8.3.3 Looking Up Element Parameters in the Database............................................. 357

4.8.4 Deleting Processes and Rungs........................................................................................357
4.8.5 Renaming Processes and Rungs.....................................................................................357
4.8.6 Copying (or Cutting) and Pasting Rungs..........................................................................358
4.8.7 Adding Descriptions to Processes and Rungs................................................................. 358
4.8.8 Printing Processes and Rungs.........................................................................................359
4.8.9 Searching Rungs..............................................................................................................359
Searching with The Find Dialog.....................................................................................359
Searching Quickly from an Open Database................................................................... 361
4.8.10 Rung Monitoring.............................................................................................................361
4.8.11 Examples of Building Rung Sequences......................................................................... 361
4.9 I/Os and Database Linking (ACE3600/MC-EDGE Only)............................................................... 363
4.9.1 I/O Link Tree.....................................................................................................................363
4.9.2 I/O Link Definition Table................................................................................................... 364
4.9.2.1 I/O Link Definition Table Parameters..................................................................365
4.9.3 Selecting Sites in the Application Programmer................................................................ 365
4.9.4 Linking I/Os to the Database............................................................................................366
4.9.5 Connecting I/O Groups.................................................................................................... 368
4.9.6 Distributing I/O Link Information.......................................................................................369
4.9.7 I/O Link Definitions........................................................................................................... 370
4.10 Finding Symbols/Variables in Applications...................................................................................371
4.11 Saving Applications in STS Mode................................................................................................ 372
4.12 Saving Applications in Standalone Mode.....................................................................................373
Saving Applications...................................................................................................................373
Saving Applications Under a Different Name............................................................................ 373
4.13 Compiling Applications (ACE3600 Only)..................................................................................... 373
4.13.1 Explicit versus Automatic Scanning............................................................................... 375
4.14 Downloading Applications in the Application Programmer.......................................................... 375
4.15 Application Monitoring..................................................................................................................377
4.15.1 Monitoring Database Tables...........................................................................................377
Starting the Table Monitor.............................................................................................. 377
Using the Table Monitor..................................................................................................379
4.15.1.1 Table Monitor Commands................................................................................ 379
4.15.2 Monitoring Rungs (ACE3600 Only)................................................................................380
Starting the Rung Monitor.............................................................................................. 380
Using the Rung Monitor..................................................................................................381
4.15.2.1 Rung Monitor Commands................................................................................ 382
4.15.3 Displaying the Performance Monitor Table.................................................................... 383
4.15.3.1 System Performance Monitoring Variables...................................................... 384

17
6802979C10-BA
Contents

4.16 Backing Up the Database............................................................................................................ 385

4.16.1 Defining Critical Database Blocks.................................................................................. 385
4.16.1.1 BlocksToBackup Table Parameters..................................................................386
4.16.2 Storing Critical Database Blocks....................................................................................387
4.16.3 Restoring Critical Database Blocks................................................................................387
4.16.4 Removing Critical Database Blocks............................................................................... 388
4.17 Converting ACE3600 Application Databases to MC-EDGE Format............................................ 388
4.18 Viewing the Application Programmer Online Help....................................................................... 390
4.19 Printing Applications.................................................................................................................... 390
4.20 Closing Applications.....................................................................................................................391
4.21 Exiting the Application Programmer Window...............................................................................392
4.22 Keyboard Commands in Application Programming..................................................................... 392
Appendix A: Site Configuration Parameters................................................................ 395
A.1 Port Parameters (ACE3600/ACE1000/MC-EDGE)....................................................................... 395
A.1.1 SI1 Port............................................................................................................................396
A.1.1.1 SI1 Port Parameters.......................................................................................... 396
A.1.1.2 ACE3600 SI1 Port Configurations..................................................................... 398
A.1.1.3 ACE1000/MC-EDGE SI1 Port Configurations................................................... 399
A.1.1.4 Link Parameters for SI1 Port..............................................................................400
A.1.1.5 Advanced Physical Parameters for SI1 Port......................................................403
A.1.1.6 Advanced Link Parameters for SI1 Port.............................................................408
A.1.1.7 PLC Parameters for SI1 Port............................................................................. 416
A.1.2 SI2 Port (ACE3600, MC-EDGE T2).................................................................................418
A.1.2.1 SI2 Port Configurations......................................................................................418
A.1.2.2 SI2 Port Parameters.......................................................................................... 419
A.1.2.3 Link Parameters for SI2 Port..............................................................................420
A.1.2.4 Advanced Physical Parameters for SI2 Port......................................................420
A.1.2.5 Advanced Link Parameters for SI2 Port.............................................................420
A.1.2.6 PLC Parameters for SI2 Port............................................................................. 420
A.1.3 SI2/SI3 Ports (MC-EDGE T3).......................................................................................... 420
A.1.4 PI1/PI2 Ports (ACE3600 and ACE1000)......................................................................... 420
A.1.4.1 PI1/PI2 Port Parameters.................................................................................... 420
A.1.4.2 ACE3600 PI1/PI2 Port Configurations............................................................... 423
A.1.4.3 ACE1000 PI1/PI2 Port Configurations............................................................... 424
A.1.4.4 Link Parameters for PI1/PI2 Ports..................................................................... 425
A.1.4.5 Advanced Physical Parameters for PI1/PI2 Ports..............................................426
A.1.4.6 Advanced Link Parameters for Ports PI1/PI2.................................................... 429
A.1.4.7 PLC Parameters for PI1/PI2 Ports..................................................................... 430
A.1.5 ETH1/ETH2/ETH3 Ports..................................................................................................430

18
 6802979C10-BA
Contents

A.1.5.1 ETH1/ETH2/ETH3 Port Parameters.................................................................. 430

A.1.5.2 ETH1/ETH2/ETH3 Port Configurations..............................................................431
A.1.5.3 Link Parameters for ETH1/ETH2/ETH3 Ports....................................................432
A.1.5.4 Advanced Physical Parameters for ETH1/ETH2/ETH3 Ports............................432
A.1.5.5 Advanced Link Parameters for Port ETH1/ETH2/ETH3.................................... 432
A.1.5.6 PLC Parameters for Port ETH1/ETH2/ETH3..................................................... 432
A.1.5.7 MC-EDGE Advanced IPsec Parameters........................................................... 432
A.1.5.8 Advanced IPsec Parameters – Usage Notes.....................................................435
A.1.5.9 Port Protocols for ETH1/ETH2/ETH3.................................................................436
A.1.6 HU1/HU2 Ports (ACE3600)............................................................................................. 436
A.1.6.1 HU1/HU2 Port Parameters................................................................................ 436
A.1.6.2 HU1/HU2 Port Configurations............................................................................437
A.1.6.3 Link Parameters for HU1/HU2 Ports..................................................................437
A.1.6.4 Advanced Physical Parameters for HU1/HU2 Ports.......................................... 437
A.1.6.5 Advanced Link Parameters for HU1/HU2 Ports.................................................439
A.1.7 USB (MC-EDGE) and USB1/USB2 (ACE1000) Ports..................................................... 440
A.1.7.1 USB and USB1/USB2 Port Parameters.............................................................440
A.1.7.2 USB and USB1/USB2 Port Configurations........................................................ 440
A.1.7.3 Advanced Link Parameters for USB and USB1/USB2 Ports............................. 440
A.1.8 APX Port (MC-EDGE)......................................................................................................441
A.1.8.1 APX Port Configurations.................................................................................... 441
A.1.8.2 Advanced Link Parameters for APX Port...........................................................441
A.1.9 LTE Port (MC-EDGE T1/T2)............................................................................................ 441
A.1.9.1 LTE Port Parameters..........................................................................................441
A.1.9.2 Advanced Physical Parameters for LTE Port..................................................... 442
A.1.9.3 Advanced Link Parameters for Port LTE............................................................443
A.1.9.4 Advanced IPsec Parameters for LTE Port......................................................... 443
A.1.9.5 Port Protocols for LTE........................................................................................ 443
A.1.10 DU1 Port (ACE3600)..................................................................................................... 444
A.1.10.1 DU1 Port Parameters.......................................................................................444
A.1.10.2 DU1 Port Configurations.................................................................................. 444
A.1.10.3 Link Parameters for DU1 Port..........................................................................444
A.1.10.4 Advanced Physical Parameters for DU1 Port.................................................. 445
A.1.10.5 Advanced Link Parameters for DU1 Port.........................................................445
A.1.11 INTR1 Port (ACE3600).................................................................................................. 445
A.1.11.1 INTR1 Port Parameters....................................................................................445
A.1.11.2 INTR1 Port Configurations............................................................................... 446
A.1.11.3 Link Parameters for Port INTR1....................................................................... 446
A.1.11.4 Advanced Physical Parameters for INTR1 Port............................................... 446

19
6802979C10-BA
Contents

A.1.11.5 Advanced Link Parameters for Port INTR1...................................................... 446

A.1.12 TSP<x> (ACE4600 Terminal Server Ports)................................................................... 446
A.1.12.1 TSP<x> Port Parameters................................................................................ 446
A.1.12.2 TSP<x> Port Configurations............................................................................447
A.1.12.3 Link Parameters for TSP<x>........................................................................... 447
A.1.12.4 Advanced Physical Parameters for TSP<x>................................................... 448
A.1.12.5 Advanced Link Parameters for TSP<x>.......................................................... 448
A.1.13 OTG Port (MC-EDGE)................................................................................................... 448
A.1.14 LoRa Port (MC-EDGE).................................................................................................. 448
A.1.14.1 LoRa Port Parameters..................................................................................... 448
A.1.14.2 LoRa Port Configurations.................................................................................449
A.1.14.3 LoRaWAN Advanced Parameters....................................................................449
A.1.14.4 LoRa Gateway Advanced Parameters.............................................................450
A.1.14.5 LoRaWAN IP Firewall...................................................................................... 450
A.2 I/O Parameters (ACE3600/ACE1000/MC-EDGE)......................................................................... 450
A.2.1 ACE3600 DI Parameters................................................................................................. 450
A.2.2 ACE3600 DO Parameters............................................................................................... 451
A.2.3 ACE3600 AI Parameters................................................................................................. 451
A.2.4 ACE1000/MC-EDGE DI Parameters............................................................................... 452
A.2.5 ACE1000/MC-EDGE DO Parameters............................................................................. 453
A.2.6 ACE1000/MC-EDGE AI Parameters............................................................................... 454
A.2.7 ACE1000/MC-EDGE AO Parameters..............................................................................455
A.3 Advanced Parameters (ACE3600/ACE1000/MC-EDGE)..............................................................456
A.3.1 'C' Application Parameters (ACE3600)............................................................................456
A.3.2 Core Dump Parameters (ACE3600)................................................................................ 458
A.3.3 DNS Client Parameters (ACE3600).................................................................................459
A.3.4 DNS Service Parameters (MC-EDGE)............................................................................ 459
A.3.5 Dynamic IP Routing Parameters (ACE3600)...................................................................461
A.3.6 Dynamic Site Table Parameters (ACE3600/ACE1000/MC-EDGE)................................. 462
A.3.7 Error Logger Parameters (ACE3600).............................................................................. 462
A.3.8 Fast Event Parameters (ACE3600)................................................................................. 463
A.3.9 Firewall & Hardening Parameters (ACE3600)................................................................. 463
A.3.10 Firewall & Hardening Parameters (MC-EDGE)............................................................. 466
A.3.11 Formatter Parameters (ACE3600)................................................................................. 466
A.3.12 Frame Sequence Application Parameters (ACE3600/ACE1000/MC-EDGE)................467
A.3.13 Frame Sequence Layer Parameters (ACE3600/ACE1000/MC-EDGE)........................ 467
A.3.14 Gap Ratio Parameters (ACE3600)................................................................................ 469
A.3.15 Gateway Parameters (ACE4600).................................................................................. 469
A.3.15.1 System Resources...........................................................................................469

20
 6802979C10-BA
Contents

A.3.15.2 Tasks Allocation............................................................................................... 469

A.3.15.3 Requests Allocation......................................................................................... 470
A.3.15.4 Flags................................................................................................................ 470
A.3.16 Hardware Test Parameters (ACE3600)......................................................................... 471
A.3.17 Heap Parameters (ACE3600/ACE1000/MC-EDGE)..................................................... 471
A.3.18 I/O Parameters (ACE3600)............................................................................................472
A.3.19 I/O Expansion Parameters (ACE3600)..........................................................................473
A.3.20 I/O Expansion Manager Parameters (ACE3600)...........................................................474
A.3.21 IP Conversion Table Parameters (ACE3600/ACE1000/MC-EDGE)..............................478
A.3.22 LEDs Management Parameters (MC-EDGE)................................................................ 479
A.3.23 MDLC GW API Parameter (MC-EDGE)........................................................................ 479
A.3.24 MQTT Parameters (MC-EDGE).....................................................................................479
A.3.24.1 Defining MQTT Topics..................................................................................... 481
A.3.25 Minisession Parameters (ACE3600/ACE1000/MC-EDGE)........................................... 481
A.3.25.1 Minisession Broadcasts................................................................................... 482
A.3.25.2 Minisession Event and Burst............................................................................482
A.3.25.3 Minisession RTU to RTU..................................................................................483
A.3.25.4 Minisession Authentication Client.................................................................... 484
A.3.25.5 Minisession Authentication Server...................................................................484
A.3.26 NTP Parameters (ACE3600)......................................................................................... 485
A.3.27 NTP Service Parameters (MC-EDGE)...........................................................................487
A.3.28 Network Parameters (ACE3600/ACE1000/MC-EDGE).................................................488
A.3.29 PLC Parameters (ACE3600)......................................................................................... 489
A.3.29.1 PLC Heap........................................................................................................ 489
A.3.29.2 PLC MOSCAD as Client (Master) (Ladder Diagram).......................................489
A.3.30 PPP Parameters (ACE3600)......................................................................................... 490
A.3.31 Power Management Parameters (ACE3600)................................................................ 490
A.3.32 Power Supply Parameters (ACE3600/ACE1000/MC-EDGE)........................................491
A.3.33 RISC Timers Parameters (ACE3600)............................................................................ 493
A.3.34 Redundancy Parameters (ACE3600)............................................................................ 493
A.3.35 RADIUS Service (MC-EDGE)........................................................................................493
A.3.36 SNMP Agent Parameters (MC-EDGE).......................................................................... 495
A.3.37 Session Parameters (ACE3600/ACE1000/MC-EDGE)................................................. 497
A.3.38 Static Route (MC-EDGE)...............................................................................................499
A.3.39 Syslog Service (MC-EDGE)...........................................................................................499
A.3.40 Time Sync Parameters (ACE3600/ACE1000/MC-EDGE)............................................. 500
A.3.41 Time Tag Parameters (ACE3600)..................................................................................501
A.3.42 Time Zone Parameters (ACE3600/ACE1000/MC-EDGE)............................................. 501
A.3.43 Timer Event Parameters (ACE3600)............................................................................. 502

21
6802979C10-BA
Contents

A.3.44 Timer Service Parameters (ACE3600/ACE1000/MC-EDGE)........................................ 503

A.3.45 USB Parameters (ACE3600)......................................................................................... 505
A.3.46 User Application Parameters (ACE3600)...................................................................... 505
A.3.46.1 Ladder Processes Tasks..................................................................................506
A.3.46.2 Database Backup.............................................................................................507
A.4 IRRInet-M Port Parameters........................................................................................................... 507
A.4.1 IRRInet-M Port 1..............................................................................................................507
A.4.1.1 IRRInet-M Port 1 Parameters............................................................................ 508
A.4.1.2 Advanced Physical and Link Parameters for IRRInet-M Port 1......................... 509
A.4.2 IRRInet-M Port 2..............................................................................................................509
A.4.3 IRRInet-M Port 2 Parameters.......................................................................................... 509
A.4.3.1 Advanced Physical and Link Parameters for IRRInet-M Port 2......................... 509
A.4.4 IRRInet-M Port 3..............................................................................................................510
A.4.4.1 IRRInet-M Port 3 Parameters............................................................................ 510
A.4.4.2 Advanced Physical and Link Parameters for IRRInet-M Port 3......................... 510
A.5 IRRInet-M I/O Parameters............................................................................................................. 511
A.6 Advanced Parameters (IRRInet-M)............................................................................................... 512
A.6.1 IRRInet-M ‘C’ Application Parameters............................................................................. 512
A.6.2 IRRInet-M Heap Parameters........................................................................................... 514
A.6.3 IRRInet-M Leds Parameters............................................................................................ 515
A.6.4 IRRInet-M Power Management Parameters....................................................................516
Appendix B: Ladder Diagram Language.......................................................................517
B.1 Inputs and Outputs........................................................................................................................ 517
B.2 Variables........................................................................................................................................517
B.3 Ladder Diagram Elements.............................................................................................................518
B.3.1 Normally-Open (N.O.) Contact Element.......................................................................... 518
B.3.2 Relay On Element............................................................................................................519
B.3.3 Normally-Closed (N.C.) Contact Element........................................................................ 519
B.3.4 Relay Off Element............................................................................................................521
B.3.5 Comparators.................................................................................................................... 521
B.3.6 Relay Latch (L) and Relay Unlatch (U) Elements............................................................ 523
B.3.7 Reset (RST).....................................................................................................................524
B.3.8 Timers.............................................................................................................................. 525
B.3.8.1 On Delay Timer (DON).......................................................................................525
B.3.8.2 Off Delay Timer (DOF)....................................................................................... 528
B.3.8.3 Retentive Timer (TRT)....................................................................................... 529
B.3.9 Differentiators: Positive (UP), Negative (DOWN).............................................................531
B.3.10 Count Up (CTU), Count Down (CTD)............................................................................ 532
B.3.11 Jump (JMP)....................................................................................................................534

22
 6802979C10-BA
Contents

B.3.12 Scan (SCN)....................................................................................................................534

B.3.13 Move Low (MOV), Move High (MOVH)......................................................................... 535
B.3.14 Arithmetical Calculations............................................................................................... 543
B.3.15 Boolean Algebraic Operations – AND, OR, XOR.......................................................... 544
B.3.16 CALC............................................................................................................................. 545
B.3.17 Jump To Subprocess (JSP), Return (RET)....................................................................547
B.3.18 SEND.............................................................................................................................548
B.3.19 Logical Shift to Left (LSL)/Right (LSR)...........................................................................549
B.3.20 Arithmetical Shift to Left (ASL)/Right (ASR).................................................................. 549
B.3.21 Rotate to Left (ROL)/Right (ROR)..................................................................................550
B.3.22 CAL................................................................................................................................551
B.3.23 Run Process (RNP)....................................................................................................... 553
B.3.24 Conversion of Variable Notation.................................................................................... 554
B.3.25 Copy Columns (CPY).................................................................................................... 555
B.3.26 User Call Function (UCL)...............................................................................................556
B.3.27 Trigger Enable (TEN)/Disable (TDS)............................................................................. 556
B.4 Ladder Diagram Reference........................................................................................................... 556
B.4.1 Input Elements.................................................................................................................557
B.4.2 Output Elements.............................................................................................................. 557
Appendix C: Database Tables and Data Types.............................................................559
C.1 MOSCAD-M and IRRInet-M RTU Database................................................................................. 559
C.2 ACE1000/MC-EDGE/IRRInet-EDGE Database............................................................................ 559
C.3 Table Types................................................................................................................................... 560
C.3.1 Single-Column Table....................................................................................................... 560
C.3.2 Multiple-Column Table..................................................................................................... 560
C.3.3 Duplicated Columns........................................................................................................ 561
C.3.4 Single- and Multiple-Column Tables Comparison............................................................561
C.4 Table Groups................................................................................................................................. 562
C.5 User Tables................................................................................................................................... 562
C.6 System Tables............................................................................................................................... 562
C.7 Constant Tables.............................................................................................................................563
C.8 Tables Descriptions....................................................................................................................... 564
C.8.1 RTU-to-RTU Controls/RTU-to-RTU Comm Buff and RTU-RTU Frame Types................ 564
C.8.2 Time & Date Table........................................................................................................... 564
C.8.3 Index Table...................................................................................................................... 568
C.8.4 Reserved Flags Table......................................................................................................572
C.8.5 Performance Monitor Table............................................................................................. 576
C.8.6 User Ports Table.............................................................................................................. 576
C.8.7 Site Table.........................................................................................................................576

23
6802979C10-BA
Contents

C.8.8 Tx Event Table.................................................................................................................576

C.8.9 Data Burst Table.............................................................................................................. 577
C.8.10 Reserved Values Table..................................................................................................577
C.8.11 PRMEVENT Table......................................................................................................... 580
C.8.12 PLC Table...................................................................................................................... 580
C.8.13 PLC Dynamic IOLINK Table.......................................................................................... 580
C.8.14 CPU Power Supply Table.............................................................................................. 580
C.8.15 Main Power Supply1 Table............................................................................................ 580
C.8.16 Main Power Supply2 Table............................................................................................ 581
C.8.17 Daylight Saving Dates Table..........................................................................................581
C.8.18 PLC IP Access Control Table........................................................................................ 582
C.8.19 Expansions Reserved Flags Table................................................................................ 582
C.8.20 Expansions Reserved Values Table.............................................................................. 583
C.8.21 ASCII Table....................................................................................................................584
C.8.22 User Port Names Table................................................................................................. 584
C.8.23 User Port Modes Table.................................................................................................. 584
C.8.24 User Port Protocols Table..............................................................................................584
C.8.25 User Port Baud Rates Table.......................................................................................... 584
C.8.26 Event Definitions 1 Table............................................................................................... 585
C.8.27 Event Definitions 2 Table............................................................................................... 585
C.8.28 MDLC Port ID’s Table.................................................................................................... 585
C.8.29 RTU-to-RTU Frame Types Table................................................................................... 585
C.8.30 Years Table.................................................................................................................... 585
C.8.31 Months Table................................................................................................................. 585
C.8.32 Days Table.....................................................................................................................585
C.8.33 Time Constants Table.................................................................................................... 586
C.8.34 PLC Status Defines Table..............................................................................................586
C.8.35 Timer Event Defines Table.............................................................................................586
C.8.36 Trigger States Table.......................................................................................................586
C.8.37 PLC Dynamic IOLINK Constants Table......................................................................... 586
C.9 Data Types.................................................................................................................................... 586
C.9.1 Discrete – Internal Bit (bit)............................................................................................... 587
C.9.2 Integer Value – Internal Integer Value (int)...................................................................... 588
C.9.3 Real Value – Internal Real Value (real)............................................................................588
C.9.4 Integer Parameter – Internal Integer Parameter (iprm)................................................... 588
C.9.5 Real Parameter – Internal Real Parameter (rprm).......................................................... 588
C.9.6 Discrete Input (d-i)........................................................................................................... 588
C.9.7 Discrete Output (d-o)....................................................................................................... 589
C.9.8 Value Input (v-i)................................................................................................................589

24
 6802979C10-BA
Contents

C.9.9 Value Output (v-o)............................................................................................................590

C.9.10 Scaled Analog Input (sAI)..............................................................................................591
C.9.11 Scaled Analog Output (sAO)..........................................................................................592
C.9.12 Mapped Discrete (mbit)................................................................................................. 592
C.9.13 Mapped Value (mval).....................................................................................................592
C.9.14 Hours Timer (Hr:Mn)......................................................................................................592
C.9.15 Minutes Timer (Mn:Sc).................................................................................................. 593
C.9.16 Seconds Timer (Sc:Ms)................................................................................................. 593
C.9.17 Pulses Per Hour (pph)................................................................................................... 593
C.9.18 Time-Tagged DI (TgDI).................................................................................................. 593
C.9.19 Programmable Ladder Controller (plc_vi, plc_vo, plc_di, plc_do, plc_ri, plc_ro)...........594
C.9.20 Index..............................................................................................................................594
C.9.21 Constants...................................................................................................................... 594
C.9.22 Byte Value......................................................................................................................594
C.9.23 Long Value.....................................................................................................................595
C.9.24 Mapped Byte................................................................................................................. 595
C.9.25 Mapped Long.................................................................................................................595
C.9.26 Byte Parameter..............................................................................................................595
C.9.27 Long Parameter.............................................................................................................595
C.9.28 IP Address..................................................................................................................... 596
C.9.29 IP Address Parameter................................................................................................... 596
Appendix D: User Defined Local Ports......................................................................... 597
D.1 User Ports Table............................................................................................................................598
D.1.1 PTxFlg Variable and SEND Operator.............................................................................. 598
D.1.2 PRxFlg Variable...............................................................................................................602
D.1.3 PRxChr Variable and GetChr Function............................................................................602
D.1.4 PRxNum Variable and GetDgt Function.......................................................................... 603
D.1.5 PrtFal Variable................................................................................................................. 604
D.1.6 PrtMod, Protcl, and PrtRat Variables............................................................................... 604
D.1.6.1 PrtMod Variable................................................................................................. 604
D.1.6.2 Protcl Variable....................................................................................................605
D.1.6.3 PrtRat Variable...................................................................................................605
D.1.7 Ready and NotRdy Functions..........................................................................................606
D.2 Example of Building Local Communication Processes................................................................. 607
D.2.1 Database Definitions....................................................................................................... 607
D.2.2 Main Process...................................................................................................................609
D.2.3 HeadrP Subprocess........................................................................................................ 609
D.2.4 KeyInP Subprocess......................................................................................................... 610
D.2.5 OutP Subprocess............................................................................................................ 610

25
6802979C10-BA
Contents

Appendix E: User Defined MDLC Communication.......................................................612

E.1 Central-to-RTU Data Transfer....................................................................................................... 612
E.2 Central-to-RTU Broadcast............................................................................................................. 613
E.3 RTU-to-RTU Communication Guidelines.......................................................................................613
E.4 Variables/Constants & Functions Used for MDLC Communication............................................... 614
E.4.1 Variables/Constants.........................................................................................................614
E.4.2 Communication Functions Available via the CALL Function........................................... 614
E.5 Site Table.......................................................................................................................................615
E.6 RTU-to-RTU Communication.........................................................................................................616
E.6.1 RTU-to-RTU Comm Buff / RTU-to-RTU Controls Tables................................................. 616
E.6.2 Last Index (BufEnd)......................................................................................................... 617
E.6.3 Transmit Variables........................................................................................................... 617
E.6.4 Receive Variables............................................................................................................ 617
E.6.5 Transmit Mode................................................................................................................. 619
E.6.6 Receive Mode..................................................................................................................619
E.7 Sequential Frame RTU-to-RTU Communication........................................................................... 620
E.8 RTU Event/Burst Reporting........................................................................................................... 621
E.8.1 TX Event Table................................................................................................................ 621
E.8.2 Event Definitions 1 and Event Definitions 2 Tables......................................................... 622
E.8.3 TxEvnt Function...............................................................................................................622
E.8.4 Data Burst Table.............................................................................................................. 623
E.8.5 Burst Function..................................................................................................................623
E.9 Example of RTU-to-RTU Communication......................................................................................624
E.9.1 Site A Database...............................................................................................................624
E.9.1.1 Internal Values................................................................................................... 624
E.9.1.2 Communication Constants.................................................................................625
E.9.1.3 Communication Timers...................................................................................... 625
E.9.1.4 Discrete Inputs................................................................................................... 626
E.9.1.5 Discrete Outputs................................................................................................ 626
E.9.1.6 Sites................................................................................................................... 626
E.9.2 Site B Database...............................................................................................................626
E.9.3 Site A User Rungs........................................................................................................... 626
E.9.3.1 Internal Values................................................................................................... 628
E.9.3.2 Communication Constants.................................................................................629
E.9.3.3 Communication Timers...................................................................................... 629
E.9.3.4 Discrete Outputs................................................................................................ 629
E.9.3.5 Sites................................................................................................................... 630
E.9.4 Site B User Rungs........................................................................................................... 630
Appendix F: MDLC Communication Protocol.............................................................. 631

26
 6802979C10-BA
Contents

F.1 Physical Layer................................................................................................................................632

F.2 Link Layer.......................................................................................................................................632
F.3 Network Layer................................................................................................................................ 632
F.4 Transportation Layer...................................................................................................................... 633
F.5 Session Layer................................................................................................................................ 633
F.6 Presentation Layer......................................................................................................................... 633
F.7 Application Layer............................................................................................................................634
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration.........................................635
G.1 MC-EDGE/ACE1000 MODBUS Client (Master)........................................................................... 635
G.2 MC-EDGE/ACE1000 MODBUS Server (Slave)............................................................................ 639
G.3 SCADA Polling and Comm Status of ACE1000 RTUs..................................................................644
G.4 Port Configuration for ACE1000/MC-EDGE MODBUS.................................................................645
G.4.1 ACE1000/MC-EDGE Port Configuration in a Mixed System...........................................645
G.4.2 ACE1000/MC-EDGE as MODBUS Server (Slave)......................................................... 645
G.4.3 MC-EDGE/ACE1000 as MODBUS Client (Master).........................................................646
G.4.3.1 MC-EDGE as MODBUS Client (Master)........................................................... 646
G.4.3.2 ACE1000 as MODBUS Client (Master)............................................................. 647
G.4.4 ACE1100 FEP Port Configuration in an ACE1000 System............................................. 647
Appendix H: Key Variable Loader 4000.........................................................................649
H.1 Setting Up Key Variable Loader 4000........................................................................................... 649
Appendix I: MC-EDGE LoRa...........................................................................................651
I.1 Enabling LoRaWAN........................................................................................................................ 651
I.2 LoRaWAN Configuration.................................................................................................................651
I.2.1 Configuring LoRaWAN Devices........................................................................................ 651
I.3 Considerations for Sending and Receiving Device Data................................................................ 652
I.4 MC-EDGE LoRaWAN Backup and Restore....................................................................................653
Appendix J: MC-EDGE Upgrade Tables........................................................................ 654
J.1 MC-EDGE Upgrade Table for ASTRO Users.................................................................................654
J.2 MC-EDGE Upgrade Table for General Purpose Users.................................................................. 655
Appendix K: MC-EDGE NFM Number of Objects Limitation....................................... 657

27
6802979C10-BA
List of Figures

List of Figures
Figure 1: Main Parts of the ACE3600 RTU.......................................................................................................61
Figure 2: Accessing and Modifying RTU Layers...............................................................................................64
Figure 3: RTU Coverage Area.......................................................................................................................... 65
Figure 4: A Simple Central Computer and RTU Connection............................................................................ 70
Figure 5: A Two-Link System............................................................................................................................70
Figure 6: A Multi-Link System...........................................................................................................................71
Figure 7: A Two-Zone System.......................................................................................................................... 71
Figure 8: A Two-Zone System Scheme............................................................................................................ 71
Figure 9: ACE3600 Multiple Zone System........................................................................................................72
Figure 10: ACE3600 Multiple Zone System Scheme....................................................................................... 72
Figure 11: ACE3600 Three-Zone, Two Node System Scheme........................................................................ 73
Figure 12: A Single-Column Table.................................................................................................................... 76
Figure 13: A Multiple-Column Table..................................................................................................................77
Figure 14: STS System View............................................................................................................................79
Figure 15: STS Site View..................................................................................................................................80
Figure 16: STS Graphical User Interface..........................................................................................................84
Figure 17: Colored Site Icons in Diagram View................................................................................................ 87
Figure 18: STS Diagram View with Several Links............................................................................................ 88
Figure 19: Select Links Dialog.......................................................................................................................... 89
Figure 20: STS–Link Information...................................................................................................................... 89
Figure 21: STS Table View............................................................................................................................... 90
Figure 22: Advanced Filtering and Sorting Form.............................................................................................. 91
Figure 23: Matches in the Advanced Filtering and Sorting Form......................................................................92
Figure 24: Select Columns Context Menu........................................................................................................ 93
Figure 25: Select Columns List of Items........................................................................................................... 94
Figure 26: System Tab......................................................................................................................................94
Figure 27: STS System Path Bar......................................................................................................................95
Figure 28: Selecting a Component in Table View............................................................................................. 96
Figure 29: Creating a New STS Project............................................................................................................98
Figure 30: Adding Files to Areas.................................................................................................................... 100
Figure 31: Removing Files from Areas........................................................................................................... 101
Figure 32: Add RTU Dialog with ACE 3600 CPU 3640 Selected................................................................... 102
Figure 33: STS System Tab............................................................................................................................104
Figure 34: Add RTU Dialog with IRRInet-M/AC Selected...............................................................................105
Figure 35: Add RTU Dialog for MC-EDGE......................................................................................................106
Figure 36: Add RTU Dialog for ACE 4600...................................................................................................... 108

28
 6802979C10-BA
List of Figures

Figure 37: Port Configuration Example: ACE3640......................................................................................... 110

Figure 38: Port Configuration Example: ACE3680 Without Redundancy....................................................... 110
Figure 39: Port Configuration Example: ACE3680 with Redundancy Enabled............................................... 111
Figure 40: Port Configuration Example: ACE1000..........................................................................................111
Figure 41: Port Configuration Example: MC-EDGE with APX........................................................................ 112
Figure 42: Port Configuration Example: IRRInet-M RTU................................................................................ 112
Figure 43: Port Configuration Example: ACE3600 with Ethernet Port Configured......................................... 113
Figure 44: ACE3600 Site Configuration - I/O Tab........................................................................................... 114
Figure 45: ACE3600 with Manually Defined I/O Modules...............................................................................115
Figure 46: Advanced Configuration Dialog – Example 1................................................................................ 115
Figure 47: Advanced Configuration Dialog – Example 2................................................................................ 116
Figure 48: Advanced Configuration Dialog – Example 3................................................................................ 116
Figure 49: Advanced Configuration Dialog – Example 4................................................................................ 116
Figure 50: Advanced Configuration Dialog – Example 5................................................................................ 117
Figure 51: Modify Expansion Frames Dialog.................................................................................................. 118
Figure 52: Accessing the Advanced Main Frame Parameters .......................................................................118
Figure 53: Main Frame - Advanced.................................................................................................................119
Figure 54: Power Supply Configuration Dialog............................................................................................... 119
Figure 55: Switch Connections Dialog............................................................................................................120
Figure 56: Select Frames to Copy from Main Frame Dialog.......................................................................... 121
Figure 57: MC-EDGE (v19.00 or Newer) Site Configuration - I/O Tab........................................................... 122
Figure 58: MC-EDGE (v19.00 or Newer) with Defined I/O Modules...............................................................122
Figure 59: Advanced Configuration Dialog – Example 1................................................................................ 123
Figure 60: Advanced Configuration Dialog – Example 2................................................................................ 124
Figure 61: Configuring the I/O Parameters of an IRRInet-M Site................................................................... 125
Figure 62: ASTRO Panel................................................................................................................................ 126
Figure 63: NFM Devices Tab.......................................................................................................................... 127
Figure 64: Site Configuration View–Advanced Tab........................................................................................ 129
Figure 65: Add-Ons List in the STS Site View................................................................................................ 130
Figure 66: NFM Devices – RFDS................................................................................................................... 131
Figure 67: RFDS Configuration Control..........................................................................................................131
Figure 68: Add RFDS Device Window............................................................................................................132
Figure 69: Warning Message on the Exceeded Number of Network Elements..............................................132
Figure 70: RFDS Parameters Window........................................................................................................... 133
Figure 71: RFDS Site......................................................................................................................................134
Figure 72: Add RFTS to Gallery..................................................................................................................... 134
Figure 73: Gallery Section.............................................................................................................................. 135
Figure 74: Select Links Dialog........................................................................................................................ 135
Figure 75: STS–Link Information.................................................................................................................... 136

29
6802979C10-BA
List of Figures

Figure 76: Site View–Legacy MOSCAD Device............................................................................................. 137

Figure 77: Importing Legacy Site Configuration............................................................................................. 138
Figure 78: STS Communication Setup........................................................................................................... 139
Figure 79: STS Communication Setup Advanced Parameters.......................................................................141
Figure 80: Example of MDLC Driver Console Tooltip..................................................................................... 143
Figure 81: CPS Mode Dialog.......................................................................................................................... 144
Figure 82: ACE3600 Site Download Dialog....................................................................................................148
Figure 83: IRRInet-M Site Download Dialog...................................................................................................148
Figure 84: ACE3600 System File Settings Dialog.......................................................................................... 149
Figure 85: IRRInet-M Download Settings Dialog............................................................................................ 149
Figure 86: IRRInet-M Pre-Download Prompt..................................................................................................150
Figure 87: STS – Site Download Dialog......................................................................................................... 152
Figure 88: Site Download Dialog with List of Available Files.......................................................................... 154
Figure 89: STS–Site Download Dialog with Various Files.............................................................................. 155
Figure 90: Site Configuration Settings Dialog.................................................................................................156
Figure 91: Ladder Application Setting Dialog................................................................................................. 156
Figure 92: Adding Files to a Site Source........................................................................................................ 157
Figure 93: STS–Upload Dialog....................................................................................................................... 160
Figure 94: STS–Site Upload Dialog................................................................................................................161
Figure 95: Change RTU Version Dialog..........................................................................................................162
Figure 96: Upgrade Information Prompt......................................................................................................... 162
Figure 97: Application Version and Site Version Mismatch............................................................................ 162
Figure 98: Closing an STS Project – Example 1............................................................................................ 164
Figure 99: Closing an STS Project – Example 2............................................................................................ 164
Figure 100: STS–Open Project Dialog........................................................................................................... 165
Figure 101: Upgrading Project to Newer STS Version................................................................................... 166
Figure 102: STS – Application Manager.........................................................................................................167
Figure 103: Naming the Upgraded Application...............................................................................................168
Figure 104: Set MDLC Link Costs Dialog....................................................................................................... 169
Figure 105: STS – Network Manager............................................................................................................. 170
Figure 106: Editing a Table in The Network Configuration Editor................................................................... 172
Figure 107: MDLC Links Configuration Utility.................................................................................................174
Figure 108: STS – IP Conversion Table File Manager................................................................................... 176
Figure 109: IP Conversion Table Editor.......................................................................................................... 178
Figure 110: STS – Add-On Manager.............................................................................................................. 181
Figure 111: Encrypted 'C' Application Parameters..........................................................................................185
Figure 112: IRRInet Client (Master) Site Table............................................................................................... 187
Figure 113: ACE IP Gateway Site Table......................................................................................................... 188
Figure 114: STS – Site Table File Manager.................................................................................................... 189

30
 6802979C10-BA
List of Figures

Figure 115: Editing an IP Gateway Site Table................................................................................................ 192

Figure 116: Editing an RTU Site Table............................................................................................................194
Figure 117: Append Group of Sites Dialog (RTU Site Table)..........................................................................196
Figure 118: Append Group of Sites Dialog (IP Gateway Site Table).............................................................. 196
Figure 119: STS – DNP File Manager............................................................................................................ 198
Figure 120: DNP Client (Master) Configuration Editor....................................................................................199
Figure 121: Initiating Field View of Locally Connected RTU...........................................................................201
Figure 122: STS–Field View........................................................................................................................... 202
Figure 123: STS–Upload New Site Dialog......................................................................................................203
Figure 124: STS–Upload New Site Dialog......................................................................................................203
Figure 125: STS–Site Exist Dialog................................................................................................................. 204
Figure 126: STS–Site Upload Dialog..............................................................................................................205
Figure 127: STS–Download All Sites Dialog.................................................................................................. 206
Figure 128: STS–Change MDLC Password Dialog........................................................................................209
Figure 129: STS–Change MDLC Password Dialog........................................................................................210
Figure 130: Confirming the MDLC Password Change....................................................................................210
Figure 131: Override MDLC Password Dialog................................................................................................212
Figure 132: Communication Settings Dialog.................................................................................................. 212
Figure 133: SSH Keys Dialog Box..................................................................................................................214
Figure 134: SSH Known Hosts List - Dialog Warning.....................................................................................215
Figure 135: Change Linux User Passwords Dialog Box.................................................................................216
Figure 136: SSHForcePassword Dialog Box..................................................................................................217
Figure 137: SNMP User Credentials Dialog Box............................................................................................ 218
Figure 138: PKI Configuration Editor.............................................................................................................. 221
Figure 139: STS Site ID Change Prompt........................................................................................................225
Figure 140: STS–SW Diagnostics and Loggers Utility................................................................................... 227
Figure 141: Retrieving the Log from a Site..................................................................................................... 228
Figure 142: Recent Logs – Error Logging.......................................................................................................229
Figure 143: SW Diagnostics and Loggers Utility–Diagnostics Tab................................................................. 230
Figure 144: Retrieving Diagnostics from a Site.............................................................................................. 231
Figure 145: Recent Logs – Diagnostics..........................................................................................................232
Figure 146: SW Diagnostics and Loggers Utility–Time Tag Tab..................................................................... 233
Figure 147: Retrieving Time Tag Events from a Site...................................................................................... 234
Figure 148: Recent Logs – Time-Tagged Events............................................................................................235
Figure 149: Site Date & Time Dialog.............................................................................................................. 235
Figure 150: RTU Modem Connection Diagram (Example)............................................................................. 238
Figure 151: Phonebook Editor........................................................................................................................ 241
Figure 152: Entering Phone Numbers in the Phonebook Editor.....................................................................241
Figure 153: STS Dialup Utility.........................................................................................................................242

31
6802979C10-BA
List of Figures

Figure 154: Paste Site Dialog......................................................................................................................... 246

Figure 155: Paste Site Dialog in Secured STS...............................................................................................247
Figure 156: Paste Site Dialog for Single Peer................................................................................................ 248
Figure 157: Paste Site Dialog for Both Peers................................................................................................. 249
Figure 158: Paste Site Dialog (Redundant) in Secured STS..........................................................................250
Figure 159: Select Area Dialog.......................................................................................................................251
Figure 160: Assign Parent Area Files Warning...............................................................................................251
Figure 161: STS Table Monitor–MC-EDGE Digital Inputs.............................................................................. 254
Figure 162: STS Table Monitor–MC-EDGE Digital Outputs........................................................................... 255
Figure 163: STS Table Monitor–MC-EDGE Analog Inputs............................................................................. 256
Figure 164: STS Table Monitor–MC-EDGE Analog Outputs.......................................................................... 257
Figure 165: Monitoring an IRRInet-M Site...................................................................................................... 258
Figure 166: STS Table Monitor–Connecting to RTU.......................................................................................259
Figure 167: Monitoring a Small Block of Values............................................................................................. 260
Figure 168: Read RTU Dialog.........................................................................................................................268
Figure 169: Hardware Test–ACE3600 Site with Expansion Frames and Modules.........................................268
Figure 170: Hardware Test–IRRInet-M Site with Expansion...........................................................................269
Figure 171: ACE3600 Module Diagnostics.....................................................................................................270
Figure 172: IRRInet-M DC (Main and Expansion) Module Diagnostics..........................................................270
Figure 173: IRRInet-M AC Module Diagnostics..............................................................................................271
Figure 174: Testing a Module Power Supply.................................................................................................. 272
Figure 175: Updating the FPGA File...............................................................................................................273
Figure 176: Testing ACE3600 Digital Inputs................................................................................................... 274
Figure 177: Testing IRRInet-M Digital Inputs.................................................................................................. 274
Figure 178: DI Filter Dialog.............................................................................................................................275
Figure 179: DI Counters Filter Dialog............................................................................................................. 275
Figure 180: Testing ACE3600 Digital Outputs on a Mixed I/O Module........................................................... 276
Figure 181: Testing ACE3600 Digital Outputs on an Output Module..............................................................277
Figure 182: Testing IRRInet-M DC Digital Outputs......................................................................................... 277
Figure 183: Testing IRRInet-M AC Digital Outputs......................................................................................... 278
Figure 184: Testing ACE3600 Analog Inputs..................................................................................................280
Figure 185: Analog Input Calibration Factors................................................................................................. 280
Figure 186: Calibrate AI Dialog.......................................................................................................................281
Figure 187: AI Filter Dialog............................................................................................................................. 281
Figure 188: AI Diff. Mode Filter Dialog............................................................................................................282
Figure 189: Testing ACE3600 Analog Outputs............................................................................................... 283
Figure 190: Analog Output Calibration Factors.............................................................................................. 284
Figure 191: Calibrate AO Dialog.....................................................................................................................284
Figure 192: Testing an ACE3600 Expansion LAN Switch.............................................................................. 286

32
 6802979C10-BA
List of Figures

Figure 193: Testing an ACE3600 Main CPU.................................................................................................. 290

Figure 194: Testing an ACE3600 Expansion Module CPU.............................................................................290
Figure 195: Testing an ACE IP Gateway CPU................................................................................................291
Figure 196: Testing an IRRInet-M CPU.......................................................................................................... 291
Figure 197: Deactivating the CPU in a Redundant Site..................................................................................292
Figure 198: ACE3600 LEDs........................................................................................................................... 295
Figure 199: ACE IP Gateway LEDs................................................................................................................295
Figure 200: IRRInet-M LEDs.......................................................................................................................... 296
Figure 201: ACE3610 LEDs State.................................................................................................................. 296
Figure 202: ACE3680 LEDs State.................................................................................................................. 297
Figure 203: ACE IP Gateway LEDs State...................................................................................................... 297
Figure 204: ACE3600 Expansion CPU LEDs State........................................................................................298
Figure 205: IRRInet-M LEDs – CPU Page..................................................................................................... 298
Figure 206: Testing the ACE3600 Power Supply............................................................................................300
Figure 207: IRRInet-M AC Power Diagnostics............................................................................................... 302
Figure 208: IRRInet-M DC Power Diagnostics............................................................................................... 302
Figure 209: Hardware Test Utility – Plug-Ins Tab............................................................................................307
Figure 210: Hardware Test Utility – Port 3 Tab............................................................................................... 308
Figure 211: Hardware Test – Wakeup Events Tab (IRRInet-M)...................................................................... 309
Figure 212: Expansion Loader Dialog............................................................................................................ 310
Figure 213: Add IO Module to Site Dialog...................................................................................................... 312
Figure 214: Add IO Group from Gallery Prompt............................................................................................. 313
Figure 215: Add Port to Site Dialog................................................................................................................ 313
Figure 216: Add New Item Dialog...................................................................................................................315
Figure 217: Gallery Source Dialog..................................................................................................................316
Figure 218: Import Gallery Dialog...................................................................................................................317
Figure 219: STS Inventory – FEP...................................................................................................................318
Figure 220: STS Inventory – RTU...................................................................................................................319
Figure 221: STS Inventory – Ports................................................................................................................. 319
Figure 222: STS Inventory – IO – ACE1000...................................................................................................320
Figure 223: STS Inventory – IO – ACE3600...................................................................................................320
Figure 224: STS Inventory – IO – MC-EDGE................................................................................................. 321
Figure 225: STS Inventory – NFM devices – RFDS Templates......................................................................321
Figure 226: STS – Parameters to Export Dialog............................................................................................ 322
Figure 227: Application Programmer in STS Mode........................................................................................ 324
Figure 228: Application Programmer – New Application Dialog..................................................................... 327
Figure 229: ACE 3600 System Tables............................................................................................................330
Figure 230: MC-EDGE System Tables........................................................................................................... 330
Figure 231: ACE3600 Constant Tables.......................................................................................................... 331

33
6802979C10-BA
List of Figures

Figure 232: Table Form (Single-Column Table).............................................................................................. 335

Figure 233: Table Form (Multiple-Column Table)............................................................................................337
Figure 234: Attribute Page Handle................................................................................................................. 339
Figure 235: Application Programmer – Find Dialog........................................................................................340
Figure 236: Paste Report Dialog.................................................................................................................... 341
Figure 237: Example 1: Single-Column Table Definition................................................................................ 343
Figure 238: Example 2: Multiple-Column Table Definition.............................................................................. 344
Figure 239: Process Tree............................................................................................................................... 345
Figure 240: Rung Without Elements...............................................................................................................347
Figure 241: Rung Element List....................................................................................................................... 347
Figure 242: Rung Element (Highlighted) in the Workspace............................................................................348
Figure 243: Select Element Dialog – Input Tab.............................................................................................. 349
Figure 244: Select Element Dialog – Output Tab............................................................................................349
Figure 245: Highlighted Link Between Two Elements.................................................................................... 350
Figure 246: Select Element Dialog – Input..................................................................................................... 352
Figure 247: Greater Than Comparator Input Element with Two Parameters................................................. 354
Figure 248: SUB Operation Output Element with Three Parameters............................................................. 354
Figure 249: CALL Operator............................................................................................................................ 354
Figure 250: UCL Operator.............................................................................................................................. 355
Figure 251: CALC Operator............................................................................................................................355
Figure 252: SEND Operator........................................................................................................................... 355
Figure 253: Rung Elements with Undefined Parameters................................................................................355
Figure 254: Assigning a Database Symbol to an Element............................................................................. 356
Figure 255: Rung Element with Assigned Database Symbol......................................................................... 356
Figure 256: Looking Up an Element Parameter............................................................................................. 357
Figure 257: Long Description Dialog.............................................................................................................. 358
Figure 258: Short Description Dialog..............................................................................................................359
Figure 259: Application Programmer – Find Dialog........................................................................................360
Figure 260: Context Menu with Find in Rungs Command.............................................................................. 361
Figure 261: Example 1 Rung Sequences....................................................................................................... 362
Figure 262: Example 2 Rung Sequences....................................................................................................... 362
Figure 263: I/O Link Tree................................................................................................................................ 363
Figure 264: I/O Link Column Definition Table................................................................................................. 364
Figure 265: Application Programmer – Select Site Dialog..............................................................................366
Figure 266: I/O Information Tab in the Output Bar..........................................................................................366
Figure 267: Setting the COS Delta Value....................................................................................................... 367
Figure 268: Connect Group of Elements Dialog............................................................................................. 368
Figure 269: Quick Find Symbol Dialog........................................................................................................... 371
Figure 270: Application Settings Dialog..........................................................................................................374

34
 6802979C10-BA
List of Figures

Figure 271: Application Programmer Connection Bar.................................................................................... 377

Figure 272: Database Table in Edit Mode.......................................................................................................378
Figure 273: Database Table in Monitor Mode.................................................................................................378
Figure 274: Selecting the Table Monitor Display Format................................................................................ 379
Figure 275: Application Programmer Connection Bar.................................................................................... 380
Figure 276: Monitoring a Rung....................................................................................................................... 381
Figure 277: Rung Monitoring – Watch Panel.................................................................................................. 381
Figure 278: Qualifier Table..............................................................................................................................382
Figure 279: Application Programmer Connection Bar.................................................................................... 383
Figure 280: Performance Monitor Table......................................................................................................... 384
Figure 281: BlocksToBackUp Table in the Database Tree..............................................................................385
Figure 282: Application Tables Conversion Report.........................................................................................390
Figure 283: Print Application Dialog............................................................................................................... 391
Figure 284: SNMPv3 - MCIOT User............................................................................................................... 496
Figure 285: Rung 1......................................................................................................................................... 547
Figure 286: Rung 2......................................................................................................................................... 547
Figure 287: Single-Column Table................................................................................................................... 560
Figure 288: Multiple-Column Table................................................................................................................. 561
Figure 289: System Tables............................................................................................................................. 563
Figure 290: Constant Tables...........................................................................................................................564
Figure 291: Time & Date Table....................................................................................................................... 565
Figure 292: Years Table.................................................................................................................................. 566
Figure 293: Months Table............................................................................................................................... 566
Figure 294: Dates Table..................................................................................................................................567
Figure 295: Days Table...................................................................................................................................567
Figure 296: Fans Table................................................................................................................................... 569
Figure 297: Reserved Flags Table..................................................................................................................572
Figure 298: Reserved Values Table................................................................................................................577
Figure 299: Expansion Reserved Flags Table................................................................................................ 582
Figure 300: User Ports Table.......................................................................................................................... 598
Figure 301: ASCII Characters.........................................................................................................................603
Figure 302: User Port Modes Table................................................................................................................ 604
Figure 303: User Port Protocols Table............................................................................................................605
Figure 304: User Port Baud Rates Table........................................................................................................ 606
Figure 305: Internal Variables Table............................................................................................................... 607
Figure 306: Internal Parameters Table........................................................................................................... 608
Figure 307: Internal Constants Table..............................................................................................................608
Figure 308: Site Table.....................................................................................................................................615
Figure 309: RTU to RTU Comm Buff Table.................................................................................................... 617

35
6802979C10-BA
List of Figures

Figure 310: RTU-RTU Frame Types Table..................................................................................................... 618

Figure 311: Tx Event Table............................................................................................................................. 621
Figure 312: Event Definitions Table................................................................................................................ 622
Figure 313: Data Burst Table.......................................................................................................................... 623
Figure 314: Internal Variable Table................................................................................................................. 625
Figure 315: Comm Constants Table............................................................................................................... 625
Figure 316: Comm Timers Table.....................................................................................................................625
Figure 317: Buttons Table...............................................................................................................................626
Figure 318: Internal Variables Table............................................................................................................... 628
Figure 319: Comm Constants Table............................................................................................................... 629
Figure 320: Comm Timers Table.....................................................................................................................629
Figure 321: LEDs Table.................................................................................................................................. 629
Figure 322: MODBUS Client (Master) – MODBUS Server (Slave)................................................................ 635
Figure 323: MODBUS Client (Master) Configuration Editor........................................................................... 636
Figure 324: SI and PI Ports Configured as MODBUS Server (Slave)............................................................ 645
Figure 325: ETH1 Port with MODBUS Protocol Support Enabled..................................................................646
Figure 326: MODBUS Server (Slave) Advanced Port Parameters.................................................................646
Figure 327: SI1 Port Configured as MODBUS Client (Master).......................................................................646
Figure 328: ETH1 Port Configured as MODBUS Client (Master)................................................................... 646
Figure 329: SI2 Port Configured as MODBUS Client (Master).......................................................................646
Figure 330: SI and PI Ports Configured as User Port.....................................................................................647
Figure 331: Standard ACE1000 RTU Ethernet Port Configuration.................................................................647
Figure 332: ACE1100 as MODBUS Server (Slave) Connected to SCADA Center........................................ 648
Figure 333: APX Port Configuration............................................................................................................... 649
Figure 334: Connecting the OTG Cable......................................................................................................... 650
Figure 335: STS – Communication Setup Dialog........................................................................................... 650

36
 6802979C10-BA
List of Tables

List of Tables
Table 1: Reserved IP Addresses...................................................................................................................... 75
Table 2: STS Tools............................................................................................................................................81
Table 3: STS User Interface..............................................................................................................................84
Table 4: Icons in the STS Menu Bar................................................................................................................. 85
Table 5: Icons Available in the STS System View.............................................................................................85
Table 6: Icons Available in the STS Site View.................................................................................................. 86
Table 7: Site Customization............................................................................................................................ 109
Table 8: ACE3600 Automatic Expansion Frame Switch Connection Configuration....................................... 120
Table 9: ASTRO Panel on the General Tab.................................................................................................... 126
Table 10: Legacy Site Configuration File Types..............................................................................................137
Table 11: ACE3600 System File Settings....................................................................................................... 149
Table 12: IRRInet-M Download Settings.........................................................................................................149
Table 13: Deselected Blocks During Non-Firmware File Download............................................................... 154
Table 14: Download Unit Reset and Flash Erase Parameters........................................................................159
Table 15: IP Conversion Table Editor Functions............................................................................................. 179
Table 16: Add-On Files for ACE3600 RTU Type.............................................................................................182
Table 17: Add-On Files per Legacy RTU Type............................................................................................... 183
Table 18: Add-On Files for IRRInet-M RTU Type............................................................................................183
Table 19: Add-On Files for ACE1000 RTU Type.............................................................................................184
Table 20: Add-On Files for MC-EDGE RTU Type2.........................................................................................184
Table 21: STS Site Table Types......................................................................................................................187
Table 22: PKI Configuration Editor Parameters.............................................................................................. 222
Table 23: Hayes Smart Modem 1200 Jumpers Settings.................................................................................238
Table 24: Jumpers Settings of the Modem Connected to the Central............................................................ 238
Table 25: Dial-Up Parameters.........................................................................................................................239
Table 26: Results of Site Definition Upload.....................................................................................................244
Table 27: ACE1000/MC-EDGE/IRRInet-EDGE STS Table Monitor Screens................................................. 262
Table 28: MOSCAD-M/IRRInet-M STS Table Monitor Screens...................................................................... 263
Table 29: MOSCAD-M/IRRInet-M STS Table Monitor Inputs Screen Fields.................................................. 264
Table 30: MOSCAD-M/IRRInet-M STS Table Monitor Outputs Screen Fields................................................265
Table 31: MOSCAD-M/IRRInet-M STS Table Monitor Reserved Bits/Values Screen Fields.......................... 265
Table 32: MOSCAD-M/IRRInet-M STS Table Monitor Power Supply Switches Screen Fields.......................265
Table 33: MOSCAD-M/IRRInet-M STS Table Monitor Power Management Status Screen Fields.................266
Table 34: MOSCAD-M/IRRInet-M STS Table Monitor Time & Date Screen Fields........................................ 266
Table 35: ACE3600 I/O Module and Expansion LAN Switch Parameters...................................................... 286
Table 36: IRRInet-M DC and IRRInet-M AC I/O Module Parameters............................................................. 286

37
6802979C10-BA
List of Tables

Table 37: Digital IOs Tab – Digital Inputs........................................................................................................ 287

Table 38: Digital IOs Tab – Digital Outputs..................................................................................................... 287
Table 39: Analog Inputs Tab........................................................................................................................... 288
Table 40: Analog Inputs Tab – Calibration Factors......................................................................................... 288
Table 41: Analog Outputs Tab.........................................................................................................................288
Table 42: Analog Outputs Tab – Calibration Fields.........................................................................................289
Table 43: Analog Outputs Tab – Calibration Factors...................................................................................... 289
Table 44: ACE3600 Main CPU/ACE IP Gateway Test Parameters................................................................ 292
Table 45: ACE3600 I/O Expansion Module Test Parameters......................................................................... 293
Table 46: IRRInet-M CPU Test Parameters.................................................................................................... 294
Table 47: ACE3600 LED Operations.............................................................................................................. 299
Table 48: IRRInet-M LED Operations............................................................................................................. 299
Table 49: ACE3600 Power Supply – Power Switches.................................................................................... 303
Table 50: ACE3600 Power Supply ROM Data (AC/DC Power Supplies)....................................................... 304
Table 51: ACE3600 Power Supply ROM Data (12V DC Low-Tier and Expansion Power Supplies).............. 305
Table 52: IRRInet-M Power Diagnostics......................................................................................................... 306
Table 53: Wakeup Events for IRRInet-M RTU................................................................................................ 309
Table 54: STS Inventory Elements Grouped by Folder.................................................................................. 318
Table 55: Parameters to Export...................................................................................................................... 322
Table 56: Single-Column Database Table Columns....................................................................................... 331
Table 57: Example 1: Database Table Characteristics................................................................................... 342
Table 58: Example 2: Database Table Columns............................................................................................. 344
Table 59: I/O Link Definition Table Parameters...............................................................................................365
Table 60: ACE 3600 I/O Definitions................................................................................................................ 370
Table 61: MC EDGE I/O Definitions................................................................................................................370
Table 62: Summary of Table Monitor Commands...........................................................................................379
Table 63: Summary of Rung Monitor Commands...........................................................................................382
Table 64: Description of System Performance Monitoring Variables.............................................................. 384
Table 65: BlocksToBackup Table Parameters.................................................................................................386
Table 66: Keyboard Commands in Application Programming........................................................................ 392
Table 67: ACE3600 SI1 Port Parameters....................................................................................................... 396
Table 68: ACE1000/MC-EDGE SI1 Port Parameters..................................................................................... 397
Table 69: ACE3600 SI1 Port Configurations...................................................................................................398
Table 70: ACE1000/MC-EDGE SI1 Port Configurations.................................................................................399
Table 71: Link Parameters for SI1 Port...........................................................................................................400
Table 72: Advanced Physical Parameters for SI1 Port (General)...................................................................403
Table 73: Advanced Physical Parameters for SI1 Port (External Modem)..................................................... 403
Table 74: Advanced Physical Parameters for SI1 Port (External Dial-Up Modem)........................................ 405
Table 75: Advanced Physical Parameters for SI1 Port (GPS Receiver).........................................................406

38
 6802979C10-BA
List of Tables

Table 76: Advanced Physical Parameters for SI1 Port (PPP Connections)................................................... 406
Table 77: Advanced Link Parameters for SI1 Port (General)..........................................................................408
Table 78: Advanced Link Parameters for SI1 Port (GPS Receivers)..............................................................410
Table 79: Advanced Link Parameters for SI1 Port (PPP Connections).......................................................... 411
Table 80: Advanced Link Parameters for SI1 Port (PPP – iDEN Modem)......................................................414
Table 81: Advanced Link Parameters for SI1 Port (PPP – ASTRO IV&D)..................................................... 415
Table 82: PLC Parameters for SI1 Port.......................................................................................................... 416
Table 83: Available Media Types for ACE3600 PI1/PI2 Ports........................................................................ 421
Table 84: ACE3600 PI1/PI2 Port Parameters for Conventional Radio........................................................... 421
Table 85: ACE3600 PI1/PI2 Port Parameters for Trunked Radio................................................................... 422
Table 86: ACE3600 PI1/PI2 Port Parameters for RS-232 Media, Sync Mode................................................422
Table 87: ACE3600 PI1/PI2 Port Parameters for 10/100 BT Media............................................................... 423
Table 88: ACE3600 Additional PI1/PI2 Port Configurations........................................................................... 423
Table 89: RS485 Port Configurations for ACE1000 PI2 Port..........................................................................424
Table 90: Additional Link Parameters for PI1/PI2 Ports..................................................................................425
Table 91: Additional Advanced Physical Parameters for PI1/PI2 Ports (Miscellaneous)................................427
Table 92: Additional Advanced Physical Parameters for PI1/PI2 Ports (Radio)............................................. 427
Table 93: Additional Advanced Physical Parameters for PI1/PI2 Ports (DHCP Client).................................. 428
Table 94: Additional Advanced Physical Parameters for PI1/PI2 Ports (XRT Gateway)................................ 429
Table 95: Additional Advanced Link Parameters for PI1/PI2 Ports ................................................................429
Table 96: ETH1/ETH2/ETH3 Port Parameters............................................................................................... 430
Table 97: General ETH1/ETH2/ETH3 Port Configurations............................................................................. 431
Table 98: MC-EDGE Ethernet IPsec Port Configurations...............................................................................431
Table 99: Advanced IPsec Parameters...........................................................................................................432
Table 100: Advanced IPSec Optional Tunnel 1-3 Parameters........................................................................434
Table 101: Phase 1 Authentication Methods and Requirements.................................................................... 435
Table 102: Protocols over ETH1/ETH2/ETH3 Ports....................................................................................... 436
Table 103: HU1/HU2 Port Parameters............................................................................................................436
Table 104: HU1/HU2 Port Configurations....................................................................................................... 437
Table 105: Advanced Physical Parameters for HU1/HU2 Ports (General)..................................................... 437
Table 106: Advanced Physical Parameters for HU1/HU2 Ports (Serial USB Host)........................................438
Table 107: HU1/HU2 Advanced Link Parameters for MotoTrbo Connect Plus...............................................439
Table 108: Port USB1/USB2/USB Parameters...............................................................................................440
Table 109: MC-EDGE USB and ACE1000 USB1/USB2 Port Configurations.................................................440
Table 110: Port APX Configurations................................................................................................................441
Table 111: MC-EDGE LTE Port Parameters................................................................................................... 441
Table 112: Advanced Physical Parameters for LTE Port................................................................................ 442
Table 113: Port Protocols for MC-EDGE LTE Port..........................................................................................443
Table 114: DU1 Port Parameters.................................................................................................................... 444

39
6802979C10-BA
List of Tables

Table 115: DU1 Port Configurations................................................................................................................444

Table 116: Link Parameters for DU1 Port....................................................................................................... 444
Table 117: INTR1 Port Parameters.................................................................................................................445
Table 118: INTR1 Port Configurations............................................................................................................ 446
Table 119: TSPx Port Parameters...................................................................................................................446
Table 120: TSPx Port Configurations..............................................................................................................447
Table 121: Link Parameters for TSPx............................................................................................................. 447
Table 122: Advanced Physical Parameters for TSPx..................................................................................... 448
Table 123: LoRa Port Parameters.................................................................................................................. 448
Table 124: LoRa Port Configurations..............................................................................................................449
Table 125: LoRaWAN Advanced Parameters.................................................................................................449
Table 126: LoRa Gateway Advanced Parameters..........................................................................................450
Table 127: ACE3600 DI Parameters...............................................................................................................450
Table 128: ACE3600 DO Parameters.............................................................................................................451
Table 129: ACE3600 AI Parameters...............................................................................................................451
Table 130: ACE1000/MC-EDGE DI Parameters.............................................................................................452
Table 131: Severity Levels..............................................................................................................................453
Table 132: ACE1000/MC-EDGE DO Parameters...........................................................................................453
Table 133: ACE1000 AI Parameters...............................................................................................................454
Table 134: ACE1000/MC-EDGE AO Parameters........................................................................................... 455
Table 135: ACE3600 "C" Application Parameters.......................................................................................... 456
Table 136: ACE3600 Core Dump Parameters................................................................................................458
Table 137: ACE3600 DNS Client Parameters................................................................................................ 459
Table 138: MC-EDGE DNS Service Parameters ........................................................................................... 459
Table 139: MC-EDGE DNS Service Parameters: Servers..............................................................................460
Table 140: ACE3600 Dynamic IP Routing Parameters.................................................................................. 461
Table 141: ACE3600/ACE1000/MC-EDGE Dynamic Site Table Parameters................................................. 462
Table 142: ACE3600 Error Logger Parameters.............................................................................................. 462
Table 143: ACE3600 Fast Event Parameters................................................................................................. 463
Table 144: ACE3600 Firewall & Hardening Parameters.................................................................................463
Table 145: MC-EDGE Firewall & Hardening Parameters............................................................................... 466
Table 146: ACE3600 Formatter Parameters...................................................................................................466
Table 147: ACE3600/ACE1000/MC-EDGE Frame Sequence Application Parameters..................................467
Table 148: ACE3600/ACE1000/MC-EDGE Frame Sequence Layer Parameters.......................................... 467
Table 149: ACE3600 Gap Ratio Parameters.................................................................................................. 469
Table 150: System Resources........................................................................................................................ 469
Table 151: Task Allocation.............................................................................................................................. 469
Table 152: Requests Allocation...................................................................................................................... 470
Table 153: Flags............................................................................................................................................. 470

40
 6802979C10-BA
List of Tables

Table 154: ACE3600 Hardware Test Parameters........................................................................................... 471

Table 155: ACE3600/ACE1000/MC-EDGE Heap Parameters....................................................................... 471
Table 156: ACE3600 I/O Parameters............................................................................................................. 472
Table 157: ACE3600 I/O Expansion Parameters............................................................................................473
Table 158: ACE3600 I/O Expansion Manager Parameters............................................................................ 474
Table 159: ACE3600/ACE1000/MC-EDGE IP Conversion Table Parameters................................................478
Table 160: MC-EDGE LEDs Management Parameters..................................................................................479
Table 161: MC-EDGE MDLC GW API Parameter.......................................................................................... 479
Table 162: MQTT Parameters........................................................................................................................ 479
Table 163: ACE3600/ACE1000/MC-EDGE Minisession Parameters............................................................. 481
Table 164: Minisession Broadcasts................................................................................................................ 482
Table 165: Minisession Event and Burst.........................................................................................................482
Table 166: Minisession RTU to RTU...............................................................................................................483
Table 167: Minisession Authentication Client................................................................................................. 484
Table 168: Minisession Authentication Server................................................................................................ 484
Table 169: ACE3600 NTP Parameters........................................................................................................... 485
Table 170: MC-EDGE NTP Service Parameters............................................................................................ 487
Table 171: ACE3600/ACE1000/MC-EDGE Network Parameters...................................................................488
Table 172: ACE3600 PLC Heap Parameters..................................................................................................489
Table 173: ACE3600 PLC MOSCAD as Client (Master) Parameters............................................................. 489
Table 174: ACE3600 PPP Parameters........................................................................................................... 490
Table 175: ACE3600 Power Management Parameters.................................................................................. 490
Table 176: ACE3600/ACE1000 Power Supply Parameters............................................................................491
Table 177: ACE3600 RISC Timers Parameters..............................................................................................493
Table 178: ACE3600 Redundancy Parameters.............................................................................................. 493
Table 179: MC-EDGE Radius Client Parameters........................................................................................... 493
Table 180: MC-EDGE SNMP Agent Parameters............................................................................................495
Table 181: Authentication Level......................................................................................................................496
Table 182: Apply Settings............................................................................................................................... 496
Table 183: ACE3600/ACE1000/MC-EDGE Session Parameters................................................................... 497
Table 184: Static Route (MC-EDGE).............................................................................................................. 499
Table 185: MC-EDGE Syslog Client Parameters............................................................................................499
Table 186: ACE3600/ACE1000/MC-EDGE Time Sync Parameters............................................................... 500
Table 187: ACE3600 Time Tag Parameters....................................................................................................501
Table 188: ACE3600/ACE1000/MC-EDGE Time Zone Parameters...............................................................501
Table 189: ACE3600 Timer Event Parameters............................................................................................... 502
Table 190: ACE3600/ACE1000/MC-EDGE Timer Service Parameters..........................................................503
Table 191: ACE3600 USB Parameters...........................................................................................................505
Table 192: ACE3600 User Application Parameters........................................................................................ 505

41
6802979C10-BA
List of Tables

Table 193: Ladder Processes Tasks Parameters........................................................................................... 506

Table 194: Database Backup Parameters...................................................................................................... 507
Table 195: IRRInet-M Port 1 Configurations................................................................................................... 507
Table 196: IRRInet-M Port 1 Parameters........................................................................................................508
Table 197: IRRInet-M Port 2 Parameters........................................................................................................509
Table 198: IRRInet-M Port 2 Parameters........................................................................................................509
Table 199: IRRInet-M Port 3 Configurations................................................................................................... 510
Table 200: IRRInet-M Port 3 Parameters........................................................................................................510
Table 201: Advanced Physical and Link Parameters for IRRInet-M Port 3.................................................... 510
Table 202: IRRInet-M I/O Parameters.............................................................................................................511
Table 203: IRRInet-M ‘C’ Application Parameters.......................................................................................... 512
Table 204: IRRInet-M Heap Parameters.........................................................................................................514
Table 205: IRRInet-M Leds Parameters......................................................................................................... 515
Table 206: IRRInet-M Power Management Parameters................................................................................. 516
Table 207: CAL Functions...............................................................................................................................551
Table 208: Input Elements.............................................................................................................................. 557
Table 209: Output Elements........................................................................................................................... 557
Table 210: The BAT1V and BAT2V Charging Levels Values.......................................................................... 578
Table 211: The SBOstatus Values.................................................................................................................. 578
Table 212: The SBOerror Values.................................................................................................................... 578
Table 213: Daylight Saving Dates Table......................................................................................................... 581
Table 214: Discrete – Internal Bit Data Type Values.......................................................................................587
Table 215: Value Input – Rated Ranges per AI Module Type......................................................................... 589
Table 216: Value Output – Rated Ranges per AO Module Type.................................................................... 590
Table 217: Standard MODBUS Data Models/Types Handled by MODBUS Client (Master).......................... 635
Table 218: MC-EDGE MODBUS Client (Master) Options.............................................................................. 636
Table 219: MC-EDGE MODBUS Server (Slave) Data Model......................................................................... 639
Table 220: System Table Parameters............................................................................................................. 643
Table 221: ACE1100 FEP Polling Register Locations.................................................................................... 644
Table 222: ACE1100 FEP Comm Status Register Locations......................................................................... 644
Table 223: MC-EDGE Upgrade Table for ASTRO Users................................................................................654
Table 224: MC-EDGE Upgrade Table for General Purpose Users................................................................. 655

42
 6802979C10-BA
List of Processes

List of Processes
Building a MOSCAD System ........................................................................................................................... 96
Enabling LoRaWAN ....................................................................................................................................... 651
Configuring LoRaWAN Devices .....................................................................................................................651

43
6802979C10-BA
List of Procedures

List of Procedures
Installing MC-IoT STS ......................................................................................................................................74
Viewing the System in Diagram View .............................................................................................................. 88
Viewing the System in Table View ................................................................................................................... 91
Navigating via the System Tree ....................................................................................................................... 94
Navigating via the System Path Bar ................................................................................................................ 95
Navigating via the Diagram View .....................................................................................................................95
Navigating via the Table View ..........................................................................................................................96
Starting the STS .............................................................................................................................................. 97
Creating Projects in STS ................................................................................................................................. 97
Setting the System Address ............................................................................................................................ 98
Setting the PRIS System Address ................................................................................................................... 99
Defining Areas in the STS System .................................................................................................................. 99
Adding or Removing Files from Areas ........................................................................................................... 100
Adding Files to Areas .....................................................................................................................................100
Removing Files from Areas ........................................................................................................................... 100
Defining Sites in the STS System ..................................................................................................................101
Defining an ACE3600 Site ............................................................................................................................. 102
Defining an IRRInet Site in the STS System ................................................................................................. 104
Defining an ACE1000, AuxIO-EDGE or MC-EDGE Site ............................................................................... 106
Defining an ACE IP Gateway Site ................................................................................................................. 107
Customizing the Site Configuration ............................................................................................................... 109
Customizing Site Port Configuration .............................................................................................................. 110
Customizing I/O Configuration for ACE3600 Sites .........................................................................................114
Customizing I/O Configuration for ACE1000 and MC-EDGE Sites ............................................................... 121
Customizing I/O Configuration for IRRInet-M Sites ....................................................................................... 125
Customizing NFM Devices for NFM-EDGE Sites .......................................................................................... 127
Customizing Advanced Site Parameters ....................................................................................................... 128
Customizing Add-On Options for Existing Sites ............................................................................................ 130
Configuring RFDS in STS ..............................................................................................................................130
Creating an RFDS Configuration from a Predefined Template ......................................................................131
Manually Creating New RFDS Configuration Files ........................................................................................133
Defining Site Communication Links ............................................................................................................... 135
Defining I/Os in Sites ..................................................................................................................................... 136
Importing Legacy RTU Site Configurations ....................................................................................................137
MDLC Communication Driver Configuration ..................................................................................................138
Setting up Communications in the Static Mode ............................................................................................. 138

44
 6802979C10-BA
List of Procedures

Switching to the Dynamic Mode .................................................................................................................... 142

APX CPS Mode (MC-EDGE v15.00 or Lower) .............................................................................................. 144
Downloading System Firmware to ACE3600 and IRRInet-M Sites ............................................................... 147
Downloading System Firmware to MC-EDGE Sites ...................................................................................... 151
Downloading Other Files to Sites .................................................................................................................. 153
Uploading Files from Sites .............................................................................................................................160
Upgrading ACE3600 System Firmware .........................................................................................................161
Closing STS Projects .....................................................................................................................................164
Opening Existing Projects ..............................................................................................................................164
Managing Applications ...................................................................................................................................166
Editing Link Type Costs ................................................................................................................................. 169
Managing Network Tables ............................................................................................................................. 170
Editing Network Tables .................................................................................................................................. 172
Configuring MDLC Links ................................................................................................................................173
Managing IP Conversion Tables .................................................................................................................... 175
Editing IP Conversion Table Files .................................................................................................................. 177
Managing Dynamic IP Access Tables ............................................................................................................180
Managing Add-On Files ................................................................................................................................. 180
Encrypting MC-EDGE Add-On Files (Secured STS Only) .............................................................................185
Managing Site Tables .................................................................................................................................... 188
Editing IP Gateway Site Tables ......................................................................................................................191
Editing RTU Site Tables .................................................................................................................................193
Appending Groups of Sites to a Table ........................................................................................................... 195
Managing DNP Client (Master) Configuration Files .......................................................................................198
Retrieving the Field View ............................................................................................................................... 201
Uploading New Sites to STS ......................................................................................................................... 202
Downloading to All Sites ................................................................................................................................ 206
Changing the MDLC Password in Project Only ............................................................................................. 209
Changing the MDLC Password in Sites .........................................................................................................209
Overriding the MDLC Password .....................................................................................................................211
Adding Comments ......................................................................................................................................... 212
Backing Up the Database .............................................................................................................................. 213
Setting Login Banner (MC-EDGE) .................................................................................................................213
Generating SSH Authentication Keys (MC-EDGE) ....................................................................................... 213
Changing Linux Passwords ........................................................................................................................... 215
Changing Linux Passwords Manually in Secured STS ..................................................................................216
Changing Default Linux Passwords in Secured and Unsecured STS ........................................................... 217
Changing SNMP User Credentials (MC-EDGE) ............................................................................................218
Resetting SNMP User Definitions ..................................................................................................................219

45
6802979C10-BA
List of Procedures

Exporting UEM Configuration Data for NFM ..................................................................................................219

Generating the NFM Site List Report .............................................................................................................219
Printing the System ........................................................................................................................................220
Creating PKI Configuration ............................................................................................................................ 220
Renaming Sites ............................................................................................................................................. 224
Changing the Site ID of Sites .........................................................................................................................225
Retrieving Error Logger Information from Sites ............................................................................................. 226
Retrieving Software Diagnostics from Sites ...................................................................................................230
Retrieving Time-Tagged Event Logs from Sites .............................................................................................233
Setting and Retrieving Site Date and Time ....................................................................................................235
Synchronizing Sites ....................................................................................................................................... 236
Editing Network Tables in Individual Sites ..................................................................................................... 237
Editing Site Tables in Individual Sites ............................................................................................................ 237
Setting Dial-Up Parameters ........................................................................................................................... 239
Editing Phonebook Files ................................................................................................................................ 241
Dialing Site-Attached Modem Numbers .........................................................................................................242
Editing IP Conversion Tables in Individual Sites ............................................................................................243
Uploading Site Definitions ..............................................................................................................................243
Opening Site Applications ..............................................................................................................................245
Copying Sites .................................................................................................................................................246
Copying Sites with CPU Redundancy ........................................................................................................... 247
Moving Sites to Areas ....................................................................................................................................250
Toggling the FEP Status ................................................................................................................................ 251
Deleting Sites .................................................................................................................................................252
Monitoring Database Tables in RTUs ............................................................................................................ 258
Refreshing Values in the Table Monitor ......................................................................................................... 261
Updating RTUs via the Table Monitor ............................................................................................................ 261
Copying Information in the Table Monitor ...................................................................................................... 262
Printing Screens in the Table Monitor ............................................................................................................ 262
Starting the STS Hardware Test Utility .......................................................................................................... 268
Testing Expansion Modules ........................................................................................................................... 269
Testing Digital Inputs ......................................................................................................................................273
Testing Digital Outputs ...................................................................................................................................275
Testing ACE3600 Analog Inputs .................................................................................................................... 279
Calibrating Analog Inputs ...............................................................................................................................281
Setting the AI Filter ........................................................................................................................................ 281
Setting the AI Differential Mode Filter ............................................................................................................ 282
Testing ACE3600 Analog Outputs ................................................................................................................. 282
Calibrating Analog Outputs ............................................................................................................................284

46
 6802979C10-BA
List of Procedures

Testing Ports on an Expansion LAN Switch ...................................................................................................285

Testing the CPU .............................................................................................................................................289
Testing LEDs ..................................................................................................................................................294
Testing the Power Supply .............................................................................................................................. 299
Testing the ACE3600 Power Supply ..............................................................................................................299
Testing the IRRInet-M Power Supply .............................................................................................................301
Testing the ACE3600 Plug-In Communication Port ....................................................................................... 306
Testing the IRRInet-M Port 3 ......................................................................................................................... 307
Power Management Test ............................................................................................................................... 308
Upgrading Expansion Loader Firmware ........................................................................................................ 310
Configuring the Advanced Parameters .......................................................................................................... 311
Analyzing MDLC Protocol .............................................................................................................................. 311
Defining and Activating Encrypted MDLC Communication ............................................................................311
Adding Elements from the Inventory ..............................................................................................................311
Storing Elements in the Gallery ..................................................................................................................... 314
Modifying Folders in the Gallery .................................................................................................................... 316
Importing the Gallery from Another STS ........................................................................................................316
Viewing the Online Help and STS Version .................................................................................................... 321
Exporting and Importing Site Properties ........................................................................................................ 322
Exporting Site Properties to a .csv File ..........................................................................................................322
Importing Site Properties Tables to Sites .......................................................................................................323
Starting the Application Programmer .............................................................................................................326
Creating New Applications .............................................................................................................................326
Opening Existing Applications ....................................................................................................................... 327
Navigating the Application Programmer Window .......................................................................................... 328
Creating Database Tables ............................................................................................................................. 333
Opening Existing Tables ................................................................................................................................ 333
Editing Single-Column Tables ........................................................................................................................334
Editing Multiple-Column Tables ..................................................................................................................... 336
Toggling the Attribute Page ............................................................................................................................339
Searching for Variables or Duplicated Columns ............................................................................................ 339
Copying (or Cutting) and Pasting Tables ....................................................................................................... 340
Deleting Tables .............................................................................................................................................. 341
Renaming Tables ........................................................................................................................................... 341
Printing Tables ............................................................................................................................................... 341
Creating Processes ....................................................................................................................................... 345
Creating Rungs ..............................................................................................................................................346
Adding Elements to Rungs Manually .............................................................................................................347
Adding Elements to Rungs Automatically ......................................................................................................348

47
6802979C10-BA
List of Procedures

Linking Elements in Rungs ............................................................................................................................ 350

Creating a New Link ...................................................................................................................................... 350
Changing an Existing Link ............................................................................................................................. 350
Deleting a Link ............................................................................................................................................... 350
Normalizing Rungs ........................................................................................................................................ 351
Creating Branches Manually ..........................................................................................................................351
Creating Branches Automatically ...................................................................................................................351
Closing Branches ...........................................................................................................................................352
Selecting Elements in Rungs .........................................................................................................................352
Copying (or Cutting) and Pasting Elements in Rungs ................................................................................... 353
Duplicating Elements in Rungs ......................................................................................................................353
Deleting Elements in Rungs .......................................................................................................................... 353
Adding Comments to the Rung Workspace ...................................................................................................353
Defining Rung Element Parameters .............................................................................................................. 355
Looking Up Element Parameters in the Database .........................................................................................357
Deleting Processes and Rungs ..................................................................................................................... 357
Renaming Processes and Rungs .................................................................................................................. 357
Copying (or Cutting) and Pasting Rungs ....................................................................................................... 358
Adding Descriptions to Processes and Rungs ...............................................................................................358
Printing Processes and Rungs ...................................................................................................................... 359
Searching Rungs ........................................................................................................................................... 359
Searching with The Find Dialog .....................................................................................................................359
Searching Quickly from an Open Database .................................................................................................. 361
Selecting Sites in the Application Programmer ..............................................................................................365
Linking I/Os to the Database ......................................................................................................................... 366
Connecting I/O Groups .................................................................................................................................. 368
Distributing I/O Link Information .................................................................................................................... 369
Finding Symbols/Variables in Applications .................................................................................................... 371
Saving Applications in STS Mode ..................................................................................................................372
Saving Applications in Standalone Mode ...................................................................................................... 373
Saving Applications ....................................................................................................................................... 373
Saving Applications Under a Different Name .................................................................................................373
Compiling Applications (ACE3600 Only) ....................................................................................................... 373
Downloading Applications in the Application Programmer ............................................................................ 375
Monitoring Database Tables .......................................................................................................................... 377
Starting the Table Monitor ..............................................................................................................................377
Using the Table Monitor ................................................................................................................................. 379
Monitoring Rungs (ACE3600 Only) ............................................................................................................... 380
Starting the Rung Monitor ..............................................................................................................................380

48
 6802979C10-BA
List of Procedures

Using the Rung Monitor ................................................................................................................................. 381

Displaying the Performance Monitor Table .................................................................................................... 383
Defining Critical Database Blocks ..................................................................................................................385
Storing Critical Database Blocks ................................................................................................................... 387
Restoring Critical Database Blocks ............................................................................................................... 387
Removing Critical Database Blocks ...............................................................................................................388
Converting ACE3600 Application Databases to MC-EDGE Format ..............................................................388
Viewing the Application Programmer Online Help .........................................................................................390
Printing Applications ...................................................................................................................................... 390
Closing Applications ...................................................................................................................................... 391
Exiting the Application Programmer Window .................................................................................................392
Defining MQTT Topics ................................................................................................................................... 481
Setting Up Key Variable Loader 4000 ............................................................................................................649

49
6802979C10-BA
About MC-EDGE® Maintenance Manual

About MC-EDGE® Maintenance Manual

This manual provides overview of features, installation, and maintenance of the MC-IoT MC-EDGE®.

Helpful Background Information

Motorola Solutions offers various courses designed to assist in learning about the system.
For more information on current course offerings and technology paths, visit http://
www.motorolasolutions.com/training.

Related Information
For more information related to MC-IoT MC-EDGE Maintenance Manual, you can refer to the following
documents.

Document
System Tools Suite Advanced Features Reference Guide
System Tools Suite Software Diagnostic Output and Error Messages Maintenance Guide
System Tools Suite Third Party Protocols Support Reference Guide
MC-EDGE Service Manual
Advanced System Security User Guide
MC-EDGE Owners Manual
System Tools Suite User Guide

50
 6802979C10-BA
Icon Conventions

Icon Conventions
The documentation set is designed to give the reader more visual clues. The following graphic icons are used
throughout the documentation set.
DANGER: The signal word DANGER with the associated safety icon implies information that, if
disregarded, will result in death or serious injury.
WARNING: The signal word WARNING with the associated safety icon implies information that, if
disregarded, could result in death or serious injury, or serious product damage.
CAUTION: The signal word CAUTION with the associated safety icon implies information that, if
disregarded, may result in minor or moderate injury, or serious product damage.
ATTENTION: The signal word CAUTION may be used without the safety icon to state potential damage
or injury that is not related to the product.
IMPORTANT: IMPORTANT statements contain information that is crucial to the discussion at hand, but is not
CAUTION or WARNING. There is no warning level associated with the IMPORTANT statement.
NOTE: NOTE contains information more important than the surrounding text, such as exceptions or
preconditions. They also refer the reader elsewhere for additional information, remind the reader how to
complete an action (when it is not part of the current procedure, for instance), or tell the reader where
something is on the screen. There is no warning level associated with a note.

51
6802979C10-BA
Style Conventions

Style Conventions
The following style conventions are used:

Convention Description
Bold This typeface is used for names of, for instance, windows, buttons, and
labels when these names appear on the screen (example: the Alarms
Browser window). When it is clear that we are referring to, for instance, a
button, the name is used alone (example: Click OK).
Monospacing font This typeface is used for words to be typed in exactly as they are shown in
the text (example: In the Username field, type Admin).
This typeface is used for messages, prompts, and other text displayed on
the computer screen (example: A new trap destination has been
added).
<Monospacing font in This typeface is used with angle brackets as placeholders for a specif-
bold Italic> ic member of the group that the words represent (example: <router
number>).
NOTE: For sequences that are to be typed in, the angle brackets
are omitted. This is to avoid confusion as to whether the angle
brackets are included in the text to be typed in.

CAPITAL LETTERS This typeface is used for keyboard keys (example: Press Y, and then press
ENTER).
Italic This typeface is used for citations. A citation usually is the name of a docu-
ment or a phrase from another document (example: DIMETRA System
Overview).
→ An → (arrow pointing right) is used for indicating the menu or tab struc-
ture in instructions on how to select a certain menu item (example: File
→ Save) or a certain sub-tab.

52
 6802979C10-BA
Model Complements

Model Complements
F7500 MC-IoT System Tools Suite (STS)

53
6802979C10-BA
Acronyms and Abbreviations

Acronyms and Abbreviations

Acronym/Abbreviation Definition
ACE Advanced Control Equipment
ACK Acknowledge
AGA American Gas Association
AI Analog Input
ANSI American National Standards Institute
AO Analog Output
ASL Arithmetical Shift to Left
ASR Arithmetical Shift to Right Convert
BCD to BCD Format
BIN Convert to Binary Format
CD Carrier Detect
CEN Customer Enterprise Network
COS Change of State
CPU Central Processing Unit
CRC Cyclic Redundancy Check
CTD Count Down
CTS Clear to Send Count
CTU Count Up
DBB Data Base Builder
DCD Data Carrier Detect
DCE Data Communication Equipment
DFM Direct Frequency Modulation
DI Digital/Discrete Input
DNP Distributed Network Protocol
DO Digital/Discrete Output
DOF Delay Off
DON Delay On
DPL Digital Private Line
DPSK Differential Phase Shift Keying
DSP Digital Signal Processing Data
DSR Set Ready
DTE Data Terminal Equipment
DTR Data Ready

54
 6802979C10-BA
Acronyms and Abbreviations

Acronym/Abbreviation Definition
EGU Engineering Units
EMI Expansion Microcode Interface
FE Front End
FEP Front End Processor (MCP-M, MCP-T, FIU, or
ACE1100 FEP)
FIU Field Interface Unit
FSK Frequency Shift Keying
GGSN GPRS Gateway Support Node
GND Ground
GPS Global Positioning System
GPRS General Packet Radio Service
GSM Global System for Mobile Communications
GW ACE IP Gateway
HDLC High-level Data Link Communication
HW Hardware
I/O Input/Output
IOEM I/O Expansion Module
INTRAC Two-layer (32 bits) protocol
IP Internet Protocol
IPGW IP Gateway
JMP Jump
JSP Jump To Subprocess
LAN Local Area Network
LED Light Emitting Diode
LSL Shift to Left
LSR Shift to Right
MDLC Motorola Data Link Communication (Seven-layer
OSI protocol)
MCC Master Control Center
MEIC Previous generation RTU type Man
HMI Human Machine Interface
MODBUS MODICON BUS Protocol
MOSCAD Motorola SCADA
MOSCAD-L Motorola SCADA-Light
MOSCAD-M Micro Motorola SCADA
MOV Move Value
MOVH Move High

55
6802979C10-BA
Acronyms and Abbreviations

Acronym/Abbreviation Definition
NACK Negative Acknowledge
N.C. Normally Closed
N.O. Normally Open
NEMA National Electrical Manufacturers Association (is-
sues enclosure standards)
NTP Network Time Protocol
OPC Open Connectivity
OSI Open System Interconnection
OVF Overflow
PC Personal Computer
PID Proportional Integral Derivative
PKI Public Key Infrastructure
PLC Programmable Logic Controller
PPH Pulse per Hour
PPP Point-to-Point Protocol
PPS Pulse per Second
PRIS PRotocol IRRInet-Slave
PSTN Public Switching Telephone Network
PTT Push to Talk (button on radio)
RAM Random Access Memory
RET Return
RF Radio Frequency
RNG Radio Network Gateway
ROM Read Only Memory
ROR Rotate to Right
RNR Receive, Not Ready
RR Receive, Ready
RST Reset
RTS Request to Send
RTU Remote Terminal Unit (e.g. ACE 36000, MOSCAD,
MOSCAD-M)
RUNP Run Process
RX Receive
SBO Select Before Operate
SCADA Supervisory Control and Data Acquisition
SNMP Simple Network Management Protocol
STS System Tools Suite

56
 6802979C10-BA
Acronyms and Abbreviations

Acronym/Abbreviation Definition
SW Software
TCP Transmission Control Protocol
TDPSK Trunked Differential Phase Shift Keying
TRT Retentive Timer
TX Transmit
UART Universal Asynchronous Receiver Transmitter
UCL User Call Function
UDF Underflow
UDP User Datagram Protocol
USB Universal Serial Bus
WAN Wide Area Network

57
6802979C10-BA
Definitions, Terms, and Conventions

Definitions, Terms, and Conventions

Definitions
Upload: Load a block of data or code, from the Radio Terminal Unit (RTU) to the System Tools Suite (STS).
Download: Load a block of data or code, from the STS to the RTU.

Terms and Conventions

In the MC-IoT STS documentation, the terms “RTU” and “site” are interchangeable.
The term “MOSCAD” refers to Motorola SCADA systems, which can include legacy RTUs and ACE3600
RTUs.
In the chapters in this manual, references to ACE3600 apply to IRRInet-ACE RTUs as well, except where
noted otherwise.

58
 6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

Chapter 1

MC-IoT System Tools Suite – Overview

The MC-IoT System Tools Suite (STS) is a package of utilities for building, configuring, and maintaining
sophisticated, distributed SCADA (Supervisory Control and Data Acquisition) systems.
MOSCAD (MOtorola SCADa) products facilitate SCADA system expansion and enhance the performance
of remote installations. MOSCAD technology combines both intelligence and communication to reliably
automate an entire system. These products are used in a diverse array of government and industry arenas,
such as:
● Emergency response
● Water monitoring
● Fire service/station alerting
● Electric power distribution
● Irrigation control systems
An MC-IoT system consists of remote terminal units (RTU) and one or more computerized control centers
connected to a communication network via an IP Gateway or Motorola OPC (M-OPC) unit. Various
communication links, such as IP, conventional radio, trunked radio, microwave, wireline, or dial system
(telephone) can be used.
Different types of RTUs are available, including the ACE3600 (the newest member of the MOSCAD family),
IRRInet-M, and MOSCAD-M. See Remote Terminal Unit (RTU) on page 60 for more details. Older RTUs
such as MOSCAD and MOSCAD-L can also operate in the system.
The communication system is used for transmitting the following from the central facility computer to the
RTUs, and vice versa:
● Alarms
● Status information
● Telemetric readings
● Calculated data
● Diagnostics
● Error logging information
The communication system is also used for downloading, monitoring, and debugging the application program
at the site.
The modularity of the ACE3600 enables optimized system configuration according to the specific and unique
requirements at a particular site. The RTU connects directly to VHF, UHF, 800 and 900 MHz trunked and
conventional radios, iDEN, TETRA, GSM, Power Line Carrier Communication (PLCC) modems, and Multiple
Address System (MAS) data radios. Its specialized I/O modules provide connectivity to both digital and
analog sensors. The PC-based STS enables the user to design, set up, maintain, and monitor an MC-IoT
system and its remote sites.
The STS also enables the engineer to program and download the application program to be executed in the
RTU, and to perform debugging in each RTU with a symbolic (graphic) debugging tool. The STS may be
operated in either of two ways:
● Locally, by directly connecting to the computer port on the selected unit
● Remotely (via the system communication network), by connecting to the computer port of any other RTU
in the system

59
6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

The STS can be used to configure and administer the ACE1000, MC-EDGE®®™, and IRRInet-EDGE RTUs,
which are added to an MC-IoT system. However, an independent ACE1000 system is defined, configured,
and administered using the web browser-based ACE1000 Easy Configurator tool. For details, see the
ACE1000 Easy Configurator User Guide. For the MC-EDGE®® gateway, the ACE1000 Easy Configurator
User Guide is not available.

1.1
MOSCAD System
The MC-IoT system can be relatively simple, comprising several RTUs and a control center. Likewise, it can
be a more complicated hierarchical system in which several subcentrals communicate with lower, parallel,
and higher hierarchies. The RTUs may also communicate with each other and/or with any other hierarchy in
the system.

1.2
Control Center
The control center computer has a graphical user interface that provides full control of the RTU. The functions
of the control center include database and parameter changes, and on-line application monitoring.
The central computer communicates with the RTUs using the MODBUS protocol by either serial or TCP/IP
media. The central computer communicates with the IP Gateway via TCP/IP protocol.
One of the functions of the control center is to exchange data with the RTUs. It may interrogate the RTUs
for any portion of their database. Multiple interrogation (polling) cycles operate with different priorities and by
different trigger mechanisms (time or events)

1.2.1
Remote Terminal Unit (RTU)
The ACE3600 RTU is an intelligent modular unit designed to operate either as a standalone controller, or
as part of a system including up to 15,000 RTUs, control centers, and subcentrals connected through a
communication network with any number of links and nodes.
Using the STS, the RTU is configured and loaded with the appropriate application.
The RTU is a microprocessor-based unit consisting of a CPU module, and various I/O and communication
modules. The wide range of I/O and communication modules makes the MOSCAD system flexible enough to
satisfy any application requirements.

60
 6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

Figure 1: Main Parts of the ACE3600 RTU

The RTUs communicate using the Motorola-patented MDLC protocol. This protocol is based on the
seven layers of the OSI (Open Systems Interconnection) model published by ISO, and is adapted for
SCADA communication. The protocol provides network support and multiple logical channels per physical
port, enabling simultaneous central-to-RTU and RTU-to-RTU sessions. It also enables each RTU to
simultaneously run several communication sessions, such as data exchange, on-line monitoring, diagnostics,
etc.
NOTE: Throughout the STS documentation, the terms "RTU" and "unit" are used interchangeably.

For technical information on the ACE3600 RTU, see the ACE3600 RTU Owner’s Manual. For technical
information on the MOSCAD-M, IRRInet-M or legacy RTUs, see the relevant owner’s manual. For technical
information on the ACE1000/MC-EDGE®, consult the ACE1000/MTC-EDGE RTU Owner’s Manual.

1.2.2
ACE IP Gateway
The ACE IP Gateway serves as an MDLC router between the SCADA computer and the RTUs. It does not
have a database or any control capabilities, because it acts solely as a gateway.
The ACE IP Gateway allows the SCADA center to conduct multiple sessions by a large number of logical
channels using a single physical RS-232 or IP port.
The ACE IP Gateway is an intermediary unit that connects the control center with the MOSCAD equipment
in the network. It acts as a gateway between these two portions of the network and communicates with the
RTUs using the Motorola-patented MDLC protocol. This protocol is based on the seven layers of the OSI
(Open Systems Interconnection) model published by ISO, and is adapted for SCADA communication. The
protocol provides network support and multiple logical channels per physical port, enabling simultaneous
central-to-RTU and RTU-to-RTU sessions. It also enables each RTU to simultaneously run several
communication sessions, such as data exchange, on-line monitoring, diagnostics, etc. Communication can
be established by radio, wireline, and other MDLC channels (dial-up is not supported).

61
6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

1.3
STS for ACE3600 RTUs
1.3.1
Features and Functions
The System Tools Suite provides an array of functions and features in a single, convenient user interface.
ACE3600 and IRRInet-M RTU functions can be achieved via local connection, or over the communication
network.
The main functions of the System Tools Suite include:
● System design (including areas, sites, and communication links) in a graphical desktop, with a system-
wide (multiple sites/areas) approach
● Configuration of up to 15,000 ACE3600 RTU sites per STS project
● Automatic network configuration, with optional, per site network configuration customization
● File downloads (e.g. configurations, applications, phone books, third-party protocols, site sources, etc.)
● File uploads (e.g. configurations, phone books, third-party protocols, network sources, site sources, IP
conversion tables, etc.)
● Configuration of the date and time at particular RTU sites
● Time synchronization of all RTUs in the system
● Hardware testing modules, including software calibration of analog inputs and outputs
● Plug-in communication port tests (Port 3 in IRRInet-M)
● Retrieval of errors logged in the RTUs (hardware or software malfunctions)
● Retrieval of time-tagged events (of very high resolution) logged in the RTUs
The following functions apply to the ACE3600 only:
● Creation and maintenance of RTU applications (database and process flow)
● Real-time symbolic (graphic) monitoring and debugging of the execution of the application in the RTU
(both database and process)
● Backup battery and power supply testing
● Retrieval of software diagnostics from the RTUs (by object entity names)
● Analysis of the seven layers of the MDLC protocol by capturing data packets on the communication links
(using an external protocol analyzer)
● Definition and activation of secure, encrypted MDLC communication (using an external encryption tool)
● Definition and activation of redundant links
NOTE: Not all functions are applicable to all RTU types. For a list of functions that can be performed by
the ACE IP Gateway, see the "ACE IP Gateway" section of the MC-IoT STS Advanced Features
manual.

62
 6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

1.3.2
ACE1000, MC-EDGE®, and IRRInet-EDGE RTUs
The STS enables the user to define and maintain ACE1000, MC-EDGE®, and IRRInet-EDGE RTUs in the
graphical depiction of a mixed MOSCAD system. These RTUs and their links are displayed in the graphical
desktop together with ACE3600 RTUs.
In a mixed system, all configuration and administration functions are performed from the STS, except
downloading system software to the ACE1000. In an ACE1000-only system, all configuration and
administration functions are performed using the web browser-based ACE1000 Easy Configurator tool. For
more information, see the ACE1000 Easy Configurator User Guide provided with ACE1000 RTUs. For the
MC-EDGE® gateway, the ACE1000 Easy Configurator is not available.
The STS provides the following functions for ACE1000, MC-EDGE®, and IRRInet-EDGE RTUs in a mixed
system:
● System design (areas, sites, communication links) in a graphical desktop, with a system-wide (multiple
sites/areas) approach
● Configuration of RTU sites
● Automatic network configuration, with optional, per site network configuration customization
● File download (e.g. configuration, application, application parameters, etc.)
● File upload (e.g. configuration, phone book, third-party protocol, network source, site source, IP
conversion table, etc.)
● Configuration of the date and time at particular RTU sites
● Time synchronization of all RTUs in the system
● Retrieval of errors logged in the RTUs (hardware or software malfunctions)
● Retrieval of software diagnostics from the RTUs (by object entity names)
● Real-time symbolic (graphic) monitoring of RTU database tables

1.3.3
Legacy RTUs
The STS enables the user to define and maintain legacy RTUs in the graphical depiction of a MOSCAD
system. Legacy RTUs and their links are displayed in the graphical desktop together with ACE3600 RTUs.
The following legacy RTUs/CPUs are currently supported by the STS:
● MOSCAD (400/420, 300, IP)
● MOSCAD-L (with or without IP)
● MOSCAD-M (firmware ≤ V3.40)
● IP Gateway
Many of the functions performed in the STS for ACE3600 RTUs are not relevant for legacy RTUs. A limited
number of STS functions are available for legacy RTUs:
● Definition of an RTU on the desktop
● Site configuration importation
● Configuration of the site date and time
● Add-on files selection
● File downloads to the RTU
● Retrieval of SW Diagnostics and Error Log messages

63
6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

Other functions can still be performed in the legacy ToolBox/Configurator.

1.3.4
RTU Programming Concept
Accessing and modifying each of the RTU layers with the System Tools Suite is possible either locally by
direct connection to the RTU, or remotely by using the communication network.
The circles illustrated below depict the RTU in layers. The first layer is the RTU hardware that is the base
for the system software and application (including configuration) software. When the application software
executes, the RTU database is updated.
Figure 2: Accessing and Modifying RTU Layers

1.3.5
Programming Sequence
Definition of the RTU application allows the system engineer to build a database as a set of tables. The
tables used for the RTU database definition are the basis for process programming, I/O link definition,
automatic central database definition, real-time monitoring of the RTU’s operation, etc.
After the database is built, the RTU application is created using the symbolic Motorola Advanced Ladder
Diagram Language. These symbolic definitions are later used for monitoring and debugging.
After the application is downloaded to the RTU, the control program of the terminal controls the RTU run-time
operations. The System Tools Suite terminal then allows the system engineer to perform any required
operation.

1.3.6
RTU Definition
Each RTU defined during system design includes a standard site configuration. This configuration defines the
RTU ports and the site address, as well as the I/O modules mounted on the RTU.
The standard site configuration can be manually tailored in the STS site view. The communication links
attached to each RTU port are defined at the site level, and the STS automatically builds a system-level
network configuration. This configuration is read-only, but can be customized by the user under a different
name.

64
 6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

The application program to be executed by the RTU is defined at the site level.

1.3.6.1
Site Configuration
The MOSCAD system operates with a very wide range of I/O modules and communication boards. To make
system operation more efficient, the configuration of the site (RTU) should be defined.
Site configuration includes definition of the following:
● I/O modules mounted on the RTU
● Location of the I/O modules in the various frames
● RTU ports and their parameters
● Site ID (logical address)
● Advanced parameters
The default settings for the advanced parameters are very detailed and specific, and generally do not require
adjustment.
The site configuration can also be defined using the Automatic Recognition feature in which the RTU
automatically identifies the I/O modules and plug-in ports. For more information, see the "Automatic
Recognition" chapter of the ACE3600 RTU STS Advanced Features manual.
Because several RTUs in the system usually have the same configuration (except for the logical address),
the system allows storing the RTU configuration in the gallery and creating new sites based on the same
configuration. Alternatively, you can copy and paste the site in the system (diagram or table view). After
copying the site, you can apply it to other RTUs with their own logical addresses assigned to it.

1.3.6.2
Network Configuration
The STS allows you to define all communication links attached to those RTUs acting as nodes in the system
network. The MDLC protocol uses these definitions for the automatic routing of packets through the network.
Most data radio communication systems have a single base transmitter located somewhere near the center
of the physical coverage area, as illustrated below. The transmitter emits radio energy; the distance the
emission travels defines the coverage limits of the system. Normally, all data equipment lies within this
coverage area.
Figure 3: RTU Coverage Area

If one or more sites with data equipment lie outside this coverage area, reliable communication with these
sites cannot be assured. The RTU provides a solution to this problem without the need for additional

65
6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

hardware. A map of the network is created, and existing units are used to relay information around the
network to its destination.
Any RTU can receive data, validate it, and store it in a buffer for retransmission. An RTU with more than
one communication medium (link), known as a “network node,” stores the data and relays it to another
RTU. Network node RTUs are also capable of operating as regular RTUs, so no dedicated hardware is
required. The data Store & Forward capability is a communication protocol task and requires nothing to be
programmed in the application.
A logical name is assigned to each communication medium in the network (e.g. Radio1, Radio2, Line1,
Line2). Some sites have a single communication medium; these are not network nodes. A few sites may
have both a radio and a wireline modem, or two radios; these are network nodes. Some sites may have
a single radio that communicates both with the main portion of the system, and also with one or more
out-of-range RTU sites. These are also network nodes; the link names would be Radio1/Zone1 and Radio1/
Zone2 (abbreviated Radio1/1 and Radio1/2, respectively) or their equivalent.
The STS builds the system-level generic network table, which includes each site and its communication links.
The network table is needed only in MOSCAD systems that use more than one communication link. A simple
network, such as one FIU connected to one communication link, does not require network configuration. The
generic network table can also be customized for certain sites by using the Network Manager to include a
subset of the available links. The costs associated with each type of communication link in the system can
also be modified. The application uses the link costs to calculate the actual costs of each transmission route,
and to decide which route to use.
The number of links in the system assigned to each medium (such as wireline, RSlink, and radio) can be
changed using the Links Configuration dialog. This should be done at the beginning of system definition,
before links have been assigned to ports in sites.

1.3.7
RTU Application
The RTU application is the control process to be executed by the remote terminal.
The application definition consists of the following:
● RTU database
● The process to be performed by the RTU (in the form of rungs, using the Motorola Ladder Diagram
Language and C functions)
● The connections between the database and the various inputs and outputs of the I/O modules (I/O link).
The I/O link portion of the RTU application is based on the definition of the RTU I/O modules, as determined
by the site configuration.
The RTU database is divided into reserved variables or constants, and user variables or constants. The
reserved variables or constants are retrieved from a wide bank of system information, such as functional
variables, reserved flags, or temporary buffers. The user variables or constants are arranged according to
various data types, such as discrete inputs/outputs, value inputs/outputs, timers, parameters, integer/real
values, etc.
User variables, in most cases, represent the actual inputs and outputs to/from the outside world. They are
designed to monitor and control the user devices connected to the appropriate RTUs. They may also be
used to represent internal inputs/outputs for intermediate results and time elements, or to perform various
calculations.
The application database is built as a set of tables, where the tables define a group of devices. Each row
defines a separate device, and each column contains device-specific data. The table entries are assigned
user-significant names, such as PUMP1.
During program execution, the process continuously updates the database according to the following:

66
 6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

● Incoming information from RTU physical inputs/outputs

● Internal data stored in the RTU memory
● Data received through the communication channel and the communication ports
One application can be defined and used in all RTUs (of the same type) in the system.

1.3.7.1
Downloading
After definition of all aspects of the RTU, the relevant files are downloaded to the RTU.
The following files can be downloaded:
● Site configuration
● Network configuration
● RTU application according to the configuration definition
● Predefined I/O module values
● Phone book
● IP conversion table
● Dynamic IP Access table
● Site source
● Network source file
● ACE1000/MC-EDGE® only: DNP Client (Master) configuration file
● Additional optional blocks, such as: ‘C’ application parameters, special drivers (MODBUS, AGA8, DNP3,
etc.)
● MC-EDGE® only: PKI Configuration
Files can be downloaded to a single site or to all sites in the system.

1.4
Communication Network
The MOSCAD system network consists of RTUs communicating with one or more computerized control
centers and/or with other RTUs. Each control center is connected to the communication network.
The system can be relatively simple, comprising several RTUs and one control center. It can be modularly
expanded to a more hierarchical system, where several subsystems (comprising intelligent RTUs and/or
subcentrals controlling their peripheral RTUs) communicate with a central computer.
The communication network is flexible, enabling each RTU to communicate with hierarchies above it (RTU-
to-central), parallel to it (RTU-to-RTU), under it (another RTU). When it serves as a communication node, an
RTU may also relay messages through the network.
While the communication protocol allows for a complex hierarchical system structure, it does not make it
complicated. Most of the communication interactions are transparent to the user, except in those cases where
the communication is to be defined by the ladder application. In such cases, you should perform simple
programming operations to configure the required application.

67
6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

1.4.1
RTUs and Network
RTUs can be configured to serve as far-end terminals, or as regional centers. They can function as
regional centers either by definition, or only after loss of communication with the central. It can act as a
communication node (an interconnection point between two or more different links) while performing other
tasks.
The RTU network uses the MDLC protocol, which incorporates all seven layers of the OSI model adapted
for SCADA. It supports multiple logical channels per physical port, enabling simultaneous central-to-RTU
and RTU-to-RTU sessions. It also enables each RTU to simultaneously run several kinds of communication
applications, such as reporting alarms by contention, on-line monitoring, performing diagnostics checks, etc.
For detailed information on the MDLC protocol, see MDLC Communication Protocol on page 631.
The System Tools Suite may perform monitoring, modification, diagnostics, error logging, etc., on any RTU in
the system, from any RS232 port in the system configured as either of the following:
● RS232 Local Computer port, RTU-to-RTU RS232 (RS-link1 – RS-link19)
● IP (LINE1 – LINE29)

1.4.2
Communication Links
The system may support a network comprising a nearly unlimited number of links.
The RTU supports a variety of communication media and data speeds, as follows.
● Through the radio/wireline communication port:
○ Direct FM (DFM) modem on conventional radio, up to 4800 bps; FSK modem on conventional radio,
up to 2400 bps
○ FSK modem on trunked radio, up to 2400 bps; External dial-up modem, up to 230,400 bps
○ External modem, wireline, up to 230,400 bps; or radio data DPSK modem, up to 1200 bps
○ COS modem
● Through the RS232 communication ports, up to 230,400 bps:
○ External modem
○ External dial-up modem GPS Receiver
○ PPP
● Through the RS485 communication ports, up to 230,400 bps
● ACE3600 only: Through the 10/100 Mb Ethernet plug-in port
Communication via the various ports may be simultaneous.
The RTU operates on all radio frequencies:
VHF
UHF
800/900 MHz
The RTU contains a circuit for monitoring activity on the radio or line communication channel. Channel
access software prevents the RTU from transmitting over a busy channel. Transmission is inhibited until the
channel is free. There are also several priority levels for access to the channel when it becomes available.

68
 6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

1.4.3
Communication Types
As defined by the system engineer, the RTUs are linked to a radio or wireline network according to user
requirements. Each RTU executes its application and simultaneously supports the communication link (or
links) defined for it. The RTU also serves as a network node, if so defined.
By default, the MOSCAD system supports up to:
● 29 wireline links (LINE 1 to LINE 29)
● 9 radio links (RADIO 1 to RADIO 9)
● 19 local RTU-to-RTU links (RS-link 1 to RS-link 19) that use RS232
● 29 IP links (LINE 1 to LINE 29)
● 1 dial link
Radios can be conventional or trunked. Computers may be connected by IP, or via ports configured as:
● RS232 Local Computer
● Local RTU-to-RTU link
For conventional radios, up to nine zones can be defined on each of the nine supported frequencies. A radio
link for conventional radios is divided into zones when not all the sites can communicate with each other,
and F1/F2 repeaters (using two frequencies) are not to be used. In this case, some RTUs serve as Store &
Forward repeaters and the link is divided into zones.
A zone is defined as a group of one or more sites that can directly communicate with each other without
a Store & Forward repeater. The name of a zone is composed of the link name and the zone number. For
example, for RADIO 3 the zone number 1 is named RADIO 3/1; zone number 2 is named RADIO 3/2; and so
on.
After defining the communication network, the user must define the various links used in the system as
well as the RTUs that serve as nodes between the links. A network node is an RTU that functions as an
interconnection point between two or more different links. A Store & Forward node, meanwhile, is a network
node that relays messages using the same physical port.

69
6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

1.5
Network Configurations
The MOSCAD system supports both simple and complex communication networks. The following sections
describe various configurations from different aspects.

1.5.1
Simple System
A simple system consists of a central computer and RTUs connected over one communication link.
Figure 4: A Simple Central Computer and RTU Connection

The STS may be connected to any port of the RTU configured as a computer port.
The ports of the RTUs should be defined by using Site Configuration. The logical name (e.g. LINE1) of the
communication link is also defined.

1.5.2
Two-Link and Multi-Link Systems
A two-link system is a communication network comprised of two communication links. A multi-link system is a
network that uses several link types.
The following figure illustrates a system in which the FIU serves as a network node between link RADIO 1
and link LINE 1. Configuring the FIU to have access to two different links enables the FIU to serve as a node
between these links.
Figure 5: A Two-Link System

The MDLC protocol permits RTU-to-RTU communication without the intervention of the central computer.
RTUs that are not on the same link communicate with each other by using a network node (in this case, the
FIU).

70
 6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

The following figure illustrates a system where a third link type, RS232, connects an RTU to another unit that
communicates over RADIO 2. RTUs connected to the IP link can reach RTU 7 via the IP network and then
RADIO 2.
Figure 6: A Multi-Link System

1.5.3
Two-Zone System
A two-zone system uses conventional radio over a single frequency.
Figure 7: A Two-Zone System

RTU 9 (Site ID = 9) is configured as a Store & Forward repeater. It performs data exchange between
units that operate on the same frequency but are unable to communicate directly for reasons of path and
propagation. Any RTU in zone 1 may communicate with any RTU in zone 2 by using this repeater.
The following figure illustrates this system schematically. In this case, RTU 9 is a network node between the
RADIO 1/1 and RADIO 1/2 links. The network software treats the Store & Forward node as it treats the node
between line and radio: logically the links appear as two different links, but physically they share the same
port.
Figure 8: A Two-Zone System Scheme

71
6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

Using Site Configuration, the FIU and the RTUs in zone 1 are configured to have access to the RADIO 1/1
link. The RTUs in zone 2 are configured to have access to the RADIO 1/2 link. The network node, RTU 9, is
configured to have access to both RADIO 1/1 and RADIO 1/2 links.
Using Network Configuration, RTU 9 is configured as the only node in the network. This terminal is
configured to have two links, RADIO 1/1 and RADIO 1/2.

1.5.4
Multiple Zone Systems
A Multiple Zone System uses nodes in separate zones to allow communication between RTUs in different
zones.
Figure 9: ACE3600 Multiple Zone System

The following figure is a schematic representation of this system. The system assumes that the two nodes,
RTU 15 and RTU 40, cannot “hear” each other. They communicate via the FIU, which is also a Store &
Forward node.
Figure 10: ACE3600 Multiple Zone System Scheme

In this scenario, three nodes with their accessible (logical) links should be defined.
Using the STS site configuration, the RTUs in zone 1 should be configured to have access to the RADIO 1/1
link. The RTUs in zone 2 should be configured to have access to the RADIO 1/2 link.
RTU 15 should be configured to have access to both RADIO 1/1 and RADIO 1/3 links. RTU 40 should be
configured to have access to both RADIO 1/2 and RADIO 1/4 links.
The FIU is configured to have access to both RADIO 1/3 and RADIO 1/4 links.
This system, therefore, consists of four zones and three nodes (RTU 15, RTU 40, and FIU). Any
communication between RTUs in different zones passes through these three nodes.
In a different scenario depicted in the following figure, the two nodes (RTU 15 and RTU 40) can communicate
with each other. The result is a system consisting of three zones and two nodes.

72
 6802979C10-BA
Chapter 1: MC-IoT System Tools Suite – Overview

Figure 11: ACE3600 Three-Zone, Two Node System Scheme

In this case, the two nodes do not communicate through the FIU. Therefore, the FIU does not serve as a
node in the system. Note that the communication between the RTUs in different zones passes through only
two nodes.

1.5.5
Standard Modem
The RTU supports links to standard modem over PPP via the built-in serial ports and plug-in ports.
The serial and plug-in ports may be connected to an external AT modem. For details, see "MDLC over
Standard Modem" in the MC-IoT STS Advanced Features manual.

1.6
RTU Software
The ACE3600 RTU software runs on the VxWorks operating system, and is based on an object-oriented
Multi-Tasking Executive System.
During startup, the Multi-Tasking Executive System creates all software entities needed to support the
different hardware modules and communication ports (as configured by the system engineer using the STS
site configuration).
The VxWorks operating system allows the use of only one standard software package for all RTUs, and
provides flexibility in supporting the application requirements without sacrificing efficiency.
The software supports a communication protocol based on the OSI model (published by ISO). The protocol
comprises all of the seven recommended layers, adapted for SCADA.
The RTU software can be updated locally or remotely.

73
6802979C10-BA
Chapter 2: MC-IoT STS

Chapter 2

MC-IoT STS
2.1
Hardware and Software Requirements
MC-IoT STS runs on a PC with Windows 7 or Windows 10.
The STS can be installed on a PC localized to many of the languages set in: Regional and Language
Options → Regional Options → Standards and Formats.

2.2
Installing MC-IoT STS
Procedure:
1. Insert the installation disk in your CD drive.
2. Open setup.exe
3. Follow the on-screen instructions.
NOTE: Written instructions can be found on the leaflet attached to the CD.

2.3
STS to RTU Connection
The connection between an RTU and a local computer can be established by using an IP connection, or a
cable. Any RS-232 port of the RTU can be used for connecting to the STS.
The RTU may be connected to a local computer via IP connection, or with an FLN6457 cable with an adapter
suitable for computer connection (25-pin female D type connector). Any RS-232 port on the RTU defined
as RS232 Local Computer may be used for connection to the STS. This connection provides access to the
particular RTU, or to any other RTU in the network, to perform all the functions described in this manual.
The default configuration for RS-232 ports is RS232 Local Computer (9600 bps, except in the case of SI2,
the default data speed of which is 115200 bps). The default configuration for IP ports is 10/100 BaseT, DHCP
Client, Ethernet, LAN.
The STS can also be connected to an ACE3680 CPU or ACE IP Gateway via the USB device port, using a
USB type connector.
The STS can also be connected to an ACE1000 or MC-EDGE® via the USB OTG port, using a USB 2.0
cable with a Micro-B connector. The unit is accessed by using the fixed IP address of the USB OTG port:
192.168.9.9 (when the USB connection is made, the PC is assigned the address 192.168.9.10 for its port).
NOTE: Only one USB connection per ACE1000 or MC-EDGE® unit is permitted.

Before using the ACE3600 USB device port or ACE1000/MC-EDGE® USB OTG port, you may need to
download the RNDIS device driver from Microsoft. For details, see the relevant USB port driver instructions
provided with the STS installation.
The IP addresses in the following table are reserved and cannot be used for any other purposes.

74
 6802979C10-BA
Chapter 2: MC-IoT STS

Table 1: Reserved IP Addresses

RTU Addresses
ACE3600 192.168.129.1
192.168.129.2

ACE1000 192.168.9.9
MC-EDGE® 192.168.9.10

For details on the cables required to connect the STS PC to the ACE3600 RTU, see “Appendix A:
Accessories, Adapters, and Cables” in the System Tools Suite Advanced Features Reference Guide, or
“Appendix C: Accessories, Adapters, and Cables” in the ACE3600 RTU Owners Manual.
For details on the cables required to connect the STS PC to the ACE1000 or MC-EDGE®, see "Appendix B:
Cables and Adapters" in the ACE1000 RTU Owner’s Manual or MC-EDGE® Owners Manual.

2.4
STS and RTU
The interaction between an RTU and the STS is based on the configuration, application database, and the
application program developed by the programmer.

2.4.1
RTU
RTUs can be programmed to perform required tasks on a continuous basis.
An RTU is much like a computer: it has a CPU, a real-time clock, RAM, ROM storage, serial communication
ports, etc. An RTU that is deployed in the field is a computer. An RTU that is configured to act as a district
controller is a computer. An RTU that functions as the communication bridge between the radio (or other)
communication system and the Master Control Center is a computer. The Master Control Center itself is a
computer.
RTUs can be programmed in an advanced, powerful version of the ladder-logic programming language
and/or ‘C.’ The programmed rungs are compiled and downloaded into the RTU flash memory. The
application, as programmed, may then be monitored and debugged.

2.4.2
Database Principles
RTU applications must have all variables defined by name and type before they may be used.
The ACE3600 RTU programmer must define the variables (including their name and logic type) before they
are used. The programming language reserves the appropriate memory for the variable type. It can check for
type mismatches as the logic statements are written, and generate an immediate error if the logic statement
uses an illegally named variable type.
From a computer programming perspective, how those named variables are organized is not a matter of
convention. However, the programmer should consider RTU-to-RTU or RTU-to-central communication.
The programming language organizes the variables into tables. Tables include rows and columns. Each
row and column intersection (cell) is a variable. Some tables have many rows, but only one column. All
the variables in a single-column table are of the same type. Each variable in the table is uniquely named:
PUMP1, PUMP2, etc. Such a table may contain up to 250 uniquely named variables.

75
6802979C10-BA
Chapter 2: MC-IoT STS

Figure 12: A Single-Column Table

Other tables have many rows and many columns. All variable types within any column are the same, but the
several different columns may be of different variable types. For example, a table may contain three columns:
one column for a digital input type, labeled PUMP; a second column for an internal value type, labeled
START; and a third column for a timer type, labeled RUNTIME. The variable names are a combination of the
column name and the row number, for example: PUMP,2 or START,4. This multiple-column table structure
is particularly attractive when dealing with dissimilar but related data. This is especially true when it applies
to some physical device, such as the pumps at a pump site. A multiple-column table may contain up to 250
rows and up to 8 columns.

76
 6802979C10-BA
Chapter 2: MC-IoT STS

Figure 13: A Multiple-Column Table

The programmer may create up to 127 custom tables. The design and organization of the tables should
be carefully planned. The operation of the application can be monitored by observing the variables. A
well-designed table collects related variables so that many different but related data points can be observed
simultaneously.
An effective table design anticipates which variables must be reported to a central site, and, whenever
possible, organizes those variables into just a few tables. An understanding of this part of the project, as well
as of the technical details of the applications, are both very important. Note that the protocol driver in the
central has the same table structures as the RTUs communicating with the central do. Data transfer becomes
a simple task of moving row/column data between identical tables.
You, the programmer, define the variable names. You are not required to use a bit and register notation that
reflects the electrical design of the RTU. You may define and name your variables as you wish, with no
restrictions other than name length. Even if you program in another language, the RTU system will accept
your variable names.
The database supports many variable data types. Unlike the ACE3600 database, most of the data in
the MOSCAD-M and IRRInet-M RTU database is read-only. There are some values that can be written/
manipulated by the application. For full details, see Database Tables and Data Types on page 559.

77
6802979C10-BA
Chapter 2: MC-IoT STS

2.4.3
Programming Philosophy
The MOSCAD application developer is not required to have a degree or background in computer science.
Any programming experience in ladder-logic, Basic, Pascal, or C is helpful, but not obligatory.
To create an application program that meets your needs, first identify the tasks required of the program,
including the information needed to complete each task (for example: digital inputs, variables from another
site, permission flags from the central, etc.).
Next, sketch, in flowchart form, the logical steps required to convert the stated inputs into the required
outputs. Make sure that all combinations of inputs are properly addressed and lead to the correct outputs.
This step is key, as correcting mistakes in a flowchart on paper is much easier than debugging and correcting
lines of programming code.
All of the logic operators that are used in Basic or Pascal or C programming languages are available to the
RTU ladder-logic programmer. Only the syntax is different. Remember, the logic statements will eventually be
compiled; you cannot tell how it was programmed by looking at the compiled code.
Ladder logic originated from the language of relays. The contacts of the relays, individually or in
combinations, appear to the left of the logic statements and constitute the tests. The coil of the relays
appears to the right of the logic statement and constitutes the actions. Tests on the left, actions on the right.
Line after line. The structure looks like the rungs of a ladder, hence the name of the programming language
and the term "rung" for each logic statement.
The RTU implementation of ladder logic programming allows numerous lines per rung, and numerous
symbols on a single line. Therefore, each RTU rung may indeed be a complete logic statement (IF this,
THEN that OR IF other-this, THEN other-that ELSE ...).
A process rung might include one or more tests, such as:
● Comparison of values using operators (>, <, =, ≠)
● The state of a Normally Open or Normally Closed fundamental relay contact
● Changes of variable state using a differentiator
The variables in question are all defined in the application database. Depending on the test results, certain
actions may be taken, such as:
● Energizing the coil of a relay
● Latching or unlatching a relay
● Reading input data from physical I/O modules
● Calling a user-defined function
For a list of the available tests and actions, see Ladder Diagram Language on page 517.

2.5
System Tool Suite Overview
The System Tools Suite (STS) enables users to design and maintain MOSCAD systems. Using the STS
framework, users can define and configure both individual sites and the network as a whole; perform
diagnostic tests on RTUs; and program the RTU application and monitor its execution.
The tools are incorporated into the STS framework and are available through the STS desktop. Certain tools
can also be executed independently from the Windows Start menu. For a list of the tools and their execution
method, see STS Tools Reference on page 81. For a detailed description of the STS and its tools, see
MC-IoT STS Operation on page 83.
The STS can be launched from Start → Programs, or from the STS icon created on the desktop during
installation.

78
 6802979C10-BA
Chapter 2: MC-IoT STS

In the system view, you can perform system level operations, such as: creating sites and areas; managing
applications and network tables; downloading to all sites; and uploading from an RTU.
Figure 14: STS System View

NOTE: System view and generic network are disabled when more than 400 RTUs exist. In such a case,
all system elements can be accessed and managed in the Table View tab.
The total number of sites and areas is displayed at the bottom of the screen. Search for elements in the
system by using the Find field in the System tab.

79
6802979C10-BA
Chapter 2: MC-IoT STS

Figure 15: STS Site View

Some of the functions available at the site level include:

● Site creation
To create a site, drag an RTU type from the list of RTUs in the Elements tree of the Inventory tab to
the Diagram view workspace.
Alternatively, upload a site definition from a local or remote RTU.
● Site administration
To administer a given site, click on the site in the project tree of the system or in the workspace (table
or diagram view).
For example, you can configure the site by:
○ Defining which I/O modules are present in the unit, and where they will be placed in the module frame
○ Specifying the functionality and link assignment of the ports on the CPU module
○ Setting the advanced parameters
○ Defining an application program for the RTU
You can also customize the network configuration for the site based on the generic network
configuration produced by the system.
● Assignment of an application to a site
To assign an application you created to a site, click the Application Programmer button. In the
Application Programmer window, you can edit the application database and the process rungs, and
link the physical I/Os to their virtual counterparts (variables in the database). You can then compile the
program to create and download an object file, which is readable and executable by the RTU.
● Connection to an ACE3600 CPU
The STS computer can be connected either directly or remotely to the CPU of an RTU. Before
communicating with a particular site in the system (e.g. to download an application), you are prompted

80
 6802979C10-BA
Chapter 2: MC-IoT STS

to enter the MDLC communication driver password. For information on setting and resetting the driver
password, see MDLC Driver Console on page 143.
● File downloads to the RTU/file uploads from the RTU
You can download a file or a set of files (e.g. application, phone book, ‘C’ parameters) to the
RTU, using the Download feature. This can be done locally, using a cable, or remotely over the
communication network (from any one site in the system to any other site).
● RTU hardware and software testing and diagnostics
You can perform tests and diagnostics on the hardware (LEDs, I/Os, communication and power
supplies) using the Hardware Test utility. You can retrieve software diagnostics and error messages
from the unit using the Logger utility.
● RTU application creation and monitoring
You can monitor the operation of an application, or retrieve the values of database tables during
runtime.

2.6
STS Tools Reference
The following table lists each available STS tool and its possible modes of execution. Not all tools are
available for all RTU types.

Table 2: STS Tools

STS Tool STS Desktop Execution Start Menu Execution

STS Interface Windows Desktop icon +
Application Programmer System menu (Application Man- +
ager); Site menu
MDLC Communication Setup Setup menu +
Change MDLC Password Setup menu
Protocol Analyzer N/A +
Stop MDLC Communication Setup menu +
Driver
Site Date & Time Site menu; Site view icon
Logger (SW Diagnostics, Error Site menu; Site view icon
Logger, Time Tag Logger)
Download Site menu; Site view icon;Sys-
tem menu (Download All Sites)
Upload Site menu, Site view icon; Sys-
tem menu (Upload New Site)
Monitor Site menu, Site view icon
Hardware Test Site menu, Site view icon
Network Editor System menu (IPC Conversion
Table Manager); Site menu
Phonebook Editor Site menu
IPC Conversion Table Editor System menu (IPC Conversion
Table Manager); Site menu

81
6802979C10-BA
Chapter 2: MC-IoT STS

STS Tool STS Desktop Execution Start Menu Execution

Dynamic IP Access Table Man- System menu (Dynamic IP Ac-
ager cess Table Manager); Site menu
Site Table Editor Site menu
Sync System menu
Set System Address System menu
Set PRIS System Address System menu
Set MDLC Link Costs System menu
MDLC Links Configuration System menu
Network Manager System menu
Application Manager System menu
IPC Conversion Table Manager System menu
Site Table Manager System menu
Add-on Manager System menu; Site menu
Dialup System menu
DNP-File Manager System menu
Field View System menu
Upload New Site System menu
Download All Sites System menu
Core Dump Upload Site menu
Synchronize Project System menu
PKI File Manager System menu
PKI Configuration Site menu

82
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Chapter 3

MC-IoT STS Operation

The MC-IoT System Tools Suite (STS) software allows you to build a graphical depiction of sophisticated
distributed SCADA (Supervisory Control and Data Acquisition) systems, and to maintain and monitor those
systems from the graphical desktop. The systems include areas consisting of sites (RTUs) and their links.

3.1
MC-IoT STS Operation Overview
This section describes MC-IoT System Tools Suite operation.
The System Tools Suite (STS) can be used to configure and administer ACE1000 RTUs that are added to an
ACE3600 system. However, an independent ACE1000 system is defined, configured and administered using
the web browser-based ACE1000 Easy Configurator tool. For details, see the ACE1000 Easy Configurator
User Guide. An ACE1000 RTU which has been configured using the STS cannot be accessed using the
ACE1000 Easy Configurator. For MC-EDGE®®, the ACE1000 Easy Configurator is not available.

3.2
Graphical User Interface Description
The STS includes a graphical user interface (GUI) that allows the user to easily navigate the system, and to
manage individual sites.
Near the top of the interface, the STS includes a menu bar, icons, and a contextual link trail for navigation.
On the left side of the interface, the System tab contains the system tree, and the Inventory tab contains
system components that can be added to the system. In the main workspace, the system is depicted either
graphically (Diagram View), or in a Table View with additional icons. A legend (located below the System
and Inventory tabs) familiarizes users with the various icons used in the GUI.

83
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 16: STS Graphical User Interface

The STS user interface is available in English only. The interface does not support Unicode (international
characters) in its fields. Only site names, site descriptions, and diagram comments can be Unicode strings.
The following terms are used in this manual when describing aspects of the user interface:

Table 3: STS User Interface

Term Description
System view Displays information on a system level, either graphically or in table format. In this
view, system level commands are available, both from the System menu and the
context menu. The system context menu is accessible by right-clicking any empty
space in the Diagram View or Table View, or by right-clicking the root of the
System tree.
Site view Displays information on a site level (relating to the selected site). In this view, site
level commands are available, both from the Site menu and the context menu. In
the site view, the site context menu is accessible by right-clicking the name of the
site in the System tree.
NOTE: The site context menu is also accessible from the Diagram View or
Table View by right-clicking the name or icon of the preferred site.

Diagram View Displays the system in the STS main window in graphical format.
Table View Displays the system in the STS main window in tabular format.

84
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Term Description
System tab Tab located on the left side of the STS interface, contains the System tree.
Inventory tab Tab located on the left side of the STS interface. Contains the elements and gallery
components, which can be used to define system components.
System tree Hierarchical depiction of the system, located in the System tab.

3.2.1
STS Icons
The STS interface includes sets of function icons in both the system and site views. Certain site view icons
may be inactive when that function or feature is not available for the selected site. Several icons for basic
functionality (such as opening and saving projects) are available from the STS menu bar in all views.

Table 4: Icons in the STS Menu Bar

Icon Name Description

New Project Create a new STS project.
See Creating Projects in STS on page 97.

Open Existing Project Open or import an existing STS project.

See Opening Existing Projects on page 164.

Save Project Save the currently open project.

Table 5: Icons Available in the STS System View

Icon Description
View the system in graphical format.
See Viewing the System in Diagram View on page 88.

View the system in tabular format.

See Viewing the System in Table View on page 91.

Create a new (blank) area.

See Defining Areas in the STS System on page 99.

Move the selected sites or areas to an existing area.

See Moving Sites to Areas on page 250.

Go to the parent area (goes up one level per click until reaching the top level
of the system view).
See Navigating the System on page 94.

Select links to display.

See Viewing the System in Diagram View on page 88.

85
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Table 6: Icons Available in the STS Site View

Icon Name Description

Date & Time Opens the Site Date & Time dialog.
See Setting and Retrieving Site Date and Time on page 235.

Logger Opens the SW Diagnostics and Loggers dialog.

See the following sections:
● Retrieving Error Logger Information from Sites on page
226
● Retrieving Software Diagnostics from Sites on page 230
● Retrieving Time-Tagged Event Logs from Sites on page
233

Download Opens the Site Download dialog.

See Downloads to Sites on page 145.

Upload Opens the Site Upload dialog.

See Uploading Files from Sites on page 160.

Monitor Opens the STS Table Monitor (MOSCAD-M, IRRInet-M,

ACE1000, MC-EDGE®, and IRRInet-EDGE only).
See STS Table Monitor on page 253.

Hardware Test Opens the STS Hardware Test utility (ACE3600, ACE4600,
and IRRInet-M only).
See Performing Hardware Tests on page 267.

3.2.2
Menus
The STS menu bar includes six menus, which provide access to a number of STS functions. Certain
functions are inactive in particular views (such as the site view or system view).
The STS menu bar includes the following menus:
● File
● View
● Site
● System
● Setup
● Help
Commands in the Site menu are generally disabled when viewing a project in the system view. To enable
these Site commands, the user opens a particular site (or selects it in the Diagram View or Table View).
Likewise, commands in the System menu are generally disabled when a given site is selected or open in site
view.

86
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.2.3
STS Diagram View
The STS user can view the system in Diagram View, which features icons representing individual site and
areas. In this view, the lines between the site icons graphically represent the system connections.
Depending on the unit type, each site icon in the STS project is assigned a particular color. For example,
MOSCAD-M and IRRInet-M sites are represented by green icons; ACE1000, MC-EDGE®, and IRRInet-EDGE
site icons are colored orange. The following figure shows a sampling of common site types and their
respective icon colors in the STS Diagram View.
Figure 17: Colored Site Icons in Diagram View

For each site, the Site name, Site ID, RTU model, STS software version, and links are displayed in the site
icon. For redundant RTUs, the displayed ID is the common ID of the redundant peers. By default, the site
description is displayed below the site. As an example, the following figure portrays the Diagram View of
a system with two ACE3600 sites and one area (containing two sites, not displayed). For instructions on
navigating the system (including areas and subareas) in Diagram View, see Navigating the System on page
94.

87
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 18: STS Diagram View with Several Links

When the mouse is positioned over a site or area in the diagram, a tooltip appears. The tooltip provides the
following:
● Site name
● Site ID
● Description
● Unit type
● System firmware version
● Number of links
● Number of I/O modules
● Application name
● Download status
For redundant RTUs, the common, private, and peer IDs are also displayed.
NOTE: When the download status is Needs Download, at least one file (such as an updated site
configuration) needs to be downloaded to the site. See Downloads to Sites on page 145.
Communication links are displayed as black lines in the Diagram View. The user can configure which links to
display in the diagram by clicking the Links icon. See Viewing the System in Diagram View on page 88.
If a link is displayed in red, the configuration includes some link conflict (such as mismatched data speed).
Hovering the mouse pointer over the red link reveals a tooltip that describes the link conflict. The Link
Information dialog provides additional information. See Viewing the System in Diagram View on page 88.

3.2.3.1
Viewing the System in Diagram View
Prerequisites: To open the system diagram, click Diagram View.
NOTE: If a particular site is open (in the site view), the Diagram View icon is not visible. In this case,
first return to the system root. See Navigating the System on page 94.

Procedure:
● To configure which links are visible in the Diagram View, perform the following actions:

88
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

a. Click the Links icon.

b. In the Select Links dialog, select the links that you want to view. If you want to hide any links in
the Diagram View, deselect them.
Figure 19: Select Links Dialog

c. To apply the changes, click OK.

● To view the details of a link, right-click the preferred link and select the <link name> link
information... command from the context menu.
Figure 20: STS–Link Information

NOTE: If the link displayed in the Diagram View is red, a link conflict exists. Hover the mouse
pointer over the link to view a tooltip with a description of the conflict. If additional information is
needed, use the Link Information dialog.
● To rearrange the sites or areas in the diagram, select one or more sites or areas and drag them to the
preferred locations.

89
6802979C10-BA
Chapter 3: MC-IoT STS Operation

● To manage site descriptions, perform any of the following steps (as needed).

If… Then…
If you want to show or hide in the System menu, toggle the Show site descriptions option.
all site descriptions,
If you want to move a site drag the description to the preferred location.
description,
If you want to edit a site de- perform the following actions:
scription, 1. Right-click the description and select Edit.
2. Enter the preferred text.
3. Click outside the description editor box.

3.2.4
STS Table View
The STS user can view the system in Table View, which provides a compact, tabular listing of individual site
and areas. Unlike the Diagram View, the Table View does not depict the links between sites. Instead, the
table lists the total number of links for each site.
The sites and areas included in the selected system location are listed in a chart (as shown in the following
figure). For instructions on navigating the system in Table View, see Navigating the System on page 94.
Figure 21: STS Table View

Information about each site is displayed in the chart, including:

● Site name
● Site ID
● Number of links
● Number of expansion frames (where relevant)
● Number of I/O modules
● Unit type
● System firmware version
● Application name
● Download status
● Product type
● Description
● Ports
● Files

90
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

For redundant RTUs, the Site ID column reflects the Private Site ID of the site. Hovering the mouse pointer
over the RTU reveals a tooltip, which reports the common ID and peer ID.
When the download status of a particular site is NeedsDownload, at least one file (such as a site
configuration) needs to be downloaded to the RTU.

3.2.4.1
Viewing the System in Table View
Procedure:
1. To view the system diagram, click Table View.
NOTE: If a particular site is open (in the site view), the Table View icon is not visible. In this
case, first return to the system root. See Navigating the System on page 94.
The Table View has new advanced Filtering and Sorting capabilities. Clicking the column header
button control opens the advanced Filtering and Sorting form.
Figure 22: Advanced Filtering and Sorting Form

2. Optional: To search for a particular site or area in the system table, perform the following actions:

a. In the Name column, click the advanced Filtering and Sorting button on the column header,
and enter the name or part of the name of the preferred site or area on the text block.
b. Press Enter.
If there are any matches, the matches are checked in the advanced Filtering and Sorting form.

91
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 23: Matches in the Advanced Filtering and Sorting Form

NOTE: The Table View operations from the previous Table View are saved in the new Table
View like, for instance, deleting, moving a site to an area, etc. In addition, the column order,
width, and visibility are immediately memorized after any Table View user change in each
project.

3.2.4.2
Ports and Files Columns
There are new columns in the Table View. They are divided into two groups: Ports and Files columns.
Ports columns are the same in each project. Files columns are visible only if the project has those files. By
adding a file to the project, it adds the column to the Table View. By adding a file to a site, it adds the file
name to the site file/site cell.
Ports columns are as following in each project:
● SI1
● SI2
● SI3
● ETH1
● ETH2
● ETH3
● APX/USB2
● LTE
● USB
● PI1
● PI2
● Ace HU1
● Ace HU2

92
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

● Ace DU1
● LORA
● Ace TSP

3.2.4.3
Select Columns Context Menu
The Select Columns context menu can be opened by right-clicking on any column header.
The context menu has an item menu called Select Columns, which can be opened by clicking on any Select
Columns menu item.
Figure 24: Select Columns Context Menu

In the opened form, you can choose to show or hide any columns by selecting or unchecking the check
boxes.

93
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 25: Select Columns List of Items

3.2.5
Navigating the System
3.2.5.1
Navigating via the System Tree
Procedure:
To navigate the system via the system tree, perform the following actions:
a. Select the System tab (located to the left of the Inventory tab, as shown in the following figure).
Figure 26: System Tab

b. To view a site or area, click the preferred system component. Expand the elements in the system tree,
if necessary.

94
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

If an area is selected, it opens in either the Table View or Diagram View (whichever was most recently
used).
If a site is selected, it opens in the site view. From the site view, the user can navigate directly to another
site or area using the system tree.

3.2.5.2
Navigating via the System Path Bar
Sites can be located directly below the system root, or lower in the system hierarchy (in areas or in subareas
within areas). The STS interface includes a clickable system path bar (shown in the following figure) to assist
the user in navigating the STS project. The bar displays the path from the system root to the currently open
site or area.
Figure 27: STS System Path Bar

Procedure:
To navigate the system via the system path bar, click the preferred location (such as the area to which the
currently selected site or subarea belongs, or the system root).
Result: The selected location opens in either Table View or Diagram View (whichever was most recently
used).
NOTE: When navigating away from an open site, the STS prompts the user to save any unsaved
changes before leaving the site view.

3.2.5.3
Navigating via the Diagram View
Procedure:
1. To view the system diagram, click Diagram View.
If a particular site is open (in the site view), the Diagram View icon is not visible. In this case, first use
the system path bar to return to the system root.
2. To navigate to a site or area, double-click the icon of the preferred component.

If an area is selected, the STS displays a diagram of the selected area.

If a site is selected, the site view opens. From the site view, the user can navigate directly to another
site or area using the system tree, or return to Diagram View using the system path bar.

3. To return to the parent area of the currently selected component, perform one of the following steps:
● If you are currently viewing an area or subarea, click the Up Area icon. The Up Area icon can be
clicked multiple times until reaching the root level of the system.
● If you are currently viewing a site, use the system path bar. See Navigating via the System Path
Bar on page 95.

95
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.2.5.4
Navigating via the Table View
Procedure:
1. To view the system table, click Table View.
If a particular site is open (in the site view), the Table View icon is not visible. In this case, first use the
system path bar to return to the system root.
2. To navigate to a site or area, double-click its entry in the table.
Figure 28: Selecting a Component in Table View

If an area is selected, the STS displays a table with all the sites and subareas located in the chosen
area.
If a site is selected, the site view opens. From the site view, the user can navigate directly to another
site or area using the system tree, or return to Table View using the system path bar.

3. To return to the parent area of the currently selected component, perform one of the following steps:
● If you are currently viewing an area or subarea, click the Up Area icon. The Up Area icon can be
clicked multiple times until reaching the root level of the system.
● If you are currently viewing a site, use the system path bar. See Navigating via the System Path
Bar on page 95.

3.3
Building a MOSCAD System
NOTE: In the System Build process, first the entire system (areas/sites) is created, and then each RTU
is configured separately. You may also fully configure each RTU as it is created. This is useful in a
simple system with a few sites.

Process:
1. Optional: Before starting the STS, plan your system on paper.
2. Start the STS interface. See Starting the STS on page 97.
3. Perform one of the following steps:
● Open an existing project. Click File → Open Project and select the project you want to modify.
● Create a new project in the STS. See Creating Projects in STS on page 97.
4. Define the areas in the system. See Defining Areas in the STS System on page 99.
5. Define the sites in the areas. See Defining Sites in the STS System on page 101.
6. Customize the site parameters, including the following elements:
● Port configurations
● I/Os attached to the site
● Advanced parameter settings

96
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

See Customizing the Site Configuration on page 109.

7. Define the communication media that link the sites. See Defining Site Communication Links on page
135.
8. Download the site definition to the sites. See Downloading Other Files to Sites on page 153.
Result: After the system becomes operational, you are able to perform administrative, monitoring, and
diagnostic operations, such as:
● Checking error logs
● Retrieving diagnostics
● Setting site date and time
See Administering Sites (Basic) on page 224 and Administering Sites (Advanced) on page 267.
NOTE: In these procedures, all references to the ACE3600 are also applicable to IRRInet-ACE RTUs,
except where noted otherwise. If figures for ACE3600 and IRRInet-M RTUs differ, both are displayed.

3.3.1
Starting the STS
Procedure:
1. From the Start menu, select Programs → MC-IoT<version> → STS.
2. In the Open Project window, perform one of the following actions:
● If you want to create a new project, select New project.... See Creating Projects in STS on page
97.
● If you want to open an existing project, see Opening Existing Projects on page 164.

3.3.2
Creating Projects in STS
Procedure:
1. From the Start menu, select Programs → MC-IoT<version> → STS.
2. In the Open Project window, click New project....

97
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 29: Creating a New STS Project

3. In the Create New Project dialog, enter the project name and description.
NOTE: In secured STS, the Create New Project window is slightly different. See “Creating a
Project” in the Advanced System Security User Guide.
4. Enter and confirm the legacy MDLC password.
5. Optional: If you want to create the new project in a directory other than the default one, click Browse.
You can also type or paste the directory name in the Location box.
6. Enter the preferred system address 0-65200
7. Click OK.

3.3.3
Setting the System Address
The system address can be used to differentiate between RTUs that are located in different systems but
communicate with each other.

Procedure:
1. In STS, select System → Set System Address.
2. In the System Address field, enter the system address (0-65200).
3. Click OK.
4. At the warning that changing the system address affects all sites in the system and requires that the
site configuration be downloaded again to all sites, click Yes.

98
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.3.4
Setting the PRIS System Address
Setting the PRIS system address enables communication with Scorpio using the PRIS protocol.

Procedure:
1. In STS, select System → Set PRIS System Address.
2. In the Set PRIS System Address dialog box, in the PRIS System Address field, enter the system
address (0-65200).
3. Click OK.
4. At the warning that changing the system address affects all irrigation Server (Slave) sites in the
system and requires the site configuration be downloaded again to all these sites, click Yes.

3.3.5
Defining Areas in the STS System
With version 33.00 and above, there is an option to attach files to an area. By attaching files to an area, every
element (site or area) that will be part of the area can inherit those files.
See Adding or Removing Files from Areas on page 100.

Procedure:
1. Open the STS project in which you want to define an area.

If… Then…
If your STS project is select System → New Area.
open in the Diagram
View,
If your STS project is perform the following actions:
open in the Table View, a. Select System → New Area
b. When the cursor turns into a crosshair, click anywhere in the Dia-
gram View workspace.

2. In the New Area dialog box, enter the name of the new area and click OK.
The new area appears in the system tree on the left side of the STS window (System tab). In the
Diagram View, the new area appears on the system layout. In the Table View, the new area appears
in the chart with no sites or subareas defined.
NOTE: To see a list of the sites or subareas within an area, in the Diagram View, point at the
area with the mouse and wait. A tooltip lists the sites, areas, and link configuration within the
indicated area.

99
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.3.5.1
Adding or Removing Files from Areas
Any file manager now offers a tree view.

Adding Files to Areas

Procedure:
To attach files to areas and sites, select the desired check box.
Figure 30: Adding Files to Areas

Removing Files from Areas

Procedure:
To remove files from areas, right-click the desired file in the table.

100
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 31: Removing Files from Areas

3.3.6
Defining Sites in the STS System
You can create a site by selecting an RTU type from the list of RTUs in the Elements tree of the Inventory
tab. To create a new site by uploading a site definition from a local or remote RTU, see Uploading New
Sites to STS on page 202. After the site is created, its configuration can be customized. For information
on uploading the I/O configuration determined automatically by the ACE3600 unit, see the “Automatic I/O
Recognition” section in the System Tools Suite Advanced Features Reference Guide.
If no site configuration is defined in the STS (for example, when the RTU is delivered from the factory), it
includes a default site configuration. In this situation, the following features are not available:
● Application: There is no application on the RTU.
● PDV: There is no PDV (Predefined Value), only KLV (Keep Last Value) for I/O modules in the event that
communication with the I/O module is interrupted. See Application Programmer on page 324.
● I/O Link, Time Tag, Timer Event: Because there is no application, there is no I/O link and therefore no
Time tag/Timer Event.
● Hot-Swap: If the expansion module is reset while the main CPU is running, and during the restart an I/O
module is removed, the expansion module will not recognize the removed module when it powers back
up and it will not report the hotswap to the main CPU when the I/O module is replaced in the slot. See the
ACE3600 RTU Owners Manual.
The configuration created by the STS is used in the Application Programmer during the definition of I/O Links.
See Application Programmer on page 324.
To save an RTU configuration in the gallery for future use in defining similar units, click Add RTU to Gallery.
For details, see Storing Elements in the Gallery on page 314.
For further specifics on defining sites in the STS system, please see the instructions for the relevant site type:
● Defining an ACE3600 Site on page 102
● Defining an IRRInet Site in the STS System on page 104
● Defining an ACE1000, AuxIO-EDGE or MC-EDGE Site on page 106

101
6802979C10-BA
Chapter 3: MC-IoT STS Operation

● Defining an ACE IP Gateway Site on page 107

3.3.6.1
Defining an ACE3600 Site
Procedure:
1. From within the Diagram View, click the Inventory tab. Under RTU, expand ACE3600 and select the
site type corresponding to the CPU model and firmware version of the RTU you want to define. Drag
the site type to the Diagram View workspace and release the mouse button. The Add RTU dialog
appears, as shown in the following figure.
Figure 32: Add RTU Dialog with ACE 3600 CPU 3640 Selected

2. In the Site ID field, enter the site ID of the new site.

NOTE:
If the site ID is already in use or reserved for the Common/Private ID of a redundant peer Site ID
(i.e. Site ID-1 or Site ID+1 of an ACE3680 with CPU redundancy), you are prompted to enter a
different site ID. In sites that support redundancy, the site ID must be greater than one.
Before assigning a site ID for a site that will use the channel access mechanism, see the
"Number of bits for staggering" parameter in Site Configuration Parameters on page 395.
3. Optional: The default site name is Site_<Site ID>. To change the default name of the new site, edit
the contents of the Site Name field.
4. Optional: In the Description field, enter a description of the new site (e.g. unit location).
This description appears below the site icon in the Diagram View, where it can later be edited, if
necessary.

5. Optional: To change the site type (e.g. from ACE3640 to ACE3610), use the drop-down Site Type list.
A message appears, listing the consequences of the change and prompting you to confirm the
change.

102
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

6. Perform one of the following steps:

If… Then…
If you are defining an ACE3680 and perform the following actions:
want to include support for CPU re- a. Select Support Dual CPU.
dundancy,
b. To add the new site (with the default settings in the site
configuration), click Add.
c. Proceed to step 7.
NOTE: When enabling dual CPU support, the site
is set to Primary by default. The site name is
changed to DualSite_<Site ID>. The Private
Site ID for the primary site is set to <Site ID>-1.
For more on ACE3680 RTU redundancy, see the
“RTU Redundancy” section of the MC-IoT STS
Advanced Features manual.

If you are: perform the following actions:

● Defining an ACE3680 but do not a. To add the new site (with the default settings in the site
want to include support for CPU configuration), click Add.
redundancy, b. Proceed to step 8.
● Defining an ACE3600 with a
CPU (e.g. 3610 or 3640) that
does not support redundancy,

NOTE: After you add a site, any changes you make to the Site ID in the site configuration do not
affect the site ID in the RTU. In this case, you must change the site ID in the RTU by using the
downloader.
7. To create a redundancy peer, click Yes when prompted.
NOTE:
If you click No, you may create the redundancy peer later in the site view by clicking Create
Peer CPU.
If another redundant CPU is defined in the system, you must change the default MDLC Link
name. Under the Port tab in the Add RTU dialog, change the Link name of the internal port
(INTR1) used to connect between the primary and secondary RTU. Click Add.
A peer site marked DualSite (Site ID) is created. A message appears that the new peer site was
created with the same port configurations as the original site. If necessary, change these port settings.
If the original site was set to Primary, the peer is set to Secondary, and vice versa. The Private
Site ID for the secondary site is set to Site ID+1.
In Diagram View, the two peer sites are attached and marked with a yellow circle, half of which marks
each peer. The primary site appears above the secondary site. Each site includes an ID, common to
both peers, and in parenthesis the private ID of each peer.
In Table View, each peer site entry includes the Site (private) ID.
In the Site ID column of the generic network table, each peer site entry includes the private ID.

8. Open the newly created site by navigating to the System tab (located to the left of the Diagram View)
and selecting the site. If necessary, you can search for the site using the Find field near the top of the
System tab, as shown in the following figure.

103
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 33: STS System Tab

9. To assign an application, click Assign Application.

The Application Manager appears. See Managing Applications on page 166 for more information on
assigning applications.
NOTE: Changing the application requires a new configuration to be loaded. Therefore, all
unsaved user site changes made prior to the application change are lost.

10. Customize the ports, I/Os, advanced parameters, and add-on files in the site configuration. See
Customizing the Site Configuration on page 109.
11. To save the site, select File → Save Project.
NOTE:
If there are inconsistencies in the project, the project is not saved and an error message
appears.
For example, in a system with redundancy, the MDLC Link Name assigned to the INTR1 port
may not be used in any other port. When saving a redundant site, if the MDLC Link Name for the
two peers is not the same, the STS offers to change the link of the peer site to match the current
site. If the links do not match, the configuration cannot be saved.

3.3.6.2
Defining an IRRInet Site in the STS System
Procedure:
1. To open the Add RTU dialog, perform the following actions:
a. Go to the Inventory tab located on the left side of the interface.
b. Under RTU → IRRInet, navigate to the folder with the relevant RTU site type and appropriate
firmware version.
c. Drag the selected site type to the Diagram View workspace and release the mouse button.

104
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 34: Add RTU Dialog with IRRInet-M/AC Selected

2. In the Site ID field, enter the site ID of the new site.

NOTE:
If the site ID is already in use or reserved for the Common/Private ID of a redundant peer Site ID
(i.e. Site ID-1 or Site ID+1 of an ACE3680 with CPU redundancy), you are prompted to enter a
different site ID.
Before assigning a site ID for a site that will use the channel access mechanism, see the
"Number of bits for staggering" parameter in Site Configuration Parameters on page 395.
3. Optional: The default site name is Site_<Site ID>. To change the default name of the new site, edit
the contents of the Site Name field.
4. Optional: In the Description field, enter a description of the new site (e.g. unit location).
This description appears below the site icon in the Diagram View, where it can later be edited, if
necessary.

5. Optional: To change the site type (e.g. from IRRInet-M/AC to IRRInet-M/DC) or to include an
expansion in the site definition, use the drop-down Main Board Type and Expansion Type menus.
A message appears, listing the consequences of the change and prompting you to confirm the
change.
NOTE: The Mixed I/O expansion type is only supported on IRRInet-M RTUs with firmware
version 6.00 or higher.

6. Select the application version (e.g. 7.00) from the Application Type drop-down list.
NOTE:
Changing the application requires a new configuration to be loaded. Therefore, all unsaved user
site changes made before the application change are lost.
When the IRRInet-M RTU Server (Slave) application is chosen, the Scorpio Address and
Scorpio System Address fields are displayed. The Scorpio Address can be entered. To change
the (disabled) Scorpio System Address, select System → Set PRIS System Address.

105
6802979C10-BA
Chapter 3: MC-IoT STS Operation

7. To add the new site (with the default settings in the site configuration), click Add.
The new site appears in the System tree (located under the System tab, to the left of the Diagram
View). If you cannot locate the newly created site, search for it using the Find field under the System
tab.

8. Customize the ports, I/Os, advanced parameters, and add-on files in the site configuration. See
Customizing the Site Configuration on page 109.
9. To save the site, select File → Save Project.
NOTE: If there are inconsistencies in the project, the project is not saved and an error message
appears.

3.3.6.3
Defining an ACE1000, AuxIO-EDGE or MC-EDGE Site
Procedure:
1. To open the Add RTU dialog, perform the following actions:
a. Go to the Inventory tab located on the left side of the interface.
b. In the Elements tree, select RTU.
c. Navigate to the folder with the relevant RTU site type and appropriate firmware version.
NOTE: The folder located in the Elements tree at RTU → MC-EDGE → MC-EDGE pertains
to MC-EDGE units with the T1 plug-in board.
d. Drag the selected site type to the Diagram View workspace, and release the mouse button.
Figure 35: Add RTU Dialog for MC-EDGE

106
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

2. In the Site ID field, enter the site ID of the new site.

NOTE:
If the site ID is already in use or reserved for the Common/Private ID of a redundant peer Site ID
(i.e. Site ID-1 or Site ID+1 of an ACE3680 with CPU redundancy), you are prompted to enter a
different site ID.
Before assigning a site ID for a site that will use the channel access mechanism, see the
"Number of bits for staggering" parameter in Site Configuration Parameters on page 395.
3. Optional: The default site name is Site_<Site ID>. To change the default name of the new site, edit
the contents of the Site Name field.
4. Optional: In the Description field, enter a description of the new site (e.g. unit location).
This description appears below the site icon in the Diagram View, where it can later be edited, if
necessary.

5. Perform one of the following steps.

● If you are defining an ACE1000 or MC-EDGE site, proceed to step 6.
● If you are defining an AuxIO-EDGE site, set the ASTRO® zone and site parameters. For
information on these parameters, see the MC-IoT STS Advanced Features Guide.
6. To add the new site (with the default settings in the site configuration), click Add.
The new site appears in the System tree (located under the System tab, to the left of the Diagram
View). If you cannot locate the newly created site, search for it using the Find field under the System
tab.

7. Perform one of the following steps.

● If you are defining an MC-EDGE site and want to assign an application, click Assign Application
to open the Application Manager. For more information, see Managing Applications on page
166.
● If you are defining an MC-EDGE site and do not want to assign an application, proceed to step 8.
● If you are defining an ACE1000 or AuxIO-EDGE site, proceed to step 8.
NOTE: Changing the application requires a new configuration to be loaded. Therefore, all
unsaved user site changes made prior to the application change are lost.
8. Customize the ports, I/Os, advanced parameters, and add-on files in the site configuration. See
Customizing the Site Configuration on page 109.
9. To save the site, select File → Save Project.
NOTE: If there are inconsistencies in the project, the project is not saved and an error message
appears.

3.3.6.4
Defining an ACE IP Gateway Site
Procedure:
1. To open the Add RTU dialog, perform the following actions:
a. Go to the Inventory tab located on the left side of the interface.
b. In the Elements tree, navigate to FEP → ACE IP GATEWAY → CPU4600.
c. Select the appropriate firmware version for your site.
d. Drag the selected site to the Diagram View workspace, and release the mouse button.

107
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 36: Add RTU Dialog for ACE 4600

2. In the Site ID field, enter the site ID of the new site.

NOTE:
If the site ID is already in use or reserved for the Common/Private ID of a redundant peer Site ID
(i.e. Site ID-1 or Site ID+1 of an ACE3680 with CPU redundancy), you are prompted to enter a
different site ID.
Before assigning a site ID for a site that will use the channel access mechanism, see the
"Number of bits for staggering" parameter in Site Configuration Parameters on page 395.
3. Optional: The default site name is Site_<Site ID>. To change the default name of the new site, edit
the contents of the Site Name field.
4. Optional: In the Description field, enter a description of the new site (e.g. unit location).
This description appears below the site icon in the Diagram View, where it can later be edited, if
necessary.

5. To support redundancy for the ACE IP Gateway, set the Gateway ID (by default 189), and select the
Redundancy Startup mode (i.e. Stand Alone, Redundant GW1, or Redundant GW2).
NOTE: When defining more than one ACE IP Gateway, the Gateway ID should be unique. For
more information on ACE IP Gateway redundancy, see the “ACE IP Gateway” section of the
MC-IoT STS Advanced Features manual.
6. To add the new site (with the default settings in the site configuration), click Add.
The new site appears in the System tree (located under the System tab, to the left of the Diagram
View). If you cannot locate the newly created site, search for it using the Find field under the System
tab.

7. Customize the ports, I/Os, advanced parameters, and add-on files in the site configuration. See
Customizing the Site Configuration on page 109.
8. To save the site, select File → Save Project.
NOTE: If there are inconsistencies in the project, the project is not saved and an error message
appears.

108
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.3.7
Customizing the Site Configuration
The STS includes a default site configuration for newly created sites. Generally, the STS user customizes this
site configuration during the site definition. The user may also customize a site configuration after the initial
site definition. The configuration of legacy RTUs cannot be customized.
Site customization can consist of one or more of the following areas:

Table 7: Site Customization

Configuration Customization
Port configuration (including terminal server ports See Customizing Site Port Configuration on page
in ACE IP Gateways) 110.
I/O configuration (not relevant to ACE IP Gate- See:
ways) ● Customizing I/O Configuration for ACE3600
Sites on page 114
● Customizing I/O Configuration for ACE1000
and MC-EDGE Sites on page 121
● Customizing I/O Configuration for IRRInet-M
Sites on page 125

ASTRO parameters (NFM-EDGE and AuxIO- See Customization of ASTRO Parameters of NFM-
EDGE sites) EDGE and AuxIO-EDGE Sites on page 125.
NFM Devices Configuration (NFM-EDGE sites on- See Customizing NFM Devices for NFM-EDGE
ly) Sites on page 127.
Advanced parameter configuration See Customizing Advanced Site Parameters on
page 128.
Optional Add-On files See Customizing Add-On Options for Existing
Sites on page 130.
Dynamic Communication setup settings See:
● Dynamic Mode on page 142
● Switching to the Dynamic Mode on page 142

NOTE: The site ID in the STS site configuration can be changed, if necessary. However, this does not
affect the site ID in the unit, which is changed during the download. In addition, changing the Site ID
does not change the site ID string in the Site Name.
In a redundant site, if both peers exist, the Site ID can only be changed in the primary site. The STS
automatically changes the Site ID of the secondary site accordingly. If no primary site exists, then the Site ID
can be configured in a secondary site.
If the site ID of a site is changed in the configuration, any tables that are indexed by the site ID are impacted.
The generic network configuration, which is generated automatically by the STS, is updated by the STS

109
6802979C10-BA
Chapter 3: MC-IoT STS Operation

when the site is saved. The user is responsible for updating any user-defined tables. The user then needs to
download the network configuration and any user-defined tables to all units.
NOTE: The I/Os in legacy RTU sites are defined and customized in the relevant ToolBox/Configurator
utility.

3.3.7.1
Customizing Site Port Configuration
The set of available ports varies between units. The INTR1 port (as shown in Figure 39: Port Configuration
Example: ACE3680 with Redundancy Enabled on page 111) appears in redundant sites only. A port on the
ACE IP Gateway marked with an asterisk is associated with a terminal server port. A tooltip identifies the
number of supported terminal server ports.
Secondary (redundant) sites by default are created with the same port configurations as the primary site, and
should be changed as necessary. Subsequent changes to the primary site must be manually applied to the
secondary site, where relevant.
The ports of a legacy RTU site are defined and customized in the relevant ToolBox/Configurator utility.
The following figures show a sampling of the ports and port parameters available on different RTU types. For
a detailed description of all the ports on a particular unit, see the owner's manual relevant to that model.
Figure 37: Port Configuration Example: ACE3640

Figure 38: Port Configuration Example: ACE3680 Without Redundancy

110
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 39: Port Configuration Example: ACE3680 with Redundancy Enabled

Figure 40: Port Configuration Example: ACE1000

111
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 41: Port Configuration Example: MC-EDGE with APX

Figure 42: Port Configuration Example: IRRInet-M RTU

Procedure:
1. To open a specific site for configuration, select it from the System tree (under the System tab).
2. Select the Ports tab.
3. For the port that needs to be configured, select the preferred port and link parameters from the
drop-down lists (such as Media, Operation Mode, Connection Type, etc.).
Each list contains corresponding port and user parameters (e.g. RS232, Async, Local Computer,
Computer 1, etc.). Other parameters (such as Links, Zones, and Protocols) are configured by
double-clicking the current parameter and changing the settings in a pop-up window. To change an IP
address, double-click the current value and input a new address.
For a detailed description of the parameters, see Site Configuration Parameters on page 395.
For more information on communication links attached to a port, see Defining Site Communication
Links on page 135.
NOTE:
In a system with redundancy, the same MDLC Link name must be defined for the INTR1 internal
port used to connect between the primary and secondary RTU. Other changes made to one
RTU’s port/link configuration are not automatically applied to its peer.
Setting the Ethernet port of the device connected to the ACE3600 Ethernet port (e.g. switch,
etc.) to Auto-Negotiation mode is recommended. If the Auto-Negotiation fails, the ACE3600
Ethernet port default is 10 Mbps half-duplex.

112
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 43: Port Configuration Example: ACE3600 with Ethernet Port Configured

NOTE: The IP addresses of redundant peers must be on the same segment. If the IP address of
one peer is changed to another segment, the Change IP Address in Redundancy Peers dialog
appears. Change the IP addresses as necessary and click OK.
4. Perform one of the following steps.

If… Then…
If you are not configuring proceed to step 5.
an ACE IP Gateway site,
If you are configuring an configure the terminal server ports by performing the following ac-
ACE IP Gateway site, tions:
a. Select the TS Ports tab and then click Add/Modify Ports.
b. To add a terminal server port, click Append Port. Set the IP
Address and Link Name as necessary.
NOTE: The IP address of the terminal server ports can-
not be same as the Gateway IP port address.
c. Select the physical port over which the Gateway should route
packets to the terminal server. The corresponding port in the
Ports tab is now marked with an asterisk.
d. Optional: To add additional terminal server ports, click Append
Port. Another port with the same IP Address/Physical Port and
the next TCP Port ID/Link Name is added to the list. Change the
fields as necessary.
NOTE: The TS ports often reside in the same terminal
server, so they may have the same IP address.
e. To save the settings and close the Add TS Ports dialog, click OK.
f. Optional: To remove a terminal server port from the TS Ports tab,
click the port name to select it, and then click Remove Port at the
bottom of the interface. For more on the ACE IP Gateway, see the
MC-IoT STS Advanced Features manual.

113
6802979C10-BA
Chapter 3: MC-IoT STS Operation

5. To change the advanced port settings, select the port name on the left (gray by default, orange when
selected) and then select Advanced Configuration. Apply the preferred settings.
For a detailed description of the advanced port parameters, see Appendix A: Site Configuration
Parameters on page 395.
NOTE:
The Advanced Configuration window has two tabs by default: Physical and Link. For third-
party protocols, an additional tab (e.g. PLC Master, PLC Slave, Modbus Master, Modbus
Slave) appears with additional parameters.
For IP ports with more than one link, the Advanced Link Layer parameters can be configured
separately for each link.
6. To save the settings, click OK.
If you click another site or area when there are any unsaved changes to the port configuration, you
are prompted to save the changes.
7. Optional: To add the port configuration to the gallery for use in other sites, click Add Port to Gallery.
For more details, see Storing Elements in the Gallery on page 314.

3.3.7.2
Customizing I/O Configuration for ACE3600 Sites
An ACE3600 RTU may include up to eight I/O modules in various combinations, arranged in a frame. If the
site is redundant and both peers exist, the I/O modules can only be configured from the primary site. In this
case, any I/O module assigned in the primary site is reflected in the secondary site as well. I/O modules can
be configured in a secondary site only if no primary site exists. No I/O modules can be configured for the ACE
IP Gateway.

Procedure:
1. To open a specific site for configuration, select it from the System tree (under the System tab).
2. To customize the I/O configuration, select the I/O tab.
The I/O tab appears, as shown in the following figure. A set of icons (1–8) represents the I/O module
slots. In the header of each frame, the power supply type is designated by a two or three letter code
(for example, ACc=AC with charger, 12L=DC 12V low-tier). See the tooltip for the full power supply
name.
Figure 44: ACE3600 Site Configuration - I/O Tab

3. Perform one of the following actions.

● To manually define the I/O modules, select the appropriate module type from the relevant drop-
down list for each position within the frame occupied by a module. Next to each assigned module,
a green icon appears signifying "Used Module."

114
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

● To allow the unit to automatically recognize the I/O modules at startup, select the Enable auto I/O
modules recognition at startup parameter. When this parameter is enabled, manual definition of
I/O modules is disabled.
NOTE: Enabling the Enable auto I/O modules recognition at startup parameter results in the
resetting of all I/O modules in all frames to Not Used. If the site already has I/O modules
defined, a warning appears before the modules are reset. If you click Yes and erase the I/O
modules configuration, the only way to restore them is to exit the site view without saving the
changes. For more information, see the “Automatic I/O Recognition” section of the MC-IoT STS
Advanced Features manual.
Figure 45: ACE3600 with Manually Defined I/O Modules

4. To configure the advanced I/O parameters, select a module from the list and click Advanced I/O
Configuration at the bottom of the interface.
The Advanced Configuration dialog for the chosen I/O module appears. The screen header reflects
the frame and module number of the chosen I/O module. The contents of the window may vary,
depending on the I/O module type.
Figure 46: Advanced Configuration Dialog – Example 1

115
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 47: Advanced Configuration Dialog – Example 2

Figure 48: Advanced Configuration Dialog – Example 3

Figure 49: Advanced Configuration Dialog – Example 4

116
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 50: Advanced Configuration Dialog – Example 5

5. Modify the parameters using the drop-down lists or fields on the screen. To apply the changes and
close the Advanced Configuration dialog, click OK.
For a detailed description of the parameters, see Site Configuration Parameters on page 395.
6. Perform one of the following steps:

If… Then…
If you are customizing: proceed to step 7.
● An ACE3640 or ACE3680
site, but do not want to add
an I/O expansion frame,
● A site that does not support
I/O expansion frames,

If you are customizing an perform the following actions:

ACE3640 or ACE3680 and a. From within the I/O tab, click Add/Modify Frames
want to add an I/O expansion
frame b. In the Modify Expansion Frames dialog that appears,
click the corresponding Used and Active fields to se-
lect/deselect and/or activate/deactivate the chosen expan-
sion frames.
c. To apply the changes and close the Modify Expansion
Frames dialog, click OK. Any changes (such as added or
removed frames) are reflected in the I/O tab.

NOTE: I/O expansion frames cannot be added to ACE CPU 3610 or any IRRInet-ACE RTU.

117
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 51: Modify Expansion Frames Dialog

By default, an added frame is also activated. Expansion frames can also be removed or deactivated
using commands from the expansion frame context menu.
Up to 13 I/O expansion frames can be added to the RTU site configuration. To be recognized by the
RTU, an expansion frame must be activated.
For more information on I/O expansion frames, see the MC-IoT RTU Owner’s Manual and the MC-IoT
STS Advanced Features manual.
7. To configure the advanced parameters of the main frame or an I/O expansion frame, click Advanced
next to the chosen frame (as shown in the following figure).
Figure 52: Accessing the Advanced Main Frame Parameters

The Main Frame - Advanced or Expansion Frame [#] - Advanced dialog appears.

118
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 53: Main Frame - Advanced

The advanced frame parameters include the frame ID (0=Main Frame, 1=Expansion Frame 1,
etc.), Active (Active/Not Active), and Power Supply information. The frame ID field is read-only.
The Active field is read-only for the main frame. The Switch Configuration is set using Switch
Connections.
For details on setting the advanced frame power supply parameters, see Site Configuration
Parameters on page 395.

8. To configure the power supply for a specific frame, perform the following actions:
a. From within the I/Otab, click PS Configuration at the bottom of the interface.
Figure 54: Power Supply Configuration Dialog

b. In the Power Supply Configuration dialog, select the preferred frame and modify the parameters
as needed.
The power supply type for the frame is designated by a two or three letter code (for example,
ACc=AC with charger, 12L=DC 12V low-tier) next to the frame name.
For details on setting the power supply parameters, see Site Configuration Parameters on page
395.

119
6802979C10-BA
Chapter 3: MC-IoT STS Operation

c. To apply the changes and close the Power Supply Configuration dialog, click OK.
9. To configure how the expansion frames are connected to the main frame, perform the following
actions.
NOTE: By default, the connection of expansion frames to the expansion LAN switches is
configured automatically.
a. From within the I/O tab, click Switch Connections.
b. To change the switch connection, click Manual and select the preferred switch configuration for
each expansion frame.
Figure 55: Switch Connections Dialog

NOTE: The expansion module can be connected directly to the ETH1 port on the main CPU,
or connected to one of eight ports on either of two expansion LAN switches (installed on the
main frame). See the following table.

Table 8: ACE3600 Automatic Expansion Frame Switch Connection Configuration

Total # of Expansion Connected Frames Connection Type

Frames
0 0 N/A
1 1 Connected Directly
1–7 1–7 Connected Via 1 Switch
1–13 1–6 Connected Via 1 Switch
7–13 Connected Via 2 Switches

For further information, see the ACE3600 RTU Owner’s Manual.

10. Optional: To copy an expansion frame configuration to other frames, perform the following step.
a. Right-click the expansion frame that you want to copy, and select Copy Frame To...
b. In the dialog that appears, select the frames where you want to duplicate the frame configuration.

120
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 56: Select Frames to Copy from Main Frame Dialog

c. To apply the changes and close the dialog, click OK.

The selected frames are configured (I/O modules, power supply, etc.) identically to the originally
selected frame (main or expansion). The Switch Connections are configured automatically.

11. To save the site configuration, select File → Save Project.

NOTE:
In a site assigned to an application for which I/O linking has already been completed, changing
the I/O configuration can impact the I/O links. In this case, the configuration cannot be saved
until the opened application is closed.
If a firewall is enabled in a system with I/O expansion, you may be prompted to add IP
addresses to the firewall IP Address List. You can do this manually or have the STS do it
automatically. You may be prompted to remove unnecessary IP addresses from the address list.
For details, see the “Firewall” section of the MC-IoT STS Advanced Features manual.
12. Optional: To add the I/O configuration to the gallery for use in other sites, click Add I/O to Gallery.
For more information, see Storing Elements in the Gallery on page 314.

3.3.7.3
Customizing I/O Configuration for ACE1000 and MC-EDGE
Sites
An ACE1000 site may include up to two I/O modules. With system v19.00 or above, an MC-EDGE site may
have up to five I/O modules.

Procedure:
1. To open a specific site for configuration, select it from the System tree (under the System tab).

121
6802979C10-BA
Chapter 3: MC-IoT STS Operation

2. To customize the I/O configuration, select the I/O tab.

The I/O tab appears, as shown in the following figure. A set of icons (numbered 1–6 for MC-EDGE
v19.00 or above, and 1–3 for ACE1000 or MC-EDGE v17.00) represents the I/O module slots.
Figure 57: MC-EDGE (v19.00 or Newer) Site Configuration - I/O Tab

The Enable latched DI option (MC-EDGE only) is for working with a latched input system (e.g.
dispatch consoles). When latched DI is disabled (default), MC-EDGE will include the latest current
presence value of the digital input. When Latched DI is enabled, MC-EDGE will include the latest
current presence value of the digital input and the former latched value. When Latched DI is enabled,
it enables the latched option for all digital inputs on all expansion I/O modules defined in the site.

3. To define the I/O modules, select the appropriate module type from the relevant drop-down list for
each position within the frame occupied by a module. Next to each assigned module, a green icon
appears signifying "Used Module."
NOTE: The main board (Module 1, as shown in the following figure) is read-only.

Figure 58: MC-EDGE (v19.00 or Newer) with Defined I/O Modules

4. To configure the advanced I/O parameters, select a module from the list and click Advanced I/O
Configuration at the bottom of the interface.
The Advanced Configuration dialog for the chosen I/O module appears. The screen header reflects
the module number of the chosen I/O module. The contents of the window may vary, depending on
the I/O module type.

122
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 59: Advanced Configuration Dialog – Example 1

123
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 60: Advanced Configuration Dialog – Example 2

5. Modify the parameters using the drop-down lists or fields on the screen. To apply the changes and
close the Advanced Configuration dialog, click OK.
For a detailed description of the parameters, see Site Configuration Parameters on page 395.
6. For MC-EDGE 29.00 or newer, if you need to define parameters for individual DI, DO, or AI instances
of a module, click the respective button, for example DI Instances.
NOTE: AO instances are currently not supported.

7. To save the site configuration, select File → Save Project.

NOTE:
In a site assigned to an application for which I/O linking has already been completed, changing
the I/O configuration can impact the I/O links. In this case, the configuration cannot be saved
until the opened application is closed.
If a firewall is enabled in a system with I/O expansion, you may be prompted to add IP
addresses to the firewall IP Address List. You can do this manually or have the STS do it
automatically. You may be prompted to remove unnecessary IP addresses from the address list.
For details, see the “Firewall” section of the MC-IoT STS Advanced Features manual.
8. Optional: To add the I/O configuration to the gallery for use in other sites, click Add I/O to Gallery.
For more information, see Storing Elements in the Gallery on page 314.

124
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.3.7.4
Customizing I/O Configuration for IRRInet-M Sites
Procedure:
1. To open a specific site for configuration, select it from the System tree (under the System tab).
2. To customize the I/O configuration, select the I/O tab.
The top section of the tab indicates the I/O configuration on the main board and the I/O configuration
on the expansion board (if one is defined). There is a fixed number of I/O elements, which is
determined by the selected Model ID (board ID and I/O expansion).
3. To configure the advanced I/O parameters, select the preferred settings from the drop-down lists
in the I/O Advanced Parameters section (shown in the following figure). The available parameters
are dependent on the board type (AC/DC). For details on the parameters, see Site Configuration
Parameters on page 395.
Figure 61: Configuring the I/O Parameters of an IRRInet-M Site

4. To save the site configuration, select File → Save Project.

3.3.7.5
Customization of ASTRO Parameters of NFM-EDGE and AuxIO-
EDGE Sites
AuxIO-EDGE and NFM-EDGE sites have a special ASTRO panel on their General tab. This panel contains
fields used for automatic generation of RTU configuration parameters based on the standard IP addresses
and fully qualified domain names for these devices and services in the ASTRO system.

125
6802979C10-BA
Chapter 3: MC-IoT STS Operation

The generated parameters can be seen on a special panel below these fields, which can be opened with
the ︾ button.
Figure 62: ASTRO Panel

Table 9: ASTRO Panel on the General Tab

Field Description
System/subsystem type (Astro Core, TSub, Defines choices for site types available in this sys-
CSub, K-Core, User defined) tem type.
Site type Defines the type of the site. The presence of other
fields depends on the selected site type.
Zone type Defines the type of a zone (non-DSR or DSR).
The Zone-DSR (Dynamic System Resilience) type
provides redundancy and allows the RTU to work
with a UEM in the DSR backup core.

The fields Zone number, RF Site number, Site number, CSub number, Conv location, NMDispatch Site
number, Prime site number, Subsite number, and RTU number are used in IP plan and IP services
calculations. Set these fields as appropriate for the location of the RTU in the system. Each of these choices
appears only when relevant.
RTU number is allocated automatically when all other fields are filled. When you are finished with the last
field, you can press Enter or leave the field to cause its allocation and IP plan recalculation.
STS increments the RTU number automatically if another RTU with the specified number exists. You can
also change the RTU number manually. The TRAK checkboxes displayed near the Prime site number and

126
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Subsite number, when relevant, indicate the presence of TRAK units at the corresponding locations. Their
presence affects NTP server addresses.
NOTE: AuxIOs and NFM RTUs share the same address space, but must be in separate STS projects. If
you have both AuxIOs and NFM RTUs at the same location in your ASTRO system, you can manually
adjust the RTU numbers at those locations in either your AuxIO or NFM project to avoid IP address
conflicts.
When you change any of the numeric fields, the IP configuration parameters are recalculated.
After the configuration parameters are calculated, you can change any of these parameters manually on the
Port and Advanced tabs of the Site View. If a non-default parameter value is entered manually on these
tabs, it is displayed in red in the Actual value column on the configuration parameters panel.

3.3.7.6
Customizing NFM Devices for NFM-EDGE Sites
Procedure:
1. To open a specific site for configuration, under the System tab, select the site from the System tree.
2. From within the site view, select the NFM Devices tab.
Figure 63: NFM Devices Tab

3. To add a device, in the Type column, select the device type and click outside the cell.
4. In the table or on the parameter panel, modify the device parameters as necessary.
5. To view or modify the parameters of device objects, perform one of the following actions:
● On the parameter panel, click the View Objects link.
● On the top, click the <Device Name> Objects link.

127
6802979C10-BA
Chapter 3: MC-IoT STS Operation

6. To return to the device list, perform one of the following actions:

● On the parameter panel, click the View Devices list.
● On the top, click the <Site> Devices link.
7. To delete a device, perform one of the following actions:
● In the table, right-click the device row and select Delete row.
● Select the whole row by pressing Ctrl+Space and then press the Del key.
8. To save the site configuration, select File → Save Project.

3.3.7.7
Customizing Advanced Site Parameters
Procedure:
1. To open a specific site for configuration, select it from the System tree (under the System tab).
2. From within the site view, select the Advanced tab (shown in the following figure.

128
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 64: Site Configuration View–Advanced Tab

3. From the list on the left side of the dialog, select a parameter category to view the corresponding
parameters.
4. Modify the parameters as necessary. For a detailed description of the advanced parameters, see
Appendix A: Site Configuration Parameters on page 395.
NOTE:
If the site supports redundancy, changes to advanced parameters in the primary site are not
automatically applied to the peer site, except the parameters in the I/O Expansion Manager
group.
The color of the parameter category reflects change status (white=Default group, red
triangle=Modified group). The color of the parameter reflects the value (red=Value Out of Range,
green=Value Different from Default).
5. To save the site configuration, select File → Save Project.

129
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.3.7.8
Customizing Add-On Options for Existing Sites
Procedure:
1. To open a specific site for configuration, select it from the System tree (under the System tab).
2. Select the General tab.
In the bottom-right corner of the General tab, the Add-Ons section displays a list of installed add-ons
(if any).
Figure 65: Add-Ons List in the STS Site View

3. To add add-on files to the project and attach them to the site, or to detach files from the site and
remove them from the project, click Add-On Manager... For more information, see Managing Add-On
Files on page 180.

3.3.7.9
Configuring RFDS in STS
Prerequisites: Before configuring the RFDS configuration in STS, the RFDS device must be defined in the
STS project and installed in the unit.

Procedure:
Open the STS project, go to the NFM tab and from the drop-down list, select the RFDS device.

130
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 66: NFM Devices – RFDS

The RFDS configuration control is displayed in the bottom window of the NFM tab.
Figure 67: RFDS Configuration Control

3.3.7.10
Creating an RFDS Configuration from a Predefined Template
Procedure:
1. In the Inventory tab, which is located in the upper left window, drag one of the predefined templates
from the NFM devices – RFDS section onto the NFM device.
The Add RFDS Device window is displayed with predefined values from the template.

131
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 68: Add RFDS Device Window

2. In the Add RFDS Device window, make any desired changes.

NOTE: The number of network elements you can define in a single rack is limited, as follows:
● one TTA
● two SiteRMCs
● two CabinetRMCs
● three WattMeters
Trying to add more than the allowed number of network elements in a single rack and clicking
Next generates the following error message:
Figure 69: Warning Message on the Exceeded Number of Network Elements

3. Click Next.
The RFDS parameters window is displayed.

132
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 70: RFDS Parameters Window

4. For each component in the template, set the corresponding path.

5. For each Base Radio (BR) in the template, set the IP address and from the drop-down lists, select RX
and TX paths.
It is assumed that the IP addresses are in the same subnet mask so the first three values in the IP
address are cloned for all radios.
6. When all fields have been assigned, to save a record of the assignment, print the page.
7. At the bottom of the window, click Finish .
NOTE: To complete the configuration of the device, you need to enter the actual data of the
base radio. If incorrect data is entered, red markers are visible on the screen.

3.3.7.11
Manually Creating New RFDS Configuration Files
Procedure:
1. On the NFM Devices tab, press on the Type combobox and from the drop-down list, select RFDS.
2. Enter the Site Controller/RDM Server IP Port.
3. Enter the IP address of the primary Site Controller/RDM and the secondary Site Controller/RDM.
4. From the RX diversity drop-down list, select the number of antennas in the site.
5. To specify which components appear in each section of the rack, click in each section of Rack1.
Each click toggles the component name (TTA, Primary RMC, Secondary_RMC, or Combiner). Only
one Tower Top Amplifier (TTA) can appear in each rack.
6. Click br slots in Rack1 which contain a base radio (up to six) connected to a component.
7. Repeat step 5 for each of the racks in the site which contain components.
8. When all racks are populated, click the Parameters Window button.
9. Set the fields for each component and base radio in the form.
10. When all fields are assigned, click the Save button.

133
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 71: RFDS Site

11. To return, click the <Site_Name> Devices button.

12. Optional: To add a name and description, perform the following actions:
a. Click the Add RFDS to Gallery... button.
A dialog box opens in which you need to select the path to save the current configuration.

b. To finish saving the configuration to the Gallery section, click OK.

Figure 72: Add RFTS to Gallery

134
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 73: Gallery Section

3.3.8
Defining Site Communication Links
The STS user can define communication links for an ACE3600 site within a system. In systems with
redundancy, changes to communications links in one RTU are not automatically applied to the peer site.
Note that the communication links for a legacy RTU site are defined and customized in the relevant utility
(ToolBox or Configurator).
By default, all links are displayed in Diagram View. To select which links to display, from within Diagram
View or Table View, click the Links icon. Deselecting a link from the Select Links dialog hides it from the
Diagram View.
Figure 74: Select Links Dialog

135
6802979C10-BA
Chapter 3: MC-IoT STS Operation

If there is any link conflict (for example, data speed), the link appears in red in the Diagram View, and a
description of the conflict is provided in a tooltip. To view the details of the conflict, right-click the link and
select the <link name> link information... command from the context menu.
Figure 75: STS–Link Information

Prerequisites: To define the communication links for a site, first you must define the port for communication
and configure its link parameters (for example, RSlink1 for port SI1). See Customizing Site Port Configuration
on page 110.

Procedure:
1. For all IP communication: From within the site view, select the Advanced tab.
2. Select Dynamic IP routingand configure the parameters as necessary. For a detailed description of
the Dynamic IP Routing advanced parameters, see Appendix A: Site Configuration Parameters on
page 395.
3. To save the changes to the parameters, select File → Save Project.

3.3.9
Defining I/Os in Sites
Procedure:
For information on defining the I/Os of a site when the site is created, see the relevant section:
● Customizing I/O Configuration for ACE3600 Sites on page 114
● Customizing I/O Configuration for ACE1000 and MC-EDGE Sites on page 121
● Customizing I/O Configuration for IRRInet-M Sites on page 125

136
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.3.10
Importing Legacy RTU Site Configurations
The site configuration of a legacy RTU (for example, MOSCAD, MOSCAD-L, MOSCAD-M) is defined in the
relevant ToolBox/Configurator utility and imported to the site. This must be done if the site configuration is to
be downloaded to the RTU.

Procedure:
1. From the site view, click Import Site Configuration.
Figure 76: Site View–Legacy MOSCAD Device

2. Navigate to the preferred site configuration file. See the following table for the relevant file type for
each type of legacy RTU.

Table 10: Legacy Site Configuration File Types

File Type RTU Type

.cfg MOSCAD/MOSCAD-L RTU
.mcf MOSCAD-M RTU
.cfg IP Gateway

137
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 77: Importing Legacy Site Configuration

3. To import the file, click Open.

Result: If the selected site configuration is appropriate for the RTU, the defined ports appear in the Ports
section of the screen. If the selected site configuration is not appropriate for the RTU, an error message
appears.

3.3.11
MDLC Communication Driver Configuration
Before the STS can communicate with the various sites in the system, the STS user must configure the
MDLC communication driver.
NOTE: Any change to a parameter in the Communication Setup automatically aborts all in-progress
MDLC communications. The MDLC driver is restarted before the next communication request is sent.
If you change communication parameters manually, it is called the “static mode”. It is a default mode and
was the only mode in older STS versions. Since version 35.00, it is possible to set up STS to change the
communication parameters automatically for each site individually when communication with this site starts.
This is called the “dynamic mode”.

3.3.11.1
Setting up Communications in the Static Mode
Prerequisites: For communication over a USB port with a PC running Windows 7, it may be necessary
to download and install the Microsoft RNDIS Host driver for USB. For details, see "Appendix I: Installing
Windows USB RNDIS Gadget" in the MC-EDGE Owner's Manual.

Procedure:
1. To set the communication driver parameters, select Setup → Comm. Setup...
The Communication Setup dialog appears.

138
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 78: STS Communication Setup

139
6802979C10-BA
Chapter 3: MC-IoT STS Operation

2. Perform one of the following steps.

If... Then...
If you want to configure the perform the following actions:
MDLC driver for Ethernet port a. Input the Local site IP address (or domain name) of the
communication (default), local RTU:
● For communication over the Ethernet port (Static
LAN) when using the default site configuration, input
10.100.100.100
● For any other site configuration, input the self IP ad-
dress that you defined in the Ethernet port configuration.
● For communication over the ACE3600 USB DU1 port,
input 192.168.129.1
● For communication over the ACE1000/MC-EDGE
USB OTG USB1 port, use the default address
(192.168.9.9).
b. Input the IP port number of the local RTU.
c. Proceed to step 4.
NOTE: An RTU with connectivity to Ethernet can act as
a bridge to the Ethernet for other RTUs in the system
with no such connectivity.

If you want to configure the perform the following actions:

MDLC driver for serial port a. Select Serial Port.
communication,
b. Select the PC Communication port from the drop-down list
(for example, COM1, COM2).
NOTE: In this drop-down list, the COM ports that do
not currently exist on your PC are grayed out.
c. Select the Data speed from the drop-down list.
NOTE: The data speed should be as specified in
the local computer port configuration (default:
9600).
d. Proceed to step 3.

3. Optional: If the PC port is also used for some third-party protocol not sophisticated enough to ignore
messages from other protocols sharing the port, select Protect third-party protocol over MDLC
port.
Enabling this feature allows you to block all messages not intended for that protocol for the length
of the session. Before each MDLC session, the MDLC protocol sends a “start protection” message,
after which the remote prevents transmission of MDLC messages to third-party protocols. At the
end of the session, the MDLC protocol sends an “end protection” message, which opens the port to
all MDLC messages. If communication fails and the “end protection” transmission is lost, protection
automatically ends after a few minutes (as determined by an internal timer).
Third-party protocol protection adds an overhead of approximately 20 bytes per session (start/end
protection bytes) and therefore should not be selected if the port is only used for MDLC. Mature
protocols such as MDLC and DNP do not require this protection and can recognize and reject
messages that are irrelevant to them.

140
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

4. To modify the advanced parameters of the MDLC driver, click More >>>.
5. Modify the advanced parameters as necessary. For an explanation of these parameters, see
Appendix A: Site Configuration Parameters on page 395.
Figure 79: STS Communication Setup Advanced Parameters

6. To save the changes and close the Communication Setup dialog, click OK.

141
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.3.11.2
Dynamic Mode
In the dynamic mode, communication parameters are defined on a per-project and per-site basis. STS
automatically sets communication parameters before each communication session according to the settings
specified for the project and, optionally, for each site separately.
NOTE:
Advanced parameters defined on the More screen are always static and never changed automatically.
You define them globally as in the static mode.
The dynamic communication setup feature is available only when a project is opened and only from
within STS. From the Change Settings dialog opened from the taskbar icon of the MDLC driver, you
cannot change the dynamic settings. You see the regular static settings for the latest communication
session. But even if you change them, they are replaced before the next communication session. Also,
if no project is opened, you work in STS in the static mode only.
In the dynamic mode, STS merely replaces communication parameters automatically each time you
start communication with an RTU, and then restarts the driver. So you cannot communicate with two
sites simultaneously if you defined different communication settings for them. Long operations such as
continuous monitoring must be stopped before starting communication with different settings. For
simultaneous operation, you should use either the static mode, or define the same Communication
Setup settings for the required sites and connect to them non-locally by MDLC using their site IDs.
If you change the Site ID on the communication panel of the dialog, it does not affect the
communication setup settings. To use a specific individual setting of the site, you must select the
required command from the Site menu on this site; in the multi-site dialogs with the project tree,
communication settings are selected according to the site currently processed.

3.3.11.2.1
Switching to the Dynamic Mode
In order to switch to the dynamic mode, perform the following procedure.

Procedure:
1. Open the Communication Setup dialog (see Figure 78: STS Communication Setup on page 139)
and select the Dynamic per site option on the top of the dialog.
In the dynamic mode, you define the default communication settings for the project, so if you have not
defined the default communication settings for the project, you are prompted to enter them right after
switching to the dynamic mode.
If you have already defined the default settings, you can change them later in this dialog by clicking
the Set default communication button.
2. In the Default Communication Setup dialog, select the default port used for communication (COM or
Ethernet), and specify its basic parameters.
For a COM port, you specify the number and the data speed, and for the Ethernet port, you specify
the IP address and the IP port number.
3. To define settings for each site individually, open its General tab and click the Dynamic
communication setup button.
You can select between the default settings set for the project (selected initially) or redefine
communication for this site by selecting serial or Ethernet port for this site specifically.
When communication starts, and the relevant site has its individual settings defined, they are used;
otherwise, the default project settings are used.

142
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.3.11.3
MDLC Driver Console
The MDLC communication driver starts when the user selects a command that requires MDLC
communication (such as Download or Hardware Test). The STS user must enter the MDLC driver
password.
NOTE:
For nonsecured communication with all sites in the project, the STS uses the MDLC password entered
during project creation. For exceptions to this rule, see Changing the MDLC Password in Sites on page
209 and Overriding the MDLC Password on page 211.
If you select a local or remote site that is not part of the project, and the selected site uses a different
password than the STS, communication fails.
For information on changing the MDLC password, see Changing the MDLC Password in Sites on page
209 and “MDLC Password Change” in the System Tools Suite Advanced Features Reference Guide.
For information on MDLC communication in a secure system, see the “MDLC Communication Driver”
section of the Advanced System Security User Guide.

While the STS is communicating with the RTU, the icon at the upper right corner of the relevant
window (generally, in the connection bar) is animated.
While the MDLC communication driver is in use, an icon representing the MDLC driver console is visible in
the system tray at the bottom of the computer screen. An icon indicates that the MDLC driver is waiting for
initialization. An icon indicates that the MDLC driver is connected.
The STS user can perform a number of actions via the MDLC driver console in the system tray:
● To stop the driver, right-click the icon and click Stop Driver.
● To change the driver communication parameters, right-click the icon and click Change Settings.
NOTE: For more information, see MDLC Communication Driver Configuration on page 138.

● To view the MDLC driver version, right-click the icon and click About....
● To check the connection status, hover over the icon. A tool tip appears above the icon.
Figure 80: Example of MDLC Driver Console Tooltip

● To close the MDLC driver console, right-click the icon and select Exit.

143
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.3.12
APX CPS Mode (MC-EDGE v15.00 or Lower)
The MC-EDGE gateway includes an internal ASTRO APX4000 RF module. The user can configure and
program the internal radio by using the Motorola ASTRO Computer Programming Software (CPS) SW Tool
via the STS.
NOTE:
This feature is supported only on MC-EDGE with firmware v15.00 or lower. It is not supported on units
with firmware v17.00 and above.
The internal APX radio must be configured only by initiating the CPS via the STS.
Setting/programming the internal APX radio is supported only via wire-line connection.
Prerequisites: Ensure that:
1. The STS and Motorola ASTRO CPS version 7.xx are properly installed on the same PC.
2. The MC-EDGE gateway (v15.00 or lower) is powered on and operational (green LED is on).
3. The MC-EDGE gateway USB OTG or IP connector is connected to the STS PC via wire-line cable.

Procedure:
1. Start the STS.
2. From the menu, select Setup → Comm. Setup...
3. In the Communication Setup dialog, click More >>>.
4. To connect to the MC-EDGE in APX CPS mode, click MC-EDGE APX CPS Mode...
NOTE: If the locally connected RTU is not an MC-EDGE, you get an error message.

Figure 81: CPS Mode Dialog

The STS checks the current mode when the dialog starts. If CPS mode is currently disabled, you can
enable it using the Enable CPS Mode button. When CPS mode is enabled, the Disable CPS mode
button is active. You can query the current CPS status at any time by clicking Refresh.
5. To run the CPS tool (installed separately), click Run APX CPS. The STS launches the Motorola
ASTRO CPS automatically.

144
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Postrequisites: After the CPS is properly initialized (without error messages), you can configure/program
the ASTRO APX parameters. After you complete the configuration, disable the CPS mode using the Disable
CPS mode button.
NOTE:
The APX configuration parameters (such as radio frequencies, Tx power, BW, etc.) are beyond the
scope of the MC-EDGE project and depend on customer-specific ASTRO infrastructure settings.
When using the CPS tool, wait at least 30 seconds between reading and writing to codeplug operation.

3.3.13
Downloads to Sites
The STS user can download multiple files/blocks to the RTU via the Site Download dialog.
Depending on the RTU type, these blocks can include (among others) some of the following file types:
● Application source files
● ‘C’ applications
● ‘C’ data
● Compressed application software and attachments for backup within the RTU
● IP conversion tables
● Ladder applications
● Phonebook data
Some of the files available for download via the Site Download dialog are files created automatically by the
STS, such as site configurations and network definitions. Other files are user-created, such as phonebooks,
IP conversion tables, and ladder applications. Before downloading user-created files, the user imports them
to the STS project via the Add-On Manager or other managers (which are accessible from the menu bar
under System). See Managing Add-On Files on page 180.
ACE3600 and IRRInet-ACE sites include a site source file, which comprises all the site files except the
firmware. The STS packs these files in a ZIP archive when the Site Source option is selected in the Site
Download dialog. Additionally, the user can add their own files (documents, drivers, spreadsheets, etc.) to
the site source. To do this, the user clicks the Settings button next to the Site Source entry and then selects
Add User File... Comments can be attached to the site source as well.
For guided instructions on how to download new system firmware (including file system and kernel files) to
sites, see the following sections:
● Downloading System Firmware to ACE3600 and IRRInet-M Sites on page 147
● Downloading System Firmware to MC-EDGE Sites on page 151
● MC-EDGE Upgrade Tables on page 654
NOTE: To download new system firmware to legacy RTU sites, use the MOSCAD Programming
ToolBox or the ACE1000 Easy Configurator.
For guided instructions on how to download other files (including bundles) to RTU sites, see Downloading
Other Files to Sites on page 153.
NOTE: On MC-EDGE® units of version 33 and higher, the downloader first checks if the target unit still
has default passwords. If yes, the user must change passwords. For details, see Changing Default
Linux Passwords in Secured and Unsecured STS on page 217.

145
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.3.13.1
Download Restrictions
For ACE1000 and MC-EDGE®, the STS limits which files can be downloaded together.
The following restrictions apply to site downloads:
● A package can be downloaded with other packages, but not with other file types.
For example, a package and site configuration cannot be downloaded together.
● A bundle can be downloaded with other bundles, but not with other file types.
For example, a bundle and site configuration cannot be downloaded together.
● IEC files (file extensions .app and .crc) must be downloaded together and separately from other file
types.
● ‘C’ application files (file extensions .plx and .dat) must be downloaded separately from other file types.
For example, a .plx file and a site configuration cannot be downloaded together.
NOTE: ‘C’ application files with file extensions .plx and .dat can be downloaded together.

3.3.13.2
MC-EDGE Site Download Options
The STS supports two options for downloading files to an MC-EDGE site.

Download via MDLC

Download via the Motorola Data Link Communication (MDLC) protocol is the default mechanism for
transmitting files to the MC-EDGE using any interface capability (Radio, Ethernet, LTE). This mechanism
is suitable primarily for small-sized files and packages, and is perfect for narrow band radio bandwidth. The
MDLC protocol is not recommended for larger files (such as file systems, kernels, bundles/packages), as
the download process would take a very long time. The STS automatically uses the MDLC option when
downloading site configurations, as well as files with a size of 10 KB or less.

Download via SFTP

Download via the SSH File Transfer Protocol (SFTP) is the preferred mechanism for downloading large files
(such as file systems, kernels, bundles/packages) to the MC-EDGE. This mechanism operates only on MC-
EDGE sites that have IP connectivity of the ETH or LTE type. Via the SFTP mechanism, firmware-over-the-air
(FOTA) updates and remote downloads of large files are significantly faster than via the MDLC mechanism.
The SFTP mechanism requires you to enter a password. The password must be identical to the mciotlogin
SSH password of the site. You can choose to use the same password for SFTP download to any MC-EDGE
site, or you can use a different password for each site. Entering a wrong password results in rejection of the
SFTP transfer. After you enter the password, it remains in the STS RAM until the project is closed.
NOTE: The STS also permits use of the two options, with SFTP as the primary mechanism, and MDLC
as the fallback mechanism when SFTP fails.

146
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.3.13.3
Downloading System Firmware to ACE3600 and IRRInet-M
Sites
You can download system firmware to an ACE3600 or IRRInet-M RTU via the Site Download dialog.
To download other file types, see Downloading Other Files to Sites on page 153.
Prerequisites: Before downloading new system software to an IRRInet-M RTU, make sure that the
communication driver is not running on the port to be used for the download.

Procedure:
1. From the system Diagram View or Table View, select the preferred site.
2. To open the Site Download dialog for the chosen site, from the menu bar click Site → Download.
NOTE: You are prompted to save any unsaved changes to the project before proceeding to the
Site Download dialog.
3. To specify the connection to be used for the download, perform one of the following steps:
● If the site is locally connected, select Local.
● If the site is remotely connected, make sure that the Site ID and Link ID are properly configured
(with the Local option deselected).
If the site supports redundancy, the Site ID field reflects the private ID (either Site ID+1 or Site ID-1),
as shown in the site view under the General tab. You cannot download firmware to the common site
ID.
NOTE: If a site is redundant, you must download to each CPU (primary and secondary)
individually.
4. Perform one of the following steps.

If… Then…
If you want to download a perform the following actions:
new system firmware file a. From the Files list, select Remote System File.
to an ACE3600 site,
b. Click the Settings button located to the right of Remote System
File.

If you want to download a perform the following actions:

new system firmware file a. From the Files list, select System File.
to an IRRInet-M site,
b. Click the Settings button located to the right of System File.

NOTE: To see all the files currently associated with the site, select View all site files (default).
To view only the selected (checked) files in the Files list, deselect View all site files.

147
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 82: ACE3600 Site Download Dialog

Figure 83: IRRInet-M Site Download Dialog

Depending on the RTU type, one of the following dialogs opens.

148
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 84: ACE3600 System File Settings Dialog

Figure 85: IRRInet-M Download Settings Dialog

5. In the ACE3600 System File Settings or IRRInet-M Download settings dialog, perform the following
actions:
a. Modify the parameters as preferred.
For a description of each parameter, see the following tables.
b. To save the changes and close the dialog, click OK.

Table 11: ACE3600 System File Settings

Parameter Description
Check CRC on startup Performs a CRC check on the system when the RTU starts up.
Evaluate request Evaluates the downloaded firmware image before writing it to the
Flash. This is to avoid a situation where a flawed firmware image
is downloaded and remote communication with the RTU becomes
impossible.

Table 12: IRRInet-M Download Settings

Parameter Description
Communication port The PC communication port to be used for the download to the RTU
(COM1-COM9)

149
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Parameter Description
Data speed The data speed (chosen from a range of 1200 to 115200 bps) to be
used for the download to the RTU

6. To download the file to the unit, perform one of the following steps.

If… Then…
If the site is an perform the following actions:
ACE3600, a. In the Settings section of the Site Download dialog, select the pre-
ferred unit reset and flash erase parameters from the drop-down lists.
See Site Download Reset and Erase Options on page 159.
b. Click Download.

If the site is an IRRI- perform the following actions:

net-M, a. Click Download. A prompt appears, as shown in the following figure.
Figure 86: IRRInet-M Pre-Download Prompt

b. Turn off the unit.

c. To enter bootstrap mode, press and hold the pushbutton and then
power on the unit.
d. After 5 seconds, release the pushbutton.
e. To begin the download1, click OK.

NOTE: If this is the first communication session of the MDLC driver, the STS prompts you for the
MDLC driver password before initiating the download.
1When a new firmware file is downloaded to an IRRInet-M RTU, the CPU fails, the LED display
illuminates, and the ERR LED flickers. See "Controls and Indicators" in the IRRInet-M AC Owner's
Manual or IRRInet-M DC Owner's Manual. In this case, press the pushbutton to erase the user part of
the Flash memory, which contains the site and network configurations, ‘C’ applications, phonebooks,
etc. The RTU then starts up with the newer firmware version and the default site configuration for that
version. If you want to retain the newer firmware version, you must download a newer, compatible
version of the configuration along with any other required user flash files. If you want to return to
the previous (older) firmware, download the older firmware file, then download the older user flash
contents (configuration, ‘C’ application, etc.).

In the right side of the window, two respective progress bars show the progress of the current file
download and of the download overall.

150
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

If the site ID was changed in the unit, the new site ID appears in the STS site view.

7. To close the Site Download dialog, click Close.

3.3.13.4
Downloading System Firmware to MC-EDGE Sites
The MC-EDGE® firmware consists of a kernel and a file system. To update the MC-EDGE system, the user
first downloads the new kernel to the unit according to the following procedure. After downloading the kernel,
the user repeats this procedure to download the file system.
For information on downloading other file types, see Downloading Other Files to Sites on page 153.
NOTE: Each file system is designed to work with one specific kernel version. During file system
downloads, the STS checks for matching kernel and file system versions.

Procedure:
1. From the system Diagram View or Table View, select the preferred site.
2. Select Site → Add-On Manager...
3. Perform one of the following steps:
● To add a kernel file to the site, select Kernel from the File Types list.
● To add a file system file to the site, select File System from the File Types list.
4. From the Files in Project list, select the preferred kernel or file system file.

NOTE: If the preferred file is not in the list, click the icon to browse for the file and import it
into the project.
5. In the Sites list, select the preferred site.
6. To add the chosen file to the selected site and close the Add-On Manager, click OK.
7. To open the Site Download dialog, from the menu bar click Site → Download.

151
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 87: STS – Site Download Dialog

NOTE: You are prompted to save any unsaved changes to the project before proceeding to the
Site Download dialog.
8. To specify the connection to be used for the download, perform one of the following steps:
● If the site is locally connected, select Local.
● If the site is remotely connected, make sure that the Site ID and Link ID are properly configured
(with the Local option deselected).
9. From the Files list, select the preferred kernel or file system (previously added via the Add-On
Manager).
NOTE: To see all the files currently associated with the site, select View all site files (default).
To view only the selected (checked) files in the Files list, deselect View all site files.
10. Optional: To use the SFTP protocol for the download instead of the default MDLC protocol, select the
Use SFTP option. If you want to allow MDLC as a fallback download method (in case of SFTP failure),
select Allow MDLC fallback.
For a comparison of the SFTP and MDLC protocols, see MC-EDGE Site Download Options on page
146.
11. To download the selected file to the unit, click Download.
NOTE:
Before you download the file system to the MC-EDGE, first download the matching kernel file.
If this is the first communication session of the MDLC driver, the STS prompts you for the MDLC
driver password before initiating the download.

In the right side of the window, two respective progress bars show the progress of the current file
download and of the download overall.

152
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

If the site ID was changed in the unit, the new site ID appears in the STS site view.

12. To close the Site Download dialog, click Close.

For some particular upgrade cases, such as upgrade from R9.5 to R11.0, special single-file composite
packages have been built, which include all that is needed for upgrade and do not require additional
files. Such packages are added to sites as reqular file system files, but they include upgrade in their
name and end with the .zip.bin suffix.
For details, see MC-EDGE Upgrade Tables on page 654.

3.3.13.5
Downloading Other Files to Sites
The STS user can download other files (including bundles) to sites via the Site Download dialog. If needed,
the STS user can also erase the flash of a unit by following this procedure.
For more information on the types of files that can be downloaded, see Downloads to Sites on page 145.
For guided instructions on how to download system firmware files (including file system and kernel files) to
sites, see the following sections:
● Downloading System Firmware to ACE3600 and IRRInet-M Sites on page 147
● Downloading System Firmware to MC-EDGE Sites on page 151
NOTE:
Once a site configuration has been downloaded to an ACE1000 RTU via the STS, it can only be
configured and administered using the STS. To administer such an RTU using the ACE1000 Easy
Configurator, first erase the flash to restore it to the default (factory) site configuration. For details on
erasing the flash using the ACE1000 Easy Configurator, see Resetting the ACE1000 RTU/FEP.

Procedure:
1. From the system Diagram View or Table View, select the preferred site.
2. To open the Site Download dialog for the chosen site, select Site → Download.
If changes were made to the project, you are prompted to save the project before opening the Site
Download dialog. For each unit type, the list of files that can be downloaded varies. Those files
marked with a check need to be downloaded.

153
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 88: Site Download Dialog with List of Available Files

NOTE: To see all the files currently associated with the site in the Files list, select the View all
site files field (default). To view only the files that are checked in the Files list, deselect the View
all site files.

3. To specify the connection to be used for the download, perform one of the following steps:
● If the site is locally connected, select Local.
● If the site is remotely connected, make sure that the Site ID and Link ID are properly configured
(with the Local option deselected).
If the site supports redundancy, the Site ID field reflects the private ID (either Site ID+1 or Site ID-1),
as shown in the site view under the General tab. You cannot download firmware to the common site
ID.
NOTE: If a site is redundant, you must download to each CPU (primary and secondary)
individually.
4. To select non-firmware files for download, ensure that the blocks in the following table are deselected
(unchecked) in the Site Download dialog.

Table 13: Deselected Blocks During Non-Firmware File Download

RTU Type Block Name

ACE1000 N/A
ACE3600 Remote System File
IRRInet-M System File
MC-EDGE ● Kernel
● File System

After deselecting the relevant blocks, the other entries are enabled and can be selected in the Site
Download dialog.

154
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 89: STS–Site Download Dialog with Various Files

Depending on the unit type of the chosen site, different file types are visible in the dialog:
● For ACE1000, ACE3600, IRRInet-M, and MC-EDGE units: Site Configuration and Network
Configuration entries appear by default. For IRRInet-M units, the Site Table entry also appears.
Other file types may be added via the Add-On Manager. See Managing Add-On Files on page
180.
● For the ACE IP Gateway, the Site Table entry appears if the user has created a site table.
● For legacy RTUs: Network Configuration appears by default. The Site Configuration entry
appears only after the user imports a site configuration. See Importing Legacy RTU Site
Configurations on page 137.
● A Settings button appears next to Site Configuration, Ladder Application, and Site Source
(where such entries exist for a particular site).

5. Select the block or blocks that you want to download to the chosen site.
NOTE:
For ACE1000 and MC-EDGE, the STS limits which files can be downloaded together. See
Download Restrictions on page 146.
A site configuration with a mixed I/O expansion module cannot be downloaded to an IRRInet-M
RTU with a firmware version lower than 6.00.

155
6802979C10-BA
Chapter 3: MC-IoT STS Operation

6. Optional: If necessary (and relevant to the files chosen for downloaded), perform any of the following
actions.

If… Then…
If you want to change the perform the following actions:
site ID in the site configura- a. Click the Settings button next to Site Configuration entry.
tion1 file,
b. In the Site Configuration Settings dialog (shown in the fol-
lowing figure), change the value in the New Site ID field to the
preferred site ID.
Figure 90: Site Configuration Settings Dialog

NOTE: The system address is used in networks

where more than one system exists.
c. To save the changes and close the dialog, click OK.

If you want to change the perform the following actions:

ladder application2 down- a. Click the Settings button next to the Ladder Application
load settings, entry.
b. In the Ladder Application Setting dialog (shown in the fol-
lowing figure), configure the settings.
Figure 91: Ladder Application Setting Dialog

c. To save the setting and close the dialog, click OK.

156
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
ACE3600/IRRInet-ACE only: perform the following actions:
If you want to modify the site a. Click the Settings button next to the Site Source entry.
source3 package,
b. To add a user file, click Add User File and select the prefer-
red file using the Open dialog.
Figure 92: Adding Files to a Site Source

c. To save the changes and close the dialog, click OK.

1Site Configuration Settings:
After you add a site, any changes you make to the Site ID in the site configuration do not affect the
site ID in the RTU. If the Site ID was changed in the STS site configuration, it must also be changed in
the download settings of the site configuration file (as described in this step). The site ID change takes
effect in the RTU after the download.
In redundant sites: If the requested new site ID is already in use or reserved for the private ID of a
redundant peer (i.e. Site ID-1 or Site ID+1 in systems with redundancy), the STS prompts you to enter
a different site ID. When the private ID of the current RTU is changed, the common ID and peer ID are
changed accordingly. The IDs only change for the downloaded site and its peer (if such exists) if the
download was successful.
2Ladder Application Setting:
Select Load and Reset to download the application and restart the RTU. Choose this option if:
● This is the first time loading the RTU with an application.
● The RTU was previously programmed, but the database of the downloaded application has been
modified.
● You want to reset the database.
Select Load Only to download the application without restarting the RTU. Choose this option if the
RTU was previously programmed, and you want to retain the current database values.
NOTE: Do not use Load Only if you made any changes to:
● Database
● Constants
● Rungs that have differentiators or constants
If you make changes to the database and select Load Only, a prompt notifies you that Load Only is
not allowed because of changes made to the database. In this case, select Load and Reset. Under

157
6802979C10-BA
Chapter 3: MC-IoT STS Operation

certain circumstances, the prompt may not appear when differentiators are added to rungs. Therefore,
always select Load and Reset when adding a differentiator to a rung.
3Site Source:
The STS packs all the files listed in the dialog into a ZIP archive, which can then be downloaded. The
name of the archive is: <project name> .zip
Downloading a site source file larger than 1 MB is not recommended.
The amount of free Flash memory in the RTU should be substantially larger than the file size.
The Remove File icon is enabled only when files added by the user are selected.
7. In the Settings section of the Site Download dialog, select the preferred unit reset and flash erase
parameters from the drop-down lists.
For a list of available reset and erase parameters, see Site Download Reset and Erase Options on
page 159.
NOTE: To restore an ACE1000 or MC-EDGE unit to the default (factory) site configuration,
select Erase all flash before download.
8. Optional: To allow automatic resuming of unfinished downloads (if supported by the chosen site),
select the Resume option (default). If you deselect it, unfinished downloads will start from the
beginning.
9. Click Download.
NOTE:
If this is the first communication session of the MDLC driver, the STS prompts you for the MDLC
driver password before initiating the download.
If changes were made to the project, you are prompted to save the project before downloading.
If a CRC discrepancy is found between the I/O site configuration in the ladder application and in
the RTU, an error appears. Download the site configuration and the application again.
If the configuration or application version is lower than that of the firmware, an error message
appears.

An Abort button replaces the Download button. Any messages/errors are displayed in the Download
Progress window.
In the right side of the window, two respective progress bars show the progress of the current file
download and of the download overall.
If the site ID was changed in the unit, the new site ID appears in the STS site view.
ACE1000 and MC-EDGE only: As the result of a bundle download, the system version displayed on
the RTU icon may change.

10. To close the Site Download dialog, click Close.

158
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.3.13.6
Site Download Reset and Erase Options
When downloading to a site via the Site Download dialog, the STS user can decide to reset the unit and/or
to erase the flash.
NOTE: Settings made in the Site Download window are retained for use during the next download
session.

Table 14: Download Unit Reset and Flash Erase Parameters

Parameter Available settings

Unit reset ● Let System decide when reset (default)
● Don’t reset after download
● Reset after total download

Flash erase type ● Don’t erase flash before download (default)

● Erase all flash before download
● Erase flash and preserve siteConf
● Erase applications before download (MC-EDGE® only)
NOTE: For remote MC-EDGE sites connected beyond RS485, do not
select the Erase all flash before download option. For any other
scenario, the user can select any preferred flash erase setting.

3.3.14
Uploads from Sites
Files from ACE1000, ACE3600, and MC-EDGE units can be uploaded to the STS, and then added to a
project. Legacy RTU units do not support this feature.
The STS user uses the Site Upload utility to view a list of the files available for upload from a chosen unit.
Only the following types of files can be uploaded and viewed using STS utilities:
● Site configurations
● Phonebooks
● Network source files
● IP conversion tables
● Site tables
● Site source files
● PKI Configuration
Other files that are stored in the unit cannot be viewed using STS utilities, and therefore cannot be uploaded.
For redundant sites, files from a secondary site cannot be uploaded to a primary site and vice versa.
Uploaded files are named according to the site ID of the unit from which they originated. For example, when
uploading an IP conversion table, the file is named: upl#<site id>.ipc
If the file has been uploaded before, you are prompted to overwrite the existing file or rename it as:
upl#<site id>_<n>.ipc
For ACE1000 and MC-EDGE units: After upload, if the DNP Client (Master) is enabled in the RTU, the
uploaded file list includes three additional files:

159
6802979C10-BA
Chapter 3: MC-IoT STS Operation

DNP Master Configuration

Specifies the configuration stored in the RTU. This file is the same configuration file that was downloaded
by the user.
DNP Master report
Specifies the mapping between the I/O Server (Slave)/Client (Master) elements in the system to the RTU
tables.
DNP Master tags
Specifies the InTouch tags that could be loaded to the InTouch application.
For ACE1000 units: After upload, if the DNP Server (Slave) is enabled in the RTU, the uploaded file list
includes one additional file:
DNP Slave report
Specifies the mapping between the I/O Server (Slave) elements to the RTU tables.

3.3.14.1
Uploading Files from Sites
This section describes the procedure for uploading files from an RTU for use in the STS project.
To create a new site in the project by uploading it from an RTU, see Uploading New Sites to STS on page
202.

Procedure:
1. From the site view, click Upload.
2. To specify the connection to be used for the upload, perform one of the following steps.
● If the site is locally connected, select Local.
● If the site is remotely connected, make sure that the Site ID and Link ID are properly configured
(with the Local option deselected).
Figure 93: STS–Upload Dialog

3. To connect to the site, click OK.

The Site Upload dialog displays a list of all the files in the RTU.

4. From the Files list, select the preferred files.

160
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 94: STS–Site Upload Dialog

NOTE:
Entries lacking a check box cannot be uploaded to the STS. See Uploads from Sites on page
159.
If no site configuration was ever downloaded to the unit, the Default Site Configuration label
appears in the Site Upload dialog.
5. To upload the selected files, click Upload.
An Abort button replaces the Upload button. The progress bar displays the progress of the upload.
Any errors or messages are displayed in the Upload Progress box in the bottom-left portion of the
dialog.

Result: After the upload, the files can be manipulated in the project.

Example:
The uploaded IP conversion table appears in the IP Conversion Table File Manager and can be assigned to
sites.

3.3.15
Upgrading ACE3600 System Firmware
Procedure:
1. Open the preferred site, and then select Site → Change RTU Version...
2. From the drop-down list, select the preferred system version and click OK.

161
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 95: Change RTU Version Dialog

NOTE: The list of system versions for each unit type can be viewed in the Inventory tab under
RTU. System firmware versions and STS (configuration/application) versions are correlated
(15.00/15.50, 16.00/16.50, 17.00/17.50, etc.)
The Upgrade Information prompt appears, describing the changes that will occur to the system,
configuration, and application.
Figure 96: Upgrade Information Prompt

If the upgraded site contains an application that is assigned to other sites, the RTU Version
Information dialog prompts the user to either upgrade all the assigned sites, or to unassign the
application from the site to be upgraded.
Figure 97: Application Version and Site Version Mismatch

162
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3. To apply the change or changes, click OK.

IMPORTANT:
The Change RTU Version operation cannot be undone.
When upgrading the firmware, the site configuration and application versions in the STS are also
upgraded.
The firmware and other upgraded files become available for download in the Site Download dialog.
The firmware file (Remote System File) is checked in the dialog, and the site status is marked as
NeedsDownload.

4. To access the Site Download dialog, click Site → Download...

5. Download the Remote System File to the RTU. See Downloading System Firmware to ACE3600 and
IRRInet-M Sites on page 147.
The upgraded firmware is downloaded to the RTU.
NOTE: When the versions of the site configuration, application and firmware are not
synchronized, the application may not operate properly.

Postrequisites:
As a result of the changed firmware version, certain site files (such as Site Configuration, Ladder Application,
IOS file, IPC V6) may be affected. In that case, these files are marked with a check mark in the Site
Download dialog (i.e. “Needs Download”). If there is an assigned application, it must be recompiled.
Download all marked files, including the recompiled application, in order to complete the firmware version
change.
For more information on downloading, see Downloads to Sites on page 145.

3.3.16
MC-EDGE RTU Version Change
You can change the MC-EDGE RTU version in the STS project in two ways.
One method is to download a file system or bundle, which automatically changes the RTU version in the STS
project. See Downloading System Firmware to MC-EDGE Sites on page 151.
The other method is to manually change the RTU version. To do this, the user selects the preferred site, and
from the menu bar clicks Site → Change RTU Version.
NOTE:
Manually changing the version via the Change RTU Version menu only changes the RTU version in
the STS project. This does not change the actual RTU version. To perform an actual RTU upgrade, you
need to either install the new system from the SD card, or use the Add-On Manager and Downloader to
download the new file system or bundle to the unit.
In both cases, the site configuration version in the project is updated. You may also need to download the
new site configuration, which includes the new features.
Manually changing the RTU version to an older system version via the Change RTU Version menu is not
possible. If you installed an older system from the SD card, you have to re-create the unit from the Inventory
using the required version in the Previous subfolder.

163
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.3.17
Closing STS Projects
Procedure:
1. To close a project in the STS, select File → Close Project.

You are prompted to save any changes made to the project.

If any sites or areas were added to the project but not yet saved, the following dialog appears:
Figure 98: Closing an STS Project – Example 1

If any other changes (not pertaining to sites or areas) were made to the project, the following dialog
appears:
Figure 99: Closing an STS Project – Example 2

2. Perform one of the following actions:

● To save the changes, click Save or Yes (depending on the dialog).
● To discard the sites/areas from the project, click Don't save or No (depending on the dialog).
● To keep the project open (without saving or discarding the changes), click Cancel.

3.4
Administering the System
3.4.1
Opening Existing Projects
Procedure:
1. Perform one of the following steps.
● If the STS is not yet open, click Start → Programs → Motorola MC-IoT System Tools Suite
<version> → STS.

164
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

● If the STS is already open, from the menu bar select File → Open Project.
The STS Open Project dialog appears.
Figure 100: STS–Open Project Dialog

2. To open a project, perform one of the following steps.

If… Then…
If you want to open a perform the following actions:
project listed in the Open a. Select the preferred project from the list.
Project dialog,
b. Click Open.

If you want to open perform the following actions:

a project (not listed in a. Click Other project...
the Open Project dia-
log) that was created in b. Browse for the preferred project file (with .spj file extension).
the same version of the c. To import the project to the current STS installation, click Open.
STS,

165
6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
If you want to open perform the following actions:
a project (not listed in a. Click Other project...
the Open Project dialog)
that was created in a b. Browse for the preferred project file (with .spj file extension.
previous version of the c. To import the project to the current STS installation, click Open
STS,
d. To upgrade the project to the current STS version, click OK when
prompted (as shown in the following figure).
Figure 101: Upgrading Project to Newer STS Version

NOTE: Projects can be removed from the projects list in the Open Project dialog. To remove a
project, right-click it and select Remove project From list. To return a project to the list, click
Other Project and browse for the project file. After you open the project, it is visible again in the
projects list.

3.4.2
Managing Applications
The STS Application Manager enables the user to create, edit, and delete ACE3600 and MC-EDGE
applications, and to assign them to sites. To view, edit, or program applications for legacy RTUs, use the
relevant Programming ToolBox or Easy Configurator tool.
The Application Manager includes a list of Applications in the left pane, and a list of Sites in the right pane.
You can view either section as either a simple list, by selecting View List; or as a detailed list, by selecting
View Details (default).

166
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 102: STS – Application Manager

Prerequisites: Open the Application Manager by clicking System → Application Manager.

Procedure:
● If you want to create an application for an ACE3600 or MC-EDGE unit, perform the following actions:

a. Click the New Application icon.

b. Enter a Name for the application.
c. Select the required application type: ACE3600 (Ladder) or MC-EDGE (User tables).
d. To create the application, click OK. The new application program opens in the Application
Programmer window.
For details on programming an application, see Application Programmer on page 324.
● If you want to import an existing application into the project, perform the following actions:

a. Click the Browse and Import icon.

b. Browse to the preferred application program (file ending in .adb, .prg, or .axml).
c. To add the selected program to the project, click Open.
NOTE: If you open a .prg file, it is converted into an ACE3600 application file ending
in .adb
● If you want to view or edit an existing application for an ACE3600 or MC-EDGE unit, perform the
following actions:
a. From the Applications list, select the preferred application.

b. To open the selected application program in the Application Programmer, click the Edit
Application icon.
● If you want to delete one or more existing applications, perform the following actions:
a. From the Applications list, select the preferred application or applications.

167
6802979C10-BA
Chapter 3: MC-IoT STS Operation

b. Click the Delete icon.

c. To delete the file and save the STS project, click Yes at the prompt.
● If you want to assign an application to one or more sites, perform the following actions:
a. From the Applications list, select the preferred application.
b. In the Sites list, select the site or sites to which you want to assign the chosen application.
NOTE: Only compatible sites are enabled in the list:
○ The application version must be greater than the system software version.
○ ACE3600 applications cannot be assigned to MC-EDGE or to legacy units.
○ MC-EDGE applications cannot be assigned to ACE3600.
○ No application can be assigned to an ACE IP Gateway.
c. To apply the changes, click Apply.
If another application was previously assigned to any of the selected sites, you are prompted to
confirm the application changes. Click OK to reassign the site or sites.
Once an application is assigned to a site, the site appears on the Select Site screen when the
application opens. See Selecting Sites in the Application Programmer on page 365.
● If you want to upgrade an application to the current version, perform the following actions:
a. From the Applications list, select the preferred application.

b. Click the Upgrade Application icon.

c. Specify the new application name.
Figure 103: Naming the Upgraded Application

d. To upgrade the application, click OK. The application version is updated and the application can
be assigned to RTUs with the corresponding system.
● If you want to convert an ACE3600 application to the MC-EDGE application format, perform the
following actions:
a. From the Applications list, right-click the preferred application.
b. Select Convert to MC-EDGE...
For more details, see Converting ACE3600 Application Databases to MC-EDGE Format on page
388.
Postrequisites:
To close the Application Manager, perform one of the following actions:
● To save any changes and close the dialog, click OK.

168
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

● To discard any unsaved changes and close the dialog, click Cancel.
NOTE:
When deleting an application or converting it to the MC-EDGE application format, the STS prompts the
user to save the project. If the user selects Yes to save these changes, they cannot be later reversed
(even if the user clicks Cancel to close the Application Manager without saving).
When creating an application or importing it to the Application Manager, the file is automatically saved
to the project. To undo this action, manually delete the application by selecting it from the Applications
list and clicking Delete.

3.4.3
Editing Link Type Costs
Each type of communication link in the system has an associated cost. The application uses the link costs to
calculate the actual cost of each transmission route and to decide which route to use.
By following the procedure in this section, the STS user can change the default cost of each link type for all
links within the entire project. To set the cost of one specific link, see Configuring MDLC Links on page 173.

Procedure:
1. To edit the default link costs, select System → Set MDLC Link Costs...
2. Change the values as preferred.
Figure 104: Set MDLC Link Costs Dialog

NOTE: You can restore the previous default values by clicking Set Defaults.

3. To save the changes and close the dialog, click OK.

Postrequisites: Editing link costs causes the existing network tables to be changed. As a result, the network
configuration must be downloaded again to existing sites. All sites with an attached network table will be
marked as Needs Download.

3.4.4
Network Tables
The STS automatically creates a system-wide network table, which defines the communication nodes (points
of interconnection between two or more links) in the network.
This table defines the network structure, which consists of those sites capable of automatically routing
information packets through the network (this excludes RTUs connected via one link only). The same network

169
6802979C10-BA
Chapter 3: MC-IoT STS Operation

table is used for all sites in the system, including both ACE3600 and legacy sites. To enable each site to route
the packets through the network, the network table must be loaded to all node sites in the system.
NOTE: Links of the type COMPUTER1-COMPUTER9 are not considered links in the network.

This generic network table is read-only and is automatically updated to reflect changes to the system (such
as new sites and new links). The user can also create customized tables, which can be edited and deleted.
The user is responsible for updating the contents of these customized tables.
The Network Manager enables the user to create, edit, copy, and delete the network tables in a project.
For more information on network configuration, see the “Network Configuration” chapter of the MC-IoT STS
Advanced Features manual. For details on customizing a network table, see Editing Network Tables on page
172.

3.4.4.1
Managing Network Tables
The Network Manager dialog includes a list of Network tables in the left pane, and a list of Sites in the right
pane.
You can view either section as either a simple list, by selecting View List; or as a detailed list, by selecting
View Details (default).
Figure 105: STS – Network Manager

NOTE: If the user adds a new site or changes the site ID of an existing site, the STS automatically
updates the generic network table. The STS applies these changes when the user saves the site. User-
created tables, however, must be manually updated by the user.
Prerequisites: Open the Network Manager by clicking System → Network Manager.

170
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Procedure:
● If you want to create a network table, perform the following actions:

a. Click the New table icon.

b. In the Network Configuration Editor, make the preferred changes to the new table.
See Editing Network Tables on page 172.

c. Click the Save icon and enter a name for the new table.
d. To save the table, click OK.
e. To close the Network Configuration Editor and return to the Network Manager, click Close.
● If you want to edit an existing network table, perform the following actions:
a. From the Network tables list, select the preferred network table.

b. Click the Edit Table icon.

c. In the Network Configuration Editor, make the preferred changes to the table.
See Editing Network Tables on page 172.

d. To save the changes, click the Save icon.

e. To close the dialog and return to the Network Manager, click Close.

To close the table editor without saving the changes, do not click the icon. Instead, click Close
and select No when prompted to save the changes.
● If you want to delete an existing network table, perform the following actions:
a. From the Network tables list, select the preferred network table.

b. Click the Delete Table icon.

c. To confirm table deletion, click Yes when prompted.
● If you want to copy an existing network table, perform the following actions:
a. From the Network tables list, select the preferred network table.

b. Click the Save Table As... icon.

c. In the Specify New Item Name dialog that appears, enter the name of the new table and click
OK.
A copy of the original table (with the new name) appears in the Network tables list, where it can be
selected for further action.

● If you want to attach a network table to one or more sites, perform the following actions:
a. From the Network tables list, select the preferred network table.
b. In the Sites list, select the site or sites to which you want to attach the table.
If a site is already selected, deselecting it will detach the table from that site.
NOTE: Only one network table can be attached to a given site. When attaching a table, any
previously attached table will be automatically detached.
c. To save the changes and close the Network Manager, click OK.

171
6802979C10-BA
Chapter 3: MC-IoT STS Operation

● If you want to detach a network table from one or more sites, perform the following actions:
a. From the Network tables list, select the preferred network table.
b. In the Sites list, deselect the site or sites from which you want to detach the table.
If a site is already deselected, selecting it will attach the table to that site.
c. To save the changes and close the Network Manager, click OK.

3.4.4.2
Editing Network Tables
The Network Manager enables the user to create and edit network tables in a project. Unlike the read-only
generic network table, which is automatically generated and updated by the STS, user-created tables are
fully customizable.
NOTE: If the site ID is changed in the project, or if a new site is added to the project, any user-defined
network tables must be updated manually by the user. For more information, see Network Tables on
page 169.
Prerequisites:
1. Open the Network Manager by clicking System → Network Manager...
2. Open a new or existing table in the Network Configuration Editor. If you want to edit the generic
network table, first make a copy of the table and then open the copied file for editing. See Managing
Network Tables on page 170.
Figure 106: Editing a Table in The Network Configuration Editor

172
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Procedure:
● If you want to add, modify, or delete the links attached to a site, use the Link ID drop-down list for that
site.
● If you want to add a site ID to the table, double-click an empty cell in the Site ID column and enter the
preferred site ID.

● If you want to remove a site ID, click the row index number for that site and select the Remove
rows icon.

● If you want to edit the link costs, click the Edit links cost icon.
NOTE: Editing link costs affects all network tables in the project. See Editing Link Type Costs on
page 169.
● If you want to allow transmitting nodes to choose an alternate data routing path when the initial direct
link fails, click the Alternative path to Local Link icon.
NOTE:
When enabled, paths via remote sites (if such an alternate exists) may be used instead of a link
that directly connects two RTUs. To disable, click the icon again.
For more information on network routing, see “Network Configuration” in the MC-IoT STS
Advanced Features manual.

● If you want to save the customized network table, click the Save icon.
● If you want to close the Network Configuration Editor, click Close.
NOTE: If you close the editor without saving, any changes are lost.

3.4.5
Configuring MDLC Links
The MDLC Links Configuration utility allows you to change the number of links (such as lines, RS links,
radio links, and zones) assigned to each medium.
The utility displays the links in a grid, where each square represents a link. Links are colored according to the
port type to which they are allocated (an unallocated link is represented by a gray box). If an allocated link is
in use, its square is also marked with lines. Links that have a specific link cost (differing from the default link
cost) are marked with a blue corner.
To see what link a particular square in the grid represents, hover your mouse over it. The link information is
displayed in the bottom-right corner of the dialog in the Link name section (as shown in the following figure).

173
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 107: MDLC Links Configuration Utility

NOTE:
MDLC Links Configuration should be performed at the beginning of system definition, before links have
been assigned to ports in sites. If necessary, links can be configured at any time.
Links that are currently assigned to sites cannot be removed.
Prerequisites: Open the MDLC Links Configuration utility by selecting System → MDLC Links
Configuration...

Procedure:
● If you wan to change the quantity of links of a certain type (for example, RS links), perform the
following actions:
a. Click the Allocated value of the chosen link type.
b. To change the value, click the up and down arrows of the spin control.
The number of Free Links changes accordingly (such as by decreasing when the user allocates
additional links). The number of squares in the grid representing the link type (such as green squares
for RS links) also changes. When allocating additional links, all subsequent link squares move lower in
the grid.
● If you want to change the quantity of radio zones (by default 9) associated with a radio link, perform
the following actions:
a. For the chosen radio zone, click the down arrow in the Allocated column.
b. From the drop-down menu, select the preferred quantity.
The number of Free Zones changes accordingly (such as by decreasing when the user allocates
additional zones).
● If you want to restore all links and zones to their default quantities, click Restore Defaults.

174
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

● If you want to set the specific link cost of an assigned link, perform the following actions:
a. Right-click the link.
b. Select Set specific cost to <link name>...
c. Input the preferred value in the Specific Cost field.
d. To save the change and close the Set Specific Cost dialog, click OK.
The specific cost of the chosen link is now set. Network routes are recalculated based on the new
cost.
NOTE: Setting the specific cost of a particular link does not change the cost of other links of
the same link type. Unless it has an assigned, specific cost, each link operates according to
the default link cost associated with its link type. For setting default link costs, see Editing
Link Type Costs on page 169.

● If you want to restore the default cost of an assigned link with a specific cost, right-click the link and
select Restore Default Cost.
The Default Cost is the default link cost for that particular link type, as set in the MDLC Link Costs tool.
See Editing Link Type Costs on page 169.

Postrequisites: To save the changes and close the MDLC Links Configuration dialog, click OK.

3.4.6
IP Conversion Tables
The STS user can create a system-wide IP Conversion Table, which contains all the sites defined in the
system with IP links, and the IP addresses defined for these sites/links. A customized IP Conversion table
can also be created for an individual site.
If the site ID is changed in the project, or if new sites are added to the project, any user-defined IP
Conversion tables must be updated manually by the user.
When an IP conversion table is assigned to an IRRInet-M RTU, DNS is not supported.

3.4.6.1
Managing IP Conversion Tables
The STS IP Conversion Table Manager enables the user to create, edit, copy, and delete IP conversion
tables, and to assign them to ACE3600 and MC-EDGE sites. IP conversion tables for legacy RTU sites are
handled via the Add-On Manager.
The left side of the IP Conversion Table Manager lists the IP Conversion Tables Files in the project. The
right side of the screen lists the Sites in the project.
You can view either section as either a simple list, by selecting View List; or as a detailed list, by selecting
View Details (default).

175
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 108: STS – IP Conversion Table File Manager

Prerequisites: Open the IP Conversion Table File Managerby clicking System → IP Conversion Table
Manager...

Procedure:
● If you want to create an IP conversion table, perform the following actions:

a. Click the New IP Conversion Table File icon.

b. In the table rows, enter the preferred site ID, link ID, and IP address/host domain name
information.

c. Click the Save icon and enter a name for the new table.
d. To save the table, click OK.
e. To close the dialog and return to the IP Conversion Table File Manager, click Close.
For information on setting up IP conversion tables, see the “IP Conversion Tables” section in the
MC-IoT STS Advanced Features manual.
● If you want to edit an existing IP conversion table, perform the following actions:
a. From the IP Conversion Table Files list, select the preferred IP conversion table.

b. Click the Edit IP Conversion Table File icon.

c. Make the preferred changes to the table.

d. To save the changes, click the Save icon.

176
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

e. To close the dialog and return to the IP Conversion Table File Manager, click Close.

NOTE: To close the table editor without saving the changes, do not click the icon.
Instead, click Close and select No when prompted to save the changes.
For information on editing the contents of IP conversion tables, see Editing IP Conversion Table
Files on page 177.
● If you want to copy an existing IP conversion table, perform the following actions:
a. From the IP Conversion Table Files list, select the preferred table.

b. Click the Copy IP Conversion Table File icon.

c. In the Enter File Name dialog that appears, enter the name of the new table and click OK.
A copy of the original table (with the new name) appears in the IP Conversion Table Files list,
where it can be selected for further action.

● If you want to attach an existing IP conversion table to one or more sites, perform the following
actions:
a. From the IP Conversion Table Files list, select the preferred table.
b. In the Sites list, select (check) the preferred site or sites.
c. To save the changes and close the IP Conversion Table File Manager, click OK.

After you attach an IP conversion table to a site, it appears in the list of downloadable files for that
site in the Site Download utility.
NOTE: Only one IP conversion table can be attached to a given site. If a site already has an
assigned IP conversion table, the previously assigned table is detached when a new table is
assigned.

● If you want to detach an existing IP conversion table from one or more sites, perform the following
actions:
a. From the IP Conversion Table Files list, select the preferred table.
b. From the list of Sites, deselect the site or sites from which you want to detach the table.
c. To save the changes and close the IP Conversion Table File Manager, click OK.
● If you want to delete an existing IP conversion table, perform the following actions:
a. From the IP Conversion Table Files list, select the preferred table.

b. Click the Delete IP Conversion Table File icon.

c. To confirm table deletion, click Yes when prompted.

3.4.6.2
Editing IP Conversion Table Files
The IP conversion table editor allows the STS user to add or modify individual entries in an IP conversion
table.
The IP conversion table editor includes additional functions beyond the scope of these instructions (such as
sorting table entries). For descriptions of all the IP conversion table editor functions, see IP Conversion Table
Editor Functions on page 179.

177
6802979C10-BA
Chapter 3: MC-IoT STS Operation

For information on setting up the IP conversion table, see the “IP Conversion Tables” section in the MC-IoT
STS Advanced Features manual.

Procedure:
1. From the menu bar, select System → IP Conversation Table Manager...
2. To open an IP conversion table for editing, perform one of the following steps in the IP Conversion
Table File Manager:
● If you want to edit an existing table, open the preferred table for editing.
● If you want to fill in a blank table, create a new table and open it for editing.
For detailed instructions on creating and opening site tables, see Managing IP Conversion Tables on
page 175.
The new or existing IP conversion table opens in the IP conversion table editor.
Figure 109: IP Conversion Table Editor

3. To define a site ID in the table, perform one of the following steps.

If… Then…
To add a new site to perform the following actions:
the table, a. Double-click an empty cell in the Site ID column.
b. Enter the site ID of the preferred site (as defined in its site configura-
tion).

To modify the site ID perform the following actions:

of an existing entry a. In the chosen entry (row), double-click the cell in the Site ID column.
in the table,
b. Modify the site ID.

NOTE: One site may appear more than once in the table, provided that each entry has a unique
link ID.
4. To define or modify the link ID, use the drop-down list in the Link ID cell (located in the same row as
the site ID of the preferred site).

178
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

5. To define or modify the IP Address or Host Domain Name, double-click the cell (located in the same
row as the site ID of the preferred site) and enter the preferred value.
NOTE: When routing on MDLC over an IP port, the fixed IP address or domain name of the FEP
should be specified for the FEP and for each RTU communicating over the FEP port. In addition,
the parameter Enable routing on MDLC over IP port must be enabled in site configuration of
the FEP port.
6. Optional: To delete one or more rows, perform the following actions:
a. In the first column (located to the left of the Site ID column), click the number of the preferred row.
To select multiple, sequential rows, click the number of the first row in the series. Then, while
holding the Shift key, select the final row in the series.

b. Click the Delete Selected Line(s) icon.

c. To confirm deletion, click Yes.
7. To close the IP conversion table editor, perform one of the following steps:

If… Then…
To save the changes to an perform the following actions:
existing site table file be-
fore closing,
a. Click the Save icon.
b. Click Close.

To save a newly created perform the following actions:

site table file before clos-
ing,
a. Click the Save icon.
b. In the Enter File Name dialog, enter a name for the new table
file.
c. To save the file, click OK.
d. Click Close.

To discard the changes perform the following actions:

and close the editor, a. Click Close.
b. When prompted to save the changes, click No.

3.4.6.3
IP Conversion Table Editor Functions
Table 15: IP Conversion Table Editor Functions

Icon Function Name Description

Save Saves any changes made to the table.

Print Opens the Windows print dialog, from which the print parameters
can be set before printing the IP conversion table.
Print Preview Opens a print preview of the IP conversion table (from which the
table can be viewed and printed)

179
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Icon Function Name Description

Insert New Line Inserts new (blank) row above the currently selected row.

Delete Selected Line(s) Deletes the selected row or rows.

NOTE:
The icon is active when at least one row is selected.
Sort Sort by Site ID: Sorts all of the entries in the table by site ID.
When multiple entries with the same site ID appear in a table, the
● Sort by Site ID (de-
entries within that group are sorted by Link ID.
fault)
Sort by Link and Site: Sorts all of the entries in the table by link
● Sort by Link and Site
ID. When multiple entries with the same link ID appear in a table,
the entries within that group are sorted by Site ID.
NOTE: By default, clicking the icon sorts by site ID. To
sort by link, use the drop-down menu located to the right
of the icon.

3.4.7
Managing Dynamic IP Access Tables
With firmware version 21.00 and above, both the ACE3600 and the ACE4600 support the use of firewalls
with IP conversion learning disabled. In this case, reception is rejected from sites that were not configured in
the IP Conversion Table, or from sites with different IP addresses.
The STS user creates a Dynamic IP Access Table to grant access to specific sites that may have one of
several IP addresses.

Procedure:
To open the Dynamic IP Access Table File Manager, select System → Dynamic IP Access Table File
Manager...
For instructions on using the Dynamic IP Access Table Manager, follow the procedure for using the IP
Conversion Table Manager. See Managing IP Conversion Tables on page 175.

3.4.8
Managing Add-On Files
The STS Add-On Manager enables the user to attach a number of files to the site, such as: PLC files, ‘C’
applications, ‘C’ application parameter files, NTP configuration files, and modem configuration files.
The window header indicates the currently selected add-on file type for the chosen type of RTU. By default
(when no particular site is selected), the Add-On Manager opens to the ‘C’ Application file type for ACE3600.

180
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 110: STS – Add-On Manager

The left pane of the Add-On Manager lists the available File Types for the selected RTU type. The user can
choose a different RTU type from the drop-down list.
The center pane (Files in Project) lists the add-on files (if any) of the selected file type that are currently
attached to the project.
The right pane lists the Sites in the project. A check mark next to a particular site indicates that the currently
selected add-on file is attached to that site.
In both the center and right panes, you can choose to view the contents as:
● a detailed list, by clicking View Details (default)
● a simple list, by clicking View List
For IRRInet-M RTUs, “slave” or “master” appears beside the application name in the Files in Project list.
For detailed information on the add-on files available for each type of RTU, see the tables in RTU Add-On
File Types on page 182.
Prerequisites: Open the Add-On Manager by clicking System → Add-On Manager....
NOTE: Alternatively, you can open the Add-On manager for a particular site by clicking the Add-On
Manager... button from within the site configuration view. However, if the chosen site definition includes
an invalid combination of ports, the Add-On Manager will not open.

Procedure:
● If you want to add a new file to the project, perform the following actions:
a. From the drop-down list in the File Types pane, select the preferred RTU type (such as ACE3600,
ACE Gateway, IRRInet-M, ACE1000, or MC-EDGE).
b. Select the preferred file type from the File Types list.

c. Click the Browse and Import icon.

d. In the Add dialog that appears, browse to the file.
e. To add the preferred file to the project, click Open.

181
6802979C10-BA
Chapter 3: MC-IoT STS Operation

● If you want to delete one or more add-on files from the project, perform the following actions:
a. From the Files in Project list, select the preferred file or files.

b. Click the Delete icon.

c. To confirm the action and delete the selected file or files, click Yes.
● If you want to attach an add-on file to one or more sites, perform the following actions:
a. From the Files in Project list, select the preferred file.
b. From the Sites list, select the preferred site or sites.
c. To save the changes and close the Add-On Manager, click OK.
The selected file is attached to the chosen site or sites. The file appears in the list of files available
for download in the Site Download dialog for the chosen site or sites. If View Details is selected,
the file name appears next to the associated site names in the Sites list (in the Add-On Manager).
The file also appears in the list of Add-Ons in the site view.
NOTE:
In a system with redundancy, add-on files attached to one peer are not automatically
attached to the other peer site.
For each file type, only one file can be attached to a given site at a time, except for:
○ ‘C’ applications
○ ‘C’ application parameters (with and without reset)
○ ACE1000 and MC-EDGE bundle files

● If you want to detach an add-on file from one or more sites, perform the following actions:
a. From the Files in Project list, select the preferred file.
b. From the list of Sites, deselect the site or sites from which you want to detach the selected add-on
file.
c. To save the changes and close the Add-On Manager, click OK.

3.4.8.1
RTU Add-On File Types
Each type of RTU is compatible with certain types of add-on files. The following tables list the file types
available for each RTU, along with the relevant file type extensions.

Table 16: Add-On Files for ACE3600 RTU Type

File Type File Extension ACE3600/ IR- ACE IP Gate-

RInet-ACE way
PLC[1|2|3] to Server (Slave) .2S_PLC[1|2|3] X
PLC[1|2|3] to Client (Master) .2M_PLC[1|2|3] X
‘C’ Application .plz X
‘C’ Application Parameters *.* X
‘C’ Application Parameters without reset *.* X
NTP Configuration .ntp X X
Modem Configuration [PI1|SI1|SI2|PI2] .stm X X

182
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

File Type File Extension ACE3600/ IR- ACE IP Gate-

RInet-ACE way
PLC Translation File .plc X

Table 17: Add-On Files per Legacy RTU Type

File Type File Exten- MOSCAD/ MOSCAD- IP Gate-

sion MOSCAD-L M way
Ladder Application .b, .s X
PLC 1, 2, 3 .fls X
PLC to Client (Master) 1, 2, 3 .fls X
Sites Table .stb X X X
‘C’ Application .fls X X
Application Source *.* X
IP Configuration .ipp X X
MOSCAD ACA Code .fls X
MOSCAD ACA Data .fls X
‘C’ Application Parameters *.* X X
NetMon ‘C’ Application Parameters .prm X X
IP Conversion Table .ipc X X X
‘C’ Application Parameters without reset *.* X X
Compressed Files .cmp X
RDLAP Modem IDs Table .fls X X
MAP27 Address Conversion Table .m27 X
Feature File .ftr X
Modem Configuration File 1, 2, 3 .stm X X X
Host Table .hst X
DataTac Modem IDs Table .rnc X
NTP Configuration .ntp X
DMS File .ind X

Table 18: Add-On Files for IRRInet-M RTU Type

File Type File Extension

‘C’ Application .fls
Application Source *.*
IP Configuration .ipp
‘C’ Application Parameters *.*
NetMon ‘C’ Application Parameters .prm
IP Conversion Table .ipc

183
6802979C10-BA
Chapter 3: MC-IoT STS Operation

File Type File Extension

‘C’ Application Parameters without reset *.*
Compressed Files .cmp
RDLAP Modem IDs Table .fls
Modem Configuration File 1, 2, 3 .stm

Table 19: Add-On Files for ACE1000 RTU Type

File Type File Extension

‘C’ Application .plx (default)
‘C’ Application Parameters .dat (default)
IEC61131 Application File (Codesys programmer file)1 .app
IEC61131 Application CRC File (Codesys programmer CRC .crc
file)1
Package .rpm (default)
Bundle .rpm (default)
DNP Client (Master) .xml

1See “Appendix E CODESYS IEC61131-3 Programmer Applications” in the ACE1000 Easy Configurator
User Guide.

Table 20: Add-On Files for MC-EDGE RTU Type2

File Type File Extension

‘C’ Application .plx (default)
‘C’ Application Parameters .dat (default)
IEC61131 Application File (Codesys programmer file)3 .app
IEC61131 Application CRC File (Codesys programmer CRC .crc
file)3
IEC61131 Ucall library file .so
Package .rpm (default)
Bundle .rpm (default)
DNP Client (Master) .xml
Kernel .rpm
File System .bin
MQTT broker certificate4 broker.crt (full file name)
MQTT broker private key4 broker.key (full file name)
CA certificate4 .crt
MQTT bridge certificate bridge.crt (full file name)
MQTT bridge key bridge.key (full file name)
LoRa Gateway station certificate .crt

184
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

File Type File Extension

LoRa Gateway station key .key
LoRa CA certificate .trust
LoRaWAN Gateway certificate .crt
LoRaWAN Gateway key .key
IPsec peer key .key
IPsec peer certificate .crt
IPsec CA certificate .crt

2Including IRRInet-EDGE, NFM-EDGE, and AuxIO-EDGE RTUs

3See “Appendix E: CODESYS IEC61131-3 Programmer Applications” in the ACE1000 Easy Configurator
User Guide.
4See the “External MQTT Applications” section in Considerations for Sending and Receiving Device Data on
page 652.

3.4.9
Encrypting MC-EDGE Add-On Files (Secured STS Only)
For MC-EDGE units in secured projects, you can add new files to the project and immediately encrypt them
to prevent unauthorized access to sensitive information (such as LTE passwords). This procedure applies
only to 'C' application parameters (.dat files) and MQTT broker private key files (broker.key).
Encrypted files are decrypted in the memory when downloaded. They can be edited without creating a
decrypted file on the disk. Only authorized users can encrypt and access encrypted files. For this purpose,
there are two permissions in the role definitions:
● Encrypt data files
● View/download/decrypt encrypted files
NOTE: If the current user has decryption access, the STS Downloader decrypts files automatically and
displays their original decrypted file size. For users with no decryption access, the size is displayed as
encrypted. Users lacking decryption access cannot download encrypted files.
Figure 111: Encrypted 'C' Application Parameters

Prerequisites:
1. Open the Add-On Manager by selecting System → Add-On Manager...
2. From the drop-down list in the File Types pane, select MC-EDGE.

185
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Procedure:
● If you want to add an existing file to the project and encrypt it, perform the following actions:
a. In the File Types pane, select the relevant file type.

b. In the Files in Project pane, click the Browse and import (encrypted) icon.
c. In the Add dialog box, browse to the file and click OK.
The file is encrypted and stored in the project. A lock sign appears on its icon. You can attach, detach,
and delete encrypted files as described in Managing Add-On Files on page 180.

● If you want to encrypt a 'C' application .dat file that already exists in the project, perform the following
actions:
a. In the File Types pane, select 'C' Application Parameters.
b. In the Files in Project list, right-click the preferred file.
c. Select Encrypt.
● If you want to decrypt a file, perform the following actions:
a. In the File Types pane, select the relevant file type.
b. In the Files in Project list, right-click the preferred file.
c. Select Decrypt.
● ASCII only: If you want to edit an encrypted file, perform the following actions:
a. In the File Types pane, select the relevant file type.
b. In the Files in Project list, right-click the preferred file.
c. Click Edit.
d. Edit the file, and then press Enter.
● Binary files only: If you want to edit an encrypted file, perform the following actions:
a. In the File Types pane, select the relevant file type.
b. In the Files in Project list, right-click the preferred file and select Decrypt.
c. Edit the file.
d. To re-encrypt the file, right-click it and select Encrypt.

3.4.10
Site Tables
A site table defines all the sites with which a particular unit communicates. Unlike the network configuration,
which defines only those sites that are nodes, the site table can include all sites in a system.
Site tables are used for the purposes of:
● RTU-to-RTU communication
● Event reporting
● Data burst
● Sync
The STS user uses the Site Table File Manager to create, copy, import, or delete site tables files. See
Managing Site Tables on page 188. The STS includes three types of site tables, as listed in the following
table.

186
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Table 21: STS Site Table Types

Site Table Type Max. Number of Records Supported RTU Types

IP Gateway Site Table 3000 ● ACE IP Gateway
● ACE 4600

Irrinet-M Site Table 999 ● MOSCAD-M

● IRRInet-M

ACE 1000 / MC-EDGE Site Ta- 999 ● ACE 1000

ble
● MC-EDGE
● IRRInet-EDGE

NOTE: For IRRInet-M (Client (Master)), the STS automatically creates a “Client (Master)” site table,
which cannot be deleted. Duplicating the Client (Master) site table and then modifying the copied table
file is recommended.
After creating or importing a site table, the user fills in or edits the table in the STS site table editor. See Site
Table Editor on page 190.
NOTE: The STS does not automatically update customized site tables (for example, when adding a
new site or changing the site ID of an existing site). The STS user is responsible for maintaining site
tables.
Figure 112: IRRInet Client (Master) Site Table

187
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 113: ACE IP Gateway Site Table

When filling in a site table, for each destination RTU, the user should define a symbolic name, logical address
(Site ID), and the link (link ID) through which it is connected. When programming the process using ladder
rungs, the user should employ only the symbolic site name in the appropriate rung for sending the data to
that site. For further details, including examples, see User Defined MDLC Communication on page 612.
NOTE: The STS project site table should not be confused with the site table in the application
database, as described in User Defined MDLC Communication on page 612. The site table in the
application database is used in RTU-to-RTU communication and displays the COMFAL bit for each site/
link.
After filling in the site table, the user attaches it to sites via the Site Table File Manager. See Managing Site
Tables on page 188. The manager does not allow the user to assign a site table to an incompatible site. For
example, assigning an IP Gateway type site table to an MC-EDGE site is not allowed. When a site table is
selected in the Site Tables Files pane of the Site Table File Manager, incompatible sites are grayed out and
cannot be selected in the Sites list.

3.4.10.1
Managing Site Tables
The STS Site Table File Manager enables the user to create, edit, copy, and delete site tables, and to assign
them to sites in the project.
The left pane of the Site Table File Manager lists the Site Table Files. The right pane lists the Sites in the
project.

188
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 114: STS – Site Table File Manager

In both the left and right panes, you can choose to view the contents as:
● a detailed list, by clicking View Details (default)
● a simple list, by clicking View List
NOTE: If a site ID is changed in the project, or if a new site is added to the project, the user-defined site
tables must be updated manually by the user.
Prerequisites: Open the Site Table File Manager by clicking System → Site Table Manager....

Procedure:
● If you want to create a new site table, perform the following actions:

a. Click the Create new site table icon.

b. Select the relevant site table type.
For information about site table types, see Site Tables on page 186.
c. In the New Site Table dialog, make the preferred changes to the new table.

d. Click the Save icon.

e. To save the site table, enter a name for the new site table file and click OK.
● If you want to edit an existing site table, not the Client (Master) file, perform the following actions:
a. In the Site Table Files list, select the preferred table.

b. Click the Edit site table icon.

c. In the Site Table dialog, make the preferred changes to the new table.
d. After making changes, click Close. You are prompted to save the changes to the new file. To save
the changes and close the dialog, select Yes.
● If you want to delete an existing site table, perform the following actions:

189
6802979C10-BA
Chapter 3: MC-IoT STS Operation

a. In the Site Table Files list, select the preferred table.

b. Click the Delete icon.

c. To confirm the operation, click Yes when prompted.
NOTE: The Client (Master) site table cannot be deleted.

● If you want to copy an existing site table, perform the following actions:
a. In the Site Table Files list, select the preferred table.

b. Click the Copy site table icon.

c. In the dialog that appears, enter the name of the new table and click OK.
A copy of the original table (with the new name) appears in the Site Table Files list, where it can be
selected for further action.

● If you want to attach a site table to one or more sites, perform the following actions:
a. In the Site Table Files list, select the preferred table.
b. In the Sites list, select the site or sites to which you want to attach the table.
NOTE: If a site is already selected, deselecting it will detach the table from that site.

c. To save the changes and close the Site Table File Manager, click OK.
● If you want to detach a site table from one or more sites, perform the following actions:
a. In the Site Table Files list, select the preferred table.
b. In the Sites list, deselect the site or sites from which you want to detach the table.
NOTE: If a site is already deselected, selecting it will attach the table to that site.

c. To save the changes and close the Site Table File Manager, click OK.

3.4.10.2
Site Table Editor
The STS includes a site table editor, which allows the user to add, modify, and delete entries in user-created
site tables.
In the site table, each column represents a unique variable, such as site ID, retries, timeout, etc. Each row in
the site table represents one particular site, and the cells within that row are used to define the variables for
that site. For example, to specify the timeout variable for a particular site, the user inputs the value in the cell
where the Timeout column intersects the row representing the chosen site.
Multiple site table varieties exist, each including different variables. For more information, see Site Tables on
page 186.
For instructions on adding, modifying, and deleting entries in site tables, see the procedures referenced in the
following table:

Site Type Reference

● ACE IP Gateway Editing IP Gateway Site Tables on page 191

● ACE 4600

190
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Site Type Reference

● MOSCAD-M Editing RTU Site Tables on page 193

● IRRInet-M
● ACE 1000
● MC-EDGE
● IRRInet-EDGE

The site table editor includes other functions, such as:

● Printing tables
● Appending groups of sites with sequential site ID numbers
● Editing or deleting multiple sites at the same time
● Automatically sorting table entries by site ID
For a descriptive listing of all the site editor functions, see Site Table Editor Functions on page 197.

3.4.10.2.1
Editing IP Gateway Site Tables
The following procedure describes how to use the site table editor to add or modify individual entries in an IP
Gateway site table. The site table editor includes additional functions beyond the scope of these instructions
(such as sorting table entries, or editing multiple site entries at the same time). For descriptions of all the site
editor functions, see Site Table Editor Functions on page 197.
For guided instructions on adding groups of sites to a site table, see Appending Groups of Sites to a Table on
page 195.
NOTE: If a site ID is changed, or if a new site is added to the project, the site table must be manually
updated by the user.
The ACE IP Gateway system includes a Health Check mechanism, which relies on the site table as the basis
for its operations. For important information on configuring the Health Check mechanism and the link validity
for the ACE IP Gateway site table, see “ACE IP Gateway” in the MC-IoT STS Advanced Features manual.

Procedure:
1. To open the Site Table File Manager, select System → Site Table Manager...
2. To open a site table for editing, perform one of the following steps:
● If you want to edit an existing table, open the preferred table for editing.
● If you want to fill in a blank table, create a new table and open it for editing.
For detailed instructions on creating and opening site tables, see Managing Site Tables on page 188.
The new or existing site table opens in the site table editor.

191
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 115: Editing an IP Gateway Site Table

3. To define a site ID in the table, perform one of the following steps.

If… Then…
To add a new site to perform the following actions:
the table, a. Double-click an empty cell in the Site ID column.
b. Enter the site ID of the preferred site (as defined in its site configura-
tion).

To modify the site ID perform the following actions:

of an existing entry a. In the chosen entry (row), double-click the cell in the Site ID column.
in the table,
b. Modify the site ID.

NOTE: The value 0 is used for MDLC broadcast.

4. To define the number of retries, double-click the Retries cell (located in the same row as the site ID of
the chosen site) and enter the preferred value.
The Retries value (chosen from a range of 1–255) is the number of attempts made to communicate
with a non-responsive RTU. The default value is 1.
5. To define the wait time (in seconds) between communication retries, double-click the Timeout cell
(located in the same row as the site ID of the chosen site) and enter the preferred value.
The minimum value is 1 second; the maximum value is 255 seconds.
6. To define the primary link ID, use the drop-down list in the Primary Link ID cell (located in the same
row as the site ID of the preferred site).
7. To define the validity of the primary link, double-click the Primary Link Validity cell (located in the
same row as the site ID of the chosen site) and enter the preferred interval.
The IP Gateway tests communication with the sites on a regular basis. If a site has not responded
within the specified interval, the link is considered unreachable.
NOTE: If a link ID in a site is empty, the corresponding link validity must be set to: 000:00:00

192
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

8. Optional: Repeat the previous steps to define the Secondary Link ID and Secondary Link Validity.
9. Optional: To delete a site from the site table, perform the following actions:
a. Select the site ID of the preferred site.

b. Click the Delete current site icon.

c. To delete the selected site, click Yes.
10. To save the site table file, perform one of the following steps:

If… Then…

To save the changes to click the Save icon.

an existing site table file,
To save a newly created perform the following actions:
site table file,
a. Click the Save icon.
b. In the Save As dialog, enter a name for the site table file.
c. To save the file, click OK.

3.4.10.2.2
Editing RTU Site Tables
The following procedure describes how to use the site table editor to add or modify individual entries in an
RTU site table. The site table editor includes additional functions beyond the scope of these instructions
(such as sorting table entries, or editing multiple site entries at the same time). For descriptions of all the site
editor functions, see Site Table Editor Functions on page 197.
For guided instructions on adding groups of sites to a site table, see Appending Groups of Sites to a Table on
page 195.
NOTE:
If a site ID is changed, or if a new site is added to the project, the site table must be manually updated
by the user.
In the IRRInet-M Client (Master) site table, the entry for Site ID 1 represents the ICC with which the
IRRInet-M Client (Master) communicates.

Procedure:
1. To open the Site Table File Manager, select System → Site Table Manager...
2. To open a site table for editing, perform one of the following steps:
● If you want to edit an existing table, other than the IRRInet-M Client (Master) table, open the
preferred table for editing.
● If you want to edit the IRRInet-M Client (Master) table, first make a copy of the table and then
open the copied file for editing.
● If you want to fill in a blank table, create a new table and open it for editing.
For detailed instructions on creating and opening site tables, see Managing Site Tables on page 188.
The new or existing site table opens in the site table editor.

193
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 116: Editing an RTU Site Table

3. To define a site ID in the table, perform one of the following steps.

If… Then…
To add a new site to perform the following actions:
the table, a. Double-click an empty cell in the Site ID column.
b. Enter the site ID of the preferred site (as defined in its site configura-
tion).

To modify the site ID perform the following actions:

of an existing entry a. In the chosen entry (row), double-click the cell in the Site ID column.
in the table,
b. Modify the site ID.

NOTE: The value 0 is used for MDLC broadcast.

4. To define the number of retries, double-click the Retries cell (located in the same row as the site ID of
the chosen site) and enter the preferred value.
The Retries value (chosen from a range of 1–255) is the number of attempts made to communicate
with a non-responsive RTU. The default value is 1.
5. To define the wait time (in seconds) between communication retries, double-click the Timeout cell
(located in the same row as the site ID of the chosen site) and enter the preferred value.
The minimum value is 1 second; the maximum value is 255 seconds.
6. To define the primary link ID, use the drop-down list in the Primary Link ID cell (located in the same
row as the site ID of the preferred site).

194
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

7. Optional: To delete a site from the site table, perform the following actions:
a. Select the site ID of the preferred site.

b. Click the Delete current site icon.

c. To delete the selected site, click Yes.
8. To save the site table file, perform one of the following steps:

If… Then…

To save the changes to click the Save icon.

an existing site table file,
To save a newly created perform the following actions:
site table file,
a. Click the Save icon.
b. In the Save As dialog, enter a name for the site table file.
c. To save the file, click OK.

3.4.10.2.3
Appending Groups of Sites to a Table
The STS site table editor allows users to append groups of sites with sequential site ID numbers. When
appending a group of sites, the same parameters (such as the number of retries, timeout interval, primary link
ID, etc.) are applied to all sites in the group.
During this operation, the user specifies the lowest site ID number, and the number of sites in the sequential
group. For example, the user sets 70 as the first site ID, and sets 3 as the number of sites. In this case, the
software populates the site table with three sites: 70, 71, and 72.

Procedure:

1. Click the Append group of sites icon.

Depending on the site table type, the Append Group of Sites dialog includes different parameters.
For IP Gateway site tables, the dialog includes additional fields for the Primary Link Validity,
Secondary Link ID, and Secondary Link Validity.

195
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 117: Append Group of Sites Dialog (RTU Site Table)

Figure 118: Append Group of Sites Dialog (IP Gateway Site Table)

2. In the First Site ID field, enter the site ID of the first site in the group (that is, the site with the lowest
site ID number).
3. In the Number of sites field, enter the number of sites in the sequential series.
4. In the Retries field, enter the preferred value.
5. In the Timeout field, enter the preferred value.
6. In the Primary link ID field, select the preferred value from the drop-down list.

196
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

7. Perform one of the following steps.

If… Then…
If the site table is not an IP append the group of sites by clicking OK.
Gateway site table,
If the site table is an IP Gate- perform the following actions:
way site table, a. In the Primary Link Validity field, enter the preferred inter-
val.
b. If the group of sites have a secondary link, define the Secon-
dary Link ID and Secondary Link Validity.
c. To append the group of sites, click OK.

3.4.10.2.4
Site Table Editor Functions

Icon Function Name Description

Save Saves any changes made to the table.

Print Opens the Windows print dialog, from which the print parameters can
be set before printing the site table.
Print Preview Opens a print preview of the site table (from which the table can be
viewed and printed).
Insert new site Inserts new (blank) row above the currently selected row.

Append group of Opens the Append Group of Sites dialog for inserting multiple sites
sites with sequential site IDs. The user specifies the first site ID, and the
number of sites to be created. For example, the user sets 70 as the first
site ID, and sets 3 as the number of sites. In this case, the software
populates the site table with site IDs 70, 71, and 72. Each site is as-
signed the same parameters (such as Retries, Timeout, Primary link
ID, etc.) specified by the user in the Append Group of Sites dialog.
Delete current site Deletes the currently selected row (site).

Delete group of se- Deletes multiple sites (icon is active only when cells from more than one
lected sites row are selected).
Sort by site ID Automatically sorts all rows in numerical order according to site ID.

Functions for Modifying Parameters in Multiple Sites

The functions in the following table enable the user to modify the parameters in multiple sites at the same
time. The same value specified by the user is applied to all selected sites. These icons are active only when
two or more cells in the same column are selected.
For IRRInet-M and ACE 1000 / MC-EDGE site tables, only the Change Retries, Change Timeout, and
Change Primary Link ID functions are available. For IP Gateway site tables, all functions listed in the table
are available.

197
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Icon Function Name

Change Retries

Change Timeout

Change Primary Link ID

Change Primary Validity

Change Secondary Link ID

Change Secondary Validity

3.4.11
Managing DNP Client (Master) Configuration Files
The STS DNP File Manager is used to create, view, and edit DNP Client (Master) configurations; and to
assign them to ACE 1000, MC-EDGE, and IRRInet-EDGE sites.
In the DNP File Manager, the left pane (Blocks) lists the DNP Client (Master) files. The right pane lists the
Sites in the project.
Figure 119: STS – DNP File Manager

In both the left and right panes, you can choose to view the contents as:
● a detailed list, by clicking View Details (default)
● a simple list, by clicking View List

198
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

For important information on configuring, see the STS Third Party Protocols Support manual.
Prerequisites: Open the DNP File Manager by clicking System → DNP-File Manager...

Procedure:
● If you want to create a new DNP Client (Master) configuration, perform the following actions:

a. Click the New block icon.

b. In the DnpMFileName dialog, type a name for the new DNP Client (Master) file and click OK.
c. In the DNP Master configuration editor (see the following figure), set the preferred parameters.
Figure 120: DNP Client (Master) Configuration Editor

d. To save the changes, click the Save icon.

e. To close the DNP Master configuration editor and return to the DNP File Manager, click Close.
● If you want to edit an existing DNP Client (Master) configuration, not the Client (Master) file, perform
the following actions:
a. In the Blocks list, select the preferred DNP configuration file.

b. Click the Edit block icon.

c. In the DNP Master configuration editor (see the previous figure), set the preferred parameters.

d. To save the changes, click the Save icon.

e. To close the DNP Master configuration editor and return to the DNP File Manager, click Close.
● If you want to delete a DNP Client (Master) configuration file, perform the following actions:

199
6802979C10-BA
Chapter 3: MC-IoT STS Operation

a. In the Blocks list, select the preferred DNP configuration file.

b. Click the Delete icon.

c. To confirm the operation, click Yes when prompted.
● If you want to copy a DNP Client (Master) configuration file, perform the following actions:
a. In the Blocks list, select the preferred DNP configuration file.

b. Click the Copy Block icon.

c. In the DnpMFileName dialog, enter a name for the new (duplicate) file.
d. To save the file, click OK.
A copy of the original file (with the new name) appears in the Blocks list, where it can be selected for
further action.

● If you want to attach a DNP Client (Master) configuration file to one or more sites, perform the
following actions:
a. In the Blocks list, select the preferred DNP configuration file.
b. In the Sites list, select the site or sites to which you want to attach the file.
NOTE:
If a site is already selected, deselecting it will detach the configuration file from that site.
You cannot select an ACE 1000, MC-EDGE, or IRRInet-EDGE site that is not configured as
a DNP Client (Master). Configure the preferred site as a DNP Client (Master) before
attaching the configuration file.
c. To save the changes and close the DNP File Manager, click OK.
● If you want to detach a DNP Client (Master) configuration file from one or more sites, perform the
following actions:
a. In the Blocks list, select the preferred DNP configuration file.
b. In the Sites list, select the site or sites from which you want to detach the file.
NOTE:
If a site is already deselected, selecting it will attach the configuration file to that site.
c. To save the changes and close the DNP File Manager, click OK.

3.4.12
Field View
The STS Field View allows the user to view the settings of an RTU without creating a new site definition from
the inventory.
The STS Field View displays RTU configuration information, which helps to uniquely identify the unit. The
information is arranged in four tabs:
● General
● Ports
● I/O
● Files
In systems with I/O expansion frames, the Field View includes a fifth tab, Frames.
For redundant sites, relevant redundancy configuration information is included.

200
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

The file size in the unit (as displayed in the Field View) differs from the file size displayed in the STS
project (in the Site Download dialog). Starting with system version 16.50, files are compressed in the RTU.
Therefore, the file size in the RTU is generally smaller, even with the header added to the compressed files.
One exception to this is the configuration file. The file size of the configuration is larger in the RTU because
the new site ID and legacy password are added when downloading.
Because only relevant links are downloaded to the RTU, the network file in the RTU is smaller than the
network file in the STS project.

3.4.12.1
Retrieving the Field View
NOTE: This feature is not supported for ACE 1000 and MC-EDGE.

Procedure:
1. From the menu bar, select System → Field View...
2. To connect to a site, perform one of the following steps.
● To upload from a site via the local connection, select Local (default).
● To upload from a site remotely, deselect Local and enter the preferred Site ID and Link ID.
Figure 121: Initiating Field View of Locally Connected RTU

3. To open the Field View of the chosen site, click OK.

201
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 122: STS–Field View

NOTE: In Field View, the unit type for IRRInet-M RTUs is listed as MOSCAD-M.

4. Optional: To save the Field View data in a file, click Save as...
5. To close the Field View, click OK.

3.4.13
Uploading New Sites to STS
A site definition can be uploaded from an RTU and used to create a new site in the STS project.
For instructions on uploading files from an RTU to the STS project without creating a new site, see Uploading
Files from Sites on page 160.
For general information about site uploads, see Uploads from Sites on page 159.

Procedure:
1. From the menu bar, select System → Upload New Site...
NOTE: If the command is disabled, ensure that you are in the system view, with no site selected.

2. In the Upload New Site dialog, perform one of the following steps.
● To upload from a site via the local connection, select Local (default).
● To upload from a site remotely, deselect Local and enter the preferred Site ID and Link ID.

202
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 123: STS–Upload New Site Dialog

3. To connect to the RTU, click OK.

The Upload New Site dialog displays RTU configuration information, which helps to uniquely identify
the unit before uploading. The information is arranged in tabs, as follows:
● General
● Ports
● I/O
● Files
● Frames (only in systems with I/O expansion frames)
Figure 124: STS–Upload New Site Dialog

NOTE: In the Upload New Site dialog, the Unit Type for IRRInet-M RTUs is listed as MOSCAD-
M.

4. To continue uploading from the RTU displayed in the Upload New Site dialog, click Continue and
perform one of the following steps.
If a site with the same site ID as the connected RTU already exists in the STS project, the Site Exist
dialog appears. Otherwise, the Site Upload dialog appears.

If… Then…
If the Site Exist dialog appears, proceed to step 5.
If the Site Upload dialog appears, proceed to step 6.

203
6802979C10-BA
Chapter 3: MC-IoT STS Operation

5. In the Site Exist dialog, perform one of the following actions:

If… Then…
If you want to upload the files to the perform the following actions:
preexisting site with the same site ID, a. Select Upload files to existing site.
b. Click Continue >>.

If you want to upload the files to a new perform the following actions:
site with a unique Site ID, a. Select Upload files to new site with new ID.
b. Enter a Site ID for the site to be created.
c. Click Continue >>.

Figure 125: STS–Site Exist Dialog

6. In the Site Upload dialog, select the files that you want to upload.

204
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 126: STS–Site Upload Dialog

NOTE:
The Site Upload dialog lists all files in the RTU, but only the following files can be uploaded:
● Site configurations
● Phone books
● Network source file
● IP conversion tables
Other types of files stored in the unit cannot be viewed using STS utilities, and are therefore not
uploaded.
If no site configuration was ever downloaded to the unit, the Default Site Configuration label
appears in the Site Upload dialog.
7. To begin the upload process, click Upload.
NOTE:
When uploading a redundant site:
● If another redundant CPU is already defined in the system, you are instructed to change the
default MDLC Link name. To do so, open the site configuration. Under the Ports tab, change
the Link name of the INTR1 internal port (which is used to connect between the primary and
secondary RTU). The MDLC Link Name must be unique for each set of peers within the
system.
● If its peer already exists in the system, the STS will force the required configuration changes.
The user is notified before the STS makes the changes (if any) to the existing site.
When uploading an IRRInet-M Server (Slave) RTU:
If the PRIS ID of the site to be uploaded is already used in the project, a dialog prompts the user
to enter a new PRIS ID.

An Abort button replaces the Upload button. The progress bar displays the progress of the upload.

205
6802979C10-BA
Chapter 3: MC-IoT STS Operation

The names of the uploaded external files appear in the Upload Progress box in the bottom-left
portion of the dialog. For example, when uploading a network source file from a unit, the file is named:
upl#<site id>_1.scf
If the file is uploaded again, it is named: upl#<site id>_2.scf
Additionally, any errors or messages are displayed in the Upload Progress box.
After the upload is completed, the newly created site appears in the Diagram View and in the project
tree (located under the System tab). If the user chose to upload the RTU files to an existing site
(instead of creating a new site), those files are now attached to that site.

3.4.14
Downloading to All Sites
The STS user can download files to more than one site at once. This is particularly useful during system
setup, and for implementing system-wide changes.For general information on downloads, as well instructions
on downloading to individual sites, see Downloads to Sites on page 145.

Procedure:
1. To open the Download All Sites dialog, select System → Download All Sites...
Figure 127: STS–Download All Sites Dialog

The System tree on the left includes all sites in the system. The check box next to each site in the
tree is used to include or exclude that site from the download process.
Clicking the name of a site in the System tree opens the download settings for that particular site.
2. Perform one of the following steps.

If… Then…
If you want to configure the down- proceed to step 3.
load settings from the start,

206
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
If you want to open the settings perform the following actions:
from a previously saved download a. Select Profile → Open...
session,
b. From the Files list, select the preferred download ses-
sion.
c. To open the settings, click Open.
d. To continue with the loaded settings, proceed to step 3.

3. To configure the download settings for a particular site, click the name of that site in the System tree.
Perform any of the following steps (as needed):

If… Then…
If you want to download to the se- in the Connection portion of the dialog, select Local (de-
lected site via the local connection, fault).
If you want to download to the se- perform the following actions:
lected site remotely, a. In the Connection portion of the dialog, ensure that
the Local option is not selected.
b. From the drop-down list, select the preferred Link ID.

If you want to choose which files in the Files list, perform the following actions:
download to the selected site, ● Select (check) the files that you want to download.
● Deselect the files that you do not want to download.

If you want to specify the order of from the drop-down list, choose a Download Priority for
sites for downloading, the site.
NOTE: When planning the site order, keep in mind
that download sites may need to restart, depend-
ing on the file type. If you choose to download first
to the local site, downloads to remote sites must
wait for the local site to restart. It is highly recom-
mended that the local site is downloaded after re-
mote sites.

NOTE: Any changes made to the files or settings apply to the selected (highlighted) site only.

4. Optional: If the communication time is limited and needs to be re-established from one site to the next,
set a time delay (sec) in the Delay between sites field.
5. Optional: To specify the number of attempts to retry failed downloads, set the preferred value in the
Auto Retry field.
For sites where the download failed, after the last site is reached, the entire download process will
restart the specified number of times.
6. Optional: To clear the Needs Download status of all selected sites (without performing the download),
perform the following actions:
a. Click the Clear File Status button.
b. To confirm the operation, click OK.
7. Optional: To save the download session settings, perform the following actions:
a. Select Profile → Save.

207
6802979C10-BA
Chapter 3: MC-IoT STS Operation

b. In the Selected file field, enter a name for the download session.
c. To save the settings, click OK.
NOTE: To overwrite an existing file, select it from the Files list and click OK. To confirm the
overwrite operation, select Yes when prompted.
8. To begin the download process, click Download.

An Abort button replaces the Download button. Any messages/errors are displayed in the Download
Progress window.
In the right side of the window, two respective progress bars show the progress of the current file
download and of the download overall.
As each site completes the download, it reverts to an unchecked state and all its files are marked as
Downloaded (unchecked).

9. To close the Download All Sites dialog, select Profile → Exit.

3.4.15
MDLC Password Change
For nonsecured MDLC communication, the system uses the MDLC legacy password defined during project
creation. This password is downloaded to the RTU in the site configuration, and is used for STS-to-RTU and
RTU-to-RTU communication. If needed, the user can change the MDLC password via the STS.
To apply the MDLC password change to a remote site, an updated site configuration must be downloaded to
the unit. The user can download the site configuration to all sites in the project at the same time, or to each
site individually. Downloading to all sites at once is simpler, but the actual download process may be lengthy
in a large system. Downloading to sites individually allows the STS user to control the timing of the process,
but requires careful tracking to avoid confusion.
To facilitate the process of downloading the new MDLC password to sites in the project, the STS includes an
MLDC Password Update Mode. While in this mode, the STS remembers the current password of each site
in the project. This ensures communication with each site to allow the updated configuration file to download
to the RTU. After all sites are successfully updated, the STS automatically leaves MLDC Password Update
Mode. For more information, see "MDLC Password Update Mode" in the MC-IoT STS Advanced Features
manual.
In case of problems, the STS user can temporarily override the password in a site during the password
change process. This is useful if communication with a site fails, and you suspect that the downloaded
configuration file was rejected by the site. For instructions, see Overriding the MDLC Password on page 211.
In addition, the STS user can choose to change the MDLC password in the project only, without downloading
to sites. This is needed when you receive the project from a third party and must change the project
password to the one used in your system. This option is also useful when preparing a project offline (for
example, from a template project).
For additional information, see “MDLC Password Change” in the MC-IoT STS Advanced Features manual.
For detailed instructions on changing the MDLC password in a project, see Changing the MDLC Password in
Sites on page 209.

208
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.4.15.1
Changing the MDLC Password in Project Only
In some cases, the STS user may want to change the MDLC password in the STS project only, without
changing the MDLC password in the sites.
For instructions on changing the MDLC password in an STS entire project, including the project sites, see
Changing the MDLC Password in Sites on page 209.

Procedure:
1. From the menu bar, select Setup → Change MDLC Password...
2. In the Change MDLC Password dialog, enter the current password (defined during project creation)
in the Old password field.
Figure 128: STS–Change MDLC Password Dialog

3. In the Password field, enter the new password (between 6 and 10 characters).
4. In the Confirm password field, enter the new password again.
5. Select Change password only in this STS project.
6. To apply the new password and close the Change MDLC Password dialog, click OK.

3.4.15.2
Changing the MDLC Password in Sites
After changing the MDLC password in the project, the STS user applies the new password to sites by
downloading an updated site configuration. The password can be downloaded to all sites at once, or to each
site individually.
For instructions on changing the MDLC password in the STS project only, without changing the MDLC
password in the sites, see Changing the MDLC Password in Project Only on page 209.
IMPORTANT: To minimize loss of communication, change the MLDC password as quickly as possible. In
large systems, tracking the progress is important to avoid confusion.

Procedure:
1. From the menu bar, select Setup → Change MDLC Password...
2. In the Change MDLC Password dialog, enter the current password (defined during project creation)
in the Old password field.

209
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 129: STS–Change MDLC Password Dialog

3. In the Password field, enter the new password (between 6 and 10 characters).
4. In the Confirm password field, enter the new password again.
5. Select Change password in STS project & All sites and click OK.
6. To begin the password change process, click OK when prompted (as shown in the following figure).
Figure 130: Confirming the MDLC Password Change

After confirming the operation, the sites are marked as Needs Download in the Table View.
Additionally, the MLDC Password Update Mode menu appears in the status bar at the bottom of
the screen.
7. To apply the new password to the sites, download the updated site configuration:
● To download to each site individually, see Downloads to Sites on page 145.
● To download to all sites at once, see Downloading to All Sites on page 206.
The STS initiates the download using the current password. After the download, the RTU restarts and
uses the updated password.
NOTE: During the password change process, sites that have the new password are marked with

the Non identical MDLC password icon. After the password change process is complete,
the user is notified and the icons are cleared.

210
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

8. Optional: During the password change process, perform any of the following, additional steps (as
needed):

If… Then…
If you want to communicate perform the following actions:
with an updated site during a. To initiate communication, click Start.
the password change proc-
ess, b. When prompted with the password mismatch message, click
Yes to change the STS password.
c. After the MDLC driver restarts, perform the chosen STS oper-
ation (such as verifying that the download was successful).
d. Continue changing the MDLC password in the next site.
NOTE: The mismatch message will appear again be-
cause of the difference between the new password of
the MDLC driver, and the outdated password of the
next site.

If you want to temporarily follow the instructions in Overriding the MDLC Password on page
override the password in 211.
a site during the password
change process,
If you want to exit MDLC perform the following actions:
Password Update Mode a. From the menu bar, select Setup → Leave MDLC Update
before the update is com- Mode.
pleted for all sites,
b. To confirm the operation, click Yes when prompted.
NOTE:
When leaving MDLC Password Update Mode:
● The MDLC driver restarts with the new password.
● The STS erases all outdated site password infor-
mation.
This is useful if remote communication with a site
fails, and the MLDC password is changed locally
(such as by erasing the RTU flash).

3.4.15.3
Overriding the MDLC Password
Procedure:

1. In the Connection section of the Site Download or Download All Sites dialog, click the icon.
2. In the Communication Settings dialog, select Override communication password.
You are prompted to enter an override password (as shown in the following figure).

211
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 131: Override MDLC Password Dialog

3. Enter the new password and click OK.

4. In the Communication Settings dialog, click OK.
Figure 132: Communication Settings Dialog

5. To restart the MDLC driver, click OK when prompted.

After the MDLC driver restarts with the override password, the gear icon (under Connection) is
highlighted in yellow.

6. To clear the password override, perform the following actions:

a. Click the gear icon (highlighted in yellow).
b. Deselect the Override communication password option.
c. Click OK.
The MDLC driver restarts with the original password. The gear icon reverts to its original state.
NOTE: The password override is automatically cleared when you exit the STS.

3.4.16
Adding Comments
Users can add comments to the STS project (for example, to provide system information, IP addresses, etc.).
These comments appear in the project Diagram View.

Procedure:
1. From the menu bar, select System → Add Comment.
NOTE: The Add Comment option is disabled whenever a particular site is open, or is otherwise
selected in the system Diagram View or Table View.
2. In the text box, type your comment.

212
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3. To save the comment, click outside the text box.

4. Optional: To manage an existing comment, perform any of the following steps (as needed):

If… Then…
If you want to move a comment to a drag the comment to the preferred location in the sys-
different location, tem diagram.
If you want to edit a comment, perform the following actions:
a. Right-click the comment and select Edit.
b. In the text box, enter the preferred changes.
c. To save the comment, click outside the text box.

If you want to delete a comment, right-click the comment and select Delete.

3.4.17
Backing Up the Database
Critical blocks of user application data can be stored in the flash memory and restored later.
For more information, see the Application Programmer on page 324 chapter.

3.4.18
Setting Login Banner (MC-EDGE)
When an MC-EDGE (NFM-EDGE) RTU is accessed via the SSH console, a login banner is displayed. For
sites with the system 29.00 or newer, you can change the default login banner in STS.

Procedure:
1. From the main manu, select System → Banner text.
2. Edit the Login Banner text according to your preferences.
3. Optional: If you want to revert to the default text, click Default Text.
4. Save the changes by clicking OK.
5. By using the Downloader, download the newly added banner.txt file to all relevant sites in the
project.

3.4.19
Generating SSH Authentication Keys (MC-EDGE)
STS can be used to generate SSH server host keys on MC-EDGE (NFM-EDGE) sites. During this process,
STS prompts the MC-EDGE RTU to generate an authentication key pair. The public key and its fingerprint
are returned to STS and can be copied elsewhere for the future authentication.

Procedure:
1. If you want to generate an SSH key for several sites, perform the following actions:
a. From the System menu, select SSH Keys.
The SSH Keys dialog box opens.

213
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 133: SSH Keys Dialog Box

b. From the project tree on the left side of the SSH Keys dialog box, select the sites for which you
want to generate the SSH keys.
c. Select the key type and key size.
NOTE: Only RSA is supported.

d. If necessary, for each site, select its communication parameters such as the link ID used to
connect to this site by MDLC.
2. If you want to generate an SSH key for one site, perform the following actions:
a. From the Site menu, select SSH Keys.
The SSH Keys dialog box opens.

b. Select the key type and key size.

NOTE: Only RSA is supported.

c. If necessary, select the site communication parameters such as the link ID used to connect to this
site by MDLC.
3. Click Start.
In the Progress section of the dialog box, you can see the progress and the connection log.
As keys are generated, you can see them for each site in the respective fields of the dialog box.
The public keys and fingerprints are stored in the project and you can view them anytime by using this
dialog box.

214
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.4.20
SSH Known Hosts List (MC-EDGE)
The SSH known hosts list is a file used by STS SSH clients to store the public keys fingerprints of remote
MC-EDGE host servers that the STS client has connected to in the past. When an STS client tries to connect
to a remote MC-EDGE by using SSH, it checks the known hosts list to verify the server’s identity.
The known hosts list serves as a security measure to prevent man-in-the-middle attacks. It helps ensure that
the STS client is connecting to the correct MC-EDGE server and not a malicious imposter. When a client
connects to an MC-EDGE server for the first time, the server's public key is added to the known hosts list.
On subsequent connections, the client compares the server's public key with the one stored in the known
hosts list. If they match, the connection proceeds; otherwise, the STS client displays a warning or refuse to
connect.
In the following figure, there is the hosts key dialog warning which is prompted to the user upon SSH
connection from STS. The SSH connection is triggered either through changing the default SSH password or
SFTP download.
Figure 134: SSH Known Hosts List - Dialog Warning

In general, it is recommended to perform the SSH key rotation in which the server host public key is stored
into the known host list file. The known host list file is located in the following STS Project folder:
Projects\<project-name>\System\known_hosts
This known hosts list file can be manually copied to a different PC.

3.4.21
Changing Linux Passwords
Procedure:
Perform one of the following actions:
● To manually change the Linux password in secured STS, perform Changing Linux Passwords
Manually in Secured STS on page 216.
● To change the default Linux password in secured or unsecured STS, perform Changing Default Linux
Passwords in Secured and Unsecured STS on page 217.

215
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.4.21.1
Changing Linux Passwords Manually in Secured STS
When you use Secured STS, you can change passwords of predefined Linux users.
NOTE: This feature is available only if you are the project administrator and there is at least one MC-
EDGE unit in the project.

Procedure:
1. From the System menu, select Set Linux passwords…
The Change Linux User Password dialog box opens.
Figure 135: Change Linux User Passwords Dialog Box

2. By using the project tree on the left panel of the dialog, select the sites for which you want to change
the password.
3. From the drop-down list, select a user.
4. Type in the outdated password.
5. Type in and confirm a new password by retyping it in the next block.
6. To start the operation, click OK.
NOTE: The root account does not require an outdated password.

216
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.4.21.2
Changing Default Linux Passwords in Secured and Unsecured
STS
On MC-EDGE units of version 33 and higher, if the target unit has default passwords from the factory, the
user is forced to change them when any download starts.

Procedure:
1. Open STS.
2. Open the Site menu and click on the Download icon or right-click on the Site and select Download.
During the download process, if the MC-EDGE has default passwords, the SSHForcePassword
dialog box appears.
Figure 136: SSHForcePassword Dialog Box

3. Change the password for either two users mciotlogin and cappl, or for one of them, depending on
which user you were logged in with.
The Current password field is the default password that is used for login for mciotlogin and cappl.
The Current password field is automatically set to the default password.
The fields New password and Confirm password are for the new password with restricted
passphrase. The SSH passphrase must be at least 16 characters long and include at least:
● one capital letter (A – Z)

217
6802979C10-BA
Chapter 3: MC-IoT STS Operation

● one small letter (a – z)

● one digit (0 – 9)
● one special character from the following list: ~!@#$%^&*()_+`{}|[]\:"";'<>?,./
Ensure that the new password is not similar to the outdated one.
4. Optional: If you want STS to remember passwords that you entered for later use when adding other
devices with default password, select the Use this password for all sites check box.

3.4.22
Changing SNMP User Credentials (MC-EDGE)
For MC-EDGE v32.00 and newer, credentials and authentication level of SNMP users (MotoAdmin,
MotoMaster, MCIOT, MotoInformA/B) can be changed using a special command, without editing and
downloading site configuration. To be able to change them, you need to know the current MotoAdmin
password.

Procedure:
1. From the System menu, select System – SNMP User Credentials.
The SNMP User Credentials dialog box opens.
Figure 137: SNMP User Credentials Dialog Box

2. By using the project tree on the left panel, select the sites for which you want to change the user
credentials.
3. Select the required user name and authentication level.

218
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

4. Type in the existing MotoAdmin password.

5. If applicable, type in the new authentication and privacy passwords for the required user.
6. Click Start.
You can see the progress and connection log in the lower panel.

3.4.22.1
Resetting SNMP User Definitions
You can reset SNMP user definitions (security levels and the passphrases) to the default factory settings.

Procedure:
● To reset SNMP user definitions for a single site, select the site and then, in the Site menu, select
Reset SNMPv3 Settings and click the Reset SNMP button.
● To reset SNMP user definitions for multiple sites, in the System menu, select Reset SNMPv3
Settings. In the project tree, select the sites you want to reset the settings for and click the Reset
button.

3.4.23
NFM
The following section describes how to export UEM configuration data and how to generate the NFM site list
report.

3.4.23.1
Exporting UEM Configuration Data for NFM
The file created in this procedure can be loaded to the UEM server.

Procedure:
1. Open the STS project and from the main menu, select System → NFM UEM Config.
2. In the confirmation message, click Yes.
The project is saved and the process of generating the configuration file begins.

3. In the message on successful completion, click OK.

The .zip UEM configuration file is created in the UEM_RTU_Project subfolder under the project
folder. The exact location is displayed in the message box which pops up after the file is created.
NOTE: To reduce the size of the .zip file uploaded to the UEM server, some large files such as
the file system and kernel files are not included in the archived project.
If you need to restore the original project from the .zip file, you may need to obtain these files
separately and reattach them to the sites by using the Add-On Manager.

3.4.23.2
Generating the NFM Site List Report
In STS, a site list report can be generated for NFM sites.

Procedure:
1. In the System menu, select Site List Report.

219
6802979C10-BA
Chapter 3: MC-IoT STS Operation

2. In the dialog box, select the zone for which you want to generate the report.
If an NFM site is selected when running the command from the menu, its zone is selected
automatically.
3. Click OK.
The report file is generated in the Reports subdirectory under the project. It also opens in the
Notepad.

3.4.24
Printing the System
Prerequisites: Depending on your printer, you may need to change the page setup before printing. To do
this, select File → Page Setup... In the Page Setup dialog, change the settings (as preferred) and click OK.

Procedure:
1. Optional: To preview a document before printing it, perform any of the following steps (as needed):
● If you want to see a print preview of all the diagrams in the system, select File → Print Preview
→ All Diagrams.
● If you want to see a print preview of the system in Table View, select File → Print Preview
→ Tables.
● If you want to see a print preview of the current area, select File → Print Preview → Current
Area.
2. To print the system, perform any of the following steps (as needed):
● If you want to print all the diagrams in the system, select File → Print → All Diagrams.
● If you want to print the system in Table View, select File → Print → Tables.
● If you want to print the current area, select File → Print → Current Area.
The standard Windows print dialog appears. Click OK to print.

3.4.25
PKI Files Management
The PKI File Manager enables the user to create, edit, copy, and delete PKI files, and to assign them to sites
in the project.
The left pane of the PKI File Manager lists the PKI files. The right pane lists the sites in the project. In both
the left and right panes, you can choose to view the contents as:
● a detailed list, by clicking View Details (default).
● a simple list, by clicking View List.
The operation in this file manager is similar to other managers described in Managing IP Conversion Tables
on page 175, Managing Site Tables on page 188, Managing DNP Client (Master) Configuration Files on page
198.

3.4.25.1
Creating PKI Configuration
Prerequisites: Open the PKI File Manager by clicking System → PKI File Manager...

220
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Procedure:

1. Click the New block icon.

2. In the PKI File Name dialog box, type a name for the new PKI configuration file and click OK.
3. In the PKI configuration editor, set the preferred parameters. See PKI Configuration Editor
Parameters on page 222.
Figure 138: PKI Configuration Editor

221
6802979C10-BA
Chapter 3: MC-IoT STS Operation

4. To save the changes, click OK.

5. To close the PKI configuration editor and return to the PKI File Manager, click Cancel.

3.4.25.2
PKI Configuration Editor Parameters
Table 22: PKI Configuration Editor Parameters

Parameter Description
CA
CA SCEP interface This field is mandatory. Select the interface from
the list that you would like to use for your PKI.
HTTP proxy server This field is optional. Use the Proxy server at
host:port.
For example: localhost:8080

SCEP server URL This field is mandatory. Insert the URL of the
SCEP server.
For example: http://10.100.100.151/
certsrv/mscep/

CA identifier This field is optional. Use the CA identifier to speci-

fy the trusted CA.
CA certificate thumbprint This field is optional. Use the certificate thumbprint
(fingerprint) to verify the authenticity and integrity
of the certificate. The certificate thumbprint should
be in hexadecimal.
CA certificate thumbprint algorithm This field is mandatory. Select the encryption algo-
rithm from the list that you would like to use for
your CA certificate thumbprint.
Enrollment
Challenge password This field is mandatory. Use the challenge pass-
word (shared secret) for the initial enrollment re-
quest. The challenge password should be in hexa-
decimal.
Polling interval [15 – 600] sec This field is mandatory. Use polling interval for pe-
riodically initial enrollment request.
Max polling time [300 – 86400] sec This field is mandatory. Use max polling time to
define maximum duration of retries.
Max number of polling requests [3 – 256] This field is mandatory. Use max number of polling
requests to define the maximum number of polling
requests.
Renewal
Auto renewal This field is mandatory. Use this field to automati-
cally renew the certificate.
Certificate renewal advance period [1 – 60] days This field is mandatory. Use the advance period
for the certificate renewal starting period before its
expiration.

222
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Parameter Description
Certificate renewal retries interval [1 – 10] days This fiels is mandatory. Define how often you
would like to retry to obtain certificate renewals.
Name policy This field is mandatory.
The parameters of a PKI entity contain the identity
information of the entity. The CA identifies a certifi-
cate applicant based on identity information provid-
ed by the entity.
For example: The user fills the country name.
To facilitate the applicant identification, configure
the country code for the PKI entity, which is used
as an alias of the entity.
After the country code is configured for a PKI en-
tity, the certificate request packet is sent by the
device to the CA server which carries this country
code. The CA server verifies every received certifi-
cate request packet. For each valid packet, the CA
server generates a digital certificate carrying the
country code of the PKI entity.

Country This field is optional. Specify the country name to

use for Certificate Signing Request (CSR) genera-
tion.
State This field is optional. Specify the state name to use
for CSR generation.
Locality This field is optional. Specify the locality name to
use for CSR generation.
Organization This field is optional. Specify the organization
name to use for CSR generation.
Organization unit This field is optional. Specify the department name
to use for CSR generation.
Unique name policy This field is mandatory.
ATTENTION: Automatic fields are filled at
the time of the PKI configuration download
and are not changed on further configura-
tion of DNS/IPSEC/SiteID.

Common/Alt names type This field is mandatory.

Select one of the following options:
● manual – Fill in distinguished names.
● (Auto)DNS – Common name and DNS Alt
name are taken from site DNS configuration.
● (Auto)DNS- IPSec – Common name and DNS
Alt name are taken from IPSec Local Id.
● (Auto)IP – Common name and IP Alt name are
taken from IP of Interface chosen for CA.

223
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Parameter Description

● (Auto)DNS - SiteID – Common name and

DNS Alt name are taken from site ID in the
format: MCEDGE_<id>

Forced parameters
Forced reinitiate on download This field is mandatory.
Use the yes option in order to restart the initial en-
rollment process. When selecting the yes option,
all current PKI public certificates are deleted upon
download and the initial enrollment is restarted.

Forced renewal on download Use the yes option in order to perform the renewal
process upon download.

3.5
Administering Sites (Basic)
Unless otherwise noted, all of the administrative procedures below are relevant to the ACE3600. Some are
also relevant to the MOSCAD-M, IRRInet-M, ACE1000, MC-EDGE® and legacy RTUs.

3.5.1
Customizing Site Configurations
A general configuration of existing sites can be performed.To customize the port configuration, the I/O
configuration, or the advanced parameters of an existing site, see Customizing the Site Configuration on
page 109.

3.5.2
Renaming Sites
NOTE: Selecting Save Project will make any unsaved changes to the STS project, including to other
sites, permanent.

Procedure:
To rename a site, perform one of the following steps:

If… Then…
If you want to rename a perform the following actions:
site in Diagram View, a. Click the site name.
b. Enter the preferred name and press Enter.
c. To save the change, select File → Save Project.

224
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
If you want to rename a perform the following actions:
site in Table View, a. Select the preferred site by clicking it once.
NOTE: If you double-click, the site opens in site view (used
for site configuration).
b. With the site highlighted, click the name.
c. Enter the preferred name and press Enter.
d. To save the change, select File → Save Project.

If you want to rename a perform the following actions:

site in the site view,
a. In the Site Name field, enter the preferred name.
b. To save the change, select File → Save Project.

3.5.3
Changing the Site ID of Sites
NOTE: Changing the site ID in the STS project does not affect the site ID in the unit. To change the site
ID in the unit, you must download an updated site configuration to the site.

Procedure:
1. From the system Diagram View or Table View, double-click the preferred site to open it in site view.
2. In the Site ID field, enter the preferred value.
3. To save the change:
a. Select File → Save Project.
b. When prompted (as shown in the following figure), click OK.
Figure 139: STS Site ID Change Prompt

The new site ID replaces the outdated one in the site view and system view. The site ID in the
system-generated generic network table is updated.

4. To apply the new site ID to the remote site, download the updated site configuration to the unit. See
Downloads to Sites on page 145.
Postrequisites: If the site is referenced in any user-created tables, you must manually update the table with
the new site ID. For further guidance, see:
● Managing Network Tables on page 170
● Managing IP Conversion Tables on page 175
● Managing Dynamic IP Access Tables on page 180
● Managing Site Tables on page 188

225
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.5.4
Site Error Logging
RTUs log certain information pertaining to hardware and software malfunctions.
In systems with I/O expansion frames, all error messages from the frames are periodically collected by the
main CPU and saved with the main frame error messages.
When an error message is logged in the RTU, the ERR LED on the CPU front panel is illuminated. In systems
with I/O expansion frames, when an error message is logged in either the main frame or one of the expansion
frames, the following occurs:
● The ERR LED on the main CPU front panel illuminates.
● The MERR LEDs on all expansion modules illuminate.
When the error messages are cleared, the ERR LED extinguishes (and in systems with I/O expansion
frames, the MERR LEDs also extinguish).

3.5.4.1
Retrieving Error Logger Information from Sites
The STS SW Diagnostics and Logging utility enables the user to retrieve error messages logged in RTUs.
For instructions on using the utility to retrieve site diagnostics, see Retrieving Software Diagnostics from Sites
on page 230.
For instructions on using the utility to retrieve time-tagged event logs, see Retrieving Time-Tagged Event
Logs from Sites on page 233.
The format of each error message is as follows:
● Severity (error, warning, message)
● RTU date and time when error occurred
● Site information
● Error # and error message text
For a detailed explanation of the error message texts, see the System Tools Suite Software Diagnostic
Output and Error Messages Maintenance Guide.

Procedure:
1. To open the SW Diagnostics and Loggers utility, click Site → Logger...

226
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 140: STS–SW Diagnostics and Loggers Utility

2. Perform one of the following actions:

● If you want to retrieve information from a locally connected site, select Local.
● If you want to retrieve information from a remote site, deselect Local and enter the preferred Site
ID and Link ID.
NOTE: To retrieve error messages from an RTU with I/O expansion via a local connection, the
STS PC must be connected to one of the following:
● STS port of the main CPU (on the main frame)
● STS port of the expansion module (on the expansion frame)
3. Optional: To retain the logged errors in the RTU after they are retrieved, deselect the Erase RTU
errors after communication option (enabled by default). For legacy RTUs, this option cannot be
disabled.
4. To connect to the unit and retrieve its error logger information, click Start. If this is the first
communication session of the MDLC driver, enter the MDLC password when prompted.
A gray header line marked PC Logger Request appears in the logger window, followed by the
errors retrieved from the RTU.
The first entry summarizes the number of errors, warnings, and messages in the log. In systems with
I/O expansion, error messages pertaining to I/O expansion frames are marked Expansion Frame
<number>. Note that in earlier versions of STS (≤12.50), errors originating in expansion frames are
displayed without this special marking.
Error logger entries are stored in a log file under the STS Log directory. The name of the log file is
Errlog<n><date><time>.log (for example, Errlog712.27.05_15.14.46.log).

227
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 141: Retrieving the Log from a Site

5. Optional: To manage the information retrieved by the SW Diagnostics and Logging utility, perform
any of the following actions, as needed:

If… Then…
If you want to stop retrieving error click Stop.
logger information from the unit,
If you want to sort the diagnostic click the corresponding column heading (such as Date &
messages, Time or Site).
NOTE:
If you sort the entries, all rows marked PC Logger
Request are permanently deleted from the view.
The leftmost column (which contains severity indi-
cations) does not have a labeled heading. Howev-
er, you can still click it to sort messages by their
level of severity.

If you want to search for text within perform the following actions:
the output, a. In the Find field, type the search term.
b. Press Enter.

If you want to clear the list of en- click Clear.

tries from the logger output,
If you want to clear the site log click Clear Errors Only.
without retrieving the entries,

228
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
If you want to view a recent log file, perform the following actions:
a. Click Recent Log...
b. In the Recent Logs dialog, double-click the preferred
log file.
Figure 142: Recent Logs – Error Logging

3.5.5
Site Diagnostics
Site software diagnostics include, among other things, data concerning the communication system
performance. STS users can use this data for maintaining the system and identifying problems with remote
services.
The RTU software is based on an “object-oriented multitasking” operating system. The software consists of
modules, named “devices” (objects, entities), that handle the various tasks of the RTU. Some of the devices
handle the operation of physical elements, such as communication ports or I/O modules. Other devices are
simply software modules, such as communication applications, time handling, etc. The devices in the RTU
are based on the user-defined site configuration.
The SW Diagnostics and Loggers utility allows access through local or remote communication to each of
the devices according to their logical names (the devices are created with a logical name). The STS user can
retrieve the status of each device at different levels of breakdown to obtain historical and statistical data on
device activities.
For a detailed explanation of the diagnostics, see the MC-IoT STS Software Diagnostic Output and Error
Messages manual.

229
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.5.5.1
Retrieving Software Diagnostics from Sites
The SW Diagnostics and Loggers utility enables the user to retrieve historical and statistical data on device
activities.
For instructions on using the utility to retrieve site error logs, see Retrieving Error Logger Information from
Sites on page 226.
For instructions on using the utility to retrieve time-tagged event logs, see Retrieving Time-Tagged Event
Logs from Sites on page 233.

Procedure:
1. To open the SW Diagnostics and Loggers utility, click Site → Logger...
2. Select the Diagnostics tab.
Figure 143: SW Diagnostics and Loggers Utility–Diagnostics Tab

3. Perform one of the following steps:

● If you want to retrieve information from a locally connected site, select Local.
● If you want to retrieve information from a remote site, deselect Local and enter the preferred Site
ID and Link ID.
4. Under the Diagnostics heading, perform one of the following steps:

If… Then…
If the RTU you se- perform the following actions:
lected does not in-
clude I/O expansion a. To update the Device drop-down list, click the Get Device List
frames, icon.
b. From the Device drop-down list, select the preferred hardware device.
c. In the Level field, enter the preferred diagnostic level.

230
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
If the RTU you se- perform the following actions:
lected includes one
or more I/O expan- a. Click the More icon.
sion frames,
b. From the Frame drop-down list, select the preferred frame (Main or
Frame 1-13).

c. To update the Device drop-down list, click the Get Device List
icon.
d. From the Device drop-down list, select the preferred hardware device.
e. In the Level field, enter the preferred diagnostic level.

NOTE: For ACE1000 and MC-EDGE, to get additional devices:

a. After updating the Device drop-down list, select SYSTEM or if this item is not in the list, type
SYSTEM
b. In the Level field, enter 11
c. Click Start.
5. To connect to the unit and retrieve its software diagnostics information, click Start. If this is the first
communication session of the MDLC driver, enter the MDLC password when prompted.

The SW Diagnostics and Loggers utility displays diagnostics entries. In systems with I/O expansion,
diagnostics retrieved from I/O expansion frames are marked Frame<number> in the diagnostics
header.
If the specified frame does not exist, an error Frame does not exist is displayed. If there is
a communication problem (for example, if the frame is disconnected) an error is displayed. If an
expansion frame is selected for a software device in a system without I/O expansion, the error
Device does not exist is displayed.
Diagnostic information is stored in a log file under the STS Log directory. The name of the log file is:
Diaglog<n><date><time>.log (for example, Diaglog712.27.05_15.14.46.log).
Figure 144: Retrieving Diagnostics from a Site

231
6802979C10-BA
Chapter 3: MC-IoT STS Operation

6. Optional: To manage the information retrieved by the SW Diagnostics and Logging utility, perform
any of the following steps (as needed):

If… Then…
If you want to stop retrieving soft- click Stop.
ware diagnostics information from
the unit,
If you want to search for text within perform the following actions:
the output, a. In the Find field, type the search term.
b. Press Enter.

If you want to clear the list of en- click Clear.

tries from the diagnostics output,
If you want to view a recent log perform the following actions:
file, a. Click Recent Log...
b. In the Recent Logs dialog, double-click the preferred
log file.
Figure 145: Recent Logs – Diagnostics

3.5.6
Time Tagged Event Logging
The STS SW Diagnostics and Logging utility enables you to retrieve time tag information from any site in
the system (except IRRInet-M and MOSCAD-M RTUs, and ACE IP Gateways). The unit keeps track of every
discrete input defined as a Time-tagged DI. Every change is stored in a time tag logger, including the time of
occurrence (in 1 msec resolution).
Time tag information includes the following:
● Every change in the state of inputs defined as Time-Tagged DIs
● Time of occurrence of every change

232
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

● When performing synchronization, the outdated time and the new time
● Power up: the time of voltage breakdown, and recovery time
NOTE: If two synchronizations have been performed and no events have occurred in between, then
only the last synchronization time is stored.
The synchronization time default is 1.1.80 0:0:0.0, and synchronization should be performed at least once
every 48 days.
The synchronization can be performed in one of the following ways:
● From the STS, by selecting System → Sync
● In the application, using the “Sync” (for ladder) or MOSCAD_sync (for ‘C’ application) function call
The time tag information may be presented in two different modes:
● If the description of the application database exists in the STS, the logical names of the variables are
displayed.
● If the database description does not exist, the coordinates (X, Y, Z) of the variables are displayed.

3.5.6.1
Retrieving Time-Tagged Event Logs from Sites
The STS SW Diagnostics and Logging utility enables the user to retrieve time-tagged event logs from sites.
For instructions on using the utility to retrieve site error logs, see Retrieving Error Logger Information from
Sites on page 226.
For instructions on using the utility to retrieve site diagnostics, see Retrieving Software Diagnostics from Sites
on page 230.

Procedure:
1. To open the SW Diagnostics and Loggers utility, click Site → Logger...
2. Select the Time Tag tab.
Figure 146: SW Diagnostics and Loggers Utility–Time Tag Tab

3. Perform one of the following steps:

● If you want to retrieve information from a locally connected site, select Local.

233
6802979C10-BA
Chapter 3: MC-IoT STS Operation

● If you want to retrieve information from a remote site, deselect Local and enter the preferred Site
ID and Link ID.
4. To connect to the unit and retrieve its time-tagged event log information, perform one of the following
steps:
● To retrieve the logs without clearing the information from the unit, click Start.
● To retrieve the logs and clear the information from the unit after retrieval, click Start & Clear.
If this is the first communication session of the MDLC driver, enter the MDLC password when
prompted.
The SW Diagnostics and Loggers utility displays time-tagged events. The events are also stored in
a log file under the STS Log directory. The name of the log file is Timelog<n><date><time>.log
(for example, Timelog712.27.05_15.14.46.log).
Figure 147: Retrieving Time Tag Events from a Site

5. Optional: To manage the information retrieved by the SW Diagnostics and Logging utility, perform
any of the following steps (as needed):

If… Then…
If you want to stop retrieving time-tag- click Stop.
ged event information from the unit,
If you want to search for text within perform the following actions:
the output, a. In the Find field, type the search term.
b. Press Enter.

If you want to clear the list of time-tag- click Clear.

ged events from the output,

234
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
If you want to view a recent log file, perform the following actions:
a. Click Recent Log...
b. In the Recent Logs dialog, double-click the prefer-
red log file.
Figure 148: Recent Logs – Time-Tagged Events

3.5.7
Setting and Retrieving Site Date and Time
The STS user can retrieve the date and time from the current site, and synchronize it to the time of the STS
PC.

Procedure:
1. Select Site → Site Date & Time....
2. In the Site Date & Time dialog, perform one of the following actions:
● If you want to manage the date and time of a locally connected site, select Local.
● If you want to manage the date and time of a remote site, deselect Local and enter the preferred
Site ID and Link ID.
Figure 149: Site Date & Time Dialog

235
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3. To retrieve the site time, click Get. If this is the first communication session of the MDLC driver, enter
the MDLC password when prompted.
4. To set the date and time of the site to that of the STS PC, click Set.
5. To close the Site Date & Time dialog, click Close.

3.5.8
Synchronizing Sites
The STS user can synchronize the date and time of sites in the system to that of an RTU connected to the
host computer. To do this, the user sends a sync command.
Synchronization can also be achieved by using a Sync function call in Ladder language.
For systems with I/O expansion, see the “Time & Sequencing Synchronization of I/O Expansion” section in
the MC-IoT STS Advanced Features manual.

Procedure:
1. From the menu bar, select System → Sync...
2. In the Sync dialog, perform one of the following steps:

If… Then…
To send a sync command to the site perform the following actions:
or sites attached to a particular link, a. Select Link ID.
b. From the drop-down list, select the preferred link ID.
c. Click Sync.

To send a sync command over all select All Links and click Sync.
links to all sites in the system, NOTE: All Links does not work on DIAL.

If this is the first communication session of the MDLC driver, enter the MDLC password when
prompted.
If the synchronization command is successful, a message appears. The date and time of the site or
sites are synchronized with the RTU connected to the PC.

3. To close the Sync dialog, click Close.

236
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.5.9
Editing Network Tables in Individual Sites
Network table files can be accessed via the Network Manager, from where the STS user can open them in
the Network Configuration Editor. Alternatively, the user can open the network table attached to a particular
site directly in the Network Configuration Editor.
NOTE:
A network table can be attached to more than one site. Any changes made to the user-created network
table of one site are reflected in all sites attached to the same table file.
The generic (system-generated) network table is read-only. To edit this generic table, the user copies it
(the duplicate file is not read-only).

Procedure:
1. From the Diagram View or Table View, select the preferred site.
2. From the menu bar, select Site → Network Editor...
If no network table is assigned to the selected site, a prompt notifies you that the Network
Configuration Editor cannot be not opened. For information on assigning tables to sites, see
Managing Network Tables on page 170.
Result: The network table attached to the selected site opens in the Network Configuration Editor. For
instructions on using the Network Configuration Editor, see Editing Network Tables on page 172.

3.5.10
Editing Site Tables in Individual Sites
Site table files can be accessed via the Site Table File Manager, from where the STS user can open them in
the site table editor. Alternatively, the user can open the site table attached to a particular site directly in the
site table editor.
NOTE: A site table can be attached to more than one site. Any changes made to the user-created site
table of one site are reflected in all sites attached to the same table file.

Procedure:
1. From the Diagram View or Table View, select the preferred site.
2. From the menu bar, select Site → Site Table Editor...
If no site table is assigned to the selected site, the Site Table Editor... option is inactive in the Site
menu. For information on assigning tables to sites, see Managing Site Tables on page 188.
Result: The site table attached to the selected site opens in the site table editor. For instructions on using the
site table editor, see Site Table Editor on page 190.

3.5.11
Phonebook Files and Modems
Two sites in the system can communicate over a telephone line, provided they both have a port defined as
an external dial-up modem on a dial link. The generic, system-wide phonebook contains all the system sites
defined with dial links, along with the phone numbers of these sites. The phonebook can be edited from the
site view of any site with a dial link.

237
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Via a dial-up modem (HAYES or compatible) in the STS PC, the user can dial in to a modem connected to
any unit in the system. This allows the user to perform all STS functions remotely (from the office, home, or
any other place). The following sections describe the setup and use of this dial-up feature.
NOTE: This feature is not supported in the ACE1000 and MC-EDGE.

3.5.11.1
Modem Connections
To connect the modem to the RTU, use the modem adapter cable FLN6458 (with male 25-pin D-type
connector). Connect the modem to the RTU communication port defined as an RS-232 local computer port.
The communication port of the RTU connected to the modem is defined as Local Computer to allow the
engineer to temporarily disconnect the modem and connect the STS PC instead. Note that the connection
cable to the PC is different.
Figure 150: RTU Modem Connection Diagram (Example)

The data speed of the communication port of the RTU connected to the modem should be equal to the data
speed of the modem itself. When connecting to the PC instead of to the modem, the data speed of the PC
COM port should also match the data speed of the RTU port.
The unit connected to the modem may be referred to as Local, or by its site ID and link ID. All other sites in
the system should be referred to by their site ID and link ID.
The modem connected to the site must be in Auto-Answer mode.
For example, for the Hayes Smart Modem 1200, the jumpers should be as detailed in the following table:

Table 23: Hayes Smart Modem 1200 Jumpers Settings

PARAMETER SWITCH OPTION POSITION

DTR Status SW1 Ignore DTR Down
Auto Answer SW5 Enabled Up
Command Recognition SW8 Disabled Up

All other jumpers should be according to the default supplied by the manufacturer.
The jumpers setting of the modem connected to the central are as detailed in the following table:

Table 24: Jumpers Settings of the Modem Connected to the Central

PARAMETER SWITCH OPTION POSITION

DTR Status SW1 Ignore DTR Down

238
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

PARAMETER SWITCH OPTION POSITION

Carrier Detect SW6 Reflects Actual State Up

All other jumpers should be according to the default supplied by the manufacturer.
For more instructions on setting up the modems, see “Appendix B: Remote STS Modem Setup” in the
System Tools Suite Advanced Features Reference Guide.

3.5.11.2
Setting Dial-Up Parameters
The user may change some of the dial-up parameters by modifying the dial-up configuration file contained in
the STS directory. The file can be modified using a standard Windows text editor.
The relevant parameters are found in the [Dial] section of the file, as shown in the following screen:
[Dial]
pcc_delay_dial0= 50
pcc_dial_method0= 0

;pcc_optional_str0=
;pcc_override0= 0

;pcc_reset_str0=ATZ
;pcc_waitafterreset0=0

Procedure:
1. Open the dial-up configuration file (wmdlcdrv.ini) in the preferred Windows text editor.
The wmdlcdrv.ini file is located in the STS directory at STS<xxxx>\Prg\
Where <xxxx> is the four-digit STS version number without breaks or punctuation.
Step example:
The STS directory for version 26.50 is installed at C:\STS2650\ (default). In this case, the dial-up
configuration file is located at C:\STS2650\Prg\wmdlcdrv.ini
2. In the text editor, modify the dial-up parameters as preferred. For parameter descriptions, see Dial-Up
Parameters on page 239.
3. To apply the changes to the dial-up parameters, perform the following actions:
a. Save the wmdlcdrv.ini file.
b. Close all STS tools.
c. Stop the MDLC communication driver.
Result: The user can start the STS Dialup utility, which now uses the new parameters.

3.5.11.3
Dial-Up Parameters
Table 25: Dial-Up Parameters

Parameter Description
pcc_delay_dial0 Sets the dial delay time, in seconds (default = 50).
pcc_dial_method0 Specifies the dialing method:

239
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Parameter Description

● 0 = Tone (default)
● 1 = Pulse
● 2 = None (defers to the phone line)
pcc_optional_str0 Specifies the text to be appended to, or sent in place of, the default
string (per pcc_override0), if such is required by the modem.
NOTE: After defining the modem string, uncomment the
line in the wmdlcdrv.ini file to enable it.
This string is sent to the modem each time before dialing.

pcc_override0 (STS version ≥ Used to send optional reset strings (defined at pcc_reset_str0):
14.50) ● If pcc_override0= 1, the optional string is used instead of
the default string.
● If pcc_override0= 0 and an optional string is defined and
uncommented, it is appended to the default string (same be-
havior as STS version < 14.50.)
NOTE: After setting the parameter, uncomment the line in
the wmdlcdrv.ini file to enable it. If the line remains
commented, the behavior is the same as in STS version <
14.50.
For reset string behavior, see pcc_waitafterreset0

pcc_reset_str0 When pcc_override0=1, specifies the reset string to be sent to

the modem instead of the default ATZ and ATS0=0 (such as when
the MDLC driver first connects to the modem, or after dialing fails).
NOTE: If pcc_override0=1, but the pcc_reset_str0
value is commented (disabled) or blank, the default ATZ
and ATS0=0 are not sent to the modem after reset.
If pcc_override0=0, the default ATZ and ATS0=0 are sent to the
modem after reset, and any string defined in pcc_reset_str0 is
ignored.
pcc_waitafterreset 0 When pcc_override0=1, specifies the time (in seconds) to wait
after sending the pcc_reset_str0 string.
When pcc_override0=0 or is not set, the specified wait time is
ignored.

The following parameters are commented out by default, and must be uncommented before use:
● pcc_optional_str0
● pcc_override0
● pcc_reset_str0
● pcc_waitafterreset0

240
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.5.11.4
Editing Phonebook Files
Procedure:
1. Select the preferred site from the Diagram View or Table View.
2. From the menu bar, select Site → Phonebook Editor...
Figure 151: Phonebook Editor

NOTE: The Phonebook Editor cannot be opened if no modem is defined in the chosen site.

3. For each site equipped with a dial-up modem (up to 1000), enter the modem phone numbers (up to
three).
Figure 152: Entering Phone Numbers in the Phonebook Editor

4. Optional: To print the phonebook, click the Print icon.

The standard Windows print dialog opens, allowing the user to set the print parameters before printing
the phonebook.

241
6802979C10-BA
Chapter 3: MC-IoT STS Operation

5. To close the Phonebook Editor, perform one of the following steps:

If… Then…
To save the changes before closing, perform the following actions:

a. Click the Save icon.

b. Select Close.

To discard the changes, perform the following actions:

a. Select Close.
b. When prompted to save the changes, select No.

3.5.11.5
Dialing Site-Attached Modem Numbers
Prerequisites: Before dialing a modem from the STS, ensure that the data speed of the PC communication
port is equal to the modem data speed. Use the Communication Setup utility to set the data speed of the
communication port. See MDLC Communication Driver Configuration on page 138.

Procedure:
1. From the menu bar, select System → Dialup...
Figure 153: STS Dialup Utility

2. In the Phone Number field, type the number of the site that you want to call.
If the chosen number was previously dialed in the Dialup utility, you can select it from the drop-down
list.
3. To dial the chosen number, click Dial.
If this is the first communication session of the MDLC driver, you are prompted to confirm the MDLC
driver password.
Any progress or error messages appear in the Dialing Status box.
4. To end the call, click Hangup.
5. To close the Dialup utility, click Close.

242
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.5.12
Editing IP Conversion Tables in Individual Sites
IP conversion table files can be accessed via the IP Conversion Table File Manager, from where the STS
user can open them in the IP conversion table editor. Alternatively, the user can open the IP conversion table
attached to a particular site directly in the IP conversion table editor.
NOTE: An IP conversion table can be attached to more than one site. Any changes made to the IP
conversion table of one site are reflected in all sites attached to the same table file.

Procedure:
1. From the Diagram View or Table View, select the preferred site.
2. From the menu bar, select Site → IP Conversion Table Editor...
If no IP conversion table is assigned to the selected site, the IP Conversion Table Editor... option is
inactive in the Site menu. For information on assigning tables to sites, see Managing IP Conversion
Tables on page 175.
Result: The IP conversion table attached to the selected site opens in the IP conversion table editor. For
instructions on using the IP conversion table editor, see Editing IP Conversion Table Files on page 177.

3.5.13
Uploading Site Definitions
Files from the current ACE3600 RTU can be uploaded to the STS project via the Site Upload dialog. This
feature is not available for legacy RTU sites.
The Site Upload dialog retrieves a list of all files in the RTU. However, only the following can be uploaded and
viewed with STS utilities:
● Site configuration files
● Phonebooks
● Network source files
● IP conversion tables
Other files stored in the unit are uploaded in binary form and cannot be viewed using STS utilities.
For information on uploading a new site from the field to the STS, see Uploading New Sites to STS on page
202.

Procedure:
1. From the Diagram View or Table View, select the preferred site.
2. From the menu bar, select Site → Upload...
3. To specify the connection to be used for the upload, perform one of the following steps.

If… Then…
If the site is locally connected, perform the following actions:
● Select Local (default).
● Click OK.

243
6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
If the site is remotely connected, perform the following actions:
● Deselect the Local option.
● Set the Site ID and Link ID of the chosen site.
● Click OK.

4. In the Site Upload dialog, select the files to be uploaded.

NOTE:
Entries lacking a check box cannot be uploaded to the STS. See Uploads from Sites on page
159.
If no site configuration was ever downloaded to the unit, the Default Site Configuration label
appears in the Site Upload dialog.
5. To start the RTU configuration upload, click Upload.

An Abort button replaces the Upload button. The progress bar displays the progress of the upload.
Any errors or messages are displayed in the Upload Progress box in the bottom-left portion of the
dialog.
The names of the external files attached to the site also appear in the Upload Progress window as
they are uploaded. For example, when uploading a network source file from a unit, the file is named
upl#<site id>_1.scf. If the file is uploaded again, it is named upl#<site id>_2.scf.
NOTE: Some file types are overwritten in the STS project when uploading the site definition.
See Results of Site Definition Upload on page 244.

6. Optional: To view site source files that were uploaded to the project, open the site folder by performing
the following actions:
a. From the Diagram View or Table View, select the preferred site.
b. From the menu bar, select Site → Open Site Folder.
The site folder is located in the STS directory under \Projects\<project name>\
Each site is assigned a folder with a unique, numerical identifier. Within each site folder is a Files
folder, where the uploaded site source files can be found and unzipped.

3.5.13.1
Results of Site Definition Upload
When uploading a site definition, some files may be overwritten. The following table describes the action
taken for each file type.

Table 26: Results of Site Definition Upload

File Type Result

Site configuration File is uploaded to the site and overwrites the existing site configuration.
Phonebook File is uploaded to the project/site and overwrites the existing phonebook (if
any).
Network source File is uploaded to the project and added to the Network Manager, from
where it can be manually attached to the site.

244
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

File Type Result

IP conversion table File is uploaded to the project and added to the IP Conversion Table File
Manager, from where it can be manually attached to the site.
Site source ● File is uploaded to the site folder in the project. The files can be viewed
using the Site → Open Site Folder command.
● File can be unzipped by the user.
● Individual files (such as ladder application source) can be manually add-
ed to the project via the appropriate STS manager utility.

3.5.14
Application Programming
The STS user uses the Application Programmer utility to define applications for non-legacy RTUs. To
program a new user application for continued use with a legacy RTU, use the Application Programmer utility
included with the MOSCAD Programming ToolBox or ACE1000 Easy Configurator (whichever relevant to the
legacy unit).
NOTE: When the user uses the STS Application Programmer to open an application originally
created for a legacy RTU, it is upgraded to the current STS version. An application that was created for
an older version ACE3600 RTU may be upgraded to the current version, if preferred. In either case, if
the upgraded application is downloaded to an RTU with older firmware, certain newer features may not
be supported by the RTU.
The Application Programmer can be executed in two ways:
● From within the STS, as part of the Application Manager.
● As a standalone application (separate from the STS), by selecting Start → Programs → Motorola
MC-IoT System Tools Suite <XX.XX> → Application Programmer.
Where XX.XX is the version number of the STS installation.
When the utility is executed from within the STS, the user can create, compile, download, and monitor
applications. See Managing Applications on page 166. When the utility is run in standalone mode, its
functionality is limited to creating applications.
For details on programming an application, see Application Programmer on page 324.

3.5.15
Opening Site Applications
The following procedure describes the process of opening the application assigned to a specific site. For
instructions on opening any existing application (including applications not yet assigned to any sites), or
importing and opening applications not already included in the STS project, see Managing Applications on
page 166.
For guidance on creating new user applications, see Managing Applications on page 166 and Application
Programmer on page 324.

Procedure:
1. From the Diagram View or Table View, select the preferred site.
2. From the menu bar, select Site → Open Application.

245
6802979C10-BA
Chapter 3: MC-IoT STS Operation

If no application is assigned to the selected site, the Open Application command is disabled. For
more information on assigning applications, see Managing Applications on page 166.
Result: The application assigned to the chosen site opens in the Application Programmer window.

3.5.16
Copying Sites
Procedure:
1. To copy a site, perform the following actions:
a. In the Diagram View, right-click the preferred site.
b. In the context menu, select Copy.
2. To open the Paste Site dialog, perform the following actions:
a. In the Diagram View, right-click the position where you want to paste the copied site.
b. In the context menu, select Paste.
3. In the Paste Site dialog, input the preferred Site ID of the site to be pasted.
Figure 154: Paste Site Dialog

4. Optional: To change the default site name, enter the preferred string in the Site name field.
5. Optional: To paste the copied site more than once, change the value in the Paste <X> time(s) field.
When the value in the Paste <X> time(s) field is greater than <1> (default), a group of sites with
sequential site ID numbers are pasted. The numbering of the series is ascending, beginning with the
number specified in the Site ID field.
For example, in the Paste Site dialog, the user sets the Site IDto <30> and chooses to paste the
site <3> times. In this case, the copied site is pasted three times, and the sites are assigned site ID
numbers 30, 31, and 32.
If a number in the series is already occupied by another site in the system, then that number is
skipped. In the previous example, if a site with site ID number 31 already exists, then the three pasted
sites are assigned site ID numbers 30, 32, and 33.

246
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

6. Perform one of the following steps.

If… Then…
If the copied site is not proceed to step 7.
secured,
If the copied site is se- perform one of the following actions (Secured STS only):
cured, ● To copy the access of all existing users from the original site to
each new site, select Include security (default).
NOTE: If your policy defines Unique M2M configuration,
then the access rights of the M2M user of the original site
are also copied to each new site.
● To paste the new sites with default user access (older STS behav-
ior), deselect Include security.

Figure 155: Paste Site Dialog in Secured STS

7. To paste the site or sites, click OK.

The new site appears in the System tree and in the system diagram. The configuration of the new site
is identical to that of the original site, except for the site ID and site name. All site files are copied to
the new site.

3.5.17
Copying Sites with CPU Redundancy
Procedure:
1. To copy a site, perform the following actions:
a. In the Diagram View, right-click the preferred site.

247
6802979C10-BA
Chapter 3: MC-IoT STS Operation

b. In the context menu, select Copy.

NOTE:
If you want to copy both peers of a redundant pair, right-click either the primary or the secondary
peer of that redundant pair. Later, when prompted by the STS, you can choose to paste both
peers (see step 3).
If you want to copy only one of the redundant sites (either primary or secondary) without its peer,
you must copy that specific site.
2. To open the Paste Site dialog, perform the following actions:
a. In the Diagram View, right-click the position where you want to paste the copied site.
b. In the context menu, select Paste.
3. Perform one of the following steps:
● If you want to paste both peers (primary and secondary), click Yes.
● If you want to paste only the selected site (without its peer), click No.
4. In the Paste Site dialog, input the preferred Site ID of the site to be pasted.
NOTE: In the case of redundant sites, the Site ID field pertains to the common ID of the peers.
The primary peer is automatically assigned Site ID-1 as its private ID, and the secondary peer is
assigned Site ID+1 as its private ID. This applies even when pasting a site separately from its
redundant peer.
Figure 156: Paste Site Dialog for Single Peer

248
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 157: Paste Site Dialog for Both Peers

5. Optional: To change the default site name of the unit to be pasted, perform one of the following
actions:
● If you are pasting only a single peer, enter the preferred string in the Site name field.
● If you are pasting both peers of a redundant pair, enter the preferred string in the Primary site
name and Secondary site name fields.
6. From the drop-down list, select a unique Redundancy link name.
The redundancy link name must be different from that of the copied redundant site, and from that of
any other redundant pair in the system.
7. Perform one of the following steps.

If… Then…
If the copied site is not secured, proceed to step 8.
If the copied site is secured, perform one of the following actions (Secured STS only):
● To copy the access of all existing users from the original
site to each new site, select Include security (default).
NOTE: If your policy defines Unique M2M con-
figuration, then the access rights of the M2M
user of the original site are also copied to each
new site.
● To paste the new sites with default user access (older
STS behavior), deselect Include security.

249
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 158: Paste Site Dialog (Redundant) in Secured STS

8. To paste the site or sites, click OK.

The new site appears in the System tree and in the system diagram. The configuration of the new site
is identical to that of the original site, except for the site ID, site name, and redundancy link name. All
site files are copied to the new site.

3.5.18
Moving Sites to Areas
Procedure:
1. In the Diagram View or Table View, select the preferred site.
2. From the menu bar, select Site → Move to Area...
If no area is defined in the system, this command is disabled. See Defining Areas in the STS System
on page 99.
3. In the Select Area dialog, select the area to which you want to move the chosen site.

250
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 159: Select Area Dialog

4. To move the site to the selected area, click OK.

If there are files that are currently attached to the area, the following window pops up.
Figure 160: Assign Parent Area Files Warning

3.5.19
Toggling the FEP Status
RTUs can be used in the system as Front-End-Processors (FEPs).

Procedure:
1. In the Diagram View or Table View, select the preferred site.

251
6802979C10-BA
Chapter 3: MC-IoT STS Operation

2. From the menu bar, select Site → Toggle FEP Status.

The site icon is replaced with the FEP icon.

3. Optional: To remove the FEP status from the site, click Toggle FEP Status again.
The FEP icon reverts to the original site icon.
NOTE: IP Gateway type units (such as the ACE4600) are always marked as FEPs.

3.5.20
Deleting Sites
Procedure:
1. In the system Diagram View or Table View, select the site that you want to delete.
2. From the menu bar, select Site → Delete.
3. Perform one of the following steps.

If… Then…
If the site you want click Yes to permanently delete it.
to delete is not redun- NOTE: Clicking Yes deletes the site and saves the project.
dant, This action cannot be undone. To cancel the operation and
keep the site, select No.

If the site you want to click Yes and perform one of the following actions:
delete is redundant, ● To delete both peers, click Yes again.
● To delete only the selected peer, click No.
NOTE: Clicking either Yes or No saves the project. This action
cannot be undone. To cancel the operation and keep both
peers, select Cancel.

If you choose to delete the primary site and leave the secondary site, you can change the Site ID and
configure I/O modules in the secondary site.

3.6
Application Monitoring (ACE3600 and MC-EDGE)
The STS user can monitor the actual values of the variables defined in the application database table or
process rungs. Monitoring in real time allows the user to ensure that the application running in the RTU is
executing properly. Application monitoring is especially useful when debugging the application.
Monitoring is performed by opening the application from the STS (running on a local or remote computer) for
a specific site. Application programs for legacy RTUs are monitored in the MOSCAD Programming ToolBox
or ACE1000 Easy Configurator.
For information on database and process monitoring, see Application Monitoring on page 377.

252
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.7
STS Table Monitor
The STS Table Monitor allows runtime monitoring of actual values in various RTU database tables.
The STS Table Monitor is available only for the following site types:
● MOSCAD-M
● IRRInet-M
● ACE1000
● MC-EDGE®
● IRRInet-EDGE
For ACE3600, runtime monitoring of database tables is performed in the ACE3600 Application Programmer.
For MOSCAD/MOSCAD-L, runtime monitoring of database tables is performed in the MOSCAD
Programming ToolBox Application Programmer.
For MOSCAD-M, runtime monitoring of database tables can also be performed using the MOSCAD-M
Configurator Monitor tool.
The tree view on the left side of the STS Table Monitor contains all screens that can be monitored for the
selected site. These screens are grouped into folders, such as System Screens, I/O Screens and User
Screens (depending on the particular RTU type).
There are two kinds of screens, “form screens” and “grid screens.” Form screens display grouped fields with
their names in a non-tabular format. Grid screens display data in tables. For grid screens, it is possible to
monitor part of a table in the same way as is possible with the Application Programmer. For more information,
see Monitoring Database Tables on page 377.
The user may select which screens to display, and how often the current values of each screen should be
retrieved from the RTU. Some screens are read-only; other screens are writable and allow the user to set
certain data values in the RTU from the STS. The Update RTU and Auto Update functions are displayed
only for writable screens.
On the bottom of the main window, the Output window displays information in exactly the same manner as
the Table Monitor of the Application Programmer.
On the bottom of each screen (in the status bar), the table coordinates of the current screen object (form field
or grid cell) are displayed. For example, Table 2 Col 0 Row 0

ACE 1000, MC-EDGE, IRRInet-EDGE RTUs

The ACE1000, MC-EDGE, and IRRInet-EDGE I/O Screens include the following:
● Digital inputs
● Digital outputs
● Analog inputs
● Analog outputs
These values reflect the I/Os on the main and expansions boards of the RTU. Only the contents of the output
screens can be updated by the user.
In addition, the ACE1000, MC-EDGE, and IRRInet-EDGE include up to six User Screens. These screens
contain general purpose values (including bits, integers, floats, and longs) that are available for use in
programming.
For detailed descriptions of the ACE1000, MC-EDGE, and IRRInet-EDGE table monitor screens, see Table
Monitor Screens on page 262.

253
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 161: STS Table Monitor–MC-EDGE Digital Inputs

254
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 162: STS Table Monitor–MC-EDGE Digital Outputs

255
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 163: STS Table Monitor–MC-EDGE Analog Inputs

256
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 164: STS Table Monitor–MC-EDGE Analog Outputs

MOSCAD-M and IRRInet-M Available Monitor Screens

The MOSCAD-M and IRRInet-M System Screens include the following:
● Analogs (for monitoring analog inputs and outputs)
● Inputs (for monitoring digital inputs)
● Outputs (for monitoring digital outputs)
● Reserved bits/values
● Power supply switches
● Power management status
● Time & date (for monitoring of the real time clock)
The MOSCAD-M and IRRInet-M User Screens contain general purpose values (including floats, integers,
and bits), which are available to the programmer for use.
For detailed descriptions of the MOSCAD-M/IRRInet-M table monitor screens and their fields, see Table
Monitor Screens on page 262.
For a more detailed description of the database and information names, types, and values, refer to the ‘C’
Toolkit for MOSCAD Family RTUs manual.

257
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 165: Monitoring an IRRInet-M Site

3.7.1
Monitoring Database Tables in RTUs
The STS Table Monitor allows the user to monitor tables in the following units:
● MOSCAD-M
● IRRInet-M
● ACE 1000
● MC-EDGE
● IRRInet-EDGE
The STS Table Monitor is disabled for ACE 3600, as well as for legacy RTUs not included in the previous
list. For more information, see STS Table Monitor on page 253.
For detailed descriptions of the STS Table Monitor screens, see Table Monitor Screens on page 262.

Procedure:
1. To monitor the database tables in a site, perform the following actions:
a. From the system Diagram View or Table View, select the preferred site.
b. From the menu bar, select Site → Monitor.
2. In the STS Table Monitor–Connect to RTU dialog, perform one of the following steps.
● If you want to monitor a locally connected site, select Local (default).
● If you want to monitor a remote site, deselect Local and enter the preferred Site ID and Link ID.

258
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 166: STS Table Monitor–Connecting to RTU

3. To connect to the RTU, click Connect.

If this is the first communication session of the MDLC driver, enter the MDLC password when
prompted.
NOTE:
For MC-EDGE prior to version 28.00, the STS Table Monitor cannot be used if an application
table file (.axml) has already been downloaded to the site. In this case, use the table monitor in
the STS Application Programmer, which is aware of the actual table structure of your
application.
For MC-EDGE 28.00 and later, this limitation does not exist. Use of the Table Monitor (for I/O
tables only) is possible, even if an application table file has been downloaded to the site.
The main STS Table Monitor window displays the RTU information. Depending on the current unit
type and configuration, this information may include:
● Unit type (DC/AC)
● Main board ID
● Expansion board ID
● System version
The actual table content (for example, the number of inputs) may vary based on the RTU
configuration.

4. To monitor one or more screens, perform any of the following steps (as needed).

If… Then…
If you want to monitor a specific perform the following actions:
screen, a. In the tree on the left side of the window, right-click
the name of the preferred screen.
b. Select Monitor.

If you want to monitor all screens in a perform the following actions:

folder, a. In the tree on the left side of the window, right-click
the name of the preferred folder.
b. Select Monitor All.

259
6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
If you want to open a second STS Ta- perform the following actions:
ble Monitor session, a. Return to the STS.
b. From the site view of the preferred site, click Moni-
tor.
Another STS Table Monitor session opens in parallel
to the current session.

The screen opens and monitoring is initialized. While the STS communicates with the RTU, the icon in
the connection bar of the Monitor window is animated.

5. Optional: To change the way that you view information in the STS Table Monitor, perform any of the
following steps (as needed).

If… Then…
If you want to monitor a small perform the following actions:
block of values within the Gen- a. Right-click the table and select Exclude Section.
eral Purpose Bits, General
Purpose Values, or General b. Left-click to select a contiguous block of cells.
Purpose Floats screens, c. Right-click the block of cells and select Add Section.
The values of the selected sections are refreshed. The number
of values received from the RTU appears at the bottom of the
screen.
Figure 167: Monitoring a Small Block of Values

If you want to change the dis- perform the following actions:

play format of the monitored a. Select Monitor → Display Format.
cell or cells,
b. Select the preferred format.

6. To stop monitoring one or more screens, perform one of the following steps.
● If you want to stop a monitoring a specific screen, click the X in the upper right-hand corner of the
screen.

260
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

● If you want to close all open screens, select Window → Close All.
NOTE: When there are no open monitor windows, the user can change the Site ID or Link ID in
the STS Table Monitor window. When the user opens the first monitored window, the STS
Table Monitor window reflects the parameters of the selected site.
7. To close the STS Table Monitor, select File → Exit Table Monitor.

3.7.2
Refreshing Values in the Table Monitor
Prerequisites: Initiate table monitoring for the preferred site. See Monitoring Database Tables in RTUs on
page 258.

Procedure:
1. If you want to manage how the STS Table Monitor refreshes the values of the currently displayed
screen, perform one of the following steps.

If… Then…
If you want to refresh the values of the currently select Monitor → Refresh.
displayed screen (or block of values) only once,
If you want to refresh the values of the currently perform the following actions:
displayed screen (or block of values) periodically, a. Select Monitor → Refresh Continu-
ously.
b. In the Rate value field, specify the rate
of the refresh (in seconds).

2. Optional: If you want to stop refreshing the values, select Monitor → Abort Monitor.

3.7.3
Updating RTUs via the Table Monitor
Some of the screens in the STS Table Monitor are writable. The user can make changes to the tables in
these screens and upload the changes to the RTU. Certain screens are read-only and do not allow the user
to make changes to the RTU.For more information on the types of screens available, see STS Table Monitor
on page 253.
Prerequisites: Initiate table monitoring for the preferred site. See Monitoring Database Tables in RTUs on
page 258.

Procedure:
If you want to update the RTU with changes made in the STS Table Monitor, perform one of the following
actions:
● If you want to update the RTU as each change is made to the current screen (while in Refresh
Continuously mode1), select Monitor → Auto Update.
● If you want to manually update the RTU (when not in Refresh Continuously mode1), select Monitor
→ Update RTU.
1See Refreshing Values in the Table Monitor on page 261.

261
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.7.4
Copying Information in the Table Monitor
The user can copy information from the screens in the STS Table Monitor, including strings of text in
individual screens, as well as the entire contents of all open screens. The user can paste the copied
information within the monitored tables (if not read-only) or into external applications.
Prerequisites: Initiate table monitoring for the preferred site. See Monitoring Database Tables in RTUs on
page 258.

Procedure:
To copy and paste information displayed in one or more STS Table Monitor screens, perform any of the
following steps (as needed).

If… Then…
If you want to copy and paste perform the following actions:
text in a specific screen, a. Select the preferred text.
b. Click the Copy icon.
c. Select the table cell where you want to paste the copied text.
d. Click the Paste icon.

If you want to copy information click the Snapshot icon.

from all the open screens, A message appears indicating that the copy was successful. The
information from all open screens is copied into the clipboard and
can be pasted as text (for example, into Microsoft Word® or Excel®).

3.7.5
Printing Screens in the Table Monitor
Prerequisites: Initiate table monitoring for the preferred site. See Monitoring Database Tables in RTUs on
page 258.

Procedure:
To print the currently open screen or screens, perform one of the following actions:
● If you want to open the Windows print dialog, select File → Print.
● If you want to view a print preview before printing, select File → Print Preview.

3.7.6
Table Monitor Screens
ACE1000/MC-EDGE/IRRInet-EDGE

Table 27: ACE1000/MC-EDGE/IRRInet-EDGE STS Table Monitor Screens

Screen Description
Digital Inputs Reports the status of various RTU digital inputs in the form of Boolean values
(ON/OFF). The values in the Digital Inputs screen cannot be updated by the user.
The Counters are read-only; they indicate the number of C.O.S used for each DI.

262
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Screen Description
Digital Outputs Reports the status of various RTU digital outputs in the form of Boolean values
(ON/OFF). The Digital Outputs screen is updated when a user ‘C’ application
scans the outputs. Digital output values can be updated by clicking spin buttons in
the table cell or pressing the up/down arrow keys. The BI is the current status of
the digital output.
Analog Inputs Contains various RTU analog inputs. The values in the Analog Inputs screen
cannot be updated by the user; the screen is updated when a user ‘C’ application
scans the analog I/Os.
Analog Outputs Analog output values can be updated by clicking spin buttons in the table cell. The
BI is the current status of the analog output (system 31.00 and newer).
General purpose Contains user values in Boolean format. The table consists of eight columns of
bits 250 lines each, for a total of 2000 values (0-1999) useable in programming. When
the General purpose bits table is used by the ‘C’ application to manipulate the
user-provided bits, the user can debug the ‘C’ application by monitoring the table.
The user can update the values in the General purpose bits screen by selecting a
value from the drop-down list.
General purpose Contains user values in integer format. The table consists of eight columns of
values/user val- 250 lines each, for a total of 2000 values (0-1999) usable in programming. When
ues screen the General purpose values/user values table is used by the ‘C’ application to
manipulate the user-provided values, the user can debug the ‘C’ application by
monitoring the table. The user can update values in the General purpose values
screen by clicking the cells in the table.
General purpose Contains user values in floating point format. The table consists of two columns
floats of 250 lines each, for a total of 500 values (0-499) usable in programming. When
the General purpose floats table is used by the ‘C’ application to manipulate the
user-provided values, the user can debug the ‘C’ application by monitoring the
table. The values in the General purpose floats screen can be updated by the
user by clicking in the table cell.

MOSCAD-M/IRRInet-M

Table 28: MOSCAD-M/IRRInet-M STS Table Monitor Screens

Screen Description
Inputs Contains the status of various digital inputs in the RTU. The values in the Inputs
screen cannot be updated by the user. Statuses are Boolean values (ON/OFF).
Outputs Contains the status of various digital outputs in the RTU. The Outputs screen
is updated when a user ‘C’ application scans the outputs. Statuses are Boolean
values (ON/OFF). Output values can be updated by clicking spin buttons in the
table cell or pressing the up/down arrow keys.
Analogs Contains the various analog inputs and outputs in the RTU, and underflow/over-
flow statuses. The values in the Analogs screen cannot be updated by the user.
The Analogs screen is updated when a user ‘C’ application scans the analog
I/Os.
Reserved bits/val- Contains the status of various elements in the RTU. The values in the Reserved
ues bits/values screen cannot be updated by the user, but are automatically updated
when:

263
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Screen Description

● Components of the RTU are manipulated by the user

● The status of bits or values changes
NOTE: In the MOSCAD-M RTU, the values are not updated if the sys-
tem is in power management Idle Sleep mode.

Power supply Indicates the status of switches attached to the power supplies in the RTU. The
switches values in the Power supply switches screen cannot be updated by the user.
The Power supply switches screen is updated by the lower priority background
task. This task runs when all other tasks are idle, provided that the system is not
in power management Idle Sleep mode.
Power management Shows the power management Wakeup events that have been defined for the
status various threads (tasks) of the RTU. The values in the Power Management
status screen cannot be updated by the user. The Power Management status
screen is updated by the lower priority background task. This task runs when all
the other tasks are idle, provided that the system is not in power management
Idle Sleep mode.
Time & date Contains the current time and date of the RTU. The values in the Time & date
screen cannot be updated by the user. The Time & date screen is updated in the
RTU every second, and redisplayed on the screen as defined by the user in the
monitor options.
General purpose Contains user values in Boolean format. The table consists of eight columns of
bits 250 lines each, for a total of 2000 values (0-1999) usable in programming. When
the General purpose bits table is used by the ‘C’ application to manipulate
user-provided bits, the user can debug the ‘C’ application by monitoring the table.
The user can update the values in the General purpose bits screen by selecting
a value from the drop-down list.
General purpose Contains user values in integer format. The table consists of eight columns of
values/user values 250 lines each, for a total of 2000 values (0-1999) useable in programming.
screen When the General purpose values/user values table is used by the ‘C’ applica-
tion to manipulate the user-provided values, the user can debug the ‘C’ applica-
tion by monitoring the table. The user can update values in the General purpose
values screen by clicking the cells in the table.
General purpose Contains user values in floating point format. The table consists of two columns
floats of 250 lines each, for a total of 500 values (0-499) usable in programming. When
the General purpose floats table is used by the ‘C’ application to manipulate the
user-provided values, the user can debug the ‘C’ application by monitoring the
table. The values in the General purpose floats screen can be updated by the
user by clicking the cells in the table.

Table 29: MOSCAD-M/IRRInet-M STS Table Monitor Inputs Screen Fields

Table field Description

Inputs Reports the digital readings from physical devices attached to the RTU. The num-
ber of inputs varies, based on the unit configuration. The inputs are Boolean values
(ON/OFF).
Counters Counts the number of pulses according to the respective inputs. The counters are
numeric (integer) values.

264
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Table 30: MOSCAD-M/IRRInet-M STS Table Monitor Outputs Screen Fields

Table field Description

Outputs Represents the discrete values that can be sent from the RTU to a physical device.
The outputs are Boolean values (ON/OFF). These values can be updated by the
user by clicking the cells in the table.
Back Indications Provides the status of the LED indicators, which reflect the results of the digital
outputs. The back indication statuses are Boolean values (ON/OFF). These values
cannot be updated by the user.

Table 31: MOSCAD-M/IRRInet-M STS Table Monitor Reserved Bits/Values Screen Fields

Table field Description

Power In Level Integer value representing the voltage. The value is updated by the lower
priority background task, which runs when all the other tasks are idle.
NOTE: In the MOSCAD-M, the value is not updated when the sys-
tem is in power management Idle Sleep mode.

Backup Battery Status Provides the status of the backup battery as a Boolean value (OK/FAIL).
The value is updated by the lower priority background task. This task runs
when all the other tasks are idle, provided that the system is not in power
management Idle Sleep mode (MOSCAD-M only).
PushButton Provides the status of the push button as a Boolean value (RE-
LEASED/PRESSED). The value is updated whenever the button is pressed
or released.
Error Logger Provides the status of the error logger in the form of a Boolean value (EMP-
TY/NONEMPTY). The value is updated by the lower priority background
task, which runs when all the other tasks are idle. Note that in MOSCAD-M,
the value is not updated when the system is in power management Idle
Sleep mode. This value can become EMPTY if all errors are retrieved from
the Logger via the SW Diagnostics tool or via the ‘C’ application.
C Task A-C Task N Provides the status of the tasks (C Task A-C Task N) in the form of Boolean
values (IDLE/INUSE). The values are updated according to their state, such
as running or stopped (via the Configurator/STS Hardware Test).

Table 32: MOSCAD-M/IRRInet-M STS Table Monitor Power Supply Switches Screen Fields

Table field Description

Main Provides the status of the Main switch in the form of a Boolean value (ON/OFF).
LED + DI Provides the status of the LED + DI switch in the form of a Boolean value (ON/OFF).
Radio Provides the status of the Radio switch in the form of a Boolean value (ON/OFF).
IO PS Provides the status of the I/O power supply switch in the form of a Boolean value
(ON/OFF).

265
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Table 33: MOSCAD-M/IRRInet-M STS Table Monitor Power Management Status Screen Fields

Table Description
Field
Thread Lists the various tasks in the RTU. The thread names are C Task A – C Task N. Each
Name thread is associated with a user task, executed in the user application by a call to
MOSCAD_run_task()
Thread Reports the number of visas held by the thread/task. The value is in integer format.
Status ● If the task is suspended, the Thread Status is Suspended
● If the task is not used, the Thread Status is Not in Use and all other cells in the row are
blank.
The number of visas granted (by other tasks) for the thread can be retrieved using the SW
Diagnostics Tool, Device: VIMNGR, Level: 1
DI1-DI3 Each of the three DIs can be set to one of the following:
● 0→1: The task will be woken up from Idle Sleep mode when the DI goes from 0 to 1.
● 1→0: The task will be woken up from Idle Sleep mode when the DI goes from 1 to 0.
● COS: The task will be woken up from Idle Sleep mode when the DI undergoes any state
change.
● None: The DI will not be used as a Wakeup event.

PB When set to ON, the task will be woken up when the pushbutton is pressed. When set to OFF,
the task will not be woken up when the pushbutton is pressed.
Power When set to ON, the task will be woken up when the system reverts from Power Fail mode to
Fail Re- its previous mode (Normal or Idle Sleep mode). When set to OFF, the task will not be woken
covery up by this transition.
Idle to When set to ON, the task will be woken up when the system is woken up from Idle Sleep
Run mode and becomes active. When set to OFF, the task will not be woken up by this transition.
Real When the timer value (in seconds) is set by the user, the task will be woken up by the real
Time time clock after that period of time. When set to Not Applicable, the task will not use the
Timer clock as a Wakeup event. The Real time timer is in floating format.

Table 34: MOSCAD-M/IRRInet-M STS Table Monitor Time & Date Screen Fields

Table Field Description

Year The year in integer format (for example, 80=1980, 0=2000, 1=2001).
Month The month in integer format (for example, 1 = January).
Date The date (day of the month) in integer format.
Day The day of the week in integer format (for example, 1 = Sunday).
Time The time in integer format, reported as the number of minutes since the beginning of
the day (for example, 09:30 a.m. = 570).

266
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.8
Administering Sites (Advanced)
3.8.1
STS Hardware Testing
The STS user can perform a number of hardware tests, diagnostic tests, and calibrations on the ACE3600,
IRRInet-M, and ACE IP Gateway, including:
● CPU data read
● I/O module testing and calibration (except for Gateway)
● Power supply tests
● Communication port tests
● LED tests
Hardware tests for legacy RTU sites are performed in the relevant utility for that device (such as the
MOSCAD Programming ToolBox or MOSCAD-M RTU Configurator). Hardware tests for ACE1000 and MC-
EDGE are performed using the OpenSSH-based hardware test. For details, see the “ACE1000 Hardware
Test” section of the ACE1000 Easy Configuration User Guide.
Hardware tests for an RTU with I/O expansion can be performed by connecting the STS PC to the STS port
of the main CPU on the main frame, or to the STS port of the expansion module (on the expansion frame).
NOTE: In systems with I/O expansion, testing the hardware requires slightly more time.

During hardware tests, various values and settings can be changed by the user. These changes revert to
their previous values/settings whenever the following events occur:
● The Hardware Test utility is closed
● A configurable number of minutes have elapsed (see the Max time freeze in min advanced Hardware Test
parameter)
● The stopped application is executed (ACE3600 and IRRInet-M)
● The frozen module is unfrozen (ACE3600 only)

3.8.2
Performing Hardware Tests
List of topics covered in this section:
● Starting the STS Hardware Test Utility on page 268
● Testing Expansion Modules on page 269
○ Testing Digital Inputs on page 273
○ Testing Digital Outputs on page 275
○ Testing ACE3600 Analog Inputs on page 279
○ Testing ACE3600 Analog Outputs on page 282
○ Testing Ports on an Expansion LAN Switch on page 285
● Testing the CPU on page 289
● Testing LEDs on page 294
● Testing the Power Supply on page 299

267
6802979C10-BA
Chapter 3: MC-IoT STS Operation

● Testing the ACE3600 Plug-In Communication Port on page 306

● Testing the IRRInet-M Port 3 on page 307
● Power Management Test on page 308
● Upgrading Expansion Loader Firmware on page 310

3.8.2.1
Starting the STS Hardware Test Utility
Procedure:
1. To open the Hardware Test utility, perform the following actions:
a. From the system Diagram View or Table View, select the preferred site.
b. From the menu bar, select Site → Hardware Test...
2. In the Read RTU dialog, perform one of the following actions:
● If you want to test a locally connected site, select Local (default).
● If you want to test a remote site, deselect Local and enter the appropriate Site ID and Link ID.
Figure 168: Read RTU Dialog

3. To connect to the chosen site, click Read.

If this is the first communication session of the MDLC driver, enter the MDLC password when
prompted.
The Hardware Test utility retrieves the unit information. If I/O modules are attached to the unit, these
are displayed. For each I/O module in the unit, the specific module type is displayed (for example, "16
DO EE Relay 2A (V616/FLN3537)"). See I/O modules for ACE3600 and IRRInet-M below.
NOTE: In systems with I/O expansion, all defined frames are displayed. Therefore, more time is
required to retrieve module information.
Figure 169: Hardware Test–ACE3600 Site with Expansion Frames and Modules

268
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 170: Hardware Test–IRRInet-M Site with Expansion

If the module that is defined in the site configuration for that slot is compatible with the actual module
in the slot, a green check appears next to the module number.
If the module that is defined in the site configuration for that slot is incompatible with the actual module
in the slot, or the module is not responding, or missing, a red X symbol appears next to the module
number.
If the main board of an IRRInet-M unit is valid, but the expansion board is in conflict, the Partial Valid
symbol appears next to the module number. In this case, hardware tests are performed for the main
board only.

4. To abort the communication with the unit, click Abort.

For details on performing I/O module/expansion LAN switch tests, see:
Testing Digital Inputs on page 273
Testing Digital Outputs on page 275
Testing ACE3600 Analog Inputs on page 279
Testing ACE3600 Analog Outputs on page 282
Testing Ports on an Expansion LAN Switch on page 285
5. To close the Hardware Test utility, click Close.

3.8.2.2
Testing Expansion Modules
The STS Hardware Test utility allows the user to test an I/O module or expansion LAN switch attached to a
site.
NOTE: I/O operations cannot be performed on the standby CPU of a redundant site.

Prerequisites: Ensure that the RTU is connected to the STS PC, and that the Hardware Test utility is
running. See Starting the STS Hardware Test Utility on page 268.

Procedure:
1. To test a module, perform the following actions in the Hardware Test utility:
a. Under the IO Modules tab, select the preferred module from the list.
NOTE: If the module is located on an expansion frame, click the name of the frame before
selecting the module.

269
6802979C10-BA
Chapter 3: MC-IoT STS Operation

b. Click Test Module.

The Module Diagnostics appear. The number and types of tabs displayed in the Module
Diagnostics depend on the types module. For a list of the possible module diagnostics parameters,
see Module Diagnostics Parameters on page 286.
Figure 171: ACE3600 Module Diagnostics

Figure 172: IRRInet-M DC (Main and Expansion) Module Diagnostics

270
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 173: IRRInet-M AC Module Diagnostics

2. Optional: To view diagnostics for a different module, click Back to Module's List and select the
preferred module.
3. To conduct testing on the selected module, perform any of the following steps (as needed).
NOTE: To abort communication during a test, click Abort.

If… Then…
If you want to retrieve/refresh click Scan.
the module parameters,
ACE3600 only: If you want to from the Module State drop-down list, select Read state.
read the current state (freeze
or run) of a module,
ACE3600 only: If you want to from the Module State drop- down list, select Freeze module.
freeze a module, The I/O module is frozen.1
No actual I/O values are transferred to the application until the
module is unfrozen.2

ACE3600 only: If you want to from the Module State drop-down list, select Unfreeze module.
unfreeze a module, The application resumes control of the I/O module.

If you want to test the appli- from the Application drop-down list, select Get State.3
cation stored in the RTU,
If you want to run the applica- from the Application drop-down list, select Run.4
tion stored in the RTU, The application is executed from the beginning. The RTU per-
forms operations as determined by the application program.

If you want to stop the appli- from the Application drop-down list, select Stop.5
cation stored in the RTU, The system stops the application; after ten minutes, the system
automatically executes it again.

271
6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
ACE3600 only: If you want to perform the following actions:
update the FPGA file in the a. Select Update FPGA File.
I/O module,
b. In the Update FPGA File dialog, click the ... button to
browse for and select the preferred FPGA file.
c. Click Update.
The FPGA file update in the I/O module begins.6
ACE3600 DI/AI modules on- perform the following actions:
ly: If you want to test the I/O a. Select the I/O Module Power Supplies tab.
module power supply,
b. From the Operation drop-down list of the preferred module
power supply, select Get State.
Figure 174: Testing a Module Power Supply

The Exist State, Expected State and Actual State are dis-
played.
1Theapplication continues to run and only the frozen I/O module is disconnected from it. All other I/O
modules continue to interact normally with the application.
2When an input is frozen, the application receives a constant predefined value, as set by the user in
the I/O link table. When an output is frozen, the application cannot approach or change the output
state. For information on the interim values that are used by the application, see the “ACE3600 I/Os”
chapter of the MC-IoT STS Advanced Features manual.
3If no application is running, or if no application exists in the unit, this menu option is disabled.
4Ifan application is already running, or if no application exists in the module, this menu option is
disabled.
5If no application is running, or if no application exists in the module, this menu option disabled.
6The FPGA file is first downloaded to the CPU memory in the unit. After the file is verified, the CPU
downloads it to the I/O module itself (see second progress bar in Operation Progress). If the FPGA
file is older than the previously downloaded version, a warning appears. If the FPGA file has the
wrong module type, an error message appears and the download aborts. If, after downloading the
FPGA to the I/O module, the I/O module does not restart properly, the unit returns the previous FPGA
file to the I/O module.

272
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 175: Updating the FPGA File

Postrequisites: To test the inputs or outputs of an I/O module, see the relevant sections:
● Testing Digital Inputs on page 273
● Testing Digital Outputs on page 275
● Testing ACE3600 Analog Inputs on page 279
● Testing ACE3600 Analog Outputs on page 282
To test the ports on an expansion LAN switch, see Testing Ports on an Expansion LAN Switch on page 285.

3.8.2.2.1
Testing Digital Inputs
Prerequisites: Ensure that the RTU is connected to the STS PC, and that the Hardware Test utility is
running. See Starting the STS Hardware Test Utility on page 268.

Procedure:
1. To view digital inputs in the Hardware Test utility, perform the following actions:
a. Navigate to the IO Modules tab.
b. From the list of I/O modules, select the module to which the preferred set of digital inputs are
attached.
NOTE: If the module is located on an expansion frame, click the name of the frame before
selecting the module.
c. When the module entry changes color, click Test Module.
d. Navigate to the Digital IOs tab.
The Hardware Test utility displays a list of the Digital Inputs and Digital Outputs (if any exist in the
module), as shown in the following figures. For a description of the DI and DO parameters, see Input
and Output Test Parameters on page 287.

273
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 176: Testing ACE3600 Digital Inputs

Figure 177: Testing IRRInet-M Digital Inputs

2. To read the current state (freeze/run) of the input module, perform one of the following steps:
● If the input module is connected to an ACE3600, from the Module State drop-down list, select
Read state.
● If the input module is connected to an IRRInet-M, click Scan.

274
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3. To manage the inputs, perform any of the following steps (as needed).

If… Then…
If you want to reset the from the Operations drop-down list next to the preferred DI, select
DI counter, Reset Counter.
ACE3600 only: If you perform the following actions:
want to perform a DI Fil- a. From the DI Test drop-down list, select DI Filter.
ter test,
b. Based on the input signal to the DIs in the module, select DC
Mode or AC Mode.
c. To retrieve the current filter setting, click Get.
d. To set a new filter value (DC Mode only), enter the preferred value
(between 0-254 msec) and click Set.
Figure 178: DI Filter Dialog

NOTE: The DI filter is the time required to be sure that the DI

is stable. The DI filter settings apply to all DIs in the module.

ACE3600 only: If you perform the following actions:

want to perform a DI a. From the DI Test drop-down list, select DI Counters Filter.
Counters Filter test,
b. To retrieve the current filter, click Get.
c. To set a new filter value, enter the preferred value (between 0-255)
and click Set.
Figure 179: DI Counters Filter Dialog

The specified filter value (multiplied by 40 μsec) is assigned to the DIs.

3.8.2.2.2
Testing Digital Outputs
Prerequisites: Ensure that the RTU is connected to the STS PC, and that the Hardware Test utility is
running. See Starting the STS Hardware Test Utility on page 268.

275
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Procedure:
1. To view digital outputs (DO or DO FET) in the Hardware Test utility, perform the following actions:
a. Navigate to the IO Modules tab.
b. From the list of I/O modules, select the module to which the preferred set of digital outputs are
attached.
NOTE: If the module is located on an expansion frame, click the name of the frame before
selecting the module.
c. When the module entry changes color, click Test Module.
d. Navigate to the Digital IOs tab.
The Hardware Test utility displays a list of the Digital Outputs and Digital Inputs (if any exist in the
module), as shown in the following figures. For a description of the DI and DO parameters, see Input
and Output Test Parameters on page 287.
Figure 180: Testing ACE3600 Digital Outputs on a Mixed I/O Module

276
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 181: Testing ACE3600 Digital Outputs on an Output Module

Figure 182: Testing IRRInet-M DC Digital Outputs

277
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 183: Testing IRRInet-M AC Digital Outputs

2. To read the current state (freeze/run) of the output module, perform one of the following steps:
● If the module is connected to an ACE3600, select Module State → Read state.
● If the module is connected to an IRRInet-M, select Scan.
3. To manage the outputs, perform any of the following steps (as needed).

If… Then…
If you want to perform the following actions:
change the state of a. Stop the application or freeze the module.
a non-SBO output,
b. From the Control drop-down list next to the preferred DO, select the
preferred state (ON or OFF).
The selected control is displayed in the Expected column.
If you want to perform the following actions:
change the state of a. Stop the application or freeze the module.
an SBO output,
b. From the Select drop-down list next to the preferred DO, select the
preferred state (ON or OFF).
The selected state is displayed in the Expected column.
If you want to oper- click Operate.
ate a DO NOTE: You may select and operate only one SBO output at a
time.
After a short wait, the Actual column (and Actual field next to the buttons)
should reflect the operate (ON) state.

278
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
If you want to deo- click Deoperate.
perate a DO, NOTE: You may select and deoperate only one SBO output at a
time.
After a short wait, the Actual column (and Actual field next to the buttons)
should reflect the deoperate (OFF) state.

If you want to per- perform the following actions:

form a DO Loop a. Stop the application or freeze the module.
Test,
b. From the DO Loop Test drop-down list, select ON or OFF.

4. To refresh the screen, perform one of the following actions:

● Unfreeze the frozen module and click Scan.
● Run the stopped application.
5. IRRInet-M DC only: To manage the capacitor voltage on a DC solenoid, perform any of the following
steps (as needed).

If… Then…
If you want to perform the following actions:
set the ca- a. Enter the preferred voltage in the DC Capacitor Voltage field.
pacitor volt-
age on a DC b. From the DC Solenoid drop-down list, select Set DC Capacitor Voltage.
solenoid, NOTE: If the set operation fails, the previous capacitor voltage value is
restored.

If you want to perform the following actions:

test the ca- a. Enter the preferred voltage in the DC Capacitor Voltage field.
pacitor on a
DC solenoid, b. From the DC Solenoid drop-down list, select DC Capacitor Test.
A message indicating whether the test passed or failed appears.

3.8.2.2.3
Testing ACE3600 Analog Inputs
Prerequisites: Ensure that the RTU is connected to the STS PC, and that the Hardware Test utility is
running. See Starting the STS Hardware Test Utility on page 268.

Procedure:
1. To view ACE3600 analog inputs in the Hardware Test utility, perform the following actions:
a. Navigate to the IO Modules tab.
b. From the list of I/O modules, select the module to which the preferred set of analog inputs are
attached.
NOTE: If the module is located on an expansion frame, click the name of the frame before
selecting the module.
c. When the module entry changes color, click Test Module.

279
6802979C10-BA
Chapter 3: MC-IoT STS Operation

d. Navigate to the Analog Inputs tab.

The Hardware Test utility displays a list of the analog inputs, as shown in the following figure. For a
description of the analog input parameters, see Input and Output Test Parameters on page 287.
Figure 184: Testing ACE3600 Analog Inputs

2. To read the current state (freeze/run) of the analog input module: from the Module State drop-down
list, select Read state.
The current state of the AI module is displayed. If the module is not frozen and you want to freeze it,
click Freeze.

3. To view the AI Calibration Factors: from the AI Test drop-down list, select ROM Data. For a
description of the AI Calibration Factors, see Input and Output Test Parameters on page 287.
Figure 185: Analog Input Calibration Factors

280
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Calibrating Analog Inputs

NOTE: Generally, inputs are calibrated in the factory and should not be calibrated in the field.
Calibration should only be performed if board components are replaced (or if UNCAL appears in the
Calibrated column) and with the advice of service personnel.

Procedure:
1. From the Operations drop-down list next to the preferred analog input, select Calibrate AI.
2. Apply the maximum input value allowed (+20mA or +5V) to the calibrated channel.
Figure 186: Calibrate AI Dialog

3. Click Calibrate.
NOTE: The I/O module must be frozen before calibrating the AI. If the I/O module is not frozen,
a message appears asking if you want to freeze it. Click Yes to freeze the module and enable
calibration.
4. At the prompt, input the maximum value and the minimum value to the calibrated AI channel.
5. To close the Calibrate AI dialog, click Close.

Setting the AI Filter

The AI filter is the number of samples for a specific AI, the average of which is the AI value.

Procedure:
1. From the AI Test drop-down menu, select AI Filter.
Figure 187: AI Filter Dialog

2. To retrieve the current filter value, click Get.

3. To set a new filter value, select the preferred value from the drop-down list and click Set. The new
filter value is assigned to the AIs.
4. To close the AI Filter dialog, click Close.

281
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Setting the AI Differential Mode Filter

Electrical interference from the local power grid can be filtered using the AI Differential Mode.

Procedure:
1. From the AI Test drop-down menu, select AI Diff. Mode Filter.
Figure 188: AI Diff. Mode Filter Dialog

2. To retrieve the current filter, click Get.

3. To set a new filter value, select the preferred value from the drop-down list and click Set.
NOTE: The filter value should be consistent with the local power grid.

3.8.2.2.4
Testing ACE3600 Analog Outputs
Prerequisites: Ensure that the RTU is connected to the STS PC, and that the Hardware Test utility is
running. See Starting the STS Hardware Test Utility on page 268.

Procedure:
1. To view ACE3600 analog outputs in the Hardware Test utility, perform the following actions:
a. Navigate to the IO Modules tab.
b. From the list of I/O modules, select the module to which the preferred set of analog outputs are
attached.
NOTE: If the module is located on an expansion frame, click the name of the frame before
selecting the module.
c. When the module entry changes color, click Test Module.
d. Navigate to the Analog Outputs tab.
The Hardware Test utility displays a list of the analog outputs, as shown in the following figure. For a
description of the analog output parameters, see Input and Output Test Parameters on page 287.

282
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 189: Testing ACE3600 Analog Outputs

2. To read the current state (freeze/run) of the analog output module: from the Module State drop-down
list, select Read state.
3. Optional: To display the numeric values in hexadecimal format: from the AO Test drop-down list,
select Hex.
To resume viewing the values in decimal format, deselect the Hex command.
4. To test the output, perform the following actions:
a. Stop the application or freeze the module.
b. From the Type drop-down list next to the preferred AO, select a type (Current/Voltage/Raw Data).
c. Enter the value of the control in either the Numeric or Physical column.
d. Press Enter.
The specified value is sent to the selected analog output. To refresh the screen, unfreeze the frozen
module and click Scan, or run the stopped application.

5. To view the AO calibration factors: from the AO Test drop-down list, select ROM Data.
For a description of the AO Calibration Factors, see Input and Output Test Parameters on page 287.

283
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 190: Analog Output Calibration Factors

Calibrating Analog Outputs

NOTE: Generally, outputs are calibrated in the factory and should not be calibrated in the field.
Calibration should only be performed if board components are replaced (or if UNCAL appears in the
Calibrated column) and with the advice of service personnel.

Procedure:
1. From the Operations drop-down list next to the preferred analog output, select Calibrate AO.
2. From the Type drop-down list, select the preferred calibration type.
The following calibration types are available:
● Current (20mA upper limit and 0mA lower limit)
● Voltage (10V upper limit and 2V lower limit)
Figure 191: Calibrate AO Dialog

3. To save the current state and enable calibration, click Start.

284
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

4. Apply the maximum output value allowed (+20mA or +10V) to the calibrated channel.
5. Optional: Use the up and down arrows to adjust the allowed deviation from the maximum output value.
6. Click Calibrate.
NOTE: The I/O module must be frozen before calibrating the AO. If the I/O module is not frozen,
a message appears asking if you want to freeze it. Click Yes to freeze the module and enable
calibration.
To refresh the screen (after calibrating), unfreeze the frozen module and click Scan, or run the
stopped application.
7. Optional: To return the output to its uncalibrated state, click Erase Cal.
8. To close the Calibrate AO dialog, click Close.

3.8.2.2.5
Testing Ports on an Expansion LAN Switch
Prerequisites: Ensure that the RTU is connected to the STS PC, and that the Hardware Test utility is
running. See Starting the STS Hardware Test Utility on page 268.

Procedure:
To view the ports on an expansion LAN switch in the Hardware Test utility, perform the following actions:
a. Navigate to the IO Modules tab.
b. Select the frame to which the preferred expansion LAN switch is attached.
c. Select the preferred expansion LAN switch from the list of modules.
d. When the module entry changes color, click Test Module.
e. Navigate to the IO Links tab.
The Hardware Test utility displays the eight Links of the LAN switch, each listed with its port number in
the Link # column. The current status of each link (Connected or Disconnected) is listed in the State
column.

285
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 192: Testing an ACE3600 Expansion LAN Switch

3.8.2.2.6
Module Diagnostics Parameters

ACE3600

Table 35: ACE3600 I/O Module and Expansion LAN Switch Parameters

I/O Module Parameter Description

Application State Running/Not running
Modules States Run/Freeze
Module Diagnostics OK/Fail
Factory Track ID Factory data, unique for each I/O module
FPGA Version Version of the FPGA file

IRRInet-M DC and IRRInet-M AC

Table 36: IRRInet-M DC and IRRInet-M AC I/O Module Parameters

I/O Module Parameter Description

Application State Running/Not running
Module Diagnostic OK/Fail
Clock Diagnostic OK/Fail

286
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.8.2.2.7
Input and Output Test Parameters

Digital Inputs

Table 37: Digital IOs Tab – Digital Inputs

Column Description
DI # Displays the input number.
State Displays the status (ON or OFF) of each input. This window cannot be
edited.
Counter Displays the value of the 64 bit counters. If there is no counter, “- ” is
displayed. This window cannot be edited.
WB State (ACE3600 only) Displays the state of the wire break indicator, which monitors the external
wire connection integrity in wet inputs.
Operations Provides access to the Reset Counter function.

Digital Outputs

Table 38: Digital IOs Tab – Digital Outputs

Column Description
DO # Displays the output number.
Expected Receives the value of the selected control. (ON/OFF)
Actual Shows the actual state (ON/OFF) of the output after the CPU reads the back
indicator from the I/O module.
In addition to ON/OFF, the following Actual values may appear for IRRInet-M
boards:
OVC (Solenoid overcurrent)
OVC_ND (Solenoid overcurrent - No discharge)
N_CO (Solenoid not connected)
SMF (Solenoid mechanical failure)
CAPF (Capacitor failed)
OP (Invalid operation)
NACK (common failure)

Control (for all DOs Enables the user to control the output by selecting ON or OFF from the
except SBO DOs) drop-down menu. The selected control is displayed in the Expected column.
Controls cannot be activated while the application is running.
Sel. Actual (for Shows the actual selection state (ON/OFF) of the output after the CPU reads the
ACE3600 SBO DOs back indicator from the I/O module.
only)
Select (for ACE3600 Enables the user to select the output by selecting ON or OFF from the drop-
SBO DOs only) down menu. The Select control is displayed in the Expected column. DOs
cannot be selected or operated while the application is running.

287
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Analog Inputs

Table 39: Analog Inputs Tab

Column Description
V. Reference (Com- Shows the internal reference value:
mon Parameter, Val- ● In AI current modules, the reference is 11200 – 11800.
ue)
● In AI voltage modules, the reference is 5900 – 6200.

AI # Displays the input number. Operation 3 -

Value Displays the value of the analog measurement for each input. The readings
may be in the range of –32,000 to 32,000.
If the measurement in the corresponding input is below the nominal range (e.g.
6144 for a 4-20mA module), then UDF (for underflow) is displayed in the Flow
State column.
If the measurement in the corresponding input is above the nominal range (e.g.
32256 for a 4-20mA module), then OVF (for overflow) is displayed in the Flow
State column.
Type Displays the type (Current, Voltage, or Test) of the analog measurement descri-
bed in Value.
Flow State Displays the type of flow state (overflow or underflow) of the analog measure-
ment, as described in Value.
Calibrated Displays the actual state of the inputs (Cal for calibrated, UnCal for uncalibrat-
ed).
Operations Lists the operations which can be performed (such as Calibrate AI).

Table 40: Analog Inputs Tab – Calibration Factors

Column Description
AI# Displays the input number.
High Scale Displays the high scale of the calibration factor.
Low Scale Displays the low scale of the calibration factor.

Analog Outputs

Table 41: Analog Outputs Tab

Column Description
AO # Displays the output number (1-4)
Type Displays the type of the analog output (Current, Voltage, or Raw Data).
Numeric Sets the output value in numerical form in the range of 0 to 16000. You
cannot set the output value while the application is running.
Physical Sets the output value either in voltage or current according to the output
type. The values for voltage are 0 to 10 V and the values for current are
0 to 20 mA. You cannot access this field unless the module is in freeze
state.

288
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Column Description
Calibrated Indicates the actual calibration states of the output. This column cannot
be edited. It may display one of the following statuses:
OK (calibrated for voltage and current)
UNCALIBRATED (not calibrated)
UNCAL CURRENT (not calibrated for current)
UNCAL VOLTAGE (not calibrated for voltage)

Operations Lists the operations which can be performed (such as Calibrate AO).

Table 42: Analog Outputs Tab – Calibration Fields

Field Description
Calibration – Type ● Current (20mA upper limit and 4mA lower limit)
● Voltage (10V upper limit and 2V lower limit)
Up Used to adjust the default values of the upper and lower limits. The next
time the Hardware Test utility is used, the upper and lower limits reflect
Down
the last value selected.
NOTE: You cannot calibrate while the application is running.

Status Indicates the status of the calibration. The possible status indicators are:
● Calibrating
● OK
● Fail
Status value is last calibration state or “Calibrating”, if calibration is in
process.

Table 43: Analog Outputs Tab – Calibration Factors

Column Description
AO # Displays the output number.
Parameter Calibration setting (Voltage High/Voltage Low, Current High/Current
Low)
Abs. Value Reflects the actual/absolute of the upper/lower values after calibration.

3.8.2.3
Testing the CPU
Prerequisites: Ensure that the RTU is connected to the STS PC, and that the Hardware Test utility is
running. See Starting the STS Hardware Test Utility on page 268.

Procedure:
1. Navigate to the CPU tab.
The Hardware Test utility reads the current CPU parameters from the unit and displays them in a
table. For detailed descriptions of the CPU parameters, see CPU Test Parameters on page 292.

289
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 193: Testing an ACE3600 Main CPU

Figure 194: Testing an ACE3600 Expansion Module CPU

290
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 195: Testing an ACE IP Gateway CPU

Figure 196: Testing an IRRInet-M CPU

2. Optional: To reread the CPU parameters, click Scan.

In a system with I/O expansion, first select the preferred frame, and then click Scan. To abort the
scan, click Abort.
3. Optional: To deactivate the active CPU in a redundant site, perform the following actions:
a. Click Deactivate CPU.
b. When prompted to confirm the operation, click Yes.
The Redundancy State changes from Active to Standby. The system prompts the user to click
Read RTU to update the state of the I/O modules in the IO Module tab.

291
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 197: Deactivating the CPU in a Redundant Site

3.8.2.3.1
CPU Test Parameters

ACE3600 Main CPU/ACE IP Gateway

Table 44: ACE3600 Main CPU/ACE IP Gateway Test Parameters

CPU Parameter Description

PB1 Status of Pushbutton 1 (ON/OFF).
PB2 Status of Pushbutton 2 (ON/OFF).
Plug-in 1 Status of Plug-in Port 1, 12V PS (ON/OFF).
Plug-in 2 Status of Plug-in Port 2, 12V PS (ON/OFF).
CPU Fast Wake Up Status of the CPU Fast Wakeup feature (Enable/Disable).
If enabled, the CPU skips the memory test on startup.

RAM Size Size of the RAM in the RTU.

Battery Backed Up RAM Size Size of the RTU plug-in SRAM, which is backed up by the on-
board rechargeable lithium battery.
Total Flash Memory Size Size of the Flash Memory in the RTU.
User Flash Memory Size Total size of the User Flash Memory in the RTU.
Free User Flash Memory Available User Flash Memory in the RTU.
CPU Serial Number CPU serial number, unique for each CPU.
System Serial Number RTU serial number, unique for each RTU.
System Version Version number of the firmware.
System CRC CRC checksum of the firmware.
System Boot Version Version of the boot mode code.
FPGA Version Version number of the FPGA.
Image Location Currently active firmware (of the two images available because of
the safe firmware remote download feature).
For more information, see “Safe Firmware Download” in the MC-
IoT STS Advanced Features manual.

Model Model type (ACE 3610, ACE 3640, ACE 3680, ACE 4600)

292
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

CPU Parameter Description

Last Burn Count Number of times the firmware was burned.
SI1 Port Status Status of the SI1 on board port (Port is not used/Port is
ready and active)
SI2 Port Status Status of the SI2 on board port (Port is not used/Port is
ready and active)
PI1 Port Status Status of Plug-in port 1 (Port is not used/Port is ready
and active)
PI2 Port Status Status of Plug-in port 2 (Port is not used/Port is ready and
active)
Ethernet 1 Port Status (ACE3640, Status of Ethernet 1 port (Port is not used/Port is
ACE3680 and ACE IP Gateway only) ready and active)
HU1 Port Status (ACE3680 and Status of the USB 1 Type A host port (Port is not used/
ACE IP Gateway only) Port is ready and active)
HU2 Port Status (ACE3680 and Status of the USB 2 Type A host port (Port is not used/
ACE IP Gateway only) Port is ready and active)
DU1 Port Status (ACE3680 and Status of the USB Type B device port (Port is not used/
ACE IP Gateway only) Port is ready and active)
Startup Mode (ACE IP Gateway on- Redundancy Startup mode (Stand Alone, Redundant GW1,
ly) Redundant GW2)
Redundancy Slot (Redundant CPU Location (slot) of the CPU in the frame (Primary/Secondary).
only) If the system does not support CPU redundancy, the value is
N/A.

Redundancy State (Redundant CPU redundancy state (Active/Standby).

CPU only) If the system does not support CPU redundancy, this field is not
shown.
Redundancy Peer State (Redun- Whether a peer CPU exists (Alive/Not alive).
dant CPU only) If the system does not support CPU redundancy, this field is not
shown.

ACE3600 I/O Expansion Module

Table 45: ACE3600 I/O Expansion Module Test Parameters

CPU Parameter Description

PB1 Status of Pushbutton 1 (ON/OFF).
PB2 Status of Pushbutton 2 (ON/OFF).
RAM Size Size of the RAM in the expansion module.
Total Flash Memory Size Size of the Flash Memory in the expansion module.
CPU Serial Number CPU serial number (unique for each CPU).
System Serial Number Serial number of the RTU, including main and expansion frames (unique for
each system).

293
6802979C10-BA
Chapter 3: MC-IoT STS Operation

CPU Parameter Description

System Version Version number of the firmware.
Expansion Loader CRC CRC checksum of the firmware.
System Boot Version Version of the boot mode code.
Expansion Loader Ver- The version of the Expansion Loader software used by the expansion mod-
sion ule when it first starts up.
For more information, see “Expansion Module” in the ACE3600 RTU Own-
er’s Manual.

FPGA Version Version number of the FPGA.

Expansion Loader Loca- Location (in the Flash memory) of the Expansion Loader software used by
tion the expansion module when it first starts up.
For more information, see “Expansion Module” in the ACE3600 RTU Own-
er’s Manual.

Model IO EXPANSION 1
Last Burn Count Number of times the firmware was burned.
STS1 Port Status Status of the STS1 on board port (Port is not used/Port is ready
and active)
Ethernet 1 Port Status Status of Ethernet 1 port (Port is not used/Port is ready and
active)
Actual Rotary Switch Current setting of the I/O expansion rotary frame number selector– must be
in the range of 1-13 (1-9, or A-D hexadecimal.)

IRRInet-M

Table 46: IRRInet-M CPU Test Parameters

CPU Parameter Description

Push Button Status of Pushbutton 1 (ON/OFF).
Battery Battery state (OK/Fail).
System CRC CRC checksum of the firmware.
System Boot Version Version of the boot mode code.
RAM Size Size of the RAM in the RTU.
User Flash Memory Programmed/Erased
User Flash Memory Size Size of the User Flash Memory in the RTU.
Free User Flash Memory Amount of free memory in the User Flash Memory in the RTU.

3.8.2.4
Testing LEDs
Prerequisites: Ensure that the RTU is connected to the STS PC, and that the Hardware Test utility is
running. See Starting the STS Hardware Test Utility on page 268.

294
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Procedure:
1. Navigate to the LEDs tab.

The Hardware Test utility displays a list of the LEDs in the unit. See the following figures depicting the
LEDs State view for ACE3600, ACE IP Gateway, and IRRInet-M.
For a detailed description of the behavior of the ACE3600/ACE IP Gateway LEDs, see the ACE3600
RTU Owner’s Manual. For a detailed description of the behavior of the IRRInet-M LEDs, see the
IRRInet-M RTU Owner’s Manual.
Figure 198: ACE3600 LEDs

Figure 199: ACE IP Gateway LEDs

295
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 200: IRRInet-M LEDs

2. To view the current state of the LEDs, perform one of the following steps.
● To view the current state of the LEDs on an ACE3600 Main CPU or ACE IP Gateway, click CPU
LEDs Page.
● To view the current state of the LEDs on an ACE3600 I/O expansion module, select the preferred
frame from the Frame LEDs drop-down list.
● To view the current state of the LEDs on an IRRInet-M Main CPU, select Scan LED Page → CPU
page.
● To view the current state of IRRInet-M LEDs on another page, select the preferred page from the
Scan LED Page drop-down list.
The current state of the LEDs is displayed. See the LEDs State for the ACE 3610, ACE 3680, ACE IP
Gateway, ACE3600 Expansion CPU, and IRRInet-M in the following figures.
Figure 201: ACE3610 LEDs State

296
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 202: ACE3680 LEDs State

Figure 203: ACE IP Gateway LEDs State

297
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 204: ACE3600 Expansion CPU LEDs State

Figure 205: IRRInet-M LEDs – CPU Page

3. To test the LEDs: from the LEDs Operations drop-down list, select the preferred operation. For a
description of the LEDs tests, see LED Operations on page 299.
To abort a test, click Abort.
4. Optional: IRRInet-M only: To turn a specific (individual) LED on or off, perform the following actions:
a. From the Scan LED Page drop-down list, select the Hardware test page.
b. Click the preferred LED button.

298
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.8.2.4.1
LED Operations

ACE3600

Table 47: ACE3600 LED Operations

LEDs Test Description

Enable LEDs LEDs are under system control and are illuminated according to
actual status.
Disable LEDs Turns OFF all the LEDs (including those on expansion frames).
Test LEDs: LEDs On Turns ON all the LEDs (including those on expansion frames) for
a short period of time.
Test LEDs: Restore LEDs State Returns all the tested LEDs to their original state.
Enable CPU LEDs CPU LEDs are under system control and are illuminated accord-
ing to actual status.
Disable CPU LEDs Turns OFF all the CPU LEDs.
Test CPU LEDs: LEDs On Turns ON all the CPU LEDs for a short period of time.
Test CPU LEDs: Green LEDs Turns ON all the green CPU LEDs for a short period of time.
Test CPU LEDs: Red LEDs Turns ON all the red CPU LEDs for a short period of time.
Test CPU LEDs: Restore LEDs Returns all the tested CPU LEDs to their original state.
State

IRRInet-M

Table 48: IRRInet-M LED Operations

LEDs Test Description

Enable LEDs LEDs are under system control and are lit according to actual status.
Disable LEDs Turns OFF all the LEDs.
Test LEDs: LEDs On Turns ON all the LEDs for a short period of time.

3.8.2.5
Testing the Power Supply

Testing the ACE3600 Power Supply

NOTE: To perform a test/operation on the ACE3600 power supply module, the module must be frozen.

For a detailed description of the behavior of the ACE3600 power supply, see the ACE3600 RTU Owner’s
Manual.
Prerequisites: Ensure that the RTU is connected to the STS PC, and that the Hardware Test utility is
running. See Starting the STS Hardware Test Utility on page 268.

299
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Procedure:
1. Navigate to the Power Supplies tab.
The Hardware Test utility displays information about the ACE3600 power supply, as shown in the
following figure. In the upper-right corner of the display, the Read Application State field reports the
status of the application (Running/Stopped). The Read Power Supply State field reports the status
of the power supply module (Run/Freeze).
For detailed descriptions of the power supply parameters, see Power Supply and Power Supply ROM
Parameters on page 303.
Figure 206: Testing the ACE3600 Power Supply

2. To retrieve the current state of the power switches and data from the power supply, click Scan Power
Supply 1.
In a system with I/O expansion, first select the preferred frame, and then click Scan Power Supply 1.
To abort the scan, click Abort.
The current power switch states and the power supply ROM data are displayed.

3. To freeze the power supply, click PS Test → Freeze PS.

NOTE: To unfreeze the power supply (for example, after completing a test), click PS Test
→ Run PS.
4. To manage the ACE3600 power supply, perform any of the following steps (as needed).

If… Then…
If you want to change the perform the following actions:
state of a power switch, a. Click to open the Operation drop-down list next to the prefer-
red power switch.
b. Select the preferred state (On/Off).
NOTE: The Operation drop-down list is disabled for the
12V DC low-tier power supply.

300
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
If you want to perform a bat- perform the following actions:
tery capacity test, a. Click to open the Operation drop-down list next to the Bat-
tery Capacity State entry.
b. Select Test.
The state of the battery appears next to the Battery Capacity
State entry (for example, Battery OK.)

If you want to change the perform the following actions:

DC value of the Aux2 con- a. Click to open the Operation drop-down list next to the Aux2
nector, DC Value entry.
b. Select the preferred DC value:
● 0V (Off)
● 3.3V
● 5V
● 7.5V
● 9V
● Main DC
CAUTION: If a device is connected to either Aux2A or
Aux2B and the supplied voltage exceeds the vendor’s
recommended maximum voltage, the device might be
damaged.

Testing the IRRInet-M Power Supply

NOTE: To perform a test/operation on the IRRInet-M power supply, the application must be stopped.

For a detailed description of the behavior of the IRRInet-M power supply, see the IRRInet- M RTU Owner’s
Manual.
Prerequisites: Ensure that the RTU is connected to the STS PC, and that the Hardware Test utility is
running. See Starting the STS Hardware Test Utility on page 268.

301
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Procedure:
1. Navigate to the Power Diagnostics tab.

The Hardware Test utility displays information about the IRRInet-M power supply. In the upper-right
corner of the display, the Read Application State field reflects the status of the application (Running/
Stopped).
For detailed descriptions of the power supply parameters, see Power Supply and Power Supply ROM
Parameters on page 303.
For a comparison of the IRRInet-M AC and IRRInet-M DC Power Diagnostics view, see the following
figures.
Figure 207: IRRInet-M AC Power Diagnostics

Figure 208: IRRInet-M DC Power Diagnostics

2. To retrieve the current state from the IRRInet-M power supply, click Scan Power Diagnostics.
3. To stop the application, select Application → Stop.
NOTE: To restart the application (for example, after testing the power supply), select
Application → Run.

302
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

4. To manage the IRRInet-M power supply, perform any of the following steps (as needed).

If… Then…
If you want to change the perform the following actions:
state of a power switch, a. Click to open the Operation drop-down list next to the prefer-
red power switch.
b. Select the preferred state (On/Off).

If you want to perform a test perform the following actions:

on a power switch, a. Click to open the Operation drop-down list next to the prefer-
red power switch.
b. Select Get State (or Get for Auxiliary Power Out).
The state of the power switch is tested and appears next to the
relevant switch (for example, ON, OFF, 14.32V.)

If you want to change the DC perform the following actions:

value of the Auxiliary Power a. Click to open the Operation drop-down list next to the Auxili-
Out connector, ary Voltage entry.
b. Select the preferred DC value:
● 5V
● 7.5V
● 9.5V
● 12V DC
CAUTION: If a device is connected to the Auxiliary Pow-
er Out connector and the supplied voltage exceeds the
vendor’s recommended maximum voltage, the device
might be damaged.

3.8.2.5.1
Power Supply and Power Supply ROM Parameters

ACE3600 Power Switches

Table 49: ACE3600 Power Supply – Power Switches

Power Switch Description

Aux1A State On/Off
Always On for the 12V DC low-tier power supply
Always N/A for the DC 12V expansion power supply

Aux1B State On/Off

Always On for the 12V DC low-tier power supply.
Always N/A for the DC 12V expansion power supply.

Aux2A State On/Off

Always N/A for the 12V DC low-tier power supply.

303
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Power Switch Description

Always N/A for the DC 12V expansion power supply.

Aux2B State On/Off

Always N/A for the 12V DC low-tier power supply.
Always N/A for the DC 12V expansion power supply.

Battery Capacity State Possible values include:

● Battery OK
● Battery Needs to be Replaced
The value is always empty for the 12V DC low-tier power supply and DC 12V
expansion power supply.
The battery capacity is only tested under the following conditions:
● If a thermistor and main power exist (>12V).
● If the battery is (95-100% charged) and within temperature limit.
● If the battery type is properly configured.
● If the power supply is frozen before the power supply test.
● If all heavy current consumers are turned off (for accuracy).
For more information, see the ACE3600 RTU Owner’s Manual.
Aux2 DC Value ● 0V (Off)
● 3.3V
● 5V
● 7.5V
● 9V
● Main DC
The value is always N/A for the 12V DC low-tier power supply and DC 12V
expansion power supply.

ACE3600 Power Supply ROM Data

Table 50: ACE3600 Power Supply ROM Data (AC/DC Power Supplies)

Power Supply ROM Parameter Description

Power supply in slot Yes/No
Load Switch State Main power switch: ON/OFF
Main DC Output Level 13.2V DC (±20%)
Main Input Power Exist/Not Exist
DC Output Exist/Not Exist
PS Type ● AC with Charger
● AC without Charger

304
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Power Supply ROM Parameter Description

● DC with Charger
● DC without Charger

Battery Charge Level Charge level, percent (for example, 100%).

Battery Voltage 12.7V
Battery Capacity ● 5AH
● 6.5AH
● 10AH
● Unknown

DO 12V Status Exist/Not Exist

(DC 12V expansion power supply only.)

Motherboard Voltage 13.2 V DC ±20%

Internal Temperature Internal power supply temperature.
External Temperature Result of measurement of external thermistor.
Range: –30 to + 60°C

PS Software Version Software version of the power supply.

Minimum DC Operation Voltage The minimum operating DC voltage for the RTU. Below this
voltage, the RTU shuts down.
Reconnect Threshold The minimum DC level required to restart the RTU after it shut
down when the voltage fell below the minimum DC operation
voltage.

Table 51: ACE3600 Power Supply ROM Data (12V DC Low-Tier and Expansion Power Supplies)

Power Supply ROM Parameter Description

Power supply in slot Yes/No
Load Switch State N/A
Main DC Output Level As source
Main Input Power N/A
DC Output N/A
PS Type 12V DC PS Low-tier
DO 12V Status Exist/Not Exist
(DC 12V expansion power supply only.)
Motherboard Voltage As source
PS Software Version N/A

305
6802979C10-BA
Chapter 3: MC-IoT STS Operation

IRRInet-M

Table 52: IRRInet-M Power Diagnostics

Power Diagnostics Parame- Description

ter
Main ● Get State
● ON
● OFF

Radio ● Get State

● ON
● OFF

IO PS ● Get State
● ON
● OFF

Power Source ● Get State

● Main
● Backup (IRRInet-M AC only)

Main Power (vin) Get State – retrieves main power voltage in.
Backup Power (vin) Get State – retrieves backup power voltage in (IRRInet-M AC only).
Auxiliary Voltage Voltage level for the auxiliary power supply:
● 5V
● 7.5V
● 9.5V
● 12.5V

3.8.2.6
Testing the ACE3600 Plug-In Communication Port
Prerequisites: Ensure that the RTU is connected to the STS PC, and that the Hardware Test utility is
running. See Starting the STS Hardware Test Utility on page 268.

Procedure:
1. Navigate to the Plug-ins tab.

306
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 209: Hardware Test Utility – Plug-Ins Tab

2. To test the plug-in port, perform any of the following steps (as needed).

If… Then…
If you want to perform a tone a. Set the Transmission Time (number of seconds to send the
transmit test on a plug-in port signal to the RTU).
attached to a radio,
b. From the PI1 or PI2 drop-down list, select Tone Transmit
Test.
c. Specify the transmission signal type (Sinus data, DC data,
Pseudo random data).

To perform a self test on a from the PI1 or PI2 drop-down list, select Self Test.
plug-in port attached to a ra-
dio,

3.8.2.7
Testing the IRRInet-M Port 3
Prerequisites: Ensure that the RTU is connected to the STS PC, and that the Hardware Test utility is
running. See Starting the STS Hardware Test Utility on page 268.

Procedure:
1. Navigate to the Port 3 tab.

307
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 210: Hardware Test Utility – Port 3 Tab

2. To perform a tone transmit test on a Port 3 attached to a radio, perform the following actions:
a. Set the Transmission Time (number of seconds to send the signal to the RTU).
b. From the PORT_3 drop-down list, select Tone Transmit Test.
c. Specify the transmission signal type (Sinus data, DC data, Pseudo random data).

3.8.2.8
Power Management Test
The STS Hardware Test utility enables the user to simulate one or more Wakeup events associated with the
Power Management feature for the IRRInet-M RTU. The various Wakeup events can be used to wake up a
task that has entered Idle Sleep mode.For more on power management, see the MOSCAD-M Configurator
User Guide.
Prerequisites: Ensure that the RTU is connected to the STS PC, and that the Hardware Test utility is
running. See Starting the STS Hardware Test Utility on page 268.

Procedure:
1. Navigate to the Wakeup Events tab.
For detailed descriptions of the parameters in the Wakeup Events tab, see Wakeup Test Parameters
on page 309.

308
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Figure 211: Hardware Test – Wakeup Events Tab (IRRInet-M)

2. In the list of Wakeup Test Parameters, select one or more preferred Wakeup events for the system
by checking the appropriate box or boxes in the Enable Events column.
NOTE: The Timer Elapsed and PushButton Pressed events are enabled by default, and
cannot be unchecked.
3. In the Max Timeout Value field, set the maximum timeout value for the selected Timer Elapsed
wakeup events (default=60 seconds).
4. Click Sleep.
If the selected event occurs, the result appears in the corresponding cell in the Actual Events column.

3.8.2.8.1
Wakeup Test Parameters

Table 53: Wakeup Events for IRRInet-M RTU

Wakeup Test Parameter Description

Timer Elapsed The value set in Max Timeout Value for the Real Time Clock
(RTC) timer has elapsed.
PushButton Pressed The RTU pushbutton was pressed.
Communication Detected On Communication was received: bits received on Port 1.
PORT1
Communication Detected On Communication was received: active RS232 driver detected on
PORT2 Port 2.
Communication Detected On Communication was received: Channel Monitor (radio channel ac-
PORT3 tive) sensed on Port 3.

309
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.8.2.9
Upgrading Expansion Loader Firmware
The STS Hardware Test utility enables the user to upgrade the expansion loader firmware in an expansion
module.For information on I/O expansion, see the ACE3600 RTU Owner’s Manual and the MC-IoT STS
Advanced Features Manual.
Prerequisites:
● Ensure that the STS PC is locally connected in standalone mode to the STS1 port on the front panel of
the expansion module.
● Configure the MDLC driver for serial communication and set the data speed to 115200.
● Disconnect the Ethernet cable so that its IP address does not collide with that of the main CPU. No other
components that might create a conflict with the default IP address can be on the network.
NOTE: Generally, if you specify local for communication with the expansion module, you are
communicating with the main CPU. In bootstrap mode, however, specifying local connection means that
you are communicating with the expansion module.

Procedure:
1. While powering up the expansion module, press PB2 continuously for 5 seconds.
The expansion module enters bootstrap mode.

2. To open the STS Hardware Test utility, perform the following actions:
a. In the Diagram View or Table View, select the preferred site.
b. From the menu bar, select Site → Hardware Test...
3. Select Local and click Read.
The Expansion Loader dialog appears.
Figure 212: Expansion Loader Dialog

4. To browse for and select the appropriate load file (.bin), click ...
5. To load the firmware, click Download.
If the file is a valid expansion loader file, the download process begins. The download progress
and any messages or errors appear in the box near the bottom of the window. When the download
completes, the expansion module restarts.

310
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

6. To close the Expansion Loader dialog, click Close.

3.8.3
Configuring the Advanced Parameters
See Customizing Advanced Site Parameters on page 128. For descriptions of the various parameters, see
Site Configuration Parameters on page 395.

3.8.4
Analyzing MDLC Protocol
The STS Protocol Analyzer is a diagnostic tool that enables the advanced user to monitor and analyze
MDLC communication over various channels. The Protocol Analyzer is executed from the Windows Start
menu by selecting Programs → Motorola MC-IoT System Tools Suite<version> → Protocol Analyzer.For
information on the Protocol Analyzer, see the MC-IoT STS Advanced Features Manual.

3.8.5
Defining and Activating Encrypted MDLC
Communication
Encryption of MDLC communication is possible in secured STS projects.For information on building and
administering a secured STS project, see the MC-IoT STS Advanced System Security User Guide.

3.9
Using the Inventory
The Inventory tab contains a library of elements that can be assigned to a system or a site. The inventory
is organized in a navigation pane with collapsible folders. The inventory consists of both default elements
(located under Elements), as well as custom elements defined and added by the STS user (located under
Gallery).
For a description of the default inventory elements, see STS Inventory Elements on page 318.

3.9.1
Adding Elements from the Inventory
Prerequisites: To add elements from the Inventory, first open the system in Diagram View or Table View. If
you are currently viewing a site, exit the site view by navigating to the system root (or to any area or subarea
within the system). See Navigating the System on page 94.

Procedure:
1. In the system Diagram View or Table View, navigate to the location where you want to use an
element from the Inventory.
2. Click the Inventory tab on the left side of the screen.
3. Under Elements or Gallery, browse for the preferred element.
The elements in the Inventory tab are organized in folders such as RTU, Ports, and IO.

311
6802979C10-BA
Chapter 3: MC-IoT STS Operation

4. Click the preferred element and drag it to the preferred site in the system diagram or table.
NOTE: You can drag and drop an FEP or RTU element in any blank area in the system view to
create a new site at that location. You can drag and drop Ports and IO elements into existing,
compatible sites. You cannot drag and drop a Ports or IO element in a blank area.
5. Perform one of the following actions:

If… Then…
If you are adding an perform the following actions:
RTU or FEP to the a. In the Add RTU dialog, enter the preferred Site ID for the new site.
system,
b. Make the preferred changes (if any) to the site configuration. See
Defining Sites in the STS System on page 101.
NOTE: For legacy RTUs, the site configuration is defined in
the relevant ToolBox/Configurator utility. To import these con-
figurations, click Import Site Configuration... in the Add RTU
dialog. See Importing Legacy RTU Site Configurations on
page 137.
c. To add the site to the system, click Add.

If you are assign- perform the following actions:

ing an individual I/O a. In the Add IO Module to Site dialog, select the preferred frame num-
module to a site, ber from the drop-down list (if applicable).
Figure 213: Add IO Module to Site Dialog

b. Click the preferred module number within the frame.

c. Click Place Module.
d. Optional: To configure the advanced parameters for the module, click
Module Configuration and click OK to save the parameter changes.
e. To save the new I/O module in the chosen site, click Finish.

312
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
MC-EDGE only: If click OK at the prompt (shown in the following figure).
you are assigning Figure 214: Add IO Group from Gallery Prompt
an I/O group to a
site,

NOTE: When you drag and drop an I/O Group to an MC-EDGE

site, all existing I/O modules in that site are deleted or overwritten.

If you are adding a perform the following actions:

port definition to a a. In the Add Port to Site dialog, select the preferred port and click Next
site, >>.
Figure 215: Add Port to Site Dialog

b. Make any preferred changes.

c. Optional: To modify the advanced physical layer and/or advanced link
layer properties, click Port Configuration and click OK to save the
parameter changes.
d. To save the port in the site, click Finish.
NOTE: If the port to be added uses a link that is not defined in
the current project (for example, a port from the user Gallery
was created in a project where the user changed the MDLC
links configuration), the user is prompted to select another link
name.

313
6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
NFM-EDGE only: If perform the following actions:
you are adding an a. In the Add RFDS Device dialog, ensure that you entered valid Site
RFDS device to a
Controller/RDM IP addresses.
site based on an ex- The secondary IP address may be 0.0.0.0, if unused.
isting template,
b. Make other changes, if necessary, and click Next.
c. In the second dialog, ensure that you entered valid IP addresses in all
relevant fields and make other changes, if necessary.
d. To save the device in the site, click Finish.

For more information on configuring RTUs, I/O modules, and ports, see Defining Sites in the STS
System on page 101 and Customizing the Site Configuration on page 109.

3.9.2
Storing Elements in the Gallery
Multiple RTUs in a system often have the same configuration. To facilitate project creation, the STS user can
store customized site configurations, I/O configurations, or port definitions in the Gallery for future use. The
user can then apply these elements (making minor changes, as necessary) to sites in any project.

Procedure:
1. Perform any of the following steps (as needed).

If… Then…
If you want to store a site perform the following actions:
configuration in the gallery, a. Open the preferred site, or select it from the system view.
b. From the menu bar, select Site → Add to Gallery...

If you want to store a port perform the following actions:

configuration in the gallery, a. Open the site view of the preferred site.
b. Navigate to the Ports tab.
c. Click to select the preferred port (for example, SI2 or ETH1).
When selected, the port name is highlighted in orange.
d. Click Add Port to Gallery...
NOTE: Only ACE1000, ACE3600, and MC-EDGE port
configurations can be saved to the gallery.

If you want to store a single perform the following actions:

I/O module configuration in a. Open the site view of the preferred site.
the gallery,
b. Navigate to the I/O tab.
c. Select the preferred I/O module from the relevant frame. De-
pending on the unit, this may be the main frame or an expan-
sion frame.
d. Click Add I/O to Gallery...
NOTE: Only ACE1000, ACE3600, and MC-EDGE I/O
module configurations can be saved to the gallery.

314
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

If… Then…
MC-EDGE only: If you want perform the following actions:
to store a group of config- a. Open the site view of the preferred site.
ured I/O modules in the gal-
lery, b. Navigate to the I/O tab.
c. Select any I/O module.
d. To add all configured I/O modules of this site as a single
gallery item ("I/O Group"), click Add I/O Group to Gallery...

2. In the Add New Item dialog, browse to the Gallery location where you want to save the new element
(for example, Ports → MC-EDGE).
To create new folders or delete existing folders in the gallery, see Modifying Folders in the Gallery on
page 316.
Figure 216: Add New Item Dialog

3. Under Item Properties, enter the Name of the new element.

To facilitate future use, choose a unique name that identifies the element.
4. Optional: In the Description field, enter a description of the new element.
5. To save the new element in the gallery, click OK.
The saved element appears in the gallery at the designated location, and is available to all sites and
projects in the STS.
NOTE: Any RTU element saved in the gallery does not include a site ID. A site ID must be
defined in the Add RTU dialog that pops up after dragging the RTU element to the system
diagram or table.

315
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.9.3
Modifying Folders in the Gallery
The user can create, rename, and delete any folder in the Gallery section of the STS Inventory.

Procedure:
Perform any of the following steps (as needed).

If… Then…
If you want to create a perform the following actions:
subfolder within an exist- a. Right-click the name of the preferred folder.
ing folder,
b. From the context menu, select Create Subfolder in <folder name>...
c. Enter the new Folder name and click OK.

If you want to delete a perform the following actions:

folder in the gallery,
a. Right-click the name of the preferred folder.
b. From the context menu, select Delete Folder <folder name>...
c. To confirm the operation and delete the folder, click Yes.

If you want to create a perform the following actions:

root folder (at the highest
a. Right-click anywhere in the gallery.
level of the tree),
b. From the context menu, select Create Root Folder...
c. Enter the preferred Folder name.
d. To create the root folder with the chosen name, click OK.
The new folder appears in the tree (placed alphabetically).

3.9.4
Importing the Gallery from Another STS
Site, I/O module, or port definitions, which were saved in the gallery of another instance or version of the
STS, can be imported into the current STS installation.
By default, STS gallery files are located in the STS installation directory at \Prg\Gallery\

Procedure:
1. To open the Gallery Source dialog, select File → Import Gallery...
Figure 217: Gallery Source Dialog

316
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

2. Perform one of the following steps.

If… Then…
If you want to import perform the following actions:
the gallery from anoth- a. From the list, select the STS installation that includes the preferred
er STS installation on gallery.
the same PC,
b. Click OK.

If you want to import perform the following actions:

the gallery from anoth- a. In the Gallery Source dialog, select Other Location...
er source,
b. In the Open dialog, browse for the preferred gallery file.
NOTE: The gallery file must be named
GalleryTree.xml (the Open dialog cannot retrieve files
of any other name, even if ending with .xml).
c. To import the selected file, click Open.

The Import Gallery dialog appears (shown in the following figure). The left pane displays the file
structure of the gallery file chosen via the Gallery Source dialog. The right pane reflects the file
structure of the gallery in the current STS installation.
Figure 218: Import Gallery Dialog

317
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3. In the Import Gallery dialog, perform one of the following steps.

If… Then…
If you want to import the perform the following actions:
entire gallery, a. In the Source Gallery pane, select (check) the Source Gallery
folder.
b. In the Destination pane, select (highlight) the This Gallery fold-
er.
c. Click OK.

If you want to import se- perform the following actions:

lect items located in dif- a. In the Source Gallery pane, select the folders containing the
ferent folders (for exam- preferred elements.
ple, a port and an I/O
module) b. In the Destination pane, select (highlight) the This Gallery fold-
er.
c. Click OK.

If you want to import se- perform the following actions:

lect items from a specif- a. In the Source Gallery pane, select one or more preferred ele-
ic folder (for example, all ments.
I/Os in the same folder),
b. In the Destination pane, select (highlight) the folder to which you
want to import the chosen element or elements.
c. Click OK.

3.9.5
STS Inventory Elements
The STS Inventory tab includes various site, I/O module, and port definitions that the user can assign to the
project. The STS user may add their own elements to the Gallery section of the inventory. The following table
describes only the default inventory elements provided by Motorola (located under Elements).

Table 54: STS Inventory Elements Grouped by Folder

Folder name Contents

FEP Includes default site definitions for the following units:
● ACE IP Gateway (CPU 4600)
● Legacy IP Gateway
Figure 219: STS Inventory – FEP

RTU Includes default site definitions for the following units:

318
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Folder name Contents

● ACE1000
● ACE3600
● AuxIO-EDGE and NFM-EDGE
● IRRInet (including IRRInet-ACE, IRRInet-EDGE, and IRRInet-M)
● Legacy (including MOSCAD, MOSCAD-L, and MOSCAD-M)
● MC-EDGE
Figure 220: STS Inventory – RTU

Ports Includes various port definitions for ACE1000, ACE3600, and MC-EDGE.
Figure 221: STS Inventory – Ports

IO Includes various I/O module definitions, such as 16AI, 32DI, etc.

For ACE1000 and MC-EDGE, the available elements include:
● 8DO/2AO expansion output module
● 12DI/8AI expansion input module
● 7DI/6DO/4AI/1AO mixed I/O expansion module
For MC-EDGE, the STS also includes two more expansion I/O modules (sup-
ported by firmware 23.00 or newer):

319
6802979C10-BA
Chapter 3: MC-IoT STS Operation

Folder name Contents

● 8DO/16DI 5–18V
● 8DO/16DI 48V
Figure 222: STS Inventory – IO – ACE1000

Figure 223: STS Inventory – IO – ACE3600

320
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Folder name Contents

Figure 224: STS Inventory – IO – MC-EDGE

NFM devices Includes predefined NFM devices (RFDS templates).

Figure 225: STS Inventory – NFM devices – RFDS Templates

3.10
Viewing the Online Help and STS Version
The STS includes an online help that opens separately from the STS in the default web browser. The online
help is organized into chapters and sections to allow the user to browse for topics of interest. While located
in certain areas of the STS, the user can open the online help directly to the relevant section for that area or
feature of the STS.

Procedure:
● If you want to open the online help to the main page, select Help → Contents.
● If you want to view the online help section for a specific feature of the STS, while using that feature
press F1.
● If you want to view the STS software version, select Help → About...
● If you want to view the legal notices, select Help → About... → Legal Notices.

321
6802979C10-BA
Chapter 3: MC-IoT STS Operation

3.11
Exporting and Importing Site Properties
The STS user can export site properties to a table in a .csv file (which can be edited in Microsoft Excel).
After cloning the port properties of a site and performing any required changes to the table, the user can
import the file data to other sites. This feature is useful when setting up Ethernet communication ports across
multiple sites.

Exporting Site Properties to a .csv File

Procedure:
1. From the menu bar, select System → Export Site Properties...
2. In the STS – Parameters to Export dialog (shown in the following figure), select the parameters that
you want to include in the .csv table file. The following table describes the parameters that can be
exported.
Figure 226: STS – Parameters to Export Dialog

Table 55: Parameters to Export

Parameter Description
Site Name Name of the current site
ETH1 IP Address Ethernet communication over LAN using a DHCP-supplied IP address.
PI1 IP Address Plug-in port 1 IP address
PI2 IP Address Plug-in port 2 IP address
Authentication serv- Authentication servers priority
er

322
 6802979C10-BA
Chapter 3: MC-IoT STS Operation

Parameter Description
For additional information, see the MC-IoT Advanced System Security
Manual.

3. To export the parameters, click OK and follow the instructions on the screen.

Importing Site Properties Tables to Sites

Procedure:
1. From the menu bar, select System → Import Site Properties...
2. In the Open dialog, browse to the .csv table file containing the preferred site properties.
3. To import the properties, click OK.

323
6802979C10-BA
Chapter 4: Application Programmer

Chapter 4

Application Programmer
4.1
Application Programmer Overview
The STS Application Programmer enables the user to create and configure a user application, and to monitor
the defined control program in an RTU.
The Application Programmer has two main functions:
● Programming of user applications (database and process) to be executed by the system software in
RTUs. See Application Programming on page 325.
● Online monitoring of defined control programs in RTUs. See Application Monitoring on page 377.
The Application Programmer can be launched from within the STS, or in standalone mode via the
Windows Start menu. See Starting the Application Programmer on page 326. STS Mode is used for
programming applications for specific sites, compiling, linking I/Os, and downloading the application to
the RTU. Standalone mode has fewer commands and functions available, and is used for programming
applications only.
The Application Programmer window (shown in the following figure) includes an Application bar, a
workspace window, and an Output bar. Note that the window differs slightly in standalone mode. When
the ACE3600 Enhanced PID Add-on has been installed, the menu bar also includes an Enhanced PID menu.
For more on Enhanced PID, see the ACE3600 Enhanced PID Application User Guide.
Figure 227: Application Programmer in STS Mode

324
 6802979C10-BA
Chapter 4: Application Programmer

The Application bar is located on the left side of the window and includes the Database, Process, and I/O
Link tabs.
The Output bar is located at the bottom of the window and includes a number of tabs, each of which displays
output information to the user. The Output bar tabs are as follows:
● Application Info
● I/O Information
● Search
● Compile
● Analyze Information
● Monitor
● Download

4.2
Application Programming
Application programming consists of multiple phases, beginning with application creation and resulting in the
execution of the application in the RTU. After execution, the application can be monitored in the Application
Programmer. Monitoring allows the STS user to check for errors and, if necessary, debug the application.
Application programming involves the following phases:
1. Creating an application. See:
● Creating New Applications on page 326
● Opening Existing Applications on page 327
2. Defining the database. See Building a Database on page 328.
3. ACE3600 only: Programming the process (building the rung sequences). See Process Programming
(ACE3600 Only) on page 344.
4. ACE3600 and MC-EDGE® only: Linking the external I/Os (between the RTUs and the external devices).
See I/Os and Database Linking (ACE3600/MC-EDGE Only) on page 363.
5. Saving the application. See:
● Saving Applications in STS Mode on page 372
● Saving Applications in Standalone Mode on page 373
6. ACE3600 only: Compiling the resulting application and correcting any errors. See Compiling Applications
(ACE3600 Only) on page 373.
7. Downloading the application to the RTU. See Downloading Applications in the Application Programmer
on page 375.
8. Monitoring the application (database and/or rungs). See Application Monitoring on page 377.
NOTE: Before configuring your database, carefully read the following:
● Database Tables and Data Types on page 559, which provides the necessary theoretical
background
● Ladder Diagram Language on page 517, which describes in detail all programming symbols
The Application Programmer Ladder Diagram process is supported only in ACE3600.
MC-EDGE® Ladder programming is performed via CODESYS.

325
6802979C10-BA
Chapter 4: Application Programmer

4.3
Starting the Application Programmer
The STS Application Programmer can be launched from within the STS, or separately from the STS in
standalone mode.

Procedure:
Perform one of the following steps.

If… Then…
If you want to access the perform the following actions:
Application Programmer in a. From the system Diagram View or Table View, select the preferred
STS mode (from within site.
the STS),
b. From the menu bar, select Site → Open Application.
NOTE:
If no application is attached to the selected site, the Open Ap-
plication command is disabled. In this case, you must use the
Application Manager to create and attach a new application to
the site, or attach an existing application. See Managing Appli-
cations on page 166.

If you want to access the from the Windows Start menu, select Programs → Motorola MC-IoT
Application Programmer in System Tools Suite XX.XX → Application Programmer
standalone mode, where XX.XX is the version number of the STS installation.

4.4
Creating New Applications
The following section describes the procedure for creating a new application in the Application Programmer
while in standalone mode. To create a new application in STS mode, use the Application Manager.For more
information on the STS Application Manager, see Managing Applications on page 166.
Prerequisites: Launch the Application Programmer in standalone mode. See Starting the Application
Programmer on page 326.

Procedure:
1. To open the New Application dialog, select File → New Application.

326
 6802979C10-BA
Chapter 4: Application Programmer

Figure 228: Application Programmer – New Application Dialog

2. Specify the name, location, and version of the new application and click OK.
a. Enter the preferred Name of the new application.
b. Optional: If preferred, change the file Location of the new application.
The default file location is in the STS installation directory under \User
c. Select the preferred RTU Type.
NOTE: For ACE3600 applications, the Application Programmer creates .prp and .adb
files; for MC-EDGE® applications, an .axml file is created.
d. Select the preferred Version.
3. To create the application with the chosen settings, click OK.
Postrequisites: After creating the application, the database and processes can be defined in standalone
mode. To perform other operations, however, you must run the Application Programmer in STS mode. Such
operations include:
● Modifying certain application settings
● Defining I/O links
● Compiling the application
● Downloading the application to the RTU

4.5
Opening Existing Applications
The following section describes the procedure for opening an existing application in the Application
Programmer while in standalone mode. To open an existing application in STS mode, use the Application
Manager.For more information on the STS Application Manager, see Managing Applications on page 166.

Procedure:
1. Select File → Open.
2. Browse to the desired directory and select the appropriate .prp,.prg,.adb, or .axml file.
3. Click Open.
If the selected application was created in a previous version of the Application Programmer, you are
prompted to upgrade it to the current version. To upgrade to the current version, click Yes. To open
the application in its current form, click No.

327
6802979C10-BA
Chapter 4: Application Programmer

4.6
Navigating the Application Programmer Window
Procedure:
● If you want to zoom in or out in the table/rung, perform any of the following actions:
● To zoom in, select View → Zoom In.
● To zoom out, select View → Zoom Out.
● To return to normal, select View → Zoom Normal.
● If you want to switch to the Application bar, select View → Application Bar.
● If you want to switch to the Output bar, select View → Output Bar.
● If you want to move between tabs in the Application or Output bars, use the Ctrl+PgUp and
Ctrl+PgDn key combinations.
● If you want to copy text from the Output bar, perform the following actions:
a. Select the preferred text.
b. Right-click the text and select Copy.
NOTE: Does not apply to the I/O Information, Search, and Compile tabs.

● If you want to clear text from the Output bar, right-click in the field and select Clear.
NOTE: Does not apply to the I/O Information, Search, and Compile tabs.

● If you want to jump to the Database tab in the Application bar, select View → Database Tree.
● If you want to jump to the Process tab in the Application bar, select View → Process Tree.
● If you want to jump to the I/O Link tab in the Application bar, select View → I/O Link Tree.
● If you want to move back and forth between a workspace window and the Application bar, press
ESC.
● If you want to jump from a table, rung or the I/O Link tab to the corresponding tree item, select View
→ Synchronize Tree.
● If you want to arrange the open windows in the workspace, click Window and select any of the
following options:
● Cascade
● Tile Vertically
● Tile Horizontally
● If you want to close all the open windows in the workspace, select Windows → Close All.

4.7
Building a Database
The data tables in an application are the basis for various processes, including I/O link definition, automatic
central database definition, process programming, and real-time monitoring of RTU operation.
The data tables contain the variables used in the application program. These variables may correspond to
various items, such as:
● Indicators
● Flags

328
 6802979C10-BA
Chapter 4: Application Programmer

● Actual physical elements of the RTU

● Inputs and outputs attached to the RTU
The database includes three types of tables:
● User tables
● System tables
● Constant tables (ACE3600 Only)
For a detailed description of the database table types, see Database Tables and Data Types on page 559.

4.7.1
User Tables
User tables contain the user-defined data (variables). One table, the Qualifiers table, is predefined for the
user. This table may be edited in a manner similar to that of other user tables.
Use the Qualifiers table to set special qualifiers (fields and/or subgroups of variables) that:
● Affect the process in another site (in RTU-to-RTU communication).
● Identify and respond to a broadcast sent by the central.
See User Defined MDLC Communication on page 612.
NOTE: When third-party protocols are used for communication, the Qualifiers table may be deleted and
recreated as a regular user table.

4.7.2
System Tables
The system tables include reserved variables that may be used as symbolic names during process
programming. Adding a new system table is not possible.
When the System Tables item (in the Database tab of the Application bar) is expanded, the Application
Programmer displays a list of the available system tables. As shown in the following figures, the available
system tables vary between the ACE3600 and the MC-EDGE.

329
6802979C10-BA
Chapter 4: Application Programmer

Figure 229: ACE 3600 System Tables

Figure 230: MC-EDGE System Tables

4.7.3
Constant Tables (ACE3600 Only)
The constant tables include reserved constants that may be used as symbolic names during process
programming. Some constant tables have been defined for the user. You can add your own tables.
When the Constant Tables item (in the Database tab of the Application bar) is expanded, the Application
Programmer displays a list of the available constant tables. See the following figure.

330
 6802979C10-BA
Chapter 4: Application Programmer

Figure 231: ACE3600 Constant Tables

4.7.4
Single-Column Tables
A single-column table includes one data type, such as parameters.
In each row you can assign a symbol name (PAR1, for example) that is referred to during the process.
The value column is used to define a preset value, to display the value during online monitoring, or both. A
single-column table may include up to 250 rows. For a detailed description of each column, see the following
table.

Table 56: Single-Column Database Table Columns

Column Description
Index The table rows are automatically numbered; the number appears in the leftmost
column and cannot be modified manually. The user can, however, change the
sequence by inserting a new line.
Name This is where the user types the name of the variable (up to 256 characters).
Value If necessary, this is where the user types the initial value of the variable.

4.7.5
Multiple-Column Tables
Multiple-column tables may include up to eight columns for several types of data (for example, discrete input,
discrete output, etc.) with common characteristics. Every column may include a distinct data type, and each
column is edited separately.
The symbol name of the column is indexed according to the row number in the column. A multiple-column
table may include up to 250 rows.

331
6802979C10-BA
Chapter 4: Application Programmer

If preferred, the user may insert a duplicate column that already exists in another table. Inserting a duplicate
column allows the user to view that information in the current table for reference. Duplicate columns cannot
be modified.

4.7.6
Data Types
Each column in a single-column or multiple-column database table may be defined as a distinct data type.
The user can assign any one of the following data types (in parentheses is the abbreviated column data type
name as it appears in the table column):
● Discrete – Internal Bit (bit)
● Integer Value – Internal Integer Value (int)
● Real Value – Internal Real Value (real)
● Byte Value (byte)
● Long Value (long)
● Integer Parameter – Internal Integer Parameter (iprm)
● Real Parameter – Internal Real Parameter (rprm)
● Byte Parameter – Internal Byte Parameter (bprm)
● Long Parameter – Internal Long Parameter (lprm)
● Discrete Input (d-i)
● Discrete Output (d-o)
● Value Input (v-i)
● Value Output (v-o)
● Scaled Analog Input (sAI)
● Scaled Analog Output (sAO)
● Mapped Discrete (mbit)
● Mapped Value (mval)
● Mapped Byte (mbyte)
● Mapped Long (mlong)
● Hours Timer (Hr:Mn) (ACE3600 Only)
● Minutes Timer (Mn:Sc) (ACE3600 Only)
● Seconds Timer (Sc:Ms) (ACE3600 Only)
● Pulses Per Hour (pph) (ACE3600 Only)
● Time-Tagged DI (TgDI) (ACE3600 Only)
● Programmable Logic Controller (plc_vi, plc_vo, plc_di, plc_do, plc_ri, plc_ro) (ACE3600 Only)
● Index (ACE3600 Only)
● Constants (ACE3600 Only)
● IP address (IPaddr) (ACE3600 Only)
● IP address parameter (IPaddrPrm) (ACE3600 Only)
For a detailed description of the MOSCAD data types, see Database Tables and Data Types on page 559.

332
 6802979C10-BA
Chapter 4: Application Programmer

4.7.7
Creating Database Tables
Prerequisites: Open the preferred application in the Application Programmer.

Procedure:
1. Navigate to the Database tab in the Application bar.
If the tree is collapsed, click + to expand it and see the types of database tables.
2. Under User Tables or Constant Tables, right-click the preferred table type and select Append Table
→ Single/Multiple Column Table.
You can select the preferred table type by right-clicking either a default table type, or an existing,
user-created table.
NOTE: For user tables, two additional table structures are available in the Append Table
context menu: PID Table (Legacy) and Backup Blocks Table. For more information on PID
and Backup Blocks tables, see the MC-IoT STS Advanced Features manual.
3. Enter a Table Name of up to 256 characters.
4. Optional: Enter the Table Symbol to be used in the programming process.
Table symbol names can be up to 256 characters long, and can include spaces and special
characters.
5. Perform one of the following steps.

If… Then…
If you want to ap- perform the following actions:
pend a single- a. From the Table Type drop-down list, select Single Column.
column table,
b. From the Data Type drop-down menu, select the appropriate data type.
c. To append the table, click OK.

If you want to ap- perform the following actions:

pend a multiple- a. From the Table Type drop-down list, select Multiple Column.
column table,
b. To append the table, click OK.
NOTE: For multiple-column tables, the data type of each column is
individually defined. See Editing Multiple-Column Tables on page
336.

The new table is added to the end of the list in the Database tab, and can be edited. For a multiple-
column table, you are prompted to define at least one column. The Table menu appears in the menu
bar.

6. Create new rows and columns, and add the table values. See Editing Tables on page 334.
7. To save the changes to the table, select File → Save.
Until the application is saved, the modified database table has an asterisk (*) beside its name in the
tree.

4.7.8
Opening Existing Tables
Prerequisites: Open the preferred application in the Application Programmer.

333
6802979C10-BA
Chapter 4: Application Programmer

Procedure:
1. Navigate to the Database tab in the Application bar.
If the tree is collapsed, click + to expand it and see the types of database tables.
2. Double-click the preferred database table.
Result: The table form is displayed in the workspace. The Table menu appears in the menu bar.

4.7.9
Editing Tables
The commands for editing tables are accessible in the Table menu (located in the Application Programmer
menu bar).
When saving changes to a database table in an application assigned to more than one site, the user may
apply the changes to all sites or to one site only.
When This site only is selected, the user is prompted to rename the modified application for that site. The
new application is assigned to the site and must be compiled and downloaded to that site.
If the changes are applied to all sites, the user must recompile the application for all sites and download it
everywhere.
To make changes to a specific site after applying the changes to all sites, the user must reopen the
application for that particular site.

4.7.9.1
Editing Single-Column Tables
Prerequisites:
1. Open the preferred application in the Application Programmer.
2. Open the preferred table in the table form:
● To edit an existing table, double-click its name in the tree in the Database tab.
● To edit a new table, create a new table as described in Creating Database Tables on page 333.

334
 6802979C10-BA
Chapter 4: Application Programmer

Figure 232: Table Form (Single-Column Table)

NOTE: If you do not see the Table & Column Properties section (also known as the "attribute page")
in the table form, see Toggling the Attribute Page on page 339.

Procedure:
● If you want to append a new row at the end of the table, select Table → Append Row.
● If you want to insert a new row before the currently select row, select Table → Insert Row.
● If you want to modify a table entry, click in a cell in the table and enter the preferred value (or overwrite
the previous value, if one exists).
● If you want to modify the Table Name, enter the preferred name in the field.
NOTE: All tables in the database must have unique names.

● If you want to modify the Table Symbol, enter the preferred symbol in the field.
NOTE: All tables in the database must have unique symbols.

● If you want to modify the change of state (COS) flag name of the table, in the COS Name field, enter
the preferred name.
This field may contain all special characters. For more information, see User Defined MDLC
Communication on page 612.
● If you want to increase the size of the table, in the Last Index field, enter the number of the last
indexed row.
You can enter any integer up to 249 (for a maximum of 250 rows, numbered 0 – 249).
● If you want to change the data type of the table, perform the following actions:
a. In the Column Type field, select a new data type from the drop-down list.
b. Click anywhere outside of the Column Type field.

335
6802979C10-BA
Chapter 4: Application Programmer

c. To confirm the change, click Yes at the prompt.

NOTE: Changing the data type of an I/O column automatically cancels the corresponding I/O
link definitions. Changing the data type of a column that has related data (like timers,
parameters) cancels their preset values.
● If you want to delete one or more rows, perform the following actions:
a. Select the preferred row or rows (to select multiple rows, press and hold the Shift key).
b. From the menu bar, select Edit → Delete.
c. To confirm the operation, click OK at the prompt.
If the row includes a variable used in the process program (such as in a rung), a warning message is
displayed. You may accept or cancel the action. If the row includes a variable used in mapped cells,
the user can choose to search for the mapped cells. The results appear in the Search tab in the
Output bar at the bottom of the screen. The mapped cells must be removed before the row can be
deleted.
● If you want to copy rows, columns, or cell contents, select the preferred content and click Edit
→ Copy.
NOTE: To select an entire table, click the upper-left corner of the table (the index column
header).
● If you want to paste rows, columns, or cell contents, select the destination and click Edit → Paste.

4.7.9.2
Editing Multiple-Column Tables
Prerequisites:
1. Open the preferred application in the Application Programmer.
2. Open the preferred table in the table form:
● To edit an existing table, double-click its name in the tree in the Database tab.
● To edit a new table, create a new table as described in Creating Database Tables on page 333.

336
 6802979C10-BA
Chapter 4: Application Programmer

Figure 233: Table Form (Multiple-Column Table)

NOTE: If you do not see the Table & Column Properties section (also known as the "attribute page")
in the table form, see Toggling the Attribute Page on page 339.

Procedure:
● If you want to append a new column after (to the right of) the existing columns, perform the following
actions:
a. From the menu bar, select Table → Append Column.
b. In the Append Column dialog, enter the preferred Column Name.
c. In the Column Type field, select a data type from the drop-down list.
d. To append the column, click OK.
● If you want to insert a new column before the currently selected column, perform the following actions:
a. From the menu bar, select Table → Insert Column.
b. In the Insert Column dialog, enter the preferred Column Name.
c. In the Column Type field, select a data type from the drop-down list.
d. To insert the column, click OK.
● If you want to duplicate a column from another table, perform the following actions:
a. From the Table menu, select either Append Column or Insert Column (depending where you
want to place the duplicated column).
b. In the Append Column or Insert Column dialog, select Duplicate column.
c. To open the Choose Symbol dialog, click the … button located to the right of the Column Name
field.
d. In the Groups pane, select the data type to filter the list of columns available for duplication.
e. In the Database Names pane, select the name of the database that contains the column that you
want to duplicate.

337
6802979C10-BA
Chapter 4: Application Programmer

f. To append or insert the duplicate column, click OK.

NOTE: The last index of the duplicated column should be less than or equal to the last index of
the original column. Otherwise, the compiler reports an error. For example, assume that a value
data type defined as V1 in a multiple-column type has 10 rows (numbered 0–9). When you
duplicate it, the last index should be less than or equal to 9.
● If you want to modify the Table Name (in the attribute page), enter the preferred name in the field.
NOTE: All tables in the database must have unique names.

● If you want to modify the Table Symbol (in the attribute page), enter the preferred symbol in the field.
NOTE: All tables in the database must have unique symbols.

● If you want to modify the change of state flag name of the table, in the COS Name field (in the
attribute page), enter the preferred name.
This field may contain all special characters. For more information, see User Defined MDLC
Communication on page 612.
● If you want to increase the size of the table, in the Last Index field (in the attribute page), enter the
number of the last indexed row.
You can enter any integer up to 249 (for a maximum of 250 rows, numbered 0 – 249).
● If you want to change the name of a column, perform the following actions:
a. Select the preferred column.
b. In the Column Name field, overwrite the existing name with the preferred one.
c. To apply the change, click anywhere outside of the Column Name field.
Duplicated columns are displayed for reference and cannot be edited. You can make changes to the
original column in the relevant table.
● If you want to change the data type of a column, perform the following actions:
a. Select the preferred column.
b. In the Column Type field, select the preferred data type from the drop-down list.
c. Click anywhere outside of the Column Type field.
d. To apply the change, click Yes.
Changing the data type of an I/O column automatically cancels the corresponding I/O link definitions.
Changing the data type of a column that has related data (like timers, parameters) cancels their preset
values.
Duplicated columns are displayed for reference and cannot be edited. You can make changes to the
original column in the relevant table.
● If you want to delete one or more columns, perform the following actions:
a. Select the preferred column by clicking its column header. To select multiple columns, press and
hold the Shift key and select a range of columns.
b. From the menu bar, select Edit → Delete.
c. To confirm the operation, click OK at the prompt.
If the column or row includes a variable used in the process program (such as in a rung) or in an I/O
link entry, a warning message is displayed. You may accept or cancel the action. If the row includes
a variable used in mapped cells, the user can choose to search for the mapped cells. The results
appear in the Search tab in the Output bar at the bottom of the screen. The mapped cells must be
removed before the row can be deleted.

338
 6802979C10-BA
Chapter 4: Application Programmer

● If you want to delete one or more rows, perform the following actions:
a. Select the preferred row by clicking its index number. To select multiple rows, press and hold the
Shift key and select a range of rows.
b. From the menu bar, select Edit → Delete.
c. To confirm the operation, click OK at the prompt.
If the column or row includes a variable used in the process program (such as in a rung) or in an I/O
link entry, a warning message is displayed. You may accept or cancel the action. If the row includes
a variable used in mapped cells, the user can choose to search for the mapped cells. The results
appear in the Search tab in the Output bar at the bottom of the screen. The mapped cells must be
removed before the row can be deleted.

● If you want to copy rows, columns, or cell contents, select the preferred content and click Edit
→ Copy.
NOTE: To select an entire table, click the upper-left corner of the table (the index column
header).
● If you want to paste rows, columns, or cell contents, select the destination and click Edit → Paste.

4.7.9.3
Toggling the Attribute Page
The table form includes an attribute page with table and column properties, which enables the user to edit
the database. At times, however, the user might prefer to simultaneously view a larger number of rows in the
table form without the need to scroll. To do so, the user deactivates the attribute page view.

Procedure:
To toggle the attribute page, perform one of the following:
● Right-click in the table form and select Attribute Page.
● Press F8.
● Click the attribute page handle (see the following figure).
Figure 234: Attribute Page Handle

4.7.10
Searching for Variables or Duplicated Columns
A search mechanism allows you to quickly search database tables for: variables (column name, or entry in a
single-column table); duplicated columns; table symbols; COS names; or last index names.
To search for variables, columns, symbols, and names in a process rung, see Searching Rungs on page 359.
To look up a specific rung parameter in the database while editing a process rung, see Defining Rung
Element Parameters on page 355.
Prerequisites: In the Application Programmer, open the application with the preferred database.

Procedure:
1. To open the Find dialog, select Edit → Find...

339
6802979C10-BA
Chapter 4: Application Programmer

Figure 235: Application Programmer – Find Dialog

2. In the Find what field, perform one of the following actions:

● To search for a column in a multiple-column table, enter the column name.
● To search for a specific cell in a multiple-column table, enter the column name and numeric index
(for example, Column3,2).
When searching tables, whole or partial words can be used. To find part of a string, deselect Whole
Names Only.
3. Select Search in Tables (default).
4. Optional: To include duplicated columns in the search, select Search Duplicated.
5. Optional: To see a catalog of all the symbols in the database, click Browse... to open the Choose
Symbol dialog. For more information, see Finding Symbols/Variables in Applications on page 371.
6. Click Find.
NOTE: If the requested name/string appears in only one database table, that table is opened
automatically.

4.7.11
Copying (or Cutting) and Pasting Tables
Procedure:
1. In the tree in the Database tab (Application bar), right-click the preferred table and perform one of
the following actions:
● To copy the table (leaving the original table intact), select Copy.
● To cut the table, select Cut.
2. To paste the table, perform the following actions:
a. Navigate to the application where you want to paste the copied table.
b. In the tree in the Database tab, right-click the table that you want to precede the pasted table.
c. Select Paste After.
Result: If no name conflict exists, the table is pasted and appears in the project tree (immediately after the
table selected in step 2b). If a name conflict exists, the Paste Report lists the source table name and the
new name of the pasted table. The Paste Report also indicates when mapped cells of the pasted table
point to nonexistent locations in the target application (such cells are cleared). Additionally, if the originals of
duplicated columns in the pasted table do not exist, they are not pasted (and this information is included in
the report).

340
 6802979C10-BA
Chapter 4: Application Programmer

Figure 236: Paste Report Dialog

4.7.12
Deleting Tables
NOTE: For Constant Tables, you can only delete user-created tables.

Procedure:
To delete a table, including all its lines and columns, perform the following actions:
a. In the tree in the Database tab (Application bar), right-click the preferred table and select Delete.
b. To confirm the operation, click Yes at the prompt.
If a column in the table is a duplicate column in another table, a warning message is displayed. You may
accept or cancel the action.
If the database table cannot be deleted because of mapped cells or duplicate columns, the user can
choose to search for such cells or columns. The results appear in the Search tab in the Output bar at the
bottom of the screen. The mapped cells and duplicate columns must be removed before the table can be
deleted.

4.7.13
Renaming Tables
Procedure:
To rename a user-defined database table, perform the following actions:
a. In the tree in the Database tab (Application bar), right-click the preferred table and select Rename.
b. Enter the preferred name.
c. To save the change, press Enter.

4.7.14
Printing Tables
Procedure:
In the tree located in the Database tab (Application bar), right-click the preferred table and perform one
of the following actions:

341
6802979C10-BA
Chapter 4: Application Programmer

a. To open the standard Windows print dialog for the selected table, click Print...
b. To view a preview of the selected table before printing it, select Print Preview.

4.7.15
Batch Printing Tables
The Application Programmer includes a batch print function that allows the user to combine multiple tables in
a single print job. If preferred, the print job can be previewed before printing.
For instructions, see Printing Applications on page 390.

4.7.16
Monitoring Tables
Database monitoring allows the user to monitor the actual values for each database table, as reported by the
RTU during run-time operations.
For information on monitoring a database table, see Monitoring Database Tables on page 377.

4.7.17
Database Building Examples
The variables from the following examples are used later in this chapter to build the sample process. See
Examples of Building Rung Sequences on page 361.
For instructions on creating and editing database tables, see the following sections:
● Creating Database Tables on page 333
● Editing Single-Column Tables on page 334
● Editing Multiple-Column Tables on page 336

Example 1: Single-Column Table

In this example, a pump (PUMP1) is actuated under the following conditions:
● 10 seconds after valve VLV1 or VLV2 turns on.
● The emergency switch (EMRG) is off.
● The water temperature is below 80 degrees.
Five new database tables with the following characteristics are required:

Table 57: Example 1: Database Table Characteristics

Table Name Table Symbol Table Type Data Type Name Value
Discrete In- DisIn Single-column Discrete Input VLV1, VLV2,
puts EMRG
Value Input ValIn Single-column Value Input AN1
Timers Sec- TimSec Single-column Timers Sec- T1 10:00 sec
onds onds
Discrete Out- DisOut Single-column Discrete Out- PUMP1
put put

342
 6802979C10-BA
Chapter 4: Application Programmer

Table Name Table Symbol Table Type Data Type Name Value
Parameter Param Single-column Integer Pa- TEMP1 3,200
rameter

NOTE: A temperature parameter of 80°C should be entered as 3,200, because the reading range of the
analog-to-digital converter is -4,000 to +4,000. Assuming a full analog scale of 100°C (100%), this
parameter value should be 3,200.
For each row in the preceding chart, the user defines a single-column table. The Table Name, Table
Symbol, Table Type, and Column Type (data type) of each table are as described in the previous chart.
The following figure shows the five required tables, as entered into the Application Programmer.
Figure 237: Example 1: Single-Column Table Definition

Example 2: Multiple-Column Table

In this example, a series of 10 inputs (the first of which is IN) can execute a series of 10 outputs. The loop is
executed 10 times in the course of one scan.
A new database table with the following table characteristics is required:
● Table Name: LOOP
● Table Symbol: Loop
● Last Index: 9
● Table Type: Multiple Column
● Last Index Name: LstInd
The table columns in this example are as follows:

343
6802979C10-BA
Chapter 4: Application Programmer

Table 58: Example 2: Database Table Columns

Column Column Type (Data Type)

IN Discrete Input (d-i)
OUT Discrete Output (d-o)

The following figure shows the foregoing database table as entered into the Application Programmer.
Figure 238: Example 2: Multiple-Column Table Definition

When a series is involved, the series elements can be used as rung symbols during process programming
either directly (such as IN,5), or as an indexed series (IN,I). The index name (I) is defined by means of the
system index table.
You can assign meaningful names to variables in the database, such as KeyInp, TxCntr, RxVal, etc., with
capital letters. The system is not case-sensitive. Therefore, when writing rungs, you do not have to type in the
variable names with capital letters. The system automatically adjusts your entries as defined in the database
tables.

4.8
Process Programming (ACE3600 Only)
Once all variables participating in the control program have been defined via the Database Builder, you can
proceed to programming the process.
Each process is built by programming a sequence of rungs in the Motorola Advanced Ladder Diagram
Language. Generally, rungs are programmed in the Main process, and additional processes are programmed
as necessary.
Each rung defines the behavior of one or several outputs as a function of both the state of their inputs
and the time. A rung may be thought of as an array of contacts representing the states of the relevant
inputs. A “current” must “flow” through these contacts towards the elements that represent the operation to be
performed on the output. When such a flow path exists, the rung is “true,” and the appropriate operation is
performed by the output.

344
 6802979C10-BA
Chapter 4: Application Programmer

A process rung consists of an entry point, rung elements, variables, and links. The process of creating a rung
is as follows:
1. Open an existing rung or append a new rung.
2. Add elements to the rung from the list of elements.
3. Add variables to elements, where necessary.
4. Link the elements to form the rung.
5. Create branches where necessary.
6. Normalize the rung to rearrange the elements neatly.

4.8.1
Process Tree
The Application Programmer includes a process tree for viewing and managing the application processes
and associated rungs.
The process tree is located in the Application bar, under the Process tab. Initially, the tree contains only the
MAIN process (system default), which cannot be modified. As you add rungs or processes, the tree view is
filled.
Figure 239: Process Tree

When you expand a process item, the corresponding rungs are displayed as the “children” of that process in
the tree. A rung marked with a red exclamation point is one where no elements are connected to the entry
point.
The user can enter names and descriptions of processes and rungs in the same manner in which tables are
edited in the Database tab.

4.8.1.1
Creating Processes
NOTE: The MAIN process is a system default. You can append processes or rungs to MAIN. However,
you cannot modify the process itself.
Prerequisites: Open the preferred application in the Application Programmer, and navigate to the Process
tab (located in the Application bar).

Procedure:
1. Perform one of the following steps:
● If you want to append a new process to the end of the process tree, right-click the application
name (top of the tree) and select Append Process.
● If you want to insert a new process before an existing process, right-click the name of the existing
process and select Insert Process.

345
6802979C10-BA
Chapter 4: Application Programmer

2. In the Append Process or Insert Process dialog, enter a Name for the new process.
3. Optional: Enter a Description for the new process.
4. To append or insert the new process, click OK.
Postrequisites: To program the process, see the following sections on creating and editing rungs.

4.8.1.2
Creating Rungs
Prerequisites: Open the preferred application in the Application Programmer, and navigate to the Process
tab (located in the Application bar).

Procedure:
1. Perform one of the following steps:
● If you want to append a new rung to the end of a process, right-click the name of the preferred
process and select Append Rung.
● If you want to insert a new rung before an existing rung, right-click the name of the existing rung
and select Insert Rung.
2. Optional: In the Append Rung or Insert Rung dialog, enter the new rung Name (up to 256
characters).
3. Optional: Enter a Description for the new rung.
See Adding Descriptions to Processes and Rungs on page 358.
4. To append or insert the new rung, click OK.
Result: The new rung name appears in the process tree, and the rung is opened for editing in the
workspace. The short description (if any) appears next to the rung name in the workspace and in the process
tree. The Ladder menu appears in the menu bar.

4.8.2
Editing Rungs
Process rungs include elements that can be added manually from the element list, or automatically using
commands.
In general, there are two types of rung elements:
● Elements that define inputs
● Elements that define outputs
For a full description of the input and output elements, see Ladder Diagram Language on page 517. For more
on the element variables, see Defining Rung Element Parameters on page 355.
The variables attached to the elements are defined in the database tables. See Building a Database on page
328 and Editing Tables on page 334.
The process rung can contain unattached rungs or elements, which are not connected to the rung entry point.
Any unattached rungs and/or elements are saved in the application, but do not undergo compilation and are
not part of the application running in the RTU. Disconnected rungs, where no elements are connected to the
entry point, are marked with a red exclamation mark in the process tree.
When changing a process or rung in an application that is assigned to more than one site, the user may apply
the changes to all sites or to one site only.
When This site only is selected, the user is prompted to rename the modified application for that site. The
new application is assigned to the site and must be compiled and downloaded to that site.

346
 6802979C10-BA
Chapter 4: Application Programmer

If the changes are applied to all sites, the user must recompile the application for all sites and download it
everywhere.
To make changes to a specific site after applying the changes to all sites, the user must reopen the
application for that particular site.

4.8.2.1
Adding Elements to Rungs Manually
For a detailed description of the ladder elements, see Appendix B: Ladder Diagram Language on page 517.
Prerequisites: Open the preferred application in the Application Programmer, and navigate to the Process
tab (located in the Application bar).

Procedure:
1. To edit a rung, perform one of the following steps:
● If you want to edit an existing rung, double-click its name in the process tree.
● If you want to edit a new rung, see Creating Rungs on page 346.
The Ladder menu appears in the menu bar, and the chosen rung is opened in the workspace. If no
elements exist in the rung (for example, in a newly created rung), only the rung name and entry point
appear (as shown in the following figure).
Figure 240: Rung Without Elements

On the right side of the window, a resizable list of elements appears.

Figure 241: Rung Element List

347
6802979C10-BA
Chapter 4: Application Programmer

2. From the list of elements, drag and drop the preferred element (typically an input element) into the
workspace.
Result:
The chosen element appears in the workspace. When selected, an element is highlighted in green (see
figure). If needed, you can reposition elements by clicking and dragging them within the workspace. The
labels (the lavender-colored areas) in the element represent the input/output variables, indices, or constants
used in the logic. See Rung Element Parameters on page 353.
Hovering over the element with the mouse pointer reveals a tooltip with information (such as element type,
variable name and type, and I/O link wiring) relevant to that type of element.
Figure 242: Rung Element (Highlighted) in the Workspace

Postrequisites: As needed, repeat the foregoing task to add additional elements to the rung. After creating
all the required rungs, link them in a logical order and assign their parameters. See the following sections:
● Linking Elements in Rungs on page 350
● Defining Rung Element Parameters on page 355

4.8.2.2
Adding Elements to Rungs Automatically
Elements can be added to a rung automatically using the Add Input, Insert Input, and Add Output
commands. When these commands are used, the elements are connected automatically by the Application
Programmer.The commands are accessible from the Ladder menu, from the context menu (by right-clicking
a rung element), or by using the keyboard shortcuts. For more on shortcut commands, see Keyboard
Commands in Application Programming on page 392.

Procedure:
1. Perform one of the following steps:
● If you want to link a new element to an existing element, select the preferred element.
● If you want to link a new element to the rung entry point in an empty rung, continue to step 2.
NOTE: When an element is selected, it is highlighted in green.

2. From the menu bar, click Ladder and perform one of the following actions:
● If you want to add an input after the highlighted element (or rung entry point, if no element exists),
select Add Input...
● If you want to insert an input before the highlighted element, select Insert Input...
● If you want to add an output after the highlighted element, select Add Output...
3. In the Select Element dialog, select the preferred type of element to add or insert.

348
 6802979C10-BA
Chapter 4: Application Programmer

Hover your pointer over any element in the Select Element dialog to reveal a tooltip with a brief
description of that element.
Figure 243: Select Element Dialog – Input Tab

Figure 244: Select Element Dialog – Output Tab

4. To add or insert the selected element type, click OK.

Result:
The new element is inserted in a logical place in the rung, linked to the rung entry point or to the selected
element/link. If you want to move an element within the workspace, click and drag it to the preferred position.
Hovering over the element with the mouse pointer reveals a tooltip with information (such as element type,
variable name and type, and I/O link wiring) relevant to that type of element.
Postrequisites:
Define the element parameters as described in Defining Rung Element Parameters on page 355.
Elements that are added automatically to the rung are also linked automatically. If, however, you want to
change an automatically created link, see Linking Elements in Rungs on page 350.

349
6802979C10-BA
Chapter 4: Application Programmer

4.8.2.3
Linking Elements in Rungs
Links are used to establish the relationship between elements. Once a link has been added, it can be moved,
redrawn, or deleted.When elements are created automatically (using the Add Input, Insert Input, and
Add Output commands), the appropriate links are also created automatically. Otherwise, the user manually
creates the links.

Creating a New Link

Procedure:
To create a link between two elements, perform one of the following steps:
● To manually link two elements, click and drag the black handle (located on the side of the element)
from the first element to the second element.
● To automatically link an element to the nearest target point, click the black handle.

Changing an Existing Link

Procedure:
If you want to change a link, perform the following actions:
a. Select the preferred link.
The black line is highlighted in green, and two green diamonds appear (one for each element).
Figure 245: Highlighted Link Between Two Elements

b. To reassign the link, click and hold the diamond next to the element that you want to disconnect, and
drag it to the new, preferred target point.
When dragging the diamond away from an element, the link remains connected to the other element.
Postrequisites: Normalizing a rung moves the rung elements and links. After moving/redrawing links,
normalize the rung to confirm that the placement of the elements reflects the rung logic.

Deleting a Link
Procedure:
Select the preferred link, and press the Delete key.

350
 6802979C10-BA
Chapter 4: Application Programmer

4.8.2.4
Normalizing Rungs
Elements and lines can be manually drawn anywhere in the window, which may lead to a disorganized
layout. When the Normalize Rung command is selected, the STS automatically rearranges the rung
elements to ensure an organized layout. In a rung with no elements, this command is disabled.The execution
order of elements in a rung is determined by the chronological order of the connections, and is displayed
clearly when normalizing the rung. When the rung is not normalized and some elements are not presented
in order of execution, these elements are marked with a yellow background. The Normalize Rung operation
correlates the display with the correct execution order and eliminates the yellow background.

Procedure:
To normalize the rung, select Ladder → Normalize Rung.

4.8.2.5
Creating Branches Manually
The user can create rung branches to include elements in parallel lines of inputs (“OR” function), or to include
multiple output elements in a single rung. Theses branches can be manually added from the element list.

Procedure:
1. From the list of elements, drag the desired branch element into the workspace.
For more details, see Adding Elements to Rungs Manually on page 347.
2. Click the black handle on the left side of the new element and drag it towards the desired position on
the existing rung link.
For more details on links, see Linking Elements in Rungs on page 350.
Postrequisites: To close the branch, see Closing Branches on page 352.

4.8.2.6
Creating Branches Automatically
The user can create rung branches to include elements in parallel lines of inputs (“OR” function), or to include
multiple output elements in a single rung. Branches can be created automatically using the Branch Input and
Branch Output commands.The Branch Input and Branch Output commands can be executed from the
Ladder menu, the context menu, or by using the keyboard shortcut commands. For more details on shortcut
commands, see Keyboard Commands in Application Programming on page 392.

Procedure:
1. Select the element from which the branch should descend.
When selected, an element is highlighted in green.
2. From the Ladder menu, perform one of the following actions:
● To add a parallel input, click Branch Input...
● To add an additional output, click Branch Output...
3. In the Select Element dialog that appears, choose the preferred element. To add it to the rung, click
OK.

351
6802979C10-BA
Chapter 4: Application Programmer

Figure 246: Select Element Dialog – Input

The new branch element appears in the workspace, linked to the original rung. If needed, you can
reposition the element by clicking and dragging it within the workspace. After moving any branch
elements, normalize the rung to confirm that the placement of the elements reflects the rung logic.
See Normalizing Rungs on page 351.

Postrequisites: To close the branch, see Closing Branches on page 352.

4.8.2.7
Closing Branches
Procedure:
To close a branch to a rung element, click the input rung element to which you are closing and select
Ladder → Close Branch.
The line closing the branch is displayed in the rung.

4.8.2.8
Selecting Elements in Rungs
Procedure:
● To select all the elements in the current rung, click Edit → Select All.
● To select multiple elements in the current rung using the mouse, perform the following actions:
a. Click the first preferred element.
b. While holding the Shift key, click to select one or more additional elements.
● To select multiple elements in the current rung using the keyboard, perform the following actions:
a. Click the first preferred element.
b. While holding the Shift key, use the arrow keys to select one or more additional elements.

352
 6802979C10-BA
Chapter 4: Application Programmer

4.8.2.9
Copying (or Cutting) and Pasting Elements in Rungs
Procedure:
1. Right-click the preferred element and select Copy or Cut.
2. In the workspace, right-click the location where you want to paste the element and select Paste.

4.8.2.10
Duplicating Elements in Rungs
Procedure:
While holding the Ctrl key, click and drag the preferred element to the position in the workspace where
you want to duplicate it.

4.8.2.11
Deleting Elements in Rungs
Procedure:
1. Select one or more elements.
See Selecting Elements in Rungs on page 352.
2. To delete the selected rungs, click Edit → Delete.

4.8.2.12
Adding Comments to the Rung Workspace
The STS user can multiple comment boxes to a rung in the Application Programmer. These comment boxes
are displayed in the workspace of an open rung and can be repositioned, if needed.
To add a description that is visible within the process tree, see Adding Descriptions to Processes and Rungs
on page 358.

Procedure:
1. To add a comment to the workspace of an open rung, perform the following actions:
a. In the workspace, double-click the location where you want to add a comment.
Alternatively, you can drag the comment icon from the rung element list (on the right side of the
screen) to the preferred location in the workspace.
b. In the text box that appears, enter the preferred text.
c. To save the comment, click outside of the text box.
2. Optional: If you want to delete a comment, select it and press the Delete key.

4.8.3
Rung Element Parameters
A rung element can have up to three parameters, which represent the input/output variables, indices, or
constants used in the logic.
For instructions on defining element parameters, see Defining Rung Element Parameters on page 355.
Most of the variables used as element parameters are predefined in the database tables.

353
6802979C10-BA
Chapter 4: Application Programmer

The Automatic constants feature included with the Application Programmer enables the user to enter
numeric constants that are not defined in the database as element parameters (or in CALC expressions).
In this case, the user enters a constant (integer, real/float, or long) in an element parameter (or
CALC expression). This number (for example, 2) is automatically added to a special constant table
of the appropriate type (such as #AutoInt1#, #AutoReal1#, or #AutoLong1#) created by the Application
Programmer.
If the Automatic constants feature is disabled (via Application → Settings...), an error message is
displayed when you enter an undefined constant.
Constants are converted to their standard form. For example, 00034.000 is converted to 34; and 1E2 is
converted to 100.
In certain cases, a numeric constant is not allowed in a given rung element, or in a particular parameter within
an element. For example, constants are not allowed as the first parameter in arithmetic operations. If the
numeric constant entered is not allowed, an error message is displayed.
When an automatic constant table reaches the last index (249), a new table of the same type is created (for
example, #AutoInt2#). Automatically generated constant tables can be renamed, if preferred.
All rung element parameters that are constants are displayed in dark red, except in CALC expressions.
Note that when a parameter is being edited, certain commands are disabled. Pressing the Esc key cancels
parameter editing and re-enables those commands.

4.8.3.1
Rung Element Parameter Examples
A rung element can have one to three parameters, depending on the element type. Some elements have
different parameter types, so the dialog listing the parameters may vary.
An Input element can have one or two parameters (for example, Input 1 and Input 2):
Figure 247: Greater Than Comparator Input Element with Two Parameters

An Output can have up to three parameters (for example, Input 1, Input 2, and Output):
Figure 248: SUB Operation Output Element with Three Parameters

The CALL operator enables the user to select a system function from a choice list, and to optionally pass a
parameter to it:
Figure 249: CALL Operator

For detailed information about the CALL operator functions, see the following sections:
● User Defined Local Ports on page 597
● User Defined MDLC Communication on page 612 (in particular, Communication Functions Available via
the CALL Function on page 614)
The UCL operator enables the user to select a user-defined C function from a choice list, and to optionally
pass parameters to it:

354
 6802979C10-BA
Chapter 4: Application Programmer

Figure 250: UCL Operator

For detailed information about the UCL operator functions, see the ACE3600 RTU ‘C’ Toolkit User Guide.
The CALC operator enables the user to enter a formula that contains operations and variables, and to store
the result.
Figure 251: CALC Operator

For more information, see CALC on page 545.

The SEND operator enables the user to record text combined with variables, which can be sent through user
ports.
Figure 252: SEND Operator

The relevant user port is selected from a drop-down list. For more information, see User Defined Local Ports
on page 597.

4.8.3.2
Defining Rung Element Parameters
Undefined parameters appear as lavender areas (labels) above, below, or beside the element.
Figure 253: Rung Elements with Undefined Parameters

Use the Tab key to jump from parameter to parameter within a given element.

Procedure:
1. To define an element parameter, click the relevant label in the preferred element.
The label is replaced by a text field with a drop-down arrow, as shown in the following figure.

355
6802979C10-BA
Chapter 4: Application Programmer

Figure 254: Assigning a Database Symbol to an Element

2. Perform one of the following steps.

If… Then…
If you want to input perform the following actions:
a database symbol, a. Click the drop-down arrow.
b. In the Quick Find Symbol dialog, select the preferred symbol. See
Finding Symbols/Variables in Applications on page 371.
c. To input the symbol and close the Quick Find Symbol dialog, click
OK.
d. To apply the chosen parameter, press Enter.

If you want to man- input the symbol name in the text field and press Enter.
ually define the pa-
rameter,

When manually defining the parameter, the Use Automatic Constants prompt appears if an
undefined numeric constant is entered. To allow the Application Programmer to automatically add
the numeric constant to the database, click Yes (the specified numeric constant can be subsequently
used in other rungs in the process). Otherwise, click No and enter another value.
NOTE:
The Automatic constants feature defines numeric constants in the database in an orderly
manner. Modifying the names and values of these constants is possible, but not recommended.
If you do not want the Use Automatic Constants prompt to be displayed again, check the
Don’t ask me again option. If you select this option and then click No, the Automatic
constants feature is disabled.
Figure 255: Rung Element with Assigned Database Symbol

356
 6802979C10-BA
Chapter 4: Application Programmer

3. CALC elements only: To enter the mathematical expression for a CALC element, perform the
following actions:
a. Click the lower parameter of the chosen CALC element.
b. To open the Formula text box, click the drop-down arrow.
c. Enter the preferred mathematical expression (for example, x+2).
d. To close the Formula text box, click OK.
e. To apply the chosen parameter, press Enter.
Result: If the entered/selected symbol is valid, the symbol appears as a label instead of the lavender area. If
the symbol is undefined or invalid for the element type, an error message appears.

4.8.3.3
Looking Up Element Parameters in the Database
Procedure:
To look up an element parameter in the database, right-click the preferred parameter name and select
Look up symbol.
Figure 256: Looking Up an Element Parameter

Result: The database table containing the chosen parameter is opened.

4.8.4
Deleting Processes and Rungs
Procedure:
1. In the Process tab, click the name of the preferred process or rung.
2. From the menu bar, select Edit → Delete.
3. To delete the chosen process or rung, click OK.

4.8.5
Renaming Processes and Rungs
Procedure:
1. In the Process tab, right-click the name of the preferred process or rung, and select Rename.
2. Enter the new name and press Enter.

357
6802979C10-BA
Chapter 4: Application Programmer

4.8.6
Copying (or Cutting) and Pasting Rungs
Procedure:
1. In the Process tab, right-click the name of the preferred process or rung and select one of the
following:
● Cut
● Copy
2. In the location where you want to paste the copied process or rung, perform the following actions:
a. Right-click the name of the existing process or rung that you want to precede the copied process
or rung.
b. Select Paste After.
NOTE: If the pasted rung contains symbols that are not defined in the current application, an
error is displayed when the application is saved. The undefined symbols are listed in the
Analyze Information tab.

4.8.7
Adding Descriptions to Processes and Rungs
The STS enables you to document the process with text descriptions.
If a brief description is adequate, use the Short Description command. Otherwise, use the Long
Description command to enter a detailed description of the process or rung.
To add a comment that is visible within the open workspace of a rung, see Adding Comments to the Rung
Workspace on page 353.

Procedure:
1. Right-click the name of the preferred process or rung and perform one of the following actions:
● To add or edit a long description, select Long Description.
● To add or edit a short description, select Short Description.
2. In the relevant dialog (see the following figures), enter the description text.
Standard text-editing commands (such as copy, cut, paste, and undo) can be used during editing.
Figure 257: Long Description Dialog

358
 6802979C10-BA
Chapter 4: Application Programmer

Figure 258: Short Description Dialog

3. To save the description and close the dialog, click OK.

Clicking Cancel discards the changes.
Result: The short description (if any) appears in the process tree, next to the name of the chosen rung. The
long description (if entered) appears in a tooltip when you hover the mouse pointer over the name of the
chosen rung in the process tree.

4.8.8
Printing Processes and Rungs
Procedure:
In the process tree, perform one of the following steps:

If… Then…
If you want to open the standard right-click the name of the preferred process or rung and select
Windows Print dialog, Print...
If you want to view a print preview perform the following actions:
before printing,
a. Right-click the name of the preferred process or rung and
select Print Preview.
b. To open the standard Windows Print dialog, click the Print
icon in the top-left corner of the Print preview dialog.

NOTE: The Print... and Print Preview commands are also accessible from the Ladder menu when
a rung is open. If multiple rungs are open in the Application Programmer, navigate to the window of
the preferred rung before accessing these commands from the Ladder menu.

4.8.9
Searching Rungs
The STS Application Programmer includes a search mechanism that allows you to quickly find rungs, or to
search the rung sequences for variables or symbols.

Searching with The Find Dialog

Procedure:
1. To open the Find dialog, select Edit → Find...

359
6802979C10-BA
Chapter 4: Application Programmer

Figure 259: Application Programmer – Find Dialog

2. Perform one of the following steps.

If… Then…
If you want to manually input enter the preferred string in the Find what field.
the search symbol,
If you want to select the perform the following actions:
search symbol from a list of all a. Click Browse...
symbols in the database,
b. In the Choose Symbol dialog, select the preferred symbol.
c. To input the symbol and close the Choose Symbol dialog,
click OK.
For more details on selecting a symbol from the database, see
Finding Symbols/Variables in Applications on page 371.

3. Perform one of the following steps.

If… Then…
If you want to search the contents of the rung perform the following actions:
sequences, a. Select Search in Rungs.
b. To limit the scope of the search, configure
the Find Input and Find Output options
(as preferred).

If you want to find a rung, select Find Rung.

4. Click Find.
Result:
Search in Rungs: The results appear in the Search tab in the Output bar at the bottom of the screen. The
number of elements found is reported in the status bar at the bottom of the window. If the variable or symbol
occurs in one rung, the rung is displayed. If the item appears in more than one rung, click the rung name in
the Search tab to open it. After opening the rung with the variable or symbol, you can look it up as described
in Looking Up Element Parameters in the Database on page 357.
Find Rung: If the rung is found, it is displayed.

360
 6802979C10-BA
Chapter 4: Application Programmer

Searching Quickly from an Open Database

When viewing a database table, the STS user can quickly find a variable or symbol in the rung via a context
menu command.

Procedure:
To find a variable or symbol that appears in an open database table, right-click it and select Find in
Rungs.
Figure 260: Context Menu with Find in Rungs Command

Result: The results appear in the Search tab in the Output bar at the bottom of the screen, and the number
of elements found appears in the status bar at the bottom of the window. If the variable or symbol occurs in
one rung, the rung is displayed. If the item appears in more than one rung, click the rung name in the Search
panel to open it.

4.8.10
Rung Monitoring
The Monitor command enables the user to monitor the rung. See Monitoring Rungs (ACE3600 Only) on
page 380.

4.8.11
Examples of Building Rung Sequences
The following is a demonstration of how to build rung sequences. These examples are based on the variables
from the Database Builder examples earlier in this chapter.
See Database Building Examples on page 342.

Example 1
Pump (PUMP1) should be actuated under the following conditions:
● 10 seconds after valve VLV1 or VLV2 turns on.

361
6802979C10-BA
Chapter 4: Application Programmer

● The emergency switch (EMRG) is off.

● The water temperature is below 80 degrees.
First Rung
Valves VLV1 (Open Branch Input) or VLV2 (Close Branch Input) are configured as N.O. contact inputs.
The output operator is an On Delay Timer (DON), designated as T1.
Second Rung:
T1 is used as an N.O. input, EMRG as an N.C. contact input, and the analog input AN1 depends on a
comparator (if less than 3,200). The numeric value of the TEMP parameter is 3,200. 3,200 is the value
of a parameter data type, predefined in the database. The output operator is Relay ON, designated as
PUMP1.
Figure 261: Example 1 Rung Sequences

Example 2 – Index Series

A series of 10 inputs (from IN,0 to IN,9) can execute a series of 10 outputs. The loop is executed 10 times in
the course of one scan.
Rung1: Reset index I.
Rung2: If input IN,I is on, perform a Relay On operation on OUT, I.
Index I counts up.
If I < 10 (the value of V10 in the database is 10), jump to rung2. Therefore, the process is repeated for IN,1 –
OUT,1; IN,2 – OUT,2... up to IN,9 – OUT9.
Figure 262: Example 2 Rung Sequences

362
 6802979C10-BA
Chapter 4: Application Programmer

4.9
I/Os and Database Linking (ACE3600/MC-EDGE
Only)
In order for the application to control the I/Os in the site, a link must be created between the variables
(defined in the database) and the physical I/Os (defined in the site configuration).
Before defining the links between the database variables and the physical I/Os, the application must be
assigned to that site. See Managing Applications on page 166.
NOTE:
Linking of variables and I/Os is performed via STS mode of the Application Programmer only. I/O linking
is not possible in standalone mode.
If the application is opened for <no specific site>, no I/Os can be linked to the database.
Any change in the RTU I/O configuration affects the application. Therefore, if you change the I/O
configuration, do not forget to update the I/O link definition. For further details on the I/O configuration of
a site, see Defining I/Os in Sites on page 136.
If you change the I/O link information in an application that is assigned to more than one site, the change is
only made in the current site.
Changes to the database tables may also create incompatibilities that affect the I/O links.

4.9.1
I/O Link Tree
The I/O link tree displays the columns in database tables that contain I/O values. The I/O link tree enables the
STS user to access the I/O link definition table for the purpose of linking physical I/Os.
The I/O link tree is located in the application bar, under the I/O Link tab. The I/O Link tree is generated on
the basis of the application database. Only those database tables that contain I/Os are displayed as entries
in the tree. If a multiple-column table has more than one linkable column, each individual column has its own
entry in the tree (located under the entry of the parent table). The I/O link tree can be expanded or collapsed
as needed.
Figure 263: I/O Link Tree

The STS user uses the I/O link tree to access the I/O link definition table, which is used for linking database
variables to the physical I/Os in a site. For more details, see I/O Link Definition Table on page 364 and
Linking I/Os to the Database on page 366.

363
6802979C10-BA
Chapter 4: Application Programmer

4.9.2
I/O Link Definition Table
The I/O link definition table enables the STS user to link the I/O variables in database tables to the physical
I/Os in a site. The I/O link definition table is accessed via the I/O link tree, by double-clicking a single-column
table or an individual column of a multiple-column table.
Each row in the I/O link definition table corresponds to a row representing a variable in the selected database
table. Each column in the I/O link definition table contains a parameter for configuring the I/O link. For
parameter descriptions, see I/O Link Definition Table Parameters on page 365. The user can configure the
parameters in each individual row. See Linking I/Os to the Database on page 366. Alternatively, contiguous
lists of variables can be configured in groups. See Connecting I/O Groups on page 368.
Figure 264: I/O Link Column Definition Table

The Table & Column Properties section (in the bottom half of the window) includes identifying information.
The Table Name field reports the name of the selected database table. If the selected database table is
defined as a multiple-column table, the name of the chosen column appears in the Column Name field. For
single-column tables, the Column Name field always displays the generic term Name. The Column Type
field displays the data type of the chosen column.
A data type may have several link options according to the I/O module defined in the site configuration. For
example, when linking a Discrete Input (d-i) variable to a Mixed I/O module (including 16DI + 4AI + 4DO),
the following options appear under I/O Link Column Definition:
● IN_1–IN_16
● BI_1–BI_4
● PS_IN_1
● PS_OUT
● PS_EXIST_X
● PS_BI_X
● MOD_SLEEP
● MOD_FAIL
For a complete list of I/O link definitions (with descriptions), see I/O Link Definitions on page 370.

364
 6802979C10-BA
Chapter 4: Application Programmer

4.9.2.1
I/O Link Definition Table Parameters
Table 59: I/O Link Definition Table Parameters

Column Name Description

Name (single-column tables only) Displays the symbol name of the variable in a particular row of a
single-column table. This name is entered in the database table
and cannot be modified in the I/O link column definition table.
Frame (ACE3600 only) Maps the link between the database I/Os and the physical I/Os
according to the respective frame and module.
Module

I/O Link Column Definition Defines the I/O link. For a list of available definitions, see I/O Link
Definitions on page 370.
COS Delta The delta since the last reported reading that causes the COS
(Change of State) flag to be set for the input.
KLV/PDV (ACE3600 only) Defines the value to be used by the application in the event that
communication with the I/O module is interrupted (for example,
when the I/O module is frozen during a hardware test). Configura-
ble options include:
● Keep Last (keeps the last value)
● Predefined (uses the value in the Predefined Value column)

Predefined Value (ACE3600 only) The predefined value to be used by the application when KLV/PDV
is set to Predefined.
Mask I/O Scan (ACE3600 only) When enabled, forces a value that masks the actual input value.
In this case, the application gets the KLV/PDV value instead of the
actual input value.

4.9.3
Selecting Sites in the Application Programmer
An application may be assigned to more than one site in the project. Such an application may be opened for
no specific site, or for one of the assigned sites. Opening for a specific site configuration allows the user to
define the link between the variables and the physical I/Os of that particular site.
When opening an application that is assigned to more than one site, the user is immediately prompted by the
Application Programmer to select a site (or <no specific site>). After opening the application, the user can
select a different site via the Select Site dialog.
Prerequisites:
1. Before selecting a new site, save any changes made to the application for the current site.
2. Ensure that the application is already assigned to the new site. See Managing Applications on page 166.

Procedure:
1. To open the Select Site dialog, click Application → Select Site...

365
6802979C10-BA
Chapter 4: Application Programmer

Figure 265: Application Programmer – Select Site Dialog

2. Select the preferred site and click OK.

NOTE: I/Os cannot be linked when <no specific site> is selected.

The application is opened for the selected site. The name of the selected site appears at the top of the
Application Programmer window, and in the Application Info tab in the Output bar (at the bottom of
the screen).

4.9.4
Linking I/Os to the Database
The I/O link function enables the user to link the physical I/Os to the I/O variables in single-column and
multiple-column database tables.
Prerequisites: In the Application Programmer, open the application for the preferred site, and navigate to the
I/O Link tab. If the tree is collapsed, expand it to view its elements.

Procedure:
1. In the I/O link tree, double-click the preferred tree entry.
The entry may be a single-column table, or an individual column belonging to a multiple-column table.
The chosen table or column is displayed in the I/O link definition table. The parameters included in this
table may vary, depending on the data type of the chosen database table or column. For descriptions
of the parameters, see I/O Link Definition Table Parameters on page 365.

2. In the Frame and Module columns, use the drop-down lists to map the I/O location for the physical
I/O.
In the Frame column, 0 represents the main frame. If no options appear in the drop-down lists, make
sure that at least one I/O module has been defined in the chosen site configuration.
NOTE: To view the I/Os available in the RTU, click the I/O Information tab in the Output bar at
the bottom of the screen. The defined I/O configuration is displayed.
Figure 266: I/O Information Tab in the Output Bar

3. In the I/O Link Column Definition column, use the drop-down list to select the preferred I/O definition
(from the database).

366
 6802979C10-BA
Chapter 4: Application Programmer

For a complete listing of the I/O definitions (with descriptions), see I/O Link Definitions on page 370.
4. For inputs defined as Value Input (v-i) or Scaled Analog Input (sAI) only: In the COS Delta column,
enter the preferred value
where the value entered equals the delta since the last reported reading that triggers the change of
state (COS) flag to be set for the input.
Figure 267: Setting the COS Delta Value

NOTE: You can also use the services provided by the ‘C’ Toolkit to set and reset the COS flag in
an application.
5. To specify how the application should handle the I/O in case of loss of communication with the I/O
module, perform one of the following steps.

If… Then…
If you want to keep the last in the KLV/PDV column, select Keep Last.
value,
If you want to use a prede- perform the following actions:
fined value, a. In the KLV/PDV column, select Predefined.
b. In the Predefined Value column, enter the preferred value
(either 0 or 1).

6. Optional: To mask the input/output, select the Mask I/O Scan entry.
When enabled, only a certain value (KLV or PDV) is shown, regardless of the actual I/O value. This
enables handling of the input/output connection or sensor without necessarily making changes in the
application program.
7. Optional: To erase an I/O link definition, perform the following actions:
a. In the row with the preferred I/O link definition, select the cell in the I/O Link Column Definition
column.
b. Select Edit → Delete.
Result: When the I/O link is complete, the table or column is marked in the I/O link tree with a green check
mark.
NOTE: After linking the physical I/Os, changing the I/O configuration in a site can impact the I/O links in
its assigned application.

367
6802979C10-BA
Chapter 4: Application Programmer

4.9.5
Connecting I/O Groups
A number of contiguous variables can be automatically linked to physical I/Os in the same module.
Connection of I/O groups is performed via the Connect Group of Elements dialog, which is accessible from
the menu bar by selecting I/O Link → Connect I/O Items... The Connect I/O Items... command is active
when an existing, defined I/O link is selected in the I/O link definition table.
Figure 268: Connect Group of Elements Dialog

The number of Remaining rows to fill depends on the placement of the cursor when the Connect I/O
Items... command is selected. When the first row (index 0) is selected in the I/O link definition table, the
Remaining rows to fill is equal to the Last Index of the database table.
The lower half of the dialog (Choose items to connect) lists the items that await connection.
Prerequisites:
1. In the Application Programmer, open the application for the preferred site, and navigate to the I/O Link
tab. If the tree is collapsed, expand it to view its elements.
2. Open the preferred table or table column by double-clicking its name in the I/O link tree.

Procedure:
1. In the I/O link definition table, click a cell in the preferred row (that is already defined).
For defining individual I/O links, see Linking I/Os to the Database on page 366.
2. From the menu bar, select I/O Link → Connect I/O Items...
If the Connect I/O Items... command is disabled, ensure that a row is defined and currently selected.
3. In the Connect Group of Elements dialog, select the items to connect to the variables.
To select contiguous items, press and hold the Shift key while selecting.
To select noncontiguous items, press and hold the Ctrl key while selecting.

368
 6802979C10-BA
Chapter 4: Application Programmer

4. To add the selected elements, click OK.

The Frame and Module from the first entry are copied to the other entries. The selected elements
appear in the I/O Link Column Definition column. The KLV/PDV setting is also copied to the other
entries.
NOTE: If the rows immediately following the row selected in step 1 already contain definitions,
the existing definitions are overwritten. If the number of items selected in the Connect Group of
Elements dialog is greater than the number of Remaining rows to fill, only the remaining rows
are filled. In this case, the remaining elements are not assigned.

5. For each entry in the group, define the remaining parameters (KLV/PDV, Predefined Value, Mask I/O
Scan for inputs, and COS Delta for value/analog inputs).
6. Optional: To erase the I/O link definition for a group of I/Os, select the group and press the Delete
key.
To select contiguous items, press and hold the Shift key while selecting.
To select noncontiguous items, press and hold the Ctrl key while selecting.

4.9.6
Distributing I/O Link Information
The STS user can copy I/O link information from the current site to other sites. This feature is especially
useful when a single application is assigned to multiple sites with the same I/O configuration.
Prerequisites:
Open the preferred application in the Application Programmer and ensure that:
1. All relevant sites are configured.
2. The application is assigned to all the sites.
3. The I/O link information in the application is saved.

Procedure:
1. From the menu bar, select Application → Distribute I/O Link...
2. In the Select Sites dialog, select one or more preferred sites.

3. To copy the I/O link information to the selected site or sites, click OK.

369
6802979C10-BA
Chapter 4: Application Programmer

4.9.7
I/O Link Definitions
ACE3600

Table 60: ACE 3600 I/O Definitions

I/O Definition Description

AN_IN_1 – AN_IN_16 Analog inputs to the RTU and internal analog reference value (previ-
ously defined in the database as value input data type, or scaled
AN_VREF
analog input data type).
IN_1 – IN_16 Discrete inputs to the RTU (previously defined in the database as
discrete input data type).
IN1_CNTR – IN12_CNTR The counters that count the number of pulses according to the re-
spective inputs (previously defined in the database as value input
data type).
OUT_1 – OUT_32 Control relay outputs of the RTU (previously defined in the database
as discrete output data type).
AN_OUT_1 – AN_OUT_4 (CUR- Analog outputs of the RTU (previously defined in the database as
RENT, VOLTAGE, or TEST) value output data type, or scaled analog output data type).
BI_1 – BI_16 Discrete inputs which are back indication for discrete outputs (dis-
crete input variables linked to a physical discrete output)
PS_IN_1 The expected status (1=ON, 0=OFF) of the removable power supply
in the I/O module (previously defined in the database as discrete
input).
PS_OUT Controls (1=ON, 0=OFF) the removable power supply in the I/O
module (previously defined in the database as discrete output data
type).
PS_EXIST_X The flag (1=Exist, 0=Missing) which indicates whether the remova-
ble power supply in the I/O module exists (previously defined in the
database as discrete input).
PS_BI_X The actual status (1=ON, 0=OFF) of the actual back indication of the
removable power supply in the I/O module (previously defined in the
database as discrete input).
MOD_SLEEP The module sleep mode status (1=Sleeping, 0=Wakeup) (previously
defined in the database as discrete input/outputinput reads sleep
mode, output sets sleep mode).
MOD_FAIL The module fail status (previously defined in the database as dis-
crete input).

MC-EDGE

Table 61: MC EDGE I/O Definitions

I/O Definition Description

DI_1 – DI_N Discrete inputs to the RTU (previously defined in the database as
discrete input data type)

370
 6802979C10-BA
Chapter 4: Application Programmer

I/O Definition Description

CNTR_DI_1 – CNTR_DI_N The counters that count the number of pulses according to the
respective inputs (previously defined in the database as value input
data type).
DO_1 – DO_N Control relay outputs of the RTU (previously defined in the database
as discrete output data type).
BI_1 – BI_N Discrete inputs which are back indication for discrete outputs(previ-
ously defined in the database as discrete input data type)
AI_1 – AI_N Analog Input of the RTU. (previously defined in the database as
value input data type).
AO_1 – AO_N Analog outputs of the RTU. (previously defined in the database as
value outputdata type).
NOTE: The AO type is done via site configuration in ad-
vanced module section.

4.10
Finding Symbols/Variables in Applications
The Application Programmer includes a Quick Find Symbol tool for quickly looking up and accessing
symbols (such as variables or rung names) in the application.
The Quick Find Symbol dialog is also accessible when:
● Searching tables and rungs, by clicking the Browse button in the Find dialog. See:
○ Searching for Variables or Duplicated Columns on page 339
○ Searching Rungs on page 359
● Editing parameters in rung elements, by selecting the drop-down button. See Defining Rung Element
Parameters on page 355.

Procedure:
1. To open the Quick Find Symbol dialog, select Edit → Find Symbol.
Figure 269: Quick Find Symbol Dialog

371
6802979C10-BA
Chapter 4: Application Programmer

The dialog is divided into two panes:

● The Groups pane lists the categories (such as basic variable types, or process names).
● The Database Names pane lists all the symbols in the selected category.
2. To filter the items listed in the Database Names pane, perform one of the following actions in the
Groups pane:
● If you want to view the symbols in a category, select the preferred category name.
● If you want to view all symbols in the database, select All.
3. In the Database Names pane, select the preferred symbol.
4. To open the chosen symbol, click OK.
The chosen symbol is opened or displayed in the Application Programmer:
● If the chosen symbol is the name of a process, the process is highlighted in the process tree.
● If the chosen symbol is the name of a process rung, the rung workspace is opened.
● If the chosen symbol is the name of a variable, the database table containing that variable is
opened. The chosen symbol is highlighted in the table.
NOTE:
If the Quick Find Symbol dialog is accessed via the Find dialog, clicking OK inserts the name
of the chosen symbol into the Find what field.
If the Quick Find Symbol dialog is accessed during definition of a rung element parameter,
clicking OK inputs the chosen symbol into the element parameter field.

4.11
Saving Applications in STS Mode
Procedure:
To save the application, perform one of the following steps.

If… Then…
If the application is assigned to select File → Save Application.
one site only,
If the application is assigned to perform the following actions:
multiple sites and you want to
a. Select File → Save Application.
save the changes to all sites,
b. In the dialog that appears, select All # Sites (where # is the
number of currently attached sites).

372
 6802979C10-BA
Chapter 4: Application Programmer

If… Then…
If the application is assigned perform the following actions:
to multiple sites and you want a. Select File → Save Application.
to save the changes to the cur-
rently selected site only, b. Select This site only.
c. In the Save As dialog, enter the preferred Name of the new
application file.
A new application file with the chosen name is created and as-
signed to the current site. The original application file (with the
original file name and without the changes) remains assigned to all
other sites.

NOTE: If symbols from pasted rungs are not defined in the current application, an error is displayed
when the application is saved. The undefined symbols are listed in the Analyze Information tab.

4.12
Saving Applications in Standalone Mode
Saving Applications
Applications can be saved with no change to the existing name. To save an application under a different
name ("Save as..."), see Saving Applications Under a Different Name on page 373.

Procedure:
To save the application, select File → Save Application.
NOTE: If symbols from pasted rungs are not defined in the current application, an error is displayed
when the application is saved. The undefined symbols are listed in the Analyze Information tab.

Saving Applications Under a Different Name

Procedure:
1. From the menu bar, select File → Save Application As...
2. In the Save As dialog, enter the preferred Name.
3. Optional: In the Location field, specify the preferred file path.
The default target location is in the STS installation directory under \Projects\<project
name>\System
where <project name> is the name assigned by the user when creating the STS project. See Creating
Projects in STS on page 97.
4. To save the application with the chosen name, click OK.

4.13
Compiling Applications (ACE3600 Only)
After programming the application, the user compiles it to create an object file that can be downloaded to the
appropriate RTU.
The Application Programmer in standalone mode does not support compiling; use STS mode.

373
6802979C10-BA
Chapter 4: Application Programmer

To compile the application for a specific site configuration, that site must be selected. See Selecting Sites
in the Application Programmer on page 365. Compilation for a specific site fails when <no specific site> is
selected. To compile the application for all sites, any site (or no specific site) may be selected.
When compiling the application for all sites, the Application Programmer optimizes the process. After
compiling the application once, it simply copies the output to the other sites with the same I/O Link data.
This reduces the required compile time considerably.
Prerequisites: Open the preferred application in the Application Programmer (STS mode). If compiling the
application for a specific site, ensure that the preferred site is selected.

Procedure:
1. From the menu bar, select Application → Settings...
2. In the Application Settings dialog, under Compiler Options, perform one of the following steps:
● To use explicit scanning, deselect AutoScan (default).
● To use automatic scanning, select AutoScan.
For a comparison of the two scanning methods, see Explicit versus Automatic Scanning on page 375.
Figure 270: Application Settings Dialog

For information on the other application settings, see the following sections:
● For Reset Load versus Load, see Downloading Applications in the Application Programmer on
page 375.
● For Automatic constants, see Rung Element Parameters on page 353.
3. Perform one of the following steps.
● To compile the application for the current site only, select Run-Time → Compile.
● To compile the application for all assigned sites, select Run-Time → Compile All Sites.
NOTE: When compiling the application for the current site only, you also have the option
toCompile & Download it to the selected site with one click. Before selecting this command,
see Downloading Applications in the Application Programmer on page 375 for important
information concerning the Load and Reset load options.
The compilation process begins (if any changes were made to the application, the application is
automatically saved before beginning the process). The Compile Information tab in the Output bar
(at the bottom of the screen) displays compiler status messages.

374
 6802979C10-BA
Chapter 4: Application Programmer

If errors are found during the compilation process, they are displayed, and the object file is not
created.
For Compile & Download only: If the compilation is successful, the downloading process begins.

4.13.1
Explicit versus Automatic Scanning
When compiling an application, the programmer chooses one of two of I/O scanning methods: explicit
(default) or automatic (also called AutoScan). Each method has its own advantages.

Explicit Scanning
In the application, the user explicitly calls the SCAN operator separately for each I/O-linked database table
column. The advantages of explicit scanning are that only the relevant I/O-linked database table columns are
scanned, and that the user decides when to operate the scan during the MAIN task flow. (This is the method
used with legacy MOSCAD applications.)

Automatic Scanning
Before compiling the ladder application, the user instructs the Main task to automatically scan in (at the
beginning of its run) and automatically scan out (before the end of its current iteration) ALL of the columns
in I/O-linked database tables. Thus all columns are scanned in or out (according to I/O type) in a single Main
task iteration. The advantages of automatic scanning are that the user needs to write fewer calls/rung steps
in the application, and that the compiled application volume is smaller.

4.14
Downloading Applications in the Application
Programmer
After the application is compiled, it needs to be downloaded to the site before it can be executed in the RTU.
The Application Programmer can download the application in STS mode (when a specific site is selected).
Alternatively, the compiled application can be downloaded via the STS (in system view or site view). For more
information, see Downloads to Sites on page 145.
When downloading applications to sites, the user chooses whether to restart the system. When Load is
selected, the application is loaded without restarting the system. This option is appropriate only if the RTU
has been programmed in the past and the following conditions are true:
1. You want to retain the current database values.
2. You made no changes in the database, to the constants, or in rungs that have differentiators or constants.
The Reset load option resets the system, and is appropriate when:
● Loading the RTU with an application for the first time
● The RTU has been programmed in the past, but the database of the downloaded application has been
modified

375
6802979C10-BA
Chapter 4: Application Programmer

● You want to reset the database

Prerequisites:
1. Open the application for the preferred site in the Application Programmer (STS mode).
2. If the application is for ACE3600, ensure that it is compiled for the chosen site. See Compiling
Applications (ACE3600 Only) on page 373.
NOTE: If you make any changes to the site configuration, update the I/O link definitions in the
application and recompile the application before downloading.

Procedure:
1. Select Application → Settings.
The Application Settings dialog appears.

2. Under Application Download, perform one of the following steps:

● If you want to download the application and restart the system, select Reset load.
● If you want to download the application without restarting the system, select Load.
NOTE: Use Reset load whenever a differentiator is added to a rung.

If you make changes to the database and select Load Only, a pop-up message informs you that this
option is not allowed because of the changes made to the database. In this case, you must use Reset
load. In the case of differentiators added to rungs, however, this pop-up message may not appear
in certain circumstances. To prevent any issues, always select Reset load when differentiators are
added to rungs.
3. To apply the settings and close the Application Settings, click OK.
For information on the other application settings, see the following sections:
● For AutoScan, see Explicit versus Automatic Scanning on page 375.
● For Automatic constants, see Rung Element Parameters on page 353.
4. Select Run-Time → Download Application.
The compiled application file (ending in .b) and the predefined I/O module values file (ending
in .ios) are downloaded to the unit. Download status messages, including any errors, are displayed
in the Download tab of the Output bar (at the bottom of the screen).

376
 6802979C10-BA
Chapter 4: Application Programmer

In the bottom-right corner of the window, two respective progress bars show the progress of the
current file download and of the download overall.

4.15
Application Monitoring
After an application is loaded in the RTU and becomes operational, the STS user can monitor the actual
values of the variables defined in the database table or rungs.
Real-time application monitoring is performed in the Application Programmer running in STS mode on a
local or remote computer. Application monitoring is especially useful when debugging the application.
During application monitoring, you can also freeze the communication between the application and the I/O
modules for simulation and system testing purposes. This allows you to change, update, or set conditions for
some of the database elements.

4.15.1
Monitoring Database Tables
Database monitoring allows the user to monitor the actual values for each database table, as reported by the
RTU during run-time operations.
For descriptions of the table monitor commands, see Table Monitor Commands on page 379.
NOTE: Users can monitor MC-EDGE system table 0 parameters, but cannot modify them.

Prerequisites: Open the application for the preferred site in the Application Programmer (STS mode).

Starting the Table Monitor

Procedure:
1. To connect the STS PC to the preferred RTU, perform one of the following steps in the connection bar
(near the top of the Application Programmer window):
● If the RTU is locally connected, select Local.
● If the RTU is remotely connected, input the Site ID and Link ID of the preferred site (with the
Local option not selected).
Figure 271: Application Programmer Connection Bar

2. In the application bar on the right side of the window, navigate to the Database tab.
3. To monitor a database, perform one of the following steps.

If… Then…
If you want to perform the following actions:
monitor a table in a. In the database tree, right-click the name of the preferred table.
its entirety,
b. Select Monitor.

377
6802979C10-BA
Chapter 4: Application Programmer

If… Then…
If you want to perform the followings actions:
monitor a portion a. In the database tree, double-click the name of the preferred table to
of a table,
open it.
b. In the table editor, select one or more cells that you want to monitor.
c. From the menu bar, select Table → Monitor.
NOTE: To add one or more cells to the monitored block, right-click
the preferred cell or cells and select Add Section. To remove cells
from the block, right-click the preferred cell or cells and select Ex-
clude Section.

The table is displayed in monitor mode. If the table is open for editing, the Monitor command switches
the table from edit mode to monitor mode (as shown in the following figures).
Figure 272: Database Table in Edit Mode

Figure 273: Database Table in Monitor Mode

In monitor mode, the database table includes a Monitor panel with commands not available in edit
mode. The cells of the table become yellow when the monitor is activated. During communication, the
Refresh Continuously button is replaced by the Abort button. Output messages are shown in the
Monitor tab of the Output bar at the bottom of the screen.
If a CRC discrepancy between the application in the RTU and in the PC is detected, the following
message appears: Project is not compatible with unit application. Continue
monitoring Table <<name>>? If you click Yes, the monitor retrieves partial information. For
example, assume that the application in an RTU includes a table with 40 lines, and the same table
on the PC includes only 20 lines. In this case, the process retrieves the 20 lines, and displays 0 in all
other lines. You cannot write to a position in the database table that is nonexistent in the RTU. In all
subsequent windows, the STS displays: No communication/incompatible CRC

378
 6802979C10-BA
Chapter 4: Application Programmer

Using the Table Monitor

Procedure:
● To retrieve the values of the monitored cells from the RTU one time only, select Refresh Once.
● To periodically retrieve the values of the monitored cells from the RTU, perform the following actions:
a. In the Refresh Rate field, enter the preferred interval between scans (in seconds).
b. Select Refresh Continuously.
● To update the RTU in real time as changes are made to the current table, select Update Every
Change.
● To manually update the RTU with the changes made to the database (when Update Every Change is
disabled), select Update RTU.
● (ACE3600 Only): To freeze the inputs and stop updating the outputs, select Scan Off.
● (ACE3600 Only): To resume refreshing the inputs and updating the outputs, select Scan On.
NOTE: The Scan On command is active only when Scan Off is enabled.

● To change the display format of a monitored cell, perform the following actions:
a. Right-click the preferred cell and select Display Format.
b. Select the preferred format.
Figure 274: Selecting the Table Monitor Display Format

● To close the monitor, select Close Monitor.

4.15.1.1
Table Monitor Commands
Table 62: Summary of Table Monitor Commands

Table Monitor Description

Command
Refresh Once Retrieves the current values of the displayed table from the RTU one time only.
Refresh Contin- Continuously retrieves the values of the displayed table from the RTU. The Refresh
uously Rate (in seconds) is defined by the user.
Update RTU Updates the RTU with the latest changes to the database. See also Update Every
Change.
Abort Aborts the monitor operation. If monitoring is inactive, the Abort icon is deactivated.

379
6802979C10-BA
Chapter 4: Application Programmer

Table Monitor Description

Command
Refresh Rate When Refresh Continuously is enabled, defines the interval (in seconds) between
scans of the database in the RTU.
Update Every Determines whether each change to the currently displayed table is sent immediate-
Change ly to the RTU. If enabled, each change is immediately sent to the RTU (without the
need to manually update the RTU via the Update RTU command).
Display Format Configures the display of a table column (except for float) in a format other than
the default format of the corresponding data type. Possible formats include Integer,
Binary, Hexadecimal, Timer MM:SS, Timer SS:MS, and ASCII.
Scan Off Applies to I/O columns only. When enabled, the application does not update the
(ACE3600 Only) inputs from the external environment, and does not send outputs. The I/O columns
in the table turn red. The Scan Off icon changes to Scan On.
Scan On Applies to I/O columns only and cancels the Scan Off state. When selected, the
(ACE3600 Only) application resumes updating the inputs from the external environment and sending
outputs.

4.15.2
Monitoring Rungs (ACE3600 Only)
Process monitoring allows you to monitor the actual values of each predefined rung, as received from
the RTU during online operations. This is useful when debugging the process. Up to 700 symbols can be
monitored in one rung.For descriptions of the rung monitor commands, see Rung Monitor Commands on
page 382.

Starting the Rung Monitor

Prerequisites: Open the application for the preferred site in the Application Programmer (STS mode).

Procedure:
1. To connect the STS PC to the preferred RTU, perform one of the following steps in the connection bar
(near the top of the Application Programmer window):
● If the RTU is locally connected, select Local.
● If the RTU is remotely connected, input the Site ID and Link ID of the preferred site (with the
Local option not selected).
Figure 275: Application Programmer Connection Bar

2. In the application bar on the right side of the window, navigate to the Process tab.
3. In the process tree, right-click the name of the preferred rung and select Monitor.
If this is the first communication session of the MDLC driver, enter the MDLC password when
prompted.
Result: The rung monitor operation begins. If the chosen rung is already open for editing, the rung
workspace is replaced by the rung monitor window. The Monitor panel (located near the top of the window)
includes various commands for use during monitoring. See Using the Rung Monitor on page 381.
NOTE: The Abort command is active only during communication with the RTU.

380
 6802979C10-BA
Chapter 4: Application Programmer

Figure 276: Monitoring a Rung

If the monitor operation is successful, the values in the rung are updated. If a CRC discrepancy between
the application in the RTU and in the PC is detected, the monitor fails. In this case, the following message
appears: RTU CRC not equal to the DB’s CRC
Output messages are shown in the Monitor tab of the Output bar, located at the bottom of the screen.

Using the Rung Monitor

Procedure:
● To view the rung element parameters as values, select Show Values.
● To view the rung element parameters as symbols, select Show Symbols.
● To monitor one or more specific symbols, perform the following actions in the Watch panel:
a. In the Symbol column, click the … browse button next to an empty cell.
Figure 277: Rung Monitoring – Watch Panel

b. Select the preferred symbol name and click OK.

You can select symbols from the current rung or from other rungs in the process.
● To search for a symbol name in a table while monitoring, perform one of the following steps:
● To search using the Find dialog, select Edit → Find...
● To search using the Quick Find Symbol tool, select Edit → Find Symbol...
For details on using the Find dialog, see Searching for Variables or Duplicated Columns on page 339.
For more information on the Quick Find Symbol tool, see Finding Symbols/Variables in Applications
on page 371.
● To refresh the rung and update the values, select Refresh.
● To set qualifiers to monitor the database elements based on certain conditions, perform the following
actions:

381
6802979C10-BA
Chapter 4: Application Programmer

a. To open the Qualifier Table, click Set Qual...

b. In the Symbol Name column, click the … browse button next to an empty cell.
c. In the Quick Find Symbol dialog, select a symbol.
d. To add the selected symbol to the Qualifier Table (and close the Quick Find Symbol dialog),
click OK.
e. In the same row as the newly added symbol, use the drop-down lists in the Operation and Value
columns to set the preferred operation and value for the condition.
NOTE: If you want to add one or more additional rows, click Add. If you want to delete a
row, select it and click Delete.
Figure 278: Qualifier Table

f. To apply the condition and close the Qualifier Table, click OK.
● To sample/monitor the current elements regardless of the qualifier conditions defined in the Qualifier
Table, select Unqual Ref.
The screen is refreshed at the rate specified in Ref Rate. Any elements whose values have changed
since the last refresh are colored red.

● To sample/monitor the current elements when all qualifier conditions are met, select Qual Ref.
The screen is refreshed at the rate specified in Ref Rate. Any elements whose values have changed
since the last refresh are colored red.

● To define the rate at which the monitored values are refreshed, enter the preferred value in the Ref
Rate field.
● To close the monitor, select Close Monitor.

4.15.2.1
Rung Monitor Commands
Table 63: Summary of Rung Monitor Commands

Rung Monitor Com- Description

mand
Unqual Ref (unqualify Samples/monitors the current elements regardless of the qualifier conditions set
refresh) in the Qualifier Table (accessible via the Set Qual... command).
In the case of an indexed element, the indexed value is sampled only if it
matches the equal (=) qualifier. For example, D,9 is sampled only when I=9.

382
 6802979C10-BA
Chapter 4: Application Programmer

Rung Monitor Com- Description

mand
If the RTU is not executing the current rung, a message appears. Press ESC to
exit.

Qual Ref (qualify re- Samples/monitors the current element upon any operation when all the condi-
fresh) tions set in the Qualifier Table (accessible via the Set Qual... command) are
met.
For example, after setting the following qualifiers: I=9, J=3, K<5, the indexed
element is sampled when all qualifier conditions are fulfilled. In the rung, only D,I
are displayed since J and K are not specified.
The values are sampled immediately after the rung has been executed. If the
rung includes the JMP, JSP, or RET operators, the values are sampled before
executing the rung.

Abort Aborts the rung monitor operation. If no operation has been started, the Abort
command/icon is inactive.
Ref rate (refresh rate) Defines the interval (in seconds) of the continuous refresh of the displayed rung.
Set Qual... (set quali- Opens the Qualifier Table, where the user defines qualifiers to monitor the
fier) database elements based on certain conditions. In the case of an indexed
element used by the rung (such as V,I), the variable is sampled when the equal
(=) operation occurs.

● Show Symbols The user toggles between two display options during run-time rung monitoring.
Depending on the user setting, the monitor displays either the database symbol
● Show Values names, or the actual values/variable names.

4.15.3
Displaying the Performance Monitor Table
The Performance Monitor table contains the system performance monitoring variables, which are reported
by fixed functions in the system.For descriptions of these variables, see System Performance Monitoring
Variables on page 384.
Prerequisites: Open the application for the preferred site in the Application Programmer (STS mode).

Procedure:
1. To connect the STS PC to the preferred RTU, perform one of the following steps in the connection bar
(near the top of the Application Programmer window):
● If the RTU is locally connected, select Local.
● If the RTU is remotely connected, input the Site ID and Link ID of the preferred site (with the
Local option not selected).
Figure 279: Application Programmer Connection Bar

2. In the application bar on the right side of the window, navigate to the Database tab and expand the list
of System Tables.
3. Right-click Performance Monitor and select Monitor.

383
6802979C10-BA
Chapter 4: Application Programmer

Figure 280: Performance Monitor Table

4.15.3.1
System Performance Monitoring Variables
Table 64: Description of System Performance Monitoring Variables

System Performance Monitoring Variable Description

ScnTim (scan time) Reports the Main process scan time (in 10 msec
resolution). The scan time is measured from the
beginning of the scan until the beginning of the
next scan.
MaxScn (maximum scan) Reports the maximum Main process scan time (in
10 msec resolution). During monitoring, this varia-
ble displays the longest scan time since the system
was started, or since the variable was reset. The
user can reset this variable during monitoring by
inputting 0
ScnLst (scan last) Reports the time (in 10 msec resolution) since the
system accessed and performed the last task (the
lowest priority task in the system software).
DtyCyc (duty cycle) Reports the percentage of CPU cycle time that is
assigned to the Main process and all system tasks
in higher priorities. The system starts with 60% du-
ty cycle for these tasks. When the system cannot
execute the lower priority tasks (including the lad-
der tasks in priorities A through D), the percentage
of CPU cycle time assigned to higher tasks is re-
duced to allow for the execution of lower priority
tasks.

384
 6802979C10-BA
Chapter 4: Application Programmer

4.16
Backing Up the Database
Critical portions of the user application database are defined as blocks, which are backed up and then
restored to the RAM.
For more information, see "Database Backup" in the MC-IoT STS Advanced Features manual.

4.16.1
Defining Critical Database Blocks
IMPORTANT: If you change the structure of a user database table (by adding or deleting rows or columns)
that is backed up in the flash, check the BlocksToBackup table to see if the block definition needs to be
changed accordingly.
Prerequisites: Open the preferred application in the Application Programmer.

Procedure:
1. In the application bar on the right side of the window, navigate to the Database tab.
2. Right-click User Tables and select Append Table → Backup Blocks table.
The BlocksToBackUp table appears in the database tree, located under User Tables. The table
number may vary, depending on the total number of user tables.
Figure 281: BlocksToBackUp Table in the Database Tree

3. To open the BlocksToBackup table, double-click its entry in the database tree.
4. Create one or more entries (rows) with values defining the block or blocks to be backed up.
NOTE: By default, the first row of the table is automatically populated with –1 in all columns.

For descriptions of the table parameters (columns), see BlocksToBackup Table Parameters on page
386.
For further information, see the "Database Backup" section of the MC-IoT STS Advanced Features
manual.
5. Save the application.
The BlocksToBackup table is saved, and the Reserved values system table is updated accordingly.

6. Compile the application.

See Compiling Applications (ACE3600 Only) on page 373.
7. With the Reset and Load option selected, download the application to the preferred site or sites.
See Downloading Applications in the Application Programmer on page 375.

385
6802979C10-BA
Chapter 4: Application Programmer

Postrequisites:
To erase a block definition after saving the BlocksToBackup table, set all the column values of the preferred
table entry to –1 (after the table is downloaded, the firmware will erase the saved block from the flash).
If you make any changes to the BlocksToBackup table after it has been downloaded:
1. Recompile the application.
2. With the Reset and Load option selected, download the application to the preferred site or sites.

4.16.1.1
BlocksToBackup Table Parameters
Table 65: BlocksToBackup Table Parameters

Value Description
Table The number of the table that contains the critical data to be backed up. This
value cannot be changed during database monitoring.
FirstCol The first column in the table to be backed up. This value cannot be changed
during database monitoring.
ExtraCols The number of successive table columns (after FirstCol) to be backed up. This
value cannot be changed during database monitoring.
FirstRow The first row in the table to be backed up.
ExtraRows The number of successive table rows (after FirstRow) to be backed up. This
value cannot be changed during database monitoring.
Interval How frequently the backup should be performed, in minutes (for example, once
every three minutes). If the interval is set to –1 or 0, no backup is performed.
This value cannot be changed during database monitoring.
LastStorRslt The result of the last store operation, which is updated in the table after the
operation, whether the operation was automatic or on demand. The value can be
one of:
● –1 (Initial value – no store has been performed)
● 0 (Last store OK)
● 1 (Preparation stage of the last store operation failed)
● 2 (Write operation of the last store to flash failed)
● 3 (At least one of the block identifiers is invalid; therefore the last store
failed)
● 7 (Failed to calculate the size of the block to store)

LastRstrRslt The result of the last restore operation, which is updated in the table after the
operation, whether the operation was automatic or on demand. The value can be
one of:
● –1 (Initial value – no restore has been performed)
● 0 (Last restore OK)
● 3 (At least one of the block identifiers is invalid; therefore the last restore
failed)

386
 6802979C10-BA
Chapter 4: Application Programmer

Value Description

● 4 (Failed to compare stored block's identifiers in the flash to its identifiers in

the current ladder's backup table)
● 5 (Last restore failed because failed to load block contents to its related
table)
● 6 (Cannot restore block because there is no stored block)
● 7 (Failed to calculate the size of the block to restore)

4.16.2
Storing Critical Database Blocks
Critical blocks can be stored automatically at regular intervals (as defined by the user), or via a ladder call in
the user application.

Procedure:
Perform one of the following steps.

If… Then…
If you want to configure the firm- set the preferred Interval value for the relevant BlocksToBack-
ware to periodically store the criti- up table entry.
cal blocks in the flash, See Defining Critical Database Blocks on page 385.

To store the critical blocks in the perform the following actions:

flash from the user application,
a. Program a rung with a CAL to the StorBlock function,
passing one of the following:
● Number of the preferred block (index to the BlocksTo-
BackUp table)
● 255 (for all blocks)
b. Save the application and download it to the RTU.

Postrequisites: To verify that a block is stored in the flash, use the SW Diagnostics and Logger, Device
MFFS, Level 0. At this device and level, each block is named BFilei (where i=block number, which is the
index to the BlocksToBackUp table).

4.16.3
Restoring Critical Database Blocks
Procedure:
● To restore a stored critical block to the RAM from the user application, perform the following actions:
a. Program a rung with a CAL to the RstrBlock function, passing one of the following:
○ Number of the preferred block (index to the BlocksToBackup table)
○ 255 (for all blocks)
b. Save the application and download it to the site.
● To restore a stored critical block to the RAM from the firmware, reset the system.

387
6802979C10-BA
Chapter 4: Application Programmer

You can reset the system by manually powering it down and then turning it on again. Alternatively, you
can perform a download operation that resets the system. Such an operation may include:
○ Via the Application Programmer, downloading a ladder application with the Reset load
option selected in the Application Settings. See Downloading Applications in the Application
Programmer on page 375.
○ Via the Site Download dialog, downloading to the site with the Reset after total download
option selected (you do not necessarily need to download any blocks to reset the system). See
Downloads to Sites on page 145.
Before the RTU restores data from a block in the flash, it checks it against the block description in the
current BlocksToBackUp table and the actual database table to which the block is to be written. A
block that fails validation is removed from the flash.

4.16.4
Removing Critical Database Blocks
Procedure:
To remove a stored critical block from the flash RAM (via the user application), program a rung with a CAL
to the RmvBlock function, passing one of the following:
● The number of the preferred block (index to the BlocksToBackUp table)
● 255 (for all blocks)
IMPORTANT: You are not prompted to confirm the operation when deleting a block. Removal is
irreversible. Be careful when removing one or all blocks from a ladder.
Postrequisites: To verify that a block is removed from the flash, use the SW Diagnostics and Logger, Device
MFFS, Level 0. At this device and level, each block is named BFilei (where i=block number).
If you no longer want a database block to be backed up in the flash, perform the following actions:
1. Reset the corresponding row in the BlocksToBackUp table. See Defining Critical Database Blocks on
page 385.
2. Recompile the application.
3. Download the application to the relevant site or sites.

4.17
Converting ACE3600 Application Databases to
MC-EDGE Format
The user can convert an existing ACE3600 Ladder application (.adb) to the MC-EDGE application tables
format (.axml). Only the user tables are converted; ladder diagrams and constant tables cannot be
converted.
Applications can be converted in the Application Programmer, or via the STS Application Manager.
During the conversion, all columns with supported data types are copied to the target MC-EDGE application.
If a column has an unsupported data type, it is converted to a supported type according to the following rules:
● If the type has no data, it is converted to Integer Value.
● If the type has parameter data, it is converted to Integer Parameter or Long Parameter, depending on
its length.
For example, Timers are converted to Integer Parameter, and IP Address Parameter is converted to Long
Parameter.

388
 6802979C10-BA
Chapter 4: Application Programmer

For a complete list of data types, see Data Types on page 332.
User table indices are retained in their original format, inherited from the source application. User table 0 is
not supported and is skipped during conversion because index 0 is used by the System table in MC-EDGE.
The COS name is not supported and is therefore skipped. Duplicated columns are not supported and are
converted to regular columns with new names generated for them.

Procedure:
● To convert an application via the Application Programmer, perform the following actions:
a. Open the preferred application in the Application Programmer.
b. Select File → Convert to MC-EDGE...
c. In the Convert User Tables to MC-EDGE dialog, browse to the directory where you want to save
the converted file.
The default target location is in the STS installation directory under \Projects\<project
name>\System\Applications\
where <project name> is the name assigned by the user when creating the STS project. See
Creating Projects in STS on page 97.
NOTE: If you select a location outside of the STS project, the target application is not added
to the project automatically.
d. Enter the preferred File name.
e. To begin the conversion process, click Save.
● To convert an application via the Application Manager, perform the following actions:
a. From the STS system view, select System → Application Manager...
b. In the list of Applications, right-click the preferred application and select Convert to MC-EDGE...
c. Enter the new application name.
d. To begin the conversion process, click OK.
Result: After the process is completed, a pop-up dialog appears with the results of the conversion (such as
the renaming of columns or changing of data types, if applicable). The report can be saved, if preferred.

389
6802979C10-BA
Chapter 4: Application Programmer

Figure 282: Application Tables Conversion Report

4.18
Viewing the Application Programmer Online Help
Procedure:
● If you want to open the Application Programmer online help to the main page, select Help
→ Contents.
● If you want to view the online help section for a specific feature of the Application Programmer (while
using that feature), press F1.
NOTE: If the current location in the Application Programmer has a dedicated help page, F1
opens that page. Otherwise, F1 acts as a shortcut to the Contents command and opens the
main page of the online help.
● If you want to view the Application Programmer software version, select Help → About Application
Programmer.
● If you want to view a reference table with the Application Programmer keyboard commands, select
Help → Keyboard Reference.
See Keyboard Commands in Application Programming on page 392.

4.19
Printing Applications
Printing application tables and rungs may be useful for documentation and debugging purposes.
Prerequisites: Open the preferred application in the Application Programmer.

Procedure:
1. Perform one of the following actions:
a. To print without previewing, select File → Print...

390
 6802979C10-BA
Chapter 4: Application Programmer

b. To view a preview before printing, select File → Print Preview.

2. In the Print Application or Print Preview dialog, perform the following actions:
a. Select one or more items (including tables, processes, and rungs) to print.
By default, all tables, processes, and rungs in the application are selected. Before printing, ensure
that only the preferred item or items are selected.
NOTE: When selecting (checking) or deselecting (unchecking) a parent element in the tree,
the items under it are also selected or deselected. Expand an element to view its contents
(and to select some of them, if preferred).
Figure 283: Print Application Dialog

b. Click OK.
Result: If you chose to preview the print job, the Print preview window appears (click the Print icon to
proceed with printing). Otherwise, the standard Windows Print dialog appears.

4.20
Closing Applications
The Application Programmer in standalone mode includes a Close Application command to close the
currently open application without exiting the software.
If you are running the Application Programmer in STS mode, the Close Application command is not
available. Instead, exit the Application Programmer. See Exiting the Application Programmer Window on
page 392.

Procedure:
To close the application, select File → Close Application.
If any changes are not yet saved, you are prompted to save the application before closing it. Click Yes to
save the changes, No to discard changes, or Cancel to remain in the application.

391
6802979C10-BA
Chapter 4: Application Programmer

If you prefer, you can save the application under a different name. Before closing the application, select
File → Save Application As.

4.21
Exiting the Application Programmer Window
Procedure:
To exit the Application Programmer window, select File → Exit.
If any changes are not yet saved, you are prompted to save the application before closing it. Click Yes to
save the changes, No to discard changes, or Cancel to remain in the application.
If you prefer, you can save the application under a different name. Before closing the application, select
File → Save Application As.

4.22
Keyboard Commands in Application Programming
The keyboard can be used to execute commands and navigate the window.

Table 66: Keyboard Commands in Application Programming

Key Action
Rung Editing
Arrows keys (left, right, Move between elements; selection is moved (the window is auto scrolled, if
up, down) necessary)
Alt + arrow keys Move between lines
NOTE: In edit mode, Alt+down opens the list of database names to
select a rung element parameter.

Ctrl + arrow keys Move focus (black frame) between elements; selection is left intact
Ctrl+Space Toggle selection of the focused (black framed) element
Shift + arrow keys Move and select the elements (“extend selection”)

● PgUp Scroll the window up and down

● PgDn

● Shift+PgUp Scroll the window left and right

● Shift+PgDn

Complex Editing Commands

A Add an Input element after the current element
I Insert an Input element before the current element
O Add an Output element after the current element
B Open a branch before the current element and add an Input element to it
C Close a branch after the current element
S Open a branch and add an Output element
Other Keys

392
 6802979C10-BA
Chapter 4: Application Programmer

Key Action
Esc ● Cancel mouse actions before finishing
● Cancel dragging
● Cancel element parameter editing in rung
● Move between different workspace windows and the Application tree

F9 Normalize the rung

F7 Compile the application
Ctrl+F7 Compile and download the application
Alt+F7 Configure application settings
Del Delete
Ctrl + C Copy
Ctrl + X Cut
Ctrl + V Paste
Ctrl + Z Undo
Ctrl + A Select all
Menu key The menu key (located next to the right Ctrl key) opens the context menu
for the selected object or field

● Ctrl+PgUp Go to the next/previous rung, database table, or I/O table

● Ctrl+PgDn

Ctrl + Num + Zoom In

Ctrl + Num – Zoom Out
Ctrl + Num * Zoom Normal

● Enter Edit the first parameter of the selected element

● Space
● E

Parameter Editing in Element

Alt + down arrow Open the Quick Find Symbol dialog

● Tab Move (forward and backward) between parameters

● Shift+Tab

Esc Cancel parameter editing without saving

Enter Save and finish parameter editing
Rung Monitor Actions
F2 Toggle Name/Value
F4 Set Qualifier Table
F5 Unqualify Refresh
F6 Qualify Refresh
Application Operations

393
6802979C10-BA
Chapter 4: Application Programmer

Key Action
Ctrl+N New application
Ctrl+O Open an application
Ctrl+S Save the application
Ctrl+P Print the application
Application Programmer Navigation
Alt+0 Go to the Workspace bar
Alt+2 Go to the Output bar
Ctrl+F Open the Quick Find Symbol dialog
Ctrl+Shift+F Find
Ctrl+1 Go to the Database tab in the Workspace bar
Ctrl+2 Go to the Process (Rung) tab in the Workspace bar
Ctrl+3 Go to the I/O Link tab in the Workspace bar
Esc Return to the editor window
Enter (on a tree control) Open the corresponding item in the editor
Miscellaneous Keys
F1 Help
Ctrl+Z Undo Last Operation
Ctrl+Shift+Z Redo Last Undo

394
 6802979C10-BA
Appendix A: Site Configuration Parameters

Appendix A

Site Configuration Parameters

A number of parameters and settings are defined when configuring an ACE3600, ACE1000, MC-EDGE®,
IRRInet-M, IRRInet-EDGE, or ACE IP Gateway site. Such settings include port parameters (for the various
on-board and plug-in communication ports), I/O parameters, and other advanced parameters.
The color of the site configuration parameters indicates their status. The color of the parameter category
reflects the change status (white=default group, red triangle=modified group). The color of the parameter
reflects the status of the inputted value (red=value out of range, green=value different from default).
Port and I/O parameters are white when set to the default value, and turn green when set to any value other
than the default one.
When configuring an ACE3600, ACE1000, MC-EDGE, or IRRInet-M site in the STS, parameters are
displayed according to context. For example, when you select a port type, only those parameters that are
applicable to the selected configuration are displayed. In addition, only those parameters that are defined for
the particular system software version are displayed.
For certain parameters, the range <minimum–maximum> and [default]: values are listed. The default value
provided is one of the possible values. The default may change according to changes in the configuration.
Not all ACE3600 parameters are available for ACE1000 and MC-EDGE.
The IRRInet-EDGE and MC-EDGE parameters are identical.

A.1
Port Parameters (ACE3600/ACE1000/MC-EDGE)
The ACE3600, ACE1000, and MC-EDGE® include a number of on-board and plug-in ports, which vary
from model to model. Each port can be configured for different connections (such as RS232, RS485, PPP,
Ethernet, or dial-up) to a number of media.
In general, the plug-in ports (PI1, PI2) have a wider variety of options than the on-board ports (SI1, SI2,
ETH1). For more information on the CPU ports, see the relevant device manual:
● ACE3600 RTU Owner’s Manual
● ACE1000 RTU Owner's Manual
● MC-EDGE Owner's Manual
The port parameters define the following:
● The communications ports of the RTU site
● The devices connected to the ports
● The type of media connection to the communication network
For each media type, a different set of port and link parameters is available. For each media type, the
provided default configuration can be modified.
To view or edit these parameters, click on a port General or Ports tab within the site configuration. The
possible port configurations and port parameters are described in the following sections.
NOTE: Any change to the port type parameters on the left side of the port definition (such as Media,
Connection type, Radio Type, Modem, etc.), causes all advanced physical and link layer parameters to
return to their default settings. To prevent loss of these parameters, save the site configuration before
making any subsequent changes to the port type.

395
6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.1
SI1 Port
A.1.1.1
SI1 Port Parameters
ACE3600

Table 67: ACE3600 SI1 Port Parameters

Parameter Allowed values

Media ● RS-232 (default)
● RS-485
● Not used

Operation Mode For RS232 media type: Async

Connection Type RS-232 ● User port (ladder controlled)
media type
● Local computer
● RTU-to-RTU (default)
● External modem
● External dial-up modem
● Protocol analyzer port
● Third party protocols
● GPS receiver
● PPP
● RTU-to-PIU (IRRInet-ACE only)

RS-485 ● RTU multi-drop (default)

media type
● User port (ladder controlled)
● Third party protocols

Connection Mode For External Modem:

● Full-duplex
● Multi-drop half-duplex with CD
● Multi-drop half-duplex without CD
● MAS (Lines) (default)
● MAS (Radios)
● Analog radio modem

For Protocol analyzer port:

Sets the port name to which the protocol analyzer listens (for
example, Receive from PI1).

Connected To For Third party protocols:

396
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values

● to Master (default)
● to Slave
See the MC-IoT STS Third Party Protocols Support manual.

Type For external modem MAS (Lines) and MAS (Radios):

● Full duplex (default)
● Multi-drop half duplex

ACE1000/MC-EDGE

Table 68: ACE1000/MC-EDGE SI1 Port Parameters

Parameter Allowed values

Media ● RS-232 (default)
● RS-485
● Not used

Connection Type RS-232 ● MDLC (default)

media type
● User port
● GPS receiver
● Modbus Slave
● DNP Master
● DNP Slave
● PPP
● MODBUS Master

RS-485 ● MDLC (default)

media type
● Modbus Slave
● User port
● MODBUS Master
● DNP Master (MC-EDGE only)
● DNP Slave (MC-EDGE only)

Connected to RS-232 Over MDLC:

media type ● Local computer
● RTU-to-RTU (default)
● External modem

Over PPP:
● Cellular modem (default)
● TETRA
● Null modem

397
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values

RS-485 RTU-to-RTU (over MDLC)
media type
Connection Mode For External modem connection type:
● Full-duplex (default)
● Multi-drop half-duplex with CD
● Multi-drop half-duplex without CD
● MAS (Radios):
○ Full-duplex (default)
○ Multi-drop half-duplex with CD

A.1.1.2
ACE3600 SI1 Port Configurations
Table 69: ACE3600 SI1 Port Configurations

Configuration Description
Not used The specified port is not in use. Setting a port to Not used frees
any resources that might otherwise be allocated to the port.
RS-232, Async, Local computer For connection to the STS or central over MDLC protocol.
RS-232, Async, RTU-to-RTU For local connection to another RTU in asynchronous mode, via
RS232 over MDLC protocol (can also be used for communicat-
ing with STS).
RS-232, Async, User port (ladder con- For use when the RS232 port is to be controlled by the ladder
trolled) program.1 Not available for ACE IP Gateway.
RS-232, Async, External modem For connection to an external modem over MDLC protocol. The
external modem can be full-duplex, multi-drop half duplex, or
MAS (Radio/Line).
RS-232, Async, External dial-up mo- For connection to a dial-up external modem over MDLC proto-
dem col.
RS-232, Async, Protocol analyzer port For defining the CPU module as a protocol analyzer bridge
between the link connected to one of the RTU ports and the
STS.
RS-232, Async, Third-party protocols, For connecting the RTU to SCADA systems based on third-par-
to Master/to Slave ty protocols. Not available for ACE IP Gateway.2
RS-232, Async, GPS receiver For connecting the RTU to a GPS timing receiver.
For details, see the MC-IoT STS Advanced Features manual.

RS-232, Async, PPP, Null modem For connecting the RTU via PPP to a null modem.3
RS-232, Async, PPP, iDen modem For connecting the RTU via PPP to a iDEN modem.3
RS-232, Async, PPP, For connecting the RTU via PPP to a standard modem.3
Standard modem

RS-232, Async, PPP, TETRA For connecting the RTU via PPP to a TETRA radio.3

398
 6802979C10-BA
Appendix A: Site Configuration Parameters

Configuration Description
RS-232, Async, PPP, ASTRO IV&D For connecting the RTU via PPP to an ASTRO® IV&D radio.2
RS-232, Async, RTU-to-PIU (IRRInet- For local connection between an IRRInet-ACE RTU and a PIU
ACE only) in asynchronous mode, via RS232 over MDLC protocol (can
also be used for communicating with STS).
RS-485, RTU multi-drop (MDLC) For local connection between two or more RTUs in asynchro-
nous mode, via RS485.
RS-485, User port (ladder controlled) For use when the RS485 port is to be controlled by the ladder
program.1 Not available for ACE IP Gateway.
RS-485, Async, Third-party protocols, For connecting the RTU to SCADA systems based on third-par-
to Master/to Slave ty protocols such as serial MODBUS (not available for ACE IP
Gateway).2

1For details, see User Defined Local Ports on page 597.

2For details, see the AC3600 STS Third-Party Protocols Support manual.
3For details, see “MDLC over IP” in the MC-IoT STS Advanced Features manual.

A.1.1.3
ACE1000/MC-EDGE SI1 Port Configurations
Table 70: ACE1000/MC-EDGE SI1 Port Configurations

Configuration Description
Not used The specified port is not in use. Setting a port to Not used frees any resour-
ces that might otherwise be allocated to the port.
RS232, MDLC, Local For connection to the STS or central over MDLC protocol.
computer
RS232/RS485, MDLC, For local connection to another RTU in asynchronous mode, via RS232 or
RTU-to-RTU RS485, over MDLC protocol (can also be used for communicating with STS).

RS232, MDLC, External For connection to an external modem over MDLC protocol. The external
modem modem can be full-duplex, multi-drop half duplex, MAS (Radios).
RS232/RS485, User For use when the RS232 or RS485 port is to be controlled by the user
port application. Not available for ACE IP Gateway.
For further details, see User Defined Local Ports on page 597.

RS232, GPS receiver For connecting the RTU to a GPS timing receiver.
For details, see the MC-IoT STS Advanced Features manual.

RS232/RS485, MOD- For connecting the RTU to SCADA systems based on third-party protocols,
BUS Server (Slave) such as serial MODBUS. Not available for ACE IP Gateway.1

RS232, PPP, Cellular For connecting the RTU via PPP to a cellular modem, TETRA, or null modem.
modem/TETRA/Null mo- For further details, see the “MDLC over IP” section in the MC-IoT STS Ad-
dem vanced Features manual.
RS232/RS485, DNP Cli- For connecting the RTU to SCADA systems based on DNP protocol.1
ent (Master)

399
6802979C10-BA
Appendix A: Site Configuration Parameters

Configuration Description
RS232/RS485, DNP For connecting the RTU to SCADA systems based on DNP protocol.1
Server (Slave)

1 For more information, see the MC-IoT STS Third-Party Protocols Support manual.

A.1.1.4
Link Parameters for SI1 Port
Table 71: Link Parameters for SI1 Port

Parameter Allowed values Default Description

value
Link name n/a n/a Contains the logical name of the link to which
the port is connected. The link name is auto-
matically selected according to the port param-
eters. For example, if the connection type is
user port (ladder controlled), then STS auto-
matically selects USER1 as the link name. If
preferred, you can select another name from
the drop-down list.
Zones... RADIO1/1 – n/a For certain External modem connection type
RADIO1/9 parameters.
Click the Zones button to open the Define
Zones dialog box.
To add a zone, select it and click Add.
To remove a zone, select it and click Remove.
To save the list and close the Define Zones
dialog, click OK.
For more information about zones, see:
● Two-Zone System on page 71
● Multiple Zone Systems on page 72

Data speed ● 600 Bps If applicable to the selected port type parame-
ters, this parameter defines the communication
● 1200 Bps data speed of the selected media.
● 2400 Bps
● 4800 Bps
● 9600 Bps1
● 19200 Bps
● 38400 Bps
● 57600 Bps
● 115200 Bps2
● 230400 Bps
1Default for ACE3600

400
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default Description

value
2Default for ACE1000/MC-EDGE

Default n/a n/a Ensures RTU “mobility.” The Default routing

routing parameter enables the RTU to be switched
from one base station to another by changing
the radio frequency (RadioX) or switching phys-
ical lines (LineX), but without changing the
Link ID and the MDLC network settings.
The following values are allowed:
● None: The feature is not used.
● To Slave(s): If the RTU serves as base
station to a central connected to it, then
one of the ports must be defined as To
Master/Central (all other ports must be set
to None). If the base station is the one
that handles the data sent by the RTUs,
one of the RTU ports must be defined as
To Slave(s). This is the port through which
the RTU communicates with the Servers
(Slaves).
● To Master/Central: If the RTU is used as
the “Server (Slave),” then one of the ports
should be defined as To Master/Central,
and its Link ID must be RadioX or LineX.

Port mode User computer/terminal ACE3600 only: The user port mode of opera-
(DTR support) tion: User computer/terminal (DTR). The port
controls DTR according to its receive buffer ca-
pacity.
GPS ● Unknown (default) ACE3600 only: The type of protocol used by
Protocol the GPS receiver.
● Motorola binary protocol
The Unknown and Motorola binary protocols
● NMEA 0183 are used for the Synergy Systems SynPaQ/E
GPS Sensor with M12+ Timing receiver. NMEA
0183 is used for the Garmin GPS 16 HVS re-
ceiver.
NOTE: For the Garmin GPS 16 HVS,
set the Data speed to 4800 Bps.

Time period 8–60 10 ACE3600 only: Amount of time (in seconds)

to get data to wait to get data from the GPS, starting from
from GPS the GPS PPS interrupt until receiving the GPS
data.
Links... LINE 1 – LINE 1 ACE3600 only: Opens the list of multiple IP
LINE 29 links used by this port (replaces the Link name
field for IP ports).
To add a link, select it and click Add. To re-
move a link, select it and click Remove. To

401
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default Description

value
save the list, click OK. Relevant for PPP con-
nection type only.
NOTE: When more than one link is se-
lected, the Advanced Link Layer pa-
rameters can be configured separately
for each link by clicking the Advanced
Configuration... button.

DNS Servers 0.0.0.0 – 0.0.0.0 ACE3600 only: Opens a dialog that allows the
255.255.255.255 user to define up to three DNS server IP ad-
dresses (relevant to PPP connection type only).
To add an IP address, type the address in
xxx.xxx.xxx.xxx format.
To remove an address, reset it to 0.0.0.0
To save the list, click OK.
NTP Servers n/a n/a ACE3600 only: Opens a dialog that allows the
user to define up to four NTP servers (relevant
to PPP connection type only).
To add a server, type its address in the one of
the fields.
To remove a server, erase it.
To save the list, click OK.

Protocols n/a n/a ACE3600 only: Opens the Select Protocols

to Support dialog for configuring third-party
protocols over an IP port (relevant to PPP con-
nection type only). To support MODBUS over
TCP/IP connections, select Modbus Slave. To
save the changes and close the dialog, click
OK.
Port name n/a n/a ACE3600 only: For third party protocols over
an IP port, specify the port name (PLC1 –
PLC3). If no third party protocol is assigned to
this port, select N/A.

402
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.1.5
Advanced Physical Parameters for SI1 Port
The following tables list the advanced physical parameters of the SI1 port. The first table includes parameters
that pertain to the SI1 port generally (i.e. to more than one connection type). The remaining tables include
parameters specific to particular connection types.

Table 72: Advanced Physical Parameters for SI1 Port (General)

Parameter Allowed Default Description

values value
Number of idles to 1–200 80 In UART communications without close characters,
announce 'End of a period of silence notifies all layers above Physical
10–2000 500
RX' <1-200> and that reception has ended. This period is calculated
NOT more than <10– in terms of idles, which are converted to time as a
2000> msec function of the data speed. The system uses this val-
ue (specified in milliseconds, in the first field) or the
value specified in the second field ("and NOT more
than..."), whichever is smaller.
Interval between 100– 5000 The interval of time (in milliseconds) that should
Link TX retries 6000 elapse before retransmission of a data frame for
which no ACK was received.
Maximum time wait- 100– 60000 The period of time (in milliseconds) that the system
ing for TX-grant 900000 waits for channel access, from the time it requests
a channel. If this period of time elapses without gain-
ing the channel, this transmit attempt is considered
failed.
Minimum time to re- 0–30000 0 For External modem / External dial-up modem:
try The minimum period of time (in milliseconds) that
should elapse between the end of a transmission
and its first retry, and between retries.
RTS always ON Yes / No No The RTS of the RTU is connected to the DTR of
the modem. It is controlled by the software, and is
on. The default setting varies for different port types.
In sync connections, RTS always ON means that
frames are not ‘wrapped’ by RTS automatically, but
may be negated by the software in some cases.

Table 73: Advanced Physical Parameters for SI1 Port (External Modem)

Parameter Allowed values Default value Description

Number of bits 2–8 4 This parameter pertains to the slotted ac-
for staggering cess mechanism used by the channel ac-
cess sub-layer of MDLC. A value of n
means that an RTU waits at most 2n free
slots before transmitting. The value of ‘n’
should be equal to, or higher than, the total
number of RTUs in the system sharing the
same media.

403
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default value Description

Special attention is required when assigning
the RTU logical address (site ID) in sites
that use the channel access mechanism.
The value of (siteID MOD n) for each site
must be unique so as to prevent collisions
between two transmissions.

Max. TX-data 1000–60000 30000 For RS-485 RTU multi-drop ports: The max-
duration imum waiting time (in milliseconds) for a
channel. After this time-out, the system ac-
cesses a channel whether or not it is free.
The default value of 0 means that this fea-
ture is disabled (the RTU does not transmit
if the channel is busy).
Channel holdup 0–1000 40 Length of time (in milliseconds) that a con-
time stant tone transmission is continued after
the end of transmission.
First warm up 10–1000 10 Specifies the delay (in milliseconds) be-
delay tween a transmission request (PTT press)
and the start of data transmission in trunked
systems. The value should be greater than
the Channel monitor time resolution.
NOTE: Before data transmission,
different types of signals are trans-
mitted for this period, depending on
the radio/modem type.

Channel monitor 10–2500 20 The size of a time slot (in milliseconds) in

time resolution the MDLC slotted channel access mecha-
nism. Defines the interval from the moment
PTT has been pressed in an RTU, until the
other RTUs sense it. This interval depends
on the type of radio used – the quicker the
response of the channel monitor, the shorter
the interval. The RTU uses this parameter
to prevent collisions on the channel when
several RTUs have messages to transmit by
contention.
This interval is used (automatically) as fol-
lows: each RTU is assigned a priority lev-
el depending on the type of data message
that it needs to transmit (new data, acknowl-
edgment, retry, etc.) and in some cases,
as a function of its address. When the
RTU needs to transmit that message, it first
checks whether the communications chan-
nel is free or not. If the channel is free, the
RTU starts transmitting only after a delay
that is equal to this parameter, multiplied by
the RTU's priority level. If in the meantime
the channel has been occupied by a higher-

404
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default value Description

priority RTU, the entire process is repeated
when the channel becomes free again.
For example, a time resolution of T is as-
signed. When the RTU accesses the chan-
nel, it starts transmitting only after a delay
that is a factor of T. When the RTU access-
es the channel for the first time, the delay is
(n+4)×T, where n represents the 4 less sig-
nificant bits in the address. When an RTU
sends an acknowledgment to another RTU,
it starts transmitting only after a delay of
0 to 3T. If a collision occurs because two
RTUs have been addressed with the same
4 less significant bits, then the address bits
are shifted automatically, and the RTU starts
transmitting after a different delay.

Tx-shutup time 0–30000 0 The minimum waiting time (in milliseconds)

between the end of one transmission and
the following one. It is measured from the
end of the Hold-up of the last transmission
for ports with channel access (for exam-
ple, Radio/RS-485 multi-drop/RS-232 half
duplex).

Table 74: Advanced Physical Parameters for SI1 Port (External Dial-Up Modem)

Parameter Allowed Default value Description

values
Hanging up an un- 1–60 20 Period of quiet time (in seconds) after
used line by INITIA- which the initiator of the conversation
TOR after 1–60 sec hangs up the phone.
Hanging up an un- 1–120 120 Period of quiet time (in seconds) af-
used line by RES- ter which the responder hangs up the
PONDER after 1–120 phone.
sec
Number of dial re- 1–10 3 Number of times the number is redialed
tries (in addition to the first time) in order to
establish communication with a unit.
Interval between re- 1–30 7 Interval of time (in seconds) between
tries a failure to establish communication
(BUSY, NO ANSWER) and the next at-
tempt. However, if a line is busy and
another line is available, the attempt is
renewed via the other line without delay.
Config modem n/a ATE0V1Q0X4&W0&C1 The AT Command string that is sent by
string \r the RTU to the external dial-up modem in
order to configure it. The RTU configures
the modem after each cold restart.
The default settings are as follows:

405
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default value Description

values

● AT – AT command string prefix.

● E0 – Set local echo to: Echo OFF
● V1 – Enables Verbal codes (OK/
Busy/Fail)
● Q0 – Display result codes
● X4 – Result code display (X4 is the
default AT command code display
and enables the display of all the
generated codes)
● &C1 – Normal CD operation (Enables
the CD signal only when there is a
connection)
● \r – Enter
If the default settings need to be
changed, first consult the specific details
in the owner’s manual of your modem.
For more information on using modems
with the RTU, see “Appendix B: Remote
STS Modem Setup” in the MC-IoT STS
Advanced Features manual.

Table 75: Advanced Physical Parameters for SI1 Port (GPS Receiver)

Parameter Allowed values Default value Description

Polarity of Rising Edge / Rising Edge The polarity of the PPS signal generated by the
PPS input Falling Edge GPS. If the input polarity is Rising Edge (Active
signal Low), a low-level pulse on the input is considered
active. If the polarity is Falling Edge (Active High),
a high-level pulse on the input is considered ac-
tive.

Table 76: Advanced Physical Parameters for SI1 Port (PPP Connections)

Parameter Allowed values Default value Description

Format ● 8 bits No Parity 1 stop bit (de- For third-party protocols: Select the appropriate
fault) bit, parity, and stop bit combination.
● 7 bits Even Parity 2 stop bit
● 7 bits Odd Parity 2 stop bit
● 7 bits Even Parity 1 stop bit
● 7 bits Odd Parity 1 stop bit
● 8 bits No Parity 2 stop bit
● 8 bits Even Parity 1 stop bit
● 8 bits Odd Parity 1 stop bit

406
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default value Description

Optional AT n/a n/a This additional AT string can be used to en-
command hance the modem immediately before returning
string it to online mode after configuration in PPP. For
more details, see “Modem Configuration” under
“MDLC over IP” in the MC-IoT STS Advanced
Features manual.
Wait time af- 0–255 7 Specifies how long (in seconds) to wait after
ter Reset ra- restarting the radio/modem before attempting
dio/modem to configure and register it. If a modem config-
uration file was downloaded, the SetRtsTime-
out variable overrides this setting. For more de-
tails, see “Modem Configuration” under “MDLC
over IP” in the MC-IoT STS Advanced Features
manual.
Number of 0–255 3 If the RTU fails to configure or register a ra-
configura- dio/modem, and the radio/modem supports this
tion at- feature, the RTU can restart it using AT com-
tempts to re- mands. The G18 (for GPRS) modem can al-
set radio/ so be powered off and on via an RTS signal
modem from the RTU over RS232. This parameter de-
termines how many failed attempts to connect
the modem are required before restarting it. If a
modem configuration file was downloaded, the
n_failstoreset variable in the file overrides this
setting. For more details, see “Modem Config-
uration” under “MDLC over IP” in the MC-IoT
STS Advanced Features manual.
PPP echo 0–255 0 When set to a value other than 0, defines the
send interval time interval to poll the modem over PPP. If no
reply is received within the maximum number
of retries (as defined by the PPP echo send
max retries parameter), it declares the cable
disconnected, and starts to reconnect with the
modem. This parameter is intended to be used
when no DCD input signal is provided by the
modem. If a modem configuration file was
downloaded, the <pppechosendinterval>
variable overrides this setting.
PPP echo 0–255 0 When set to a value other than 0, defines the
send max re- number of retries to poll the modem if it does
tries not reply. If the maximum number of retries is
reached without receiving a response, the data
cable to the modem is regarded as disconnect-
ed.
This parameter is intended to be used when no
DCD input signal is provided by the modem. If a
modem configuration file was downloaded, the
<pppechosendmaxretry> variable overrides
this setting.

407
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default value Description

PPP proto- Disable / Enable If enabled, this configures PPP to use protocol
col compres- Enable field compression as defined in RFC1661. If a
sion modem configuration file was downloaded, the
<pppprocomp> variable overrides this setting.
PPP address Disable / Enable If enabled, this configures PPP to use address
compression Enable field compression as defined in RFC1661. If a
modem configuration file was downloaded, the
<pppaddrcomp> variable in the file overrides
this setting.
User Name n/a n/a The user name to be entered for PPP authen-
tication when connecting to the modem. If a
modem configuration file was downloaded, the
<username> variable in the file overrides this
setting.
Password n/a n/a The password to be entered for PPP authen-
tication when connecting to the modem. If a
modem configuration file was downloaded, the
<password> variable in the file overrides this
setting.
Allow Dupli- Disable / Disable If enabled, the internal IP address of the mo-
cate Modem Enable dem is ignored. Thus, several modems (such
IP Address- as G24) with the same internal IP address can
es be used on different PPP ports at the same
time.

A.1.1.6
Advanced Link Parameters for SI1 Port
The following tables list the advanced link parameters of the SI1 port. The first table includes parameters
that pertain to the SI1 port generally (i.e. to more than one connection type). The remaining tables include
parameters specific to particular connection types or modem configurations.
The default values for the following parameters may vary for different media.
NOTE: When more than one link is defined, the advanced link layer parameters can be configured
separately for each link.

Table 77: Advanced Link Parameters for SI1 Port (General)

Parameter Allowed val- Default Description

ues value
TX queue size (2^)3 – (2^)6 Maximum number of MDLC frames that can be placed
(2^)9 in the transmission queue before a transmission proc-
ess starts.
Number of ACK 5–50 8 The reception process of the Data Link layer prepares
buffers an ACK for each received data frame. This process is
capable of issuing, in a single ACK message, up to
57 ACKs for data frames that arrived in uninterrupted
sequence. This parameter determines the number of
ACK buffers in which ACKs are prepared and moved

408
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default Description

ues value
to transmission before the “Cannot get ACK buffers”
message is issued to the Error Logger. This message
means that the acknowledging side is unable to move
to ACK transmission because of heavy reception traf-
fic, or because it cannot access a channel for transmis-
sion.
Number of Tx 0–9 2 Number of times that the Data Link layer retransmits a
retries data frame for which an ACK was not received.
Number of TX 0–9 2 Number of times that the Data Link layer retransmits
retries upon a data frame for which a BUSY ACK was received
BUSY ACK (BUSY ACK is issued when all Data Link layer boxes of
the switching node on are full).
Interval be- 10–100 40 Interval of time (in milliseconds) that should elapse be-
tween TX re- fore retransmission of a data frame for which a BUSY
tries upon ACK was received.
BUSY ACK
Number of TX 0–9 0 Number of retries for broadcast frames. Because
broadcast broadcast frames are not acknowledged, specifying a
(Group call) re- value greater than 0 increases the chances of the
tries frames reaching their destination.
A broadcast that activates a momentary operation (not
latch!) is likely to reactivate the operation if the number
of TX broadcasts is greater than 0.

Interval be- 10–100 40 Period of time (in milliseconds) that should elapse be-
tween broad- tween retries of broadcast frames (if the Number of TX
cast (Group broadcast (Group call) retries parameter is not 0).
call) retries
Interval be- 10–100 50 Period of time that should elapse before a retry takes
tween FULL place in Full Duplex. New data frames cannot be sent
DUPLEX TX re- to the retried unit.
tries
Clock synchro- 0–200 22 Delay (in milliseconds; applied to the channel) between
nization delay the end of a transmission of the transmitting RTU and
the beginning of reception of the receiving RTU, for
clock synchronization purposes. The default depends
on the chosen medium. However, the user can change
it.
Maximum num- 1–4 4 Maximum number of units the Data Link layer is capa-
ber of address- ble of addressing in a single transmission. Set to 1 for
able sites in a “private conversation.”
transmission
TX to failed 0–30 5 If the Periodic check of failed RTU parameter is set
RTU every <0: to Disable, specifies the period of time (in minutes)
DISABLE 0-30> after which a failed link is considered back in order.
mi If the Periodic check of failed RTU parameter is set
to Enable, specifies the period of time (in seconds)

409
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default Description

ues value
after which the Network layer issues a control frame to
check the failed link.

Periodic check Disable / Disable The network sends a control frame to check whether
of failed RTU Enable the link is still in "failed" status. The frame is issued if
the link has been in "failed" status for the period of time
specified in the TX to failed RTU every <O:DISABLE
0-30> Min parameter.
Force 'Local’ Default / Force Conducting a session based on Site ID/Link ID using
response Force Local is possible if the port is of the Computer/RSlink
type. Normally, the port is defined for Local Response
if the medium is not “multidrop.” In any case, “local re-
sponse” can be forced on a port if it is not “multidrop.”
The default value depends on the port type. Keeping
the default setting is recommended.
Enable recep- Disable / Enable This parameter is relevant if the parameter with the
tion from re- Enable same name in the firewall section is enabled. If this
mote RTU advanced link parameter is set to Enable, it accepts
communication from a remote RTU that is connected
using another RTU. When this parameter is set to Dis-
able, it rejects communication received on this port if it
originates from a remote RTU (unless the communica-
tion is initiated by the STS).
Enable commu- Disable / Enable This parameter is relevant if the parameter with the
nication with Enable same name in the firewall section is enabled. If this
remote STS advanced link parameter is set to Enable, it allows
communication from the STS when connected via a
remote RTU using this port.
Enable commu- Disable / Enable When set to Enable, allows communication with the
nication with Enable STS when connected locally on this port.
local STS NOTE: On an IP port (such as LAN, PPP, or
RNDIS/USB), local communication means the
port IP address set by the user in STS Com-
munication Setup.

Table 78: Advanced Link Parameters for SI1 Port (GPS Receivers)

Parameter Allowed val- Default Description

ues value
Offset in msec 0–86400000 0 The time offset (in milliseconds) of the current loca-
tion from the Universal Time Coordinate (UTC).
Powerup with Disable / Disable Power up the RTU with factory defaults for GPS
factory defaults Enable receiver.

Set GPS in Posi- Disable / Enable In order to perform precise timing, the GPS receiver
tion Hold (timing Enable position is determined and then the receiver is put
only) into Position-Hold mode in which the receiver no
longer solves for position. With the position known,
time is the only remaining unknown. When in this

410
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default Description

ues value
mode, the GPS receiver requires only one satellite
to accurately determine the time. If multiple satellites
are tracked, then the time solution is based on an
average of the satellite measurements.
● Enable: The GPS timing receiver position is de-
termined once in the beginning.
● Disable: The GPS timing receiver position must
be determined again each time.

Table 79: Advanced Link Parameters for SI1 Port (PPP Connections)

Parameter Allowed values Default val- Description

ue
Default group 000.000.000.000 – 0.0.0.0 For PPP and 10/100 BT connections:
IP address 255.255.255.255 Identifies Site ID 0, which is used for
Group Call.
Get host by Disable / Enable Enable When enabled, allows retrieval from the
name using DNS server of the IP address that corre-
DNS sponds to a given Internet host name.
MDLC over IP 1–65535 2002 For PPP and 10/100 BT connections: This
port number number identifies the MDLC, and is com-
mon to all RTUs and IP Gateways con-
nected to the link. This is a UDP port
number and the provider should be con-
sulted. Ensure that this number is not in
use, as specified by the TCP/IP standard
RFC0960.
Enable sync Disable / Enable Disable For PPP and 10/100 BT connections: En-
ables or disables synchronization over IP.
Must be enabled in both the sending and
receiving unit in order to synchronize.
NOTE: Synchronization is inaccu-
rate because of the IP media. Us-
ing NTP instead (where possible)
is recommended.

Enable reply to Disable / Enable Disable For PPP and 10/100 BT connections: En-
time synchro- ables or disables reply to time synchroni-
nization zation over IP.
Enable routing Disable / Enable Disable For PPP and 10/100 BT connections: En-
on MDLC over ables or disables routing on MDLC over
IP Port an IP port. Enables an FIU to act as a
bridge between two RTUs without fixed IP
addresses.
Notify IP Ad- Disable / Enable Enable For PPP and 10/100 BT connections:
dress when When enabled, as soon as a radio is con-
connecting

411
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default val- Description

ue
text activated, the RTU sends a message
to update its IP address in all sites.
NOTE: These messages are sent
one after the other. Their delivery
and acceptance is not guaran-
teed.
When enabled, if the IP address of an
RTU is changed or obtained from a mo-
dem, the RTU sends a message to update
its IP address in all sites.

Check alive 0–65535 0 For PPP and 10/100 BT connections:

timeout Specifies the timeout (in seconds) from
the last reception from a peer. If nothing
has been received from the peer during
that timeout, the peer is paged before
the next transmission (see the following
description of Poll interval). This behav-
ior guarantees that a peer is reachable
over IP. If the peer does not respond,
route transmissions to it through alternate
routes. The Check alive timeout param-
eter is measured independently for each
site in the IP conversion table. If this pa-
rameter is set to 0, the peer is always
considered reachable as soon as a single
reception has been received from it. This
parameter is treated as 0 regardless of its
value if the Maximum number of polls is
set to 0.
NOTE: This parameter is not to
be confused with the Check alive
timeout for third-party PLC.

Poll interval 0–65535 0 For PPP and 10/100 BT connections:

(sec) Specifies the interval (in seconds) be-
tween repeated polls of a peer. When a
peer is being paged, a poll request is sent.
If no answer is received after that period
of time, another poll request is sent until
the Maximum number of polls is sent
(see the following parameter description).
The Poll interval is measured independ-
ently for each site in the IP conversion
table. If this parameter is set to 0, a single
poll (or no polls) is sent to the peer ac-
cording to the Maximum number of polls
(0 to send no polls).

412
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default val- Description

ue
Maximum 0–255 0 Specifies the number of poll requests to
number of send to check if the peer is alive. When
polls paging a peer, if no answer is received,
it is polled again. If the peer has been
polled for the Maximum number of polls
without response, it is considered failed
and all transmissions are routed through
an alternate path.
Disconnect on Disable / Enable Disable For PPP connections: When set to Ena-
icmp:netun- ble, connection to the modem/radio is ter-
reach minated by force when an icmp:netun-
reach message is received. This mes-
sage specifies that the peer site is un-
reachable because of network problems.
Sometimes these problems can be re-
solved by reconnecting to the modem. For
TETRA, the recommended setting is Dis-
able.
Disconnect on 0–65535 0 For PPP connections: When greater than
idle timeout 0, specifies the timeout (in seconds) dur-
(sec) ing which the RTU monitors the delay
from the last time anything was received
from the modem (during PPP mode). If
this time expires, this means that a prob-
lem with the modem connection exists .
The RTU disconnects and reconnects to
the modem. When set to 0, this parameter
is ignored.
Does modem Disable / Enable Disable For PPP connections: With TETRA radios
support abort such as the MTM700, no abort sequence
sequence is supported. An abort sequence is a ++
+ string sent with a 1 second delay be-
fore and after it, causing the modem to
switch into command mode. Disabling this
parameter expedites connection to a TET-
RA radio.
Ignore CD Never / Always / When Never For PPP connections: When connecting to
connect the modem, its CD is constantly polled,
and, if found to be inactive, the RTU re-
connects to it. This parameter enables the
user to bypass the polling by ignoring CD.
When the parameter is set to Always, the
RTU never checks CD.
When the parameter is set to When con-
nect, the RTU ignores CD during the PPP
connection phase. After PPP is connect-
ed, the RTU resumes polling CD.
When the parameter is set to Never, the
RTU always checks CD.

413
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default val- Description

ue
Modem config- 40–255 40 For PPP connections. The period of time
uration time- (in seconds) the network waits for suc-
out cessful configuration of the modem upon
power up of modem or MOSCAD. If within
this period, the modem configuration does
not complete, MOSCAD marks the port as
Failed, though configuration continues. If
configuration fails, the modem may not be
properly configured. Configuration status
can be checked using the Error Logger
and Software Diagnostics device LIN1L
Level 0, 101. For more details, see “Mo-
dem Configuration” in “MDLC over IP” in
the MC-IoT STS Advanced Features man-
ual.
Registration 0–65535 7200 For PPP connections. If not 0, this sets an
life time (sec) interval (in seconds) in which a connect-
ed radio/modem is deregistered and rere-
gistered for packet data. The RTU adds
an offset to this number, which is derived
from its site ID, so not all radios are re-
started and context activated at the same
time. If a file was downloaded, this param-
eter can be overridden using the regLife-
Timeout variable. For more details, see
“Modem Configuration” in “MDLC over IP”
in the ACE3600 STS Advanced Features
manual.

Table 80: Advanced Link Parameters for SI1 Port (PPP – iDEN Modem)

Parameter Allowed Default Description

values value
Enable Disable / Enable Enabling the Radio Application Layer Protocol (RALP) al-
RALP Enable lows periodic sampling of the modem to get messages about
its status (whether it is registered with the network, and able
to send/receive packet data over the infrastructure). Modem
diagnostics can also be checked using the STS SW Diag-
nostics utility. Like RCP, RALP uses a separate socket from
the data socket and works in parallel to MDLC over the air
using a PPP connection.
The following parameters are relevant only if Enable RALP is set to Enable.
Get modem 0–255 10 The period of time (in seconds) to wait between checking
status sam- the status of the modem.
ple time
Restart mo- Disable / Enable If Restart modem when deregistered is set to Enable, the
dem when Enable modem is restarted each time it is detected that the modem
deregistered has been de-registered by the system. This makes the mo-

414
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
dem more reliable. However, MDLC data may be lost when
restarting the modem (until it initiates itself).

Table 81: Advanced Link Parameters for SI1 Port (PPP – ASTRO IV&D)

Parameter Allowed Default value Description

values
Context acti- Disable / Enable When set to Enable, the radio is context ac-
vate radio Enable tivated via SNMP and monitored according
to the following parameters.
The following parameters are relevant only if Context activated radio is set to Enable.
Get radio 0–255 10 As soon as the radio is context activated,
status sam- the RTU monitors it periodically to see that
ple time it is still context activated. This parameter
specifies how frequently (in seconds) the
RTU checks the radio.
SNMP Agent 0–65535 161 Specifies the UDP port number for setting
Port Number the SNMP context activate MIB variable in
the radio.
SNMP Trap 0–65535 162 Specifies the UDP port number for getting
Port Number traps from the radio via SNMP during con-
text activation.
SNMP Sock- 0–255 10 When the Context activate radio parame-
et timeout ter is enabled, the RTU sets the context ac-
(sec) tivate variable of a radio and monitors it via
an SNMP socket. This parameter specifies
how long (in seconds) to wait for a response
from the radio before declaring it failed. If
failed, the RTU reconfigures the radio, and
restarts it if needed.
Radio con- 0–255 30 Specifies how long (in seconds) to wait for
text activa- a radio to be context activated. If the time-
tion timeout out expires, the RTU reconfigures the radio,
(sec) and restarts it if needed.
Packet Data n/a .1.3.6.1.4.1.161.3 String identifying the MIB name for context
Status MIB .6.30.2.1.1.1 activating the radio. It is called packet data
name status (PDS) MIB.

415
6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.1.7
PLC Parameters for SI1 Port
Table 82: PLC Parameters for SI1 Port

Parameter Allowed values Default value Description

'No response' 2–200 10 For third-party protocols: Maximum time (in
time out milliseconds) to wait for the first character
when a reply is expected.
RAM size for 5000–1000000 20000 For third-party protocols: The amount (in
loaded PLC bytes) of RAM (workspace) required for
driver the downloadable module.
Maximum reply 2–200 70 For third-party protocols: The maximum
timeout from lo- time during which a reply should be ob-
cal PLC tained from the current MOSCAD or the
PLC connected to the PLC port of the cur-
rent MOSCAD. If a reply is not received
by the end of this period, MOSCAD starts
to receive the next command from SCADA
through the to Master port. The reply that
was not received is considered to be the
last.
Maximum reply 2–3000 300 For third-party protocols: The maximum
timeout from re- time during which a reply should be ob-
mote PLC tained from a remotely connected PLC
(MOSCAD as PLC). If a reply is not re-
ceived by the end of this period, MOSCAD
starts to receive the next command from
SCADA through the to Master port. The
reply that was not received is considered
to be the last.
Register map ● table=32 column=8 row=250 MODBUS to ACE3600 register mapping.
(default) Relevant for a third-party protocol port con-
figured as Connected to Master Comput-
● table=64 column=8 row=128 er when the corresponding PLC file was
downloaded. The two byte MODBUS reg-
ister/data type can be represented as a
16 bit number, which translates to z,x,y co-
ordinates (table#, column #, row # in the
ACE3600 database). The valid map values
are:
● table=32 column=8 row=250
up to 32 tables, 8 columns, 250 rows
(5, 3, 8 bits)
● table=64 column=8 row=128

416
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default value Description

up to 64 tables, 8 columns, 128 rows

(6, 3, 7 bits)
NOTE: For MODBUS on
ACE1000/MC-EDGE, the location
of registers is described in MC-
EDGE/ACE1000 MODBUS Con-
figuration on page 635.

Driver Specific 0–65535 0 For third-party protocols: These parame-

Parameter #1 ters are for passing up to ten parameters
to the PLC downloadable module: for Cli-
Driver Specific
ent (Master) or Server (Slave).
Parameter #2
Driver Specific
Parameter #3
Driver Specific
Parameter #4
Driver Specific
Parameter #5
Driver Specific
Parameter #6
Driver Specific
Parameter #7
Driver Specific
Parameter #8
Driver Specific
Parameter #9
Driver Specific
Parameter #10
Master commu- 0–86400 0 For third-party protocol MODBUS over
nication interval TCP/IP: The maximum time (in seconds)
during which a request is expected to be
received from the Client (Master). If no
communication occurs, the connection is
considered unstable.
Check alive Passive / Passive For third-party protocol MODBUS over
mode Active TCP/IP: Whether TCP is controlled by the
TCP stack of the operating system, or by
application. The valid values are:
● Active: TCP is controlled by the TCP
stack of the VxWorks operating sys-
tem. The MODBUS Server Slave) is
polled by the Client (Master)’s connec-
tion using the TCP socket’s ‘Check
alive’ option. If the idle time on the con-
nection exceeds 60 seconds, a ‘Check
alive’ probe is triggered. After the first

417
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default value Description

Check alive probe, a probe is sent ev-

ery 75 seconds (up to four times), un-
less a probe response is received. If no
probe response is received after send-
ing out four Check alive probes, the
TCP connection is dropped.
● Passive: TCP is controlled by the ap-
plication. In this case, the Check alive
timeout parameter must be set. The
application checks whether the server
received any communication until the
Check alive timer expires. If the Check
alive timeout parameter is set to 0, the
check alive mechanism is not used.

Check alive 0–65535 35 For third-party protocol MODBUS over

timeout TCP/IP (relevant only if Check alive mode
is set to Passive): The timeout (in sec-
onds) from the last communication re-
ceived from a Client (Master). If this pa-
rameter is set to 0, a Client (Master) is
always considered reachable as soon as a
single reception has been received from it.
Otherwise, the Server (Slave) RTU discon-
nects from the Client (Master).
TCP listen port n/a 502 For third-party protocol MODBUS over
TCP/IP: The TCP port used by the Serv-
er (Slave) for MODBUS communications.
The default value (502) is standard in TCP.
Therefore, retaining the default value is
highly recommended.
Connection cre- 0–65535 500 For third-party protocol MODBUS over
ate timeout TCP/IP: Timeout (in milliseconds) for an at-
tempt to create a connection between the
Client (Master) and Server (Slave).
Maximum num- 20–40 20 For third-party protocol MODBUS over
ber of connec- TCP/IP: The maximum number of connec-
tions tions between the Client (Master) and
Server (Slave).

A.1.2
SI2 Port (ACE3600, MC-EDGE T2)
The following section describes various SI2 port parameters.

A.1.2.1
SI2 Port Configurations
The port configurations available for the ACE3600 SI2 port are identical to the RS-232, Async configurations
available for the SI1 Port. See ACE3600 SI1 Port Configurations on page 398. The port configurations

418
 6802979C10-BA
Appendix A: Site Configuration Parameters

available for MC-EDGE T2 SI2 port are identical to those available for the SI1 port. See ACE1000/MC-EDGE
SI1 Port Configurations on page 399.

A.1.2.2
SI2 Port Parameters
The SI2 port parameters are identical to those of the SI1 port. See SI1 Port Parameters on page 396.
NOTE: For the ACE3600 SI2 port Media parameter, only RS-232 is available (the ACE3600 SI1 port is
configurable as either RS-232 or RS-485).

419
6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.2.3
Link Parameters for SI2 Port
The link parameters of the SI2 port are identical to those of the SI1 port. See Link Parameters for SI1 Port on
page 400.

A.1.2.4
Advanced Physical Parameters for SI2 Port
The advanced physical parameters of the SI2 port are identical to those of the SI1 port. See Advanced
Physical Parameters for SI1 Port on page 403.

A.1.2.5
Advanced Link Parameters for SI2 Port
The advanced link parameters of the SI2 port are identical to those of the SI1 port. See Advanced Link
Parameters for SI1 Port on page 408.

A.1.2.6
PLC Parameters for SI2 Port
The PLC parameters of the SI2 port are identical to those of the SI1 port. See PLC Parameters for SI1 Port
on page 416.

A.1.3
SI2/SI3 Ports (MC-EDGE T3)
The configurations and parameters available for the SI2 and SI3 ports on the MC-EDGE T3 are identical to
those available for the PI1 and PI2 ports on the ACE1000. The physical and link parameters of these ports
are also identical to the corresponding ACE1000 PI1/PI2 ports.
See PI1/PI2 Ports (ACE3600 and ACE1000) on page 420.

A.1.4
PI1/PI2 Ports (ACE3600 and ACE1000)
PI1 and PI2 are plug-in ports designed for various radio or line communications. For more information on
plug-in ports, see the ACE3600 RTU Owner’s Manual or the ACE1000 RTU Owner’s Manual.

A.1.4.1
PI1/PI2 Port Parameters
The ACE1000 PI1/PI2 port parameters are identical to those of the SI1 port. See Table 68: ACE1000/MC-
EDGE SI1 Port Parameters on page 397.

420
 6802979C10-BA
Appendix A: Site Configuration Parameters

All of the RS-232 (Async) and RS-485 port parameters of the ACE3600 SI1 port (see Table 67: ACE3600
SI1 Port Parameters on page 396) apply to the PI1/PI2 ports as well. In addition, the ACE3600 PI1/PI2 ports
include the parameters listed in the following tables.

Table 83: Available Media Types for ACE3600 PI1/PI2 Ports

Parameter Allowed/default values

Media ● Radio
● RS-232
● RS-485 (see SI1 Port Parameters on page 396)
● 10/100BT (see Table 87: ACE3600 PI1/PI2 Port Parameters for 10/100 BT Media on
page 423)
● Not used (default)

Operation For RS-232 media type only:

Mode ● Async (default; see SI1 Port Parameters on page 396)
● Sync (see Table 86: ACE3600 PI1/PI2 Port Parameters for RS-232 Media, Sync
Mode on page 422)

Radio Sys- ● Conventional (default; see Table 84: ACE3600 PI1/PI2 Port Parameters for Conven-
tem tional Radio on page 421)
● Trunking (see Table 85: ACE3600 PI1/PI2 Port Parameters for Trunked Radio on
page 422)

Table 84: ACE3600 PI1/PI2 Port Parameters for Conventional Radio

Parameter Allowed/default values

Radio Type ● HT750/GP320/PRO5150 (default)
● CM200/CM140/EM200/GM3188
● GM328/338/GM339/GM340
● CDM750
● General radio
● APX6500li
● XPR5350

Max. no. of ● No repeater (default)

repeaters
● 1 repeater
● 2 or more repeaters

Modem ● HT750/GP320/PRO5150: DPSK

● CM200/CM140/EM200/GM3188: FSK, DPSK
● GM328/338/GM339/GM340: FSK, DPSK
● CDM750: DFM, FSK, DPSK
● General radio: COS, DFM, FSK, DPSK

421
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed/default values

● APX6500li: DPSK
● XPR5350: FSK, DPSK
NOTE: For all conventional radios, DPSK is the default Modem setting.

Table 85: ACE3600 PI1/PI2 Port Parameters for Trunked Radio

Parameter Allowed/default values

Radio Type ● XTL 2500/5000 Trunked Analog (default)
● General radio
● APX6500li

Trunk system For XTL2500/5000 Trunked Analog:

● SmartNet (default)
● Simulcast
● SmartZone
For General radio:
● SmartNet
● Simulcast
● SmartZone
● General system (default)
For APX6500li:
● SmartNet (default)
● Simulcast
● SmartZone
Modem ● XTL 2500/5000 Trunked Analog: DPSK
● General radio:
○ SmartNet/General system: FSK, DPSK
○ Simulcast/SmartZone: DPSK
● APX6500li: DPSK
NOTE: For all trunk systems, DPSK is the default Modem setting.

Table 86: ACE3600 PI1/PI2 Port Parameters for RS-232 Media, Sync Mode

Parameter Allowed/default values

Connection ● External modem (DTE) (default)
Type
● RTU as DCE
● RTU as DCE with RxClk input
● RTU-to-RTU

422
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed/default values

Connection For External modem (DTE):
Mode ● Full-duplex
● Multi-drop half-duplex with CD (default)
For all other Connection Type settings:
● Full-duplex

Table 87: ACE3600 PI1/PI2 Port Parameters for 10/100 BT Media

Parameter Allowed/default values

Media ● 10/100 BT (PI1 only)
● 10 BT (PI2 only)

Address mode ● DHCP Client (default)

● Static LAN

Connection type Ethernet

Connected to For 10/100 BT:
● LAN (default)
● MotoTrbo Connect Plus XRT Gateway

A.1.4.2
ACE3600 PI1/PI2 Port Configurations
The PI1/PI2 ports can be configured with all of the RS232 (Async) and RS485 port configurations available
for the SI1 port. In addition, PI1/PI2 ports include the following port configurations not applicable to the SI1
port (see table).
For a summary of the SI1 RS232 (Async) and RS485 port configurations that also apply to PI1/PI2 ports, see
ACE3600 SI1 Port Configurations on page 398.

Table 88: ACE3600 Additional PI1/PI2 Port Configurations

Configuration Description
RS232, Sync, RTU-to- For local connection to another RTU via RS232 in synchronous mode. No
RTU (MDLC) hardware flow control.
RS232, Sync, For connection to an external modem via RS232 in synchronous mode over
External modem MDLC protocol (the RTU acts as Data Terminal Equipment):
(DTE) ● Modem can be full-duplex or multi-drop half-duplex with CD.
● Uses hardware flow control.
● The RTU receives both transmit and receive clocks from the partner mo-
dem/RTU.

RS232, Sync, RTU as For interface between the network and user Data Terminal Equipment via
DCE RS232 in synchronous mode over MDLC protocol (the RTU acts as DCE):
● Uses hardware flow control.

423
6802979C10-BA
Appendix A: Site Configuration Parameters

Configuration Description

● The RTU sends both transmit and receive clocks.

RS232, Sync, RTU as For local connection via RS232 in synchronous mode over MDLC protocol to
DCE with RxClk input another RTU as DCE with RxClk input:
● Uses hardware flow control.
● Each RTU sends its transmit clock and receives its receive clock.

Radio, Conventional, Direct FM modulation for conventional radio. For the Radio Type, Max. number
<Radio Type>, of repeaters, and Modem parameters, select the preferred value from the
<Max. number drop-down list. If the preferred value is not included in a particular list, select
of repeaters>, the "General" parameter (for example, the General Radio setting for the Radio
<Modem> Type parameter).
Radio, Trunking, Trunked radio. For the Radio Type, Trunk system, and Modem parameters,
<Radio Type>, select the preferred value from the drop-down list. If the preferred value is not
<Trunk system>, included in a particular list, select the “General” parameter (for example, the
<Modem> General Radio setting for the Radio Type parameter).
10/100 BT, DHCP Cli- For Ethernet communication over LAN with a DHCP-supplied IP address.
ent, Ethernet, LAN
10/100 BT, Static For Ethernet communication over LAN with a static IP address.
LAN, Ethernet, LAN
10/100 BT, Static For Ethernet communication over LAN with a static IP address, as an XRT
LAN, Ethernet, Client device connected to an XRT Gateway.
MotoTrbo Connect
Plus XRT Gateway

A.1.4.3
ACE1000 PI1/PI2 Port Configurations
All of the RS-232 (Async) port configurations available for the ACE1000 SI1 port (see ACE1000/MC-EDGE
SI1 Port Configurations on page 399) also apply to the PI1/PI2 ports. In addition, the ACE1000 PI2 port
includes the following RS485 port configurations (see table).
NOTE: No RS-485 port configurations are available for the ACE1000 PI1 port.

Table 89: RS485 Port Configurations for ACE1000 PI2 Port

Configuration Description
RS485, MDLC, For local connection to another RTU via RS485 in asynchronous mode over
RTU-to-RTU MDLC protocol (can also be used for communication with STS).

RS485, User port For use when the RS485 port is to be controlled by the user application. Not
available for ACE IP Gateway.
For further details, see User Defined Local Ports on page 597.

424
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.4.4
Link Parameters for PI1/PI2 Ports
When the PI1/PI2 ports are defined as RS-232 (Async) or RS-485, the associated link parameters are
identical to those of the corresponding SI1 port configurations (see Link Parameters for SI1 Port on page
400). The following table lists the parameters that apply to PI1/PI2 ports in configurations other than RS-232
(Async) or RS-485.
NOTE: Certain parameters for the Radio, RS-232 (Sync), and 10/100 BT media may have different
defaults.

Table 90: Additional Link Parameters for PI1/PI2 Ports

Parameter Allowed/default values Description

Links... LINE 1 – LINE 29 ACE3600 only: Opens the list of multiple IP
Default: LINE 1 links used by this port (replaces the Link name
field for IP ports).
To add a link, select it and click Add. To remove
a link, select it and click Remove. To save the
list, click OK. Relevant for PPP connection type
only.
NOTE: When more than one link is se-
lected, the Advanced Link Layer param-
eters can be configured separately for
each link by clicking the Advanced
Configuration... button.

Zones... RADIO1/1 – RADIO1/9 The Zones... button is available when config-

Default: RADIO 1/1 uring conventional radio port type parameters.
Click the button to open the Define Zones dia-
log box.
To add a zone, select it and click Add.
To remove a zone, select it and click Remove.
To save the list and close the Define Zones
dialog, click OK.
For more information about zones, see:
● Two-Zone System on page 71
● Multiple Zone Systems on page 72

Host full n/a For 10/100 BT DHCP Client connections: The

name name of the host (such as www.mysite.com) that
is registered in the DHCP server, which enables
other RTUs to communicate with the host name.
For details, see “Dynamic Configuration over IP
using DHCP” in the MC-IoT STS Advanced Fea-
tures manual.
Self 0.0.0.0 – 255.255.255.255 For 10/100 BT Static LAN connections: The IP
IP Address Default: 0.0.0.0 address of this Ethernet port. This parameter is
0.0.0.0 by default. Do not change this value; it
is read from the modem when it is connected.1

425
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed/default values Description

In redundant sites, the Self IP Address must be
a unique value on the same segment.

Default 0.0.0.0 – 255.255.255.255 For 10/100 BT Static LAN connections: the IP

routing IP Default: 0.0.0.0 Address of the default router/the home agent
address of the iDEN infrastructure. This parameter is
000.000.000.000 by default. Do not change
this value; it is read from the modem when it is
connected.1
IP network 0.0.0.0 – 255.255.255.255 For 10/100 BT Static LAN connections: the sub-
mask Default: 0.0.0.0 net mask assigned to the port. This parameter is
000.000.000.000 by default. Do not change
this value; it is read from modem when it is con-
nected.1
DNS 0.0.0.0 – 255.255.255.255 For 10/100 BT and PPP connections: a list of up
Servers Default: 0.0.0.0 to three DNS server IP addresses. To add an IP
address, enter it in xxx.xxx.xxx.xxx format.
To remove an address, reset to 0.0.0.0
To save the list, click OK.
NTP n/a For 10/100 BT and PPP connections: a list of
Servers up to four NTP server/options. To add an entry,
enter the server and option in one of the four
fields. To remove an entry, erase the server and
option.
To save the list, click OK.

Protocols... n/a ACE3600:

Opens the Select Protocols to Support dialog
for configuring third-party protocols over an IP
port. For MODBUS over TCP/IP connections,
select Modbus Slave. To save the changes and
close the dialog, click OK.
ACE IP Gateway:
Opens the Select Protocols to Support dialog
for configuring SCADA support over an IP port
(10/100 BT, Static LAN only). For SCADA con-
nections, select SCADA. To save the changes
and close the dialog, click OK.

1For details, see “IP Communication” in the MC-IoT STS Advanced Features manual.

A.1.4.5
Advanced Physical Parameters for PI1/PI2 Ports
The advanced physical parameters associated with the SI1 port also apply to the PI1/PI2 ports (see
Advanced Physical Parameters for SI1 Port on page 403). In addition, the advanced physical parameters
in the following tables are available for PI1/PI2 ports in configurations other than RS-232 (Async) or RS-485.
The following table contains parameters pertaining to certain RS-232 (Sync) and Radio media types:

426
 6802979C10-BA
Appendix A: Site Configuration Parameters

Table 91: Additional Advanced Physical Parameters for PI1/PI2 Ports (Miscellaneous)

Parameter Allowed Default Description

values value
Minimum number of flags 0–15 0 Number of HDLC flags between frame
between HDLC frames transmissions.

The following table contains parameters pertaining only to ports defined as media type Radio.

Table 92: Additional Advanced Physical Parameters for PI1/PI2 Ports (Radio)

Parameter Allowed values Default Description

value
Channel ● CM CM When applicable, specifies which signal is used to
busy indica- declare a channel busy (channel busy indication
tion ● CM&TD technique used for radio ports). Can be Channel
● TD Monitor (CM), Tone Detect (TD), or both (CM&TD).
CM can be set to Active Low or Active High (see
PTT polarity later in this section).
Consequent 10–2500 350 In subsequent sessions (after the first warm up de-
warm up lay), specifies the delay (in milliseconds) between
delay a transmission request (PTT press) and the start
of data transmission in trunked systems. The value
should be greater than or equal to the First Warm
Up Delay, because the first time the trunked sys-
tem performs part of the warm up by itself. See the
previous parameter.
Disconnect 100–500 200 In a trunked system, specifies the period of time (in
time milliseconds) that should elapse after releasing the
PTT, and before the radio is ready for reception.
Channel re- 500–1000 500 In a trunked system, specifies the maximum peri-
quest PTT od of time (in milliseconds) during which the PTT
active time should be pressed in order to access a channel.
Channel re- 5000–10000 5000 In a trunked system, the PTT pressing time cycle
quest cycle (in milliseconds) until a channel is accessed.
time (Channel request PTT active time / Channel re-
quest cycle time = the PTT active duty cycle.)

Tx level 0–47 32 Sets the transmission modulation level to the radio.

Applies to General radio.
PTT polarity Active Low / Ac- Active Relates to radio channel busy criteria and the re-
tive High High ception conditions for Channel Monitor. Polarity
should be set based on the digital signal used by
the radio (see radio specifications).
Channel 0–320000 0 For radio ports, the maximum waiting time (in milli-
monitor over- seconds) for a channel. After this timeout, the sys-
ride delay tem accesses a channel whether or not it is free.
When set to 0 (default), this feature is disabled
(meaning that the RTU does not transmit if the
channel is busy).

427
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default Description

value
Time before 0–3000 0 In Smartzone trunked systems, this parameter
long warm up specifies the on channel/free channel condition (in
milliseconds) which, if exceeded, requires a longer
warm up. Specify 0 to ignore this parameter.
Long warm 0–2500 0 Specifies the long warm up time (in milliseconds).
up Relevant when that the Time before long warm up
parameter is enabled (set to a value greater than
0). Recommended value in Smartzone systems is
1000
Time resolu- 50–1000 50 In a trunked system, this parameter specifies the
tion in con- size of the time slot (in milliseconds) during which
trol channel the radio is on the control channel trying to gain
transmit permission (TXE). PTT will be pressed af-
ter a period of time equal to the current slot number
multiplied by this parameter.
Tone detect 0–255 132 For trunked General radio, the level of the Tone
level Detect (TD) audio signal used to detect radio RF
activity.

The following table contains parameters pertaining to 10/100 BT media configured as a DHCP Client.

Table 93: Additional Advanced Physical Parameters for PI1/PI2 Ports (DHCP Client)

Parameters Allowed Default Description

values value
Notify host name Disable / Enable If enabled, the RTU requests the DHCP server to in-
to DNS server Enable form its DNS server (if one exists) of the new allocated
address and the fully qualified domain name that it
should have. This name is built from the domain name
that was configured for this RTU.
DHCP client n/a n/a A unique identifier that is used to identify the RTU
unique ID (MAC) within the DHCP server.
DHCP client class n/a n/a Class identifier that identifies the RTU class within the
ID DHCP server.
DHCP client lease 0–65535 3600 How frequently (in seconds) the IP address of the
renewal DHCP client is renewed in the DHCP server.
interval in sec

DHCP notify Style ASCII / ASCII The fully qualified domain name can be built in either
for DNS server DNS ASCII or DNS-style format.

The following table contains parameters pertaining to 10/100 BT media configured for connection to
MotoTrbo Connect Plus XRT Gateway.

428
 6802979C10-BA
Appendix A: Site Configuration Parameters

Table 94: Additional Advanced Physical Parameters for PI1/PI2 Ports (XRT Gateway)

Parameter Allowed values Default Description

value
XRT Gateway IP 0.0.0.0 – 0.0.0.0 IP Address of the XRT Gateway. Only one
Address 255.255.255.255 address is allowed per physical port. The
RTU is an XRT Client and connects with
the specified IP address using XRT Client
protocol.
XRT Gateway 1–65535 10001 TCP port to connect with in XRT Gateway.
TCP port The RTU is an XRT Client and connects
with the specified TCP port using XRT Cli-
ent protocol.
XRT Client data 0–16776413 0 Subscriber ID configured in XRT Gateway
path ID for this RTU. Set to 0 if identical to the RTU
Site ID.
XRT Client con- 1–60 10 Time (in seconds) to wait for the connection
nect timeout with the XRT Gateway to succeed. If no
connection is established, a retry is made
after this timeout. When powering up or
connecting the radio cable, this continues
periodically until connection succeeds. If af-
ter 2 minutes the connection is failed, an
error is logged.
XRT Client idle 0–65535 0 Timeout (in milliseconds) to declare end of
time to declare reception. After this timeout, the process re-
end reception ceives bytes from the XRT. If set to 0, the
(milliseconds) default value is used.
XRT Client trans- 16–64 32 Maximum number of requests that can be
mit queue size queued before being sent to the XRT. Re-
served for future use.
XRT Client pack- 1–65535 210 When transmitting a raw data request and
et data request getting no response from XRT, the timeout
fail timeout (sec- (in seconds) to declare a transmit failed.
onds)

A.1.4.6
Advanced Link Parameters for Ports PI1/PI2
The advanced link parameters associated with the SI1 port also apply to the PI1/PI2 ports (see Advanced
Link Parameters for SI1 Port on page 408). In addition, the port parameters in the following table are
available for PI1/PI2 ports in configurations other than RS-232 (Async) or RS-485.

Table 95: Additional Advanced Link Parameters for PI1/PI2 Ports

Parameter Allowed Default Description

values value
Wait for DHCP 1–255 30 For 10/100BT DHCP connections: Number of seconds
lease timeout to wait for a DHCP lease from the DHCP server.

429
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
Enable non-IP Disable / Enable For 10/100 BT static LAN connection to a MotoTrbo
communication Enable XRT Gateway: When enabled, the Link ID associated
to XRT Gateway with the XRT Gateway is dedicated to MotoTrbo XRT
non-IP communication with other RTUs on Connect Plus
radios. In the IP Conversion Table the addresses for that
Link ID are non-IP subscriber IDs. When disabled, the
Link ID associated with the XRT Gateway is MDLC over
LAN. In the IP Conversion Table the IP addresses are
associated with that Link ID.

A.1.4.7
PLC Parameters for PI1/PI2 Ports
The PLC parameters associated with the PI1/PI2 ports are identical to those of the SI1 port. See PLC
Parameters for SI1 Port on page 416.

A.1.5
ETH1/ETH2/ETH3 Ports
ACE3600, ACE1000, and MC-EDGE T1/T3 each include one Ethernet port (ETH1). Only the MC-EDGE T2
includes ETH2 and ETH3 ports.

A.1.5.1
ETH1/ETH2/ETH3 Port Parameters
Table 96: ETH1/ETH2/ETH3 Port Parameters

Parameter Allowed values

Media 10/100 BT
Address mode ● DHCP Client (default)
● Static LAN
● I/O Expansion Comm. (ACE3600 only)
NOTE: For ACE3640: If at least one expansion frame is defined,
then the ETH1 port must be defined as either I/O Expansion
Comm. (recommended setting) or Static LAN. If the port is config-
ured as DHCP Client, an error message prompts the user to
change the Address mode to I/O Expansion Comm.

Connection type ● Ethernet

● Ethernet - IPsec tunnel (MC-EDGE only)

Connected to ● LAN
● MOTOTRBO Connect Plus XRT Gateway (ACE36000 only, for Static
LAN)
● MOTOTRBO MNIS Data Gateway (MC-EDGE only, for Static LAN)

430
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.5.2
ETH1/ETH2/ETH3 Port Configurations
Table 97: General ETH1/ETH2/ETH3 Port Configurations

Configuration Description
Not used The specified port is not in use. Setting a port to Not used
frees any resources that might otherwise be allocated to the
port.
NOTE: For MC-EDGE T1 and T2, the ETH1 port can-
not be set to Not used.

10/100 BT, DHCP Client, For Ethernet communication over LAN using a DHCP-supplied
Ethernet, LAN IP address.

10/100 BT, Static LAN, Ethernet, LAN For Ethernet communication over LAN using a static IP ad-
dress. This is the default port configuration for ACE IP Gate-
way, MC-EDGE and ACE1000.
10/100 BT, Static LAN, Ethernet, Mo- For Ethernet communication as an XRT Client device connect-
toTrbo Connect Plus XRT Gateway ed to an XRT Gateway, over LAN using a static IP address.
10/100 BT, Static LAN, Ethernet, Mo- MC-EDGE only: For Ethernet communication with the MotoTr-
toTrbo MNIS Data Gateway bo data core component, over LAN using a static IP address.
10/100 BT, I/O Expansion Comm., ACE3600 only: For Ethernet communication over LAN in a
Ethernet, LAN system with I/O expansion, using a predefined static IP ad-
dress.

NOTE: If the ACE3600 site includes expansion frames, the ETH1 port cannot be set to Not used or
DHCP Client. The recommended configuration for ETH1 is I/O Expansion Comm.
In addition to the configurations listed in the previous table, the MC-EDGE includes the following ETHx port
configurations.

Table 98: MC-EDGE Ethernet IPsec Port Configurations

Configuration Description
10/100 BT, DHCP Client, Ethernet - IP- For Ethernet communication over IPsec VPN using a DHCP-
sec tunnel, LAN supplied IP address.
10/100 BT, Static LAN, Ethernet - IP- For Ethernet communication over IPsec VPN using a static IP
sec tunnel, LAN address.
10/100 BT, Static LAN, Ethernet - IP- For Ethernet communication as an XRT Client device connect-
sec tunnel, MotoTrbo Connect Plus ed to an XRT Gateway, over IPsec VPN using a static IP
XRT Gateway address.
10/100 BT, Static LAN, Ethernet - IP- For Ethernet communication with the MotoTrbo data core com-
sec tunnel, MotoTrbo MNIS Data Gate- ponent, over IPsec VPN using a static IP address.
way

431
6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.5.3
Link Parameters for ETH1/ETH2/ETH3 Ports
The link parameters associated with the ETH1/ETH2/ETH3 ports are identical to those of the PI1/PI2 ports
defined as 10/100 BT (see Link Parameters for PI1/PI2 Ports on page 425). MC-EDGE IPsec configurations
include an additional link parameter, Remote gateway, which is mandatory.
NOTE: When configured for I/O expansion communication, the ACE3600 ETH1 port does not include
the DNS Servers, NTP Servers, and Protocols... parameters.

A.1.5.4
Advanced Physical Parameters for ETH1/ETH2/ETH3 Ports
The advanced physical parameters associated with ETH1/ETH2/ETH3 ports are identical to those of PI1/PI2
ports configured for 10/100 BT connectivity. See Advanced Physical Parameters for PI1/PI2 Ports on page
426.

A.1.5.5
Advanced Link Parameters for Port ETH1/ETH2/ETH3
The advanced link parameters associated with ETH1/ETH2/ETH3 ports are identical to those of PI1/PI2 ports
configured for 10/100 BT connectivity. See Advanced Link Parameters for Ports PI1/PI2 on page 429.

A.1.5.6
PLC Parameters for Port ETH1/ETH2/ETH3
The PLC parameters associated with the ETH1/ETH2/ETH3 ports are identical to those of SI1/SI2 ports
configured for third party protocols over TCP/IP. See PLC Parameters for SI1 Port on page 416.
NOTE: To access the PLC parameters, the relevant protocol must be enabled in the Select Protocols
to Support dialog. For more details, see the Protocols parameter in Link Parameters for SI1 Port on
page 400.

A.1.5.7
MC-EDGE Advanced IPsec Parameters
For specific information on the usage of certain parameters, see Advanced IPsec Parameters – Usage Notes
on page 435.

Table 99: Advanced IPsec Parameters

Parameter Allowed Values Default Value Description

Remote gateway N/A N/A The Address or fully qualified host
name of the firewall to establish a
tunnel with
Remote Subnet IP / 0 – 33 0.0.0.0/0 Remote Subnet in a site organiza-
tion
Remote ID N/A N/A Remote participant identifier for au-
thentication (i.e. IP address, a fully-
qualified domain name, etc.)

432
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Values Default Value Description

Manual VPN IP 000.000.000.000 – 0.0.0.0 Defines the source IP address of
255.255.255.255 the internal (site-to-site) VPN tun-
nel.
When set to 0.0.0.0 (default), the
source IP is the virtual source IP.
In this case, the tunnel serves as
a remote access client (initiator)
dependent on the remote gateway
(responder) to generate a virtual IP
address.
NOTE: Available in STS
version 27.00 and above.

Local ID N/A Unique identifier Local participant identifier for au-

is generated auto- thentication (i.e. IP address, a fully-
matically. qualified domain name, etc.)
IKE Version V1 / V2 V1 Key exchange protocol version
used to initialize the connection:
IKEv1 or IKEv2
Negotiation Main mode / Main mode IKEv1 Phase 1 negotiation mode:
mode Aggressive mode Main Mode or Aggressive Mode

Authentication Pre-Shared Key / RSA Authentication via a pre-shared se-

mode RSA cret key (PSK) or a public key sys-
tem (RSA)
Pre-shared key 8..32 characters N/A Pre-shared secret key for PSK au-
thentication
XAUTH Enable / Disable Disable Extended authentication protocol
XAUTH User ID N/A N/A User identity for extended authenti-
cation protocol
XAUTH User N/A N/A Password for extended authentica-
Password tion protocol
Encryption algo- 3des / aes128 / aes256 ESP encryption algorithm to be
rithm aes192 / aes256 used for connection
Authentication md5 / sha1 / sha2_256 ESP authentication algorithm to be
algorithm sha2_256 used for connection
Diffie-Hellman Group1 / Group2 / Group 2 The Diffie-Hellman group for IKE
group for IKE Group5 / Group14 –
Group31
Perfect Forward Enable / Disable Disable Enables Perfect Forward Secrecy
Secrecy of keys on the keying channel of the
connection
Protocols ESP ESP Authentication and encryption pro-
tocols used by IPsec
Dead Peer De- Enable / Disable Disable Enables Dead Peer Detection pro-
tection tocol

433
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Values Default Value Description

Dead Peer De- 1–180 180 Defines the timeout interval (in sec-
tection timeout, onds) after which all connections to
sec a peer are deleted in case of inac-
tivity
Dead Peer De- 1–30 30 Defines the interval (in seconds)
tection delay, between consecutive R_U_THERE
sec messages/INFORMATIONAL ex-
changes with the peer.
Phase 1 key 30 - 86400 86400
lifetime <30 –
86400> sec
Phase 2 key 30 – 86400 3600
lifetime <30 –
86400> sec

Table 100: Advanced IPSec Optional Tunnel 1-3 Parameters

There is an option to create up to four IPSEC Tunnels on a single port.

Parameter Allowed Values Default Value Description

Remote gateway N/A N/A The Address or fully
qualified host name of
the firewall to establish
a tunnel with
Remote Subnet IP / 0 – 33 0.0.0.0/0 Remote Subnet in a
site organization
Remote ID N/A N/A Remote participant
identifier for authentica-
tion (i.e. IP address,
a fully-qualified domain
name, etc.)
Manual VPN IP 000.000.000.000 – 0.0.0.0 Defines the source IP
255.255.255.255 address of the internal
(site-to-site) VPN tun-
nel.
When set to 0.0.0.0
(default), the source IP
is the virtual source IP.
In this case, the tunnel
serves as a remote ac-
cess client (initiator) de-
pendent on the remote
gateway (responder) to
generate a virtual IP
address.
NOTE: Availa-
ble in STS ver-
sion 27.00 and
above.

434
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.5.8
Advanced IPsec Parameters – Usage Notes
Connection IDs
By default, the connection ID strings are empty. During each connection, the peer attempts to identify the
remote ID and local ID.

Phase 1 Authentication Method

Phase 1 negotiations begin with authentication via either RSA public key or a pre-shared key. The default
setting for MC-EDGE is RSA Authentication. The requirements for using each authentication method are
listed in the following table.

Table 101: Phase 1 Authentication Methods and Requirements

Authentication method Requirement

RSA User must generate an IPsec peer key, peer certifi-
cate, and CA Certificate, and download them to the
RTU.
Pre-shared key User enters a 32-string shared secret

Phase 2 Extended Authentication Method

If XAUTH is enabled, extended authentication is required during Phase 2 negotiations. XAUTH can be
applied to both IKEv1 and IKEv2 connections.

Protocols
Only Encapsulating Security Payload (ESP) protocol is supported. MC-EDGE does not support IPsec
Authentication Header (AH) protocol.

Perfect Forward Secrecy

When Perfect Forward Secrecy (PFS) is enabled, the same Diffie-Hellman (DH) group serves both IKE and
PFS.

Encryption and Authentication Algorithm

The user can choose from several encryption and authentication methods. However, MC-EDGE (R8.0) uses
the same encryption and authentication algorithms (chosen by the user) during both Phase 1 (IKE) and
Phase 2 (ESP) negotiations. The user cannot choose distinct algorithms for the different phases of IPsec
negotiation.

435
6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.5.9
Port Protocols for ETH1/ETH2/ETH3
ACE3600 supports MODBUS protocol; ACE1000 and MC-EDGE support both MODBUS and DNP protocols.
For further information, refer to the MC-IoT STS Third Party Protocols Manual.

Table 102: Protocols over ETH1/ETH2/ETH3 Ports

Protocol Description
DNP Client (Master) ACE1000/MC-EDGE only: For connecting the RTU to SCADA systems
based on DNP protocol.
DNP Server (Slave)
MODBUS Server (Slave) For connecting the RTU to SCADA systems based on MODBUS protocol.
MODBUS Client (Mas- For connecting with a PLC.
ter)

A.1.6
HU1/HU2 Ports (ACE3600)
A.1.6.1
HU1/HU2 Port Parameters
Table 103: HU1/HU2 Port Parameters

Parameter Allowed values

Media USB Host
Operation Mode Async
Connection type ● Remote NDIS Host (default)
● Serial USB Host (non-IP)

Connected to ● MotoTrbo (Remote NDIS Host only)

● Mototrbo connect plus radio [Serial USB Host (non-IP) only]

436
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.6.2
HU1/HU2 Port Configurations
Table 104: HU1/HU2 Port Configurations

Configuration Description
Not used The specified port is not in use. Setting a port to Not used frees any
resources that might otherwise be allocated to the port.
NOTE: If one Host USB port is set to Not used but the other
Host USB port is used for MOTOTRBO™, both ports are ena-
bled for USB communication. This is because they are both
connected via the USB root hub. If the Host USB port detects
that a MOTOTRBO radio is connected to it, even though the
port is set to Not used in the parameters, the following occurs:
● The port LED is illuminated (which is reflected in the SW di-
agnostic).
● The port cannot connect to the radio.

USB Host, Async, Remote For connection to MOTOTRBO radio in digital mode (as a raw IP de-
NDIS Host, MotoTrbo vice).
USB Host, Async, Serial USB For connection to MOTOTRBO Connect Plus radio (as a raw non-IP
Host (non IP), MotoTrbo Con- device).
nect Plus Radio

A.1.6.3
Link Parameters for HU1/HU2 Ports
The link parameters for the HU1/HU2 ports include Links..., DNS Servers, and NTP servers. These
parameters are identical to those of the SI1 port.
See Link Parameters for SI1 Port on page 400.

A.1.6.4
Advanced Physical Parameters for HU1/HU2 Ports
The following tables list the advanced physical parameters for HU1/HU2 ports. The first table (General)
includes those parameters which pertain to HU1/HU2 ports in all configurations. The parameters in the
second table apply only to ports configured as Serial USB Host (non IP) for connection to Connect Plus
radios.

Table 105: Advanced Physical Parameters for HU1/HU2 Ports (General)

Parameter Allowed Default Description

values value
Number of input 1–1024 64 The number of buffers for the USB and RNDIS layers to
buffers be used for receiving data.1
Number of out- 1–1024 64 The number of buffers for the USB and RNDIS layers to
put buffers be used when transmitting data.1

437
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
KeepAlive time- 0–65535 5 The interval at which the RTU polls the MotoTrbo radio to
out period (sec- check the connectivity status.1
onds)

Table 106: Advanced Physical Parameters for HU1/HU2 Ports (Serial USB Host)

Parameter Allowed Default Description

values value
Radio connect 1–60 10 Time (in seconds) to wait for the connection to the
timeout (sec- radio to succeed. If the radio is not connected after
onds) this timeout elapses, a retry is made. When powering
up or connecting the radio cable, this continues peri-
odically until connection succeeds. If the connection
fails after 2 minutes, an error is logged.
Radio idle time 0–255 0 Time (in milliseconds) before declaring the end of
to declare end re- reception. After this timeout elapses, the process re-
ception (millisec- ceives bytes from the radio. When set to 0, the de-
onds) fault value is used.
Radio minimal 1–60 1 If the radio does not acknowledge the transmission,
time to retry (sec- the time (in seconds) to wait before retrying. This is
onds) relevant to XCMP/XNL communication with the radio
itself, and does not pertain to communication over
the air.
Radio request 1–65535 10 When a request is sent but a response is not re-
fail timeout (sec- ceived from the radio, the time (in seconds) to wait
onds) before declaring failure. This is relevant to communi-
cation with the radio itself, and does not pertain to
communication over the air. Unlike the Radio minimal
time to retry (seconds) parameter, this pertains to an
XCMP data response, such as radio signaling level.
Radio packet 1–65535 30 When a raw data request is transmitted but a re-
data request sponse is not received from the radio, the time (in
fail timeout (sec- seconds) to wait before declaring the transmit a fail-
onds) ure. Unlike the Radio request fail timeout parameter,
this pertains to a XCMP data response, such as Data
reply or Data Broadcast. If no response received, the
connection is re-initiated after this time expires.
Radio minimum 1–10 5 After successful transmission of a raw data request
packet data re- to the radio, the time (in seconds) to wait before
quest interval sending the next one.
Radio transmit 16–256 32 The maximum number of XCMP requests that can
queue size be queued before being sent to the radio. This is
relevant to XCMP/XNL communication with the radio
itself, and does not pertain to communication over
the air.

1For details, see “MDLC over MotoTrbo” in the MC-IoT STS Advanced Features manual.

438
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.6.5
Advanced Link Parameters for HU1/HU2 Ports
The advanced link parameters of the ACE3600 HU1/HU2 ports are mostly identical to those of the ACE3600
SI1 port configured as RS-232, PPP connection type. See Advanced Link Parameters for SI1 Port on page
408. In addition, the following parameters (not relevant to the SI1 port) pertain to HU1/HU2 ports defined as
Serial USB Host (non IP) for connection to MOTOTRBO™ Connect Plus radio.
NOTE: The advanced link parameters for HU1/HU2 ports defined as Remote NDIS Host are wholly
encompassed by the corresponding SI1 parameters.

Table 107: HU1/HU2 Advanced Link Parameters for MotoTrbo Connect Plus

Parameter Allowed Default Description

values values
Radio configura- 1–255 30 When powering up the radio or RTU, the amount
tion timeout (sec) of time (in seconds) that the network waits for suc-
cessful connection to the radio. If the connection
is not established within this time, MOSCAD de-
clares the port failed (though configuration contin-
ues). Configuration fails in either of the following
situations:
● No connection with the radio exists
● The radio is connected but not registered (its
signaling mode is not Connect Plus, or RSSI is
lower than the threshold).
The configuration status can be checked in the
Error Logger and in the SW Diagnostics (Device:
LIN1L, Level: 0, 101).
Get radio status 1–255 10 After connection to the radio is established (via
sample time XCMP/XNL), the RTU periodically monitors the ra-
dio to ensure that it is still connected, that its sig-
naling mode is Connect Plus, and that the RSSI
is higher than the threshold value. This parameter
specifies how frequently (in seconds) to perform
this check.
Number of config- 0–255 3 This parameter is relevant whenever the RTU fails
uration attempts to connect with the radio. It specifies how many
to reset radio failed attempts to connect the modem are required
before restarting it. This parameter is reserved for
future use.
Wait time after Re- 0–255 5 This parameter specifies how long (in seconds)
set radio (sec) to wait after restarting the USB connection before
attempting to connect again. This parameter is re-
served for future use.
RSSI signal lev- 0–255 125 A value other than 0 signifies the threshold RSSI
el to declare level of the radio channel. As the signal level is
radio not regis- constantly monitored, any higher number indicates
tered <0:DISABLE that the RF coverage is low, or that the Connect
0-255> Plus controller is inoperative. Setting the parameter
to 0 disables this feature.

439
6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.7
USB (MC-EDGE) and USB1/USB2 (ACE1000) Ports
A.1.7.1
USB and USB1/USB2 Port Parameters
Table 108: Port USB1/USB2/USB Parameters

Parameter Allowed values

Media USB Host
Connection type Remote NDIS Host
Connected to ● ASTRO APX
● MOTOTRBO

A.1.7.2
USB and USB1/USB2 Port Configurations
Table 109: MC-EDGE USB and ACE1000 USB1/USB2 Port Configurations

Configuration Description
Not used The specified port is not in use. Setting a port to Not used frees any
resources that might otherwise be allocated to the port.
NOTE: If one USB Host port is set to Not used but the other USB
Host port is used for MOTOTRBO™, both ports are enabled for
USB communication. This is because they are both connected via
the USB root hub. If the USB Host port detects that a MOTOTRBO
radio is connected to it, even though the port is set to Not used in
the parameters, the following occurs:
● The port LED is illuminated (which is reflected in the SW diag-
nostic).
● The port cannot connect to the radio.

USB Host, Remote NDIS For connection to MotoTrbo radio in digital mode (as a raw IP device).
Host, MotoTrbo
USB Host, Async, Serial For connection to MotoTrbo radio in Connect Plus (as a raw non-IP device).
USB Host (non-IP),
MotoTrbo Connect Plus
Radio

USB Host, Remote NDIS For connection to ASTRO APX radio in digital mode.
Host, ASTRO APX

A.1.7.3
Advanced Link Parameters for USB and USB1/USB2 Ports
The advanced link parameters of the ACE1000 USB1/USB2 and MC-EDGE USB ports for connection type
Remote NDIS Host (for connection to MOTOTRBO™ and ASTRO® APX™), are identical to the advanced link

440
 6802979C10-BA
Appendix A: Site Configuration Parameters

parameters of the SI1 port for connection type PPP. See Advanced Link Parameters for SI1 Port on page
408.
The advanced link parameters of the ACE1000 USB2 and MC-EDGE USB ports for connection type Serial
USB Host (non IP) (for connection to MOTOTRBO Connect Plus) are identical to those of the ACE3600
HU1/HU2 ports. See Advanced Link Parameters for HU1/HU2 Ports on page 439.

A.1.8
APX Port (MC-EDGE)
A.1.8.1
APX Port Configurations
Table 110: Port APX Configurations

Configuration Description
Not used The specified port is not in use. Setting a port to Not used frees any resources
that might otherwise be allocated to the port.
MDLC The port is used for connection to ASTRO® APX™ radio in digital mode.

A.1.8.2
Advanced Link Parameters for APX Port
The advanced link parameters of the MC-EDGE APX port are identical to those of the SI1 port configured as
media type RS232 for PPP connection. See Advanced Link Parameters for SI1 Port on page 408.

A.1.9
LTE Port (MC-EDGE T1/T2)
A.1.9.1
LTE Port Parameters
Table 111: MC-EDGE LTE Port Parameters

Parameter Allowed values

Media ● Not used (default)
● LTE

Connection Type ● MDLC (default)

● MDLC+IPsec

441
6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.9.2
Advanced Physical Parameters for LTE Port
Table 112: Advanced Physical Parameters for LTE Port

Parameter Allowed Values Description

Cellular Tech- LTE LTE technology supported
nology
Operator parameters:
Operator Mode Automatic Automatic operator mode is supported – operator is automati-
cally selected according to the SIM card.
SIM card PIN N/A Personal identification number code
Code (4-8 digits) By default the parameter is empty, which means that no au-
thenticating user is used to access the LTE.
This field is used when the customer and the operator agree
to implement authenticating user access to the LTE network.

APN parameters:
In general, these APN fields are left empty. In some cases, however, certain LTE operators may require
the customer to enter these values in order to use the APN. If required to do so, follow the LTE operator
requirements and enter the parameters accordingly.

APN N/A Defines the LTE operator data Access Point Name.
In the event that the modem does not automatically connect
to the LTE operator, the user manually enters the default APN
name of the operator (such as "VZWINTERNET").

Authentication ● None (default) Protocol used for APN authentication.

method
● PAP
● CHAP

User name N/A N/A

Password N/A N/A
Keepalive Disable / Enable
Keepalive Host IP address or Host Host to ping to
IP name
Keepalive Peri- 10 - 60000 Intervals to perform the keepalive check
od <10-60000>
(sec)
Keepalive Retry 1 - 200 Retries to perform the keepalive check before resetting the
Threshold Modem
<1-200>
Keepalive Ping 1 - 10 Number of ICMP pings to send every keepalive check cycle
Count <1-10>
Keepalive Ping 1 - 10 Seconds to wait for the ICMP ping response
Response Time-
out <1-10>

442
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Values Description

3G Disable/Enable To allow only 4G LTE Network mode, user must disable 3G
Network mode.
MTU 0-1500 The MTU (Maximum Transmission Unit) size refers to the
maximum size of a packet that can be transmitted over an
LTE cellular network. For example, changing the MTU default
(1430) cellular size to 1500 with IPSec is necessary.

A.1.9.3
Advanced Link Parameters for Port LTE
The advanced link parameters associated with the MC-EDGE LTE port are identical to those of the ACE3600/
ACE1000 SI1 port configured for the PPP connection type. See Advanced Link Parameters for SI1 Port on
page 408.

A.1.9.4
Advanced IPsec Parameters for LTE Port
The advanced IPsec parameters associated with the MC-EDGE LTE port are identical to those of the ETH1/
ETH2/ETH3 ports. Screen reader support is enabled. See MC-EDGE Advanced IPsec Parameters on page
432.

A.1.9.5
Port Protocols for LTE
The MC-EDGE LTE port supports MODBUS and DNP protocols. For further information, see the MC-IoT STS
Third Party Protocols Manual.

Table 113: Port Protocols for MC-EDGE LTE Port

Protocol Description
DNP Client (Master) For connecting the RTU to SCADA systems based on DNP protocol.
DNP Server (Slave)
MODBUS Server For connecting the RTU to SCADA systems based on MODBUS protocol.
(Slave)
MODBUS Client (Mas- For connecting with a PLC.
ter)

443
6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.10
DU1 Port (ACE3600)
A.1.10.1
DU1 Port Parameters
Table 114: DU1 Port Parameters

Parameter Allowed values

Media ● Not used (default)
● USB Device

Operation Mode Async

Connection type Remote NDIS Device
Connected to PC/STSHost

A.1.10.2
DU1 Port Configurations
Table 115: DU1 Port Configurations

Configuration Description
Not Used The specified port is not in use. Setting a port to Not used frees any
resources that might otherwise be allocated to the port.
USB Device, Async, Remote For connection to the STS via USB type B.
NDIS Device, PC/STS

A.1.10.3
Link Parameters for DU1 Port
Except as noted in the following table, the link parameters associated with the ACE3600 DU1 port are
identical to those of the PI1 port defined as 10/100 BT for Static LAN connections. See Link Parameters for
PI1/PI2 Ports on page 425.

Table 116: Link Parameters for DU1 Port

Parameter Default value Description

Self IP Ad- 192.168.129.1 The IP address of this USB device. This IP address should
dress be entered in the STS Communication Setup dialog, under
Ethernet port.
For details, see MDLC Communication Driver Configuration on
page 138.

444
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Default value Description

NOTE:
The Default routing IP address is set to 0.0.0.0 by default. Changing this value is not recom-
mended, because doing so may slow the STS PC.
The DU1 port configuration does not include the DNS Servers, NTP Servers, and Protocols...
parameters.

A.1.10.4
Advanced Physical Parameters for DU1 Port
The advanced physical parameters of the ACE3600 DU1 port are identical to those of the HU1 port. See
Advanced Physical Parameters for HU1/HU2 Ports on page 437.

A.1.10.5
Advanced Link Parameters for DU1 Port
The advanced link parameters of the ACE3600 DU1 port are identical to those of the HU1 port. See
Advanced Link Parameters for HU1/HU2 Ports on page 439.

A.1.11
INTR1 Port (ACE3600)
The ACE3600 INTR1 port is an internal Ethernet port dedicated to connecting the active and standby CPUs
in a redundant site.
For more information on the INTR1 port, see the ACE3600 RTU Owner’s Manual.
For more information on RTU Redundancy, see the MC-IoT STS Advanced Features manual.

A.1.11.1
INTR1 Port Parameters
The ACE3600 INTR1 port appears only when Support Dual CPU is enabled in the site configuration.

Table 117: INTR1 Port Parameters

Parameter Allowed values

Media ● Redundancy Primary
● Redundancy Secondary
NOTE: This parameter is automatically set by the STS. To modify it, ad-
just the Redundancy setting in the site configuration; the Media parame-
ter automatically changes accordingly. For more details, see Defining an
ACE3600 Site on page 102.

445
6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.11.2
INTR1 Port Configurations
Table 118: INTR1 Port Configurations

Configuration Description
Redundancy Primary For Ethernet communication over LAN between redundant RTU peers
only, using a static IP address. The specified port belongs to the primary
peer and is configured for communication with the secondary peer.
Redundancy Secondary For Ethernet communication over LAN between redundant RTU peers
only, using a static IP address. The specified port belongs to the secon-
dary peer and is configured for communication with the primary peer.

A.1.11.3
Link Parameters for Port INTR1
The link parameters of the INTR1 port are identical to those of the PI1/PI2 port defined as 10/100 BT for
Static LAN connection, but with different default values. See Link Parameters for PI1/PI2 Ports on page 425.
NOTE: If you change the Self IP address of the INTR1 port, you must change the Default group IP
address (in the INTR1 advanced link parameters) to the correct broadcast IP address.

A.1.11.4
Advanced Physical Parameters for INTR1 Port
No advanced physical parameters are associated with the INTR1 port.

A.1.11.5
Advanced Link Parameters for Port INTR1
The advanced link parameters of the INTR1 port are identical to those of the S1 port configured for PPP
connection, except that some of the defaults are different. See Advanced Link Parameters for SI1 Port on
page 408.

A.1.12
TSP<x> (ACE4600 Terminal Server Ports)
The ACE IP Gateway (ACE4600) supports MDLC connection to multiple RTUs (ACE3600 and legacy
MOSCAD RTUs) via terminal server ports (TSPs) from multiple SCADA clients. In the STS site configuration,
these ports are designated as TSP<x> and can be assigned to physical SI1/SI2, PI1/PI2, or ETH1 ports. Up
to 32 TSPs can be assigned to a single ACE4600 unit.

A.1.12.1
TSP<x> Port Parameters
Table 119: TSP<x> Port Parameters

Parameter Allowed value

Media RS-232

446
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed value

Operation Mode Async
Connection Type Terminal Server

A.1.12.2
TSP<x> Port Configurations
Table 120: TSP<x> Port Configurations

Configuration Description
RS232, Async, Ter- For terminal server ports associated with a physical port on the ACE 4600 only.
minal Server

A.1.12.3
Link Parameters for TSP<x>
Table 121: Link Parameters for TSP<x>

Parameter Default value Description

Terminal server 0.0.0.0 IP address of the terminal server to which the specified port be-
IP address longs. The default value of 0.0.0.0 is not allowed and must be
changed. All ports on a given terminal server can share the same
IP address, but the TCP Port ID and Link Name must be unique.
For details, see “ACE IP Gateway” in the MC-IoT STS Advanced
Features manual.
TCP Port ID 2001 Port number associated with the specific RS-232 port in the ter-
minal server (unique to that terminal server). This port number
is associated with the Link Name specified for it (see the follow-
ing parameter). For each subsequent terminal server port that is
created, the TCP Port ID is assigned sequentially based on the
previous value (by default from 2001–2032.) These automatically
assigned values can be changed.
Link Name RSlink1 Logical name of the link to which the port is connected. For each
subsequent terminal server port that is created, the Link Name
is assigned sequentially based on the previous value (by default:
RSlink1–RSlink19, and then LINE1–LINE13.) These automatically
assigned names can be changed.
Physical Port ETH1 Physical port on the RTU to which the terminal server is connect-
ed. Can be Ethernet (ETH1) or any RS-232 port (SI1, S2, PI1,
PI2) configured as an IP port. Up to 32 terminal server ports can
be assigned to a physical port. For each subsequent terminal
server port that is created, the same physical port assigned to
the previous terminal server port is assigned. These automatically
assigned physical ports can be changed.

447
6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.12.4
Advanced Physical Parameters for TSP<x>
Table 122: Advanced Physical Parameters for TSP<x>

Parameter Allowed Default Description

values value
Idle interval between RX 1–2000 500 The interval (in milliseconds) of idle link time
frames and end recep- after frames are received and before recep-
tion tion is regarded as having ended.
Interval to wait for a 5000– 5000 Time (in milliseconds) to wait for a frame to be
frame to be received 10000 received. After this interval, the link resends
the frame (retry).

A.1.12.5
Advanced Link Parameters for TSP<x>
The advanced link parameters of the terminal server ports are identical to those of the SI1 port. See
Advanced Link Parameters for SI1 Port on page 408.

A.1.13
OTG Port (MC-EDGE)
The MC-EDGE OTG port parameters cannot be modified, and are displayed for reference only.

A.1.14
LoRa Port (MC-EDGE)
A.1.14.1
LoRa Port Parameters
NOTE: For MC-EDGE firmware versions 21.00 and earlier, MQTT Service parameters appear here,
together with the LoRa port parameters.

Table 123: LoRa Port Parameters

Parameter Allowed values Description

Region ● None (default) LoRa region (i.e. frequency plan)
● AU915–928
● AS923
● US902–928
● EU863–870
● AS923-4
● IN865

448
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Description

Enabled up- ● US/AU Sub-band #1-[B0-B7,B64] This parameter is visible only if the
link chan- US or AU region is selected. It de-
nels ● US/AU Sub-band #2-[B8-B15,B65] fines the sub-band for uplink chan-
● US/AU Sub-band #3-[B16-B23,B66] nels.
● US/AU Sub-band #4-[B24-B31,B67]
● US/AU Sub-band #5-[B32-B39,B68]
● US/AU Sub-band #6-[B40-B47,B69]
● US/AU Sub-band #7-[B48-B55,B70]
● US/AU Sub-band #8-[B56-B63,B71]

Select chan- Allows the user to select specific channels from the sub-band (double-click this field to
nels open the Select Channels dialog box). By default, all channels of the chosen sub-band
are selected.
Extra chan- Allows the user to insert extra channels for IN865 Region (double-click this field to open
nels the ExtraChannels dialog box). By default, there is no extra channels.

A.1.14.2
LoRa Port Configurations
Table 124: LoRa Port Configurations

Configuration Description
Not used The specified port is not in use. Setting a port to Not used frees
resources that might otherwise be allocated to the port.
LoRa, LoRaWAN For connection to LoRa in LoRaWAN® mode.
LoRa, LoRa Gateway Type, Ba- For connection to LoRa in LoRa Basics™ Station mode.
sics Station

A.1.14.3
LoRaWAN Advanced Parameters
NOTE: For MC-EDGE firmware versions 21.00 and earlier, MQTT Service parameters appear here,
together with LoRaWAN® port parameters.
See the LoRaWAN Regional Parameters specification for valid options.

Table 125: LoRaWAN Advanced Parameters

Parameter Allowed values Default value

Uplink dwell time 400 ms Yes / No Yes
Rx2 Frequency 100000000 – 999000000 N/A
Rx2 Data Rate 0 – 15 N/A
Authentication None / TLS / MTLS None

449
6802979C10-BA
Appendix A: Site Configuration Parameters

A.1.14.4
LoRa Gateway Advanced Parameters
Table 126: LoRa Gateway Advanced Parameters

Parameter Allowed Values Default Value

Server Name or IP address Name or IPv4 address N/A
Server Port 0 – 65519 3001
Interface LTE / ETH1 ETH1
Authentication None / TLS / MTLS None

A.1.14.5
LoRaWAN IP Firewall
When enabling/disabling LoRaWAN® or changing the LoRa bridge configuration, the LoraWAN IP firewall
ports are opened or closed accordingly (a notification message informs the user of the automatic changes).
In the event that not enough slots are available to open the required IP ports, the user is notified to arrange
the ports manually.
IMPORTANT: After you configure the LoRaWAN in the WebUI, close port 8080 to maintain a high security
level.
For more information, see Firewall & Hardening Parameters (MC-EDGE) on page 466.

A.2
I/O Parameters (ACE3600/ACE1000/MC-EDGE)
A number of Advanced I/O parameters can be set when configuring the I/O module in a site. To view/edit
these parameters, navigate to the I/O tab of the site configuration, select a defined I/O module, and click the
Advanced I/O Configuration... button.

A.2.1
ACE3600 DI Parameters
The following parameters apply to any type of ACE3600 I/O module that includes digital inputs (including
DI/DO FET modules).

Table 127: ACE3600 DI Parameters

Parameter Allowed Default Description

values value
FAST CAP- Disable / Disable Fast capture causes the SCAN ladder output operation
TURE Enable to get the first change since the previous SCAN. When
fast capture is disabled, the SCAN gets the current value
of the DI.
AC/DC AC / DC DC (ex- The power type of the DI
cept in 16
DI
120/230V
module)

450
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
DI Counter
Counter filter- 0–255 20 The DI Counter filter is the time required to be certain
ing time that the DI counter is stable. Enter a filter time to be
multiplied by a factor of 50 microseconds.
Result n/a 1000 Shows the resultant DI Counter filter time (Counter fil-
tering time multiplied by 50 microseconds).
DI Filter
DI filtering time 0–254 50 The DI filter is the time required to be certain that the DI
is stable. Enter a filter time to be multiplied by a factor of
200 microseconds.
Result n/a 10000 Shows the resultant DI filter time (DI filtering time multi-
plied by 200 microseconds).

A.2.2
ACE3600 DO Parameters
The following parameters apply to any type of ACE3600 I/O module that includes digital outputs.

Table 128: ACE3600 DO Parameters

Parameter Allowed Default Description

values value
Reset DO at Yes / No Yes When set to Yes, the DO is reset to 0 when the RTU is
startup started up.
DO relay power 12V / 12V 12V DO 12V: Relay inhibiting is disabled. The relay power source
source DO is from the Main 12V from the motherboard.
12V DO: Relay inhibiting is enabled. The relay power
source is from the 12V DO line, controlled by the 12V
DO input connector on the panel of the power supply
(relays inhibited).
In order for relay inhibiting to be controlled by this param-
eter, the S3 switches on the DO relay board must be
SW1=ON and SW2=OFF.

A.2.3
ACE3600 AI Parameters
The following parameters apply to all ACE3600 analog input modules, including both ±5V and ±20mA
modules.

Table 129: ACE3600 AI Parameters

Parameter Allowed (default) values Description

AI Differential Parameters 50Hz (default) / 60Hz The AI differential signal.

451
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed (default) values Description

AI Filter ● 1 The number of samples for a
specific AI, the average of which
● 2 is the AI value.
● 4
● 8
● 16
● 32 (default)
● 64
● 128

AI Range For ±5V modules: The range of the AI.

● –5V to +5V (default)
● +1V to +5V
● +0V to +5V
For ±20 mA modules:
● –20mA to +20mA (default)
● +4mA to +20mA

A.2.4
ACE1000/MC-EDGE DI Parameters
The following parameters apply to any type of ACE1000 or MC-EDGE I/O module that includes digital inputs
(including mixed and digital mixed I/O modules).

Table 130: ACE1000/MC-EDGE DI Parameters

Parameter Allowed values Default Description

value
Debounce ● 0 msec 30 msec The time frame (in milliseconds) required to filter
(module only) out the input bounce and get one signal from the
● 10 msec DI. This determines how long a DI COS should
● 20 msec remain stable before it is counted as a change.
● 30 msec
● 40 msec
● 50 msec

Notifications ● Disable COS Sends notification when the DI has any change of
state (COS), when it goes to NO, when it goes to
● COS NC, or in none of these scenarios (Disable).
● NO
● NC

Persistence 0–240 0 The persistence time (in seconds) used to filter out
minor/temporary changes in the input. This ensures
that the value is stable before reporting it to the
center.

452
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default Description

value
Dry/Wet Dry / Wet Dry For digital mixed 8DO/16DI 5–18V expansion
module (MC-EDGE) only:
Sets the input contact type.

Name (instan- Digital_In- The object name diplayed in UEM.

ces only) put
“On” message Alarm The text used by UEM to display the state.
(instances only)
“Off” message Normal The text used by UEM to display the state.
(instances only)
Severity (instan- See Table 131: Critical The severity of a change of state.
ces only) Severity Levels
on page 453.
Status (instan- OFF (Normally OFF (Nor- Tells the UEM which value is “normal”, OFF or ON.
ces only) open / ON (Nor- mally
mally closed) open)

Table 131: Severity Levels

In the UEM server, severity values correspond to the following levels and colors.

Severity Value Color

CommFailure – not set by the 1 (highest) Black
STS
Critical, Indeterminate, Automat- 2 Red
ic
Major 3 Orange
Minor 4 Yellow
Warning 5 Blue
Normal (Status) 6 (lowest) Green

A.2.5
ACE1000/MC-EDGE DO Parameters
The following parameters apply to any type of ACE1000 or MC-EDGE I/O module that includes digital outputs
(including mixed and digital mixed I/O modules).

Table 132: ACE1000/MC-EDGE DO Parameters

Parameter Allowed values Default value Description

Reset DO at Enable / Disa- Enable When set to Enable, the DO is reset to 0
startup (mod- ble when the RTU is started up. Relevant for ML
ule only) (magnetic latch) relays only.
Back indica- Enable / Disa- Enable When set to Enable, the actual state feedback
tion ble is shown when changing the status of the digi-
tal output. For future use.

453
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default value Description

Name (instan- Digital_Output The object name diplayed in UEM.
ces only)
“On” message Alarm The text used by UEM to display the state.
(instances only)
“Off” message Normal The text used by UEM to display the state.
(instances only)

A.2.6
ACE1000/MC-EDGE AI Parameters
The following parameters apply to all ACE1000 and MC-EDGE I/O modules with analog inputs, including
mixed I/O modules.

Table 133: ACE1000 AI Parameters

Parameter Allowed val- Default value Description

ues
Type (module ● Current 0mA to +20mA The type of AI.
only)
● Current +4mA to +20mA*
● Volt 0V to +5V
*Default

Noise Filter- ● Disable Disable Used to filter noise generated by the electrical
ing (module network. Set this parameter to 50 Hz or 60 Hz,
only) ● 50 Hz based on the electric current frequency in your
● 60 Hz country.

Smoothing 1–128 10 The number of samples from the sensor that are
(module only) required to calculate an average value and pro-
duce a more stable value. If this parameter is
set 1, no calculation is done. If this parameter
is set to the default 10, the average of the last
10 sampled values is calculated. The ACE1000
samples the AI sensor every 160 msec.
Persistence 0–240 0 The persistence time (in seconds) used to filter
out minor/temporary changes in the input. This
ensures that the value is stable before reporting
it to the center.
Scaling
Units n/a n/a The engineering units used in scaling the AI.
Min Scale n/a 0 The minimum value of the range used in scaling
the AI.
Max Scale n/a 100 The maximum value of the range used in scaling
the AI.
Alarms
Low–Low 0–100 0 The range values for alerts of changes to the AI.

454
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default value Description

ues
Low 0–100 0 A value between Low and High is considered
normal.
High–High 0–100 100
A value between Low–Low and Low is consid-
High 0–100 100
ered out of range.
A value between High and High-High is consid-
ered out of range.
NOTE: The STS performs validation on
the values (e.g. that Low–Low is not
greater than Low.)

Change res- 0–100 10 Enter the AI change resolution percentage. De-

olution termines when to create a burst when the value
of the AI changed (measured from the last burst).
Name (in- Analog_Input The object name diplayed in UEM.
stances only)
Severity – See Table 131: Critical The severity of value being below the Low value.
Low (instan- Severity Levels
ces only) on page 453.
Severity – See Table 131: Critical The severity of value being above the High val-
High (instan- Severity Levels ue.
ces only) on page 453.
Notifications Enable/Disable Enable Enable causes bursts upon the change of value
(Bursts) (in- (a change greater than delta).
stances only)
Burst when Enable/Disable Enable Enable causes bursts when the value is changed
in/out of de- from normal (in range) to not normal (out of
fined range range).
(instances on-
ly)

A.2.7
ACE1000/MC-EDGE AO Parameters
The following parameters apply to all ACE1000 and MC-EDGE I/O modules with analog outputs, including
mixed I/O modules.

Table 134: ACE1000/MC-EDGE AO Parameters

Parameter Allowed values Default value Description

Type ● Current 0mA to +20mA The type of AO.
● Current +4mA to +20mA*
● Volt 0V to +10V
*Default

Scaling

455
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default value Description

Units n/a n/a The engineering units used in scaling the
AO.
Min Scale n/a 0 The minimum value of the range used in
scaling the AO.
Max Scale n/a 100 The maximum value of the range used in
scaling the AO.
Scaling Method Linear The scaling method for the AO.

A.3
Advanced Parameters (ACE3600/ACE1000/MC-
EDGE)
This section covers the parameters located under the Advanced tab of the site configuration. For each
parameter, the range of allowed values and the default value are listed.
NOTE: Exceeding the range of allowed values may consume additional memory and may cause
unexpected or incorrect behavior in the RTU.
The list of displayed advanced parameters varies for each unit type. For example, certain groups of advanced
parameters available for the ACE3600 do not appear in the MC-EDGE® advanced site configuration. Except
where specified otherwise, the same advanced parameters apply to the ACE3600 and the ACE IP Gateway
(ACE4600).
Some of the ACE3600 parameters relate to advanced features and are documented in the ACE3600 STS
Advanced Features manual.
For more information on configuring sites and accessing the advanced site parameters, see MC-IoT STS
Operation.

A.3.1
'C' Application Parameters (ACE3600)
The following parameters do not apply to the ACE4600.

Table 135: ACE3600 "C" Application Parameters

Parameter Allowed Default Description

values value
Number of user 0–10 10 In addition to the tasks defined by the system (main
tasks for 'C' blocks process, Task priority A-Task priority D. CB_TaskA-
CB_TaskD), up to 10 additional tasks can be defined.
These tasks (CB_TaskECB_ TaskN) can be activated
via a user-defined C function which can be called
with ucall. The tasks can be activated or suspend-
ed using a 'C' routine. Each task allocates ≈2KB of
stack. For details, see the ACE3600 'C' Toolkit User
Guide.
Size of each buffer 0–2048 0 Maximum buffer size in the heap used by the 'C'
in the 'C' applica- application when allocating memory using linked list
tion heap (bytes) functions.

456
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
Number of buffers 0–255 0 Maximum number of buffers in the heap used by the
in the 'C' applica- 'C' application when allocating memory using linked
tion heap list functions.
RAM size for 256– 256 The amount of memory reserved for dynamic alloca-
dynamic alloca- 16384 tions at runtime.
tion <256-16384> 'C' programs require dynamic allocations. Therefore,
kbytes the value of this parameter should be determined ac-
cording to the amount of memory required by the 'C'
programs, or according to the number of 'C' program
blocks.

Number of slave 'C' 0–250 3 Number of 'C' language functions to be supplied by

functions for ses- the 'C' application for MDLC communication session
sion based proto- based protocol. For more information, see “DCF1” in
col the ACE3600 'C' Toolkit User Guide. This parameter
pertains to the Number of SLAVE logical channels
parameter (see Frame Sequence Layer Parameters
(ACE3600/ACE1000/MC-EDGE) on page 467).
Number of 'C' func- 0–250 0 Number of 'C' language functions to be supplied by
tions called by the the 'C' application to the 10 millisecond task. For
10 msec task more information, see “DCF2” in the ACE3600 'C'
Toolkit User Guide.
NOTE: 10 ms functions must have short ex-
ecution times in order not to adversely affect
important system functions.

Number of 'C' func- 0–250 10 Number of 'C' language functions to be supplied by

tions called by the the 'C' application to the 100 millisecond task. For
100 msec task more information, see “DCF3” in the ACE3600 'C'
Toolkit User Guide.
Number of 'C' func- 0–250 10 Number of 'C' language functions to be supplied by
tions called by the the 'C' application to the 1 second task. For more
1 sec task information, see “DCF4” in the ACE3600 'C' Toolkit
User Guide.
Number of 'C' func- 0–250 10 Number of 'C' language functions to be supplied by
tions called by 1 the 'C' application to the 1 minute task. For more
min task information, see “DCF5” in the ACE3600 'C' Toolkit
User Guide.
Number of diag- 0–250 10 Number of 'C' language functions to be supplied by
nostics functions the 'C' application to the Software Diagnostic utility.
for 'C' application These functions add user-defined diagnostics about
user C blocks, in addition to the system diagnostics
about the system devices. For more information, see
“DCF6” in the ACE3600 'C' Toolkit User Guide.
Size of I2phys 0–250 3 Number of 'C' language functions to be supplied by
functions table the 'C' application to the I2Phys. These functions
interface between the RTU MDLC protocol or anoth-
er user physical protocol. For more information, see
“DCF7” in the ACE3600 'C' Toolkit User Guide.

457
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
Size of dynamic DB 0–250 0 Number of 'C' language functions to be supplied by
access functions the 'C' application to the DB map. For Motorola use
table only.
Number of com- 0–250 5 The user may allocate memory from a 'C' block
mon named point- (using the MOSCAD_malloc function), in order to
ers hold the allocated buffer in named pointers between
downloads, and to get it back after the download
ends. This feature enables the user to keep data
between different downloads. Variable pointers can
be passed from one block to another.
Timeout to resume 0–180000 60000 When running the system in 'C' application DEBUG
debug (msec) mode, the timeout (in milliseconds) to resume the
system run after pausing the system at startup for
debug.
Maximum size of 0–1500 1000 The first parameters is the maximum size (in kbytes)
flash memory for of the flash memory in the unit allocated for logging
0–40 30
user logging, in user data. The size cannot exceed the percentage
kbytes and NOT of the total Flash memory specified in the second
more than <0-40> parameter.
percentage of total
user flash
Number of '100 0–1000 10 The number of 'C' application 100 msec timers
msec' timers for 'C' that can be used. For more information, see the
applications ACE3600 'C' Toolkit User Guide.
Number of '10 0–100 0 The number of 'C' application 10 msec timers
msec' timers for that can be used. For more information, see the
"C" applications ACE3600 'C' Toolkit User Guide.
Alert about C appli- No / Yes No When set to Yes, the user is alerted of 'C' application
cation ucalls which ucalls that are listed in the user jump table, but which
are not called from are not called from a ladder application (using the
ladder UCL operator). For details on calling "C" applications
from the ladder, see the ACE3600 'C' Toolkit User
Guide.

A.3.2
Core Dump Parameters (ACE3600)
Table 136: ACE3600 Core Dump Parameters

Parameter Allowed val- Default Description

ues value
SMA online Reduced Reduced Saves a “frozen” image of the system memory before
functionali- functional- an RTU crash to help identify the cause of the failure.
ty / Disable ity For more details, refer to “Core Dump” in the MC-IoT
STS Advanced Features manual.

458
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default Description

ues value
When set to Reduced functionality, the Core Dump
saves a partial image only, and sends a message to the
Error Logger and to the system console.
When set to Disable, a system memory image is not
saved.

A.3.3
DNS Client Parameters (ACE3600)
Table 137: ACE3600 DNS Client Parameters

Parameter Allowed Default Description

values value
Retransmission 1–5 1 Time interval (in seconds) for resending resolve queries
interval when to the domain name server(s), until a reply is received.
resolve Using the default setting is recommended, because in-
creasing the value delays communication on all MDLC
over IP ports. Increase the interval only if resolving fails
as a result of very slow media.
Number of re- 1–2 2 Number of times to retry sending resolve queries to the
tries to resolve domain name server(s), until a reply is received.

A.3.4
DNS Service Parameters (MC-EDGE)
Table 138: MC-EDGE DNS Service Parameters

Parameter Allowed values Default Description

value
DNS Serv- ● Disable Disable This feature provides the ability to define
ice up to three external DNS servers, which
● Enable the MC-EDGE DNS client can query for
name-IP resolution. If enabled, the MC-
EDGE queries the DNS servers for server
name resolution if required.
The connectivity may be through any sup-
ported IP (Eth, LTE). The query occurs only
if other features involve the definition of ex-
ternal server names (for example, if NTP
service is enabled, and the NTP server
is defined by name and not by IP). The
DNS servers themselves must be defined
by their IP address.

Host Alphabetic characters: a-z, A- mciot Device label allowing identification on net-
Name Z; digits: 0-9; hyphen: ‘-‘. work over DNS

459
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed values Default Description

value

● Total length cannot exceed

63 characters.
● Name cannot begin or end
with hyphen.
● Name cannot contain digits
only.

Domain ● Up to three parts (labels) n/a May consist of one or more labels to ful-
Name separated by dots. fill FQDN, which refers to a DNS name
with everything required to unambiguously
● Each label consists of 2– resolve it
63 characters (letters, num-
bers, or hyphens). Cannot
begin or end with a hyphen.

Table 139: MC-EDGE DNS Service Parameters: Servers

Parameter Allowed values Description

DNS primary server
IP address <0.0.0.0-255.255.255.2 The primary external DNS server in IPv4 address
55> format; an empty line means no server/
Interface ● LTE The primary DNS server interface definition.
● ETH1 (default)
● ETH2
● ETH3

DNS secondary server

IP address <0.0.0.0-255.255.255.2 The secondary external DNS server in IPv4 address
55> format; an empty line means no server.
Interface ● LTE The secondary DNS server interface definition.
● ETH1 (default)
● ETH2
● ETH3

DNS tertiary server

IP address <0.0.0.0-255.255.255.2 The tertiary external DNS server in IPv4 address
55> format; an empty line means no server.
Interface ● LTE The tertiary DNS server interface definition.
● ETH1 (default)
● ETH2
● ETH3

460
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.5
Dynamic IP Routing Parameters (ACE3600)
Table 140: ACE3600 Dynamic IP Routing Parameters

Parameter Allowed (default) val- Description

ues
Learn route- ● Always learn When receiving an ICMP transmission, determines wheth-
ICMP receive er the RTU learns the dynamic IP route and updates the
● Never learn routing table accordingly.
● Learn if not modi- When set to Learn if not modified, the dynamic IP route
fied (default) is learned provided that it does not modify routing.

Learn route- ● Always learn When receiving a TCP transmission, determines whether
TCP receive the RTU learns the dynamic IP route and updates the
● Never learn routing table accordingly.
● Learn if known ap- When set to Learn if known application/socket ID,
plication/socket ID the dynamic IP route is learned only when the applica-
(default) tion/socket ID is known.

Learn route- ● Always learn When receiving a UDP transmission, determines whether
UDP receive the RTU learns the dynamic IP route and updates the
● Never learn routing table accordingly.
● Learn if known ap- When set to Learn if known application/socket ID,
plication/socket ID the dynamic IP route is learned only when the applica-
(default) tion/socket ID is known.

Learn route ● Always learn When receiving an IGMP (multicast) transmission, deter-
(multicast) re- mines whether the RTU learns the dynamic IP route and
ceive ● Never learn (default) updates the routing table accordingly.
Size of dy- Range: –1 – The maximum number of entries in the dynamic IP routing
namic IP rout- 2147483647 table.
ing table Default: –1 When set to –1 (default), the maximum table size table
is determined by the firmware capability (555 for firmware
v17.00). If the user sets the table size to a value greater
than the firmware maximum, the STS will ignore the set-
ting and use the default.
When set to 0, the feature is disabled. If the table is
full, the RTU cannot communicate with new/learned IP ad-
dresses for a limited time until an entry becomes vacant.
This to prevent resource exhaustion and denial of service.
Time to keep Range: 0–2147483647 Amount of time (in seconds) to keep a dynamic IP routing
dynamic IP Default: 120 entry in the dynamic IP routing table.
route When set to 0, the entry is kept indefinitely.

Keep dynamic ● No Determines whether an entry in the dynamic IP routing

route for open table for an opened TCP socket is retained.
socket ● Yes (default)

461
6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.6
Dynamic Site Table Parameters (ACE3600/ACE1000/MC-
EDGE)
Table 141: ACE3600/ACE1000/MC-EDGE Dynamic Site Table Parameters

Parameter Allowed Default Description

range value
Number of entries in 0–100 15 The regular Site table (a Database system table)
the dynamic Site Table can be expanded using the dynamic site-table,
which is accessible via 'C' Toolkit.

A.3.7
Error Logger Parameters (ACE3600)
Table 142: ACE3600 Error Logger Parameters

Parameter Allowed Default Description

values values
Error logger 0–1000000 32768 In the Flash memory, the maximum size of the file that
maximum flash is used to store error logger messages.
file size Error messages are generated by modules to inform
the user of unusual system events. Increasing the file
size is recommended if the user expects a large num-
ber of errors. If the file is full, no new messages can
be added to the file and any subsequent error messag-
es are lost. To avoid filling up the file, errors should
be frequently retrieved and deleted in the Error Logger
utility. The status of the Error Logger flash file can be
monitored using the ErAlmostFul and ErFull flags in the
system Reserved Flag table. Error messages from the
logger flash file are also backed up on the STS PC hard
drive for future reference.

Length of 51000– 100000 The length (in bytes) of the buffer used to accumulate
queue for user 1000000 errors before they are written to the Error Logger file
message/jobs in the Flash memory. Increasing the size of the queue
is recommended for systems with a large number of
errors.
Almost full val- 50–100 50 When the Error Logger files occupies this amount (per-
ue (%) centage) of the Flash memory, an ‘Almost Full’ warning
is sent to the system.

462
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.8
Fast Event Parameters (ACE3600)
The following parameters do not apply to the ACE4600.

Table 143: ACE3600 Fast Event Parameters

Parameter Allowed Default Description

values value
Maximum run- 100–2000 2000 The maximum runtime for a fast event process before
time duration in alerting the user. Because a fast event process has the
microseconds highest execution priority in the system, it can often pre-
empt all other processes. In order to prevent a fast proc-
ess from monopolizing the system, an alert is sent to
the user if it has executed for longer than the specified
maximum runtime duration.
Queue size for 50–1000 200 The size of the queue that is used to store incoming fast
incoming events that trigger the execution of fast processes.
events
Number of de- 50–1000 50 The maximum number of delay triggers that can be
lay triggers used by the TEN ladder operator or by the C toolkit
'MOSCAD_fastevent_enable_trigger()' service.
Number of fast 1–10 5 The maximum number of fast processes that can be at-
processes per tached to a unique fast event trigger (e.g. if DI 1 changes
trigger from 0 to 1). This parameter determines the amount
of memory allocated for each trigger. If only a few fast
processes are attached to triggers, do not increase this
value.

A.3.9
Firewall & Hardening Parameters (ACE3600)
Table 144: ACE3600 Firewall & Hardening Parameters

Parameter Allowed Default Description

values value
Activate firewall? Disable / Disable In an I/O expansion system with an activated fire-
Enable wall, the IP address range of all expansion frames
configured in the system must be listed in the
approved Firewall address list, as well as the IP
address of the main CPU expansion port. For ex-
ample, in a system with 13 frames, specify the
IP address range 10.100.100.100 (main CPU) to
10.100.100.113. These IP addresses comprise:
1. The number set in the rotary frame number se-
lector switch (1–13) of the I/O expansion mod-
ule.
2. Either the Self IP address from the ETH1 → I/O
Expansion Comm. port configuration, or the

463
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value

Expansion module first frame IP address pa-

rameter (see I/O Expansion Manager Parame-
ters (ACE3600) on page 474).
NOTE: For more on enabling the firewall in
expansion systems, see the “Firewall” sec-
tion of the MC-IoT STS Advanced Features
manual.

Firewall address n/a n/a The list of IP addresses allowed to pass through
List... this firewall. If no IP address is defined, then all ad-
dresses are allowed. To append a line, start typing
in the blank row at the bottom of the list. To modify
an existing line, double-click it. To remove a line,
right-click it and select Delete row. To save the list,
click OK.
NOTE: For more on firewall IP addresses in
expansion systems, see the “Firewall” sec-
tion of the MC-IoT STS Advanced Features
manual.

Max size of ICMP 0–65535 100 The maximum size of the ICMP Echo (ping) allowed.
packet (bytes) A ping packet with a larger size is ignored; no re-
sponse is sent back.
Enable communica- Disable / Enable Determines whether the RTU allows communication
tion with remote Enable from the STS via a remotely connected RTU (Ena-
STS ble), or via a locally connected RTU only (Disable).
A parameter with the same name exists in the ad-
vanced link layer settings of each port. If this param-
eter in the firewall is set to Disable, then it applies to
all ports. If it is set to Enable in the firewall, then the
individual setting of each port determines whether
connection is allowed via that port.

Allow C toolkit de- No / Yes No Pertains to secured systems. Determines whether

bugging 'C' toolkit debugging is allowed in the RTU. For
more information, see “IP Firewall” in the MC-IoT
Advanced System Security User Guide.
Disable C applica- No / Yes No Pertains to secured systems. Determines whether
tions in RTU 'C' applications can run in the RTU. For more infor-
mation, see “IP Firewall” in the MC-IoT Advanced
System Security User Guide.
Lock firmware code No / Yes Yes Pertains to secured systems. When set to Yes, the
firmware code in the RTU memory is locked to pre-
vent any change, even of a single byte. For more
information, see the “IP Firewall” section of the MC-
IoT Advanced System Security User Guide.
Avoid gratuitous Disable / Enable When set to Enable, gratuitous ARP transmissions
arp. Enable are not sent. Otherwise, gratuitous ARP transmis-
sions are sent.

464
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
Enable reception Disable / Enable When this parameter is set to Enable, communica-
from remote RTU Enable tion from remote RTUs (connected via another RTU)
is allowed by the firewall.
Each port also has the same parameter in the ad-
vanced link layer settings. Ports may be configured
to Enable or Disable reception, provided that the
same parameter on the firewall level is set to Ena-
ble.
When this parameter is set to Disable on the fire-
wall level, then communication from remote RTUs is
rejected on all ports (regardless of the individual set-
ting of each port), except for communication initiated
by the STS.

Enable RTU-to-RTU Disable / Enable When set to Enable, the RTU accepts and forwards
Store & Forward Enable communication intended for other RTUs via the Link
IDs specified in the network manager configuration.
If set to Disable, it rejects this communication and
does not forward it, except for communication initiat-
ed by the STS.
NOTE: This parameter is not related to the
Enable routing on MDLC over IP port pa-
rameter in the advanced link layer port set-
tings. The user may enable Enable routing
of MDLC over IP port in the advanced link
layer, even if the parameter referenced in
this section is disabled.

Enable IP Conver- Disable / Enable If set to Enable, learns the IP addresses of frames
sion Learning Enable received over IP (LAN, PPP, MotoTrbo radios).
When receiving from a site that has an IP address
differing from the one defined in the IP Conversion
Table, communication is accepted and the IP ad-
dress is updated (along with the UDP port number).
When receiving from a site that does not appear in
the IP Conversion Table, communication is accepted
and the IP address is added (along with the UDP
port number). This is the default behavior of IP Con-
version Table.
If set to Disable, when receiving from a site with an
IP address that is missing or different from the ad-
dress in the IP Conversion Table, the site is ignored,
and the reception process of the frame is aborted.
To support redundant IP addresses, the “Dynamic
IP Access Table Manager” tool enables the user to
define several IP addresses for a specific site (and
link). When Enable IP Conversion Learning is set
to Disable, any one of the addresses defined in the
Dynamic IP Access Table Manager is accepted.

465
6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.10
Firewall & Hardening Parameters (MC-EDGE)
Table 145: MC-EDGE Firewall & Hardening Parameters

Parameter Allowed Default Description

values value
Activate fire- Disable / Enable When set to Enable, the system firewall is activated.
wall? Enable
Firewall ad- n/a n/a The list of IP addresses to pass through the firewall.
dress list... When the firewall is enabled, if no IP address is defined,
then all addresses are allowed.
To append a line, start typing in the blank row at the bot-
tom of the list. To remove a line, right-click it and select
Delete row. To save the list, click OK.
NOTE: When replacing the default APX IP ad-
dress using the CPS tool, manually add the up-
dated IP address to the firewall IP address list.

Firewall port n/a n/a List of ports allowed to pass the firewall (when the fire-
list... wall is enabled).
To add a port to the list, type the preferred port number
and select port type from the drop-down menu. To re-
move a port from the list, right-click it and select Delete
row. To save the list, click OK.

Enable commu- Disable / Enable When set to Enable, the RTU allows communication
nication with Enable from an STS PC connected to a remote RTU. Otherwise,
remote STS only communication from an STS PC locally connected
to the RTU is allowed.
A parameter with the same name exists in the advanced
link layer settings of each port. If this parameter is set
to Disable on the firewall level, then the setting applies
to all ports. If it is set to Enable in the firewall, then
the individual setting of each port determines whether
connection is allowed via that port.

A.3.11
Formatter Parameters (ACE3600)
The following parameters do not apply to the ACE4600.

Table 146: ACE3600 Formatter Parameters

Parameter Allowed Default Description

values value
Length of queue 0–10000 200 The transmission queue of a user port is used for
for user message/ SEND purposes. This parameter determines the size
jobs (bytes) of the queue. Increase the value if the number of bytes
to be transmitted by SEND is expected to exceed 200
during one SCAN of the ladder diagram.

466
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.12
Frame Sequence Application Parameters (ACE3600/
ACE1000/MC-EDGE)
The following parameters do not apply to the ACE4600.

Table 147: ACE3600/ACE1000/MC-EDGE Frame Sequence Application Parameters

Parameter Allowed Default Description

values value
Ladder received- 1–30 10 The maximum number of frames that can be stored
frame-sequence in the frame sequence device queue (waiting to be
queue size handled by the application). If more frames arrive,
an error is issued to the Error Logger. In this case,
Call RcvSeq should be performed from the ladder
diagram.

A.3.13
Frame Sequence Layer Parameters (ACE3600/
ACE1000/MC-EDGE)
Table 148: ACE3600/ACE1000/MC-EDGE Frame Sequence Layer Parameters

Parameter Allowed val- Default Description

ues value
Stop transmitting 5–10000 100 Duration of time (in seconds) during which a Re-
'reset ack' after set ACK should be transmitted to a unit that is
<5-10000> sec expected to return a void frame at the Transport
Multiplex level for each Reset ACK. After the
specified time elapses, the unit stops sending
Reset ACKs in order to identify another reset sit-
uation (if one occurs).
Maximum allowed 5–200 30 A frame that is received again during this period
delay for a dupli- of time (in seconds) is considered a duplicate,
cate frame and is discarded. If it arrives after this time, it is
considered to be a new frame.
'Hole declaration' 1–30000 30 Duration of time (in seconds) during which
time out frames that failed to arrive as part of a chain are
allowed to be retried at the Data Link level. This
timeout is calculated as a function of the number
of retries and the data speed.
Allowed reception 4–128 16 The gap that causes the unit to move to synchro-
range from 'ex- nization at the Transport Multiplex level. For ex-
pected frame' ample, if the parameter is set to 16 and frame
x+16 arrives (when x was expected), the unit
moves to synchronization.

467
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default Description

ues value
Maximum range 4–128 10 The allowed interval between retried frames. For
to declare 'Dupli- example, if the parameter is set to 16 and x-16
cate frame' arrived (when x is expected), the unit moves to
synchronization as in the previous parameter.
Restart declara- 5–200 30 Time interval (in seconds) between two Restart
tion time out control frames at the Transport Multiplex level.
Timeout for URGE 0–3000 15 Duration of time (in seconds) after which an
transmission after “urge” frame is issued if a gap is formed at the
hole detection Transport Multiplex level. A response to the urge
frame signifies that the gap can never be filled
because all Data Link layer retries have already
been exhausted.
Size of TX queue 30–200 80 Because Transport Multiplex consumes buffers
for transmission, the number of buffers is limited
via this parameter in order to prevent the TX
heap from being completely emptied.
Number of retries 0–9 0 The number of times an urge frame is to be re-
for 'URGE frame' transmitted.
Number of MAS- 0–5 0 Number of logical channels in the MDLC protocol
TER logical chan- capable of initiating communication via a session
nels oriented channel. Do not change this value (it
should remain 0) because in the current version
no Client (Master) application exists in the termi-
nal unit. For ACE IP Gateway, this value is set to
64 by default.
Number of SLAVE 0–7 4 Number of MDLC logical channels that can be
logical channels accessed through one or more Clients (Masters)
simultaneously.
Send broadcast Yes / No Yes Set to Yes to broadcast to all units defined after
reset after restart Reset Load in order to synchronize at the Trans-
port Multiplex level.
Health-check (ap- No / Yes Yes Set to Yes to enable the ACE IP Gateway Health
plication) support Check mechanism. When enabled, Health Check
verifies which links are available, and routes
frames to operational links accordingly. When
Health Check is disabled, the ACE IP Gateway
assumes that all sites registered in the site table
are reachable. For detailed information on the
Health Check mechanism, see the MC-IoT STS
Advanced Features manual.

468
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.14
Gap Ratio Parameters (ACE3600)
The following parameters do not apply to the ACE4600.

Table 149: ACE3600 Gap Ratio Parameters

Parameter Allowed Default Description

values value
Main proc- 0–100 40 The ratio between the time allocated to the main process
ess duty cy- of the application (including higher priority tasks, such as
cle MDLC reception), and tasks of lower priority.
The objective of this parameter is to enable lower priority
tasks to perform even when the application is busy.

A.3.15
Gateway Parameters (ACE4600)
NOTE: The parameters in this section do not apply to the ACE3600.

A.3.15.1
System Resources
Table 150: System Resources

Parameter Allowed Default Description

values value
Clients 1–10 4 The maximum number of SCADA clients that can be allocat-
ed at one time.
Channels 1–40 16 The maximum number of SCADA channels that can be allo-
cated at one time.

A.3.15.2
Tasks Allocation
Table 151: Task Allocation

Parameter Allowed Default Description

values value
Overall tasks 1–20 6 The maximum number of overall, concurrent application
tasks.
Dedicated CMD 0–10 1 The maximum number of concurrent command tasks
tasks (dedicated for sending commands).
Dedicated DATA 0–15 1 The maximum number of concurrent data tasks (dedicated
tasks for polling RTUs and for downloading parameters).

469
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
Dedicated 1–5 1 The maximum number of concurrent service tasks (dedi-
SERVICE tasks cated for sending/reading the RTU time).

A.3.15.3
Requests Allocation
Table 152: Requests Allocation

Parameter Allowed val- Default value Description

ues
Overall pending 1–125 30 The maximum total number of requests which
requests can be pending at one time.
Pending CMD re- 1–105 10 The maximum number of CMD requests
quests which can be pending at one time.
Pending DATA 1–105 10 The maximum number of DATA requests
requests which can be pending at one time.
Pending SERV- 1–105 10 The maximum number of SERVICE requests
ICE requests which can be pending at one time.

A.3.15.4
Flags
Table 153: Flags

Parameter Allowed Default Description

values value
Send TCP check Yes / No Yes When set to Yes, the ACE IP Gateway IP stack sends
alive requests check alive messages to the SCADA central to keep
the connection alive.
“Send Data” re- Disable / Disable Determines whether the priority of Send Data requests
quest priority Enable is the same as that of Send Command requests.
as “Send Com-
mand”
Enable wait be- Disable / Disable Determines whether to wait between SCADA requests.
tween SCADA re- Enable
quests
Log SCADA ap- No / Yes No When set to Yes, SCADA application statistics mes-
plication statis- sages (counts of poll/command/service requests sent
tics messages by the SCADA to the Gateway) are recorded in the
Error Logger.

470
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.16
Hardware Test Parameters (ACE3600)
Table 154: ACE3600 Hardware Test Parameters

Parameter Allowed Default Description

values value
Max time 0–255 10 Maximum amount of time (in minutes) to wait before un-
freeze in min freezing an I/O module or power supply module that was
frozen during a hardware test, or before running an appli-
cation which was stopped during a hardware test.
During hardware testing, the I/O module can be frozen by
the user. If the user exits the Hardware Test utility without
unfreezing the module, all frozen modules are unfrozen
after the specified period of time elapses. Likewise, if the
user remains in the Hardware Test utility but no activity
is detected, all frozen modules are unfrozen after this
amount of time.

A.3.17
Heap Parameters (ACE3600/ACE1000/MC-EDGE)
Table 155: ACE3600/ACE1000/MC-EDGE Heap Parameters

Parameter Allowed Default Description

values value
Number of for- 50–2000 200 The number of formatted buffers designed for RTU-to-
matted buffers RTU burst, event, burst seq, and event seq transmis-
in TX-heap sions, as well as for transmissions from MDLC applica-
tions such as Diagnostics, Error Logger, Processes/Ta-
bles Monitor, Site Configuration and Downloader. If DE-
VICE=HP_F_TX is frequently emptied, increase the val-
ue of this parameter.
IMPORTANT: Each buffer consumes about 250 bytes of
RAM.

Number of for- 50–2000 500 The number of formatted buffers designed for RTU-to-
matted buffers RTU burst, event, burst seq, and event seq receptions,
in RX-heap as well as for receptions from broadcasts and MDLC
applications such as Diagnostics, Error Logger, Process-
es/Tables Monitor, Site Configuration and Downloader. If
DEVICE=HP_F_TX is frequently emptied, increase the
value of this parameter.
IMPORTANT: Each buffer consumes about 250 bytes of
RAM.

Formatted buf- 160–2000 160 The size (in bytes) of the formatted buffer.
fer size
Unformatted 120–2000 120 The size (in bytes) of the unformatted buffer that serves
(Adapter) buf- as an asynchronous port. The overhead is ≈15 bytes.
fer size

471
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
See the Number of idles to announce 'End of RX' pa-
rameter, in the advanced physical layer port parameters.
Ladder-dia- 0–1000 56 The size (in bytes) of the buffer used for transmission
gram user port and reception. It defines a user port, including buffer
buffer size management overhead (≈ 15 bytes). If the user port is
used for communication with the terminal, the default
size is sufficient. If the communication protocol is applied
to the user port (if the port is to handle larger quantities
of data), increasing the buffer size according to scan
time is recommended. The buffers need to be large
enough to store all characters received during one scan
time. For example, at a data speed of 9600, each char-
acter takes about 1 msec to arrive. If the scan time is
greater than 8*84 msec, increase this parameter.
The user port is capable of handling up to 8 buffers. If
all are full, the port sets DTR to OFF, or issues XOFF
according to its configuration.

Number of buf- 0–200 40 Number of buffers for transmission and reception in the
fers in ladder- user port. For each user port the value of this parameter
diagram user must be at least 17.
port

A.3.18
I/O Parameters (ACE3600)
The following parameters do not apply to the ACE4600.

Table 156: ACE3600 I/O Parameters

Parameter Allowed Default Description

values value
I/O Legacy ● Actual Actual Determines the analog I/O bit resolution in ACE3600 appli-
Resolution cations.
● Lega-
cy When set to Legacy, the value range is as in MO-
SCAD/MOSCAD-L:
● AI Voltage: 13 bit signed
± 4000 = ±5V
● AI Current: 13 bit signed
± 4000 = ±20mA
● AO Voltage : 12 bit unsigned
0–4000 = 0-5V
● AO Current : 12 bit unsigned
0–4000 = 0–20mA
When set to Actual, the value range is as in the ACE3600:
● AI Voltage: 16 bit signed

472
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value

±32000 = ±5V
● AI Current: 16 bit signed
±32000 = ±20mA
● AO Voltage : 14 bit unsigned
0–16000 = 0–10V
● AO Current : 14 bit unsigned
0–16000 = 0–20mA
For systems with both ACE3600 RTUs and legacy (MO-
SCAD/MOSCAD-L) RTUs, select Legacy if you prefer to
upgrade MOSCAD/MOSCAD-L applications to ACE3600
without modifying the applications (‘C’ or ladder).
If your application uses scaled AI or scaled AO, do not use
legacy I/O resolution. When scaling is used, the values of
the AIs and AOs reflect the required values automatically.
NOTE: The AO voltage range of ACE3600 is 0 to
10V (versus 0 to 5V in MOSCAD).

SBO relay 0–65535 50 For SBO DOs only: Time (in milliseconds) to wait for the
check hard- Hardware Check. After this timeout, a hardware failure
ware timeout message is sent. Internal use only.
SBO relay se- 0–65535 5000 For SBO DOs only: Amount of time (in milliseconds) which
lect timeout is allowed to elapse between the Select and the Oper-
ate. After this timeout, the SBO DO is reset (Select is
aborted). This parameter is only relevant when the user
calls Select, Check, and Operate separately. When the
system performs the SBO automatically, this parameter is
not checked.

A.3.19
I/O Expansion Parameters (ACE3600)
The following parameters do not apply to the ACE4600.
For detailed information on I/O expansion, see MC-IoT STS Advanced Features and ACE3600 RTU Owner’s
Manual.

Table 157: ACE3600 I/O Expansion Parameters

Parameter Allowed Default Description

values value
Main to expansion 4–190 120 Time (in microseconds) to be added to the clock time
frame TX delay of the main CPU for time stamps of events in the
expansion frames.
I/O frames cycle time 1–100 1 Total time (in units of 10 milliseconds) required for the
<1-100> (1 X 10msec) main CPU to scan all the frames in the system.
Expansion frames 2–100 50 Period of time (in scan cycles) after which the com-
comm. status re-esti- munication status between the main frame and each
expansion frame is checked.

473
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
mation time period (in
scan cycles)

A.3.20
I/O Expansion Manager Parameters (ACE3600)
The following parameters do not apply to the ACE4600.
NOTE: Unlike other advanced configuration parameters, changes to the I/O Expansion Manager
group parameters in a redundant primary peer are applied automatically to the secondary peer.

Table 158: ACE3600 I/O Expansion Manager Parameters

Parameter Allowed Default Description

values value
Expansion Mod- n/a 57002 The number of the TCP server data port (private port
ule Upload TCP number) used by the expansion module to upload the
data port number image and user files from the main CPU.
Main to Expan- n/a 57001 The number of the TCP server port. The main CPU
sion Connectivi- uses this port to listen to expansion requests. The ex-
ty TCP control pansion module uses this port to:
port number ● Register its I/Os with the main CPU.
● Learn its data port number, and other parameters
related to loading files from the main CPU.
● Send I/O information to the main CPU.
● Send keepAlive messages.
The default value is the same as the UDP port over
which the Expansion Loader searches for the main
frame CPU (discovery), but this port number can be
changed. For more on the Expansion Loader, see the
ACE3600 RTU Owner’s Manual.

Configured ex- 1–65535 60 Number of seconds to wait for recognition of the ex-
pansion module pected I/O expansion module or modules during sys-
recognition time- tem startup. This parameter is relevant when at least
out one expansion frame is configured, and auto-recogni-
tion is not configured. Do not set 0 for this parameter.
This is the amount of time that the main CPU should
wait for all configured expansion modules to connect
completely.
Expansion mod- 0–65535 5 Number of seconds to wait during startup for the main
ule frame detec- CPU to detect if at least one expansion frame exists.
tion timeout This parameter is relevant when auto-recognition is
configured (either with the default configuration, or
when the user sets auto-recognition). If the main CPU
does not detect any frame after this time elapses, it
assumes that no expansion frames exist. If this param-
eter is set to 0, frame detection does not occur and the

474
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
main CPU waits according to either the Configured
expansion module recognition timeout or Expan-
sion module auto-recognition timeout parameter.
Expansion mod- 1–65535 60 Number of seconds to wait for completion of the ex-
ule auto-recogni- pansion module auto-recognition during system start-
tion timeout up. This parameter is relevant when no expansion
frames are configured, but auto-recognition is config-
ured. During this time, the main CPU waits for all ex-
pansion modules identified during auto-recognition to
become fully operational. Do not set 0 for this parame-
ter.
Expansion load 1–65535 60 Limits the number of seconds that an I/O expansion
image timeout module takes to load its image from the main frame
CPU. During this time, the main CPU denies requests
from other expansion modules with the same ID. After
this time expires, the expansion module is expected to
restart if it has not completed loading its image.
Expansion mod- 0–65535 0 Limits the number of seconds it takes for an expansion
ule initialization module to be initialized, i.e. to load the user configura-
timeout tion and application files, and to register its I/O informa-
tion (I/O data image) with the main CPU. During this
time, its frame ID is considered “in use,” and the main
frame CPU denies requests from any other expansion
module with the same ID. After this time, if the expan-
sion module has not been fully initialized, it restarts.
When set to 0, no time limit is applied (initialization is
allowed to continue indefinitely).
Expansion mod- 0–65535 0 For expansion modules:
ule EMI protocol Number of seconds to wait for the Expansion Micro-
connect timeout code Interface (EMI) to connect. If both the expansion
module and the main CPU are started at the same
time, the expansion module is initialized first and then
starts running before the main CPU completes system
startup (the main CPU waits for this process to com-
plete before continuing its start sequence). During this
time, no EMI connection is established between the
two.
This parameter limits the time expected (by the expan-
sion module) for the main CPU system startup to com-
plete and connect EMI. If the main CPU does not
complete its startup after this time, or if a cable is
disconnected, EMI is not connected. This causes the
expansion module to restart. If this parameter is set to
0, no time limit is applied.

Expansion mod- 1–65535 10 For expansion modules only:

ule TCP connec- Number of seconds to wait for a TCP connection to
tion timeout succeed with the main CPU. The expansion module
uses TCP communication in order to upload files from

475
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
the main CPU, and to register its I/O module informa-
tion.
During runtime, a keepalive is sent to maintain the TCP
connection. This parameter limits the time spent wait-
ing for the main CPU to acknowledge a TCP connec-
tion attempt. After this time expires, if no TCP session
established, a new TCP connection attempt is made.

Expansion mod- 1–65535 10 In the expansion module, this timer limits the number
ule TCP re- of seconds to wait for a response after sending a re-
sponse timeout quest. After this time elapses, a retry is sent by es-
tablishing a new TCP connection and resending the
request. When set to 0, no time limit is applied.
In the main CPU, this parameter limits the time that
the main CPU waits for an authentication response
from the expansion module for the initial connection.
After this time elapses, it discards any unauthenticated
request.

Expansion mod- 0–65535 10 For the main CPU only:

ule fail download To download to an expansion module, the user down-
timeout loads first from the STS to the main CPU, and then
from the main CPU to the expansion module. As a
result, downloading to the expansion module may fail
due to problems in synchronization or communication.
The Expansion module fail download timeout pa-
rameter limits the number of seconds that the main
CPU waits for the expansion module to reboot and re-
connect after a failed STS download causes a restart.
During this time, the main CPU marks the expansion
module as Not Exist, but denies requests from other
expansion modules with the same frame ID.
When set to 0, the main CPU does not wait.

Expansion mod- 0–65535 60 In the main CPU, specifies the number of seconds
ule fail timeout to wait after getting a disconnect indication from the
to restart Expansion Microcode Interface (EMI). In this case, the
expansion module is marked as “fail” but active. During
this period (before the timeout):
● The module may resume connection without being
initialized.
● Requests from other expansion modules with the
same frame ID are denied.
After timeout, the module may still resume connection
(without being initialized), but other expansion modules
with the same frame ID may connect instead if they get
initialized (i.e. go through discovery and initialization,
and are given the same IP address). If the original
expansion then sends a request, it is denied.

476
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
When set to 0, the expansion module enters the fail
timeout state immediately after being disconnected.

In the expansion module, specifies how many seconds

to wait to perform a restart after getting a disconnect
from the EMI Server (Slave).
When set to 0, the expansion module never restarts as
a result of a disconnect.
NOTE: During disconnect from the EMI, the
application gets the PDV/KLV of the inputs.
The I/O modules are in fail mode and get the
PDV/KLV of the outputs.
Expansion mod- 0–65535 60 For expansion modules:
ule KeepAlive Number of seconds to wait after the last received com-
timeout munication before sending a keepalive message. The
keepalive message is used to keep the control channel
open between each expansion module and the main
CPU. This helps the expansion module know when the
main CPU is reset, so that it can reset itself.
When set to 0, no keepalive is sent.

Expansion mod- 0–65535 4 This parameter (measured in seconds) is the same

ule KeepAlive as the Expansion module KeepAlive timeout (see
timeout when previous parameter), but applies to any of the following
disconnected cases:
from main frame ● When a cable is disconnected.
CPU
● Immediately after the EMI gets connected (to en-
able the main CPU to detect frames faster after
restart).
As soon as a communication is received, the timeout
is set as in the Expansion module keepalive timeout
parameter.
Expansion mod- Enable / Disable When set to Enable, the expansion module sets the
ule sets main Disable main frame CPU as an NTP server.
frame CPU as When set to Disable, the main CPU performs time
NTP server synchronization and event sequencing for the expan-
sion module.
NOTE: If the Ethernet port of the main CPU is
not configured to retrieve its time from an NTP
server, this parameter must be disabled.
For more on time synchronization of expansion frames,
see the MC-IoT STS Advanced Features manual.

Expansion mod- n/a 0.0.0.0 For the main CPU only:

ule first frame IP The IP address to allocate for frame ID number 1.
address This address is given when replying to a discovery
request from an expansion module (each expansion

477
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
module “learns” its own IP address during discovery).
The IP address allocated to each subsequent frame
is this first IP address plus the frame ID minus one.
For example, if the first frame IP address is set to
10.100.100.101, then 10.100.100.105 is assigned
to frame number 5.
When set to 0.0.0.0, the main CPU produces the IP
address of the expansion frame by adding the frame ID
to the IP address of the main CPU expansion port.
IMPORTANT: The allocated IP address must be in the
same network as the main CPU (same subnet mask,
as defined for the main CPU expansion port).
Expansion mod- 1024– 8192 For the main CPU only:
ule read block 1048576 The size of the block when sending a file or image to
size an expansion module.

Main waits for 0–60 15 For the main CPU only:

expansion CPUs After redundancy switchover, the number of seconds
to recover af- the new active main CPU should wait for the expansion
ter redundancy CPUs to connect with it. If after that period they fail to
switchover connect, the main CPU issues a restart command for
all expansions.
When set to 0, the main CPU issues a restart com-
mand immediately after the switchover.

Standby CPU 1–60 5 Relevant to standby CPUs when the site supports I/O
waits to connect auto-recognition. The number of seconds the standby
with active CPU CPU waits for the active CPU to complete I/O auto-rec-
ognition and to send the recognized I/O module infor-
mation to the standby CPU so that it can complete the
startup.

A.3.21
IP Conversion Table Parameters (ACE3600/
ACE1000/MC-EDGE)
Table 159: ACE3600/ACE1000/MC-EDGE IP Conversion Table Parameters

Parameter Allowed Default val- Description

values ue
Maximum rows in IP 1–65535 200 The maximum number of entries in the IP con-
conversion table per version table for each link ID. The IP conver-
link ID sion table specifies Site IDs and IP addresses.

478
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.22
LEDs Management Parameters (MC-EDGE)
Table 160: MC-EDGE LEDs Management Parameters

Parameter Allowed Default Description

values value
LEDs operating ● Light up to time- When set to Light up to timeout, the LEDs illuminate at
mode out (default) CPU startup, and extinguish after the timeout defined in
the following parameter.
● Light up always
When set to Light up always, the LEDs on the LED pan-
el of the CPU and I/O modules are constantly illuminated.

Timeout for 1–6000 6000 When the previous parameter is set to Light up to time-
switching the out, pressing PB for five seconds lights up the LEDs for
LEDs off the number of seconds defined in this parameter.

A.3.23
MDLC GW API Parameter (MC-EDGE)
Table 161: MC-EDGE MDLC GW API Parameter

Parameter Allowed values Description

MDLC GW API ● Disable (de- This feature provides the ability to enable or disable the MC-
fault) EDGE MDLC API GW service. The MDLC API GW provides
the capability to handle GW API protocol with external GW
● Enable API clients. This is a Motorola Solutions proprietary protocol
with a set of predefined APIs. The protocol is supported
through IP.

A.3.24
MQTT Parameters (MC-EDGE)
NOTE: For MC-EDGE firmware versions 21.00 and earlier, MQTT parameters appear under LoRa port
parameters.

Table 162: MQTT Parameters

Parameter Allowed Values Default Value Description

MQTT ● Disable (default) Enables or disables the MC-EDGE
Broker MQTT Broker. The following parame-
● Enable ters can be defined if the broker is en-
abled.
MQTT cli- ● Client certificate with MQTT name/pass- Allows you to select the TLS/mTLS
ent au- word authentication type for MQTT broker
thentica- with external MQTT client. The au-
tion type ● Client certificate with identity thentication may be protected with a
● Client certificate with subject name and password or a certificate, or
both.
● MQTT name/password only (default)

479
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Values Default Value Description

MQTT n/a n/a Double-click the cell to open the
Broker MQTT Broker Credentials dialog,
name/ which allows the user to enter the
password MQTT name and password. The
name and password may be mandato-
ry or not, depending on the selected
value of the MQTT client authentica-
tion type parameter. The MQTT brok-
er password must comply with a num-
ber of rules listed in the dialog box.
MQTT ● Disable (default) Provides external MQTT client(s) with
SCADA ta- the ability to get/set MC-EDGE SCA-
bles client ● Enable DA BL tables.
MQTT ● 0 - At most once (default) Message delivery quality of service
SCADA ta- for SCADA tables (if defined). This pa-
bles client ● 1 - At least once rameter is available when the MQTT
QoS ● 2 - Exactly once SCADA tables client parameter is set
to Enable.
MQTT ● Disable (default) When set to Enable, the MQTT Bridge
Bridge is enabled on this site. The bridge
● Enable is configured in the following parame-
ters, which appear when the bridge is
enabled.
Interface ● None This instructs the bridge through which
type interface to communicate with the re-
● LTE mote broker. The availability of ports
● ETH1 (default) depends on the chosen device. Ports
ETH2–ETH3 are available only on T2
● ETH2
sites.
● ETH3

Connection n/a n/a Mandatory. Assigns the bridge a

name name, which is used as the client ID
on the remote broker.
Connection ● TLS (default) Determines whether TLS security
type should be used.
● TCP (no TLS)

Connection n/a n/a Mandatory. Remote broker IP ad-

address dress.
Connection 1024–65534 ● 8883 (TLS) Remote broker IP port.
port
● 1883 (no TLS)

Remote n/a n/a Optional. Complete these fields if the

broker remote broker requires a name and
name password.
Remote
broker
pass-
word...

480
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Values Default Value Description

QoS (if no ● 0 - At most once (default) Message delivery quality of service
topics de- (only if no topics are defined). For
fined) ● 1 - At least once more information about topics, see
● 2 - Exactly once Defining MQTT Topics on page 481.

Keepalive 10–65535 60 Number of seconds after which the

interval bridge sends a ping if no other traffic
(sec) occurs.
MQTT top- n/a No topics – all messages For more information, see Defining
ic defini- are allowed in both direc- MQTT Topics on page 481.
tions... tions.

A.3.24.1
Defining MQTT Topics
STS allows you to define up to 10 specific topics for an MQTT bridge.

Procedure:
In the MQTT Topics dialog box, perform the following actions:
a. Define the Pattern using MQTT topic syntax.
This field cannot be empty.
b. From the Direction drop-down list, select the preferred setting.
The following settings are available:
● in
● out
● both
c. In the QoS level field, define the Quality of Service level.
d. Optional: In the Local prefix field, enter a local prefix.
e. Optional: In the Remote prefix field, enter a remote prefix.

A.3.25
Minisession Parameters (ACE3600/ACE1000/MC-EDGE)
Table 163: ACE3600/ACE1000/MC-EDGE Minisession Parameters

Parameter Allowed Default val- Description

values ue
Period of time that a 5–255 10 Number of seconds that a data frame re-
message is waiting in mains in the receive buffer. If the application
mailbox does not retrieve it during that time, the data
frame is deleted.

481
6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.25.1
Minisession Broadcasts
Table 164: Minisession Broadcasts

Parameter Allowed Default Description

values value
Broadcast 1–31 6 The number of boxes allocated for storing frames broad-
(group call) cast from the central unit and that are to be processed by
number of box- the RTU.
es The RTU scans the box queue at one-second intervals,
and updates the Qualifiers table accordingly. Increase this
value if the reception rate is greater than the queue scan-
ning rate.

Broadcast Enable / Enable Specifies whether to allow receipt of frames that were
(group call) Disable broadcast from the central unit without a password.
password Change the default if the central unit is capable of broad-
casting frames without a password.
RTU-to-RTU 0–20 0 Specifies the number of retries at the source/destination
number of TX level if an answer was not received for a transmission via
retries SndFrm (and not via TxFrm).
RTU-to-RTU In- 0–1000 0 Specifies the interval (in seconds) between retries. This
terval between period of time starts after the Data Link layer of the MDLC
TX retries protocol finalizes the transmission of a frame (that is, after
it receives an appropriate ACK, or exhausts all retries at
From/To level).

A.3.25.2
Minisession Event and Burst
Table 165: Minisession Event and Burst

Parameter Allowed Default Description

values value
RTU To RTU 1–31 8 The number of boxes allocated at any given time for
number of transmitting data frames via the Burst and TxEvnt func-
boxes tions.
RTU To RTU 0–20 1 Number of retries to be performed by the RTU towards
number of TX the central unit, if it does not receive “Application Data-
retries Ack from central” to Burst or TxEvnt calls. If the value of
the “Application Data-Ack from central” is NO, this param-
eter is irrelevant (because the system relies on ACK at
Data Link level, that is, at the From/To level, and does not
need any further acknowledgments at RTU/Central Unit
level).
RTU To RTU 1–1000 60 The interval of time (in seconds) that should elapse be-
Interval be- tween two retries from the RTU towards the central unit.
tween TX re- (Retries may be requested if the RTU does not receive
tries

482
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
“Application Data-Ack from central” to Burst or TxEvnt
calls. See previous parameter.)
This period of time starts after the Data Link layer of the
MDLC protocol finalizes the transmission of a frame (that
is, after it has received an appropriate ACK or exhausted
all retries at From/To level).
If the value of the “Application Data-Ack from central” is
NO, this parameter is irrelevant (because the system re-
lies on ACK at Data Link level, that is, at the From/To
level, and does not need any further acknowledgments at
RTU/Central Unit level).
RTU To RTU Enable / Enable Enables the user to transmit events of bursts with a com-
Password Disable munication password.
The value of this parameter must be identical for all RTUs
and the central unit.

Event and No / Yes Yes When set to Yes, the system requires that the central unit
Burst Applica- issues an ACK to the RTU (RTU/Central Unit level), in
tion data ack addition to a Data Link ACK.
from central When set to No, the system relies on a Data Link ACK (at
the From/To level) without the need for an ACK from the
central unit at RTU/Central Unit level.

A.3.25.3
Minisession RTU to RTU
Table 166: Minisession RTU to RTU

Parameter Allowed Default Description

values value
RTU-to-RTU 1–31 8 Number of boxes allocated at any given time for han-
number of box- dling data frames in RTU-to-RTU communication (re-
es ceived, transmitted, waiting for answer, empty).
Data frames are the information stored in Txbuf in case
of transmission, and in Rxbuf in case of reception.

RTU-to-RTU 0–20 1 Specifies the number of retries at the source/destination

number of TX level if an answer is not received for a transmission via
retries SndFrm (and not via TxFrm).
RTU-to-RTU In- 1–1000 60 Specifies the interval (in seconds) between retries. This
terval between period of time starts after the Data Link layer of the
TX retries MDLC protocol finalizes the transmission of a frame (that
is, after it receives an appropriate ACK, or exhausts all
retries at the From/To level).
RTU-to-RTU Enable / Enable Determines whether data frames are protected by a
Password Disable communication password. The value of this parameter

483
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
must be identical in both the transmitting and the receiv-
ing side.

A.3.25.4
Minisession Authentication Client
NOTE: These parameters pertain only to secured systems.

Table 167: Minisession Authentication Client

Parameter Allowed Default Description

values value
RTU-to-RTU 1–31 24 Number of boxes allocated at any given time for han-
number of box- dling data frames in RTU-to-RTU communication (re-
es ceived, transmitted, waiting for answer, empty).
Data frames are the information stored in Txbuf in case
of transmission, and in Rxbuf in case of reception.

RTU-to-RTU 0–20 0 Specifies the number of retries at the source/destination

number of TX level if an answer was not received for a transmission
retries via SndFrm (and not via TxFrm).
RTU-to-RTU In- 1–1000 3 Specifies the interval (in seconds) between retries. This
terval between period of time starts after the Data Link layer of the
TX retries MDLC protocol finalizes the transmission of a frame
(that is, after it receives an appropriate ACK, or exhausts
all retries at the From/To level).
RTU-to-RTU Enable / Enable Determines whether data frames are protected by a
Password Disable communication password. The value of this parameter
must be identical in both the transmitting and receiving
side.

A.3.25.5
Minisession Authentication Server
NOTE: These parameters pertain only to secured systems.

Table 168: Minisession Authentication Server

Parameter Allowed Default Description

values value
RTU-to-RTU 1–31 24 Number of boxes allocated at any given time for handling
number of box- data frames in RTU-to-RTU communication (received,
es transmitted, waiting for answer, empty).
Data frames are the information stored in Txbuf in case
of transmission, and in Rxbuf in case of reception.

484
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
RTU-to-RTU 0–20 0 Specifies the number of retries at the source/destination
number of TX level if an answer was not received for a transmission via
retries SndFrm (and not via TxFrm).
RTU-to-RTU In- 1–1000 3 Specifies the interval (in seconds) between retries. This
terval between period of time starts after the Data Link layer of the
TX retries MDLC protocol finalizes the transmission of a frame (that
is, after it receives an appropriate ACK, or exhausts all
retries at the From/To level).
RTU-to-RTU Enable / Enable Determines whether data frames are protected by a
Password Disable communication password. The value of this parameter
must be identical in both the transmitting and receiving
side.

A.3.26
NTP Parameters (ACE3600)
Table 169: ACE3600 NTP Parameters

Parameter Allowed Default Description

values value
Disable NTP Yes / No No Determines whether NTP is disabled. If a port is configured
from running as GPS, it operates without NTP.
Disable NTP Yes / No No Determines whether NTP is prevented from updating the
from updat- clock.
ing clock
NTP in De- Yes / No No Determines whether NTP runs in Debug mode. In debug
bug mode mode, debug messages are printed from NTP to the inter-
nal SMC debug port and can be viewed using Hypterminal.
NOTE: Debug mode slows down the NRP task.

NTP correct Yes / No Yes Determines whether NTP corrects the time offset (if any).
any time off- When set to No, a time offset that is too large is ignored.
set If an extremely large time offset is received several times,
NTP aborts, an error is logged, and the unit must restart in
order to resume NTP.
Clock drift (–500)– 0 Expected frequency drift (in pulses per minute) of the RTU
frequency 500 clock from its server(s) and GPS (if any). Retaining the
(PPM) default value (0) is recommended.
Max sync off- 0–500 0 Maximum permitted offset of the RTU clock from its NTP
set in msec server(s). If the offset exceeds this amount, the NTP serv-
ers are polled frequently to correct the offset, possibly
causing a heavy communication load. When set to 0 (de-

485
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
fault), the offset is not checked. Retaining the default value
is recommended.
NOTE: The clock offset depends on the media
used, ranging from 1 millisecond (in LAN) to 100
milliseconds (in GPRS). Query the SW Diagnostics
at Device: NTP, Level: 1 to see the average clock
offset in seconds. Level: 10 shows the maximal
average clock offset obtained.
Minimal poll 1–64 2 Minimal interval (in seconds) between polling the NTP
interval in server(s). NTP works by polling its servers. This is the min-
sec imal interval. After a poll and sync, the interval to the next
poll is multiplied until reaching the Maximal poll interval in
seconds (see the following parameter).
NOTE: When contact with the server is lost, the
minimal poll interval is used to resync as fast as
possible.

Maximal poll 1– 1000 The maximal interval in seconds between polling the NTP
interval in 1311072 server(s). See Minimal poll interval in sec (previous pa-
seconds rameter).
Transmit Yes / No Yes Determines whether a burst should be transmitted when
BURST when polling NTP servers. When set to Yes, upon each poll, sev-
poll eral messages are sent every few seconds apart in order
to sync as fast as possible. If a single poll message is sent
(when set to No), sync takes longer.
Transmit ver- Yes / No Yes Determines whether NTP version 3 frames should be
sion 3 frames transmitted or not.
Time sync 0–65535 120 When no reply is received from the NTP server after a poll,
lost before specifies the number of seconds to wait before declaring
declare ‘no ‘no sync.’ During this wait period, polling is increased. If ‘no
sync’ in sec sync’ is declared, the ClockValid in the Reserved Flags da-
tabase system table is set to 'no,' and a message is logged
in the Error Logger (see the following parameter). If GPS or
another clock source is configured, ‘no sync’ occurs when
no valid satellite/clock source status is received for this
period of time.
Notify error Yes / No Yes Determines whether notification should be sent to the Er-
logger when ror Logger when declaring ‘no sync.’ When set to Yes
losing sync (default), a message is logged into the Error Logger when
getting into "no sync" state after being in sync. If ‘no sync’
again, no message is logged until the user retrieves SW
diagnostics for Device: NTP, Level: 10
NTP option n/a n/a Reserved for advanced NTP settings. Leaving this parame-
#1 ter blank is recommended.
NTP option
#2

486
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
NTP option
#3
NTP option
#4
NTP option
#5

A.3.27
NTP Service Parameters (MC-EDGE)
Table 170: MC-EDGE NTP Service Parameters

Parameter Allowed values Description

NTP Service ● Disable (default) This feature provides the ability to define
up to two external NTP servers, which the
● Enable MC-EDGE NTP client can query for time
synchronization. If the feature is enabled,
the MC-EDGE NTP client queries the NTP
servers.
The connectivity may be through any sup-
ported IP (ETH, LTE).

NTP primary server

Name or IP address Server name or IPv4 address The first external NTP server; an empty
(<0.0.0.0-255-255-255-25 line means no server.
5>)

Interface ● LTE The first NTP server interface definition.

● ETH1 (default)
● ETH2
● ETH3

NTP secondary server

Name or IP address Server name or IPv4 address The second external NTP server; an emp-
(<0.0.0.0-255-255-255-25 ty line means no server.
5>)

Interface ● LTE The second NTP server interface defini-

tion.
● ETH1 (default)
● ETH2
● ETH3

487
6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.28
Network Parameters (ACE3600/ACE1000/MC-EDGE)
Table 171: ACE3600/ACE1000/MC-EDGE Network Parameters

Parameter Allowed Default Description

values value
System con- 1–50 1 Number of paths the Network layer is allowed to learn. This
figuration parameter is for future use. In the current version, Network
stock size can learn only one path (even if a different value is speci-
fied).
Addr. range (–100)– 0 For assigning alternate addresses to an RTU. If the basic
response for 100 address is X and the range is Y, then the unit responds to
'All RTU sim- all calls in the range of {X,X+1,...,X+Y}. If the range is -Y, the
ulation' <Si- unit responds to all calls in the range of {X-Y, X-Y+1, ..., X}.
tID + This parameter is for field simulation in laboratory condi-
(-100)-100> tions. For sites that support redundancy, this parameter is
modified by the STS. For more information, see “RTU Re-
dundancy” in the MC-IoT STS Advanced Features manual.
NOTE: To use this parameter in secured systems,
the M2M credentials configuration must be set to
Common. For more information, see “Unique or
Common M2M Credentials” in the MC-IoT Ad-
vanced System Security User Guide. For informa-
tion on other aspects of All RTU simulation in a se-
cured system, see “User Authentication Types” in
the MC-IoT Advanced System Security User Guide.

Time To Live 0–255 0 The preset value for the Time To Live counter, which is
preset value inserted into each frame by the frame originator. When set
to 0, the Time To Live Counter feature is not activated. The
value must be greater than the longest path in the network
(the total number of nodes in the longest path).
NOTE: Activating this feature requires that all units
in the system support this feature. Failure to comply
with this requirement will result in lost frames.

Remote 0–200 0 The maximum number of entries in the Remote Failed Links
Failed Links Table. When set to 0, Remote Failed Links awareness is not
Table size activated.
NOTE:
To activate this feature:
1. All units in the system must support this feature.
2. The Time To Live Counter feature must be ac-
tive.
Increasing this value to more than 100 may require
an increase in the Stack size of the application
manager task for using SW Diagnostic device
NSTOCK level 5.

488
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
Remote 0–255 15 When the Remote Failed Links Table feature is enabled,
Failed Links sets the maximum time an entry will live in the Remote
Table entry Failed Links Table. When the timeout has expired, the entry
timeout (min) is removed from the table.
Do not route Yes / No Yes When the Remote Failed Links Table feature is enabled,
returned determines whether a returned frame from a remote failed
frame link is dropped or rerouted to the destination using another
available link. When set to Yes, only the next transmission
will choose another available path.

A.3.29
PLC Parameters (ACE3600)
The following parameters do not apply to the ACE4600.

A.3.29.1
PLC Heap
For background on the PLC, see the ACE3600 Third Party Protocols Support manual.

Table 172: ACE3600 PLC Heap Parameters

Parameter Allowed Default Description

values value
Number of buffers 5–30 14 Number of communication buffers in HEAP for one
per each PLC port PLC port.
Maximum buffer size 160– 300 Maximum buffer size (in bytes) in the PLC heap.
2200

A.3.29.2
PLC MOSCAD as Client (Master) (Ladder Diagram)
The two following parameters are relevant for a ladder application performing third party PLC communication.

Table 173: ACE3600 PLC MOSCAD as Client (Master) Parameters

Parameter Allowed Default Description

values value
Maximum reply 2–200 70 Maximum time during which a reply from the local
timeout from local PLC (the PLC directly connected to the PLC port) is
PLC (100 msec) anticipated. If a reply is not received by the end of
this period, the value of the PLCStt variable is set to
“PLCtim” to inform the ladder.
Maximum reply 2–3000 300 Maximum time during which a reply from a remote
timeout from re- PLC (the PLC that is not connected to the current
mote PLC (100 MOSCAD) is anticipated. If a reply is not received by
msec)

489
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
the end of this period, the value of the PLCStt variable
is set to “PLCtim” to inform the ladder.

A.3.30
PPP Parameters (ACE3600)
Table 174: ACE3600 PPP Parameters

Parameter Allowed val- Default Description

ues value
Clusters size 640–100000 640 Amount of memory (in kbytes) used for buffer alloca-
for PPP ports tions when communicating over PPP; used by all PPP
ports.
RAM size for 640–100000 640 Amount of RAM (in kbytes) used for dynamic alloca-
PPP ports dy- tion of memory; used by all PPP ports.
namic alloca-
tion

A.3.31
Power Management Parameters (ACE3600)
Table 175: ACE3600 Power Management Parameters

Parameter Allowed Default Description

values value
LEDs operating ● Light up to time- When set to Light up to timeout, the LEDs illuminate at
mode out (default) CPU startup, and extinguish after the timeout defined in
the following parameter.
● Light up always
When set to Light up always, the LEDs on the LED pan-
el of the CPU and I/O modules are constantly illuminated.
For information on the LEDs behavior, see the ACE3600
RTU Owner’s Manual.
Timeout for 1–6000 6000 When the previous parameter is set to Light up to time-
switching the out, pressing PB1 for five seconds lights up the LEDs for
LEDs off the number of seconds defined in this parameter.
Power manag- 1–200 20 Size of the message queue for the power manager, used
er’s message to accumulate requests for Power Management opera-
queue tions.

490
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.32
Power Supply Parameters (ACE3600/ACE1000/MC-
EDGE)
To view/configure the power supply parameters, click Power Supply... button. In a system with I/O
expansion, click on the desired expansion frame in order to view/configure the power supply parameters
for that frame.

Table 176: ACE3600/ACE1000 Power Supply Parameters

Parameter Allowed val- Default val- Description

ues ue
PS Type ● AC 100-264V with charger ACE3600 only:
(default) Defines the power supply type.
● AC 100-264V
● DC 18-72V with charger
● DC 18-72V
● DC 12V
● DC 12V Low-tier
● DC 12V Expansion

Power supply ● OFF OFF ACE3600 only:

1 auxiliary 2 The voltage of the Auxiliary 2 output connector of
voltage ● 3.3V Power Supply 1. The Main setting is ~13.8 V @
● 5.0V 25°C. Relevant for the AUX2A and AUX2B connec-
tors.
● 7.5V
NOTE: In the default configuration, the
● 9.0V
Auxiliary 2 Voltage is set to OFF. It can be
● Main turned on by the application in the Main
power supply table. If a value other than
“OFF” is chosen, this sets the Auxiliary 2
switches to “ON” upon startup with the
chosen output voltage.

Power supply ● OFF OFF ACE1000, MC-EDGE only:

auxiliary volt- The voltage of the on-board Auxiliary output con-
age ● 5.0V nector.
● 7.5V
● 9.5V
● 12.0V
● Vin

Minimum DC 105–135 108 For ACE3600:

operation The minimum operating DC voltage for the RTU, in
voltage units of volts multiplied by 10 (for example, 105 =
10.5V). When the voltage is set to 105–135 and
the main input is disconnected, the unit works from
the battery, from an external DC power source, or

491
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default val- Description

ues ue
from a solar panel. Below this voltage, the RTU
shuts down.

Minimum DC 8000–30000 8000 For MC-EDGE:

operation Minimum operating DC voltage for the RTU, in mil-
voltage livolts (for example, 10500 = 10.5V). See also the
description of this parameter for the ACE3600.

External DC 4–20 4 For ACE3600:

recovery hys- The lowest voltage delta, in units of volts multiplied
teresis (volts by 10. This is added to the Minimum DC opera-
X 10) tion voltage for the Power Supply to restart the
CPU after the voltage falls below the minimum DC
operation voltage. For example, if Minimum DC
operation voltage is set to 110, and the External
DC recovery hysteresis is 4, the reconnect voltage
is 11.4 V (11.0 + 0.4). Below this value the RTU
does NOT restart.
This value is relevant only for external DC or solar
panel power supplies. For all other power supply
types, only the recovery of the Main input recon-
nects the RTU, and the reconnect voltage value is
set to 15.6V by the system (no matter what value is
set in this parameter). Thus, for these power supply
types, the reconnect voltage displayed in Hardware
Test or in SW Diagnostics is always 15.6V.
NOTE: The sum of the Minimum DC op-
eration voltage and the External DC re-
covery hysteresis should not exceed
15.5V.

External DC 400–2000 1000 For MC-EDGE:

recovery hys- The lowest voltage delta, in millivolts. This is add-
teresis ed to the Minimum DC operation voltage for the
Power Supply to restart the CPU after the voltage
falls below the minimum DC operation voltage.
See also the description of this parameter for the
ACE3600.

Power Supply ● 5 Ah ACE3600 only:

1 battery type The capacity (in Ah) of the battery connected to
● 6.5 Ah (default) Power Supply 1.
● 10 Ah NOTE: The power supply is not able to de-
● Other tect which battery is connected to it, and
performs all tests based on this configura-
tion value.

492
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.33
RISC Timers Parameters (ACE3600)
Table 177: ACE3600 RISC Timers Parameters

Parameter Allowed Default Description

values value
Base scan period 4–190 50 For internal use of the driver only. Used to set the resolu-
in microseconds tion (in microseconds) of the internal RISC Timers. Never
change this parameter without direction from product sup-
port.

A.3.34
Redundancy Parameters (ACE3600)
The following parameters do not apply to the ACE4600.

Table 178: ACE3600 Redundancy Parameters

Parameter Allowed Default Description

values value
Maximum RAM size for Re- 5–400 400 Maximum amount of memory used when
dundancy tables copy (KB) copying database tables from one RTU to its
redundant peer RTU.

A.3.35
RADIUS Service (MC-EDGE)
Table 179: MC-EDGE Radius Client Parameters

Param- Allowed Value De- Description

eter fault
Value
RADI- ● Disable Disa- The MC-EDGE RADIUS Client provides the abili-
US ble ty to approach external Domain Controller (RADI-
Service ● Enable US Server) for user-password verification
RADIUS primary server:
Name Server name or IPv4 address n/a Primary external RADIUS server IP/name; a
or IP of server blank line means no server.
ad- <0.0.0.0-255.255.255.25
dress 5>

Inter- ETH1, ETH2, ETH3, LTE ETH1 Interface for communication with the external
face server.
Port 1–65535 1812 Defines the server DTS port.
Time- 1–10 3 Specifies the number of seconds that the local
out device waits to receive a response from a RADI-
US server

493
6802979C10-BA
Appendix A: Site Configuration Parameters

Param- Allowed Value De- Description

eter fault
Value
Shared 14 to 128 characters n/a Specifies the shared secret key between the cli-
se- ent and the server.
cret...
RADIUS secondary server:
Name Server name or IPv4 address n/a Secondary external RADIUS server IP/name; a
or IP of server blank line means no server.
address <0.0.0.0-255.255.255.25
5>

Inter- ETH1, ETH2, ETH3, LTE ETH1 Interface for communication with the external
face server.
Port 1–65535 1812 Defines the server DTS port.
Timeout 1–10 3 Specifies the number of seconds that the local
device waits to receive a response from a RADI-
US server
Shared 14 to 128 characters n/a Specifies the shared secret key between the cli-
Secret ent and the server.
RADIUS tertiary server:
Name Server name or IPv4 address n/a Tertiary external RADIUS server IP/name; a
or IP of server blank line means no server.
address <0.0.0.0-255.255.255.25
5>

Inter- ETH1, ETH2, ETH3, LTE ETH1 Interface for communication with the external
face server.
Port 1–65535 1812 Defines the server DTS port.
Timeout 1–10 3 Specifies the number of seconds that the local
device waits to receive a response from a RADI-
US server
Shared 14 to 128 characters n/a Specifies the shared secret key between the cli-
Secret ent and the server.

NOTE: The shared secret can be saved either for this site only, or for all sites with this RADIUS server,
or for all RADIUS servers, in a similar way to SNMP passphrases described in Table 182: Apply
Settings on page 496.

494
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.36
SNMP Agent Parameters (MC-EDGE)
Table 180: MC-EDGE SNMP Agent Parameters

Parameter Allowed values Description

SNMP Agent ● Enable This feature provides the ability to enable or disable
the MC-EDGE SNMPv3 Agent. The SNMPv3 Agent
● Disable (default) provides the capability to handle SNMP MIBs proto-
col with an external SNMPv3 server. The protocol is
supported through IP.
SNMP Name 2 to 63 characters A MIB-II sysName.
SNMP Location n/a The sysLocation string of SNMP configuration.
SNMP Contact n/a The sysContact string of SNMP configuration.
MotoAdmin user... n/a (System 31.00 and older) Opens dialog for configu-
ration of MotoAdmin user parameters1.
MotoMaster n/a (System 31.00 and older) Opens dialog for configu-
user... ration of MotoMaster user parameters1.
MCIOT user... n/a (System 31.00 and older) Opens dialog for configu-
ration of MCIOT user parameters1.
Active MotoIn- ● MotoInformA (de- (System 31.00 and older) (NFM-EDGE only) Selects
form user fault) the active MotoInform user (either A or B).
● MotoInformB

MotoInformA n/a (System 31.00 and older) (NFM-EDGE only) Opens

user... dialog for configuration of the active MotoInform user
parameters1.
MotoInformB
user...

UEM network n/a (NFM-EDGE only) Opens dialog for modification of

managers... the list of UEM network managers.

1See the user configuration dialog below.

NOTE:
For NFM or AuxIO unit located in the K-core system, the UEM IP address is configured automatically by
the STS in the Static Route section of advanced parameters.
The default settings are:
For the IP address: 10.1.233.20
For the interface: ETH1
The user can change these settings to other values.
For system 32.00 or newer, the SNMP users are configured in the new SNMP User Credentials dialog
box. For more information, see Changing SNMP User Credentials (MC-EDGE) on page 218.

495
6802979C10-BA
Appendix A: Site Configuration Parameters

SNMP User Configuration Dialog (system 31.00 and older)

Figure 284: SNMPv3 - MCIOT User

This dialog displays parameters for configuring a specific SNMP user:

Table 181: Authentication Level

Level Description
noAuthNoPriv Communication without authentication and privacy.
authNoPriv Communication with authentication and without pri-
vacy.
authPriv Communication with authentication and privacy.

NOTE: For MotoAdmin user, authPriv is the only choice and it cannot be changed. For the other
user, the default choice is noAuthNoPriv.

Passphrases – configures passphrases for authentication and privacy when relevant (according to the
selected level). The passphrases must be 8 to 64 characters long.

Table 182: Apply Settings

Option Description
This site only Saves these security level and passphases only for this site (default).

496
 6802979C10-BA
Appendix A: Site Configuration Parameters

Option Description
All sites in the project Saves these parameters for all MC-EDGE sites in the project where
SNMP agent is enabled.
NOTE: When you press OK, the site configurations of other sites
in this project may change, and you may need to re-download
them to the respective sites.

All sites in zone <N> This option is displayed only for AuxIO sites where an ASTRO zone is
defined. The SNMP user settings will be saved only for the sites with the
same ASTRO zone.

NOTE: Both of the "all sites" options also store these parameters as defaults for this user. When
you add a site in the future and open the user dialog, these parameters will be auto filled based
on these defaults. The defaults are kept for the project and for each zone separately.

A.3.37
Session Parameters (ACE3600/ACE1000/MC-EDGE)
Table 183: ACE3600/ACE1000/MC-EDGE Session Parameters

Parameter Allowed val- Default Description

ues value
Application manager 2000– 5000 The workspace allocated to MDLC applications
workspace (bytes) 40000 for the transmission and reception of data
frames. Reserved for the development needs of
the software engineer (the end user is not ex-
pected to modify this parameter). It enables the
engineer to accurately determine the memory
requirements of MDLC applications.
Stack size of appli- 4000– 8048 Size of the stack to be allocated for the MDLC
cation manager task 10000 application manager task.
(bytes)
Encryption/Compres- 0–100 0 For future use.
sion buffer length
(bytes)
Number of retries to 1–5 4 Number of retries at session oriented logical
declare TX FAIL channel level, after which the Transport Layer
declares that transmission to the destination site
has failed.
Number of retries to 1–10 5 When the source site sends frames to a destina-
declare 'Logical chan- tion site, specifies the number of times to retry
nel BUSY' when a “logical channel busy” signal is received
(because the channels are busy transmitting da-
ta from other applications that already accessed
them). After this predefined number of retries,
the source site declares the channel “busy.”
Number of transmit- 2–32 4 Number of MDLC frames that are sent in a sin-
ted frames in one gle burst, after which the Transport Layer waits
BURST for ACK from the destination site before sending
the next burst.

497
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default Description

ues value
Number of entries in 5–32 16 Number of MDLC frames the Transport Layer
transmit queue is capable of receiving from upper layers (Appli-
cation, Presentation, and Session) for transmis-
sion. When this number is reached, the Trans-
port Layer signals to the application to stop
sending frames until it makes room for more
frames. This number should be at least twice the
size of the burst.
Number of entries in 5–32 32 Number of MDLC frames en route to the upper
receive queue layers that the receiving site is capable of han-
dling. This number should be at least twice the
size of the burst.
Number of entries in 5–64 64 Number of MDLC frames en route from the low-
temporary queue er layers (Data Link Reception, Network, Trans-
mission Multiplex) that the receiving site is capa-
ble of handling.
Task suspension be- 0–1000 50 A delay (in milliseconds) that can be inserted
tween transmitted between transmissions of frames in order to op-
frames timize CPU allocation to other processes (espe-
cially to processes that have a priority level low-
er than that of the application).
Interval between TX 1–1000 15 Specifies the interval (in seconds) that elapses
retries between two retries at the Source/Destination
level. This period of time starts after the Data
Link layer finalizes the transmission of a frame
(that is, after it receives an appropriate ACK,
or exhausts all retries for a frame that was not
acknowledged).
Interval between 'Lo- 1–1000 10 Specifies the interval (in seconds) between re-
gical channel BUSY' tries when the receiving end issues a BUSY sig-
retries nal (because all of its logical channels are busy).
Delay after last re- 1–1000 5 If the called unit receives only some of the
ceived frame for parti- frames that were supposed to arrive in one
al ACK burst, it waits the specified number of seconds
before issuing a partial ACK at the Source/Desti-
nation level.
Interval before start- 1–1000 50 Specifies the number of seconds that elapse be-
ing 'IS SESSION ON' fore the “is session on” check occurs. See the
checks following parameter.
Number of 'IS SES- (–1)–20 3 If a period of silence is detected in the channel
SION ON' checks at the Source/Destination level, a special mech-
anism checks whether the logical channel is still
available. This parameter determines the num-
ber of times that the channel is checked. In any
case, the first “is session on” check does not
take place before the timeout defined in the pre-
vious parameter.

498
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default Description

ues value
Interval between 'IS 1–1000 120 The interval (in seconds) between two “is ses-
SESSION ON' checks sion on” checks. See the previous parameter.

A.3.38
Static Route (MC-EDGE)
Table 184: Static Route (MC-EDGE)

Parameter Allowed Value Description

Static Route (MC-EDGE) n/a The Static Route section allows
the user to configure static
routes between the MC-EDGE
unit and other devices. For each
such device, its IP address and
the interface in the MC-EDGE
(e.g. ETH1) should be config-
ured.

A.3.39
Syslog Service (MC-EDGE)
Table 185: MC-EDGE Syslog Client Parameters

Parame- Allowed Value Description

ter
Syslog ● Disable (default) The MC-EDGE Syslog Client provides ability to
Service send events into an external Centralized Log-
● Enable ging event (Syslog Server)
Syslog Range: 0–7 Defines the syslog recording level
Priority
Default: 4 ● 0 – Emergency
● 1 – Alert
● 2 – Critical
● 3 – Error
● 4 – Warning
● 5 – Notice
● 6 – Info
● 7 – Debug

Syslog primary server:

Name or Server name or IPv4 address of the serv- Primary external Syslog server IP/name; a
IP ad- er blank line means no server.
dress <0.0.0.0–255.255.255.255>

499
6802979C10-BA
Appendix A: Site Configuration Parameters

Parame- Allowed Value Description

ter
Interface ● LTE Interface for communication with external serv-
er
● ETH1 (default)
● ETH2
● ETH3

Syslog secondary server:

Name or Server name or IPv4 address of the serv- Secondary external Syslog server IP/name; a
IP ad- er blank line means no server.
dress <0.0.0.0–255.255.255.255>

Interface ● LTE Interface for communication with external serv-

er
● ETH1 (default)
● ETH2
● ETH3

A.3.40
Time Sync Parameters (ACE3600/ACE1000/MC-EDGE)
Table 186: ACE3600/ACE1000/MC-EDGE Time Sync Parameters

Parameter Allowed/default values Description

Time sync ● Extended sync Defines what method is used when sending time synchroni-
method zation.
● Legacy sync (default) When set to Extended sync, the RTU sends sync proto-
col frames containing the time zone and password, with
nanosecond resolution (1 millisecond accuracy over syn-
chronous media [radio] and over asynchronous RTU to
RTU media).
NOTE: The RTU checks the password in extended
sync frames and authenticates sync messages be-
fore updating the clock. If it does not match, it is re-
jected. Query SW Diagnostics for Device:
TIMESYN at Level: 10 for statistics of received/
ignored sync frames.
Legacy sync is for synchronizing legacy MOSCAD RTUs
(no time zone or password, with milliseconds resolution).
This setting assumes that the sending RTU is in the same
time zone (5 millisecond accuracy).

What to do ● Ignore legacy sync When set to Ignore legacy sync messages, the RTU does
with re- messages not update the clock from when the legacy sync messages
ceived lega- are received. Otherwise, the RTU does updates the clock.
cy sync ● Don’t ignore legacy
messages? sync messages (de-
fault)

500
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.3.41
Time Tag Parameters (ACE3600)
The following parameters do not apply to the ACE4600.

Table 187: ACE3600 Time Tag Parameters

Parameter Allowed De- Description

values fault
value
Time tag 100–8192 4096 The time tag buffer stores two types of messages:
buffer size ● Messages regarding changes in the status of discrete in-
puts at locations defined as time tags.
● Clock synchronization messages.
Increase the buffer size (number of bytes) if you expect a
large number of changes.

A.3.42
Time Zone Parameters (ACE3600/ACE1000/MC-EDGE)
Table 188: ACE3600/ACE1000/MC-EDGE Time Zone Parameters

Parameter Allowed val- Default val- Description

ues ue
Time zone ● No time zone (default) ACE3600 only:
learning Determines how the time zone of the unit is set.
mode ● User configured
NOTE: If a user-configured RTU powers up
when daylight savings time is in effect, and er-
rors occur during startup, those errors are log-
ged with no daylight savings time.
When set to No time zone, the RTU is not configured
with a time zone, and the following parameter (Time-
zone offset in minutes) is ignored. If an extended
time sync frame is received, it will sync without adjust-
ing for the time zone. If the sync source is GPS or an
NTP server, its time will be GMT time. The Daylight
Savings database table is ignored.
When set to User configured, when an extended time
sync from the STS PC or another RTU in another time
zone is received, the clock sync is adjusted by the
time zone difference (based on the following parame-
ter, Timezone offset in minutes).
If the port is configured for GPS or NRP, the specified
time offset is added so that the unit time base is local
time and not GMT.
In this mode, daylight savings time start/end dates can
be specified in the Daylight Savings database table.

501
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default val- Description

ues ue
When the unit enters Daylight Savings mode, the time
tag logger is notified that the time has changed.

Time zone (–720)–720 120 ACE3600 only:

offset in The time zone offset from GMT (counting east). This
minutes parameter is relevant if the Time zone learning mode
parameter is set to User configured.

Time zone n/a UTC ACE1000, MC-EDGE only:

Sets the time zone for the location of the RTU.

A.3.43
Timer Event Parameters (ACE3600)
The following parameters do not apply to the ACE4600.

Table 189: ACE3600 Timer Event Parameters

Parameter Allowed val- Default Description

ues value
Maximum 10–10000 1000 Maximum time (in units of 10 milliseconds) that the
EVENT timer “event timer” can be activated.
value Event timers can be activated via the SetTmr func-
tion in relation to events that have been received via
GtEvnt. The timers and events are accurate within
10 msec. The timers are activated when the event
actually takes place (and not when GetEvent was per-
formed).
Increasing the maximum time consumes about 4
bytes per time unit.

Total number 10–1500 150 Along with the Maximum EVENT timer value param-
of EVENTs eter, defines the number of events and event timers
(status/timer) that can be received simultaneously.
Increasing the number of events consumes ~35 bytes
per event.

Timer event 30–1000000 150 After an event occurs, the delay (in milliseconds) re-
main frame quired to collect events from expansion frames to the
delay time main frame. After this interval, the events are availa-
ble to the user application via GetEvent. If this param-
eter is set too low, events may be lost.
Timer event 5–1000000 10 Time (in milliseconds) required to collect a number of
time to buffer events in the expansion frame before they are sent to
events in ex- the main frame. In a system with heavy traffic, the val-
pansion ue should be low. In a system with light traffic, raising
the value reduces communication overhead.

502
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default Description

ues value
Timer event n/a 57003 The UDP port number used for internal communica-
UDP port tion between the main frame and expansion frames.
number Retaining the default value is highly recommended.
Expansion 1–1000000 25 Time (in milliseconds) that the expansion frame waits
timer event re- for an acknowledgement from the main frame. After
quest timeout this time, an error message is logged.

A.3.44
Timer Service Parameters (ACE3600/ACE1000/MC-
EDGE)
Table 190: ACE3600/ACE1000/MC-EDGE Timer Service Parameters

Parameter Allowed Default Description

values value
Number of 10–300 150 The 100 msec task enables different modules to perform
connected specific activities with a resolution of 100 msec. This is
service-users achieved by allowing each module to link itself to the
with '100 100 msec task. The number of service users (modules)
msec' device depends on the configuration. Increasing the value of
this parameter is sometimes necessary if the configu-
ration includes more modules than the default number
specified here.
Number of '100 3–10 4 Specifies the number of times that the operating system
msec' ticks fails to activate the 100 msec task before an error mes-
passed before sage is sent to the Error Logger. The operating system
declaring error is designed to activate the 100 msec task every 100
msec. When set to 4 (default), an error message is sent
after four failures (that is, after failing to activate during
400 msec).
This is not a fatal error. If the system fails to activate the
task, this means that it is experiencing an unusual bur-
den. Investigating the origin of the problem is advised.

100 msec 0–8000 8000 Size of the 100 millisecond timer stack. When a user
stack size connects a routine to a specific timer, the timer stack
size may need to be increased if the routine activates
functions that in turn activate other functions.
Number of 10–300 30 The 1 sec task enables different modules to perform
connected specific activities with a resolution of 1 sec. This is
service-users achieved by allowing each module to link itself to the
with '1 sec' de- 1 sec task. The number of service users (modules) de-
vice pends on the configuration. Increasing the value of this
parameter is sometimes necessary if the configuration
includes more modules than the default number speci-
fied here.

503
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
Number of '1 2–5 4 Specifies the number of times that the operating system
sec' ticks fails to activate the 1 sec task before an error message
passed before is sent to the Error Logger. The operating system is de-
declaring error signed to activate the 1 sec task every 1 second. When
set to 4 (default), an error message is sent after four fail-
ures (that is, after failing to activate during 4 seconds).
This is not a fatal error. If the system fails to activate the
task, this means that it is experiencing an unusual bur-
den. Investigating the origin of the problem is advised.

1 sec stack 0–8000 8000 Size of the 1 second timer stack. When a user connects
size a routine to a specific timer, the timer stack size may
need to be increased if the routine activates functions
that in turn activate other functions.
1 min stack 0–8000 8000 Size of the 1 min timer stack. When a user connects a
size routine to a specific timer, the timer stack size may need
to be increased if the routine activates functions that in
turn activate other functions.
Number of 10–300 30 The 1 min task enables different modules to perform
connected specific activities with a resolution of 1 min. This is
service-users achieved by allowing each module to link itself to the
with '1 min' de- 1 min task. The number of service users (modules) de-
vice pends on the configuration. Increasing the value of this
parameter is sometimes necessary if the configuration
includes more modules than the default number speci-
fied here.
Number of 2–4 4 Specifies the number of times that the operating system
'1min' ticks fails to activate the 1 min task before an error message
passed before is sent to the Error Logger. The operating system is de-
declaring error signed to activate the 1 min task every 1 minute. When
set to 4 (default), an error message is sent after four fail-
ures (that is, after failing to activate during 4 minutes).
Number of 10–300 30 The 10 msec task enables different modules to perform
connected specific activities with a resolution of 10 msec. This is
service-users achieved by allowing each module to link itself to the
with '10 msec' 100 msec task. The number of service users (modules)
device depends on the configuration. Increasing the value of
this parameter is sometimes necessary if the configu-
ration includes more modules than the default number
specified here.
Number of '10 3–10 5 Number of times that the operating system fails to acti-
msec' ticks vate the 10 msec task before an error message is sent
passed before to the Error Logger. The operating system is designed to
declaring error activate the 10 msec task every 10 milliseconds. When
set to 5 (default), an error message is sent after five
failures (that is, after the 10 msec task fails to activate
during 50 milliseconds).

504
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default Description

values value
This is not a fatal error. If the system fails to activate the
task, this means that it is experiencing an unusual bur-
den. Investigating the origin of the problem is advised.

10 millisecond 0–8000 8000 Size of the 10 millisecond timer stack. When a user
stack size connects a routine to a specific timer, the timer stack
size may need to be increased if the routine activates
functions that in turn activate other functions.

A.3.45
USB Parameters (ACE3600)
Table 191: ACE3600 USB Parameters

Parameter Allowed Default Description

values value
USB host bulk 0–97 80 Relevant for Full Speed only: Specifies the percentage of
list enable time that the USB Host Controller chip accesses the bus
(BLE) off ratio (transfer of USB host data packets [bulk list] is OFF, and only
control and interrupt packets are transferred). Used to miti-
gate hardware performance issues concerning 100Mb Ether-
net when the USB Host is used.
Setting this ratio higher makes the USB slower by up to a
few hundred milliseconds when pinging the MotoTrbo. Set-
ting it lower makes the USB work faster, but may cause er-
rors when transmitting/receiving Ethernet packets larger than
1500 bytes over the 100Mb Ethernet port.

USB host par- 640– 1024 Size of the USB host partition in memory.
tition size in 8192
kbytes

A.3.46
User Application Parameters (ACE3600)
The following parameters do not apply to the ACE4600.

Table 192: ACE3600 User Application Parameters

Parameter Allowed val- Default Description

ues value
Timers ac- ● No condition The “By DON/DOF Fail” timer starts to decrease after its
tivation input fails. In the following example, TMR starts to decrease
● By DON/DOF Fail (de- only when ‘b’ gets 0.
fault)

505
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default Description

ues value

When set to No condition, the timers start to decrease

immediately (without regard to DON/DOF).
Time be- 0–10000 5 At the end of the main process and after the timeout speci-
tween fied by this parameter, the system checks for bursts await-
BURSTs ing transmission. If the period of time between bursts has
not yet elapsed, new bursts can be added to the buffer
during the next scan.
Number of 0–6 1 Number of frames for which a burst can be created during
BURST the same scan.
destina-
tion Buf-
fers
Minimum 20–200 50 The PPH calculation accuracy depends on the number of
calcula- samplings. The greater the number of samplings, the great-
tion period er the calculation accuracy for the specific period.
<20-200> For a minimum calculation period of 20, 5% accuracy is
scans achieved. For 200, the accuracy is 0.5%.

Flow input 1–10 4 Specifies the time (in units of 10 * msec) that elapses be-
scan rate tween two samplings of the PPH columns.
<1-10>
*10msec

A.3.46.1
Ladder Processes Tasks
Table 193: Ladder Processes Tasks Parameters

Parameter Allowed / de- Description

fault values
Task prior- ● Disable Enable these parameters if you intend to use the RUNP operator in a
ity A ena- ladder defined process with priorities TskPrA, TskPrB, TskPrC, or TskPrD
ble ● Enable OR MOSCAD_run_task() in a C application user task with priorities
(default) CB_TaskA, CB_TaskB, CB_TaskC or CB_TaskD. If you do not intend
Task prior-
to use RUNP/run_task(), disabling the parameters saves RAM (approxi-
ity B ena-
mately 2KB per task).
ble
NOTE: As soon as such a task priority is enabled, the first appli-
Task prior-
cation that actually runs the task (ladder or 'C' application) is the
ity C ena-
sole user of this task and no other application can run the same
ble
task.

506
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed / de- Description

fault values
Task prior-
ity D ena-
ble

A.3.46.2
Database Backup
Table 194: Database Backup Parameters

Parameter Allowed Default Description

values value
Maximum number of 127–250 127 Maximum number of backup operations that can
backup operations in be stored in the backup queue. For more de-
queue tails, see “Database Backup” in the MC-IoT STS
Advanced Features manual.

A.4
IRRInet-M Port Parameters
The IRRInet-M unit includes three on-board ports. Each port can be configured for different connections
(RS232, RS485, PPP, Ethernet, dial-up, etc.) to a number of media.For more information on the
communication ports, see the IRRInet-M RTU Owner’s Manual.
The Port parameters define the communications ports of the RTU site, the type of media connection to the
communication network and the devices connected to them. For each media type, a different set of port and
link parameters is available. For each media type, a default configuration is defined which can be modified.
To view/edit these parameters, click on a port in the site’s General or Ports tab. The possible port
configurations and port parameters are described below.
NOTE: Any change to the port type (i.e. parameters on the left side of the port definition, such as
Media, Connection/Operation Mode, Connection/Radio Type, Radio System, Modem), causes all
advanced physical and link layer parameters to return to their default settings.
Some of the port parameters which are already described above for ACE3600 ports are not repeated.

A.4.1
IRRInet-M Port 1
The following port configurations are available for IRRInet-M Port 1.

Table 195: IRRInet-M Port 1 Configurations

Configuration Description
Not Used Means that the specific port is not used. Setting a port to Not Used frees up any
resources that might otherwise be allocated to the port.
Default: Port 1: RS485 57,600 bps

RS232, RTU-to-RTU For local connection to another RTU in synchronous mode, via RS232.

507
6802979C10-BA
Appendix A: Site Configuration Parameters

Configuration Description
RS232, External Mo- For connection to an external modem using the MDLC protocol. The external
dem, Connection modem can be full-duplex, multi-drop half duplex, MAS (Radio/Line).
Mode
RS232, External dial- For connection to an external dial-up modem using the MDLC protocol.
up modem
RS485, RTU Multi- For local connection between two or more RTUs in asynchronous mode, via
drop, Multi-drop half RS485. The external modem can be multi-drop half duplex.
duplex (Default)
RS232, PPP, NULL For MDLC over IP above PPP connection type. Suitable for direct cable connec-
Modem tions over PPP. A LAN-connected IP Gateway, or an RTU with an Ethernet Plug
in board (EU), can communicate directly with these RTUs over the infrastructure,
if enabled by the operator. For further details, refer to the “MDLC over IP” section
in the MC-IoT STS Advanced Features manual.
NOTE: The EU can be configured using the Ethernet IP Interface Con-
figurator utility which is available only in MOSCAD Programming Tool-
Box V9.54 (with MOSCAD over IP option) or the MOSCAD-M Configura-
tor v3.50 and above (with MOSCAD over IP option.) For more informa-
tion, see the MOSCAD Programming ToolBox User Guide/MOSCAD-M
Configurator User Guide.

RS232, PPP, iDEN For MDLC over IP above PPP connection type. For further details, refer to the
Modem “MDLC over IP” section in the MC-IoT STS Advanced Features manual.
RS232, PPP, Stand- For MDLC over IP over packet data modem operating above PPP connection
ard modem types. This includes GPRS g18 modem and Tetra radios. A LAN-connected IP
Gateway can communicate directly with these RTUs over the infrastructure, if
enabled by the operator. For further details, refer to the “MDLC over IP” section
in the MC-IoT STS Advanced Features manual.
RS232, PPP, TETRA For MDLC over IP over Tetra radio above PPP connection type. Tetra infrastruc-
ture and radio should support packet data. The connection to Tetra can be
made via LAN or via radio. An IP Gateway can be connected to a LAN. For
further details, refer to the “MDLC over IP” section in the MC-IoT STS Advanced
Features manual.

A.4.1.1
IRRInet-M Port 1 Parameters
Table 196: IRRInet-M Port 1 Parameters

Parameter Description
Link name Contains the logical name of the link that the port is connected to. The link name is
automatically selected, based on the Port parameters. For example, if the connec-
tion type is External Dialup Modem, then the STS automatically selects DIAL as link
name. If relevant, you can open the drop down list and select another name.
Data speed If data speed is applicable to the port type parameters selected earlier, this param-
eter defines the communication data speed of the selected media. The default is
9600 baud.

508
 6802979C10-BA
Appendix A: Site Configuration Parameters

A.4.1.2
Advanced Physical and Link Parameters for IRRInet-M Port 1
After clicking one of the advanced parameters options, you can change a paramter. After changing a
parameter, you can restore all changes to their default, by clicking the Restore Defaults button. Modified
parameters appear against a green background.
For a description of any given Port 1 parameter, see the corresponding entry under the ACE3600 ports. The
description is the same, although the default values may vary for IRRInet-M RTUs.

A.4.2
IRRInet-M Port 2
The following port configurations are available for IRRInet-M Port 2.For an explanation of the selection
method and options, see IRRInet-M Port Parameters on page 507.

Table 197: IRRInet-M Port 2 Parameters

Parameter Description
Not Used Means that the specific port is not used. This definition saves RAM
memory (about 2Kb) that can be used by the application.
RS232, RTU-to-RTU (Default) For local connection to another RTU in synchronous mode, via
RS232.

A.4.3
IRRInet-M Port 2 Parameters
Table 198: IRRInet-M Port 2 Parameters

Parameter Description
Link name Contains the logical name of the link that the port is connected to. The link name
is automatically selected according to the Port Type parameters. If relevant, you
can open the drop down list and select another name.
Data speed If data speed is applicable to the port type parameters selected earlier, this pa-
rameter defines the communication data speed of the selected media. The default
is 9600.

A.4.3.1
Advanced Physical and Link Parameters for IRRInet-M Port 2
See Advanced Physical and Link Parameters for IRRInet-M Port 1 on page 509.

509
6802979C10-BA
Appendix A: Site Configuration Parameters

A.4.4
IRRInet-M Port 3
The following port configurations are available for IRRInet-M Port 3. For an explanation of the selection
method, options, and possible combinations, see Port 1 and Port 2.

Table 199: IRRInet-M Port 3 Configurations

Configuration Description
Not Used Means that the specific port is not used. This definition saves RAM memory
(about 2Kb) that can be used by the application.
Radio, External radio DPSK 1200 bps modulation for conventional radio. For all parameters that
type, max. number of re- appear italicized above, open the drop-down list and select the correspond-
peaters, modem ing value. Default is Radio, HT/GP/PRO, with DPSK modem, 1200 bps with
Auxiliary DC power level of 7.5V set in the Advanced configuration.
Line, modem Line communication via DPSK.

A.4.4.1
IRRInet-M Port 3 Parameters
Table 200: IRRInet-M Port 3 Parameters

Parameter Description
Link name Contains the logical name of the link that the port is connected to. The link name
is automatically selected according to the Port parameters. For example, if the
medium is Radio, then the STS automatically selects RADIO1 as link name. If
relevant, you can open the drop-down list and select another name.
Data speed If data speed is applicable to the port type parameters selected earlier, this
parameter defines the communication data speed of the selected media. The
default data speed varies based on radio type and modem type.

A.4.4.2
Advanced Physical and Link Parameters for IRRInet-M Port 3
See Advanced Physical and Link Parameters for IRRInet-M Port 1 on page 509. Many of the advanced
parameters for Radio/Line port configurations available for Port 3 are identical to those available for ACE3600
radio ports. The following additional configurations apply to Port 3 only.

Table 201: Advanced Physical and Link Parameters for IRRInet-M Port 3

Parameter Allowed val- Default val- Description

ues ue
Auxiliary PS 5V, 7.5V, n/a Defines the voltage level of the main power supply,
level 9.5V, 12V DC which supplies the power to the expansion board,
internal radio and the AUX power supply connector.
Changing the main power supply level changes the
power supply level for all of the above accordingly.
The available levels are: 5V, 7.5V, 9.5V and 12V DC.

510
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default val- Description

ues ue
If Port 3 is set to Not Used, the main power supply
level is set to 9.5V DC.
Tx-Holdoff 0-10000 0 The minimum interval between two consecutive trans-
time missions of data (not relevant for acknowledgment
messages).
Channel- 0-10000 40 The period of time during which the PTT should be
holding tail msec held pressed at the end of data transmission or be-
tween frames. Enter 0 to ignore this feature. The de-
fault for external radios is 40 msec.

A.5
IRRInet-M I/O Parameters
A number of Advanced I/O parameters can be set when configuring the IRRInet-M site. To view/edit these
parameters, click on the site’s I/O tab. The I/O Advanced Parameters are displayed on the bottom of the
screen. For each unit type (IRRInet-M AC or IRRInet-M DC), a different set of I/O parameters is available.

Table 202: IRRInet-M I/O Parameters

Parameter Allowed values Default val- Description

ue
Capacitor fail n/a 3 The number of times to try to charge the capacitor to
retries operation voltage after charging fails. (IRRInet-M DC
only).
Capacitor op- n/a 35V DC The capacitor operation voltage. It should be set ac-
eration volt- cording to solenoid specifications. (IRRInet- M DC
age only)
Reset DO at Yes/No Yes Whether the DO should be reset to 0 when the RTU
startup is started up.
Minimum 10-10000 ms 50 The pulse width for recognizing a DI change of state.
pulse width
recognition
Main AC Internal/External Internal The main board AC power source. (IRRInet-M AC
Power source only)
Expansion Internal/External Internal The expansion board AC power source. (IRRInet-M
AC Power AC only)
source
Voltage input AC/DC AC The input source of voltage. (IRRInet-M AC only)
source

511
6802979C10-BA
Appendix A: Site Configuration Parameters

A.6
Advanced Parameters (IRRInet-M)
This section reviews the STS advanced configuration parameters, which apply to the IRRInet- M unit.
Throughout the STS, advanced parameters are displayed according to context. For details on opening the
Advanced parameters windows, see the MC-IoT STS Operation on page 83. For each parameter, the range
of allowed values and a default value are listed.
NOTE: Exceeding the range may consume additional memory and may cause unexpected or incorrect
behavior in the RTU.
To view/edit these parameters, click on the site’s Advanced tab.
Parameters, which appear above for the ACE3600 RTU, may be repeated in the following sections.

A.6.1
IRRInet-M ‘C’ Application Parameters
Table 203: IRRInet-M ‘C’ Application Parameters

Parameter Allowed Default val- Description

values ue
Number of user 0-10 10 In addition to the 4 tasks defined by the system (Task
tasks for ‘C’ priority A...Task priority D), up to 10 additional tasks
blocks can be defined. These tasks can be activated via a
user-defined C function. The tasks can be activated
or suspended using a C routine. Each task allocates
≈2KB of stack. By default, CB_TaskA-CB_TaskD are
enabled in the IRRInet-M, but it is recommended that
the user use CB_TaskE-CB_TaskF, which are the high-
est priority user tasks. For details, consult the ‘C’ Tool-
kit for MOSCAD Family RTUs User Guide.
User ‘C’ task A Enable/ Enable The four tasks defined by the system.
Disable
User ‘C’ task B
User ‘C’ task C
User ‘C’ task D
Number of com- 0-100 1 It is possible to allocate memory from a ‘C’ block (using
mon named the MOSCAD_malloc ‘C’ function), to hold the allocat-
pointers ed buffer in named pointers between downloads, and
to get it back after the download ends. This feature
enables you to keep data between different downloads.
Variable pointers from one block can be passed from
one block to another.
Number of slave 0-255 4 Number of ‘C’ language functions to be supplied by the
‘C’ functions for ‘C’ application for session-based protocol. For more
session based information, see “DCF1” in the ‘C’ Toolkit for MOSCAD
protocol Family RTUs User Guide.
Number of ‘C’ 0-255 0 Number of ‘C’ language functions to be supplied by
functions called the ‘C’ application to the 10 millisecond task. For more
by the 10 msec
task

512
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default val- Description

values ue
information, see “DCF2” in the ‘C’ Toolkit for MOSCAD
Family RTUs User Guide.
NOTE: 10 ms functions must have short exe-
cution times in order not to adversely affect im-
portant system functions.

Number of ‘C’ 0-255 5 Number of ‘C’ language functions to be supplied by the

functions called ‘C’ application to the 100 millisecond task. For more
by the 100 information, see “DCF3” in the ‘C’ Toolkit for MOSCAD
msec task Family RTUs User Guide.
Number of ‘C’ 0-255 5 Number of ‘C’ language functions to be supplied by the
functions called ‘C’ application to the 1 second task. For more informa-
by the 1 sec tion, see “DCF4” in the ‘C’ Toolkit for MOSCAD Family
task RTUs User Guide.
Number of ‘C’ 0-255 5 Number of ‘C’ language functions to be supplied by the
functions called ‘C’ application to the 1 minute task. For more informa-
by the 1 min tion, see “DCF5” in the ‘C’ Toolkit for MOSCAD Family
task RTUs User Guide.
Number of diag- 0-255 20 Number of ‘C’ language functions to be supplied by the
nostics func- ‘C’ application to the Software Diagnostic utility. These
tions for ‘C’ ap- functions add user-defined diagnostics about user C
plication blocks, in addition to the system diagnostics about the
system devices. For more information, see “DCF6” in
the ‘C’ Toolkit for MOSCAD Family RTUs User Guide.
Size of each 0-2048 3 Maximum buffer size in the heap used by the ‘C’ appli-
buffer in the ‘C’ cation.
application heap
Number of buf- 0-255 3 Maximum number of buffers in the heap used by the
fers in the ‘C’ ‘C’ application.
application heap
Size of I2phys 0-255 3 Number of ‘C’ language functions to be supplied by
functions table the ‘C’ application to the I2Phys. These functions inter-
face between the RTU's MDLC protocol other anoth-
er user physical protocols. For more information, see
“DCF7” in the ‘C’ Toolkit for MOSCAD Family RTUs
User Guide.
Size of dynamic 0-255 1 Number of ‘C’ language functions to be supplied by the
DB access func- ‘C’ application to the DB map. For Motorola use only.
tions table
Size of LOG- 0-3 3 Number of callback functions to be supplied by the
FLASH func- ‘C’ application for logging flash operations. The first
tions table entry in the table always contains the Program callback
function, the second entry always contains the Erase
callback function, and the third entry always contains
the Disable callback function.
RAM size for 1-300 K- 5 The amount of memory reserved for dynamic alloca-
dynamic alloca- bytes tions at runtime.
tion

513
6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed Default val- Description

values ue
‘C’ programs require dynamic allocations. Therefore,
the value of this parameter should be determined ac-
cording to the amount of memory required by the ‘C’
programs, or according to the number of ‘C’ program
blocks.

Number of en- 0-350 10 You can expand the regular Site table (a Database
tries in the dy- system table) using the dynamic site-table, which is
namic Site Ta- accessible via ‘C’ Toolkit.
ble
Number of ’10 0-100 0 The number of ‘C’ block 10 msec. timers that can be
msec’ timers for used. For details on how 10 msec. timers in ‘C’ block
‘C’ applications can be used, see the ‘C’ Toolkit for MOSCAD Family
RTUs User Guide.
Number of ’100 0-100 10 The number of ‘C’ block 100 msec. timers that can be
msec’ timers for used. For details on how 100 msec. timers in ‘C’ block
‘C’ applications can be used, see the ‘C’ Toolkit for MOSCAD Family
RTUs User Guide.

A.6.2
IRRInet-M Heap Parameters
Table 204: IRRInet-M Heap Parameters

Parameter Allowed val- Default Description

ues value
Number of for- 50-500 70 The number of formatted buffers designed for the follow-
matted buffers in ing:
TX-heap ● RTU-to-RTU burst
● event
● burst seq
● event seq transmissions
● Transmissions from MDLC applications such as: Di-
agnostics, Error Logger, Processes/Tables Monitor,
Site Configuration, and Downloader
If DEVICE=HP_F_TX is emptied frequently, increase the
value of this parameter.
NOTE: Each buffer consumes about 230 bytes
of RAM (160 for User data and 70 bytes for com-
munication slices.)

Number of for- 50-500 100 The number of formatted buffers designed for the follow-
matted buffers in ing:
RX-heap ● RTU-to-RTU burst
● event

514
 6802979C10-BA
Appendix A: Site Configuration Parameters

Parameter Allowed val- Default Description

ues value

● burst seq
● event seq receptions
● Receptions from broadcasts and MDLC applications
such as Diagnostics, Error Logger, Processes/Tables
Monitor, Site Configuration, and Downloader.
If DEVICE=HP_F_TX is emptied frequently, increase the
value of this parameter.
NOTE: Each buffer consumes about 230 bytes
of RAM.

Unformatted 10-1000 50 The size of the unformatted buffer that serves as asyn-
(Adapter) buffer chronous port. The overhead is ≈15 bytes. See the ad-
size vanced physical parameter Number of idles to announce
'End of RX'.
Formatted buffer 160-2000 160 The size of the formatted buffer.
size

A.6.3
IRRInet-M Leds Parameters
Table 205: IRRInet-M Leds Parameters

Parameter Allowed val- Default Description

ues value
Leds operating Light up to Light Al- This parameter determines whether the LEDs on
mode timeout/Light ways the LED panel of the CPU and I/O modules
Always are lit constantly or temporarily. If you choose
“Light_up_to_time_out”, the LEDs go on at CPU start-
up, and go off after the timeout defined in the next
parameter. If you choose “Light_up_always”, the LEDs
stay on.
Pressing the push-button (PB) one short press
changes to the next display mode. One long press
(several seconds) lights all LEDs regardless of the
display mode. When the push button is released, the
display returns to the CPU display state. However, if
the push button is pressed for 10 seconds, the display
returns to the CPU display state, even if the push
button is still pressed.

Timeout for 1-6000 6000 If the Leds operating mode parameter is

switching the Light_up_to_time_out, using PB1 lights up the LEDs,
LEDs off (sec) which remain on for the period of time defined in this
parameter.

515
6802979C10-BA
Appendix A: Site Configuration Parameters

A.6.4
IRRInet-M Power Management Parameters
The Power management advanced parameters below are used by the IRRIV application only.

Table 206: IRRInet-M Power Management Parameters

Parameter Allowed val- Default value Description

ues
Low battery re- 10-14 volt 11.5 The power level (in volts) at which a low battery
covery level recovers and resumes full functionality. A recov-
ery message is sent to the ICC by the IRRIV
Client (Master) RTU.
Low battery 10-14 volt 11.2 The power level (in volts) at which a low battery
warning warning is sent to the ICC (by the IRRIV Client
(Master) RTU.)
Low battery 10-14 volt 10.1 The power level (in volts) at which the IRRInet-
alarm M RTU reduces the functionality (including oper-
ation of outputs and RTU communication.) A low
battery alarm is sent to the ICC (by the IRRIV
Client (Master) RTU only.)
HW DC fail level n/a 9 The approximate DC power level (in volts) at
(approximate) which the unit, which fails and powers off.
volt

516
 6802979C10-BA
Appendix B: Ladder Diagram Language

Appendix B

Ladder Diagram Language

The ladder diagram language defines the functions, which can be performed by the RTU. To define the
control program, its outputs should be defined as a function of the inputs and time.
The user control program is divided into one or more processes. Each process has a name (up to 256
characters) and a short description, which appears next to the process name on the Process tab.
Each process consists of functions (rungs) that may have a logical name and a short description, which
appears next to the rung name. It is possible to add a detailed description of the function.
The logical name is necessary only when activating the JMP operator to that rung. Assigning a logical name
and a brief description to each rung is helpful when performing maintenance and modifications.
The first process in the Process List is always the main process. This process must be defined since it is
performed by the system. Additionally, the commands that activate other processes are issued from the main
process by special operators.
The system software performs the process in cycles. All rungs are executed sequentially in each cycle. The
time needed to perform one cycle is called “scan time.”

B.1
Inputs and Outputs
Each rung defines the behavior of an "output" (or "outputs") as a function of both the state of the "inputs" and
the time. The entire control program is defined by building a rung for each "output" (or "outputs") separately.
"Inputs" and "outputs" are designated by the general designation variables.
The words "inputs" and "outputs" are enclosed within quotation marks because these variables are not
necessarily physical inputs and outputs. They may also be "internal variables" - variables that comprise the
"output" of a rung and that may serve as an "input" in another rung. The use of such internal variables
enables the appropriate RTU to define and perform complex monitoring and control functions.
The relationship between the "inputs" and the "output" (the function) is indicated in a symbolic manner that
expresses a relationship of logical conditions between the "inputs" and the "outputs." The RTU executes
(computes) the logic function defined by the rung. The result for each "output" is either "1" or "0" where
"1" means "the rung is true" and "0" means "the rung is false." The operation on the "output" is performed
according to the result received from the rung.

B.2
Variables
The database includes variables of various data types. Each variable is described by a symbolic name:
<Name> for a single-column table and <Name>,<Index> for a multi column table.
The variables in the system may be of the following data types:
● Discrete
● Integer Value, Real Value, Byte Value, Long Value
● Integer Parameter, Real Parameter, Byte Parameter, Long Parameter
● Timers (three resolutions: Hours, Minutes, and Seconds)
● Mapped Discrete, Mapped Value, Mapped Byte, Mapped Long

517
6802979C10-BA
Appendix B: Ladder Diagram Language

● Discrete Input, Discrete Output

● Value Input, Value Output
● Scaled Analog Input, Scaled Analog Output
● Time-Tagged DI
● PPH
● Index
● Integer Constant, Real Constant, Byte Constant, Long Constant
● IP Address, IP Address Parameter
See Database Tables and Data Types on page 559 for reference.

B.3
Ladder Diagram Elements
The following chapter describes each element variable and its relevant data types.
The ladder-diagram language uses two types of elements:
● Elements that define relations to "inputs" ("input operator")
● Elements that define an operation to be performed on an "output" according to the "result" of the rung
("output operator")
The rung may be perceived as an "array" of contacts. The contacts are representing the states of the
relevant "inputs," through which "current" must "flow" towards the element that represents the operation to be
performed on the "output." When such a flow path exists, the rung is "true" and the appropriate operation is
performed on the "output." When a rung does not include any "input" element, it is considered true and the
output operation is always performed.

B.3.1
Normally-Open (N.O.) Contact Element

This element is used to designate an N.O. type contact element, such as:
● Switch
● Device
● Timer
● Internal variable
When entered, the element name appears above the element.
When the state of the element is "0" (false, not operating), the contact is open (not conducting current). When
the state of the element is "1" (true, operating), the contact is closed (connected, conducting current).

The above contact represents the state of switch SW1. When switch SW1 is activated, the contact
representing it is "connected", and when the switch is not activated, the contact is in its normal state (not
connected).

The data type of the variable above the N.O. element may be one of the following:

518
 6802979C10-BA
Appendix B: Ladder Diagram Language

● Discrete (internal bit)

● Discrete Input
● Timer Contact
● Mapped Discrete
● Discrete Output
● Time-Tagged DI

B.3.2
Relay On Element

This element designates an operation performed on a two-state element ("0" – not activated, "1" – activated).
When the name of the controlled element is entered, it appears above the element, as follows:

If the rung is "true", the element (in the above case, MOTOR) is activated. If the rung is "false", the controlled
element is stopped.

The data type of the variable above the "relay on" element may be one of the following:
● Discrete (internal bit)
● Discrete Output
As an example, consider the automatic operation of a heating coil (Heater). The coil is activated when a
heating control switch (HeatSw), and a float installed in a tank (LvLSw), are activated.
The rung for performing the activation of the heating coil should be as follows:

Only when both contacts are activated the rung is "true"; "current" reaches the "relay on" element and the
heating coil is activated. The order in which the two "input" elements appear in the rung is not important and
has no influence on its operation. In Boolean algebra, the rung above represents an AND operation:
Heater is "on" when:
HeatSw is "on" AND LvlSw is "on"
In notation form:
Heater = HeatSw^LvlSw

B.3.3
Normally-Closed (N.C.) Contact Element

Sometimes it is necessary to condition a rung on a certain device that is in the OFF state. This means that
the contact, which represents the device closes (conducts current) when the device is not activated and
opens (does not conduct) when the device is activated. This function is achieved by the Normally-Closed
Contact element.

519
6802979C10-BA
Appendix B: Ladder Diagram Language

The data type of the variable above the N.C. element may be one of the following:
● Discrete (internal bit)
● Discrete Input
● Timer Contact
● Mapped Discrete
● Discrete Output
● Time-Tagged DI
The Motorola Advanced Ladder-Diagram Language enables you to define complex rungs, with the only
restriction being that the branches of the rung do not cross each other logically.

1
Refer to the activation of the heating coil and add one more condition for its activation. Assume that a valve is
installed for emptying water from the container, and stipulate that the heating coil is activated on the condition
that the Valve is closed (not activated). The rung looks as follows:

When the Valve is not activated (the contact is closed), the rung is "true" and the heating coil is activated.

2
A motor (MOTOR) switches on when at least one of the three push-buttons (PB1, PB2, or PB3) is pressed,
but on the condition that an emergency relay (EMRG) is not activated:

3
Device X is activated when a current flows through any of the branches in the rung:

520
 6802979C10-BA
Appendix B: Ladder Diagram Language

B.3.4
Relay Off Element

The Relay Off element is the opposite of the Relay On element. When the rung is "true", the controlled device
is stopped; as long as the rung is not "true", the controlled device is operating.

The variable above the Relay Off element may be defined as one of the following data types:
● Discrete (internal bit)
● Discrete Output
For example, suppose that device C is to be stopped on the operation of device A or B:

If either A or B is operating, the condition of the rung is fulfilled and device C is not operating.

In Boolean algebraic notation this may be expressed as a NOR operation:

Note that if C stops when A or B is actuated, then C is activated when both A and B stop, as expressed in the
following rung:

Or in Boolean algebraic notation: C = A^B

The two rungs given for this example are equivalent. The De-Morgan law of Boolean algebra states that:

B.3.5
Comparators

Sometimes it is necessary to make a function (rung) conditional on the values of variables. For this purpose,
the language includes symbols representing four different types of comparators. When the equality or
inequality described by the comparator is fulfilled, the result is a closed "contact" (enabling the flow of current
through the "contact" of the comparator). When the equality or inequality is not fulfilled, an open "contact"
results.

The data type of the V1 and V2 variables may be one of the following:
● Integer Value, Byte Value, Real Value, Long Value

521
6802979C10-BA
Appendix B: Ladder Diagram Language

● Integer Parameter, Byte Parameter, Real Parameter, Long Parameter

● Value Input, Value Output
● Integer Constant, Real Constant, Long Constant
● Timers (hour, minute, second)
● PPH
● Index
● Mapped Value, Mapped Real, Mapped Long
● IP Address, IP Address Parameter
If one of the values is constant, then the second value should not be constant. If the variable is defined as a
timer, the system automatically refers to the "time-left" value (refer to Timers.) With the comparator operator,
you may use real values and integer values.

As an example of the use of comparators, refer again to the case of the heating element and add another
condition for its actuation: the temperature of the water in the tank must be less than 95°C. Suppose that
a thermometer with a continuous analog output is installed in the tank, connected to an analog input of the
RTU, and that an integer variable designated TEMP has been defined (in the value input data type).
The rung performing the required control function is described below:

"95deg" is a constant defined as equal to the value input corresponding to the analog reading of 95°C.

The comparator compares TEMP to 95deg. Only if it is less than 95deg (and, of course, all the other
conditions are also fulfilled) is the heater activated.
Using the example above, assume that instead of a constant, the temperature is compared to the value
obtained from an external potentiometer (which serves as a sort of thermostat). If we designate the value
obtained from the potentiometer with the symbolic name Preset (in the value input data type), we get the
following rung:

The condition "greater-or-equal to" and "smaller-or-equal to" should be written as follows: For Speed ≥ Limit:

For Speed ≤ Limit:

522
 6802979C10-BA
Appendix B: Ladder Diagram Language

B.3.6
Relay Latch (L) and Relay Unlatch (U) Elements

In some cases, it is more convenient to define separately;

● the conditions under which an "output" (relay or any other) is activated
● the conditions under which that same "output" is stopped (released)
Also, assume that while the conditions for its activation or release are not fulfilled, the "output" remains in its
last state. These two elements perform the respective operation on the "output" when the rung is true. The
symbol name of the relay output is always entered and appears above the element. When the rung is false, it
has no influence on the "output".

The data type of the variable above the "Relay Latch" and "Relay Unlatch" elements may be one of the
following:
● Discrete (internal bit)
● Discrete Output

For example, refer to the turning on and off of a lighting system from five different locations and with two
push-buttons in each location, shown below.

Five pairs of ON/OFF switches are connected to the RTU, which activates LIGHT.

The rung for performing this control function may be built in the conventional "START-STOP" circuit form:

Each momentary pressing of one of the ON switches activates LIGHT, which then provides "self-holding" or
latching function. Each momentary pressing of one of the OFF switches turns the lighting off.

523
6802979C10-BA
Appendix B: Ladder Diagram Language

The same control function may be performed using the ( L ) – "relay latch" and ( U ) – "relay unlatch" element:

The latching and unlatching operations occur only if the rung is true, therefore there is no need for "self-
holding" of LIGHT.

The advantages of these elements become apparent in complex systems where they are used with additional
elements that are explained in the following sections.

B.3.7
Reset (RST)

When the conditions of the rung are fulfilled, the variable that appears above the element is reset to zero.
This variable may be of the following data types:
● Integer Value, Byte Value, Long Value
● Integer Parameter, Byte Parameter, Long Parameter
● Value Output
● Index
● Retentive Timer
In the case of retentive timers, the RST operator presets the timer. That means the operator returns the timer
to its preset time so that it may be actuated again by an appropriate rung (see Retentive Timer (TRT) on page
529).
To zero a Real variable, use MOV to move the value 0 to it.

524
 6802979C10-BA
Appendix B: Ladder Diagram Language

B.3.8
Timers
One of the most important parts of any control system is the timer. The timer provides delays between
different processes or the activation of a certain process for a predetermined time period.
During database building, it is possible to define specific columns as Timers. The resolution of the Timer is
according to the selected type: Hours, Minutes, or Seconds Timer.
Each Timer may function as one of the following:
● On-Delay (DON) Timer
● Off-Delay (DOF) Timer
● Retentive Timer
The Timer mode of operation is set according to its definition as an output in the Ladder Diagram.
The Timer has an unlimited number of contacts of the "normally open" and "normally closed" types that may
be used as "inputs" to other rungs. (This is done simply by writing the same symbolic name that was used for
the output operator).
When defining a Timer in the Database Builder, its "duration time" (preset value) is also defined. The preset
value may be modified in the course of control program execution. This happens through other rungs by
using any "output" element that updates the value such as MOV, or Arithmetical Calculation operators. The
new preset value is used by the Timer when next started.

When all conditions of the rung are fulfilled, the value of the NewPst constant or variable is used as the new
preset for Timer1.

When you define constants to be used as preset values for timers, you should consider the following:
● For Hours Timer: the HH:MM preset value (0≤ HH≤ 99, 0≤ MM≤ 59) should be defined as 60(HH) + MM,
since in memory the Hours Timer counts with resolution of 1 minute.
● For Minutes Timer: the MM:SS preset value (0≤ MM≤ 99, 0≤ SS≤ 59) should be defined as 60(MM) +
SS, since in memory the Minutes Timer counts with resolution of 1 second.
● For Seconds Timer: the SS:mm preset value (0≤ SS≤ 99, 0≤ mm≤ 99) should be defined as 100(SS) +
mm, since in memory the Seconds Timer counts with resolution of 10 milliseconds.
● For Hours Timer and Minutes Timer you can define timers in the Time Constants table. In this table,
you can define timers in the XX:XX format.
The Time Constants table (one of the Constants tables) may be used for defining hour and minute timer
constants, without the need to perform the calculations described above.

B.3.8.1
On Delay Timer (DON)

The DON timer operates as a function of the rung's being true or false as follows:
1. When the rung is false, the timer is in its normal state (not actuated). All its "normally open" type contacts
are open. The contacts of the "normally closed" type are closed (actuated).

525
6802979C10-BA
Appendix B: Ladder Diagram Language

2. When the rung changes its state to true, the timer begins to run until its preset time period elapses. While
the timer is running, the state of its contacts is as described in the previous point.
3. When the preset time of the timer elapses, the timer changes its state to true. All its contacts of the
"normally open" type close while those of the "normally closed" type open.
4. As soon as the rung ceases to be true, the timer stops, returns immediately to its normal state. The state
of its contacts is once again as described in the first point. The On Delay Timers timing diagram is shown
below.

The "time left" comprises the delay time left. This time is kept at the preset value as long as the rung is false
and is then counted down when the rung is true. When the time left reaches zero, the "on delay" is finished.

The following are some examples of the use of "on delay" timer.

1. The pump PUMP1 is to be actuated 10 seconds after valve VLV1 is opened (actuated).

The contact Tmr1, which is a contact of the timer of the same name, is actuated 10 seconds after VLV1 is
actuated. It turns on PUMP1.
2. The light must turn on for a predetermined period of 10 minutes as a result of the momentary pressing of
the push-button START.

To explain this example, see the timing diagram given previously, and assume that the rung, which
actuates the timer is constantly true and ceases to be true for a short period of time.

526
 6802979C10-BA
Appendix B: Ladder Diagram Language

We get a pulse of the duration of the timer's preset time, plus the time for which the push-button was
pressed. (A "differentiator" may be used to cancel the influence of the push button on-time). The ladder
diagram for this example looks as follows:

3. Turn on a lamp every 4 seconds for a short time.

Before explaining this example, let us first explain the concept of "scan."
In order to execute the control program defined in the ladder-diagram, the RTU periodically performs all
functions written in the Ladder Diagram. It performs them one after another. After a certain period of time,
the RTU repeats this procedure. The performance of the Ladder Diagram functions is called "scan" and
the time between two scans is called "scan time".
Sometimes it is necessary to build, via the rungs of the ladder-diagram, a "clock function" for
synchronizing and actuating various processes. For our example, let us assume that such a "clock
function," designated CLOCK, is to be built. Also, that CLOCK should be true once every 4 seconds for
the period of one scan time.
Let us further assume that each time CLOCK is true, a lamp, designated LIGHT, is latched. The lamp is
turned off by an OFF condition external to the system.

The ladder diagram for performing these functions looks as follows:

527
6802979C10-BA
Appendix B: Ladder Diagram Language

CLOCK is a timer with a preset time of 04:00 seconds. The special rung in which the timer is actuated (on
condition that it is not true) provides a pulse, shown below.

In this example, the rung with the DON output must be located after the rungs using the timer contacts.
During that scan in which the timer concludes the countdown of the delay (the delay is over), it again
presets itself.

B.3.8.2
Off Delay Timer (DOF)

The operation of this timer is similar to that of the "on delay" timer, except that the delay starts with the
transition of the rung to the state of OFF ("0") instead of the transition to ON ("1").

The DOF Timer may be set to any one of the three resolutions: hours, minutes, or seconds.
The DOF Timer can generate a positive pulse with a duration that is equal to the Timer delay if it receives
TRIG (TRUE) for one SCAN. The appropriate rungs are described below.

528
 6802979C10-BA
Appendix B: Ladder Diagram Language

As an example let us assume that a delay is necessary between the two outputs A and B. Output B should
start 5 seconds after output A has started and stops 20 seconds after output A has stopped.

The two delays are added "in series," one influencing the upward transition and the other – the downward
transition. In this example the order in which the rungs are written is irrelevant and DOF can precede DON.

B.3.8.3
Retentive Timer (TRT)

529
6802979C10-BA
Appendix B: Ladder Diagram Language

The retentive timer operates as follows:

1. As long as the rung is true ("1"), the timer counts down from its preset time.
2. When the rung ceases to be true, the time left is "frozen". The timer stops counting, but remains at the
point in the countdown that it reached while the rung was true.
3. When the rung again becomes true, the timer resumes its countdown from the "frozen" point.
4. When the time left is zero, all the "normally open" contacts of the timer close, while all the "normally
closed" contacts open.
5. The retentive timer remains in this state until preset again by an RST output operator having the same
symbolic name as the timer.

The main application of the retentive timer is for accumulating the operating time of a certain installation
or device. Also, it is supplying an indication that a certain predetermined operation period has come to an
end. This indication may merely serve as a warning to the operator of the system, or may automatically start
another operation.
In cases where more than 99 hours must be counted, this may be done by combining a counter and a
retentive timer.

An RTU operates a motor, designated MOTOR, and that an external maintenance alarm via a lamp,
designated L1, should be activated after 75 hours of operation. After servicing the motor, a switch, SW1, is
pressed and the time count starts again. In this example, we use a retentive timer with resolution of minutes,
named MotrHr, that has a preset time of 75:00 hours.

530
 6802979C10-BA
Appendix B: Ladder Diagram Language

B.3.9
Differentiators: Positive (UP), Negative (DOWN)

The number of usable differentiators in the application is unlimited.

The operation of the differentiator is explained in the following example.

A stepping motor, designated StpMtr, is to be actuated by pulses of 0.5 second resulting from the pressing
of a switch designated STEP. The pressing of the switch may take longer than the actuating pulse itself. In
addition, the motor should not react to a further pressing of the switch within less than 4 seconds.

A convenient way for performing this task is to identify the start of the pressing of the switch by a
"differentiating operation" performed by the positive differentiator operator.
The differentiator is located on the branches of the rung as are the input operators. The task of the positive
differentiator is to identify and conduct current for the duration of one scan when all the contacts along the
branch, which includes the differentiator (from its beginning to the location of the positive differentiator), have
changed state from open to closed.
The task of the negative differentiator is to identify and conduct current for the duration of one scan when the
contacts from the beginning of that branch to the location of the negative differentiator stop being true.
In order to execute the task set in the example, two "off delay" timers must be used (refer to Timers above):
one of 0.5 second for actuating the stepping motor; the other of 4 seconds for preventing an additional
actuation. Both timers are actuated by the pressing of the switch (the 0.5-second timer actuates the 4-second
timer).
It should be noted that the differentiator in the first rung identifies the point in time at which the switch STEP is
pressed and timer T4S is not actuated. If STEP is pressed before the timer has completed its countdown, the
differentiator "waits" for the timer (on condition that STEP is still pressed).

531
6802979C10-BA
Appendix B: Ladder Diagram Language

The following are examples illustrating the influence of the differentiators in a more complex rung.

Relay (L) is executed every time that the function (AB)+C becomes true. In this case, the differentiator
influences the entire rung, from its beginning.

In the last rung, RELAY is unlatched when E is true in addition to one or both of the following conditions: F is
true or a COS (Change of State) from 0 to 1 in G and (H or K).

B.3.10
Count Up (CTU), Count Down (CTD)

If the rung with the CTU or CTD operator is true, then the variable above the operator can be:

532
 6802979C10-BA
Appendix B: Ladder Diagram Language

● incremented in the case of the CTU operator

● decreased in the case of the CTD operator
If the rung is true, its condition continues for more than one scan and only one count is required, a
differentiator must be included in the rung. This is to ensure that the output operator is activated only once.
The CTU and CTD operators may be used with the following data types:
● Index
● Integer Value, Byte Value, Long Value
● Value Output
● Timers (Hour, Minute, Second)
● Integer Parameter, Byte Parameter, Long Parameter
You can apply the CTU and CTD operators to a Real variable by using—[+] or —[-] where the added/
subtracted value is 1.

1
For a packing machine: when "n" products have been packed into a case, the conveyor belt on which the
cases are located should move forward to position the next case to be filled. For each product placed into a
case, a contact closes at an input designated LOAD. The conveyor belt is advanced via an output designated
STEP, which should be actuated for 1 second.

Where M = n – 1.
The COUNTR variable (of value data type) counts the cases. When COUNTR≥n a DOF Timer (see Off Delay
Timer (DOF) on page 528), named Pls1Sc, is activated with a preset time of 1 second. This timer activates
the STEP output and resets the COUNTR variable.

2
For a tank or reservoir that is filled through two pipes: each pipe is equipped with an output that emits a pulse
for every liter of liquid passed into the tank. The tank also has an outlet pipe equipped with the same kind of
output, which emits a pulse for every liter of liquid emptied from the tank. It is required to set up a counter to
indicate the exact quantity of liquid in the tank at any given time. Note that the pulses from the various pipes
may appear simultaneously.
The value, designated TOTAL, is incremented with every liter of liquid going into the tank, and decreased with
every liter of liquid going out of it. The value is always equal to the exact quantity of liquid in the tank at any
given time.

533
6802979C10-BA
Appendix B: Ladder Diagram Language

B.3.11
Jump (JMP)

The JMP operator is the only operator that affects the sequential order of the rungs performance. When the
JMP operator is activated, the program "jumps" to the rung whose name is specified above the operator.
The JMP operator may be used in the following two ways:
● Jump forward (skip)
● Jump backward (for a loop)
The jump forward is used to skip several rungs that should not be performed if the rung with the JMP
operator is true. For example, if FLAG is true, the program jumps to the rung named NEXT.

Using the JMP operator reduces the necessary memory space. The alternative to the JMP operator is to
insert a N.C. element (on the FLAG variable) in each rung to be skipped when FLAG is true. It also reduces
the time performance since some rungs are skipped.
The jump backward is usually used when performing a loop with an index.
The JMP operator should be used only for skipping rungs within the process and not between processes.
For jumping from one process to another, refer to Jump to Subprocess.
When using the JMP operator, it is not possible to add other output elements in the same rung.

B.3.12
Scan (SCN)

The Scan (SCN) operator is used for the following:

● Reading data from physical input modules to update a table column defined as Discrete Input, Value
Input, PPH, or Scaled AI.
● Writing data from a Discrete Output, Value Output, or Scaled AO column to the physical output modules.

534
 6802979C10-BA
Appendix B: Ladder Diagram Language

The SCN operator is also used for updating the Mapped Discrete or Mapped Value columns. The column
name above the operator indicates to the system if inputs are to be scanned or outputs to be updated. In
addition, the SCAN is used to get data from an external PLC using the Third-Party protocols (refer to the
MC-IoT STS Third Party Protocols Support manual).
Using this operator, the user can control the refresh rate for all types of variables. Important data should be
scanned at a high rate, while other data can be scanned at a low rate.

Refer to the following pumps table:

This table includes n+1 rows for n pumps and the following columns (variables):
● <Flow> – a Value Input variable that specifies the flow for each pump.
● <Presur> – a Value Input variable that specifies the pressure of each pump.
● <Fail> – a Discrete Input variable that indicates a failure of the pump.
● <Control> – a Discrete Output variable used a control for the pump operation.
The table includes other internal variables and parameters, not shown in the table.
The variables of this table are used by an algorithm to compute the Contrl output as a function of the
<Flow>, <Presur>, <Fail>, and other variables. Before performing the algorithm, the actual values of
these variables should be read (by using the SCAN operator) from the appropriate physical inputs of the I/O
modules into the table columns.
Once the algorithm has been performed, the calculated values of the Control column should be sent (by
using the SCAN operator) to the appropriate physical outputs of the I/O modules.

B.3.13
Move Low (MOV), Move High (MOVH)

MOV is an output operator; when the conditions of the rung are fulfilled, the value below the operator (A) is
stored in the <B> variable, specified above the operator.

The <A> variable may be of the following data types:

● Integer Value
● Real Value, Byte Value (MOV only)
● Integer Parameter, Real Parameter, Byte Parameter

535
6802979C10-BA
Appendix B: Ladder Diagram Language

● Long Value, Long Parameter (MOV only)

● Value Input, Value Output
● Integer Constant, Byte Constant
● Real Constant, Long Constant (MOV only)
● PPH
● Index
● Scaled AI, Scaled AO
● Mapped Value
● Mapped Long, Mapped Byte (MOV only)
● Discrete, Mapped Discrete
● IP Address, IP Address Parameter (MOV only)
The <B> variable may be of the following data types:
● Integer Value, Real Value, Byte Value
● Integer Parameter, Real Parameter, Byte Parameter
● Long Value, Long Parameter (MOV only)
● Value Output
● Index
● Scaled AO, Scaled AI
● PPH
● Mapped Long, Mapped Byte (MOV only)
● Mapped Value, Mapped Discrete
● IP Address, IP Address Parameter (MOV only)

Moving 8 bits to the low byte of an integer variable

The MOV operator may also be used to transfer eight bits (starting with a byte boundary) of discrete variables
to the low byte of an integer variable.

In this rung, the MOV operator takes a series of eight consecutive bits (starting with b1) from a single-column
table and inserts it to the low byte of A (the high byte of A is not influenced).
The following diagram describes the bits arrangement in the integer variable. Note that the first bit (b1) is
inserted into a7.

536
 6802979C10-BA
Appendix B: Ladder Diagram Language

The bits table may be of the following data types:

● Discrete (internal bit)
● Discrete Input
● Discrete Output
● Time-Tagged DI
● Mapped Discrete
The <A> variable may be of the following data types:
● Integer Value
● Value Output
● Integer Parameter

Moving the low byte of an integer variable to 8 bits

The MOV operator may also be used to transfer the low byte of an integer variable to eight consecutive bits,
starting with a byte boundary. The following rung transfers the low byte of A to eight consecutive bits of a
single-column, starting with the bit named b1.

The following diagram describes the operator in this case.

537
6802979C10-BA
Appendix B: Ladder Diagram Language

The <A> variable may be of the following data types:

● Integer Value
● Integer Parameter
● Value Input, Value Output
● Mapped Value
● Constant
● Index
The bits table may be of the following data types:
● Discrete
● Discrete Output

Moving 8 bits to the high byte of an integer variable

The MOVH operator is used to transfer eight bits of discrete variables to the high byte of an integer variable.

This operator takes a series of eight consecutive bits (starting from b1) from a single-column table and inserts
it to the high byte of A (the low byte of A is not influenced).
The following diagram describes the bits arrangement in the integer variable. Note that the first bit of the byte
(b1) is inserted into a15.

538
 6802979C10-BA
Appendix B: Ladder Diagram Language

The bits table may be of the following data types:

● Discrete (internal bit)
● Discrete Input, Discrete Output
● Time-Tagged DI
● Mapped Discrete
The <A> variable may be of the following data types:
● Integer Value
● Value Output
● Integer Parameter

Moving the high byte of an integer variable to 8 bits

The MOVH operator may also be used to transfer the high byte of an integer variable to eight bits.

The following diagram describes the operator in this case.

539
6802979C10-BA
Appendix B: Ladder Diagram Language

The <A> variable may be of the following data types:

● Integer Value
● Integer Parameter
● Value Input, Value Output
● Mapped Value
● Constant
● Index
The bits table may be of the following data types:
● Discrete
● Mapped Discrete
● Discrete Output
Sometimes it is necessary to hold groups of discrete variables as values for storing and communication
purposes. When it is necessary to perform an operation on these values, they should be transferred to a
column of single bits (having a name for each bit). At the end of the operation, the result is returned to the
value variable form.
The Packed column of the following multicolumn table includes 100 packed groups of bits (16 bits in each
packed group are represented as a value).

540
 6802979C10-BA
Appendix B: Ladder Diagram Language

The single-column table of discrete data type, named Unpacked Bits (below), includes 16 specific names for
each one of the bits in the Packed value. In this example we refer to the bits as Bit15, Bit14, etc. In a real
system, we refer to the bits in meaningful names such as, Status, Fail, Alarm, Contrl, etc. The order of the
bits is from Bit15 to Bit0 to fit the MOV operator.

The following rungs perform a loop with index over all 100 values in the Packed column. All values are
moved, each at a time, into the Unpacked Bits table. The algorithm is performed on the bits and the result is
returned to the Packed table; the index is advanced to the next row.
The dashed rungs perform the algorithm on the unpacked bits. The algorithm does not include an index since
the same algorithm is applied on all groups.
Bit15 is the first bit of the high byte and Bit7 is the first bit of the low byte.
Temp is a temporary variable of Integer Value type.

541
6802979C10-BA
Appendix B: Ladder Diagram Language

MOV/MOVH between an integer variable and a bits column of a multicolumn table

The operators that perform these operations are the following:

542
 6802979C10-BA
Appendix B: Ladder Diagram Language

BitCol is the name of the bits column of a multicolumn table. Note that in this case, the number 0 is not an
index, but the byte number (8 bits). BitCol,0 is the first byte, BitCol,1 is the second byte, and so on.
The data types for these four cases are as specified above.

B.3.14
Arithmetical Calculations

Arithmetical calculations are always used in the rung as output operators. When the conditions in the rung
are fulfilled (the rung is true), the calculation is performed and its result is stored in C (A and B are not
affected).
The A and B "inputs" to the operator may be of the following data types:
● Integer Value
● Integer Parameter
● Mapped Value
● Value Input, Value Output
● Index
● Real Value
● Real Parameter
● Scaled AI, Scaled AO
● Byte Value
● Byte Parameter
● Long Value
● Long Parameter
● Real Constant
● Integer Constant
● Byte Constant
● Long Constant
The C output of the operator may be of the following data types:
● Integer Value
● Integer Parameter

543
6802979C10-BA
Appendix B: Ladder Diagram Language

● Value Output
● Index
● Real Value
● Real Parameter
● Byte Value
● Byte Parameter
● Long Value
● Long Parameter
● Scaled AO
● PPH
In arithmetical calculations you cannot, normally, mix real values and integer values. However, to mix real
values and integers, you can move the integers to temporary Real-type variables and perform the operations
you want.
When defining the control program, take into consideration that the arithmetical calculations (in particular
multiplication and division) use considerable scan time. They should be performed only when strictly
necessary, and not with every scan.
The calculation is performed only when the rung is true. If the calculation is to be performed only once, the
positive differentiator must be inserted in front of the calculation symbol.
For example, the variable <X> must be divided once every second by the variable <Y>. The result should
be applied to an analog output (digital-to-analog conversion) connected to a meter that indicates a value
designated RATIO.

T1Sec is true for the duration of one scan once every second. Therefore, the calculation is performed every
second.
In many cases, a sequence of arithmetical calculations is to be performed only under certain conditions. In
such cases, the JMP operator may be used to skip over this sequence when the calculation is not required.

B.3.15
Boolean Algebraic Operations – AND, OR, XOR

544
 6802979C10-BA
Appendix B: Ladder Diagram Language

The AND, OR, and XOR operators perform (when the rung is true) a (Boolean) logic-bitwise operation on two
variables (designated A and B in the elements above), and the result is stored in the variable designated C (A
and B are not affected).
The A and B inputs to the operator may be of the following data types:
● Integer Value, Byte Value, Long Value
● Mapped Value, Mapped Byte, Mapped Long
● Value Input, Value Output
● Integer Parameter, Byte Parameter, Long Parameter
● Integer Constant
● Index
● Timers (hour, minute, second)
The C output of the operator may be of the following data types:
● Integer Value, Byte Value, Long Value
● Value Output
● Integer Parameter, Byte Parameter, Long ParameterIndex
● Timers (hour, minute, second)

B.3.16
CALC
The CALC function enables you to write arithmetic expressions as you would on paper.
The system software then calculates the expression according to common mathematical rules, (for example:
x+y*z is considered as x+(y*z)) and the result is stored in the output operator.
The inputs to the operator may be of the following data types:
● Integer Value, Real Value, Byte Value, Long Value
● Timers Hour
● Timers Minute
● Timers Second
● Integer Parameter, Real Parameter, Byte Parameter, Long Parameter
● Mapped Value
● Value Input, Value Output
● Scaled AI, Scaled AO
● PPH
● PLC Value Input
● PLC Value Output
● PLC Real Input, PLC Real Output
● Integer Constant, Real Constant, Byte Constant, Long Constant
● Index
The output of the operator may be of the following data types:
● Integer Value, Real Value, Byte Value, Long Value
● Timers Hour

545
6802979C10-BA
Appendix B: Ladder Diagram Language

● Timers Minute
● Timers Second
● Integer Parameter, Real Parameter, Byte Parameter, Long Parameter
● Mapped Value
● Value Output
● Scaled AO
● PPH
● PLC Value Output
● PLC Real Output
All the binary operators require two parameters of the same type, <integer value> or <real value>.
If one parameter is an <integer value> and the other is a <real value>, the <integer> is cast to
<real>.
The only exception to this rule is the power (^) operation, which always converts the operands to <real
value> data type.
A valid arithmetic expression may contain:
● The following operators:
+ (Plus), - (Minus), * (Multiply), / (Divide), ^ (Power), % (Mod), & (And), | (Or), $ (XOR), Log, Log2,
Log10, ACos, ASin, ATan, Cos, Sin, Tan, Exp, Sqrt, Abs, and Neg (negative).
Note that the operators are not case-sensitive.
● Balanced parenthesis.
● The string '<??????>' which represents an unknown symbol.
● "Blanks" (which are ignored during compilation).
Before using the CALC function for your computations, please note the following restrictions:
1. Do not use <bit> variables, neither in the expression nor in the result.
2. Do not use a <real value> operand in a logic operator, either as a symbol, or as a partial expression
result.
3. Enter only Radian values in the trigonometric functions.
4. Do not use the plus (+) symbol to label a positive number.
5. Use the Neg function to label a negative number. Do not use the minus (-) symbol for this purpose.
6. Do not use variable names, which are identical with the functions' names (for example: Sin and Cos),
since they will be considered as functions.
7. Do not include operator characters into the symbols names (for example: 'n1+n2' or 'n3/'), since the
characters will be considered as operators.
8. The user is responsible for the function's parameters legality. No warning appears if a function receives a
parameter with an illegal value. Examples of illegal values include: Log(0), Log2(0), Log10(0), Sqrt(<y>)
where <y> is a negative number, ASin(<x>) where <x><=1 and <x>>= -1, ACos(<x>) where <x><=1
and <x>>= -1, Tan(p/2+<n>*p) where <n> is an integer.
9. Each arithmetic expression may include up to 26 functions and 26 different variables.
10. The system software does not check the overflow during computation. The overflow is checked while
placing the expression result into the result symbol.
The ladder controlled ClcStt value is included in the Reserved Values table (System Tables). When an
overflow occurs, ClcStt is set to '1' and it is the user responsibility to reset it.

546
 6802979C10-BA
Appendix B: Ladder Diagram Language

The following example illustrates the significance of data type selection.

Let <x1>=1, <x2>=2 and <y1>=2 where <x1>, <x2> are of integer value data type and <y1> is real value.
The two rungs below provide different results for the same expression, due to the different selected data
types.
Figure 285: Rung 1

The above expression is calculated as follows: first <x1> is divided by <x2> (integer division) and the result
is 0. Then 0 is added to <x1> (integer addition), so the final result is 1. (Note that the expression is typed into
a Formula text box.)

Figure 286: Rung 2

The above expression is calculated as follows: first <x1> is divided by <y1> (<real> division), so the result
is 0.5. Then 0.5 is added to <x1> (real data type addition), and the final result is 1.5 if the "Result" variable
data type is <real value> and 1 if the "Result" variable data type is <integer>. In this case, the ClcStt
value becomes '1'.

B.3.17
Jump To Subprocess (JSP), Return (RET)

As mentioned earlier, it is very convenient to divide the control program into processes according to different
subjects. Each process should handle one table or a few tables. One way (see also Run Process) to activate
a process is to call it as a "subroutine" by using the JSP output element, as follows:

When all conditions of the rung ending with the JSP operator, are fulfilled, the system "jumps" to perform the
process, specified above the JSP operator, as a subprocess. It is also possible to call another subprocess
from that subprocess (subprocess nesting).
The performance of the subprocess stops when one of the following occurs:
1. The last rung has been performed.
2. A true rung that ends with the RET operator is encountered. When the program returns to the original
process (from which the subprocess has been called), it continues by performing the rung following the
rung with the JSP operator.

547
6802979C10-BA
Appendix B: Ladder Diagram Language

For example, refer to the following table that consists of n+1 rows (n+1 devices) and eight values (columns)
for each device (A to H).

There is a process, named FindH, that computes H as function of A to F and I (the row index):
H,I = H(I) = f(A,B,C,D,E,F,I). The process includes the necessary rungs to compute H for a specific row that
is, the index I is set and then the subprocess is called to compute H. Note that the "calling" process defines
the row while the "called" subprocess performs the computation as a separate algorithm.
Suppose that the DEVICE variable indicates the row number and I is defined in the Index table. The
appropriate rungs for calling the FindH subprocess are:

The FindH process:

The FindH process returns to the Main process if the last rung is performed or the algorithm has found that E
< D.

It is not necessary to use the RET operator in the last rung of a subprocess. Use this operator in a specific
rung (not the last one) when you condition the return to the calling process. When JSP or RET is used in a
rung as an output operator, it is not possible to add other output operators to that rung.

B.3.18
SEND

548
 6802979C10-BA
Appendix B: Ladder Diagram Language

The SEND operator enables you to send a free-format message to the ports defined as User Ports
(controlled by the Ladder Diagram). The User Ports may be used to connect a computer, printer, or any
other device that requires serial communication.
For a detailed description of this operator, see User Defined Local Ports on page 597.

B.3.19
Logical Shift to Left (LSL)/Right (LSR)

LSL
When the rung is true, a logical shift is performed on the variable (A), specified above the operator, n times (1
to 15) to the left. '0' are inserted to the shifted least significant bits.
The A variable may be of the following data types:
● Integer Value, Byte Value, Long Value
● Value Output
● Integer Parameter, Byte Parameter, Long Parameter
● Timers (hour, minute, second)
For example, if LSL is executed with n=4 on A=01011000 10101101, the result is: A=10001010 11010000.

LSR
The same as LSL, but with the shift to the right:

B.3.20
Arithmetical Shift to Left (ASL)/Right (ASR)

549
6802979C10-BA
Appendix B: Ladder Diagram Language

ASL/ASR
Arithmetical shift to the left/right of the integer variable <A>, n times (1 to 15). In the arithmetical shift the sign
bit (bit 15) of the value does not change when the shift occurs.
The <A> variable may be of the following data types:
● Integer Value, Byte Value, Long Value
● Value Output
● Integer Parameter, Byte Parameter, Long Parameter
● Timers (hour, minute, second)

ASL
Shift to the left.

ASR
Shift to the right.

For example, if ASR is executed with n=2 on A=01110101 10111001, the result is A=00011101 01101110.
Note that using ASL is multiplying by 2^n and using ASR is dividing by 2^n. It is more efficient (less time
consumption) to use the ASL or ASR operators to multiply/divide by 2, 4, 8, etc.

B.3.21
Rotate to Left (ROL)/Right (ROR)

ROL
When the rung is true, the bits of the A integer are shifted n times to the left. For every shift, the bit in a15 is
inserted in a0. Note that the rotated bits are "wrapped around" (in comparison to the shift operators).
The <A> variable may be of the following data types:
● Integer Value, Byte Value, Long Value
● Value Output

550
 6802979C10-BA
Appendix B: Ladder Diagram Language

● Integer Parameter, Byte Parameter, Long Parameter

● Timers (hour, minute, second)

ROR
The opposite of ROL (rotate right).

B.3.22
CAL

The CAL function allows "calling" various functions that receive and return variables through the various
tables in the system tables.
When the CAL operator is selected, a choice list of all available functions is displayed. Select the required
function by using the arrow keys and pressing Enter.
The following table lists the diverse functions:

Table 207: CAL Functions

Function Description
GetChr, GetDgt These functions are used to read characters or dig-
its from the User Port. For further information, see
User Defined Local Ports on page 597.
Ready This function controls the Data Terminal Ready
(DTR) and switches it from 'off' to 'automatic'. If the
input buffers are clear, the Data Terminal Ready is
'on', otherwise it is 'off'.
NotRdy This function switches the Data Terminal Ready
(DTR) from 'automatic' to 'off'.
SndFrm, AnsFrm, RcvFrm, TxFrm See User Defined MDLC Communication on page
612.

551
6802979C10-BA
Appendix B: Ladder Diagram Language

Function Description
SndSeq, GetSeq, BrstSq, Burst, TxEvnt, Evntsq See User Defined MDLC Communication on page
612.
Fetch, Store See “Accessing Database Variables via Coordi-
nates” in the System Tools Suite Advanced Fea-
tures Reference Guide.
GtEvnt, StEvnt, SetTmr, Time See “Event Driven Software” in the System Tools
Suite Advanced Features Reference Guide.
SetCOS This function sets the specified COS flag.
Sync This function allows for sites synchronization using
the ladder diagram language. The synchronizing
site time may be received from the Time&Date or
from the GPS connected to the synchronizing site's
port.
This function has two parameters: the function
name itself "Sync", and the Site ID, defined in the
Site table (System Tables).

AGA3, AGA7M, AGA7V See the MC-IoT STS AGA7+AGA8 (AGA78) Gas
Flow Calculations manual, available with AGA add-
on only.
P.I.D. See “PID LOOP - Proportional Integral Derivative”
in the System Tools Suite Advanced Features Ref-
erence Guide.
GtExDt See Expansions Reserved Values Table on page
583 and the System Tools Suite Advanced Fea-
tures Reference Guide.
SBO, SBOoperate, SBOreset, SBOselect See Reserved Values Table on page 577 and the
System Tools Suite Advanced Features Reference
Guide.
Tb2Cpy Relevant for redundant systems only. See Re-
served Values Table on page 577 and the System
Tools Suite Advanced Features Reference Guide.
GetSecLog Relevant for secured systems only. See “Security
Log Record Retrieval” and “User Application Pro-
gramming for a Secured System” in the Advanced
System Security User Guide.
StorBlock, RstrBlock, RmvBlock See “Database Backup” in the System Tools Suite
Advanced Features Reference Guide.

Following are two examples illustrating full system synchronization, and the synchronization of all the units
with Radio1 connected to one port (link ID=RADIO1), as illustrated in the site table below:

552
 6802979C10-BA
Appendix B: Ladder Diagram Language

1. Full system synchronization:

2. Synchronization of all units with Radio1 connected to one link ID:

B.3.23
Run Process (RNP)

The RTU is based on a multitasking operating system. From all tasks that support the system, five tasks may
be used by the user processes written in ladder diagram language. These five tasks run under five different
priorities, as follows (high priority is the highest priority and TskPrD - the lowest one):
● High priority task (main process)
● TskPrA (task priority A)
● TskPrB (task priority B)
● TskPrC (task priority C)
● TskPrD (task priority D)
One of many advantages of dividing the user application into processes is the capability to run them under
different priority tasks. The MAIN process is automatically run by the system under the High priority task.
It is possible, but not always efficient, to call all the processes by the JSP operator as subroutines of the
MAIN process. Since all processes have the same priority, the Scan Time is very long (all processes have to
be executed).
Usually, some of the processes are executed more often than others. Therefore, if some of the processes run
under lower task priority, the MAIN process and the processes connected to it by the JSP operator run at a
faster speed.

553
6802979C10-BA
Appendix B: Ladder Diagram Language

In a multitasking system, the MAIN process may perform a few cycles while another process that runs under
a lower priority task performs only one cycle.
To run a process under a specific task, you should use the RUNP operator in the following manner:
When the rung is true, the process appearing above the operator, is run under the task specified below
the operator. Before running the process, you should ensure that this task is not busy. For this purpose,
the system provides four task priority flags in the Reserved Flags table (one of the System tables), named
TskPrA, TskPrB, TskPrC, and TskPrD.
When a task is busy, its corresponding flag is '1'. Therefore, one of the conditions of the rung that includes the
RUNP operator is that the relevant task flag is '0'.
It is very important not to run a task continuously because it will be impossible to run tasks that have lower
priority, including the system tasks. Thus, you should condition the RUNP operator on a timer that defines the
cycle time.

The following rungs run a process called EXEC under TskPrA. The conditions are that the task is not busy
(TskPrA=0) and the DOF Timer has completed its delay.

If the timer delay is too short, then TskPrA runs continuously and lower priority tasks are not handled.

B.3.24
Conversion of Variable Notation

Sometimes it is necessary to convert variables appearing in memory from one notation to another.

554
 6802979C10-BA
Appendix B: Ladder Diagram Language

The BCD operator refers to the value of the variable below the operator as a number in binary format and
converts it to a number in BCD format. The converted number is assigned to the variable above the operator.
The BIN operator refers to the value of the variable below the operator as a number in BCD format and
converts it to a number in binary format. The new number is assigned to the variable above the operator.
The input to be converted may be of the following data types:
● Integer Value
● Value Input
● Integer Constant
● Integer Parameter
● Index
● Mapped Value
● Timers (hour, minute, second)
The converted value may be of the following data types:
● Integer Value
● Value Output
● Integer Parameter

B.3.25
Copy Columns (CPY)

The CPY operator allows you to copy columns of any data type to any other data type. The number of bytes
to be copied is specified by the Count variable.
The Dest variable may be any variable of a single-column table or any column of a multiple column table.
This variable may be of any data type, except index.
The Src variable may be any variable of a single-column table or any column of a multiple column table. This
variable may be of any data type.
The Count variable, that specifies the number of bytes to be copied, may be any variable of a single-column
table or a specific variable of a multiple-column table. This variable may be of the following data types:
● Integer Value
● Index
● Integer Parameter
● Integer Constant

555
6802979C10-BA
Appendix B: Ladder Diagram Language

1
Copying a floating-point column to the TxBuf column in order to transmit it to another RTU. For explanation of
how to use the TxBuf, refer to Appendix E: User Defined MDLC Communication.

If Presur has x rows, then Length=4x (since a floating-point variable is four-bytes long).

2
Copying 16 bytes for a vector of values, named V, to a 128-bit vector, named B.

#16 is a constant defined in a Constants table. Its value is 16 (16 bytes*8=128 bits).

During the copy operation, the RTU checks that the number of bytes to be copied is not greater than the size
of the Dest column. If the number of bytes is greater than the size of the Dest column, the copy operation is
not performed and an appropriate message is sent to the Error Logger.

B.3.26
User Call Function (UCL)

The UCL operator together with the 'C' Toolkit allows you to program the application using 'C' blocks. Refer to
the 'C' Toolkit for ACE3600 RTUs User Guide.

B.3.27
Trigger Enable (TEN)/Disable (TDS)

The TEN operator enables a trigger (such as a pushbutton or DI) which activates the associated fast process
at the highest priority. The TDS operator disables the enabled trigger.

For more information on fast events, see the MC-IoT STS Advanced Features manual.

B.4
Ladder Diagram Reference
The following section is a quick reference of all elements, input/output, used in the Ladder Diagram
Language.

556
 6802979C10-BA
Appendix B: Ladder Diagram Language

B.4.1
Input Elements
Table 208: Input Elements

Element Meaning
⚊| |⚊ Normally Open (N.O.) Contact
⚊| / |⚊ Normally Closed (N.C.) Contact
⚊| = |⚊ Comparator Equal to
⚊| < |⚊ Comparator Less Than
⚊| ≠ |⚊ Comparator Not Equal to
⚊| > |⚊ Comparator Greater than
⚊| ↑ |⚊ Positive Differentiator (up - rising edge)
⚊| ↓ |⚊ Negative Differentiator (down - dalling edge)

B.4.2
Output Elements
Table 209: Output Elements

Element Meaning
⚊( ) Relay On Contact
⚊( / ) Relay Off Contact
⚊( L ) Relay Latch
⚊( U ) Relay Unlatch
⚊(DON) On Delay Rimer
⚊(DOF) Off Delay Timer
⚊(TRT) Retentive Timer
⚊(CTU) Count Up Counter
⚊(CTD) Count Down Counter
⚊(RST) Reset
⚊(SEND) Send Message (to RS232/RS485 User Port)
⚊( + ) Arithmetical Calculation + (plus)
⚊( - ) Arithmetical Calculation - (minus)
⚊( * ) Arithmetical Calculation x (multiply)
⚊( / ) Arithmetical Calculation / (divide)
⚊(AND) Boolean Bitwise AND
⚊(OR) Boolean Bitwise OR
⚊(XOR) Boolean Bitwise XOR
⚊(CAL) Call a function

557
6802979C10-BA
Appendix B: Ladder Diagram Language

Element Meaning
GetChr, GetDgt, Ready, NotRdy,
SndFrm, AnsFrm, RevFrm, TxFrm,
SndSeq, GetSeq, TxEvnt, Burst,
BrstSq, EvntSq, Fetch, Store, AGA3,
AGA7V, AGA7M, GtEvnt, StEvnt, SetTmr,
Time, Sync, SetCOS, P.I.D., GtExDt,
SBO, SBOoperate, SBOreset, SBOselect,
Tb2Cpy, GetSeeLog, StorBlock,
RstrBlock, RmvBlock
⚊(SCN) Scan physical and mapped I/O
⚊(MOV) Move Value or Low Byte
⚊(BCD) Convert to BDC Format
⚊(BIN) Convert to Binary Format
⚊(JMP) Jump
⚊(JSP) Jump to SubProcess
⚊(RET) Return form SubProcess
⚊(ROR) Rotate to Left
⚊(ROL) Rotate to Right
⚊(RNP) Run Process
⚊(CALC) Calculate Arithmetic Expression
⚊(CPY) Copy Memory Vectors
⚊(UCL) User C Call Function
⚊(TEN) Trigger Enable
⚊(TDS) Trigger Disable

You can also add a comment to a rung using the Comment operator.

558
 6802979C10-BA
Appendix C: Database Tables and Data Types

Appendix C

Database Tables and Data Types

This chapter describes the ACE3600 database system and constant tables, including examples, and the data
types used. The order of description is according to the system tables list. The constant tables are described
with the relevant system table.
The ACE3600 RTU database is the collection of all local variables such as inputs, outputs, calculated
values, parameters, and those variables received via the communication link. It is composed of up to 127
user-oriented tables employing user-defined symbolic names.
The Application Programmer includes a powerful, yet simple table editor, called Database Builder, which
makes database definition and modification a “snap.”
Defining the database as a set of structured tables provides the following advantages:
● The user-oriented database is easy to understand, define, and modify.
● The same tables are used during automatic creation of the central database.
● The same tables are used during symbolic run-time monitoring of the database.
● Adding/deleting devices is done by modifying the number of rows in the specific table (table’s last index).
The process is automatically adjusted to the new number of devices.
● Since tables are known to the central, communication between central and RTUs is transparent to the
RTU process. (No process has to be written for handling the communication).
● Any portion of any table can be downloaded from or uploaded to the central.
● Qualification formulas may be used as filters at the transmitting site, to reduce the amount of transmitted
data.

C.1
MOSCAD-M and IRRInet-M RTU Database
The IRRInet-M RTU database is also organized in tables. Most of the data is read-only, but there are some
values, which can be written/manipulated by the application. The user can view the contents of the database
(and the operation of the RTU) using the Monitor utility. For more information, see Monitoring an STS Table
(MOSCAD-M and IRRInet-M) in the Operation chapter of this manual.
For a more detailed description of the database and information names, types, and values, refer to the ‘C’
Toolkit for MOSCAD Family RTUs manual.

C.2
ACE1000/MC-EDGE/IRRInet-EDGE Database
The ACE1000/MC-EDGE® database is also organized in tables. The database includes a system table for
the digital inputs on the ACE1000/MC-EDGE main board, and a system table for the digital outputs on the
ACE1000/MC-EDGE main board.
The database includes:
● A user table for General-purpose bits (250 rows, 8 columns, each cell is 1 byte that reflects the value of a
single bit)
● A table for General-purpose values/user values (250 rows, 8 columns, each cell is 2 bytes)
● A table for General-purpose float values (250 rows, 4 columns, each cell is 4 bytes)

559
6802979C10-BA
Appendix C: Database Tables and Data Types

All user values, regardless of their type, are accessed discretely.

Using the STS Monitor utility, the user can view and modify the contents of the user tables, view the contents
of the I/O tables, and operate the digital outputs. For more information, see the Monitoring an STS Table
(MOSCAD-M and IRRInet-M) section of the Operation chapter of this manual.

C.3
Table Types
The ACE3600 database includes two types of tables:
● Single-column tables
● Multiple-column tables

C.3.1
Single-Column Table
Single-column tables hold global RTU variables. All variables in the table (column) are of the same data
type. Each entry in this table is assigned a unique symbolic name. The data type of the table appears in the
Columns section below the table name and table symbol.
For every row in the table, there is an associated Change of State (COS) flag. This flag is used for
communication with qualifiers. You may define a name for this flag (in the COS Name box) to be used in
the process (ladder diagram rungs). The following figure illustrates a single-column table:
Figure 287: Single-Column Table

C.3.2
Multiple-Column Table
Multiple-column tables hold symbolic structured data. Each table represents a group of 1 to 250 similar
devices (for example, pumps, reservoirs, transformers, etc.).
A row (record) in the table represents a single device, and a column a value, which is common to all devices.
Each column has a unique symbolic name.
All variables in a specific column share the same data type.
Each variable in the table has a unique logical name: <column name>, <row (device) index>.
The following figure illustrates a multiple-column table:

560
 6802979C10-BA
Appendix C: Database Tables and Data Types

Figure 288: Multiple-Column Table

The above table contains 5 rows (for 5 pumps) and one of the columns is called “Flow”. Here, “Flow,0”
defines the flow of the first pump, and “Flow,4” – the flow of the fifth pump. In other words, “Flow,x” defines
the flow of pump x, where x is the pump index. In each column, the column data type appears below the
column name.
For every row in the table, there is an associated COS flag. This flag is used for communication with
qualifiers. You may define a name for this flag (in the COS Name field) to be used in the process (ladder
diagram rungs).
The Last Index (last device) is given a free name by the user (LstPmp in the above example; it is seen when
the table is scrolled). This name is used in the process to indicate the last device in the table. The process is
automatically adjusted to the actual number of devices (rows) when it is changed by the user.

C.3.3
Duplicated Columns
The system enables you to define columns that are windows to other columns in different tables. These are
called duplicated columns. This feature is designed to build a table that serves as a report to the central. This
table may include various columns that have been defined in different tables.
This feature may also be helpful during debugging. You may define a table of duplicated columns (windows)
to view simultaneously specific values, located in different tables.
When using the duplicate column operation, the original column is not duplicated in the database; the
duplicated column only holds a “pointer” to the original column.

C.3.4
Single- and Multiple-Column Tables Comparison
In a single-column table, each variable is specified by a name. In a multiple-column table, each column is
specified by a name and each variable in the table is defined by the column name and an index, as follows:
<Column Name>,Index.
A single-column table holds single variables, while a multiple-column table is designed to hold N devices
(rows) that have the same structure.
A multiple-column table allows you to write an algorithm for a single row (device) and to apply it to all the
rows (devices) using an index. In a single-column table, it is not possible and not necessary to use an index.

561
6802979C10-BA
Appendix C: Database Tables and Data Types

C.4
Table Groups
The tables in the system are arranged in three groups:
● User tables
● System tables
● Constants tables

C.5
User Tables
User tables are defined according to application requirements. Up to 127 user tables may be defined.
The first table in this group is already defined as a single-column table called Qualifiers. The variables in this
table may be named by the user. The Qualifiers table can be used:
● To set special qualifiers (fields and/or subgroups of variables) that affect the process in another site
● In RTU-to-RTU communication
● To set qualifiers that will identify and respond to a broadcast sent by the central (refer to the User Defined
MDLC Communication on page 612).
A special PID user table can be added for the PID LOOP - Proportional Integral Derivative feature. For more
information, see the MC-IoT STS Advanced Features manual.
A special user table can be added for the Database Backup feature. For more information, see the MC-IoT
STS Advanced Features manual and the Backing up the Database section of the Application Programmer
chapter.

C.6
System Tables
The system tables are predefined tables, designed to hold communications buffers, index pointers, time and
date variables, and other system-related variables. While the user tables and some constant tables may be
modified by the user to meet specific needs, the system tables may not be modified. The following figure
shows the system tables.

562
 6802979C10-BA
Appendix C: Database Tables and Data Types

Figure 289: System Tables

The system tables include reserved variables that may be used as symbolic names during process
programming.

C.7
Constant Tables
The user may use symbolic constants (instead of their numeric value) during process (ladder) editing. For
example, if a limit for a process is 100, a symbolic name such as LIMIT 1 is used in the process instead of
the value.
The symbolic constants provide the following:
● Simplified modification, as the constant is modified in only one place.
● More understandable ladder and ease of maintenance.
Some of the constants tables are predefined, including constants such as, ASCII characters, port names,
modes, and protocols, etc. These tables are described later in this chapter.
Two tables in this group (Event Definitions 1 and 2) are provided for event definitions (up to 500 events) via
symbolic names. The event names should be defined in these tables. These events become automatically
known to the control center during the creation of the central database.
Symbolic constants that appear in the tables but are not used in the process (Ladder Diagram) do not
consume any memory space.
The following figure illustrates the constants tables.

563
6802979C10-BA
Appendix C: Database Tables and Data Types

Figure 290: Constant Tables

C.8
Tables Descriptions
The following is a description of the pre-defined tables.

C.8.1
RTU-to-RTU Controls/RTU-to-RTU Comm Buff and RTU-
RTU Frame Types
The RTU-to-RTU Comm Buff and RTU-to-RTU Controls system tables enable the user to define buffers
for RTU-to-RTU communication (the communication protocol is defined by the user). The RTU-RTU Frame
Types constants table includes the various types of frame transmission in RTU-to-RTU communication.
For further details about RTU-to-RTU configuration, see the MDLC Communication Protocol on page 631.

C.8.2
Time & Date Table
The Time & Date system table, displayed below, includes variables that enable the user to write programs
with time-dependent processes.
To facilitate the use of the Time & Date table, the system provides constant tables to be used in the ladder
application.

564
 6802979C10-BA
Appendix C: Database Tables and Data Types

Figure 291: Time & Date Table

There is an appropriate constants table for each variable in the Time & Date table (except for the Seconds
variable). The user may define constants to be used with the Seconds variable.
These constants should be in the range of 00 to 59.
Year variable: the Years table includes symbolic names for the years (starting from 1991). The user may add
constants to this table and also modify the names of the existing constants.

565
6802979C10-BA
Appendix C: Database Tables and Data Types

Figure 292: Years Table

Month variable: the Months variable includes the names of the months of the year. This table is protected and
is not editable.
Figure 293: Months Table

566
 6802979C10-BA
Appendix C: Database Tables and Data Types

Date variable: the Dates table includes all possible dates - from the first of the month up to the 31st. This
table is also protected and is not editable.
Figure 294: Dates Table

Day variable: the Days table includes the days of the week. This table is also protected and is not editable.
Figure 295: Days Table

567
6802979C10-BA
Appendix C: Database Tables and Data Types

Time variable: the Time constants table allows you to define constants with values in the 24-hour format
Hr:Mn (Hr varies between 0 and 23, and Mn varies between 0 and 59).
Example:
1. The following rung activates the DyStrt process at a specific hour, defined as SrtTim.

NOTE: The differentiator causes a single access to the DyStrt process at the beginning of the
minute defined by the StrTim variable.
2. The following rung performs the same operation 5 days a week (Saturday and Sunday are not included).

3. The following rung performs the MnStrt process once, on the first of the month. In the same way, it is
possible to make process performance conditional on a month and/or year.

C.8.3
Index Table
This system table (which may be edited) allows the user to define the necessary indices for writing programs.
It is recommended to define indices with one-character symbolic names (such as I, J, K) for creating symbolic
names for variables. An example of a variable name field with index in the Ladder Diagram is SYMBOL,x
One of the advantages of building the database in multiple column tables (in which each row represents a
controlled device) is that it provides the possibility to define one algorithm for one device and to run this
algorithm by an “index” on all the devices. The index is actually a variable pointer to the table rows. For this
purpose, the system provides an index data type. To define indices, use the Index table (one of the system
tables). Each variable defined in this table is an index.
Example:
1. Refer to a system that consists of 50 fans, represented in the following table:

568
 6802979C10-BA
Appendix C: Database Tables and Data Types

Figure 296: Fans Table

The various variables are described below:

● ENABLE – a bit variable that specifies whether the air conditioner in a specific section should be
activated or not.
● TEMP – a value input variable that is the temperature reading from a specific section.
● HiLmt – a parameter that defines the temperature upper limit for a specific section.
● FAN – a digital output variable used to activate the fan.
The LstFan variable (defined by the user) indicates the number of the last fan, in this case 49. The
following rungs activate all 50 fans; I is the index, defined in the Index table.

569
6802979C10-BA
Appendix C: Database Tables and Data Types

Before performing the algorithm, the 50 temperatures (complete column) are read by the SCAN operator.
The I index is then reset to point the first row in the table. When I=0, all values of the indexed variables
refer to the first section. Therefore, the algorithm starts with the first row (that is, the first section).
The algorithm is written as a loop (rungs 3 to 6), starting at the FnLoop rung and ending at the rung with
the JMP operator. The algorithm logic is as follows:
● If the section is ENABLED and the actual temperature is higher than HiLmt, the fan is activated by
the LATCH operator (rung 3).
● If the section is not ENABLED or the actual temperature is lower than LowLmt, the fan operation is
stopped (rung 4).
● The I index is advanced by the CTU (count up) operator to perform the algorithm on the next section
(rung5).
● The I index is compared to the LstFan variable (rung 6). If it is found smaller or equal to the LstFan
variable, it means that the loop is to be performed again (for the next section). If the I index is higher
than the LstFan variable, the program exits the loop and proceeds to the next rung(7).
The last rung (7) scans the FAN variable to update physical outputs according to the FAN column in the
table.
By using an index, the algorithm is written only once and not n times.

570
 6802979C10-BA
Appendix C: Database Tables and Data Types

The loop size is defined by the LstFan variable, and not 49 (the last section in our example). That is, by a
single operation (see the Application Programmer on page 324) you can reduce or enlarge the size of the
table – the algorithm is automatically adjusted to the number of sections.
You can refer to a specific row by assigning a number rather than the index. For example, TEMP,3
indicates the temperature of section number 3 (the fourth row, starting from 0).
2. When the algorithm for an external device (for each row in the table) is long and complicated (considering
CPU time), you may want to divide the control operation so that only one row of the table is handled in
a process SCAN. This case is different from the previous example, where the algorithm for all rows is
handled in one SCAN. In this case, the rungs are as follows:

The first rung check that the I index is in the correct range. If I>LstFan, it is reset to 0. Only when I=0, all
temperatures are read by the SCAN operator.
The logic of activating and deactivating the fans is similar to the previous example and so are the rungs (3
and 4). The I index is incremented by the CTU operator to be ready for the next row in the next SCAN.
When I>LstFan the FAN column is scanned to send the values to the physical outputs.
NOTE: The SCAN operator is performed on the TEMP and FAN variables once every 50 cycles (in
this case) and not in every cycle.
In example 1 on page 568, the I index of the loop may be used in the same process for another loop, since
the index is used only within the loop.
In example 2 on page 571, you should not use the I index again, since it is incremented in between cycles
and keeps the pointer for the next cycle. Therefore, it cannot be used in another loop.
It is recommended to define indices of one character to enable assigning meaningful names to variables in
the Ladder Diagram, the format is <name>,<index>.
Indices are defined only in the Index table. You may perform arithmetic operations on indices beside the RST,
CTU, and CTD operators. Refer to the description of the relevant operator.

571
6802979C10-BA
Appendix C: Database Tables and Data Types

C.8.4
Reserved Flags Table
This system table, shown below, includes variable flags (such as I/O Fail, Power-up), handled by fixed
functions in the system. These flags are used for exchanging information between the control program written
by the user and the RTU system software, or used by the appropriate rungs when requested through the
appropriate functions.
Figure 297: Reserved Flags Table

I/O_Fl: This variable is set by the system; ‘1’ indicates that one of the I/O modules is faulty. This variable may
be used to activate a local relay output, named BELL, that is reset by a local push-button, named ACK.

The differentiator causes the Latch operation to be performed only at I/O_Fl appearance. The I/O_Fl variable
may also be used for sending events to the central. Refer to RTU Event/Burst Reporting on page 621.
Init: Initialization. This variable is set by the system to ‘1’ when a new application is downloaded to the RTU
during “reset-load” (all variables are preset), or when a “cold-restart” is performed. If this variable is used, it
should be reset at the end of the process. For example, the PreSet process is run at initialization. At the end
of the process, the Init variable is reset to ‘0’.

572
 6802979C10-BA
Appendix C: Database Tables and Data Types

PwrUp: A variable set by the system to ‘1’ upon power-up or power restore (not as the Init variable that is
set to ‘1’ only at cold startup). If the PwrUp variable is used, it should be reset after performing all power-up
operations. The PwrUp variable may be used as a condition to perform various operations at power-up as in
the following example.

When the PwrUp variable is not true (no power-up), the rungs that perform the power-up operations are
skipped.
NOTE: During “cold-restart” the Init and the PwrUp flags are set to ‘1’. It is the user’s responsibility to
reset these flags.
MainFail: This flag is set by the system to ‘1’ when a power failure causes the RTU main frame to switch to a
backup battery. It is reset when power is restored. (This parameter was named AC_Fal in older versions.)
NOTE: This flag is relevant only if the unit is equipped with a backup battery.

For example, if the AC power failure is longer than 10 minutes, a local buzzer sounds and an event is sent
to the central. The FalDly delay-on timer is defined as a Minutes Timer and its value is set to 10:00 (10
minutes).

BatFal: This flag is set by the system to ‘1’ when the voltage of the RTC lithium battery is low.
PushB1, PushB2: These two variables allow you to access the status of the PB1 and PB2 push-buttons via
the ladder diagram. When a push button is pressed, the appropriate variable is set to ‘1’. The variables may
be reset by the rungs (latch operation).
AuthOK: This variable is set to '1' when the second and third Authentication keys (used in the synchronization
of an RTU) are valid. The first key (used in authenticating incoming frame data) may not be valid.
Synchronization messages from a server to a client are processed. Incoming data frames are accepted
by the RTU if the timestamp is valid and are rejected if it is not.
The AuthOK variable is set to '0' when the second and third Authentication keys are not valid, but the first
key may be valid. In this case, synchronization messages from a server to the client are no longer processed.
Incoming data frames are accepted by the RTU if the timestamp is valid and are rejected if it is not. As soon
as the receiving RTU's clock becomes unsynchronized, no incoming data frames are accepted by the RTU.
The user must then redefine the second and third authentication keys and download them to the RTU using
the Network Configuration utility.
TskPrA - TskPrD (Task Priority): These four system flags indicate to the ladder whether the A to D tasks are
running or not. Refer to the Output Elements on page 557.

573
6802979C10-BA
Appendix C: Database Tables and Data Types

ClockValid: This variable indicates if the clock source is communicating with the MOSCAD, or if it is
disconnected. It is set by the system to ‘1’ when the communication is valid, and to ‘0’ when it is null. (This
parameter was named GPSVal in older versions.) Refer to the MC- IoT STS Advanced Features manual for
more on clocks.
PrmFlg: For Dual CPU Mode, ‘1’ indicates that the CPU is plugged in Slot-0 (Primary).
PrmFal: For Dual CPU Mode. The Secondary’s application may use this flag to check if a failure has occurred
in the Primary CPU module. ‘1’ indicates that there is a failure in the Primary.
DisCom: When active (1), the CPU does not respond to messages that were sent to its main address, and in
addition, does not send any message (burst, SndFrm etc.). The CPU responds only to messages that were
sent to its secondary address or messages that were sent in LOCAL Mode.
ErrLog: This flag is set by the system to ‘1’ when there is at least one error in the error log file. It is reset
when the file is empty. The ErrLog variable may be used to inform the control center that there is an error
(ErrLog=1) – as in the following rung.

When ErrLog=1, the program jumps to the INFOER (inform error) process. This process performs the task of
sending events to the control center. In this case, the event is an error event. An example of such a process
is given in Appendix E: User Defined MDLC Communication - RTU Event Reporting.
TimTag: This flag is set by the system to ‘1’ when there is at least one message in the Time Tag log file. It
is reset when the file is empty. The TimTag variable may be used to inform the control center that there is a
message (TimTag=1) in the Time Tag log file – as in the following rung.

When TimTag=1, the program jumps to the INFTAG (inform time tag) process. This process performs the
task of sending events to the control center. In this case, the event is a message in the Time Tag log file. An
example of such a process is given in RTU Event/Burst Reporting on page 621.
DefC_Y: This flag is set by the system to ‘1’ only when the RTU “knows” its default central. At the first
transmission of the central (after system setup), each RTU holds the routing to the default central. If such a
transmission has not occurred (DefC_Y=0), then an RTU transmission to the default central results in an error
– the ERR LED of the RTU lights. For example, refer to a process that performs burst communication towards
the default central. This process includes the following rungs:

To prevent an RTU transmission to the default central without “knowing” the default central (such a
transmission results in an error), the transmission rung should be conditioned by the DefC_Y flag, as follows:

574
 6802979C10-BA
Appendix C: Database Tables and Data Types

The TxEvnt function is called only when DefC_Y=1, that is RTU “knows” its default central.
CntCom: This variable indicates whether there is any communication (interrogation, command, broadcast,
event acknowledge) to the central or not. This variable is set to ‘1’ whenever the central has succeeded
in communicating with the unit. For example, it is possible to activate a DOF timer (with a T preset time)
according to the CntCom variable in order to change the RTU mode of operation in case of central failure
(CntCom=0), as follows:

The MODE2 user bit may be used to activate the RTU in an independent mode of operation. If MODE2=0,
there is communication with the central. If MODE2=1, there is no communication with the central.
EvOvfl: This flag is set by the system. ‘1’ indicates that the event queue is full and the next event is written
over the existing events. It is the user’s responsibility to reset this flag.
Warn: When there is at least one warning in the Error Logger.
Messg: When there is at least one message in the Error Logger.
ErAlmostFul: When the Error Logger file in the flash memory is almost full.
ErFull: When the Error Logger file in the flash memory is full.
SBOoprChk: Indication of SBO operation mode (Operate or not.) Relates to the Select Before Operate
(SBO).
ActivePS: Relates to Dual Power Supply. For redundant sites. ‘0’ indicates that this is the backup power
supply or that redundancy not supported; ‘1’ indicates that this is the active power supply.
PS1_MainFail: When a failure has occurred in the external input (not battery) to Power Supply 1 on the main
frame.
PS2_MainFail: When a failure has occurred in the external input (not battery) to Power Supply 2 on the main
frame. Relates to Dual Power Supply.
PS1_12VDoFail: When a failure has occurred in the 12V DO control of Power Supply 1 on the main frame.
PS2_12VDoFail: When a failure has occurred in the 12V DO control of Power Supply 2 on the main frame.
Relates to Dual Power Supply.
expCommFail: When a communication error has occurred between the main frame and any one of the
expansion frames. To check out the specific expansion frame, use the Expansions Reserved Flags Table.
expSyncFail: When a synchronization error has occurred between the main frame and any one of the
expansion frames. To check out the specific expansion frame, use the Expansions Reserved Flags Table.
SecureLogEvents: For secured systems only. This flag is set by the system to ‘1’ when there is at least one
event in the security log file. It is reset when the file is empty.

575
6802979C10-BA
Appendix C: Database Tables and Data Types

The SecureLogEvents variable may be used to inform the control center that there is a security event
(SecureLogEvents =1). See theMC-IoT Advanced System Security User Guide.
SecureLogSeverity: For secured systems only. This flag is set by the system to ‘1’ when there is at least one
event in the security log file whose severity is greater than, or equal to the predefined ‘High severity threshold
level’ in the policy. It is reset only when the security log is erased. This variable may be used to inform the
control center that the high severity event has occurred (SecureLogSeverity = 1). Note: If the security log is
full, older events are overwritten. Therefore it is possible that the SecureLogSeverity flag is set to 1, but the
high severity event itself is no longer there. See the MC-IoT Advanced System Security User Guide manual.
SecureLogAlmostFull: For secured systems only. This flag is set by the system to ‘1’ when the security log
file is 80% full. It is reset when the number of events in the file falls below this threshold. This variable may
be used to inform the control center that the security log file is almost full (SecureLogAlmostFull = 1). See the
MC-IoT Advanced System Security User Guide manual.
SecureLogFull: For secured systems only. This flag is set by the system to ‘1’ when the security log file is
100% full. It is reset when the number of events in the file falls below this threshold. This variable may be
used to inform the control center that the security log file is full (SecureLogFull = 1) and outdated messages
are being discarded. See the MC-IoT Advanced System Security User Guide manual.
NOTE: These flags do not appear in the Reserved Flags table in a nonsecured system.

CpuActive: For redundant sites. ‘0’ indicates that the CPU is the standby peer or that redundancy not
supported; ‘1’ indicates the CPU is active.

C.8.5
Performance Monitor Table
The Performance Monitor values are handled by fixed functions in the system. They may be displayed during
on-line monitoring.

C.8.6
User Ports Table
The User Ports system table is a buffer that is used in communication for ports defined as User Ports (ladder
controlled) in the Site Configuration program. The associated constants tables are: User Port Names, User
Port Modes, User Port Protocols, and User Port Baud Rates. For a detailed explanation and examples, refer
to the User Defined Local Ports on page 597.

C.8.7
Site Table
The Site table is applicable only for RTU-to-RTU communication, event reporting, data burst, and sync.
This system table is used to define all the RTUs that the present RTU wishes to communicate with. For
each destination RTU, the user should define a symbolic name, logic address (Site ID), and the link (link
ID) through which it is connected. When programming the process using the ladder rungs, the user should
employ only the symbolic site name in the appropriate rung for sending the data to that site. For further
details including examples, refer to the User Defined MDLC Communication on page 612.

C.8.8
Tx Event Table
The Tx Event system table is used as a buffer when sending events to the central.The events should be
defined in the constants Event Definitions 1 & 2 tables. The MDLC Port ID’s table includes one or more port

576
 6802979C10-BA
Appendix C: Database Tables and Data Types

names, which connect the central computer to the FIU. For further details, see Appendix E: User Defined
MDLC Communication on page 612.

C.8.9
Data Burst Table
The Data Burst system table is used by the RTU to transmit data to the central. The data to be transmitted
may be either a complete row of a multicolumn table or a single-column table. For further details, refer to the
User Defined MDLC Communication on page 612.

C.8.10
Reserved Values Table
This system table includes system values that may be used in the process programming for various
purposes.
Figure 298: Reserved Values Table

SelfID: This variable provides the Site ID of the unit. For example, this variable may be used when you do not
want to create many applications with minor changes. You can use the SelfID variable to modify one common
application according to the needs of a specific RTU.
PLCStt: This variable provides an indication on the communication with third-party PLCs. The values for this
variable defined in the PLC Statuses table (one of the Constant Tables). For further details about Third-Party
Protocols, see the MC-IoT STS Third Party Protocols Support manual.
ClcStt: This variable is updated following a Calc operation. When an overflow occurs, CllStt is set to ‘1’ and it
is the user’s responsibility to reset it.
UclStt: This variable is used by the ‘C’ Toolkit and it is updated following a Ucl output operation. It is the
user’s responsibility to reset this variable.
GpsOfs: This variable enables the user to update the RTU to daylight savings time. The GpsOfs default value
is ‘0’, and it may be either positive or negative according to the local time offset in respect to the universal

577
6802979C10-BA
Appendix C: Database Tables and Data Types

time (measured in hours). For further details about the GPS, refer to the MC-IoT STS Advanced Features
manual.
BAT1V: This variable indicates the charging level (in percentages) of the battery attached to Power Supply 1.
BAT2V: This variable indicates the charging level (in percentages) of the battery attached to Power Supply 2.
This data is valid only if a dual power supply exists. This feature is not currently available.

Table 210: The BAT1V and BAT2V Charging Levels Values

Charging Level Value Description

0-100 The charging level (in percentages) of the battery.
254 Battery does not exist.
255 Battery was charging when interrogated, so the
charging level could not be reported. As the power
supply is monitored periodically, this value is tem-
porary by nature. Alternatively, the user can initiate
an update of the power supply values by reading
the power supply data in the Hardware Test.

SBOduration: This output value enables the user to set the duration of the SBO DO relay activation (i.e. the
pulse width of the SBO operation.) Set the value to -1 for infinite duration. Note: The duration is in units of 1
msec, although system time resolution is 10msec.
SBOstatus: This input value enables the user to track the status of the SBO process and to know whether
another SBO operation can be generated.

Table 211: The SBOstatus Values

Value Description
0 Idle.
1 SBO was selected.
2 SBO was checked.
3 SBO was operated.

SBOerror: This input value indicates the type of error, which occurred in the SBO process.

Table 212: The SBOerror Values

Value Description
0 No error
1 Fail to select – Probably because select was done
during operate.
2 Fail to check – System failed to check, probably
due to a hardware problem.
3 Fail to operate – Select timeout was reached be-
fore the user operated the SBO.
4 Invalid operation – Operate during operate or Op-
eration with 0 duration.

578
 6802979C10-BA
Appendix C: Database Tables and Data Types

For further details on using SBO DOs, refer to the Select Before Operate Dos section of the MC-IoT STS
Advanced Features manual.
Tb2CpyResult: The return code of the Tb2Cpy function CALL in a redundant site. This call checks the result
of the Tb2Cpy operation, which copies a predefined list of tables from the Active CPU’s database to the peer
CPU. When the tables are copied successfully, Tb2CpyResult is set to ‘0’. Otherwise it is set to the relevant
nonzero error code. For more information, see the RTU Redundancy section of the MC-IoT STS Advanced
Features manual.
NOTE: When using Tb2Cpy, the user should check that the initial copy to memory succeeded and then
that the copy from memory to the peer CPU was completed successfully.
Sec_EventID: For secured systems only. The ID of the retrieved security log event. If ‘0’, then no high severity
events exist in the log. See the MC-IoT Advanced System Security User Guide manual.
Sec_RoleID: For secured systems only. The user’s role ID in the retrieved security log event. See the MC-IoT
Advanced System Security User Guide manual.
Sec_UserID: For secured systems only. The user’s ID in the retrieved security log event. See the MC-IoT
Advanced System Security User Guide manual.
Sec_Severity: For secured systems only. The severity of the retrieved security log event. Can be one of 1 =
information, 3 = moderate, 5 = high, or 7 = critical. See the MC-IoT Advanced System Security User Guide
manual.
Sec_TimeEventHigh: For secured systems only. The high byte of the date and time of the security log event
(day, year). See the MC-IoT Advanced System Security User Guide manual.
Sec_TimeEventLow: For secured systems only. The low byte of the date and time of the security log event
(milliseconds from the Sec_TimeEventHigh day). See the MC-IoT Advanced System Security User Guide
manual.
MdlcKeyIndex: For secured systems only. The active MDLC encryption key index in the list of keys.
Note: At startup, this is set to 0 (= no active key and no encryption) until it gets its actual value. Ignore this
value when it is set to 0. See the MC-IoT Advanced System Security User Guide manual.
MdlcKeyAlert: For secured systems only. The number of minutes remaining until MDLC payload encryption
keys are swapped. If the value is < 32767, it reflects the actual number of minutes until the key swap. If
the value is = 32767 minutes (22.75 days,) the key swap will take place in at least 32767 minutes (could be
more.)
Note: At startup, this is set to 0 until it gets its actual value. Ignore this value when it is set to 0. See the
MC-IoT Advanced System Security User Guide manual.
Sec_Param1High: For secured systems only. The high byte of the first parameter of the security log event
text message. See the MC-IoT Advanced System Security User Guide manual.
Sec_Param1Low: For secured systems only. The low byte of the first parameter of the security log event text
message. See the MC-IoT Advanced System Security User Guide manual.
Sec_Param2High: For secured systems only. The high byte of the second parameter of the security log event
text message. See the MC-IoT Advanced System Security User Guide manual.
Sec_Param2Low: For secured systems only. The low byte of the second parameter of the text messages
sent to the security log. See the MC-IoT Advanced System Security User Guide manual.
Sec_Param3High: For secured systems only. The high byte of the third parameter of the security log event
text message. See the MC-IoT Advanced System Security User Guide manual.
Sec_Param3Low: For secured systems only. The low byte of the third parameter of the security log event text
message. See the MC-IoT Advanced System Security User Guide manual.
DBbackTblNo: The table number of the BlocksToBackup database table. For more information, see the
Database Backup section of the MC-IoT STS Advanced Features manual.

579
6802979C10-BA
Appendix C: Database Tables and Data Types

C.8.11
PRMEVENT Table
The PRMEVENT system table enables the user to define buffers for the Event Driven software. Unlike
polling/scanning, the Event Driven software performs calculations or sends commands only when changes
occur at the inputs.
For further details about the Event Driven software, refer to Event Driven Software in MC-IoT STS Advanced
Features manual.

C.8.12
PLC Table
The PLC system table is used to define the connectivity to third-party controllers in the system.
For further details about Third-Party Protocols, refer to the ACE3600 STS Third Party Protocols Support
manual.

C.8.13
PLC Dynamic IOLINK Table
The PLC Dynamic IOLINK system table is used to define the connectivity to third-party controllers in the
system at runtime. This corresponds to the static I/O linking, which is done before compilation in the
Application Programmer for a PLC data type column in an application database table.
For further details about Third-Party Protocols, refer to the ACE3600 STS Third Party Protocols Support
manual.

C.8.14
CPU Power Supply Table
The CPU Power Supply system table represents the state of the 12V power supplies of the CPU plug-in
ports. The table can be used to read the state and change the output state. The first row in the table
represents the power supply for PI1 and the second row in the table represents the power supply for PI2.
CpuIn: This variable is used to read the status of the 12V power supply.
CpuOut: This variable is used to control the 12V power supply.
The status of these power supplies can also be checked using the Hardware Test CPU test. See CPU Test
above.
For further details about the CPU module, refer to the ACE3600 RTU Owner’s Manual.

C.8.15
Main Power Supply1 Table
The Main Power Supply1 system table represents the state of the auxiliary outputs AUX1A, AUX1B, AUX2A,
and AUX2B and the AUX2 DC voltage value on the first Main power supply and on the current expansion
power supply. The table can be used to change the output states, except for the voltage. The AUX2 DC
voltage can only be changed using the STS site configuration.
MPS1In: This variable is used to scan in the values of the auxiliary outputs AUX1A (row 0), AUX1B (row 1),
AUX2A (row 2), and AUX2B (row 3) and the AUX2 DC voltage value (row on the first Main power supply.
MPS1Out: This variable is used to scan out the values of the auxiliary outputs AUX1A (row 0), AUX1B (row
1), AUX2A (row 2), and AUX2B (row 3) on the first Main power supply.

580
 6802979C10-BA
Appendix C: Database Tables and Data Types

ePS1In: This variable is used to scan in the values of the auxiliary outputs AUX1A (row 0), AUX1B (row 1),
AUX2A (row 2), and AUX2B (row 3) and the AUX2 DC voltage value (row 4) on the current expansion power
supply. The initial values of the auxiliary outputs and DC voltage are derived from the site configuration.
The outputs can then be modified by the user in the ladder/ ‘C’ application. Before using this flag, see the
important note under Expansions Reserved Values Table below.
NOTE: This variable is only relevant if the power supply on the expansion frame is a model which
includes auxiliary outputs. When the expansion power supply is used, this value is always 0 (not
relevant).
ePS1Out: This variable is used to scan out the values of the auxiliary outputs AUX1A (row 0), AUX1B (row
1), AUX2A (row 2), and AUX2B (row 3) on the current expansion power supply. The initial values of the
auxiliary outputs and DC voltage are derived from the site configuration. The outputs can then be modified
by the user in the ladder/ ‘C’ application. Before using this flag, see the important note under Expansions
Reserved Values Table below. Note: This variable is only relevant if the power supply on the expansion frame
is a model which includes auxiliary outputs. When the expansion power supply is used, this value is always 0
(not relevant).
For further details about the auxiliary outputs on the power supply modules, refer to the ACE3600 RTU
Owner’s Manual. For further details on the MOSCAD_GetExpData ‘C’ Toolkit function, see the C Toolkit for
the MOSCAD Family RTUs manual.

C.8.16
Main Power Supply2 Table
The Main Power Supply2 system table represents the state of the auxiliary outputs AUX1A, AUX1B, AUX2A,
and AUX2B and the AUX2 DC voltage value on the second Main power supply. The table can be used to
change the output states, except for the voltage. The AUX2 DC voltage can only be changed using the STS
site configuration. This table is not currently in use.
For further details about the auxiliary outputs on the power supply modules, refer to the ACE3600 RTU
Owner’s Manual.

C.8.17
Daylight Saving Dates Table
The Daylight Saving Dates table is used to define the start and end dates for daylight savings time.

Table 213: Daylight Saving Dates Table

Variable Description
MonthStart: This variable represents the month during which
daylight savings begin.
DayStart: This variable represents the day during which day-
light savings begin.
HourStart: This variable represents the hour during which
daylight savings begin.
MonthEnd: This variable represents the month during which
daylight savings end.
DayEnd: This variable represents the day during which day-
light savings end.
HourEnd: This variable represents the hour during which
daylight savings end.

581
6802979C10-BA
Appendix C: Database Tables and Data Types

C.8.18
PLC IP Access Control Table
The PLC IP Access Control system table is used to define the connectivity over IP to third-party controllers in
the system.
For further details about Third-Party Protocols, refer to the MC-IoT STS Third Party Protocols Support
manual.

C.8.19
Expansions Reserved Flags Table
The Expansions Reserved Flags system table includes variable flags (such as I/O Fail, Power- up), handled
by fixed functions in the system. These flags are used for exchanging information between the control
program (written by the user), and the RTU system software. Also, they can be used by the appropriate rungs
when requested through the appropriate functions.

IMPORTANT: Before using any flags in this table, see the important note under Expansions Reserved Values
Table below.
Figure 299: Expansion Reserved Flags Table

eMainFail: This flag is set by the system to ‘1’ when a power failure causes the RTU expansion frame to
switch to a backup battery. It is reset when power is restored. See MainFail above.
NOTE: This variable is only relevant if the power supply on the expansion frame is equipped with a
backup battery. When the expansion power supply is used (no backup battery), this value is always 0
(not relevant).

582
 6802979C10-BA
Appendix C: Database Tables and Data Types

eActivePS: Whether this expansion power supply is the active one in a redundant site. This variable relates to
Dual Power Supply.
ePS1_MainFail: This variable is used to indicate a failure in Power Supply 1 on the current expansion frame.
ePS2_MainFail: This variable is used to indicate a failure in Power Supply 2 on the current expansion frame.
Relates to Dual Power Supply.
ePS1_12VDoFail: This variable is used to indicate a failure in the 12V DO control of Power Supply 1 on the
current expansion frame.
ePS2_12VDoFail: This variable is used to indicate a failure in the 12V DO control of Power Supply 2 on the
current expansion frame. Relates to Dual Power
Supply.
eCommFail: This variable is used to indicate that a communication error has occurred between the main
frame and the current expansion frame. See expCommFail above.
eSyncFail: This variable is used to indicate that a synchronization error has occurred between the main frame
and the current expansion frames. See expSyncFail above.

C.8.20
Expansions Reserved Values Table
The Expansions Reserved Values system table includes expansion-related system values that may be used
in the process programming.
CurrExpNum: This variable is used to identify the current expansion frame number. This variable is not
writable in the table. Its value is set when the expansion data is retrieved.
The ACE3600 RTU can include up to 13 expansion frames, each of which has its own expansion module,
power supply, and I/Os. Before using any columns in the Expansions Reserved Flags or Expansions
Reserved Values system tables, or the ePS1In/ePS1Out columns of the Main Power Supply<n> tables, the
user application must first call the GtExDt ladder call or the MOSCAD_GetExpData ‘C’ Toolkit function to set
the desired expansion frame to be the current frame. After that call, the relevant flags/values are retrieved
and displayed in these specific database tables.
In the example below, the user application is setting a specified expansion frame as the current expansion
frame.

eBAT1V: This variable indicates the charging level (in percentages) of the battery attached to Power Supply 1
on the current expansion frame.
eBAT2V: This variable indicates the charging level (in percentages) of the battery attached to Power Supply 2
on the current expansion frame. This data is valid only if a dual power supply exists.
NOTE: eBAT1V and eBAT2V variables are only relevant if the power supply on the expansion frame is
equipped with a backup battery. When the expansion power supply is used (no backup battery), this
value is always 0 (not relevant).

583
6802979C10-BA
Appendix C: Database Tables and Data Types

C.8.21
ASCII Table
The ASCII constant table contains ASCII representation for the basic character set (alphanumeric and special
characters.) These character values can then be compared to constant variables in the ladder.

C.8.22
User Port Names Table
The User Port Names constant table defines the names for up to four user ports.

C.8.23
User Port Modes Table
The User Port Modes constant table defines the possible modes (7/8 bit, odd/even parity, 1/2 stop bit) for the
user port.
For detailed explanation, see the User Defined Local Ports on page 597.

C.8.24
User Port Protocols Table
The User Port Protocols constant table defines the possible protocols (Binary, XonXoff) for the user port.
For a detailed explanation and examples, refer to the User Defined Local Ports on page 597.

C.8.25
User Port Baud Rates Table
The User Port Baud Rates constant table defines the possible data speed (300, 600, 1200, 2400, 4800,
9600, 19200, 38400, 57600) for the user port.
For a detailed explanation and examples, refer to the User Defined Local Ports on page 597.

584
 6802979C10-BA
Appendix C: Database Tables and Data Types

C.8.26
Event Definitions 1 Table
The Event Definitions 1 constant table enables the user to define up to 250 events via symbolic names.
These events become automatically known to the control center during the creation of the central database
and can be used in the ladder and in event reporting.

C.8.27
Event Definitions 2 Table
The Event Definitions 2 constant table enables the user to define up to 250 events via symbolic names.
These events become automatically known to the control center during the creation of the central database
and can be used in the ladder and in event reporting.

C.8.28
MDLC Port ID’s Table
The MDLC Port ID’s constant table includes one or more port names which connect the central computer to
the FIU.For further details, see the User Defined MDLC Communication on page 612 and see the Tx Event
Table on page 576.

C.8.29
RTU-to-RTU Frame Types Table
The RTU-RTU Frame Types constants table includes the various types of frame transmission in RTU-to-RTU
communication. It is used with the RTU-to-RTU Comm Buff system table.
For further details, see the User Defined MDLC Communication on page 612 and RTU-to-RTU Controls/
RTU-to-RTU Comm Buff and RTU-RTU Frame Types on page 564.

C.8.30
Years Table
The Years constant table contains year names (for example, "Yr2000") which can be compared to constant
variables in the ladder.

C.8.31
Months Table
The Months constant table contains month names (for example, "Jan") which can be compared to constant
variables in the ladder.

C.8.32
Days Table
The Days constant table contains day names (for example, "Thu") which can be compared to constant
variables in the ladder.

585
6802979C10-BA
Appendix C: Database Tables and Data Types

C.8.33
Time Constants Table
The Time Constants constant table is used to define times (for example, 60:00 for a timer of MM:SS) which
can be compared to constant variables in the ladder.

C.8.34
PLC Status Defines Table
The PLC Status Defines constant table contains possible status values (for example, PLCBsy) for third-party
PLCs for the PLCStt variable, which provides an indication on the communication with third-party PLCs.
Before performing a SCAN on a PLC database column, the PLCStt status is checked for communication
busy.
For further details, refer to Third Party Protocols Support manual.

C.8.35
Timer Event Defines Table
The Timer Event Defines constant table defines the possible timer events (for example, TETimr, TEPwUp)
which can occur in the RTU and require that certain tasks be started.
For further details about timer events, refer to Event Driven Software in the MC-IoT STS Advanced Features
manual.

C.8.36
Trigger States Table
The Trigger States constant table defines the possible fast event triggers (for example, FE_DI_COS) which
can occur in the RTU and require that certain high priority tasks be started immediately.
For further details about fast events and triggers, refer to the Trigger Enable (TEN)/Disable (TDS) on page
556 in the Ladder Diagram Language on page 517.

C.8.37
PLC Dynamic IOLINK Constants Table
The PLC Dynamic IOLINK Constants table contains constants used when connecting to the PLC dynamically
in runtime. For further details about Third-Party Protocols, refer to the MC-IoT STS Third Party Protocols
Support manual (in the "Dynamic I/O Link for PLC Data Type Columns" section.)

C.9
Data Types
Every column in the database tables (single or multiple-column), may be defined as one of the following data
types (the name in parentheses indicates the column data type in a multiple-column table):
● Discrete – Internal Bit (bit)
● Integer Value – Internal Integer Value (int)
● Real Value – Internal Real Value (real)
● Byte Value – Internal Byte Value (byte)
● Long Value – Internal Long Value (long)

586
 6802979C10-BA
Appendix C: Database Tables and Data Types

● Integer Parameter – Internal Integer Parameter (iprm)

● Real Parameter – Internal Real Parameter (rprm)
● Byte Parameter – Internal Byte Parameter (bprm)
● Long Parameter – Internal Long Parameter (lprm)
● Discrete Input (d-i)
● Discrete Output (d-o)
● Value Input (v-i)
● Value Output (v-o)
● Scaled Analog Input (sAI)
● Scaled Analog Output (sAO)
● Mapped Discrete (mbit)
● Mapped Value (mval)
● Mapped Byte (mbyte)
● Mapped Long (mlong)
● Hours Timer (Hr:Mn)
● Minutes Timer (Mn:Sc)
● Seconds Timer (Sc:Ms)
● Pulses Per Hour (pph)
● Time-Tagged DI (TgDI)
● Programmable Ladder Controller (plc_vi, plc_vo, plc_di, plc_do, plc_ri, plc_ro)
● Index (indx)
● Integer Constant (icon)
● Real Constant (rcon)
● Byte Constant (bcon)
● Long Constant (lcon)
● IP Address (IPaddr)
● IP Address Parameter (IPaddrPrm)

C.9.1
Discrete – Internal Bit (bit)
This data type may be used for internal logical (calculated) variables that have the following values:

Table 214: Discrete – Internal Bit Data Type Values

Value Meaning
‘0’ (false) The operation indicated that by the logical variable
is not active.
Examples: a machine that is not operating, a de-
energized relay, an alarm that is not activated, or a
disconnected switch.

587
6802979C10-BA
Appendix C: Database Tables and Data Types

Value Meaning
‘1’ (true) The operation indicated that by the logical variable
is active.
Examples: an energized relay, an operating ma-
chine, an activated alarm, a connected switch.

Variables of this data type are products of internal functions (rungs) or received from another site through the
communication system.. When the system starts up/restarts, all Discrete variables are reset to ‘0’.

C.9.2
Integer Value – Internal Integer Value (int)
This data type includes the internal (calculated) integer variables (positive and negative) in the range of
-32,768 to +32,767. These variables are represented by two bytes in 2’s complement format.
Variables of this data type are products of internal functions (rungs) or received from another site through the
communication system. When the system starts up/restarts, all Integer Value variables are preset to ‘0’.

C.9.3
Real Value – Internal Real Value (real)
This data type includes the internal (calculated) real variables (floating point) in the range
of - 3.402823466x1038 (displayed as -3.402823466E+38) to +3.402823466x1038 (displayed as
+3.402823466E+38). These variables are represented by four bytes in scientific notation.
Variables of this data type are products of internal functions (rungs) or received from another site through the
communication system.. When the system starts up/restarts, all Real Value variables are preset to ‘0’.

C.9.4
Integer Parameter – Internal Integer Parameter (iprm)
The variables of this data type are almost identical to Integer Value variables. The difference is that they
receive initial values at cold start of the system. While Integer Value variables are reset to ‘0’ at cold startup,
the Integer Parameter variables receive a value defined by the user. However, this value may be changed
during operation by means of the ladder diagram.

C.9.5
Real Parameter – Internal Real Parameter (rprm)
The variables of this data type are almost identical to the Real Value variables. The difference is that they
receive initial values at cold start of the system. While the Real Value variables are reset to ‘0’ at cold startup,
the Real Parameter variables receive a value defined by the user. However, this value may be changed
during operation by means of the ladder diagram.

C.9.6
Discrete Input (d-i)
This data type includes all discrete bits received by the Discrete Input modules of the RTU. The variables of
this data type may be assigned the logical value ‘0’ or ‘1’.
The user can connect each entry of any column, defined as Discrete Input, to any physical input in one of the
RTU Discrete Input modules. See Linking I/Os to the Database on page 366.

588
 6802979C10-BA
Appendix C: Database Tables and Data Types

The user controls when the physical inputs are read into any column, which is defined as Discrete Input.
Refer to Ladder Diagram Language on page 517.
The physical inputs are usually read before using the values of the column during the process.
The possibility of reading the inputs for each column separately enables you to perform various operations at
different rates (priorities).

C.9.7
Discrete Output (d-o)
This data type includes all discrete bits that are to be sent to the Discrete Output modules of the RTU. The
variables of this data type may be assigned the logical value ‘0’ or ‘1’.
The user can connect each entry of any column, defined as Discrete Output, to a physical output in one of the
RTU Discrete Output modules. (See Linking I/Os to the Database on page 366).
The user controls when the values of a specific column are sent to the physical outputs (refer to the Scan
(SCN) on page 534 in the Ladder Diagram Language on page 517).
The values of the column are usually sent to the physical outputs at the end of the column calculation (by the
process).

C.9.8
Value Input (v-i)
This data type includes the positive and negative integer variables read by the I/O modules (inputs or
counters) that provide numerical values. The absolute range of the Value Input for ACE3600 RTUs is from
-32,768 to +32,767 (same as Integer Value and Integer Parameter). If the I/O Legacy Resolution Advanced
Parameter was set to Legacy, the MOSCAD/MOSCAD- L Analog I/O bit resolution is used, and the range of
the Value Input is -4096 to 4095.
Each AI module type has a rated range of values, beyond which the values may not be assured due to
calibration. It is highly recommended to remain within the rated range for each module. (Beyond the rated
range, an Underflow/Overflow LED is lit on the I/O module.) For more information, see the AI Module Value
Representation section of the ACE3600 RTU Owner’s Manual.
Each module type may provide different ranges of values, as shown below:

Table 215: Value Input – Rated Ranges per AI Module Type

AI Module Type Resolution Value - Rated Range

AI Voltage ±5V ACE3000 (16 bit signed) ±32000
AI Current ±20mA ACE3000 (16 bit signed) ±32000
AI Voltage ±5V Legacy (13 bit signed) ± 4000
AI Current ±20mA Legacy (13 bit signed) ± 4000

Modules that include counters (accumulators) provide values in the range of 0 to +Full Scale. When the
counter reaches the upper value (+32,767 or +4095) and is advanced, it returns to 0.
Modules that include A/D conversion (the A/D provides a value that is proportional to the analog
measurement) provide a number in the range of -Full Scale to +Full Scale.
The connection between the variables in the columns, defined as Value Inputs, and the I/O modules is
performed by the I/O Link program. (See Linking I/Os to the Database on page 366).
The user controls when the physical inputs are read into any column defined as Value Input (refer to the Scan
(SCN) on page 534 in the Ladder Diagram Language on page 517).

589
6802979C10-BA
Appendix C: Database Tables and Data Types

Usually, the physical inputs are read before using the values of the column during the process.
The possibility of reading the inputs for each column separately enables you to perform various operations at
different rates (priorities).

C.9.9
Value Output (v-o)
This data type includes the positive and negative integer variables that are to be sent to one of the I/O
modules as a numeric or analog output. The range of the Value Output is from -32,768 to +32,767 (same as
Integer Value and Integer Parameter). If the I/O Legacy Resolution Advanced Parameter was set to Legacy,
the MOSCAD/MOSCAD-L Analog I/O bit resolution is used, and the range of the Value Output is -4096 to
4095.
Each module type may provide different ranges of values, as shown below:

Table 216: Value Output – Rated Ranges per AO Module Type

AO Module Type Resolution Value - Rated Range

AO Voltage 0-10V ACE3000 (14 bit signed) 0-16000
AO Current 0-20mA ACE3000 (14 bit signed) 0-16000
AO Voltage 0-10V Legacy (12 bit signed) 0-4000
AO Current 0-20mA Legacy (12 bit signed) 0-4000

The connection between the variables in the columns, defined as Value Outputs, and the I/O modules is
performed by the I/O Link program. (See Linking I/Os to the Database on page 366).
The user controls when the values of a specific column are sent to the physical outputs (refer to the Scan
(SCN) on page 534 in the Ladder Diagram Language on page 517).
Usually, the values of the column are sent to the physical outputs at the end of the column calculation (by the
process).

590
 6802979C10-BA
Appendix C: Database Tables and Data Types

C.9.10
Scaled Analog Input (sAI)
This data type includes the variables representing physical values that are read by the A/D modules only
and scaled to Engineering Units (EGU) (real values). The range of the Scaled Analog Input variable is from
-3.402823466E+38 to +3.402823466E+38 (same as Real Value and Real Parameter).
The user has to define the physical value at two points, so that the system translates the sensor output to a
physical value, as demonstrated in the following graph:

The first point, EGU High (EGUH), is the physical value when the sensor is at full scale. The second point
is the physical value when the sensor output is 0 or live-zero, as in the case of the 4-20 mA sensors. This
second point is called EGU Zero, EGU0. For sensors that output voltages in the range of ±V, the calibrating
point is the physical value when the sensor output is 0 and not -V.
The values of EGU Zero and EGU High should be defined in the relevant table by means of the Show
Related Data function. You also may define whether the EGU Zero is live-zero or not.
The connection between the variables in the columns, defined as Scaled Analog Inputs, and the A/D modules
is performed by the I/O Link program (refer to the I/Os and Database Linking (ACE3600/MC-EDGE Only) on
page 363 in the Application Programmer on page 324).
The user controls when the values of a specific column are read from the physical inputs (refer to the Scan
(SCN) on page 534 in the Ladder Diagram Language on page 517).
Usually, the physical inputs are read before using the values of the column calculation during the process.
The possibility of reading the inputs for each column separately enables performing various operations at
different rates (priorities).

591
6802979C10-BA
Appendix C: Database Tables and Data Types

C.9.11
Scaled Analog Output (sAO)
This data type includes the variables that are scaled to Engineering Units and are to be sent to one of the I/O
modules. The range of the Scaled Analog Output variable is from - 3.402823466E+38 to +3.402823466E+38
(same as Real Value and Real Parameter).
The user may define the two points (EGU Zero and EGU High) of the scaling function. Refer to Scaled
Analog Input.
The connection between the variables in the columns, defined as Scaled Analog Outputs, and the I/O
modules is performed by the I/O Link program (refer to the I/Os and Database Linking (ACE3600/MC-EDGE
Only) on page 363 in the Application Programmer on page 324).
The user controls when the values of a specific column are sent to the physical outputs (refer to the Scan
(SCN) on page 534 in the Ladder Diagram Language on page 517).
The values of the column are usually sent to the physical outputs at the end of the column calculation (by the
process).

C.9.12
Mapped Discrete (mbit)
This data type enables you to define a column of discrete variables that are a copy of discrete variables in
other tables. In this case, the discrete variables are copied from various tables (for a copy of a complete
column, refer to the Duplicate Column operation described in this chapter).
For each variable in a column defined as Mapped Discrete you should define the discrete variable from which
it is to be copied.
The user controls when the values are copied to the table (refer to the Scan (SCN) on page 534 in the Ladder
Diagram Language on page 517). Performing the Scan operation on a Mapped Discrete column is the same
as separately mapping each variable in the column.

C.9.13
Mapped Value (mval)
This data type enables you to define a column of value variables that are a copy of value variables in other
tables. In this case, the value variables are copied from various tables (for a copy of a complete column, refer
to the Duplicate Column operation described in this chapter).
For each variable in a column defined as Mapped Value, you should define the value variable from which it is
to be copied.
The user controls when the values are copied to the table (refer to the Scan (SCN) on page 534 in the Ladder
Diagram Language on page 517). Performing the Scan operation on a Mapped Value column is the same as
separately mapping each variable in the column.

C.9.14
Hours Timer (Hr:Mn)
This data type includes timers to be used as delays or retentive timers with resolution of 1 minute. The
maximum value of this type of timer is 99:59 (99 hours and 59 minutes).
A timer of less than 1 hour should be defined as a Minutes Timer, rather than Hours Timer, in order to
improve its resolution.

592
 6802979C10-BA
Appendix C: Database Tables and Data Types

In each column defined as Hours Timer, the user should define the preset time of every timer. This preset
time is assigned to the timer at cold startup of the system and may be set to another value by the appropriate
ladder diagram functions.
A detailed explanation about the use of the Hours Timer is provided in Ladder Diagram Language on page
517.

C.9.15
Minutes Timer (Mn:Sc)
This data type includes timers to be used as delays or retentive timers with a resolution of 1 second. The
maximum value of this type of timer is 99:59 (99 minutes and 59 seconds).
A timer of less than 1 minute should be defined as Seconds Timer rather than Minutes Timer in order to
improve its resolution.
In each column defined as Minutes Timer, the user should define the preset time of every timer. This preset
time is assigned to the timer at cold startup of the system and may be set to another value by the appropriate
ladder diagram functions.
A detailed explanation about the use of the Minutes Timer is provided in Ladder Diagram Language on page
517.

C.9.16
Seconds Timer (Sc:Ms)
This data type includes timers to be used as delays or retentive timers with resolution of 10 milliseconds. The
maximum value of this type of timer is 99:99 (99 seconds and 990 milliseconds).
In each column defined as Seconds Timer, the user should define the preset time of every timer. This preset
time is assigned to the timer at cold startup of the system and may be set to another value by the appropriate
ladder diagram functions.
A detailed explanation about the use of the Seconds Timer is provided in Ladder Diagram Language on page
517.

C.9.17
Pulses Per Hour (pph)
This data type defines variables (integers) with a value equal to the pulse rate in pulses per hour.
The user has full control of the time that the pph is updated in the column (refer to the Scan operator in the
Ladder Diagram Language on page 517.)
The user can connect each entry of any column, defined as Pulses Per Hour, to any physical input in one of
the RTU Discrete Input modules. (See Linking I/Os to the Database in the Application Programmer on page
324.)

C.9.18
Time-Tagged DI (TgDI)
This data type is similar to the DI data type. In addition, the system keeps track of these inputs. Every change
is recorded in a Time-Tag log buffer and/or events buffer. It is recorded together with the date and time in 1
msec resolution. The Time-Tag buffer can be read using the Time-Tag Logger tool. The events buffer can be
read via a ladder construct by calling the GtEvnt function.
See the Event Driven Software in the MC-IoT STS Advanced Features manual.

593
6802979C10-BA
Appendix C: Database Tables and Data Types

This data type is relevant for electric applications and only the important inputs should be defined as Time-
Tagged DI, since this feature is CPU-time consuming.
The user can connect each entry of any column, defined as Time-Tagged DI, to any physical input in one of
the RTU Discrete Input modules. (See Linking I/Os to the Database in the Application Programmer on page
324).

C.9.19
Programmable Ladder Controller (plc_vi, plc_vo, plc_di,
plc_do, plc_ri, plc_ro)
This data type is used to read from the PLC or write to the PLC, which supports the Third-Party protocols.
See the MC-IoT STS Third Party Protocols Support manual for more information.

C.9.20
Index
This data type includes pointers to rows of multiple-column tables. Since each row in a multiple-column table
represents the variables of a device, the Index is a pointer to the device.
The Index enables the user to write an algorithm for one row of the table and apply it to all table rows. The
Index variable may be defined only in the Index table (one of the system tables). The index value is limited to
the range 0-250 at any given time (the number of rows in a table is limited to 250). If an index exceeds the
250 limit, an error message is recorded in the Error Logger, because no tables have more than 250 rows.

C.9.21
Constants
Constants are defined by a symbolic name and numeric value in single-column tables. The symbolic names
of the constants are used in the ladder diagram.
There are four types of constants:
● Integer
● Real
● Byte
● Long
The advantage of using the symbolic name in the ladder diagram rather than the value is that in case of
changes, it is easier to change the value only in one place (in the table) rather than searching in all functions.

C.9.22
Byte Value
This data type includes the internal (calculated) single-byte integer variables (positive and negative) in the
range of -128 to +127. These variables are represented by one byte in 2’s complement format.
Variables of this data type are products of internal functions (rungs) or received from another site through the
communication system. When the system starts up/restarts, all Byte Value variables are preset to ‘0’.

594
 6802979C10-BA
Appendix C: Database Tables and Data Types

C.9.23
Long Value
This data type includes the internal (calculated) long integer variables (positive and negative) in the range of
-2147483648 to +2147483647. These variables are represented by four bytes in 2’s complement format.
Variables of this data type are products of internal functions (rungs) or received from another site through the
communication system. When the system starts at cold start (for example, after reset load), all Long Value
variables are preset to 0.

C.9.24
Mapped Byte
This data type enables you to define a column of byte variables that are a copy of byte variables in other
tables. In this case, the byte variables are copied from various tables. For a copy of a complete column, see
Duplicated Columns on page 561.
For each variable in a column defined as Mapped Byte, you should define the byte variable from which it is to
be copied.
The user controls when the bytes are copied to the table (refer to the Scan (SCN) on page 534). Performing
the Scan operation on a Mapped Byte column is the same as separately mapping each variable in the
column.

C.9.25
Mapped Long
This data type enables you to define a column of long variables that are a copy of long variables in other
tables. In this case, the long variables are copied from various tables. For a copy of a complete column, see
Duplicated Columns on page 561.
For each variable in a column defined as Mapped Long, you should define the long variable from which it is to
be copied.
The user controls when the bytes are copied to the table (refer to the Scan (SCN) on page 534). Performing
the Scan operation on a Mapped Long column is the same as separately mapping each variable in the
column.

C.9.26
Byte Parameter
The variables of this data type are almost identical to the Byte Value variables. The difference is that they
receive initial values at cold start of the system. While the Byte Value variables are reset to ‘0’ at cold startup,
the Byte Parameter variables receive a value defined by the user.
However, this value may be changed during operation by means of the ladder diagram.

C.9.27
Long Parameter
The variables of this data type are almost identical to the Long Value variables. The difference is that they
receive initial values at cold start of the system. While the Long Value variables are reset to ‘0’ at cold startup,
the Long Parameter variables receive a value defined by the user.
However, this value may be changed during operation by means of the ladder diagram.

595
6802979C10-BA
Appendix C: Database Tables and Data Types

C.9.28
IP Address
This data type represents IP addresses (in the form of 0.0.0.0 to 255.255.255.255), represented by four
bytes. Variables of this data type are products of internal functions (rungs) or received from another site
through the communication system. When the system starts up/restarts, all IP addresses variables are preset
to ‘0.0.0.0’.

C.9.29
IP Address Parameter
The variables of this data type are almost identical to the IP Address variables. The difference is that they
receive initial values at cold start of the system. While the IP Address variables are reset to ‘0.0.0.0’ at cold
startup, the IP Address Parameter variables receive a value defined by the user. However, this value may be
changed during operation by means of the ladder diagram.

596
 6802979C10-BA
Appendix D: User Defined Local Ports

Appendix D

User Defined Local Ports

Some ports in the system may be defined as user ports via Site Configuration. The user ports are controlled
by the ladder application through the appropriate functions and through the user ports table (one of the
system tables).
There are specific constant tables, described below, that play a role in user-defined communication.
When a port is defined as a user port, the port and the protocol are controlled by the user that writes the
rungs. For example, you may use a port for printing on a printer or for connection to a computer (or any other
smart unit) by writing the appropriate protocol.
The RS-232 ports in the system use a telephone-type 8-pin connector. To connect any equipment that
requires a standard RS-232 interface, use one of the following cables:
● Modem adapter cable FLN6458 (with male 25-pin D-type connector) for connection to an external
modem.
● Modem adapter cable FLN6458 (with male 25-pin D-type connector) for connection to an external
modem.
To connect two RS-232 ports of two sites (configured as RS-Link in Site Configuration), use the above-
mentioned cables (connect the male and female 25-pin D-type connectors).
IMPORTANT: You can only connect two RS-232 ports with these cables.

597
6802979C10-BA
Appendix D: User Defined Local Ports

D.1
User Ports Table
The user ports table is the link between the user rungs and the communication software that is part of the
RTU system software. The number of rows in the table should be modified according to the number of user
ports defined in Site Configuration.
Figure 300: User Ports Table

Each row in the table includes the variables and flags for each User Port:
● User_1 refers to row 0
● User_2 refers to row 1
● User_3 refers to row 2
Use these symbols to refer to the port (the assignment of the physical ports is performed by Site
Configuration).
You can open the User Ports table from the System Tables list.

D.1.1
PTxFlg Variable and SEND Operator
The PTxFlg flag is updated once the SEND operator is called. The SEND operator sends messages
(character strings) to the appropriate port. After calling the SEND operator, the PTxFlg flag specifies whether
or not the message has been taken by the system for transmission (queue is full). PTxFlg = ‘1’ means
that the message has been taken.
Example:

598
 6802979C10-BA
Appendix D: User Defined Local Ports

This rung sends the message in the window to USER_2 (User Port no.2). The next rung, after performing the
SEND operator, should check whether the message is to be sent or not (since the system buffer is full). Insert
the value of USER_2 into an index variable (for example, x) and then check if x is equal to 1 or not.
If the message was not taken for transmission, then the SEND operator should be activated again after a
while.
You may call the SEND function with an index that has been loaded with the appropriate value: USER_1 to
USER_4.
Instead of using PTxFlg,x, you may use the following:
● PTxFlg or PTxFlg, 0 for User Port 1
● PTxFlg, 1 for User Port 2
● PTxFlg, 2 for User Port 3
The SEND operator sends a free-format message to the ports defined as user ports.

When the rung is true, the message in the window is sent to the user port specified above the SEND
operator.
The message may include characters, text, and also variables combined with text. The message may be sent
to a printer, terminal, or may be used for communicating with any other unit using serial protocol. If the rung
conditions are constantly fulfilled and you want to send the message only once, a differentiator should be
used.
Example 2: The following rungs print a message that includes the temperature when it exceeds HiLmt or
goes below LowLmt. TEMP is the temperature variable and HiLmt and LowLmt are constants.

<TEMP> indicates to the unit that the value of the TEMP variable should be sent. The variable in between the
angular brackets must be defined in the data base. The variable may be either from a single-column table or
from a multicolumn table including an index (for example, Status, I).
The variable values will be printed/displayed according to the following formats:
1. <BIT>: Sends the value of a discrete variable (0 or 1) with a space before the digit: “ 0” or “ 1” (that is,
two characters).
2. <VAL>: Sends the value of the VAL variable defined as one of the following data types:

599
6802979C10-BA
Appendix D: User Defined Local Ports

● Integer Value, Parameter

● Byte Value, Parameter
● Long Value, Parameter
● Value Input, Value Output
● Mapped Value, Mapped Byte, Mapped Long
● PPH
● Index
The value is sent as a fixed field of six characters in the range of -32,768 to +32,767. For example:
● 30000
● -27263+12
● -500
● +1
● 0
If the VAL variable is defined as one of the following data types, then the value is sent as a fixed field of
16 characters in the range of -3.402823466x1038 to +3.402823466x1038:
● Real Value
● Scaled AI, Scaled AO
● Real Parameter
● Real Constant
3. <<BIT>: Sends the value of a discrete variable (0 or 1) without a leading space.
4. <<VAL>: Sends the value of the VAL variable in its actual length (not as a fixed field length).
Note that formats 1-4 convert the value of the variable into an ASCII string while Format 5 sends the
value of the variable as a character directly to the port.
5. ‘n<STRING,I>: Sends a series of characters (n characters) whose codes (variables) are stored in the
low bytes of the variables in a column named STRING (starting at STRING,I). For I=K the first string to
be sent is LOWBYTE (STRING,K) and the last one LOWBYTE (STRING,K+n). It should be noted that n
may be an integer constant or index. n as index enables sending a string with variable length (supported
from version ≥ V1.63).
The ‘<STRING,I> sends a single character; that is, ‘<STRING,I> = ‘1<STRING,I>.
IMPORTANT:
● The ‘ character (in ‘n<STRING,I> or ‘<STRING,I>) should be the ASCII character 39
● The number, n, preceding the string (as in ‘n<STRING,I>) should be a fixed number, for example,
'5<STRING>, rather than a constant number ‘#5<STRING,I>.
● If n (in ‘n<STRING,I>) is an existing valid variable (index) which is changed by the user elsewhere,
it will be updated in the SEND function.
● If n (in ‘n<STRING,I>) does not exist, 'n is presented as two ASCII characters and the variable
<STRING,I> is presented as an integer value.
When the RTU sends the text, it adds <LF> and <CR> characters at the end of each line. The codes
appear in the following order: <LF> (Hex-0A) and <CR> (Hex-0D).
You may cancel the insertion of these two codes by adding the “\” character at the end of the line (after
the last character). This feature is useful when defining a protocol by the SEND operator and also when
sending “Escape Sequences” or parts of sentences to a terminal screen.

600
 6802979C10-BA
Appendix D: User Defined Local Ports

If you use “\”, make sure that there are no additional spaces after the character. Otherwise, it is not
considered as CR-LF cancellation.
Example:
The rung below positions the cursor on column 30 of the first line and then sends the following heading:
ALARM REPORT SCREEN.
NOTE: Make sure that the terminal accepts “Escape Sequences”.

The first line in the window positions the cursor on the screen. The “Escape Sequence” starts with the Esc
character; type the Esc character on your keyboard – the symbol will appear on the screen.
The “\” character at the end of the first line informs the system not to insert <LF> and <CR> at the end of the
“Escape Sequences”. If the “\” character at the end of a line is part of your text, then add a space at the end
of the line.
The rung may be written in another way:

In this example, it is difficult to identify the beginning of the text.

To print a variable in 24-hour format, use %<VAL>
This will send the VAL variable as: “_HH:MM”. For example, %<TIME> will send the TIME variable in this
format.
The system automatically identifies a Timer variable (Hours, Minutes, or Seconds) in between <> or << >,
and sends it in Timer format: “_XX:YY” for <Timer> and “XX:YY” for <<Timer>.
To print at different locations of the screen, use the following format:
[<<y>;<<x>H

where:
y is the variable that represents the row number
x is the variable that represents the column number

For example, for row 14, column 24: y=0x3134 (the ASCII values of 1 and 4, respectively) and x=0x3234
(the ASCII values for 2 and 4, respectively).

601
6802979C10-BA
Appendix D: User Defined Local Ports

D.1.2
PRxFlg Variable
The PRxFlg variable is updated by the system when the GetChr and GetDgt functions are called. The
variable receives the value ‘1’ whenever a character is read from the selected User Port. If the PRxFlg
variable is ‘0’ after calling the GetChr function, it means that no character has been received. Refer to the
PRxChr and PRxNum variables.

D.1.3
PRxChr Variable and GetChr Function
The GetChr function is called by the CALL operator. It reads one character from the specified port into the
PRxChr variable in the appropriate row of the user ports table.
Ensure that the reading operation was successful (a character has been read) by checking the PRxFlg
variable.
The following rung will read a character from User Port no.3:

The ASCII table, accessed from the Constant Tables list, contains all the characters that you may use for
comparison with the PRxChr value. The ASCII characters are detailed in the following table.

602
 6802979C10-BA
Appendix D: User Defined Local Ports

Figure 301: ASCII Characters

D.1.4
PRxNum Variable and GetDgt Function
The PRxNum variable may receive a series of digits by using the GetDgt function. It indicates the equivalent
of that series at any given time.
The GetDgt function is called by the CALL operator. It reads one digit from the specified port into the
PRxNum variable in the specified row. PRxNum = (outdated PRxNum)*10 + Input Digit.
Once the GetDgt function has been executed, you should check the following:
● PRxFlg is ‘1’, indicating that a digit has been read from the port.
● PRxChr has received the value of ChrDgt (8196 – refer to the ASCII table). If the value of the PRxChr
variable is not equal to ChrDgt, it means that the received character is not a digit. In this case, the
received character is stored in the PRxChr variable and PRxNum is not affected.

603
6802979C10-BA
Appendix D: User Defined Local Ports

D.1.5
PrtFal Variable
The PrtFal (Port Fail) variable is updated by the system when the SEND function is called. The PrtFal
variable specifies the status of the port:
● PrtFal=0 indicates that the port is OK.
● PrtFal=1 indicates that the port is faulty.

D.1.6
PrtMod, Protcl, and PrtRat Variables
The PrtMod (Port Mode), Protcl (Protocol), and PrtRat (Port Rate) variables allow you to define the mode
of operation, protocol, and data speed for the communication port. These variables may be set by the user
when building the user ports table using the Show Related Data option. The default is: 8 bit, no parity, one
stop bit, binary protocol, and 1,200 bps. The user can modify these variables during runtime by using the
MOVE operator on the appropriate constants, detailed in the following tables.

D.1.6.1
PrtMod Variable
The PrtMod variable may receive one of the modes that appear in the User Port Modes table (one of the
Constant tables) shown below:
Figure 302: User Port Modes Table

The various modes are described in the following way:

604
 6802979C10-BA
Appendix D: User Defined Local Ports

● 7b/8b – stand for 7 bits or 8 bits, respectively.

● Np/Ev/Od – stand for no parity, even parity, or odd parity, respectively.
● 1S/2S – stand for 1 stop bit or 2 stop bits, respectively
For example, 7bEv2S means 7 bits, even parity, and 2 stop bits.

D.1.6.2
Protcl Variable
The Protcl variable defines the protocol to be used. It may receive one of the options that appear in the User
Port Protocols table (one of the Constant tables) as shown below:
Figure 303: User Port Protocols Table

In the Binary Protocol (default in the table and in the system), the characters are transparently transferred.
The XonXof Protocol defines the ports for ASCII and automatically supports the Xon and Xoff control
characters. If you use Xon/Xof, make sure that the data that is sent does not conflict with the Xon/Xof
values (the data should not include the values 10/13)

D.1.6.3
PrtRat Variable
The PrtRat variable defines the port data speed. It may receive one of the options that appear in the User
Port Baud Rates table as shown below:

605
6802979C10-BA
Appendix D: User Defined Local Ports

Figure 304: User Port Baud Rates Table

D.1.7
Ready and NotRdy Functions
The Ready and NotRdy functions are called by the CALL operator. They allow manual control (via rungs) of
the DTR (Data Ready) or CTS (Clear To Send) signals, depending on the type of connection. The functions
may be applied on user ports only.
If the RTU acts as DTE, then the Ready and NotRdy functions control the DTR signal. If the RTU acts as
DCE, then these two functions control the CTS signal.
The default mode of operation is that the system software automatically controls the communication. Calling
the NotRdy function will reset either the DTR or CTS signal. Calling the Ready function will return the
automatic mode of operation (controlled by the system software).
Contrary to the Send operation, which sends the job to the system software for execution, the Ready/NotRdy
functions affect the port immediately. This means that, if you need to perform an operation between Ready
and NotRdy, use a delay timer to ensure the execution of the Send operation.
NOTE: Before calling the Ready function, you must call the GetChr function once in order to enable
control of the DTR signal.

606
 6802979C10-BA
Appendix D: User Defined Local Ports

D.2
Example of Building Local Communication
Processes
The following example describes the relevant processes of a simple case: A keyboard and screen of a
terminal is connected to the unit port. A header will be displayed at the top of the screen and then the
message “Enter Number”. The end user will enter a number while each digit will be displayed (echo). After
pressing ENTER, the number is multiplied by a factor (defined in the database). The result is then displayed.
The database of definitions (variables and constants) and the process/subprocesses of this simple example
are shown below.

D.2.1
Database Definitions
Two value variables (STATE and RESULT) are used in the process programming. They are defined in a User
table named Internal Variables.
Figure 305: Internal Variables Table

An internal parameter (FACTOR) is also used in the process programming. It is defined in a User table
named Internal Parameters.

607
6802979C10-BA
Appendix D: User Defined Local Ports

Figure 306: Internal Parameters Table

Four constants, Header, KeyIn, OutSt, and Finish, which define the STATE variable, are also used in the
process programming. They are defined in a Constant table named Internal Constants.
Figure 307: Internal Constants Table

The following process list includes all subprocesses.

608
 6802979C10-BA
Appendix D: User Defined Local Ports

● MAIN – The main process calls the subprocesses as a function of the STATE variable.
● HeadrP – Sends a header and instructions to the screen.
● KeyInP – Positions the cursor and displays the typed number after each digit.
● OutP – Sends a message to the screen including the result.

D.2.2
Main Process
The main process controls the RTU local communication. The main process checks the STATE variable and
jumps to a subprocess accordingly. First, the process sends the headers to the screen. Then, it receives the
number entered by the end user and multiplies it by an internal factor. Finally, the result is sent to the screen,
and the STATE variable is reset to 0.
NOTE: The process is serial and any subprocess will not be performed until the previous one has been
executed (by the STATE variable that is advanced after the subprocess execution).
After performing one complete cycle of receiving, computing, and displaying the result, the STATE variable is
compared to the Finish variable to start another cycle.
The main process rung list is displayed:

The rungs are as follows:

D.2.3
HeadrP Subprocess
This subprocess sends messages (headers) to the screen by the following rungs:

609
6802979C10-BA
Appendix D: User Defined Local Ports

The first row in the window clears the screen. The second row positions the cursor in column 25 of the first
line of the screen. The third row includes the header to be displayed. The fourth row positions the cursor at
the beginning of line 3 of the screen, and the last row includes the message “Enter Number :” to be displayed.
The second rung checks the PTxFlg,0 (indicates the flag of port USER_1) variable. If it is 1, it means that the
messages have been taken for transmission to the port, and the STATE variable is assigned the KeyIn value.

D.2.4
KeyInP Subprocess
This subprocess receives each key press (checks whether it is a numeric or non-numeric key) and displays
the digits typed in. Then, upon receiving the CR character, the number is multiplied by the FACTOR constant.
At this stage, the STATE variable is advanced. The subprocess comprises the following rungs:

● The first rung (1) calls the GetDgt function in order to read a digit into the PRxNum variable.
● The second rung (2) checks that a digit has been received (PRxFlg,0 is true) and that it is a digit by
comparing the value of the received digit (PRxChr,0) to ChrDgt. If so, then the accumulated number
PRxNum is sent to the screen.
● The third rung (3) checks if a CR character has been received (PRxFlg,0 is true and the value of the
received character is Chr_CR). If it so, then the received number, accumulated in PrxNum, is multiplied
by the FACTOR constant. The result is inserted into the RESULT variable, and the STATE variable is
advanced.

D.2.5
OutP Subprocess
This subprocess sends the result to the screen. It comprises the following rungs:

610
 6802979C10-BA
Appendix D: User Defined Local Ports

611
6802979C10-BA
Appendix E: User Defined MDLC Communication

Appendix E

User Defined MDLC Communication

The MOSCAD system uses the MDLC protocol, based on the OSI (Open Systems Interconnection) model
published by ISO. The protocol comprises the seven recommended layers adapted for SCADA and supports
all Toolbox functions.
It also supports the following functions:
● Central-to-RTU data transfer
● Central-to-RTUs broadcast
● RTU event reporting
● RTU burst reporting
● RTU-to-RTU communication

E.1
Central-to-RTU Data Transfer
The central is able to affect (read/write from/to) any RTU in the system, since all RTU database tables are
known to the central. The definition of the RTU database tables is automatically transferred to the central.
In addition, any cross section of any table can be downloaded from or uploaded to the central. The central
may download/upload any number of rows, columns, a complete table, and one or more columns in one or
more rows if they meet specific conditions.
This type of communication is almost transparent to the process in the RTU. The definition of the database
tables cross sections to be included in each transmission is performed by the Data Transaction Selectors.
The central may condition the data transfer from the RTU on the COS (Change of State) flag. The RTU will
transmit only the row numbers of the required tables in which the COS flag is true, and the relevant data.
When the data is transferred to the central, the RTU resets the COS flag to 0.
The COS flag is a single bit for every row of all tables. It may be true in the following cases:
● Any change in one of the table entries, defined as Discrete Input, automatically sets the COS flag of the
appropriate row.
● In table columns defined as Value Input/Scaled Analog Input, any change in the last reported data that
is greater than COS delta (defined for every Value Input in the I/O Link) automatically sets the COS flag
of the appropriate row. The user can also set and reset the COS flag in an application, using services
provided by the ‘C’ Toolkit.
● By applying the Ladder Diagram operators on the COS Name variable, the user can define the conditions
(such as calculated variables) to set/reset the COS flag.
To set the COS flag in a single/multi-column table, use the following rung:

<Name> is the COS name that you have assigned to the single/multi-column table. I is an index that
indicates the row of the relevant COS flag.

612
 6802979C10-BA
Appendix E: User Defined MDLC Communication

In previous versions of the Toolbox, the COS flag was supported by means of the SetCOS function. From
version 1.74 of the Toolbox, the COS flag is supported by the COS Name variable. When upgrading previous
versions, the SetCOS function is still supported.
Remember that if the relevant rungs of the SetCOS function are deleted, you will have to use the COS Name
variable to handle the COS flag.

E.2
Central-to-RTU Broadcast
The system enables simultaneous data transmission to a group of RTUs. This type of communication, called
Broadcast, should modify the RTUs’ mode of operation or serve as a trigger for a specific operation. The
broadcast command includes the necessary information concerning the addressed RTUs and the command
itself.
The broadcast may be transmitted over a specific link or all links in the system. The broadcast message
includes a condition (qualifier). The broadcast is received by all RTUs on one or more specified links. Only
the RTUs that fulfill the condition will refer to the broadcast (the other RTUs, which do not fulfill the conditions
will ignore the broadcast). An unlimited number of RTU groups may be created by defining different qualifiers.
The qualifiers are defined in the Qualifiers table (reserved by the system as one of the User Tables).
Since the value of the qualifier can be dynamically changed, the composition of the RTU group can vary
accordingly. Each RTU checks the validity of the qualifier; if the condition is valid, the RTU automatically
belongs to the group.
The broadcast command then assigns a value to a specific variable in the Qualifiers table in all RTUs that
belong to the group.
The broadcast command then assigns a value to a specific variable in the Qualifiers table in all RTUs that
belong to the group.
Broadcast reception does not require any support in ladder diagram; it is sufficient to define the qualifiers in
the Qualifiers table to be used by the user process.
Since the IP Gateway does not know how many RTUs will belong to the group, there is no acknowledgment
for this type of communication. Therefore, you should use broadcasts only when a synchronized operation is
to be performed on a group of RTUs.
Logically, the broadcast may be described in the following manner (Qual1 and Qual2 are two variables
defined in the Qualifiers table):
If (Qual1 = x) then Set Qual2 = y.
The Qual2 variables of all RTUs having a Qual1 variable equal to x, receive the value of y. The y value may
be used to control the RTUs’ mode of operation or as a trigger for a specific operation. You may create any
number of groups by defining different qualifiers in the Qualifiers table. Each RTU may belong to more than
one group, according to the defined qualifiers.

E.3
RTU-to-RTU Communication Guidelines
RTU-to-RTU communication is used for transferring data between different RTUs. The system provides all
variables and constants to be used for this type of communication. The communication system supports
network communications, including transmission retries in case of communication failures.
All variables and constants required for this type of communication are already included in the appropriate
System tables. The user may build the applicable communication process through the process programming,
using rung sequences. The user should specify the data to be transmitted and the name of the addressed
RTU.

613
6802979C10-BA
Appendix E: User Defined MDLC Communication

Each RTU may send/receive frames in two ways:

● Normal fashion – the order of the transmitted frames is not guaranteed. The order of the received frames
may be different from the order of the transmitted frames.
● Sequential fashion – the order of the received frames is identical to the order of the transmitted frames.

E.4
Variables/Constants & Functions Used for MDLC
Communication
E.4.1
Variables/Constants
The user can control the MDLC two-way communication between RTUs (burst and broadcast) and event
reporting to the central. This is achieved by using the appropriate variables/constants and functions provided
by the system.See Communication Functions Available via the CALL Function on page 614.
The variables and constants are from the following database tables:
● Site table
● RTU-to-RTU Comm Buff
● RTU-to-RTU Controls
● Tx Event
● Tx Burst
● Event Definitions

E.4.2
Communication Functions Available via the CALL
Function
Data transfer between RTUs and event reporting to the central are supported by the following functions that
are executed by the CALL output operator:
● SndFrm (Send Frame): Transmission of an MDLC frame initiated by the RTU to another RTU. Answer
is required. Appropriate when the data is being relayed through other sites (that is, when Source/
Destination sites are not the From/To sites.)
● AnsFrm (Answer Frame): Answering of an MDLC frame in response to another RTU transmission.
Appropriate when the data is being relayed through other sites (that is, when Source/Destination sites are
not the From/To sites.)
● RcvFrm (Receive Frame): Reception of an MDLC frame transmitted by another RTU.
● TxFrm (Transmit Frame): Transmission of an MDLC frame initiated by the RTU to another RTU. No
answer is required. No retries are initiated at the application level. Usually appropriate when the data is
being sent directly to the destination site.
● EvntSq (Transmit Event Sequential): Sequential transmission of an event to the central (legacy central)
using frame sequence communication. No Ack is sent.
● Burst: Transmission of data to the central. An ACK is only sent if the appropriate Data- Ack from central
Advanced Parameter is set.

614
 6802979C10-BA
Appendix E: User Defined MDLC Communication

● SndSeq (Send Sequence): Sequential transmission of MDLC frames initiated by the RTU to another
RTU. No Ack is sent.
● GetSeq (Get Sequence): Sequential reception of MDLC frames transmitted by another RTU. No Ack is
sent.
● BrstSq (Burst Sequence): Sequential transmission of data bursts to a central.

E.5
Site Table
In the Site table, you should define all the RTUs, which perform RTU-to-RTU communication, and the
centrals to which you want to send events. The Site table includes four columns/fields, as detailed below:
Figure 308: Site Table

● Site Name – symbolic name of the RTU or group of RTUs.

● Site ID – the RTU Site ID as defined in the Site Configuration program.
● Link ID – the link through which the RTU is connected to the network. Pressing [Enter] when the cursor is
in this field will display a choice list.
● ComFal – indicates if communication to this site exists. When the site comes up or when communication
to the site is initiated (SndFrm, Burst, SndSeq, GetSeq, BrstSq), the ComFal bit is set to ‘0’. If no ACK
is received, even after retries at all level of communications have been exhausted, the ComFal bit is set
to ‘1’(SndFrm, Burst only). Any subsequent communication with the same site that succeeds, resets the
ComFal to ‘0’ (SndFrm, Burst, SndSeq, GetSeq, BrstSq). Note that in cases of serial transmissions to the
same site, the ComFal will continuously be reset, and the Error bit in the SndFrm routine should be used.
See Transmit Mode on page 619.
The site names defined in this table should be used when writing rungs. The system will communicate with
the RTUs according to the Site IDs and Link IDs defined in this table.

615
6802979C10-BA
Appendix E: User Defined MDLC Communication

The first row in the table, Cntral (for central), is the system default central (legacy central only). If the system
includes several centrals that are designated to receive events, they should be defined in this table: the
central symbolic name and the Site ID and Link ID of the RTU/FIU connected to that central.
In this table, you may also define names of groups for transmitting broadcasts (do not confuse RTU-to-RTU
communication broadcast with broadcasts that are sent from the central to a group of RTUs according to
qualifiers). To define a broadcast, define the Site ID as 0. The Link ID should be the link name to which
the broadcast is to be transmitted. To send a broadcast to all RTUs in the system, the Link ID should be
ALL_LINKS (selected from the choice list).
When Site ID = 0, all RTUs in the specified link (or all RTUs in the system if Link ID = ALL_LINKS) will
receive the transmitted frame. You may add conditions to the transmitted frame by using the variables of the
Qualifiers table. In this case, only the RTUs that fulfill the conditions will refer to the transmitted frame.
When using the Site_ID variable for setting the DstSit, or for comparison with SrcSit, the Database Table
Monitoring mode displays the Site_ID index in the Site table and not its real value. This is different from other
variables in order to make the communication more efficient without wasting time on the conversion of indices
to names.

E.6
RTU-to-RTU Communication
RTU-to-RTU communication consists of transferring information between an application defined for one RTU
and another application defined for a parallel RTU. When configuring the RTU application, the user should
update the applicable tables previously defined.
The RTU-to-RTU communication includes a frame transmission (of Origin type or FrmSeq – see Receive
Variables on page 617) from RTU A to RTU B and a frame transmission (of Answer type – see Receive
Variables on page 617) from RTU B to RTU A, with or without data as an acknowledgment.
You may also send a broadcast from RTU A to a group of RTUs. There is no acknowledgment.

E.6.1
RTU-to-RTU Comm Buff / RTU-to-RTU Controls Tables
The communication between RTUs is carried out by the RTU-to-RTU Controls and the RTUto- RTU Comm
Buff tables, which include buffers for transmission and reception (TxBuf and RxBuf). Data is transmitted by

616
 6802979C10-BA
Appendix E: User Defined MDLC Communication

inserting it into the TxBuf and calling the SndFrm, AnsFrm, TxFrm, or SndSeq functions. The data received
by the RcvFrm or GetSeq functions is stored in RxBuf.
Figure 309: RTU to RTU Comm Buff Table

E.6.2
Last Index (BufEnd)
The Last Index (BufEnd) defines the size of the transmit/receive buffers – the maximum number of values (up
to 80) to be transmitted/received. The buffers consist of values, each comprised of 16 bits.

E.6.3
Transmit Variables
● DstSit (Destination Site): The name of the addressed RTU, as defined in the Site table. The DstSit
variable is used only by the SndFrm and SndSeq functions.
● Tx_Len (Transmit Length): The number of values to be transmitted. This number must be between 1 and
the number of values defined in the buffer. After the frame is taken by the system, the system clears
Tx_Len variable to 0. Otherwise, it means that the queue is full.
● TxBuf (Transmit Buffer): Up to 80 variables that are the transmit buffer. Use the MOVE or CPY operators
to insert the variables into the TxBuf (you may use indexes).

E.6.4
Receive Variables
● ScrSit (Source Site): After calling the RcvFrm or GetSeq functions, this variable receives the name of the
transmitting RTU. The site identification is performed by comparing the RTU name (in the SrcSit variable)
to the RTU names defined in the Site table. See Site Table on page 615.
● FrmTyp (Frame Type): When a frame is received, this variable is updated according to the type of
frame received. There are six types of frames in the RTU-RTU Frame Types table (one of the Constants
Tables), as follows:

617
6802979C10-BA
Appendix E: User Defined MDLC Communication

Figure 310: RTU-RTU Frame Types Table

○ Origin – For a frame that has been transmitted by the SndFrm function from the other RTU. An
answer is required.
○ Answer – For a frame that has been transmitted by the AnsFrm function from the other RTU. No
answer is required.
○ GrpCal – For a frame that has been transmitted by the TxFrm/ SndFrm function from the other RTU.
No answer is required.
○ Messag – For a frame that has been transmitted by the TxFrm function from the other RTU. No
answer is required.
○ NO_Ans – When the RcvFrm function is activated and the addressed unit has not answered, SrcSit
receives the index of the unit and Rx_Len is reset to 0.
○ FrmSeq – For a frame that has been transmitted by the SndSeq function from the other RTU.
● Rx_Len (Receive Length): The number of values received (up to 80). When the frame is received by the
RcvFrm or GetSeq functions, the Rx_Len variable is set to the number of values received by the buffer. If
no frame is received, Rx_Len is reset to 0.
● RxBuf (Receive Buffer): Up to 80 variables that are the receive buffer.
If a frame of Origin type is received, a frame of Answer type should be sent as an acknowledgment. If there is
no data to send back, you should send a frame (of one value) as an acknowledgment. If such a frame is not
transmitted as an answer, the frame of Origin type will be retransmitted.

618
 6802979C10-BA
Appendix E: User Defined MDLC Communication

E.6.5
Transmit Mode
The transmission is performed through the RTU-to-RTU Controls and RTU-to-RTU Comm Buff tables. The
user should write rungs to set the destination site name (DstSit variable), the Tx_Len (number of values to
be transmitted in the frame), and move the values to be transmitted by the MOVE/CPY operators, to the
corresponding variables in TxBuf.
The transmission is initiated by calling the SndFrm function.

After calling the SndFrm or SndSeq functions, the Tx_Len variable should be checked. If this variable has
been reset to 0, it means that the frame has been queued for transmission. If it has remained the same, it
means that the frame has not been taken for transmission because the internal buffers are full. In this case,
you should retry sending the frame after a period of time (by using a timer).
In case of failure, such as faulty addressed RTU, or if no Ack is received, the bit (<Error>,n) specified by the
user below the CALL operator is set to ‘1’ to indicate a failure. Note that this bit is reset to ‘0’ at the beginning
of the transmission routine. Select the name of the variable (after defining it in the database). You also can
define a column for these error bits and use an index (for example, Err,x) to indicate an error for each RTU.
This Error bit is useful when several transmissions are to be sent to the same site. Because the ComFal
bit defined in the Site table for each site is reset to 0 each time transmission is initiated, the Error bit in the
SndFrm function can be used to track the status of each transmission to the site, rather than the status of the
site itself. Otherwise, the behavior of the error bit is exactly like that of the ComFal bit (see Site Table on page
615).
Another transmit function, TxFrm can be used in RTU-to-RTU communications. TxFrm, unlike SndFrm, does
not perform retries on the application level and does not require an answer. This function is appropriate when
the transmitting site is also the Source site and the receiving site is the Destination site (that is, when the data
is not being relayed through other sites.) The one exception to this is when the Destination is a Dual CPU.
In this case, if the CPU is secondary/not active, it can only react (Answer) and cannot initiate transmission.
Therefore, SndFrm/Answer should be used.

E.6.6
Receive Mode

The receive function is carried out by using one of the following rungs:

When a frame is received, the Rx_Len variable is set by the system to the number of values in the received
frame, and the SrcSit variable is set to the name of the transmitting site. The transmitting site name (SrcSit)
should be checked by comparing it (using comparator elements) to the site names defined in the Site table.
The frame type should be compared to the frame types defined in the RTU-RTU Frame Types table.
If no frame has been received, the function is returned with Rx_Len=0.
If the transmitting site is not defined in the Site table, the frame is received by the system and SrcSit = -1.
To answer a call initiated by another RTU, the answering function is carried out by using the following rungs:

619
6802979C10-BA
Appendix E: User Defined MDLC Communication

DstSit should receive the SrcSit from which the Origin frame has been sent. Tx_Len should be assigned the
value of 1 even if there is no data to transmit (used as an acknowledge).
The AnsFrm function is identical to the SndFrm function except that the error bit name is not included.
The answer frame is transmitted to the site that sent the frame of Origin type.

E.7
Sequential Frame RTU-to-RTU Communication
When using regular RTU-to-RTU communication, transmitted frames are not guaranteed to be received
in their original transmit order because of the unknown number of retries and acknowledgments. It is the
application’s responsibility to rearrange the data in its logical order. In some applications, such as file transfer,
it is important to receive frames in their original order. The system features a unique sequential frame RTU-to-
RTU communication (SndSeq and GetSeq functions) which does not use retries and acknowledgments. This
type of communication rearranges the frames at the receiving site in their original transmit order.
Every transmitted frame is assigned a sequential number, which is used at the receiving site to re-arrange the
frames by means of an internal buffer.
Following is an example of a site that transmits frames in Sequential Communication, to Site2 and Site3. A
counter is included in TxBuf,0 to allow the application at the receiving site to check the numbering of the
received frames.
The rungs at the transmitting site are as follows:

620
 6802979C10-BA
Appendix E: User Defined MDLC Communication

E.8
RTU Event/Burst Reporting
E.8.1
TX Event Table
Transmitting an event (including the data and time of occurrence) to a central (legacy central only) is
performed by the variables defined in the Tx Event table.
Figure 311: Tx Event Table

The Tx Event table includes the following variables:

● Event: This variable should be loaded with the name of the event to be transmitted by using the MOVE
operator. The event names are defined by the user in the Event Definitions tables. After calling the
TxEvnt/EvntSq function, check if this variable has been reset to 0. If it is reset, it means that the event has
been sent. If not, try to resend it after a period of time (by using a timer).
● EvIndx (Event Index): This index, attached to the event, provides additional information on the event. For
example, refer to a pump table of five rows defined for five pumps. If a failure (defined as PmpFal) has
occurred, then the EvIndx can be used to indicate the row number (pump) that has failed.
● ESite (Event Site ID): This variable should be loaded with the name of the central site to which the events
are to be transmitted. If the system includes several centrals, then the Site ID and Link ID of the RTU/FIU
to which each central is connected, should be defined in the Site table. If you wish to transmit only to
the active central (default central), use the Cntral name that appears in the first row of the Site table, and
check that DefC_Y=1 and not 0 (legacy central only).
● EPrtID (Event Port ID): The central is usually connected to one of the FIU ports (in some cases directly
to an RTU). Since the event is transmitted to the FIU address, the port should also be specified. This
variable should be loaded with one of the following values: Comp_1 or Comp_2 (refer to the MDLC Port

621
6802979C10-BA
Appendix E: User Defined MDLC Communication

ID’s table in the Constants Tables menu). If the ESite variable is defined as the default central (the first
line in the Site table), do not refer to the EPrtID variable (legacy central only).

E.8.2
Event Definitions 1 and Event Definitions 2 Tables
These two identical tables enable the user to fill in event definition names. The code values are automatically
inserted for each name, but you can manually change them. These event names are automatically
transferred to the central by the Central File and may be used in the central without the need to redefine
them.
Figure 312: Event Definitions Table

Use the MOVE operator to move an event name to the Event variable before calling the TxEvnt/EvntSq
function.
Do not use the first entry (index=0), since after calling the TxEvnt/EvntSq function, this value is reset by the
system to 0. This indicates that the event has been transferred to the transmission queue.

E.8.3
TxEvnt Function
To send an event, enter the values into the Tx Event table variables by the MOVE operator and call the
TxEvnt function. Refer to the following rungs as an example.

In this example, the I index indicates the number of the failed pump.
If all events are to be transmitted to the same central, then you should activate the first two rungs only once
since the ESite and EprtId variables will not change.
After calling the TxEvnt function, you should check that the Event variable has been reset, as indication that
the event has been taken by the system for transmission. If the Event variable has not been reset, it means
that the event has not been taken for transmission (all buffers are full). In this case, you should try resending
the event after a period of time (by using a timer).

622
 6802979C10-BA
Appendix E: User Defined MDLC Communication

The RTU sends the event through the communication network to the central and receives an
acknowledgment for the event from the central.
If the event has not been acknowledged after a specific number of retries, the system sets a bit (<error>,n;
defined by the user), to indicate that the event has not been acknowledged by the central.
If the events must be transmitted in order, use the EvntSq function instead of TxEvnt. EvntSq uses frame
sequence communication. No Ack is sent. Note: Unlike TxEvnt, the EvntSq function does not take any
parameters (see CALL in the fourth rung above.)

E.8.4
Data Burst Table
Transmitting data (a row of a table) from an RTU to the central (IP Gateway) is performed by the variables
defined in the Data Burst table.
Figure 313: Data Burst Table

The Data Burst table includes the following variables:

● BSite: The name of the central site (IP Gateway) to which the data is to be transmitted. If the system
includes several centrals, then the Site ID and Link ID should be defined in the Site table.
● BPrtID: If the central (legacy central only) is connected to one of the FIU ports (in some cases RTU).
Since the data is transmitted to the FIU address, the port should also be specified. This variable should
be assigned one of the following values: Comp_1 or Comp_2 (refer to the MDLC Port ID’s table in the
Constants Tables menu). If the BSite variable is defined as the default central (the first line in the Site
table), you should not refer to the BPrtID variable (legacy central only).
● BStat: After calling the Burst function, you should check the BStat variable. When the data burst is taken
for transmission into one of the system buffers then BStat=0. When there is no free buffer, the burst data
will not be transmitted and BStat=1. If the burst data is not transmitted, try to resend it after a period of
time (by using a timer).
In case of a burst transmission, the RTU can transmit data equivalent to one complete row of a table or
multiple rows of the same scan that have fit in one communication buffer. The table name and row number
must be specified in the process programming.

E.8.5
Burst Function
To transmit data from an RTU to the central specify the name of the central to which the data is to be
transmitted, and define the data to be transmitted (table symbol and row number). Refer to the following
rungs as an example.

Tbl is the data table symbol and I is the row number index.

623
6802979C10-BA
Appendix E: User Defined MDLC Communication

After calling the Burst function, check the Bstat variable to see if it equals ‘0’. If Bstat=0, that does not
necessarily mean that the burst transmission has been received by the central. To ensure that the burst
transmission has been received, check the ComFal bit in the Site table after a period of time. If ComFal=1,
it means that the central has not received the burst transmission. If ComFal=0, it means that the central has
received the burst transmission.
Note that the Burst function will only raise the ComFal bit if the Application Data-Ack from Central parameter
(in Site Configuration Advanced Parameters) is enabled.
The line of data to be transmitted (table, row #) is typically much smaller than the size of a frame (160 bytes).
Therefore the system has the ability to send multibursts, that is, several lines of data in one burst, to a given
unit. The actual transmission will take place either:
1. when the frame is full,
2. when the scan of the ladder ends,
3. when the scan time is so long that it exceeds the timeout for sending (as defined by the system.)
The IP Gateway can handle single or multibursts without any special notification.
The BrstSq function, like the Burst function, can send single or multibursts, though it differs from Burst in that
it does not send Ack and cannot raise the ComFal bit.
The rung at the receiving site is as follows:

E.9
Example of RTU-to-RTU Communication
The following example is an application of RTU-to-RTU communication, designed to evaluate the
communication between two sites, named Site A and Site B. Database definitions and rung processes are
included.
Site A initiates, at definite intervals, a value transmission to Site B. Site B, after receiving the value, is
supposed to transmit back the same value to Site A.
Each transmission, initiated by Site A, is conditioned on the success of the previous transmission cycle. Any
failure in the communication should stop the system, and show the failure cause. Site A increments the
transmitted value when starting a new cycle.
It is possible to get a printout of the number of transmissions and receptions that Site A has performed at any
time by pressing the PRINT push-button.
The RESET push-button allows the restarting of the application (as well as when the system has stopped).

E.9.1
Site A Database
E.9.1.1
Internal Values
The following value variables are used in the process programming:
● TxVal – the transmitted value
● RxVal – the received value
● TxCntr – counts the number of transmissions.
● RxCntr – counts the number of receptions.

624
 6802979C10-BA
Appendix E: User Defined MDLC Communication

● BsyTry – counts the number of retries if the value is not taken for transmission (no free buffers in the
transmit queue)
These variables are defined in one of the User tables, named Internal Variables table (“Integer Value” data
type).
Figure 314: Internal Variable Table

E.9.1.2
Communication Constants
Three constants, #0, ONE, and N are also used in the process programming. They are defined in one of the
Constant tables, named Comm Constants table.
Figure 315: Comm Constants Table

E.9.1.3
Communication Timers
Two Seconds timers are used in the process programming, as follows:
● TryDly – timer of 1:00 second used in case the value has not been taken for transmission.
● Cycle – timer of 30:00 seconds, a complete transmission cycle
These timers are defined in one of the User tables, named Comm Timers.
Figure 316: Comm Timers Table

625
6802979C10-BA
Appendix E: User Defined MDLC Communication

E.9.1.4
Discrete Inputs
Two discrete inputs, RESET and PRINT, are used in the process programming. They are defined in one of
the User tables, named Buttons table.
Figure 317: Buttons Table

E.9.1.5
Discrete Outputs
The following discrete outputs (LEDs), defined in one of the User tables, named LEDs table, are used in the
process programming:
● TxOn – transmit indicator
● BsyFal – indicates that the value has not been taken for transmission.
● TxFail – indicates that acknowledgment has not been received.

E.9.1.6
Sites
Site B (the name of the site that Site A communicates with) should be defined in the Site table (one of the
System tables).

E.9.2
Site B Database
E.9.3
Site A User Rungs
The rungs are as follows:

626
 6802979C10-BA
Appendix E: User Defined MDLC Communication

The Prepar rung checks if a new cycle is to be started according to the Off Delay timer of 30:00 seconds. The
transmission of another value is disabled by this timer during the transmission cycle. The rung also verifies
that no failures have occurred by comparing TxVal and RxVal. If they are not equal, it means that a failure has
occurred.
If a new value is to be transmitted, then TxVal is advanced by the CTU operator and its value is assigned
to TxBuf,0 for transmission. Site_B is moved to the DstSit variable to specify the destination site. Tx_Len
receives the value ONE (one value is to be transmitted), and BsyTry receives the value of N, which indicates
the number of retries in case the value is not taken for transmission.

The Trnsmt rung calls the SndFrm function until BsyTry is 0 (the value has been transmitted). The TxOn
LED is lit by the relay on element. The rung checks that the TryDly is not on (delay between retries). The
transmission is then enabled by calling the SndFrm function. TxFail will be set to ‘1’ in case of failure. BsyTry
is decreased (the value has been transmitted once).
If the value has been taken for transmission (Tx_Len=0), BsyTry is reset to 0 (to prevent calling the SndFrm
function) and TxCntr (counts the number of transmissions) is advanced.
If the value has not been transmitted (Tx_Len≠0), the Off Delay timer TryDly is activated.
If all retries have been performed (BsyTry=0) and the value has not been transmitted (Tx_Len≠0), the BsyFal
LED is lit and Tx_Len is reset to 0.

627
6802979C10-BA
Appendix E: User Defined MDLC Communication

The reception is carried out by calling the RcvFrm function. If a value has been received, Rx_Len is not 0, the
SrcSit (transmitting site) is Site_B, and the received frame is of Answer type (FrmTyp=Answer), then RxBuf,0
(the received value) is moved into the RxVal variable. Rx_Cntr is advanced.

The buttons are scanned by the SCAN operator. If the RESET button is pressed, all variables (TxVal, RxVal,
TxCntr, RxCntr, BsyTry, Tx_Len, and Rx_Len) are reset to 0. If the PRINT button is pressed, the message in
the window will be sent to the screen. Note that since there are no codes in the window, the message will be
displayed in scroll mode.

E.9.3.1
Internal Values
The BsyTry value variable is used in the process programming. This variable counts the number of retries in
case the value is not taken for transmission. It is defined in one of the User tables, named Internal Variables
table.
Figure 318: Internal Variables Table

628
 6802979C10-BA
Appendix E: User Defined MDLC Communication

E.9.3.2
Communication Constants
Three constants, #0, ONE, and N are also used in the process programming. They are defined in one of the
Constant tables, named Comm Constants table.
Figure 319: Comm Constants Table

E.9.3.3
Communication Timers
A Seconds timer, TryDly, is used in the process programming. This timer is of 1:00 second and is used in
case the value has not been taken for transmission. It is defined in one of the User tables, named Comm
Timers table.
Figure 320: Comm Timers Table

E.9.3.4
Discrete Outputs
The following discrete outputs (LEDs) are used in the process programming:
● TxOn – transmit indicator
● BsyFal – indicates that the value has not been taken for transmission.
These discrete outputs are defined in one of the User tables, named LEDs table.
Figure 321: LEDs Table

629
6802979C10-BA
Appendix E: User Defined MDLC Communication

E.9.3.5
Sites
Site A should be defined in the Site table (one of the System tables).

E.9.4
Site B User Rungs
The rungs are as follows:

The first rung checks that the unit is not transmitting (BsyTry=0) before calling the RcvFrm function. Then, if
Rx_Len≠0 (a frame has been received) and the received frame is of Origin type, then the received value (in
RxBuf,0) is assigned to TxBuf,0 (for transmission, Site B transmits back to Site A the same value). Tx_Len is
set to ONE and BsyTry is set to N (10).

The Trnsmt rung transmits the value until BsyTry is 0. The TxOn LED is lit by the relay on element. The rung
checks that TryDly is not on (delay between retries). The transmission is then enabled by calling the AnsFrm
function. BsyTry is decreased (the value has been transmitted once).
If the value has been transmitted (Tx_Len=0), BsyTry is reset to 0.
If the value has not been transmitted (Tx_Len≠0), the Off Delay timer TryDly is activated. When the timer is
on, the value is not transmitted (because of the Normally Closed element applied on TryDly).
If all retries have been performed (BsyTry=0) and the value has not been transmitted (Tx_Len≠0), the BsyFal
LED is lit and Tx_Len is reset to 0.

630
 6802979C10-BA
Appendix F: MDLC Communication Protocol

Appendix F

MDLC Communication Protocol

The MDLC communication protocol is based on the OSI (Open Systems Interconnection) model published
by ISO. The protocol comprises the seven recommended layers adapted for SCADA, in which every RTU is
simultaneously a distributed control unit and a communication node serving itself as well as other units.
Information is transmitted in the form of variable-length digital words. Advanced security techniques are
employed to provide protection against false messages.
The protocol is efficient for transferring:
● small quantities of information, such as measurements and discrete statuses
● large quantities of information, such as downloading software applications, including database, process,
etc.

The following sections describe the seven layers of the protocol, shown in the figure above:
● Physical layer
● Link layer
● Network layer
● Transportation layer
● Session layer
● Presentation layer
● Application layer

631
6802979C10-BA
Appendix F: MDLC Communication Protocol

F.1
Physical Layer
The physical layer comprises the various communication ports and their associated software.
The software contains all the specific handling required by the communication ports and provides an identical
interface to the link layer. In this way, it is possible to define a standard entity for the link layer.
The software is flexible and adapts itself to the number of ports and their various types as defined by the
user. The possibility of defining a large number of ports of various types does not impair software efficiency.
The physical ports may also be configured to provide hard-copy printout to a printer.

F.2
Link Layer
The function of the link layer is to ensure proper communication over a single communication channel.
The information is stored in variable-length frames where the link layer protocol contains the following fields
(for a DATA frame):
● The address of the unit to which the DATA is transmitted
● The address of the transmitting unit
● The number of the frame
● CRC for error detection
Dual addressing is used to allow RTU-to-RTU transmission without central intervention, transmission to
several centrals, or a hierarchical system where some of the RTUs serve as subcentrals for the lower
hierarchies.
During reception, the address is identified by hardware (and not by software) at the physical level. This is to
save software time on checking words that are not intended for that specific RTU. This preliminary screening
enables reception of at least four different addresses per RTU: single address to access a specific RTU,
broadcast address to access a group of RTUs, and two additional addresses enabling various communication
operations.
A link entity associated with a channel may receive several types of information: information that is intended
for that specific RTU and information passing through it and is designated to other RTUs. The link entity
transmits an acknowledgment (ACK) to each RTU according to the DATA received from it. The ACK word is
separated from the DATA word, since the RTU receiving the DATA is not necessarily the same RTU to which
the ACK is addressed.
The ACK word enables the receiving site to identify the missing frames and retransmit only those frames,
thus saving air time by not repeating all the information transmitted. The CRC is 32 bits or 16 bits per CCITT
definition.
The frame synchronization (FLAG), at the beginning and at the end of each word, is transmitted in different
ways for different physical ports.

F.3
Network Layer
A system is defined as a network whenever it uses more than one communication medium, such as wireline
and/or various radios, as well as Store & Forward repeaters, all on a single frequency. The communications in
the network occur among nodes, which physically may be RTUs, centrals, or repeaters.
The network layer and its protocol are responsible for routing packets in the network via the various nodes to
enable communication between any two sites in the network.

632
 6802979C10-BA
Appendix F: MDLC Communication Protocol

It is possible to access any application anywhere in the system from any port in the system. For example,
the RS-232 ports of the various RTUs, for purposes of definition, monitoring, modification, diagnostics, error
logging, etc.

F.4
Transportation Layer
The transportation layer ensures END-to-END completeness of the information transmission (between the
RTU that has transmitted the message and the one that should receive it). This layer transfers the DATA
in an orderly fashion to the session layer above it. The protocol of this layer assigns sequential numbers to
the packets (independent of the numbers assigned by the link layer). The protocol transmits an ACK word to
indicate that the DATA is complete and all packets are transferred in the appropriate order to the layer above.
The transport layer performs multiplexing, thus enabling several session entities (logical channels) to operate
via one physical port or several physical ports. It is possible to define any number of logical channels,
regardless of the number of physical channels defined.

F.5
Session Layer
The session layer enables the definition of any number of entities (instances), which are capable of
conducting a session with a parallel entity in another RTU, a central, or a subcentral.
These entities and their protocol simultaneously conduct several sessions between any two sites, that
is, to simultaneously run several applications such as data transfer, diagnostics, monitoring, etc., without
interference between the applications. The session handling includes the following:
● Start session
● Synchronization of message direction
● End session
● Abort session
● Resynchronize session
The session layer also allows transfer of short one-frame messages from one site to the parallel application
at another site. This occurs without the need to start a session.

F.6
Presentation Layer
This layer handles the presentation of the DATA received from the various applications within the various
packets.
It performs the following functions:
● Checks that the information transferred to the application is complete.
● Compresses the information
● Encrypts the information

633
6802979C10-BA
Appendix F: MDLC Communication Protocol

● Checks authentication

F.7
Application Layer
This layer contains all the communication applications required for maintaining a SCADA system, as detailed
below:
● Application enabling bidirectional data transfer upon request from the databases of the sites
● Software for downloading configuration to the sites:
○ I/O modules definition
○ Communication ports definition
● Software for downloading and monitoring application software (defined by the user in the ladder diagram
language) to the sites, including:
○ Definition of the data structure
○ Object code of processes
○ Real-time symbolic monitoring of database and processes
● Application for transmitting events and short messages
● Application for broadcasts
● Application for remote diagnostics of the hardware and the software
● Application for the retrieval of error messages stored in the error logs of the sites.
● Application for the calibration of A/D and D/A modules
● Application for communication analysis and accumulation of statistics
● Application for downloading various blocks (for example; site configuration, ladder applications, network
configuration, phone book, “C” blocks, third-party drivers, x.25 conversion table, IP conversion table, etc.

634
 6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

Appendix G

MC-EDGE/ACE1000 MODBUS
Configuration
MC-EDGE®/ACE1000 supports MODBUS Client (Master) and MODBUS Server (Slave) protocols. MODBUS
protocol is based on Client (Master) “polling” Servers (Slaves).
MODBUS Client (Master)
Usually used on MC-EDGE/ACE1000 RTU for communication with wireline external PLCs/devices.
MODBUS Server (Slave)
Usually used on MC-EDGE/ACE1100 FEP for communication with wireline external SCADA center.

G.1
MC-EDGE/ACE1000 MODBUS Client (Master)
MC-EDGE® as MODBUS Client (Master) can work with up to seven MODBUS Servers (Slaves).
MC-EDGE as MODBUS Client (Master) can work with each MODBUS Server (Slave) having up to 24 DIs,
24 Coils, 24 Input Registers, 24 Holding Registers. All MODBUS Servers (Slaves) connected with the same
MC-EDGE must have the same data models address.
Each Server (Slave) must have a unique address – Server (Slave) ID.
Communication is always initiated by Client (Master).
Communication may be handled through TCP/IP (Eth) or Serial (RS232 or RS485).
Server (Slave) nodes transmit data only when receiving a request from Client (Master).
Server (Slave) nodes never communicate with each other.
MODBUS Client (Master) initiates only one MODBUS transaction at a time.
Figure 322: MODBUS Client (Master) – MODBUS Server (Slave)

MODBUS Client (Master) MODBUS Server (Slave)

RTU PLC

Standard MODBUS Data Models/Types Handled by MODBUS Client (Master)

Table 217: Standard MODBUS Data Models/Types Handled by MODBUS Client (Master)

MODBUS Data Type Command MODBUS Function RTU Equivalent

Code
Logic Coils Read 1 Discrete Output
Discrete Inputs Read 2 Discrete Input
Holding Registers Read 3 Value Input

635
6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

MODBUS Data Type Command MODBUS Function RTU Equivalent

Code
Input Registers Read 4 Value Input
Logic Coils Write (single coil) 5 Discrete Output
Holding Registers Write (single register) 6 Value Output
Logic Coils Write 15 Discrete Output
Holding Registers Write 16 Value Output

MC-EDGE MODBUS Client (Master) Options

Figure 323: MODBUS Client (Master) Configuration Editor

STS allows you to define MC-EDGE MODBUS Client (Master) with the following options:

Table 218: MC-EDGE MODBUS Client (Master) Options

Parameter Description
MODBUS Client (Master) General

636
 6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

Parameter Description
Interface ● IP – communication between the Client (Master) and Server (Slave) handled
through IP (Eth)
● RS232 – communication between the Client (Master) and Server (Slave) han-
dled through Serial RS232
● RS485 – communication between the Client (Master) and Server (Slave) han-
dled through Serial RS485

Slave response Defines the duration between retries specified in the Max failure before declar-
timeout ing comm fail attempts field.
Polling interval Defines the interval time for the Client (Master) to poll all Servers (Slaves).
time Setting this parameter to 0 disables automatic polling and sets it to manual, which
is handled by using C or IEC APIs to manually poll all Servers (Slaves).

Slave response Defines the timeout interval between two consecutive bytes of the same message.
bytes timeout
Max failure before Defines the number of retries the system should attempt before a Server (Slave)
declaring comm failure is declared.
fail attempts
Byte order Allows you to select ABCD or DCBA, according to PLC behavior.
Add New Defines the amount of Servers (Slaves) to work with: 1 to 7 Servers (Slaves).
Remove Removes Servers (Slaves).
Server (Slave) contents – General tab
MODBUS Slave ID Defines the identifying number of the Server (Slave), which is between 1 and 250,
and must be unique for each Server (Slave). STS automatically increments each
new Server (Slave) definition. Users can change the default number.
Slave Active Defines whether the Server (Slave) is active or not.
Slave Comm fail Defines whether MODBUS Client (Master) will MDLC burst to center upon com-
burst munication failure with that Server (Slave).
IP Address When MODBUS Client (Master) – Server (Slave) communication is handled
through IP, this parameter defines the Server (Slave) IPv4 address, which must be
unique IP for each Server (Slave).
TCP Port When MODBUS Client (Master) – Server (Slave) communication is handled
through IP, this parameter defines the IP port. The default port is 502.
Server (Slave) contents – Discrete Inputs tab
Add Amount of DIs (1 to 24).
Remove Removes the defined DI.
Persistence Defines the duration before a burst.
Notify On (bursts ● No Notifications – no bursts.
are from MC-EDGE
to FEP): ● Notify on rising and falling edge – bursts when any change between ON
and OFF states occurs.
● Notify on falling edge – bursts when a change from ON to OFF occurs.
● Notify on rising on rising edge – bursts when a change from OFF to ON
occurs.

637
6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

Parameter Description
Server (Slave) contents – Coils tab
Add Amount of Coils (1 to 24).
Remove Removes the defined Coil.
Notifications Enables/disables notifications.
Server (Slave) contents – Input Registers tab
Options to define 16 bit integer, 32 bit integer, 32 bit floating.
Add Amount of Input registers (1 to 24)
Remove Removes the defined Input Register
Notify On (bursts ● No Notifications – no bursts.
are from MC-EDGE
to FEP): ● Always – burst on any change
● Notify on delta change – when the value changes by the delta, the RTU
bursts to FEP.
● Notify on range change – when the range changes by the delta, the RTU
bursts to FEP.
● Notify on delta and range change – when the value changes by the delta or
range, the RTU bursts to FEP.
● Persistence – defines the duration for the change to persist before a burst.
● Low & High – for Low and High values with persistence equal to 0, when the
value reaches the high or low limit for the first time, the RTU bursts to FEP. If
the value returns to the range (over the Low value and below the High value)
and reaches the limit again, a burst or event takes place again. For Low and
High values with persistence other than 0, when the value reaches the High or
Low limit for the first time and remains stable for the Persistence duration, the
RTU bursts to FEP. If the value returns to the range (over the Low value and
below the High value) within the persistence duration, no burst takes place
and the count starts again.

Server (Slave) contents – Holding Registers tab

Options to define 16 bit integer, 32 bit integer, 32 bit floating.
Add Amount of Input registers (1 to 24).
Remove Removes the defined Input Register.
Notification ena- N/A
ble/disable (bursts
are from MC-EDGE
to FEP)
Server (Slave) contents – Common MODBUS Slave Address tab
Users can define the start address of each of the following MODBUS data models:
● Discrete Input start address
● Coils start address
● Input Registers start address (int 16 bit)
● Input Registers start address (int 32 bit)

638
 6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

Parameter Description

● Input Registers start address (float 32 bit)

● Holding Registers start address (int 16 bit)
● Holding Registers start address (int 32 bit)
● Holding Registers start address (float 32 bit)

NOTE:
The definition of each data model address must correspond to the specific connected MODBUS Server
(Slave) mapping.
All MODBUS Servers (Slaves) connected with the same MC-EDGE must have the same data models
address.
After all data models addresses are defined, the MC-EDGE MODBUS Client (Master) includes single
table mapping (address: 0–65535) with all the defined data models.

G.2
MC-EDGE/ACE1000 MODBUS Server (Slave)
Communication between MODBUS Client (Master) (for example, SCADA center) and MODBUS Server
(Slave) (for example, MC-EDGE®/ACE1100 acting as FEP) is handled through TCP/IP (Eth) or Serial
(RS232, RS485). Communication occurs by using the unique Server (Slave) ID address (1 to 255).

MODBUS Client (Master) MODBUS Server (Slave)

SCADA Center FEP

STS allows you to define the TCP/IP port (default: 502) or the Serial baud rate.
On a MODBUS Server (Slave) configuration, the MC-EDGE provides an external MODBUS Client (Master)
ability to handle request-reply/polling according to the following MC-EDGE MODBUS Server (Slave) data
model table:

Table 219: MC-EDGE MODBUS Server (Slave) Data Model

Data (Ob- Type Address Notes

ject) Type
Coils DO MC-EDGE: 0–40* *The last address depends on the num-
ber of connected Expansion I/O mod-
ACE1000: 0–16*
ules and their type.
The following table1 describes the max-
imum number of DOs available for MC-
EDGE.
Example: the MODBUS address of
DO-1 in Exp2 is: 9
Example: the MODBUS address of
DO-8 in Exp3 is: 24

639
6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

Data (Ob- Type Address Notes

ject) Type
1 Maximum number of DOs available for MC-EDGE:

IO module IO Index MODBUS Address

Main 1 0
Exp 1 1–8 1–8
Exp 2 1–8 9–16
Exp 3 1–8 17–24
Exp 4 1–8 25–32
Exp 5 1–8 33–40

Coils POLL_COM 1000–1999 Only for ACE1100

M STATUS MC-EDGE – N/A

Coils USER BITS 2000–3999 MC-EDGE User Bit Table#6

TABLE 8 Columns x 249 rows including 2000
values of bits

Discrete DI MC-EDGE: 0–62* *The last address depends on the num-

Registers ber of connected Expansion I/O mod-
ACE1000: 0–26*
ules and their type.
The following table2 describes the max-
imum number of DIs available for MC-
EDGE.
Example: the MODBUS address of
D1-1 in Exp2 is: 15
Example: the MODBUS address of
DI-12 in Exp3 is: 38
2 Maximum number of DIs available for MC-EDGE:

IO module IO Index IO Index MODBUS Address

Main 1–3 0–2
Exp 1 1–12 3–14
Exp 2 1–12 15–26
Exp 3 1–12 27–38
Exp 4 1–12 39–50
Exp 5 1–12 51–62

Discrete DI BI MC-EDGE: 1000–1040* DO Back Indication

Registers ACE1000: 1000–1016* *The last address depends on the num-
ber of connected Expansion I/O mod-
ules and their type.

640
 6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

Data (Ob- Type Address Notes

ject) Type
The following table3 describes the max-
imum number of DOs Back Indication
available for MC-EDGE.
3 Maximum number of DOs Back Indication available for MC-EDGE:

IO Module IO Index MODBUS Address

Main 1 1000
Exp 1 1–8 1001–1008
Exp 2 1–8 1009–1016
Exp 3 1–8 1017–1024
Exp 4 1–8 1025–1032
Exp 5 1–8 1033–1040

Input Regis- AI MC-EDGE: 0–37* *The last address depends on the num-
ters ber of connected Expansion I/O mod-
ACE1000: 0–15*
ules and their type.
The following table4 describes the max-
imum number of AIs available for MC-
EDGE.
Example: the MODBUS address of
A1-1 in Exp2 is: 8
Example: the MODBUS address of AI-8
in Exp3 is: 23
4 Maximum number of AIs available for MC-EDGE:

IO Module IO Index MODBUS Address

Main N/A N/A
Exp 1 1–8 0–7
Exp 2 1–8 8–15
Exp 3 1–8 16–23
Exp 4 1–8 24–29
Exp 5 1–8 30–37

Input Regis- SYSTEM MC-EDGE: 1000–1015* *The System Table last address de-
ters TABLE pends on whether it is MC-EDGE or
ACE1000: 1000–1008*
ACE1000.
The following table5 describes the
MODBUS addresses corresponding to
the System Table values.
5 MODBUS addresses corresponding to the System Table values:

641
6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

Data (Ob- Type Address Notes

ject) Type

Value MODBUS Address

IS_ERROR_EXISTS 1000
INPUT_VOLTAGE 1001
TEMPERATURE 1002
IS_PB_ON 1003
IS_CONF_CHANGED 1004
IO_MAIN_BOARD_STATUS 1005
IO_EXP_1_STATUS 1006
IO_EXP_2_STATUS 1007
PIGGYBACK_TYPE 1008
N/A 1009
APX_EXISTS 1010
LTE_EXIST 1011
LORA_EXIST 1012
IO_EXP_3_STATUS 1013
IO_EXP_4_STATUS 1014
IO_EXP_5_STATUS 1015

Input Regis- COMM 2000–2999 Only for ACE1100

ters STATUS MC-EDGE: N/A

Holding Reg- AO MC-EDGE: 0–11* *The last address depends on the num-
isters ber of connected Expansion I/O mod-
ACE1000: 0–5*
ules and their type.
The following table6 describes the max-
imum number of AOs available for MC-
EDGE.
Example: the MODBUS address of
AO-1 in Exp2 is: 4
Example: the MODBUS address of
AO-2 in Exp3 is: 7
6 Maximum number of AOs available for MC-EDGE:

IO module IO Index MODBUS Address

Main 1 0–1
Exp 1 1–2 2–3
Exp 2 1–2 4–5
Exp 3 1–2 6–7

642
 6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

Data (Ob- Type Address Notes

ject) Type

IO module IO Index MODBUS Address

Exp 4 1–2 8–9
Exp 5 1–2 10–11

Holding Reg- USER INT 1000–2999 MC-EDGE User INT Table#7, 8 Col-
isters TABLE umns x 249 rows including 2000 values
of Integers

Holding Reg- USER INT 3000–4999 MC-EDGE User INT Table#9, 8 Col-
isters TABLE umns x 249 rows including 2000 values
of Integers

Holding Reg- USER INT 5000–6999 MC-EDGE User INT Table#10, 8 Col-
isters TABLE umns x 249 rows including 2000 values
of Integers

Holding Reg- USER 7000–8999 MC-EDGE User FLOAT Table#8, 8 Col-

isters FLOAT TA- umns x 249 rows including 1000 values
BLE of floating. Each float value is spread
over 2 addresses.

Holding Reg- USER 9000–12999 MC-EDGE User LONG Table#11, 8 Col-

isters LONG TA- umns x 249 rows including 2000 values
BLE of long. Each value is spread over 2
addresses.

Table 220: System Table Parameters

Name Description
IS_ERROR_EXISTS 0 – No (no error exists)
1 –Yes ()

INPUT_VOLTAGE The last reading of the input power level in milli-

volts
TEMPERATURE The last measured temperature of the board in
Celsius degrees
IS_PB_ON 0 – No (push button not pushed)
1 – Yes (push button pushed)

IS_CONF_CHANGED 0 – No (configuration not changed)

1 – Yes (configuration changed)

IO_MAIN_BOARD_STATUS 0 – OK
1 – Communication failure (between CPU and ex-
pansion module)
2 – Configuration mismatch (actual expansion is
different that the expansion specified in the config-
uration)

643
6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

Name Description
4 – General error
255 – Module is not configured

IO_EXP_1_STATUS or 0 – OK
IO_EXP_2_STATUS or 1 – Communication failure (between CPU and ex-
IO_EXP_3_STATUS or pansion module)
IO_EXP_4_STATUS or
IO_EXP_5_STATUS

G.3
SCADA Polling and Comm Status of ACE1000
RTUs
The SCADA can poll ACE1000 RTUs for updated data by writing a "1" to the corresponding register in
the FEP. See Table 221: ACE1100 FEP Polling Register Locations on page 644 for the polling register
locations in the FEP. This can be useful to retrieve data when alerts are disabled in an RTU, or to restore
communication between the FEP and an RTU if it is has failed.

Table 221: ACE1100 FEP Polling Register Locations

Polling Values (FEP only) Register Location

SCADA Polling of RTUs via FEP – Set register to 1 Register 1001 = MODBUS address 2 (first RTU)
to poll the specific RTU. Register 1099 = MODBUS address 100 (up to 99
RTUs)

NOTE: Currently, an ACE1000 system can include up to 250 RTUs. In general, the SCADA will poll a
smaller number of RTUs (for example, 10) at one time.
In an ACE1000 system, when the SCADA polls the FEP for data on existing RTUs, the Comm. Status is
returned in a MODBUS frame. The value is a bit mask of three bits. The value can be one of:
● 7 – RTU is connected and synced with the FEP
● 0 – RTU has no communication with the FEP
● 32767 (0x7FFF) – nonexistent MODBUS address in the FEP
● Otherwise – in the process of establishing communication with the FEP
The SCADA can also retrieve the Comm Status of individual RTUs from the FEP registers. See Table 222:
ACE1100 FEP Comm Status Register Locations on page 644 for the RTU Comm Status register locations in
the FEP.

Table 222: ACE1100 FEP Comm Status Register Locations

Comm Status Values (FEP only) Register Location

Retrieve RTU Comm Status from the FEP Register 2001 = MODBUS address 2 (first RTU)
Register 3000 = MODBUS address 1001 (up to
1000 RTUs)

644
 6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

G.4
Port Configuration for ACE1000/MC-EDGE
MODBUS
G.4.1
ACE1000/MC-EDGE Port Configuration in a Mixed
System
In a mixed system, the RTU port is configured using the MC-IoT STS.

G.4.2
ACE1000/MC-EDGE as MODBUS Server (Slave)
The following ACE1000 ports can be configured as MODBUS Server (Slave):
● Serial RS232 (SI1), Plug-in (PI1/PI2 – ACE1000 only)
● Serial RS485 (SI1)
● LAN (ETH1) (MODBUS over TCP/IP)
NOTE: Only one ACE1000/MC-EDGE port can be configured as MODBUS Server (Slave) at any time.

On the following figures, the ACE1000 RTU serial RS232/RS485 ports are configured as MODBUS Server
(Slave) (Connection type set to Modbus Slave).
Figure 324: SI and PI Ports Configured as MODBUS Server (Slave)

On the following figure, the ACE1000 RTU LAN port is configured as MODBUS Server (Slave) (Connection
type set to Ethernet, Modbus Server (Slave) Protocols selected). In addition, the MODBUS Address is set
on the ETH1 Advanced Configuration → Modbus Server (Slave) tab).

645
6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

Figure 325: ETH1 Port with MODBUS Protocol Support Enabled

Figure 326: MODBUS Server (Slave) Advanced Port Parameters

G.4.3
MC-EDGE/ACE1000 as MODBUS Client (Master)
G.4.3.1
MC-EDGE as MODBUS Client (Master)
MC-EDGE can be configured to act as MODBUS Client (Master) through STS Serial or Eth ports. Only a
single MODBUS Client (Master) port at a time can be deployed at a single MC-EDGE.
The following figures show examples of port selection:
Figure 327: SI1 Port Configured as MODBUS Client (Master)

Figure 328: ETH1 Port Configured as MODBUS Client (Master)

Figure 329: SI2 Port Configured as MODBUS Client (Master)

646
 6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

G.4.3.2
ACE1000 as MODBUS Client (Master)
On the following figure, the ACE1000 RTU serial RS232/RS485 ports are configured as MODBUS Client
(Master) (Connection type set to User port).
Figure 330: SI and PI Ports Configured as User Port

On the following figure, the standard ACE1000 RTU Ethernet port configuration (Static LAN or DHCP Client)
is used for MODBUS Client (Master) (Connection type set to LAN).
Figure 331: Standard ACE1000 RTU Ethernet Port Configuration

G.4.4
ACE1100 FEP Port Configuration in an ACE1000 System
In an ACE1000 system, the FEP port is configured using the web browser-based Easy Configurator. Drag the
interface type from the Add Communication General list to the port.
In the following figure, the ACE1100 FEP serial RS232 port is configured as connected (as a MODBUS
Server (Slave)) to a SCADA center.

647
6802979C10-BA
Appendix G: MC-EDGE/ACE1000 MODBUS Configuration

Figure 332: ACE1100 as MODBUS Server (Slave) Connected to SCADA Center

648
 6802979C10-BA
Appendix H: Key Variable Loader 4000

Appendix H

Key Variable Loader 4000

This section of manual provides information about manual Key setting. For additional information, see the
KVL4000 User Guide.
The KVL 4000 Key Variable Loader is a portable, handheld, rugged device whose most basic function is to
transfer encryption keys to a target device.
Encryption keys can be entered manually by the KVL user, auto-generated by the KVL, or obtained from
or shared with another KVL. Keys can be transferred to secure mobile and portable radios, infrastructure
devices, and system test equipment.

H.1
Setting Up Key Variable Loader 4000
Prerequisites: Radio must have the option QA01767 that supports “P25 Link layer authentication”. Make
sure that the APX port is enabled by downloading the appropriate site configuration.
Figure 333: APX Port Configuration

Procedure:
1. Power on KVL and enter the application.
a. Connect OTG cable between KVL4000 and RTU.

649
6802979C10-BA
Appendix H: Key Variable Loader 4000

Figure 334: Connecting the OTG Cable

b. Power on KVL4000.
2. Enter CPS mode in MC-EDGE®.
a. On the Setup tab, select Communication Setup and enter the RTU IP. Click Apply.
Figure 335: STS – Communication Setup Dialog

b. Click More.
c. Connect the OTG cable from the MC-EDGE to PC.
d. In the extended Communication Setup window, click the MC-EDGE APX CPS Mode button.
e. In the CPS Mode window, click Enable CPS Mode.
Wait until indication status in the Current CPS status field changes to Enabled.
f. Select the Key Variable Loader application in the MC55x.
g. Tap OK to proceed.
h. Tap Define & load key and select Manually entered.
3. After the process is complete, provide the ASTRO Network Manager with the key and the radio ID.

650
 6802979C10-BA
Appendix I: MC-EDGE LoRa

Appendix I

MC-EDGE LoRa
I.1
Enabling LoRaWAN
MC-EDGE LoRaWAN® requires enabling through STS before you can work with it.

Process:
1. In STS, select MC-EDGE → ports → LoRa → LoRaWAN.
2. Perform Customizing the Site Configuration on page 109 on the MC-EDGE Port LoRa section.
For a description of LoRa port parameters, see LoRa Port Configurations on page 449.
3. Download the changes.

I.2
LoRaWAN Configuration
Enabling LoRaWAN® allows users to configure the LoRaWAN server through the LoRaWAN WebUI or
external integration APIs.
To facilitate this process, the MC-EDGE® has predefined mandatory sections such as Network Servers,
Service Profile, Gateways, and Application. These are advanced sections that rarely need changing.
Other sections allow users to define and add end devices.
MC-EDGE® also has two predefined users with different permissions:
● admin@mciot.com – can define all sections.
● mciotlogin@mciot.com – can define, add, and monitor devices.

I.2.1
Configuring LoRaWAN Devices
Prerequisites:
Ensure a Windows PC (it may be the STS PC) is connected to MC-EDGE through IP.
The IP connectivity may be through any of the MC-EDGE enabled IP interfaces (OTG, ETH, LTE).

Process:
1. On the connected windows PC, launch a web browser.
2. In the web browser address bar, type: https://<MC-EDGE IP address>:8080
Step example: On a connectivity to MC-EDGE USB OTG, type: https://192.168.9.9:8080
3. When the MC-EDGE LoRaWAN® WebUI appears, log on as a user or admin by entering the relevant
password.
NOTE: Motorola Solutions provides a predefined LoRaWAN network, and all users required are
to add, configure, remove, and monitor their own LoRa end devices. These activities can be
handled by user login and do not require admin login. Motorola Solutions recommends that
usual/most entries be handled as users and not as admin.

651
6802979C10-BA
Appendix I: MC-EDGE LoRa

4. To create or update LoRa end devices, define a Device Profile in the WebUI main window.
See Device Profiles.
5. After the Device Profile is defined, create or update the LoRa end device in the WebUI main window.
See Devices.
After all LoRa end devices are defined, the LoRaWAN network is ready to work.

6. Log out from the LoRaWAN WebUI.

I.3
Considerations for Sending and Receiving Device
Data
All real-time LoRa end device transmissions and receptions can be handled by MQTT protocol. The MC-
EDGE® includes MQTT Broker, which allows MQTT clients to publish messages to LoRa end devices and
subscribe to messages from LoRa end devices.

Local MQTT Applications

The C_Programing SDK includes the https://mosquitto.org/ third-party open source, which provides a
C library for implementing MQTT clients. For detailed information on the Mosquito API, see https://
mosquitto.org/api/files/mosquitto-h.html.
The C application client can publish and subscribe messages to MQTT on a local host (address
127.0.0.1), port 1883. This option is blocked for external MQTT clients.
For more information on writing C applications with LoRa services, see the 'C' Programming SDK and
Migration Guide.
NOTE:
Messages are in .json format (Key:Value). The data payload is under the key data. Use the
C_Programing SDK c-json lib to parse .json messages.
Data payload is also encoded in base64. Decode the payload before parsing. The data parsing may be
different for every end device according to the provider.
See the ctkmosquittoclient.c LoRa example for this process.

External MQTT Applications

External MQTT clients can connect to the MQTT broker through all configured interfaces. The listener is on
port 8883 and it is protected with a user name, password, and TLS.
● The user name and password are set through STS LoRa advanced parameters.
● TLS files (root certificate, broker certificate, broker key) are loaded through the STS Add-On Manager.
Default TLS files are already loaded to the MC-EDGE, and the matching root certificate is provided
together with all MC-EDGE deliverables.
NOTE: It is highly recommended for the user to replace the default TLS certificates with their own newly
created certificates.

Bridging the Remote MQTT Broker

The MC-EDGE MQTT broker can be bridged to an external broker.
Users can define the remote broker connection parameters such as address, port, user name, password, and
TLS as well as define which interface to bind.

652
 6802979C10-BA
Appendix I: MC-EDGE LoRa

See LoRaWAN Advanced Parameters on page 449 to set bridge parameters.

IMPORTANT: Currently, the bridge is using the same TLS files as the broker. Therefore, it must use the same
root certificate for a successful connection.

Device MQTT Topics

● Uplink topic: application/1/device/+/rx
● Downlink topic: application/1/device/+/tx
● Join topic: application/1/device/+/join
● Ack topic: application/1/device/+/ack
● Error topic: application/1/device/+/error
● Status topic: application/1/device/+/status
NOTE:
The application ID is 1 for the predefined application. If a user changes or adds an application via
LoRaWAN® WebUI, the ID can be different from 1.
The + in the topics refers to all devices. If you need to handle a specific device, replace the + with the
device EUI.

I.4
MC-EDGE LoRaWAN Backup and Restore
STS provides the ability to back up and restore the MC-EDGE® site LoRaWAN® configuration.
The backup includes all MC-EDGE site LoRaWAN information defined through the LoRa web UI/Rest APIs,
including: end nodes, keys, users, network, and application definitions. The MC-EDGE site LoRaWAN
information is saved internally on the MC-EDGE Flash so it remains available for disaster recovery. The
backup allows you to restore all already defined LoRaWAN network configuration data on the replaced unit.
The backup and restore operations need to be performed separately for each site. The backup of LoRaWAN
information for a specific site can be restored only on that site or its replacement unit.
The LoRaWAN backup is handled like any similar STS upload file process. However, the restoration is
handled by both the STS file download process and the MC-Edge RTU. The invocation of the MC-Edge
is required to allow the usage of LoRaWAN backup data from another RTU. To support this feature, it is
required to replace some unique value stored into backup with the value that is relevant for the target box.

653
6802979C10-BA
Appendix J: MC-EDGE Upgrade Tables

Appendix J

MC-EDGE Upgrade Tables

J.1
MC-EDGE Upgrade Table for ASTRO Users
Table 223: MC-EDGE Upgrade Table for ASTRO Users

Procedure Upgrade Path Steps Comments

1 Auxio (Remote): 1. Install STS of R11.0. ● The Composite file
R9.5 → R11.0 Document: contains the new ker-
MCIOT_LLT_002_STS_Upgrade nel and FS changes.
2. Import the R9.5 STS project with ● The Composite file
the new STS. name is fs-32-
Document: MCIOT LLT 003 Up- upgrade.zip.bin
grade STS Project (or similar).
3. Install the Composite file. ● It takes about 10 mi-
Document: MCIOT_LLT_001_MC- nutes to install the
EDGE_Upgrade Composite file.
Procedure: “Kernel / Bundle / Ki- ● It takes approximate-
netis / Composite Upgrade” ly 15 minutes to up-
4. Install the site configuration. grade one unit.
Document: MCIOT_LLT_001_MC- ● Upgrading more than
EDGE_Upgrade one unit takes 15 mi-
Procedure: “Site Configuration” nutes each, as there
is no parallel process-
5. Install the Kinetis file. ing. This is unique
Document: MCIOT_LLT_001_MC- to the upgrade from
EDGE_Upgrade R9.5 to R11.0. In later
Procedure: “Kernel / Bundle / Ki- upgrades, the use of
netis / Composite Upgrade” a regular bundle en-
ables parallel installa-
tion.
2 Auxio (Local): R9.5 1. Install STS of R11.0.
→ R11.0 Document:
MCIOT_LLT_002_STS_Upgrade
2. Import the R9.5 STS project with
the new STS.
Document: MCIOT_LLT_003_Up-
grade_STS_Project
3. Upgrade with the SD card.
Document: MCIOT_LLT_001_MC-
EDGE_Upgrade
Procedure: “SD-card Upgrade”

654
 6802979C10-BA
Appendix J: MC-EDGE Upgrade Tables

Procedure Upgrade Path Steps Comments

4. Install the site configuration.

Document: MCIOT_LLT_001_MC-
EDGE_Upgrade
Procedure: “Site Configuration”
5. Install the Kinetis file.
Document: MCIOT_LLT_001_MC-
EDGE_Upgrade
Procedure: “Kernel / Bundle / Ki-
netis / Composite Upgrade”

J.2
MC-EDGE Upgrade Table for General Purpose
Users
Table 224: MC-EDGE Upgrade Table for General Purpose Users

Procedure Upgrade Path Steps Comments

1 Auxio (Remote): 1. Install STS of R11.0. ● The Composite file
R9.5 → R11.0 contains the new ker-
2. Import the R9.5 STS project with
the new STS. nel and FS changes.

3. Install the Composite file by per- ● The Composite file

forming the following actions: name is fs-32-
upgrade.zip.bin
a. Select System → Add-On (or similar).
Manager.
● It takes about 10 mi-
b. On the top of the File Types nutes to install the
panel, select MC-EDGE. Composite file.
c. For a file type, select File Sys-
● It takes approximate-
tem, e.g. fs-32-
ly 15 minutes to up-
upgrade.zip.bin
grade one unit.
d. Browse to the file and attach it ● Upgrading more than
to the site. one unit takes 15 mi-
e. To install the selected file, use nutes each, as there
the Download tab. is no parallel process-
ing. This is unique
4. Install the site configuration by us-
to the upgrade from
ing the Download tab.
R9.5 to R11.0. In later
5. Install the Kinetis file by per- upgrades, the use of
forming the following actions: a regular bundle en-
a. Select System → Add-On ables parallel installa-
Manager. tion.

b. On the top of the File Types

panel, select MC-EDGE.

655
6802979C10-BA
Appendix J: MC-EDGE Upgrade Tables

Procedure Upgrade Path Steps Comments

c. For a file type, select Kinetis

File, e.g.
k10proj_R05_00_05.hex
d. Browse to the file and attach it
to the site.
e. To install the selected file, use
the Download tab.

2 Auxio (Local): R9.5 1. Install STS of R11.0.

→ R11.0
2. Import the R9.5 STS project with
the new STS.
3. Upgrade with the SD card by per-
forming the following actions:
a. Copy the content of the
SDCard folder onto your SD
card.
b. Put the SD card in its slot in the
MC-EDGE® unit.
c. Disconnect the power of the
MC-EDGE unit.
d. Reconnect the power of the
MC-EDGE unit.
e. Ping the MC-EDGE unit and
wait until it responds (approx.
five minutes).
f. Pull out the SD card from its
slot.
4. Install the site configuration by us-
ing the Download tab.
5. Install the Kinetis file by per-
forming the following actions:
a. Select System → Add-On
Manager.
b. On the top of the File Types
panel, select MC-EDGE.
c. For a file type, select Kinetis
File, e.g.
k10proj_R05_00_05.hex
d. Browse to the file and attach it
to the site.
e. To install the selected file, use
the Download tab.

656
 6802979C10-BA
Appendix K: MC-EDGE NFM Number of Objects Limitation

Appendix K

MC-EDGE NFM Number of Objects

Limitation
For MC-EDGE® units which are configured as NFM, the maximum number of objects derived from the
following:
SCADA tables that are allocated for NFM devices (not including RFDS): 7, 9, 10, 20–30 (14 tables in total)
In each of those tables, rows 2–248 are used, i.e. 247*14=3458 (the total amount of objects that can be used)
The following is the number of objects allocated for each device:
MNI-PROTEUS: 29
TRAK-9100: 8
IpManaged: 2
CBRonGTR8000: 43
SatRxGPW8000: 25
MsRxGPW8000: 31
MBRonGTR8000: 36
RBRonGTR8000: 36
NOTE: For RFDS, tables 100–105 are used.

657