Once the site has been created, the default configuration will display. The default configuration supports the pre-wired mains power failure and battery low inputs.
If configuring the site remotely before installation, the controller assignment can be completed last, prior to site activation.
To associate a controller with a site, perform the following procedure:
Navigate to the customer's site.
Click the Scan controller QR code button and scan the QR code printed on the controller.
If using a laptop, take a photo of the QR code using your phone and present it to the laptop. If you are unable to scan the controller's QR code, you can enter the controller's ID in the Controller ID field. The controller's ID is printed on the controller, below the QR code.
Click the ASSIGN CONTROLLER button.
The controller will come online and connect to the Gallagher cloud. An IP address is automatically assigned to the controller via DHCP. There is no MAC address or IP addressing required. The controller will download the latest firmware and update its default configuration. This takes approximately five ( 5 ) minutes.
Notes:
If the controller does not come online, check the site has an internet connection.
If the site has a firewall preventing the controller from connecting to the internet, the following ports on the controller need to be reachable:
Port | Protocol | Details |
---|---|---|
If the message 'Cannot assign controller' displays, the controller has already been assigned to a site.
Select the Controller.
The ‘Controller’ lightbox displays.
Notes:
If the site is using tamper detection, the controller’s optical tampers can be enabled here.
The controller’s firmware version and application version are shown here.
The Controller's 'EOL Resistors' setting is only applied to the '8In Board 1' by default; not the '8In4Out Board 1'. This is because the 8In4Out Board's two power-monitored inputs (Battery Low and Mains Failure) require 4k7 Ohm Rs in order to function, and therefore are set this way in the 8In4Out Board's default configuration.
The controller’s ‘Event History’ shows events generated by the controller, and cloud events that are related to the controller. Use the event history to help diagnose issues with the site.
67
UDP
DHCP to internal router
53
UDP
DNS to internal router
123
UDP
NTP to time.google.com
443
TCP
SMB Cloud HTTPS