ACE1000 Easy Configurator User Guide-D

User Guide
ACE1000 Easy
Configurator
0 3.00
Version
AB
6802988C98-D
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
product or service names are the property of their respective
owners.
Copyright © 2015 All rights reserved

COMPUTER SOFTWARE COPYRIGHTS
The Motorola products described in this instruction manual may include copyrighted Motorola computer programs stored in
semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola certain
exclusive rights for copyrighted computer programs including the exclusive right to copy or reproduce in any form the
copyrighted computer program. Accordingly, any copyrighted Motorola computer programs contained in the Motorola
products described in this manual may not be copied or reproduced in any manner without the express written permission of
Motorola. Furthermore, the purchase of Motorola 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, except for the normal
non-exclusive, royalty free license to use that arises by operation of law in the sale of a product.
This media, software or hardware ("Product") obtained from Motorola Solutions, Inc. ("Motorola Solutions") may include
Motorola Solutions’ Software, Third Party Software (defined below), and/or Open Source Software (defined below).
The object code or source code (collectively, the "Software") included with the Product is the exclusive property of Motorola
Solutions or its licensors, and any use is subject to the terms and conditions of one or more agreements in force between the
purchaser of the Motorola Solutions Product or licensee of the Motorola Solutions Software and Motorola Solutions.
SOFTWARE IS PROTECTED BY U.S. COPYRIGHT LAWS AND INTERNATIONAL LAWS AND TREATIES.
UNAUTHORIZED COPYING, DISTRIBUTION OR OTHER USE OF THIS PRODUCT IS STRICTLY PROHIBITED. ANY
DISTRIBUTION OR USE NOT SPECIFICALLY APPROVED BY MOTOROLA SOLUTIONS IS STRICTLY PROHIBITED.
Motorola Solutions’ Software is subject to the commercial terms and conditions entered into with Motorola Solutions, any
other use is strictly prohibited. Commercial Software licensed for redistribution by Motorola Solutions ("Third Party
Software") is subject to the terms and conditions in force between Motorola Solutions and the licensor of the Third party
Software. The terms and conditions governing the usage of Third Party Software may be part of the agreement entered into
by the purchaser of the Product with Motorola Solutions or separate Third Party Software license agreement(s) included with
the Product.
Software provided by Motorola Solutions which is covered by a publicly available license governed solely under Copyright
law, whereas the complete terms and obligations of such license attach to a licensee solely through the act of copying, using
and/or distribution of the licensed Software, such obligations often include one or more of attribution obligations, distribution
obligations, copyleft obligations, and intellectual property encumbrances is referred to herein as "Open Source Software".
The use of any Open Source Software is subject to the licenses, terms and conditions of the commercial agreement in force
between the purchaser of the Product and Motorola Solutions as well as the terms and conditions of the corresponding
license of each Open Source Software package. If there is a conflict between the terms and conditions of any commercial
agreement and the terms and conditions of the Open Source Software license, the applicable Open Source Software license
will take precedence. Copies of the licenses for the included Open Source Software as well as their attributions,
acknowledgements, and software information details, are listed below. Motorola Solutions is required to reproduce the
software licenses, acknowledgments and copyright notices as provided by the authors and owners, thus, all such information
is provided in its native language form, without modification or translation.
For instructions on how to obtain a copy of any source code made publicly available by Motorola Solutions related to Open
Source Software distributed by Motorola Solutions, you may send your request in writing to:
Motorola Solutions, Inc.

Open Source Software Management
1301 E. Algonquin Road
Schaumburg, IL 60196
USA.
In your request, please include the Motorola Solutions Product name and version, along with the Open Source Software
specifics, such as the Open Source Software name and version.
Note: the source code for the Open Source Software included by Motorola Solutions may be resident on the Product’s
installation media provided with the Product or on supplemental Product media. Please reference and review the entire
Motorola Solutions Open Source Software “Legal Notices” and any corresponding “End User License Agreement” provided
with the Product or the commercial agreement under which the Product was purchased for details on the availability, location
and method for obtaining source code. Further, depending on the license terms of the specific Open Source Software,
source code may not be provided. Please reference and review the entire Motorola Solutions Open Source Software “Legal
Notices” and “End User License Agreement” to identify which Open Source Software packages have source code provided
or available.
To view information regarding licenses, acknowledgments and required copyright notices for Open Source Software used in
this Product, please select “Legal Notices” from the graphical user interface of the Software (if applicable) or as specified in
the “Legal Notices” or End User License Agreement File/README associated with the Product. Use of any Software is
subject to acceptance of the corresponding terms associated with the Software and by using the Software you agree you
have reviewed the terms and agreed to be bound by said terms.
MOTOROLA, 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 Motorola Solutions, Inc. or
their respective owners. All rights reserved.
Motorola Solutions, Inc.

1301 E. Algonquin Road,
Schaumburg, IL 60196 U.S.A.
Table of Contents
TABLE OF CONTENTS .......................................................................................................................................... I

REFERENCE ....................................................................................................................................................... III
Glossary .......................................................................................................................................................iii
Terms and Conventions ............................................................................................................................... iv
Applicable Documentation ........................................................................................................................... v
ACE1000 EASY CONFIGURATOR DESCRIPTION ..............................................................................................1-1
ACE1000 System Overview .......................................................................................................................1-1
ACE1000 Easy Configurator Overview .....................................................................................................1-2
ACE1000 Easy Configurator User Interface .............................................................................................1-7
ACE1000 EASY CONFIGURATOR OPERATION .................................................................................................2-1
Getting Started with the ACE1000.............................................................................................................2-1
Building an ACE1000 System ..................................................................................................................2-11
ACE1000 System Administration .............................................................................................................2-37
ACE1000 Site Administration (Basic) .....................................................................................................2-42
ACE1000 Monitoring Mode ....................................................................................................................2-47
Administering a Site (Advanced) .............................................................................................................2-57
Maintaining an ACE1000 Site (Advanced) ..............................................................................................2-59
ACELogic...................................................................................................................................................... 1
ACE1000 TROUBLESHOOTING........................................................................................................................3-1
APPENDIX A: SITE CONFIGURATION PARAMETERS ........................................................................................ A-1
ACE1000 Port Parameters ....................................................................................................................... A-1
ACE1000 General Parameters ................................................................................................................. A-2
Application Parameters ............................................................................................................................ A-2
ACE1000 I/O Parameters ....................................................................................................................... A-21
ACE1000 Settings ................................................................................................................................... A-23
APPENDIX B: ACE1000 EASY CONFIGURATOR ICONS ................................................................................... B-1
APPENDIX C: ACE1000 MODBUS CONFIGURATION .................................................................................... C-1
ACE1000 MODBUS Support in a Mixed System...................................................................................... C-1
ACE1000 MODBUS Support in an ACE1000 System .............................................................................. C-1
MODBUS Address .................................................................................................................................... C-2
ACE1000 Data Register Location ............................................................................................................ C-2
ACE1000 MODBUS Data Types .............................................................................................................. C-5
SCADA Polling and Comm Status of ACE1000 RTUs ............................................................................. C-5
Port Configuration for ACE1000 MODBUS ............................................................................................ C-6
MODBUS Configuration .......................................................................................................................... C-7
APPENDIX D: ACE1000 USE CASES .............................................................................................................. D-1
Performing System-Wide Clean Install via the FEP................................................................................. D-1
Performing Clean Install One Unit at a Time .......................................................................................... D-2
Replacing a Defective Unit on Site (Disaster Recovery) .......................................................................... D-3
Restarting a Unit (Disaster Recovery) ...................................................................................................... D-3
Restoring a Defective Unit to the Factory Default (Disaster Recovery) .................................................. D-3
Adding and Configuring New RTUs On-Site (System Expansion) ........................................................... D-4
Adding and Configuring New RTUs Off-Site (System Expansion) ........................................................... D-5
Changing an Existing RTU Configuration On-Site (System Expansion) .................................................. D-5
Upgrading to a Higher ACE1000 version (System Upgrade) .................................................................. D-6
i
Table of Contents
Downgrading to a Lower ACE1000 version (System Downgrade) .......................................................... D-7
ii
Table of Contents
APPENDIX E: CODESYS IEC61131-3 PROGRAMMER APPLICATIONS ........................................................... E-1

APPENDIX F: ACE1000 DESIGN GUIDELINES ................................................................................................ F-1
Setting Time Zone ..................................................................................................................................... F-1
ACE1000 System with ASTRO IV&D Radio ............................................................................................. F-1
ACE1000 System with MotoTrbo Digital Radio ....................................................................................... F-2
ACE1000 System with MotoTrbo Connect Plus ....................................................................................... F-2
ACE1000 System with Dynamic IP ........................................................................................................... F-3
ACE1000 System with Serial RS485 Link ................................................................................................. F-4
ACE1000 System with SCADA ................................................................................................................. F-4
ACE1000 System with PLC....................................................................................................................... F-4
ACE1000 System with Redundant Links ................................................................................................... F-4
ACE1000 System with Burst Transmissions ............................................................................................. F-4
ACE1000 System with Automatic Polling ................................................................................................. F-5
APPENDIX G: ACE1000 CREDENTIALS .......................................................................................................... G-1
iii
Reference
Glossary
This list of terms consists of abbreviations, acronyms and specialized words used in this
manual.
Acronyms and Abbreviations
ACE Advanced Control Equipment

AI Analog Input
AO Analog Output
CPU Central Processing Unit
DI Digital/Discrete Input
DO Digital/Discrete Output
FEP Front End Processor
GPS Global Positioning System
I/O Input/Output
ISO International Organization for Standardization
IP Internet Protocol
LAN Local Area Network
LED Light Emitting Diode
MDLC MDLC Motorola Data Link Communication (Seven-layer OSI protocol)
MODBUS MODICON BUS Protocol
OSI Open System Interconnection
OTG On-The-Go
PC Personal Computer
PLC Programmable Logic Controller
iii
Reference
Terms and Conventions

In the ACE1000 Easy Configurator documentation, the terms “RTU” and “site” are
interchangeable.
The term “unit” refers to either the ACE1000 RTU or the ACE1100 FEP.
iv
Reference
Applicable Documentation
The ACE1000 system includes the following manuals:
• ACE1000 Easy Configurator User Guide,

Motorola publication no. 6802988C98
• ACE3600 STS/ACE1000 Software Diagnostic Output and Error Messages Manual,

• ACE1000 C Toolkit User Guide,

• ACE1000 RTU Owner’s Manual,

v
ACE1000 Easy Configurator Description
The ACE1000 Easy Configurator is a Web-based interface to the ACE1000

RTU/ACE1100 FEP used to build, configure and maintain an ACE1000 system.
ACE1000 System Overview

The ACE1000 system provides SCADA technology used to automate a control system,
such as emergency response, water monitoring, electric power distribution and irrigation
control systems.
An ACE1000 system consists of ACE1000 remote terminal units (RTU), each connected
to an ACE1100 Front End Processor (FEP) concentrator in a computerized control center
via a communication network. Various communication links, such as Ethernet LAN,
radio, or wireline can be used.
The communication system is used for transmitting alarms, status information, telemetric
readings, calculated data, diagnostics and error logging information from the RTUs in the
sites through the FEP to the central facility computer.
In addition to on-board Inputs/Outputs (I/Os), additional I/O modules can be added to the
RTU. The digital and analog I/Os connected to the RTU monitor/control the site. The
RTU can also monitor third party Programmable Logic Controllers (PLC).
The RTUs communicate with the FEP using the MDLC protocol, based on the seven
layers of the OSI (Open Systems Interconnection) model published by ISO, and adapted
for SCADA communication. The protocol provides network support and multiple logical
channels per physical port, enabling simultaneous central-to-RTU sessions. It also enables
each RTU to simultaneously run several communication sessions, such as data exchange,
on-line monitoring, diagnostics, etc.
1-1
Figure 1-1 ACE1000 System Diagram
For technical information on the ACE1000 RTU and ACE1100 FEP, see the ACE1000
RTU Owner’s Manual.
ACE1000 Easy Configurator Overview

The ACE1000 Easy Configurator, which runs on a personal computer, enables the user to
design, setup, maintain, and monitor a system and its sites. The user connects via the
Google Chrome™ Web browser (version 39.X.YY) to the RTU, either directly or via the
FEP.
ACE1000 Easy Configurator Functions

The ACE1000 Easy Configurator provides the following functions:
• Building an ACE1000 System
• Configuring the RTU/FEP ports and communication
• Configuring the RTU on-board I/Os and I/O modules
• Monitoring the System/RTU
• Installing files in the RTU/FEP (e.g. site configuration, ‘C’ application, etc.)
• Managing users for the RTU
• Defining rule-based logic for RTU operation
1-2
• Uploading a site configuration to the FEP files
• Updating the date and time in RTU sites
• Synchronizing all RTUs to the FEP time
• Retrieving errors logged in the RTUs/FEP (hardware or software malfunctions)
• Retrieving software diagnostics from the RTUs/FEP (by object entity names)
• Retrieving I/O events logged in the RTUs
• Backing up the RTU configuration and data
• Generating SCADA tags (Wizcon, Intouch and general formats)
• Deploying configurations to the RTU/FEP
ACE1000 RTU Definition

When a new RTU is added to the system, the system designer selects a configuration from
a set of standard RTU site configuration (e.g. a Main unit + 1 Input module + 1 Output
module). The system designer defines the unit’s ports (communication links) and the site
name/address.
Default configuration parameters provided by the system for all RTUs and for the FEP. If
tuning is required, an experienced administrator or technician can modify the parameters
of an RTU or FEP. For details see Appendix A: Site Configuration Parameters.
ACE1000 Communication Interfaces

The FEP/RTU supports a variety of communication media.
Most of the interfaces listed below are used for MDLC communication between the FEP
and RTU. The interfaces marked (non-MDLC only) are used for non-MDLC, general
communication with the FEP or RTU, as marked below.
Up to two of the following ports can be defined in each unit.
• Through the Micro USB 2.0 On-the-Go port
ASTRO IV&D (ASTRO APX radio)

MotoTRBO XPR 5350 Digital
• Through the 10/100 Mb Ethernet port
LAN (Ethernet)
SCADA Center (non-MDLC only)
User device (non-MDLC only)
PLC (non-MDLC only)
MotoTrbo XRT Gateway (FEP only)
1-3
• Through the RS232/RS485 port
Cellular modem: Siarra wireless (AirLINK FXT edge) or Maxon - intelimax

MDS SD 4710 modem
External modem (Westremo)
TETRA MTM5200
Serial RS232
Serial RS485 multidrop
PLC (non-MDLC only)
GPS (non-MDLC only)
• Through the USB 2.0 Host port (MDLC)
ASTRO IV&D (ASTRO APX radio)

MotoTRBO XPR 5350 (either USB port)
MotoTRBO Connect Plus radio (RTU only)
• Through the P1 Plug-in RS232 port
Cellular modem: Siarra wireless (AirLINK FXT edge) or Maxon - intelimax

MDS SD 4710 modem
TETRA MTM5200
Serial RS232
PLC (non-MDLC only)
• Through the P2 Plug-in RS232 port

Serial RS232
PLC (non-MDLC only)
Communication via the various ports may be simultaneous.
The RTU operates on all radio frequencies: VHF, UHF and 800/900 MHz.
1-4
ACE1000 User Management

ACE1000 users access the RTU/FEP via the Google Chrome™ Web browser. Each user
is assigned a role, associated with certain permissions. The three roles are:
• Admin – Has full access to all administrative features within a system, including all
units
• Technician – Has full access to all non-administrative features within a system,

including all units.
• Viewer – Can view the system layout, including all units. Cannot view administrative
features or change the system.
By default, each unit has three built-in users, one for each of the supported roles. The
default usernames are admin, viewer, and technician. The default usernames can be
deleted from the unit as long as at least one other Admin user exists.
An Admin user can define other users, assign/change user roles, and change passwords.
Users are managed at the unit level, not at the system level. However, changes made on
the FEP can be applied to the all units in the system (e.g. using the Apply to all units
option.)
The following permission table describes the permissions of each role:
Functionality Sub- Admin Technician Viewer

Functionality
Save/Discard Yes Yes No

Deploy Yes Yes No
Install S/W (kernel, file Yes Yes No
system, package)
Import Project Yes Yes No
Export Project Yes Yes No
Backup Data Yes Yes No
Generate SCADA Yes Yes No
Error Log Read log from Yes Yes Yes
unit
Erase log in unit Yes Yes No
Export to CSV Yes Yes Yes
IO Event Log Read event log Yes Yes Yes
Diagnostics Read diagnostics Yes Yes Yes
1-5

Functionality
Poll Yes Yes No

Time Sync (MDLC) On FEP only in Yes Yes No
System View
On RTU when
connected
locally
Date & Time Read time Yes Yes Yes
Set time Yes Yes No
Sync time Yes Yes No
General Change project Yes Yes No
name and
description
Change unit Yes Yes No
name and
description
Add/Remove/Duplicate Yes Yes No
RTU
Add/Remove/Edit Yes Yes No
Communication
Add/Remove IO Yes Yes No
modules
Switch I/O modules Yes Yes No
Configure DI, DO, AI, Yes Yes No
AO
Applications View all Yes Yes Yes
applications
Modify Yes Yes No
parameters in
any application
Rule Set View rules Yes Yes Yes
Add/remove rule Yes Yes No
Edit rules Yes Yes No
User Management (all Yes No No
functionality)
View System/Unit Yes Yes Yes
Monitor
1-6

Functionality
Set DO, AO Yes Yes No

View System/Unit Yes Yes Yes
Configuration
Change System Settings Yes Yes No
Reset Options Reboot Yes Yes No
Erase all flash Yes Yes No
Erase all flash Yes Yes No
and preserve
configuration
ACE1000 Application
The default application which runs in the FEP/RTU can be enhanced by user-defined rules
using the ACE1000 Easy Configurator. For complex applications/systems, experienced
users can program a ‘C’ application using the ACE1000 ‘C’ Toolkit, or an IEC61131
compliant application using the Codesys programming software. The ‘C’ or Codesys
IEC61131 application is installed in the RTU using the ACE1000 Easy Configurator. For
details on the Codesys IEC61131 application, see ACE1000 IEC61131 Developer's Guide.
ACE1000 Software
The ACE1000 software runs on the Linux operating system.
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 using the ACE1000 Easy
Configurator.
ACE1000 Easy Configurator User Interface

The ACE1000 Easy Configurator Web-based graphical user interface has two views and
two basic modes:
• RTU View/Configuration mode – where the RTU of a specific site is displayed

and configured.
• RTU View/Monitoring mode – where the RTU’s current communication, I/O and
power level status can be viewed. Information from the RTU can be retrieved or
modified.
• System View/Configuration mode (FEP only) – where the FEP and all sites in the
system are displayed and configured.
1-7
• System View/Monitoring mode (FEP only) – where the current communication,

I/O and power level status can be viewed for each RTU in the system.
Information from a given RTU can be retrieved or modified.
You can perform various functions from the tool bar at the top of the screen, from the icon
bar on the right side of the window, and from icons on the picture of the RTU/FEP on the
left side of the screen. In System View/Monitoring Mode, the icons are attached to the
FEP/sites instead of the icon bar on the on the right side of the window.
Pointing the mouse at certain GUI elements displays a tooltip with additional information.
In FEP System View, you can specify a text string in the Search field and view only those
RTUs whose site names include the specified string.
Figure 1-2 depicts the components of the GUI. Figure 1-2 - Figure 1-5 depict the four
main windows.
For a description of the icons, see Appendix B: ACE1000 Easy Configurator Icons.
Important: When configuring/monitoring an RTU via the FEP’s interface, files are
transferred between the FEP and the RTU. This can take much longer than
configuring/monitoring the RTU directly via its own interface.
Figure 1-2 RTU View/Configuration Mode
1-8
Figure 1-3 System View/Configuration Mode
Figure 1-4 RTU View/Monitoring Mode
1-9
Figure 1-5 System View/Monitoring Mode
1-10
ACE1000 Easy Configurator Operation
This chapter details tasks that you perform to build, configure and maintain an ACE1000
system using the Web-based ACE1000 Easy Configurator.
Unless otherwise stated, all functions are available for Administrator, Technician, and
Viewer roles. For more on roles, see ACE1000 User Management.
Note: When interfacing with an ACE1000 unit (ACE1100 FEP or ACE1000 RTU), the
speed of response from the FEP/RTU depends on the actual communication media.
Getting Started with the ACE1000

Follow this process to familiarize yourself with the ACE1000 system and build a system
using the easy-to-use Project Wizard.
Process 1-1 Getting Started with the ACE1000
1. Access the ACE1100 FEP/ACE1000 RTU. See Accessing the ACE1100

FEP/ACE1000 RTU via the Web Interface.
2. Build a simple project on the FEP using the Project Wizard. See either
Generating a New ACE1000 Project using the Project Wizard or
Generating a New ACE1000 Project based on an Existing Project using the
Project Wizard.
For specific guidelines on different system, media, and transmission types, see
Appendix F: ACE1000 Design Guidelines.
3. Learn about viewing the system on the FEP. See Navigating the ACE1000
System on the FEP. See ACE1000 Easy Configurator User Interface to learn
about the elements of the user interface.
Accessing the ACE1100 FEP/ACE1000 RTU via the Web Interface

Access to an ACE1000 unit requires logging in with valid credentials.
During a session, you also may have to log in again under the following circumstances:
• Session timed out after 15 minutes of inactivity.
• A new configuration was imported.
• The unit was reset or flash was erased.
• A file system, kernel, package, or bundle was installed.
Follow this procedure to access the ACE1100 FEP/ACE1000 RTU via the Web interface.
2-1
Operation
Note: The initial connection to any ACE1000 unit is only via the USB OTG port, using a
standard USB type connector. It is recommended to download the OTG driver from
Microsoft when using the USB console port from a PC/laptop.
Procedure 1-1 Accessing the ACE1100 FEP/ACE1000 RTU via the Web Interface
4. In the Google Chrome™ Web browser, enter the IP address of the RTU/FEP.
• If your PC/laptop is connected to the USB OTG port, enter
https://192.168.9.9.
• If your PC/laptop is connected to another port over TCP/IP, enter the allocated
IP address, e.g. https://18.188.18.131.
5. If the PC/laptop does not have an appropriate local area connection for
accessing the unit, do the following:
a) In Control Panel -> Network and Internet -> Network Connections,
select a TCP/IP connection and click Properties.
b) If your PC/laptop is connected to the USB OTG port, click Use the
following IP address and enter https://192.168.9.10. This is the address
allocated to a PC/laptop communicating with the USB OTG part.
c) To use a dynamically allocated IP address, click Obtain an IP address
automatically.
d) If you are prompted that the site’s security certificate is not trusted, click
Proceed anyway.
6. In the Log in to FEP/Log in to RTU dialog box, enter the Username and
Password.
Note: The first time you log in, use the default username (administrator,
technician or viewer). For the default passwords, see Table G-1. After the
initial login, all default passwords must be changed to protect the system. See
Managing Users and Passwords.
Note: Username must be 6-15 characters long and may contain: A-Z, a-z, 0-9,
_, -
Password must be 14-30 characters long and must contain at least one of each
of the following: digit <0-9>, lower/upper case letter <A-Z, a-z>, special
character <`~!@#_\$%^&*()-+=|[]{}/.,?<>:';\>
2-2
Operation
7. Click Login.
8. If you entered valid user credentials, read the login notice and click Continue.
If you entered invalid user credentials, repeat this procedure with the valid
Username and Password.
Result: The RTU/FEP home page is displayed in Configuration mode.
9. If you are accessing an RTU via the FEP, click the RTU’s site name link.
For a description of the window components, see ACE1000 Easy Configurator User
Interface.
Note: If there is a mismatch between the configured I/O module configuration and the
actual modules connected to the unit, an error is displayed when entering the RTU View.
See Resolving ACE1000 Configuration Mismatch.
Note: When accessing different RTUs via USB, you must open a new browser session per
RTU. This can be done with the browser’s Refresh/F5 button or the New window/New
tab commands.) Unless you are browsing in Google Chrome’s incognito mode, if the
initial session is opened by a user with an Administrator role, and a second browser
session is opened by a user with a Viewer role, the first session loses the Administrator
permissions.
Note: To access an ACE1000 unit via SSH/putty SCP/WINSCP, use the terminal login
user or non-root administrator user. See Table G-2.
2-3
Operation
Generating a New ACE1000 Project using the Project Wizard

Follow this procedure to build a project for an ACE1000 system on an FEP with the
factory default configuration (either a new FEP or an FEP whose flash was erased.)
If the FEP default configuration has already been modified, see Generating an ACE1000
Project.
Procedure 1-2 Generating a New ACE1000 Project using the Project Wizard
1. (Optional) Plan your system, including the number of RTUs to be deployed, IP

addresses, etc.
2. Access the ACE1100 FEP. See Accessing the ACE1100 FEP/ACE1000 RTU via
the Web Interface.
3. In the Welcome to Wizard dialog box, select Generate new project. Click Next.
4. In the New Project dialog box, enter the Project Name, where Project Name
must be 1-40 characters long and may contain: A-Z, a-z,0-9, and special characters
,`!@#$%^*() []{}_
5. (Optional) Enter the Description, where Description must be 0-400 characters
long and may contain: A-Z, a-z,0-9, and special characters ,`!@#$%^*() []{}_
6. Select up to two instances of Communication Type for FEP-RTU communication
in a project. For a description of the options, see Configuring Communication in
an ACE1000 RTU.
7. Enter the Number of Units to add to the system (not including the FEP.) The
maximum is 250 RTUs.
2-4
Operation
8. Do one of the following:

IF THEN
If you choose to generate the click Generate.
project now and perform I/O
configuration later,
If you choose to perform I/O do the following:
configuration now and build the a. Click More Options.
project afterwards,
b. In the Project dialog box, set the number
of units for each of the module
configurations (Main, Main+ 1 Input
module, Main + 1 Output module, etc.)
Click Generate.
2-5
Operation
Result: The requested number of units are generated and displayed in the FEP System
View.
Note: If the total number of units/configurations selected in step 8 is different than the
Number of Units specified in step 7, a message is displayed. The number of generated
units reflects the selected units from step 8.
Postrequisites: Before your system is ready to use, you must do the following:
• Configure basic information such as unit time zone, IP addresses, and system-dependent
parameters (e.g. auxiliary power voltage.) See Configuring ACE1100 FEP/ACE1000 RTU
Parameters. For specific guidelines for different system, media and transmission types,
see Appendix F: ACE1000 Design Guidelines.
• If you did not configure the I/O module layout in the wizards, configure it in the RTUs
before deploying the system. See Changing the Operating System Account Password.
• You must change the default passwords to protect your system. See Managing Users
and Passwords.
Once the system is operational, you can perform administrative, monitoring and diagnostic
functions such as checking error loggers, retrieving diagnostics, setting site date and time,
producing reports, etc. See ACE1000 Site Administration (Basic) and Administering a Site
(Advanced) and ACE1000 System Administration below.
If you performed this procedure as a part of configuring the IRM server, go back to
Configuring IRM Server.
2-6
Operation
Generating a New ACE1000 Project based on an Existing Project using the

Project Wizard
Follow this procedure to build a project based on an existing project for an ACE1000
system on an FEP with the factory default configuration (either a new FEP or an FEP
whose flash was erased.)
If the FEP default configuration has already been modified, see Generating an ACE1000
Project.
Procedure 1-3 Generating a New Project System using the Project Wizard
1. (Optional) Plan the changes to be made to the existing project, including the
number of RTUs to be deployed, IP addresses, etc.
the Web Interface.
3. In the Welcome to Wizard dialog box, select Generate project based on existing
one.
4. Click Select Project.

5. In the Import dialog box, browse to the preferred configuration.db file, select it,
and click Open.
6. Click OK.
7. In the Welcome to Wizard dialog, enter the Project Name.
8. (Optional) Enter the Description. Click Next.
Result: The project is built.
9. When the Log in to FEP dialog box appears, log in to the FEP again. See
Accessing the ACE1100 FEP/ACE1000 RTU via the Web Interface.
2-7
Operation
Postrequisite: Before your system is ready to use, you may need to modify the I/O
configuration, users, or system configuration, such as unit time zone, IP addresses, and
system-dependent parameters (e.g. auxiliary power voltage.) For specific guidelines on
different system, media and transmission types, see Appendix F: ACE1000 Design
Guidelines.
etc. See ACE1000 Site Administration (Basic) and Administering a Site (Advanced)
below.
If you performed this procedure as a part of configuring the IRM server, go back to
Configuring IRM Server.
Navigating the ACE1000 System on the FEP

Follow this procedure to navigate the ACE1000 system on the FEP.
Procedure 1-4 Navigating the ACE1000 System on the FEP
1. If you are not already logged in, access the ACE1100 FEP. See Accessing the
ACE1100 FEP/ACE1000 RTU via the Web Interface.
Result: The FEP System View is displayed in Configuration mode. The
project name, unit type (ACE1100 FEP), username, and user role appear at the
top of the screen.
2. To filter the displayed RTUs based on site name, enter the preferred string in
the Search field.
3. Note: If the text in the System View Search field does not match any site
names, no RTUs are displayed.
4. To select more than one site, CTRL-click the preferred sites, or click next to a
site and drag the mouse over the preferred sites.
5. To view the port configuration and I/O configuration of a specific site as a

tooltip, point the mouse at a specific site.
2-8
Operation
6. To switch to the local FEP View (e.g. for local configuration of the ACE1100
FEP,) click the FEP – sitename link.
Result: The FEP’s local RTU View (System View-> RTU View | sitename) is
displayed in Configuration mode.
2-9
Operation
7. To switch to the RTU View of an ACE1000 RTU (e.g. to configure the RTU,)
click the site link (e.g. Site 002).
Result: The RTU View of the selected site (RTU View | sitename) is
displayed in Configuration mode.
Note: If there is a mismatch between the configured I/O module configuration
and the actual modules connected to the unit, an error is displayed. See
Resolving ACE1000 Configuration Mismatch.
8. To minimize/maximize an I/O module attached to an RTU, click < or > in the

upper right corner of the I/O module.
9. To return to the System View, click the System View link at the top of the
window.
10. In Configuration mode, to select a command from the menu bar on top of the
window, or an option from the icon bar at the side of the window, point at the
command/option and click it when the cursor appears.
11. In Configuration mode, click the Tools menu to view the commands available
(e.g. Install, Export, Report, etc.) Different commands are available in the FEP
System View, in the FEP RTU View, and locally in the RTU’s RTU View.
Note: To select a command, click the icon or the first line of the command when
the cursor appears.
12. In Configuration mode, to set basic settings, click the gear

icon on the top of the window.
13. To save the changes made to a unit in Configuration mode, click Save. If you
do not want to save the changes, click Discard. When configuring from the
FEP, changes are saved at the System View level only, for the whole system.
2-10
Operation
14. To switch to Monitoring mode, click Monitoring.
15. In Monitoring mode, to select a command from the icon bar at the side of the
window, point at the command and click it when the cursor appears.
Building an ACE1000 System

Follow this process to build a project for an ACE1000 system.
Process 1-2 Building an ACE1000 System
1. (Optional) Plan your system, including the number of RTUs to be deployed, IP

addresses, etc.
the Web Interface.
3. Generate the project using one of three methods:
• Project Wizard - new project - See Generating a New ACE1000 Project using the
Project Wizard.
• Project Wizard – based on existing project - See Generating a New ACE1000
Project based on an Existing Project using the Project Wizard.
• Step-by-step - new project - See Generating an ACE1000 Project.
For specific guidelines on different media and system types, see Appendix F:
ACE1000 Design Guidelines.
4. Deploy the project in the FEP.
5. Deploy the project in the RTUs.
Generating an ACE1000 Project

Follow this procedure to generate or add RTUs to an ACE1000 project. Each project
represents one system.
Procedure 1-5 Generating an ACE1000 Project
1. In the FEP home page System View, click the General icon.
2. In the General dialog box, enter a Project Name and Description. Click OK.
2-11
Operation
3. Add the RTUs:
a) Click the Add Units icon.

b) In the Add Units dialog box, click the preferred module configuration (Main,
Main+ 1 Input module, Main + 1 Output module, etc.)
4. c) In the Add RTU dialog box, select the Number of RTUs to add. Click OK.
5. When a message appears prompting you to deploy the FEP, click Close.
2-12
Operation
6. Configure the communication.
a) In the System View, click the Communication icon.
7. b) Select the preferred RTUs (using the mouse or CTRL-click).
8. c) In the Communication dialog box, click the preferred communication type.

For a description of the options, see Table 1-1 in Configuring Communication
in an ACE1000 RTU.
9. d) When a message appears asking if you want to add the selected

communication type to the selected RTUs, click OK.
10. e) When a message appears that the port configuration succeeded, click Close.
11. f) Repeat steps b-e until the port configuration is complete for all RTUs. Close
the Communication dialog box.
12. Customize the configuration of the system and each individual RTU, as
necessary. See Customizing the ACE1100 FEP/ACE1000 RTU Configuration.
13. Click Save.
14. Deploy the system:

• To deploy the system from the FEP using Deploy, see Deploying an ACE1000
System from the FEP.
• To deploy the system from the PC using Export, see Deploying an ACE1000
System from the PC.
Postrequisite: Before your system is ready to use, you must do the following:
• Configure basic information such as unit time zone, IP addresses, and system-dependent
parameters (e.g. auxiliary power voltage.) See Configuring ACE1100 FEP/ACE1000 RTU
Parameters. For specific guidelines for different system, media and transmission types,
see Appendix F: ACE1000 Design Guidelines.
2-13
Operation
• If you did not configure the I/O module layout in the wizards, configure it in the RTUs
before deploying the system. See Changing the Operating System Account Password.
• You must change the default passwords to protect your system. See Managing Users.
producing reports, etc. See ACE1000 Site Administration (Basic) and Administering a Site
(Advanced) and ACE1000 System Administration below.
Deploying an ACE1000 System from the PC

Follow this procedure to deploy a newly built ACE1000 system from the PC using
Export/Import. To deploy an ACE1000 system from the FEP using Deploy, see
Deploying an ACE1000 System from the FEP.
Procedure 1-6 Deploying an ACE1000 System from the PC
the Web Interface.
2. If you haven’t already done so, generate and configure a new project, including all
RTUs, with site name, MDLC site ID, port and I/O configuration. See Generating
an ACE1000 Project or Generating a New ACE1000 Project using the Project
Wizard or Generating a New ACE1000 Project based on an Existing Project using
the Project Wizard.
3. From the System View, export the project to the PC. (See Exporting the ACE1000
Configuration.)
4. From the PC, access an RTU. See Accessing the ACE1100 FEP/ACE1000 RTU
via the Web Interface.
5. In the RTU View, import the project from the PC to the RTU and deploy it in the
RTU. See Importing the ACE1000 System Configuration.
6. Repeat step 4 to step 5 for each RTU in the system.
Note: When accessing different RTUs via USB, you must open a new browser
session per RTU. This can be done with the browser’s Refresh/F5 button or the
New window/New tab commands.)
7. From the PC, access the FEP. See Accessing the ACE1100 FEP/ACE1000 RTU
8. In the FEP System View, click Deploy to deploy the system in the FEP.
Result: A progress bar on the top of the screen indicates the status of the
configuration file transfer to the remote unit, while the progress icon indicates that
the progress of the configuration deployment on the unit.
Postrequisite: Once the system is operational, you can perform administrative, monitoring
and diagnostic functions such as checking error loggers, retrieving diagnostics, setting site
date and time, etc. See ACE1000 Site Administration (Basic) and Administering a Site
(Advanced) and below.
2-14
Operation
Deploying an ACE1000 System from the FEP

Follow this procedure to deploy a newly built ACE1000 system using from the FEP using
Deploy. To deploy an ACE1000 system from the PC using Export/Import, see Deploying
an ACE1000 System from the PC.
Procedure 1-7 Deploying an ACE1000 System from the FEP
1. Set up the FEP-RTU communication for each ACE1000 RTU, according to the
system plan. See Setting up FEP-ACE1000 RTU Communication.
the Web Interface.
3. If you haven’t already done so, generate and configure a new project, including all
RTUs, with site name, MDLC site ID, port and I/O configuration. See Generating
an ACE1000 Project or Generating a New ACE1000 Project using the Project
Wizard or Generating a New ACE1000 Project based on an Existing Project using
the Project Wizard.
4. In the System View, click the FEP - sitename link.
5. In the FEP’s local page (System View-> RTU View | FEPsitename), click
Deploy to deploy the configuration in the FEP.
6. In the System View, click Deploy to deploy the configuration to all RTUs in the
system.
Result: The progress of each file transfer and deployment is shown. A table lists
the status of each RTU as it is deployed.
Postrequisite: Once the system is operational, you can perform administrative, monitoring
and diagnostic functions such as checking error loggers, retrieving diagnostics, setting site
date and time, etc. See ACE1000 Site Administration (Basic) and Administering a Site
(Advanced).
Setting up FEP-ACE1000 RTU Communication

When building a system using Deploy, follow this procedure for each ACE1000 RTU, to
set up communication between the FEP and the ACE1000 RTUs.
Procedure 1-8 Setting up FEP-ACE1000 RTU Communication
1. Access the ACE1000 RTU. See Accessing the ACE1100 FEP/ACE1000 RTU
2-15
Operation
2. In the RTU home page (RTU View | sitename), click the General icon.
3. In the General dialog box, set the Site Name, Description, and Site ID
according to the system plan. Click OK.
4. On the RTU home page, near the Main Board, click .
5. From the window of communication components (port type), drag the preferred
communication component to the preferred port for ACE1000 RTU to FEP
communication. For a description of the options, see Table 1-1 in Configuring
Communication in an ACE1000 RTU.
Note: When dragging, the possible ports for the specific port type (e.g. Serial
2-16
Operation
RS232 to P1, P2 or RS232/RS485) are framed in light blue (broken lines.)

Result: The configured port is framed in light blue (solid line.)
6. If an error message is displayed that the maximum number of ports has already
been configured, do the following:
a) Click one of the configured ports.
b) Click the Delete icon to delete the port configuration.
c) Repeat step 5.
7.
8. Close the window of communication components.
9. To save the changes, click Save. To discard the changes, click Discard.
10. Postrequisite: Communication interfaces changes must be deployed in order

for them to take effect in the unit.
2-17
Operation
Exporting the ACE1000 Configuration

Follow this procedure to export the ACE1000 configuration from the FEP/RTU to the PC.
Procedure 1-9 Exporting the ACE1000 Configuration
1. If you are not already logged in, access the ACE1100 FEP/ACE1000 RTU. See

• If you are connected to an FEP, in the System View, select Tools -> Export
Project configuration.
• If you are connected to an RTU, in the RTU View, select Tools -> Export
RTU configuration.
Result: The configuration.db file is downloaded to the PC. Subsequent
exports to the same PC are named configuration (n).db.
Importing the ACE1000 System Configuration

Follow this procedure to import the ACE1000 system configuration from the PC to the
FEP.
Procedure 1-10 Importing the ACE1000 System Configuration
2. In the System View, select Tools -> Import Project configuration.
3. In the Import dialog box, click Choose File, browse to the preferred
configuration.db file and click Open.
2-18
Operation
4. In the Import dialog box, click OK.
5. When the Log in to FEP dialog box appears, log in to the FEP again. See
6. Review the configuration and deploy it. See Deploying an ACE1100

FEP/ACE1000 RTU.
Importing an ACE1000 RTU Configuration

Follow this procedure to import an ACE1000 system configuration from the PC to an
RTU.
Procedure 1-11 Importing an ACE1000 RTU Configuration
1. If you are not already logged in, access the ACE1000 RTU. See Accessing the
2. In the RTU View, select Tools -> Import RTU configuration.
3. In the Import dialog box, click Choose File, browse to the preferred
configuration.db file and click Open. Click OK.
4. If the imported configuration.db file contains more than one RTU

configuration (a full project configuration), select the relevant configuration for
the site in the Import dialog. Click OK.
2-19
Operation
5. When the Log in to FEP dialog box appears, log in to the RTU again. See
6. Review the configuration and deploy it. See Deploying an ACE1100

FEP/ACE1000 RTU.
Configuring Communication in an ACE1000 System

Follow this procedure to configure communication interfaces in an ACE1000 system from
the FEP.
Procedure 1-12 Configuring Communication in an ACE1000 System
1. Access the ACE1100 FEP. See Accessing the ACE1100 FEP/ACE1000 RTU
2. In the System View, click the Communication icon.
3. Select the preferred RTUs (using the mouse or CTRL-click).
4. In the Communication dialog box, click the preferred communication type.

For a description of the options, see Table 1-1 in Configuring Communication
in an ACE1000 RTU.
5. When a message appears asking if you want to add the selected communication
type to the selected RTUs, click OK.
Note: If a message is displayed that a plug-in port does not exist, see Resolving
ACE1000 Configuration Mismatch.
6. When a message appears that the port configuration succeeded, click Close.
7. Repeat steps 2-5 until the port configuration is complete for all RTUs. Close
the Communication dialog box.
9. Deploy the system to the RTUs and on the FEP. See Deploying an ACE1100
FEP/ACE1000 RTU.
2-20
Operation
Configuring Communication in an ACE1000 RTU

Follow this procedure to configure communication interfaces in an ACE1000 RTU.
Procedure 1-13 Configuring Communication in an ACE1000 RTU
1. Access the ACE1000 RTU. See Accessing the ACE1100 FEP/ACE1000 RTU
2. In the RTU home page (RTU View | sitename), near the Main Board,, click
3. From the window of communication components (port type), drag the preferred
communication component to the preferred port for ACE1000 RTU to FEP
communication. For a description of the options, see Table 1-1.
Note: When dragging, the possible ports for the specific port type (e.g. Serial
RS232 to P1, P2 or RS232/RS485) are framed in light blue (broken lines.)
Result: The configured port is framed in light blue (solid line.)
Note: If a message is displayed that a plug-in port does not exist, see Resolving
ACE1000 Configuration Mismatch.
4. If an error message is displayed that the maximum number of ports has already
been configured, do the following:
a) Click one of the configured ports.
b) Click the Delete icon to delete the port configuration.
c) Repeat step 5.
5. Close the window of communication components.
7. Postrequisite: Communication interfaces changes must be deployed in order

for them to take effect in the unit.
Table 1-1 ACE1000 Communication Interfaces
Communication Description
Interface
Cellular modem Siarra wireless (AirLINK FXT edge) or Maxon –
intelimax (MDLC and non-MDLC)
ASTRO APX For connection to an ASTRO APX IV&D radio
MotoTrbo XPR 5350 For connection to a MotoTrbo XPR 5350 digital
radio
MotoTrbo XPR 5350 For connection to a MotoTrbo XPR 5350 Connect
Connect Plus Plus (non-IP)
MDS SD 4710 modem For connection to an MDS SD 4710 modem
External modem For connection to an external modem
(Westremo)
TETRA MTM5200 For connection to a TETRA MTM5200 radio
2-21
Operation
Communication Description
Interface
Serial RS232 For serial RS232 communication with a variety of
devices
Serial RS485 multidrop For serial RS485 communication with a variety of
devices
LAN For Ethernet IP connection
LAN XRT Gateway For Connect Plus XRT Gateway on LAN
PLC For connection to a PLC, e.g. for a unit acting as
MODBUS master to a PLC (non-MDLC only)
GPS For connection to a GPS receiver (non-MDLC)
SCADA center For connection to a SCADA, e.g. for an FEP/RTU
acting as MODBUS slave to a SCADA Center, via
RS232 or RS485 (non-MDLC only)
User device For connection to a User device with a user
protocol (non-MDLC only)
Configuring ACE1000 Auxiliary Power

If the ACE1100/FEP ACE1000 RTU includes an optional plug-in board with an auxiliary
power connector, follow this procedure to set the auxiliary power voltage level in the unit
configuration.
Procedure 1-14 Configuring ACE1000 Auxiliary Power
2. In the RTU/FEP home page (RTU View | sitename or System View-> RTU
View | sitename), click the AUX power connector which is marked with a
white square.
Note: If the current plug-in board does not support the AUX feature, an error is
displayed.
3. When the Settings icon appears, click the icon.
4. In the AUX Configuration dialog, select the preferred AUX voltage level from
the drop-down list. Click OK.
2-22
Operation
6. Postrequisite: Auxiliary power configuration changes must be deployed in

order for them to take effect in the unit.
Managing Users and Passwords

If you are a user with administrator privileges, follow this procedure to add/modify users,
user roles, and user credentials in an ACE1100 FEP/ACE1000 RTU. For more
information, see ACE1000 User Management.
Note: After the initial login, all default passwords must be changed to protect the system.
For a list of the default usernames and passwords, see Table G-1. It is recommended to
change passwords periodically to protect your system.
Procedure 1-15 Managing Users
View | sitename), click the User Management icon.
9. To add a new user, in the User Management screen, do the following:

a) Click Add User under the preferred role.
b) In the New User dialog, enter the Username, First Name, and Last Name.
_, -
2-23
Operation
First Name/Last Name must be 0-15 characters long and may contain: A-Z, a-
z, 0-9, _, -
character <`~!@#_\$%^&*()-+=|[]{}/.,?<>:';\>
c) Enter the Password and then Confirm Password.
d) If you are on the FEP and want to add this user to all RTUs, check Add this
user to all units.
e) Click OK.
Result: If the user credentials are valid, the new user appears next to the role.
10. To edit an existing user, do the following:

