Controller Install/Set-up

This topic covers installing and configuring the Galaxy Controller at the Customer/End-User’s building or facility.

 

REQUIREMENTS

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

     

 

635 Controller Installation:

 

STEPS

  1. Leave the Ethernet cable disconnected from the CPU until 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 board ...

    1. before you install the board in the enclosure, set a unique board address using the DIP switch. You cannot reach the dip switch after the board is installed.

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

  4. Complete all of the field wiring to the card readers, locks, door position switches and REX request to exit devices. See the GCS Hardware Installation Manual for details.

  5. Apply power to the 635 controller panel. The yellow “power” LED should be illuminated on each board. The DRM and other daughter boards should come up with their correct IDs based on their DIP switch settings.

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

     

    635 CPU Programming

  7. 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 Server utility.

    You will need the Event Server information from your On-boarding Document ...

    • Event Server IP:     [ Event Server IP Address ]       

    • Remote TCP Port:  [ Event Server Remote Port]     

    • Encryption Key:     [ Event Server Pass-phrase ]     

     

  8. Connect the Ethernet cable to the CPU Board. The board should automatically connect with the Event Service using the settings done in the prior step.

  9. Sign-in to your System Galaxy software on the cloud server using the VPN Client and Windows Remote Desktop. (these steps were discribed in the topic Establish Dealer VPN Connection.

  10. In System Galaxy software, verify that your new controller is connected by one of the following ways

    • open the Diagnostics screen from the View > Loop/Cluster Diagnostics Verify that the controller has connected status or by the presence of new transactions in the monitoring tab.

  11. Update the controller to the latest (flash) firmware – (right-click on the Cluster in the Hardware Tree, choose Load).

  12. Load the controller with the current database information.

  13. Continue with normal programming.

 

 


Notes / Best Practices:

  • Two 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