Connections

The Coordinator allows communication with the onboard WiMAC hardware in most non-Server Cloud Nodes. Normally, you won't need to add this Connection to a Cloud Node unless the Connection was deleted.

Name -  Enter a name for the connection here. This is typically named Wireless Coordinator. 

Port - This will always be 0.

After adding the Coordinator Connection, select Save.

An Ethernet connection is a Controller that uses a CAT5/CAT6 network cable to connect 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 the Controller is not discoverable, you can manually add the connection for Red-series controllers if you have obtained the Controller's IP address. However, this is not recommended, as the Cloud Node may not detect the Controller as a Red-series Controller, limiting Red-series Controller functionality.

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. Assign 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 module's web interface (access it by entering the module's IP address into a web browser).

First, select whether the Controller is a PDK (Red-series) Controller with an integrated PDK module or a Legacy Controller with a 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 10001 unless PDK Technical Support or IT personnel at the installation site specifies otherwise.

Notes regarding Lantronix Modules:

When configuring an Ethernet connection for Legacy hardware, you must select Lantronix. 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 on the computer.

After adding the Ethernet Connection, select Save.

A Gateway Connection, also known as a Wireless Gateway Connection, is a Legacy connection used to provide the WiMAC signal to a Cloud Node without wireless connectivity, such as a server Cloud Node or an 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 controller's location).

Port - This is normally 2101 unless you change it in the Gateway web interface.

IP Address - Enter the IP address for the Gateway. Set this to Static in the Gateway web interface.

After adding the Gateway Connection, select Save.

An Onboard Connection only applies to the built-in Controller in non-Server Cloud Nodes, both Legacy and Red series hardware. Normally, you won't need to add this Connection to a Cloud Node unless the Connection was deleted.

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 attached door or the installation location of the Controller.

Port - This will always be 1.

After adding the Onboard Connection, select Save.

This connection allows communication with Aperio hubs and the Cloud Node. More information can be found here. 

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.

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

After adding the Aperio Connection, select Save.

A Red Hub is a Connection that adds the HubNet (BLE Network) to your system, allowing you to connect Red Wireless Locks to the Cloud Node.

Name -  Enter a name for the connection here. This can be anything you like, from an internal code to a descriptive name for the connection, such as the Hub's location.

IP Address - Enter the Hub's IPv4 or IPv6 address.

MAC Address - Enter the MAC Address for the Hub. 

Port - Use the default Port 10001 unless PDK Technical Support specifies otherwise. 

Antenna - Select External Antenna if installed; otherwise, select Internal Antenna.

After adding the Red Hub Connection, select Save.

Selecting a previously added Connection name displays the Connection details, allowing the Connection to be edited. All settings available during initial setup, except Connection Type, are available when editing the Connection. The Connection can also be deleted from the drawer.

When editing a Red High-security Ethernet connection through the Connections tab, the options displayed differ from those shown on Discovery. Use the default IPv6 option to reduce the chance of an IP conflict. 

Controller Ethernet

You can adjust the Ethernet Module settings 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.

Connection Locking

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