NCD5500 Configuration Software

Not only is a web UI supported (as in previous generations), but also this new Windows application may be used to change settings and recover modules with an unknown IP address.  New firmware upgrade options are now available, allowing users to upgrade firmware as new features are released.

Gen3 Ethernet Relay

Ethernet Relay Control

Introducing the NCD5500 Ethernet to Serial Converter.  NCD's 3rd Generation Converter setting new standards for reliability, low-cost, and ease of use!  Connect the complete line of NCD Industrial Devices to your Ethernet Network using this modular communications module from NCD.  Based on the their next generation Ethernet to Serial Converter, the NCD5500 was customized specifically for use with NCD devices to ensure optimal compatibility with our complete line of products.  This Ethernet communications module essentially converts TCP/IP data into serial data bytes, and sends these bytes to the complete line of NCD devices via Serial Communications.  This Ethernet communications module is suitable for use with endNode, ProXR*, ProXR Lite*, Fusion, Reactor*, and Taralist* series controllers as well as a broad range of IoT connected devices.  This Ethernet to Serial Communication Module is also Compatible with Alpha Station and Base Station, Making it Easy to Discover the IP Address.  Please note the Default Web Page Login Password is “admin” and may be changed by the user.

Ethernet to Serial Communications Module

This Ethernet to Serial Communications Module converts TCP packets to Serial data and vise versa.  This device can be configured to automatically close the socket after a programmable timeout or to leave the socket open.  A blue LED light indicates an open socket connection.  Program the Baud Rate of this Device from 9600 to 115.2K Baud and communicate to this device over the default TCP port 2101.  This device also supports Static IP Addresses, DHCP, and has the ability to recover back to factory default settings with a simple press of a button!

DHCP and Static IP Addresses

This module supports both DHCP and static IP Addressing. For communications reliability, especially via Remote Access, we recommend using a Static IP Address when you feel comfortable doing so.  This will ensure that the device will always be where you expect it to be when you try to connect to it.

TCP/IP Communications

The main method of communication to the Ethernet modules is a standard TCP Socket.  This communication protocol makes use of Network Sockets to create point to point tunnels that data can flow through bi-directionally.  In this way the computer that is controlling the relay can send commands and shortly thereafter receive the response through the same Socket.

3rd Generation Hardware Now Shipping

This is NCD's 3rd generation hardware for Ethernet to Serial communications, representing giant steps forward in reliability, easy of use, recover-ability, and LOW COST.  Yes, we are actually LOWERING the price of this device as costs have shrunk considerably from previous generation Ethernet to Serial conversion technologies.  Other significant improvements include new recovery options.  Not only is a web UI supported (as in previous generations), but also a new Windows application may be used to change settings and recover modules with an unknown IP address!  New firmware upgrade options are now available, allowing users to upgrade firmware as new features are released.

Password Protection

The Gen3 Module has security built-in.  Under the management tab users have the ability to assign a password to the module for security.

Port Forwarding

When using this board over the internet and outside the Local Area Network, Port Forwarding will be required.  Port Forwarding is a protocol used by your router to allow incoming requests for connections to get through to a specific device on a specific port.  Below is an example of how it works.  In this example a router has been setup to forward incoming requests for port 2101 to the device at the IP Address 192.168.2.19 on port 2101.  Now when any device that tries to access this Port on the External IP Address the router will see the request and automatically forward the request to the device at the IP Address of 192.168.2.19 on port 2101.  If this Port Forwarding rule was not in place and a request came in on port 2101 the router would not know which port or device to forward it to and the request for connection would be denied.  Note: Port Forwarding will not be necessary when using this within a Local Area Network.  For more on Port Forwarding with detailed instructions for every router visit: https://portforward.com/ .

Sending Commands

Base Station Software is available at no charge to get you up and running fast (more on Base Station below).  Once powered up, the controller waits for a ProXR command.  A command consists of a few bytes of data in numerical format (ProXR Enhanced Command Set) usually between 2 and 6 bytes.  Once the command has been received, the controller processes the command, and sends you back ASCII character code 85 to signal the completion of your command.  If a command was sent to read the status of the relay the status is sent back.

Before You Start (Requirements)

It should be noted that these boards do not communicate over an internet connection.  Both boards must be on the same LAN.  Also both boards will require an assigned static IP address.  We recommend that you assign the boards with IP addresses outside the DHCP range of your network router.  If you are connecting these devices to an IT managed network it is recommended that you review this guide with the Network Administrator prior to proceeding.

Static IP Required

Each board will utilize a static IP address.  One board will act as the server while the second board will act as the client.  The connection between the two boards is via a TCP socket.  The port number used by this TCP socket is arbitrary and can be configured to any port you wish.  In our setup we used port 2101.  This may be important information if the boards are on separate subnets.  Relay Pros or NCD is not capable of providing technical support for complex networks, this should be handled by the Network Admin.

Windown Configuration

We will be using configuration software which requires Windows so a Windows computer connected to the same network as the boards will be required.

Managed Network Required for Setup

Initially both boards will be in DHCP mode so a managed network is required, at least for initial configuration.  It is not possible to configure these devices on an unmanaged switch, however after configuration is complete it is absolutely possible to install the boards on an unmanaged network.

Configuration

Initial setup

• Download and install the NCD5500 configuration software available here: NCD 5500 Configuration Software.
• Connect standard Ethernet cables to the boards and plug them into the network. Then power the boards up using a regulated 12VDC power supply source.
• Open the NCD5500 Configuration software.
• Click the Search Button in the Configuration software until you have discovered both boards.  You will see them listed by their MAC address.  This Mac address is also printed on top of the Ethernet module installed in the board.  This information can be used to differentiate between the two boards.

First board Configuration (Server)

• Click on one of the boards to open it’s settings.  All settings we will be covering will be under Basic Settings.  We do not need to do anything under Advanced Settings.
• Set the baud rate to 57600.
• Change the Network Settings Radio button to Use the Follow IP address.
• Enter a Static IP address for the board into the IP address field, and enter information into Subnet Mask, Gateway, and DNS Server as per the requirements of your network.
• If you would like this board to act as the Server(does not matter which board you choose to act as the server) then Under Connection set Work As to TCP Server. Set the Local Port field to any port you wish other than 80. This will be the port the module listens for incoming TCP Socket connections on. This information is applicable if there are any firewalls. For our setup we are using port 2101.
• Click Apply Settings.

Second Board Configuration (Client)

• Click on the other board in the list to open it’s settings.
• Set the baud rate to 57600.
• Change the Network Settings Radio button to Use the Follow IP address.
• Enter a Static IP address for the board into the IP address field, and enter information into Subnet Mask, Gateway, and DNS Server as per the requirements of your network.
• This board will act as the Client and will connect to the previous board we configured.   Click the Work As Drop down menu and change it to TCP Client.  Do not worry about the Local Port Setting as it does not apply.
• Enter the Static IP address entered for the first board acting as the server into the Remote Host field.
• Enter the Port number entered as the Local Port on the first board acting as the Server into the Port field to the right of the Remote Host Field.
• Click Apply Settings.

Final Testing

Both boards should now be configured and should work.  You can validate that the boards have a valid TCP socket connected by checking the Red LED on the Ethernet module adjacent to the metal Ethernet Jack.  If it is on solid then the connection is established between the boards.  You may also monitor the Busy/Ready LEDs on the boards which should flash on/off periodically indicating the boards are communicating.  You may now close the inputs on the boards and should see the relays on the remote unit turning on/off.

Data Sheets & Quick Start Guides

Download the complete Command Set for the ProXR boards.