a) Click the Edit icon.
b) To change the user, enter the Username, First Name, and Last Name.
_, -
First Name/Last Name must be 0-15 characters long and may contain: A-Z, a-
z, 0-9, _, -.
c) To change the user password, enter the new password in the Password field
and again in the Confirm Password field.
character <`~!@#_\$%^&*()-+=|[]{}/.,?<>:';\>
d) To reset the password, click Reset to Default Password.
e) If you are on the FEP and want to apply the changes to all RTUs, check
Apply changes to all units.
f) Click OK.
2-24
Operation
11. To delete an existing user, do the following:

a) Click the Delete icon.
b) When prompted to confirm the deletion, click Delete.
12. Close the User Management window.
14. Postrequisite: User management changes must be deployed in order for them
to take effect in the unit.
15. To change the operating system account password, see Procedure 1-16.
Changing the Operating System Account Password

Follow this procedure to change the operating system account password.
Note: After the initial login, all default passwords must be changed to protect the system.
For a list of the default usernames and passwords, see Table G-1. It is recommended to
change passwords periodically to protect your system.
Procedure 1-16 Changing the Operating System Account Password
1. Log into the ACE1000 unit via SSH/putty using the terminal login user
credentials listed in Table G-2.
2. To switch to the root user, enter: “su –” and the admin password listed in Table
G-1.
3. Run: “passwd <username>”, where <username> is the username for the

account whose password you are changing.
2-25
Operation
4. When prompted, enter the new password (twice) for the <username> account.
character <`~!@#_\$%^&*()-+=|[]{}/.,?<>:';\>
Configuring I/O Modules in an ACE1000 RTU

Follow this procedure to configure I/O modules in an ACE1000 RTU.
Procedure 1-17 Configuring I/O Modules in an ACE1000 RTU
1. If you are not already logged in, access the ACE1100 FEP/ACE1000 RTU.
See Accessing the ACE1100 FEP/ACE1000 RTU via the Web Interface.
View | sitename), click the Add Module icon.
3. Select Add Input Module or Add Output Module.
4. The default settings for a specific I/O are shown in a tooltip over the I/O. If
necessary, click the I/O to change the default settings. See Configuring I/O
Settings in an ACE1000 RTU. For a description of the parameters, see
Appendix A Site Configuration Parameters. Click OK.
5. To swap the position of the I/O modules (left/right), click the swap modules
icon .
6. To delete an I/O module, click the Delete icon.

Note: If the I/O module is minimized, first click > to maximize it.
7. To save the I/O changes, click Save. To discard the I/O changes, click Discard.
8. Postrequisite: Configuration changes must be deployed in order for them to

take effect in the unit.
Note: If there is a mismatch between the configured I/O module configuration and the
actual modules connected to the unit, an error is displayed when entering the RTU View.
See Resolving ACE1000 Configuration Mismatch.
Installing an Application, Package, or Bundle to a Site via FEP

Follow this procedure to install applications, packages, or bundles (sets of packages) to
one or more sites, from the FEP.
Procedure 1-18 Installing an Application, Package, or Bundle to a Site via FEP
2. In the RTU View (System View-> RTU View | sitename) in Configuration

mode, select Tools -> Install applications, packages, bundles.
2-26
Operation
3. In the Install SW dialog, click the arrow keys to move the preferred units from
the Available Units list to the Units to Install list. Click OK.
4. In the SW Install window, select the Installation Type.

Note: The File System, Kernel and License File cannot be installed in an RTU
when viewing the RTU from the FEP.
Result: You are prompted to browse and select the file(s) to install.
2-27
Operation
5. Click Browse and select the preferred file(s):

• If you are installing a ‘C’ application, you select both an application (default
.plx) and a parameters file (default .dat). Note: The length of the ‘C’
application name should not exceed 13 characters.
• If you are installing an IEC (Codesys programmer file) application, you select
both an application (.app) and a checksum file (.crc).
• If you are installing a package or a bundle, you select only one file (default
.rpm).
6. Click Install.
Result: The progress of the file transfer to the remote unit(s) and the installation
in the remote unit(s) is shown.
• If you are installing a package or a bundle, the SW Install window displays
the status of each unit (OK, unit rebooting/failure). Note that unit reboot takes
two-three minutes. After the reboot, the Log in to FEP/Log in to RTU
window is displayed.
• If you are installing an IEC (Codesys programmer) or ‘C’ application, the SW
Install window displays the status of each unit (OK/failure).
Note: If you abort the installation of a file to multiple units, the current
installation is completed. Installation to subsequent units is not performed.
7. If you are installing an IEC (Codesys programmer) or ‘C’ application, when a

message appears that the installation finished, click Close to close message.
8. To install another file to the same set of units, click Install Another File) and
repeat this procedure from step 4.
9. Click Close to close the SW Install window.
Note: If you try to navigate to another page while the install operation is in progress, a
confirmation message is displayed. If you chose to leave the current page, the install
operation continues and there is no way to view the final status (success/failure.)
Installing an Application, Package, Bundle, File System, Kernel, or License

File Directly to a Unit
Before downloading new system software, check your file versions carefully.
Follow this procedure to install a file system, kernel, package, bundle (set of packages) or
license file directly to a unit (FEP or RTU).
If you want to install the IEC application and run it, perform the following
actions:
1. Install the IEC application files.

2. Install the IEC application license using the License File option.
3. Reboot the unit.
2-28
Operation
Procedure 1-19 Installing an Application, Package, Bundle, File System, Kernel, or

License File Directly to a Unit
2. In the RTU View (RTU View | sitename or System View-> RTU View |
FEPsitename) in Configuration mode, select Tools -> Install applications,
packages, licenses.
3. In the SW Install window, select the Installation Type.

Result: You are prompted to browse and select the file(s) to install.
Note: An IEC (Codesys programmer) application cannot be installed on the
FEP.
4. Click Browse and select the preferred file(s):

• If you are installing a ‘C’ application, you select both an application (default
.plx) and a parameters file (default .dat). Note: The length of the ‘C’
application name should not exceed 13 characters.
• If you are installing an IEC (Codesys programmer) application (on RTU only),
you select both an application (.app) and a checksum file (.crc).
• If you are installing a file system, kernel, package, bundle or license file, you
select only one file (default .rpm).
5. Click Install.
Result: The progress of the file transfer to the remote unit(s) and the installation
in the remote unit(s) is shown.
Note: If the selected file system, kernel, package, or bundle is already installed
on the unit, you can opt to Continue, Select a different file or Close.
2-29
Operation
6. Finish the installation:

• If you installed a file system, kernel, package or bundle, after the unit reboots
(reboot takes two-three minutes) and the Log in to FEP/Log in to RTU
window is displayed, log in again. See Accessing the ACE1100 FEP/ACE1000
RTU via the Web Interface.
Note: When a new file system is installed, the previous configuration is deleted.
In this case, access to the unit is only via the USB OTG port.
• If you installed an IEC (Codesys programmer) or ‘C’ application or license
file, when a message appears that the installation finished, click Close to close
message.
• If the installation of a file system or kernel fails, the unit may go into failsafe
mode. See ACE1000 Troubleshooting for details.
7. To install another file, do the following:

• If you installed an IEC (Codesys programmer) or ‘C’ application or license
file, click Install Another File and repeat this procedure from step 3.
• If you installed a file system, kernel, package or bundle, repeat this procedure
from step 1.
8. If the SW Install window is open, click Close.
Note: If you try to navigate to another page while the install operation is in progress, a
confirmation message is displayed. If you chose to leave the current page, the install
operation continues and there is no way to view the final status (success/failure.)
Resolving ACE1000 Configuration Mismatch

Follow this procedure to resolve a mismatch between the configured I/O module
configuration and the actual modules connected to the unit, or between the configured
plug-in configuration and the actual plug-ins connected to the unit.
Procedure 1-20 Resolving ACE1000 Configuration Mismatch
1. If, when switching to the RTU View of an RTU or FEP, a message is displayed
that an I/O module in the configuration does not match the physical I/O setup
on the unit, do one of the following:
• To automatically change the unit configuration to match the physical setup,
click OK.
• To ignore the mismatch and resolve it manually later, click Cancel.
Note: If one of the I/O modules is not functioning, communication to the I/Os is
delayed.
2. If, when dragging a communication type to the P1/P2 port, a message is

displayed that a plug-in port does not exist (no option board is physically
installed on the unit), do one of the following:
• Add a plug-in board that includes the port, if you own one.
• Order an ACE1000 model that includes a plug-in board.
3. If, when configuring the plug-in AUX power voltage level, a message is
displayed that a plug-in port does not exist (no option board is physically
installed on the unit) or that the option board does not support the AUX feature,
do one of the following:
2-30
Operation
• Add a plug-in board that supports the AUX feature, if you own one.
• Order an ACE1000 model that includes a plug-in board with the AUX feature.
2-31
Operation
ACE1000 System Administration

In Configuration mode, the user can perform operations required to administer the
ACE1000 system.
Uploading a Site Configuration to the FEP

Follow this procedure to upload a site configuration of an RTU to the FEP and add it to the
system configuration. This is done when the RTU site configuration is changed locally.
Procedure 1-21 Uploading a Site Configuration to the FEP
2. From the System View, click the preferred RTU site name link.
3. In the RTU View (System View-> RTU View | sitename), select Tools ->
Upload RTU to this FEP.
Result: The Upload window appears with the RTU name and Status and
Upload Summary. The progress of the upload and deploy operation appears in
the progress bar.
4. When the upload and deploy operation complete, a message is displayed, click
Close.
Note: Deploy to the FEP is always performed after the upload operation
(regardless of the success/failure of the upload). This is done to ensure the
communication parameters between FEP and RTU are in sync.
5. Close the Upload window.
Deploying Multiple Sites

For more efficient system setup and system changes, deploy site configuration files
changes to more than one site at once.
Follow this procedure to deploy several or all sites in the system.
2-32
Operation
Procedure 1-22 Deploying Multiple Sites
7. From the System View in Configuration mode, click Deploy.
8. Select either the All modified units or Selected units radio button.
9. Select the units from the Available Units list and click to move them to the
Units to Deploy list. Click OK.
Result: The progress of each file transfer and deployment is shown. A table
lists the status of each RTU as it is deployed. See the figures below.
2-33
Operation
10. To stop the deployment, click Stop Deploy. The current site deployment
continues. The deployment of any subsequent sites is aborted.
Generating SCADA Tags

Follow this procedure to generate SCADA tags from an ACE1100 FEP, from ACE1000
RTU.
Procedure 1-23 Generating SCADA Tags
2. In the System View on the FEP or RTU View on an RTU, select the preferred
SCADA tags format:
Result:
- If you select Tools -> Wizcon format, the wizcon.csv file is downloaded to
the PC. Subsequent reports are named wizcon (n).csv.
- If you select Tools -> Intouch format, the intouch.csv file is downloaded to
the PC. Subsequent reports are named intouch (n).csv.
- If you select Tools -> General format, the general.csv file is downloaded to
the PC. Subsequent reports are named general (n).csv.
If you generated tags from FEP for multiple sites, the downloaded file is a .tar file,
which contains one .zip file for each site. In that case, unzip all files and load .csv
files to SCADA one by one.
Duplicating a Site
Follow this procedure to create a copy of an existing site.
Procedure 1-24 Duplicating a Site
2-34
Operation
2. In the System View in Configuration mode, click the Duplicate icon on the
site to be copied.
3. In the Duplicate dialog box, specify the number of new sites to create, and click
OK.
4. When a message appears that the new system configuration must first be
deployed in the FEP, and then in the new RTUs, click Close.
5. In the new RTU, in the RTU home page (RTU View | sitename), click the
General icon.
6. In the General dialog box, change the Site Name, Description, and Site ID
according to the system plan. Click OK.
7. If a port in the new RTU requires an IP address (e.g. LAN, ASTRO APX radio,)
click the LAN port and click the Settings icon.
8. Change the IP configuration for the new RTU according to the system plan.
Click OK. For a description of the IP parameters, see Appendix A: Site
Configuration Parameters.
Deleting a Site
Follow this procedure to delete one or more sites from a system.
2-35
Operation
Procedure 1-25 Deleting a Site
2. From the System View, click the Delete icon on the preferred site(s).
3. When a message appears asking you to confirm the deletion of the selected
site(s), click OK.
Producing a Report of the Site/System

Follow this procedure to produce a report of all the elements in the site/system, including:
• General unit information: (Site name, MODBUS address, MDLC site ID)
• I/O information (element name, type, description, module index, where Main=1,
Expansion1=2, and Expansion2=3, object index on module)
• Port information (port name, connected to media e.g. GPS, LAN, application e.g.
MDLC, MODBUS)
• Installed user files (‘C’ application files, IEC61131 Codesys programmer

application files, bundles, packages or license files that have been downloaded)
Procedure 1-26 Producing a Report of the Site/System
2. In the FEP System View or from the RTU’s RTU View, select Tools ->
Report.
Result: The Reports.csv file is downloaded to the PC. Subsequent reports are
named Reports (n).csv.
2-36
Operation
ACE1000 Site Administration (Basic)

