The Cloud Node is the main system panel and the gateway to the pdk io cloud platform; it’s the only device needed to get a system up and running. The Cloud Node includes a built-in single io with the ability to control a single door, making it ideal for a single-entry location. The Cloud Node connects to the Internet, access control hardware, and to the network. Up to 1000 access control devices can be configured on a single Cloud Node.
PDK Cloud Node Overview
NOTE: A Cloud Node MUST have a hard-wired Ethernet cable connection with Internet access.
Additional single io, eight io, and eight io+ door controllers can be added to the Cloud Node to control any additional doors. The single io can be installed at each door location. It can even power locks, Rex devices, and more.
To set up the Cloud Node to the network, the node’s serial number, a unique descriptive node name, and the Internet are required. A node name can be defined by its location or any schema of your choice needed to identify the node.
NOTE: Multiple customers may not control the same Cloud Node. Each customer has their own Cloud Node(s).
Click the + icon next to Cloud Nodes.
Enter the node’s Assembly Serial # (on the inside cover of the Cloud Node’s box), similar to the following: 1071XXX (where XXX are unique alphanumeric characters).
Enter a unique descriptive Name for the Cloud Node. Click REGISTER.
Once registered, the newly created node is listed in the Cloud Nodes section of the screen (in alpha order where multiple nodes exist).
To configure and manage the newly created Cloud Node and its available features and options, click the Cloud Node icon in the Cloud Nodes section.
The Cloud Node’s Appliances Home screen icons are displayed.
NOTE: The type of icons shown in this Cloud Node Appliances home screen varies depending on the user’s role assigned in Permissions.
NOTE: If two Cloud Nodes are in the same vicinity (even within a mile) and you are unable to detect a wireless device on the nearest Cloud Node, check the other Cloud Node in Discovery to see if it connected to the wrong Cloud Node.