# Connect to RTU using COM Port and Serial Cable

To connect to an RTU locally via your computer's communications port, follow the steps as described below:

1. If you have not done so already, start Alarmware™.
2. Choose an existing RTU from the list, or add a new RTU via the Add button.
3. Make a physical cable connection between your computer's Com Port and the Alarmware™ connection port on the RTU. See Alarmware™ Serial Port Connection.
4. Click on the Connect Com Port button.
5. Alarmware™ will attempt to connect to the RTU. If the unit is ready to accept Com Port access, you should be able to make the connection rather quickly.
6. Upon establishing connection with the RTU, if PINs have been configured for this RTU, you will be prompted to enter a valid PIN of at least "Program" privilege level. Exception: If you have previously entered a PIN in the special Retained Alarmware™ PIN dialog box and the "Save PIN for future use" box has been checked, the entry of that PIN will be done automatically by Alarmware™.
7. Alarmware™ then checks for agreement between the configuration in its database and the configuration of the RTU.
8. If there is any mismatch, you will be presented with a choice of either importing the RTU current configuration into Alarmware™, or exporting the Alarmware™ configuration to the RTU. You must do one or the other before you will be able to proceed with the session.

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"):

1. Verify that the basic information is correct.
2. Verify that your Com Port settings are correct.
3. Verify that the RTU is not in use from the Front Panel.

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.