HOT CROSS-REFERENCE SEARCHES All Products
HR911105A Cisco GLC-LH-SMD Pulse J1011F21PNL LPJG0926HENL TE 2170704-1 SFP-10G-SR
POPULAR CATEGORIES
Matched Parts (Real-time ES) Use ↑ ↓ to select, Enter to open
ACCESS CONTROL ETHERNET

Ethernet and PoE Connectivity for Access Control and Network Door Controllers

Design the wired interface of access-control panels, network door controllers and edge door modules around the actual reader bus, credential logic, Ethernet MAC/PHY, PoE power path, door inputs, relay outputs and lock-power architecture. LINK-PP supports integrated RJ45 MagJacks, discrete LAN transformers and modular connectors rather than credential databases, authorization policy, reader-protocol firmware, lock control logic or the complete access-control platform.

CREDENTIAL → READER → CONTROLLER → DOOR I/O → ETHERNET / PoE CREDENTIAL CARD · MOBILE · PIN · BIOMETRIC READER OSDP / WIEGAND CREDENTIAL INPUT NETWORK DOOR CONTROLLER RULES · CREDENTIALS · SCHEDULES DOOR I/O · RELAY · EVENTS LOCAL / SERVER-ASSISTED DECISION DOOR I/O LOCK / STRIKE · DOOR CONTACT · REX TAMPER · FIRE / AUXILIARY INPUT ETHERNET PHY 10/100 · 1G PLATFORM-DEPENDENT RJ45 + MAGNETICS DATA + OPTIONAL PoE TO ACCESS SWITCH ACCESS SERVER / CLOUD / SECURITY PLATFORM CONFIGURATION · EVENTS · CREDENTIAL MANAGEMENT READER / CONTROLLER · READER BUS / ETHERNET · PoE INPUT / LOCK POWER
READER → CONTROLLER → ETHERNET DOOR I/O AND NETWORKING ARE SEPARATE DESIGN LAYERS

Quick answer: a networked access-control system separates credential reading, access decisions, door I/O and host networking into distinct functions. A typical architecture uses a card, mobile, PIN or biometric reader connected to a door controller through OSDP or legacy Wiegand; the controller applies access rules, operates locks and door inputs, and communicates with the management platform over Ethernet. PoE can power compatible controllers or readers over the network cable. LINK-PP supports the Ethernet physical interface rather than credential databases, authorization policy, reader-protocol firmware, lock control logic or the complete access-control platform.

OSDP · Wiegand

Reader-to-Controller Interfaces

100M · 1G

Controller Ethernet Context

PoE · Door I/O

Network + Control Hardware

RJ45 · LAN Magnetics

LINK-PP Core Scope

READER · CONTROLLER · DOOR I/O · NETWORK

Access-Control Systems Separate Credential Capture, Authorization, Door Control and IP Management

The same enclosure can combine several functions, but the hardware roles remain distinct and should be validated independently.

CREDENTIAL INPUT

Reader

Captures card, mobile, PIN, QR or biometric information and passes credential data toward the controller.

OSDPWiegandCredential
ACCESS DECISION

Door Controller

Applies rules, schedules and local or server-supplied permissions, then controls the relevant door output.

RulesLocal CacheEvents
DOOR HARDWARE

Inputs & Outputs

Connects locks, strikes, door contacts, request-to-exit inputs, tamper signals and related field wiring.

LockREXContact
IP NETWORK

Ethernet / PoE

Connects the controller to management software, events, configuration and optional PoE power infrastructure.

RJ45PHYPoE
ACCESS-CONTROL ARCHITECTURE

Door Controllers Range from Single-Door Edge Devices to Multi-Door Network Panels

Reader count, door count, Ethernet role, PoE budget and local decision capability should be treated as separate controller specifications.

SINGLE-DOOR IP CONTROLLER READER OSDP / WG CONTROLLER RJ45 / PoE ACCESS-CONTROL DATA PATH READER → CONTROLLER → DOOR I/O + ETHERNET → SERVER

