PoE PSE Controller Selection: Budget Power Across Ports

Table of Contents

• How much power can the PSE allocate across its ports?
• Why is instantaneous measured consumption not the same as a commitment?
• Which controller features must be evaluated together?
• How should simultaneous startup and supply loss be tested?
• What should procurement retain before approving an alternate?

Per-port power ratings can hide a system-level shortfall. A network switch may support a high-power PoE device on each port while lacking enough total supply capacity to run every port at its maximum simultaneously, so Power Sourcing Equipment (PSE) controller selection needs a shared policy. The PoE PSE power budget is therefore a system decision, not a per-port number.

This is the source-side decision. The PoE powered-device controller guide covers how the receiving device budgets power after the cable and conversion stages. Compare the two ends of a link at the same power boundary.

How much power can the PSE allocate across its ports?

Start with the supply power available under the intended operating conditions, subtract the switch’s own consumption and applicable losses, and retain the reserve required by the design. Compare port commitments at the same electrical boundary.

Assume 240 W is available at the power supply’s DC output under the chosen conditions. Reserve 24 W for the switch and internal losses and 16 W for the design’s margin. The resulting modeled port budget is 240 − 24 − 16 = 200 W.

Four ports allocated 30 W and four allocated 15 W require 4 × 30 + 4 × 15 = 180 W. A new 30 W allocation would exceed the remaining 20 W. The controller and system software need an explicit response: deny the request, reduce a permitted allocation, or remove a lower-priority load according to the product policy. The allocations are round numbers for the example, not IEEE power classes.

A supply’s nominal label may not describe its output at the highest enclosure temperature or after a redundant supply is removed. Use the applicable derating and redundancy conditions before calculating the shared budget.

Why is instantaneous measured consumption not the same as a commitment?

A device drawing little power at one moment may still be permitted to draw more later. A budget based only on instantaneous consumption can overcommit the supply unless the system has a validated control policy for that behavior.

TI’s port-power-management discussion explains admission control and priority-based removal of lower-priority loads when necessary. It also notes that systems containing multiple PSE devices may need central management. The important purchasing question is where that policy runs and what state survives a reset or communication failure.

Define whether the implementation uses classified/allocated power, negotiated information, measured consumption or a supported combination. Document how it handles changing load, oversubscription and the time needed to reduce demand. Do not assume that a current monitor by itself provides safe or predictable shared-budget enforcement.

Which controller features must be evaluated together?

Evaluate port topology, external power components, current sensing, firmware and host control as one design. A shared “PoE PSE controller” category does not make two devices interchangeable.

The TPS23881 datasheet, reviewed November 4, 2026, provides a concrete example of a multi-channel PSE controller with configuration and firmware requirements. Its channel count must be interpreted with the selected two-pair or four-pair port configuration; a channel label should not be read as an unlimited count of independent high-power ports.

Selection field	What the buyer needs from engineering
Port configuration	Number of powered ports, pair arrangement and required device compatibility
Power path	External transistor, sense resistor, protection and thermal requirements
Control architecture	Host ownership, initialization sequence, firmware image and configuration retention
Shared budget	Admission policy, priority order and behavior under a reduced supply budget
Diagnostics	Fault reporting, measurement accuracy and evidence available after an event

For industrial power and interface sourcing, supply the full controller code and the associated power-path BOM. A controller substitution that changes sensing or firmware can invalidate the existing power-allocation behavior even if the pins appear compatible.

How should simultaneous startup and supply loss be tested?

Test the intended port population through cold startup and the reduced-power conditions the product claims to support. Verify both the electrical supply response and the policy that decides which devices receive or lose power.

The test sequence should cover all intended loads requesting power after a cold start, a high-priority device arriving when the budget is nearly exhausted, and removal of a redundant supply where supported. Record port allocations, supply voltage/current, reported faults and the sequence of device recovery.

Include the difference between a temporary request denial and a latched fault. Repeatedly attempting to power a load without resolving the budget condition can create unstable restart behavior. The required retry, priority and recovery rules should come from the product specification and controller capabilities, not a technician’s ad hoc adjustment.

Then exercise communication loss or reset between the host and PSE controller. Determine whether existing ports stay powered, shut down or enter another documented state. That behavior matters to applications such as cameras and access points even when average power consumption remains within the budget.

What should procurement retain before approving an alternate?

Retain the approved port map, firmware/configuration versions, power-path components, budget policy and acceptance results alongside the full ordering code. Those records describe what the replacement must preserve. Ask the PSE controller IC supplier for the configuration, firmware and power-path requirements that belong with the orderable code; a generic family datasheet is not enough for an alternate review.

A component-alternatives comparison should identify changes in channel mapping, host commands, current measurement, external components and fault recovery. If any of these changes, qualify the complete revised PSE implementation.

The release criterion is a source that powers the intended population predictably, including the defined overload and recovery cases. A higher per-port headline rating is useful only when the shared power system and management policy can deliver the required behavior.