To connect to an RTU locally via your computer's communications port, follow the steps as described below:
Note: While Alarmware™ is connected to an RTU via the com port, all outgoing calls that the RTU might normally make will be held off until the end of the com port session.
Troubleshooting: If the unit does not make connection (usually indicated by a box that says, "session concluded, transaction failure"):
Recorded speech data is a special case, because as a practical matter, recorded speech data comprises a much larger block of data than other configuration data. If there is a discrepancy only with respect to recorded speech data, you will get a dialog box that allows you to import or export for reconciliation as described above. However, due to the very large amount of data and transfer time involved, you will be given a third choice, to do nothing and proceed with the session.
The speech message import process can take up to 2 hours via modem or preferably about ½ hour via serial port connection to the RTU at 57,600-baud speed. While you may choose to defer this step initially, It is good defensive practice to have recorded speech data so saved, to avoid need to re-record messages if some unusual event requires restoration of the recorded speech data.
Note: At the end of any Alarmware™ online session, if there are any unacknowledged or acknowledged alarms, they will be automatically cleared out (corresponding to what otherwise happens when the respective Alarm Reset Timers time out). Then, if there are any alarm criteria violations existing, after the respective Alarm Trip Delays elapse, new unacknowledged alarms will be created.