Keri Systems Doors32 - Manual (Page 6)

Doors32 to DoorsNET™ Database Conversion and Troubleshooting
Application Note
Page 6 of 7 P/N: 01255-002 Rev. D
12. Open the Live Events grid and one by one you should see online messages appear for all the PXL
controllers on the network as the master starts to poll the slave controllers one-by-one. If the PXL
network fails to come online refer to the troubleshooting section at the end of this document.
7.0 Auto-Configuration and Initial Update
Now you need to Auto-configure the network.
1. Ensure the master PXL is highlighted and showing as online, then click the Auto-Config button.
2. Monitor the messages that appear in the Status Messages grid of the Auto-Config page. You
should see “PXL Master is searching for slave controllers.”
3. After 2 or 3 minutes all the detected slave controllers will appear in the Available Controllers list.
Review the detected controller information then click the Apply button to complete the Auto-
Configuration.
4. Close down the Auto-Configuration page and return to the Hardware Setup page.
5. Double-click the master controller and a list of all controllers on the network appears. To the right
of each controller will be an “Update Network” indicator. A full update network is required on
each PXL controller to synchronize the hardware configuration with the Doors.NET software.
6. Highlight the master PXL controller then click the Update Network icon on the ribbon bar near
the top of the screen. In Live Events you will see a message appear stating: “Update Network
Started.”
7. Wait for the Update Network Completed message to appear a few minutes later and then the
system will be fully up and running and converted over to Doors.NET.
8.0 Troubleshooting
Simple Steps:
• If the master controller does not come online then you may need to restart the PXL Gateway
windows service. This can be done by selecting the Kiwi bird icon in the bottom right in the
Windows Toolbar Tray and clicking the Restart All button.
• Doors.NET will not operate correctly if Doors32 is actively trying to communicate with the
controllers. If the master controller does not come online and the Doors32 software is still open.
Click on Operate > Net Disconnect within the Doors32 program.
Detailed Routine:
1. Stop all Doors.NET Services.
2. Run Doors32 > Setup System > SET TIME button to test the connection to the PXL Master. If the
system connects, then the connection wiring is OK, the PXL Master is OK, and PC data
communications are OK.
3. Disconnect from the PXL Master and close Doors32.
4. Stop the PXL Gateway Service.
5. In the Doors.NET Client GUI, select PXL Master.
6. Change “Connection Control” to “Manual” and SAVE the change.
7. Wait at least 60 seconds for the PXL Master to prepare for a new, incoming connection request.
8. Start the PXL Gateway Service.
9. In the Doors.NET Client GUI, select PXL Master, right-click, and select “Connect.”
10. Watch the “Live Events” to see if the PXL Master comes online.