Technical information

The RMS Enterprise SDK (v4)
23
RMS Enterprise - NetLinx Programmer’s Guide
RMS Power Distribution Unit (PDU) Monitor
Devices such as the NXA-PDU-1508 provide an interesting combination of integration requirements. The PDU unit itself is an
asset with many parameters to be registered and monitored in RMS. However, the monitored usage of power for each outlet may
truly represent real power consumption on behalf of another asset being registered and monitored in RMS. This scenario presents a
use case where an asset is tracking parameter changes on behalf of another asset. The RMS Enterprise SDK provides a default
monitoring module for the PDU device to accommodate this cross-asset monitoring requirement.
The diagram in FIG. 12 illustrates the file dependency chain for the RmsPowerDistributionUnitMonitor module integration:
The code below illustrates the NetLinx code required to integrate the PDU monitor module. The first thing that must be defined is
the PDU base device. The NXA-PDU-1508 is a collection of 8 AxLink devices.
For the purposes of RMS, only the first (base) address must be defined:
DEFINE_DEVICE
dvPDU_Base = 96:1:0 // AMX PDU (Physical Device (first device))
Next, an array of devices must be defined that map asset relationships to each of the outlets on the PDU unit. The code snippet
below illustrates this array definition.
// PDU Energy./Power Monitored Device Array
// The PDU can support up to 8 devices, 1 in each
// of the 8 physical outlets on the unit.
VOLATILE DEV dvPowerMonitoredDevices[8] =
{
dvDVR, // Outlet #1
dvDiscDevice, // Outlet #2
dvDocCamera, // Outlet #3
dvDSS, // Outlet #4
dvVideoProjector, // Outlet #5
0:0:0, // Outlet #6 -- null device (nothing plugged in here...)
0:0:0, // Outlet #7 -- null device (nothing plugged in here...)
0:0:0 // Outlet #8 -- null device (nothing plugged in here...)
}
Finally, the RmsPowerDistrubitionUnitMonitor module must be defined:
FIG. 12 RMS SDK File Dependencies - Power Distribution Unit Implementation