AMX RMS 3.0, Manual

Page: 46 / 104

Custom Device Monitoring Programming
38
RMS NetLinx Programmer’s Guide
Programming
These modules require a virtual device, the real device of the device to be
monitored, and the RMS Engine module's device. If you are using an AMX
module for communicating with a device, the virtual device used for the Comm
module can be passed to the device monitoring support module. Since the
support modules are written to listen for the messages for the particular device
types they support, no additional programming is needed. Simply define the
devices, add the module, and pass the device numbers as module parameters. An
example:
DEFINE_DEVICE
dvSlide = 96:1:0
dvVPROJ = 5001:1:0
dvVCR = 5001:2:0
dvSWT = 5001:3:0
vdvVPROJ = 33001:1:0
vdvVCR = 33002:1:0
vdvSWT = 33003:1:0
vdvRMSEngine = 33003:1:0
// Projector Monitoring Code
DEFINE_MODULE 'RMSProjectorMod' mdlProj1(vdvVPROJ,
dvVPROJ,
vdvRMSEngine)
DEFINE_MODULE 'COMM_XXXXX' COMM(dvVPROJ, vdvVPROJ)
// VCR Monitoring Code
DEFINE_MODULE RMSTransportMod' mdlVCR1 (vdvVCR,
dvVCR,
vdvRMSEngine)
DEFINE_MODULE 'COMM_XXXXX' COMM(dvVCR, vdvVCR)
If you are not using an AMX module for communicating with a device, you will
need to add programming to notify the module of changes in the device state. For
the Basic Device and Projector module, you will need to notify the module when
the power is turned On or Off. Optionally, if you have polled for projector lamp
hours, you can provide this value directly. For the transport module, you will
need to notify the module when the power is turned On or Off and when the
transport state changes.