Technical informational / commercial investigation
Hills Reliance Wiring Overview
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
- Existing Legacy System - Third-party or discontinued
- Existing Cabling - Identify and test
- Technical Inspection - Manual and site checks
- Existing Field Devices - Assess individually
- Current Replacement System - Not assumed compatible
- Replacement Category - Current product pathway
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 | Existing Field Devices | Existing Cabling | Existing cable - identify | 4-core minimum; 6-core recommended for a new run | Data/control | Not stated | Existing field cable |
| C2 | Existing Cabling | Existing Legacy System | Existing cable - identify | Confirm from the exact device functions | Data/control | Not stated | Legacy connection |
| C3 | Technical Inspection | Existing Cabling | Test equipment | Confirm from the exact device functions | Data/control | Not stated | Cable inspection |
| C4 | Technical Inspection | Current Replacement System | Design review | 2-core dry-contact control; 4-core allows spare/status | Data/control | Not stated | Replacement planning |
| C5 | Current Replacement System | Replacement Category | Product-selection path | 4 twisted pairs / 8 conductors | Data/control | Not stated | Current category |
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 | Existing cable - identify | Existing Field Devices to Existing Cabling | 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. |
| C2 | Existing cable - identify | Existing Cabling to Existing Legacy System | 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. |
| C3 | Test equipment | Technical Inspection to Existing Cabling | 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 | Design review | Technical Inspection to Current Replacement System | 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 | Product-selection path | Current Replacement System to Replacement Category | 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. |
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 |
|---|---|---|---|
| NX/Reliance zone | Usually yes when the panel is programmed for EOL supervision | At the field contact/detector | Common NX/Reliance installations use 3.3 kohm single EOL. Zone doubling uses paired values such as approximately 3.74 kohm and 6.98 kohm; identify the exact NX/Reliance board and programming before reuse. |
| Special smoke-capable zone | Circuit-specific | At the end of the compatible smoke loop | The NX-8V2 documentation identifies a 680 ohm EOL for its specific two-wire smoke configuration on zone 8. Do not apply this value to ordinary zones or another Reliance model. |
| POS/COM/DATA codepad bus, AUX power and siren | No zone EOL resistor | Not applicable | These are power, data or output circuits. |
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.
What the existing wiring usually looks like
Hills Reliance systems are closely associated with the NetworX NX family, but NX-4, NX-6, NX-8/Reliance 8 and NX-8E/Reliance 128 boards, keypads and expansions are not identical.
| Existing circuit | Usual cable | What the conductors do | What varies or must be checked |
|---|---|---|---|
| Powered PIR / detector zone | Normally 4-core stranded security cable | AUX PWR+ and COM power pair; zone-to-COM alarm loop | Identify any EOL or zone-doubling resistors before removal. NX/Reliance variants and programming can change how a zone loop is interpreted. |
| Reed / unpowered contact | Normally 2-core; 4-core where EOL, tamper or spare conductors are needed | Zone input to COM through the contact and required resistor network | NX-8V2 documentation notes open or short zone behaviour and special handling for its smoke-capable zone. Do not generalise that special circuit to every zone or model. |
| Codepad and expansion bus | Normally a 3-conductor NetworX/Reliance bus for POS, COM and DATA; some field cables contain a spare core | Bus power, common and shared data | This is not the same bus as Bosch, Ness, DSC or Paradox even if the cable has three or four cores. Enrolment and current capacity also matter. |
| Siren / smoke / auxiliary power | Dedicated two-core or multicore wiring sized to each load | Separate bell/siren, smoke power, keypad power and auxiliary-power functions depending on the board | Document the exact panel variant and every powered load before selecting a replacement PSU or output. |
| Communicator | Legacy telephone cable or a model-specific three-wire bus module; modern modules may also use Cat6 to the router | Panel reporting path | A connected network cable does not make the detector/keypad bus Ethernet. Treat the communicator and alarm field wiring as separate subsystems. |
Replacement rule: compare functions, not wire colours. Preserve photographs, labels, resistor locations, bus topology and power measurements before any old equipment is removed.
How to compare it with a replacement
- Record every panel, keypad, detector, siren, communicator and expansion-module model.
- Separate device power, supervised zones, proprietary bus, outputs and communications into different cable groups.
- Identify cable core count, gauge, printed sheath, joins and end-of-line components.
- Measure continuity only with the system safely isolated; identify any fixed mains supply before opening equipment.
- Build the replacement schedule from the new system manual, then mark which existing cables satisfy it without adaptation.
- Replace any unidentified, damaged, undersized or topology-incompatible path rather than promising unreliable reuse.
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
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 |
|---|---|---|---|---|---|
| Interlogix / Hills Reliance | NetworX NX-8V2 Control Panel Installation Instructions | 466-2339 Rev B | 1-2 | Official/source reference | 2026-07-19 |
Diagram revision: 0.9. 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.