Thursday, August 20, 2026

Power over Ethernet (PoE) Explained: Power Classes, Cable Limits, and Design Checks

Power over Ethernet (PoE) Explained: Power Classes, Cable Limits, and Design Checks

Updated August 2026 · Structured cabling

PoE sends DC power and Ethernet data over the same balanced cable. It simplifies installation for IP cameras, wireless access points, phones, access control, sensors, and lighting, but it does not eliminate electrical design. The cable, channel length, connector quality, bundle temperature, and powered-device demand determine whether the system remains reliable.

What PoE changes

A data cable used to be treated mainly as a signal path. With PoE it is also a power path. The relevant question is not merely whether a device powers on; it is whether enough power reaches it continuously under maximum load, channel resistance, expected temperature, and bundle conditions.

Common nameIEEE familyTypical planning use
PoE802.3afPhones, basic cameras, simple devices
PoE+802.3atAccess points and higher-load cameras
PoE++802.3btHigher-power access points, lighting, displays, building devices

The labels are useful shorthand, but a procurement document should identify the required IEEE class/type, the power required at the powered device, the switch capability, and the channel assumptions. “PoE supported” is not a complete requirement.

Distance is a power calculation, not only a 100-meter rule

A conventional balanced-cabling channel is commonly planned as up to 100 meters, including permanent link and patch cords. That does not mean every cable at that length delivers the same usable PoE power. Current passing through DC resistance creates voltage drop and heat. Longer channels, smaller conductors, poor terminations, non-copper conductors, and uneven resistance reduce margin.

The five checks before purchase

  1. Powered-device demand: use maximum input power, not a typical marketing number.
  2. PSE capability: confirm switch or injector type, available power budget, and port limits.
  3. Channel construction: specify solid bare copper for permanent cabling; confirm AWG, component category, and termination compatibility.
  4. Path conditions: calculate length, bundle size, ambient temperature, tray fill, and airflow.
  5. Verification: require field certification and inspect DC loop resistance and resistance unbalance where PoE is material.

Bundling and temperature

Heating is often ignored because a single cable may seem harmless. Cables installed together cannot reject heat as effectively. Temperature also increases insertion loss, reducing data margin. The risk is higher for high-power loads, dense pathways, warm ceilings, and large bundles. Design documents should state bundle-management and derating assumptions rather than leaving them to the installer.

Common failure patterns

  • A camera works by day but restarts at night when infrared illumination increases load.
  • An access point negotiates but becomes unstable under client traffic.
  • Several ports fail after a bundle is added, although each was acceptable in isolation.
  • A switch reports power denied because total power budget—not cable data speed—is exhausted.

Bottom line

PoE is dependable when it is engineered as both a communications and power system. Start from the device’s maximum demand, validate the PSE budget and channel, use standards-compliant copper cabling, control thermal conditions, and certify installed links. Testing only for link speed leaves the failure mechanism untested.

Sources

No comments:

Post a Comment