Single-Door IP Controller

One door with local reader, lock and network connectivity

  • READERCredential InputOSDP or Wiegand reader provides card, mobile, PIN or other credential data.
  • CONTROLDoor ControllerApplies access rules and manages the door contact, REX and lock-control path.
  • NETWORKEthernet / PoEConnects management traffic and optional power through the RJ45 physical interface.
CREDENTIAL INPUT vs ACCESS DECISION

Readers Capture Credentials; Door Controllers Apply Access Rules and Operate the Door

The reader collects identity data. The controller evaluates permissions, schedules and door state before commanding the relevant output.

Reader

Reads card, mobile, PIN, QR or biometric data and sends credential information to the access-control function.

Typical interfaces: OSDP · Wiegand · integrated IP on some platforms

Access Controller

Processes permissions, local rules, schedules, inputs and output actions, then records events for the host platform.

Typical interfaces: reader bus · door I/O · Ethernet
Boundary: reader ≠ access controller.
READER BUS OPTIONS

OSDP and Wiegand Connect Readers to Controllers in Different Ways

Wiegand remains a common legacy integration requirement. OSDP provides a modern bidirectional reader-to-controller architecture with supervision and optional Secure Channel when both endpoints support it and it is enabled.

Property
Wiegand
OSDP
Design Meaning
Communication
Primarily one-way credential data
Bidirectional
OSDP supports richer reader/controller interaction
Physical Layer
Dedicated signal wires
RS-485
Wiring, topology and termination requirements differ
Supervision
Limited
Supported
OSDP can provide better device visibility
Secure Channel
No native equivalent
Supported when both endpoints support it and it is enabled
Do not assume an OSDP link is protected unless Secure Channel is configured and operating
Legacy Compatibility
Very common
Increasingly common
Controller design often needs one or both interfaces
LOCAL READER BUS vs IP UPLINK

Reader Communication and Controller Ethernet Serve Different Network Segments

A common access-control design uses OSDP or Wiegand between the reader and door controller, then Ethernet between the controller and management network.

Reader Credential Input
→
OSDP / Wiegand Local Reader Bus
→
Door Controller Decision + I/O
→
Ethernet Server / Cloud Uplink
OSDP / Wiegand ≠ controller Ethernet uplink.
CONTROLLER CAPACITY

Door Count and Reader Count Are Separate Controller Limits

One door can use a single entry reader, entry and exit readers, or additional credential interfaces. A two-door controller therefore does not automatically mean only two reader ports.

Door 1 Entry + Optional Exit
+
Door 2 Entry + Optional Exit
→
Reader Interfaces Platform-Dependent
→
Controller Door + Reader Limits
Always check door capacity, reader-port count and OSDP device capacity separately.
EDGE ACCESS CONTROL

Access Decisions Can Continue Locally on Supported Controllers during a Server or Network Outage

Where the controller supports local decision-making, cached credentials, schedules and rules allow the door to continue operating even if the management platform is temporarily unreachable.

Server Available

Controller exchanges configuration, credential updates, events and health information with the access-management platform.

Path: controller ↔ Ethernet ↔ server / cloud

Server Unavailable

Supported controllers can continue applying local rules and cached credentials, while event synchronization resumes when connectivity returns.

Requirement: platform-specific offline capability
PoE DOOR CONTROLLER POWER

A PoE-Powered Controller Must Budget Power across Electronics, Readers and Door Hardware

PoE can simplify controller installation, but the available input power must still cover the controller CPU, Ethernet, reader loads, auxiliary circuits and any powered lock outputs included by the platform.

PoE Input Total Available Budget
→
Controller CPU · PHY · I/O
+
Readers / Aux Peripheral Loads
+
Lock Output If Powered by Controller
Controller PoE input ≠ unlimited lock power.
Design rule: calculate each controller’s power tree from the actual PoE class, conversion losses, reader loads, auxiliary outputs, lock current, duty cycle and thermal limits.
DRY RELAY vs POWERED LOCK OUTPUT