In Configuration mode, the user can perform operations required to administer an
ACE1000 site.
Configuring I/O Settings in an ACE1000 RTU

Follow this procedure to configure I/O Settings in an ACE1000 RTU equipped with I/O
modules. For details on adding an I/O to the unit, see Configuring I/O Modules in an
ACE1000 RTU.
Procedure 1-27 Configuring I/O Settings in an ACE1000 RTU
2. To display the advanced I/O parameters, in the RTU View, double-click an I/O
name in the I/O Module.
Result: The selected I/O is highlighted in blue. The corresponding LED on the
front panel is framed in orange.
2-37
Operation
3. If preferred, in the I/O dialog box, edit the I/O name (e.g. from DI_1 to Door, or
from DO_3 to Light) and the description to more meaningful values.
4. In the I/O dialog box, configure the preferred I/O settings. Where relevant,
click the tabs to see other parameters. Click OK. For a description of the
parameters, see Appendix A Site Configuration Parameters.

Renaming a Site
Follow this procedure to rename an existing site.
Procedure 1-28 Renaming a Site
2-38
Operation
View | sitename), click the General icon.
3. In the General dialog box, edit the Site Name and/or Site ID. Click OK.
Site Name must be 1-40 characters long and may contain: A-Z, a-z,0-9, and
special characters ,`!@#$%^*() []{}_
Note: If the new name/ID is already in use, an error message is displayed.
Deploying an ACE1100 FEP/ACE1000 RTU

Follow this procedure to deploy the system configuration to an ACE1100 FEP/ACE1000
RTU when changes have made, as indicated by the Needs Deploy icon (on a site in
System View) or the icon (in the menu bar). For details on deploying more
than one unit, see Deploying Multiple Sites.
Note: When the IP address of an RTU/FEP is changed and deployed, the unit resets.
When changes are made to the IP address of a site in the field from the FEP, first deploy
the changes in the RTU, and then in the FEP, to avoid losing the FEP-RTU connection.
Procedure 1-29 Deploying an ACE1100 FEP/ACE1000 RTU
2. In Configuration mode, do one of the following,
• If you are connected to the preferred RTU in RTU View, and the
icon appears in the menu bar, click Deploy.
• If you are connected to the FEP in System View, and the Needs Deploy
icon appears on the site, click the site link, and in System View-> RTU View |
sitename, click Deploy.
3. If a message appears prompting you to save the changes, click Yes.
4. When a message appears that configuration deployment has finished, click

Close.
Note: When you are connected directly to the preferred RTU/FEP, a progress
bar on the top of the screen indicates the status of the configuration file transfer
to the remote unit, while the progress icon indicates the progress of the
configuration deployment on the unit.
2-39
Operation
5. Click Close to close the Deploy window.
6. Note: If you click Close while the deploy operation is in progress, a

confirmation message is displayed. If you chose to close, the deploy operation
continues and there is no way to view the final status (success/failure.)
Logging out of the ACE1100 FEP/ACE1000 RTU

Follow this procedure to log out of the ACE1100 FEP/ACE1000 RTU.
Procedure 1-30 Logging out of the ACE1100 FEP/ACE1000 RTU
1. From the FEP/RTU, click the Logout icon.
2-40
Operation
ACE1000 Monitoring Mode

In Monitoring mode, the user can monitor the status of units in the system, diagnose
problems, and maintain the units/system. In addition, the states of I/Os connected to a
specific ACE1000 RTU can be set.
Configuration changes must be deployed in the unit before monitoring.
In Monitoring mode, status indications are displayed on each unit, in both RTU View and
System View for communication status, unit power level, unit errors and configuration
changes. See Appendix B: ACE1000 Easy Configurator Icons for details. Pointing the
mouse at certain GUI elements displays a tooltip with additional information.
In System View, a red frame around a site indicates that the FEP does not recognize the
site (i.e. before the configuration has been deployed in the FEP and RTU.)
In ACE1000 Monitoring mode, the data on the screen is refreshed constantly.
Note: When monitoring an ACE1000 unit, the speed of response from the FEP/RTU
depends on the actual communication media.
While in ACE1000 Monitoring mode, the session does not time out after 15 minutes of
inactivity, and prompt the user to log in again. Therefore users in Monitoring mode should
manually lock the screen for security purposes.
2-41
Operation
Retrieving Error Logger Information from an ACE1000 Unit

Error messages relating to hardware and software malfunctions are logged to a file in the
RTU. The log file (size 200Kb, ~2,000 errors) is saved in the RTU’s flash memory.
When the log is full, no more errors can be logged, and it must be cleared manually.
Follow this procedure to retrieve error messages logged in the RTU and/or clear the log
file.
For a detailed explanation of the error message texts, see the ACE3600/ACE1000/ACE IP
Gateway RTU Software Diagnostic Output and Error Messages manual.
Note: When an error message is logged in the RTU, the ERR LED on the CPU front panel
changes to red. When the messages are cleared, the ERR LED changes to green.
Procedure 1-31 Retrieving Error Logger Information from an ACE1000 Unit
2. Go to Monitoring mode:
• If you are connected to the preferred RTU in RTU View or System View->
RTU View | sitename, click Monitoring.
• If you are connected to the FEP in System View and want to monitor the FEP
or a site in System View, click Monitoring.
• If you are connected to the FEP in System View and want to monitor a site in
RTU View, click the site link, and in System View-> RTU View | sitename
click Monitoring.
Note: If an error message is logged in the RTU, the Error icon appears in
Monitoring mode.
3. In the Monitoring window, open the Error Log window:

• If you are connected to the RTU in RTU View or System View-> RTU View
| sitename, click the Error Log icon.

• If you are connected to the FEP in System View, select
from the icon on the preferred site or the FEP.
4. In the Error Log window, click Get.

Note: The number of errors displayed per page is determined in the Logging
settings from the gear icon on the top of the window.
2-42
Operation
5. To filter the displayed error messages by text or to search for text within the
logger window, enter the preferred string in the Search field.
6. To display only certain types of error messages, select Error, Warning or

Information from the drop-down list next to the Search field. (Default is All.)
Click Get.
7. To export the errors in the Error Log to a file, click Export.

Result: The errorlog-DD-MM-YYYY-HH-MM.csv file is downloaded to the
PC, where HH is UTC format in 24-hour format. Subsequent error log file
downloads for that time are named errorlog-DD-MM-YYYY-HH-MM
(n).csv.
Note: If the exported file is downloaded to the PC without the .csv extension
file, add the extension manually.
8. To sort the messages in the Error Logger window by Time Stamp, Severity
or Description, click the column heading and click the arrow.
9. To page through the list of messages, click the arrow keys.
10. To clear the Error Log in the RTU and the list of logger entries from the Error
Logger window, click Clear.
Note: Before you click Clear, you may want to click Get again to retrieve any
errors which were logged while the Error Log window was open. Otherwise,
these incoming errors are deleted in the unit and not displayed in the GUI.
11. Close the Error Logger window.
2-43
Operation
Retrieving Software Diagnostics from an ACE1000 Unit

Follow this procedure to retrieve software diagnostics information from the RTU for
system maintenance, problem identification for remote services and statistics data on the
communication system performance.. For a detailed explanation of the diagnostics, see the
ACE3600/ACE1000/ACE IP Gateway RTU Software Diagnostic Output and Error
Messages manual.
Procedure 1-32 Retrieving Software Diagnostics from an ACE1000 Unit
RTU View, click the site link, and in System View-> RTU View | sitename,
click Monitoring.
3. In the Monitoring window, open the Diagnostics window:

| sitename, click the Diagnostics icon.

from the icon on the preferred site or the FEP.
4. In the Diagnostics window, select a device (logical name), enter a diagnostic

level number (0-255), and click Get.
Note: Each device has a different set of diagnostic levels. Level 255 displays
the list of levels defined for the device.
2-44
Operation
5. To filter the displayed diagnostics by text or to search for text within the logger
window, enter the preferred string in the Search field.
6. To export the diagnostics to a file, click Export.

Result: The diaglog-DD-MM-YYYY-HH-MM.csv file is downloaded to the
PC, where HH is UTC format in 24-hour format. Subsequent diagnostics file
downloads for that time are named diaglog-DD-MM-YYYY-HH-MM (n).csv.
7. To clear the contents of the Diagnostics window, click Clear.
8. Close the Diagnostics window.
Retrieving Event Logger Information from an ACE1000 Unit

Follow this procedure to retrieve events logged in the RTU.
The ACE1000 RTU event logger maintains up to 5,000 events in RAM, added cyclically
(FIFO.) When the event log is full, approximately 30% of the old events are cleared
making room for new events. Events include Bursts (changes that occurred) and Controls
(command requests that were sent).
Note: When the unit is reset or I/O definitions are changed (an I/O module is
added/removed, or I/O attributes are changed,) the events in the unit are cleared.
Therefore the contents of the event logger should be exported before resetting or changing
the I/Os.
Procedure 1-33 Retrieving Event Logger Information from an ACE1000 Unit
2-45
Operation
System View, click Monitoring.
click Monitoring.
3. In the Monitoring window, open the Event Log window:

| sitename, click the Event Log icon.

from the icon on the preferred site.
4. In the Event Log window, click Get.

Note: The number of events displayed per page is determined in the Logging
settings from the gear icon on the top of the window.
5. To filter events or to search for text within the logger window, enter the
preferred string in the Search field.
6. To limit the number of retrieved events, select the preferred number from the
drop-down list at the top of the screen. Click Get. Use this option when
communicating over a low bandwidth media.
2-46
Operation
7. To export the events in the RTU to a file, click Export.

Result: The eventlog_sitename.csv file is downloaded to the PC. Subsequent
event log file downloads are named eventlog_sitename (n).csv.
8. To sort the messages in the Event Logger window by Time Stamp, Type,
Source, or Description, click the column heading and click the arrow.
9. To page through the list of messages, click the arrow keys.
10. Close the Event Logger window.
Setting/Getting a Site's Date and Time

Follow this procedure to set/get a site’s date and time.
Note: The default time zone for ACE1000 units is UTC. During initial site configuration,
you must set the Application -> Time Zone-> Time zone offset parameter to the
appropriate value for the unit location. See Appendix A: Site Configuration Parameters
for a description of the parameter. For specific guidelines on setting time zone during
system setup, see Appendix F: ACE1000 Design Guidelines.
Procedure 1-34 Setting/Getting a Site's Date and Time
click Monitoring.
3. In the Monitoring window, open the Date & Time utility:

| sitename, click the Date & Time icon.

from the icon on the preferred site.
4. When the RTU Time appears in the Date and Time window, click Set to Unit
to set the site’s date and time to that of the PC.
2-47
Operation
5. To retrieve the date and time from the site again, click Refresh.
6. Close the Date & Time window.
Polling an ACE1000 Site

Follow this procedure to instruct an RTU whose alerts were disabled to synchronize its
runtime data from the FEP.
Procedure 1-35 Polling an ACE1000 Site
3. In the Monitoring window, do one of the following:

• If you are connected to the RTU in System View-> RTU View | sitename,
click the Poll icon.
• If you are connected to the FEP in System View, select from the
icon on the preferred site.
4. When a message appears that a polling request was sent to the site, click Close.
5. To see the updated information in the RTU, in System View, click the site link.
Synchronizing ACE1000 RTUs

Follow this procedure to synchronize the date and time of all RTUs in the system to that of
the FEP.
Note: Time sync has low accuracy over IP interfaces.
Procedure 1-36 Synchronizing ACE1000 RTUs
2. Make sure that the Application -> MDLC -> <port>Enable Sync parameter is
set to Enable.
2-48
Operation
4. In the Monitoring window, do one of the following:

• If you are connected to the RTU in RTU View | sitename, click the Time
Sync icon.
• If you are connected to the FEP in System View, select from
the icon on the preferred site.
5. When a message appears that a time synchronize command was sent, click
Close.
Monitoring ACE1000 RTU I/Os

Follow this procedure to monitor/set the state of I/Os connected to an ACE1000 RTU.
This procedure cannot be performed on an ACE1100 FEP.
Procedure 1-37 Monitoring ACE1000 RTU I/Os

Note: It may take a few seconds for the monitoring data to appear on the screen.
Result: An I/O element’s name is marked in red when its value changes
between monitoring cycles. Analog values are marked yellow when the value is
out of range. The data on the screen is refreshed constantly.
Note: If an AI value fluctuates to <0, it can appear in the SCADA as the high
end of the scale, because MODBUS does not recognize negative values.
2-49
Operation
3. In the panel to the right of one of the modules in the Monitoring window, point
the cursor at an I/O to and view the tooltip description.
4. To see where the I/O is physically located on the board, click the I/O name.
Result: The I/O name is highlighted in blue. The corresponding LED on the
front panel is framed in orange.
5. To set a DO in the Main or Output Expansion module, do the following:

a. Click the On/Off button next to the DO.
b. When the Set value for: <DOx> dialog box appears, click the On/Off button
to change its value. Click Set.
Result: A message appears that the set operation is in progress. Close the
message and wait until the updated (actual) I/O status is reflected in the
Monitoring window (based on the DO back indication.)
6. To set an AO in the Output Expansion module, do the following:

a. Click the indicator next to the AO name.
b. When the Set value for: <AOx> dialog box appears, drag the slider to the
preferred value. Click Set.
2-50
Operation
Administering a Site (Advanced)
Customizing the ACE1100 FEP/ACE1000 RTU Configuration

Follow this process to customize the configuration of an ACE1000 RTU or ACE1100
FEP.
Process 1-3 Customizing the ACE1100 FEP/ACE1000 RTU Configuration
1. Access the ACE1100 FEP/ACE1000 RTU. See Accessing the ACE1100

FEP/ACE1000 RTU via the Web Interface.
2. Configure the FEP/RTU parameters, if necessary. See Configuring ACE1100
FEP/ACE1000 RTU Parameters.
3. Configure the rules set, if necessary. See Error! Reference source not found..
4. (RTU only) Configure the I/O settings, if necessary. See Configuring I/O Settings
in an ACE1000 RTU.
5. (Administrators only) Configure the users, if necessary. See Managing Users.
6. Deploy the configuration. See Deploying an ACE1100 FEP/ACE1000 RTU.
Configuring ACE1100 FEP/ACE1000 RTU Parameters

Follow this procedure to configure parameters in an ACE1100 FEP/ACE1000 RTU. In
most cases, the default values of parameters are correct. Only experienced technicians and
administrators should change parameters.
Procedure 1-38 Configuring ACE1100 FEP/ACE1000 RTU Parameters
2. To configure general parameters (such as Site Name, Site ID), in the RTU/FEP
home page (RTU View | sitename or System View-> RTU View | sitename),
click the General icon. Click OK.
3. To configure parameters which relate to on board applications and services

(such as DNS Client, NTP & GPS, MDLC, Time Zone and Power
2-51
Operation
Management,) do the following:
a) Click the Application icon.

b) Change the parameter settings, as necessary.
Note: In the MDLC parameters window, click the port name (ETH1, P1, SI1)
to change port-specific parameters, or click General to change general MDLC
parameters.
c) Click OK.
5. For details on specific parameters, see Appendix A Site Configuration

Parameters.

Backing up the ACE1100 FEP/ACE1000 RTU Data and Configuration

Follow this procedure to back up the data and configuration from an ACE1100
FEP/ACE1000 RTU to a PC.
Procedure 1-39 Backing up the ACE1100 FEP/ACE1000 RTU Data and Configuration
2. In the System View or RTU View, select Tools -> Backup.

Result: The ace_1000_backup.tar file is downloaded to the PC. Subsequent
reports are named ace_1000_backup (n).tar.
3. Backed up files include configuration files and log files.
4. Postrequisite: Once the unit files are backed up, specific files can be restored
manually or copied to another computer (e.g. to analyze logs off line)
Uninstalling ACE1000 User Applications

Follow this procedure to uninstall user applications from a site.
Procedure 1-40 Uninstalling ACE1000 User Applications
6. In the RTU View (RTU View | sitename or System View-> RTU View |
sitename) in Configuration mode, select Tools -> Uninstall user applications.
7. When a message appears asking you to confirm the uninstall, which will stop
the ‘C’ applications, erase the application executable and configuration files and
uninstall the IEC (Codesys programmer) application, click Yes.
2-52
Operation
8. When a message appears that the uninstall of the user applications has finished,
click Close.
Resetting the ACE1100 FEP/ACE1000 RTU

Follow this procedure to reset the ACE1100 FEP/ACE1000 RTU, if you are a user
assigned either an Administrator and Technician role only.
Procedure 1-41 Resetting the ACE1100 FEP/ACE1000 RTU
View | sitename), click the Reset icon.
3. In the Reset options dialog box, select the preferred option:
• To reboot, click Reboot.
• To erase the entire flash, uninstall all applications and rules, and restore the unit to
its default configuration, click Erase all flash.
Note: On the FEP, the project with all configured units is deleted when the flash is
erased.
When the flash is erased, the previous configuration is deleted. In this case, access
to the unit is only via the USB OTG port.
Result: After the operation completes, the Log in to FEP/Log in to RTU dialog
box appears.
Maintaining an ACE1000 Site (Advanced)
ACE1000 Hardware Test

A number of hardware tests, diagnostics and calibrations can be performed by experienced
administrators on the ACE1100 FEP/ACE1000 RTU components.
2-53
Operation
During hardware tests, various values and settings can be changed by the user. These
changes revert to their previous values/settings under the following circumstances:
• when performed in service mode (e.g. calibration)

• when the change is temporary (e.g. lighting LEDs)
Operations such as I/O calibration must always be performed in service mode to avoid
interference with the RTU application.
Running the ACE1000 Hardware Test Utility

Follow this procedure to the hardware test utility on an ACE1100 FEP/ACE1000 RTU.
Procedure 1-42 Running the ACE1000 Hardware Test Utility
1. From the PC, run PuTTY or another OpenSSH utility.
2. In the PuTTY Configuration Session window (or parallel window in another

OpenSSH utility), enter the IP address of the ACE1000 unit in the Host Name
(or IP address) field.
3. (PuTTY only) In the PuTTY Configuration Terminal window, erase text in

the Answerback to ^E field. Click Open.
2-54
Operation
4. In the PuTTY window, log in using the terminal login user credentials listed in
Table G-2Error! Reference source not found.Error! Reference source not
found..
5. Enter su - to log in as root, using the admin password listed in Table G-1Error!
Reference source not found..
6. Enter cd /opt/ltr/bin/.
7. Enter ./hwtool.sh to run the hardware test utility. Click Enter.

Result: The list of hardware test functions is displayed. See Table 1-2.
Table 1-2 ACE1000 Hardware Test Functions
Function Number Description

1 General Information
2 Digital Input (DI) Operations
3 Digital Output (DO) Operations
4 Analog Input (AI) Operations
5 Analog Output (AO) Operations
6 Power Management
7 Miscellaneous
99 Exit the utility
2-55
Operation

• To retrieve general information, see Retrieving ACE1000 General
Information.
• To perform DI operations, see Performing ACE1000 DI Operations.
• To perform DO operations, see Performing ACE1000 DO Operations.
• To perform AI operations, see Performing ACE1000 AI Operations.
• To perform AO operations, see Performing ACE1000 AO Operations.
• To test/set the power management profile or clock frequency, see Performing
ACE1000 Power Management Operations.
• To test LEDs, see Testing ACE1000 LEDs.
• To test Service mode, see Testing ACE1000 Service Mode.
• To test auxiliary power, see Testing ACE1000 Auxiliary Power.
2. Enter 99 to exit the hardware test utility.
Retrieving ACE1000 General Information

Follow this procedure to retrieve general information on an ACE1100 FEP/ACE1000 RTU
using the hardware test utility.
Procedure 1-43 Retrieving ACE1000 General Information
1. If you are not currently in an encrypted communication session with the

FEP/RTU, run the ACE1000 hardware test utility. See Running the ACE1000
Hardware Test Utility.
2. At the Enter the function number prompt, enter 1. Click Enter.

Result: The ACE1000 general information is displayed for the unit, for the
main board and for any attached I/O expansion modules. See Table 1-3 for the
list of information.
Table 1-3 ACE1000 Hardware Test General Information
Information Description
Product Type from The type of unit. Can be one of:
eeprom 1=ACERTU
2=ACEFEP
3=IRMRTU
4=IRMFEP
Product Type from The type of unit and prototype. Can be one of:
hardware ACE1000-Main Px
ACE1000-ATEX with battery Px,
ACE1000-ATEX without battery Px
IRM-Main Px
Where x is the prototype number.
File System Version The current file system, e.g. 1.01-81
Kernel Version The version of the kernel e.g. Linux-3.2.0-ACECPU-
1.00.015
2-56
Operation
Uboot Version The version of the bootstrap loader e.g. Linux-3.2.0-
ACECPU-1.00.008
Option Board Type The ID of the optional plug-in board, if one is attached.
from eeprom Can be one of:
RS232 w/ AUX
RS232 w/o AUX
RS232 w/o AUX – ATEX
Rubicon
Option Board Type The ID and prototype number of the optional plug-in
from hardware board, if one is attached. Can be one of:
RS232 w/ AUX Px
RS232 w/o AUX Px
RS232 w/o AUX – ATEX Px
RS232 Rubicon Px
Where x is the prototype number.
Clock Frequency The clock rate/ microprocessor frequency. Can be either
300 MHz or 600 MHz.
Power Management The current power management profile. See Table 1-5
Profile for details.
Module Type The type of module. Can be one of: Main Board, Input
Board or Output Board.
Board ID The type of board. Can be one of:
1= IRM1500 main board
2= ACE1000 main board
3= ACE1000 main board with RTC battery ATEX
4= ACE1000 main board without RTC battery ATEX
5= I/O Exp. 1 AI Current
6= I/O Exp. 1 AI Current ATEX
7= I/O Exp. 1 AI Voltage
8= I/O Exp. 1 AI Voltage ATEX
9= I/O Exp. 2
10=I/O Exp. 2 ATEX
Kinetis Version The microcontroller version, e.g. D1.99.63
Serial Number The board serial number
FCN Factory Catalog Number printed on the board and used
when ordering.
Track ID Factory data, unique for each I/O module. Can be Null.
Board Temperature The last measured temperature of the specific board in
(C) °Celsius
Board Temperature The last measured temperature of the specific board in
(F) °Farenheit
2-57
Operation
Board Voltage (V) The voltage of the board. Should be between 9V and
30V.
3. To exit the hardware test utility, enter 99. Click Enter.
Changing Product Type

Follow this to change the product type from ACE 1000 RTU or RTU via FEP to IRM and
from IRM to ACE 1000 RTU.
Procedure 1-44 Changing Product Type
1. After logging on to RTU, from the right-hand panel, click .
2. In the Reset Options pop-up window that opens, select the Switch to radio
button and from the drop-down list, select the product type to which you want
to switch.
If you are switching to IRM, a message warning you about applications to be

uninstalled appears.
3. In the pop-up message window, click OK.
The system takes some time to change the product and reboot the unit. After the
reboot, the procedure is completed.
Performing ACE1000 DI Operations

Follow this procedure to perform DI operations on an ACE1000 RTU using the hardware
test utility.
Procedure 1-45 Performing ACE1000 DI Operations
1. If you are not currently in an encrypted communication session with the RTU,
run the ACE1000 hardware test utility. See Running the ACE1000 Hardware
Test Utility.

Result: The DI values from the Main board and the Input module (if such
exists) are displayed.
Performing ACE1000 DO Operations

Follow this procedure to perform DO operations on an ACE1000 RTU using the hardware
test utility.
2-58
Operation
Procedure 1-46 Performing ACE1000 DO Operations
Test Utility.

Result: The DO values from the Main board and the Output module (if such
exists) are displayed.
5. To set or clear a specific DO, at the next Enter the function number prompt,
enter the number for the corresponding DO control function (Clear DOx/Set
DOx) from the displayed list. Click Enter. Repeat this step as many times as
required.
Note: After setting a DO, the new DO status that is listed is the actual state of
the DO (based on the DO back indication.)
6. To return to the Main Menu, enter 88.
7. To exit the hardware test utility, enter 99.
8. To return to the Main Menu, enter 88. Click Enter.
Performing ACE1000 AI Operations

Follow this procedure to perform AI operations on an ACE1000 RTU using the hardware
test utility.
Important: Generally, I/Os are calibrated in the factory and should not be calibrated in the
field. Calibration should only be performed on the advice of service personnel.
Procedure 1-47 Performing ACE1000 AI Operations
Test Utility.

Result: The AI values from the Input module (if such exists) are displayed.
3. To get all AI values, at the next Enter the function number prompt, enter 1.
Click Enter.
4. To calibrate a specific AI, do the following

a. At the next Enter the function number prompt, enter the function number
for the corresponding AI to be calibrated (Calibrate AIx) from the displayed
list. Click Enter.
b. When prompted, apply 5 V or 20 mA using the appropriate equipment. Click
Enter.
Result: The AI calibration and its results are displayed. The AI values are
redisplayed.
2-59
Operation
Performing ACE1000 AO Operations

Follow this procedure to perform AO operations on an ACE1000 RTU using the hardware
test utility.
Important: Generally, I/Os are calibrated in the factory and should not be calibrated in the
field. Calibration should only be performed on the advice of service personnel.
Procedure 1-48 Performing ACE1000 AO Operations
Test Utility.

Result: The AO values from the Output module (if such exists) are displayed.
3. To set an AO value, do the following:

a. At the next Enter the function number prompt, enter the function number
for the corresponding AO set function (Set AOx) from the displayed list. Click
Enter.
b. Enter the AO value. Click Enter.
c. Repeat this step as many times as required.
4. To calibrate a specific AO, do the following

a. Attach the multimeter/test equipment to pins 7 and 8 for voltage, or to pins 9
and 10 for current.
b. At the next Enter the function number prompt, enter the function number
for the corresponding AO calibration function (Calibrate AOx) from the
displayed list. Click Enter.
c. When prompted, enter the AO mode number (2=0 to +20 mA, 3=4 to +20
mA, 5=0 to +10 V). Click Enter.
d. When prompted for the AO low value, enter the value displayed on the
multimeter. Click Enter.
e. When prompted for the AO high value, enter the value displayed on the
multimeter. Click Enter.
Result: The AO calibration its results are displayed. The AO values are
redisplayed.
f. Repeat the calibration as many times as required.

2-60
Operation
Performing ACE1000 Power Management Operations

Follow this procedure to set the power management profile or clock frequency or to reset
the microcontroller on an ACE1100 FEP/ACE1000 RTU using the hardware test utility.
Note: The current clock frequency and power management profile retrieved with the unit’s
General Information (Function #1). See Retrieving ACE1000 General Information.
Procedure 1-49 Performing ACE1000 Power Management Operations


Result: The power management profile and clock frequency are displayed.
3. At the next Enter the function number prompt, enter the preferred function
from Table 1-4. Click Enter.
Table 1-4 ACE1000 Hardware Test Power Management and Clock Frequency Functions

1 Set Power Management Profile
2 Set Clock Frequency to 300 MHz.
3 Set Clock Frequency to 600 MHz
4 Reset Kinetis Main Board
5 Reset Kinetis Exp1 Input Board
6 Reset Kinetis Exp1 Input Board
88 Main Menu
99 Exit
4. If you are prompted to select a power management profile, enter the number
from Table 1-5 and click Enter. After the message appears that the profile was
set, restart the unit.
Table 1-5 ACE1000 Hardware Test Power Management Profiles
Name Configura Eth CAN SD WLAN OTG HOST URT1 URT3 URT5 WAN
tion
0) ltr-non1 Minimum N Y N N N N Y N N N
1) ltr-non2 Basic Y Y Y N Y Y Y N N N
2) ltr-non3 Basic Y Y N N Y Y Y N N N
IRM
2-61
Operation
Name Configura Eth CAN SD WLAN OTG HOST URT1 URT3 URT5 WAN
tion
3) ltr-ser1 Full + RS Y Y Y Y Y Y Y Y Y N
Option
Board +
LAN
4) ltr-ser2 Full IRM Y Y Y Y Y Y Y Y Y N

+ RS
Option
Board
5) ltr-ser3 Basic + Y Y N N Y Y Y Y Y N
RS Option
Board
6) ltr-gri1 Minimum Y Y N N N N Y N N N
+ LAN
7) ltr-gri2 Full + w/o N Y Y Y Y Y Y Y Y N

LAN
8) ltr-gri3 Minimum Y Y N N N N Y Y Y N
+ RS
Option
Board +
LAN
9) ltr-lan2 Minimum N Y N N N N Y Y Y N
+ RS
Option
Board
11) ltr- Minimum N Y N N Y Y Y Y Y N

wan2 + RS
Option
Board +
USB
12) ltr- Minimum N Y N N Y Y Y N N N

wan3 + USB
5. If you chose to set the clock frequency, after the message appears that the
frequency was set, restart the unit.
Testing ACE1000 LEDs

Follow this procedure to test LEDs using the hardware test utility on an ACE1100 FEP/
ACE1000 RTU.
2-62
Operation
Procedure 1-50 Testing ACE1000 LEDs

3. At the next Enter the function number prompt, do one of the following and
click Enter:
• To select the main board, enter 1.
• To select the first I/O module, enter 2.
• To select the first I/O module, enter 3.
Result: The LEDs on the selected board are turned on for a short period of
time.
Testing ACE1000 Service Mode

Follow this procedure to test/set service mode from the hardware test utility on an
ACE1100 FEP/ACE1000 RTU. Operations such as I/O calibration must always be
performed in service mode to avoid interference with the RTU application.
Procedure 1-51 Testing ACE1000 Service Mode

3. At the next Enter the function number prompt, enter 2. Click Enter.
Result: The current service mode state is displayed.
Table 1-6 ACE1000 Hardware Test Service Mode Functions

1 Enter Service Mode.
2 Exit Service Mode.
3 Get Service Mode.
88 Main Menu
99 Exit

2-63
Operation
Testing ACE1000 Auxiliary Power

Follow this procedure to set the auxiliary power on an ACE1100 FEP/ACE1000 RTU
using the hardware test utility.
Note: This option is not available in a unit with no plug-in installed.
Procedure 1-52 Testing ACE1000 Auxiliary Power

3. At the next Enter the function number prompt, enter 3. Click Enter.
Result: The current service mode state is displayed.
Table 1-7 ACE1000 Hardware Test Auxiliary Power Settings

1 Set AUX Power OFF
2 Set AUX Power 5V
3 Set AUX Power 7.5V
4 Set AUX Power 9.5V
5 Set AUX Power 12V
6 Set AUX Power VIN ON
88 Main Menu
99 Exit
Updating the Kinetis Microcontroller Firmware

Follow this procedure to update the Kinetis Microcontroller Firmware on an ACE1100
FEP/ACE1000 RTU.
Procedure 1-53 Updating the Kinetis Microcontroller Firmware
1. Use SCP/WINSCP to log in to the unit as terminal login user. See the
credentials in Table G-2.
2. Navigate to the /home/acelogin folder.
2-64
Operation
3. Upload the updated Kinetis firmware file (e.g.

k10proj_D01_99_<version>_boot.hex) from your PC to the unit.
4. Log in to the unit as root, using the admin password listed in Table G-1Error!
Reference source not found..
5. Run: ltr_hwclient n
6. Wait 15 seconds for the unit to enter service mode.
7. Run the command: Bootloader.sh <FileName> <Board>,

where <FileName> is the Kinetis firmware file you copied to the board and
<Board> is one of 0=Main, 1=FirstExpansion, or 2=SecondExpansion.
8. Run: ltr_hwclient v to exit service mode.
ACE1000-IRM Configuration
This section guides you through the configuration of IRM server and IRM units in
ASTRO, MotoTRBO Connect Plus, and MotoTRBO Conventional infrastructures.
For IRM parameters, see “IRM Application Parameters” in the Appendix A of IRM1500
Easy Configurator User Guide.
In this document, other sections relevant for IRM configuration are:
• “ACE1000 Troubleshooting”
• Appendix B: “ACE1000 Easy Configurator Icons”
• Appendix D: “ACE1000 Use Cases”
• Appendix G: “ACE1000 Credentials”
Also, refer to the IRM1500 Intelligent Radio Modem System Planner for more information.
ACE1000-IRM Product Overview

ACE1000-IRM is an Intelligent Radio Modem (IRM), used in SCADA systems, for data
communication from substations and other distribution system sites over LMR (ASTRO
P25, MotoTRBO) infrastructure. Using the ACE IRM unit, fixed grid assets (for example
Remote Terminal Units, intelligent electronic devices, capacitor banks) can connect
wirelessly to the SCADA application server.
The ACE1000-IRM unit is a low-cost option which can be incorporated into existing
SCADA systems to enable replacement of leased or owned 4W lines, cellular 3G\4G
modules or private data radio systems while maintaining communication capabilities. The
ACE1000-IRM complements other Motorola SCADA solutions, such as the ACE3600
family of Remote Terminal Units (RTUs).
ACE1000-IRM
2-65
Operation
ACE1000-IRM transports incoming data from RS232/RS485 over the air, while utilizing
the LMR infrastructure (currently supported MOTOTRBO and ASTRO), to the IRM
server connected to the SCADA control center via LAN, and the other way around.
ACE1000-IRM functionality can be provided either using the IRM1500 dedicated HW

device, or as an IRM application running on ACE1000 RTU. For ACE1000-IRM device
support options, see ACE1000-IRM over ASTRO, ACE1000-IRM over MotoTRBO Connect
Plus, and ACE1000-IRM over MotoTRBO Conventional.
IRM Server
The IRM server acts as a terminal server, which represents each of the remote ACE IRM
units, as a serial port over IP and provides a two-way path to the communication system
and to remote ACE IRM units from the SCADA host entity.
ACE1000-IRM over ASTRO
Configuring IRM Server for ASTRO

Procedure 1-54 Configuring IRM Server for ASTRO
1. Log on to IRM server.
2. Perform one of the following actions:
• If you want to generate a new project, see Generating a New ACE1000

Project using the Project Wizard.
• If you want to generate a new project based on an existing project, see

Generating a New ACE1000 Project based on an Existing Project using
the Project Wizard.
3. Configure the project:
a) Enter the project name.
b) Select ASTRO.
c) Enter the number of the IRM units you want to add.
The system can include up to 24 IRM units. If you enter 0, you can add IRMs in
the next window.
4. Click Generate.
5. If you added 0 units in the previous window, in the IRM system view, from the
right-hand panel, select Add Units.
2-66
Operation
Click IRM, specify the number of units, and click OK.
6. Click the IRM Server to view configuration and configure the infrastructure on
the LAN port.
7. In the Main Board panel, click the LAN port and click the blue spanner icon.
Enter the data as required.
8. From the right hand panel, click Application.
9. Optional: Click NTP & GPS and configure the parameters. For details, see
Appendix A.
10. Optional: Click Time Zone and configure the parameters. For details, see
Appendix A.
11. In the system view, from the right-hand panel click Add Units. Select IRM and
specify the number of IRM units. Click OK.
You can add up to 24 IRM units.
2-67
Operation
You can also duplicate and remove IRM units as required.
12. In the system view, select each IRM client. Configure USB2 with RADIO APX
infrastructure and set port configuration with radio IP address.
13. Verify that RS-232 port is set as IRM on each IRM client.
The default port for IRM application is RS-232. You can remove it, drag and
drop the IRM application, and select RS-485.
14. Configure the application parameters by clicking Application → IRM

Application → Link. Configure the parameters as required by IRM server ID.
Configure the IRM Server IP Address.
Exporting Project Configuration

1. Access the IRM Server WEB interface.
2. In the systemroot, click Tools → Export Project Configuration.
Importing Project Configuration

1. On each IRM, log on to WEB interface of IRM while the unit is connected to
PC using an OTG cable (192.168.9.9).
2. Import the previously exported configuration. Click Tools → Import

Project Configuration.
3. Select the required IRMs and click OK.
Postrequisites: Log on to the IRM server and deploy the system

configuration:
1. Verify that the correct radio (with correct ID) is connected to specific
IRM client.
2. Deploy the IRM server.
3. Deploy the IRM units.
Configuring ACE1000-IRM Locally

Configure the IRM locally before the configuration and deployment from IRM Server.
Perform this procedure only if you choose not to export and import the configuration
and instead decide to configure each ACE1000-IRM unit locally after configuring the
IRM server.
1. Log on to ACE1000-IRM.
2. Click the USB2 spanner icon and configure the Radio IP address.
3. From General, configure the required IRM Site ID.
2-68
Operation
4. Click Application → IRM Application → Link. Configure IRM Server IP and

ID.
5. Deploy the configuration.
After deploying locally, you can perform remote deployment from IRM server.
ACE1000-IRM over MotoTRBO Connect Plus
Configuring IRM Server for MotoTRBO Connect Plus

Procedure 1-55 Configuring IRM Server for MotoTRBO Connect Plus


the Project Wizard.
d) Enter the project name.
e) Select MotoTRBO Connect Plus.
f) Enter the number of the IRM units you want to add.
The system can include up to 24 IRM units. If you enter 0, you can add IRMs in
the next window.
4. Click Generate.
2-69
Operation
the LAN port.
Enter the data as required.
Appendix A.
2-70
Operation
10. Click MDLC and configure the parameters. In the ETH1 tab, under Physical,
perform the following actions.
a) Enter your XRT Gateway IP Address.
b) Enter your XRT Gateway TCP port number.
c) Enter your XRT Client user name and password.
For details on MDLC parameters, see Appendix A.
11. If you need MDLC functionality over the IP port of the server, perform the
following actions:
a) Click Links and set the Number of link IDs to 2.
b) Go back to Advanced, select the second link, change the Link name to
LINE 2 and disable the Enable non-IP communication to XRT Gateway.
c) In the IRM Server Application, set the Number of slots for simultaneous
transmissions to 2 or more, depending on number of data channels.
12. Optional: Click Time Zone and configure the parameters. For details, see
Appendix A.
14. In the system view, select each IRM client. Verify that the Connect Plus radio is
assigned to the USB2 port and specify the radio ID in address configuration of
the USB2 port.
The information required is available from the XRC Users table.
16. Configure the application parameters by clicking Application → IRM


2-71
Operation

2. Import the previously exported configuration. Click Tools → Import

Project Configuration.
Postrequisites: Log on to the IRM server and deploy the system

configuration:
4. Verify that the correct radio (with correct ID) is connected to specific
IRM client.

Configure the ACE1000-IRM locally before the configuration and deployment from
IRM Server. Perform this procedure only if you choose not to export and import the
configuration and instead decide to configure each ACE1000-IRM unit locally after
configuring the IRM server.
1. Log on to ACE1000-IRM.
2. Delete the default ASTRO configuration by clicking USB and selecting the trash
icon.
3. Drag and drop the MOTOTRBO Connect Plus Radio infrastructure.
4. Click the spanner icon and configure the Radio ID.
6. Click Application → IRM Application. Configure IRM Server IP and ID.
ACE1000-IRM over MotoTRBO Conventional
Configuring IRM Server for MotoTRBO Conventional

Procedure 1-56 Configuring IRM Server for MotoTRBO Conventional.
2-72
Operation


the Project Wizard.
g) Enter the project name.
h) Select MotoTRBO Mobile infrastructure.
i) Enter the number of the IRM units you want to add.
The system can include up to 24 IRM units. If you enter 0, you can add IRMs in the next
window.
4. Click Generate.
the LAN port. Verify that IRM is configured to Site 1 and the USB2 port is set
with a MotoTRBO mobile radio.
a) Set the IP address of the radio according to its ID and CAI network.
b) Set the ETH1 IP Address, Network Mask, and Default Gateway as

required.
2-73
Operation
Appendix A.
2-74
Operation
11. In the system view, select each IRM client. Verify that the MotoTRBO (mobile)
radio is assigned to the USB2 port. Specify the IP address of the radio
according to the radio ID and CAI network as done in the IRM server.
13. If you want to configure the application parameters, click Application → IRM


2. Import the previously exported configuration. Click Tools → Import Project

Configuration.
Postrequisites: Log on to the IRM server and deploy the system configuration:
1. Verify that the correct radio (with correct ID) is connected to specific IRM
client.

Configure the IRM locally before the configuration and deployment from IRM
Server. Perform this procedure only if you choose not to export and import the
configuration and instead decide to configure each IRM unit locally after configuring
the IRM server.
1. Log on to IRM.
2. Delete the default ASTRO configuration by clicking USB and selecting the trash
icon.
3. Drag and drop the MOTOTRBO Conventional Radio infrastructure.
4. Click the spanner icon and configure the Radio ID.
2-75
Operation
6. Click Application → IRM Application. Configure IRM Server IP and ID.
2-76
ACELogic
© 2016 Motorola Solutions, Inc. All rights reserved

ACELogic Overview
ACELogic Overview
ACELogic is a user-friendly interface that allows users to create a control program for the ACE1000
RTU by defining chains of conditional statements, called rules.
Rules link devices controlled by the RTU according to this pattern: “When this happens – Do this”,
where some type of event in one device can trigger an action in another (or the same) device.
Rules consist of two elements: a Trigger (“When this happens”) and an Action (“Do this”) – for
example, when a tank has reached the “full” level - close the supply valve.
To make rules easier to create and manage, devices or collections of sensors or actuators in the
system are organized into logical entities with their own states and actions. Users can create entities
and name them to reflect the actual devices in their system. Users can edit the labels of states and
actions of the entities so as to adjust them to the actual occurrences in the system.
Each state and action is then mapped to a physical sensor or actuator controlled by the RTU, or an
internal indicator. Because of that, ACELogic can be applied to different purpose systems in various
environments and the user-configured rules can still adequately describe the system. To continue the
previous example, the following entities will be defined for the system:
Entity
Tank
State
Full/Not full
Mapping
RTU 100, Digital Input 1
Entity
Supply valve
Action
Close/Open
Mapping
RTU 100, Digital Output 2
Physical and logical layers are separated, so the user who defines system behavior does not need to
have extensive knowledge of the system physical layer. The users of ACELogic are only expected to
have the knowledge of the context for the rules they want to create.
Another important factor for a user of ACELogic is that it makes the creation of rules much more
efficient. A user can add the rules he creates to all entities of the same type across the system.
Multiple sub-entities can be created under all entities of a given type by performing only one action.
Entities can be duplicated, generating a specified number of instances of the same type. After logging
to FEP, a user can make system-wide changes to all RTUs. For example, if there is an entity called
Room on more than one RTU, by adding a sub-entity under one instance of Room sub-entities of this
type are added to all Room entities in the system.
The friendly user interface and an inbuilt easy logic application makes Easy Rules an effective tool to
handle local control logic and notifications on ACE1000 mid-tier controllers for a user with little or no
programming knowledge.
Configuring RTU Control Program

Follow this process to configure the RTU using the Easy Rules.
Prerequisites: Define the physical layer of the system. See "Building an ACE1000 System".
Send Feedback 3
ACELogic Overview
Process:
1 Perform one of the following actions:
• If you want to work on local configuration, log on to the RTU.
• If you want to work on the system-wide view, log on the FEP and select the RTU to run the
control program.
2 Switch to the logical view by clicking Logical.
3 Define logical entities in the system. See Creating Entities on page 6.
4 Define states and actions for each entity. See State and Action Types on page 11.
5 Switch to the summary view and update the I/O links. See Accessing Physical I/O Parameters
Summary View on page 41.
6 Define rules. Creating Rules on page 21.
7 Save and deploy the configuration. See "Deploying an ACE1000 System from the PC".
System Capacity
The following data present the system capacity.
Maximum entities in RTU
100
Maximum rules in RTU
20
Maximum actions and states in RTU
50
Maximum entities in system
1000
4 Send Feedback
Operations on Entities
Entities within ACELogic are virtual representations of logical components. You can create rules for
entities to manage the behavior of entities. Programming the entities on the logical level is separated
from I/O allocation on the physical level, which makes the maintenance of entities much easier.
Entities appear on a tree structure within the application. You can:
• browse the structure of entities and edit it by adding and deleting entities
• create new entities of the same type and new types of entities
• modify existing entities.
The purpose of the entity structure is to make it easier for the user to manage the components of the
system and apply rules for the entities to behave in a specified way. UI elements are intuitive and easy
to use. Entities are created under all instances of the parent entity type across the system and can be
multiplied, which makes creating a logical structure efficient and clear.
You can log on either to FEP or to RTU. After you log on to FEP, the system view is available – it gives
you the possibility of making system-wide changes and applying them to all entities of the same type
across the system. Rules that you define include only states and actions from the site on which the rule
is run.
After you log on to a specific RTU, changes are applied to one site only, without affecting the entities
from other sites.
The following figure presents the Entities view:
Figure 1: Entities View UI Elements
1. Entities Tree
Shows the hierarchy of the entities in your system. You can expand and collapse the structure.
In the RTU view, the entities that belong to the given RTU appear under the All node. In the
System view, entities appear under the names of respective sites.
2. New Entity Tile
A blank tile for adding new entities.
3. Rules for This Entity
Shows how many rules are defined for a given entity. You can click it to view the summary of the
rules.
4. Add Rule Button
You can click this button to go to the rule creation screen.
5. More Options Button
You can click this button to delete, edit, or clone a given entity.
Send Feedback 5
6. Existing Entity Tile

The tile that represents an entity that is already added to the system.
7. Entity Search Bar
You can search for entities by their name. As you type, options filtered by your keywords appear.
8. Entity Sort Button
You can sort your entities alphabetically from A to Z or from Z to A.
Creating Entities
You can create entities of a new or existing type. If you choose to create an entity of a new type, the
type itself is created and saved. The new entity type name must be unique across the system.
If you create an entity of an existing type, it inherits all the sub-entities and rules defined for the entity
type.
Procedure:
2 From the left-hand panel tree, click the level on which you want to create the entity.
3 In the Entities pane, click the new entity tile with a large + icon.
The following tile appears:
Figure 2: New Entity Tile
4 In the new entity tile, specify the type for the new entity by performing one of the following
actions:
• If you want to create an entity of a new type, in the Entity Type field, enter the name of the
new type.
• If you want to create an entity of an existing type, in the Entity Type field, enter the type or
select it from the list.
You can use up to 15 characters. The type can include uppercase and lowercase letters,
numbers, and the following special characters: `!@_$^{}[]()
If you are creating an entity of an existing type, it inherits all sub-entities, actions, states, and
rules specified for the given type. The tool automatically allocates the next free I/Os (if available)
to the new entity actions and states.
5 In the Entity name field, enter the name for the entity.
You can use up to 15 characters. The name can include uppercase and lowercase letters,
The default, auto-generated name is a respective sequential number.
6 Optional: If you want to add remarks to the entity, in the Notes field, enter the notes.
6 Send Feedback
You can use up to 30 characters. The description can include uppercase and lowercase letters,
numbers, and the following special characters: ,`!@#$%^*{}[]_
7 Click the Add button.
If you are adding this entity under a parent entity of a given type, a pop-up message appears
asking you to either confirm the update on all entities of this type or change the type only in this
instance of the parent entity.
8 If the Do you wish to update the type <name> prompt appears, perform one of the
following actions:
• If you want to add the entity under all entities of the parent entity type, select the Yes, add
the entity to all <Type> radio button and click OK.
• If you want to add the entity only in this instance of the parent entity type, select the No,
change only <Type> type to radio button and in the entity type name field, enter the new
type name. Click OK.
The entity you created appears as a new node in the entities tree and as a new tile in the main pane
under its parent entity .
Postrequisites: If you performed this procedure as a part of the RTU control program configuration,
go back to Configuring RTU Control Program on page 3.
Cloning Entities
You can duplicate the entities in your system. During one cloning operation, you can create multiple
clones of the same entity type at a selected location.The cloned entities inherit all sub-entities, actions,
states, and rules specified for the given type. The tool automatically allocates the next free I/Os (if
available) to the new entity actions and states.
Procedure:
2 From the left-hand panel tree, click the level on which the entity you want to clone is located.
3 On the tile of the entity you want clone, click the icon and from the additional elements, click
the clone button .

The Duplicate <Entity name> window opens.
Send Feedback 7
Figure 3: Duplicate Entity Window
4 In the Duplicate window, select the location and number of the entities you want to create. Click
Duplicate.
If you are adding this entity under a parent entity of a given type, a pop-up message appears
asking you to either confirm the update on all entities of this type or change the type only in this
instance of the parent entity.
following actions:
• If you want to add the entity under all entities of the parent entity type, select the Yes, add
the entity to all <Type> radio button and click OK.
• If you want to add the entity only in this instance of the parent entity type, select the No,
The entities you created appear at the selected location. Their names have a _<number> suffix added
to the original name. If the entity you cloned has sub-entities, the clones have parallel sub-entities.
Postrequisites: If required, edit the names of the cloned entities. See Editing Entities on page 8.
Editing Entities
Follow this procedure to edit existing entities.
Procedure:
2 From the left-hand panel tree, click the level on which the entity you want to edit is located.
3 On the tile of the entity you want edit, click the button and from the additional elements, click
the edit button .

4 Update the entity name and notes as required.
8 Send Feedback
5 Click the Update button.
Deleting Entities
You can delete the entities in the system.
Procedure:
2 From the left-hand panel tree, click the level on which the entity you want to delete is located.
3 On the tile of the entity you want delete, click the button and from the additional elements,
click the delete button .

If you are deleting an entity under a parent entity of a given type, a window appears asking you
to either confirm the update on all entities of this type or change the parent entity type.
4 If the Are you sure you want to delete <name> prompt appears, perform one of the
following actions:
• If you want to delete the entity from all entities of the parent entity type, select the Yes,
delete <name> to all entities with type <Type> radio button and click OK.
• If you want to delete the entity only in this instance of the parent entity type, select the No,
The entities are deleted as specified.
Searching for Entities by Name

You can search for specific entities by looking up their names.
Procedure:
2 In the left-hand panel, click the search icon .

3 In the search field that appears, enter your keywords.
4 From the list of entities, select the one for which you want to perform an action.
Send Feedback 9
10 Send Feedback
State and Action Types

You can configure states and actions for your defined entities.
Entity states
Entity states are derived from inputs (measurement or event detections) of one or more sensors
that comprise the entity, and reflect the semantic meaning of the measurement. Changes in
measurement or detection of an event may cause a state transition of the entity.
Entity actions
Entity actions are controls that trigger one of the actuators that comprise the entity (and, in addition,
optionally set the data to be applied by the actuator).
State and Action I/O Links

All states and actions are mapped to the RTU physical layer via I/O link configuration. When you add
states or actions, they are automatically mapped to the next free I/O link. The user can modify the
mapping.
The following I/O link types are supported:
• Basic I/O
• Value
• Flag
A flag and a value appear as a state and as an action.
On adding a digital output action, a back indication for that action is automatically added as a state.
Action and state names can be up to 20 characters long. They can include uppercase and lowercase
letters, numbers, and the following special characters: ,`!@#$%^*{}[]_
Basic I/O
Digital Input (DI)
A physical (read only) digital input in one of the RTU I/O modules.
Scaled Analog Input (AI)
A physical (read only) analog input value on one of the RTU I/O modules scaled to Engineering
Units. For scaling, see "AI Parameters".
Digital Output (DO)
A physical (write only) digital output in one of the RTU I/O modules.
Digital Output back indication (DO BI)
A back indication of one of the physical digital outputs in one of the RTU I/O modules (read only).
Scaled Analog Output (AO)
A physical (write only) analog output value scaled to Engineering Units to be sent to one of the RTU
I/O modules. For scaling, see "AI Parameters".
Send Feedback 11
Figure 4: Basic I/O – Available States
Figure 5: Basic I/O – Available Actions
To set a Basic I/O as your state or action, see Creating Basic I/O States and Actions on page 13.
Value
Long Value
In memory, (read\write) long integer variable in the range of -2147483648 to +2147483647.
Float Value
In memory, (read\write) floating point variable in the range of -3.4e+38 to 3.4e+38.
To set Value as your state or action, see Creating Value States and Actions on page 15.
Flag
In memory, (read\write) boolean variable that has a value of TRUE or FALSE.
Entity State Types

