wireless-tag WT32-ETH02 WiFi Module Owner’s Manual

wireless-tag WT32-ETH02 WiFi Module Owner’s Manual

Datasheet
Version 1.0
October 31, 2023

Disclaimer and Copyright Notice

The information in this document, including the URL addresses for reference, is subject to change without notice.

This document is provided “as is” without warranty of any kind, including any warranty of merchantability, fitness for a particular purpose, or non- infringement, and any warranty that any proposal, specification, or sample is referred to elsewhere. this document disclaims all liability, including liability for infringement of any patent, arising out of the use of the information in this document. This document does not grant any license, express or implied, by estoppel or otherwise, to use any intellectual property.

The Wi-Fi Alliance member logo is owned by the Wi-Fi Alliance.

All trade names, trademarks and registered trademarks mentioned herein are the property of their respective owners and are hereby acknowledged.

Revision History

Overview

WT32-ETH02 is an embedded serial-to-Ethernet development board based on ESP32series launched by Wireless-Tag Technology Co., Limited with the development board’ module internal integration of the optimized TCP/IP stack, which facilitates the user to easily complete the networking function of the embedded device and greatly reduces the development time and cost. Moreover, the board is compatible with half-pad and connector through-hole design, and the board width is universal, which is convenient for users to use indifferent scenarios.

The ESP32 family of IC is an integrated 2.4GHz Wi-Fi and Bluetooth B L E SOC with ultra-high RF performance, stability, versatility and reliability, and ultra-low power consumption.

Features

Form