Door-Control Outputs May Be Dry Relays or Powered Lock Outputs

The controller may only switch an external door-power circuit, or it may supply a regulated lock output itself. Those architectures have different current, protection and wiring requirements.

Dry Relay Output

NO / NC / COM contacts switch an external lock or strike power source without necessarily supplying the load power from the controller.

Path: controller relay → external PSU → lock

Powered Lock Output

Controller power electronics provide a regulated output for the lock or strike within the published voltage, current and duty-cycle limits.

Path: controller PSU / DC-DC → protected lock output
DOOR INPUTS & OUTPUTS

Reader, Door Contact, Request-to-Exit and Lock Output Serve Different Functions

Door-state and egress inputs are part of the access-control logic, not additional credential readers. Validate each signal independently.

Reader

Provides credential input to the controller through OSDP, Wiegand or an integrated network path.

Door Contact

Reports physical door state for held-open, forced-open and normal closure monitoring.

Request-to-Exit

Signals authorized egress without presenting an entry credential.

Lock / Strike

Receives the controller output that actuates the door hardware.

Tamper / Fire / Aux

Provides enclosure, life-safety or additional field-state inputs depending on the controller design.

AUTHORIZATION vs VISITOR COMMUNICATION

Access Control and Intercom Systems Can Integrate without Serving the Same Primary Role

Access control determines whether a credential is permitted to open a door. An intercom establishes visitor communication with a resident, desk or operator. One product can contain both functions, but the control paths remain different.

Access-Control Path

Credential → reader → controller → authorization → door output.

Primary role: identity · permission · door state

Intercom Path

Visitor → call button → SIP / media session → resident, desk or indoor station.

Primary role: communication · visitor interaction
AUTHORIZATION LOGIC vs PHYSICAL PASSAGE

Access Controllers Make the Authorization Decision; Turnstiles and Speed Gates Enforce the Physical Passage

A turnstile, speed gate or barrier can be one of the controlled mechanisms. The reader and controller still handle credential processing, permissions and event logic.

Credential Card / Mobile / PIN
→
Reader Credential Capture
→
Controller Grant / Deny
→
Door / Turnstile Physical Passage
The passage mechanism is controlled hardware, not the access-decision engine.
100M · 1G · PLATFORM-DEPENDENT

100M and 1G Ethernet Cover Most Door-Controller Network Roles

Access-control traffic is usually modest: credentials, events, health status, configuration and management. The controller PHY should therefore follow the actual host platform rather than assumptions based on other security devices.

Ethernet Rate
Controller Context
Physical-Layer Meaning
Selection Logic
10/100BASE-TX
Single-door / multi-door controller · compact panel
Fast Ethernet
Strong fit for event and credential traffic
1000BASE-T
Newer integrated security panel · higher service integration
Four-pair Gigabit Ethernet
Use when required by the controller SoC / PHY or wider platform architecture
ETHERNET DATA + PoE POWER

Ethernet Carries Controller Data while PoE Adds DC Power on the Same Cable

The Ethernet PHY handles management traffic and events, while the PoE powered-device subsystem extracts and converts DC power for the controller and supported peripheral loads.

PoE Switch PSE
→
RJ45 / Magnetics Cable Interface
→
Data Branch PHY → Controller CPU
+
Power Branch PD → DC/DC → Loads
Verify center taps, current path, isolation, winding resistance and thermal behavior against the actual PoE design.
UPSTREAM MANAGEMENT & BACKBONE

Cloud Management and Local Door Decisions Can Be Separate Availability Domains

The controller normally reaches management software over Ethernet. Fiber can appear upstream between buildings, gatehouses or the security core, while the door controller itself remains a copper Ethernet endpoint in many deployments.

