ACE3600 System Planner 2011

System Planner
??
ACE3600 RTU
ab
6802979C45-F
Draft 2
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 2011 Motorola Solutions, Inc. All Rights Reserved April 2011
DISCLAIMER NOTE The information within this document has been carefully checked and is believed to be entirely reliable. However, no responsibility is assumed for any inaccuracies. Furthermore Motorola reserves the right to make changes to any product herein to improve reliability, function, or design. Motorola does not assume any liability arising out of the application or use of any product, recommendation, or circuit described herein; neither does it convey any license under its patent or right of others. All information resident in this document is considered copyrighted. COMPUTER SOFTWARE COPYRIGHTS The Motorola products described in this Product Planner include copyrighted Motorola software stored in semiconductor memories and other media. Laws in the United States and foreign 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 Motorola products described in this Product Planner may not be copied or reproduced in any manner without written permission from Motorola Solutions, Inc. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyright, patents, or patent applications of Motorola, except for the normal nonexclusive, royalty free license to use that arises by operation in law of the sale of a product. TRADEMARKS MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license. All other product or service names are the property of their respective owners.
Table of Contents
TABLE OF CONTENTS ...............................................................................................................I ACE3600 SYSTEM OVERVIEW................................................................................................ 1 ACE3600 RTU CONSTRUCTION.............................................................................................. 3 19 METAL BACK INSTALLATION COMBINATIONS ..................................................................... 7 POWER SUPPLY MODULES .................................................................................................... 8 12V BACKUP BATTERY ............................................................................................................... 9 CPU MODULES.......................................................................................................................... 10 I/O MODULES ............................................................................................................................ 12 DIGITAL INPUT MODULES ................................................................................................... 15 DIGITAL OUTPUT RELAY MODULES ................................................................................ 24 ANALOG INPUT MODULES................................................................................................... 35 ANALOG OUTPUT MODULES............................................................................................... 43 DIGITAL OUTPUT AND DIGITAL INPUT FET MODULES............................................. 49 MIXED I/O MODULES ............................................................................................................. 56 MIXED ANALOG MODULES.................................................................................................. 58 I/O EXPANSION......................................................................................................................... 60 EXPANSION POWER SUPPLY MODULE ............................................................................ 64 EXPANSION MODULE............................................................................................................. 65 MODULE FIRMWARE AND OPERATION MODES......................................................................... 66 EXPANSION LAN SWITCH..................................................................................................... 69 RTU I/O EXPANSION - POWER CONSIDERATIONS........................................................ 71 CPU AND POWER SUPPLY REDUNDANCY ....................................................................... 74 GENERAL ................................................................................................................................... 74 REDUNDANT CPU AND POWER SUPPLY FRAME ....................................................................... 74 REDUNDANCY DEFINITIONS...................................................................................................... 74 REDUNDANT CPU ..................................................................................................................... 75 REDUNDANT POWER SUPPLY .................................................................................................... 75 REDUNDANT CPU AND POWER SUPPLY CONFIGURATIONS ..................................................... 76 CPU AND POWER SUPPLY REDUNDANCY WITH I/O EXPANSION .............................................. 77 REDUNDANT CPU ADDRESSING ............................................................................................... 78 CPU DATABASE SYNCHRONIZATION ........................................................................................ 79 ACE IP GATEWAY MODULE................................................................................................. 81 ORDERING INFORMATION .................................................................................................. 82 ACE3600 RTU ORDERING FLOW: ............................................................................................ 82 LIST OF ACE3600 MODELS ....................................................................................................... 92 LIST OF ACE3600 OPTIONS ...................................................................................................... 94
GENERAL ORDERING REQUIREMENTS ...................................................................................... 98 ACE3600 INSTALLATION GUIDELINES ........................................................................... 100 DIMENSIONS ............................................................................................................................ 100 GENERAL SAFETY INFORMATION: ................................................................................ 102 MOUNTING THE ACE3600 FRAME ON A WALL ...................................................................... 103 INSTALLING THE ACE3600 IN A 19" RACK ............................................................................. 106 HOUSING INSTALLATION......................................................................................................... 108 COMMUNICATIONS .............................................................................................................. 110 MDLC PROTOCOL................................................................................................................... 111 COMMUNICATION LINKS ......................................................................................................... 115 RS232 PORTS .......................................................................................................................... 115 RS485 PORTS .......................................................................................................................... 116 IP PORTS (MDLC OVER IP)..................................................................................................... 118 RADIO COMMUNICATIONS ...................................................................................................... 139 COMMUNICATION NETWORK .................................................................................................. 149 MDLC ENCRYPTION ............................................................................................................... 155 CLOCK FUNCTIONS AND SYNCHRONIZATION ........................................................... 159 RTU CLOCK ............................................................................................................................ 159 TIME ADJUSTMENT AND SYNCHRONIZATION ......................................................................... 159 NTP CLOCK SYNCHRONIZATION ............................................................................................ 161 GLOBAL POSITIONING SYSTEM (GPS) .................................................................................... 163 SCADA SYSTEM COMPONENTS ........................................................................................ 164 CONTROL CENTER SCADA MANAGER................................................................................ 164 M-OPC .................................................................................................................................... 164 ACE IP GATEWAY .................................................................................................................. 166 MOSCAD IP GATEWAY ......................................................................................................... 175 LEGACY MODBUS FEP ........................................................................................................... 175 APPENDIX A - ACE3600 SPECIFICATIONS...................................................................... 177 POWER SUPPLY MODULE SPECIFICATIONS ............................................................................. 181 CPU 3610*/CPU 3640 MODULE SPECIFICATIONS .................................................................. 184 CPU 3680 MODULE SPECIFICATIONS ..................................................................................... 185 DI MODULE SPECIFICATIONS .................................................................................................. 187 DO/DI FET MODULE SPECIFICATIONS ................................................................................... 191 DO RELAY MODULE SPECIFICATIONS .................................................................................... 192 AI MODULE SPECIFICATIONS .................................................................................................. 195 AO MODULE SPECIFICATIONS ................................................................................................ 196 MIXED I/O MODULE SPECIFICATIONS..................................................................................... 197 MIXED ANALOG MODULE SPECIFICATIONS............................................................................ 199 EXPANSION POWER SUPPLY MODULE SPECIFICATIONS ......................................................... 201 EXPANSION MODULE SPECIFICATIONS ................................................................................... 202 EXPANSION LAN SWITCH SPECIFICATIONS ............................................................................ 203 ACE IP GATEWAY MODULE (CPU 4600) SPECIFICATIONS .................................................... 204 APPENDIX B - FCC INFORMATION SPECTRUM AND REGULATORY UPDATE... 205 FCC RULES UPDATE ............................................................................................................... 205 LICENSING OF FIXED DATA SYSTEMS ..................................................................................... 208
SPECTRUM AVAILABLE FOR FIXED DATA SYSTEMS ............................................................... 208 APPENDIX C: ACE3600 MAXIMUM POWER RATINGS ................................................ 211
ACE3600 System Overview

The purpose of ACE3600 system is typically to provide some degree of automatic operation to a new or existing customer process. The process may be found in water pump stations, sewage lift stations, communication system monitoring, security, public notification control, electrical substation monitoring, distribution automation, demandside management, automated meter reading, or other applications. This automation is provided by a combination of hardware. Remote Terminal Unit (RTU):
RTU
OTPUTS Communication Communication System System INPUTS
The field sites are equipped with ACE3600 RTUs that collect data from on-site sensors, add data from off-site sources, and use this data aggregate to make decisions regarding how the process is operating. Changes to the local process may be made; messages may be initiated that send data elsewhere to influence the operation of off-site equipment or to advise the SCADA Manager of some important change. Communications:
The multiple sites in the system may communicate among themselves by utilizing FEP STS a variety of communication choices: IP networks, two-way conventional, trunked, or data radio or any other communication network. MDLC, the main communication SCADA protocol employed by ACE3600, is based Manager on the seven-layer OSI recommendation, and is designed to be totally functional on variety of communication media. MDLC includes a store-&-forward capability that permits different communication media links to be incorporated into the total system, i.e. conventional radio and trunked radio and microwave radio and LAN all interconnected by ACE3600 into a single communication system. Data may be passed from any site to any other site in the system (peer-to-peer) either directly or by multiple hops through intermediate ACE3600 sites. This peer-to-peer communication capability enables system designs that use a distributed-intelligence operating philosophy; central-intelligence-only systems may also be implemented if the load on the communication system permits it.
ACE3600 System Overview
The Front End Processor (FEP):
The Front End Processor is used at the central site(s) to provide a two-way path to the communication system and the distant RTUs from the SCADA Manager hardware and software. The FEP converts MDLC protocol data from the RTUs to a protocol used by the SCADA Manager vendor: when the OPC or ModBus protocol is used, the FEP will maintain a local database of all the data from the multiple in-field sites; when TCP/IP gateway is used, the FEP is simply a gateway between the two different protocols. The FEP always acknowledges all RTU-initiated messages. The FEP can also provide a twoway path between the ACE3600 STS and the field RTUs for those functions unique to ACE3600 that are not provided by the SCADA Manager software (over-the-air programming download, diagnostics upload, and more.) SCADA Manager:
The SCADA Manager provides the operator with the display and report tools necessary to view and manage the associated process(es). The SCADA Manager obtains data from the FEP according to its needs and typically presents that data on custom-created display formats; control messages may also be initiated from these custom screens. Security is typically implemented via permission levels activated by the operators sign-on password. Microsoft Windows is becoming the operating system of choice because it easily supports the desired graphic symbols used on the custom screens. The report capability may be provided by the SCADA software or a data export to Microsoft Excel or equivalent may be utilized. The end result is an easy to use pictorially-described representation of the field status of key equipment items plus the means to make changes in how those pieces of equipment operate. System Tools Suite (STS):
The ACE3600 STS is a software program that allows the system engineer to set up and maintain the ACE3600 system in accordance with system-specific requirements. The STS computer (PC) may be connected to any RTU/FEP or to the other network points in the system and have connectivity established with any other site through the store-&forward capability of the MDLC protocol; all the capabilities available during a local connection may then be enjoyed by the remotely-connected system engineer: the communication network topography may be defined; the application(s) for each site may be created and downloaded into the RTUs; run-time and diagnostic data may be uploaded.
ACE3600 RTU Construction

The ACE3600 RTU is a universal device that may serve as an RTU, a Programmable Logic Controller (PLC), or as the system FEP. It is placed at the systems field sites to collect data from on-site sensors, add data from off-site sources, and use this data aggregate to make decisions regarding how some process is operating. The RTU may make changes to the local process; messages may be initiated that send data elsewhere to influence the operation of off-site equipment or to advise the SCADA Manager of some important change. The ACE3600 is available in various structures: Frame which can accommodate a varied number and type of modules Metal chassis which accommodates the frame, and optional radios, backup battery and communication interfaces Protective housing which accommodates the frame, and optional radios, backup battery and communication interfaces (suitable for outdoor installation)
The ACE3600 frame consists of the following elements: Plastic slots which accommodate the power supply, CPU and I/O modules, and backplane bus motherboard Mounting plate for attaching the plastic slots together and mounting the frame on a wall Backplane bus motherboard which connects the modules to each other via the signal buses and connects the modules with operating voltages Power junction box for AC or DC power source and ground connections
A frame can be mounted on the wall or installed in a 19" rack or customer enclosure.
Each RTU can include a number of options, including portable and mobile radios, and plastic accessory boxes with interface card for communication, etc.
Housing/Mounting Type Capacity/Options Illustration
No I/O slot frame Basic (default) model. Can be installed on a wall.
Power supply and CPU Can be ordered with metal chassis or housing options. Can be ordered with 19" frame metal back. Power supply and CPU, up to 2 I/Os Can be ordered with small metal chassis.
2 I/O slot frame Can be installed on a wall.
Power supply and CPU, up to 3 I/Os Can be ordered with metal chassis or housing. Can be ordered with 19" frame metal back. Power supply and CPU, up to 5 I/Os Can be ordered with large metal chassis or housing. Can be ordered with 19" frame metal back. Power supply and CPU, up to 7 I/Os Can be ordered with large metal chassis or housing.
8 I/O slot frame Can be installed on a wall or in 19" rack/enclosure.
Power supply and CPU, up to 8 I/Os Can be ordered with metal chassis option for accessories: 6.5 or 10 Ah Lead-Acid backup battery 1 radio; up to four accessory boxes.
Housing/Mounting Type
Capacity/Options
Illustration
I/O expansion frame 2 I/O slot, 3 I/O slot, 5 I/O slot, 7 I/O slot, or 8 I/O slot
I/O expansion power supply, I/O expansion module, up to 8 I/Os. Can be connected to the main RTU frame. Can be ordered with large metal chassis or housing. 2 power supplies and 2 CPUs, 4 I/Os.
Redundant CPU and power supply frame Can be installed on a wall, in housing, or in 19 rack/enclosure. Small metal chassis Enables installation of radio, backup battery and other accessories. Can be installed on a wall or in housing. Medium metal chassis Enables installation of radio, backup battery and other accessories. Can be installed on a wall or in housing. Large painted metal chassis Enables installation of radio, backup battery and other accessories. Can be installed on a wall or in housing.
Power supply and CPU, up to 2 I/Os, 1 mobile/portable radio, 6.5Ah Lead-Acid backup battery; 1 accessory box can be installed in place of the radio. Power supply and CPU, up to 3 I/Os, 1 mobile/portable radio, 1 accessory box, 6.5 Ah Lead-Acid backup battery Power supply and CPU, up to 7 I/Os, 1 accessory box, up to 2 mobile/portable radios, 6.5 or 10 Ah Lead-Acid backup battery
Housing/Mounting Type
Capacity/Options
Illustration
19" frame metal back Enables installation of radio, backup battery and other accessories. Can be installed in 19 rack or on a wall.
Power supply and CPU, 0, 3, 5 or 8 I/Os, 1 radio, 6.5 or 10 Ah Lead-Acid backup battery, and up to 4 accessory boxes. (Not all combinations are valid together.) Can be ordered with ACE IP Gateway, power supply, radio, 6.5 or 10 Ah Lead-Acid backup battery and up to 2 accessory boxes. Power supply and CPU, up to 3 I/Os, 1 mobile/portable radio, 1 accessory box, 6.5 Ah Lead-Acid backup battery Power supply and CPU, up to 7 I/Os, 1 accessory box, up to 2 mobile/portable radios, 6.5 or 10 Ah Lead-Acid backup battery
Small NEMA 4/IP66 housing Enables installation of radio, backup battery and other accessories. Can be installed on a wall. Large metal NEMA 4/IP66 housing Enables installation of radio, backup battery and other accessories. Can be installed on a wall.
19 Metal Back Installation Combinations

The 19 metal back can be ordered with a variety of frames, modules, and accessories (e.g. battery, radio, plastic accessory box.) In certain cases, choosing a certain accessory reduces the other options. For example, the portable radio is installed on the 19 metal back with the No I/O Frame in place of one accessory box. Likewise a battery is installed on the 19 metal back with the No I/O Frame in place of one accessory box. Note: By default the 8 I/O frame comes with the 19" metal back. For diagrams of the various combinations, see the figures below.
Power Supply Modules

The ACE3600 power supply module provides the other modules in the RTU with their operating voltages via the motherboard bus. The following power supply options are available: DC power supply low-tier (10.8-16V) DC power supply (10.8-16V) provided as default DC power supply (18-72V) DC power supply (18-72V) with battery charger AC power supply- 100-240V AC power supply- 100-240V with battery charger
Common characteristics of all power supply modules: (except the DC power supply low-tier) On/Off switch on the front panel Controlled auxiliary voltage outputs Heat convection cooling (no need for fans) Short protection outputs Over heating protection The module operation is monitored by the CPU module. Status LEDs on the front panel The PS module is always located in the leftmost slot of the frame. In a frame with both redundant CPUs and redundant power supplies, the third slot from the left (between the primary CPU and the secondary CPU) is used by the redundant power supply. Input current protection fuse Controlled power line enables centralized disabling of Electrically Energized and Magnetically Latched relay outputs in selectable DO modules.
Note: The DC power supply low-tier does not support radios that require input power other than 10.8-16V. Do not use portable radios which require 7.5V input with this option. Note: The low limit of the DC power supply (10.8-16V) can be configured to 10.5V. The default is 10.8. Common characteristics of power supply modules with battery charger: Automatic switchover to battery on power fail Automatic switchover to main power on power return Temperature compensated charging Over-charging protection
Characteristics of the DC power supply low-tier: Two auxiliary voltage outputs Short circuit protection outputs PS located on the leftmost slot of the frame Overvoltage protection for CPU and I/Os Reverse voltage protection
Power supply modules with a battery option support a 6.5 or 10 Ah Lead-Acid battery. The power supply automatically switches to the backup battery as a 12V DC power source for the RTU and communications when the main AC or DC power source fails. Power supply modules with battery charger option charge the backup battery when not in use, and protect the battery from over-discharge. The charger performs battery tests/diagnostics, including controlled battery discharge, when requested by the user. If the battery is failed, the charger will not charge it and will send a failed status signal to the CPU. If the battery is remotely located, long battery cables can be used. The charging voltage of the Lead-Acid battery is controlled by the charger as a function of the battery temperature. The charging profile is set to comply with the temperaturecompensated float-voltage of the ACE3600 battery. A battery test can be performed on the Lead-Acid battery, either from the ACE3600 STS Hardware Test utility or from the user application program. The battery test includes disabling the battery charger, discharging the battery and measuring the capacitance. Note: An additional power supply module for use with I/O expansion frames is described in the Expansion Power Supply Module section below. Redundant power supplies are used to ensure a continuous supply of the required RTU voltages, in the event that one power supply fails. For details on the redundant power supply, see CPU and Power Supply Redundancy below.
12V Backup Battery

The ACE3600 backup 12V Lead-Acid battery provides backup for the main input power. The battery is available in two capacities: 6.5 Ah and 10 Ah. Switching from main input power to the battery and charging of the battery is performed by the ACE3600 power supply module. Sealed Lead-Acid technology batteries can be recharged and discharged at a temperature range of -30 to +60C. Storage and operating temperatures affect the battery capacity and lifespan. ACE3600 power supply modules include a special charging power supply designed to fit the specific temperature-compensated float-voltage-charging curve of the battery.
CPU Modules
The main element of the ACE3600 is the CPU module. It controls the I/O modules, processes the gathered data and communicates with the outside world. The core of the module is Freescales MPC8270 32-bit microprocessor which has extended communication capabilities, high speed core, DMA and floating point calculation support. The module includes on-board memory, communication ports, I/O bus interface and other circuits. The firmware is based on Wind Rivers VxWorks operating system. Module Location: The CPU is a removable module located in a dedicated slot in the RTU rack. The CPU module must be plugged into the wide slot to the right of the Power Supply module. The CPU module includes several communication ports: On Board ports: USB HOST 1 ( HU1) - USB Type A host full speed port (CPU 3680 only) for MotoTrbo radio interface USB HOST 2 ( HU2) USB Type A host full speed port (CPU 3680 only) for MotoTrbo radio interface Serial 1 (SI1) RS232/RS485 serial port (configurable) Serial 2 (SI2) RS232 serial port Ethernet (Eth1) 10/100BaseT Ethernet port (CPU 3640 and CPU 3680 only) USB Device (DU1) USB Type B device full speed port (CPU 3680 only - future option) Internal Ethernet port (Int 1) Internal 100 Mb Ethernet port, located on the rear MB connector (comm. between dual redundant CPUs) (CPU 3680 only) Plug-in ports bays, where different types of ports can be installed: Plug-in 1 (PI1) fits RS232, RS485, 10 MB Ethernet, 10/100 MB Ethernet, or Radio Modem Plug-in option Plug-in 2 (PI2) fits RS232, RS485, 10 MB Ethernet, or Radio Modem Plug-in port option. Note: For information on the ACE3600 Ethernet port and Auto-Negotiation, see the Auto-Negotiation Note at the end of the IP Ports (MDLC over IP) section below. The ACE3600 CPU memory includes FLASH, SDRAM, and optional SRAM Plug-in memory. The FLASH stores the firmware, the user application program, and the user data. The SDRAM memory stores the temporary data. The optional SRAM memory expansion is used for logging user data. The SRAM data is retained using an on-board rechargeable lithium battery.
10
CPU Modules
Model 3640 Flash memory SDRAM memory: User FLASH: User SDRAM: SRAM Plug-In
Model 3680
Model 3610*(discontinued)
16 Mb 32 Mb 3 Mb 10 Mb 4 Mb
32 Mb 128 Mb 19 Mb 100 Mb 4 Mb
16 Mb 32 Mb 3 Mb 10 Mb 4 Mb
The CPU has a low drift RTC. The date and time are retained using an on-board rechargeable lithium battery. The CPU date and time can be set using the ACE3600 STS. The CPU can also be synchronized with other RTUs in the system, using the system clock. The CPUs rechargeable lithium battery provides backup power and data retention for the SRAM and RTC. Typically, the battery will preserve the data stored in the SRAM and RTC for 60 continuous days without power. When the SRAM option is not used, the Lithium battery will keep the Real Time Clock (RTC) running for a longer period of time. The CPU module also includes: Buzzer (audio indication), which is used to indicate task completion (such as end of download/upload, restart etc.) and can also be controlled from the user application program. Pushbuttons on the front panel, PB1 and PB2. These pushbuttons are used for activating and testing the module LEDs, restarting the unit, erasing the user Flash memory and activating memory test. The pushbuttons can also be monitored by the user application program (when it is running) for the application purposes. Status LEDS which indicate the CPU status during startup (boot), run-time or when there is a failure. Communication LEDs are used to indicate the communication port status. User LEDs can be used by the user application program.
The CPUs firmware is a real-time multitasking operating system, based on the Wind River VxWorks OS. The CPU is shipped from the factory with the most recent firmware version, and it can be updated/replaced using a remote or local connection. Downloading firmware updates is performed using the STS. (See Downloading to a Site in the ACE3600 STS User Guide.) If the new firmware download stops or fails, the CPU will restart with the existing firmware. CPU redundancy (ACE3680 only) ensures continuous RTU operation if one CPU fails. For details on the redundant CPU, see CPU and Power Supply Redundancy below.
11
I/O Modules
The ACE3600 RTU can include up to eight I/O modules, depending on the frame size. A variety of I/O modules is available. The I/O modules can be positioned in the slots to the right of the CPU. As with all ACE3600 modules, the I/O modules can be replaced while the power is on (hot swap.) Each I/O module includes an ERR status LED, individual I/O status LEDs, an array of I/O connectors, and a coding mechanism for the terminal cable connector or TB holder option. The ERR LED indicates an I/O module fault and errors. It will remain lit until all the errors have been eliminated. Diagnostic and error messages can be retrieved from the module using the ACE3600 STS Error Logger or SW Diagnostics. The I/O status LEDs in Digital Input (DI) and Digital Output (DO) modules indicate ON and OFF (LED lit when the I/O is ON.) In Analog Input (AI) modules, each input has two LEDs, indicating Overflow (OF) and Underflow (UF). In Analog Output (AO) modules, each output has three LEDs, indicating voltage output (Vout), current output (Iout), and calibration (Cal). Each I/O module can be ordered either with a set of two, three or four TB connectors or with a TB holder. TB connectors have a fixed female side on the module and a male plug for the sensor/device wire connection. The TB male side in all modules is screw type for up to 1mm (18 AWG) wire in modules with two/four TBs (3.5 mm pitch) or 1.6 mm (14 AWG) wire in modules with three TBs (5 mm pitch). Two TB extractor tools (FHN7063A) are provided for easy removal of TBs, one for modules with two/four TBs and one for modules with three TBs. The TB holder secures the male TBs neatly in place and forms a single connector plug per module. The wires connected to the TBs are concealed in the holder. The module and the TB holder provide a coding mechanism to prevent cabling errors. Ejector handles enable easy release of the TB holder connector from the module. An optional three-meter cable braid, completely wired with holder and cable, is available. A TB holder kit is available to enable self-assembly of cables. User assembled cables should use wires of up to 0.4mm (26 AWG) in modules with two/four TBs (3.5 mm pitch) or wires of up to 0.8 mm (20 AWG) in modules with three TBs (5 mm pitch). The TB holder kit does not include a cable.
12
I/O Modules
TB Holder
I/O Module
Ejector Handles
Terminal Blocks (TB)
Terminal Block (TB) Positioner Screw

OF 16 UF
Terminal Block (TB) Positioner
OF
24V
Code Key TB Holder I/O Module
Code Key
Up to two 24V DC floating plug-in power supplies can be added to certain I/O modules, as detailed in the table below. Up to four 24V DC floating plug-in power supplies can be added per rack.
Module Type Number of Power Supplies
32 DI Fast 24V/IEC TYPE 2 16 DI Fast 24V/IEC TYPE 2 16 AI 8 AI Mixed I/O Mixed Analog
2 1 1 1 1 1
13
I/O Modules
Spacers Optional 24V Floating Power Supply Plug-In Motherboard Location PIN Motherboard Connector
ERR
1 UF OF 2 UF OF 3 UF OF 4 UF OF 5 UF OF 6 UF OF 7 UF OF 8 UF OF
24V
9 UF OF 10 UF OF 11 UF OF 12 UF OF 13 UF OF 14 UF OF 15 UF OF 16 UF OF
24V
14
Digital Input Modules

Low Voltage DI Modules: The ACE3600 low voltage Digital Input (DI) module can have 16 or 32 inputs. The following DI modules are available: 16 DI Fast 24V 32 DI Fast 24V 16 DI Fast 24V IEC TYPE 2 32 DI Fast 24V IEC TYPE 2 32 DI Fast 48V
Two types of low voltage (wet) inputs are supported, IEC 61131-2 Type II compliant inputs and 24V MOSCAD compatible inputs. In the 32 DI modules, the first 20 inputs can function as fast counters. In the 16 DI modules, all inputs can function as fast counters. A counters maximum rate is dependent on the module type (see the specifications below.) All the inputs are optically isolated. The DI modules support optional 24V DC floating plug-in power supplies (for contact wetting or other purposes). The 16 DI Fast 24V and 32 DI Fast 24V modules can handle AC and DC input signals. The user can select DC or AC operation per module. When AC configuration is selected, the Fast Capture, Counter Function and Input Filters (see below) are disabled. The 32 DI 48V modules can handle DC input signals only. 120/230V (HV) DI module: The ACE3600 high voltage Digital Input (DI) module has 16 inputs. All the inputs are IEC 61131-2 Type 1 compliant and all are optically isolated. This module supports high voltage AC or DC signals in the inputs. The Counter function is not supported in this module. Common Characteristics to all DI modules: Each DI can be an event trigger (interrupt-driven) to a high priority fast process. The high priority fast process enables very fast activation of an output in response to an input trigger and logical conditions. This high priority fast process is not dependent on the I/O scan. When the DI module is in DC mode, each DI can be configured as a Fast Capture DI. Fast capture causes the SCAN ladder output operation to get the first change that
15
occurred since the previous scan. When fast capture is disabled, the scan gets the current value of the DI (in this case, any DI changes between scans are missed.) When the DI module is in DC mode, each input has a HW input filter to make sure that the input reading is stable. The range of the HW DI filter is 0 to 50.8 millisecond (in 0.2 mS steps). The Fast Counter DI filter range is 0 to 12.75 millisecond (in 0.05 mS steps). The DI module features which can be configured are listed in the table below. Some parameters are per module and some are per input.
Feature Parameter Settings Default Setting Per Module/ Input Parameter Setup Location
DC or AC operation Fast Capture DI Filter (DC)
AC/DC Disabled /Enabled 0-254 (x 0.2 mS) 0-255 (x 0.05 mS) Disabled/ Enabled KLV/PDV PDV=0/1 No /Yes
DC Disabled 50 (10 mS)
Module Input Module
STS site configuration STS site configuration STS site configuration; C User Program STS site configuration C User Program User Program I/O link table User Program I/O link table User Program I/O link table
Counter Filter (DC) Event Time Tagging Keep Last Value and Predefined Value Mask
20 (1 ms)
Module
Disabled KLV
Input Input
No
Input
Note: In the 120/230V DI module, the minimum effective DI Filter parameter value is 7.0 mSec. Each DI can be set in the user application programs I/O link table to trigger recording of time tagged events upon any input change of state. The time tagged events are recorded in the CPU memory and can be retrieved for various purposes. Each input can be configured to Keep Last Value (KLV) or to Predefined Value (PDV 0 or 1). This value is shown to the user application program in the event of DI module failure. The PDV can also be used during normal operation to force a value that
in Fast 24V IEC TYPE II modules only DC
16
masks the actual input value. In this case the user program will get the PDV instead of the actual input value. Each DI module can be switched by the user application program to Sleep Mode. In Sleep Mode, the module does not function and the power consumption is minimized. During Sleep mode, the user application program will get the predefined values (PDV) for each I/O. The DI module can be diagnosed and monitored using the STS Hardware Test utility. This test verifies that the module is operational, presents the module configuration and shows the actual value of each input. It is also possible to change the input filter setup temporarily for the duration of the Hardware Test. In the STS Hardware Test utility, it is possible to set the DI module to Freeze Mode. In this mode the user application program will get the predefined value of each input in the module, instead of the actual input value. Freeze mode enables testing the inputs while the user application program is running. Connection of a dry contact sensor to the low voltage DI module requires wetting the contact with a voltage. This can be done using the 24V DC floating plug-in power supplies that can be added to the module. The 24V can be also used to power wet sensors. The 24V can be also used to power wet sensors. (Low voltage only)
Low Voltage DI I/O Circuit Diagram:
DI - Typical Input Circuit
DI Status
DI Full Diode
Vz
Bridge Rectifier
Current Limiter Fast 24V Fast 24V IEC Fast 48V R Vz 255 33V 255 33V 10mA 3.32K 68V 3mA
COM
Current 3.5mA Limiter
17
16 DI Module Block Diagram:

16 DI
18
32 DI Module Block Diagram:
19
Low Voltage DI I/O Connection Diagram:
DI Module
DIx (input x) Dry Contact Sensor COM (common)
External Wetting Source
+ DI Module
+ External Wetting Source + Wet Sensor DIx (input x) COM (common)
DI Module
DIx (input x) Dry Contact Sensor +24V (Plug-in PS)
DI Module +24V (Plug-in PS) + Wet Sensor DIx (input x) COM (common)
Note: The 24V DC floating plug-in power supplies can be added to the 16/32 DI Fast 24V/ Fast 24V IEC TYPE 2 modules only.
20
High Voltage DI I/O Circuit Diagram:
High Voltage DI - Typical Input Circuit

DI Status 1238 10K 47nF
DI
62V
COM
Current Circuit
21
16 DI 120/230V Module Block Diagram:

16 DI High Voltage
1 2 3 4 5 6 7 8 9 10 DI5 DI6 COM 1-6 DI1 DI2 DI3 DI4
Input Circuit
11 12 13 14 15 16 17 18 19 20
DI7 DI8 DI9 DI10
Control
Bus Interface
DI11 DI12 COM 7-12
21 22 23 24 25 26 27 28 29 30
DI13 DI14 DI15 DI16
22
16 DI 120/230V I/O Connection Diagram:
DI 120/230V Module
DIx (input x) AC / DC Signal Source COM (Common)
DI 120/230V Module Ext. Relay / Switch DIx (input x) AC / DC Signal Source COM (Common)
23
Digital Output Relay Modules

Low Voltage DO Relay Modules: The DO Relay modules have 8 or 16 outputs. There are two types of DO relays: Electrically Energized (EE) - the outputs return to the non-energized state in case of power off or module failure. Magnetic Latch (ML) - Relay outputs are magnetically latched, the outputs maintain their state in case of power off or module failure.
The following DO relays modules are available: 8 DO EE Relay 2A 16 DO EE Relay 2A 8 DO ML Relay 2A 16 DO ML Relay 2A SBO 8 DO 2 FormA EE Relay 2A
In the 8 DO modules except for the SBO 8 DO 2 FormA EE Relay 2A, the relays of outputs 1 through 5 are Single Pole Single Throw (SPST) normally open (NO) and are referred to as the Form A relays. The relays of outputs 6 through 8 are Single Pole Double Throw (SPDT) and are referred to as the Form C relays. In the 16 DO modules, the relays of outputs 1 through 5 and 9 through 13 are Single Pole Single Throw (SPST) normally open (NO) Form A relays. The relays of outputs 6 through 8 and 14 through 16 are Single Pole Double Throw (SPDT) Form C relays. The 8 DO Select Before Operate (SBO) Relay modules have Electrically Energized (EE) 2 Form A relay outputs. The modules are supported by ACE3600 firmware v14.00 and above. The 8 DO SBO module is used to ensure that the correct DO has been selected before actually activating the relay. Each DO in the module has two relays. When the module is in Idle state, the operate signal is disabled and no relay is activated. On DO Select command, both DO relays are selected. The select command is physically monitored by a back indication signal (Check Select.) After validation that only the requested relays were selected, the Operate command is set and enables the relay activation. The physical back indications from both relay contacts can be monitored by the application program to verify successful operation. Note that only a single SBO DO can be selected at a time. Each output has two types of back indications: a. Back indication of the relay select command. b. Back indication from the relay auxiliary contact (each relay has 2 contacts- one connected to user and the other as back indication.)
24
In the 8 DO SBO modules, the relays of the 8 outputs are Single Pole Single Throw (SPST) normally open (NO) and are referred to as the Form A relays. 120/230V DO Relay Modules: The ACE3600 DO Relay 120/230V (High Voltage DO) modules have 12 outputs. Each output is switched by a relay. There are two types of DO relays: Electrically Energized (EE) - the outputs return to the non-energized state in case of power off or module failure. Magnetically Latched (ML) - Relay outputs are magnetically latched, the outputs maintain their state in case of power off or module failure. The following DO relays modules are available: 12 DO EE Relay 120/230V 3A 12 DO ML Relay 120/230V 3A
DO Modules Common Characteristics: The physical position of each relay is monitored by the module logic, using a back indication signal which is connected to the relays second contact set. Any contradiction between the required position and the back indication signal is reported to the CPU and is available to the user program. In some applications it is necessary to inhibit relay output operation when attending the site for safety reasons. In all DO relay modules, it is possible to inhibit all relays per DO module. When a module is configured to enable relay inhibiting, the power to the relays is provided from the power supply via a dedicated power line (12V DO), controlled from the 12V DO input (TB located on the power supply module front panel). When the inputs terminals are shorted, the relays are operational. When the inputs terminals are open, the relays are inhibited (EE relays in 0 position and ML relays do not change state.) The user program can monitor the relay inhibiting status and act accordingly. Also, when the modules relays are inhibited, any mismatch between the relay position and the output logical state is ignored. Each output can be configured to Keep Last Value (KLV) or to a Predefined Value (PDV 0 or 1). This value is executed when the user program stops or when the module has no communication with the CPU module. Also, the PDV can be used during normal operation to force a value on the output by ignoring the user program value (mask).
25
In the ML relay modules, it is possible to configure the module to reset all the ML relays positions on startup. This is set in the STS site configuration.
Parameter Selection Default Setup Per Module/ Input Parameter Setup Location
DO Keep Last Value & PreDefined Value DO Mask
KLV/PDV PDV = 0/1 No /Yes
KLV
Output
Application Programmer I/O link table Application Programmer I/O link table Site configuration Site configuration
No
Output
Reset DO at Startup Relay Inhibiting (SW selectable)
Disable/Enable Disable/Enable
Disable Disable
Module Module
Each DO module can be switched by the user program to Sleep Mode. In Sleep Mode, the module does not function and the power consumption is minimized. The DO module can be diagnosed and monitored using the STS Hardware Test utility. This test verifies that the module is operational, presents the module configuration and shows the actual value of each output. It is also possible to change the DOs value. In the Hardware Test utility, it is possible to set the module to Freeze Mode. In this mode, the DOs will keep the last value they had at the time they were frozen. Freeze mode enables testing the inputs and outputs while the user program is running. Note: In systems with I/O expansion, the power supplies on I/O expansion frames can be attached via DC cable to the power supply on the previous I/O expansion frame in a daisy-chain manner, or directly to the main power supply. In this case, the 12V DO control on the main power supply can control all DO EE relays in the entire RTU that were configured by dip switch for 12V DO. This enables the user to inhibit all DO EE relays in the entire RTU simply by removing the plug from the 12V DO control in the main power supply.
26
Low Voltage DO I/O Circuit Diagrams:
DO EE Relay (SPST) - Typical Output Circuit

