The following are basic setup instructions for the LAN-520-AESP module. Some settings may not apply to every application.

Note: The LAN-520 AESP is an updated version of Keri’s LAN-520X device. If you are using the new NC-485X Network Converter with the LAN-520, you must use the LAN-520 AESP module (or the existing LAN-520X module). The original NC-485 Network Converter is NOT compatible with the new LAN-520 AESP (or the existing LAN-520X module).

Note: To set up the LAN-520-AESP, you MUST have technical knowledge of general networking in a PC environment. Please have a network administrator on site to resolve any special networking issues that might occur during device programming. Network topologies and strategies will vary.

As well as PXLs, LAN-520-AESP modules also provide Ethernet connectivity to Entraguard controllers.

2.0 Installing the LAN-520-AESP on the
PXL-500 Controller

1. Power-down the PXL-500 controller.
   
2. On the Primary PXL-500 remove jumpers from JP6 and JP7 (highlighted).
   
   
   
   
3. Carefully insert the LAN-520-AESP into TB13 with the RJ-45 connector to the right. Mounting screws are supplied to secure the LAN-520 to the PXL-500 controller. (The PXL500 will have to be removed from its enclosure to do this).
4. Connect the RJ-45 port on the LAN-520-AESP to the network or directly to the host PC via a cross-over network cable.
5. Power up the PXL-500 (if it is a new controller a RAM reset is required).
   
6. The LAN-520-AESP module should be displaying 1 x amber LED and 2 x green LEDs.
   
   
   
   
   

3.0 Installing the LAN-520-AESP on an Entraguard Controller

Support for the LAN unit on Entraguard begin with PCB 23217-001 Rev. E. Earlier units cannot support a LAN unit.

1. Power-down the Entraguard controller.
   
2. On the Entraguard PCB, remove jumpers from J11, J19, and J20.
   
3. Insert the LAN-520X into J7 on the Entraguard. Orient the LAN unit as shown in the image below.
   
   
   

   Note: Mounting screws are supplied to secure the LAN-520 to the Entraguard unit. The Entraguard PCB will have to

   be removed from its enclosure to do this.

   
   
4. Connect the RJ-45 port on the LAN-520 to the network or directly to the host PC via a cross-over cable.
   
5. Power up the Entraguard unit (if this is a new Entraguard panel, or a Primary controller from a Doors32 conversion then a RAM reset is required).
   
   

4.0 Factory Default DHCP Setting

The LAN-520 AESP module is DHCP enabled by default. When the LAN-520 AESP module is connected to a DHCP enabled router it automatically receives an IP address. The quickest way to find out what DHCP address has been assigned to the module is to download and run Grid Connect Device Manager. Perform the following steps to download and use this program:

5.0 Download the Grid Connect Device Manager Software

Note: To download the Grid Connect Device Manager from the Kerisys.com website you will need to first register an account and then log into the site with your registered e-mail address and password.

1. Register for an account by going to kerisys.com, click on Member Login, and fill out the form.
   
   
   
   
2. You will receive an approval email to create your password.
   
3. Once logged in to Kerisys.com click on Supporting Software.
   
4. The list of software applications will appear.
   
5. Click on Grid Connect Device Manager.
   
   
   
   
6. Click the DOWNLOAD button.
   
7. The Device Manager application will be downloaded to the host PC.
   
8. You can now run the Device Manager software.
   
   

6.0 Run the Grid Connect Device Manager Software

7.0 Assigning a Static IP Address to
the LAN-520

Note: By default, the LAN-520 will be configured for DHCP - So it will try to obtain an IP address automatically. If the module fails to obtain a DHCP address it will be assigned an IP address in the range of 169.254.x.x

1. From the list on the left, click on the module that you wish to configure.
2. The device details will be displayed on the right, including the currently assigned IP address.
   
   
   
   
3. Click the TELNET CLIENT button.
   
4. Press enter to make a Telnet connection to the module.
   
5. All device configuration will be displayed as well as the setup menu.
   
6. At the prompt, enter 0 then <ENTER>.
   
7. Enter the first 3 digits of the IP address you wish to set, then <ENTER>.
   
8. Enter the second 3 digits of the IP address to set, then <ENTER>.
   
9. Enter the third 3 digits of the IP address to set, then <ENTER>.
   
10. Enter the last 3 digits of the IP address to set, then <ENTER>.
    
    
    
    
11. Enter through the remaining settings.
    
12. At the change setup menu enter the number 9 to save and exit.
    
    
    
    
13. The settings will be saved to the device and the telnet session will be disconnected.
    