The following list presents the available state types.
Basic I/O DI
Used when the state reflects whether something in the physical world is on or off, active or inactive.
For example: door open or closed, panic button pressed or not pressed, and so on.
12 Send Feedback
Basic I/O AI
Used when the state reflects an actual sensed or measured quantity such as temperature, humidity,
and so on.
Basic I/O DO BI
Used when the state reflects an execution status of a control. A state of this type is automatically
created when an action that is linked to a physical digital output is created.
Value
Used when the state of the entity is derived logically from other states through rules, or set by the
SCADA center through a communication system. Value states enable the user to define more
complex monitoring and control programs.
Flag
Used when the state of the entity is derived logically from other states through rules, or set by the
SCADA center through communication system. Flag states enable the user to define more complex
monitoring and control programs.
Entity Action Types

The following list presents the available action types.
Basic I/O DO
Used when the action controls whether something in the physical world should be on or off, active
or inactive. For example: open or close a door, turn on or turn off a light, and so on.
Basic I/O AO
Used when the action controls a quantity such as temperature, humidity, and so on.
Value
Used when the action controls or modifies an entity internal logically derived state or should serve
as a trigger event to another rule.
Flag
Used when the action controls or modifies an entity internal logically derived state or should serve
as a trigger event to another rule.
Creating Basic I/O States and Actions

Follow this procedure to set Basic I/O as a state or as an action.
Procedure:
1 In the rule view, decide whether you want to add a state or an action:
• If you are adding a state, on the Conditions tab, verify that you are in the States view and
click the plus button.
• If you are adding an action, click the Actions tab and click the plus button.
2 In the pop-up that opens, perform the following actions:
a From the Type drop-down list, select Basic I/O.
Send Feedback 13
Figure 6: Add State Window – Analog I/O
b From the State drop-down list, select one of the digital or analog states.
The digital states appear in pairs at the top of the drop-down list. The analog states appear
as a list of separate items below the digital states.
Select the state whose icon matches the behavior of your entity.
c In the Show as field (analog state) or fields (digital state), enter the text you want to appear
as a state label.
The text you enter in the label appears in your states and actions, as well as in the rules
created using those states and actions.
You can change the label freely to accurately describe the state behavior. For example, if
your entity is a water sprinkler, you can change the ON/OFF labels to sprinkle/stop
sprinkling.
d In the Parameters section, in the RTU Name field, verify that the default name is correct (the
same name that is assigned to the RTU).
e In the I/O Link drop-down list, verify if the default I/O link is correct (the appropriate sensor is
connected to this I/O). If not, from the drop-down list, select a different I/O link.
Below the I/O Link field, the relevant I/O module name and I/O user connection information
appears.
f If you want to change the default I/O logical name, in the I/O Logical Name modify the
default value.
The default name has the following structure: <X><Z>_<label>, where <X> is the first letter
of the entity type, <Z> is the first letter of the entity instance name, and <label> is a state or
action label.
g Optional: If you want to modify physical I/O parameters, next to Physical I/O
Parameters, click Edit.
Physical I/O parameters available are dependent on the I/O link selected.
14 Send Feedback
h Click the Add button.

If you are adding a digital I/O action, its equivalent is created in states as a back indication. Its
default name is <ActionName>_BI.
Creating Value States and Actions

Follow this procedure to create a Value state and its parallel Value action.
Procedure:
1 In the rule view, decide whether you want to add a state or an action:
• If you are adding a state, on the Conditions tab, verify that you are in the States view and
click the plus button.
• If you are adding an action, click the Actions tab and click the plus button.
2 In the window that opens, perform the following actions:
a From the Type drop-down list, select Value.
Figure 7: Add State Window – Value
b In the Show as field, enter the text you want to appear as the value label.
c In the Parameters section, from the Data Type drop-down list, select the data type.
Data types available are Long and Float.
d Click the Add button.
The value field appears on both Conditions and Actions tabs. The tool automatically allocates
the next free index in the relevant user data table. For checking the allocated index, see I/O Link
Creating Flag States and Actions

Follow this procedure to create a Flag state and its parallel Flag action.
Send Feedback 15
Procedure:
1 In the rule view, on the Conditions or Actions tab, click the plus button.
2 In the window that opens, perform the following actions:
a From the Type drop-down list, select Flag.
Figure 8: Add State Window – Flag
b In the Show as field, enter the text you want to appear as the flag label.
c Click the Add button.
The flag field appears on both Conditions and Actions tabs. The tool automatically allocates
the next free index in the relevant user data table. For checking the allocated index, see I/O Link
Editing States and Actions

Follow this procedure to edit states or actions for existing rules.
Procedure:
1 In the rule view, from the left-hand panel tree, select the entity whose states or actions you want
to edit.
2 In the right corner of the state or action, click the pencil icon.
3 In the Update Action or Update State screen, update the relevant fields.
4 Click OK.
All rules that contain the modified action or state are updated automatically.
16 Send Feedback
Deleting States and Actions

Follow this procedure to delete states and actions.
Procedure:
1 In the rule view, from the left-hand panel tree, select the entity whose states or actions you want
to delete
2 In the right corner of the state or action, click the pencil icon.
A window appears asking if you want to delete the state\action from all entities of this type or
delete it only from the current entity instance.
3 Select one of the options and click Delete.
All rules that contain the modified action\state are automatically deleted. A prompt with confirmation for
the rules to be deleted appears.
When you delete a BI state, the corresponding BI action is deleted as well (and the other way around).
Send Feedback 17
18 Send Feedback
Rule Creation
Rule Creation
The purpose of ACELogic is to provide non-code-writers both the ability and the flexibility to use the
sensors in the system and to best meet the customers' needs.
Rules are combinations of defined conditions and actions. The actions you set take place after
conditions are satisfied. The following figure shows the rule configuration window.
Figure 9: New Rule Window – UI Elements
1. Rule Name Field

