The Configuration option in the Cloud Node Appliances home screen is used to configure door and elevator access control devices and communication methods. Up to 1000 access control devices can be configured on a Cloud Node.
Integrator is the only Permission role able to access the Configuration features.
NOTE: Adding permissions to a Cloud Node must be done by the dealer/customer; it cannot be done by Technical Support.
Click the Configuration icon in the Appliances home screen to configure, modify, and view existing devices as well as to add new devices. A list of all added devices can be seen in the Configuration screen listed in alphabetical order. By default, when the Configuration screen is opened, the DEVICES tab is displayed.
Any current devices are listed in alphabetical order. Select an existing device from the list to configure / modify / view any of the devices’ options.
When a device has been connected with a touch io reader, a touch icon appears beneath the device name.
Use the + icon to add a new device.
A device represents a piece of equipment that has been added to the access control system through a connection to a controller.
Add a New Device
Click on the + icon in the lower right of the DEVICES tab in the Configuration screen to add a new device.
1 - Select device category
Depending on the type of device being added, select from one of three categories of device types:
Covers anything used for ingress/egress that is similar to a door or gate.
All other devices that are not a door or gate or elevator such as lights, alarms, etc.
Anything having to do with elevators or elevator control.
2 - Select device type
Dependent on the device category selected you will be presented with a selection of device types to choose.
Primary Reader - The primary reader is the main reader for a single access point and has access to all of its associated ports components (Reader input, AB inputs, Relay) and is also able to be manipulated from states and the touch app.
Additional Reader - The Additional Reader device type is used when associating multiple readers with a single ingress/egress point. The additional reader inherits all of its rules and configuration from the primary reader it is associated to. It is associated with the reader component of its port only and is not visible in states or the touch app.
Generic - The Generic IO Device is used for devices that you do not want direct control of for example a piezo alarm. The Generic IO Device is associated with the AB inputs and Relay components of its assigned port and is not visible in states or the touch app.
Premium - Premium IO Devices are devices that are not related to a door or gate or elevator and that you still want to directly activate or deactivate. An example of a Premium IO Device is a burglar alarm. The Premium IO has access to all of its associated ports components (Reader input, AB inputs, Relay) and is also able to be manipulated from states and the touch app.
Primary Reader - The primary reader is the main reader for an elevator. It is associated with the reader component of its port only and is also able to be manipulated from states and the touch app.
Additional Reader - The Additional Reader device type is used when associating multiple readers with a single elevator. The additional reader inherits all of its rules and configuration from the primary reader it is associated to. It is associated with the reader component of its port only and is not visible in states or the touch app.
Floor Relay - Consists of the floors that the elevator can go to and is used for the specific floors to which the elevator/user has permissions. The Floor Relay device has access to the AB inputs and Relay components of its associated port and is also able to be manipulated from states and the touch app.
|Device Type||Reader Input||A B Inputs||Relay||TouchApp / Door States Control||Door States Display|
|Primary Door or Gate Reader||X||X||X||X||X|
|Additional Door or Gate Reader||X|
|Generic IO Device||X||X||X|
|Premium IO Device||X||X||X||X||X|
|Elevator Primary Reader||X||X||X|
|Elevator Additional Reader||X|
|Elevator Floor Relay||X||X||X||X|
3 - Provide details
Step 3 presents required fields tailored to the device selected in step 2. For example, when adding an additional device you don’t select a connection, but instead, you select a primary reader.
Name - Enter a unique descriptive name for the device in the Name field.
Door or Gate Type - Click on the icon or down arrow to select from the available public icons.
NOTE: These icons will be used in the TouchApp and areas of PDK io such as within the Device Selection dialog in the Access rules.
Connection - Click in the Connection field or the down arrow to select a connection controller. The type of connection selected determines the connection options displayed in this Add Device window.
Port - Enter the port number for the connected access control device.
NOTE: Each controller starts at Port 1.
Wireless Address - The appearance of the Wireless Address field indicates that the device’s selected Connection type requires its MAC address to be entered in this field.
Primary Reader - Click in this field or the down arrow to select the primary reader.
Click ADD to complete the Add Device wizard.
Edit An Existing Device
Click on an existing device name in the DEVICES tab of the Configuration screen.
In the Device screen, the OPEN DOOR and CLOSE DOOR buttons are available.
Click OPEN DOOR to send an Open to the selected door controller to open (unlock) the door. The relay remains open (unlocked) until a Close (lock) is sent.
Click CLOSE DOOR to send a Close to the selected door controller to close (lock) the door. The relay remains closed (locked) until an Open (unlock) is sent.
Click PAIR touch to pair your device with the touch io reader. Follow the on-screen instructions and touch your smart device to the touch io reader.
NOTE: We have found a Bluetooth issue with Samsung Note 7 and Note 8 phones. It appears to be an incompatibility with their Bluetooth chipset in these devices.
Doors that have been paired with touch io display the touch logo.
Click the SETTINGS touch button to define settings for the reader.
The assigned device name is displayed.
Enable or disable Inside/Out technology for the touch io reader.
In most cases, between the ASK and FSK options, FSK is the option to select. FSK has several advantages over ASK since the carrier has a constant amplitude.
ASK - Amplitude-Shift Keying is a type of amplitude modulation that assigns bit values to discrete amplitude levels. The carrier signal is then modulated among the members of a set of discrete values to transmit information.
FSK - Frequency-Shift Keying is a method of transmitting digital signals and refers to a type of frequency modulation that assigns bit values to discrete frequency levels. FSK is divided into noncoherent and coherent forms.
Bluetooth Range determines whether the end user's mobile device must be physically presented to the touch io or if it can remain in the user’s pocket or purse and touch the reader with their hand. This is an important security consideration since it is advisable to set the range to be as short as possible.
For maximum security, it is advisable to have the reader’s Bluetooth signal reception strength set to the minimal level, requiring end-users to present their mobile device to the reader in order to request access.
Further / Closer - Set the distance at which your mobile device credential connects with and accepts the touch io reader. Use your finger to set the range Closer or Further. Move the stick figure to the right for closer detection. Move the stick figure to the left for further distance detection. The Bluetooth Range can vary from approximately 30 feet or more, down to about one inch. A closer setting is more secure and less prone to potential security risks. The distance at which the reader responds to the phone can vary by phone type so it may be necessary to play with this slider setting until you are satisfied with a setting that is acceptable and secure enough for you.
At an interior doorway where security may be less of a factor, Bluetooth reception strength may be adjusted to allow users to request access without having to present their mobile device to the reader. (This distance can vary from phone to phone.)
Click the Kabob Menu to expose several options
Move to Another Type
To migrate from a legacy device to the new device type, deleting the legacy and creating the new device works, but there’s an easier way. To begin, click on "Move to Another Type"
Once the Move to Another Type option is selected, a wizard similar to the Add Device wizard is launched. The configuration is automatically transferred from the legacy device to the new device. As a result of the wizard, very few details are needed on the last step.
Recent Audit Logs
Click to view the Recent Audit Logs screen. The audit log provides an account of changes and shows system activity from controller events, commands, additions, and modifications to access control devices, the device names, and the names of persons who caused those events and changes.
NOTE: This Recent Audit Logs list only shows the ten most recent events. If desired, Reports can be used to view all logged events and modifications for a specific time period, by device name, user names, etc.
ALL and MODIFICATION Tabs
ALL - Shows the ten most recent commands and filtered results that have occurred for the available devices.
MODIFICATION - Shows the ten most recent modifications made to doors and elevators by device name, rules, and groups used, and the names of those making changes.
By clicking on each of the column headings (Occurred, Info Text, Event, and Result), an edit field opens that enables entering text on which to search and refine the contents of the listed column topic. This can be useful when there is a list of audit log items that need to be refined to a particular date and time, specific text content, a particular event, or a certain result.
Click on the column heading (Occurred, Info Text, Event, and Result) and enter the text on which to search for that column’s information.
Date and time when the event occurred in the form YYYY-MM-DD HH:MM:SS (Year, Month, Day, Hour, Minutes, Seconds).
Information on the person / device / input that was affected by the addition / modification.
A brief description of the added or modified event that occurred.
The result of the event.
To the far right of each log entry is the DETAILS link. Clicking this link displays the Log Entry Details window showing the Door Name.
To update and display the most recent audit log additions / changes / updates, click the REFRESH button in the upper right of the Recent Audit Logs screen.
Delete An Existing Device
In the event that a device needs to be remove click Delete. You will then be prompted with a message stating "Are you sure you want to delete device "device name"?". Click delete to remove the device from the system.
Auto Open After First Allow
When a door schedule is set (for example, auto open at 8:00 AM and close at 6:00 PM) to open at 8:00 AM, the door will not unlock until there is a valid credential read. Following the first valid device read, the door opens and remains open until the set close time. This feature works in conjunction with the Auto Open rule.
Displays the name of the device. (The device name in this field can be edited.)
Displays the device type of the current device.
Displays the Public icon of the current device. Click on the icon or down arrow to select from the available public icons.
Displays the selected connection type. Update or change connection settings. Click in the Connection field or on the down arrow to select from the list of assigned connection device types. The type of connection controller selected determines the connection options that are displayed.
Update or change the assigned port number for the connected access control device.
NOTE: Each controller starts at Port 1.
Only viewable if Connection is a wireless type and corresponds to com module number. Enter the MAC address for a WiMAC access control device or for an Ethernet device.
Click inside the field or on the down arrow to view and select from the list of options.
- No Policy - Neither a key card nor PIN are required for access.
- Card Only - May only use a key card for access.
- PIN Only - May only use a PIN for access.
- Card or PIN - Either a key card or a PIN may be used for access.
- Card and PIN - A key card and a PIN are required for access.
The amount of time that the door delays opening after a valid credential scan. Set a time delay value (in tenths of a second) before a device Action is initiated following a valid read. For example, to set a delay of two seconds before a door is unlocked after a valid read, the Delay value would be set to 20. This option is available if the Action supports it.
This is the amount of time that the door stays unlocked on a valid credential scan. Set a time duration value (in tenths of a second) that a device remains unlocked after a valid read. For example, to set a door to remain unlocked for 5 seconds after a valid read, Dwell time would be set to 50. This option is available if the Action supports it.
A Door Position Sensor records the position of the door (open or closed) at all times. Check DPS when there is a Door Position Sensor being used (on Port A).
NOTE: A DPS device is the suggested use for Port A. This isn’t all Port A can do, however; anything can be used on this port that is needed as a Trigger. More can be wired to this port than just a DPS.
When DPS is checked, the Prop Alarm option is available for selection.
The Prop Alarm allows an alarm to be added in the log when a door is propped (or remains) open for the amount of time entered in the Prop Delay. When Prop Alarm is checked, the Prop Delay option is available for selection.
Prop Delay is the amount of time, in seconds, the system waits after a door is open prior to logging a Prop Alarm, allowing time for the door to close.
Request to Exit (REX ) records every time the REX device is tripped. When Rex is checked, the Forced Alarm option is available for selection. Rex and DPS must be selected in order to receive the Forced Alarm option. Check Rex when there is a Request to Exit device being used (on Port B).
NOTE: A Rex device is specially designed for indoor Request-To-Exit applications. The Rex sensor features passive infrared technology with qualified motion analysis. It is the suggested use for Port B. This isn’t all Port B can do, however; anything can be used on this port that is needed as a Trigger. More can be wired to this port than just a Rex.
NOTE: When a System Event is created for a REX device, in order for the REX to follow the rule, ensure that the Rex box is checked under Configuration and Devices.
This option logs any time a door has been opened without a valid card scan or when the REX has been tripped, showing the door was forced open. An alarm can be set for a forced door when Forced Alarm is checked. Forced Alarm is an option when both DPS and REX are checked.
Existing partitions that have been created are listed and can be added to a device. Multiple partitions created previously are listed in alpha order. Click on a partition name to view / edit that partition’s information.
NOTE: A Default partition exists but the Partition field does not appear until an initial partition is created.
See Partitions for additional information.
After making the necessary selections in this screen, click SAVE in the upper right.
NOTE: As is the case with most of these screens in this application, the SAVE button does not appear unless and until additions/changes have been made to the information in that screen.
The CONNECTIONS tab displays any connected access control device names (in alpha order) showing their connection type (Coordinator, Ethernet, Gateway, USB, or Aperio).
A green dot by the name indicates the device is successfully connected and working as expected.
A red dot indicates the device is not connected.
Edit a Connection Device
Clicking on a listed device name displays the device connection information: Name, IP or MAC Address, Port, and connection Type.
NOTE: Connection information for a device varies depending on the connection type.
Add a Connection Device
To add a connection device, click the + icon in the lower right of the CONNECTIONS tab of the Configuration screen. The Add Connection screen is displayed.
Click inside the Connection Type field or on the down-arrow to select a type. Based on the selected Connection Type (Coordinator, Ethernet, Gateway, USB, or Aperio), enter a Name, Port, and IP Address or MAC address. These options vary based on the selected connection type.
Name - Assign a unique descriptive name for the connection device.
Port - Assign a port number for the Coordinator, Ethernet (Port 10001), Gateway (Port 2101), or USB device.
IP Address - Enter the IP address for the Ethernet or Gateway device.
MAC Address - Enter the MAC address for an Aperio access control device.
Coordinator is a wireless device. Enter the Name and Port number.
Utilizes a CAT5 cable network connection. The Ethernet COM module is set up to obtain an IP address automatically through DHCP. Ethernet connected controllers accept RJ45 connections. When used, the controller will be assigned a DHCP address. Controllers can be assigned a static IP address by using the Lantronix network utility software referred to below.
For Ethernet Connection Type, use the default Port 10001.
NOTE: By default, wireless devices use what is known as DHCP (Dynamic Host Configuration Protocol), which automatically assigns a dynamic (temporary) IP address for a network. For single io and eight io Ethernet connections, a static (permanent) IP address is REQUIRED; a static IP address is not required for Cloud Nodes.
Use the default PDK Manufacturer or select Lantronix for a static IP address.
To set up a static IP address for an Ethernet device, the third-party Lantronix DeviceInstaller application can be used. The suggested static IP address can be obtained from your IT manager or network administrator. The default dynamic IP address that is already assigned to the device by the router may also be used and converted to a static IP address.
Download the Lantronix DeviceInstaller (stand-alone version) at the Lantronix website for the necessary zip file (and DeviceInstaller Help, if necessary) to install and use this application.
NOTE: When adding an Ethernet door controller, ensure that when you are using the Lantronix device installer app that your WiFi is turned off and you are hard-wired from your laptop to the customer’s network, otherwise you will not be able to see the devices.
Enter a Name and use the default Port number 10001.
Static IP Address
See Ethernet Device Installer for instructions on installing and using this application.
The Gateway option utilizes a wireless gateway connection. (Same options as the Ethernet connection type.)
Enter a Name for the Gateway and an IP Address. The Port should be set to 2101, not the default 10001.
Used for the onboard single io (single-door controller) included with the Cloud Node. Enter a Name and Port number.
Used to add an Aperio hub.
NOTE: If or when you set a static IP on a Cloud Node and the Cloud Node does not come back online immediately, give it a few minutes. If it still does not come online then power cycle the Cloud Node for approximately 10 seconds; the Cloud Node should come back online.
Delete Config Connections
Hover the cursor over the configuration connection to be deleted and click the trash icon.
The DISCOVERY tab is used to discover and list the wireless devices that are attached to the Cloud Node. It may also be used for auditing and troubleshooting purposes. Wireless devices need to be discovered, using the Discover tool before they are listed.
Click the Wireless Discover button in the lower right to reveal and display any wireless controllers or connections attached to the Cloud Node. Wireless devices that have been configured into the system are listed.
The DISCOVERY tab is also used for auditing and troubleshooting purposes.
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.
Clicking the CONFIG tab enables selection of various configuration options.
Log Purge Days
Log Purge Days pertains to data that is gathered for reports defined and created in the Reports feature. The default purge is 90 days. Enter the number of days to gather and retain the history of log data; however, this can be adjusted up to 180 days, matching the Cloud Nodes limit to log information. If a user needs to pull a log exceeding the 180-day limit, pdk archives backup information for 365 days. Reach out to support to gain access to the archived backup.
All log data for any report is deleted after the number of days specified in Log Purge Days. After the specified number of days, current report data is purged and the system begins gathering and retaining report data again. This cycle repeats each time the number in Log Purge Days has been reached.
Select a language (English, Spanish, French, or Russian) from the drop-down menu.
In the Common section of the CONFIG tab, select the Region and then the Time Zone associated with the region. Timezones are used for Recent Audit Logs (for the Person Details, Group Details, Door Details pages) as well as in the Events Reports and Live Events screens.
Select the appropriate time zone from the Region and Time Zone drop-down menus.
The list of timezones is grouped by regions. Select the Region and then the Time Zone associated with the region. Timezones are used for Recent Audit Logs (for the Person Details, Group Details, Door Details pages) as well as in the Events Reports and Live Events screens of PDK.io.
NOTE: Be sure to indicate the proper time zone during daylight savings time (if applicable). Remember to set the timezone for daylight savings time. If there are groups that are not 24-hour access, the cards may not work if the timezone is off.
Select the format of the credentials used with the access control system. Only one format can be used system wide. Click inside the Card Format field or on the down arrow to view the drop-down list of formats, the default and most common is the Standard 26-bit Format. Select from:
- 24-bit Card IDs
- 34-bit ADEMCO Format
- 40-bit FIPS Compatible
- Combo 24-bit ID & Standard 26-bit no facility code
- Combo 40-bit FIPS and 26-bit Format
- Combo Ademco 34-bit & Standard 26-bit no facility code
- Combo D10202 & Standard 26-bit no facility code
- Combo D10202 & Standard 26-bit with facility code
- Combo H10304 & Standard 26-bit no facility code
- Combo H10304 & Standard 26-bit with facility code
- Combo N10002 & H10304 no facility code
- HID 32-bit no facility code (N10002)
- HID 33-bit with facility code (D10202)
- HID 37-bit no facility code (H10302)
- HID 37-bit no facility code (H10304)
- HID 37-bit with facility code (H10304)
- HID Corporate 1000 no facility code
- Keyscan 36-bit with facility code (C15001)
- Norris Corp 1000 48-bit no facility code
- Standard 26-bit Format
- Standard 26-bit with facility code
NOTE: If you find it necessary to determine the facility code for your cards, go to Configuration and select the CONFIG tab. Change the card format by selecting Standard 26-bit Format with facility code from the drop-down list. In the Facility Codes field, enter any random facility code number (such as 22). Go to Live Events and it will display the card facility code.
MANAGE CARD FORMATS
Click the MANAGE CARD FORMATS button to view and manage the card formats that have already been set up.
Click the + icon in the lower right to add an additional card format to the existing listed card formats. The Add Card Format screen is displayed.
Enter the Facility Code number.
Video Intercom Connections
PDK and Comelit Database Integration Overview
Integrating Comelit with PDK io
Whether you live in a single home, a multi-tenant building, or a commercial space, there is no need to not feel safe! Comelit and pdk have partnered to provide the right solution for making any area safer.
Comelit specializes in the design and manufacture of video entry, video surveillance, anti-intrusion, and access control systems. Thanks to innovative technology, Comelit's video entry systems are adaptable to each site, with no limits to distance or space. Comelit entry video phone products are installed and used worldwide in residential complexes. Comelit products stand out not only for their style but also for their technology and unique graphic interface.
Since your home is where you should feel the safest, you can see who is at your door with the advanced Comelit and pdk security products; from a simple doorbell to the most modern video entry systems provided with Wi-Fi. Pdk has partnered with this innovative company to provide data sync integration that elevates pdk users to a new level as a Comelit multi-user. With the Comelit and pdk apps on your mobile phone, you can comfortably answer your door entry monitor calls no matter where you are!
Using pdk's data sync integration with Comelit in a multi-story condo or apartment facility, users can be linked to a specific unit in a building to connect via phone and video. The pdk user database integrates with Comelit, allowing its interface to place calls to pdk users.
To add a Comelit integration connection, click the + icon.
In the Add Connection screen, click on the in the Comelit ID32 field and follow the indicated instructions for the required Comelit ID32 information.
Assign a name for the Comelit connection in the Name field.
In the Login section, enter your Comelit Username and Password. Confirm the password and click ADD.
Click on the PDK logo at the upper left of the screen to access the PDK io Cloud Node Appliances home screen again and select People .
NOTE: It is here, in the People feature of PDK io, that you will be adding each of the individuals that will be associated with a Comelit Unit or apartment. In essence, the people that are registered in the PDK io application can be selected and assigned to their respective Comelit apartment or Unit; in the steps that follow, you will link the appropriate person from PDK io with their Comelit apartment (or Unit).
In the People screen, click on a person that is to be linked to and associated with their apartment or Unit information from the Comelit application.
In the Person screen, click the + icon to the right of Video Intercom Links to view the Add Link screen.
Intercom Connection - Click in this field or on the down arrow to select the connection (person's) name.
Unit - Click in this field to select the apartment unit that should be associated with the person named in Intercom Connection.
Phone Number - Enter that person's phone number to be associated with the Unit (apartment).
Click SAVE. A green dot indicates that the PDK io and Comelit information has synced and is working as it should.
Repeat this process for each person that needs to be added and assigned to a Comelit apartment or Unit.
Ecards (Emergency Cards) is a unique feature with access control devices to ensure there is always access to doors. In the event that a loss of connection occurs between a device and the Cloud Node for more than four minutes, Ecards can be used to gain access at that door.
Ecard numbers are stored directly to access control devices for the system. Up to 10 Ecards can be entered in the system for each door controller.
Enter the card number on a line (up to ten card numbers). Click WRITE.
NOTE: If a new device is added to the system, you’ll want to revisit this CONFIG tab in the Configuration screen and update the new controller with Ecards for the new device.
The DIAGNOSTICS tab displays a visual representation of the Cloud Node(s) and controller device(s), by connection type, that are attached to the system.
The example illustration above shows the ProWireless Cloud Node and the connected controller devices. The color codes on the right illustrate the strength and status for each of the connected device(s).
Hovering the cursor over a device indicates its connection information.
Short Address: Similar to a local IP address; used if needed to define a Personal Area Network, dividing devices into different networks.
Full Address: The device’s MAC address.
Average RTT: Average Round-Trip Time. The duration in milliseconds for a network request to go from a starting point to a destination and back to the starting point.
Average Retries: When a connection fails, this is the number of retries in order to connect.
Failure Rate: Percentage of connection failure. 0 indicates no failure; 1 is 100% failure.
Hovering the cursor over the connection lines between the coordinator and a device indicates the strength of the signal between them.
These signal values range from 0 to 255 (255 being the best and strongest possible signal).
START LINKS TEST / STOP LINKS TEST
Click START LINKS TEST to update the graphic representation of device connection links to the Cloud Node.
Click STOP LINKS TEST to end the device connection test.