AMX RMS 3.0, Руководство пользователя

Страница: 48 / 104

Custom Device Monitoring Programming
40
RMS NetLinx Programmer’s Guide
as both the virtual and real device of the support module. However, in this case,
you cannot use SEND_STRING for notifying the module of transport state.
You may notice that for transport state, you can pulse a channel between 241-248
to set the transport state. Since AMX SYSTEM_CALLs use those channels to
store transport state, no additional programming is needed to send transport state
to the module when using a SYSTEM_CALL. In this case, simply pass the real
device as both the virtual and real device of RMSTransportMod. However, in this
case, you cannot use SEND_STRING for notifying the module of transport state.
Control Failure
When the device is IR, power status is monitored using channel 255. Axcent3's,
NXC_IRS4 cards, NXI's and NI series controllers can all provide an IO link that
enables an IO status to appear on channel 255 of the device. These modules will
watch for power attempts using channel 9, 27 or 28 and report a control failure if
the power of the device does not respond properly. Additionally, the module will
monitor channel 254, used as a power fail channel when using the 'PON'
commands, and report control failure conditions when this channel is on. This
functionality must be enabled via the RMSEnablePowerFailure() function,
defined in the RMSCommon.axi include file. For example:
DATA_EVENT[vdvRMSEngine]
{
ONLINE :
{
RMSEnablePowerFailure(dvProj)
}
}
Device Information
You may want to define the name, manufacturer, and model using
RMSSetDeviceInfo(). Device information is usually sent in a device registration
message and can only be sent when the RMS engine module connects to the
RMS server. However, if the device is monitored by a support module, the device
info message can be sent at any time. For example:
DATA_EVENT[vdvRMSEngine]
{
ONLINE :
{
RMSSetDeviceInfo(dvProj,'Name','Manufacturer','Model
Number')
RMSSetDeviceInfo(dvVCR,'Name','Manufacturer','Model Number')