Cabling, power, and distance caveats

Check cable, equipment, distance and power requirements against the actual installation. Have the responsible qualified person confirm the design and applicable requirements.

Overview#

There is no safe universal “maximum distance” table. Distance is a property of an exact PHY, cable and connector channel, data rate/timing, topology, transceivers, loading, environment, installation, power requirement, standard edition, and product limits.

This page doesn't approve electrical work. Follow the applicable standards, manufacturer instructions, qualified designer/installer, electrical and fire codes, accessibility rules, and authority having jurisdiction (AHJ). Life safety, egress, fire, lift, gate, lock, and mains decisions require the responsible qualified parties.

Required physical layer record#

Technology caveats#

Use serial and field interfaces, Ethernet, PoE, and power budgets, dry contacts and supervised circuits, and wireless and radio fundamentals.

DC voltage drop model#

For a simple two conductor DC circuit:

R_loop = resistance_outbound + resistance_return
V_drop = I_load × R_loop
V_at_load = V_source_min - V_drop - other_series_losses
P_at_load = V_at_load × I_load

This is an orientation formula, not a complete design. Account for:

• conductor resistance at maximum operating temperature and actual conductor material/gauge;
• connector, fuse, protection, distribution, and contact resistance;
• steady, boot, heater, IR illuminator, motor, audio, relay, lock and accessory peaks;
• shared return/common conductors and simultaneous loads;
• source tolerance, battery discharge, UPS/converter efficiency, and low temperature behaviour;
• device minimum input voltage at the required load and transient behaviour;
• code required overcurrent protection, voltage class, separation, derating, and fire performance.

Never increase voltage, bypass protection, parallel outputs, or change conductor arrangements from a desk calculation. A qualified electrical design and approved product instructions own those decisions.

PoE budget chain#

utility / generator / UPS
        ↓
switch PSU capacity and redundancy
        ↓
PSE total budget and per-port negotiated state
        ↓
cable/channel loss and temperature
        ↓
PD input and conversion
        ↓
camera/reader/intercom plus heater, IR, motor, relay, USB

Record both normal and degraded/failover budgets. Common failure cases include:

• all heaters/illuminators/motors starting together;
• a redundant switch or PSU lacking equivalent PoE capacity;
• LLDP/class negotiation changing after firmware/configuration;
• a link remaining up while a high draw function browns out;
• simultaneous restoration causing boot surge and network/authentication load;
• UPS runtime based on nameplate load rather than measured full path and aged battery;
• a midspan, extender, surge protector, media converter, or patching element absent from the channel record.

Remote PoE cycle is actuation: it can interrupt recording, door readers, intercom, sensors, or alarms. Gate it through the safety impact checklist.

Serial multidrop design questions#

• Which node owns termination at each physical end, and are there exactly the intended terminations?
• Which device/network owns bias/failsafe state?
• What is the maximum stub length under the exact rate/topology/product, not a generic rule?
• Is a reference conductor required, and what common mode range applies?
• Where is galvanic isolation and surge protection required?
• Does any adapter or gateway transmit during boot, discovery, driver installation, reconnect, or configuration?
• How are duplicate addresses, simultaneous transmitters, token loss, turnaround, and retries detected?
• Does bus power share conductors or reference with signalling, and what is its worst case drop?
• How will passive observation avoid changing termination/bias/loading?

See serial transports, OSDP, and BACnet MS/TP.

Acceptance evidence#

A continuity test alone doesn't certify a data channel. Link up doesn't prove error margin. A protocol reply doesn't prove power headroom or safe physical behaviour.

Mandatory deferral and stop conditions#

Stop and defer to the manufacturer, qualified engineer/installer, AHJ, and responsible system owner when:

• voltage, pinout, polarity, wet/dry contact, signal standard, or power source is unknown;
• mains, batteries, fire rated pathways, lightning/surge, hazardous locations, or building penetrations are involved;
• work can interrupt egress, locks, gates, lifts, fire/emergency systems, alarms, dispatch, or recording obligations;
• grounding/bonding/earth potential difference is unresolved;
• the proposed distance exceeds an exact standard/product channel or depends on undocumented extenders;
• two products claim the same connector but not the same electrical/power profile;
• approval, rollback, isolation, and witnessed acceptance are absent.

This reference supplies planning boundaries; connection, measurement, certification, and functional acceptance require qualified site procedures and retained environment evidence.

Sources#

• IEEE8023, IEEE 802.3-2022 Ethernet Standard, IEEE Standards Association; amendments and current project status must be checked at use time.
• IEEE POE, IEEE 802.3 Power over Ethernet information, IEEE 802.3 working group, accessed 25 August 2026.
• TIA, TIA standards catalogue and purchase path, Telecommunications Industry Association, accessed 25 August 2026.
• SIA OSDP, Open Supervised Device Protocol, Security Industry Association, accessed 25 August 2026.
• SIA OSDP CHECK, Implementing OSDP Access Control? Follow This Simple Checklist, Security Industry Association, 10 February 2026.
• BACNET MSTP, BACnet MS/TP technical bulletin, ASHRAE BACnet Committee.
• MODBUS SERIAL, Modbus over Serial Line Specification and Implementation Guide V1.02, Modbus Organization.
• USB, USB IF specifications and compliance resources, USB Implementers Forum, accessed 25 August 2026.

Section overview · Wiki home