Rms Control Functions And Macros; Device Interrogation - AMX CP-3017-TR-US Instruction Manual

RMS Configuration
When you configure the peer group on a ControlPad, you must restart the proxy after the ControlPad comes back online
for the proxy to get an updated beacon and match peer groups.
For first time installations, you should program and configure all ControlPads that connect to a proxy using a zero-
configuration client before starting the CP-RMS Service. If you are using a zero-configuration client, and the IP address
of the ControlPad is changed for any reason (for example, the DHCP server assigns a different IP upon reboot of the
ControlPad), the CP-RMS Service needs to be restarted for it to update the ControlPad's IP address.
If you add a ControlPad as a room in RMS, and then change the device name on the
Controlpad to display updated information regarding the device name, you must
delete the room in RMS and re-add it for the changes to appear.

RMS Control Functions and Macros

When a ControlPad connects to RMS, all physical and virtual buttons that have been programmed properly with scripts
and Button Assigned Names using AMX DCS display as available control functions in RMS (see the Button Actions and
Events section on page 50 for more information). These control functions are available for inclusion in macros. You can
schedule the macros to execute by using the RMS Internal Scheduler or an external scheduler.
When you execute a button press on the ControlPad, physically or through RMS, the script that is programmed for that
button executes. The ControlPad only runs one script at a time, so if it is busy running a script and a new button event is
received, the button event is ignored.
The most efficient way to execute multiple events in one macro through RMS is to create a virtual button that contains all
desired events. When programming the keypad through DCS, make sure to select one of the existing RMS standard
functions from the Button Assigned Name options menu or create a custom name for the virtual button. This virtual
button then appears in RMS as a control function and you can create and schedule a macro, containing only that control
function, in RMS.

Device Interrogation

If you program a ControlPad for device interrogation, and later re-program the ControlPad, but add a new input on a
device, you must not only clear the device, re-select it, and reprogram the ControlPad from DCS, but you also need to
delete the ControlPad from RMS, and restart the proxy to guarantee that the new inputs show up in the notification
menus and the status is shown in the RMS server.
When the ControlPad boots up, it only runs device interrogation after the CP-RMS Proxy successfully connects to it.
Additionally, the ControlPad only sends values to the CP-RMS proxy on the initial connection, and when they update.
This means that for formula results, the result of the formula calculation must change at the integer/whole number level.
If a device was returning lamp hours as seconds, and the formula converts seconds to hours, then the final integer result
must increment or decrement to update the proxy, and ultimately RMS Server.
If a device goes offline or fails to respond to the ControlPad Status Query, no update is sent since the device is in an
unknown state. A device which has lost power, or has had a disconnected serial cable, will appear online, but will never
update its status.
68 Novara 3000 Series ControlPads Instruction Manual