What Are the Common Abnormal Situations of Serial to Ethernet Server

Serial to Ethernet server is like a microcomputer with a CPU, real-time operating system, and TCP/IP protocol, which is convenient for data transmission between serial ports and network devices. In the process of using the Serial to Ethernet server, the problem can be basically solved by operating according to the operation manual. However, some abnormal faults may still occur in the actual operation. The common abnormal conditions of the Serial to Ethernet server are listed as follows:

I. Cannot find the device using the changer setup

1. Because the converter setup program is set using the UDP protocol, it is generally possible that the firewall of the anti-virus software blocks the UDP request, resulting in the failure to find the device.

2. Sometimes the customer has turned off the anti-virus software such as Rising and Norton, but still cannot find the device. In this case, it is possible that the built-in firewall of WINDOWS XP has blocked UDP requests. If you want to turn off the firewall, please follow the following steps: right-click "Network Neighborhood", select "Properties", and right-click "Local Area Connection". Select "Properties", select the "Advanced" option, click "Settings", enter the relevant page, and turn off the firewall.

3. Turn off all firewalls. If you still cannot find the device, you must find the network administrator. In this case, it is possible that the IP address set by the Serial to Ethernet server conflicts with the IP address of the computer in the LAN, or the device cannot be found. It is also possible that the network administrator manages the local area network and does not allow IP addresses without registration. MAC addresses run in the local area network and can be required to be opened by the network administrator.

II. After device completion on the converter, it was found that a TCP connection could not be established

1. It is possible that the firewall will block the TCP connection and prevent it from establishing a connection. The solution can be solved by referring to some of the above methods.

2. The IP address may be set incorrectly. If the converter is used as a client, the IP address of the server is the IP address of the computer or the network device communicating with the converter. If the converter is used as a server when using the "Connection Management System" of the virtual serial port, there is a setting of "Converter as a Server" in the setting wizard, and the IP address and port number of the converter are filled in.

3. If the virtual serial port is used, "Use virtual serial port" must be selected in the "Serial port parameter setting" of the "Converter setting program". If this option is not selected, the connection management system cannot establish a TCP connection. However, if the virtual serial port is not used, this option must be removed if the program is directly based on WINSOCKET, otherwise, the data will be garbled.

III. A TCP connection was established, but communication was not possible

This situation is generally reflected in the use of virtual serial ports, mostly in the case of RS485 to TCP/IP. Under normal circumstances, the communication protocol of the RS485 bus is to achieve point-to-multipoint communication through polling. If the master calls the slave and there is no response within a specified time, the master is regarded as the slave does not exist. Because our default parameter has a certain delay, So the delay modification can solve this problem. That is to say, in the "Serial Port Parameter Setting" of the "Converter Setting Program" of the Serial to Ethernet server, setting the network minimum sending time and the network maximum sending a byte to 0. 0 can basically solve this problem.