How do you determine which commands are ready to be sent to an RTU?To view the Command Queue Page, click on the CMD QUEUE tab.
Some RTU configuration changes (such as message changes or assigning specific alarm conditions to Notification Groups) apply solely to the web site. Others (such as changing alarm criteria for a given channel) must be transmitted to the RTU. Poll requests and output relay changes must also be transmitted to the RTU. Operations which require such transmissions are called RTU Commands, and they are indicated in red font on the applicable web site pages.
RTU Command transmissions must be issued by the web site in a particular sequence, and spaced out over a span of two or more minutes. Further, the web site does not consider an RTU Command to have been actually implemented at the RTU until it has received a subsequent transmission from the RTU confirming the change. This means that when you change an item shown in red font (i.e. requiring an RTU Command), there will be a delay before the web site considers it to be in effect.
In particular, this means that when you make a change that requires an RTU command, it will initially appear as though the change did not occur, in turn suggesting that you might need to issue the same command again. Do not do this! In order to remind you of this, each time you make such a change, you are automatically taken to the RTU Command Queue page. This page shows the status of any such changes you have made which have not yet been transmitted and confirmed.
Because of the way web pages are presented by web browsers, even after RTU commands have been transmitted and confirmed back from the RTU to the web site, it may be necessary to click on the browsers refresh button in order for the changed setting to appear on the relevant page.