1.0 Introduction

The NC-485 module was designed to provide RS-485 connectivity across an Ethernet network and to simplify the management of a Doors32 system - as it allowed multiple PXL networks to be combined and then administered and monitored as a single site.

However, Doors.NET does not have the same limitations as Doors32, such as only being able to view live events from one site or having to disconnect from one site before connecting to another.

Doors.NET system architecture and the PXL gateway communicates to multiple physical PXL networks concurrently. So even if a Doors.NET system has several PXL primary controllers, each with multiple secondary controllers, all controllers will be online at the same time and live events from each physical network will appear in Doors.NET as though it is one site.

So effectively, multiple sites in Doors32 become a single site in Doors.NET or Borealis even if the system consists of multiple PXL networks.

This document explains how to convert your Doors32 networking to a Doors.NET networking following a Doors32 to Doors.NET conversion. It can simplify the management and maintenance of a network that spans a broad geographical area as individual networks can be created, such as for each building.

Note: This document assumes your Doors32 system has already been converted to Doors.NET and the controllers have been imported as a single site - 1 x primary controller, addressed as #1, and multiple secondary controllers - as it was configured in Doors32.

2.0 Remove the NC-485 modules

In your Doors32 installation, when using NC-485 modules with LAN-520 modules all controllers will be listed and viewed as a single site.

However, one or more of the PXL secondary controllers will have a LAN-520 module connected as well as an NC-485 module connected beneath it.

There is no method in the software to identify which of the secondary controllers has a LAN-520/NC-485 module connected so the only way to find out is to physically inspect the controllers and look for one which has both modules connect (in the upper-right corner of the controller PCB).

Once you have located a secondary controller with a LAN-520 and NC-485 connected, press the white S1 button to discover the controller's address - then make a note of this address.

Remove the NC-485 module and Re-connect the LAN-520:

1. Power-down the PXL-500 controller.
2. Unscrew and disconnect the LAN-520 module from the NC-485 module.
3. Disconnect the NC-485 power connector (connected to the white JP-9 connector in the top right-corner of the controller).
   
   
   
   
   
4. Unscrew and disconnect the NC-485 from the TB13 LAN connector port on the PXL.
5. The LAN-520 has the same number of PINs on the underside, allowing you to then connect the LAN-520 module to the TB13 connector. Ensure the row of pins line up correctly with the holes on the TB13 connector.
6. Once the LAN-520 module has been connected to TB13, power-up the controller again. The LAN-520 should be displaying 1 x amber LED and 2 x green LEDs.
   
   
   

Important Note: Additionally, make a note of the MAC address for the LAN-520 (printed on the top of the module). The MAC address will be required for finding out what IP address the module is configured with.

3.0 Address the Secondary Controller as a Primary Controller

If you have a network of 50 x PXL controllers, for example, you may have LAN-520 and NC-485 modules connected to secondary controllers #20 and #35. Once the NC-485 modules have been disconnected from these controllers, the controllers would then need to be addressed as #1. So in this example, the network would then have 3 x primary controllers (all addressed as #1).

Change the PXL controller's address

Important Note: As previously mentioned... it is important to first press the white S1 button (located beneath the address display) to find out what address the controller is currently configured with. In the Doors.NET software this controller would then be added as an additional primary controller. The controller's reader's would then be renamed (on the primary controller) and re-added to the relevant access groups) - then the original secondary controller can be deleted.

1. To set the desired operating address for the controller, verify the jumper to JP10 is NOT installed (if the jumper on JP10 is installed, the controller RAM will be reset when the power is turned on).
2. Hold the S1 Options Button down and turn the controller's power on. The beeper for the reader attached to the controller will beep as power comes on.
3. Release S1.
4. The address display LEDs then become active and the controller's address can be set. If an Alpha/Numeric Display is connected to the controller, “ADDRESS CHANGE” will appear on the display.
5. The address range is from 1 to 128 (the Master Controller must be set to address 1). Quickly double clicking S1 toggles between increasing and decreasing the controller address. The top LED character will display either a "+" or a "-" to show which direction is active. A single click of S1 changes the controller address by 1. If you're at address 128, a +1 click will roll the address over to 1; conversely, if you're at address 1 a -1 click will roll the address over to 128. Holding S1 down rapidly scrolls through the addresses. After the new address has been set, you must wait approximately 30 seconds after releasing the S1 button. After 30 seconds, the selected address will be set.
6. You will hear a beep-beep from the reader.
7. The controller's address LEDs will then turn off.
8. If an Alpha/Numeric Display is connected to the controller, “UNIT ##” will appear on the display - (where ## is the controller's address).
9. To ensure the address change will be recognized by Doors.NET, power down the controller.
10. Then, after verifying the JP10 jumper is NOT installed, apply power to the controller.
11. The controller is now ready to be used with its new address.

