NCD5500 Configuration Software for Windows
NCD5500_CONFIG
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.Network Relay Control
Send relay control commands over your network using our industry-leading command set. You can also configure the module and upload custom web pages, giving you browser-based control of your relays from any device.
Gen3 Ethernet Relay
NCD5500_CONFIG - Next-Generation Ethernet Relay Control
Meet the NCD5500 Ethernet-to-Serial Converter, NCD's 3rd-generation Ethernet module designed for exceptional reliability, ease of use, and lower cost. This modular interface brings the entire line of NCD Industrial Devices onto your Ethernet network with plug-and-play simplicity.Built on NCD's next-generation Ethernet-to-Serial platform, the NCD5500 is customized specifically for NCD controllers to ensure full compatibility across our product families, including ProXR, ProXR Lite, Reactor, and Taralist boards. The module converts TCP/IP data into serial bytes and routes them directly to your controller via standard serial communication.
The NCD5500 works seamlessly with Base Station, making IP discovery and configuration fast and simple.
Default web-page login password: admin (user-changeable).
Ethernet to Serial Communications Module
The Gen3 module converts TCP packets to serial data (and back again) for smooth, real-time control.- Features include:
- Auto Socket Control - Choose to close the socket after a programmable timeout or keep the connection open
- Connection Status LED - A blue LED indicates an active socket connection
- Flexible Baud Rates - Adjustable from 9600 to 115.2K, using the default TCP port 2101
- Network Options - Supports both Static IP and DHCP
- One-Button Recovery - Restore factory defaults instantly with a simple button press
DHCP and Static IP Addresses
This module supports both DHCP and Static IP addressing.For the most reliable remote access, we recommend using a Static IP Address once you are comfortable with the network configuration. This ensures consistent communication and predictable device access.
TCP/IP Communications
The primary communication method is a standard TCP Socket. This creates a bi-directional connection, allowing your computer or control system to send commands and immediately receive responses through the same socket - fast, robust, and ideal for relay control applications.3rd Generation Hardware
The latest hardware represents a major leap forward in reliability, usability, and cost efficiency.- Key improvements include:
- Lower overall cost compared to previous generations
- Enhanced recovery options
- Web-based configuration UI
- Windows utility for discovering devices with unknown IP addresses
- Firmware upgrade support for feature updates and improvements
Password Protection
Password protection is built in.Under the management tab, users can assign a password for added security and access control.
Port Forwarding
To access the module from outside your Local Area Network, Port Forwarding is required.Your router forwards incoming requests on a specific port (e.g., 2101) to the device's local IP address.
Example:
A router is configured to forward port 2101 to 92.168.2.19:2101. Any external request to port 2101 is automatically routed to the module. Without this rule, the router would not know where to send the request, and the connection would fail.
Note: Port Forwarding is not needed for communication within your LAN.
For step-by-step instructions for virtually any router, visit https://portforward.com/ .
Managed Network Required
Initially both boards will be in DHCP mode so a managed network is required, at least for initial configuration. It's not possible to configure these devices on an unmanaged switch.
MCNET / MXNET Setup
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.