| Sports event| Product Specification
---|---|---
WiFi| RF certification| FCC/CE/RoHS
Pact| 802.11 b/g/n/e/i (802.11n at speeds up to 150
A-MPDU and A-MSDU aggregation with 0.4 _s
Frequency range| 2.4~2.5 GHz
Bluetooth| Pact| Compliant with Bluetooth v4.2 BR/EDR and BLE
Radio frequency| NZIF receiver with -97 dBm sensitivity
Software| Mesh specification| RJ45, 10/100Mbps, Cross Direct Adaptive
Serial port baud rate| 80~5000000
Onboard Flash| 128Mbit
Operating voltage| 5V or 3.3V supply (either)
Operating Current| Average: 80mA
Supply Current| Minimum: 500 mA
Operating Temperature| -40°C~+85°C
Ambient temperature| normal temperatures
Seal inside| Half-pad/connector through-hole connection
Hardware| Wi-Fi Mode| Station/softAP/SoftAP+station/P2P
| Wi-Fi security mechanisms| WPA/WPA2/WPA2-enterprise/WPS
| Encryption Type| AES/RSA/ECC/SHA
| Firmware Upgrade| Remote OTA upgrade over the network
| Software development| SDK for secondary user development
| network protocol| IPV4, TCP/UDP
| IP acquisition method| Static IP, DHCP (default)
| Simple Transmission| TCP Server/TCP Client/UDP Server/UDP Client
| User configuration| AT+ Instruction Set

Hardware Specifications

System Block Diagram

Product image

Pin Description

Power supply characteristics

Supply voltage

The power supply voltage of the module can be either 5V or 3V3, only one of them can be selected

Power supply modes

Users are free to choose according to their needs:

1. Through-hole (soldered row of pins): breadboard connection / Dupont wire connection for power supply.
2. Half-pad (soldered directly to the board): User board power supply.

Instructions

Power-on instruction

If the DuPont cable is used: find the 3V3 or 5V power input port and connect the corresponding voltage, the indicator light (LED1) will be on to indicate successful power-up.

Indicator Instruction

LED1: Power indicator, power on normal, light on;
LED3: Serial port indicator, lighted when there is data streaming fromRXD2 (IO5);
LED4: Serial port indicator, lighted when TXD2 (IO17) has data stream;

Usage Instruction

Three ways of use, the user can choose according to the needs of their own:

1. Through-hole (soldered row of pins): Connect using Dupont wire;
2. Through-hole (soldering row of pins): placed on the breadboard for use;
3. Half-pad: Users can directly solder the module to their own boards.

Network Port Indicator Instruction

send, including when the module receives a network broadcast packet

Product Functions

Default parameters

Basic Functions

Set IP/ Subnet Mask / Gateway

The IP address is the identity representation of the module in the LAN and is unique in the LAN, so it cannot be duplicated with other devices in the same LAN. The IP address of the module can be obtained in two ways: static IP and DHCP/dynamic IP.

1. Static IP needs to be set manually by the user. During the setting process, pay attention to write IP, subnet mask and gateway at the same time, static IP is suitable for the scenario that needs to count IP and devices and corresponds to each other one by one. Pay attention to the correspondence between IP address, subnet mask and gateway when setting. To use static IP, you need to set up each module and make sure that the IP address is not duplicated with other network devices in the LAN.
2. DHCP/Dynamic IP The main function is to get the IP address, Gateway address, DNS server address and other information from the gateway host dynamically, so as to avoid the tedious steps of setting IP address. It is suitable for the scenarios where the reisno requirement for IP and the IP is not forced to correspond with the module one by one.

Note: The module cannot be set to DHCP when it is directly connected to a computer. Generally, computers do not have the ability to assign IP addresses, so if the module is set to DHCP when it is directly connected to a computer, it will cause the module to be in astute of waiting for an IP address to be assigned, which will result in the module not being able to carry out normal work in the pass-through. The module defaults to static IP: 192.168.0.7.

Restore factory settings

1. AT command to restore factory settings: Restore factory via AT+ RESTORE.
2. Hardware restoration of factory settings: Ground the CFG pin and reboot the module.

Firmware upgrade

The module upgrades the firmware by OTA remote upgrade, by upgrading the firmware, you can get more application functions.

1. Firmware upgrade can be done via wired network or wifi.
2. Operate GPIO2 to ground, reboot the module and enter OTA upgrade mode.
3. Upgrade is completed, disconnect GPIO2 from ground, restart the module, and the module enters the normal working mode

OTA Firmware Upgrade Indication Description: Firmware is being downloaded, serial port TXD indicator is flashing fast; download is completed and upgrading is in progress, serial port TXD indicator is always on; upgrading is successful, serial port TXD and RXD indicators are always on; upgrading is failed, serial port TXD indicator is flashing slowly.

Command Function Settings

Users can set the function of the module by inputting AT command through the serial port. For details, please refer to esp32 wired module AT command set.

Date Transmission Function

The module has four data transmission ports: serial, wifi, Ethernet and Bluetooth.
Users can combine the four data ports two by two through the AT command for data transmission. Set/query the pass-through channel of the module through
AT+PASSCHANNEL command. After setting, the module needs to be restarted to takeeffect.

Socket Function

The socket operation modes of the module are divided into four types: TCP Client, TCP Server, UDP Client, and UDP Server, which can be set by the AT command. For AT command operation, please refer to esp32 wired module AT command routinev1.2.

TCP Client

TCP Client provides client connection for TCP network service. It initiates a connection request to the server and establishes a connection, which is used to realize the interaction between serial port data and server data. According to the relevant provisions of the TCP protocol, the TCP Client has the difference between connecting and disconnecting, so as to ensure the reliable exchange of data. It is usually used for data interaction between devices and servers, and is the most commonly used networking communication method.

When the module connects to TCP Server as a TCP Client, you need to pay attention to the parameters such as target IP/domain name and target port number. The target IP can be a local device in the same local area, or an IP address of a different local area network (LAN) or an IP of a cross-public network; if you connect to a server of a cross-public network, it is required for the server to have a public network IP.

TCP Server

Usually used for communication with TCP clients on a LAN. It is suitable for the scenario that there is no server in the LAN and there are many computers or cell phones requesting data from the server. Like TCP Client, there is a difference between connecting and disconnecting to ensure reliable data exchange.

UDP Client

UDP Client is a connectionless transport protocol that provides a simple, transaction-oriented, unreliable messaging service. There is no connection to make or break, and all that is needed is an IP and port to send data to the other party. It is usually used in data transmission scenarios where there is no requirement for packet loss, where packets are small and sent quickly, and where the data is destined for a specified IP.

UDP Server

UDP Server means that on the basis of ordinary UDP, without verifying the source IP address, every time it receives a UDP packet, it will change the destination IP to the data source IP and port number, and when it sends data, it will send it to the most recently communicated IP and port number. This mode is usually used in data transmission scenarios where multiple network devices need to communicate with the module and do not want to use TCP due to the high speed and frequency.

Serial Port Function

AT Command Settings

The user can set the function of the module by inputting AT command through the serial port.

Transmit serial data

The user can make the module enter the data transmission mode by AT command, and the module can directly transmit the serial data to the corresponding data transmission terminal (wifi, Ethernet and Bluetooth) through the already set transmission channel.

Bluetooth function

Through the existing Bluetooth function of the module, the module can acquire
Bluetooth data, and through the transmitting channel that has been set up, it can directly transfer Bluetooth data to the corresponding data transmission terminal (wifi, Ethernet and serial port).

WiFi function

Module wifi access to the Internet or LAN through the router, the user configures the socket function through the AT command, the module can establish a TCP/UDP connection, and can access the user’s designated server.

Wired Port Access Function

The module is connected to the Internet or LAN through a wired network. Users can configure the socket function through the AT command, and the module can establish TCP/UDP connection to access the user’s specified server

Federal Communication Commission Statement (FCC, U.S.)

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant
to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequencenergy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which canbe determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one of the following measures:

• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
• Consult the dealer or an experienced radio/TV technician for help

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

1. This device may not cause harmful interference, and
2. this device must accept any interference received, including interference that may cause undesired operation.

FCC Caution:

Any changes or modifications not expressly approved by the party responsible for compliance couldvoidthe user’s authority to operate this equipment.

FCC Radiation Exposure Statement:

This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 20cm between the radiator &your body

IMPORTANT NOTES

Co-location warning:
This transmitter must not be co-located or operating in conjunction with any other antenna or transmitter

OEM integration instructions:
This device is intended only for OEM integrators under the following conditions:

The transmitter module may not be co-located with any other transmitter or antenna. The module shall
be only used with the external antenna(s) that has been originally tested and certified with this module.

As long as the conditions above are met, further transmitter test will not be required. However, the OEM integrator is still responsible for testing their end-product for any additional compliance requirements required with this module installed (for example, digital device emissions, PC peripheral requirements, etc.).

Validity of using the module certification:

In the event that these conditions cannot be met (for example certain laptop configurations or co-location with another transmitter), then the FCC authorization for this module in combination with the host equipment is nolonger considered valid and the FCC ID of the module cannot be used on the final product. In these circumstances, the OEM integrator will be responsible for re-evaluating the end product (including the transmitter) and obtaining a separate FCC authorization.

End product labeling:
The final end product must be labeled in a visible area with the following: “Contains Transmitter Module FCC ID: 2AFOS-WT32-ETH02”.

Information that must be placed in the end user manual:

The OEM integrator has to be aware not to provide information to the end user regarding how to install or remove this RF module in the user’s manual of the end product which integrates this module. The end user manual shall include all required regulatory information/warning as show in this manual.

Integration instructions for host product manufactures according to KDB 996369 D03OEMManual v01

List of applicable FCC rules
FCC Part 15 Subpart C 15.247 & 15.207 & 15.209

Specific operational use conditions
The module is a WiFi Module with 2.4G WLAN and BLE 2.4G function.

2.4G WLAN Specification：

• Operation Frequency: 2412~2462MHz
• Number of Channel: 11
• Modulation: DSSS, OFDM
• Type: PCB Antenna
• Gain: 2.86dBi

BLE Specification：

• Operation Frequency: 2402~2480MHz
• Number of Channel: 40
• Modulation: GFSK
• Type: PCB Antenna
• Gain: 2.86dBi

The module can be used for mobile or applications with a maximum 2.86dBi antenna. The host manufacturer installing this module into their product must ensure that the final composit product complies with the FCC requirements by a technical assessment or evaluation to the FCC rules, including the transmitter operation. The host manufacturer has to be aware not to provide information to the end user regarding how to install or remove this RF module in the user’s manual of the end product which integrates this module. The end user manual shall include all required regulatory information/warning asshow in this manual.

Limited module procedures
Not applicable.

Trace antenna designs
Not applicable. The module has its own antenna, and doesn’t need a host’s printed board microstrip trace antenna etc.

RF exposure considerations
The module must be installed in the host equipment such that at least 20cm is maintained between the antenna and users’ body; and if RF exposure statement or module layout is changed, then the host product manufacturer required to take responsibility of the module through a change in FCC ID or newapplication. The FCC ID of the module cannot be used on the final product. In these circumstances, the host manufacturer will be responsible for re- evaluating the end product (including the transmitter) and obtaining a separate FCC authorization

Antennas

Antenna Specification are as follows:
Type: PCB Antenna
Gain: 2.86dBi

This device is intended only for host manufacturers under the following conditions: The transmitter module may not be co-located with any other transmitter or antenna; The module shall be only used with the internal antenna(s) that has been originally tested and certified with this module. The antenna must be either permanently attached or employ a ‘unique’ antenna coupler.

As long as the conditions above are met, further transmitter test will not be required. However, the host manufacturer is still responsible for testing their end-product for any additional compliance requirements required with this module installed (for example, digital device emissions, PC peripheral requirements, etc.)

Label and compliance information

Host product manufacturers need to provide a physical or e-label stating “Contains Transmitter Module
FCC ID: 2AFOS-WT32-ETH02” with their finished product.

Information on test modes and additional testingrequirements

Operation Frequency: 2402~2480MHz
Number of Channel: 40
Modulation: GFSK

2.4G WLAN

Operation Frequency: 2412~2462MHz
Number of Channel: 11
Modulation: DSSS, OFDM

Host manufacturer must perfom test of radiated & conducted emission and spurious emission, etc according to the actual test modes for a stand-alone modular transmitter in a host, as well as for multiple simultaneously transmitting modules or other transmitters in a host product. Only when all the test results of test modes comply with FCC requirements, then the end product can be sold legally.

Additional testing, Part 15 Subpart B disclaimer
The modular transmitter is only FCC authorized for FCC Part 15 Subpart C 15.247 & 15.207 & 15.209 and that the host product manufacturer is responsible for compliance to any other FCC rules that apply to the host not covered by the modular transmitter grant of certification. If the grantee markets their product as being Part 15 Subpart B compliant (when it also contains unintentional radiator digital circuity), then the grantee shall provide a notice stating that the final host product still requires Part 15 Subpart B compliance testing with the modular transmitter installed.

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>