12V
Back Indication
COM NO
DO Control
DO ML Relay (SPST) - Typical Output Circuit

12V
Back Indication
COM NO
DO Set Control
DO Reset Control
27
DO EE Relay (SPDT) - Typical Output Circuit

12V
NC
Back Indication
COM NO
DO Control
DO ML Relay (SPDT) - Typical Output Circuit

12V
NC
Back Indication
COM NO
DO Set Control
DO Reset Control
28
DO SBO EE Relay (SPST) -Typical Output Circuit

12V Control*
Back Indication A
COMA NOA
Back Indication Logical AND in FGPA 12V Control
Back Indication B
COMB NOB
Check Select
DO Select
*Both the 12V and the Operate must be ON in order to power the circuit.
29
8 DO Module Block Diagram:
30
16 DO Module Block Diagram:
31
8 DO SBO I/O Circuit Diagram:
32
120/230V DO I/O Circuit Diagram:
HV DO EE Relay (SPST) - Typical Output Circuit

12V
Back Indication
NO
DO Control
HV DO ML Relay (SPST) - Typical Output Circuit

12V
Back Indication
NO
DO Set Control
DO Reset Control
33
120/230V DO Module Block Diagram:

12 V Vr 12 V DO (User Controlled)
1 2 3 4 5 6 7 8 9 10 NO3 NO4 NO1
Back Indication Vr V NO2
11 12 13 14 15 16 17 18 19 20
NO5
NO6
Module Control
NO7 NO8
Bus Interface
21 22 23 24 25 26 27 28 29 30
NO9
NO10
NO11 NO12
34
Analog Input Modules

The Analog Input (AI) modules have 8 or 16 inputs. The modules sample and convert analog data into digital format and transfer the digital data to the CPU module. The following modules are available: 8 AI, 20 mA (supports 4-20 mA) 16 AI, 20 mA (supports 4-20 mA) 8 AI, 5 V (supports 0-5 V and 1-5 V) 16 AI, 5 V (supports 0-5 V and 1-5 V)
The modules analog-to-digital conversion resolution is 16 bit (including sign). Each input is fully isolated from the other inputs on the module and also optically isolated from the module internal circuits. The modules are fully calibrated and can be tested and recalibrated in the field. The measured values are digitally filtered to reduce 50 or 60 Hz noise. The user can select the filtering frequency per module. The measured values can be smoothed by digital filtering. Smoothing is accomplished by calculating the running average values of a defined number of converted analog values (samples). The user can select the level of smoothing per module. The higher the smoothing level chosen, the more stable the smoothed analog value and the longer it takes until the smoothed analog signal is applied after a step response. The user can select how the analog values are represented to the user application program, as unit-less numeric values or as scaled values that represent certain Engineering Units (EGU). Each AI module can include an optional plug-in floating 24V DC power supply to power external devices. Each analog input has two status LEDs: UF - indicates Underflow when lit OF - indicates Overflow when lit
35
The AI Module Configuration includes: 50/60 Hz Filtering - This parameter enables the user to configure the module to use 50 or 60 Hz filter on all inputs. AI Filter (Smoothing) - This parameter enables the user to configure the level smoothing (averaging) on all inputs. It can be set to 1, 2, 4, 8, 16, 32, 64,128 samples. Change Of State (COS) Delta - This parameter sets a delta value for each input. This enables the user application program to get an indication when the input value change is more than delta value. Input Range - This parameter sets the input overflow and underflow LEDs limits (refer to AI Module value representation below). In the current input modules, the ranges that can be selected are: 20 mA (default) and 4-20 mA. In voltage input modules, the ranges that can be selected are 5V (default), 0-5 V and 1-5 V. Keep Last Value (KLV) and Predefined Value (PDV) - Each input can be configured to KLV or to a PDV. This value is shown to the user application program in the event of AI module failure. The predefined value can also be used during normal operation to force a value that masks the actual input value. In this case the user program will get the PDV instead of the actual input value. I/O Legacy Resolution Parameter - In systems with both ACE3600 RTUs and legacy (MOSCAD/MOSCAD-L) RTUs, some MOSCAD/MOSCAD-L applications can be upgraded to ACE3600 without modifying the references to analog values in the applications (C or ladder). The I/O Legacy Resolution STS advanced parameter sets the Analog I/O bit resolution to either Actual (ACE3600) or Legacy (MOSCAD/MOSCAD-L).
Selection Default setup Per Module/ Input Parameter Setup location
Parameter
50/60 Hz Filtering AI Filter (Smoothing) Input Range
50/60 1/2/4/8/16/32/64/128 (x10 mS) Current: 20 mA/ 4-20 mA Voltage: 5 V/0-5V/ 1-5V value
50 Hz 32 Current: 20 mA Voltage: 5 V
Module Module Module
STS Site configuration STS Site configuration STS Site configuration
COS Delta
0 (disabled)
Input
Application Programmer I/O link table Application Programmer I/O link table Application Programmer I/O link table
KLV & PDV
KLV/PDV PDV=value No /Yes
KLV
Input
Mask
No
Input
36
In the event of AI Module failure, the I/O module ERR LED will be lit. The event is registered by the CPU in the Error Logger. AI Module failure status is also visible to the user application program. In addition to the ERR LED, the module includes an Underflow (UDF) and Overflow (OVF) LED for each input. When the UDF LED is lit, it indicates that the signal level in the corresponding input is below the nominal range. When the OVF LED is lit, this indicates that the signal level in the corresponding input is above the nominal range. If both the UDF and OVF LEDs of the same channel are lit, the channel is uncalibrated.
The AI module can be diagnosed and monitored using the STS Hardware Test utility. The Hardware Test verifies that the module is operational, presents the module configuration and shows the actual value of each input, including overflow and underflow. It is also possible to change the input filter setup for the duration of the Hardware Test. In the Hardware Test utility, it is possible to set the AI module to Freeze Mode. In this mode, the program user will get the KLV or PDV of each input in the module instead of the actual input value. Freeze mode enables testing the inputs while the user application program is running.
37
AI Module Value Representation:

In 20 mA current inputs Decimal Value Input Current Indication
< -32256 -32000 0 32000 > 32256

In 4 - 20 mA current inputs Decimal Value
< -20.16 mA -20 mA 0 mA +20 mA > +20.16 mA

Input Current
Underflow LED ON Rated range (no LED active) Overflow LED ON

Indication
< 6144 6400 0 32000 > 32256

In 5 V current inputs Decimal Value
< 3.84 mA +4 mA 0 mA +20 mA > +20.16 mA

Input Voltage

Indication
< -32256 -32000 0 32000 > 32256

In 0 - 5 V current inputs Decimal Value
<-5.04V -5 V 0V +5 V > +5.04 V

Input Voltage

Indication
< -256 0 32000 > 32256

In 1 - 5 V current inputs Decimal Value
< -0.04 V 0V +5 V > +5.04 V

Input Voltage

Indication
< 6144 6400 32000 > 32256
< 0.96 V 1V +5 V > 5.04 V
38
I/O Circuit Diagram:
AI 20 mA - Typical Input Circuit

AN+
A/D
124
15V
PGND
51
AN -
Channel Select
AI 10 V - Typical Input Circuit

51
AN+
A/D
15V
PGND
51
AN -
Channel Select
39
8 AI Module Block Diagram:
40
16 AI Module Block Diagram:
41
I/O Connection Diagrams: There are two types of current sensors/transmitters, namely 2-wire and 4-wire. The 2wire transmitters require a serial power feed for the current loop, whereas 4-wire transmitters have a separate power supply connection. As a result, with 4-wire transmitters a single power supply may be used to provide power to several sensors; the diagram below describes the connection of the two types of current sensors to the analog input module.
AI Module
+ -
+ 4 Wire + Current Sensor -
Shield
AI+ (input x) AI - (input x)
AI Module
2 Wire + Current Sensor -
Shield
The diagram below describes the connection of 2-wire and 4-wire current sensors using the 24V PS plug-in on the Analog Input module. Note: 24V Plug-in is a future option.
AI Module +24V (Plug-in PS) + + 4 Wire Current Sensor Shielded Wire
+ -
COM (common)
AI Module
Shielded Wire
2 Wire + Current Sensor -
AI+ (input x) +24V (Plug-in PS) AI- (input x) COM (common)
42
Analog Output Modules

The Analog Output (AO) modules have four optically-isolated analog output channels for controlling user devices (see Figure 1). Each channel has two possible outputs: 0-20 mA Interface industry standard current output and 0-5 V Interface industry standard voltage output. Only one of the outputs can be enabled in a particular channel - either current or voltage. The modules digital to analog converter resolution is 14 bit. The Analog Output channels are optically isolated from the module internal logic circuits. The modules are fully calibrated and can be tested and recalibrated in the field. Each analog output has three status LEDs, Vout, Iout, and CAL which represent the calibration status of each output for voltage/current. The AO Module Configuration includes: AO Type - The analog outputs can be set to voltage, current, or raw data. AO Value - The analog outputs can be set to a numeric value (in the range of 0 to 16000) or either in voltage or current according to the output type. The values for voltage are 0 to 10 V and the values for current are 0 to 20 mA. AO Calibration - The upper and lower limits of analog outputs can be calibrated either as current (20mA upper limit and 4mA lower limit) or voltage (10V upper limit and 2V lower limit). Default upper and lower calibration limits are provided from the factory. Keep Last Value (KLV) and Predefined Value (PDV) - Each output can be configured to KLV or to a PDV. This value is maintained in the event of AO module failure or communication failure with the CPU. The predefined value can also be used during normal operation to force a value that masks the actual output value. Sleep Mode - Each AO module can be switched by the user application program to Sleep Mode. In Sleep Mode, the module does not function and the power consumption is minimized. During Sleep mode the user application program will get the predefined values for each output. I/O Legacy Resolution Parameter - In systems with both ACE3600 RTUs and legacy (MOSCAD/MOSCAD-L) RTUs, some MOSCAD/MOSCAD-L applications can be upgraded to ACE3600 without modifying the references to analog values in the applications (C or ladder). The I/O Legacy Resolution STS advanced parameter sets the Analog I/O bit resolution to either Actual (ACE3600) or Legacy (MOSCAD/MOSCAD-L).
43
Parameter
Selection
Default setup
Per Module / Output
Parameter Setup location
AO Type
Voltage/Current
User Defined
Output
STS HW Test/User application program STS HW Test/User application program STS HW Test
AO Value
Voltage - 0 to 10 V Current - 0 to 20 mA Voltage - 2 to 10 V Current - 4 to 20 mA KLV/PDV PDV=value No /Yes
User Defined
Output
AO Calibration
Voltage - 2 to 10 V Current - 4 to 20 mA KLV
Output
KLV & PDV Mask
Output
Application Programmer I/O link table Application Programmer I/O link table
No
Output
In the event of AO Module failure, the I/O module ERR LED will be lit. The event is registered by the CPU in the Error Logger. AO Module failure status is also visible to the user application program. In addition to the ERR LED, the module includes a voltage output (Vout), current output (Iout), and calibration (CAL) LED for each output.
CAL Vout Iout Indication
On On On Off Off Off
On Off On On On Off
On On Off On Off On
Neither output is calibrated. Iout is uncalibrated. Vout is uncalibrated. Both outputs are defined by the user, either using HW test or user application program to send raw data. Vout is defined by the user, either using HW test or user application program. Iout is defined by the user, either using HW test or user application program.
The AO module can be diagnosed and monitored using the STS Hardware Test utility. The Hardware Test verifies that the module is operational, shows the type and actual value of each output, enables calibration, and presents the ROM data calibration factors. The AO type can be set either in the user application program or in the Hardware Test.
44
To set the output value in the Hardware test, the user application program must be stopped or the AO module frozen. To calibrate the output in the Hardware test, the user application program must be stopped or the AO module frozen. In the Hardware Test utility, it is possible to set the AO module to Freeze Mode. In this mode, the AOs will keep the last value they had at the time they were frozen. Freeze mode enables testing the inputs and outputs while the user program is running. AO Module Value Representation:
In 0-20 mA current outputs Decimal Value Output Current
0 4000 8000 16000

In 0- 10 V voltage outputs Decimal Value
0 5 mA 10 mA 20 mA
Output Voltage
0 4000 8000 16000
0V 2.5 V 5V 10 V
45
AO - Typical Output Circuit

Variable Current source 12V 20V 50 330
Floating Voltage Converter

30V D/A Control
Iout
PGND
RET
30V 26V
- + Variable Voltage source
Vout
46
4 AO Module Block Diagram:
47
I/O Connection Diagram:
Current Output wiring
AO Module
+ Device / Load -
Shield
Iout x Ret x
Voltage Output wiring
AO Module
+ Device / Load -
Shield
Vout x Ret x
48
Digital Output and Digital Input FET Modules

The Digital Output/Digital Input (DO/DI) FET modules have 16 or 32 configurable user connections, organized in groups. Each group can be configured as an 8 DO group or as an 8 DI group. The outputs are optically isolated current sink FET type with back indication. The inputs are optically isolated Dry Contact type with internal wetting voltage. In the 32 DO/DI module, the following I/O combinations can be configured in the ACE3600 STS site configuration:
I/O combination DI location DO location
32 DO 8 DI + 24 DO 16DI + 16 DO 24 DI + 8 DO 32 DI
1-8 1-16 1-24 1-32
1-32 9-32 17-32 25-32 -
In the 16 DO/DI module, the following I/O combinations can be configured in the ACE3600 STS site configuration:
I/O combination DI location DO location
16 DO 8 DI + 8 DO 16 DI
1-8 1-16
1-16 9-16 -
The appropriate combination is selected as the I/O module type, when configuring the I/Os in the ACE3600 STS site configuration. Each DI can be configured as Fast Capture DI in the STS advanced I/O configuration. Fast capture causes the SCAN ladder output operation to get the first change that occurred since the previous scan. When fast capture is disabled (default), the scan gets the current value of the DI (in this case DI changes between scans are missed). Each input has a hardware input filter to make sure that the input reading is stable. The hardware DI filter range is 0 to 50.8 mS (in 0.2 mS steps). Counter DI filter range is 0 to 12.75 mS (in 0.05 mS steps). The DI filter can be set in the STS advanced I/O configuration. Note: In this module, the minimum effective filter value is 1 mS.
49
Each DI can be set in the Application Programmer I/O link table to trigger recording of time tagged events upon any input change of state. The time tagged events are recorded in the CPU memory and can be retrieved for various purposes. Each input can be configured to KLV or to a PDV (0, 1) in the Application Programmer I/O link table. This value is shown to the user application program in the event of DI module failure. Also, the predefined value can be used during normal operation to force a value that masks the actual input value. In this case the user application program will get the PDV instead of the actual input value. Each output can be configured to Keep Last Value KLV or to a Predefined Value PDV (0, 1). This value is executed when the user application program stops or when the module has no communication with the CPU module. Also, the predefined value can be used during normal operation to force a value on the output by ignoring the user application program value. The DO/DI FET module features which can be configured are listed in the table below. Some parameters are per module and some are per input.
Parameter Selection Default Setup Per Module/ Input Parameter Setup Location
DI Fast Capture DI Filter * DI Counter Filter* DI Event Time Tagging DI Keep Last Value & Predefined Value DI Mask
Disabled /Enabled 0-254 (x 0.2 mS) 0-255 (x 0.05 mS) Disabled /Enabled
Disabled 50 (10 mS) 20 (1 ms) Disabled
Input Module Module Input
RTU configuration RTU configuration; C Program RTU configuration; C Program Application Programmer I/O link table Application Programmer I/O link table Application Programmer I/O link table Application Programmer I/O link table
KLV/PDV PDV = 0/1 No /Yes
KLV
Input
No
Input
DO Keep Last Value & Predefined Value
KLV/PDV PDV = 0/1
KLV
Output
The counters are limited to 1Khz; therefore filtering is relevant from 1mS and above. In this module the minimum relevant value for DI Filter is 5 and the minimum value for DI Counter Filter is 20.
50
Parameter
Selection
Default Setup
Per Module/ Input
Parameter Setup Location
DO Mask
No /Yes
No
Output
Application Programmer I/O link table
Each DO/DI module can be switched by the user application program to Sleep Mode. In Sleep Mode, the module does not function and the power consumption is minimized. During Sleep mode, the user application program will get the KLV or PDV per each DI. In the event of a DO/DI module failure, the ERR LED on the module will be lit. This event is registered by the CPU in the Error Logger. DO/DI module failure status is also visible to the user application program. The DO/DI module can be diagnosed and monitored using the STS Hardware Test utility. The Hardware Test verifies that the module is operational, presents the module configuration and shows the actual value of each input and output. It is also possible to change the input filter setup for the duration of the Hardware test and change the value of the DOs. In the Hardware Test utility, it is possible to set the module to Freeze Mode. In this mode the user application program will get the KLV/PDV of each input in the module instead of the actual input value. The DO values will keep the last value they had when the module was switched to Freeze Mode. Freeze mode enables testing the inputs and outputs while the user application program is running.
51
DO/DI - Typical I/O Circuit

12V 5V
Floating Voltage Converter

DI Status/ DO Back Indication
20K
Self Recovery Fuse 1A
DO/DI
* DO Control 33V
COM
in DI configuration * FET Always OFF
52
16 DO/DI Module Block Diagram:
53
32 DO/DI Module Block Diagram:
54
I/O Connection Diagram:

DI wiring DO/DI FET Module
DIx (input x) Dry Contacts Switch / Sensor
COM (Common)
DO wiring DO/DI FET Module Load DC Source + DOx (Output x) Diode (Inductive load)
COM (Common)
55
Mixed I/O Modules

The ACE3600 Mixed I/O modules include a mixture of Digital Inputs, Relay Outputs and Analog Inputs on the same module. The available Mixed I/O modules are: 16 Digital Inputs + 4 EE DO Relay Outputs + 4 Analog Inputs ( 20 mA) 16 Digital Inputs + 4 ML DO Relay Outputs + 4 Analog Inputs ( 20 mA)
For operation, description, and configuration of the DIs, refer to the Digital Input Modules chapter. For operation, description, and configuration of the DOs, refer to the Digital Output Relay Modules chapter. For operation, description, and configuration of the AIs, refer to the Analog Input Modules chapter. For operation, description, and configuration of the AOs, refer to the Analog Output Modules chapter.
56
Mixed I/O Modules
Mixed I/O Module Block Diagram:
57
Mixed Analog Modules

The ACE3600 Mixed Analog modules include a mixture of Analog Inputs and Analog Outputs on the same module. The available Mixed Analog modules are: 4 Analog Outputs + 8 Analog Inputs (0-20 mA) 4 Analog Outputs + 8 Analog Inputs (0-10V) For a description of the AIs in the Mixed Analog modules, see the Analog Input Modules chapter. For a description of the AOs in the Mixed Analog modules, see the Analog Output Modules chapter. The Mixed Analog modules support an optional 24V DC floating plug-in power supply to power external devices.
58
Mixed Analog Modules
Mixed Analog Module Block Diagram:
59
I/O Expansion
The ACE3600 RTU includes the option of expanding the number of I/O modules controlled by a single CPU module on the main frame. The I/O expansion frames can be co-located with RTU on the main frame (installed in the same 19 rack or cabinet) or distributed in the same site (up to 50 meters from the main frame.) I/O expansion is based on a 100 Base-T full duplex Ethernet connection between the CPU module and the expansion modules. This type of connection enables the user program application to control and monitor the I/O modules on the expansion frames transparently as if they are located on the main frame. The user can diagnose all the modules on the expansion frames using the STS connected to the CPU on the main frame (locally or remotely.) The STS can also be connected locally to the expansion modules RS232 (STS1) port. I/O expansion is based on three modules: Expansion LAN Switch: This module is part of the expansion frame. It is installed in the main frame in an I/O module slot. Up to seven expansion frames can be connected through a single expansion LAN switch. (For one expansion frame, the switch is not required.) Eight to thirteen expansion frames can be connected using a combination of two expansion LAN switches. Expansion Power Supply: This module is installed in the I/O expansion frame. It extends power (and 12V DO control) from the power supply on the RTUs main frame to the I/O expansion frame, or from one I/O expansion frame to another. This module can be replaced by another ACE3600 power supply option per power requirements or when the expansion frame is not co-located with the main frame. Expansion Module: This module is part of the expansion frame. It is installed in the I/O expansion frame next to the power supply. It is connected via LAN to the RTUs main frame, either to the CPU module or to the expansion LAN switch, depending on the configuration. For more information, see Expansion Module below.
Note: Only a dedicated LAN with ACE3600 components should be used by the main CPU and expansion modules to communicate with each other. Connecting other elements such as routers and other devices to the LAN may disrupt the I/O expansion system operation. Note: The main CPU must include an Eth1 Ethernet port. Therefore, only the CPU 3640 can be used for I/O expansion on the main frame. The figure below provides a general view of an ACE3600 CPU with a single I/O expansion frame. The expansion module on the I/O expansion frame is connected using a crossed LAN cable to the CPU 3640 on the main frame (Port Eth1.) The expansion power supply on the I/O expansion frame is attached via DC cable to the power supply on
60
I/O Expansion
the main frame. Accessories such as a mobile radio, battery, etc. are attached to a separate optional 19" frame metal back.
Main Frame Main PS (AC/DC) CPU3640
Radio/Batt. Chassis
(optional)
DC Cable
Crossed LAN Cable
Expansion PS Expansion Module
I/O Frame
ACE3600 I/O Expansion Single Frame Example
The figure below provides a general view of an ACE3600 CPU with a single I/O expansion frame. The expansion module on the I/O expansion frame is connected using a crossed LAN cable to the CPU 3640 on the main frame (Port Eth1.) The expansion power supply on the I/O expansion frame is attached via DC cable to the power supply on the main frame. Accessories such as a mobile radio, battery, etc. are attached to a separate optional 19" frame metal back.
Main Rack Main PS (AC/DC) CPU (3640) Expansion Switch Communication Cable DC Cable Expansion PS (DC) Expansion Module Radio/Batt. Chassis
(optional)
LAN Cable
LAN Cable
LAN Cable
I/O Rack #1
I/O Rack #2
I/O Rack #7
ACE3600 I/O Expansion Multi-Frame Example
61
I/O Expansion
Note: The number of expansion power supplies that can be cascaded to the power supply on the main frame is limited. When required, optional DC or AC power supplies should be installed on the expansion frames to meet the accumulated power consumption and voltage level requirements. In the maximal configuration, up to 110 I/Os can be connected to the ACE3600, by using two expansion Ethernet switches on the main frame and thirteen I/O expansion frames. See the figure below.
Main Rack Main PS (AC/DC) CPU 3640 Expansion Switch 1 Expansion Switch 2 Communication Cables LAN Cable LAN Cable PS (AC) Expansion Module LAN Cable Radio/Batt. Chassis
I/O Rack #7
I/O Rack #8
I/O Rack #13
DC Cable
LAN Cable
LAN Cable
LAN Cable
Expansion PS (DC) Expansion Module
I/O Rack #1
I/O Rack #2
I/O Rack #6
ACE3600 I/O Expansion Maximal I/O Configuration
The following table shows the various configurations per required number of I/O slots:
Number of I/O Slots Main Frame F75xx LAN Switch option Exp. Frame F7510 LAN Cable LAN Crossed Cable 0-8 9-16 17-23 24-31 32-39 40-47 48-55 56-63 64-70 71-78 79-86 87-94 95-102 103-110
10
11
12
13
0 0
0 1
2 0
3 0
4 0
5 0
6 0
7 0
8 0
9 0
10 0
11 0
12 0
13 0
Note: This table assumes the main frame and expansion frames have 8 I/O slots (use option V108).
62
I/O Expansion
I/O Expansion Frame An I/O expansion frame always includes an expansion module to enable the CPU in the main frame to communicate with and control the expansion frame and its I/O modules. The expansion module is provided with each expansion frame (model F7510). Like the ACE3600 main frame, the I/O expansion frame can contain 2, 3, 5, 7 or 8 I/O slots. The expansion frame is compatible with the chassis and housing options. I/O Expansion Power The choice of power supplies for a system with I/O expansion is determined by the specific configuration and the power requirements of the system. In a co-located system where the power supply on the main frame feeds the I/O expansion frame, a low-tier power supply cannot serve as the main power supply. In a distributed system where the power supply on the I/O expansion frame is not connected to the main frame, any power supply modules can be used which suit the power requirements of the system. When applicable, it is recommended to have an external single power on/off switch to control all the power supplies simultaneously. Similarly, it is very important to have a single on/off switch for all 12V DO controls. Power-up/Restart/Power-down In a system where the power supply on the main frame feeds the I/O expansion frame, powering up/restarting the main power supply will power-up/restart the expansion frames as well. Power down of the main power supply will power-down the expansion frames as well. In a system where the power supply on the I/O expansion frame is not connected to the main frame, powering down or restarting the main power supply will not impact the I/Os on the expansion frame I/Os. However, these expansion I/Os may be reset after a period of time as a result of this action. If the expansion frame loses communication with the main frame for more than a certain number of seconds (configurable), it will restart. For information on configurable timeouts which may cause the expansion module to restart, see the ACE3600 STS User Guide - Appendix A: Site Configuration Parameters. Status and Diagnostics Status and diagnostics information can be retrieved from the expansion module, LAN switch, and power supply using the STS Hardware Test utility and SW Diagnostics and Loggers, via the CPU on the main frame. In a system where the expansion frames are not co-located with the main frame, status and diagnostics information on the expansion components can be retrieved by connecting a PC running STS directly to any expansion module RS232 port.
63
Expansion Power Supply Module

The expansion power supply module (10.8-16V DC) extends power from the power supply on the RTUs main frame to the I/O expansion frame, or from one I/O expansion frame to another. Note that this module is provided as default power supply in each I/O expansion frame unless replaced with the other power supply options. Characteristics of the expansion power supply module: Located on the leftmost slot of the expansion frame Provides overvoltage protection for the I/O expansion frame
The expansion power supply can only be connected to the power supply on the ACE3600 RTU main frame and to other expansion power supply modules. If all the power supplies on I/O expansion frames are attached via DC cable to the power supply on the previous I/O expansion frame in a daisy-chain manner, the main power supply controls the entire RTU. This enables the user to turn off the entire RTU simply by turning off the main power supply. If the main power supply does not control all other power supplies in the RTU (e.g. when the total power consumption required does not allow all frames to be daisy chained), it is recommended that the main power provided to the power supplies be connected to a single external on/off power switch. Important: When adding expansion power supplies, make sure that you do not exceed the total power limit of the main power supply, as all connected expansion power supplies drain energy from it. Also make sure that the voltage provided to each power supply (when connected in a daisy-chain manner) does not fall below the minimum operating voltage (see RTU I/O Expansion - Power Considerations below). The power supply on each expansion frame must be connected to the grounding strip of its frame. The expansion power supply includes two slow blow fuses, one 4A fuse for overcurrent protection for the I/O expansion frame and one 8A fuse for maximum current via the Power in/out circuit. The expansion power supply module is connected to another ACE36000 power supply using a DC power cable (FKN8559A/3002360C26).
64
Expansion Module
The expansion module provides an interface from the CPU module (either directly or via the expansion LAN switch) on the ACE3600 main frame to the I/O modules on the expansion frame. This enables the CPU on the main frame to control the I/O modules on the expansion frame and process the gathered data. This module is installed in the I/O expansion frame in the CPU slot, second slot from the left and is connected via dedicated LAN to the RTUs main frame. The expansion module includes two on board communication ports: Exp Eth1 (E1) - 10/100BaseT Ethernet port, used to connect to the expansion Ethernet switch or to the main CPU STS 1 (STS1) RS232 port, used to connect a PC running the ACE3600 STS to perform diagnostics and other STS operations (for distributed I/O), as if it is connected directly to the main CPU.
The expansion module includes a (rotary) selector switch which enables the user to determine the frame number in the expanded RTU. The frame number is used during communication with the main CPU, with the STS, etc. The expansion frame number range is 1 to 13. On the selector switch, A, B, C and D refer to 10,11,12 and13. Note: Changing the selector position when the expansion frame is running, takes effect only after the next restart. The expansion module shipped from the factory is set by default to 1. In a multiexpansion frame configuration, the settings of additional I/O expansion frames must be changed accordingly to provide each frame with a unique number. The expansion module can be connected to the main frame in two ways:
Single expansion frame - Direct connection:
In a system with a single expansion frame, connect the Eth1 port on the expansion module directly to the Eth1 port on the main CPU, using a crossed LAN cable (V665/FKN8525A).
Switch connection:
In an RTU with more than one expansion frame, the Eth1 port on the expansion module is connected to one of the Ethernet ports Eth2-Eth8 on the expansion Ethernet switch (situated on the main frame). Note: The Eth1 port in the expansion Ethernet switch is reserved for connection to the main CPU. If two switches are used, the Eth1 port on the expansion module is connected to one of the Ethernet ports (Eth3-Eth8) on the first expansion Ethernet switch or to one of
65
I/O Expansion
the Ethernet ports (Eth2-Eth8) on the second switch. (The Eth2 port on the first switch is connected to the Eth1 (M) port on the second switch Ethernet LAN.) Expansion frames are provided without cables. For connection, use one of the cables listed below or use any other standard Category 5E shielded (FTP) LAN cable (up to 50 meter length). Three different Ethernet cables are available for this purpose. Choose the cable length based on the distance from the main frame to the expansion frame. 60 cm (Motorola p/n V529 / FKN8561A) - This cable is used for local connection of the main CPU to the expansion switch, or connection of the first LAN switch to the second, if such exists. 2 meter (Motorola p/n V648 / FKN8562A) 3 meter (Motorola p/n V666 / FKN8563A)
Module Firmware and Operation Modes

The expansion module firmware extends the main CPU control to the I/O modules located in the expansion frame. The expansion module (expansion CPU) is shipped from the factory with a dedicated firmware called Expansion Loader. After connecting to the main CPU (MCPU), the expansion module loads the Expansion Firmware Image from the main CPU to ensure that all modules use the same firmware version. The following diagram describes the initiation process of an expansion module after power-up/restart and during run-time.
66
I/O Expansion
no
yes The Expansion module discovers the main CPU (MCPU) via UDP/IP (broadcast). Expansion Loader Discovery succeededobtained self and MCPU IP address? yes 1. Loads the Firmware Image into RAM from the MCPU (using TCP). 2. Turns off all LEDs and runs the loaded Expansion Firmware Image. 3. Auto-recognizes actual I/O modules. Loads user files from the MCPU (using TCP) and saves in FLASH: 1. Configuration, if such exists 2. Application database, if such exists 3. Predefined input and output values and I/O link (if such exist) 4. Encryption files, if such exist
no
yes Failed to load one or more files? no 1. Registers its actual I/O modules information in the MCPU (using TCP). 2. Initializes the Expansion Image (system startup). 3. Negotiates Ethernet addresses (MAC) and starts EMI with the MCPU via TCP. Expansion Firmware Image
yes
Failed to negotiate or start EMI? no
Running: 1. Monitor EMI communication with the MCPU. 2. Monitor the MCPU status via TCP. 3. Monitor actual I/O modules change (hot-swap) and update the MCPU.
yes
Has the MCPU restarted, or disconnected for more than fail time (60 seconds)?
no
67
I/O Expansion
Expansion Module Power-up and Restart

The MCOM LED on the expansion module indicates the connection status between the expansion module and the main CPU and expansion frame initialization progress. The main CPU expects the expansion frames to complete the initialization within a configurable period of time (60 seconds default). After this period of time elapses, the main CPU will operate normally with the connected frames and their I/O modules. Any expansion frame that has not completed initialization within that time (e.g. because it was connected later to the RTU) will be ignored until the next main CPU restart. Note that after the main CPU starts up, it waits for the expansion modules to complete the initialization process. The wait time is derived from the number of expansion frames configured in the RTU. After all the expansion frames have completed the initialization, the main CPU will continue its system startup. The main CPU will wait 60 seconds (default) for all expansion frames to connect.
Expansion Module during Run-Time

The expansion module constantly exchanges I/O data and status data with the main CPU, using the Ethernet Micro-code Interface (EMI). The EMI enables the main CPU to be updated by all the expansion modules every very short period of time via the expansion Ethernet LAN. The main CPU constantly synchronizes the expansion module date and time, and periodically polls the errors, pushbuttons and time tagged data from all the connected expansion modules. If the connection between the expansion module and the main CPU is lost (e.g. due to main CPU restart, cable disconnection, etc.) for a configurable period of time (1 minute default), the expansion module will restart and the initialization process will begin again. After the expansion frames have initialized, it is possible to download to the RTU a user program or other user defined files. After successful download, the main CPU automatically updates each expansion module. Note that if the main CPU tries to download a user program or other files to an expansion module during initialization, the expansion module is restarted.
68
Expansion LAN Switch