Reader / Door Local Field I/O
→
Controller Local Access Logic
→
RJ45 Switch Local Ethernet
→
Server / Cloud Management / Events
Optional fiber typically belongs in the building or campus backbone, not between an OSDP reader and controller.
ACCESS-CONTROL TROUBLESHOOTING

Separate Ethernet, Reader Bus, Access Logic, Door I/O, Power and Server Fault Domains

A controller can be online while a reader is offline, a credential can be read while policy denies access, and an access decision can succeed while the lock circuit still fails.

Symptom
Likely Area
Check First
Do Not Assume
Controller powered, no LAN
PHY / magnetics / cable
PHY reset, clock, MDI, RJ45, cable and switch port
PoE power proves Ethernet data is healthy
LAN works, reader offline
OSDP / Wiegand bus
Power, address, polarity, wiring, termination and controller configuration
The Ethernet uplink is necessarily faulty
OSDP reader unstable
RS-485 topology
Bus length, device address, termination, grounding and cable routing
Secure Channel alone fixes physical-layer faults
Credential reads, access denied
Access policy
Credential status, schedule, access level and local rule set
Reader communication is the first fault domain
Access granted, lock stays closed
Relay / lock power / wiring
Output mode, PSU, voltage, current, relay state and field wiring
Authorization logic failed
Door opens, alarm remains
Door contact / input logic
Contact wiring, supervision and normal-open / normal-closed configuration
The lock output is still the root cause
Controller reboots when lock fires
Power / inductive load / thermal
PoE budget, PSU margin, flyback suppression, lock current and DC/DC stability
Network traffic caused the reboot
Server offline, door still works
Local decision architecture
Confirm whether the controller is designed to operate from cached rules
The controller is bypassing security policy
Server online, events missing
Controller-server communication
Routing, firewall, time sync, service status and event forwarding
The reader must be offline
VALIDATION & PRODUCT MAPPING

Qualify the Controller Ethernet Port from the Actual PHY, PoE Budget and Door-I/O Architecture

Provide the door-controller SoC / PHY, Ethernet rate, PoE role, original component, reader-bus architecture and enclosure constraints rather than a generic request for an “access-control RJ45.”

1. Ethernet Component

Review turns ratio, OCL, insertion loss, return loss, crosstalk, CMRR, isolation, pinout, shield and PoE current path.

Evidence: PHY reference design · component datasheet

2. Reader Bus

Verify OSDP or Wiegand electrical requirements, power, address, topology and controller capacity separately from Ethernet.

Evidence: reader + controller interface documentation

3. PoE / Lock Power

Exercise controller, reader and door loads against the actual PSE, cable channel, DC/DC conversion and lock output architecture.

Evidence: power · thermal · transient validation

4. Door Inputs / Outputs

Validate relay, powered outputs, door contacts, REX, tamper and auxiliary wiring independently of the Ethernet interface.

Owner: access control · field wiring · power design

Controller Platform

  • Single-door / multi-door / edge controller
  • SoC and Ethernet PHY
  • 10/100 or 1G Ethernet
  • PoE PD: yes / no
  • Local offline decision support

Reader / RJ45

  • OSDP / Wiegand / integrated IP reader
  • Reader count and door count
  • Original MagJack / transformer P/N
  • Footprint / pinout / LEDs / shield
  • Center taps / PoE current path

Door / Program

  • Dry relay or powered lock output
  • Door contact / REX / tamper inputs
  • Indoor / outdoor enclosure
  • Prototype and annual quantity
  • Lifecycle / second-source requirement
PRIMARY

Integrated RJ45 Connectors

MagJack families for access-control panels and network door controllers where the integrated magnetics match the actual PHY and PoE design.

PRIMARY

LAN Transformers

Discrete magnetics for controller boards using a separate modular jack, sealed cable interface or mechanically constrained enclosure.

FAST ETHERNET

10/100 Base-T RJ45

Fast Ethernet connector families aligned with many compact door-controller and entrance-control platforms.

GIGABIT