4.0 Find out the LAN-520s IP Address Using Lantronix Device Installer

1. Go to the Lantronix website and download 'Lantronix Device Installer'. https://www.lantronix.com/products/deviceinstaller
2. If the URL is not valid go to a search engine and enter 'Lantronix Device Installer Download'.
3. Download and install the Device Installer utility.
4. Run Device Installer once it is installed.
5. When you open Device Installer it will immediately scan the local area network for any Lantronix devices.
6. Locate the device which has the MAC address that you have noted down.
7. Next to the MAC address you will see the module's programmed IP address.
   
   
8. Make a note of the programmed IP address.
   

5.0 Reset the LAN-520 to Clear Its Channel 2 Settings

The next step is to connect to the LAN-520 via Telnet (using Device Installer) and then perform a reset on the module. This will not clear the module's IP address or other network settings but it will clear the controller's Channel 2 settings (which were used to communicate with the LAN-520 connected to the primary controller) when using Doors32.

1. From Lantronix Device Installer, double-click the LAN-520 that's connected to the controller which is now an additional primary controller.
2. Additional tabs will appear at the top of the scan window.
3. Click on the Telnet Configuration tab.
   
   
   
   
4. Click the CONNECT button.
5. The press <ENTER> on the keyboard to access the module's setup menu.
6. The cursor will be at the bottom of the list of menu items.
7. Press 7 to set the default configuration. Then <ENTER> again.
8. Press 9 to Save and Exit. Then <ENTER> again.
   
   
   
   
9. The default settings will be stored and Telnet will disconnect.
10. Repeat all the previous steps for any other LAN-520 modules which were connected to secondary controllers (and are now setup as additional primary controllers).
    
    Note: You do not need to reset the LAN-520 module that is connected to the original primary controller.

6.0 Add the Controller as a Primary Controller in Doors.NET

The following steps explain how to add the controller as an additional primary controller in Doors.NET. Once the controller's reader names have been edited the readers are then added to the access groups that the original readers are assigned. The original secondary controller can then be deleted from Doors.NET.

6.1 Add a new Network Communication Channel

1. In Doors.NET go to Setup >> Hardware Setup >> All.
2. The hardware tree will be displayed. The PXL gateway will be listed at the top and the PXL controllers will be listed beneath it.
3. Click on Communication Channels.
4. Click the Network icon locate on the ribbon bar.
   
   
   
   
5. Select the New Entry channel on the hardware tree.
6. The channel properties will be located on the right.
7. Enable the channel and enter a new name.
8. Save the channel settings. The other two settings can remain at their default values
   
   
   
   
9. The network communication channel is now enabled and added to the system.

6.2 Manually add the PXL as a Primary Controller in Doors.NET

