Knowledge base 73: Wiring Requirements

Knowledge base 73: Wiring Requirements

Cable Specifications

For RS485 connections between ACUs we recommend using Belden 8723 or equivalent. This is a 2 twisted pair cable, with each pair screened as well as an overall screen.
Note: the RS485 ‘+’ and ‘–’ connections must be run on either side of the same twisted pair (e.g. Green and White), with a separate core (e.g. Black) used for the reference.
The total distance of an RS485 bus must not exceed 1000m.

From the i-Net ACU to Wiegand readers we recommend using Belden 9538 (or equivalent). This is an untwisted 8 core cable with an overall screen. Do not use twisted pair CAT5 or CAT6 cables to connect readers to the i-Net ACU.
The maximum length of the Wiegand reader cable is 80m but if this exceeds 25m we recommend using a local power supply for the reader.

Between the i-Net ACU and Locks/Exit Buttons we recommend a 22 AWG or thicker gauge alarm cable. We recommend cables with spare cores in case a core breaks. Do not use CAT5 or CAT6 cables to connect locks or exit buttons.

 

To ensure optimum performance on the i-Net RS485 bus, please ensure that the following rules are implemented:

1)  The bus must be wired as a 3 wire bus using Belden 8723 (or equivalent) cable with the ‘+’ and ‘-‘ connections on same twisted pair (e.g. green and white).

2) For older legacy controllers (V1 & V2) the RS485 REF connection must be connected to GND at the Master i-Net as shown below, this isn't required for the iNet Plus (V3) -



3)    The bus must not exceed 1 Km end to end and devices at each end of the bus must be terminated.  Never spur off the RS485 bus to create a “third end”.

4)    Each device on the bus must have a unique address.  The Master i-Net must have address 0, and each expansion device (expander or slave i-Net) are configured in the range 1 to 15 (F).

5)    Devices must be connected to the correct bus;  expanders (AC-3151 / AC-4311) to RS485 A or slave i-Nets to RS485 B.  Always ensure that the Master i-Net is configured to operate on the correct bus (switch 2 on the bank of 4 option switches).

For further information, please refer to the Installation Manual for the i-Net and expanders.


    • Related Articles

    • Knowledge base 136: Changing a Downstream (RS-485) iNet into a Master iNet.

      This document explains how to change an iNet door controller from being on the RS-485 bus into a Master controller. In the following screenshots, the downstream iNet with bus address #1 on the “Ground Floor” Master will be changed to a Master called ...
    • Knowledge base 216: iNet IP Utility

      The iNet IP Utility has been designed to make the setup of iNet's onto your customers network as simple as possible. The tool gives the ability to setup your controllers to static addresses, without the need to only plug 1 iNet onto the network at ...
    • Knowledge base 207: Identity Access Removed or Lost without backups

      If the PC holding Identity Access software has failed and no external backup is available, then a reinstallation and recommission of the system will be required. A site survey may be required to ensure the system is setup as it was previously. Some ...
    • Knowledge base 114: Tamper on HID iCLASS SE and multiclass SE Readers.

      The following bulletin explains how to use the Tamper feature on iCLASS SE and multiclass SE Readers. The tamper is enabled as default on the above readers, the Tamper sensor being signaled via the VIOLET wire in the pigtail, or by connector P2-5 on ...
    • Knowledge Base 217 : Performing iNet Controller Firmware Updates

      Requirements - - iNet Door Controller. - iNet Controller Firmware Files. - Provisions to to make sure the doors and door controllers are accessible during the update. - Access to the Identity Access software. Identifying your iNet controller version ...