1000 Base-T RJ45

Gigabit connector families for newer integrated access-control and security platforms where the host PHY requires 1G Ethernet.

Single-Port RJ45

Single Ethernet interface families for network door controllers, access panels and entrance-control equipment.

Low-Profile / SMT RJ45

Connector options for compact access-control PCBs, wall-mounted panels and constrained controller enclosures.

IP Intercoms

For SIP calls, visitor communication and video door stations, use the dedicated intercom solution.

Security & Surveillance

Review the broader LINK-PP security networking architecture for cameras, monitoring, alarms, intercoms and access systems.

PoE Standards and Wattage

Review PoE PSE/PD roles and power-delivery considerations for network controllers and supported field loads.

Read PoE Guide →

RJ45 Integrated Magnetics Design

Review OCL, turns ratio, isolation, CMRR, EMI, PoE and PHY-to-MagJack considerations.

Read Magnetics Design Guide →

Ethernet PHY vs MAC

Review the boundary between the controller CPU / MAC, Ethernet PHY and external magnetic interface.

Read PHY vs MAC Guide →

Ethernet Transformer Design

Review discrete LAN transformer selection for embedded access-control and security Ethernet interfaces.

Read Transformer Guide →
FAQ

Access Control, OSDP, Wiegand, PoE and Door-Controller Questions

Practical answers for access-control engineers, security OEM teams, system integrators and component sourcing.

What is the difference between an access-control reader and a door controller?

A reader captures credential information such as card, mobile, PIN or biometric data. A door controller applies access rules, monitors door inputs and commands locks or relays.

Is OSDP the same as Ethernet?

No. OSDP is commonly used between readers or peripherals and the access-control unit over an RS-485 physical layer. Ethernet normally connects the network door controller to the wider IP network or management platform.

What is the difference between OSDP and Wiegand?

Wiegand is a long-established reader interface with limited supervision, while OSDP supports bidirectional communication, device supervision and optional Secure Channel when both endpoints support it and it is enabled.

Does a two-door controller always support only two readers?

No. Door count and reader-interface count are separate specifications. A controller may support entry and exit readers on the same door, so reader capacity can exceed door count.

Can an access-control door continue working if the server connection is lost?

On platforms that support local decision-making, the controller can continue applying cached credentials, schedules and access rules during a server or network outage.

Does PoE power to a door controller automatically provide enough power for the lock?

No. The PoE input budget must be divided among the controller, readers, auxiliary loads and any powered lock outputs. Some controllers use dry relays and require a separate door power supply.

Does an access-control controller need Gigabit Ethernet?

Not necessarily. Many door controllers use 10/100 Ethernet because access-control traffic is modest. Gigabit Ethernet can be used on newer or more integrated platforms when required by the controller architecture.

What information is needed to select RJ45 magnetics for a network door controller?

Provide the Ethernet PHY or SoC, 10/100 or Gigabit requirement, PoE role, original component, footprint, pinout, shield, LEDs, operating temperature and enclosure constraints.

NEXT STEP

Move from the Door-Controller Architecture to the Correct Ethernet and PoE Interface

Send the controller SoC / PHY, Ethernet rate, PoE role, reader-bus design, original MagJack or transformer, enclosure and door-power architecture. Those details determine compatibility more reliably than a generic request for an “access-control connector.”

For Access-Control Hardware Engineers

Match the PHY, Magnetics and PoE Path

Share the Ethernet controller reference design, 10/100 or Gigabit requirement, PoE architecture, pinout, shield and enclosure constraints.

Contact Engineering →
For Security-System Integrators

Separate Reader, Controller and Door-Power Layers

Provide the OSDP / Wiegand topology, door count, reader count, local decision architecture and lock-power design.

Request Interface Review →
For Procurement / OEM

Cross-Reference the Controller Ethernet BOM

Send the original RJ45 or LAN transformer part number, quantity, lifecycle target, PoE requirement and operating environment.

Submit BOM →