AlarmAgent -- CSA -- RTU Commands and the Command Queue

How does the RTU use commands and what is the purpose of the command queue?

There are three types of RTU Commands:


Not all RTU configuration changes require RTU Commands to execute. All three types of RTU Commands involve sending transmissions from the web site to the RTU. The wireless communication system requires time to send these transmissions in the proper sequence to the proper RTU among all RTUs in the entire AlarmAgent system.

      Important Note: Configuration changes that require RTU Commands are indicated in red on the corresponding configuration web pages.

Therefore, all RTU Commands are initially placed in the "RTU Command Queue." The command queue page shown above displays the scheduling status of upcoming Command transmissions. The Command transmissions are then automatically sent to the RTU according to the Command Queue. The web site then waits for the RTU to confirm that the command has been executed.

This process can take a few minutes, depending in part upon how many other users in other companies are initiating RTU Commands at the same time. Correspondingly, when you make a change to a configuration item indicated in red and click SAVE, the change does not appear on the corresponding web site page until the change has been transmitted to the RTU and the RTU has confirmed back to the web site that the change has been executed. To remind you of this, each time you do confirm a change to an item indicated in red by clicking SAVE, you are taken to the Command queue page. Even after the transmission and confirmation process has been completed, you may have to hit the refresh button on your web browser in order for the displayed page to reflect the competed change.

Monthly limitations on the number of RTU Commands sent: Beginning on the day you import your RTU into your system, and for an additional full calendar month afterwards, there is essentially no limitation on the number of RTU Commands. This allows for the initial configuration of the RTU as needed. After the expiration of the first full calendar month after the RTU is imported, the number of RTU Commands allowed each calendar month is determined by your selected Service Level. The number of RTU Commands remaining unused for the current calendar month is indicated on pages from which RTU Commands can be initiated. Unused RTU Commands do not roll over into following months.

      IMPORTANT: The practical effect of all this is that you will not initially see configuration changes which require RTU commands reflected on the corresponding web site pages.