1. Select the PXL gateway located at the top of the hardware tree.
2. Click the ADD PXL icon from the ribbon bar.
   
   
   
   
3. Enter a name for the controller (typically this will be the location where it is installed).
4. Select the correct PXL model (it doesn't matter if you are unsure as the exact model can be attributed to the controller once it is online).
5. Click the ACCEPT button.
6. The new primary controller will be added to the hardware tree.
7. Select the new controller on the hardware tree and the controller properties will be displayed on the right.
8. Locate the communication channel setting and select the communication channel that you created in the previous section.
9. Enter the IP address that you made a note of (displayed in Lantronix Device Installer).
10. Save the controller settings.
    
    
    
    
11. Within a few seconds the controller should come online.
12. A network update will automatically be performed when the controller comes online.
    
    

6.3 Rename the Readers for the New Primary Controller

The next step is to expand the secondary controller on the hardware tree (the physical controller which is now configured as a primary controller) and find out the names of the readers. The reader names will then need to be entered into the new primary controller settings.

1. On the hardware tree, double-click the controller that was previously configured as a secondary controller (for example, controller #20).
2. The reader names will appear.
3. Make a note of these reader names.
   
   
   
   
4. Scroll to the new primary controller (located at the bottom of the hardware tree).
5. Double-click the new primary controller to view the readers.
6. Enter the reader names that you made a note of (but don't enter the names exactly as they will need to be distinguished from the previous readers when verifying what access rights to edit). For example, add the #2 at the end.
   
   
   

7.0 Add the new Primary Controller's Readers to Existing Access Groups

The next step is to add the new primary controller's readers to any existing access groups that the previous, secondary controller's readers were added.

Note: This only needs to be done for the readers on the primary controller. The additional secondary controllers will be transferred over to the new primary controller and by doing that the reader names will be retained along with their access group assignment.

1. Go to Home >> Access Groups.
   
   
   
   
2. The existing access group names will be listed on the left. The readers on the system and time schedules will be listed on the right.
   
   
   
   
3. Expand the first access group to view the list of readers which are assigned to the group.
4. Look through the list of assigned readers to see if the secondary controller's doors are added to the group.
   
   
   
   
5. If the doors are in the group, select the access group name (click on the small black arrow to the left of the access group name).
6. Select the new readers (connected to the controller now addressed as #1).
7. Select the same time schedule which is assigned to the previous (secondary controller) readers (in this example it is Always).
8. Click the ASSIGN icon.
9. The new readers will be added to the group and will be displayed as well as the previous readers.
   
   
   
   
10. Repeat steps 3 - 8 for any other access groups that the readers need to be assigned.

8.0 Delete the old (Secondary PXL) Controller

Once the doors for the primary controller have been assigned to the relevant access groups you can now delete the old secondary controller from the hardware tree.

1. Go to Setup >> Hardware Setup >> All (if the hardware tree is not already open.
2. Select the old, secondary controller.
3. Click the REMOVE icon locate in the upper-left.
4. Confirm to go ahead with removing the controller.
5. The secondary controller will now be removed from the hardware tree.
6. You can now edit the reader names on the new primary controller (so they will be displayed exactly the same as they were on the secondary controller).
   
   

9.0 Transfer the Other Secondary Controllers to the New Primary Controller

The next step is to transfer the remaining PXL secondary controllers to the new PXL primary controller. These are the controllers which are physically connected to the new primary controller via the RS-485 network. So, for example, if controller #20 was a secondary controller with a LAN-520 and NC-485 and controller #40 was a secondary controller with a LAN-520 and NC-485 then controllers 21-39 would all need to be transferred to the new controller (that was previously address as #20). This can be done using Doors.NET's Design Mode feature (which unlocks hidden functionality such as the ability to transfer controllers to a different PXL network).

The following steps will explain how to transfer a few of the remaining secondary controllers to the new primary PXL and to get them online.

1. Near the top-left corner of the admin client, click on the small Design Mode icon.
   
   
   
   
2. The title bar will then state (Design Mode) indicating that it is enabled.
3. If the hardware tree is open, close it and then re-open it (via Setup >> Hardware Setup >> All).
4. Select the first of the secondary controllers that needs to be transferred to the second primary controller.
   
   
   
   
5. Drag the controller down to the new primary controller until the cursor displays as shown below.
   
   
   
   
6. Release the mouse button and you will see a message asking you if you wish to go ahead with transferring the controller. Click YES to this message.
   
   
   
   
7. The secondary controller will be transferred and will be listed beneath the new primary controller (at the bottom of the hardware tree).
   
   
   
   
8. Repeat steps 4-6 for all the additional secondary controllers which are physically connected to the new primary controller.
9. All transferred controllers will now be listed at the bottom of the hardware tree beneath the new primary controller.
   
   
   
10. You will notice that the transferred controllers are offline following the transfer. They will come online following an auto-config.

10.0 Perform an Auto-Config to get the Transferred PXL Controllers Online

1. Select the new PXL Primary Controller.
2. Click the Auto-Config icon located on the ribbon bar.
   
   
   
   
3. Doors.NET will then instruct the new primary controller to scan its RS-485 network for the transferred secondary controllers.
4. After a couple of minutes, the detected controllers will then appear in a list.
5. Click the APPLY button.
   
   
   
   
6. Within a few seconds the auto-config will complete and the transferred secondary controllers will be online.

11.0 Send a Total Network Update to the Controllers

The system is now setup. The final step is to select the new primary controller and perform a network update.

1. Select the new primary controller.
2. Click the Update Network Icon on the ribbon bar.
   
   
   
   
3. A prompt will appear asking you if you wish to also send an update to the secondary controllers. Click YES to this.
   
   
   
   
4. The network update should be completed within a few minutes but may be slightly longer for large systems (which have a lot of cardholders and access groups).
5. Once the update is completed, cardholders which have access rights to the readers on the transferred controllers will be able to continue gaining access.