E90-DTU (400SL30-ETH) User Manual

1. Product Overview

1.1 Introduction

The E90-DTU (400SL30-ETH) is a wireless modem and data transceiver that supports adaptive network speed up to 100M full-duplex. It offers four working modes: TCP Server, TCP Client, UDP Server, and UDP Client, and supports two-way SOCKET communication. The device utilizes LoRa direct sequence spread spectrum technology for extended communication distance, high power density, and strong anti-interference capabilities. It incorporates a software FEC (Forward Error Correction) algorithm for high coding efficiency and robust error correction, enabling active correction of interfered data packets to enhance reliability and transmission distance. This facilitates efficient transparent transmission of long-distance data. Configuration is accessible via a web page.

Device Description: The E90-DTU (400SL30-ETH) is a compact, black rectangular device. The front panel features indicators labeled 'PWR' (Power), 'LINK' (Connection), and 'DATA' (Serial port TX and RX). Connectivity includes a DC power input (DC8-28V), an Ethernet port (RJ45), and an ANT (antenna) connector. The top surface displays a world map graphic and the EBYTE logo.

2. Parameters

2.1 General Parameter

2.2 Wireless Parameter

2.3 Dimension and Pin Definition

The device dimensions are approximately 84mm (width) x 82mm (depth) x 25mm (height). Detailed drawings show the placement of ports and mounting holes. The top view indicates dimensions of 82mm width and 50mm internal width. Side views show the 84mm width and 25mm height. Front and rear views detail port locations and dimensions.

Port Definitions:

2.4 Connection Method

The connection method illustrates using an RJ45 Ethernet cable to connect a PC/Router/Switch to the E90-DTU device. This setup is typical for network communication between devices.

3. Product Functions

3.4 Basic Function

Ethernet

SOCKET

The E90-DTU-(400SL30-ETH) can establish two Sockets: Socket A1 and Socket B1. Socket A1 supports TCP Client, TCP Server, UDP Client, and UDP Server. Socket B1 supports TCP Client, UDP Client, and UDP Server. Both sockets can run simultaneously and connect to different networks for data transmission.

TCP Client

The TCP Client mode provides a client connection for TCP network services. It initiates connection requests to a server for data interaction. This mode ensures reliable data exchange through connection and disconnection, commonly used for device-to-server communication. When connecting to a server with local port 0, a random port is used. The device supports a short connection function. For devices on the same LAN using static IP, ensure the IP and gateway are on the same network segment for proper communication.

Diagram: Illustrates a TCP Client device connecting to a TCP Server, with network data flowing between them.

TCP Server

In TCP Server mode, the E90-DTU-(400SL30-ETH) listens on a local port, accepts connection requests, and establishes data communication. Received data is sent to all connected client devices. This mode is suitable for LAN communication where multiple clients (computers or mobile phones) request data from the server. It also ensures reliable data exchange through connection and disconnection. The device can accept up to 6 client connections (customizable), with a fixed local port number. The maximum number of connections can be configured, allowing for kicking off old connections or disabling new ones.

Diagram: Shows multiple TCP Clients connecting to a TCP Server (E90-DTU), with network data flowing.

UDP Client

UDP Client is a connectionless protocol for simple, unreliable data transmission. It requires only IP and port to send data. It's used for scenarios where packet loss is acceptable, data packets are small, and transmission is frequent. In this mode, the device only communicates with the specified target IP and port. Setting the destination address to 255.255.255.255 enables UDP broadcast across the network segment, allowing reception of broadcast data.

Diagram: Illustrates UDP Client configurations, including sending data to a specific IP/port and a broadcast scenario.

UDP Server

UDP Server mode does not verify the source IP address. Upon receiving a UDP packet, it forwards the data to the source IP and port. This mode is efficient for scenarios where multiple network devices need to communicate quickly without the overhead of TCP. Note that UDP Server cannot initiate data transmission; it only responds to received data by sending it back to the source.

Diagram: Shows a UDP Client sending data to a UDP Server, which then forwards it to another UDP Client, highlighting the 'To the nearest TX port' functionality.

WOR Role

WOR Closed: The DTU operates in transmission mode, sending data received via Ethernet wirelessly. Wireless reception is active, and received data is output via Ethernet.

WOR Transmitter: The DTU sends and receives data, adding a wake-up code for a specific period during transmission.

WOR Receiver: The DTU only listens in WOR mode and cannot transmit data. The listening period is configured via the web interface. Longer listening intervals reduce power consumption but increase data delay; consistency between devices is crucial.

Fixed Point Transmission

This function supports addressing, enabling the master device to transmit data to specific addresses and channels, facilitating networking and relay functions. For example, module A sending data to module B requires specifying module B's address (e.g., 0x00 01) and channel (e.g., 0x80). The communication format would be '00 01 80 AA BB CC', where only module B receives 'AA BB CC'.

3.5 Featured Function

3.5.1 Web Page Configuration

The device supports web page configuration. Users can access the configuration interface by entering the module's IP address (default: 192.168.4.101) and port (default: 80) in a web browser. After successful login, the web configuration page is displayed.

Web Interface Description: The Ebyte IOT web interface provides sections for 'Current State', 'IP Setting', 'Parameter Setting', 'Advanced Setting', and 'Management'. It displays device information such as Type (E90-DTU(900SL30-ETH)), Version (V1.1), Current IP Address (192.168.4.101), MAC Address, SN Code, and connection status for Socket A and B. Helpful tips are provided for SN code and connection status.

3.5.2 Heartbeat Function