14. You can now close the Telnet window.
    
15. Click the SCAN DEVICES button and select the specific LAN-520 again that you modified.
    
16. The new IP address will be displayed in the device details.
    
    
    
    
    

9.0 Perform the Initial Update on the Controller

1. Locate the new controller on the hardware tree.
2. You will see that there is an update indicator next to the controller.
   
   
   
   
3. Select the controller then click the Update Network icon in the ribbon bar.
   
   
   
   
4. View Live Events and you will see update in progress events.
5. Wait until you see an update complete message.
6. The PXL-500 is now setup and ready for further configuration.
   

10.0 Troubleshooting

10.1 Initial Checks

1. Ensure the primary controller that the LAN-520 is connected to is addressed as number 1. You can check the address by pressing the white S1 button once. S1 is located beneath the address display.
   
2. Ensure the JP6 and JP7 jumpers have both been removed. The JP6 and JP7 pins are located directly to the right of the LAN-520-AESP Ethernet port when it is connected to the controller.
   
3. Ensure the controller has been factory reset - this is especially important if it is a new controller or one that ha been redeployed from a different system.
   
4. Verify that the controller is receiving the correct voltage. This is indicated by a green power LED (LED 8).
   
   
   
   
5. Ensure the port number is correct. By default, the LAN-520 communicates using TCP/IP port number 10001. Verify that the port number is correct in the Doors.NET software. This value is found in the primary controller properties.
   
   
   
   

10.2 Telnet Session to Verify Communication

This will test the default port used by Doors32/Doors.NET to communicate to the device.

The telnet command is preferred over the ping command in testing communications because the telnet command will give a specific response from the device, whereas the ping command may give a response from a different device (if there is a duplicate IP address on the network).

1. In a command prompt window type in, telnet [IP address] 10001 then enter.
2. If successful a blank screen and a blinking cursor will appear. The link LED (bottom green LED) will blink on and off on the LAN-520 AESP indicating that port 10001 is open. Close the command prompt window and the link LED should stop blinking.
3. If telnet is unable to connect, then review the settings. If the settings are correct then contact a network administrator to verify the needed ports are available. Some operating systems and hardware, such as routers and firewalls are set to block ports. Ensure these firewalls have ports 10001, 10021, and 9999, open for communication with the Doors32 or Doors.NET software.
   

10.3 Enable Telnet Client in Windows

If you try to make a telnet connection to the LAN-520 but you see the following message: ‘telnet is not recognized as an internal or external command, operable program or batch file’ then it is likely you are using Windows 10. Telnet Client is disabled by default on certain Windows operating systems.

Perform the following steps to enable Telnet in Windows 10:

1. From the Windows start menu go to Control Panel >> Programs and Features.
2. On the left of the program list click Turn Windows Features on or off.
3. From the Windows features list locate Telnet Client.
4. Place a checkmark against Telnet Client.

11.0 LAN-520 AESP Factory Reset Procedure

Perform the following steps to reset the LAN unit to its factory default settings:

1. Power the unit OFF.
2. Place a jumper across the Factory Default Jumper pins (located next to the MAC address label).
3. Power the unit ON – this resets the LAN unit.
4. Power the unit OFF.
5. Remove the jumper from the Factory Default Jumper pins.

12.0 General Notes

1. The new LAN-520 AESP unit start with the MAC address of 00-80
2. We recommend setting a static IP address to the module using Grid Connect Device Manager. If the DHCP address changes then Doors32 or Doors.NET will no longer be able to connect to the LAN-520 AESP.
3. The original NC-485 module is NOT compatible with the LAN-520 AESP or the LAN-520X. Only the NC-485X is compatible with these modules.
4. To setup a LAN-520 AESP module you must have technical knowledge of general networking in a PC environment. Please have a network administrator on site to resolve any special networking issues that might be encountered during device setup and programming. Network topologies and strategies will vary.
5. If the LAN-520 AESP is connected to a network that isn’t DHCP enabled the module will set itself to an IP address in the range of 169.254.XX.XX with a netmask of 255.255.0.0
6. Keep in mind that although the Device Manager is capable of finding LAN520 devices on a local LAN even if they are on different subnets. However, routers and firewall settings can prevent the application from finding them.
7. If you are able to telnet into port 9999 in the command prompt but not to 10001, it is very likely that the ports required by Doors32/Doors.NET are blocked and will require that a Network Administrator address the issue so a successful telnet session to port 10001 may take place.
8. To use the LAN-520 AESP the PXL firmware must be at v8.4.43 (or greater).