Configuration - Connections

The Coordinator option is present to allow communication with the onboard WiMAC hardware in most non-Server Cloud Nodes. Normally you will not have to add this Connection to a Cloud Node unless the Connection was deleted.

Name -  Enter a name for the connection here. We normally recommend naming the Connection as Onboard WiMac but this can be named differently if you like.

Port - This will always be 0.

When finished adding the Coordinator Connection, tap/click the Save button.

An Ethernet connection is a Controller using a CAT5/CAT6 network cable to connect the Controller to a Cloud Node on the same local network.

For Red High-Security controllers, it is recommended to discover the Controllers using the Discovery tab. If you can not discover the Controller, you can manually add the connection for the Red series controllers if you have obtained the IP address for the Controller. It is not recommended to do this, as the Cloud Node may not detect the Controller as a Red-series Controller, limiting access to some of the functionality of the Red-series Controller.

With Legacy Controllers (Single IO, Eight IO, Gate IO, and Pedestal IO units), the Lantronix module is initially set up to use DHCP to automatically obtain an IP address. These modules must be assigned a static IP address using the Lantronix network utility software, by configuring a DHCP reservation (contact the Network Administrator for information on this), or through the web interface for the module (accessed by entering the IP address for the module into a web browser).

First, select if the Controller is a PDK (Red-series) Controller, with an integrated PDK module or a Legacy Controller with a Lantronix Module with an installed Lantronix module.

Name -  Enter a name for the connection here. This can be anything you like, from an internal code to a descriptive name for the controller, for example, naming the Controller for the door(s) attached or the installation location of the Controller.

IP Address - Enter the IP address for the Ethernet controller.

Port - Use the default Port of 10001 unless specified otherwise by either PDK Technical Support or IT  personnel at the installation site.

Notes regarding Lantronix Modules:

When configuring an Ethernet connection for Legacy hardware, you must select Lantronix for the module. Selecting PDK for the module will cause issues with the module's functionality.

Download the Lantronix Device Installer (either the web-based or stand-alone version) from the Lantronix website to install and use this application.

When adding an Ethernet door controller, ensure that you are connected to the same network as the Legacy Controller and that the correct Network is selected in the Lantronix Device Installer. If the correct Network is not listed in the Lantronix Device Installer, turn off the WiFi adapter on the computer.

When finished adding the new Ethernet Connection, tap/click the Save button.

A Gateway Connection, also known as a Wireless Gateway Connection, is a Legacy connection that is used to provide the WiMAC signal to a Cloud Node without wireless connectivity, such as a server Cloud Node or Ethernet-only version of Red Cloud Node. Unlike using additional Cloud Nodes in a multi-site Customer Account, a Gateway Connection must be on the same local area network as the Cloud Node.

Name -  Enter a name for the Gateway Connection. This can be anything you like, from an internal code to a descriptive name for the Gateway (for example, the location where the controller is located).

Port - This will normally be 2101 unless changed in the web browser interface for the Gateway.

IP Address - Enter the IP address for the Gateway. This needs to be set to 'Static' in the web interface for the Gateway.

When finished adding the new Gateway Connection, tap/click the Save button.

An Onboard Connection only applies to the built-in Controller in non-Server Cloud Nodes, both Legacy and Red series hardware. 

Name -  Enter a name for the Onboard Connection here. This can be anything you like, from an internal code to a descriptive name for the controller, for example, naming the Controller for the door attached or the installation location of the Controller.

Port - This will always be 1.

When finished adding the new Onboard Connection, tap/click the Save button.

When connecting a new Aperio Hub to the Cloud Node, select Aperio as the Connection Type.

Name -  Enter a name for the connection here. This can be anything you like from an internal code to a descriptive name for the controller such as the door(s) attached to the Aperio hub or the location where the Aperio hub is located.

MAC Address - Enter the MAC address for the new Aperio hub.

When finished adding the new Aperio hub Connection, click the Add button.

This allows you to make changes to the settings for the Ethernet Module on the Red High-Security device.

Address Mode: This allows the Red High-Security device to use IPv6 or IPv4. Please note that IPv6 cannot be used if the Cloud Node and Red High-Security devices are on different subnets/networks.

Auto - This will show the current IPv6 and IPv4 addresses.

IPv4 Static -  This allows you to configure the IPv4 address as a static IP.

This feature allows an Integrator-Partner to 'lock' the Connection for the selected Red series Controller. This will remove the ability to physically change the hardware for the current connection on the Cloud Node and use it elsewhere without the Controller being 'unlocked' first. This will also keep a different Cloud Node on the same network from discovering and adding the Red Controller to the other system.

Tapping or clicking on the button shown above will display the pop-up shown in the image below and the Connection can be 'Locked'.