In network transparent transmission mode, the E90-DTU-(400SL30-ETH) can send heartbeat packets to the web server. This function is primarily used to maintain a connection with the server and is effective in TCP Client and UDP Client modes. The module supports custom heartbeat packets up to 40 bytes.

Diagram: Shows an ETH Device (E90-DTU) sending heartbeat packets to a Server.

3.5.3 Registration Package Function

In network transparent transmission mode, users can send a registration packet to the server for device recognition or authorization. This packet can be sent upon connection establishment or spliced into data packets. The registration data can be a MAC address or custom data (up to 40 bytes). This mechanism is used for servers requiring registration and is available only for TCP Client and UDP Client modes.

Diagram: Illustrates carrying registration packages (AA, BB, CC) from E90-DTU devices to a TCP Server.

3.5.4 Short Connection Function

TCP short connections save server resources and are suited for multi-point scenarios. This function, applied to TCP Client mode, automatically disconnects if no data is received within a set time. It is turned off by default, with a configurable disconnection time ranging from 2 to 255 seconds.

3.5.5 KeepAlive Function

The Keep-Alive mechanism detects dead TCP connections. If no data is sent, periodic 'Keep-Alive' information is transmitted to maintain the link, preventing dead connections and conserving resources. Users can customize the Keep-Alive switch and parameters like time (seconds to start probe), intv (time interval between probes), and probes (maximum probe failures before disconnection).

3.5.6 Timeout Restart Function

The timeout restart function ensures stable operation. If the network port does not receive data for a prolonged period, the device restarts after a set time to prevent communication anomalies. The timeout can be set via the web page, with a normal working range of 60-65535 seconds (default 3600 seconds). Setting it to 0 disables the function.

3.5.7 Clearing the Cache Function

When a TCP connection is not established, received data is stored in a 2Kbyte buffer. When a connection is established, network cache data can be managed as required. The device has two buffer areas: serial data and network data. Enabling the 'Socket clear cache' function clears only the relevant socket's cache data, not the serial cache data.

Diagram: Shows 'UART cache area' and 'Network data cache area'.

3.5.8 Link/ Data Transmission Indication

The 'Link' indicator shows network connection status: off when disconnected, always on when connected (TCP mode). It's always on in UDP mode. The 'Data' indicator shows transmission status: off when idle, flashing when data is being transmitted (10ms on, 60ms off cycle).

3.5.9 Restore to Factory Setting

The device can be restored to factory settings via software or a button press.

4. Quick Start

4.1 Default Parameter

4.2 SOCKET Instruction

Preparation: Set the PC's IP address and subnet mask to be the same as the E90-DTU. For example, PC IP: 192.168.4.100, Module IP: 192.168.4.101.

4.3 TCP Client Guidance

1. On Computer A and Computer B, open 'Network Debugging Assistant'. Set the protocol to TCP Server and configure the local IP to 192.168.4.100 and port to 8886.

2. Configure Socket A1 on Device A and Device B to TCP Client mode. Set the destination IP to 192.168.4.100 and the destination port to 8886. The local port can be 0 (random). Click 'Save' to restart the module.

3. The DTU is connected via Network Debugging Assistant for communication test. Screenshots show the setup where one computer acts as a TCP Server and the other as a TCP Client, demonstrating data exchange.

4.4 TCP Server Guidance

1. On Computer A and Computer B, set the 'Network Debugging Assistant' to TCP Client mode. Set the remote host IP to 192.168.4.101 and the remote host port to 8886.

2. Configure Socket A1 on Device A and Device B to TCP Server mode. Set the local port to 8886. Click 'Save' to restart the module.

3. The DTU is connected via Network Debugging Assistant for communication test. Screenshots show the setup where one computer acts as a TCP Client and the other as a TCP Server, demonstrating data exchange.

4.5 UDP Client Guidance

1. Set 'Network Debugging Assistant' to UDP mode (no need to specify Client/Server). Set the master IP to 192.168.4.100, local port to 8887, and remote master to 192.168.4.101:8886.

2. Configure Socket A1 on Device A and Device B to UDP Client mode. Set the target IP to 192.168.4.100 and the destination port to 8887. Click 'Save' to restart the module.

3. The DTU is connected via Network Debugging Assistant for communication test. Screenshots show the setup for UDP Client communication between two computers.

4.6 UDP Server Guidance

1. Set 'Network Debugging Assistant' to UDP mode. Set the local host IP to 192.168.4.101 and the local port to 8886. Set the remote host to 192.168.4.101:8887.

2. Configure Socket A1 on Device A and Device B to UDPS (UDP Server) mode. Set the local port to 8887. Click 'Save' to restart the module.

3. The DTU is connected via Network Debugging Assistant for communication test. Screenshots show the setup for UDP Server communication between two computers.

4.7 WEB Introduction

The module supports web page configuration. Access the configuration interface by entering the module's IP address and port (default 80) in a web browser. After successful login, the web page is displayed, allowing parameter browsing and configuration, such as LoRa settings.

Web Interface Description: The Ebyte IOT web interface includes sections for 'Current State', 'IP Setting', 'Parameter Setting', 'Advanced Setting', and 'Management'. It displays device type, version, IP address, MAC address, SN Code, and connection status for Sockets A and B. Helpful tips are provided.

After entering parameters, click 'Save setting'. The page will redirect to the module management page. Restarting the module applies the saved settings.

Revision History

About Us

Technical support: support@cdebyte.com

Documents and RF Setting download link: www.cdebyte.com/en/

Tel: +86-28-61399028

Fax: 028-64146160

Web: www.cdebyte.com/en/

Address: B5 Mould Park, 199# Xiqu Ave, High-tech District, Sichuan, China

Company: Chengdu Ebyte Electronic Technology Co., Ltd.