Keeping a PoE Device Powered During Low Load Sleep

A PoE device can shut down unexpectedly after firmware successfully reduces its power consumption. The source may interpret the resulting low load as a disconnected device if the required maintain power signature is absent. Review the interface’s sleep behavior before treating every power loss as a converter stability problem.

Identify how presence is maintained

The TI TPS23731 data sheet describes the maintain power signature used after startup and the source’s removal of power when that signature is lost. The selected PD controller’s implementation determines how the required behavior is produced at light load.

Distinguish ordinary operating current, automatic signature generation, and any special sleep mode. A controller with one method should not be assumed to behave like another family with a similarly named low power feature.

Map the low load states

List every state that can reduce input demand: processor sleep, radio off, display blanked, converter shutdown, and operation from an alternate source. Record which circuits remain connected to the PoE input in each case.

Include transitions between states. A short active burst followed by a long quiet interval can create a different signature pattern from a steady low current load, even when the average consumption is identical.

Measure at the powered device input

Capture input current and voltage long enough to observe the relevant signature and source decision intervals. A highly averaged current display can hide short pulses that maintain the connection or conceal a long gap that causes disconnection.

Correlate the current waveform with the PD mode controls and firmware state. Determine whether the source removed power first or the downstream converter stopped first; those events call for different investigations.

Verify sleep and wake with real sources

Test the intended low power states using representative compatible source equipment. Confirm that the port remains powered for the required sleep duration and that waking the downstream load does not create an unsupported startup event.

Check alternate supply insertion and removal if supported by the product. An externally powered load may draw almost nothing from PoE while still expecting PoE to remain available for a later handover.

Save controller configuration, current waveforms, sleep duration, source identity, and wake result. If a supplemental load is part of the supported solution, include its power cost in the standby budget. A successful sleep implementation demonstrates both reduced consumption and continued recognition by the source. Measuring an impressively low average current alone does not establish that the Ethernet power connection will stay available.