Figure 142.   Example of an added device exceeding the global capacity device limit

As shown above, the property sheet of the device shows this reason in Fault Cause. You must delete this (or any) component with a similar fault cause, as otherwise it remains in fault.

Note that corresponding events are also entered in the station’s LogHistory, as shown here.

Figure 143.   LogHistory entries from exceeding globalCapacity

As shown below, the globalCapacity count for any exceeded resource appears in the corresponding entry in the station’s Resource Manager.

Figure 144.   Example globalCapacity entry for a resource over license limit

Note the necessary deletion of an over-limit device (51) does not decrement the count back at that time—instead, a periodic recount (about every 10 minutes) or station restart is needed for this.

Similar component faults and error logs apply to networks, points, links, and schedules.

Figure 145.   Example globalCapacity fault for proxy point

As shown above, the ProxyExt for a proxy point shows a Fault Cause reason. The property sheet of a network in global capacity fault is similar Exceeded network limit for globalCapacity, and this applies also to a schedule in global capacity fault: Exceeded schedule limit for globalCapacity.

Exceeding the globalCapacity link limit produces a popup Capacity Licensing window on the wire sheet or active view, saying “Exceeded Link Limit”, and the link is not functional.

Histories exceeding globalCapacity limits can manifest in different ways. See “Capacity licensing notes about histories”.