The expansion Ethernet switch provides an interface from the ACE3600 CPU (on the master RTU frame) to up to seven expansion frames, or up to 13 expansion frames when two switches are used. This enables up to 110 I/O modules in a single RTU. The expansion modules can be co-located with the switch (installed in the same 19" frame or cabinet) or distributed in other locations. The switch is installed only in the RTUs main frame, in either of the first two I/O module slots. The ACE3600 expansion LAN switch is configured to prioritize different Ethernet data frame types. A special protocol, used for communication between the expansion LAN switch and the main CPU, quickly collects I/O information from the expansion frames to the main CPU and adds the highest priority and special tags to these Ethernet frames. The switch recognizes these frames and gives them the highest priority in the buffer queue, higher than the frames of the standard protocols (MDLC, TCP/IP) used for communication in the ACE3600 system. For this reason, only the ACE3600 expansion LAN switch can be used in an I/O expansion system. IMPORTANT: When an expansion LAN switch is used on an I/O expansion LAN, only the main CPU and the expansion frames (expansion modules) can be connected to the expansion switch(es). Any attempt to connect other devices to the expansion switch(es) may result in unpredictable communication delays between the main CPU and the expansion frames and malfunction of the expanded RTU. The expansion LAN switch includes eight 100BaseT Ethernet communication ports: The expansion LAN switch can be inserted and extracted while the system is powered up. LAN switch status and diagnostics information can be retrieved via the main CPU using the STS Hardware Test utility. LAN switch warnings and errors are logged in the main frame CPU memory. The RTU error logger information can be retrieved using the STS Error Logger utility. The expansion LAN switch option includes a 60 cm Ethernet cable (Motorola p/n V529/FKN8561A). Use this cable to connect from the Eth1 port on the main CPU to the Eth1 (M) port on the expansion switch. For the second switch in a system (if such exists), use this cable to connect from the Eth2 port on first switch to the Eth1 (M) port on the second switch.
69
I/O Expansion
One of three Ethernet cables can be used to connect an Ethernet port on the expansion LAN switch to an expansion module in an expansion frame. If the system includes one switch (for up to seven frames), ports Eth2-Eth8 are available. If the system includes two switches (for up to thirteen frames), ports Eth3-Eth8 are available on the first switch and ports Eth2-Eth8 are available on the second switch. Note: The Eth.1 (M) port on the expansion LAN switch is reserved for connection to the main CPU. For details on the Ethernet cables, see Expansion Module above. In systems with several expansion frames, the ACE3600 STS can be used to provide automatic switch connection configuration. The following physical connections are assumed: A system with one expansion frame is connected directly to the main CPU. A system with 1-7 frames (frame IDs 1-7) is connected via one switch (to expansion LAN switch ports Eth2-Eth8 respectively.) A system with 1-13 frames is connected via two switches (frame IDs 1-6 connected to expansion LAN switch 1 ports Eth3-Eth8 respectively and frame IDs 7-13 connected to expansion LAN switch 2 ports Eth2-Eth8 respectively.) If the expansion frames are not physically connected as described above, the switch connection must be manually configured in the STS Switch Connections dialog. For more information, see the ACE3600 STS User Guide.
70
RTU I/O Expansion - Power Considerations

When planning a co-located multi-I/O expansion frame configuration (where all frames are located in the same enclosure or 19" rack), it is possible to cascade the power supplies of the expansion frames to the power supply in the main frame. In the system design stage (before ordering), it is critical to calculate the maximal accumulated power consumption from the main frame power supply (or from a power supply located on an expansion frame which is not an expansion power supply) to make sure it is not overloaded. It is also critical to consider the voltage drop due to the cascading of power supplies.
Power Consumption
The first step in the design is to calculate the number of expansion frames that can be cascaded per the power supply specifications. The following power consumption information should be accumulated for the RTU: Maximal accumulated power consumption of the main frame (CPU, I/O modules, 24 V floating power supplies on modules, radio, etc.) Maximal accumulated power consumption of the each expansion frame (expansion module, I/O modules, floating power supplies on modules) Note: The power consumption information is described in the ACE3600 Owners Manual and in this document in Appendix C: ACE3600 Maximum Power Ratings. The accumulated power consumption from the main power supply (located in the main frame) should not exceed its maximum current output specifications. Consider the following example: An expanded RTU requires five expansion frames. The accumulated power consumption of all frames exceeds the main power supply specifications. The accumulated power consumption of the main frame and the four first frames exceeds the main power supply specifications. The accumulated power consumption of the main frame and the three first frames does not exceed the main power supply specifications. This means that from the power consumption perspective the first three expansion frames can be cascaded to the power supply in the main frame, the expansion power supply on the fourth expansion frame should be replaced with AC or DC power supply option and the fifth expansion power supply can be cascaded to this added power supply.
Voltage Drop
The second step is to calculate the number of expansion power supplies that can be cascaded per the allowable input voltage to the expansion power supply.
71
I/O Expansion
Each cascaded expansion power supply gets a lower input voltage from the preceding power supply. The voltage drop is a function of the expansion power cable resistance and the current flowing through the cable (which is the accumulated current of the expansion frame and all the following expansion frames cascaded to it.) The paragraph below shows how the input voltage of a cascaded expansion frame can be calculated. Below is a block diagram of cascaded power supplies.
n Vo Ix Vx
the number of expansion frames the output voltage of the main power supply the maximal power consumption of expansion frame #x (x = 1,2,3..n) the voltage in the input of expansion power supply #x (x = 1,2,3..n)
The equivalent electrical circuit diagram of such system is:
The values of V1, V2..Vn must be calculated. For example: Assume n= 4 V1 = Vo - 0.15(I1+I2+I3+I4) - 0.15(I1) V2 = Vo - 0.15(I1+I2+I3+I4) - 0.15(I2+I3+I4) - 0.15(I2) V3 = Vo - 0.15(I1+I2+I3+I4) - 0.15(I2+I3+I4) - 0.15(I3+I4) - 0.15(I3) V4 = Vo - 0.15(I1+I2+I3+I4) - 0.15(I2+I3+I4) - 0.15(I3+I4) - 0.15I4 0.15(I4)
72
I/O Expansion
The general equation for Vx is:
Vo depends on the power supply configuration. Vo should be 13 V DC when the backup battery option is not used. If the battery option is used with the main power supply, during power fail Vo depends on the battery voltage (which may be below 13 V DC). It is highly recommended to use at least 11 V DC for input voltage Vx. Consider the following example: An expanded RTU includes five expansion frames. The maximal accumulated current consumption of each expansion frame (expansion module, I/O modules, floating power supply on modules, etc.) is calculated. The input voltage Vx of each expansion power supply (V1-V5) is calculated as described above. The input voltage at the first three expansion power supplies (V1,V2, V3) is above 11 V DC. The input voltage at the last two expansion power supplies (V4, V5) is below 11 V DC. This means that from the voltage drop perspective, the first three expansion frames can be cascaded to the power supply in the main frame, the expansion power supply on the fourth expansion frame should be replaced with an AC or DC power supply option and the fifth expansion power supply can be cascaded from the fourth frame power supply.
IMPORTANT: Design note: The design must take into account the worst case result of both the power consumption calculation and voltage drop calculations.
73
CPU and Power Supply Redundancy

General
The ACE3600 CPU and power supply redundant configuration enables installation of two redundant CPUs (CPU3680 only) and two redundant power supply modules. The CPU redundancy feature is supported only by the CPU 3680 module, which enables motherboard Ethernet interconnection between the two CPUs. The CPU redundancy ensures continuous RTU operation if one CPU fails. The redundant power supply configuration ensures the supply of the required RTU voltages when one of the power supplies fails. For detailed information on configuring and programming CPU and power supply redundancy, see the RTU Redundancy section of the ACE3600 STS Advanced Features manual.
Redundant CPU and Power Supply Frame

The redundant CPU and power supply configuration requires the dedicated dual power supply, dual CPU and 4 I/O slots frame and motherboard. This frame fits a wall mount installation, large metal chassis and large housing or 19 metal base options.
Redundancy Definitions
Primary CPU/power supply leftmost CPU/power supply Secondary CPU/power supply rightmost CPU/power supply Active CPU the CPU that controls the I/O modules. Standby CPU the CPU that does not control the I/O modules.
74
Redundant CPU
Redundant CPU Behavior
When redundant CPUs (ACE3680 only) are used, the CPU in the leftmost CPU slot (to the right of the first power supply) is the primary CPU. The CPU in the rightmost CPU slot is the secondary CPU. The primary CPU communicates with the primary power supply and the secondary CPU communicates with the secondary power supply (if the secondary power supply exists.) When the RTU is powered up, the primary CPU becomes the active CPU (monitors/controls the I/O modules.) If the primary CPU does not exist or has failed, the secondary CPU becomes the active CPU. If the primary exists and is working, the secondary CPU becomes the standby CPU (which continuously monitors the active CPU.) On the active CPU, the I1 ACTV LED is lit. If the standby CPU detects that the active CPU has failed, it automatically becomes the active CPU and controls the I/O modules. The CPU switchover takes typically 1530 milliseconds. When the faulty CPU is repaired or replaced with a working CPU, the newly installed CPU becomes the standby CPU. If both the primary and secondary CPUs exist and are working, a forced active CPU switchover can be performed from the STS Hardware Test by deactivating the active CPU, after which the standby CPU will become active. A forced switch can also be performed from a C user application. If both the primary and secondary CPUs exist and are working, hot swap of the CPU is supported. Note that if the active CPU is removed, the standby CPU automatically becomes active. Redundancy switchover occurs within 10 msec of loss of active CPU control (i.e. if the active CPU does not reset the watchdog for more than 5 msec, if the active CPU resets, or if the active CPU is removed from its slot.)
The ACE3680 CPUs include an internal Ethernet 100 Mb/s port used for redundancy only. This interconnection (via motherboard) between the active and standby CPUs enables the active CPU to continuously synchronize the standby CPUs database and clock.
Redundant Power Supply

Redundant power supplies are used to ensure a continuous supply of the required RTU voltages, in the event that one power supply fails. When one of the power supplies fails, the user application program can sense it and send an alarm to the control center. Both the primary and secondary power supplies must be of the same type. Note that only the
75
primary power supply is configured in the STS and the configuration is duplicated to the secondary power supply.
Redundant Power Supply Behavior

The primary power supply always has priority in providing power to the CPUs and I/O modules. The secondary power supply takes over if the primary fails or if the voltage level of the primary is lower than the secondary voltage level by 0.4V. The primary PS takes over after a failed primary PS is replaced and switched on. In a normal condition when both power supplies are operational (and the primary has control) the auxiliary power outputs of both power supplies can be used to power external devices such as modem, radio, etc.
Redundant CPU and Power Supply Configurations

By default, the Redundant CPU and Power Supply option includes a special frame/ motherboard designed for dual power supply, dual CPU, and four I/Os. In addition, two CPU3680 modules, one 12V DC power supply and one blank power supply module are provided.
Default Redundant RTU Configuration
It is possible to replace the default single 12V power supply with any of the power supply options (AC, AC with charger, 18-72 VDC, etc.) except the low-tier power supply. In the case of AC PS or 18-72 VDC PS with battery charger, it is also possible to order a 6.5 Ah
76
or 10 Ah backup battery option, which also requires ordering the large metal chassis or large metal housing or 19 metal base. If a radio and/or accessory box is ordered, a large chassis or housing option is also required. Each CPU in the redundant configuration can have the same or different plug-in ports configuration. It is possible to order plug-in port options that will be installed by the factory on the primary CPU, and plug-in ports options that will be installed on the secondary CPU (each plug-in port option also has a secondary CPU plug-in port option. The SRAM option can also be ordered for the secondary CPU.
Redundant Power Supply Options

It is possible to order a secondary 12V power supply (dual power supply configuration) instead of the blank power supply module. In this case a dual power cable connecting between the Power junction box and the two power supplies will be provided too. Note: Dual power supply configuration can be ordered from the factory only with the 12V power supply. If dual AC PS or dual 18-72 V DC PS is required, the secondary PS and connecting cable should be ordered separately (not as an option). The primary and secondary PS must be of the same type. Important Note: When using dual AC PS or dual 18-72 V DC PS, the maximum ambient operating temperature of the RTU is limited to: 50C (122F) - when installed inside a metal chassis or closed cabinet. 60C (140F) - when installed without enclosure or closed cabinet. Redundant CPUs and power supplies are supported for CPU 3680 firmware version 15.0 and above, with power supply version V2.75 and above only (manufactured from April 2011.) The STS Hardware Test can be used to view the power supply version. The power supply version is not upgradeable.
Backup Battery
A 12V backup battery can be connected to the primary PS only. Important Note: Connecting a backup battery to the secondary PS may result in improper behavior of dual PS configuration.
CPU and Power Supply Redundancy with I/O Expansion

The redundant CPU configuration supports I/O expansion, but are limited to 12 expansion frames. The primary CPU and secondary CPU must be connected to the I/O expansion LAN switch(es). The I/O expansion frames must be connected to the LAN switch (note that with redundant CPUs even a single I/O expansion frame requires an expansion LAN switch module.)
77
The I/O expansion frames communicate with the active CPU only. When the active CPU fails and the peer CPU becomes active (or when the user deliberately switches the active CPU), the I/O expansion frames will reconnect to the current active CPU (in rare situations the expansion frame will restart before the reconnection.) The I/O expansion frames switchover typically takes 5-15 seconds. During this transition time, the I/O modules in the expansion frames use the Pre-Defined Value / Keep Last Value (PDV/KLV) mode until connection is established with the new active CPU. The I/O expansion frames can be cascaded only to the primary PS or to the secondary PS.
Redundant CPU Addressing

In the redundant CPU configuration, the RTU Site ID is referred to as the Common ID. Only the active CPU responds to MDLC packets addressed to the Common ID. Each CPU has its own Private ID: Primary CPU private ID = Common ID 1 Secondary CPU private ID = Common ID + 1 The Private IDs enable specific communication with the primary CPU or with the secondary CPU.
78
The active CPU responds to: Local STS MDLC messages targeted to the RTU Common ID MDLC messages targeted to its Private ID The active CPU forwards MDLC messages targeted to the peer CPU and other RTUs (per the network table.) The standby CPU responds to: Local STS MDLC messages targeted to his Private ID The standby CPU forwards MDLC messages targeted to the peer CPU and other RTUs (per the network table.) To enable routing through both the active and the standby CPUs, the generic network table includes the primary and secondary private IDs, and does not include the common site ID. To route only via the active CPU (the common site ID), the two redundant peers must have identical ports and links, and the network table must list the common site ID only. In this case, create a copy of the generic network table and replace the two private ID entries with one common site ID (with the same identical link/s as before.) The private IDs must be deleted from this copy of the network table. Download the modified network table to any RTUs which will route using the common site ID. IMPORTANT: The network table downloaded to the redundant peers themselves must include the private IDs.
CPU Database Synchronization

The new CPU3680 and the new redundant RTU motherboard enable the active and standby CPUs to communicate via the internal Ethernet interconnect on the motherboard. To ensure data integrity when CPU switchover occurs, the user program application running in the active CPU must continuously synchronize the data in the standby CPU database. Each CPU has new dedicated status flags in the system table: Active/Standby Flag - indicates if the CPU is Active or Standby. Peer CPU Fail Flag - indicates that there is a failure in the peer CPU. Primary/Secondary Flag - indicates if the CPU is Primary or Secondary.
79
These flags can be monitored by the Ladder application program (also available for C programs) running in each CPU. To facilitate the database synchronization, a CALL function (Tb2Cpy) enables batch copy of the required data from the active CPU database to the standby CPU database (available in STS V15.50 and above). A single parameter of this CALL function points to a table that includes two lists of tables (2 columns): Column 0: Source list of tables to copy from Column 1: Destination list of tables to copy into, in the peer CPU For detailed information, see the RTU Redundancy section of the ACE3600 STS Advanced Features manual and the ACE3600 STS User Guide.
80
ACE IP Gateway Module

The ACE IP Gateway module (CPU4600) is a Front End Processor (FEP) which enables SCADA control centers to communicate and interface with ACE3600 RTUs and legacy (MOSCAD-M, MOSCAD, and MOSCAD-L) RTUs in a control system. It acts as an interface between the MDLC world and the TCP/IP world. The ACE IP Gateway (IPGW) supports MDLC connection to multiple RTUs (ACE3600 and legacy MOSCAD RTUs) via terminal server ports from multiple SCADA clients. Data exchange between the SCADA (client) and the ACE IPGW (server) is carried out using peer -to-peer communication over a LAN. SCADA clients can be located on the same TCP/IP segment (location), connected directly to the ACE IPGW, or on different TCP/IP segments (locations), connected to the ACE IPGW via a WAN or a bridge device. The ACE IP Gateway, like all ACE3600 RTUs supports MDLC and NTP time synchronization, both as client and as server, MDLC encryption, IP firewall, and dynamic IP conversion table update at run time. The Gateway supports all ACE3600 and MOSCAD RTU data types. The ACE IP Gateway does not run a user application and does not support I/O modules. Like the legacy MOSCAD IP Gateway, the ACE IP Gateway supports redundancy. The primary and secondary ACE IPGWs share the same site ID. The primary ACE IPGW enables bi-directional transfer of both SCADA application messages and Gateway management messages. The secondary ACE3600 IPGW enables transferring of Gateway management messages only. (It does not send or receive any MDLC messages and is logically disconnected from the link.) For general information on using the ACE IPGW module, see ACE IP Gateway below. The ACE IPGW module can be installed on any of the existing ACE3600 chassis options including 19" rack configuration. Physically, the ACE IP Gateway module is comparable to the CPU 3680 module, in terms of available communication ports, memory, front panel and LEDs. Note that CPU 3680 is not compatible with the ACE IP Gateway firmware. For more information, see ACE IP Gateway below.
81
Ordering Information
ACE3600 RTU Ordering Flow:
For RTUs without I/O expansions, follow only the ordering steps for Main Frame below. For RTUs without redundant CPU & PS, follow the steps below for a main frame and an expansion frame.
Main Frame - Step 1 Select ACE3600 model Note: CE countries (Western Europe) Can only order ACE without radio (F7509) Without Radio
Model Type? ! You must specify frequency in the order
Model F7509 With Radio Conventional/ MotoTrbo radio
No
Need Radio installation kit? Yes Add Radio installation kit option
Select Radio Type
Trunked radio
Specify RTU model in the main row
Analog Trunk
Select Trunking Type
Digital Trunk (IV&D)
Portable radio HT750/GP320/ GP328/RO5150
What radio Type selected?
Specify Analog Trunk Radio model in the main row
Specify Digital Trunk Radio model in the main row
Add regional option V95X
Mobile radio CM200/EM200/ CM140/GM3188 CDM750
What radio Model selected?
MotoTrbo radio Add regional option V85X Add regional option V75X
Go to Main Frame - Step 2
82
Main Frame - Step 2 Set # of I/O Modules Slots and add I/O modules ! The default frame includes CPU 3640 and 12V DC PS Need slots for I/O modules or Exp. switch? 8 I/O Slots fits wall mount and 19 rack only Yes Add the required Option to set the frame to 2,3,5,7 or 8 I/O module slots No
The number of modules MUST match the number of available I/O slots Expansion LAN Switch occupies I/O module slot
Add the required I/O and Exp. Switch modules options
Cables, etc.
Add the required I/O modules Accessories Options
83
Main Frame - Step 3 Select installation type
! For models with radio and/or battery and/or accessories you must add a metal chassis or a housing
Need metal chassis, housing or 19 installation? Yes
No
Select the suitable metal chassis or housing

Number of I/O slots 2 (V102) 3 (V103) 5 (V 105) 7 (V107) 8 (V108) v v v v v v v Default v v v v
Chassis / Housing Small metal chassis (V229) Medium metal chassis (V214) Large metal chassis (V056) 19" metal back (V120) Small housing (V276 or VA00406 ) Large housing (V228 or VA00405)
0 v v v v v v
! Installation on 19 rack requires ordering 19 metal back V120 and 19 brackets option V051
! 8 I/O slots with radio and/or battery and/or accessory requires ordering option V269
84
Main Frame - Step 4 Select PS & Battery
! Default PS is 12 V DC Change Default PS Yes No
Yes
Needs backup battery?
No
Add AC PS or DC PS with charger option
Add AC PS or DC PS without charger option
Large Chassis /housing
What type of Installation?
Small /medium Chassis or Small housing
Add 6.5 Ah or 10 Ah battery option
Add 6.5 Ah battery option
Go to Expansion Frame - Step 5
85
Main Frame - Step 5 Select CPU and Plug-in
! Default CPU is CPU 3640 in all model except MotTrbo models which have CPU 3680 ! I/O Expansion requires CPU 3640 or CPU 3680
Change Default CPU Yes
No
! IP Gateway does not support I/O modules
Add CPU 3680 option or IP Gateway CPU (CPU 4600) option
Need Plug-in option
No
Please note! Conventional radio installation kit includes radio modem plug-in
Yes Add CPU Plug-in option
86
Main Frame - Step 6 Miscellaneous
Need miscellaneous Options? Yes Add miscellaneous options
No
Tamper switch, R S485 Junction Box, dummy module, etc.
Need I/O Expansion?
Yes
No
End
87
Expansion Frame Step 1 Select model Set # of I/O Modules Slots and add I/O modules
! The default frame includes Expansion module and Expansion PS
Select model F7510
8 I/O Slots fits wall mount and 19 rack only
Need slots for I/O modules or Exp. switch? Yes Add the required Option to set the frame to 2,3,5,7 or 8 I/O module slots
No
The number of Modules MUST match the number of available I/O slots
Add the required I/O Modules options
Cables
Add the required I/O modules Accessories Options
88
Expansion Frame - Step 2 Select installation type
! For frames with battery and accessories you must add metal chassis or housing
Need chassis, housing or 19 installation? Yes
No
Select the suitable metal chassis or housing

Number of I/O slots 2 (V102) 3 (V103) 5 (V 105) 7 (V107) 8 (V108) v v v v v v v v v v v v
Chassis / Housing Small metal chassis (V229) Medium metal chassis (V214) Large metal chassis (V056) 19" metal back (V120) Small housing (V276 or VA00406 ) Large housing (V228 or VA00405)
0 v v v v v v
! Installation on 19 rack requires ordering 19 metal back V120 and 19 brackets option V051
! 8 I/O slots with radio and/or battery and/or accessory requires ordering option V269
89
Expansion Frame - Step 3 Select PS & Battery
! Default PS is Expansion PS Change Default PS Yes No
Change PS per power requirements or if the expansion is not located with the main frame
Yes
Needs Backup battery?
No
Add AC PS or DC PS with charger option
Add AC PS or DC PS without charger option
Large chassis or housing
What type of Installation?
Small / medium chassis or small housing
Add 6.5 Ah or 10 Ah battery option
Add 6.5 Ah battery option
90
Expansion Frame - Step 4 Miscellaneous
Need miscellaneous Options? Yes Add miscellaneous options
No
Tamper switch, LAN cable, Dummy module, Driver license, etc.
Need additional I/O Expansion? No
Yes
End
91
List of ACE3600 Models

Note All RTU models include no I/O slots frame, 10.8-16 V DC PS and CPU 3640. No Radio Model ACE3600 Basic Model No Radio I/O Expansion Model Expansion Frame Conventional VHF Radio Models ACE3600 with CM200/CM140/EM200/GM3188 VHF ACE3600 with CDM750 136-174 MHz ACE3600 with HT750/GP320/GP328 /PRO5150 VHF Conventional UHF Radio Models ACE3600 with CM200/CM140/EM200/GM3188 UHF ACE3600 with CDM750 403-512 MHz ACE3600 with HT750/GP320/GP328 /PRO5150 UHF Analog Trunked VHF Radio Models ACE3600 with XTL2500 136-174 MHz Analog ACE3600 with XTL2500 136-174 MHz Digital ACE3600 with XTS2500 136-174 MHz Digital Trunked UHF Radio Models ACE3600 with XTL2500 380-520 MHz Analog ACE3600 with XTL2500 380-520 MHz Digital ACE3600 with XTS2500 380-520 MHz Digital Trunked 800MHz Radio Models ACE3600 with XTL2500 800MHz Analog ACE3600 with XTL2500 800MHz Digital ACE3600 with XTS2500 800MHz Digital MotoTrbo Digital Models ACE3600 with XPR4350/XPR4380/DM3400/XiR M8220/DGM4100 VHF ACE3600 with XPR4350/XPR4380/DM3400/XiR M8220/DGM4100 UHF ACE3600 with XPR4380 800MHZ Other Models CPU 3640 F7509 F7510 F7573 F7563 F7553 F7574 F7564 F7554 F7533 F7593 F7543 F7534 F7594 F7544 F7538 F7598 F7548 F7583 F7584 F7588 F7502
92
ACE3600 IP Gateway CPU4600 ACE3600 CPU 3680
F7507 F7508 F7500 F7600 FVN5680 FVN5809 FVN5510 FVN5810
Software ACE3600 System Tool Suite (STS) ACE3600 C Toolkit (CTK) ACE3600 Enhanced PID ACE3600 AGA 3 + 8 ACE3600 AGA 7 + 8 AGA History Upload Tool
Note: All radio models require Metal Chassis or Housing option. IMPORTANT: Only model F7509A and all its options, including radio installation kits, may be shipped to European Union (EU) countries. The installer must confirm that there are no emissions or harmful interference to the spectrum due integrating the radio into this model.
93
List of ACE3600 Options

Regional radio options CM200/CM140/EM200/CM3188 One of the following options must be ordered for models F7573 and F7574: CM 200 CM140 GM3188 EM200 HT750/GP320/GP328/PRO5150 One of the following options must be ordered for models F7553 and F7554. HT750 GP320 GP328 PRO5150 XPR4350/XPR4380/DM3400/XiR M8220/DGM4100 XPR4350/XPR4380 DM3400 XiR M8220 DGM4100 Radio Installation Kits options CDM750 installation kit CM200/CM140/EM200/GM3188 installation kit MDS X710/9810 installation kit HT750/GP320/GP328 /PRO5150 installation kit XTS 2500 installation kit XTL5000/2500 Analog installation kit MDS INET900/Transnet installation kit XTL5000/2500 Digital installation kit XPR4350/4380/DM3400/XiR M8220/DGM4100 installation kit Transnet900 OEM installation kit Frames 2 I/O slots frame 3 I/O slots frame 5 I/O slots frame 7 I/O slot frame 8 I/O slots frame 19" rack adjustable installation brackets
V851 V852 V853 V854
V951 V952 V953 V954 V751 V752 V753 V754 V143 V148 V152 V154 V156 V157 V680 V681 V682 VA00225 V102 V103 V105 V107 V108 V051
94
Metal Chassis 48 x 48 cm Metal Chassis (up to 7 I/O slots) 38 x 38 cm Metal Chassis (up to 3 I/O slots) 28 x 36 cm Metal Chassis (up to 2 I/O slots) 8 I/O (Expanded 19") Metal Chassis 19" Frame Metal Back Housing 50x50 cm Metal Housing (up to 7 I/O slots) 50x50 cm Metal Housing with padlock accessory 40x40 cm Metal Housing (up to 3 I/O slots) 40x40 cm Metal Housing with padlock accessory Housing Tamper Switch Power Supply, Battery Charger & Backup Battery (Default PS is 10.8-16 V DC input) DC Power Supply Low-Tier 10.8-16V AC Power Supply 100-240 V DC Power Supply 18-72V AC PS 100-240 V with Battery charger DC PS 18-72V with Battery charger 6.5 Ah Backup Battery 10 Ah Backup Battery CPU Upgrade (Default CPU is CPU 3640) Plug-in SRAM ACE3600 CPU 3680 ACE IP Gateway CPU 4600 CPU Plug-in Ports Plug-in RS232 Port Plug-in RS 485 PORT Plug-in Ethernet 10M Port Plug-in Ethernet 10/100 M Port Plug-in Radio Port Digital Input Modules 16 DI FAST 24V DC 32 DI FAST 24V DC 16 DI FAST 24V IEC TP2 32 DI FAST 24V IEC TP2 32 DI FAST 48V DC 16 DI 120/230V
V056 V214 V229 V269 V120 V228 VA00405 V276 VA00406 V224
V149 V346 V251 V261 V367 V114 V328
V447 V448 V449 V184 V440 V204 V212 VA00362 V265 V379 V117 V959 V474AB VA00331AA
95
Relay Output Modules 8 DO EE relay 2A 16 DO EE relay 2A 8 DO ML relay 2A 16 DO ML relay 2A 12 DO EE relay 120/230V 12 DO ML relay 120/230V SBO 8 DO 2 FormA EE Relay 2A Analog Input Modules 8 AI, 20 mA 16AI, 20 mA 8 AI, 5 V 16AI, 5 V Analog Output Modules 4 AO, 20 mA Mixed Input/Output Modules 16 DI/DO FET 32 DI/DO FET 16 DI 4 DO EE 4 AI, 20mA 16 DI 4 DO ML 4 AI, 20mA Mixed Analog Modules 4AO/8AI 20 mA 4AO/8AI 5 V Blank Module Blank I/O module I/O Module Cables 20-wire cable braid with TB holder 3 m 30-wire cable with TB holder 3 m 40-wire cable braid with TB holder 3 m 20-pin TB Holder kit 30-pin TB Holder kit 40-pin TB Holder kit I/O Expansion ACE3600 Expansion LAN Switch LAN Cable 60cm length LAN Cable 2 Meter length LAN Cable 3 Meter length LAN Cross Cable
V508 V616 V314 V516 VA00348 VA00332 VA00343AB V318 V463 V741 V742 V118 V480 V481 V245 V453 V562 V460 V20 V253 V202 V358 V158 V203 V153 VA00226 V529 V648 V666 V665
96
CPU and PS Redundancy ACE3600 Redundancy Secondary DC PS 10.5-15.5V Secondary CPU Plug-In RS-232 Port Secondary CPU Plug-In Ethernet 10M Port Secondary CPU Plug-In Ethernet 10/100 M Port Secondary CPU Plug-In RS 485 Port Secondary CPU Plug-In Radio Port Secondary CPU Plug-In 4 MB SRAM Communications Interface RS485 Connection Box Third Party Protocol Third party protocol license Accessories ACT module 24V Plug-in Floating Power Supply Software License (RTU Options) AGA License DNP3+ License IEC 60870-5-101 License
VA00433 V275 V185 V205 V215 V441AF VA00364 V444 V186 V377 V155 FPN1653A V284 V283 V242
97
General Ordering Requirements

1. All orders must list the Model (F75XX) as a main line item. 2. Models F7573 and F7574, (CM200 / CM140 / EM200 / GM3188 conventional radio models) require ordering option V85x (radio type by region). 3. Models F7553 and F7554 (HT750/GP320/GP328 /PRO5150 conventional radio models) require ordering option V95x (radio type by region). 4. Models F7583 and F7584 (XPR4350/DM3400/XiR M8220/DGM4100 VHF MotoTrbo radios models) require ordering option V75x (radio type by region). 5. Entering a frequency is mandatory for all models with radio. 6. The default frame for all models is No I/O Slots Frame (CPU and PS slots only). To change to 2, 3, 5, 7 or 8 I/O slots, add the required Frame option to the order (V102, V103, V104, V105, V107 or V108). 7. A frame with 2 I/O slots only fits the Small Metal Chassis option (V229). 8. Installation on 19" rack requires ordering 19" metal back and brackets options (V120 &V051). 9. For installation, when a radio and/or battery and/or accessory are required with 8 I/O slots, V269 metal chassis is required. To install V269 on the 19" rack option, the 19 metal bracket option V051 is required. 10. The Default Power Supply in all models excluding F7510 (expansion frame) is DC 10.8-15.5 V (12 V DC PS), to change the power supply type, add the required PS option. 11. The default CPU module for all models is CPU 3640 (except for MotoTrbo models F7573 / F7574 and Expansion Frame model F7510). To change to CPU 3680 add V448. 12. I/O expansion requires CPU 3640 or CPU 3680. 13. Model with conventional radio or analog trunked radio are provided with plug-in radio modem installed in the CPU module. 14. Models with radio and orders that include battery option or accessories option (such as RS-485 Junction Box) must be ordered with metal chassis or housing options (mandatory).
98
15. Model F7510 (I/O Expansion Frame) includes an expansion module (expansion CPU), expansion power supply and expansion power cable. To change the power supply type, add the required PS option to the order. 16. The expansion LAN switch occupies an I/O module slot. It is provided with a 60 cm LAN cable. 17. To connect a single expansion frame (for an RTU with up to 16 I/O module slots), use a crossed LAN cable (3 meter length).
99
ACE3600 Installation Guidelines

The ACE3600 RTU is shipped from the factory with the modules and plug-in ports assembled. The RTU frame is ready for mounting directly on a wall or in a customers enclosure. The 8 I/O frame can be installed on a 19" rack. Note: For specific installation instructions, please refer to the ACE3600 Owners manual.
Dimensions
Frame Dimensions:
No I/O slots - PS and CPU modules only, wall mount 117 W x 209 H x 198 D mm (4.61" x 5. 30" x 7.80"), 0.95 Kg (2.1 lb) 2 I/O slots - PS, CPU and 2 I/O modules, wall mount, 194 W x 244 H x 198 D mm (7.64" x 9.61" x 7,80"), Approx. 1.6 Kg (3.56 lb) 3 I/O slots - PS, CPU and up to 3 I/O modules, wall mount 234 W x 244 H x 198 D mm (9.21"x 9.61" x 7.80"), Approx. 1.9 Kg (4.19 lb) 5 I/O slots - PS, CPU and up to 5 I/O modules, wall mount 314 W x 244 H x 198 D mm (12.36"x 9.61" x 7.80"), Approx. 2.4 Kg (5.3 lb) 7 I/O slots - PS, CPU and up to 7 I/O modules 391 W x 244 H x 198 D mm (15.39" x 9.61" x 7.80"), 3. Kg (6.6 lb) 8 I/O slots - PS , CPU and up to 8 I/O modules, wall mount or 19" rack 435 W x 244 H x 198 D mm (17" x 9.61" x 7.80"), Approx. 3.3 Kg (7.3 lb)
Metal Chassis Dimensions:

Large - for PS, CPU and up to 7 I/O slot frame, two radios and 6.5 or 10 Ah backup battery, wall mount , 448 x 468 mm x 200 D ** mm (17.64"x 18.43" x 7.88") Medium - for PS, CPU and up to 3 I/O slot frame, one radio and 6.5 Ah backup battery, wall mount, 335 W x 355 H x 198 D** mm (17.64"x 18.43" x 7.80") Small - for PS, CPU, 2 I/O slot frame, 1 radio (or 1 accessory box), and 6.5Ah backup battery, wall mount, 264 W x 365 H x 200 D** mm (11.02"x 14.17" x 7.88"*)
**
Depth Including Module panel Depth Including Frame and Module
100
Housing Dimensions:
Large NEM A4/IP66 painted metal - up to 7 I/O slot frame, two radios and 6.5 or 10 Ah, backup battery, 500 W x 500 H x 210 D mm (19.7" x19.7" x 8.26" ) Small NEMA 4/IP66 painted metal - up to 3 I/O slot frame one radio and 6.5 Ah backup, Battery, 380 W x 380 H x 210 D mm (15" x 15" x 8.26")
101
GENERAL SAFETY INFORMATION:

WARNING:
Installation of the ACE3600 should be done only by authorized and qualified service personnel in accordance with the US National Electrical Code. Only UL Listed parts and components will be used for installation. Use UL Listed devices having an environmental rating equal to or better than the enclosure rating to close all unfilled openings. If the installation involves high-voltage connections, technicians must be specifically qualified to handle high voltage. If the I/O connections are powered by a hazardous voltage (>60VDC or >42Vpeak), all inputs should be defined as hazardous and the unit must be installed in a restricted access area for service personnel only. If the I/O connections are powered by a safety extra low voltage (SELV) (<60VDC or <42Vpeak), all inputs should be defined SELV. INSTALLATION CODES This device must be installed according to the latest version of the countrys national electrical codes. For North America, equipment must be installed in accordance to the applicable requirements in the US National Electrical Code and the Canadian Electrical Code. INTERCONNECTION OF UNITS Cables for connecting RS232 and Ethernet Interfaces to the unit must be UL-certified type DP-1 or DP-2. (Note- when residing in a non LPS circuit.) OVERCURRENT PROTECTION A readily accessible Listed branch circuit over current protective device rated 20 A must be incorporated in the building wiring.
102
Mounting the ACE3600 Frame on a Wall

WARNING:
Before drilling holes for mounting the frame, make sure there are no electrical wires installed inside the wall at the holes location.
CAUTION:
If the ACE3600 is subject to high levels of shock or vibration, you must take suitable measures to reduce the acceleration or amplitude. We recommend that you install the ACE3600 on vibration-damping materials (for example, rubber-metal anti-vibration mountings).
Wall Mount Installation

For convenient installation of the ACE3600 RTU on a wall, allow an additional 6 cm (2.4") (in W, H) and 7 cm (2.75") (in D) around the plate. Four holes are provided, one in each corner of the RTU metal chassis, for wall mounting the RTU. The figures below show the dimensions (in mm) of the various frames/metal chassis and the distances between the holes.
448 mm 410 mm
365 mm 340 mm
335 mm 295 mm
264 mm 205 mm
Small Metal Chassis Large Metal Chassis Small/Medium/Large Metal Chassis Installation Dimensions and Screw Holes for Installation
355 mm 330 mm
103
468 mm 443 mm
117 mm 82 mm
195 mm
234 mm
199.6 mm
161 mm
209 mm 124 mm
244 mm
0 I/O Frame
124 mm
2 I/O Frame
244 mm 124 mm
3 I/O Frame
No I/O, 2 I/O and 3 I/O Frame Installation Dimensions and Screw Holes for Installation
314 mm 278.5 mm
391 mm 356.9 mm
244 mm 124 mm
5 I/O Frame
244 mm 124 mm
7 I/O Large (and Redundant) Frame
5 I/O and 7 I/O Frame Installation Dimensions and Screw Holes for Installation
The 8 I/O slots frame (V108), the 8 I/O (expanded 19") metal chassis (V269), and the 19" frame metal back (V120) can be installed on a wall using the brackets that are shipped with these options. The figure below shows the required dimensions (in mm) for installation.
104
465.9 mm
146.1 mm*
88.9 mm*
235 mm
*Additional screws for extra fortification
105
Installing the ACE3600 in a 19" Rack

The 19 Metal Back (V120) and the 19" Metal Chassis (V269) (including the redundant frame) can be installed on 19" racks using the 19" rack brackets option (V051) as depicted in the pictures below.
19 Rack Unit Metal Uprights
106
Metal Uprights
Screws for Hanging
Screws for Reinforcement
107
Housing Installation
For convenient installation of the ACE3600 RTU with the NEMA 4 housing, allow an additional 6 cm (2.4") (in W, H) and 7 cm (2.75") (in D) around the housing. Four mounting brackets are provided, one in each corner of the RTU, for wall mounting the RTU housing (see the figures below). The figures below show the distances between the bracket holes.
17.40" (44.2 cm) 20.86" (53.0 cm)
20.86" (53.0 cm)
17.40" (44.2 cm
Horizontal Bracket Installation Vertical Bracket Installation Large NEMA 4 Housing - Installation Dimensions
12.6" (32.0 cm) 16.2" (41.2 cm)
16.2" (41.2 cm)
12.6" (32.0 cm)
Small NEMA 4 Housing - Installation Dimensions
108
MOUNTING BRACKET
PREINSTALLED (WELDED) ON SOME HOUSING BRANDS
Mounting the NEMA 4 Housing
109
Communications
The ACE3600 (as well as MOSCAD family RTUs) facilitates the establishment of a highly sophisticated hybrid data communication network for SCADA that utilizes a variety of radio and/or line communication links. Radio links may include conventional (VHF, UHF, 800 & 900 MHz), analog trunked, digital trunked, and both analog and digital microwave radio technologies. Line links may include point-to-point, multi-drop, Public Service Telephone Network (PSTN) voice/data via dial-up modems, cellular packet data modems and Local Area Networks (LAN). Multiple data bit rates are available to accommodate the particular need of these links. Lower data speeds are used when the bandwidth of the link is reduced either by their design or by laws in the users country, or when data speed is sacrificed to achieve greater communication range. The higher data speeds typically usable, combined with the optimized-for-radio MDLC data protocol, ensure high network throughput even if the network is spread over a large geographical area. The ACE3600 system network consists of RTUs communicating with one or more computerized control centers and/or with other RTUs. Each control center is connected to the communication network. The system can be relatively simple, comprising several RTUs and one control center. It can be modularly expanded to a more hierarchical system, where several sub-systems (comprising intelligent RTUs and/or sub-centrals controlling their peripheral RTUs) communicate with a central computer. The communication network is flexible, enabling each RTU to communicate with hierarchies above it (RTU-to-central), parallel to it (RTU-to-RTU), under it (another RTU), and also relaying messages through it (when the RTU serves as a communication node). While the communication protocol allows for a complex hierarchical system structure, it does not make it complicated. This is because most of the communication interactions are transparent to the user, except in those cases where the communication is to be defined by the user program ladder application. In such cases, you should perform simple programming operations to configure the required application. Each RTU may be configured to serve as a far-end terminal or as a regional center. The RTU may function as a regional center either by definition or only after loss of communication with the central. It also can act as a communication node (an interconnection point between two or more different links) while performing its other tasks. The RTU network uses the MDLC protocol, which incorporates all seven layers of the OSI model adapted for SCADA. It supports multiple logical channels per physical port, enabling simultaneous central-to-RTU and RTU-to-RTU sessions. It also enables each
110
Communications
RTU to simultaneously run several kinds of communication applications, such as reporting alarms by contention, on-line monitoring, performing diagnostics checks, etc. The MDLC protocol is discussed below.
MDLC Protocol
The MDLC protocol is a Motorola SCADA protocol that is based on the Open System Interconnection (OSI) model recommended by the International Organization for Standardization. MDLC utilizes all seven layers of the OSI model. This protocol is designed for optimum operation in SCADA systems which operate with diverse communication media such as two-way radio, line, LAN, etc. Each RTU, FEP, or ToolBox has all seven layers of the MDLC protocol available to them. The functions of the seven layers are summarized below.
Layer Layer 1: Physical Layer 2: Link Function
This layer caters to communications over conventional radio, trunked radio, data radio, serial data channels, modems, Ethernet or telephone lines. The layer is also responsible for channel access and collision control on shared media. This layer ensures proper communications over a physical link. The layer arranges the data in variable-length frames and attaches addresses, frame sequence numbers, and Cyclic Redundancy Code (CRC) to the frames. This layer is responsible for the establishment of end-to-end communication paths in a network. This is necessary since communications may take place on more than one link and a message may travel through several nodes before reaching the final destination. This layer ensures end-to-end integrity of the information flow between two nodes in the network. This is achieved by remote-end acknowledgement that data has been received completely and passed in the correct order to the next layer. This layer allows the definition of any number of entities capable of conducting simultaneous sessions with an equivalent entity in some remote unit. This enables transparent communications among multiprocessing machines without interference in their applications. This layer structures the information to/from various applications. This layer may also perform format conversion, data authentication, etc. if implemented. This layer interfaces to the various applications such as data transfer, configuration downloading, application software monitoring, remote diagnostics, etc.
Layer 3. Network
Layer 4. Transport
Layer 5. Session
Layer 6. Presentation Layer 7. Application
The MDLC protocol is intended for operation in point-to-multipoint links, such as twoway radio or multidrop wireline, as well as in point-to-point communication networks. The protocol facilitates communications among all sites in the system, including extensive diagnostic messaging. MDLC is transparent and liberates the system engineer
111
Communications
from the technical constraints and complexities of network operations thus allowing the intended application to be the item of focus. MDLC uses a semi-synchronous data format on two-way radio and an asynchronous format on wirelines. It is not correct to refer to message size in byte notation because of the 16-bit architecture; the data may not be sent in asynchronous formatno start and stop bitsbut it is not true synchronous either because there is no single networkprovided clock signal. Instead, each CPU has a clock that is entirely adequate to provide the synchronize signal for data transfer. It is therefore better to refer to MDLC in terms of data words where each word may be variable in length, consist of both header and body components, and contain up to 80 16-bit variables within the body. A physical message may consist of a single word or may consist of a concatenated series of words (packets), each word addressed to one or more destination sites with some or all words requiring subsequent store-&-forward operation by the recipient site(s). The concatenated data words may be any combination of the supported functions, i.e. data upload to the SCADA Manager, error logger data to the STS/ToolBox, etc.
112
Communications
The lower three layers of the MDLC protocol stack are commonly known as Network Services. These layers only are used when communicating with intermediary sites which make it possible to pass any data through the system and not require the total system to know the details of the data. Each layer adds (removes) data to what was received and thereby communicates with equivalent layers in the destination (source) sitesee figure above. RTU-to-RTU communications suppress the Presentation, Session, and Transport layers; all layers are present for SCADA Manager-to-RTU communication and for communications with the STS.
113
Communications
MDLC Data Transfer Methods

Three messaging methods are commonly used by the Motorola RTU: Contention (transmission upon change-of-state; also called burst), Polling (interrogation), and Report-by-Exception. The Contention method has the RTU report upon a change-of-state (COS) of conditions/values without waiting for a poll from the SCADA Manager. The RTU recognizes a COS and reports relevant data to the SCADA Manager or to another site as soon as the shared communication medium becomes available. The RTU will repeat the data message until confirmation of reception is received. The RTU listens to the shared communication medium before sending a message and then uses a slotted channel acquisition method to avoid synchronized message collisions. This is the messaging method most often used by Motorola RTUs because it uses the shared communication medium properly. The Polling (interrogation) method is a periodic activity used to confirm the proper operation of the normally silent RTUs and/or to update the SCADA Manager database at specified intervals or when manually instructed by the operator. The Report-byException method has the RTU report only the conditions/values that have changed since the last poll. The SCADA Manager retains all data conditions and values in a local database for instant use.
114
Communications
Communication Links
The system may support a network comprised of a nearly unlimited number of links. The RTU supports a variety of communication media, protocols and data speeds, as detailed below: Serial RS232 ports, up to 115.2 kbps, supports: Local PC using MDLC (MDLC or User Protocol) RTU to RTU (MDLC) External Data (MAS) radio (MDLC, ModBus RTU, DF1 or user protocol) External Wire-line modem (MDLC, ModBus RTU, DF1 or user protocol) External Dial up modem PSTN or Cellular (MDLC) External Cellular packet data modem (MDLC/PPP) ASTRO Digital Trunk Radio (IV&D) XTL5000/XTS2500 (MDLC/PPP) TETRA MTM700/MTM 800 Radio (MDLC/PPP) Third party PLC/Device (ModBus RTU, DF1 or user protocol) GPS receiver interface
The ACE3600 supports RS232 links to standard modem over PPP on the built-in serial ports and on the plug-in ports. These ports may be connected to an external modem supporting AT commands. RS-485 ports, multi-drop 2-Wire up to 460.8 kb/s, supports: RTU to RTU on multi-drop connection (MDLC). Third party PLC/Device on multi-drop connection (ModBus RTU or User protocol). Ethernet port, up to 100 Mbps, supports: Local PC using MDLC (MDLC over IP or User Protocol on TCP/IP) RTU to RTU (MDLC over IP) Third party Device (MODBUS RTU, DNP 3.0 and User Protocol on TCP/IP) Radio modem port, supports: Conventional radio DPSK 1.2 kbps, FSK 2.4 kbps, DFM 2.4/3.6/4.8 kbps Analog Trunked radio - DPSK 1.2 kbps (MDLC) - See the list below.
RS232 Ports
On ACE3600 CPU modules, Serial Port 1 and Serial Port 2 (SI1 and SI2) are RS232 ports. Additionally up to two RS232 Plug-in ports can be installed on the CPU module (on PI1 and PI2 plug-in ports). The RS232 ports can be configured to Async or Sync operation mode and they enable local connection of a PC with the ACE36000 STS to the RTU, direct connection of another RTU, connection of modems, digital radios, data radios, third party PLCs and other devices. In addition, the ACE3600 supports RS232 links to standard modem over PPP on the built-in serial ports and on the plug-in ports. These ports may be connected to an external modem supporting AT commands (refer to
115
Communications
IP Ports). The RS232 ports may operate at data speeds up to 115.2 kbps (depending on the total wire length).
RS485 Ports
On ACE CPU modules, Serial Port 1 (SI1) can be configured as RS485 port. Additionally up to two RS485 Plug-in ports can be installed on the CPU module (on PI1 and PI2 plugin ports). The RS485 ports permits up to 32 2-wire RS485 devices to be parallel-connected (multidrop) onto one pair of wires for the exchange of data. A typical ACE3600 use for RS485 is the interconnection among multiple RTUs in the same site. RS485 is also used to connect various devices in the site to the RTU using the ModBus protocol or a user defined protocol. The RS485 Connection Box is available to make this interconnection; or the installer may make the cables by using the small handset-size connectors commonly found on modular telephones. The RS485 port may operate at data speeds up to 460 kbps (depending on the total wire length). The RS485 specification calls for the circuitry to be capable of communicating at 10 Mbit/s for 40 feet (12 meters). At 4000 feet (1200 meters), maximum cable length, the data rate is reduced to 100 Kbit/s. There are other factors involved including the network configuration; wire characteristics, the device used, biasing resistors and termination resistors (see later) that can influence the data rate. One of the most frequently asked questions and one of the most difficult to answer is the speed/distance/number of drops tradeoff. Different studies in the industry have given some of the following (often conflicting) results, however the table below provides a conservative estimate based on the assumption of a daisy chain topology with no stubs.
Data Rate (Kbps) Distance Distance (feet) (meters)
<100 200 300 400 500*
4000 2000 1000 800 700
1200 600 300 240 210
The following factors affect how far one can reliably transmit at a given data rate: Cable length: At a given frequency, the signal is attenuated by the cable as a function of length. Cable construction: Cat 5 24AWG twisted pair is a very common cable type used for RS485 systems. Adding shielding to the cable enhances noise immunity, and thereby increases the data rate for a given distance.
116
Communications
Cable characteristic impedance: Distributed capacitance and inductance slows edges, reducing noise margin and compromising the eye pattern. Distributed resistance attenuates the signal level directly. Termination: A long cable can act like a transmission line. Terminating the cable with its characteristic impedance reduces reflections and increases the achievable data rate. Although normally required at higher transmission frequencies, it is good practice to terminate the cable runs with a resistor equal to the characteristic impedance of the cable. This reduces the reflection of a signal when it reaches the end of the cable. Avoid adding a termination resistor at other locations as this can overload the driver and reduce the reliability of the data transfer. The distance can be increased by the use of repeaters.
117
Communications
IP Ports (MDLC over IP)

ACE3600 RTUs can use IP (Internet Protocol) technology to interface to advanced radio infrastructure (e.g. TETRA or GPRS) and to standard private IP networks. Most benefits of the MDLC protocol are preserved. MDLC and IP networks can be integrated in the same system, as networking properties are preserved. MDLC applications need not be modified as the lower layers of the protocol support IP. MDLC packets to be transmitted are enveloped inside UDP/IP datagrams and sent between remote RTUs or between an IP Gateway and an RTU over UDP port 2002. The UDP Port number is configurable for each port. The ACE3600 RTU can have several MDLC over IP ports, each identified by its own link ID: MDLC over RS232 PPP ports, and MDLC over LAN/Ethernet ports that can have static or DHCP addressing modes. In some cases it is required that an MDLC over IP port have more than one link ID. Each MDLC over IP port has its own unique link ID. An IP address identifies each port, and is set by the user in a static LAN port (fixed IP address). For DHCP and PPP this address is learned automatically (dynamic IP address), and the user does not need to define it. A PC running STS can be connected to one of the RTU ports, to one of the serial ports of the IP Gateway, FEP or to the Ethernet. An MDLC over IP port can be used in one of four ways: 1. ACE3600 RTU port connected to a packet data radio/modem over PPP (Point to Point Protocol). The RTU can act as a remote unit or as a front end serving a SCADA control center (over PLC or user port). 2. ACE3600 RTU port connected to a LAN through one of its on-board or plug-in Ethernet port. A direct LAN connection exists between the Ethernet port and the radio infrastructure. The RTU an act as a remote unit or as a front-end, serving a SCADA center. This port can be configured as static LAN or as DHCP LAN. 3. ACE3600 FEP connected to LAN. An FEP serves as a front-end for a TCP/IP based SCADA central and enables it to communicate with remote RTUs. The FEP can use MODBUS over RS232 or any other propriety protocol over RS232 or LAN to communicate with the SCADA. If a LAN is used, the C Toolkit socket (user protocol over IP) functions provide that functionality. The ACE36000 RTU can use a direct LAN port connection with other RTUs over the radio infrastructure. It can also be connected with a packet data modem/radio over PPP. For information on the C Toolkit socket functions, see the ACE3600 RTU C Toolkit User Guide.
118
Communications
4. IP Gateway connected to LAN. An IP Gateway (IPGW) serves as a front-end for a TCP/IP-based SCADA central and enables it to communicate with remote RTUs. The IPGW uses a direct LAN connection to the radio infrastructure. It cannot be connected with a packet IP Ports (IP LAN/WAN ports) data modem/radio over PPP. For this purpose an RTU (with packet data radio/modem) is needed with RS232/RS485 to connect them. Note: Although the ACE3600 RTU has Ethernet ports, it does not have the IP Gateway functionality. Auto-Negotiation Note: The ACE3600 Ethernet port performs one Auto-Negotiation procedure upon startup. It is recommended to configure the Ethernet port of the device connected to the ACE3600 Ethernet port (e.g. switch, etc.) to Auto-Negotiation mode. If the Auto-Negotiation fails, the ACE3600 Ethernet port default is 10 Mbps half-duplex.
Broadcast and Setcalls

Most wireless packet data networks do no support broadcast IP. When transmitting a group call (Site 0), a separate frame is transmitted to each site specified in the IP Conversion Table over UDP/IP. If broadcast IP exists, then this IP can be specified in the IP Conversion Table under Site 0 with the proper link ID (port). Sending to Site 0 with that link ID will transmit a single message, through that port, to all RTUs over UDP/IP using that address. Note that in ASTRO IV&D, GPRS, TETRA and most wireless media, this is not supported, so a separate message is transmitted to each site. It is preferable to transmit to each site separately, rather than send this setcall, with a delay around 100-300 milliseconds between one transmission and another.
New Features for MDLC over IP in ACE3600

The following features are available in ACE3600 that are not available in legacy MOSCAD RTUs and IP Gateway. These features apply to Ethernet static IP address, Ethernet DHCP, and RS232 PPP port types. Multiple IP Ports The user can specify more than one MDLC over IP port in ACE3600. The IP Conversion Table includes a link ID column which enables the same ACE3600 site ID to appear several times, with a different link ID and the same IP address. In some cases, it is necessary to have more than one link ID per MDLC over IP port. For example, if RTU 1 has a single Ethernet MDLC over IP port, and it communicates with another RTU that has two (or more) MDLC over IP ports LINE1 and LINE2. In this case RTU 1 must have its MDLC over IP port assigned with two link IDs: LINE1 and LINE2. This will enable direct communication to RTU 2 LINE1 port or to RTU 2 LINE2 port.
119
Communications
IP Conversion Table Enhancements An IP conversion table can be assigned to each RTU/FEP. It maps each site ID+link ID (port) to an IP address. The link ID column supports multiple MDLC over IP ports per RTU. Each link ID uniquely identifies the port/IP connection of that RTU. The table enables the MDLC over IP port to transmit MDLC packet to its destination based upon its site ID and link ID (port). The enhanced IP conversion table also supports the user of a host name instead of a numeric IPv4 address (IP address). In order to use host names, the operator must support this in the network DNS Server, and the user must specify them in the appropriate port configuration. The IP conversion table is dynamic, which means its numeric addresses are automatically learned/updated in runtime, for example when a new RTU is added, or an existing one changes its addresses. In some cases, such as dynamic addresses of RTUs, there is no need to download that table to FEP, simply because RTUs addresses are updated when they transmit to the FEP. In this case, it is recommended that the user application perform these transmissions periodically. Note: The IP conversion table learns only numeric IP addresses. Host names of other RTUs are not learned. Using Host Names Sometime it is necessary to refer to an RTU or FEP using a host name rather than a numeric IP addresses. Any MDLC over IP port (Ethernet or RS232/PPP) has that option, however it is the responsibility of the user and network to make sure this is supported. In the IP conversion table, it is possible to set a host name instead of a numeric IP address for a specific site + link ID. The link ID, for example LINE5, identifies the port/IP connection of that site. To enable this, the port needs the list of DNS servers for that MDLC over IP port. DNS list can be automatically learned. The list must be set only for an Ethernet port configured as Static IP address mode. An Ethernet port configured as DHCP or an RS232 port configured as PPP automatically learns this list from the network, and the user does not need to set them. Note: Some PPP connected radios such as TETRA and ASTRO IV&D radios do not provide DNS information. These systems usually do not use host names either, but if necessary, the user can set the list of DNS Servers in the port configuration. The FQDN option for an Ethernet port configured as DHCP updates the DNS servers when a new IP address is allocated to it by DHCP. The user need only set the full host name of that port. A warning is logged if the router/DHCP server does not support this option.
120
Communications
Configuring NTP Servers An Ethernet or RS232 PPP port can be configured for NTP protocol (NTP is UDP port number 123.) In this case, the RTU will retrieve its time from a set of NTP servers specified by the user. The clock offset between the RTU and these servers depends on network delays, and may be up to 100 milliseconds in some wireless media. The clock offset on LAN in the same Ethernet network is approximately 1 millisecond. Note: It is possible to define an NTP server with a full host name (e.g. www.mysite.com). To do so, the user must set DNS servers for this port, either statically, or from a DHCP server or PPP modem. User Protocol over IP Both Ethernet and PPP ports provide an interface for a user application written in the C Toolkit using MOSCAD_socket() functions, also known as User protocol over IP. An MDLC over IP port can serve a user application at the same time as it serves MDLC which is built in the socket API. MDLC takes one logical UDP port number (2002 by default); other applications can use other TCP or UDP port numbers. For more information on the C Toolkit socket functions, see the ACE3600 RTU C Toolkit User Guide. Dynamic IP Address Many wireless networks do not allocate a fixed IP address to a PPP modem (such as the GPRS network). For the FEP to communicate with the RTU it must know its address or host name. Since these networks do not provide a name for each modem, there is no option of setting them in the FEP beforehand. In this case, the FEP should not be assigned an IP conversion table with that link ID (port). The RTUs should be associated with a table which has the FEPs IP address. If the network operator assigns a host name to the FEP instead of a numeric address, this can be set in the IP conversion table. When the RTU detects that its modem is connected, it will notify this address, the FEP, of its new IP address, thus updating its table in runtime. Since this process does not guarantee that the FEP will be updated, it is highly recommended that user application periodically send a message to the FEP. For example, if the user application expects an interrogation every two minutes from the FEP, and it has not received that, it will send a message to the FEP. This will update the RTU address in the FEP. MDLC over IP Port Routing In the example mentioned in Dynamic IP Address above, for RTU-to-RTU (modem to modem) communication, set Enable routing of MDLC over IP port parameter in the FEP. Then assign to the RTUs an IP conversion table which list the RTUs site IDs as having the FEP IP address.
121
Communications
When one RTU transmits to another, the transmission will go through the FEP which will route it to its destination, without the need of a network configuration. Note: This feature can also be used in an FEP connected to the CEN of ASTRO IV&D, where it is required for one RTU connected to a radio to communicate with another RTU.
MDLC over IP PPP Connections

The ACE3600 RTU can include up to four RS232/PPP ports - two on-board (SI1 and SI2) and two plug-in RS232 ports (PI1 and PI2.) Each port may be PPP connected to a packet data radio/modem over PPP and have its own link ID. Several RS232 over PPP connections are supported: MDLC via IDEN modem (e.g. iM1000, iM1500) MDLC via ASTRO IV&D digital radio (e.g. XTL5000) MDLC via Standard modem, (e.g. GPRS data modem.) See MDLC over Standard Modem Setup for configuration details. A modem configuration file must be attached to the site and downloaded to the RTU when using this connection. MDLC via Tetra radio. This is similar to Standard modem. See MDLC over Tetra Setup for configuration details. When using a Motorola radio (e.g. MTM800), no modem configuration file needs to be downloaded. MDLC via Null modem. This is suitable for direct cable connections over PPP with devices such as Terminal Servers, wireless modem, etc. Depending on the modem used you may or may not need to download a modem configuration file. MDLC over ASTRO IV&D. See MDLC over ASTRO IV&D for configuration details. When using the ASTRO IV&D (Integrated Voice & Data) connection, no modem configuration file needs to be downloaded.
In order for a variety of modems to be used, a modem configuration file is downloaded to a specific port configured for MDLC over IP. The modem/radio can also be diagnosed using AT commands specified in that file. For MDLC over IP this feature is applicable to all connections: Standard Modem, Null Modem, Tetra, iDEN, and ASTRO IV&D. Note: The same modem configuration file can be used when configuring a port for MDLC over IP or when configuring the port for dialup. For details, see Modem Configuration File below. Note that for iDEN, Tetra and ASTRO IV&D the modem configuration is not required, since the firmware already has these commands built in.
MDLC over IP/LAN Connections

The ACE3600 RTU can include one on-board 10/100 Ethernet BaseT port (ETH1) and up to two plug-in 10/100 BaseT ports (PI1 and PI2.) Each Ethernet port has its own link ID and can be connected to the same or to a different network mask. An Ethernet (LAN) port can be configured in one of several modes:
122
Communications
Static IP address mode Dynamic (DHCP)
With static IP address mode, the user is required to set the link ID, IP address, subnet mask and default gateway. If DNS or NTP servers are required, these must be defined as well. DNS servers are only required if this port is to be accessed via a host name rather than a numeric IP address. In this case the operator assigns a host domain name to the FEP or RTU. The IP conversion table must include the domain name well. If an NTP server is to be used to obtain the time, the numeric IP address or domain name of the NTP server must be defined. In DHCP address mode, the user is only required to set the link ID for this port. If DNS servers are required there is no need to set them, since they are learned from the network. If NTP servers are required, the user must set them since they are not learned from the network. As an option, user can set a full host domain name for an Ethernet port that is configured as a dynamic DHCP client. Each port should be set with a different name. This option allows the network DNS servers to be updated when the DHCP server changes its IP address, keeping its name up to date. This is called FQDN and is not always supported by the DHCP server (in this case a warning is logged.)
MDLC over IP Site Paging

A paging mechanism is available in each site (peer) to make MDLC over IP more reliable. (This feature is the same as in Toolbox V9.54 and MOSCAD V9.25.) Paging a site before transmitting MDLC data to it over IP, guarantees that the site is reachable. This is necessary because MDLC over IP does not have a confirmed type of link in which the peer acknowledges received packets (as opposed to other types of MDLC ports). It relies on the radio to have a link layer that will guarantee a best effort delivery, and thus avoids overloading the channel with excessive traffic. A site is paged by sending it a poll request and awaiting a poll reply. During this time, the RTU can continue to transmit to other sites (and receive transmission from other sites). If the site responds with a poll reply, or any other MDLC data, it is considered as reachable and all pending transmissions are sent to it immediately. Further transmissions will be sent to it as well without paging until the site is declared as failed. If an ICMP Destination Unreachable message is received or if the site does not respond to paging for a configurable poll interval, it will be polled again for a maximum number of polls. If there is still no response, the site is considered to be failed, and the network layer is notified so any pending transmissions can be redirected to an alternative route. If subsequent transmissions are to be sent to the site through an MDLC over IP port, paging will be performed again before actual transmission takes place. The Site Paging mechanism can be enabled or disabled.
123
Communications
MDLC over LAN/Ethernet

The ACE3600 RTU can communicate over Ethernet media, via the onboard Ethernet port or 10/100BT plug-in ports. The figure below illustrates an example of a SCADA system with IP Gateway and ACE3600 RTUs connected to Ethernet LAN:
SCADA Central
STS Ethernet 1
LINE 1 RS-232 STS IP Gateway
IP Network
Ethernet 2
Ethernet 3 10BaseT 10BaseT RTU-IP3 on Ethernet Plug-in Port
10BaseT RTU-IP1 RS-232 STS
RTU-IP2 on Ethernet on-board Port
With SCADA systems the ACE3600 RTU can be connected to Ethernet/LAN as an FEP (FIU) for a SCADA, and an RTU. It communicates with MDLC over IP between FEP/IP Gateway and RTU. The IP Gateway unique functionality provides an API over TCP/IP API, for the SCADA PC. It provides the SCADA with the current values of the RTU tables and with the events (Bursts) that are associated with each entity. The ACE3600 does not have that functionality built-in and requires an IP Gateway. Unlike IP Gateway, ACE3600 can be connected to several Ethernet connections. They can reside on the same or on different network subnet masks, and are distinguished from one another by a link name.
124
Communications
A number of connection methods are available when configuring an Ethernet-based RTU: 1. Static IP address The user sets the IP address within the configuration of the device in the STS. To use this method, follow the instructions for configuring an RTU in the Operation chapter in the ACE3600 STS User Guide. All DHCP parameters will remain at default values. 2. DHCP-supplied reserved IP address For every ACE3600 RTU, an IP address will be reserved within the DHCP server. The link between the RTU and the reservation will be based on unique ID. In the DHCP Server, set the unique ID. The default unique is the MAC address. In the DHCP server, define a reservation for a specific RTU based on its MAC address. 3. DHCP-supplied dynamic IP address A dynamic IP address is distributed from the DHCP server to the ACE3600 RTUs. The IP address of each ACE device is unpredictable. In this case you will need a DNS server that will resolve the link between the IP address and the RTU. You will have to supply a name for each RTU. This name will be updated within the DNS server along with IP address of the RTU. Within IP conversion table of ACE3600 RTU you will use this DNS name instead of IP address. In order to comply with IP networks standards, all configuration methods described in this chapter are based on standard procedures used in IP networks.
MDLC over ASTRO IV&D

With SCADA systems, ACE3600 RTUs can be connected to an ASTRO IV&D radio. The ASTRO infrastructure (R6.4 or higher) and radio must support integrated voice and data (named IV&D). This is relevant to Motorola subscriber data radios such as the XTL5000 mobile and XTS2500 portable. The connection to ASTRO IV&D can be made via LAN or via radio. The LAN is called a CEN (Customer Enterprise Network). An IP Gateway or RTU with an Ethernet port can be connected to the CEN. On the other end, an RTU can be connected to an ASTRO IV&D radio via an RS232 data cable. Note that a specific codeplug which supports the data option must be used when programming them. In the figure below, the SCADA central and IP Gateway are connected via LAN to a Customer Enterprise Network (CEN). The CEN is connected via a border router gateway to the ASTRO IV&D infrastructure. An RTU, running MDLC over IP protocol over PPP, is connected via XTL5000 radio using an RS232 data cable. A unique IP address is assigned by the GPRS Gateway Support Node (GGSN) to each RTU according to its radio individual unit ID (UID), such that when a frame is transmitted from the CEN to that IP address, the Packet Data Router (PDR) and Radio Network Gateway (RNG) transmit it to the appropriate radio.
125
Communications
Unlike other infrastructures (such as iDEN and TETRA), this IP address and radio unit ID cannot be retrieved for diagnostics from the radio. Instead a dummy IP Address is provided by the radio as it is configured using the CPS (Codeplug Programming Software).
SCADA Central Ethernet LINE 1 RS-232 STS IP Gateway Customer Enterprise Network
ASTRO IV&D infrastructure
GGSN PDR
Base Station
RNG
LINE 1
XTL5000 Radio RS-232 STS RTU-A
XTL5000 Radio RTU-B
A PC running STS can be connected directly to an RTU, directly to a radio, or it can operate remotely over the CEN. For an RTU or PC to communicate over the air using an ASTRO IV&D radio, the radio must be context activated, or registered for data, in addition to the PPP connection over RS232 interface. The RTU uses SNMP protocol and sets a value in a MIB variable defined for this radio. When this succeeds, the radio configuration is completed, and the radio (using the IP address provided periodically by the GGSN in the infrastructure) is able to receive and transmit data. If the context activation fails or is deactivated, the RTU causes the radio to restart (power itself off and on.) Once the radio has been context activated, an RTU (or PC) can transmit IP frames over the air to the PDR which routes them to the GGSN and CEN.
126
Communications
Certain configuration steps are performed on the radio itself using the CPS and in the infrastructure using the UCM tool. See the relevant radio documentation for more information. There are two types of hardware interface between the RTU and the radio: For a mobile radio such as the XTL5000, the interface is comprised of a radio data cable over RS232. Note: A PC needs a tool called Data Link Manager (DLM) in order to communicate over the air NOTE: ASTRO IV&D does not support group calls (RTU-to-RTU broadcasts). To send a frame to a group of sites, the application should send to each site individually, leaving a short wait time between each transmission (300-1000 milliseconds depending upon the communication used.) Sending frames from one RTU to another when both are connected to radios may not be reliable, because of the ASTRO IV&Ds limited resources. It is recommended to have an RTU connected to LAN (CEN) that will route the information between them.
MDLC over MotoTrbo

With SCADA systems, ACE3600 RTUs and ACE IP Gateways can be connected to a MotoTrbo radio in digital mode, to use MDLC over IP communication via the MotoTrbo digital mode radio system. The MotoTrbo radio is connected directly (not via hub) to one of the RTU/IPGWs USB host ports. The port connection between the RTU and the radio is a USB host running IP over RNDIS (Microsoft Remote NDIS protocol version Revision 1.1.) Note: The DHCP protocol is also used for obtaining IP address from the radio. This IP address is internal within the USB connection and does not reflect the actual IP address over the air. The STS (PC) may be connected directly (locally) to the radio via a single unit, by specifying the radios IP address in the Communication Setup. For example, if radios network ID is 12 and the radio ID is 10, specify 13.0.0.10 (13 because to access the unit specify the network ID 12 plus 1). The STS should not be connected remotely to other units connected to the MotoTrbo radio network due to performance issues. The user may perform STS operations such as loggers, download, hardware test, monitor, and set/ get date & time (effective data throughput ~800 bps). MDLC time synchronization is not recommended, because of the long delays added by the radio/repeater. Network Time Protocol (NTP) provides better time synchronization accuracy, ~200 ms accuracy with a repeater. By default, MDLC time synchronization is disabled, but it can be enabled in the ports advanced physical parameters. In single repeater or IP site connect topologies, the unit attached to the MotoTrbo radio may initiate or receive MDLC group calls over a single link ID. For example: If a radio network group ID=225, set site ID 0 to IP address 225.0.0.1. Note: Adding this feature
127
Communications
requires changes in the CPS of the radio (adding a digital Call to the contact list, and referring to it in the RX Group list; marking the forward to PC field in the network folder.) If using MDLC time synchronization, it is important to set a group IP address. For example if using Digital Call ID 1, set it to 225.0.0.1 in the STS.) Note: There may be delays, depending on the topology used. IMPORTANT: For sending group calls, the default group IP address can be configured in the advanced link layer of the HU1/HU2 port tab, or in the IP conversion table for site ID 0 and the proper link ID. This is the only way a setcall can be delivered by MotoTRBO in digital mode. Each RTU or FEP has a fixed IP address. This address is derived from the radio to which it is connected. For example: If the radio ID=1 and the network ID=12, the address is 13.0.0.1. The network mask is always 255.255.255.0. The unit learns the local radio IP address dynamically. For example: If 199.19.10.1 is configured in the radio CPS, this is not the real IP address transmitted over the air. The real IP is 13.0.0.1. Unlike other infrastructures such as iDEN and TETRA, the radios IP address and radio unit ID cannot be retrieved for diagnostics from the radio. Instead a dummy IP Address is provided by the radio as configured in its CPS. The general steps of the MDLC over MotoTrbo Setup are like those of MDLC over IP Setup. There is no need to download a modem configuration file, just an IP conversion table. Note that the data throughput over the MotoTrbo system is up to 900 bps (less if the same frequency/slot is shared for voice and data).
MDLC over iDEN

ACE3600 RTUs can be connected to iDEN iM1000/iM1500 modems (OEM version 35.01.00) to communicate using RS232/PPP port on iDEN infrastructure to the IP network. Since iDEN infrastructure connects to Local Area Networks (LAN) as well, a LAN-connected IP Gateway or FEP can communicate directly with these RTUs over iDEN infrastructure. The iM1000/iM1500 is configured to operate works in various modes, including: Packet Data (PD) Circuit Data (CD) Packet Data over Circuit Data (PD over CD)
MDLC over iDEN, which uses IP technology, deals only with the first mode (PD). The other two modes can only be used with an external dialup port in the RTU, and do not
128
Communications
support direct communication with another RTU/IP Gateway having an MDLC over IP port. Therefore they are not relevant to MDLC over IP topic. In the figure below, the SCADA central and IP Gateway are connected via LAN to iDEN infrastructure. Each RTU has an iM1000 or iM1500 modem connected to RS232/PPP Port. A unique IP address is assigned to each RTU according to its modems identifier. All communication between RTUs and the IP Gateway involves sending datagrams in packets over the network (IP). A PC running ACE3600 STS can be connected directly to an RTU or operate remotely over IP.
SCADA Central Ethernet LINE 1 RS-232 STS IP Gateway IP Routing Net
iDEN infrastructure
Home Agent Interface Router Mobile Data Gateway
Base Station
LINE 1
iDEN iM1000 Packet Data modem STS RS-232 RTU-A
iDEN iM1000 Packet Data modem RTU-B
MDLC over Tetra

ACE3600 RTUs can be connected to a Tetra radio. Tetra infrastructure and radio should support packet data. The connection to Tetra can be made via LAN or via radio. An IP Gateway or an RTU with and Ethernet plug-in or on-board port can be connected to a LAN. In Tetra terms, an RTU that is connected through LAN is called a LAN RTU. An RTU that is connected to
129
Communications
a radio is called a PEI (Peripheral Interface) RTU. A PEI RTU is connected to a radio through RS232 using standard PPP (Point to Point Protocol). In the figure below, the SCADA central and IP Gateway are connected via LAN to Tetra infrastructure. Each RTU has an MTM700 or MTM800 radio connected to its MDLC over IP Port using PPP. A unique IP address is assigned to each RTU according to its radios identifier (SSI). All communication between RTUs and the IP Gateway involve sending datagrams in packets over the Internet (IP). A PC running ACE3600 STS can be connected directly to an RTU or operate remotely over IP.
SCADA Central Ethernet LINE 1 RS-232 STS IP Gateway IP Routing Net
Tetra Infrastructure SW MI
LINE 1
Tetra MTP700 radio STS RS-232 RTU-A
Tetra MTP700 radio RTU-B
The STS can communicate with remote RTUs over IP using the Tetra infrastructure. The PC running the STS is connected to the Tetra radio (e.g. MTH500 radio) or to the RTU. For this purpose, the PC should have a Tetra PD installation (as specified in the CPS user manual). After setting up the connection, the user should run the STS Communication Setup utility, select Ethernet port and specify in a focal point RTU/IP Gateway IP Address under Local Site IP Address. It is important to note that RTU to RTU communication is routed through the infrastructure LAN system and not directly.
130
Communications
Note that a paging mechanism to each site (peer) in IP conversion table makes MDLC over IP more reliable. For details, see MDLC over IP Site Paging. Tetra does not support group calls (RTU-to-RTU broadcasts). To send a frame to a group of sites, the application should send to each site individually, leaving a short wait time between each transmission (about 300 milliseconds).
131
Communications
MDLC over IP - Standard Modem

To avoid system setup for each modem/radio which supports packet data, a general concept has been introduced for, whereby IP can connect to any modem or radio supporting packet data. A standard modem supporting packet data is a modem which requires an AT command set to configure and PPP to initiate. It can connect to a PC using Microsoft Standard Modem and RAS setup. A modem configuration file can be downloaded into the RTU specifying the exact command set needed by the modem/radio. A default AT command set is used in case this file is not downloaded. The same concept is used for circuit data modem over dial port. For information of downloading modem configuration files, refer to ACE3600 STS Advanced Features Manual. Connection to Standard modem is made using RS232 PPP over the operator infrastructure. Since the operator infrastructure connects to LAN as well, a LANconnected RTU can communicate directly with these RTUs over that infrastructure, if enabled by the operator. Some modems have an internal fixed IP address for PPP connection. If so, only one modem of the same vendor can be connected to RTU, since they all have the same IP address. Other modems such as Motorola g18 do not have an internal IP address; in this case several MDLC over IP ports can be configured to connect with them. To verify if more than one modem can be used, try to connect two modems and see if you get an error message: IP Address in use by other ports.
MDLC over Null Modem

The RTU can connect to any device using PPP. This connection is made using PPP and is basically the same as MDLC over Standard modem. When the RTU is powered up, it sends a client string and expects a client-server response. Only when it gets that response will it initiate PPP and poll for CD signal (carrier detect). CD is constantly being polled, and if it drops, PPP is disconnected. The user can opt to ignore CD using Advanced Link Layer parameters in the site configuration. In this case, PPP is initiated upon power up. When connected, CD is polled in order to stay connected. If it drops, then PPP is reconnected. By default, the RTU acts as a Windows Null modem connection. It sends a client string and expects a client-server response before initiating PPP. The user can override this behavior by downloading a modem configuration file.
132
Communications
MDLC over GPRS Network

An RTU can be connected to GPRS (GSM) network through a LAN or through a radio. An IP Gateway or an RTU with an Ethernet port can be connected to the LAN. In the figure below, the SCADA central and IP Gateway are connected via LAN to the GPRS infrastructure. Each RTU has a G18 GPRS/GSM modem connected to its MDLC over IP Port using PPP. A unique IP address is assigned to each RTU according to its modem identifier (IMSI). All communication between the RTUs and the IP Gateway involves sending datagrams in packets. The GPRS infrastructure routes those packets directly between two RTUs, or between IP Gateway and an RTU. A PC running STS can be connected directly to an RTU or operate remotely over IP.
SCADA Central Ethernet IP Gateway RTU RSlink1 g18 GPRS Packet Data modem
GPRS infrastructure
LINE 1
g18 GPRS Packet Data modem STS RS-232 RTU-A
g18 GPRS Packet Data modem RTU-B
A single GPRS modem can be connected to an RTU. Other ports can be connected to other GSM modems using dialup ports. It is recommended that the operator provides an APN (Access Point Name) for a fixed IP address and enable one modem to communicate with another over UDP port 2002. However it is not always possible, so the following steps can be made:
133
Communications
1. Assign FEP need to have a fixed IP or host name. Make sure operator support UDP port 2002 from modem to FEP and vice versa. 2. Assign an IP conversion Table for RTUs having that FEP IP address or host name. 3. In application of RTUs transmit periodically to FEP, so it learns the recent address. Recommended time every 2 minutes. A better example is to wait for a timeout and if not getting anything from FEP send it a message. Since there is no fixed IP addresses one modem cannot communicate with another. If this is required, the FEP can be used to route information between modems as follows: 1. Assign an IP conversion Table for RTUs that has the FEP Site ID + Link ID and IP address, along with all other relevant sites it needs to communicate over that GPRS Link ID. 2. In FEP enable the Enable routing of MDLC over IP port parameter for that Link ID. GPRS does not support group calls (RTU-to-RTU broadcasts). To send a frame to a group of sites, the application should send to each site individually, leaving a short wait time between each transmission (about 300 milliseconds). Configuring an RTU to operate over GPRS is the same as configuring MDLC over IP for the Standard modem connection. If a modem configuration file is used (e.g. G18.stm), this too must be downloaded to the appropriate RTU port. Note that before downloading the modem configuration file for GPRS, you need to change its APN according to your operator instructions. The APN (Access Point Name) is an address such as intranet.motorola.com. The APN defines the security and capabilities set by your provider for your SIM cards. Note: Each SIM Card has unique identifiers for a GPRS/GSM modem. Placing a given SIM card on different modems causes the same settings to be retrieved from infrastructure (phone number, IP Address etc.) regardless of the modem. Use the STS Add-Ons Manager and Downloader to select the modem configuration file for the specified port and download the G18.stm file.
134
Communications
IP Conversion Tables
The IP conversion table is created in the ACE3600 STS using the IP Conversion Table Manager. Note that unlike the network configuration, there is no default, and any IP conversion tables must be created manually. The IP conversion table maps sites in the system (site ID+link ID) to IP addresses or host names. Each site ID/link ID pair can have one unique entry in the table, though an IP address can appear in more than one row. A site ID of 0 is reserved for a group call. In RS232/PPP and Ethernet DHCP, the IP address is read from the network once it is connected to the RTU. In ASTRO IV&D, this is not the real IP address set by the infrastructure; rather, it is a dummy address configured in the radio via the CPS Mobile Computer IP address which is (by default 192.168.128.2). In the IP conversion table do not specify this address, but the actual IP address assigned by the infrastructure operator. The ACE3600 IP conversion table format includes a link ID column which allows more than one port in the same site to be connected to LAN or to PPP. Any legacy MOSCAD RTU or IP Gateway in the network must defined using its own Toolbox IP Conversion Table utility.
Control Center CEN LAN FEP 100 LINE 2 LINE 1 FEP 10.5.1.xx
Packet Data Network
192.5.1.xx
Subscriber Radio 1 LINE 1 PEI RTU-A LINE 2 LAN 155.9.1.xx PPP/RS-232
Subscriber Radio 2 LINE 1 PPP/RS-232
PEI RTU-B LINE 2
135
Communications
In the example above, two sets of IP conversion tables should be created and the FEPs Table should be assigned to the RTUs: The following IP Conversion Table should be loaded to the RTUs:
Site ID 100 100 Link ID LINE1 LINE2 IP Address or Host name 10.5.1.160 155.9.1.17
The following IP Conversion Table should be loaded to the FEP:

Site ID 1 1 2 2 Link ID LINE1 LINE2 LINE1 LINE2 IP Address or Host name 192.5.1.161 155.9.1.18 192.5.1.162 155.9.1.19
As another example the IP conversion table can be set with names rather than numeric IPv4 addresses. In this case make sure these names are the full host names set by your network administrator. Make sure the DNS Servers are either learned (DHCP or PPP) or set them manually in port configuration (Static LAN). In this example assume the operator has assigned two names for the FEP: FEP1.moto.com for port LINE1 FEP2.moto.com for port LINE2. The following IP Conversion Table should be loaded to the RTUs:
Site ID 100 100 Link ID LINE1 LINE2 IP Address or Host name FEP1.moto.com FEP2.moto.com
In this example, LINE2 is Static LAN so the user needs to set the DNS servers of LINE2 network in the LINE2 port configuration of RTU #1 and RTU #2. LINE1 is PPP, so there is no need to set these servers they are learned from the network automatically. In principle it is recommended to create two sets of IP conversion tables one that will be assigned to an FEP/IP Gateway on the LAN, and one to all other RTUs which are connected with the ASTRO IV&D radios. The first will include the above information concerning each RTU, and the second will have only the FEP/IP Gateway. For MDLC over iDEN, MDLC over Tetra, and MDLC over Standard or Null Modem, consult the system provider for the infrastructure relating to the IP addresses.
136
Communications
Firewall
The ACE3600 Firewall enables the user to define a variety of firewall protections. The firewall is configured and activated in the ACE3600 STS site configuration per site, for all IP ports in the site. The user can specify the list of IP addresses to accept, i.e. the list of IP addresses allowed to pass through this firewall. If no IP addresses are defined, then all addresses are allowed. When the firewall is active, all UDP/ TCP ports will be blocked (e.g. telnet, http) except the following: DHCP port DNS port MDLC port (UDP 2002) NTP port MODBUS port (TCP 502) Expansion TCP connectivity and data ports (configurable, by default 57001, and 57002) Expansion UDP discovery port (57001, not user configurable) Timer event (UDP 57003)
The firewall also enables the user to define the maximum length of ICMP Echo (ping) allowed. A ping packet with a bigger size will be ignored, no response will be sent back. In a system with I/O expansion, an enabled firewall could potentially block communication from expansion frames to the main frame. To enable communication from expansion frames to a main frame with enabled firewall, either: Manually enter the IP addresses of the expansion frames and main frame OR Make sure that no address ranges are defined in the firewall Address List (default) and the firewall will allow all IP communication.
137
Communications
MDLC over Dialup Modem Configuration

The ACE3600 can be connected to dial-up modem. The user can configure the modem from the RTU using the MDLC over Dialup port. A configuration modem string can be defined in the Physical Layer to configure the modem. The modem configuration file enables the user includes the configuration modem string and other AT commands. If no modem configuration file exists, the configuration modem string will be used. If both exist, the modem configuration file will be used. MDLC over Dialup is different than MDLC over IP in the way it configures modem and connects it. It is important to note that in many cases the same modem can work in both modes, but the user must decide when configuring the port, what method to use. With MDLC over Dialup, the modem is placed in circuit data mode, meaning it establishes phone call conversations with remote sites upon transmitting to them. It accepts calls when another site transmits an MDLC frame to it. Most of the time the modem is idle, meaning it is in command mode. It only moves into data mode, when it needs to transmit or is called from another site. After a predetermined idle time, the modem disconnects the call. With MDLC over IP, the modem is ALWAYS in a call. The call is actually PPP mode. This enables it to receive MDLC over IP frames from remote sites, as well as sending them. This call does not consume any air resources since it begins with the RTU and ends in the modem itself. To make it more reliable when using wireless modems in dial mode, the modem can be monitored periodically to check if it is registered in the wireless network. This is done periodically every few seconds.
138
Radio Communications
The ACE3600 RTU is designed to operate with various Motorola conventional and trunked radio transceivers (see table below). Other Third Party conventional radios can be interfaced to the ACE3600 using the radio modem ports using DPSK 1.2 kbps modulation (for more information consult Motorola support).
Radio HT750 - North America GP320 - Europe, Middle East, Africa GP328 - Asia & Pacific Pro5150 - South America CDM750 North America Bands VHF 136-174 MHz UHF 403-470 MHz UHF 450-512 MHz Modulation DPSK 1200 bps
VHF 136-174 MHz UHF 403-470 MHz UHF 450-512 MHz VHF 146-174 MHz UHF 438-470 MHz
DPSK 1200 bps FSK 2400 bps DFM 4800 bps DPSK 1200 bps FSK 2400 bps DFM 4800 bps
CM200 - North America CM140 - Europe, Middle East, Africa GM3188 - Asia & Pacific EM200 - South America XTL5000/XTL2500 Analog Trunk XTL5000/XTL2500 Digital Trunk (IV&D)
VHF 136-174 MHz UHF 450-520 MHz UHF 380-470 MHz 764 - 806 MHz 806 - 869 MHz VHF 136-174 MHz UHF 380-470 MHz UHF 450-520 MHz 764 - 806 MHz 806 - 869 MHz
DPSK 1200 bps (analog operation)
XTS2500 Digital Trunk (IV&D)
N/A
139
Communications
Radio FCC information

Radio Band Power Output* Transmitter Type Acceptance Emissions Applicable Rules
HT750
VHF 136-174 MHz UHF 403-470 MHz UHF 450-512 MHz
1-5W 1-4W 1-4W 1-25W 1-25W 1-25W
AZ489FT3794 AZ489FT4826 AZ489FT4834 AZ492FT3796 AZ492FT4835 AZ492FT4829
16K0F3E, 11K0F3E
90
CDM750
VHF 136-174 MHz UHF 403-470 MHz UHF 450-512 MHz
16K0F3E 11K0F3E 11K0F2D 5K60F2D 11K0F3E 16K0F3E 16K0F2D 11K0F2D 8K10F1D 8K10F1E 11K0F3E 16K0F3E 20K0F1E 20K0F1D 8K10F1D 8K10F1E 11K0F3E 16K0F3E 20K0F1E 20K0F1D 11K0F3E 16K0F3E 20K0F1E 8K10F1E 8K10FID
22 74 90 90.210 90 90.210
CM200
VHF 146-174 MHz UHF 438-470 MHz
1-25W 1-25W
AZ492FT3805 AZ492FT4856
XTL5000
VHF 136-174 MHz UHF 450-520 MHz UHF 380-470 MHz 764 - 806 MHz 806 - 869 MHz
10-50W 10-45W 10-40W 10-35W 10-50W 10-35W 10-40W 10-35W 1-5W 1-5W 1-5W 1-3W
AZ492FT3806 AZ492FT4867 AZ492FT4862 AZ492FT5823 AZ492FT3806 AZ492FT5823 AZ492FT4862 AZ492FT5823 AZ489FT3807 AZ489FT4865 AZ489FT4866 AZ489FT5804
22 74 90
XTL2500
22 74 90
XTS2500
22 74 90
140
Communications
XPR4350/ /XiR M8220/ DGM4100
136-174 MHz 403-470 MHz 450-512 MHz
1-25 W 1-25 W 1-40 W
ABZ99FT3083 ABZ99FT4081 ABZ99FT4083
12.5 kHz Data Only: 7K60FXD 12.5 kHz Data & Voice: 7K60FXE 12.5 kHz Data Only: 7K60FXD 12.5 kHz Data & Voice: 7K60FXE
XPR4380
806-870 MHz 1035 W 896-941 MHz* 1030 W
800 ABZ99FT5010 MHz: 1035W 900 MHz: 1030W
*For frequencies 901902, 940941 MHz, FCC Rule Part 24 limits power to 7W ERP.
141
Communications
Conventional and Analog Trunked Radio Modulation Types The physical interface to the conventional or analog trunked radio is through a plug-in radio modem board on the CPU module; the characteristics programmed into the plug-in modem determine the emission characteristics of the radio. The data may directly modulate the FM transceivers oscillator to most effectively use the radio bandwidth. Motorola refers to this modulation technique as DFM; in the U.S. this is also described by the FCC as an F1 emission. The figure below shows the modulation sideband created by DFM. FCC licenses specifically state when F1 emission may be used and only radios having an F1 emission designator may be used in those licensed systems. No F1 emission is suitable when intermediate amplifiers (voice/RT repeaters) are present and should not be used with PL/DPL, but F1 emissions are fully compatible with the ACE3600 store-&forward operation. The data may instead modulate a tone oscillator to produce a variable tone or variable phase output; this signal output then modulates the FM transceivers oscillator. Motorola refers to this modulation technique as FSK (variable tone) or DPSK (variable phase). The figures below show the modulation sidebands created by FSK and DPSK. The FCC has revised the rules governing the use of these emissions, so please read carefully the Refarming section below. FSK or DPSK must be used whenever any intermediate amplifier (voice/RT repeater: conventional or trunked) is present; DPSK must be used when any degraded bandwidth condition (notch filters, etc.) exists, and DPSK is the only emission allowable in the U.S. VHF splinter channels. FSK and DPSK are also fully compatible with store-&-forward operation.
Modulation Technique
Data Speeds in bps (* = recommended)
DFM FSK DPSK
4800(*), 3600, 2400 2400(*), 1800 1200
Note: Intrac modulation is not supported in ACE3600. PL & DPL Private Line (PL) and Digital Private Line (DPL), also known as Continuous Tone-Coded Squelch System (CTCSS), was created for voice users of two-way radio to suppress activity from other co-channel users from being heard; it offered the illusion of a private channel. PL/DPL adds a decoder to the receiver that keeps the receiver muted until a signal having a specific low-frequency tone (PL) or slow data code (DPL) is received. All transmitters must encode the proper tone/code to open the protected receiver. Some repeaters, notably those in the UHF band, use PL or DPL to prevent unwanted access to the repeater system by co-channel users.
142
Communications
In the U.S. the FCCs rules for Fixed Secondary Signaling and for Telemetry operations require data not to interfere with voice operationsthe data message must wait until the voice message is finished. This is a practical matter alsoif a data message were attempted simultaneously with any co-channel message, there is a high probability that the data would be corrupted and throughput would be zero. So why create the interference for no gain. Therefore the data equipment must listen to all on-channel activity; PL/DPL protection on the receiver is unwanted. PL/DPL may be used in ACE3600 or MOSCAD systems when it operates through some existing voice repeater system that requires PL or DPL for repeater access, but the PL/DPL is added to the transmitter and not the receiver. Note that PL/DPL should never be used on VHF splinter channels: the FCC limits the occupied channel bandwidth by severely limiting deviation; PL or DPL would consume too much of the authorized deviation to produce an effective system. Never use PL/DPL with DFM modulation. FCC Reframing (USA only) In the U.S., the FCC has revised the rules that govern the frequencies between 150.8 and 512 MHz; the rules for the frequencies above 806 MHz have not changed. Two issues addressed by the new rules are channel bandwidth and data efficiency on those channels. The VHF and UHF channel bandwidth have been split. The former 25 kHz channels have been split into two 12.5 kHz channels and will be split further into four 6.25 kHz channels in the future. Manufacturers are required to design all new products to comply with the new channel bandwidth requirements, but there are no requirements that force licensees to migrate to 12.5 kHz channel operation. The MT-2000 and MCS-2000 radios used within MOSCAD may operate on either 25 kHz or 12.5 kHz bandwidth channels; Radio Service Software is used to define the mode of operation. Radios used for data must meet a minimum efficiency requirement. In a separate action, the FCC clarified key definitions.

Data is any signal that bypasses the microphone inputs filters (i.e., the splatter filter). Voice is any signal that passes through the microphone inputs filter.
The FSK and DPSK modulating signals are indeed data superimposed onto tone carriers and these signals always pass through the radios splatter filter. Therefore, these modulating signals are voice, require an emission designator with the F3E characteristic, and are not required to satisfy a data efficiency requirement. VHF Splinter Channels (USA only) In the U.S. the FCC has defined certain frequencies in the 154 MHz and 173 MHz bands for data operationthe splinters. The frequencies are few in number, some have a 12.5 kHz bandwidth, all have a FCC-imposed deviation restriction, and are very commonly used. In an attempt to insure that the transmitted emission stays within the assigned channel bandwidth, the FCC has stipulated that an F2 emission must be used and that the
143
Communications
Sum of the Highest Modulating Frequency plus Deviation shall not exceed a stated maximum. For most channels, that maximum is 2800 Hz but on two frequencies (173.2100 and 173.3900 MHz) the maximum is 1700 Hz. The splinters were exempt from all Refarming actions and still require a 5K60F2D emission designator. ACE3600, when using DPSK modulation, uses a 1200 Hz modulating tone; the legal allowable deviation on the 2800 channels is therefore 1.6 kHz whereas on the 1700 channels the legal deviation is an unusable 500 Hz. FSK is theoretically usable but at an impractical small deviation (300 Hz); DFM may not be used because it is not an F2 emission. PL/DPL must never be used because their deviation (750 Hz) must be subtracted from the data deviation which worsens an already marginal situation. Therefore, DPSK modulation at 1.6 kHz is the only legal emission available for 2800 splinter frequency use; never use the 1700 frequencies and never use PL/DPL on a splinter frequency. Refer to the FCC rules or other applicable regulations to understand additional constraints on maximum Effective Radiated Power, antenna height, and antenna directivity.
144
Communications
Analog Trunked Radio Systems

In an analog trunked radio system, any unit that needs to send a message, requests, and is assigned to, a channel by the trunking system controller. The ACE3600 RTUs are typically clustered into a single trunked data group and are managed by the trunking system controller as a single entity. Therefore, any RTU that requests a channel causes all RTUs to switch to the assigned channel so that all units hear, decode, and may appropriately respond to the data transmitted. Two way data transfer among many RTUs may occur following a single channel request/assignment. Also, trunked systems provide an infrastructure that is inherently redundantif one base station should fail, the trunked system automatically assigns communications to a remaining station. SCADA system data and trunked radio systems are very compatible! Most analog trunked radio systems are set up to optimize the performance of the many mobile and portable voice radios in the system. This setup may not be optimal for data users. ACE3600 operates best in the Message Trunking mode whereas many systems are setup to use the PTT-ID Trunking mode. ACE3600 may be made compatible by lengthening the delay-before-transmit time to allow the PTT-ID activity to be completed before the ACE3600 data is transmitted. Many trunked radio systems are designed with multiple transmit and receive sites. This is advantageous for the mobile and portable users that roam over a large territory but detrimental to ACE3600 data use. Receiver voting is present so the best quality received audio will be used; a quality analysis will occur at regular intervals, typically 350 msec, and a switch to the better quality signal may occur. That switch (revote) may introduce a small hole and/or a signal phase change into the audio message. Voice users are minimally affected by the hole/phase-change, but those artifacts may compromise the data message so that no throughput occurs (complete destruction). When ACE3600 is used in a multi-site system, the antenna choice and placement must be carefully selected so that only one site will receive a strong signal this will prevent the site switch associated with a revote. System engineers are encouraged to contact the ACE3600 Product Support Group during the design phase of any trunked radio system so that these and other issues may be discussed.
145
Communications
Digital Trunked Radio Systems

In digital trunked radio systems such as ASTRO IV&D and TETRA (Dimetra), the ACE3600 uses the packet data capability of the system. The digital trunked radio system behaves as an IP network. The ACE3600 interfaces to the digital radio using an RS232 port configured to PPP protocol. For more information refer to the MDLC over ASTRO IV&D chapter in the ACE3600 STS Advanced Features Manual.
Conventional Radio Interoperability

Introduction Since the first MOSCAD RTU was introduced to the market, various models of Motorola conventional radios had been used with Motorola RTUs. In cases where new RTUs are added to existing systems with newer radio models, or when legacy radios are replaced with newer models, it is important to make sure the radios can interoperate in the same system. The purpose of this technical note is to provide important information on Motorola radio interoperability in control systems that use MOSCAD, MOSCAD-L, MOSCAD-M, ACE3600, and Front End Processors (FEPs) such as MCP-M and IP Gateway. The radios discussed in this document are Motorola conventional radios. Channel Monitor Resolution Parameter (MDLC Slot Time) The MDLC protocol uses a slotted time channel access algorithm for radio communications. The Channel Monitor Resolution parameter sets the time slot period (in milliseconds) in the RTU/FEP. The types of radios used in the system determine the value of this parameter (typically 100 to 300 ms). Please note that the Channel Monitor Resolution parameter should be the same in all the RTUs/FEPs in the system. When different radios are used in the system, the parameter is determined by the radio that requires the longest slot time. For example, in a system which uses both 200 ms and 300 ms radios, the Channel Monitor Resolution parameter should be set to 300 ms in all the RTUs/FEPs in the system. To determine how to set up the Channel Monitor Resolution parameter in RTUs in your system, see the table on the following page. First Warm-up Delay Parameter When the radios PTT is activated, the radio starts transmitting a carrier wave. The other radios on the same frequency channel that receive the carrier wave activate the Channel Monitor and signal the RTU that the channel is busy. For each type of radio, there is a specific delay between the activation of the PTT in the transmitting radio and the activation of the channel monitor signal in the receiving radios. The types of radios that are used in the system determine the value of this parameter (typically 200 to 350 ms in Motorola conventional radios).
146
Communications
Please note that this parameter should be the same in all the RTUs that reside on the same frequency channel and communicate with each other. When different radios reside on the same frequency channel, the parameter is determined by the radio that requires the longest Warm-up. For example, in a system which uses both 200 ms and 300 ms radios on the same channel, the First Warm-up parameter should be set to 300 ms in all the RTUs. To determine how to set up the First Warm-up Delay parameter in RTUs in your system, see the table on the following page. F1-F2 Repeater Considerations When the system uses an F1-F2 repeater, the First Warm-up Delay Parameter should be longer from the values in the table below. Also the Channel Monitor Resolution Parameter might be longer. In this case, the parameter setting in the system is determined by the RTUs/FEP radios and the repeaters performance. For technical support concerning setting parameters in system with F1-F2 repeaters, please contact Motorola technical support. Parameter Setting for Motorola Conventional Radios in MOSCAD / ACE3600 Systems
Radio Modulation First WarmUp Delay [ms] Channel Monitor Resolution [ms]
XTL2500/5000 analog conventional operation CDM750
DPSK only FSK & DPSK @ 12.5 KHz channel spacing DFM @ 25KHz channel spacing
300 200 200 300 300 200 200 300 300
200 100 100 200 200 100 100 200 200
CM140;CM200;EM200;GM3188; GM338;GM339;GM340;GM350
FSK & DPSK @ 12.5 KHz channel spacing DFM @ 25KHz channel spacing
MCS2000; Maxtrac
FSK & DPSK @ 12.5 KHz channel spacing DFM @ 25KHz channel spacing
MTS2000 HT1000
FSK & DPSK @ 12.5 KHz channel spacing DPSK only
147
Communications
Setting the Parameters in the MOSCAD/MOSCAD-L ToolBox The Channel Monitor Resolution and First Warm-up Delay parameters are set in the Site configuration -> Port 3 -> Advanced Physical Layer screen.
Setting the Parameters in the ACE3600 STS The Channel Monitor Resolution and First Warm-up Delay parameters are set in the Site -> Port Tab -> Port X -> Advanced Configuration -> Physical Tab screen.
148
Communications
Communication Network
The ACE3600 system network consists of RTUs communicating with one or more computerized control centers and/or with other RTUs. Each control center is connected to the communication network. The system can be relatively simple, comprising several RTUs and one control center. It can be modularly expanded to a more hierarchical system, where several sub-systems (comprising intelligent RTUs and/or sub-centrals controlling their peripheral RTUs) communicate with a central computer. The communication network is flexible, enabling each RTU to communicate with hierarchies above it (RTU-to-central), parallel to it (RTU-to-RTU), under it (another RTU), and also relaying messages through it (when the RTU serves as a communication node). While the communication protocol allows for a complex hierarchical system structure, it does not make it complicated. This is because most of the communication interactions are transparent to the user, except in those cases where the communication is to be defined by the ladder application. In such cases, you should perform simple programming operations to configure the required application. Each RTU may be configured to serve as a far-end terminal or as a regional center. The RTU may function as a regional center either by definition or only after loss of
149
Communications
communication with the central. It also can act as a communication node (an interconnection point between two or more different links) while performing its other tasks. The RTU network uses the MDLC protocol, which incorporates all seven layers of the OSI model adapted for SCADA. It supports multiple logical channels per physical port, enabling simultaneous central-to-RTU and RTU-to-RTU sessions. It also enables each RTU to simultaneously run several kinds of communication applications, such as reporting alarms by contention, on-line monitoring, performing diagnostics checks, etc. The MDLC protocol is discussed later in this manual. The ACE3600 System Tools Suite (STS) may perform monitoring, modification, diagnostics, error logging, etc., on any RTU in the system from any RS232 port in the system, configured as either RS232 Local Computer port, RTU-to-RTU RS232 (RSlink1) or from any IP port in the system (not necessarily RTU port).
Communication Types
The RTUs in the system are linked to a radio or line network as defined by the system engineer, according to user requirements. Each RTU executes its application and, simultaneously, supports the communications link (or links) defined for it, and serves as a network node, if so defined. The ACE3600 system supports up to 29 line links (LINE 1 to LINE 29), up to nine radio links (RADIO 1 to RADIO 9), up to 19 local RTU-to-RTU links (RS-link 1 to RS-link 19) that use RS232, up to 29 IP links (LINE 1 to LINE 29), and one dial link. Any of the radios may be either conventional or analog trunked. Computers may be connected to the ports configured as RS232 Local Computer, as local RTU-to-RTU link, or via Ethernet. For conventional radios, up to nine zones can be defined on every frequency (of the nine supported frequencies). A radio link for conventional radios is divided into zones when not all sites can communicate with each other and F1/F2 repeaters (using two frequencies) are not to be used. In this case, some RTUs will serve as Store & Forward repeaters and the link is divided into zones. A zone is defined as a group of one or more sites that can directly communicate with each other without a Store & Forward repeater. The name of a zone is composed of the link name and the zone number. For example, for RADIO 3 zone number 1 is named RADIO 3/1, zone number 2 - RADIO 3/2 and so on. After defining the communications network, the user must define the various links used in the system as well as the RTUs that serve as nodes between the links. A network node is an RTU that functions as an interconnection point between two or more different links. A Store & Forward node, on the other hand, is a network node, which relays messages using the same physical port.
150
Communications
Network Configurations
The ACE3600 system supports both simple and complex communication networks. The following sections describe various configurations from different aspects. Simple System A simple system, comprised of a central computer and RTUs connected over one communication link, is shown in the following figure:
Central Computer
IP / RS232 Media FEP RS232 RTU 1 RTU 2 RTU 3 RADIO 1 Central Computer RTU 1 RTU 2 RS232 FEP RTU 3 RTU 6 LINE 1 RTU 4
STS
STS
The STS may be connected to any port of the RTU. The ports of the RTUs should be defined via Site Configuration. The logical name (e.g. LINE1, etc.) of the communication link is also defined. Two-Link and Multiple Link Systems A two-link system utilizing a communications network, comprised of two communication links, is described in the following figure:
151
RTU 5
Communications
The FEP in the system illustrated above serves as a network node between link RADIO 1 and link LINE 1. Configuring the FEP to have access to two different links enables it to serve as a node between these links. The MDLC protocol permits RTU-to-RTU communications without the intervention of the central computer. RTUs that are not on the same link communicate with each other via the network node (in this case, the FEP). A multi-link system is a network that uses several link types. The following figure illustrates a system where a third link type, RS232, connects an RTU to another terminal that communicates over RADIO 2. RTUs connected to the IP link can reach RTU 7 via IP network and then RADIO 2.
IP Central Computer RTU 1 RTU 2 RTU 3 RS232 RTU 7 ZONE 2 RTU 6 RTU 5 RTU 1 RTU 4 RTU 2 RTU 6 RTU 3 RS232 FEP
RADIO 2
RTU 4
Two-Zone System A two-zone system that uses conventional radio over a single frequency is described in the following figure:
ZONE 1 RTU 9 FEP
Store & Forward
152
RTU 5
Communications
RTU 9 (Site ID = 9) is configured as a Store & Forward repeater. It performs data exchange between units that operate on the same frequency but are unable to communicate directly for reasons of path and propagation. Any RTU in zone 1 may communicate with any RTU in zone 2 via this repeater. The figure below illustrates this system schematically. In this case, RTU 9 is a network node between the RADIO 1/1 and RADIO 1/2 links. The network software treats the Store & Forward node as it treats the node between line and radio: logically the links appear as two different links, but physically they share the same port.
RADIO 1/1 FEP RTU 9 RADIO 1/2
RTU 1
RTU 2
RTU 3
Using Site Configuration, the FEP and the RTUs in zone 1 are configured to have access to the RADIO 1/1 link. The RTUs in zone 2 are configured to have access to the RADIO link, and RTU 9, the network node, is configured to have access to both RADIO 1/1 and RADIO 1/2 links. Using Network Configuration, RTU 9 is configured as the only node in the network. This terminal is configured to have two links, RADIO 1/1 and RADIO 1/2. Multiple Zone System The following figure illustrates an ACE3600 system spanning multiple zones.
FEP
RTU 15
ZONE 1
ZONE 2 RTU 5 RTU 40 RTU 1 RTU 6 RTU 2 RTU 3 RTU 4
153
RTU 4
Communications
The schematic representation of this system is shown below. The system assumes that the two nodes, RTU 15 and RTU 40, cannot hear each other. They communicate via the FEP, which is also a Store & Forward node. This system, therefore, consists of four zones and three nodes (RTU 15, RTU 40, and FIU). Any communication between RTUs in different zones passes through these three nodes.
ZONE 1 RADIO 1/3 RTU 15 RTU 1 RADIO 1/1
FEP
RTU 2 ZONE 2 RADIO 1/2 RTU 2 RTU 5 RTU 2
RADIO 1/4 RTU 40 RTU 1
In the above situation, three nodes with their accessible (logical) links should be defined. Using the STS site configuration, the RTUs in zone 1 should be configured to have access to the RADIO 1/1 link, and the RTUs in zone 2 to the RADIO 1/2 link. RTU 15 should be configured to have access to both RADIO 1/1 and RADIO 1/3 links, while RTU 40 should be configured to have access to both RADIO 1/2 and RADIO 1/4 links. The FEP is configured to have access to both RADIO 1/3 and RADIO 1/4 links. Assuming that the two nodes (RTU 15 and RTU 40) can hear each other, the result is a system consisting of three zones and two nodes, as shown in the following figure:
RADIO 1/1 RTU 15 RTU 4 RADIO 1/2 RTU 40 RTU 1
FEP
RADIO 1/3
154
Communications
In this case, the two nodes do not communicate through the FEP. Therefore, the FEP does not serve as a node in the system. Note that the communication between RTUs in different zones passes only through two nodes.
MDLC Encryption
Overview
Encryption prevents any non-authorized party to communicate on MDLC network. The level of protection provided by encryption is determined by an encryption algorithm. The encryption strength is measured by the number of possible encryption keys and the key size. ACE3600 and legacy MOSCAD and MOSCAD-L RTUs can communicate using encrypted MDLC protocol. The Encryption is based on Tiny Encryption Algorithm (TEA). The information being sent within the MDLC packets is encrypted using a 128 bit encryption key. To enhance security, each RTU can store 9 replaceable encryption keys. The encryption keys can be replaced in all the RTUs in a system at the same time. Encryption is possible on all the types of communication links that use MDLC protocol. MDLC data encryption is supported by: ACE3600 MOSCAD IP Gateway MOSCAD (CPU420) MOSCAD-L (CPU020) Only encrypted RTUs / IP Gateways that are using the same Encryption Key are able to exchange data and commands An RTU that receives data or a command from another encrypted RTU that uses a different key (or from a non-encrypted RTU) will reject the received data or command.
155
Communications
Both a non-encrypted RTU and an encrypted RTU can serve as an MDLC network node for encrypted or non-encrypted RTUs.
Encryption Keys
A set of Encryption Keys is defined for the system using the MDLC Encryption Tool. The Keys File (KF) is saved and then downloaded to the IP Gateway and to the RTUs using the MDLC Encryption Tool. The KF can be loaded to a local or a remote RTU. Each KF contains nine keys, indexed 1 to 9. The same KF is used by the IP Gateway, the RTUs and the ToolBox MDLC driver. The KF is encrypted and cannot be obtained from without password The KF in stored encrypted in the RTU and in the IP Gateway. Only one KF is in use in a system at any given time. Only one Encryption Key from the KF should be active at any given time, and it is identified by its index (1-9). If the active key index is set to 0, the MDLC Encryption is disabled (the RTU / IP Gateway / ToolBox becomes non-encrypted). The MDLC Encryption Tool enables setting and managing the encryption in a system. It has the following major features: Building a system site map Defining KF with 9 encryption keys Downloading the encryption KF to the RTUs and IP Gateway Setting Active Key index in RTUs, IP Gateway and in the ToolBox MDLC driver.
The encryption keys are stored in the RTU / IP GW FLASH memory.
156
Communications
When an RTU is first configured and stars up (cold start in MOSCAD and MOSCAD-L RTUs), the key index is set to 0 (non-encrypted mode). Encryption is then activated by changing the Active Key index to a number other than 0 (1-9). This is done using the MDLC Encryption Tool. The replacement of the encryption key is initiated by the MDLC Encryption tool. Successful replacement of the active key requires that all RTUs in the system be timesynchronized by the IP Gateway. To compensate for possible time drifts during a transition from one encryption key to another, there is a configurable time interval where both the old and new keys are valid.
Accept old and new keys for RX. Switch to new key Uses old key for TX. Uses new key for TX. Uses new key for TX. Accept new key for RX.
TE1 TE2
time
TE1 is the interval, in seconds, which represents the possible time drift. Note: It is recommended that at least one non-encrypted IP Gateway (FIU) will be connected to the system to enable communication with non-encrypted RTUs when necessary
Encryption in the STS/ToolBox MDLC Driver

Once KF is defined in the MDLC Encryption Tool, it can be set as the Active File in the STS/ToolBox MDLC driver The Active Key Index is then set to the same index (1-9) of the Active Key of the system. This enables the STS or ToolBox to exchange data with encrypted RTUs. In the event that the STS/ToolBox must send a non-encrypted message, (to an RTU that performed a cold restart), the encryption should be deactivated by setting the MDLC driver Key Index to 0.
157
Communications
Security Administration Tool

The Security Administrator Tool, provided with the MDLC Encryption Option is used to control access to the MDLC Encryption Tool and files. Using this tool, the administrator can define users and groups, and grant permissions to authorized personnel as necessary.
MDLC Encryption Implementation Considerations

Encryption Interoperability: Encrypted system requires using the following versions of firmware and tools in the same system. The following versions should be used in the same system: 1. 2. 3. 4. 5. 6. 7. MOSCAD firmware V9.29 or higher IP Gateway firmware V5.40 or higher ACE3600 firmware V11.05 or higher MOSCAD/MOSCADL ToolBox V9.54 with Service Pack 2 (SP2) IP Gateway Toolbox V5.52 or higher ACE3600 STS V11.70 or higher Encryption Tool 1.00 or higher
The Encryption Tool, STS and IP Gateway ToolBox require that MOSCAD/MOSCAD-L ToolBox V9.54 with Service Pack 2 (SP2) will be installed on the same PC to be able to work in encryption mode. (This requirement is valid to STS and Encryption Tool V1.00 only. STS will not require ToolBox V9.54 when higher Encryption Tool versions will be used).
158
Clock Functions and Synchronization

RTU Clock
The ACE3600 RTU has one time source, an internal system clock which is in microsecond resolution. This time source is updated using a backup source of the RTC hardware component - Real Time Clock (seconds accuracy). In addition, external clocks, such as GPS and NTP servers can be used as a time source. See NTP Clock Synchronization and Global Positioning System (GPS) below. The time resolution of the system clock is hour, minute, second, millisecond, microsecond. The date resolution is day, month, year. Leap year support is automatic. When the RTU first starts up, the system clock is set according to the RTC, which always retains its time in seconds (even when the RTU is powered down.) The RTU time can then be set using a number of mechanisms. The RTU clock controls the date and time of the ACE3600 unit. Date and time information is used for timestamps on events such as time tagging changes to time tagged discrete inputs, etc. The ACE3600 includes configurable time zone support, where RTUs in one time zone can adjust messages received from another time zone. The time zone is commonly used in conjunction with NTP servers and GPS receiver. These servers operate in UTC (Universal Time Clock) which is in the (Greenwich Mean Time) GMT time zone. Setting time zone in a unit will adjust it to the local time. The ACE3600 also supports daylight savings time. Daylight savings time is used only in conjunction with a time zone. The start and end dates for daylight savings time (month, day, our) can be defined in the Daylight Saving Dates table. (The current year is assumed.) The RTU will check these dates and adjust the time by one hour when appropriate. The time zone is set in the STS site configuration and the daylight savings time is set in the application system table.
Time Adjustment and Synchronization

MDLC time synchronization of the RTU clock can be performed locally or remotely, using MDLC protocol over a variety of communication media, including conventional radio, RS485, and RS232. Synchronization is accurate to 1 millisecond+0.5 (very low delay). With IP media, this feature can be enabled, but because its accuracy/delay is unpredictable it is not recommended. NTP, the recommended method of obtaining the time over IP media (PPP or Ethernet), allows accuracy of 1 to 100 milliseconds depending on the media.
159
In ACE3600 RTUs, a new MLDC extended time synchronization can be enabled which includes the synchronizing RTUs password. In this case, all RTUs in the system must use the same password. This extended time synchronization also enables synchronizing two RTUs in different time zones, and better accuracy than the MOSCAD MDLC legacy synchronization. Note that by default, the ACE3600 uses MOSCAD MDLC legacy synchronization (to support IP Gateway and MOSCAD RTUs) which does not include the time zone and password features. Note: An extended time synchronization of two RTUs, where only one is configured for time zone, will proceed as if both RTUs are in the same time zone. The RTU clock can be synchronized during runtime using a number of methods. Before synchronizing the clock, make sure that the appropriate parameters have been configured properly. (See Time Parameter Configuration below.)
User Time Control Actions

STS Date & Time utility From the STS, the user sets the RTU date/time to the PCs date/time (which is limited to second accuracy.) For information on using the Date & Time utility, see the Operation chapter of the ACE3600 STS User Guide. STS Sync utility From the STS, the user instructs the local RTU to synchronize (in milliseconds accuracy) the date/time of other RTUs attached to one or all links. It is recommended to synchronize all links, so that the entire system has the same date/time. For information on using the Sync utility, see the Operation chapter of the ACE3600 STS User Guide. Note that MDLC dialup links do not support synchronization. User Application The user application (ladder or C) can synchronize RTUs on one or all links using the Sync function. It is recommended that an RTU with a reliable clock source synchronize all RTUs in the system once per day to correct clock drift. The requirement for legacy MOSCAD RTUs to synchronize RTUs at least once every 48 days is not relevant to ACE3600 RTUs. However, ACE3600 has a drift of 30 ppm which is 2.6 seconds per day if not connected to an NTP server and/or GPS receiver. The worst case is a drift of 1.8 milliseconds per minute, or 18 milliseconds per 10 minutes. Typical tests shows better results at 1 millisecond per 2 minutes, or 5 millisecond per 10 minutes. The interval of sending a time sync, is proportional to that clock offset/accuracy sending a sync every 2 minutes assures a 1 millisecond offset typically.) For information on the Sync function, see Appendix B: Ladder Diagram Language in the ACE3600 STS User Guide and C Toolkit for ACE3600 RTUs User Guide. When the user application (ladder or C) updates the Time & Date database
160
system table, it also changes the RTU time and date. For more information on the Time & Date database system table, see Appendix C: Database Tables and Data Types in the ACE3600 STS User Guide. The user can update the same Time & Date database system table (HH:MM:SS) using the Application Programmer database monitor function. In this case, synchronization is direct (no time zone aspect.) For information on monitoring a database table, see the Application Programmer chapter of the ACE3600 STS User Guide.
System Time Control Actions

GPS Connection An RTU which is connected to a GPS receiver continuously polls the GPS time and synchronizes itself. Because the clock source is reliable, this RTU can be used to synchronize the rest of the system. See the Global Positioning System (GPS) section below. NTP Connection An RTU which is connected to an NTP server continuously polls the NTP server(s). Because the clock source is reliable, this RTU can be used to synchronize the rest of the system. The accuracy of NTP time depends on the link to the NTP server. It can be 1 millisecond in a LAN where the NTP server resides on the same network, and up to 100 milliseconds if using wireless media such as GPRS or TETRA. See the NTP Clock Synchronization section below.
If the synchronizing RTU is in a different time zone than the RTU being synchronized, the system will adjust the time accordingly; the receiving RTU will add the time zone of the sender to the global time (GMT) and use this. If only one of the two RTUs involved is configured for time zone support, the synchronization will proceed as if both sites are in the same time zone. Note: A legacy MOSCAD RTUs is treated as an RTU which is not configured for time zone support. Note: In systems with I/O expansion, clock synchronization of the expansion modules is controlled by the main CPU. In addition, a sequencing mechanism ensures that time tags and timer events are sequenced properly in chronological order.
NTP Clock Synchronization

The Network Time Protocol (NTP) can be used as an external clock source to synchronize the ACE3600 RTU over IP with one or more NTP servers. In the MOSCAD system, the NTP works in client/server mode, in which a client RTU polls another server and gets a reply. The server can be another RTU operating NTP, or a host (PC, Unix, Linux). NTP poll the server RTU every 2 seconds, every 4 seconds, 8 and so on, up to a poll every 17 minutes. NTP provides client accuracies typically within a millisecond on LANs and up to 100 milliseconds on WANs (Internet, GPRS). Any
161
RTU (usually FEP) can act as a server. This enable setting its time via MDLC time sync, for example, and having other RTUs specify it as an NTP server and obtain their time from it. NTP synchronizes clock both in time and frequency. In time means it make its clock offset as close as possible to the server. In frequency means it learns the server drift (time between ticks) in order to avoid polling it every few seconds. An example, not related to NTP, is ACE3600 send MDLC Sync over radio to another ACE3600. The clock offset guaranteed to be less than 1 millisecond. However a 30ppm clock drift after 1 minute offset will be 1.8 milliseconds. NTP prevents that by learning the drift frequency of the server. User can set a single NTP server, or several ones. NTP operates under the assumption that each server's time should be viewed with a certain amount of distrust. NTP really prefers to have access to several sources of lower stratum time (at least three) since it can then apply an agreement algorithm to detect insanity on the part of any one of these. Normally, when all servers are in agreement, NTP will choose the best of these, where "best" is defined in terms of lowest stratum, closest (in terms of network delay) and claimed precision, along with several other considerations. As the below figure shows, at the top of any NTP hierarchy are one or more stratum 0 reference clocks. These are electronic clocks such as GPS signals, radio signals, or extremely accurate frequency control. Reference clocks are assumed to be accurate. In ACE3600 a GPS port can be configured, it will serve as a reference clock for that RTU. In this case RTU will operate on stratum 1 with an accuracy of 200 microseconds.
NTP Architecture
As the above figure shows, time is distributed from an NTP subnet of servers. Each server comprises a stratum, which designate its location in terms of hops to the UTC source. The stratum 1 is the most accurate server of which all servers should be synchronized to. Up to 15 stratum levels may exist. Stratum 16 means server unreachable.
162
The accuracy of other clocks is judged according to how close a clock is to a reference clock (the stratum of the clock, the network latency to the clock, and the claimed accuracy of the clock. The accuracy of NTP thus depends on the network environment. Because NTP uses UDP packets, traffic congestion could temporarily prevent synchronization, but the client can still self-adjust, based on its historic drift. Under good conditions on a LAN without too many routers or other sources of network delay, synchronization to within a few milliseconds is normal. Anything that adds latency, such as hubs, switches, routers, or network traffic, will reduce this accuracy. The synchronization accuracy on a WAN is typically within the range of 10-100 ms. For the Internet/GPRS synchronization accuracy is unpredictable, so special attention is needed when configuring a client to use public NTP servers. Testing with the ACE3600 connected with the Internet gains accuracy of 20-30ms, but theoretically it may be even 100ms. NTP uses UTC time base (Coordinated Universal Time). UTC evolved from Greenwich Mean Time (GMT). GMT is based on the earths rotation, which is not constant enough to be used for detailed time measurements. UTC is based on a standard second length determined by the quantum phenomena. There is a difference of a few seconds between the two (14seconds in 2006), so every several years add one more second (called leap second) to UTC. This is built in NTP protocol. To translate the UTC time into local time, user can configure Time zones and Daylight Savings in RTU. Note however, that if setting NTP server to another stand alone ACE3600, which has no time zone, both will operate with the same local time if no time zone set. If that ACE3600 is connected to a GPS or to another NTP server then there is a need to set a time zone.
Global Positioning System (GPS)

The ACE3600 system can use a GPS receiver precise time measurement application for synchronization purposes, to synchronize the RTU with other SCADA systems. The ACE3600 RTUs use GPS timing receivers equipped with a 1 Pulse per Second (PPS) output. The receivers are connected to an RTU port. In case of a satellite failure, the time is manufactured internally and the receiver indicates its inability to trace the satellite. The recommended GPS receiver is the Synergy Systems SynPaQ/E GPS Sensor with M12+ Timing Receiver which must be purchased from a Synergy vendor. Along with the timing receiver, a data/power cable and antenna should be purchased. For details on connecting to the GPS receiver, see Appendix A: RS232/RS485 Adaptor Cables in the ACE3600 STS Advanced Features manual.
163
SCADA System Components

Control Center SCADA Manager
Supervisory Control And Data Acquisition (SCADA) originally described a monitor and control process wherein all intelligence resided in a central computer (the SCADA Manager). The human operators would manage the system by observing the data as presented on the computers terminal(s).
FEP
The SCADA Manager in most cases consists of a personal computer(s), the software package on that computer, the configuration files/screens created for the system and an interface assembly between the computer system and the communication systemthis interface is the Front End Processor (FEP). Commonly, the FEP is isolated and the term SCADA Manager is used instead to describe the computer, software, etc.; that convention will be used hereafter. The SCADA Manager typically does not support the MDLC protocol; the SCADA Manager might not support conventional, trunked, or data radio; it might not support LAN or dial-up. The FEP provides this support and passes data to the SCADA Manager. The SCADA Manager assumes it is communicating with the field units but is truly communicating only with (or through) the FEP. The technology used within the FEP is necessarily different according to the connectivity available in the SCADA Manager.
M-OPC
OPC defines an open industry-standard interface based on OLE and ActiveX technology that provides interoperability between different field devices, automation/control and business systems. The OPC specification defines a set of interfaces for easy to use objects including methods and properties to manipulate these objects. The basic transport layer for OPC is DCOM and therefore, a Man-Machine Interface (MMI) or supervisory control and data acquisition (SCADA) software package can process and collect data from OPC servers that are running on different computers in the network. The specification also defines a standard mechanism to access named data items contained in an OPC server. Motorola used the OPC specification to build the M-OPC server. This server enables exchange of information over the communication system between SCADA managers (or any other application) and Motorola RTUs. The M-OPC software package comprises: M-OPC server M-OPC client interface MDLC communications driver M-OPC Monitoring and Setup Tool Security Administration Tool
164
All the M-OPC components run on a standard PC hardware platform that supports both MS Windows 2000 Pro and MS Windows XP Pro. The M-OPC solution uses a standard client/server architecture. The Control center components include Client(s) (SCADA software or other applications), M OPC server, MDLC driver and Field Interface Unit FIU (ACE3600, MOSCAD or MOSCAD-L CPU). The FIU provides MDLC networking and various media connectivity to the RTUs. The M-OPC offers the following functionality: Standard interface between ACE3600 and MOSCAD family RTUs and many control center SCADA managers. Support of special features unique to Motorola RTUs. Support of the MDLC protocol and all Motorola RTU types, i.e., ACE3600, MOSCAD, MOSCAD-L and MOSCAD-M.
The M-OPC server uses OPC Data Access (DA) V2.05. The server enables the clients to organize the field data according to the OPC logical object model and read/write data either synchronously or asynchronously. It automatically updates clients when new groups are created and also enables SCADA clients to retrieve new groups without having to restart the server. The server uses the MDLC driver to: Poll the RTU databases Send commands to the RTUs Receive data bursts from the RTUs The server scheduler is responsible for scheduling the polling of RTU data. Data polling can be performed in periodic intervals or upon specific requests from clients. Schedules are set using the M-OPC Monitoring and Setup Tool. The scheduler optimizes the communications with the RTUs to minimize the MDLC network communication load. This feature is extremely important in radio networks. The server holds the information received from the RTUs in a cache database. The cache reflects the latest value of the data as well as its quality and the server time-stamp.
165
During the M-OPC Server operation, various operational data are collected and logged for user diagnostics purposes.
ACE IP Gateway
The ACE IP Gateway is a real-time protocol converter that connects MDLC on its communication medium to TCP/IP. It does not contain a database. It is configured using the ACE3600 STS by simply assigning an MDLC and an IP address for their respective systems use. An API is provided to enable SCADA HMI vendors to develop a communication driver between the SCADA programs that require data from the IP Gateway and the IP Gateway itself (contact your Motorola Data Specialists to determine if a driver is already available for the host hardware/software being used). A typical example of the ACE IP Gateway (IPGW) is shown in the figure below; a SCADA control center is connected via the ACE IP Gateway to RTUs on a radio link, to RTUs on an RS485 link and to RTUs on an IP in the ACE3600 system.
The SCADA control center, which includes workstations and a SCADA computer, exchanges data with the ACE3600/MOSCAD system via the ACE IP Gateway, which serves as a Gateway from the TCP/IP world to the MDLC world. The ACE IP Gateway uses the TCP/IP LAN Protocol for exchanging data application messages with the SCADA software. The ACE IP Gateway API (Application
166
Programming Interface) allows SCADA driver developers to quickly and easily build the ACE IP Gateway Interface (driver), which serves as a communication interface with the MDLC world. Data exchange between the SCADA (client) and the ACE IP Gateway (server) is carried out using TCP/IP peer -to-peer communication over LAN. The ACE IP Gateway can support multiple connections that are initiated from multiple SCADA computers. The implementation of the ACE IP Gateway interface in the SCADA software allows the SCADA to perform the following operations: Poll an RTU in order to get data and COS (Change-of-State) events from the RTU tables. Send commands to the RTU and download parameters to its local process. Send commands via broadcasts to any required group of RTUs. Download parameters (set-points) to the RTU local process. Receive spontaneous reports (by contention) from RTUs (both burst and event transmission). Receive time-tagged events logged in the RTUs (1 msec resolution). Adjust the RTUs clocks (1 sec resolution). Synchronize the RTUs clocks. Support redundant ACE IP Gateway configuration by setting the Gateway mode to be Primary/Secondary). Retrieve Gateway status. Retrieve RTU links status. Update RTU links in the site table. Retrieve software diagnostics from ACE IP Gateway itself. For a detailed description of the interface, please refer to the ACE IP Gateway API manual.
ACE IP Gateway System Overview

SCADA System The complete control system is comprised of the SCADA control center (or centers) communicating with ACE3600/MOSCAD RTUs over various communication links, such as: Conventional radio Analog trunked radio ASTRO IV&D radio TETRA radio Motorola MotoTrbo radio (digital mode) Data radio Cellular modems Dial-up lines IP network (LAN, WAN) Mixed media networks
167
The communication system is used for transmitting alarms, status and telemetry, calculated data diagnostics and error logging information from the RTUs to the central facility computer and vice versa. It is also used for downloading, monitoring and debugging the application program at the sites. The system may be relatively simple, comprising several RTUs and a single control center, or a more complicated hierarchical system, where several sub-control-centers communicate with lower, parallel and higher hierarchies. The RTUs may also communicate with each other and/or with any other hierarchy in the system. The figure below depicts a system with more than one SCADA control center, an ACE IP Gateway, and RTUs which are connected to a variety of media including RS232, RS485, IP and radio link. Note that the ACE3600 STS can be connected to the ACE IP Gateway or to any ACE3600 RTU over RS232 or over Ethernet.
The ACE3600/MOSCAD system uses the MDLC protocol, based on the seven layers of the OSI model published by ISO, and adapted for SCADA communications. It provides network support, multiple logical channels per physical port, allowing each RTU to simultaneously run several communication sessions, such as data exchange, on-line monitoring, diagnostics, etc.
168
The ACE3600 system is supplied with a Software Tools Suite (STS) package that runs on a PC running Windows XP or Windows Vista. All RTU functions such as configuration, database and process definition, downloading, monitoring, hardware and software diagnostics, etc. are defined using the STS. The ACE3600 STS can communicate with the Gateway via RS232 or IP. The STS may be connected either locally to an RTU or via the MDLC port of the ACE IP Gateway to any RTU in the system. All programming and monitoring functions can be performed either locally or remotely. (The Gateway can serve as an MDLC router between the ACE3600 STS and RTUs.) Note: When the ACE3600 STS is connected locally to one of the RTUs in the system, it can service any other RTU in the system via the MDLC communication network. Multiple SCADA control centers can simultaneously perform multiple sessions with the ACE IP Gateway in order to send commands and polling requests to the RTUs and to receive data and contention reports from the ACE3600 RTUs. All this can be done via a single physical Ethernet Gateway static LAN port. By default the Gateway port is ETH1, but any Ethernet port may be used. In a SCADA system, ACE3600 RTUs and ACE IP Gateways can use IP (Internet Protocol) technology to interface to advanced radio infrastructure (e.g. digital ASTRO IV&D and TETRA systems) and to standard private IP networks. MDLC and IP networks can be integrated in the same system, as MDLC networking properties are preserved. MDLC applications need not be modified as the lower layers of the protocol support IP. For details on these various interfaces, see MDLC over IP Communication above. SCADA Interface
Client-Server environment
The SCADA application for the ACE IP Gateway is based on a client-server approach. The Gateway application acts as a server while the SCADA Interface acts as a client. In such a relationship, the SCADA Interface must establish the connections with the Gateway needed for communicating with the ACE3600 RTUs. After the connections have been established, the SCADA Interface can send data, commands, and polling requests to the field RTUs. It can also establish a special connection that enables receipt of data transmissions initiated by the field RTUs (so called burst/RTU event data, contention data or Change-Of-State [COS] messages). Note: The ACE IP Gateway checks its connections to the SCADA from its end, to make sure they are alive. At the same time, the SCADA must check from its end that its connections to the ACE IP Gateway are alive.
169
Channels and Channel types
The SCADA Interface must establish at least one connection toward the Gateway server. These connections are called channels and are used to transfer messages from the SCADA center toward both the Gateway and the RTUs in the field. The client application can open different types of channels to best serve its SCADA Interface process. The two basic channel types are: Regular Spontaneous A Regular channel enables asynchronous sending/receiving of data and requests. It uses a mailbox mechanism for mapping the request messages to their replies. A Spontaneous channel allows receiving burst data (Spontaneous COS messages) and RTU events - i.e. transmissions initiated by the field RTUs. This feature almost eliminates the need for the SCADA application to poll data since every change in one of the telemetry field variables can immediately be transmitted to the SCADA application.
ACE3600/MOSCAD System - RTU Definitions
To make the ACE3600/MOSCAD field system definition transparent to the SCADA client application and to correctly parse the data received from the ACE3600/MOSCAD system, the API builds an internal data structure defining the types and numbers of the field RTUs. To do so, it uses two external system definition files (in ASCII format). This automatic system definition done by the API routines hides the field system structure from the SCADA application and eliminates the need for any application modifications when working with different ACE3600/MOSCAD systems. Moreover, new RTUs can be added to the system at run time using the appropriate API routine.
Primary/Secondary Gateway Modes
The ACE IP Gateway supports a redundant configuration. There are two modes of operation: Primary and Secondary. If there is a single standalone ACE IP Gateway, then it starts up as Primary. If the system configuration includes redundant Gateways, then both start up as Secondary and the SCADA must determine which one will be set to function as Primary. At any other time, the SCADA can change the mode of operation by calling the appropriate API set mode routine. The API also supplies a routine for checking the current mode of operation. This functionality of the ACE IP Gateway provides redundant gateway operation, which minimizes the risk of communication failure. For more information, see ACE IP Gateway Redundancy below.
Communicating with the ACE IP Gateway
Once a channel has been established with the Gateway, the SCADA interface can issue requests to the Gateway. The request categories are Send routines, Receive routines, Data Analysis routines and Management routines.
170
Typical API sequence calls are the following: Connect /* Establish Connection to Gateway. */ Poll /* Send a polling request. */ Receive /* Receive MDLC communication (answer) buffer. */
Troubleshooting
The ACE IP Gateway communication can be diagnosed using the STS Software Diagnostics and Loggers tool. For detailed information, see the ACE3600 Software Diagnostics and Error Messages manual.
Health Check Mechanism

General The ACE IP Gateway system includes a Health Check mechanism which manages the MDLC connectivity to the sites. Associated with each site are two links, through which the site can be reached. A background MDLC ping mechanism in both the Gateway and the ACE3600 units constantly verifies which links are available. If both links are failed, no communication will be forwarded from the SCADA to that failed RTU. The Health Check mechanism uses the site table as the basis for its operations. Health Check reduces communication overhead (retries and delays) by identifying which links are available and routing frames to operational links. MDLC Infrastructure MDLC provides a frame-sequence service for the Health Check mechanism. Specifically, a dedicated channel is allocated for this activity at both the RTU and the Gateway. All Health Check messages are transmitted and received through this channel. Being a frame-sequence channel, the Health Check MDLC channel is both reliable and a lowresource consumer at the same time. MDLC provides a framework for the two entities (the Gateway and RTUs) to maintain this mechanism but the actual protocol (data, timing, policy, etc.) is determined in the RTU/Gateway firmware. Mechanism In the ACE IP Gateway, the Health Check mechanism relies on the MDLC infrastructure denoted above. When activated, it takes the dedicated Health Check channel provided by MDLC and uses the site table as a source for all sites to be managed. For each site, the Health Check performs the following process: At a predefined interval, the Gateway sends a ping frame to each site, one through each of the sites links. It then expects to receive a response frame for each ping sent. A ping arriving from a certain site through a certain link, will set the communication status of that link to OK. A site that possesses at least one link in OK status is considered reachable. This process constantly monitors the status of each sites links and provides the ACE IP Gateway with an updated communication status of all sites in the field.
171
The Health Check protocol uses a minimal amount of system resources (length of data, and time.) On the RTU side, the Health Check mechanism relies on the MDLC infrastructure described above. It operates in slave mode. When a ping frame is received by the RTU, the RTU Health Check mechanism replies with an echo of that frame. The RTU transmits a response back to the ACE IP Gateway over the same link. Unless it is pinged, the RTU Health Check mechanism will not initiate any communication.
Disabled Health Check
When Health Check is disabled in the ACE IP Gateway, the Gateway assumes that all sites registered in the site table are reachable. When Health Check is disabled in the RTU, the RTU MDLC stack will not allow any incoming Health Check messages. Instead, an automatic response indicating that Health Check application is blocked will be communicated back to the originator of an incoming ping frame. The ACE IP Gateway Health Check assumes the link is OK if such a response is received. However, indications received from the Health Check mechanism may not be accurate, since the specific path through which the response packet arrived cannot be determined.
ACE IP Gateway Terminal Server Ports

The ACE IP Gateway (CPU 4600) supports a number of on-board and plug-in ports. If more serial ports are required for MDLC communications, external hardware such as a Terminal Server can be added. The Terminal Server, which has an Ethernet port and many RS232 ports, conveys communication traffic from the Ethernet port to the RS232 ports and vice versa. The ACE IP Gateway establishes a connection to the Terminal Server over the LAN and establishes IP sessions for each RS232 port that is utilized for MDLC communication. The connection remains opened even if there is no data to transmit/receive. Every connection is associated with an IP address (of the Terminal Server), a TCP port ID (associated with the specific RS232 port in that specific Terminal Server), the MDLC link ID for the port, and the physical port over which the Gateway will route packets to the Terminal Server. The Gateway is designed to support up to 32 ports connected to one or more Terminal Servers. For more information on adding and configuring ACE IP Gateway Terminal Server ports in the ACE3600 STS, see Customizing the Configuration of a Site in the Operation chapter of the ACE3600 STS User Guide.
172
IP Address = xxx.xxx.xxx.xxx
SCADA Computer ACE IP Gateway
IP Address = yyy.yyy.yyy.yyy
IP Address = zzz.zzz.zzz.zzz
PORT 2008
PORT 2008
RTU #1
...
RTU #N
RTU #1
...
RTU #N
ACE IP Gateway Redundancy

A redundant ACE IP Gateway can be configured to minimize the risk of a SCADA control center single point of failure (lost contact with sites), and to ensure high availability for its applications. Two Gateways are set up with similar configurations. After startup, both will act as secondary Gateways. When the SCADA establishes connections to the Gateways, the SCADA driver designates one of the Gateways as primary and the other as secondary. Only one ACE IP Gateway can be primary at any time. When redundant ACE IP Gateways peers exist, only the primary Gateway will update the network. Note: When the unit is shipped from the factory, it will start up initially (before site configuration download), as a primary Gateway in Standalone mode, even in systems with redundant Gateways.
ACE IP Gateway Site ID 10044/1 Gateway Designation Startup Mode ACE IP Gateway Site ID 10044/2 Gateway Designation Startup Mode
When the unit is shipped from the factory: After initial download of site configuration: After SCADA driver changes the Gateway Redundancy Mode:
Primary
Standalone
Primary
Standalone
Secondary
Redundant GW1
Secondary
Redundant GW2
Primary
Redundant GW1
Secondary
Redundant GW2
173
After the 1st ACE IP Gateway becomes unavailable and the SCADA changes the 2nd Gateway to Primary:
Secondary
Redundant GW1
Primary
Redundant GW2
The primary Gateway communicates properly over MDLC communication and over the SCADA channels. There is bi-directional transfer of both SCADA application messages and ACE IP Gateway management messages. The secondary Gateway transfers ACE IP Gateway management messages only. (It does not send or receive any MDLC messages, since it is logically disconnected from the link.) The secondary Gateway does not acknowledge any frame received by the MDLC communication (except local connection). The requests queued in the secondary Gateway will return errors once activated. (In most cases this will be immediately. However, in some cases it could take as long as the longest MDLC session timeout defined.) The secondary Gateway disconnects from all the Terminal Server ports defined in the site configuration. When the primary Gateway becomes unavailable, the secondary (similarly configured) Gateway takes over. To increase the availability of the LAN network, dual Ethernet segments can be used, and each Gateway can be connected to a different segment. When a Gateway is configured for redundancy, it checks each of the channels to the unit. If all the channels to the Gateway are disconnected or unavailable, the Gateway automatically switches to secondary mode. Redundant ACE IP Gateway Configurations There are several possible options for Redundant ACE IP Gateway system configuration: 1. Both ACE IP Gateways are connected to the MOSCAD system over an IP network. Using this configuration, the ACE IP Gateways mode change takes effect immediately for requests going from the ACE IP Gateway to the RTUs. The SCADA should initiate a communication to the RTU through the new primary ACE IP Gateway in order for the RTU being able to send Bursts to it. 2. Both ACE IP Gateways are connected to the MOSCAD system over the same manyto-many media (i.e. RS485/Radio). In this configuration, when the secondary ACE IP Gateway becomes primary, the ACE IP Gateways mode changes take effect immediately. 3. Both ACE IP Gateways are connected to the MOSCAD system over the same Terminal Sessions. In this configuration, the old primary ACE IP Gateway must close all of the Terminal Server connections, the terminal server must end its sessions with the old primary ACE IP Gateway and then the new primary ACE IP Gateway must
174
establish connection with the Terminal server. In this configuration, several minutes may elapse before the ACE IP Gateways mode changes take effect.
MOSCAD IP Gateway
The legacy MOSCAD IP Gateway (was MCP-T) supports this TCP/IP connectivity. The legacy IP Gateway module has communication ports but it does not support any I/O modules. Both 10BaseT and AIX connectors are available to connect the IP Gateway to the 10 Mbps Ethernet LAN. As with the ACE IP Gateway, the IP Gateway is a gatewaya real-time protocol converterthat connects MDLC on its communication medium to TCP/IP. It does not contain a database. It is configured by simply assigning an MDLC and an IP address for their respective systems use; a configuration software program is provided with the IP Gateway to ease this task. An API is also provided which the system engineer must use to develop a driver between the programs in the server that require data from the IP Gateway and the IP Gateway itself. Contact your Motorola Data Specialists to determine if a driver is already available for the host hardware/software being used.
Legacy ModBus FEP

ModBus is a wireline protocol in common use in SCADA markets (now also available on TCP/IP networks). It is supported by many SCADA Manager vendors and it is traditionally used in MOSCAD systems at the central. ModBus drivers typically expect prompt communications between the computer and the field units; they do not tolerate well the random delays encountered when a shared communication medium is used. The legacy MOSCAD Communications Processor for ModBus (MCP-M) was designed to interface ModBus to both MDLC and the shared media. MCP-M exists in many existing MOSCAD system where additional ACE3600 RTUs can be installed. Note: The .out file created by the STS can be used to create the central file for MCP-M with the following limitations: 1. The user tables in the user program should use only MOSCAD data types and should not use the new data types added to the ACE3600. 2. The first six characters of each variable in the user program should be unique. The MCP-M contains a Series 400 CPU module with a RAM expansion board and a special FEP program. The MCP-M is packaged in the small NEMA 4 enclosure, contains the 8Amp power supply/charger, battery, and communications device (radio or wireline modem) according to the needs of the system. The FEP program retains the communication ports but does not support any I/O modules. A serial data cable connects between either Port 1B or Port 2 (or boththe MCP-M supports two simultaneous ModBus sessions) on the CPU module and the appropriate COM port on the PC computer; ModBus data typically at 19.2 kbps exists on this connection.
175
The MCP-M maintains an internal database of all the reportable data from all of the MOSCAD RTUs in the system. A System Builder software program is provided with the MCP-M to ease this task: it reads the export file created by the MOSCAD Programming ToolBox for each of the many RTUs applications and prompts the system engineer to identify which data items are to be collected and which are not. Each identified data item has an equivalent ModBus address according to some very simple yet rigorous rules; therefore, the database in the MCP-M may easily be read, or written to, by the SCADA Manager. The MCP-Ms database is kept accurate by any combination of the communication modes discussed in the Communication chapter. If the SCADA Manager should change the contents of any database items defined as outbound (a control), that change will automatically be sent to the associated RTU. The MCP-M may be configured to periodically interrogate (poll) one or more RTUs to collect some or all of the reportable data in those RTUs and to update the MCP-M database accordingly. Multiple interrogation schedules may be defined: short time intervals for the sites with more interesting data and less often for the other sites.
176
Appendix A - ACE3600 Specifications

General Frames No I/O slots - PS and CPU modules only, wall mount, * Dimensions (WxHxD ): 117 x 244 x 198 mm (4.61" x 8.23" x 7.80"), Weight: 0.95 Kg (2.1 lb) 2 I/O slots - PS, CPU and 2 I/O modules, wall mount, * Dimensions (WxHxD ): 194 x 244 x 198* mm (7.64" x 9.61" x 7.80"*), Weight: approx. 1.6 Kg (3.56 lb) 3 I/O slots - PS, CPU and 3 I/O modules, wall mount, * Dimensions (WxHxD ): 234 x 244 x 198 mm (9.21" x 9.61" x 7.80"), Weight: approx. 1.9 Kg (4.19 lb) 5 I/O slots - PS, CPU and 5 I/O modules, wall mount, * Dimensions (WxHxD ): 314 x 244 x 198 mm (12.36" x 9.61" x 7.80"), Weight: approx. 2.4 Kg (5.3 lb) 7 I/O slots - PS, CPU and 7 I/O modules; wall mount, * Dimensions (WxHxD ): 391 x 244 x 198 mm (15.39" x 9.61" x 7.80"), Weight: 3.0 Kg (6.6 lb) 8 I/O slots - PS, CPU and 8 I/O modules, wall mount OR 19" rack, * Dimensions (WxHxD ): 435 x 244 x 198 mm (17" x 9.61" x 7.80"), Weight: approx. 3.3 Kg (7.3 lb) Redundant CPU and power supply frame - Dual PS, Dual CPU, and 4 I/O modules; wall mount OR 19" rack, * Dimensions (WxHxD ): 391 x 244 x 198 mm (15.39" x 9.61" x 7.80"), Weight: 3.0 Kg (6.6 lb)
Depth including Module panel
177
Appendix A ACE3600 Specifications
Expansion Frame
Number of I/O slots Default power supply Compatible power supplies power supply
3, 5, 7, or 8 Expansion power supply All except: 10.8-16V DC low-tier
Metal Chassis
19" frame metal back - for PS, ACE IP Gateway, radio and 6.5 or 10 Ah backup battery, 2 accessory boxes; wall/rack mount, OR PS, CPU, radio and 6.5 or 10 Ah backup battery, 0, 3, 5, 8 I/O slot frame, up to 2 accessory boxes, wall/rack mount, ** Dimensions (WxHxD ): 434.5 x 310.4 x 200 mm (17.11"x 12.22" x 7.88"). Large - for PS, CPU and up to 7 I/O slot frame, two radios and 6.5 or 10 Ah backup battery, wall mount, Dimensions (WxHxD**): 448 x 468 x 200 mm (17.64"x 18.43" x 7.88") Medium - for PS, CPU and up to 3 I/O slot frame, one radio and 6.5 Ah backup battery, wall mount, Dimensions (WxHxD**): 335 x 355 x 198 mm (13.19" x 13.98" x 7.80") Small - for PS, CPU, 2 I/O slot frame, 1 radio (or 1 accessory box), and 6.5Ah backup battery, wall mount, Dimensions (WxHxD**): 264 x 365 x 200 mm (11.02"x 14.17" x 7.88").
Housing
Large NEMA 4/IP66 painted metal - up to 7 I/O slot frame, two radios and 6.5 or 10 Ah, backup battery, Dimensions (WxHxD): 500 x 500 x 210 mm (19.7" x19.7" x 8.26" ) Small NEMA 4/IP66 painted metal - up to 3 I/O slot frame one radio and 6.5 Ah backup battery, Dimensions (WxHxD): 380 x380 x 210 mm (15" x 15" x 8.26")
Power Supply
10.8-16 V DC low-tier 10.8-16 V DC (default) 18-72 V DC 18-72 V DC with 12V smart battery charger 100-240 V AC, 50-60 Hz 100-240 V AC, 50-60 Hz, with 12V smart battery charger 6.5 Ah - Sealed Lead-Acid 10 Ah - Sealed Lead-Acid
Backup Battery
**
Depth including Frame and Module
178
Operating Temperature
-40 C to +70 C (-40 F to 158 F) Notes: 1) When using a metal housing option, the maximum operating temperature outside the housing is +60 C (140 F). 2) ACT module and Motorola radios operating temperature range is:-30 C to +60 C (-22 F to 140 F). 3) In redundant AC or 18-72 VDC power supplies: up to 50C (122F) - when installed inside a metal chassis or closed cabinet. up to 60C (140F) - when installed without enclosure or closed cabinet. The full operating temperature range is supported when using redundant 12V power supplies.
Storage Temperature Operating Humidity Mechanical Vibrations Operating Altitude
-55 C to +85 C (-67 F to 185 F) 5% to 95% RH @ 50 C without condensation Per EIA/TIA 603 Base-station, Sinusoidal 0.07mm @ 10 to 30 Hz, 0.0035 mm @ 30-60 Hz -400m to +4000 meter (-1312 ft to + 13120 ft) above sea level Note: When using 18-72V DC or 100-240 VAC power supply, the operating altitude is -400 to +3000m.
Regulatory Standards Safety UL 60950-1 (UL listed), CSA 22.2-950-1, EN60950-1, IEC 60950-1, AS/NZS 60950 FM/cFM certified as Nonincendive Class I, Division 2 - standard FM 3611 (Note: FM approval refers to model F7509 only and most of the ACE3600 options) Emission standards for industrial environments CFR 47 FCC part 15, subpart B (class A); CE EMC: EN50081-2/EN61000-6-4 (CISPER 11/EN55011 class A) Immunity standards for industrial environments Per EN50082-2 /IEC 61000-6-2
Emission
Immunity
179
Communications Communication Ports Up to 5 ports per CPU (CPU 3640), up to 8 ports per CPU (CPU 3680/4600) Serial - up to 4 RS232 ports Multi-drop up to 3 RS485 port Ethernet - up to 2 10/100 MB ports and 1 10 MB Two-way radio/analog trunked radio - up to 2 modem ports USB Host for MotoTrbo- up to 2 ports Internal Ethernet 10/100 Mb/s port (for redundant CPU configuration) Mobile conventional two-way radios CM 200, CM 340, GM 3188, EM 200, CDM750 Portable two-way radios HT750, GP320, GP328, PRO5150 Analog trunked radios XTL5000, XTL2500 Digital trunked radios XTL5000, XTL2500, XTS2500, MTM800 (TETRA) MotoTrbo radios XPR4350/4380, DM3400, XiR M8220, DGM4100 Two-way radios, Data radios, TETRA radios (PD) Dial-up modems, Cellular modems (dial mode and PD) MDLC, TCP, UDP, IP, PPP, NTP, DHCP MODBUS RTU: master and slave on RS232/RS485/Ethernet DF1 (Allen Bradley): master on RS232 DNP 3.0: master/slave on RS232/RS485/Ethernet IEC 60870-5-101: slave on RS232 Possible on RS232, RS485 and Ethernet ports
Motorola Radio Support
Third Party Radio Support Modem Support Protocols Third Party Protocols
User Protocol (user program)
Specifications subject to change without notice.
180
Power Supply Module Specifications

The following charts detail the specifications of the various power supply modules. For specifications of the power supply module used with I/O expansion frames, see Expansion Power Supply Module Specifications below.
12V DC Power Supply Module (Default)
Input Voltage
DC 10.8-16 V The low limit of the DC power supply (10.8-16V) can be configured to 10.5V. The default is 10.8. Motherboard connector (to CPU and I/O modules): equal to input voltage, max. 4 A AUX1A/AUX1B: equal to input voltage, max. 8 A, on/off controlled by user program AUX2A/AUX2B (configurable): 3.3, 5, 7.5, 9 V DC 10%, max. 2.5A, on/off (default) OR equal to AUX1A/AUX1B output voltage max. 8A Note: max. 8 A total current consumption from all outputs Max. 50 mA Status LED for: input voltage, AUX1 and AUX2 outputs, 12V control for DO modules Internal line fuse, replaceable AUX2A/B short circuit, automatic recovery on 3.3, 5, 7.5, 9 V 56 mm W x 225 mm H x 180 mm D (2.2" W x 8.7" H x 7.1" D) Approx. 0.43Kg (0.95 Lb)
Outputs
No Load Power Consumption Diagnostic LEDs Input Protection Output Protection Dimensions Weight
12V DC Low-Tier Power Supply Module
Input voltage Outputs
10.8-16 V DC Motherboard connector (to CPU and I/O modules): The same as input voltage / max. 4 A AUX1A/AUX1B: equal to input voltage max. 8A Note: max. 8 A total current consumption from all outputs Internal line fuse, replaceable 56 mm W x 225 mm H x 180 mm D (2.2" W x 8.7" H x 7.1" D) Approx. 0.43Kg (0.95 Lb)
Input Protection Dimensions Weight
181
18-72V DC Power Supply Modules
Input Voltage Total Power Outputs
18-72 V DC 18-72 V DC Max. 60 W continuous; max. 105 W peak @ 25% duty cycle Motherboard connector (to CPU and I/O modules): 13.2 V DC 20%, max. 4 A AUX1A/AUX1B: 13.2 V DC 20%, max. 8 A, on/off controlled by user program AUX2A/AUX2B (configurable): 3.3, 5, 7.5, 9 V DC 10%, max. 2.5A, on/off (default) OR equal to AUX1A/AUX1B output voltage max. 8A Note: max. 8 A total current consumption from all outputs 12 V Lead Acid battery charger (in PS model with charger) Automatic charging of 6.5 or 10 Ah backup battery, battery temperature sensing, overcharging protection, battery capacity test and diagnostics, automatic battery switch-over Status LED for: input voltage, AUX1 and AUX2 outputs, 12 V Control DO for DO modules, and battery Max. 250 mA 80% typical, 76% with full load 10 A maximum, for 2 mSec. Max, cold start at 25C Internal line input fuse (replaceable), short circuit automatic recover AUX2A/B short circuit, automatic recovery on 3.3, 5, 7.5, 9 V Input to case: 500 V DC, input to output 500 V DC 56 mm W x 225 mm H x 180 mm D (2.2" W x 8.7" H x 7.1" D) Approx. 1Kg (2.2 Lb)
Battery Charger
Diagnostic LEDs No Load Power Consumption Efficiency Inrush Current Protection Output Protection Insulation Dimensions Weight
182
AC Power Supply Modules
Input voltage
100-240 V AC, 50/60 Hz 100-240 V AC, 50/60 Hz with 12V smart battery charger Maximum 60 W continuous; maximum 105 W peak @ 25% duty cycle Motherboard connector (to CPU and I/O modules): 13.2 V DC 20%, max. 4 A AUX1A/AUX1B: 13.2 V DC 20%, max. 8 A, on/off controlled by user program AUX2A/AUX2B (configurable): 3.3, 5, 7.5, 9 V DC 10%, max. 2.5A, on/off (default) OR equal to AUX1A/AUX1B output voltage max. 8A Note: max. 8 A total current consumption from all outputs 12 V Lead Acid battery charger (in PS with charger) Automatic charging of 6.5 or 10 Ah backup battery, battery temperature sensing, overcharging protection, battery capacity test and diagnostics, automatic battery switch-over Status LED for: input voltage, AUX1 and AUX2 outputs, 12V Control for DO modules, and battery 130 mA @ 220 V AC 80% typical @230 V AC, 76% typical @115 V AC (full load) 25 A maximum, for 2 mSec. Max, cold start at 25C 0.98 typical at 230 V AC, 0.99 typical at 115 V AC Internal line fuse, replaceable AUX2A/B short circuit, automatic recovery on 3.3, 5, 7.5, 9 V Input to case: 1500 V AC, input to output: 3000 V AC 56 mm W x 225 mm H x 180 mm D (2.2" W x 8.7" H x 7.1" D) Approx. 1kg (2.2 lb)
Total Power Outputs
Battery Charger
Diagnostic LEDs No Load Power Consumption Efficiency Inrush Current Power Factor Protection Output Protection Insulation Dimensions Weight
183
CPU 3610*/CPU 3640 Module Specifications

Microprocessor Microprocessor Clock Memory Freescale Power PC II MPC8270, 32-bit, extended communication capability, DMA and floating point calculation support 200 MHz Flash: 16 MB/3 MB free for user DRAM: 32 MB/10 MB free for user SRAM plug-in (Optional): 4 MB total, all free for user Full calendar with leap year support (year, month, day, hours, minutes, seconds). Time drift: max. 2.5 Seconds per day (when power is on) 3 V Rechargeable lithium backup battery Configurable RS232 or RS485 port: - RS232: Asynch, Full Flow Control, up to 230.4 kb/s, GPS receiver interface - RS485, multi-drop 2-Wire up to 230.4 kb/s RS232, Asynch, Full Flow Control, up to 230.4 kb/s, GPS receiver interface 10/100 Mb/s (on CPU 3640 only) Supports the following Plug-In ports: - Radio Modem, DPSK 1.2 kb/s, FSK 1.2/1.8/2.4 kb/s, DFM 2.4/3.6/4.8 kb/s - RS232, Sync/Asynch, Full Flow Control, up to 230.4 kb/s, GPS receiver interface - RS485, multi-drop 2-Wire up to 230.4 kb/s - Ethernet 10/100 Mb/s Supports the following Plug-In ports: - Radio Modem, DPSK 1.2 kb/s, FSK 1.2/1.8/2.4 kb/s, DFM 2.4/3.6/4.8 kb/s - RS232, Sync/Asynch, Full Flow Control, up to 230.4 kb/s, GPS receiver interface - RS485, multi-drop 2-Wire up to 230.4 kb/s - Ethernet 10 Mb/s 4 CPU diagnostic LEDs, Port status LEDs and user application LEDs Refer to Appendix C: ACE3600 Maximum Power Ratings. 10.8-16 V DC (from the motherboard connector) 56 mm W x 225 mm H x 180 mm D (2.2" W x 8.7" H x 7.1" D) Approx. 0.38 Kg (0.84 Lb)
Real-Time Clock
SRAM and RTC Retention Serial Port 1
Serial Port 2 Ethernet Port 1 Plug-In Port 1
Plug-In Port 2
LEDs Display Power Consumption Operating Voltage Dimensions Weight

* Discontinued model
184
CPU 3680 Module Specifications

Microprocessor Microprocessor Clock Memory Freescale Power PC II MPC8270, 32-bit, extended communication capability, DMA and floating point calculation support 200 MHz Flash: 32 MB/19 MB free for user SDRAM: 128 MB/100 MB free for user SRAM plug-in (Optional): 4 MB total, all free for user Full calendar with leap year support (year, month, day, hours, minutes, seconds). Time drift: max. 2.5 Seconds per day (when power is on) 3 V Rechargeable lithium backup battery Type A host full speed 12 Mbs ports (HU1 on left and HU2 on right) for MDLC over IP communication via the MotoTrbo digital mode radio system. For MotoTrbo radio only; No other USB devices or USB Hubs are supported. Configurable RS232 or RS485 port: - RS232: Asynch, Full Flow Control, up to 230.4 kb/s, GPS receiver interface - RS485, multi-drop 2-Wire up to 230.4 kb/s RS232, Asynch, Full Flow Control, up to 230.4 kb/s, GPS receiver interface Ethernet 10/100 Mb/s USB device port, Type B connector (for future use) Supports the following plug-in ports: - Radio Modem, DPSK 1.2 kb/s, FSK 1.2/1.8/2.4 kb/s, DFM 2.4/3.6/4.8 kb/s - RS232, Sync/Asynch, Full Flow Control, up to 230.4 kb/s, GPS receiver interface - RS485, multi-drop 2-Wire up to 230.4 kb/s - Ethernet 10/100 Mb/s Supports the following plug-in ports: - Radio Modem, DPSK 1.2 kb/s, FSK 1.2/1.8/2.4 kb/s, DFM 2.4/3.6/4.8 kb/s - RS232, Sync/Asynch, Full Flow Control, up to 230.4 kb/s, GPS receiver interface - RS485, multi-drop 2-Wire up to 230.4 kb/s - Ethernet 10 Mb/s
Real-Time Clock
SRAM, RTC, and Security Chip Retention USB Host Port 1, 2
Serial Port 1
Serial Port 2 Ethernet Port 1 USB Device Port 1 Plug-In Port 1
Plug-In Port 2
Internal Port 1
LEDs Display
Ethernet 10/100 Mb/s (for redundant CPU configuration)

4 CPU diagnostic LEDs, Port status LEDs and user application LEDs
185
Module Replacement Power Consumption Operating Voltage Dimensions Weight
Hot swap replacement module extraction/insertion under voltage in redundant CPU configuration only. Refer to Appendix C: ACE3600 Maximum Power Ratings. 10.8-16 V DC (from the motherboard connector) 56 mm W x 225 mm H x 180 mm D (2.2" W x 8.7" H x 7.1" D) Approx. 0.38 Kg (0.84 Lb)
186
DI Module Specifications
16/32 DI FAST 24V Modules
Total Number of Inputs Input Arrangement Fast Counter Inputs AC Input Frequency AC Input Delay Fast Counter Input Frequency Max. DC Input Voltage ON DC Voltage Range OFF DC Voltage Range ON AC Voltage Range OFF AC Voltage Range Input Current Fast Capture Resolution Event Time Tagging Resolution Input Filtering Counter Input Filtering 24 V DC Output Diagnostic LEDs User Connection Cable and TB Holder Module Replacement Input Isolation Input Insulation Operating Voltage Power Consumption Dimensions
16 DI (Option V265); 32 DI (Option V379) Isolated groups of 16 inputs with shared common Inputs that can be used as fast counters: - All inputs in 16 DI module; - First 20 inputs in 32 DI module 45 65 Hz Maximum 0.2 mS 0 - 12.5 KHz, minimum pulse width 40 S Max. 40 V DC (relative to input common) +9 to +30 V DC, -30 to -9 V DC -3 to +3 V DC 10 to 27 V AC (RMS) 0 to 5 V AC (RMS) Max. 3.5 mA 1 mS (Interrupt upon change of state) 1 mS (Interrupt upon change of state) 0 to 50.8 mS (DC, programmable in 0.2 mSec steps) 0 to 12.75 mS (programmable in 0.05 mSec steps for inputs configured as high speed counters) Supports optional isolated 24 V plug-in Wetting Power Supply (one in 16 DI, two in 32 DI) Status LED per each input, module error LED, 24V plug-in status LED 2 or 4 Terminal Blocks (3.5mm pitch), Maximum 18 AWG 20 or 40 Wire Cable with TB Holder connector, 26 AWG wires Hot swap replacement module extraction/insertion under voltage 2.5 kV RMS between input and module logic per IEC60255-5 Insulation resistance 100 M @ 500 V DC, per IEC60255-5 10.8-16 V DC and 3.3 V DC (from the motherboard connector) Refer to Appendix C: ACE3600 Maximum Power Ratings. 37 mm W x 225 mm H x 180 mm D, (1.5" W x 8.7" H x 7.1" D)
187
Weight
16 DI: approx. 0.28 Kg (0.62 lb); 32 DI: approx. 0.29 Kg (0.63 lb)
16/32 DI FAST 24V IEC 61131-2 TYPE II Modules
Total Number of Inputs Input Arrangement Fast Counter Inputs
16 DI (Option V117) 32 DI (Option V959) Isolated groups of 16 inputs with shared common Inputs that can be used as fast counter: - All inputs in 16 DI module - First 20 inputs in 32 DI module
0 - 10 KHz, minimum pulse width 50 S
Fast Counter Input Frequency Max. DC Input Voltage ON DC Voltage Range OFF DC Voltage Range Input Current Fast Capture Resolution Event Time Tagging Resolution Input Filtering Counter Input Filtering 24V DC Output Diagnostic LEDs User Connection Cable and TB Holder Module Replacement Input Isolation Input Insulation Operating Voltage Power Consumption Dimensions
Max. 40 V DC (relative to input common) +11 to +30 V DC, -30 to -11 V DC -5 to +5 V DC 6-10 mA 1 mS (Interrupt upon change of state) 1 mS (Interrupt upon change of state) 0 to 50.8 mS (DC, programmable in 0.2 mSec steps) 0 to 12.75 mS (programmable in 0.05 mSec steps for inputs configured as high speed counters) Supports optional isolated 24 V plug-in Wetting Power Supply (one in 16 DI, two in 32 DI) Status LED per each input, module error LED, 24V plug-in status LED 2 or 4 Terminal Blocks (3.5mm pitch), Maximum 18 AWG 20 or 40 Wires Cable with Terminal Block Holder connector, 26 AWG wires Hot swap replacement module extraction/insertion under voltage 2.5 kV RMS between input and module logic per IEC60255-5 Insulation resistance 100 M @ 500 V DC, per IEC60255-5 10.8-16 V DC and 3.3 V DC (from the motherboard connector) Refer to Appendix C: ACE3600 Maximum Power Ratings. 37 mm W x 225 mm H x 180 mm D, (1.5" W x 8.7" H x 7.1" D)
188
Weight
16 DI: approx. 0.28 Kg (0.62 lb) 32 DI: approx. 0.29 Kg (0.63 lb)
32 DI FAST 48V Modules
Total Number of Inputs Input Arrangement Fast Counter Inputs Fast Counter Input Frequency Max. DC Input Voltage ON DC Voltage Range OFF DC Voltage Range Input Current Fast Capture Resolution Event Time Tagging Resolution Input Filtering Counter Input Filtering Diagnostic LEDs User Connection Cable and TB Holder Module Replacement Input Isolation Input Insulation Operating Voltage Power Consumption Dimensions Weight
32 DI Isolated groups of 16 inputs with shared common Inputs that can be used as fast counters: First 20 inputs
2.0 KHz (minimum pulse width 250 S)

Max. 72 V DC (relative to input common)
+36 to +60 V DC 0 to +6 V DC Max. 3 mA

1 mS (Interrupt upon change of state) 1 mS (Interrupt upon change of state) 0 to 50.8 mS (DC, programmable in 0.2 mSec steps) 0 to 12.75 mS (programmable in 0.05 mSec steps for inputs configured as high speed counters) Status LED per each input, module error LED 4 Terminal Blocks (3.5mm pitch), Maximum 18 AWG 40 Wire Cable with TB Holder connector, 26 AWG wires Hot swap replacement module extraction/insertion under voltage 2.5 kV RMS between input and module logic per IEC60255-5 Insulation resistance 100 M @ 500 V DC per IEC60255-5 10.8-16 V DC and 3.3 V DC (from the motherboard connector) Refer to Appendix C: ACE3600 Maximum Power Ratings. 37 mm W x 225 mm H x 180 mm D, (1.5 W x 8.7 H x 7.1 D)
16 DI: approx. 0.28 Kg (0.62 Lb); 32 DI: approx. 0.29 Kg (0.63 Lb)
120/230V 16DI Module
Total Number of Inputs Input Characteristics Input Arrangement AC Input Frequency
16 DI IEC 61131-2 Type 1 Two isolated groups of 6 inputs and one isolated group of 4 inputs. 47 63 Hz
189
AC Input Change Delay Max. DC Input Voltage DC Input Pulse Width ON DC Voltage Range OFF DC Voltage Range ON AC Voltage Range OFF AC Voltage Range Input Current
Maximum 25.0 msec Max. 264 V DC (relative to input common) Minimum 7.0 msec @ 230 V DC +79.0 V DC to +264.0 V DC, -79.0 V DC to -264.0 V DC -40 to +40 V DC 79 to 264 V AC (RMS) 0 to 40 V AC (RMS) At 110V DC At 230V DC At 110V AC At 230V AC 2.5 kV RMS 0 to 50.8 msec (DC, programmable in 0.2 msec steps) Note: Minimum effective filter value is 7.0 msec. Status LED per each input, module error LED 3 Terminal Blocks (5.00mm pitch), Maximum 14 AWG 30 Wire Cable with TB Holder connector, 20 AWG wires Hot swap replacement module extraction/insertion under voltage 2.5 kV RMS between input and module logic per IEC60255-5 Insulation resistance 100 M @ 500 V DC 10.8-16 V DC and 3.3 V DC 10% (from the motherboard connector) Refer to Appendix C: ACE3600 Maximum Power Ratings. 37 mm W x 225 mm H x 180 mm D, (1.5" W x 8.7" H x 7.1" D) approx. 0.367 kg (0.80 lbs) 1.0 to 3.0 mA 0.4 to 2.0 mA > 2.0 mA RMS > 3.0 mA RMS
Permitted Voltage Difference Between Groups Input Filtering Diagnostic LEDs User Connection Cable and TB Holder Module Replacement Input Isolation Input Insulation Operating Voltage Power Consumption Dimensions Weight
190
DO/DI FET Module Specifications

Total Number of I/Os I/O Arrangement 16 (Option V480); 32 (Option V481) Two or four group of 8 I/Os with shared common Each group can be configured as FET DO or dry contact DI Selectable combinations (32 DO/DI): 32 DO/ 8 DI+24 DO/ 16 DI+16 DO/ 24 DI+8 DO/ 32 DI Selectable combinations (16 DO/DI): 16 DO/ 8 DI+8 DO/ 16 DI The first 20 inputs (of the 32 DI) and all 16 inputs (of the 16 DI) can be used as counter inputs. 0 - 1 KHz, minimum pulse width 500 S. Note: Although filters are defined in steps of 0.2mSec and 0.05mSec, it is relevant only from 1mSec. Max. 30 V DC (relative to input common) 0-4 k 50 k 1 mS (Interrupt upon change of state) 1 mS (Interrupt upon change of state) Max. 0.3 mA (when the input is shorted) 0 to 50.8 mS (programmable in 0.2 mSec steps), minimum effective filter value - 1mSec 0 to 12.75 mS (programmable in 0.05 mSec steps), minimum effective filter value - 1mSec MOSFET 5-30 V DC (user supplied voltage) Max. 1 KHz (resistive load) Max. 500 mA sink current (resistive load) Configurable output state on CPU fail: On, Off or last value LED per each input / output status, module error LED 4 Terminal Blocks (3.5mm pitch), Maximum 18 AWG 20 or 40 Wire Cable with Terminal Block Holder connector, 26 AWG Hot swap replacement module extraction/insertion under voltage 1.5 kV between input/output and module logic Insulation resistance 100 M @ 500 V DC per IEC60255-5 10.8-16 V DC and 3.3 V DC (from the motherboard connector) Refer to Appendix C: ACE3600 Maximum Power Ratings. 37 mm W x 225 mm H x 180 mm D (1.5" W x 8.7" H x 7.1" D) Approx. 0.25 Kg (0.55 lb) Specifications subject to change without notice.
Counter Inputs Counter Input Frequency Max. DC Input Voltage Input ON Resistance Input OFF Resistance Fast Capture Resolution Event Time Tagging Resolution Input Current Input Filtering Counter Input Filtering Output Type Output Voltage Range DO Frequency DO Output Current Output Fail State Diagnostic LEDs User Connection Cable and TB Holder Module Replacement Input/Output Isolation Input Insulation Operating Voltage Power Consumption Dimensions Weight
191
DO Relay Module Specifications

8/16DO Relay EE/ML Modules
Total Number of Outputs
8 EE relay outputs (Option V508) 16 EE relay outputs (Option V616) 8 ML relay outputs (Option V314) 16 ML relay outputs (Option V516) 8 DO : 3 X Form C (SPDT) and 5 X Form A (SPST) 16 DO: 6 X Form C (SPDT) and 10 X Form A (SPST) Max. 60 V DC or 30 V AC RMS (42.4 V peak). 2A @ 30 V DC, 0.6A @ 60V DC or 0.6A @ 30V AC (resistive load) Contact position - hardware back indication Max. 10 Hz LED per each output status, module error LED 2 or 4 Terminal Blocks (3.5mm pitch), Maximum 18 AWG 20 or 40 Wire Cable with Terminal Block Holder connector, 26 AWG Configurable relay state on CPU fail: On, Off or last value Selectable per module, controlled from the power supply Hot swap replacement module extraction/insertion under voltage Between open contacts: 1kV, Between contact and coil: 1.5 kV, Between contact sets: 1.5 kV Insulation resistance 100 M @ 500 V DC per IEC60255-5, Insulation impulse 1.5 kV per IEC60255-5 10.8-16 V DC and 3.3 V DC (from the motherboard connector) Refer to Appendix C: ACE3600 Maximum Power Ratings. 37 mm W x 225 mm H x 180 mm D (1.5" W x 8.7" H x 7.1" D) 8 DO : approx. 0.29 Kg (0.64 lb) 16 DO: approx. 0.32 Kg (0.7 lb)
Output Arrangement Contact Voltage Ratings Contact Power Ratings Relay Back Indication DO Frequency Diagnostic LEDs User Connection Cable and TB Holder Fail State All Relays Disable/Enable Module Replacement Output Isolation
Insulation Operating Voltage Power Consumption Dimensions Weight
192
8 DO SBO Relay Modules
Total Number of Outputs Output Arrangement Contact Voltage Ratings Contact Power Ratings Relay Back Indication Relay Select Back Indication DO Frequency Diagnostic LEDs
8 EE relay outputs 2 X Form A (SPST) - (two Normally Open contacts per DO) Max. 60 V DC or 30 V AC RMS (42.4 V peak). 2A @ 30 V DC, 0.6A @ 60V DC or 0.6A @ 30V AC (resistive load) Contact Back Indication: Indicating Contact position Indicating relay selection before relay activation Max. 10 Hz LED per each output status, module error LED, Controlled DO LED Controlled DO LED states: a. OFF - 12V is not controlled. b. ON - 12V is controlled and exists. c. Blinking - 12V is controlled and does not exist. 4 Terminal Blocks (3.5mm pitch), Maximum 18 AWG 40 Wire Cable with Terminal Block Holder connector, 26 AWG Configurable relay state on CPU fail: On, Off or last value Selectable per module, controlled from the power supply Hot swap replacement module extraction/insertion under voltage Between open contacts: 1kV, Between contact and coil: 1.5 kV, Between contact sets: 1.5 kV Insulation resistance 100 M @ 500 V DC per IEC60255-5, Insulation impulse 1.5 kV per IEC60255-5 10.8-16 V DC and 3.3 V DC (from the motherboard connector) Refer to Appendix C: ACE3600 Maximum Power Ratings. 37 mm W x 225 mm H x 180 mm D (1.5" W x 8.7" H x 7.1" D) Approx. 0.29 Kg (0.64 Lb)
User Connection Cable and TB Holder Fail State All Relays Disable/Enable Module Replacement Output Isolation
Insulation Operating Voltage Power Consumption Dimensions Weight
193
120/230V 12DO Relay Modules
Total Number of Outputs Output Arrangement Contact Power Ratings Minimum Contact Load Current Maximum Switching Current Relay Back Indication DO Frequency Diagnostic LEDs User Connection Cable and TB Holder Fail State All Relays Disable/Enable Module Replacement Output Isolation Insulation Operating Voltage Power Consumption Dimensions Weight
12 EE relay outputs 12 ML relay outputs 12 x 1 Form A 3A @ 250 V AC, 3A @ 30 V DC, or 0.20A @ 125 V DC (resistive load) 10.0 mA @+5.00 V DC 3.00 A Contact position - hardware back indication Max. 10 Hz (resistive load) LED per each output status, module error LED 3 Terminal Blocks (5.00mm pitch), Maximum 14 AWG 30 Wire Cable with Terminal Block Holder connector, 20 AWG Configurable relay state on CPU fail: On, Off or last value Selectable per module, controlled from the power supply Hot swap replacement module extraction/insertion under voltage Between output and module logic 2.5 kV per IEC60255-5 Insulation resistance 100 M @ 500 V DC per IEC60255-5, Insulation impulse 5 kV per IEC60255-5 10.8-16 V DC and 3.3 V DC 10% (from the motherboard connector) Refer to Appendix C: ACE3600 Maximum Power Ratings. 37 mm W x 225 mm H x 180 mm D (1.5" W x 8.7" H x 7.1" D) approx. 0.423 kg (0.90 lbs)
194
AI Module Specifications
Total Number of Inputs 8 AI 20 mA (4-20 mA) (Option V318) 16 AI 20 mA (4-20 mA) (Option V463) 8 AI 5 V (0-5 V, 1-5 V) (Option V742) 16 AI 5 V (0-5 V, 1-5 V) (Option V743) Isolated (floating) analog inputs 16 bit (including sign) 0.1% full scale @ -40C to +70C 10 mSec @ 50 Hz filtering ;8.33 mSec @ 60 Hz filtering Selectable input averaging: 1,2,4,8,16,32,64,128 samples (x10 mS) 75 V DC, 60 V AC (RMS) 20 mA input: Rin < 250 5 V input: Rin > 1 M Better than 80 dB between any pair of inputs 25 PPM/C Selectable 50 or 60 Hz filtering, Common mode rejection > 100 dB, Differential mode rejection > 50 dB Supports optional isolated 24V plug-in Power Supply (one in 8 DI, two in 16 DI) Overflow and Underflow LED per each input status, Module error LED The module Overflow and Underflow levels can be configured to: Current inputs: 20mA / 4-20 mA Voltage inputs: 5 V / 0-5 V /1-5 V 2 or 4 Terminal Blocks (3.5mm pitch), Maximum 18 AWG 20 or 40 Wire Cable with TB Holder connector, 26 AWG Hot swap replacement module extraction/insertion under voltage 1.5 kV RMS between input and module logic, per IEC60255-5 Insulation resistance 100 M @ 500 V DC, per IEC60255-5 10.8-16 V DC and 3.3 V DC (from the motherboard connector) Refer to Appendix C: ACE3600 Maximum Power Ratings. 37 mm W x 225 mm H x 180 mm D, (1.5" W x 8.7" H x 7.1" D) 8 AI : approx.032 Kg (0.71 lb) 16 AI: approx. 0.34 Kg (0.75 lb)
Input Configuration A to D Resolution Input Accuracy Input Sampling Time Smoothing Permitted Potential Between Inputs Input Impedance Crosstalk Rejection Temperature Stability Interference Suppression
24 V DC Output Diagnostic LEDs
User Connection Cable and TB Holder Module Replacement Input Isolation Input Insulation Operating voltage Power Consumption Dimensions Weight
195
AO Module Specifications
Total Number of Outputs Output Arrangement D to A Resolution Output Accuracy Temperature Stability Internal Settling Time Output Load Crosstalk Rejection Interference suppression Output Protection Diagnostic LEDs User Connection Cable and TB Holder Module Replacement Isolation Insulation Operating voltage Power Consumption Dimensions Weight 4 AO current (0-20 mA) or voltage (0-10 V) Isolated floating channels, each channel can be connected as 0-20 mA or 0-10 V DC voltage 14 bit 0.1% full scale @ 25C 25 PPM/C Max. 1.0 msec Voltage: > 1.0 k, < 1.0 f Current: < 750 (internal power source) Better than 50 dB between any pair of outputs Common mode rejection > 60 dB Voltage output: short circuit current, max. 30 mA Current output: No-load voltage max. 22 V DC Module error LED, Voltage mode LED, Current mode LED, Calibration LED per channel 2 Terminal Blocks (3.5mm pitch), Maximum 18 AWG 20 Wire Cable with TB Holder connector, 26 AWG Hot swap replacement module extraction/insertion under voltage 1.5 kV between output and module logic Insulation resistance 100 M @ 500 V DC, per IEC602555 10.8-16 V DC and 3.3 V DC (from the motherboard connector) Refer to Appendix C: ACE3600 Maximum Power Ratings. 37 mm W x 225 mm H x 180 mm D, (1.5" W x 8.7" H x 7.1" D) Approx. 0.29 Kg (0.64 Lb)
196
Mixed I/O Module Specifications

Total Number of Inputs / Outputs 16 Digital Inputs + 4 EE Relay Outputs + 4 Analog Inputs ( 20 mA) (Option V245) 16 Digital Inputs + 4 ML Relay Outputs + 4 Analog Inputs ( 20 mA) (Option V453) I/O Arrangement 1 group of 16 DIs with shared common 4 relay outputs - Form C 4 isolated analog inputs The first 12 inputs can be configured as fast counters. 0 - 1 KHz 0 - 5 KHz, minimum pulse width 100 S Max. 40 V DC +11 to +30 V DC, -30 to -11 V DC -5 to +5 V DC 6-10 mA 1 mS (Interrupt upon change of state) 1 mS (Interrupt upon change of state)
0 to 50.8 mS (DC, programmable in 0.2 mSec steps) 0 to 12.75 mS (programmable in 0.05 mSec steps for inputs configured as high speed counters)
DI Counter Inputs DI Frequency DI Fast Counter Frequency DI Max. DC Voltage DI ON DC Voltage Range DI OFF DC Voltage Range DI Current Fast Capture Resolution Event Time Tagging Resolution DI Filtering DI Counter Filtering DO Contact Voltage Ratings DO Contact Power Ratings DO Relay Back Indication DO Fail State AI Resolution AI Accuracy AI Sampling Time AI Smoothing AI max. Potential between AIs AI Impedance AI Crosstalk Rejection AI Temperature Stability
Max. 60 V DC or 30 V AC RMS (42.4 V peak). 2A @ 30 V DC, 0.6A @ 60V DC or 0.6A @ 30V AC (resistive load) Contact position - hardware back indication Configurable relay state on CPU fail: On, Off or last value 16 Bit (including sign) 0.1% full scale @ -40C to +70C 10 mSec @ 50 Hz filtering 8.33 mSec @ 60 Hz filtering Selectable input averaging: 1, 2, 4, 8, 16, 30, 60 or 128 samples (x10 mS) 75 V DC, 60 V AC (RMS) Rin < 250 Better than 80 dB between any pair of inputs 25 PPM/C
197
AI Interference Suppression Diagnostic LEDs
Selectable 50 or 60 Hz filtering, common mode rejection > 100 dB, differential mode rejection > 50 dB Module error LED, Status LED per each DO and DI. Overflow and Underflow LED per each AI, 24V Plug-in status LED (AI) AI Overflow and Underflow levels can be configured to: Current inputs: 20mA / 4-20 mA Voltage inputs: 5 V / 0-5 V /1-5 V Supports one isolated 24V plug-in wetting power supply 4 Terminal Blocks (3.5mm pitch), Maximum 18 AWG 40 wire cable with Terminal Block Holder connector, 26 AWG Hot swap replacement module extraction/insertion under voltage DI: 2.5 kV RMS between input and module logic per IEC60255-5 DO: Between open contacts: 1kV, between output and module logic: 1.5 kV, per IEC60255-5 AI: 1.5 kV between input and module logic, per IEC60255-5 Insulation resistance 100 M @ 500 V DC per IEC60255-5 10.8-16 V DC and 3.3 V DC (from the motherboard connector) Refer to Appendix C: ACE3600 Maximum Power Ratings. 37 mm W x 225 mm H x 180 mm D (1.5" W x 8.7" H x 7.1" D) Approx. 0.31 Kg (0.68 lb)
24 V DC Output User Connection Cable and TB Holder Module Replacement Input/Output Isolation
Input Insulation Operating Voltage Power Consumption Dimensions Weight
198
Mixed Analog Module Specifications

Total Number of I/Os I/O Arrangement 4 Analog Outputs + 8 Analog Inputs ( 20 mA) or 4 Analog Outputs + 8 Analog Inputs ( 5V DC) AO - each channel can be connected as 0 -20 mA or 0-10 V, AI - Isolated (floating) analog inputs 14 bit 0.1% full scale @ 25C 25 PPM/C Max. 1.0 msec Voltage: > 1.0 k, < 1.0 f Current: < 750 (with internal power supply) Better than 50 dB between any pair of outputs Common mode rejection > 60 dB Short circuit protection, max. 30 mA (all other operating channels remain fully functional) Max. 22.0 V DC 1.5 kV between output and module logic Insulation resistance 100 M @ 500 V DC per IEC60255-5 16 Bit (including sign) 0.1% full scale 10 mSec @ 50 Hz filtering 8.33 mSec @ 60 Hz filtering Selectable input averaging: 1, 2, 4, 8, 16, 32, 64 or 128 samples (x10 mS) 75 V DC, 60 V AC (RMS) 20 mA input: Rin < 250 5 V input: Rin > 1 M Better than 80 dB between any pair of inputs 25 PPM/C Selectable 50 or 60 Hz filtering, common mode rejection > 100 dB, differential mode rejection > 50 dB Supports one isolated 24V Plug-in wetting power supply
AO D to A Resolution AO Accuracy AO Temperature Stability AO Internal Settling Time AO Load AO Crosstalk Rejection AO Interference suppression AO Voltage Output Protection AO Current Output No-load Voltage AO Isolation AO Insulation AI A to D Resolution AI Accuracy AI Sampling Time AI Smoothing Permitted. Potential between Inputs AI Input Impedance AI Crosstalk Rejection AI Temperature Stability AI Interference Suppression 24 V DC Output
199
Diagnostic LEDs
AO - Voltage mode LED, Current mode LED, Calibration LED per channel AI - Overflow and Underflow LED per each input, 24V Plug-in status LED The module Overflow and Underflow levels can be configured to: Current inputs: 20mA / 4-20 mA Voltage inputs: 5 V / 0-5 V /1-5 V General - Module error LED 1.5 kV between input and module logic Insulation resistance 100 M @ 500 V DC per IEC60255-5 4 Terminal Blocks (3.5mm pitch), Maximum 18 AWG 40 wire cable with Terminal Block Holder connector, 26 AWG Hot swap replacement module extraction/insertion under voltage 10.8-16 V DC and 3.3 V DC (from the motherboard connector) Refer to Appendix C: ACE3600 Maximum Power Ratings. 37 mm W x 225 mm H x 180 mm D (1.5" W x 8.7" H x 7.1" D) Approx. 0.34 Kg (0.75 Lb)
AI Input Isolation AI Input Insulation User Connection Cable and TB Holder Module Replacement Operating Voltage Power Consumption Dimensions Weight
200
Expansion Power Supply Module Specifications

Input Voltage Outputs Over Current Protection Maximum Current via Power IN/OUT circuit Over Voltage Protection Absolute Maximum Voltage Dimensions Weight DC 10.8-16 V To Motherboard connector +10.80 to +16.00 VDC, max. 4A To cascaded expansion power supply - +10.80 to +16.00 VDC, max. 8A 4.0 A (Slow blow fuse), protecting the expansion frame 8.0 A (Slow blow fuse), protecting the cascaded expansion power supply 8.0 A (Slow blow fuse)
+17.00 1 VDC (protecting the expansion frame) +18.00 VDC 56 mm W x 225 mm H x 180 mm D (2.2" W x 8.7" H x 7.1" D) Approx. 0.43Kg (0.94 Lb)
201
Expansion Module Specifications

Microprocessor Microprocessor Clock Serial Port Ethernet Port LAN Cable LEDs Display Power Consumption Operating Voltage Dimensions Weight Freescale Power PC II, MPC8270, 32-bit 200 MHz RS232C Asynch, Full Flow Control port, up to 230.4 kb/s; used for STS only 10/100 Mb/s connection to the main frame Category 5E shielded (FTP), up to 50 meter 4 CPU diagnostic LEDs, Port status LEDs and Expansion Address LEDs Refer to Appendix C: ACE3600 Maximum Power Ratings. 10.8-16 V DC (from the motherboard connector) 56 mm W x 225 mm H x 180 mm D (2.2" W x 8.7" H x 7.1" D) Approx. 0.38 Kg (0.84 Lb) TBD
202
Expansion LAN Switch Specifications

Ethernet Port 1-8 LEDs Display Power Consumption Module Replacement Operating Voltage (from the motherboard connector) User Connection (Ethernet Ports) LAN Cable Dimensions Weight 8 on board 10/100 Mb/s Ethernet ports (Auto crossover) Error LED, Port status LEDs Refer to Appendix C: ACE3600 Maximum Power Ratings. Hot swap replacement module extraction/insertion under voltage 10.8-16 V DC, 3.30 VDC +/-10% 8 shielded RJ45 connectors Category 5E shielded (FTP), up to 50 meter 37 mm W x 225 mm H x 180 mm D (1.5" W x 8.7" H x 7.1" D) Approx. 0.32 Kg (0.7 Lb)
203
ACE IP Gateway Module (CPU 4600) Specifications

Microprocessor Microprocessor Clock Memory Real-Time Clock Freescale Power PC II MPC8270, 32-bit, extended communication capability, DMA and floating point calculation support 200 MHz Flash: 32 MB SDRAM: 128 MB Full calendar with leap year support (year, month, day, hours, minutes, seconds). Time drift: max. 2.5 Seconds per day (when power is on) 3 V Rechargeable lithium backup battery Configurable RS232 or RS485 port: - RS232: Asynch, Full Flow Control, up to 230.4 kb/s, GPS receiver interface - RS485, multi-drop 2-Wire up to 230.4 kb/s RS232, Asynch, Full Flow Control, up to 230.4 kb/s, GPS receiver interface
RTC Retention Serial Port 1
Serial Port 2
Ethernet Port 1
Plug-In Port 1
10/100 Mb/s
Supports the following plug-in ports: - Radio Modem, DPSK 1.2 kb/s, FSK 1.2/1.8/2.4 kb/s, DFM 2.4/3.6/4.8 kb/s - RS232, Sync/Asynch, Full Flow Control, up to 230.4 kb/s, GPS receiver interface - RS485, multi-drop 2-Wire up to 230.4 kb/s - Ethernet 10/100 Mb/s Supports the following plug-in ports: - Radio Modem, DPSK 1.2 kb/s, FSK 1.2/1.8/2.4 kb/s, DFM 2.4/3.6/4.8 kb/s - RS232, Sync/Asynch, Full Flow Control, up to 230.4 kb/s, GPS receiver interface - RS485, multi-drop 2-Wire up to 230.4 kb/s - Ethernet 10 Mb/s Type A host full speed 12 Mbs ports (HU1 on left and HU2 on right) for MDLC over IP communication via the MotoTrbo digital mode radio system USB Device port (for future use) 4 CPU diagnostic LEDs and Port status LEDs Refer to Appendix C: ACE3600 Maximum Power Ratings. 10.8-16 V DC (from the motherboard connector) 56 mm W x 225 mm H x 180 mm D (2.2" W x 8.7" H x 7.1" D) Approx. 0.38 Kg (0.84 Lb)
Plug-In Port 2
USB Host Port 1, 2 USB Device Port 1 LEDs Display Power Consumption Operating Voltage Dimensions Weight
204
Appendix B - FCC Information Spectrum and Regulatory Update

The Federal Communications Commission (FCC) has made a series of changes over the years to the rules and regulations that govern the use of frequencies that constitute the VHF and UHF bands. They affect in several ways how MOSCAD devices are used on traditional, conventional two-way radio channels. This update is a summary document and not intended as a complete licensing guide. Refer to the FCC rules or other applicable regulations for additional information or requirements. This summary will cover: FCC Rules Updates Licensing of Fixed Data Systems Spectrum available for Fixed Data Systems
FCC Rules Update

Refarming and Narrow Banding
In the mid 90s, the FCC began implementing a plan to increase the capacity and promote spectrum efficiency within the VHF and UHF frequency bands, 150MHZ to 512 MHz. The rule changes established a channel plan that includes 25 kHz channels (the original legacy channels), 12.5 kHz channels, (the old offset frequencies) and 6.25 kHz channels. Users could, and until January 1, 2011 can still, license at all three bandwidths. The FCC instituted a minimum data efficiency standard of 4800 bps per 6.25 KHz (9600 bps per 12.5 kHz). In the initial decision, the FCC declined to establish deadlines for existing users to convert systems to 12.5 and/or 6.25 kHz technologies, deciding instead to manage the narrowband conversion through the equipment certification process (type acceptance). Starting in January 1997, all new radio designs submitted for FCC approval by radio manufacturers were required to include a 12.5 kHz operational mode. Dual mode 25 kHz and 12.5 kHz designs were also permitted and manufacturers could continue to sell previously approved radios that only contained a 25 kHz mode of operation. Existing users/licensees of 25 kHz equipment were not mandated to migrate to narrowband operation.
UHF Offset Channels

Prior to the FCCs adoption of refarming, FCC Rule Section 90.267 allowed for the use of 25 kHz bandwidth offset channels in the 450-470 MHz band. These were channels offset 12.5 kHz from the primary UHF channels and limited to 2 watts ERP and antenna heights of 20 feet. The offset channels supported 25 kHz wide transmissions. These
205
were channels licensed for data (or voice) use on a secondary basis; that is usage could not interfere with operations licenses on the primary channels. Through the adoption of the refarming decision, the low-power, secondary offset channels have been converted to primary channels with a maximum bandwidth of 12.5 kHz. Many of the old offset channels have been (or soon will be) converted to high power operations. However, a fairly large number of these channels have been designated for continued low power use and can be a good source of spectrum for some MOSCAD systems. More about this in the Spectrum section.
VHF Splinter Channels

The FCC had defined certain frequencies in the 154 MHz and 173 MHz bands for data operation. The frequencies are few in number, are heavily used and have severe deviation restrictions. These splinter frequencies, whose availability and use were not affected by refarming, require the use of a radio certified with a less common F2 emission designator (digital FM emission with a modulated subcarrier). A few radios may be used with MOSCAD for these frequencies, but refer to the FCC rules for limitations on power output, antenna height and antenna gain.
Emission Designators
MOSCAD units interface to the radio through several different modems, typically DFM, FSK or DPSK. The nature of these modems will determine the type of emission characteristics of the radio. FCC rules define and classify the basic characteristics of the radio waves according to the type of modulation of the main carrier as well as the nature of the signals that modulate the main carrier and the general type of information that is transmitted (see FCC rule sections 2.201 and 90.207) 1 . Traditional MOSCAD radios such as a MTS2000 use FM modulation (indicated by the FCC emission designator F), operate in the analog mode (indicated by the FCC emission designator -3) and are used for voice (telephony) (indicated by FCC emission designator E), or Data, (telemetry, or telecommand) (indicated by emission designator D). Hence, a radio used for DPSK or FSK could use a F3E or F3D designation whereas a DFM application would require a F1D to reference a digital FM signal containing digital information. See section below on data efficiency.
Data Efficiency Standards

As part of its initial refarming decisions, the FCC adopted a new minimum data efficiency standard of 4800 bits per second per 6.25 kHz of channel bandwidth. Initially, the FCC definition of data was not clear and caused confusion as to how the standard was
1
FCC Rules can be found in Title 47 of the Code of Federal Regulations. Part 90 of that title provides rules applicable to the private land mobile radio services. Among other things, Part 2 of that title provides rules governing the equipment authorization process. Current FCC rules can be found at this web site: http://wireless.fcc.gov/rules.html
206
to be applied. In a subsequent decision, (FCC MO&O96-492) the FCC clarified their intent and restated the previous classes of data operations. Key to the issue of the type of operation is determining the actual path of the signaling through the radio. The FCC acknowledged a difference between signals that pass through a radios external microphone port and those that do not. The former path, since it includes FCCproscribed audio filters does not have to meet the data rate standard. The interpretation of this statement however still allows for some confusion. If the signal is not required to meet the data efficiency standard, is it still considered data? The consensus opinion is that it is audio and can be considered as telephony, and not telemetry. This seemingly minor detail consideration is important, since it will influence what radio or model of radio that can be used. All Motorola radios carry a F3E designator, not all of them are also certified for F3D or F1 or F2 operation. This interpretation says MOSCAD can use radios only certified for F3E operation. This opinion is based on the consideration that the source of the signal whether microphone or tone modem (MOSCAD) is of concern to the user of the system, but not the licensing party whose only concern is the type of signal, not content. Note however, that this opinion and the FCC stop short of considering this type of signaling used by MOSCAD as voice except for the express purpose of satisfying the data efficiency standards.
Narrowbanding Update
The FCC set dates for mandatory moves to narrowband channels in February 2003. In December 2004, in response to several Petitions for Reconsideration, they modified the deadlines as follows: No new applications for operations using 25 kHz channels after 1/1/11 unless they meet the 12.5 kHz efficiency standards 2 . No modifications to existing 25 kHz systems that exceed existing interference contours after 1/1/11 unless the equipment meets the 12.5 kHz efficiency standard 3 No equipment capable of 1 voice path per 25 kHz will be certified beginning 1/1/05. (Deadline stayed as of 12/22/04 until FCC rules on issues raised in Third Further Notice in WT Docket 99-87) No manufacture or importation of 25 kHz equipment beginning 1/1/11 unless it meets the 12.5 kHz efficiency standard 4 . Mandatory migration to 12.5 kHz technology: o Non-Public Safety 1/1/13 o Public safety 1/1/13
2 3
One voice channel per 12.5 khz of bandwidth or 4800 bits per second per 6.25 kHz of bandwidth for data Ibid 4 Ibid
207
In February of 2003, the FCC asked for comments on its tentative conclusion that transition dates for 6.25 kHz conversion would have to be adopted. Many commenters said that it was too soon to establish a date for conversion to 6.25 kHz technologies; there is no interoperability standard for 6.25 kHz equivalent technologies and equipment has not been fielded and tested under real world conditions. The FCC has not yet made a decision, but transition deadlines may be issued for conversion to 6.25 kHz technology.
Licensing of Fixed Data Systems

There are a few important considerations when applying for a license for a MOSCAD system. 1. Location Description Code: Fixed, unless applying for certain frequencies that allow Mobile designations to be used for fixed sites, typically with power and/or antenna restrictions. Various Motorola radios can be licensed as mobile, but the MOSCAD units are almost always at fixed, permanent locations. 2. Define operations as telephony, transfer of analog information from one to multiple sites. 3. If the User is a Public entity, use the appropriate frequencies listed in the Public Safety Pool.
Spectrum Available for Fixed Data Systems

UHF Low Power Pool
There are several options available for licensing Fixed Data systems. One of the possible good ones is the new low power pool. In March of 2003, the FCC adopted new LMCC low power pool recommendations. These frequencies come from the old UHF offset channels and are grouped into five subsets, all 12.5 kHz. They are defined as: Group A Campus type systems Group B Data primary operations such as crane control Group C - Uncoordinated, itinerant use such as construction Group D Central Station protection operation Public Safety
Using these low power pool channels, MOSCAD can be licensed as mobile, defining the service area by KMRA of set of coordinates. You must observe the mobile power restrictions. Fixed use on these channels is considered primary status unlike the old rules where data was secondary.
208
Low Power Pool Group Specifications

Limitation Group A Group B Group C Group D Public Safety
# Channels
39 pairs, 1 unpaired Group A1; 10 pairs Group A2 Co-Primary A1 within 50 miles of Top 100 cities; A2 Nationwide 20 watts* 6 watts* 2 watts* N/A 75' Yes No
10 pairs
21 pairs, 4 unpaired
5 pairs
14 pairs
Data Low Power
Primary Nationwide
Co-Primary Nationwide
ERP Base ERP Mobile ERP Portable TPO Antenna Height to Tip Frequency Coordination Itinerant
6 watts 6 watts 2 watts N/A 20' Yes No
6 watts 6 watts 2 watts N/A 20' No Yes
N/A N/A N/A 2 watts 20' Yes No
6 watts 6 watts 2 watts N/A 20' Yes No
*Outside 50 MIRA of top 100 cities, these frequencies can be used at full power, up to 500 watts (90.205)
For Public Safety Operations, the following frequencies are available nationwide:
453/458.0375 453/458.0625 453/458.0875 453/458.1125 453/458.1375 453/458.8875 453/458.9125 453/458.9375 453/458.9625 453/458.9875 460/465.4875 460/465.5125 460/465.5375 460/465.5625
Fixed stations may be licensed as mobiles Base station maximum antenna height to tip: 20 Operational fixed, base and mobile maximum ERP: 6 watts Portable maximum ERP: 2 watts
209
Other Part 90 Frequency Options

There are several other options that could be used depending on the availability of frequencies or existing infrastructure. Section 90.235 Secondary fixed signaling UHF or VHF high power bands. The fixed operations are secondary to mobile voice or data operations and must be licensed as part of the voice system. No additional channels can be added to accommodate the fixed operations. 800 or 900 MHz private or commercial trunked systems Fixed data can be added to existing trunked systems, although they do not count toward channel loading. 700 MHz Guard band systems Fixed data can be added to existing trunked systems although they do not count toward channel loading. 700 MHz Public Safety systems NPSTC (National Public Safety Telecommunications Council) is seeking a clarification from the FCC as to whether fixed data is permitted in the 700 MHz band in the same manner it is permitted in the 800 MHz band. ASTRO 25 Digital Trunked Systems with Data option. Starting with release 6.3, MOSCAD data systems can be added to this digital trunked infrastructure. There are some differences in operation than with analog, so check with the MOSCAD product group for details.
210
Appendix C: ACE3600 Maximum Power Ratings

The tables below list the typical maximum power consumption (at room temperature) for each of the ACE3600 RTU building blocks (CPU, Power Supply, I/O modules, radios, etc.) and the maximum peak power allowed for a fully loaded RTU, based on the housing type. The values in the tables below are derived by using the power supply (AC: 100 to 240 VAC or DC: 18 to 72 VDC and 13.8 VDC) and have the power supply efficiency factor included in them. Before deploying your RTU, add up the power consumption of all components of your system to verify that it is within the maximum peak power for your housing type. In systems with I/O expansion, consider all modules which consume power from their respective AC/DC main power sources when calculating the required power requirements.
Table C-1 Maximum Peak Power Allowed for Fully Loaded RTU
Housing Type Description 19" Rack (w/out metal enclosure) Large NEMA metal housing (50x50 cm) Small NEMA metal housing (40x40 cm) Maximum Input Power into Power Supply Module (Watts) 100 120 105
Table C-2 Power Consumption per RTU Module

Self Power Consumption, no active I/O (Watts) Maximum Power Consumption, per Active I/O (Watts) Self Power Consumption, no active I/O (Watts) Vin = +13.8 VDC 2.20 (156 mA) (12 VDC Power Supply Module ONLY) 0.0 Maximum Power Consumption, per Active I/O (Watts) Maximum Power Consumption, all I/Os, LEDs Active (Watts)
Module Name
AC: 100 to 240 VAC DC: 18 to 72 VDC Power Supply (maximum) Power Supply (Expansion) 12.60 N/A
N/A
N/A
0.0
N/A
N/A
N/A
NOTE: When powered at Vin = 100VAC, the maximum input power of the power supply module is limited to 80 Watts ONLY.
211
Module Name
Self Power Consumption, no active I/O (Watts)
Maximum Power Consumption, per Active I/O (Watts)
Self Power Consumption, no active I/O (Watts) Vin = +13.8 VDC 4.20 (304 mA) 4.20 (304 mA) 1.20 (87 mA)
Maximum Power Consumption, all I/Os, LEDs Active (Watts)
AC: 100 to 240 VAC DC: 18 to 72 VDC CPU (3640/3610 ** ) Expansion Module Expansion LAN Switch Digital Input Fast 24V (x16/x32) Digital Input Fast 24V IEC Type 2 (x16/x32) Digital Input Fast 48V (x32) Digital Input 120/230V Digital Output ML Relay (x8/x16) Digital Output EE Relay (x8/x16) Digital Output SBO EE Relay (x8) Digital Output ML Relay 120/230V Digital Output EE Relay 120/230V 0.100 0.015 5.20 5.20 1.50 N/A N/A 0.220 0.100 (powered by internal 24V PS) 0.230 (powered by internal 24V PS)
N/A N/A 0.176 (12.75 mA) 0.100 (7 mA) (powered by internal 24V PS) 0.230 (17 mA) (powered by internal 24V PS)
4.00 (290 mA) 4.00 (290 mA) 3.10 (225 mA) (x8 ports ON) 3.50 (254 mA) (x32 inputs ON powered by x1 internal 24V PS) 8.20 (594 mA) (x32 inputs ON powered by x2 internal 24V PS) 3.50 (254 mA) (x32 inputs ON) 0.524 (38 mA) (x16 inputs ON) 0.483 (35 mA) (x16 relays ON) 3.26 (236 mA) (x16 relays ON) 3.26 (236 mA) (x8 relays ON) 0.248 (18.0 mA) (x12 relays ON) 3.12 (226 mA) (x12 relays ON)
0.100
0.080 (5.8 mA)
0.100
0.080 (5.8 mA)
0.100
0.100
0.080 (5.8 mA)
0.100 (7 mA)
0.080 (5.8 mA)
0.012 (1 mA)
0.120
0.010
0.100 (7.2 mA)
0.008 (0.5 mA)
0.170
0.200
0.136 (10 mA)
0.160 (11.6 mA)
0.170
0.400
0.136 (10 mA)
0.320 (23.2 mA)
0.200
0.006
0.160 (11.6 mA)
0.005 (0.4 mA)
0.290
0.260
0.232 (17 mA)
0.210 (0.15 mA)
**
The CPU 3610 model is discontinued.
212
Module Name
Self Power Consumption, no active I/O (Watts)
Self Power Consumption, no active I/O (Watts) Vin = +13.8 VDC
Maximum Power Consumption, all I/Os, LEDs Active (Watts)
AC: 100 to 240 VAC DC: 18 to 72 VDC FET Digital Output/Digital Input DI = 0.014 (per input channel) DO = 0.014 (per output channel)
DI = 0.011 (per input channel) 0.100 (7.2 mA) DO = 0.011 (per output channel) DI = 0.250 (powered by internal 24V PS) DO = 0.008
0.120
0.552 (40 mA) (x32 LEDs/ inputs ON) 4.70 (341 mA) (x4 relays ON x16 inputs ON x4 AI ON powered by internal 24V PS) 5.50 (400 mA) (x4 relays ON x16 inputs ON x4 AI ON powered by internal 24V PS) 3.33 (241 mA) (x4 outputs sourcing 20.0 mA) 3.61 (261 mA) (x4 outputs sourcing 20.0 mA) 0.870 (63.0 mA)
Mixed I/O (DO ML +DI IEC Type 2)
0.480
DI = 0.250 (powered by internal 24V PS) DO = 0.010
0.384 (28 mA)
Mixed I/O (DO EE + DI IEC Type 2)
0.480
DI = 0.250 (powered by internal 24V PS) DO = 0.200
0.384 (28 mA)
DI = 0.250 (powered by internal 24V PS) DO = 0.160 0.480 (35 mA) (per output channel @20.0 mA) 0.480 (35 mA) (per output channel @20.0 mA) N/A
Analog Output
1.10
0.600 (per output channel @20.0 mA) 0.600 (per output channel @20.0 mA)
0.880 (64 mA)
Mixed Analog Current/Voltage Analog Input Current/Voltage (x8/x16) 24V Floating Plug-In Power Supply (No load) 24V Floating Plug-In Power Supply (externally loaded 150 mA)
1.40
1.12 (81 mA)
0.530
N/A
0.440 (32.0 mA)
0.410
N/A
0.328 (24 mA)
N/A
N/A
4.80
N/A
3.84 (278 mA)
N/A
N/A
213
Accessory Box Interface

Audio Control and Tone (ACT) Module
Power when all Typical I/Os are on Power (Watts) (Watts) AC: 100 to 240 VAC DC: 18 to 72 VDC
0.60 2.20
Typical Power (Watts)
Power when all I/Os are on (Watts)
Vin = +13.8 VDC

0.480 (35 mA) 1.76 (127.50 mA)
Radios
Power in RX Power in TX Mode Mode (Watts) (Watts) AC: 100 to 240 VAC DC: 18 to 72 VDC
8.80 8.80 1.20 66.90 66.90 9.90
Power in RX Mode (Watts)
Power in TX Mode (Watts)
Vin = +13.8 VDC

7.10 (515 mA) 7.10 (515 mA) 1.00 (72.5 mA) 53.50 (4.0 A) 53.50 (4.0 A) 8.00 (580 mA)
XTL5000 (15 Watt) XTL2500 (15 Watt) XTS2500 (3 Watt) HT750/GP320/PR O5150/GP328 (UHF 4 Watt/ VHF 5 Watt) CM200/CM140/E M200/GM3188 (UHF 20 Watt/ VHF 25 Watt) GM328/338/339/3 40 (UHF 20 Watt/ VHF 25 Watt) CDM750 (UHF 20 Watt/VHF 25 Watt) XPR4350/4380 DM3400/ XiR M8220/ DGM4100 (UHF 20 Watt/ VHF 25 Watt)
0.70
13.10
0.560 (40.6 mA)
10.50 (761 mA)
3.70
75.10
3.00 (217 mA)
60.00 (4.40 A)
3.60
73.20
2.90 (210 mA)
59.00 (4.3 A)
3.90
74.50
3.20 (232 mA)
60.00 (4.40 A)
10.50
51.5
8.4 (600 mA)
41.5 (3 A)
214

ACE3600 System Planner 2011

Uploaded by

Copyright:

Available Formats

ACE3600 System Planner 2011

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

ACE3600 System Planner 2011

Uploaded by

Copyright:

Available Formats

System Planner

ACE3600 System Overview

ACE3600 System Overview

The Front End Processor (FEP):

ACE3600 RTU Construction

ACE3600 RTU Construction

No I/O slot frame Basic (default) model. Can be installed on a wall.

2 I/O slot frame Can be installed on a wall.

3 I/O slot frame Can be installed on a wall.

5 I/O slot frame Can be installed on a wall.

7 I/O slot frame Can be installed on a wall.

8 I/O slot frame Can be installed on a wall or in 19" rack/enclosure.

ACE3600 RTU Construction

ACE3600 RTU Construction

ACE3600 RTU Construction

19 Metal Back Installation Combinations

ACE3600 RTU Construction

Power Supply Modules

ACE3600 RTU Construction

12V Backup Battery

Terminal Blocks (TB)

Terminal Block (TB) Positioner Screw

Terminal Block (TB) Positioner

Code Key TB Holder I/O Module

Digital Input Modules

Digital Input Modules

DC or AC operation Fast Capture DI Filter (DC)

DC Disabled 50 (10 mS)

Module Input Module

in Fast 24V IEC TYPE II modules only DC

Digital Input Modules

Low Voltage DI I/O Circuit Diagram:

DI - Typical Input Circuit

Current 3.5mA Limiter

Digital Input Modules

16 DI Module Block Diagram:

Digital Input Modules

32 DI Module Block Diagram:

Digital Input Modules

Low Voltage DI I/O Connection Diagram:

DIx (input x) Dry Contact Sensor COM (common)

External Wetting Source

+ External Wetting Source + Wet Sensor DIx (input x) COM (common)

DIx (input x) Dry Contact Sensor +24V (Plug-in PS)

Digital Input Modules

High Voltage DI I/O Circuit Diagram:

High Voltage DI - Typical Input Circuit

Digital Input Modules

16 DI 120/230V Module Block Diagram:

DI7 DI8 DI9 DI10

DI11 DI12 COM 7-12

DI13 DI14 DI15 DI16

Digital Input Modules

16 DI 120/230V I/O Connection Diagram:

DIx (input x) AC / DC Signal Source COM (Common)

Digital Output Relay Modules

Digital Output Relay Modules

Digital Output Relay Modules

DO Keep Last Value & PreDefined Value DO Mask

KLV/PDV PDV = 0/1 No /Yes