Page 28 - GuardII+ Series 4208 Platform PD User Manual

PD Card Operation

The Trigger interval for is 30 days; additionally, the current PD levels must be higher than
the Moderate Threshold setting, and the Trigger must be confirmed over multiple
measurement cycles before the Trigger actually occurs.

A measurement saved in the Archive due to a Temperature Dependence Trigger will
appear in PDView with a flag indicating the specific combination of sensor and polarity that
caused the Trigger:
• A “PDTD_C1” flag indicates that positive direct temperature dependence was detected
on the ‘C1’ sensor
• A “PDTD_C2” flag indicates that positive direct temperature dependence was detected
on the ‘C2’ sensor
• A “NITD_C1” flag indicates that negative inverse temperature dependence was
detected on the ‘C1’ sensor
• A “NITD_C2” flag indicates that negative inverse temperature dependence was
detected on the ‘C2’ sensor

Figure 4-8 Example of a Temperature Dependence Trigger in PDView

NOTE:
Temperature Dependence Triggers will not occur unless the monitor can
acquire the machine’s active power and asset temperature Operating
Conditions either through a Remote I/O Unit or directly through Modbus.
This configuration is done using IAM; refer to Section 6.3.

4.6.10. User Defined Trigger

Occasionally, some more frequent PD data over the short term is desirable; perhaps some
machine maintenance was just performed, and you want to check to make sure that the
machine PD hasn’t become worse. Or perhaps the machine is having sudden spikes of PD
that you want to capture. The User Defined Trigger is there for this purpose; it works
separately from the other Triggers and has its own storage location in the Archive.
NOTE:
One recommended use of the User Defined Trigger is to capture additional
data once a Very High PD Level Trigger has occurred; the Very High
Trigger is an indicator that PD levels have reached a point to cause
concern, so some more frequent data collection is a good idea.

20
www.irispower.com