Hardware Installation

This topic covers Hardware Programming Requirements and Controller Installation Steps for installing the hardware install on the End-User’s site.

 

FEATURED TOPICS

 


 

Board Programming Requirements

This section lists the requirements and tools you must have to program the controller boards.

 

  1. You will need a Programming Cable and Board Programming Tool (Web Config Tool or Direct Serial Connect) to configure the CPU and daughter boards.

     

    Additional Requirements ...

  2. Each Controller must be set to the correct Cluster ID and must match the SG software programming. However, if you are adding more than one controller, you must configure those in the SG software to match the additional panels.

    1. When you are adding hardware for the first Customer in System Galaxy, you may add the first Controller to the first Cluster. You can add additional controllers to the first cluster and one panel may be pre-configured for you. Add additional panels for that customer to the same cluster - or you can add a second cluster if you need to and put additional panels in the additional cluster(s).

    2. When you are adding hardware for a different Customerin System Galaxy, you must create a new Cluster for the new customer. Do not mix the hardware programming for Customer 1 with the hardware programming for Customer 2, or Customer 3, and so on. Each Customer’s hardware must be on different Clusters.

  3. Each Controller must have a unique Unit ID number within the Cluster, as determined by the SG software.

     

  4. The CPU Number should be set to "1".
     If a second (dual) CPU board is installed, its CPU number should be set to "2".

     

  5. All daughter boards (DPI, DIO, DSI, etc.) must have a unique Board ID within their Unit (controller/panel).

    • Board numbers 1 through 16 are valid for each controller.

    • For 635-DPI(DRM): use onboard DIP switches to set a unique binary address on the data bus.

      You must set the DIP switch address before you install the board into the board slot.

       

  6. A Unique/Valid IP Address must be used for each 6xx-series controller. This address is typically provided by the IT Department or Internet Service Provider. The IP Address assigned to the controller must have the capability to access the Internet. 6xx-series controllers also support DHCP addressing; however, it is recommended to use static addresses for the stability of the Access Control System.

     

  7. The controllers communicate with the Event Server on the port# that is shown in your Onboarding Document.

    1. The Outbound Port must be unblocked at firewalls, routers and switches, etc.

    2. Typical "NAT" type routers do not need special configuration, as they allow any/all outbound traffic.

       

  8. See the Controller Panel Configuration for steps to configure your panel by Web Connect or by Direct Connect.  

 

 

 

 

Control Panel Installation Steps

This section provides basic, high-level steps to install a controller.

 

REQUIREMENTS

  • Before you can do this step, you must have the Event Server IP Settings that the controller needs to establish connection to the cloud server are found in the On-boarding Document (PDF) that Galaxy provides.

     

 

STEPS

  1. Leave the Customer’s Ethernet Network cable disconnected from the CPU until you reach Step #8.

  2. Install the 635-CPU in the first slot (farthest from the power supply) in the enclosure.

  3. To install each 635-DRM(DPI) board ...

    1. Before you install the board, set a valid, unique board ID address using the binary DIP switch. Address 1 - 16 is valid. Each daughter board ID must be unique within the panel.

    2. Install DRM boards in the same sequential order as their addresses, with DRM #1 being next to the CPU board.

  4. Complete all of the field wiring to the card readers, door locks, door position switches and REX request to exit devices. Make sure to install door lock surge suppression diodes correctly.
    See the GCS Hardware Installation Manual for details.

  5. Apply power to the controller panel. The yellow “power” LED should be illuminated on each board.

    NOTE: The DRMs and other daughter boards (DIO, DSI, etc.) should come up with their correct IDs based on their DIP-Switch settings. Each board must have a valid, unique ID on the data bus in the panel(no duplicates).

  6. Perform a “cold reset” by holding the reset button on the CPU board for fifteen (15) seconds.

  7. Connect the Ethernet Network cable to the CPU Board.

    • Configure the CPU and other hardware using the Web Config Tool (instructions below).

    • (optionally) Configure the CPU and hardware using Direct Connect to Serial port (below).

    • After you save the CPU settings, the controller CPU should come up and connect to the Event Service using the settings you configured.

     

  8. Now you can import the controller into System Galaxy from the Loop Diagnostics screen. See

 

 

 

Controller CPU Programming

  1. Configure the Panel’s CPU with the IP Address, Cluster ID, Unit ID and other information using either a Serial Connection or the 635 Web configuration Tool.

     

     

     

     

     

  2. Verify that your new controller is connected in System Galaxy software ...

  3. Update the controller to the latest (flash) firmware as needed – The CPU must run the flash version that is compatible with the System Galaxy software.

    • Begin loading flash by right-clicking on the appropriate Cluster icon in the SG Hardware Tree, choose ‘Load’. The GCS Loader window will open. You can select the individual controller and send a ‘Get Controller Info’ command.

    • You can find the compatible Flash version in the Help About screen from the SG menu.

       

  4. Also Load Data to the controller with the current database information from the GCS Loader window.

  5. Continue with normal programming.

 


Notes / Best Practices:

  • Two surge suppression diodes are included with each 635 DRM board. It is imperative that a diode is installed at each locking device - as close to the lock as possible - for stable operation.

  • Magnetic locks ("maglocks") typically contain their own surge suppression circuitry, and do not require a diode. All other devices - including relays and contactors - should have a diode installed.

  • Locking hardware designed to operate on AC or DC voltage source may contain a bridge rectifier within the wiring harnes. This component should be removed when the lock is used with DC voltage sources - it impairs the effectiveness of the diode.

  • The use of AC powered locking devices is not recommended.

  • The proper configuration of the network filter options is necessary for stable operation. These filters are completely disabled when the controller door is open! For this reason, you must verify that the tamper switch is correctly wired, and that the controller door closes properly. If you are not using a tamper switch, the tamper input should be jumpered to ground.

  • If you are not using door contacts, you should jumper the door status input (CNT) to ground (COM). Failure to due so will result in alarm events, and adversely affects the behavior of the reader LED.

 

 

 

 

NEXT STEPS