Google Chat: zj734465502@gmail.com
+86-0755-88291180
sales01@spotpear.com
dragon_manager@163.com
services01@spotpear.com
manager01@spotpear.com
WhatsApp:13246739196
It is a UART to Ethernet module designed for industrial environments, small in size, easy to embed and integrate, with device data collector/IoT gateway, serial server, Modbus gateway, MQTT gateway, UART to JSON, and many other functions in one. It has a UART interface and an Ethernet interface.
Pin | Model | Description |
---|---|---|
5V | Power | 5V Power Input |
3.3V | Power | 3.3V Power Input |
GND | Ground | Ground |
RST | Reset | Reset pin, low active. It is recommended to use max811reus or a similar reset chip. Noise can be filtered by a 0.1u capacitor. Low-level minimum time 100ns. |
TXD | OUT | Serial data transmitting pin of the module, 3.3V TTL level, can be connected to RXD of user MCU. |
RXD | IN | Serial data receiving pin of the module, 3.3V TTL level, can be connected to the user MCU's TXD. |
DEF | IN | When the parameter is reset to 0 and held for more than 1 second, the module will restart with the default IP of 192.168.1.254, static IP mode, 255.255.255.0 gateway, and 192.168.1.1 gateway. You can also set your own reset parameters with the param.txt configuration file. |
RUN | OUT | Working indicator, the chip works properly, and will output a square wave with a period of 2 seconds. You can connect a 4.7K resistor and then connect the LED to the ground and the LED is on indicating the chip has been working. |
EN | OUT | The 485 transmit controller, normally 0, becomes 1 when the module sends data to the serial port. It can be connected directly to the TXD_EN pin of the MAX485 chip. |
RTS | OUT | Hardware flow control output. After the flow control is set to CTS/RTS, DTR/DSR, RTS=0 normally, if RTS=1, it means the module can't receive data and the user MCU should stop sending data to the module. |
CTS | IN | Hardware flow control input, when the chip is configured for CTS/RTS, DSR/DTR serial mode, only when CTS=0, the chip serial port will output data to the outside. |
GND | Ground | Ground |
LINK2 | OUT | When it is 0, it indicates that the module RJ45 network cable is connected. |
ACT | OUT | Data indicator. When it is 0, it indicates that there is data being sent and received at the serial port. But when there is data, this pin will jump between 0 and 1. ACT=1, which cannot be used as a flag for no data communication. |
LINK | OUT | TCP connection indicator. When it is 0, the module has established TCP/UDP connection with the network server, and the module can send and receive data normally. If the network cable is unplugged at this time, the LINK will change to 1. |
Generally speaking, the serial server only needs to connect the power supply, serial port, and network cable. Among them, the power supply can use the field 2-wire power supply, which can be directly connected to the positive and negative terminals of the power supply. The serial port needs to be connected according to the user's UART device. The network port is connected to a common network cable, which can be directly connected to the computer or connected to the network through a switch.
Vircom can be used to configure parameters such as device IP and create virtual serial ports. If you don't need the virtual serial port function, you can just download the free version configuration software.
The driver installation needs to be decompressed. Double-click the software to install. If the virtual serial port in Vircom is not displayed, restart it and check it again.
After Vircom is installed and the device hardware connection is finished, the software is run as shown in the figure, and then you can click "Device Management" as shown in the figure. With Vircom, it is very convenient to search and configure device parameters in different network segments, as long as the device and the computer running Vircom are under the same switch.
The UART port to Ethernet port and Ethernet port to UART port data transparent forwarding function of the serial port server. Assuming that the COM port (USB TO TTL) of the PC is now connected to the serial port of the serial port server, then open the serial port debugging assistant window and open the corresponding COM port, as shown below:
In addition, open another serial port debugging assistant window and use it as a TCP client mode, fill in the destination IP as the IP of the serial port server (currently 192.168.1.200), the destination port as 4196, and then click the "Open" button, as shown in the figure below:
In the serial debugging assistant SSCOM2 set as TCPClient, enter "TCPClient: Waveshare Test" and click send, then the data will be transferred to the TTL interface through the serial server's network port, and then sent to the USB TO TTL, and then displayed in the serial debugging assistant SSCOM1 out; conversely, enter "USB TO RS485: Waveshare Test" in SSCOM1, click send, you can also send to SSCOM2, and display it.
The SSCOM2 in the figure communicates directly with the serial port server through TCP. In order to allow the user's already developed serial port software to communicate with the serial port server, a virtual serial port needs to be added between the user program and the serial port server. As shown in the figure, Vircom, and user programs run on one computer, Vircom virtualizes a COM port and makes this COM port corresponding to the serial port server. When the user program opens COM communication, it can be sent to the user's serial device through the Vircom serial server. The steps to do this are shown below:
Click the "UART management" in the Vircom interface, click "add", and then choose COM2. Among them, COM5 is the COM port that did not exist in the computer.
Then enter the device management, and double-click the device that needs to be bound to COM2. As shown in the figure, select COM2 in the "Virtual Serial Port" list in the upper left corner. Then click "Modify Settings", and then click "Restart Device". and return to the main interface of Vircom. It can be seen that COM2 has been connected to the device whose IP is 192.168.1.200. In this case, COM2 can be used instead of SSCOM2 for communication.
Open SSCOM to simulate the user's serial port program, open COM2 (the virtual serial port above), open another SSCOM to simulate a serial port device, and open COM3 (hardware serial port). At this time, the data link sent by COM2 is as follows: COM2 —> Vircom —> the network port of the serial server —> the serial port of the serial server —> COM3.
Conversely, COM3 to COM2 can also transmit data: COM3 -> the serial port of the serial server -> the network port of the serial server -> Vircom -> COM2. As shown in the figure below, both parties send and receive data. If COM4 is replaced with the user serial device, then COM5 can realize the communication with the user device.
By default, the data between the serial port and network port is transparently transmitted. If you need to convert Modbus TCP to RTU, you need to select the conversion protocol as "Modbus TCP<-->RTU" in the device settings dialog box, as shown in the figure below. At this time, the device port automatically changes to 502. At this time, the user's Modbus TCP tool is connected to the IP port 502 of the serial server and the sent Modbus TCP command will be converted into an RTU command and output from the serial port. For example, if the serial port server network port receives the Modbus TCP command of 00 00 00 00 00 0601 03 00 00 0a, the serial port outputs the command of 01 03 00 00 00 0a c5 cd. Note: The serial port may send multiple 01 03 00 00 00 0a c5 cd commands because the default Modbus adopts the storage mode, which will automatically train the query commands. How to switch to non-storage mode will be explained later.
If the user's Modbus TCP software is used as a slave station (Slave), it is necessary to select the conversion protocol, then change the working mode to the client, the destination IP to the IP of the computer where the Modbus TCP software is located, and the destination port to 502, as shown in the figure below shows.
Using Vircom, you can search and configure device parameters in different network segments. For Web configuration, you must first ensure that the computer and the serial server are in the same IP segment, and you need to know the IP address of the serial server in advance. But web configuration can be done on any computer without Vircom.
1. Enter the IP address of the serial server in the browser, such as http://192.168.1.200.
2. Enter a password in Password: There is no login password set by default in the factory, you can enter a password at will, and click the Login button to log in. After setting the password to log in, the settings at "Modify webpage login password" will take effect:
3. The serial server parameters can be modified on the web page that appears. For the relevant parameters, please refer to Table 4 for the meaning of the parameters.
4. After modifying the parameters, click the "Submit Modification" button.
5. If configuring and downloading MQTT and Jetson Modbus firmware overwrites the webpage file of the configuration interface, resulting in the failure to open the configuration webpage, please follow the steps below to re-download the webpage file:
Configuration and download other firmware such as MQTT and Jetson Modbus cover the configuration interface web page file, you need to re-download configuration interface web file to RS485 TO ETH (B):
1) Check the status of the indicator light, the link light blue is always on that tcp channel is established; Vircom software on the automatic search view, TCP has been established, indicating that the channel is established.
2) If the link light is not blue always on, it is yellow-green/not on, then first vircom software/webpage login to see if you can log in, ping the device IP, whether this ping through? If you can search, ping through, indicating that the device is not dead, the upper computer software to connect the device IP and port, to see if it can be connected normally.
3) TCP connection channel established, no data up, according to the above 1 after the judgment, found that the TCP channel is established, but no data up, then need to troubleshoot.
4) RS485 TO ETH (B) is set to 192.168.1.200 port number 1111; the computer is set to 192.168.1.199 port number 1111.
5) The network supervisor is not sending data normally? can configure network heartbeat packet verification, if normal, it will send down data regularly.
6) SSCOM needs to be added to the firewall, otherwise the firewall will organize the TCP connection, or close all firewall tests on the computer.
1) Confirm hardware connections such as serial devices and check that your gateway and energy meter is properly connected. Ensure that the power and data cables are connected correctly and that there are no loose connections.
2) The Serial terminal device received data and did not answer properly? Then you need to listen to the serial device data judgment, find a 485 to USB serial cable and received a 485 device interface to the computer USB, computer mapping a com port number, open the serial debugging assistant software - set the serial port parameters to maintain consistency, enter the corresponding com port - listen to the 485 device data to see. 485 wiring: T + - A T - - B; - see 485 this side is received by the next command is correct; correct command sent, 485 whether the normal answer?
3) Confirm the baud rate, data bits, stop bits, and other serial parameters configuration: baud rate should be configured according to the access RS485 device, commonly used is 9600 and 115200; specifically check the device manual or contact RS485 device technical support to confirm; if set to Modbus mode, please confirm whether the function code matches.