Technical informational / commercial investigation
Two-Door and Four-Door Access Controller Wiring
Wiring and cabling guide
Confirm the exact equipment models, cable types, power capacity, distances and current manufacturer instructions before installation. Terminal names and ratings vary between products.
Main diagram
Equipment list
- Reader Options - OSDP / RS-485 or point-to-point Wiegand
- 2 / 4 Door Controller - Secure-side access decision and I/O
- Security LAN - Cat6 to switch, server or browser
- Door Contacts and REX - Separate low-voltage inputs per door
- Controller Door I/O - Inputs and relays in the same controller
- Locks and Battery PSU - Dedicated lock power and release path
Cable schedule
Use the diagram reference to follow the same connection from the main diagram into the detailed explanation below.
| Diagram ref | From | To | Cable type | Core count | Power or data | Maximum distance | Purpose / important notes |
|---|---|---|---|---|---|---|---|
| C1 | Reader Options | 2 / 4 Door Controller | OSDP: shielded twisted pair plus power; Wiegand: shielded 6- or 8-core | Protocol and optional functions determine cores | Reader supply to exact model | Confirm controller and reader manuals | Choose OSDP/RS-485 or Wiegand per reader |
| C2 | 2 / 4 Door Controller | Security LAN | Cat6 U/UTP 4-pair solid copper | 4 twisted pairs | Ethernet data | 90 m permanent link / 100 m channel | Controller management LAN |
| C3 | Door Contacts and REX | Controller Door I/O | 2-core 0.5 mm2 per dry-contact function; 4-core or more for powered REX/monitoring | 2 per dry contact; 4+ for powered devices | Input/control | Site-specific | Door contact and request-to-exit inputs |
| C4 | 2 / 4 Door Controller | Controller Door I/O | Internal controller relationship - no external field cable | Same physical controller | Internal | Not applicable | Same controller: management above, door I/O below |
| C5 | Controller Door I/O | Locks and Battery PSU | 2-core 0.5 mm2 low-voltage control cable per door | 2 per relay/control path | Dry-contact control unless exact manual states otherwise | Site-specific | Controller relay to lock PSU/control relay |
No maximum distance is invented. Where the exact figure depends on Ethernet design, voltage drop, current draw or the selected device, the schedule tells the installer to confirm it.
What the wiring actually is
Match each C reference to the same label on the main diagram and cable schedule. The line name alone is not a complete cable specification, so this table explains the physical cable, conductor or pair use, what it carries and how it normally terminates.
| Diagram ref | Cable shown | Physical path | Cable construction | Conductors or pairs | What it carries | Normal termination | Confirm before installation |
|---|---|---|---|---|---|---|---|
| C1 | OSDP: shielded twisted pair plus power; Wiegand: shielded 6- or 8-core | Reader Options to 2 / 4 Door Controller | Reader cable selected for the protocol: commonly 6-8 core shielded security cable for Wiegand, or a 120-ohm twisted RS-485 pair plus power pair for OSDP. | Wiegand normally uses power, 0 V, D0 and D1 plus optional LED/buzzer/tamper. OSDP normally uses A/B as one twisted pair plus reader power. | Credential data and reader power; OSDP and Wiegand are different interfaces and are not paralleled. | Dedicated controller reader port using only the exact model's labelled terminals. | Protocol, shield treatment, topology, termination, reader current, voltage drop and supported distance. |
| C2 | Cat6 U/UTP 4-pair solid copper | 2 / 4 Door Controller to Security LAN | Solid-copper Cat5e or Cat6 balanced Ethernet cable; Cat6 is the normal new-install choice. Fibre may replace copper for distance or electrical isolation. | Four twisted pairs / eight conductors, terminated consistently to T568A or T568B. | Ethernet data only unless the named port is specifically documented as PoE. | RJ45 network termination or the stated SFP/fibre interface. | 90 m permanent link / 100 m channel for copper Ethernet, port role, VLAN and whether the port supplies PoE. |
| C3 | 2-core 0.5 mm2 per dry-contact function; 4-core or more for powered REX/monitoring | Door Contacts and REX to Controller Door I/O | Stranded security/alarm cable. Four-core is common for a powered detector or many keypad buses; use six/eight core where extra circuits or spares are required. | Powered devices normally need positive and negative supply conductors plus a zone/relay pair or manufacturer bus conductors. | Low-voltage power and zone, tamper or proprietary bus data as defined by the panel/device. | Panel zone/bus and device terminals; end-of-line resistors belong at the supervised end only when the exact panel requires them. | Exact conductor functions, EOL value/configuration, cable gauge, bus topology, current draw, voltage drop and maximum bus length. |
| C4 | Internal controller relationship - no external field cable | 2 / 4 Door Controller to Controller Door I/O | Normally a dedicated two-core low-voltage control pair for a dry contact; use additional cores where power, supervision or status feedback is required. | A relay uses COM with NO or NC as selected by the required normal/fail state. The relay contact must not be mistaken for a power source. | A command, status or release state. Lock/gate operating power normally comes from a separate correctly sized supply path. | Exact relay and receiving input terminals from both current manuals; fire/egress interfaces require the approved project design. | NO/NC logic, voltage/current rating, wet versus dry input, supervision, required fail state and fire/egress compliance. |
| C5 | 2-core 0.5 mm2 low-voltage control cable per door | Controller Door I/O to Locks and Battery PSU | Normally a dedicated two-core low-voltage control pair for a dry contact; use additional cores where power, supervision or status feedback is required. | A relay uses COM with NO or NC as selected by the required normal/fail state. The relay contact must not be mistaken for a power source. | A command, status or release state. Lock/gate operating power normally comes from a separate correctly sized supply path. | Exact relay and receiving input terminals from both current manuals; fire/egress interfaces require the approved project design. | NO/NC logic, voltage/current rating, wet versus dry input, supervision, required fail state and fire/egress compliance. |
What "security cable" means
Security cable is a trade description, not a complete specification. On these pages it means multicore, stranded, full-copper extra-low-voltage alarm/access cable. A common Australian product is described as 14/0.20, approximately 0.44 mm2 per conductor, or nominal 0.5 mm2. The installer must still specify core count, conductor area, copper construction, twist/shield requirement, jacket/environment rating and permitted route. It is not Cat5e/Cat6, mains cable, fire-rated cable or automatically suitable for lock power.
| Cable description | Typical use | Important limitation |
|---|---|---|
| 2-core stranded copper | A simple unpowered contact, dry-contact trigger or separately designed DC power pair | Not enough for a powered PIR that also needs an alarm-contact pair. For lock power, calculate conductor size from voltage, current, inrush and distance. |
| 4-core stranded copper | Common for one powered PIR: positive and negative supply plus two alarm-loop conductors; also used for some proprietary four-wire keypad/module buses | Four cores do not define the function or resistor. Label both ends and follow the panel/device manual. |
| 6-core or 8-core stranded copper | Powered devices needing alarm, tamper, auxiliary functions or useful spare conductors | Do not join spare conductors to increase current capacity unless the equipment/cable design explicitly allows it. |
| Twisted or shielded security/bus cable | RS-485/OSDP and other buses only where the manufacturer specifies impedance, twist and shield treatment | Ordinary alarm cable is not automatically a compliant RS-485, OSDP or Ethernet cable. |
| Heavier two-core lock/power cable | Electric strikes, maglocks, sirens or other higher-current ELV loads | Common 0.5 mm2 alarm cable may be too small. Select 1.0 mm2, 1.5 mm2 or another size only after a voltage-drop and inrush calculation. |
Core colours are identification aids only; they do not create a universal positive, negative, zone, tamper or data standard.
Are any resistors required?
| Circuit | Resistor required? | Where it belongs | How to select it |
|---|---|---|---|
| Door contact or REX input | Only if the selected controller supports and is programmed for supervised inputs | At the field contact/device | Use the controller's exact resistor value and arrangement. Many basic access inputs are ordinary unsupervised dry contacts and use no resistor. |
| Wiegand, OSDP/RS-485, Ethernet and reader power | No EOL zone resistor | Not applicable | RS-485 termination, where required, is a bus-termination issue and must not be confused with alarm EOL supervision. |
| Strike, maglock or relay coil | Not an EOL resistor | Suppression is fitted at the inductive load when required | A flyback diode for DC or an approved MOV/RC suppressor may be required by the lock/controller manufacturer. Polarity and device type matter. |
Never choose a resistor by cable colour or by the phrase "security cable". First identify the exact input, panel model and programmed supervision mode. An EOL resistor belongs at the end of the supervised circuit; placing it across the panel terminals defeats cable supervision.
Recommended cable schedule by function
A multi-door system is not one cable loop. Plan a separate, labelled home run for each reader and each door's field devices unless the selected controller manual explicitly permits a shared OSDP/RS-485 bus.
| Function | Recommended cable type | Route | Distance rule | Design notes |
|---|---|---|---|---|
| Controller network | Cat6 U/UTP, 4-pair solid copper; do not use CCA | Controller to switch/router | Design to a 90 m permanent link / 100 m channel | Use a dedicated LAN outlet, document the IP address and keep it on the approved security network or VLAN. |
| OSDP / RS-485 reader data | One 120-ohm shielded twisted pair for A/B, plus a separate power pair; a 4- or 6-core composite reader cable is commonly practical | Reader to compatible controller port | Exact controller/reader manual | Keep A/B as a twisted pair. Follow the controller's permitted bus topology and termination; do not assume star splices are supported. |
| Wiegand reader | 6-core shielded security cable minimum; 8-core where LED, buzzer, tamper or a spare pair is required | One point-to-point cable per reader | Exact controller/reader manual | Typical conductors are reader power, 0 V, D0 and D1, with optional LED/buzzer/tamper. Wiegand and OSDP are alternatives, not conductors to parallel together. |
| Reader power | Dedicated 2-core power pair, commonly 0.5 mm2 or larger after voltage-drop calculation | Controller/reader PSU to reader | By voltage drop and reader current | Do not borrow a data conductor as a higher-current return. Confirm whether the controller port can power the selected reader. |
| Door position contact | 2-core 0.5 mm2 security cable; use 4-core where monitoring, EOL placement or a spare pair is required | Door reed/contact to controller door input | Site-specific | Run separately from lock power where practical. Use only the resistor arrangement required by the exact controller. |
| Request to exit | 2-core 0.5 mm2 for a dry-contact button; normally 4-core or more for a powered PIR REX | REX device to controller input | Site-specific | A powered REX needs supply conductors as well as the relay pair. Safe egress must not depend on guessed controller programming. |
| Controller to lock PSU trigger | 2-core 0.5 mm2 low-voltage control cable per door | Controller relay to lock PSU/control relay | Site-specific | Use the controller relay as a control path. Do not place lock current through it unless the selected controller's published rating and the lock load explicitly permit it. |
| Lock power | Dedicated 2-core 1.0 mm2 or 1.5 mm2 is a common starting point; final size must follow voltage-drop and current calculations | Battery-backed lock PSU to strike or maglock | By lock current, voltage and cable run | Keep each door identifiable. Confirm 12/24 VDC, fail-safe/fail-secure behaviour, inrush current and required power-failure state. |
| PSU status / cabinet tamper | 4- or 6-core 0.5 mm2 security cable as required | PSU fault, AC-fail, low-battery and tamper contacts to monitored inputs | Site-specific | Only connect monitoring states the selected PSU and controller support; label every input. |
| Fire / emergency release | Cable and interface specified by the fire, access and egress design | Fire interface / emergency release to locking circuit | Project-specific | This is not a generic security-cable decision. The release path, supervision, cable type and fail state require project-specific compliance review. |
Practical rough-in allowance per door: one reader cable, one door-contact cable, one REX cable, one lock-control/power route and any required emergency-release wiring. Provide a Cat6 outlet, controller power, battery space and labelled spare cores at the secure controller cabinet.
Which Security Wholesalers systems does this apply to?
| System family | Door capacity | Reader/network path | Where it fits |
|---|---|---|---|
| Hikvision DS-K2602-GN/Aust | 2 doors | TCP/IP uplink; RS-485 and Wiegand readers | Suitable for a conventional two-door controller cabinet. Match DS-K1100-series or other supported readers to the selected protocol. |
| Hikvision DS-K2604-GN/Aust | 4 doors | TCP/IP uplink; up to 8 RS-485 or 4 Wiegand readers | Direct match for four controlled doors with door contacts, exit buttons and lock relays. |
| Hikvision DS-K2702X-P / DS-K2704X or X-P | 2 or 4 doors, expandable | Web-managed; OSDP/RS-485 and Wiegand options vary by model | Better fit where web configuration, expansion, anti-passback or interlocking is required. Confirm whether the packaged AC cabinet or low-voltage module version is being ordered. |
| Dahua ASC2204C-D | Up to 4 doors, including two-way reader arrangements | TCP/IP with RS-485 and Wiegand reader interfaces | Current Dahua multi-door match for offices, commercial sites and larger residential projects. Use Dahua's exact port allocation and reader manual. |
| Inner Range Inception | Up to 4 lock outputs in a compact integrated intrusion/access design | Ethernet management with Inner Range reader and expansion options | Applies where access control and alarm functions belong in one platform. It is not terminal-for-terminal equivalent to a dedicated Hikvision or Dahua four-door board. |
This drawing is deliberately platform-neutral: the physical functions are common, but the terminal names, allowable reader topology, relay ratings, software and licensing are not interchangeable. Select the controller family first, then issue the final cable schedule from that exact model's current manual.
OSDP or Wiegand?
RS-485-based OSDP can provide supervised two-way reader communication and is the stronger choice for a new high-security installation. Use the cable, topology, addressing and termination required by both controller and reader.
Wiegand remains common and broadly compatible, but each reader normally needs its own home-run cable and the interface provides less supervision. Allow enough cores for power, D0, D1 and optional LED, buzzer or tamper functions.
Two-door versus four-door planning
- Choose two-door when the finished scope is genuinely limited to two controlled openings and there is no near-term expansion case.
- Choose four-door when three or four openings are known, when a reception/rear-door/records-room layout is likely to grow, or when spare capacity is worth more than a later controller replacement.
- Count reader directions as well as doors. Entry-only and entry/exit reader arrangements consume different reader ports even when the number of physical doors is unchanged.
- Keep the controller secure. Locate the board, network termination and battery-backed supplies on the secure side; external readers should not contain the lock-power decision.
- Separate access logic from life safety. Maglocks, fire release, emergency break-glass and free-egress hardware require a project-specific release design.
Power requirements
Confirm the selected equipment's supply method, PoE class or DC input, total load and backup requirements before ordering. Keep lock power separate from data-path assumptions, calculate voltage drop for low-voltage loads, observe battery polarity and isolate any 230-240 VAC work to an appropriately licensed electrician.
How the wiring path works
Read the physical cable path first, then power, relay or I/O paths, network addressing and finally app or cloud registration. A device that appears offline may have a physical link, power, addressing or configuration fault; Wi-Fi and cloud registration should not be used to hide an incorrect LAN design.
Practical installation sequence
- Confirm every exact device model and current manual.
- Confirm cable types, routes, separation and distances.
- Check PoE or DC power capacity and site voltage drop.
- Mount and cable devices with power isolated.
- Test continuity, polarity and earth/surge arrangements where applicable.
- Power one subsystem at a time.
- Activate and address network devices.
- Configure relay, call or recording behaviour only after the physical path works.
- Test local operation, remote operation and failure modes separately.
- Record final models, IP addresses, cable IDs, settings and diagram revision.
Common mistakes
- Assuming a port provides PoE without checking the port and total switch budget.
- Confusing a recorder's isolated camera ports with its main LAN uplink.
- Powering a lock from an unsuitable relay or supply.
- Guessing normally-open, normally-closed, polarity or resistor details.
- Ignoring voltage drop, surge exposure or power-failure behaviour.
- Treating app setup as proof that the physical cabling is correct.
Troubleshooting
| Symptom | Likely cause | Test | Corrective action |
|---|---|---|---|
| Device has no power | Incorrect supply method or exhausted PoE budget | Check port status and measure only with the correct procedure | Match the power source to the exact device manual |
| Device powers but is offline | Wrong LAN path, addressing or activation state | Confirm link lights, subnet, gateway and device state | Correct physical LAN and addressing before cloud setup |
| System works locally but not remotely | Internet, DNS, account or cloud registration issue | Prove local operation first, then test WAN services | Correct router or account configuration; do not recable a working local link |
| Relay or lock action fails | Wrong contact logic, power path or load assumption | Test relay and lock supply as separate subsystems | Use the exact manual and suitable lock PSU; confirm egress requirements |
Compatible products and categories
Confirmed live product page
Confirmed live product page
Confirmed live product page
Confirmed live product page
Confirmed live product page
Browse current category
Browse current category
Browse current category
Browse current category
Exact product links above were confirmed on the current Security Wholesalers site on 2026-07-19. Category links are used when an exact active compatible product was not confirmed.
Related diagrams
Frequently asked questions
Can I buy cable using this guide?
Use the cable schedule and buying list to shortlist the cable, then confirm the exact equipment model, route, distance, environment and manufacturer requirements before ordering.
Can cable distance or power capacity be assumed from this drawing?
No. Confirm the selected devices, PoE budget, voltage drop, cable construction and current manufacturer instructions.
Where do terminal names and resistor values come from?
They must come from the exact current manual for the selected model. Do not transfer terminal names, polarity or resistor values from a similar product.
Can this replace the manufacturer manual?
No. It is a planning and support reference only and does not replace manufacturer instructions, licensed work, fire engineering, egress assessment or site commissioning.
Technical references
| Manufacturer | Document | Revision | Relevant pages | Reference | Accessed |
|---|---|---|---|---|---|
| Hikvision | DS-K2600 series controller product specifications and current Security Wholesalers listings | Current listing | Interfaces and door capacity | Official/source reference | 2026-07-19 |
| Hikvision | DS-K2704X access controller product specification | Current listing | Reader interfaces, inputs and outputs | Official/source reference | 2026-07-19 |
| Dahua | ASC2204C-D multi-door controller product specification | Current listing | Door capacity and reader interfaces | Official/source reference | 2026-07-19 |
| Inner Range | Inception Controller data sheet | October 2020 | Access-control examples, inputs, relays and power | Official/source reference | 2026-07-19 |
Diagram revision: 1.1. Confirm the exact current manual for the selected equipment before installation.
Australian installation and safety notice
General guide only. Confirm current manufacturer instructions and site requirements. Work involving 230-240 VAC must be completed by an appropriately licensed electrician. Fire-release interfaces, emergency exits and door locking require project-specific compliance assessment. Keep mains and ELV cabling appropriately separated, isolate power before work, observe battery polarity and calculate voltage drop for the real load and cable run.