|
Feature Summary  Following is a summary of some of the features of the RTU:
 Contact Closures. These are referred to as Digital I/O ports in the documentation. Each port can individually be configured as input or output via software command
Relay Output Ports. The output relays allow the RTU to switch other devices. The relays retain their state even if power to the RTU is lost
Analog Input Ports. The analog input ports can handle up to 70V DC, or 4-20mA Current. Each analog input port can be individually switched between voltage and current measurement. This is done by means of a hardware switch inside the RTU. When measuring direct voltage, the sensitivity of the A/D converter can be increased (via software command) for smaller voltage ranges
Temperature Sensors. Each RTU has an internal temperature sensor and an external temperature sensor. These sensors are supplied standard with every RTU
Power Fail Detection. If an RTU is connected via an Ethernet network, the RTU will send a notification if it detects a loss of power
Power Source. The RTU can be purchased for 12V DC, 24V DC, 48V DC, or auto-ranging mains AC
Port customization. Each port in the RTU has many individual settings that can be customized (via software command or the front panel) by users to meet their specific requirements. Each port has 3 labels that are sent with each notification, alarm condition, historic indicator, duty cycle collection, hysteresis settings, zoom values and other settings
On Board Web Server. The RTU has an HTTP web server on board. The embedded web pages are small and make it quick and easy to investigate current port status and logged information, even over a slow dialup connection
On Board Logging. The RTU stores log information on board. Three logs are available: Audit, Events, and Timed. The Audit log records changes to configuration, dialup attempts etc. The Events log records alarm history. The Timed log can be used to store snapshots of individual ports at regular intervals, e.g. the battery voltage every 5 minutes. The logs can be extracted from the RTU and stored in a database or spreadsheet for further manipulation, analysis, graphing, etc
Duty Cycle Collection. The RTU will collect duty cycle information for all ports. The Duty Cycle gives the amount of time that a port has been active / in alarm since the Duty Cycle was last reset for that port
Scripting. A scripting engine enables users to write simple scripts that allow the RTU to take action independently, without external intervention. As an example, if it is getting warm the RTU will send a notification in the normal manner, but it can be scripted to also activate a relay output that is connected to a cooling fan
Acknowledgement of Notifications. SNMP and email do not have a built in mechanism for confirming delivery to their destination. The RTU implements a simple strategy for acknowledgement, reducing the possibility of notification messages being lost in the network (Ethernet connected RTUs only)
Failover Options. If the RTU is primarily to be connected via Ethernet and an external modem (leased line, PSTN, GSM, or CDMA) is supplied, the RTU can be configured to use the external modem when it detects a failure of the Ethernet link
Initiating a Dialup. If an RTU is connected via external modem, the RTU will only dial into the Operations Center when a new event occurs (i.e. a notification needs to be sent). It is always possible for staff at the Operations Center to dial into the RTU at any time
Dialup Configurable to Prevent Blocking. Where an RTU is connected via dialup, it can be configured to prevent it blocking the communications lines. Communications lines can be blocked by a device continuously re-dialing when it encounters an intermittent problem. Once an RTU has connected successfully with the Operations Center, it will wait for some time before it dials in again, even if a notifiable event takes place. You specify the number of minutes to wait in a configuration setting. This feature is disabled by setting the number of minutes to zero
Nine Levels of Priority. Each port can be assigned a priority level from 1 to 9. For dialup RTUs, only events on ports with priority levels 1 to 3 will cause the RTU to initiate a dialup connection
Local Time. The time in the RTU is stored in GMT. This allows the time to be viewed correctly in multiple time zones. A user may also choose to view the time (e.g. timestamps on logs) in another user’s time zone to facilitate easier discussion
Pass Thru. This feature allows legacy, serial-based equipment to be connected to an RTU. Management software in the Operations Center can then communicate with the legacy equipment via the RTU
Firmware Updates. It is possible to update the networking software over the IP network using UDP protocols
No Moving Parts. The RTU has no moving parts. Moving parts reduce the life expectancy of a device. There are no cooling fans (not even on the processors), hard disks, belts or other moving parts
Analog Port Calibration. User calibration of analog ports can be carried out using the GUI software, making it quick and easy. Calibration can also be carried out using the front panel
Passwords. It is possible to set separate passwords for administrators and operators. If the passwords are enabled, configuration settings can only be altered by administrators, and commands can only be sent by operators and administrators
Front Panel Lockout. It is possible to lock out the front panel so that settings cannot be altered on site. When locked out the front panel still gives operator feedback. The panel can be unlocked by entry of the administrator password or via use of a once-off override PIN
IP Connection Status. If an RTU is connected (via Ethernet or dialup) it will display the IP address in the run-time information area of the front panel. If there is no connection, the entry remains blank
Notifications Queue. If a notifiable event occurs but the RTU is unable to communicate (e.g. it cannot establish IP), it will queue the notifications until communication can be established so notifications will not be lost
SNMP. The RTU is compatible with SNMPv2c and tables. The IP ports and community strings are configurable
ARA Indicators. The RTU, and each port of the RTU, has an ARA indicator. ARA means Alarm Receiving Attention. If a technician is working on an alarm, it is possible to turn on the indicator to notify others that the problem is being investigated
Historic Alarm Indicators. Each port can be configured to maintain an indication that an alarm condition occurred even though it is no longer present. This indication is useful to trigger investigation of potential problems especially when alarms are fleeting
Alarms and Duty Cycles. Each port can be configured to trigger an alarm event and / or duty cycle collection separately. In some cases you may want to monitor how long a device (e.g. generator) has been active, even though the usage of the device itself is not an alarm condition
Virtual Ports. The scripting feature of the RTU allows virtual ports (they are ports defined only in software) to be used as inputs or outputs. When used as inputs they can generate alarms based on combinations of external inputs; when used as outputs they can be used as timers to activate external outputs
Audible Alarm Indication. For manned sites, an audible alarm can be selected to attract attention
Visual Alarm Indication. For manned sites, the RTU can be made to flash with high visibility to attract attention
Front Panel Display And Buttons. The backlit LCD display and front panel buttons allow technicians to configure and work on the RTU on site without needing laptops or other devices
Connecting to a Network. The IP address and settings of the RTU are entered via the front panel, making it very easy to connect an RTU to the network
Alarm Outputs. The RTU comes with external relay outputs that are activated when the RTU is in Alarm and ARA (Alarm Receiving Attention) states. RTUs can also be wired together and with other devices to place them into ARA state from one point
Fully Open Standards. The RTU utilizes XML and the HTTP protocol for its communication. No proprietary protocols are used. All commands, file formats, etc are published on the Downloads page of this web site and can be used by clients to develop customized GUIs and interfaces
Installation and Configuration. All settings can be entered through the GUI and almost all settings (script is an exception) can be entered through the easy-to-use front panel. The GUI is graphical and intuitive
Customizable Solution. In some instances the RTU firmware has been customized to meet specific customers’ needs
| 
