7.2. Serial to Ethernet converter

7.2.1. General information

Sometimes there is a need to control the device via the serial port, and it is not always convenient to place the computer next to the device, and sometimes it is simply impossible. And then various Serial to Ethernet converters come to the rescue. Serial to Ethernet converters is designed so that devices having a serial connection type, when connected to it, are converted into network and are open for access from anywhere on the network. In addition, the function of multi-user access to a single device appears

In this chapter, MOXA converter will be used as a Serial to Ethernet converter, but you can use any Serial to Ethernet converter, from the cheapest to the most expensive. For example, Ch9121 module or USR-TCP232-410s


Outward appearance of MOXA converter

MOXA device with increased reliability and a large number of functions makes it simple and reliable for Ethernet applications.
The model is equipped with an RS-232 serial port. The server is simple and easy to configure. In 3 steps, the device can be configured in Serial-to-Ethernet.
In addition, MOXA has a built-in web administration interface that allows you to easily configure the device.

7.2.2. Connecting converter to the 8SMC5 controller

To connect the MOXA converter to the controller, you will need a communication board, such as Waveshare RS232


Waveshare RS232 Communication Board

  • Connect the RS232 board to the controller according to the following scheme:

Connecting scheme Waveshare RS232 to the 8SMC5 controller


The Rx and Tx lines must be connected as shown in the scheme above. Rx -> Rx, Tx -> Tx

  • Connect the RS232 board to the MOXA converter using the DB9 connector
  • Connect the Ethernet cable and the power supply that comes with the MOXA
  • Connect the power supply and the stage to the 8SMC5 controller
  • Turn on the 8SMC5 controller and the MOXA converter

7.2.3. Network configuration

Connecting the controller via a local network:

  • You must have a DHCP server that supports an automatic distribution of ip addresses. The simple DHCP server that satisfies all requirements can be downloaded here.
  • Server and your computer must support IPv4 protocol.

The Ethernet converter can also be used with the direct connection to the PC with working DHCP-server. The example of configuring the local connection for Windows OS:

  • Download the simple DHCP server.
  • Use the default config file for that server (lines 19 to 31 may be different) or configure the DHCP by yourself.
  • Find out the IP address given to the converter, and open it in your web browser.


If necessary, you can use a static IP address.
The converter and your PC must be on the same subnet!

7.2.4. Configuring the MOXA NPort converter via the web interface

  • Find MOXA on your local network to make sure the installation is working


By default, the MOXA Nport device has an IP address of
Use “moxa” as the password, then press “Enter”.

  • In the “Operating Settings” section, select the “TCP Server Mode” operation mode

Do not forget to specify the “Local TCP port” through which the connection will be established



After making any changes to the converter settings, you need to save and restart the device!

7.2.5. Getting started with XILab

Launch XiLab and make the following. It is assumed that the above connection and configuration instructions have been followed.

At first start, XiLab opens controller detection window with two virtual devices.


Click Settings, check Enumerate network devices in the right tab. Enter the IP address of the MOXA converter and do not forget to specify the port. Then click Rescan button in the left tap, XILab will find controller connected to the converter.


In controller detection window choose an axis you need. You can control it in single-axis mode or in multi-axis mode if more than one axis was chosen. For additional information please refer to Getting started with XILab software and XILab application User’s guide.


Once the device IP address has been found, it should be understood that moving the device to another location may lead to a change in its IP.