LAN-520 Basic Setup

1.0 Introduction

The following are basic setup instructions for the LAN-520 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, 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 and Entraguards, some of the Mercury SPM models also support direct connection of a LAN-520. The models include; The AP-SPM, SPM-C and SPM-E.

Note: PXL and Entraguard controllers are not supported in Doors.NET effective from v6.0.0 but ongoing support for these controllers is available in Borealis.

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

• Power-down the PXL-500 controller

• On the Primary PXL-500 remove jumpers from JP6 and JP7 (highlighted).

• Insert the LAN-520 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).
  
  

• Connect the RJ-45 port on the LAN-520 to the network or directly to the host PC via a cross-over network cable.
  
  
• Power up the PXL-500 (if it is a new controller a RAM reset is required).
  

3.0 Installing the LAN-520 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.

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

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.

• Connect the RJ-45 port on the LAN-520 to the network or directly to the host PC via a cross-over cable.
• 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 Default DHCP Setting

The LAN-520 AESP has 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 install and run Lantronix Device Installer. Perform the following steps to install and use this program:

5.0 Installing Lantronix Device Installer

The Device Installer software can be installed from the Kerisys.com website after registering a user account and then logging in:

1. Once logged in to Kerisys.com click on Supporting Software.

2. The following list of software applications will appear.
   
   
   
   

3. Click on Lantronix Device Installer.

4. Select Lantronix_Installer_4.4.0.7.zip.

5. Device Installer application will be downloaded to the host PC.

6. You can now install Lantronix Device Installer.

7. Click on the downloaded installer executable file and the installation will initialize.
8. The installer will indicate any components that need to be installed first.
9. Click the INSTALL button.
   
   
   
   
10. You will not need an active internet connection as all the required components are included in the executable file.
11. Check the check box to confirm you have read the Microsoft Terms and Agreements.
12. Click install and the .NET Framework 4 Client Profile will install.
    
    
    
    
13. Click Finish once installation is complete.
14. The Lantronix Device Installer Setup Wizard will then start automatically.
15. Click Next on the Welcome page.
16. The Installation Folder page displays the default location where the program will be installed. You can click Browse to locate and select a different location.
17. Click Next, then Next again to start installing Device Installer. Installation of this program should take no longer than a minute.
18. Once installation is complete you can locate the application via; Start >> All Programs >> Lantronix >> Device Installer 4.4 >> Device Installer.
19. Right-click the Device Installer application file and select Send to – Desktop (create shortcut).

6.0 Starting Lantronix Device Installer

• The Device Installer icon will be found on the desktop so double-click this to open up the application.
  
  

• When you first open the program you may see a notification that no serial port has been detected, this is not of any concern so select ‘Do not prompt me about this’. Then click OK.
• Click No to the prompt asking if you want to check for updates.
• If the LAN-520 AESP module has been connected to a DHCP router which is on the same physical subnet as the host PC then the device should appear. It should also show as online. The software automatically searches for the device via its MAC address.
• The device should display along with its assigned IP address. The MAC address will begin 00-80 if it is a LAN-520 AESP.
• Even if the address assigned by DHCP is an acceptable IP address it is still a dynamic address and therefore can still change. We therefore recommend assigning the IP which will make the assigned address static.

7.0 Assigning a Static IP Address

1. Highlight the LAN-520 entry and click the Assign IP button.
2. The Assignment Method page defaults to ‘Assign a specific IP address’ so click Next.
3. Enter a new static IP address or leave as is (if you are happy with the address that was assigned by DHCP). On this page you can optionally add a gateway IP address as well. A gateway address is not required if the PC running Doors32/Doors.NET is on the same subnet. Click Next again.
4. Click the Assign button to complete the static IP address assignment.
5. Click Finish when you see assignment has successfully completed.

8.0 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).

• In a command prompt window type in, telnet [IP address] 10001 then enter.
• 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.
• 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.
  

9.0 Enable Telnet Client Windows 10

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 a Windows 7 operating system.

Perform the following steps to enable Telnet in Windows 10:

• From the Windows start menu go to Control Panel >> Programs and Features
• On the left of the program list click Turn Windows Features on or off
• From the Windows features list locate Telnet Client
• Place a check mark against Telnet Client

10.0 Calculate Netmask: Number of Bits for Host Part

During the configuration of the LAN-520 AESP's TCP/IP address it will be necessary to add the subnet mask in number of host bits. The following is one way of calculating the host bits in a subnet.

A Decimal to Binary conversion of 255 will be all 1’s (11111111) and a 0 will equal 8 0’s (00000000).

If there are two 0’s in the subnet (255.255.0.0) there will be 16 0’s thus the host part will be 16.

1. To calculate a subnet like 255.255.255.248, open the Windows Calculator.
2. Click on View > Scientific.
3. Dec (Decimal) will already be selected.
4. Type in the last segment (248).
5. Select Bin (Binary) and the binary conversion will take place.
6. The 0s will represent the number of available bits. This number will be the Number of Bits for Host Part (248 =11111000 = 3). Number of Bits for Host Part is 3.

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
3. Power the 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

• The new LAN-520 AESP unit start with the MAC address of 00-80
• We recommend setting a static IP address to the module using Device Installer. If the DHCP address changes then Doors32 or Doors.NET will no longer be able to connect to the LAN-520 AESP.
• 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.
• 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.
• 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
• Keep in mind that although the Device Installer is capable of finding LAN520 devices on a local LAN even if they are on different subnets, routers and firewall settings can prevent the application from finding them.
• 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.
• To use the LAN-520 AESP the PXL firmware must be at v8.4.43 (or greater).