{}

Our Brands

Search FAQs

AP9613/AP9614 Dry Contact I/O SmartSlot Card "Legacy Fault" Definition


Issue

What do the Legacy Faults refer to within the AP9613/AP9614 Dry Contact I/O SmartSlot Configuration Utility?

Configuration Interface



Product Line
  • UPS Device Management
    • AP9613 - Dry Contact I/O SmartSlot Card
    • AP9614 - Dry Contact I/O SmartSlot Card
Environment
  • All serial numbers
  • All firmware versions

Cause

These legacy fault options carry over from the AP9610 Relay I/O SmartSlot Card and the three configurations available with that older card for output #6. These are intended to be configurable for the AP9613/AP9614 as well, especially for environments with both AP9610 and AP9613/AP9614 cards. Further explanation below.


Resolution

The "Fault Legacy" items within the Dry Contact I/O SmartSlot Card Configuration Utility refer to the "legacy" configurations available for Output #6 in Configuration #1, #2, or #3 with the from the older AP9610 Relay I/O SmartSlot Card. Using Fault Legacy 1, 2, or 3 should be used if you are trying to mimic the behavior of the older AP9610 Output #6 in either configuration #1, #2, or #3.

Since AP9610 is only supported older style UPS-Link model units, legacy faults (which may be different across different UPS models) only work with those types of units where as "Fault" should be more used with newer Micro-link UPSs where you do not necessarily want to mimic output #6's behavior on AP9610.

Attached to this knowledge base are the fault definitions used by either UPS-Link or Micro-link style UPSs respectively that would be considered Fault.

Figure 1: Available Configurations from the discontinued AP9610 Relay I/O SmartSlot Card.

Configuration Matrix


Some examples of Legacy Faults may include an overload, hardware bypass, or battery charger failure - as defined above.

APC Canada

Attachment(s)

AP9610_AP9613_FaultDefinitions.xlsxAP9610_AP9613_FaultDefinitions.xlsx [10.96 KB]
Explore more
Range:
Users group

Discuss this topic with experts

Visit our Community for first-hand insights from experts and peers on this topic and more.
Explore more
Range: