Technical informational / commercial investigation
Hikvision AX PRO System Layout
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
- Wireless PIRs - Interior detection
- Wireless Alarm Hub - System control
- Router / Internet - Cloud path
- Wireless Contacts - Perimeter detection
- Wireless Siren - Local warning
- Mobile App - Users and notifications
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 | Wireless PIRs | Wireless Alarm Hub | Manufacturer radio | No field cable across wireless path | Data/control | Not stated | Wireless detector path |
| C2 | Wireless Contacts | Wireless Alarm Hub | Manufacturer radio | No field cable across wireless path | Data/control | Not stated | Wireless contact path |
| C3 | Wireless Alarm Hub | Wireless Siren | Manufacturer radio | No field cable across wireless path | Data/control | Not stated | Wireless siren path |
| C4 | Wireless Alarm Hub | Router / Internet | Ethernet or Wi-Fi to model | 4 twisted pairs / 8 conductors | Data/control | Not stated | Internet path |
| C5 | Router / Internet | Mobile App | Internet / mobile data | No field cable across wireless path | Data/control | Not stated | Notification path |
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 | Manufacturer radio | Wireless PIRs to Wireless Alarm Hub | No data cable spans the wireless path. Each radio, router or mobile endpoint still needs its specified local Ethernet and power connection. | Radio link through free space; local device cables are documented separately. | Network data over Wi-Fi, licensed/unlicensed point-to-point radio or public mobile/internet service. | Aligned radios/antennas or the applicable router/cloud service. | Line of sight, Fresnel clearance, channel/interference, mounting, surge/earthing, bandwidth, data allowance and failover. |
| C2 | Manufacturer radio | Wireless Contacts to Wireless Alarm Hub | No data cable spans the wireless path. Each radio, router or mobile endpoint still needs its specified local Ethernet and power connection. | Radio link through free space; local device cables are documented separately. | Network data over Wi-Fi, licensed/unlicensed point-to-point radio or public mobile/internet service. | Aligned radios/antennas or the applicable router/cloud service. | Line of sight, Fresnel clearance, channel/interference, mounting, surge/earthing, bandwidth, data allowance and failover. |
| C3 | Manufacturer radio | Wireless Alarm Hub to Wireless Siren | No data cable spans the wireless path. Each radio, router or mobile endpoint still needs its specified local Ethernet and power connection. | Radio link through free space; local device cables are documented separately. | Network data over Wi-Fi, licensed/unlicensed point-to-point radio or public mobile/internet service. | Aligned radios/antennas or the applicable router/cloud service. | Line of sight, Fresnel clearance, channel/interference, mounting, surge/earthing, bandwidth, data allowance and failover. |
| C4 | Ethernet or Wi-Fi to model | Wireless Alarm Hub to Router / Internet | 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. |
| C5 | Internet / mobile data | Router / Internet to Mobile App | No data cable spans the wireless path. Each radio, router or mobile endpoint still needs its specified local Ethernet and power connection. | Radio link through free space; local device cables are documented separately. | Network data over Wi-Fi, licensed/unlicensed point-to-point radio or public mobile/internet service. | Aligned radios/antennas or the applicable router/cloud service. | Line of sight, Fresnel clearance, channel/interference, mounting, surge/earthing, bandwidth, data allowance and failover. |
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 |
|---|---|---|---|
| Wireless detector path | No field EOL resistor | Not applicable | The radio link is supervised by the platform. A wired input on a detector, transmitter or hybrid panel may still need the exact manufacturer's resistor network. |
| Hybrid/wired expansion input | Model and programming dependent | At the field end when the input is EOL supervised | Use the exact expansion-module manual; do not borrow a value from Bosch, DSC, Ness, Hills or Paradox. |
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.
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 |
|---|---|---|---|---|---|
| Hikvision | DS-PWA96-M-WE AX PRO Datasheet | 2024-03-22 | Wireless zones, network and power overview | 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.