Description
E90-DTU(xxxSLxx)E includes the following models:
This document applies to five models: E90-DTU(230SL30)E, E90-DTU(400SL22)E, E90-DTU(400SL30)E, E90-DTU(900SL22)E, and E90-DTU(900SL30)E.
During debugging, use the E90-DTU(400SL22) radio for demonstration, and set the gateway RF parameters to be consistent with the radio RF parameters.
Some functional descriptions and usage precautions
1. Timeout restart
If the device runs for a long time and you are worried that the device may have abnormal conditions, you can enable the timeout restart function.
Timeout restart time: During this time, if no data is received from the network port, the device will automatically restart, ranging from 60-65535 seconds. (When restarting, if you connect to a computer, you can see that the network adapter will show that the network cable connection is disconnected, which lasts about 5 seconds)
2. DHCP
When the gateway is directly connected to the router or connected to the router through a switch, the DHCP service can be enabled to avoid IP conflicts or unavailable IP settings. However, when directly connected to a computer, both the computer and the gateway need to set a static IP, and DHCP cannot be set. (Because in DHCP mode, IP allocation is performed by the router or management switch, and neither the computer nor the gateway has the function of allocating IP to the other party, so neither can get an IP address, and therefore communication is impossible)
3. TCP/UDP working mode
(1) TCP server
1. Applicable to scenarios where the communication partner is a TCP client.
2. Before use, set the gateway IP and the communication partner IP to the same network segment and do not conflict with each other. For example, if the gateway IP is 192.168.3.8, then the communication partner IP is set to 192.168.3.6 (note that IP cannot conflict); if the communication partner IP cannot be changed, set the gateway IP address to the same network segment as the communication partner. For example, if the communication partner IP is 192.168.1.5, set the gateway IP to 192.168.1.6.
When the gateway is in TCP server mode, the communication partner needs to be set as a TCP client. At this time, the gateway IP is used as the communication partner's target IP, and the gateway local port needs to be set as the communication partner's target port. Example: Gateway parameters are IP: 192.168.3.8; Local port: 8886. Then the communication partner IP: 192.168.3.6; Target IP: 192.168.3.8; Target port: 8886; Local port: 0 (dynamic port, if it is a static port, communication may be poor)
Note: When used as a server mode, a single link supports 5 TCP client accesses. If the number exceeds 5, new connections will be rejected. When 2 links are enabled in server mode at the same time, 2×5 TCP client accesses are supported.
(2) TCP Client
1. Applicable to scenarios where the communication partner is a TCP server.
2. Before use, set the gateway IP and the communication partner IP to the same network segment and not conflict with each other. For example, if the gateway IP is 192.168.3.8, then the communication partner IP is set to 192.168.3.6; if the communication partner IP cannot be changed, set the gateway IP address to the same network segment as the communication partner. For example, if the communication partner IP is 192.168.1.5, then set the gateway IP to 192.168.1.6
3. When the gateway is in TCP client mode, the communication partner needs to be set to a TCP server. At this time, the communication partner IP is used as the gateway target IP, and the communication partner port is the gateway target port
For example: The communication partner parameters are IP: 192.168.3.6; local port: 2000
Then set the gateway IP: 192.168.3.8; target IP: 192.168.3.6; target port: 2000; local port: 0 (the gateway will automatically change to 0, dynamic port, no need to set manually)
Note: If you use a computer for debugging, you need to turn off the firewall in client mode, otherwise the gateway and computer cannot establish a connection normally.
(3) UDP server
1. In principle, the UDP protocol does not have the concept of server and client. This device is used as a gateway, and there may be multiple UDP protocol devices interacting with it. In order to facilitate the return to multiple hosts, the server concept is designed. It is suitable for scenarios with multiple UDP devices interacting with it.
2. Before use, set the gateway IP and the communication partner IP to the same network segment and do not conflict with each other. For example, if the gateway IP is 192.168.3.8, then the communication partner IP is set to 192.168.3.6; if the communication partner IP cannot be changed, set the gateway IP address to the same network segment as the communication partner. For example, if the communication partner IP is 192.168.1.5, set the gateway IP to 192.168.1.6
3. When the gateway is in UDP server mode, it only returns the message to the UDP device that communicated with it for the last time. Therefore, the communication partner needs to set the gateway IP as the target IP and the gateway port as the target port. The gateway cannot actively send messages before receiving messages from other UDP devices.
For example:
Device 1 IP: 192.168.3.6; Port: 2222
Device 2 IP: 192.168.3.6; Port: 1111
Gateway IP: 192.168.3.8; Port: 8886
The gateway cannot actively send messages to other devices. For example, if gateway 1 sends information to the gateway, the gateway will subsequently send the message to gateway 1 (IP: 192.168.4.222; Port: 2222). If device 2 (IP: 192.168.4.111; Port: 1111) sends a message to the gateway, the gateway will not reply to device 1, but only to device 2, unless device 1 sends data to the gateway again.
(4) UDP client
1. UDP client is suitable for scenarios with high frequency of data interaction and low requirements for data reliability.
2. Before use, set the gateway IP and the communication partner IP to the same network segment and not conflict with each other. For example, if the gateway IP is 192.168.4.101, then the communication partner IP is set to 192.168.4.x (IP cannot conflict); if the communication partner IP cannot be changed, set the gateway IP address to the same network segment as the communication partner. For example, if the communication partner IP is 192.168.1.5, then set the gateway IP to 192.168.1.x
3. When the gateway is in UDP client mode, the communication partner needs to be set to UDP mode. At this time, the communication partner IP is used as the gateway target IP, and the communication partner port is the gateway target port.
Example: The communication partner parameters are IP: 192.168.4.100; local port: 8886
Then set the gateway IP: 192.168.4.x; local port: 1234; target IP: 192.168.4.100; target port: 8886;
Since the gateway sets the target IP and port, the data will be sent directly to IP: 192.168.4.100; local port: 8886
When the communication partner sends data, it is necessary to specify the IP as the gateway IP: 192.168.4.x and the port as the gateway local port: 1234