You can enter text that appears as the rule name. You can use up to 40 characters. The name can
include uppercase and lowercase letters, numbers, and the following special characters: `!@_$^{}
[]()
2. Active/Inactive Switch
You can disable a rule if you do not want it executed. The default setting for new rules is Active.
3. Entities Tree
Shows the hierarchy of the entities in your system. You can expand and collapse the structure.
In the RTU view, the entities that belong to the given RTU appear under the All node. In the
System view, entities appear under the names of respective sites.
4. Conditions Tab
In this tab, you can define conditions for your rules. Conditions can be based on states or time. All
states of the selected entity appear on the Conditions tab. You can use the states to define the
condition of the rule.
5. Actions Tab
In this tab, you can define actions for your rules. Actions define how the system behaves once the
condition is satisfied. All actions of the selected entity appear on the Actions tab. You can use
actions to define how the system behaves once the condition is satisfied.
6. States View
In the States view, you can define states for the selected entity to use them in your rules. For state
types, see State and Action Types on page 11.
Send Feedback 19
Rule Creation
7. Time View
In the Time view, you can create time conditions for your rules. Time conditions allow you to
schedule the actions in your rule. Your scheduled actions can occur at a given time or repeat
periodically. For time, see Time as a Condition on page 26.
8. Digital State
A digital state area divided into digital state options, including buttons for each state option.
9. Add Digital State Button
You can click one of the digital state options to use it in a rule condition.
10. Analog State
An analog state area divided into analog state options, including the condition and modifier drop-
down lists and the value field or fields.
11. Condition Drop-Down List
You can choose one of the three ways in which the conditions are satisfied. The is option makes
the condition true as long as the given state is maintained. The Changed to option activates the
action after the state changes to the specified value or range. In the Changes option, the condition
is satisfied via any change in and out of the defined value or range.
12. Modifier and Value Fields
In these fields, you can set the value (=) or a range (<, <=, >, >=, between) for the analog state
used in the condition.
13. Add Button
Using this button, you can add a new state or action, depending on the view you are in.
14. When This Happens Window
In this window, the state and time modifiers that constitute your condition appear. A rule is
dependent only on the conditions that appear in this window – the States and Time views are used
only for adding conditions to the When This Happens window.
You can also create complex conditions in this window, with two or more states or times dependent
on each other. See Figure 11: Complex Condition Example on page 22.
15. Condition Added to the Rule
A condition that you added to your rule appears in the When This Happens window. You can
double-click an item to edit it on textual level. If you hover your cursor over an item, an X delete
button appears on the right of the bar.
16. Do This Window
In this window, the actions that you added to your rule appear.
17. Action Added to the Rule
An action you added to the rule appears in the Do This window. You can double-click an item to
edit it on textual level. If you hover your cursor over an item, an X delete button appears on the right
of the bar.
Rules View
In the Rules view, you can see a list of rules for the specific entity selected from the entity hierarchy.
20 Send Feedback
Rule Creation
Figure 10: Rules View Example
You can click on each rule name to display a given rule in detail in the view below. In the When This
Happens and Do This panes, the condition and action for the rule are available. If the condition or the
action is complex, the structure appears in full, similarly to the rule creation window.
You can edit your rules and activate or deactivate them.
You can also delete your rules. See Deleting Rules on page 37.
You can also go to the rule creation using the Add Rule button.
Creating Rules
Follow this process to define rules for the entities in your system.
There are two types of conditions: states and time. If a rule is dependent on a state, it is triggered by
occurrences and changes happening in the system. If a rule has a time condition, it is triggered at a
specified point in time, once or recurrently.
NOTICE: Once you know the states and actions configured in your system, you can add them
to your rule using the auto-complete functionality. See Using the Auto-Complete Functionality
for Conditions and Actions on page 26.
Prerequisites: Predefine states and actions for your entities so that you can add them to your rule. For
adding states and actions, see State and Action Types on page 11. For adding time, see Time as a
Condition on page 26.
Procedure:
1 In the left-hand panel tree, select the entity you want to add rules to.
2 In the main pane, select the Rules view.
3 From the top right corner, click the Add Rule button.
4 In the rule creation screen, in the Rule Name field, enter the name for your rule.
You can use up to 40 characters. The name can include uppercase and lowercase letters,
5 Optional: If you want your rule always executed, do not add any conditions and proceed on to
step 9.
Send Feedback 21
Rule Creation
6 Add conditions to your rule. Depending on the kind of conditions you want to add, follow one or
more of the following procedures:
• If you are adding a digital state, see Adding Digital States to Rules on page 25.
• If you are adding an analog state or a value state, see Adding Analog States or Value States
to Rules on page 25.
• If you are adding a flag state, Adding Flag States to Rules on page 25.
• If you want to set a time condition, see Setting Recurrent Time on page 27 or Setting Non-
Recurrent Time on page 29.
7 If you want to use the states predefined for physical entities, perform the following steps:
a In the left-hand panel, select the Physical view.
b Select the entity whose states you want to display.
c Add the predefined states as conditions. See step 6.
8 If you added more than one state and you want to create a complex condition, in the When This
Happens window, perform one or more of the following steps as required:
• If you want to push an existing condition one level down on the tree, select a node and click
the indent icon .
• If you want to push an existing condition one level up on the tree, select a node and click the
outdent icon .
• If you want to delete a condition, hover your cursor over the condition and click the X button
that appears.
• If you want to add persistence for a condition, select a node and click .
NOTICE:
If you add persistence in a condition that uses the is option, the action occurs after
the state persistence time and keeps on occurring as long as the state is fulfilled.
If you add persistence in a condition that uses the Changes to or Changes option,
the action occurs only after a change of state and the persistence time.
• If you want to indent or outdent more than one condition, hold CTRL and click the nodes you
want to select. Perform the action.
• If you want to swap the AND modifier for OR (or the other way around), click the modifier
icon.
Thanks to the complex condition functionality, you can create any logical expression that you
need for your system.
The following figure presents an example of a complex condition:
Figure 11: Complex Condition Example
9 Add actions to your rule. Depending on the kind of action you want to add, perform one or more
of the following steps:
• If you are adding a digital action or a flag action, on the Actions tab, in your action field, click
the preferred action value.
22 Send Feedback
Rule Creation
• If you are adding an analog action or a value action, in the value field, enter the preferred
action value.
Your action appears in the Do This pane.
10 If you want to implement sequence to your actions, perform the following steps:
a Click the icon.

The action fields change.
b For each of your actions, in the After fields, specify the delay in seconds, minutes, or hours.
The range is up to 24 hours.
Setting 0 means no delay.
c From the drop-down list for each action, select when you want the delay for the action to
start.
The following delay options are available:
From Beginning
The time interval between the moment when the condition becomes true and the execution of the
current action.
From Start of last action
The time interval between the moment when the previous action is scheduled to start and the
execution of the current action.
From End of last action
The time interval between the moment when the previous action ends and the execution of the
current action.
d For digital actions, in the For fields, specify the duration in seconds, minutes, or hours.
The duration range is up to 24 hours. After the duration period, the opposite action is
executed.
NOTICE:
In this case, the action is not refreshed when reset manually.
An action with a configured duration does not delay the evaluation of other rules.
Step example:
Figure 12: Sequence for Analog Action – Example
Figure 13: Sequence for Digital Action – Example
11 If you created a sequence and want to add recurrence to your digital actions, perform the
following steps:
a Click the icon.

The following field appears for your digital actions:
Send Feedback 23
Rule Creation
Figure 14: Repeat Field Example
b From the Repeat fields, select how many times you want the action repeated.
c From the Intervals fields, select the interval between each repetition in seconds, minutes, or
hours.
Repeat and interval values are available only if the digital action includes time.
The interval range is up to 24 hours. Setting 0 means that the action is repeated as soon as it
finishes.
NOTICE: The action is repeated the specified number of times each time the
sequence is triggered. While the sequence is running, the condition is not evaluated.
The interval timer is started once the action ends. The delay setting applies only for
the first execution of the action. In the repetitions that follow, only the interval time
applies.
12 If you created a sequence and want to add recurrence to the entire sequence, perform the
following steps:
a Click the icon.

b From the Repeat fields, select how many times you want your sequence to repeat.
• If you want your sequence to repeat for a specified number of times, from the drop-down
list select Times and enter the number of repetitions.
• If you want your sequence to repeat indefinitely, from the drop-down list select Forever.
Select this option if you want the sequence repeated in an infinite loop once the condition
is satisfied. The condition is not re-evaluated again.
c From the Intervals fields, select the interval between each repetition of the sequence in
seconds, minutes, or hours.
The interval range is up to 24 hours. Setting 0 means that the sequence is repeated as soon
as it finishes.
NOTICE:
While the sequence is being executed, the condition is not evaluated.
Ignoring conditions when sequence is running means that COS in the condition side is
ignored.
A sequence can be defined for any simple or complex condition with I/O, time, user flag
\value, or always.
13 In the rule window, click OK.
The tool automatically identifies the entity to have the new rule allocated.
If there are more entities of the same type as the one to which you are adding a rule, a prompt
appears asking you to choose whether you want to add the rule to all entities of this type or
change the entity type only in this instance.
following steps:
• If you want to add the rule to all entities of the parent entity type, select the Yes, add my new
rule to all <Type> radio button and click OK.
24 Send Feedback
Rule Creation
• If you want to add the rule only in this instance of the parent entity type, select the No,
change only <name> type to radio button and in the entity type name field, enter the new
Adding Digital States to Rules

Follow this procedure to add a digital state to a rule.
Prerequisites: In the main pane, select the Rules view.
Procedure:
On the Conditions tab, in the States view, in your digital state field, perform one of the following
actions:
• If you want your condition to be fulfilled as long as your state has one of the digital values,
from the drop-down list select is and click the preferred state value.
• If you want your condition to be fulfilled when your state changes to one of the digital values,
from the drop-down list select Changes to and click the preferred state.
• If you want your condition to be fulfilled when any change of the digital state occurs, from the
drop-down list, select Changes and click the merged state field.
Your condition appears in the When This Happens pane.
Adding Analog States or Value States to Rules

Perform this procedure to add an analog state or a value states to your rule.
Procedure:
1 On the Conditions tab, click the States view.
2 In your state field, in the first drop-down list, perform one of the following steps:
• If you want your condition to be fulfilled as long as your state equals the specific value or is
within a specific range, select is.
• If you want your condition to be fulfilled when your state changes to the specified value or
range, select Changes to.
• If you want your condition to be fulfilled when a change of the value occurs (for states with =)
or when the actual value goes in or out of the specified range (for states with <, <=, >, >=,
between), select Changes.
3 From the second drop-down list, select the modifier for your condition.
The available modifiers are: <, <=, >, >=, =, and between.
4 In the value field or fields, enter the value.
Adding Flag States to Rules

Follow this procedure to add a flag state to a rule.
Send Feedback 25
Rule Creation
Procedure:
1 On the Conditions tab, click the States view.
2 In your flag field, perform one of the following steps:
• If you want your condition to be fulfilled as long as your flag is true or false, from the drop-
down list, select is and click True or False.
• If you want your condition to be fulfilled when your flag changes to true or false, from the
drop-down list, select Changes to and click True or False.
• If you want your condition to be fulfilled when there is any change of the flag, from the drop-
down list, select Changes and click the merged field.
Using the Auto-Complete Functionality for Conditions and

Actions
You can simplify adding conditions and actions to your rules by using the auto-complete functionality.
The functionality allows you to add conditions and actions easier and faster by using only your
keyboard.The auto-complete option makes the entities, actions, and states in the system easily
available without the user needing to know them. You do not have to browse the system entities to see
the relevant action or a state – you can just type in the beginning and move down the list using the
arrow buttons to select it.
Prerequisites: Define the states and actions you want to reuse.
Procedure:
1 In the When This Happens or Do This window, in the bottom left corner, click the plus button.
An empty field for the new condition or action appears.
2 Start typing the text of a condition or action that exists in the system.
Condition text usually starts with the entity name, for example Door 1 is opened. Action text
usually starts with the action, for example Open Door 2.
Conditions or actions that match the text you typed in appear as a list.
3 Using the up and down arrow keyboard buttons or a TAB button (scrolling down), select the
condition or action you want to use. Press ENTER.
The new condition or action appears in the When This Happens or Do This window.
Time as a Condition
The actions that you create can be dependent not only on states but also on time. Time is a
functionality that you can use to schedule the actions in your system. You can schedule your actions
for specific points in time and make them recurrent or non-recurrent events. You can also schedule an
action to happen once within a period if a given state occurs within that period.
You can either use time as a condition independently of the used states or create more complex
conditions by combining states and time. For example, you can set an action to be triggered once a
day only if a given state condition is fulfilled.
You also have the option to set your rule to be executed always. To do that, create a rule with an
empty condition part.
26 Send Feedback
Rule Creation
Setting Recurrent Time

Follow this procedure to specify a recurrent point in time or a recurrent period as a condition in your
rule.
NOTICE: If you update the ACE1000 controller time to the time used in the condition, that
condition is not satisfied.
Procedure:
1 In the new rule window, on the Conditions tab, click Time.
2 From the left-hand panel, select the frequency.
The following frequencies are available:
• Daily
• Weekly
• Monthly
• Yearly
For the Once option, see Setting Non-Recurrent Time on page 29.
Figure 15: Setting Time – Yearly
3 Choose whether you want to set a point in time as your condition or a period of time in which the
condition can be fulfilled. Perform one of the following actions:
• If you want to set a point in time as the condition, click Time is and specify the hour.
The action based on this condition occurs at a specified minute on a specified day.
• If you want to set a period of time in which your condition can be fulfilled, click Time is
between and specify the starting and closing time.
Specifying a period of time as a condition means that your action happens once within that
period. For example, you can combine the time period condition with a state condition which,
Send Feedback 27
Rule Creation
if fulfilled in the period specified, triggers the action. You can use this option to specify a
period during which the condition may be satisfied. This option does not trigger the action at
the start of the period or stop the action at the period's end.
4 In the Repeat every field, enter the recurrence frequency in the specified unit.
This setting specifies the interval in days, weeks, months, or years, depending on the frequency
selection. The number you enter means the interval period in the given time unit (for example, 2
for repeating every two weeks and so on). If the user restarts the RTU, performs the deploy
action, or even changes the date on RTU, the condition is always evaluated against how long
passed since the set start date. If the modulo operation of the number of time units that passed
and the number of time units interval equals 0, the condition holds. Otherwise it is false.
5 Depending on your recurrence selection, perform one of the following actions:
If… Then…
If you selec- proceed to step 6.
ted Daily,
If you selec- in the Repeat on row, select the check boxes of the days of the week
ted Weekly, (from Monday to Sunday) on which you want your event to occur.
You can specify more than one day a week, up to seven days. If you do
not select any day, the Set Time button remains inactive.
If you selec- below the Repeat every field, make one of the following choices:
ted Monthly, • If you want the event to occur on a specific day of the month, select the
Day option and specify the date of the event, from 1st to 31st.
• If you want the event to occur on a specific instance of a day of the
week, select the Or option and from the drop down-lists, select the con-
secutive week and a day in a week (Monday to Sunday).
If you selec- below the Repeat every field, make one of the following choices:
ted Yearly, • If you want the event to occur on a specific day of the specific month,
select the Day In Month option and from the drop down-lists, select the
month and the day.
• If you want the event to occur on a specific day in a specific week of a
specific month, select the Or option and from the drop down-lists, select
the consecutive week, day of the week, and the month.
6 In the Start field, set the start date.

7 Using the End radio buttons, select the end for the period:
• If you want your rule to keep going with no definite end date, select Never.
• If you want your rule to stop after a defined number of occurrences, select after and enter the
number of occurrences after which the condition is to expire.
Here you can specify the number of times for the event. 0 means that no event is to take
place. 1 means one event and so on. In the case of weekly repetitions (only weekly
repetitions accept more than one event per week), the number means the number of events
and not the number of weeks.
The number does not mean actual events that occurred. It means the number of times they
were supposed to occur. Actual events are not counted and the number of events is not
saved in non-volatile memory before restart. The calculation is always the same regardless
of whether the user performs a restart or a deploy operation or changes the RTU date.
• If you want your rule to end on a specific date, select On and specify the condition end date.
28 Send Feedback
Rule Creation
This is an end date when all events stop. It includes the last event if one is supposed to occur
on this date. After current date is past the end date, no more events take place and all above
conditions are false.
8 Click Set Time.
Setting Non-Recurrent Time

Follow this procedure to set a non-recurrent time as a condition for your rule.
NOTICE: If you update the ACE1000 controller time to the time used in the condition, that
condition is not satisfied.
Procedure:
1 In the new rule window, on the Conditions tab, click Time.
2 In the left-hand panel, click Once.
Figure 16: Setting Time – Once
3 Choose whether you want to set a point in time as your condition or a period of time in which the
condition can be fulfilled. Perform one of the following actions:
• If you want to set a point in time as the condition, click Time is and specify the hour.
The action based on this condition occurs at a specified minute on a specified day.
• If you want to set a period of time in which your condition can be fulfilled, click Time is
between and specify the starting and closing time.
Specifying a period of time as a condition means that your action happens once within that
period. For example, you can combine the time period condition with a state condition which,
if fulfilled in the period specified, triggers the action. You can use this option to specify a
period during which the condition may be satisfied. This option does not trigger the action at
the start of the period or stop the action at the period's end.
4 In the On field, set the date.
NOTICE: If the condition has the is modifier, the condition qualifies if the start date is
current day and the time is current time (in minutes). In all other cases, the condition
does not qualify and no action is taken.
Send Feedback 29
Rule Creation
5 Click Set Time.
Notify Functionality
Users can notify the SCADA on state as a result of any condition. The conditions can be scheduled,
complex, or nested conditions that contain DIs, DOs, AIs, Values, and Flags, are based on is, change
of state, changes operators or the persistence parameter.
When using a notify action with a change of state condition, notification on existing value occurs once
when the change of state takes place.
When using a notify action with an is condition, notification on existing value occurs when the change
of state takes place, and notifications on every change in state value occur when condition is satisfied.
States on which user can notify the SCADA are the states that contain values (long and float) and
flags. The state must be defined by the user before it is used in the rule.
To enable the notify on states, you must update the following FEP-RTU Application parameters:
• Number of Bits values in User Table to sync
• Number of Floats values in User Table to sync
• Number of Longs values in User Table to sync
Notify on value and flags uses the parameters in the FEP-RTU configuration. This means that the user
data (long, float, and bits) are allocated sequentially in the next free index in the user data tables when
the maximum limit for notify index is specified in the configuration.
The notify option is used as an action in the rule. It can be part of a sequence or not. The notify action
has the recurrence option (the notification can repeat for a specified number of time with specified
intervals), but not the time option (you cannot configure the For option, as in the case of digital
actions). The user can use it in the rule by selecting the relevant status to notify from the actions tab
and pressing the Notify button. If there is no free index for allocation, the Notify button is disabled.
NOTICE: The user should change the index to burst indexes. If the user changes the index to
the not burst index, and this notify functionality is a part of the rule already, the notify cannot
function, but the rule will.
Rule Examples
The following examples illustrate the way rules should be created to correctly control the system
behavior. You can review them to learn the possibilities of the system and analyze how the rules work
in practice.
Example 1 – Heating Coil Automatic Operation

A heating coil is actuated when a heating control switch is activated and when a float switch installed in
a tank indicates that there is water in the tank. The configuration for performing the actuation of the
heating coil would be as follows:
Entities Tree:
Tank A
Heating switch
HeatSw
Float switch
WaterLevelSw
30 Send Feedback
Rule Creation
Heating coil
Heater
Table 1: Example 1 – Entity Details
Type:
Heating Switch
Name:
HeatSw
State Name Type:

On/Off Basic I/O
State:
ON OFF
RTU Name:
Site 001
I/O link:
Physical name:
DI1
Device:
Main Board (wired to tank heating control
switch)
Type:
Float switch
Name:
WaterLevelSw
State name: Type:

AboveMinimum\BelowMinimum Basic I/O
State:
ON OFF
RTU Name:
Site 001
I/O link:
Physical name:
DI2
Device:
Expansion 1 (wired to tank float switch)
Type:
Heating Coil
Name:
Heater
Action name Type:

TurnOn\TurnOff Basic I/O
Table continued…
Send Feedback 31
Rule Creation
Type:
Heating Coil
Name:
Heater
Action:
OPEN CLOSE
RTU Name:
Site 001
I/O link:
Physical Name:
R1-s/R1-r
Device:
Main Board (wired to tank heating coil)
State name: Type:

TurnedOn\TurnedOff Basic I/O
Action:
OPEN CLOSED
RTU Name:
Site 001
I/O link:
Physical Name:
R1-s/R1-r
Device:
Main Board (wired to tank heating coil back
indication)
The following figure presents the structure of the desired rule.

Figure 17: Example 1 - Rule Structure
Example 2 – Adding Heater State Initialization

To add initialization of the heater state to the configuration presented in Example 1 – Heating Coil
Automatic Operation on page 30, the following entity and rules should be added.
Entities Tree:
Tank A
Heating switch
HeatSw
Float switch
WaterLevelSw
32 Send Feedback
Rule Creation
Heating coil
Heater
TankApp
1
Type:
TankApp
Name:
1
Action/State name: Type:

InitDone Flag (Internal RTU indicator)
NOTICE: The default value for a
flag on RTU startup is false.
The two rules required to make that system work correctly are presented in the following figures.
Figure 18: Example 2 – Rule Structure 1
Send Feedback 33
Rule Creation
Example 3 – Adding Temperature Condition

In this example, the additional condition of the heating coil actuation is considered: the temperature of
the water in the tank must be lower than 95°C. A thermometer with a continuous analog output is
installed in the tank and connected to an analog input of the RTU.
Type:
Tank
Name:
A
State name: Type:

WaterTemp Basic I/O
State
TEMPERATURE
RTU Name:
Site 001
I/O link:
Physical Name:
AI1+/AI1-
Device:
Expansion 1 (wired to thermometer)
In this case, the rule presented in Figure 19: Example 2 – Rule Structure 2 on page 34 requires an
addition of the following When this happens condition parallel to the others: Tank A WaterTemp is
< 95
34 Send Feedback
Rule Creation
The following figure presents another rule that is required for stopping the heating coil once the heating
switch is off, or temperature rises above 95°C.
Figure 20: Example 3 – Rule Structure
Example 4 – Adding Hourly Breaks

In this example, another condition is taken into account: after an hour of heating, the heating coil
should stop working for at least five minutes.
Type:
Heating coil
Name:
Heater
State/action name: Type:

CanContinue Flag
The following rule should be formulated:
Send Feedback 35
Rule Creation
NOTICE: A trigger is defined using the persistence option. An action is defined using sequence
option.
The action is specified to set the flag CanContinue to false for five minutes, starting from the moment
that the trigger occurred. After five minutes, the flag changes to True, regardless of the flag state
before trigger occurred.
The following modifications to the rules should be implemented:
• In Figure 18: Example 2 – Rule Structure 1 on page 33, add in parallel to the other two actions:
HeatingCoil Heater CanContinue=True.
• In Figure 20: Example 3 – Rule Structure on page 35, to the OR node, add in parallel:HeatingCoil
Heater CanContinue is False.
• Expand Figure 19: Example 2 – Rule Structure 2 on page 34 by the following two conditions:
36 Send Feedback
Rule Creation
Figure 22: Example 4 - Rule Structure 2
Deleting Rules
Follow this procedure to delete rules from entities.
Procedure:
1 In the left-hand panel tree, select the entity whose rules you want to delete.
2 Go to the rules view by clicking Rules.
3 From the list of rules, delete the selected rules by clicking the respective X icons.
Interface to IIOT HMI Control Application

Control room application can also trigger events that are processed by ACELogic.
States and actions of flag and value types are managed in the ACE1000 RTU user application data
tables. Bits table is used for flag states and actions. Long integers table is used for value long states
and actions. Float table is used for states and actions of type value float). Control room application can
access this data using MODBUS protocol.
MODBUS address that should be used depends on the state or action attributes:
• User data
• User data index
These attributes can be viewed and modified using the States and Actions summary on the User Data
tab. For the summary view details, see I/O Link Summary View on page 41. For ACE1000 RTU/FEP
User Table Data Register Locations table, converting user data, and user data index, see "Appendix C:
ACE1000 MODBUS Configuration".
Example: Assume a state of type flag with the index=1. MODBUS address would be Coils
2000. States of type flag are stored in the bits user table, which is exposed as MODBUS Coils.
Send Feedback 37
Rule Creation
Location of the first element is 2000. The address would be: <location of the first
element> + <state user data index>– 1.
Interface to Local C Application

A local C application on ACE1000 RTU can coexist and interact with the ACELogic application.
States and actions of type flag and value are managed in the ACE1000 RTU user application data
tables (bits table used for states and actions of type flag, long integers table is used for states and
actions of type value). C application can access this data using C Toolkit API.
The parameters that should be used depend on the state or action attributes:
• User data
• Table
• Row
• Column
These attributes can be viewed and customized using the States and Actions summary on tab User
Data.
Refer to ACE1000 ‘C’ Programming SDK & Migration Guide.
Example: Assume a state of type flag with the following attributes:

User Data = BIT
Table = 6
Row = 0
Column = 0
The state can be accessed by a local C application by calling: MOSCAD_get_user_bit with
row=0 and column=0 as parameters.
ACELogic Application Execution Flow

The ACELogic application is based on the CLIPS rules engine. Only one ACELogic application can run
on the RTU.
The general flow of execution is as follows:
1 The ACELogic application is deployed as part of site configuration. It might be followed by a reboot,
depending on the configuration changes.
2 The ACELogic application is launched after RTU database completes initialization.
3 All states and actions of flag or value type are initialized to 0.
4 All current states are treated as new events
5 The application enters a waiting mode for new events.
6 New events in the system trigger the evaluation of relevant rules.
7 If a trigger condition of a rule is fulfilled, the actions are scheduled for execution.
8 Execution of actions of the different rules that were scheduled for execution is performed in an
arbitrary order.
NOTICE: The execution flow of sequence rules differs. See Sequence Rules on page 39.
38 Send Feedback
Rule Creation
Rules Evaluation
Rule triggers are not re-evaluated constantly. Upon entity state transition (for example, an update of a
sensor measurement or a flag or value change) or upon state persistence time completion, only the
rules that refer to that state in the trigger are evaluated. Upon time change (resolution of one minute),
only rules that refer to time in the trigger are evaluated. On startup, all current states are treated as
new events.
Rules Execution Order

When more than one of the evaluated rules have the trigger condition fulfilled, the order of the different
rules actions execution is arbitrary. If an order of execution is required (for example, for initialization), it
should be controlled by using states of flag or value type. If different rules trigger the same action, only
the last execution applies.
Rules Using the is and change of state triggers

For a rule that uses the change of state operator for a specific state in the rule trigger condition, the
rule action is executed only once, upon a change of the specific state for digital input states and flag
states, or on crossing low/high threshold of a range, for analog input states and value states.
Notification occurs only once when the condition is satisfied.
When the is operator is used in a rule trigger, the action is re-applied if the ACELogic application
detects that the current state is not as was set by the rule. Notification on every change in state value
occurs when condition is satisfied.
Supported Event Rate

ACELogic application supports up to 100 different entity state transitions in a second. If a specific entity
state changes at a rate higher than 100 milliseconds, the state change event might not be processed
by the application. Diagnostics for the ACELogic application can indicate if events were lost.
Time-Triggered Rules
Time resolution for triggering rules is one minute. This implies that:
• A rule might be triggered any time during the scheduled minute.
• As long as the time fits the condition, the action is re-applied if the ACELogic application detects
that the current state is not as was set by the rule.
For example, the user can define the following rule: When the time is 6:00 o'clock, power
off the Air Condition. This rule means that as long as time is 6:00 o'clock, the Air Condition is
triggered to power off.
If an action is scheduled for an interval of time, the action is re-applied if the easy rule application
detects that the current state is not as was set by the rule. If the desired interval of time spans two
days, two different rules should be configured.
Sequence Rules
If a sequence of actions is defined in one rule, these actions occur according to the scheduling defined
in the sequence. If two actions are scheduled for the same time after the trigger event occurs, they are
executed according to the order in which they appear in the sequence.
Sequence execution cannot be interrupted in the following two cases:
When a sequence is triggered using the change of state operator for a specific state:
If Repeat is not used, the sequence is executed once.
If Repeat is used, the sequence is executed for the specified number of times.
Send Feedback 39
Rule Creation
If the state changed during the sequence execution, this event is disregarded. Only state changes
that occur after the sequence is completed are set to trigger the sequence again.
When a sequence is triggered using the is operator for a specific state:
If Repeat is not used, the sequence is executed, after which the trigger condition is evaluated
again. If the trigger condition is fulfilled, the sequence is executed again.
If Repeat is used, the sequence is executed for the specified number of times, after which the
trigger condition is evaluated again. If the trigger condition is fulfilled, the sequence is executed
again for the specified number of times.
40 Send Feedback
I/O Link Summary View

The States & Actions Summary view allows the user to display all states, actions, and their physical
I/O links in one view.
In this view, you can also edit physical I/O parameters.
Accessing Physical I/O Parameters Summary View

Follow this procedure to access the parameters of a given physical I/O in the Summary view.
Procedure:
1 In the top right corner of the Easy Configurator window, click Tools.
2 Under Miscellaneous, click States & Actions Summary.
3 In the States & Actions Summary view, click the tab of the I/O whose parameters you want to
modify.
Digital Input Links in Summary View

You can edit your digital input links from the States & Actions Summary view.
You can edit only the active columns. Columns that are grayed out are read-only.
The following columns are available:
Site Name
The site where the entity is located.
Entity Type
Type of the given entity.
Entity Name
The entity instance name.
State
The label set for the state.
Physical I/O name
appears.
If you want to edit physical I/O name for any item, from the Physical I/O Name column, you can
expand the drop-down list and select a new name.
I/O Type
For digital input links, only Wet is supported.
I/O State
The physical value used for each state. The available values are ON (1) and OFF (0). The first
defined digital state is always ON and the second is OFF.
I/O Module
The I/O module name: Main, Exp1, or Exp2.
I/O User Connection
The connected I/O name as it appears on the RTU I/O label.
Send Feedback 41
Properties
You can edit the properties of a given state by clicking the icon. For details on the properties,
see "ACE1000 I/O Parameters" in ACE1000 Easy Configurator User Guide.
Digital Output Links in Summary View

You can edit your digital output links from the States & Actions Summary view.
Site Name
Entity Type
Entity Name
Action
The label set for the action.
Back Indication Name
The label of the back indication composed of the relevant action name and the _BI suffix.
Physical I/O name
appears.
I/O Type
The available types are EE (Electrically Energized) and ML (Magnetically Latched), fixed according
to the physical digital output.
I/O Module
I/O State
States are available for selection according to the following pattern:
• R1-r: relay reset
• R1-s: relay set
or:
• NO1: Normally Open
• NC1: Normally Close
Properties
Analog Input Links in Summary View

You can edit your analog input links from the States & Actions Summary view.
42 Send Feedback

Site Name
Entity Type
Entity Name
State
The label set for the state.
Physical I/O name
appears.
I/O Type
Current or voltage according to the I/O configuration.
I/O Module
I/O User Connection
Properties
Analog Output Links in Summary View

You can edit your analog output links from the States & Actions Summary view.
Site Name
Entity Type
Entity Name
Action
The label set for the action.
Physical I/O name
appears.
I/O Type
Current or voltage according to the I/O configuration.
Send Feedback 43
I/O Module
I/O User Connection
Properties
User Data Links in Summary View

States and actions of flag and value types are managed in the ACE1000 RTU user application data
tables. Bits table is used for states and actions of flag type. Long integers table is used for value states
and actions. Float table is used for value float states and actions.
You can edit your user data index in tables from the States & Actions Summary view. You can edit only
the active columns. Columns that are grayed out are read-only. The following columns are available:
Site Name
Entity Type
Entity Name
State/Action
The label set for the user data.
User Data
Table type - Bit, Long, or Float.
User Data Index
Allocated index for user data state or action in user table.
Table
Table number of allocated user data according to user data type.
Row
Row number of allocated user data according to user data index.
Column
Column number of allocated user data according to user data index.
44 Send Feedback
ACELogic Maintenance
If the ACELogic application requires a modification after deployment, the user should make the change
using the FEP and afterwards deploy the modified site configuration using the FEP onto all units that
were impacted by the change. If the change was done locally on a site using the ACE1000 RTU itself,
the user should modify the ACELogic configuration on the FEP in the same way to prevent the override
of ACELogic configuration on the local ACE1000 RTU by future deployments from the FEP.
Send Feedback 45
46 Send Feedback
ACE1000 Troubleshooting
The ACE1000 Easy Configurator software generally provides prompts and error messages
to guide you in the use of the tool. The table below provides additional tips on solving
problems with the ACE1000.
Symptom Action
ACE1000 unit does not Do the following:
respond at all.
1) Connect the PC to the unit’s USB OTG port using a
standard USB cable.
2) Use PuTTY to log in to the following IP: 192.168.9.9
If you cannot access the unit via PuTTY, do the following:
1) Power cycle the unit (turn the power off and on).
2) If you still cannot access the unit, create a file named
force_boot, which consist of the string “force_boot” at the
beginning of the file.
3) Copy the force_boot file from the PC to the root folder on
a FAT32 formatted SD card.
4) Plug in the SD card into the SD card slot on the ACE1000
front panel.
5) Power cycle the ACE1000 (turn the power off and on).
Result: The unit should now boot the failsafe kernel &
failsafe root file system.
Install a new copy of the kernel and file system to the unit, from
the firmware ISO on the MOL web site.
ACE1000 unit does not First make sure the proper IP address was pinged.
respond to ping.
If a Web browser with the unit is open, check that the configured
Ethernet port IP address was set correctly and deployed.
If the IP address is correct, try the following:
1) Connect an OTG cable between your PC and the unit.
2) Use PuTTY to log in to the following IP: 192.168.9.9
3) Run ifconfig command and check that eth0 is defined as
expected.
3-1
ACE1000 unit responds First make sure the proper IP address was entered in the Web
to ping but cannot browser (either 192.168.9.9 for the USB OTG port or the unit’s
connect via the Web. Ethernet port.)
If the IP address is correct, trythe following:
1) Use PuTTY to log in to the unit.
2) Run: ps | grep httpd
3) Check if there are at least five httpd processes running.
4) Do one of the following:
• If there are not at least five httpd processes are running,
check the following logs: /tmp/log/apache2/ssl_access.log
& /tmp/log/apache2/error.log, or send them to your
ACE1000 support team.
• If there are at least five httpd processes running:
a) Run: top
b) If there is a process with a high percentage of CPU use
for long/infinite period of time, contact your ACE1000
support team.
After connecting to the Do the following:
ACE1000 unit via the
1) Close all Chrome sessions and then reopen them.
Web, GUI components
are gray or truncated. 2) If the GUI still looks abnormal, clear your browser data
(specifically cookies and cached images/files) in the
Chrome Settings->advanced settings page.
The FEP does not have If a Web browser session can be opened with the RTU, try one of
communication with the the following:
RTU.
• Check if the RTU configuration needs to be saved/deployed.
• Retrieve Software Diagnostic device RTU, levels 1 and 3, and
IPCNTBL level 3.
If a Web browser session can be opened with the FEP, retrieve
Software Diagnostic device IPCNTBL level 3, and FEP level 3.
An I/O application error The application is trying to modify outputs on the I/O expansion
appears after a wakeup modules immediately after waking up.
event occurs on an RTU
The application should be modified to give the I/O expansion
with I/O expansion
modules time to boot (6-8 seconds), before changing the outputs.
modules and a ‘C’
application that changes
the output statuses and
goes to sleep for 30
seconds.
3-2
After 15 minutes of The user is probably in Monitoring mode.

inactivity, the ACE1000
Manually lock the screen for security purposes.
Easy Configurator GUI
does not time out and
prompt the user to log in
again.
Download of a ‘C’ If the name of the application (.plx) is longer than 13 characters,
application fails. shorten the application name.
After updating the Kinetis Disregard the error.
firmware file, an error is
displayed: # 7900 ioappl
Communication Failure
in reading IO module
number 0 (io_errno = 2)
Expected errors do not If the user clicks Clear in the Error Log window, errors which
appear in the Error Log were logged while the Error Log window was open are deleted in
window. the unit and not displayed in the GUI. It is recommended to click
Get again to retrieve any new errors before clicking Clear.
Expected events do not The unit may have been reset or the I/O definitions changed (an
appear in the Event Log I/O module is added/removed, or I/O attributes are changed,)
window. which caused the unit to restart. In these cases, the event logger in
the unit is cleared.
Export the contents of the event logger to the PC before resetting
the unit or changing the I/Os.
3-3
An error occurred during To check if you are in fail safe mode, do the following:
the install process. Unit
1) Use PuTTY/ssh to log in to the unit as the non-root
may be in fail safe mode.
administrator user. See the credentials in Table G-2.
2) Run: get_device_mode
3) Check the return value for “System mode”. Can be either
Failsafe, or Main.
To install the main file system from fail safe mode, do the
following:
1) Make sure you are in fail safe mode.
2) Use SCP/WINSCP to log in to the unit as terminal login
user. See the credentials in Table G-2.
3) Navigate to /ltr/tmp/download/web/System/FileSystem/.
4) Upload the main file system from your PC to the unit:
(e.g. fs-1.00-xx.bin)
6) Run: install_fs fs-x.yy-zz.bin (e.g. fs-1.00-xx.bin)
7) Run: updateutil -s (required step to sign the version)
8) Run: reboot –main
To install the main kernel from fail safe mode, do the following:
1) Install the main mode kernel itself:
a. Make sure you are in fail safe mode.
b. Use SCP/WINSCP to log in to the unit as terminal
login user. See the credentials in Table G-2.
c. Navigate to
/ltr/tmp/download/web/System/Kernel/.
d. Upload the main mode kernel from your PC to the
unit: (e.g. uImage-1.00.016)
e. Use PuTTY/ssh to log in to the unit as the non-
root administrator user. See the credentials in
Table G-2.
f. Run: install_kernel uImage-x.yy.zzz (e.g.
uImage-1.00.016)
2) Run: reboot –main
3) After the unit is restarted in main mode, re-install the
kernel via the Web (Tools -> Install applications,
packages and licenses and select Kernel.)
3-4
After the default admin Install the main file system from fail safe mode:
password, the user forgot
1) Make sure you are in fail safe mode.
the new admin password.
2) Use SCP/WINSCP to log in to the unit as terminal login
user. See the credentials in Table G-2.
3) Navigate to /ltr/tmp/download/web/System/FileSystem/.
4) Upload the main file system from your PC to the unit:
(e.g. fs-1.00-xx.bin)
6) Run: install_fs fs-x.yy-zz.bin (e.g. fs-1.00-xx.bin)
7) Run: updateutil -s (required step to sign the version)
Run: reboot –main
3-5
Appendix A: Site Configuration Parameters
A number of parameters and settings can be configured for the ACE1000 unit.
 Port Parameters for the various on-board and plug-in communication ports
 I/O Parameters
 Application and Services Parameters
When configuring an ACE1000 RTU/FEP, 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 which are defined for the
particular system software version are displayed.
Some parameters are displayed as checkboxes which can be selected or unselected. 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 changes according to changes in the
configuration.
The icon indicates that a parameter value is different than the default.
ACE1000 Port Parameters

The following parameters are set from the specific port’s Settings icon.
LAN (Ethernet) Port Settings Parameters

IP Address [0.0.0.0]
The (private) IP address of the LAN port. This address is used to access the unit via LAN
when a Public IP Address is not specified.
Subnet Mask [0.0.0.0]

The subnet mask of the LAN port.
Default Gateway [0.0.0.0]

The default gateway of the LAN port.
Public IP Address [0.0.0.0]

The IP address used to access the unit via LAN, in systems with modems/cellular modems,
when the modem has its own (private) IP address. If
If it is set to 0.0.0.0, the (private) IP Address parameter is used.
A-1
USB1/USB2 Port Settings Parameters

Public IP Address [0.0.0.0]
The IP address of the USB port used to access the unit.
ACE1000 General Parameters
The following parameters are set from the unit’s General icon.
Name
The name of the site. Must be unique within the system. This name appears on the site “box”
in the FEP System View, when all system sites are displayed, and at the top of the screen in the
FEP or RTU’s RTU View. Can be 1-40 characters long, including A-Za-z0-9,`!@#$%^*()
[]{}_
Description
(Optional) A description of the site. Can be 0-400 characters long, including A-Za-z0-
9,`!@#$%^*() []{}_
Site ID
Unique MDLC site identifier. Logical address. The Configurator assigns a default site ID, but
this ID can be changed. Can be a digit from 1-65287.
MODBUS Address
Unique address of the device used in MODBUS communication. This parameter is assigned
automatically by the Configurator and can be edited by the user.
MAC Address
Identifier used by network adapters to uniquely identify themselves on a LAN. This parameter
is assigned automatically by the Configurator and is read only. Visible only in the FEP’s RTU
View or the RTU’s RTU View when viewed directly (not through the FEP.)
Application Parameters
The following parameters are set from the unit’s Application icon.
When setting Application parameters from the FEP, the Apply changes to all units checkbox
may appear. If you select this option, the parameters changes will be apply in all RTUs when
the system configuration is deployed.
DNS Client/Server Parameters

DNS server enable Disable
For PPP connections. The list of up to three DNS server IP addresses. To add an IP address,
type in the address in xxx.xxx.xxx.xxx format.
A-2
To remove an address, reset to 0.0.0.0.

To save the list, click on OK. Relevant for PPP connection type only.
DNS Server 1, 2, 3 [0.0.0.0]:

Range: 0.000.000.000-255.255.255.255. Relevant for PPP connection type only.
DNS host name

For PPP connections. .
DNS domain name

For PPP connections. .
ACE1000 - FEP Parameters

Enable FEP-RTU application
Select this checkbox to enable the ACE1000 FEP-RTU application. Disable this parameter in
systems with other tailored FEP-RTU applications, or systems with no FEP.
Time interval between periodic polling cycles (min) <1-1440> [60]

The number of minutes that the FEP should wait between the end of one poll cycle of RTUs
and the beginning of the next poll cycle of the RTUs.
Time interval between units in each periodic polling cycle (sec) <10-300> [300]
The number of seconds that the FEP should wait after polling an RTU before polling the next
RTU in the polling cycle.
ACE1000 - RTU Parameters

Enable FEP-RTU application
Select this checkbox to enable the ACE1000 FEP-RTU application. Disable this parameter in
systems with other tailored FEP-RTU applications, or systems with no FEP.
Number of initial registration attempts <0-100> [3]

The number of times that the RTU should try to initially register with the FEP (e.g. after the
unit is powered up or after the unit is disconnected from the FEP.) If registration is successful,
the RTU runtime information is updated in the FEP.
Time interval between initial registration attempts (sec) <5-600> [300]

The number of seconds between attempts at initial RTU registration with the FEP.
Time interval between initial registrations after all initial registration attempts failed (min)
<0-1400> [300]
The number of minutes to wait between attempts at registration with the FEP, after the initial
registration attempts failed.
A-3
Health check time interval (min) <1-1440> [5]

The number of minutes of quiet (i.e. no communication between RTU and FEP) to wait before
the RTU sends a health check message to the FEP. If the FEP does not respond to the health
check message, the RTU declares that communication has failed (reflected in the icon.)
When communication is restored, the registration process begins again. To try to manually
restore communication from the FEP, poll the RTU or change a DO/AO set control.
Number of Bits values in User Table to sync <0-250> [0]

The number of elements in the Bit User Table to synchronize between the FEP and the RTU.
Number of Integers values in User Table to sync <0-250> [0]

The number of elements in the Integer User Table to synchronize between the FEP and the
RTU.
Number of Floats values in User Table to sync <0-250> [0]

The number of elements in the Float User Table to synchronize between the FEP and the RTU.
Number of Longs values in User Table to sync <0-250> [0]

The number of elements in the Long User Table to synchronize between the FEP and the RTU.
NTP & GPS Parameters

GPS enabled
Select this checkbox to enable GPS time synchronization. When enabled, NTP client is also
enabled and one or more NTP servers may be specified.
NTP server enabled

Select this checkbox to enable a NTP server for time synchronization.
NTP client enabled

Select this checkbox to enable NTP client for time synchronization. When enabled, specify
one or two NTP servers.
NTP Server 1/NTP Server 2 [0.0.0.0]

Specify the IP address of one or two NTP servers for time synchronization. This parameter is
displayed only if NTP client is enabled.
MODBUS Parameters
Slave Response Bytes Timeout <0-65000 ms>
Timeout interval between two consecutive bytes of the same message.
MDLC Parameters
The MDLC parameters vary per port. Parameters which are relevant for more than one port are
described once.
A-4
By default, the advanced General MDLC parameters, which are not associated with a specific
port, are displayed. To see the advanced MDLC parameters associated with a specific port,
click the ETH1, SI1, P1, P2 USB1, or USB2 port link.
ETH1 Port MDLC Parameters

The following MDLC parameters can be set for the Ethernet LAN (ETH1) port.
Link name [LINE 1]:

Contains the logical name of the link that the port is connected to. The link name is
automatically selected according to the Port parameters. If relevant, you can select another
name from the drop down list.
MDLC over IP port number <1-65535> [2002]:

This number is common to the FEP and all RTUs connected to the link. This number identifies
the MDLC. This is a UDP port number and the provider should be consulted. It is important
that this number not be in use as specified by the TCP/IP standard RFC0960.
Enable sync <Disable/Enable> [Disable]:

Enables/disables synchronization over IP. Must be enabled in both the sending and receiving
unit in order to synchronize. Note: Synchronization is inaccurate because of the IP media. Use
of NTP is recommended instead where possible.
Number of link IDs <1-9> [1]:

The number of Ethernet links defined for the port.
Check alive timeout (sec) <0-65535> [0]:

Specify timeout in seconds from the last reception from the FEP/RTU. If nothing is received
from the FEP/RTU during that timeout, the unit is polled (see Poll Interval below). This
behavior guarantees that a unit is reachable over IP. If this parameter is 0, a unit is considered
reachable, once a single reception has been received from it. This parameter is considered to
be 0 regardless of its value if ‘Maximum number of polls’ is 0.
Poll interval (sec) <0-65535> [0]:

Specify interval in seconds between polls of a unit. If no reply is received to a poll request,
another poll request is sent after the Poll interval, until the Maximum number of polls is sent
(next parameter).Poll interval is measured independently for each site in the IP conversion
table. If this parameter is 0, a single poll (or no polls) is sent to the unit according to Maximum
number of polls (0 or not.)
Maximum number of polls <0-255> [0]:

Specify the number of poll requests to send in order to check if a unit is alive. If no response is
received, it is polled again. If a unit has been polled for the Maximum number of polls without
answering, it is considered as failed.
Notify IP Address when connected <Disable/Enable> [Enable]:

When enabled, if an RTU’s IP address is changed or obtained from a modem, the RTU sends a
message to update its IP address in the IP conversion table for that link.
A-5
Note: These messages are sent one after the other, and it is not guaranteed they will be
delivered and accepted.
Enable routing on MDLC over IP Port <Disable/Enable> [Disable]:

Enables/disables routing on an MDLC over IP port.
TX to failed RTU every (min) <O: DISABLE 0-30> [3]:

Specifies a period of time in minutes, after which a failed link is considered as being back in
order, provided the value of the Periodic check of failed RTU parameter is set to Disable. If the
Periodic check of failed RTU parameter is enabled, it specifies the period of time in minutes
after which the Network layer issues a control frame to check the failed link.
Periodic check of failed RTU [Disable]:

The network sends a control frame to check whether 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.
Get host by name using DNS <Disable/Enable> [Enable]:

When enabled, allows retrieval from the DNS server of the IP address which corresponds to a
given Internet host name.
Default group IP address <000.000.000.000-255.255.255.255> [0.0.0.0]:

Identifies Site ID 0 which is used for Group Call.
Notify private Site IDs when connecting [Enable]

When enabled, the RTU sends its private Site ID when it connects to the FEP.
Notify changes from other links [Never]

Relevant for RTU redundancy. For future use.
In addition, the following parameters exist for Connect Plus XRT Gateway:
XRT Gateway IP Address [0.0.0.0]:

For 10/100 BT static LAN connections to a MotoTrbo XRT Gateway. IP Address of the XRT
Gateway. Only one address is allowed per physical port. The RTU is an XRT Client and it
connects with that IP address using XRT Client protocol.
XRT Gateway TCP port <1-65535> [10001]:

For 10/100 BT static LAN connections to a MotoTrbo XRT Gateway. TCP port to connect
with in XRT Gateway. The RTU is an XRT Client and it connects with that TCP port using
XRT Client protocol.
A-6
XRT Client data path ID <0-16776413> [0]:

For 10/100 BT static LAN connections to a MotoTrbo XRT Gateway. The "Subscriber ID"
configured in XRT Gateway for this RTU. Setting it to 0 means that it should be the same as
RTU Site ID.
XRT Client connect timeout <1-60> [10]:

For 10/100 BT static LAN connections to a MotoTrbo XRT Gateway. Timeout in seconds to
wait for the connection to succeed with the XRT Gateway. After this timeout elapses and no
connection is established, a retry is performed. When powering up or connecting the radio
cable, this continues periodically until connection succeeds. If the connection fails after 2
minutes, an error is logged.
XRT Client idle time to declare end reception (milliseconds) <0-65535> [0]:
For 10/100 BT static LAN connections to a MotoTrbo XRT Gateway. Timeout in
milliseconds to declare end of reception. After this timeout elapses, end of reception is
declared and all bytes received from XRT are processed.
XRT Client transmit queue size <16-64> [32]:

For 10/100 BT static LAN connections to a MotoTrbo XRT Gateway. The maximal number of
requests that can be queued before being sent to the XRT. This is reserved for future use.
XRT Client packet data request fail timeout (seconds) <1-65535> [210]:
For 10/100 BT static LAN connections to a MotoTrbo XRT Gateway. Timeout in seconds to
declare transmit failure when transmitting a raw data request and getting no response from
XRT.
SI1 Port MDLC Parameters

The following MDLC parameters can be set for the Serial RS232/R485 (SI1) port. Some of
the MDLC parameters listed for the ETH1 port are also relevant to the SI1 port.
Link name [RSlink 1]:

Data speed [115200 bps]:

The communication data speed of the selected media.
Default Routing [None]

Ensures RTU “mobility”. The Default Routing parameter allows you to define the RTU as one
that can be switched from one base station to the other by changing the radio frequency
(RadioX) or switching physical lines (LineX), but without changing the Link ID and the
MDLC network settings.
The choices are:
A-7
Choice Description
None This feature is not used.
To Slave(s) 1) 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
others must be set to None.
2) If the base station is the one that handles the data sent by the
RTUs, then one of its ports must be defined as To Slave(s). This
is the port through which the RTU communicates with the
slaves.
To Master/Cntrl If the RTU is used as “slave”, then one of the ports should be
defined as To Master/Central, and its Link ID must be RadioX
or LineX.
TX queue size <(2^)3-(2^)9> [(2^)6]:

This is the maximum number of MDLC frames that can be placed in the transmission queue
before a transmission process starts.
Number of ACK buffers <5-50> [8]:

The reception process of the Data Link layer prepares an ACK for each received data frame,
and 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 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 traffic, or because it cannot access a
channel for transmission.
Number of TX retries <0-9> [2]:

The number of times the Data Link layer retransmits a data frame for which ACK was not
received.
Number of TX retries upon BUSY ACK <0-9> [2]:

The number of times the Data Link layer retransmits a data frame for which BUSY ACK was
received (BUSY ACK is issued when all Data Link layer boxes of the switching node on are
full).
Interval between TX retries upon BUSY ACK (msec) <10-100> [40]:

The interval of time that should elapse before a data frame for which BUSY ACK was
received, is retransmitted.
Number of TX broadcast (Group call) retries <0-9> [0]:

The number of retries for broadcast frames. Since broadcast frames are not acknowledged,
specify a value greater than 0 to increase the chances of the 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.
A-8
Interval between broadcast (Group call) retries (msec)<10-100> [40]:

The period of time that should elapse between retries of broadcast frames (if the previous
parameter is not 0).
Maximum number of addressable sites in a transmission <1-4> [4]:

Maximum number of units the Data Link layer is capable of addressing in a single
transmission. For “private conversation”, specify 1.
Interval between FULL DUPLEX TX retries/Channel Busy TX Retries (msec) <10-100>

[50]:
The period of time that should elapse before a retry takes place in Full Duplex. New data
frames cannot be sent to the retried unit.
Clock synchronization delay <0-50> (msec) [0]:

The delay (applied to the channel) between 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 selected medium. However, the user can change it.
Force 'Local’ response [Force]:

It is possible to conduct a session based on Site ID/Link ID using Local if the port is of
Computer/RSlink type. Normally the port is defined for Local Response if the medium is not
“multidrop”. In any case, “local response” can be forced on a port if it is not “multidrop”. The
default value is based on the port type. It is recommended to leave the default as is.
Number of idles to announce 'End of RX' <1-200> [80]:

and NOT more than <10-2000> ms [500]:
In UART communications without close characters, a period of silence notifies all layers above
Physical that reception has ended. This period is calculated in terms of idles which are
converted to time as a function of the data speed. The system uses this value or the value
specified in the second field (and NOT more...), whichever is the smallest.
Interval between Link TX retries <100-6000> (msec) [5000]:

The interval of time that should elapse before a data frame for which no ACK was received, is
retransmitted.
Maximum time waiting for TX-grant <100-900000> (msec) [60000]:

The period of time the system waits for channel access, from the time it requests a channel. If
this period of time elapses without gaining the channel, this transmit attempt is declared as
failed.
RTS always ON [Yes]:

The RTS of the RTU is connected to the modem’s DTR. It is controlled by 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.
A-9
Number of bits for staggering <2-8> [4]:

This parameter is related to the slotted access mechanism used by the channel access 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.
Special attention is required when assigning the RTU logical address (site ID) of sites which
use the channel access mechanism. For each site, the value of (siteID MOD n) must be unique,
in order to prevent collisions between two transmissions.
Max. TX-data duration <1000-60000> msec [30000]:

The maximum time during which data can be transmitted. After this period of time
transmission stops even if it has not yet ended.
Busy-channel TX-override delay <0-320000> msec [0]:

The maximum waiting time for a channel. After this time-out, the system accesses a channel
whether or not it is free. The default value of 0 means that this feature is disabled, i.e., the
RTU does not transmit if the channel is busy. (For RS485 RTU multi-drop ports.)
Channel monitor time resolution <10-1000> msec [60]:

The size of a time slot in the slotted channel access mechanism of MDLC. 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 the radio used – the quicker the channel monitor's response, the shorter
this 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 follows: each RTU is assigned a priority level as a
function of the data message it wants to transmit (new data, acknowledgment, retry, etc.) and in
some cases, as a function of its address. When the RTU wants to transmit that message, it first
checks whether the communications channel 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 taken by a higher-priority RTU, the whole
process is repeated when the channel is free again.
For example, let's assign the time resolution T. When the RTU accesses the channel, it starts
transmitting only after a delay that is a factor of T. When the RTU accesses the channel for the
first time, the delay is (n+4)T, where n represents the 4 less significant 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> msec [0]:

The minimum waiting time between the end one transmission and the next one. It is measured
from the end of the Hold-up of the last transmission for ports with channel access (e.g.
Radio/RS485 multi-drop/RS232 half duplex.).
Minimum time to retry <0-30000> msec [0]:

The minimum period of time that should elapse between the end of a transmission and its first
retry, and between retries.
A-10
P1 Port/P2 Port MDLC Parameters

The following MDLC parameters can be set for the Plug-in RS232 (P1/P2) port. Many of the
MDLC parameters listed for the SI1 or ETH1 port are also relevant to the P1/P2 port.
Link name [RSlink 2]:

USB1/USB2 Port MDLC Parameters

The MDLC parameters which can be set for the USB On-the-Go or USB 2.0 Host port
(USB1/USB2) port are listed under the ETH11port.
In addition for Connect Plus radios (non-IP) on USB2, the following MDLC
parameters exist:
Radio connect timeout (seconds) <1-60> [10]:

A parameter specific for Connect Plus radio. Timeout in seconds to wait for the connection
with the radio to succeed. After this timeout elapses and radio has not been connected, a retry
is performed. When powering up or connecting the radio cable, this continues periodically
until connection succeeds. If the connection fails after 2 minutes, an error is logged.
Radio idle time to declare end reception (milliseconds) <0-255> [0]:

A parameter specific for Connect Plus radio. Timeout in milliseconds to declare end of
reception. After this timeout elapses, the end of reception is declared and all received bytes are
processed. 0 means that the default value is used.
Radio minimal time to retry (seconds) <1-60> [1]:

A parameter specific for Connect Plus radio. Timeout in seconds to retry transmission to the
radio after the transmission is not acknowledged by the radio. This is specific for
communicating XCMP/XNL with the radio and is not related to communication over the air.
Radio request fail timeout (seconds) <1-65535> [10]:

A parameter specific for Connect Plus radio. Timeout in seconds to declare a failure when
sending a request to the radio and getting no response from it. It is specific for communicating
with the radio and is not related to communication over the air. Unlike the previous parameter,
it is related to an XCMP data response, such as radio signaling level.
Radio packet data request fail timeout (seconds) <1-65535> [30]:

A parameter specific for Connect Plus radio. Timeout in seconds to declare a transmit failure
when transmitting a raw data request and getting no response from the radio. Unlike previous
parameter, it is related to an XCMP data response, such as Data reply or Data Broadcast. After
this time expires and no response has been received, connection needs to be re-initiated.
Radio minimum packet data request interval <1-10> [5]:

A parameter specific for Connect Plus radio. The timeout in seconds to wait after a successful
transmission of a raw data request to the radio before sending a new one.
A-11
Radio transmit queue size <16-256> [32]:

A parameter specific for Connect Plus radio. The maximal number of XCMP requests that can
be queued before being sent to the radio. This is specific for communicating XCMP/XNL with
the radio and is not related to communication over the air.
RSSI signal level to declare radio not registered <0:DISABLE, 1-255> [100]:
A parameter specific for Connect Plus radio. Setting it to a value other than 0 denotes the
threshold RSSI level of radio channel. As the signal level is constantly monitored, any higher
number indicates that RF coverage is low, or that Connect Plus controller is down. Setting it to
0 disables this feature.
Radio configuration timeout (sec) <1-255> [30]:

For MotoTrbo Connect Plus radio. The period of time the network waits for a successful
connection to the radio upon powering up radio or RTU. If the connection is not completed
within this period, MOSCAD marks the port as Failed, but the configuration continues. If
configuration fails, it means that either there is no connection with the radio, or it is connected
but not "registered" (its signaling mode is not Connect Plus, or RSSI is lower than threshold).
Configuration status can be checked using the Error Logger and Software Diagnostics device
LIN1L Level 0, 101.
Get radio status sample time <1-255> sec [10 sec]:

For MotoTrbo Connect Plus radio. Once the radio is connected (via XCMP/XNL), the RTU
monitors it periodically to see that it is still connected, its signaling mode is Connect Plus, and
RSSI higher than threshold. This parameter determines how frequently this check is performed.
Number of configuration attempts to reset radio [3]: <0 to 255>

For MotoTrbo Connect Plus radio. If the RTU fails to connect with the radio, it can restart the
connection with it. This parameter determines how many failed attempts to connect the modem
are required before restarting it. This parameter is reserved for future use.
Wait time after Reset radio (sec) [5]: <0 to 255 seconds>
For MotoTrbo Connect Plus radio. It specifies how long to wait after restarting the USB
connection before attempting to connect again. This parameter is reserved for future use.
General MDLC Parameters

To see the advanced MDLC parameters which are not associated with a specific port, click the
General link.
Application manager workspace (bytes) <2000-40000> [4000]:

The workspace allocated to MDLC applications (for the transmission and reception of data
frames). The end-user is not expected to modify this parameter as it is reserved for the software
engineer’s development needs. It enables the engineer to accurately determine the memory
requirements of the MDLC applications.
Stack size of application manager task (bytes) <4000-10000> [8048]:

The size of the stack to be allocated for the MDLC application manager task.
A-12
Encryption/Compression buffer length (bytes) <0-100> [0]:

For future use.
Number of retries to declare TX FAIL <1-5> [4]:

Number of retries at session oriented logical channel level after which the Transport Layer
declares that transmission to destination site has failed.
Number of retries to declare 'Logical channel BUSY' <1-10> [5]:

When the source site sends frames to a destination site and receives a “logical channel busy”
signal (because the channels are busy transmitting data from other applications that already
accessed them), it retries as many times as determined in this parameter. After this pre-defined
number of retries, the source site declares the channel as being “busy”.
Number of transmitted frames in one BURST <2-32> [4]:

Number of MDLC frames that are sent in a single burst after which the Transport Layer waits
for ACK from the destination site before it sends the next burst.
Number of entries in transmit queue <5-32> [16]:

Number of MDLC frames the Transport Layer is capable of receiving from upper layers
(Application, Presentation and Session) for transmission. When this number is reached, the
Transport Layer signals to the application to stop sending frames until it makes room for more
frames. This number should be equivalent to twice the size of a burst or more.
Number of entries in receive queue <5-32> [32]:

The number of MDLC frames the receiving site is capable of handling on their way to the
upper layers. This number should be equivalent to twice the size of a burst or more.
Number of entries in temporary queue <5-64> [64]:

The number of MDLC frames the receiving site is capable of handling on their way from the
lower layers (Data Link Reception, Network, Transmission Multiplex).
Task suspension between transmitted frames (msec) <0-1000> [50]:

A delay that can be inserted between transmissions of frames in order to optimize CPU
allocation to other processes (especially to processes that have a priority level which is lower
than that of the application).
Interval between TX retries (sec) <1-1000> [20]:

The interval of time that should elapse between two retries at Source/Destination level. This
period of time starts after the Data Link layer finalizes the transmission of a frame (that is, after
it received an appropriate ACK or exhausted all retries for a frame that was not acknowledged).
Interval between 'Logical channel BUSY' retries (sec) <1-1000> [10]:

The waiting time between retries if the receiving end issued a BUSY signal (because all of its
logical channels were busy).
A-13
Delay after last received frame for partial ACK (sec) <1-1000> [5]:
If the called unit receives only some of the frames that were supposed to arrive in one burst, it
waits a certain period of time, defined in this parameter, before it issues a partial ACK at
Source/Destination level.
Interval before starting 'IS SESSION ON' checks (sec) <1-1000> [325]:
The period of time that should elapse before the “is session on” check takes place. See next
parameter.
Number of 'IS SESSION ON' checks (-1 = Forever) <-1-20> [3]:

If a period of silence is detected in the channel at source/destination level, a special mechanism
checks whether the logical channel is still available. This parameter determines the number of
times the channel is checked for availability. In any case, the first “is session on” check does
not take place before the timeout defined in the previous parameter.
Interval between 'IS SESSION ON' checks (sec) <1-1000> [120]:

The interval of time between two “is session on” checks. See previous parameter.
Period of time that a message is waiting in mailbox <5-255> sec. [10]:

The amount of time that a data frame remains in the receive buffer. If the application does not
retrieve it during that time, the data frame is deleted.
Minisession RTU-to-RTU number of boxes <1-31> [31]:

The number of boxes allocated at any given time for handling data frames in RTU-to-RTU
communication (received, transmitted, waiting for answer, empty).
Data frames are the information stored in Txbuf in case of transmission, and in Rxbuf in case
of reception.
Minisession RTU-to-RTU number of TX retries <0-20> [1]:

The number of retries that should take place at source/destination level if an answer was not
received for a transmission via SndFrm (and not via TxFrm).
Minisession RTU-to-RTU Interval between TX retries <1-1000> sec [60]:

The interval of time that should elapse between retries. This period of time starts after the Data
Link layer of the MDLC protocol finalizes the transmission of a frame (that is, after it received
an appropriate ACK or exhausted all retries at From/To level).
Minisession RTU-to-RTU Password <Enable/Disable> [Enable]:

Enables the user to add a communication password to data frames. The value of this parameter
must be identical in both the transmitting and receiving side.
Minisession RTU-to-RTU number of channels <0-10> [2]:

The number of channels (means of associating inter-process communication between a user
application and MDLC) allocated at any given time for RTU-to-RTU communication
(received, transmitted, waiting for answer, empty). When developing a ‘C’ application, set this
parameter so that there is one channel per each thread performing RTU-to-RTU
communication.
A-14
Minisession Event and Burst RTU To RTU number of boxes <1-31> [31]:
The number of boxes allocated at any given time for transmitting data frames via the Burst and
TxEvnt functions.
Minisession Event and Burst RTU To RTU number of TX retries <0-20> [1]:
Number of retries to be performed by the RTU towards the central unit, if it does not receive
“Application Data-Ack from central” to Burst or TxEvnt calls. If the value of the “Application
Data-Ack from central” is NO, this parameter is irrelevant (because the system relies on ACK
at Data Link level, that is, at From/To level, and does not need any further acknowledgments at
RTU/Central Unit level).
Minisession Event and Burst RTU To RTU Interval between TX retries <1-1000> sec [60]:
The interval of time that should elapse between two retries from the RTU towards the central
unit. (Retries may be requested if the RTU does not receive “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 relies on ACK at Data Link level, that is, at From/To level, and does not
need any further acknowledgments at RTU/Central Unit level).
Minisession Event and Burst RTU To RTU Password <Enable/Disable> [Enable]:

Enables the user to transmit events of bursts with a communication password. The value of
this parameter must be identical for all RTUs and the central unit.
Minisession Event and Burst number of channels <0-10> [1]:

The number of channels (means of associating inter-process communication between a user
application and MDLC) allocated at any given time for transmission of events and bursts..
When developing a ‘C’ application, set this parameter so that there is one channel per each
thread performing Event and Burst communication.
Minisession Event and Burst Application data ack from central [Yes]:
The valid values are:
No There is no need for ACK from the central unit at RTU/Central Unit level.
The system relies on Data Link ACK (at From/To level).
Yes The system requires that the central unit issues ACK to the RTU
(RTU/Central Unit level), in addition to Data Link ACK.
Minisession Broadcast (group call) number of TX retries <0-20> [0]:

The number of retries that should take place at source/destination level if an answer was not
received for a transmission via SndFrm (and not via TxFrm).
A-15
Minisession Broadcast (group call) number of boxes <1-31> [31]:

The number of boxes allocated for storing frames that were broadcast from the central unit and
that are to be processed by the RTU.
The RTU scans the box queue with intervals of 1 second, and updates the Qualifiers table
accordingly. Increase this value if the reception rate is greater than the queue scanning rate.
Minisession Broadcast (group call) Interval between TX retries <0-1000> sec [0]:
The interval of time that should elapse between retries. This period of time starts after the Data
Link layer of the MDLC protocol finalizes the transmission of a frame (that is, after it received
an appropriate ACK or exhausted all retries at From/To level).
Minisession Broadcast (group call) password <Enable/Disable> [Enable]:

Enables the user to transmit group calls with a communication password. Change the default if
the central unit is capable of broadcasting frames without a password.
The value of this parameter must be identical for all RTUs and the central unit.
Minisession Broadcast (group call) number of channels <0-10> [1]:

The number of channels allocated for broadcasting from the central unit and that are to be
processed by the RTU.
Number of MASTER logical channels <0-5> [5]:

Number of logical channels in the MDLC protocol capable of initiating communication via a
session oriented channel. Do not change this value (it should remain 0) since in the current
version there is no master application in the terminal unit. For ACE IP Gateway, this value is
set to 64 by default.
Number of SLAVE logical channels - <0-7> [5]:

Number of MDLC logical channels that can be accessed through one or more masters
simultaneously.
Stop transmitting 'reset ack' after <5-10000> sec [100]:

The period of time during which a Reset ACK should be transmitted to a unit that is expected
to return a void frame at Transport Multiplex level for each Reset ACK. After the period of
time specified here, the unit stops sending Reset ACKs in order to identify another reset
situation, should it occur.
Maximum allowed delay for a duplicate frame <5-200> sec [30]:

A frame that is received again during this period of time is considered a duplicate, and
discarded. If it arrives after this time, it is considered to be a new frame.
'Hole declaration' time out <1-30000> sec [30]:

The period of time during which frames that failed to arrive as part of a chain are allowed to be
retried at Data Link level. This timeout is calculated as a function of the number of retries and
the data speed.
Restart declaration time out <5-200> sec [30]:

Time interval between two Restart control frames at Transport Multiplex level.
A-16
Allowed reception range from 'expected frame' <4-128> [16]:

The gap that causes the unit to move to synchronization at the Transport Multiplex level. For
example if the value is 16 and frame x+16 arrives while x was expected, synchronization will
take place.
Maximum range to declare 'Duplicate frame' <4-128> [10]:

The allowed interval between retried frames. For example, if the value is 16 and x-16 arrived
while x is expected, the unit moves to perform synchronization as in the previous parameter.
Send broadcast reset after restart <Yes/No> [No]:

Specify Yes to broadcast to all units defined after Reset Load in order to synchronize at
Transport Multiplex level.
Time out for URGE transmission after hole detection (sec) <0-3000> [15]:
The period of time after which an “urge” frame is issued if a gap is formed at the Transport
Multiplex level. A response to the urge frame means that the gap will never be filled since all
Data Link layer retries have already been exhausted.
Number of retries for 'URGE frame' <0-9> [0]:

The number of times an urge frame will be retransmitted.
Size of TX queue (number of frames) <30-200> [80]:

Since Transport Multiplex consumes buffers for transmission, the number of buffers is limited
via this parameter in order to prevent the TX heap from being emptied completely.
Number of formatted buffers in TX-heap <50-2000> [350]:

The number of formatted buffers designed for RTU-to-RTU burst, event, burst seq, and event
seq transmissions, as well as for transmissions from 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.
IMPORTANT: Each buffer consumes about 250 bytes of RAM.
Number of formatted buffers in RX-heap <50-2000> [500]:

The number of formatted buffers designed for RTU-to-RTU burst, event, burst seq, and event
seq receptions, as well as for 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.
IMPORTANT: Each buffer consumes about 250 bytes of RAM.
Formatted buffer size <160-2000> byte [160]:

The size of the formatted buffer.
Unformatted (Adapter) buffer size <120-2000> bytes [120]:

The size of the unformatted buffer that serves as asynchronous port. The overhead is 15 bytes.
See the advanced physical parameter Number of idles to announce 'End of RX'.
A-17
Number of buffers in ladder-diagram user port <0-200> [40]:

Number of buffers for transmission and reception in the user port. For each user port the value
of this parameter must be at least 17.
Ladder-diagram user port buffer size <0-1000> byte [56]:

The size of the buffer used for transmission and reception. It defines a user port, including
buffer management overhead ( 15 bytes). If the user port is used for communication with the
terminal, the default size is enough. If the communication protocol is applied to the user port (if
the port is to handle larger quantities of data), it is advisable to increase the buffer size
according to scan time. The buffers should be sufficient to store all characters received during
one scan time. For example, under a data speed of 9600, each character 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 connected service-users with 10 msec device <10-300> [150]:

The 10 msec task enables different modules to perform specific activities with a resolution of
10 msec. This is achieved by letting each module link itself to the 100 msec task. The number
of service users (modules) depends on the configuration and sometimes it may be necessary to
increase the value of this parameter (if the configuration includes more modules than the
default number specified here).
Number of 10 msec ticks passed before declaring error <3-10> [5]:

The operating system is supposed to activate the 10 msec task every 10 msec. If it fails to
activate the task as many times as the number specified in this parameter (for example, 5 means
if the system fails to activate the task during 50 msec), an error message is sent to the Error
Logger.
This is not a fatal error. If the system fails to activate the task this means that it is experiencing
an unusual burden (in which case it is advisable to locate the origin of the problem).
10 msec stack size (bytes) <0-8000> [8000]:

The size of the 10 millisecond timer stack. When a user connects a routine to a specific timer,
the timer stack size may need to be increased if the routine activates functions which in turn
activate other functions.
Number of connected service-users with 100 msec device <10-300> [30]:

The 100 msec task enables different modules to perform specific activities with a resolution of
100 msec. This is achieved by letting each module link itself to the 100 msec task. The number
of service users (modules) depends on the configuration and sometimes it may be necessary to
Number of 100 msec ticks passed before declaring error <3-10> [4]:
The operating system is supposed to activate the 100 msec task every 100 msec. If it fails to
if the system fails to activate the task during 400 msec), an error message is sent to the Error
Logger.
A-18
100 msec stack size (bytes) <0-8000> [8000]:

The size of the 100 millisecond timer stack. When a user connects a routine to a specific timer,
the timer stack size may need to be increased if the routine activates functions which in turn
Number of connected service-users with 1 sec device <10-300> [30]:

The 1 sec task enables different modules to perform specific activities with a resolution of 1
sec. This is achieved by letting each module link itself to the 1 sec task. The number of service
users (modules) depends on the configuration and sometimes it may be necessary to increase
the value of this parameter (if the configuration includes more modules than the default number
specified here).
1 sec stack size (bytes) <0-8000> [8000]:

The size of the 1 second timer stack. When a user connects a routine to a specific timer, the
timer stack size may need to be increased if the routine activates functions which in turn
Number of 1 sec ticks passed before declaring error <2-5> [4]:

The operating system is supposed to activate the 1 sec task every 1 second. If it fails to activate
the task as many times as the number specified in this parameter (for example, 4 means if the
system fails to activate the task during 4 seconds), an error message is sent to the Error Logger.
Number of connected service-users with 1 min device <10-300> [30]:

The 1 min task enables different modules to perform specific activities with a resolution of 1
min. This is achieved by letting each module link itself to the 1 min task. The number of
service users (modules) depends on the configuration and sometimes it may be necessary to
1 min stack size (bytes) <0-8000> [8000]:

The size of the 1 min timer stack. When a user connects a routine to a specific timer, the timer
stack size may need to be increased if the routine activates functions which in turn activate
other functions.
Number of 1 min ticks passed before declaring error <2-4> [4]:

The operating system is supposed to activate the 1 min task every 1 minute. If it fails to
if the system fails to activate the task during 4 minutes), an error message is sent to the Error
Logger.
A-19
Ladder received-frame-sequence queue size frames <1-30> [10]:

The maximum number of frames that can be stored in the frame sequence device queue waiting
to be 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.
Time sync method <Extended sync/Legacy sync> [Legacy sync]:

Define what method used when sending time synchronization.
Extended sync – RTU sends sync protocol frames containing time zone and password,
with nanosecond resolution. (1 millisecond accuracy over
synchronous media (radio) and over asynchronous RTU to RTU
media.) :
Note: The RTU checks the password in extended sync frames and
authenticates sync messages before updating the clock. If it does not
match it is rejected. See SW Diagnostics Device TIMESYN level 10
for statistics of received/ignored sync frames.
Legacy sync – For synchronizing legacy MOSCAD RTUs. No time zone or password,
with milliseconds resolution. Assumes sending RTU is in the same
time zone. (5 millisecond accuracy)
What to do with received legacy sync messages? [Don’t Ignore legacy sync messages]:
The valid values are:
Ignore legacy sync messages – Do not update the clock from when legacy sync
messages are received.
Don’t Ignore legacy sync messages – Update the clock from when legacy sync messages
are received.
Remote Failed Links Table entry timeout (min) <0-255> [15]:

When the Remote Failed Links Table feature is enabled, this parameter sets the maximum time
an entry will live in the Remote Failed Links Table. When the timeout has expired, the entry is
removed from the table.
Addr. range response for 'All RTU simulation' <Site ID +- (-100)-100> [0]:
Assigning alternate addresses to an RTU. If the basic address is X and the range is Y, then the
unit responds to all calls in the range of {X,X+1,...,X+Y}. If the range is -Y, the unit responds
to all calls in the range of {X-Y, X-Y+1, ..., X}.
This parameter is for field simulation in laboratory conditions. For sites that support
redundancy, this parameter is modified by the STS. See the “RTU Redundancy” section of the
ACE3600 STS Advanced Features manual for more details.
System configuration stock size <1-50> [1]:

Number of paths the Network layer is allowed to learn. This parameter is for future use. In the
current version, Network can learn only one path even if a different value is specified.
A-20
Do not route returned frame <Yes/No> [YES]:

When the Remote Failed Links Table feature is enabled, this parameter determines whether a
returned frame from a remote failed 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.
Maximum rows in IP conversion table per link ID <1-65535> [200]:

The maximum number of entries in the IP conversion table for each link ID. The IP
conversion table specifies Site IDs and IP addresses.
Time Zone Parameters

Time zone offset [UTC]:
The time zone offset of the RTU. Select the location from the drop-down list.
Note: The time zone definitions incorporate daylight saving configuration.
Power Management Parameters

Voltage low level <8-30> [8]:
The power level (in volts) at which the power level is considered low and the unit shuts down.
Voltage normal level <8-30> [8.5]:

The power level (in volts) at which the power level is considered normal and the unit resumes
full functionality.
ACE1000 I/O Parameters

The following parameters can be set for I/Os on the ACE1000 RTU CPU or I/O expansion
module. Click the relevant tab to view the parameter to be changed.
Each I/O has a Name and Description parameter which can be modified.
DI Parameters
The following parameters can be set for the DI on the Alerts or Filter tabs.
Notify SCADA Center of Digital Input (DI) state changes: [COS]

Send notification when the DI has any change of state (COS), when it goes to NO, when it goes
to NC, or disable change notification.
High level filter

Persistence <0-240> sec [0]:
The change to the DI is only taken into account if the value remained stable for the specified
number of seconds. This filters out temporary changes in the input.
A-21
Low level filter

Debounce msec [30]:
The time frame (in milliseconds) required to filter out input bounce and get one signal from the
DI. This determines how long a DI COS should remain stable before it is counted as a change.
AI Parameters
The following parameters can be set for the AI on the Scaling, Filter, Alerts, and Type tabs.
Engineering units
The engineering units used to convert the AI raw data to a user defined scale.
Scaling range
The Min value and Max value of the range used to convert the AI raw data to a user defined
scale.
High level filter

Persistence <0-240> sec [0]:
The change to the AI is only taken into account if the value remained stable for the specified
number of seconds. This filters out temporary changes in the input.
Low level filter

Smoothing <1-128> [30]:
The number of samples taken from the sensor’s AI values that are required to calculate an
average value and produce a more stable value. If this parameter is set 1, no calculation is
done. If this parameter is set to the default 30, the average of the last 30 sampled values is
calculated. The ACE1000 samples the AI sensor every 160 msec with AC noise filtering , or
every 90 msec without AC noise filtering.
Notify [Enabled]:
By default, notification is sent to the SCADA Center for all AI value changes within the Min
Value-Max Value range. You can change the default range by dragging the small blue
pointers to set the Low, Low-Low (Min Value), High and High-High (Max Value). Unselect
to disable notifications.
Change resolution [10]:

The percentage of AI value change resolution at which notification is sent to the SCADA
Center.
Filter noise generated by electrical network

To filter noise generated by the electrical network, set this parameter to the electric current
frequency in your country. Can be one of: Disable (default), 50MHz, or 60 MHz.
Type [Current +4mA to +20mA]:

The type of connected input module. Can be one of: Current 0 mA to +20 mA, Current +4 mA
to +20 mA (default), Voltage 0 V to +5 V).
A-22
DO Parameters
The following parameters can be set for the DO.
Show back indication

Enable this parameter to show the actual state feedback, when changing the status of the digital
output.
Reset at startup <Yes/No> [Yes]

Enable this parameter to reset the DO (ML DOs 6-9 only) when the RTU is started up (after
Power OFF). When disabled, the DO retains the value from the time of the RTU reset (after
Power OFF).
Reset at startup is operational only after the power is off.
In case DOs (Both ML and EE) are ON, after reset/reboot (power is not off), the DO maintains
its last value. This means that if a DO was on, after the reboot (without power off), it is still on,
despite the fact that it was configured to reset at startup in case of ML. In EE, there is no option
to reset at startup.
If a user wants to reset DO at startup, the following operation must be performed in the
application:
1. Use any user flag and add state/condition if a user flag is 0 - Clear Physical DO/AO.
2. Set the user flag to 1.
AO Parameters
The following parameters can be set for the AO on the Type or Scaling tabs.
Type [Current +4mA to +20mA]:

The type of AI. Can be one of: Current 0 mA to +20 mA, Current +4 mA to +20 mA (default),
Voltage 0 V to +10 V).
Engineering units
The engineering units used to convert the AO raw data to a user defined scale.
Scaling range
The Min value and Max value of the range used to convert the AO raw data to a user defined
scale.
ACE1000 Settings
The following settings can be changed from the gear icon on the top of the
window.
A-23
MDLC System
System Address [0]:
The MDLC communication system address. Range: 0-65287. This parameter is visible only on
the FEP.
Legal
Login user notice
The text displayed to the user after logging in.
Logging
Records per page
Error Log [10]:
Event Log [10]:
The number of error log and event log records displayed per page.
A-24
Appendix B: ACE1000 Easy Configurator
Icons
The following icons are used in the ACE1000 Easy Configurator GUI.
Table B-1 ACE1000 GUI Icons
Icon Description
Configure general parameters.
Configure application parameters.
Define rules for RTU application.
Manage users.
Add communication.
Add RTUs.
Set date and time.
Retrieve diagnostics from the RTU/FEP.
Retrieve errors, warnings and information from the RTU/FEP Error Log.
Retrieve I/O events from the RTU.
Synchronize the RTU date and time with the FEP.
Reset the unit.
Poll the unit from the FEP.
Unit has been changed and needs to be deployed.
Unit has been changed and needs to be deployed.
Configuration has been changed and needs to be saved.
Monitoring mode menu.

Duplicate unit.
Delete port, unit or user.

Edit port and auxiliary power settings.
B-1
Appendix B: ACE1000 Easy Configurator Icons
Icon Description
Edit user.
Configuration parameter default value has been changed.
In Monitoring mode, the following icons are used in the ACE1000 Easy Configurator GUI.
Table B-2 ACE1000 Status Indications Icons
Icon in FEP Icon in FEP Description

RTU View System View
Communication with FEP OK. Tooltip
shows last good communication and last bad
communication.
Communication with FEP failed.
Unit power level (also visible in RTU view

from RTU)
Unit has errors in Error Log. (also visible in
RTU view from RTU)
Communication between RTU CPU and I/O
module has failed.
Unit configuration has changed and needs to
be uploaded or deployed.
B-2
Appendix C: ACE1000 MODBUS
Configuration
The MODBUS protocol is supported in ACE1000-only systems and in mixed systems (ACE3600 +
ACE1000 + Legacy MOSCAD RTUs), to provide the SCADA center with data from the field.
ACE1000 MODBUS Support in a Mixed System

In a mixed system, the ACE1000 RTU can be configured as:
 MODBUS master - for communication with PLCs
 MODBUS slave - for communication with the SCADA center
ACE1000 MODBUS Support in an ACE1000 System

In an ACE1000-only system, the ACE1000 RTU can be configured as:
However, the SCADA generally communicates with the ACE1100 FEP, and not directly with the
ACE1000 RTU.
In an ACE1000-only system, the ACE1100 FEP can be configured as:
Because the FEP is not connected to PLCs, configuration as MODBUS master is not relevant in the
ACE1000 concept.
C-1
Appendix C: ACE1000 MODBUS Configuration
MODBUS Address
In an ACE1000 system, the SCADA communicates with ACE1000 units using the MODBUS address
assigned during initial system configuration. MODBUS Address 1 is always assigned to the ACE1100
FEP. Each ACE1000 RTU is automatically assigned the next address, starting with MODBUS Address
2. The user is allowed to edit the MODBUS address, but each MODBUS address should be unique. The
MODBUS Address is displayed in the General dialog box with the site Name and Site ID parameters.
In a mixed system, the MODBUS Address for a MODBUS slave RTU is assigned manually.
The SCADA can communicate with an RTU directly or via the FEP.
ACE1000 Data Register Location

The SCADA communicates with ACE1000 units using the MODBUS address.
Using the proper function codes/MODBUS library APIs, the SCADA can access the ACE1000 unit data
(I/Os and system values) directly in its registers. This is unlike the ACE3600 data which is accessed
using a register mapping which corresponds to the ACE3600 database table, row and column.
The tables below list the register locations of the specific ACE1000 data. Table C-1 details the register
location of the specific ACE1000 I/O data. Registers are listed for I/Os on the Main board, I/Os on the
first instance of an I/O Expansion Module Type in the RTU, and I/Os on the second instance of the same
type. Table C-2 details the register location of system values on the RTU.
C-2
Table C-1 ACE1000 I/O Data Register Locations
I/O Data Register Location Register Location on I/O Register Location on I/O
(RTU Only) for Main Board Expansion Module Expansion Module
I/O (1st Instance) (2nd Instance of Same
Type)
DI Register 0 Register 3 Register 15
DO Back Register 1000 Register 1001 Register 1009

Indication
AI N/A Register 0 Register 8
DO Register 0 Register 1 Register 9
AO N/A Register 0 Register 2
Table C-2 ACE1000 RTU System Values Register Locations
System Values Register Location Description

IS_ERROR_EXISTS Register 1000 0 – No (no error exists) or
1 – Yes ()
INPUT_VOLTAGE Register 1001 The last reading of the input
power level in millivolts
TEMPERATURE Register 1002 The last measured temperature
of the board in Celsius
IS_PB_ON Register 1003 Can be one of:
0 – No (pushbutton not pushed)
or
1 – Yes (pushbutton pushed)
IS_CONF_CHANGED Register 1004 Can be one of:
0 – No (configuration not
changed) or
1 – Yes (configuration
changed)
IO_MAIN_BOARD_STATUS Register 1005 Can be one of:
0 – OK
1 – Communication failure
(between CPU and expansion
module)
2- Configuration mismatch (actual
expansion is different that the
expansion specified in the
configuration.
4 – General error.
255 – Module is not configured.
C-3
System Values Register Location Description

IO_EXP_1_STATUS Register 1006 Can be one of:
0 – OK
1 – Communication failure
(between CPU and expansion
module)
configuration.
IO_EXP_2_STATUS Register 1007 Can be one of:
0 – OK
1 – Communication failue (between
CPU and expansion module)
configuration.
OPTION_BOARD_ID Register 1008 Can be one of:
1 – RS232 w/ AUX
2 – RS232 w/o AUX
3 – RS232 w/o AUX – ATEX
Table C-3 ACE1000 RTU/FEP User Table Data Register Locations
Data Type Location for the Number of elements Comments

first element
Bit Coil 2000 2000 – RTU

(Discrete)
250 – FEP (per RTU)
Integer Register 1000 6000 – RTU

(Holding
Register ) 250 – FEP (per RTU)
Long (2 Register 9000 2000 – RTU Register id jump in 2

Holding and is calculated by
Registers) 250 – FEP (per RTU) <9000 +
register_index*2>
C-4
Float(2 Register 7000 1000 – RTU Register id jump in 2

Holding and is calculated by
Registers) 250 – FEP (per RTU) <7000 +
register_index*2>
ACE1000 MODBUS Data Types

The MODBUS master can access the following data types/commands:
MODBUS Data Type Command MODBUS RTU Equivalent

Function
Code
Logic Coils Read 1 Discrete Output
Discrete Inputs Read 2 Discrete Input
Holding Registers Read 3 Value Input
Input Registers Read 4 Value Input
Logic Coils Write (single 5 Discrete Output
coil)
Holding Registers Write (single 6 Value Output
register)
Logic Coils Write 15 Discrete Output
Holding Registers Write 16 Value Output
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 C-4 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 C-4 ACE1100 FEP Polling Register Locations
Polling Values (FEP only) Register Location
C-5
Polling Values (FEP only) Register Location

SCADA Polling of RTUs Register 1001 = MODBUS address 2 (first
via FEP – Set register to 1 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 (e.g. 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
C-5 for the RTU Comm Status register locations in the FEP.
Table C-5 ACE1100 FEP Comm Status Register Locations
Comm Status Values (FEP Register Location

only)
Retrieve RTU Comm Register 2001 = MODBUS address 2 (first
Status from the FEP RTU)
.
.
.
Register 3000 = MODBUS address 1001 (up to
1000 RTUs)
Port Configuration for ACE1000 MODBUS

ACE1100 FEP Port Configuration in an ACE1000 System
In an ACE1000 system, the FEP port is configured using the Web browser-based ACE1000 Easy
Configurator. Drag the interface type from the Add Communication General list to the port.
In the figure below, the ACE1100 FEP serial RS232 port is configured as connected (as a MODBUS
slave) to a SCADA center.
C-6
MODBUS Configuration
MODBUS Master Performance
MODBUS Master supports the following communication media: RS48, RS232, and IP.
The time needed to sample 6 PLCs in IP was checked to be 201 milliseconds.
For RS232, one RTU was sampled in different Baud rates:
RS 232 9600 Bps 19200 Bps 38400 Bps 57600 Bps 115200 Bps
705 ms 359 ms 183 ms 124 ms 63 ms
For RS485, six RTUs were sampled in different Baud rates:
RS 485 – six 9600 19200 38400 57600 115200

slaves Bps Bps Bps Bps Bps
4:182 ms 2:117 ms 1:075 ms 735 ms 375 ms
C-7
Configuring MODBUS Master

Perform this procedure to configure MODBUS Master on RTU.
C-8
The tag generation feature for all physical I/Os and user data is available. Tags also support the
MODBUS virtual I/Os.
1. After logging on to RTU, in the Main Board, click Add Communication.
2. Drag and drop MODBUS Master onto LAN or Serial port and from the pop-up, select RS485
or RS232.
3. From the right-hand menu, select Application.
4. In the Application screen, from the left-hand panel, select MODBUS Master.
5. Click RS232/RS485 Physical and modify the following parameters: Data speed, Parity,
Number of stop bits, Number of data bits.
6. If you want to change the default parameters, click Comm. Setup and modify the values
according to your requirements:
a) In the Slave Response Timeout field, type in the duration between retries specified in the
Max failures before declaring comm fail field.
b) In the Polling Interval Time (ms) field, set the interval time for the master to poll all slaves.
Setting this parameter to 0 disables polling. You can use C or IEC APIs to poll all slaves
manually.
If you are using power management and sleep functionality, disable automatic polling.
c) From the Byte Order drop-down list, select ABCD or DCBA, according to PLC behavior.
d) In the Max failures before declaring comm fail field, type in the number of retries the
system should attempt before the slave failure is declared.
The serial on the plug-in board is supported for PI1/PI2.
In case of PLC fail, after an X -parameter in Master configuration indicates a PLC fail, stop
communication with this PLC in the current cycle.
If PLC fails in the next cycle, make one attempt to communicate with this PLC.
C-9
Adding and Modifying MODBUS Slaves
Perform this procedure to add and configure Slaves for MODBUS Master in your system.
1. From the right-hand menu, select Application.
2. In the Application screen, from the left-hand panel, select MODBUS Master.
3. Click Slaves→Add and select one of the following options:
 If you want to add multiple Slaves, click Add multiple and in the pop-up, specify the
number up to seven Slaves.
 If you want to clone existing slaves, click Clone. Change the IP of the cloned item.
Only slaves with the same addressing data are supported. The addressing data are common to all
slaves.
4. Select MODBUS addresses and in the parameter fields, specify the values according to the
connected PLC.
5. To modify Slave parameters, expand the node of the Slave whose parameters you want to modify.
Click General & Comm. Setup and edit the parameters.
6. Add discrete inputs by selecting Discrete Input(s), clicking Add, and performing one of the
following actions:
 If you want to add multiple discrete inputs, select Add multiple and in the pop-up, enter
the number from 1 to 24.
 If you want to clone existing inputs, select Clone. Change the IP of the cloned item.
7. For each discrete input, perform the following actions:
a) In the Notify on section, set the reporting to FEP dependent on the change of state:
 If you do not want any bursts, select No notifications.
C-10
 If you want bursts when any change between on and off states occurs, select Notify on
rising and falling edge.
 If you want bursts when a change from on to off occurs, select Notify on falling edge.
 If you want bursts when a change from off to on occurs, select Notify on rising edge.
b) In the Persistence (sec) <0-240> field, enter the duration for which you want the change to
persist before a burst.
8. Select Coil(s). Click Add and add up to 24 coils. If you want FEP notified when the state
changes, select the Notifications check box.
Notifications are for back indications.
9. Select Input Registers and click Input Register(s) 16-bit integer. Click Add and add up to 24
registers.
10. For input registers 16-bit integer, edit the following parameters:
a) Set the notification level by selecting one of the Input Registers state changes radio
buttons.
b) In the Persistence (sec) <0-240> field, enter the duration for which you want the change
to persist before a burst.
c) In the Low <-32767-32766> field, enter the low value, and in the High <-32767-32766>
field, enter the high value.
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 and the Event is recorded in Event
Logger. 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 take place again.
For Low and High values with persistence not equal to 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 and the Event is recorded in Event Logger. 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.
d) In the Delta <0-32766> field, enter the delta value.
When the value changes by the delta, the RTU bursts to FEP and the Event is recorded in
Event Logger.
11. Perform steps 9 and 10 for Input Register(s) 32-bit integer and Input Register(s) 32-bit
floating point.
C-11
12. Select Holding Registers and click Holding Register(s) 16-bit integer. Click Add and add up to
24 registers.
The Holding Registers option is used for controls.

13. Optional: If you want to delete any of the items, in a relevant view, select the item and click
Delete.
C-12
Appendix D: ACE1000 Use Cases
The following are the relevant use cases when defining, administering, and maintaining an
ACE1000 system:
• System Clean Install –for installing and configuring a new system, either via the FEP or
one unit at a time
• Disaster Recovery – for recovering the system after a disaster
• System Expansion – for adding RTUs to the system, either on-site or off-site
• System Expansion – for adding I/O expansion modules to RTUs in the system
• System Expansion – for changing the site configuration of a system
• System Upgrade – for upgrading to a higher ACE1000 version
• System Downgrade – for downgrading to a lower ACE1000 version
Note: Some of the procedures/steps are performed by field technicians and some by system
administrators.
Note: The ACE1000 units can be accessed by the Web browser based-ACE1000 Easy
Configurator tool from a PC, laptop, or other device running Google Chrome™.
Performing System-Wide Clean Install via the FEP

Follow this process to perform a system-wide clean install via the FEP.
1. Access the FEP for the first time:
a. Connect the PC/laptop to the FEP via the USB OTG port (RNDIS).
Result: The FEP distributes its IP address automatically to the PC/laptop. The user
can access the FEP using the ACE1000 Easy Configurator tool and can build the
system.
2. Define the project:
a. Create a project and add the RTU(s).
b. Configure each RTU (communication interfaces, I/Os, logical rules set.)
c. Deploy the FEP.
Result: A project is created on the FEP with a set of RTUs, each of which has a site
ID.
3. Define the RTUs:
D-1
Appendix D: ACE1000 System Use Cases
a. Connect to each RTU, one by one, via the USB OTG port (RNDIS).
b. On each RTU, define the site ID (per the configuration in the project on the FEP,)
using the ACE1000 Easy Configurator tool.
c. On each RTU, configure relevant communication parameters to enable access to

the RTU from the FEP.
d. Deploy the RTU locally.
Result: A system of RTUs with site IDs is ready to communicate with the FEP.
4. Deploy the configuration to the RTUs via the FEP:

a. Connect the partially configured RTUs to the network (e.g. LAN).
b. Deploy the configuration to the unit(s) using the ACE1000 Easy Configurator
tool. (The FEP automatically deploys the relevant configuration to the each unit.)
Result: A system consisting of fully configured RTU(s) and the FEP is ready.
Performing Clean Install One Unit at a Time

Follow this process to perform a system-wide clean install, one unit at a time.
1. Access the FEP for the first time:
a. Connect the PC/laptop to the FEP via the USB OTG port (RNDIS).
Result: The FEP distributes its IP address automatically to the PC/laptop. The user
can access the FEP using the ACE1000 Easy Configurator tool and can build the
system.
2. Define and export the project:
a. Create a project and add the RTU(s).
b. Configure each RTU (communication interfaces, I/Os, logical rules set.)
c. Export the project definition using the ACE1000 Easy Configurator tool and save
it on the PC/laptop.
Result: A project is created on the FEP with a set of RTUs, each of which has a site
ID.
3. Import the configuration to the RTUs:

a. Connect to each RTU, one by one, via the USB OTG port (RNDIS).
b. On each RTU, import the relevant RTU configuration from the project
configuration file exported to the PC/laptop.
D-2
c. Deploy the RTU locally.
Result: A system consisting of fully configured RTU(s) and the FEP is ready.
Replacing a Defective Unit on Site (Disaster Recovery)

Follow this process to replace a defective RTU (hardware failure) on site, using an existing
(previously exported) RTU configuration.
1. Access the new RTU for the first time:
a. Connect the PC/laptop to the RTU via the USB OTG port (RNDIS).
2. Import the RTU configuration:
a. Import the previously exported RTU configuration from the PC/laptop to the new
RTU, either from the project configuration file or from an RTU configuration file,
using the ACE1000 Easy Configurator tool.
3. Replace the defective RTU in the field:

a. Disconnect the defective RTU and connect the new RTU in its place.
Result: The system is completely operational.
Restarting a Unit (Disaster Recovery)

Follow this process to restart an RTU.
1. Access the RTU:
a. Connect the PC/laptop to the RTU remotely via the network, or locally via the
USB OTG port (RNDIS).
If you cannot access the unit, see the Troubleshooting chapter.
2. Reset the RTU:
a. Select the Reset command Reboot option, using the ACE1000 Easy Configurator
tool.
b. Reset the unit.
Result: The RTU restarts.
D-3
Restoring a Defective Unit to the Factory Default (Disaster

Recovery)
Follow this process to restore a defective RTU to the factory default.
1. Access the RTU:
a. Connect the PC/laptop to the RTU remotely via the network, or locally via the
If you cannot access the unit, see the Troubleshooting chapter.
2. Reset the RTU:
a. Select the Reset command Erase all flash option, using the ACE1000 Easy
Configurator tool.
b. Reset the unit.
Result: The RTU restarts with the factory default configuration and firmware version.
Adding and Configuring New RTUs On-Site (System

Expansion)
Follow this process to add new RTUs, on site.
1. Access the FEP:
a. Connect the PC/laptop to the deployed FEP remotely via the network, or locally
via the USB OTG port (RNDIS).
b. Add the new RTUs to the project and configure them, using the ACE1000 Easy
Configurator tool.
c. (Optional) Generate the new SCADA tags and load them to the SCADA.
d. Export the new RTU configuration or the updated system configuration (project) to
the PC/laptop.
Result: The updated system project includes the new RTUs and is available on the
PC/laptop.
a. Connect to the new RTUs, one by one, via the USB OTG port (RNDIS).
Result: The new, fully configured RTUs are ready to be installed.
D-4
3. Install the new RTUs in the field:
a. Install the new RTUs in the remote sites.
Result: The system is completely operational with the new RTUs.
Adding and Configuring New RTUs Off-Site (System

Expansion)
Follow this process to add new RTUs, off site.
1. Access the FEP:
a. Connect the PC/laptop to a non-deployed FEP remotely via the network, or locally
b. If the project is not defined on the FEP, import it from the PC/laptop, using the
ACE1000 Easy Configurator tool.
c. Add the new RTUs to the project and configure them.
d. (Optional) Generate the new SCADA tags and load them to the SCADA computer.
e. Export the new RTU configuration or the updated system configuration (project) to
the PC/laptop.
Result: The updated system project includes the new RTUs and is available on the
PC/laptop.
a. Connect to the new RTUs, one by one, via the USB OTG port (RNDIS).
Result: The new, fully configured RTUs are ready to be installed.
3. Install the new RTUs in the field:

a. Install the new RTUs in the remote sites.
b. Import the new system configuration from the PC/laptop to the FEP in the
SCADA center.
c. (Optional) Generate the new SCADA tags and load them to the SCADA
computer.
Result: The system is completely operational with the new RTUs.
D-5
Changing an Existing RTU Configuration On-Site (System

Expansion)
Follow this process to change an existing RTU’s configuration, on site.
1. (Optional) Physically connect new I/O elements:
a. Connect new expansion module(s) to the RTU.
b. Connect new I/O sensors to the new expansion module(s).
2. Update the RTU configuration:

a. Connect the PC/laptop to the deployed RTU remotely via the network, or locally
b. Add the new physical elements, or other configuration changes to the RTU
configuration, using the ACE1000 Easy Configurator tool.
Result: The RTU configuration is updated. The updated RTU notifies the FEP of the
configuration change.
3. Synchronize the system configuration with the modified site configuration:
a. Connect the PC/laptop to the FEP remotely via the network, or locally via the
b. Upload the site configuration from the updated RTU, using the ACE1000 Easy
Configurator tool.
Result: The FEP and system configuration is synchronized with the updated RTU
configuration.
4. (Optional) Generate SCADA tags:

a. If needed, generate the SCADA tags of the updated system configuration on the
FEP.
b. Upload the new tags to the SCADA system, and make the proper adjustments in
the SCADA computer.
Result: The SCADA system configuration is completely up-to-date.
Upgrading to a Higher ACE1000 version (System Upgrade)

Follow this process to upgrade an ACE1000 system to a higher version.
1. Save the current project configuration:
a. Connect the PC/laptop to the deployed FEP remotely via the network, or
locally via the USB OTG port (RNDIS).
D-6
b. Install the new kernel in the FEP and in the RTUs (locally or remotely), using
the ACE1000 Easy Configurator tool.
c. Install the new file system in the FEP and in the RTUs locally, using the
d. Update the Kinetis microcontroller firmware in the FEP and in the RTUs
locally. See Updating the Kinetis Microcontroller Firmware in the Operation
chapter.
3. Import the saved project configuration and deploy the units:
a. Import the saved project configuration from the PC to each RTU locally, using
b. Deploy the project configuration on each RTU locally.
c. Import the project to the FEP, using the ACE1000 Easy Configurator tool.
d. Deploy the FEP locally.
e. Deploy the RTUs from the FEP remotely.
Upgrading to a Higher ACE1000 Version by Installing

Bundle (System Upgrade)
Follow this process to upgrade an ACE1000 system to a higher version.
1. Save the current project configuration (For backup only):
a. Connect the PC/laptop to the deployed FEP/RTU remotely via the network, or
b. Export the ACE1100 FEP project configuration from the FEP to the PC, using
2. Connect the PC/laptop to RTU remotely via the network, or locally via the USB OTG
port (RNDIS).
3. Install Bundle. See Installing an Application, Package, or Bundle to a Site via FEP
procedure).
4. Connect the PC/laptop to FEP remotely via the network, or locally via the USB OTG
port (RNDIS).
5. Deploy FEP configuration
6. Deploy RTU configuration
D-7
Downgrading to a Lower ACE1000 version (System

Downgrade)
Follow this process to downgrade an ACE1000 RTU to a lower version (for ACE1000 version
1.5).
7. (Optional) Save the current project configuration:
a. Connect the PC/laptop to the deployed FEP remotely via the network, or
b. Export the ACE1000 project configuration from the FEP to the PC, using the
8. Downgrade the kernel, file system, and microcontroller firmware in the RTU:
a. Connect the PC/laptop to the deployed RTU remotely via the network, or
b. Install the new file system in the RTU locally, using the ACE1000 Easy
Configurator tool.
c. Install the new kernel in the RTU (locally or remotely), using the ACE1000
Easy Configurator tool.
Update the Kinetis microcontroller firmware in the FEP and in the RTUs locally. See
Updating the Kinetis Microcontroller Firmware in the Operation chapter.
D-8
Appendix E: CODESYS IEC61131-3
Programmer Applications
For CODESYS IEC61131-3 Programmer Applications, see the ACE1000 IEC61131-3

Developer's Guide. The ACE1000 IEC61131-3 Developer's Guide manual contains the
information which was covered in this Appendix in the past releases of this manual.
E-1
Appendix F: ACE1000 Design Guidelines
The ACE1000 Easy Configurator provides many basic default values. When planning and
setting up an ACE1000 system using the ACE1000 Easy Configurator, special considerations
and tuning of parameters may be required for various media and transmission types.
For all media types, basic configuration must include the following:
• Unit time zone
• Communication between the FEP and RTU
Setting Time Zone

When setting up your system, you must set the time zone for each unit (default is UTC).
1. First connect the FEP to a time source (GPS/NTP).
2. Set the FEP time zone in the Application -> Time Zone-> Time zone offset parameter
and apply to all units.
3. Deploy the FEP.
4. Deploy the RTUs.
5. Sync the time for all units in the system.
ACE1000 System with ASTRO IV&D Radio

To define an ACE1000 system with ASTRO IV&D radio, do the following:
1. Define a USB port to be used with the radio.
2. Set the auxiliary power voltage level for the radio.
3. Set the following parameters to the value specified in []:

In the ASTRO infrastructure, set the parameter below to No.
Affiliation Inactivity Timeout Enabled
F-1
Appendix G: ACE1000 Design Guidelines
ACE1000 System with MotoTrbo Digital Radio

To define an ACE1000 system with MotoTrbo radio, do the following:
1. Define a USB port to be used with the radio.

ACE1000 System with MotoTrbo Connect Plus

To define an ACE1000 system with MotoTrbo connect plus radio, do the following:
In ACE1000 RTU:
1. Define a USB port to be used with the radio as MotoTrbo connect plus radio.
2. Set radio ID according to the XPR5350 radio CPS.
4. Click Applications.
5. Click MDLC.
6. Click USB2 and set the following parameters to 0:
Check alive timeout (sec) <0-65535> [0]

Poll interval (sec) <0-255> [0]
Maximum number of polls <0-255> [0]
7. Press General and set the following parameters to the value specified in general []:

Delay after last received frame for partial ACK (sec) <1-1000> [15]
F-2
In ACE1000 FEP:
Define a LAN port to be used as XRT Gateway. Verify that there is a LAN connection between
the FEP and XRT Gateway, for example by pinging its IP address (not necessarily within the
same subnet).
1. Set IP address, network mask and default gateway.

2. If MDLC over IP communication over LAN with STS or other RTUs is needed, set public
IP address.
3. For Connect Plus communication, set XRT datapath ID according to the XRT
Configuration.
4. Click Applications.
5. Click MDLC and ETH1.
6. Set Number of Link IDs to 2.
7. Set the link names. Set first link ID for MDLC over IP (LINE1) and the second link for
MDLC over Connect Plus (LINE7).
8. Set the first appearance of “Enable non-IP communication to XRT Gateway” as
DISABLE, and the second as ENABLE.
That means LINE1 is used for MDLC over IP, and LINE7 is used for MDLC over Connect
Plus.
9. Set the XRT Gateway IP address to the IP address of XRT.
10. Set the user name and password assigned in XRT for ACE1000 FEP.
11. Click General and set the following parameters to the value specified in general []:

Delay after last received frame for partial ACK (sec) <1-1000> [15]
ACE1000 System with Dynamic IP

To define an ACE1000 system with dynamic IP, do the following:
1. Define the Ethernet port and IP address of the units. The FEP LAN port must be defined
as Static LAN.
Health check time interval (min) <1-1440>

In a system with dynamic IP addresses, shorten the Health check time interval parameter to
avoid losing communication if the RTU’s IP address was changed and FEP is not aware of the
change.
Note: First deploy the RTUs with the FEP IP. Then burst the RTUs IPs and the FEP learns the
IP addresses of the RTUs in the system.
F-3
ACE1000 System with Serial RS485 Link

To define an ACE1000 system with serial RS485 communication, do the following:
1. Define the S1 port as Serial RS485 Multidrop.
2. Set the following parameter to the value specified in []:
Channel monitor time resolution <10-2500> msec [200]:

Note: The channel time resolution parameter for RS485 must be at least 60.
ACE1000 System with SCADA

To define an ACE1000 system with SCADA:
1. Configure either a serial or LAN port as SCADA center. For a serial port, specify either
via RS232 or RS485.
2. Configure the FEP and RTUs.
3. Generate the SCADA tags.
4. Import the tags file to the SCADA.
Note: For Wonderware, edit the tags file and update the PC name.
ACE1000 System with PLC

To define an ACE1000 system with PLC, the ACE1000 RTU must be configured as a
MODBUS slave PLC.
• Configure either a serial or LAN port as PLC.
ACE1000 System with Redundant Links

To create an ACE1000 system with redundancy, define two communication interfaces for the
FEP/RTUs. If one interface fails, the second interface continues to enable communication with
the unit.
ACE1000 System with Burst Transmissions

By default, the ACE1000 I/Os send burst transmissions whenever there is a Change of State
(COS).
F-4
To change the default, click on the I/O, and modify the default setting of the attribute (e.g.
Notify SCADA Center of Digital Input (DI) state changes, Show back indication, Notify).
ACE1000 System with Automatic Polling

By default, the system has automatic polling from the ACE1100 FEP to the ACE1000 RTU,
with the following settings. If you want to change the polling cycles, change them:
1. Set the following Application-> ACE1100 – FEP parameters to the value specified in []:
Time interval between periodic polling cycles (min) <1-1440> [60]

Time interval between units in each periodic polling cycle (sec) <10-300> [300]
2. Click OK and deploy the FEP configuration.
ACE1100 FEP Capacity Requirements

ACE1100 Front End Processor maximum configuration size is 20 MB.
Per this limit, the user needs to allocate the configuration resources between additional IO
EXP, Third-party protocol MODBUS Master and its slaves, and ACELogic entities.
To calculate the actual size of a certain configuration consider the following components size:
One RTU with no I/O Expansion – 25 kB + one I/O Expansion 6 kB – 31
One MODBUS Master and 1 slave – 110 kB
One Entity (with 50 action and states and 4 rules) – 35 kB
The following table lists the capacity for a basic configuration: 250 RTUs with two I/O
Expansion units plus up to one MODBUS Master with seven slaves per a single RTU and up to
340 entities per single RTU.
Number of MODBUS Masters with

Number of Entities
Seven Slaves
X Y
109 0
108 5
106 10
104 15
103 20
101 25
100 30
98 35
96 40
95 45
F-5
93 50
92 55
90 60
88 65
87 70
85 75
84 80
82 85
80 90
79 95
77 100
76 105
74 110
73 115
71 120
69 125
68 130
66 135
65 140
63 145
61 150
60 155
58 160
57 165
55 170
53 175
52 180
50 185
49 190
47 195
45 200
44 205
42 210
41 215
39 220
38 225
36 230
34 235
33 240
31 245
30 250
28 255
26 260
F-6
25 265
23 270
22 275
20 280
18 285
17 290
15 295
14 300
12 305
10 310
9 315
7 320
6 325
4 330
3 335
1 340
The following table lists the capacity for a basic configuration: 250 RTUs with two I/O
Expansion units plus up to one MODBUS Master with one slave per a single RTU and up to
340 entities per single RTU.
Number of MODBUS Masters with One

Number of Entities
Slave
X Y
249 236
238 241
226 246
214 251
203 256
191 261
179 266
168 271
156 276
144 281
133 286
121 291
109 296
98 301
86 306
74 311
63 316
51 321
39 326
F-7
28 331
16 336
4 341
The following table lists the capacity for a basic configuration: 250 RTUs (main CPU only)
plus up to one MODBUS Master with one slave per a single RTU and up to 541 entities per
single RTU.
Number of MODBUS Masters with One

Number of Entities
Slave
X Y
249 436
238 441
226 446
214 451
203 456
191 461
179 466
168 471
156 476
144 481
133 486
121 491
109 496
98 501
86 506
74 511
63 516
51 521
39 526
28 531
16 536
4 541
F-8
Appendix G: ACE1000 Credentials
The following credentials are used to access the ACE1000 unit via Web browser using the
ACE1000 Easy Configurator.
Table G-1 ACE1000 Default User Credentials
Username Password
admin Batw1ngs-Adm1n1!
technician Batw1ngs-Adm1n1!
viewer Batw1ngs-User12!
The following credentials are used to access the ACE1000 unit via SSH/PuTTY.
Table G-2 ACE1000 Operating System User Credentials
Username Password Description

abuilder Batw1ngs-Adm1n1! non-root administrator user
acelogin Batw1ngs-User12! terminal login user
root Batw1ngs-Adm1n1! terminal login root user
Note: After the initial login, all default passwords must be changed to protect the system. It is
recommended to change passwords periodically to protect your system.
To change the password for root, log in as acelogin and execute the “su –” command.
G-1

ACE1000 Easy Configurator User Guide-D

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ACE1000 Easy Configurator User Guide-D

Uploaded by

Copyright:

Available Formats

User Guide

MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized

Copyright © 2015 All rights reserved

Motorola Solutions, Inc.

Motorola Solutions, Inc.

TABLE OF CONTENTS .......................................................................................................................................... I

Downgrading to a Lower ACE1000 version (System Downgrade) .......................................................... D-7

APPENDIX E: CODESYS IEC61131-3 PROGRAMMER APPLICATIONS ........................................................... E-1

Acronyms and Abbreviations

ACE Advanced Control Equipment

Terms and Conventions

• ACE1000 Easy Configurator User Guide,

• ACE3600 STS/ACE1000 Software Diagnostic Output and Error Messages Manual,

• ACE1000 C Toolkit User Guide,

• ACE1000 RTU Owner’s Manual,

The ACE1000 Easy Configurator is a Web-based interface to the ACE1000

ACE1000 System Overview

Figure 1-1 ACE1000 System Diagram

ACE1000 Easy Configurator Overview

ACE1000 Easy Configurator Functions

• Building an ACE1000 System

• Configuring the RTU/FEP ports and communication

• Configuring the RTU on-board I/Os and I/O modules

• Monitoring the System/RTU

• Managing users for the RTU

• Defining rule-based logic for RTU operation

• Uploading a site configuration to the FEP files

• Updating the date and time in RTU sites

• Synchronizing all RTUs to the FEP time

• Retrieving errors logged in the RTUs/FEP (hardware or software malfunctions)

• Retrieving I/O events logged in the RTUs

• Backing up the RTU configuration and data

• Generating SCADA tags (Wizcon, Intouch and general formats)

• Deploying configurations to the RTU/FEP

ACE1000 RTU Definition

ACE1000 Communication Interfaces

Up to two of the following ports can be defined in each unit.

• Through the Micro USB 2.0 On-the-Go port

ASTRO IV&D (ASTRO APX radio)

• Through the 10/100 Mb Ethernet port

• Through the RS232/RS485 port

Cellular modem: Siarra wireless (AirLINK FXT edge) or Maxon - intelimax

• Through the USB 2.0 Host port (MDLC)

ASTRO IV&D (ASTRO APX radio)

• Through the P1 Plug-in RS232 port

Cellular modem: Siarra wireless (AirLINK FXT edge) or Maxon - intelimax

• Through the P2 Plug-in RS232 port

External modem (Westremo)

Communication via the various ports may be simultaneous.

ACE1000 User Management

• Technician – Has full access to all non-administrative features within a system,

The following permission table describes the permissions of each role:

Functionality Sub- Admin Technician Viewer

Save/Discard Yes Yes No

Functionality Sub- Admin Technician Viewer

Poll Yes Yes No

Functionality Sub- Admin Technician Viewer

Set DO, AO Yes Yes No

ACE1000 Easy Configurator User Interface

• RTU View/Configuration mode – where the RTU of a specific site is displayed

• System View/Monitoring mode (FEP only) – where the current communication,

Figure 1-2 RTU View/Configuration Mode

Figure 1-3 System View/Configuration Mode

Figure 1-4 RTU View/Monitoring Mode