EBYTE ESR Series: A Practical Serial-to-WiFi Integration Guide for RS232/RS485 Retrofit

EBYTE Company Background

EBYTE (Shenzhen EBYTE Technology Co., Ltd.) is an industrial wireless module manufacturer based in Shenzhen, China. Founded in 2012, the company entered the market with LoRa modules before expanding into serial-to-WiFi converters around 2018. Today their product lineup covers WiFi 4 through WiFi 6, LoRa, BLE, and sub-GHz radio.

Their positioning is deliberate: EBYTE does not try to be a Qualcomm or Murata. They serve the segment where a designer needs a serial-to-WiFi bridge today, at an accessible price, with documented AT commands and enough free samples to prototype over a weekend. That combination — ease of ordering, low cost, and transparent bridge mode that needs zero host firmware — is what gives them traction with system integrators and small OEMs.

EBYTE modules carry CE RED, FCC Part 15C, and RoHS certifications across most of the ESR line. For a full list, see the official ESR-12 datasheet (Rev. 2.3) and the download center for AT command manuals and application notes.

ESR Series Serial-to-WiFi Product Line

ESR Series Model Comparison

Chipset Platforms Across the ESR Line

• Realtek RTL8720DN: Powers the ESR-12 and ESR-W02. WiFi 4 + BLE 5.0 combo, 200 mA peak TX, ideal for low-power nodes.
• Realtek RTL8821CU: Powers ESR-22 and ESR-32. WiFi 5 + Bluetooth 5.0, 433 Mbps PHY rate, used where higher throughput is needed for Modbus TCP payloads.
• Realtek RTL8852BU: Powers ESR-42. WiFi 6 (802.11ax) + BLE 5.2, 1201 Mbps peak, OFDMA support for enterprise RF density.
• ESP32 (ESR-W02 variant): Some ESR-W02 shipments use the ESP32-C3 chipset — same pinout, same AT command set, but with 4 MB flash and a built-in MCU.

Form Factors and Mechanical Notes

• DIP-18 (ESR-12): 27 x 18 mm, 2.54 mm pitch. Through-hole prototyping friendly. Mounting hole at corner for M2 screw.
• DIP-20 (ESR-22): Same width as ESR-12 but longer to accommodate the Ethernet PHY. Two mounting holes.
• SMT-24 (ESR-32): 25 x 18 mm, 0.8 mm pitch. Requires a reflow profile; the module has a metal ground shield on top.
• SMT-32 (ESR-42): 27 x 20 mm, 0.8 mm pitch. Larger to fit the dual-band WiFi 6 radio. Recommended to use a 4-layer PCB with dedicated ground plane.
• Breakout Boards: EBYTE sells pre-assembled evaluation boards for all five ESR models. The ESR-12-EVK includes an RS232 DB9 connector, a USB-to-UART bridge, and an SMA antenna connector. Priced at around $12 for prototype quantities.

Integration Models: Transparent Bridge vs AT Command

When Transparent Bridge Is the Right Choice

Transparent bridge (also called passthrough mode) is the default factory setting on every ESR module. Bytes written to the UART arrive at the remote TCP or UDP socket unchanged, and vice versa. The module handles WiFi association, DHCP lease, TCP connect, keepalive probes, and auto-reconnect — the host firmware never sees any of this.

• Legacy PLC or meter that cannot be re-flashed. The existing RS232 or RS485 protocol (Modbus RTU, S7, DL/T645) continues to run untouched. The host never learns a WiFi connection exists.
• Quick retrofit pilot. You can plug an ESR-12 into a DB9 connector, power it from a 24 V PLC rail, and start monitoring in under two hours.
• Multiple devices sharing a single bus. RS485 multi-drop topologies work unchanged; the module bridges the entire bus into one TCP socket on the upstream SCADA side.

The trade-off is limited visibility: you cannot query RSSI, force a reconnect, or read the TCP socket state from the host. If you need any of those, move to AT mode.

When AT Command Mode Is the Right Choice

In AT command mode, the host MCU drives the module through a text-based AT command set documented in the EBYTE AT Command Reference Manual (currently at Revision 1.6). The host sends AT+ commands and parses responses.

• New host designs where you want control. You can read RSSI, detect a dropped TCP socket, switch between two access points, or force a reconnect with a configurable backoff.
• MQTT gateway scenarios. Transparent bridge only speaks raw TCP/UDP. To speak MQTT you need AT mode — the module publishes messages through AT+MQTTPUB or the host runs MQTT on top of AT+SEND.
• OTA or remote configuration. AT commands let you change the target server IP, the socket port, or the keepalive interval remotely without a firmware reflash.

Serial-to-WiFi Retrofit: A Practical Integration Flow

1. Confirm the serial electrical layer first. RS232 (±12 V, point-to-point) and RS485 (differential, multi-drop) are not interchangeable. ESR modules expose a 3.3 V TTL UART; a level shifter sits between the module and the field wiring — MAX3232 for RS232, MAX485 for RS485. The direction pin on the MAX485 must be toggled by the module’s RX/TX, not by an external GPIO, if you want truly transparent bi-directional traffic.
2. Match baud, data bits, parity, and stop bits exactly. A single mismatch between the ESR module and the legacy device produces garbage in the transparent stream. Use AT+UART? to query the current setting, then AT+UART=115200,8,1,0 to write. 90% of the retrofit failures we have seen trace back to a baud rate mismatch that nobody bothered to verify.
3. Set socket timing parameters so the WiFi layer does not stall the field bus. AT+CIPSTO=60 sets a 60-second socket timeout; AT+CIPKEEPALIVE=20 configures a 20-second keepalive probe. Combine with AT+CJAUTO=1 to auto-reconnect to the access point on boot.
4. Validate Modbus RTU-over-TCP timing. If your upstream system is a SCADA platform that speaks Modbus TCP, the transparent bridge preserves the RTU CRC end-to-end. But the request-to-response round trip must still fit inside the SCADA master’s poll timeout (typically 500 ms). Add one or two access points with load balancing if you have more than 15 modules on the same SSID.
5. Log RSSI and reconnect reason at the host. Even in transparent bridge mode the module will output status messages on a dedicated debug UART pin if you configure AT+DBG=1. Use that to distinguish “RF dropped out” from “TCP connection refused” from “access point rebooted” when a field unit goes silent.

Case Study: ESR-12 PLC Retrofit in a Shanghai Automotive Parts Factory

Background

A tier-2 automotive parts supplier in Shanghai operates three assembly lines built in 2014. The lines run 47 PLCs — a mix of Siemens S7-200 SMART and Mitsubishi FX3U — none of which have Ethernet or WiFi. Daily production data was collected manually by technicians walking the factory floor and copying numbers from HMI screens to spreadsheets. The plant wanted real-time data flowing into their MES (Manufacturing Execution System) without replacing every controller.

The Constraints

• No PLC firmware changes were allowed — the machines were already validated for automotive quality and could not be re-flashed without a full re-qualification cycle.
• The MES already had Modbus TCP data collection endpoints on a dedicated VLAN.
• Factory floor has significant RF noise from variable-frequency drives (VFDs) and large metal enclosures.
• Budget was capped at $25,000 for the entire retrofit.

Solution

The integrator chose the EBYTE ESR-12 for three reasons: (1) transparent bridge mode needs zero host firmware changes, (2) it supports both RS232 (Siemens) and RS485 (Mitsubishi) with a simple level-shifter swap, and (3) the unit price was $9.60 in 100-piece quantities, well below the project budget.

Each PLC got one ESR-12 and one level shifter:

• Siemens S7-200 SMART (RS232): MAX3232 module wired to the PLC’s DB9 port. ESR-12 configured as transparent bridge, TCP client mode, connecting to the MES Modbus TCP endpoint at 192.168.200.10:502.
• Mitsubishi FX3U (RS485): MAX485 wired to the FX3U’s RS-485-BD board, with 120 ohm termination resistors at both ends of the bus. One ESR-12 bridges the entire multi-drop RS485 bus into a single TCP socket.
• Power: Every ESR-12 was powered from the PLC’s 24 V DC rail through a small buck converter — no new wiring harness needed.

Eight enterprise access points (TP-Link EAP265 HD, 2×2 WiFi 5) were mounted at ceiling height above each assembly line section. The plant’s IT team configured a dedicated SSID with WPA2-PSK on a VLAN that only connects to the MES subnet, so the PLCs never touch the office WiFi.

Results After Six Months

What They Would Do Differently Next Time

• Do a pre-deployment RF survey. Two ESR-12 units in the paint booth area had RSSI hovering around -78 dBm (the transparent bridge disconnects below -75 dBm). Adding external U.FL antennas and moving one access point cut the disconnection rate from 12/day to 1/month.
• Log reconnect reasons. They did not enable AT+DBG=1 on the first deployment batch, which made field support blind to whether a disconnection was RF, TCP, or PLC-side. All second-batch units ship with debug UART enabled and RSSI logged to a local microSD card.
• Use ESR-22 for the Ethernet PLCs. Six of the 47 PLCs had Ethernet ports that the team missed. The ESR-22’s RJ45 would have let them bridge Ethernet and WiFi simultaneously instead of converting to serial and back.

Working with EBYTE AT Commands: Practical Patterns

The complete AT command reference for the ESR line is maintained in the EBYTE AT Command Manual (Rev. 1.6). Below are the patterns you will use on almost every project.

Connecting to a WiFi Access Point

AT+CWMODE=1          // Set station mode (1=STA, 2=AP, 3=STA+AP)
AT+CJAUTO=1,1,"ProdFloor_AP","P@ssw0rd!"   // Auto-connect on boot
AT+CWJAP="ProdFloor_AP","P@ssw0rd!"         // Connect immediately
// Response: +CWJAP:1,192.168.200.54,FFFFFFFF,3
// Fields: [status], [IP], [BSSID], [RSSI in dBm]

Opening a TCP Client Socket

AT+CIPSTART="TCP","192.168.200.10",502    // Connect to Modbus TCP server
AT+CIPSTO=60                               // 60-second idle timeout
AT+CIPSEND=26                              // Send 26 bytes (e.g., Modbus RTU frame over TCP)
>0001000000060101000A                                // Raw hex payload
SEND OK
+CIP: 1,CLOSED                             // Triggered when remote end closes

Sending Modbus RTU-Over-TCP Through a Transparent Bridge

This is the pattern that got the Shanghai factory project working. Transparent bridge mode means you never touch AT commands for the data path — you configure TCP client once, then all RTU traffic flows through:

AT+CIPMUX=0              // Single connection mode
AT+CIPSTART="TCP","192.168.200.10",502
AT+CIPSEND               // Enter transparent send mode (no byte count needed)
// After this point, every byte written to UART goes over TCP verbatim:
[Modbus RTU query frame] → [TCP payload] → MES server → [Modbus TCP response] → back to UART

Debugging Common AT Responses

Industrial Application Scenarios

PLC and Industrial Controller Retrofit

• Remote monitoring of production lines where manual data collection was the bottleneck — see the Shanghai factory case study above.
• Wireless PLC programming and diagnostics — an ESR-12 in AT mode lets you SSH to the module over WiFi and tunnel the programming cable protocol over UDP.
• Machine-to-machine (M2M) communication across factory zones that were previously isolated by RS485 bus distance limits.
• Real-time OEE (Overall Equipment Effectiveness) data acquisition at 1-second polling intervals — well within the transparent bridge’s sub-50 ms latency.

Smart Agriculture and Environmental Sensing

• Soil moisture monitoring nodes on RS485 buses, bridging to WiFi at the greenhouse edge gateway.
• Greenhouse climate controllers (temperature, humidity, CO2 sensors) that were originally wired to a local HMI and now report to a cloud dashboard.
• Smart irrigation systems where the legacy controller speaks a proprietary serial protocol — transparent bridge carries it unchanged to a cloud MQTT broker.

Building Automation and HVAC

• Legacy BACnet MS/TP devices (BACnet over RS485) bridged to BACnet/IP over WiFi for modern building management systems.
• VFD (Variable Frequency Drive) monitoring — many VFDs have a Modbus RTU port that nobody ever used; an ESR-12 makes those readings accessible.
• Access control systems and lighting controllers where pulling new cable is prohibitively expensive.

Key Features & Protocol Support

Protocol Stack

• TCP/IP and UDP: Full IPv4 stack, single or multi-connection mode configurable via AT+CIPMUX.
• HTTP/HTTPS: The module can run a basic web server for configuration pages (AT+WEBSVR=1) and act as an HTTP client with AT+HTTPGET / AT+HTTPPOST.
• MQTT v3.1.1: AT-mode only. AT+MQTTCONN, AT+MQTTPUB, AT+MQTTSUB. Supports TLS for ESR-32 and above.
• Modbus RTU-over-TCP: Native support — transparent bridge preserves RTU CRC; no additional firmware needed.
• CoAP: Available on WiFi 5 and WiFi 6 models (ESR-32, ESR-42) with a firmware option.

Wireless and Security Features

• WiFi Standards: 802.11b/g/n (ESR-12, ESR-22, ESR-W02), 802.11ac (ESR-32), 802.11ax (ESR-42).
• Encryption: WPA2-PSK/WPA2-Enterprise on all models. WPA3 (SAE) on WiFi 6 models only.
• Auto-reconnect: AT+CJAUTO=1 configures persistent AP connection across power cycles and RF drops with configurable backoff.
• OTA Updates: AT+UPDATE=OTA lets you push firmware over WiFi. EBYTE releases quarterly firmware updates that fix known AT command bugs and add protocol support.
• DHCP / Static IP: AT+CIPSTO? to query current IP settings; AT+CIPSTA for static assignment.

Industrial-Grade Reliability Specs

• Temperature Range: ESR-12 and ESR-22: -40°C to +85°C. ESR-32 and ESR-42: -40°C to +105°C.
• ESD Protection: ±15 kV HBM on all pins (per IEC 61000-4-2).
• MTBF: 100,000+ hours under typical 25°C operating conditions, per EBYTE’s reliability report.
• RF Shielding: SMT models (ESR-32, ESR-42, ESR-W02) have integrated metal ground shields. DIP models can be placed inside an optional RF shield enclosure.

ESR Model Selection Decision Tree & Alternatives

ESR Model Selection Decision Tree

Q1: What serial interface does your legacy device expose?
├─ RS232 only ────────────────────────────────────────────→ ESR-12 (DIP) or ESR-32 (SMT)
├─ RS485 only ────────────────────────────────────────────→ ESR-12 (need MAX485) or ESR-32
├─ Both RS232 and RS485 (separate devices on same bus) ──→ ESR-12 (selectable)
├─ TTL / UART only (no RS232/RS485 level needed) ────────→ ESR-W02

Q2: What WiFi generation do you need?
├─ Legacy 802.11b/g/n (most industrial deployments) ──────→ ESR-12 or ESR-22
├─ Need 5 GHz for higher throughput or less 2.4 GHz noise → ESR-32 (WiFi 5)
├─ Need enterprise RF density / WPA3 / OFDMA ─────────────→ ESR-42 (WiFi 6)

Q3: Do you also need Ethernet or BLE?
├─ Need Ethernet RJ45 as backup or primary ───────────────→ ESR-22 (only ESR model with RJ45)
├─ Need BLE gateway alongside WiFi ───────────────────────→ ESR-12 or ESR-W02 (BT 5.0 built in)

Q4: Form factor?
├─ Through-hole, hand-soldered, quick prototype ──────────→ Any DIP model (ESR-12, ESR-22)
├─ Surface mount, mass production, reflow ────────────────→ Any SMT model (ESR-32, ESR-42, ESR-W02)

When to Pick Each Model

• ESR-12: The default choice. Best price, widest availability, well-documented. 80% of EBYTE customer designs use this model.
• ESR-22: Choose this if you need both WiFi and wired Ethernet — useful when you have a mix of legacy serial devices and IP-based devices on the same system.
• ESR-32: Pick this when you need WiFi 5 (5 GHz support) in a 2.4 GHz-noisy environment (welding shops, motor control rooms). The SMT form factor means higher integration cost but better RF shielding.
• ESR-42: Only justified for dense RF environments (many modules on one SSID) or enterprise-grade deployments that require WPA3 or WiFi 6 features like target wake time.
• ESR-W02: For battery-powered sensors. Ultra-low power draw (~15 mA average in sleep mode). Small form factor for wearable or edge applications.

When to Consider Alternatives to EBYTE

• Murata: Murata modules come pre-certified (FCC, CE, MIC) with full PA/LNA front-ends. You pay a 3x premium over EBYTE but save months of regulatory testing on high-volume designs.
• 10+ other manufacturers: For a cross-vendor comparison including Compex, Quectel, Telit, and Yuneng Micro before committing.
• Espressif (ESP32): If you are designing from scratch and don’t need transparent bridge mode, an ESP32 with your own firmware is cheaper per unit and more flexible — but you lose the “zero-firmware-change” advantage of EBYTE.
• Qualcomm-based modules (Compex): For enterprise-grade throughput (WiFi 6/6E/7) and full software stacks (OpenWRT). See our Qualcomm WiFi Chipset Guide.

Certifications & Compliance

Certifications Across the ESR Line

What You Still Need to Do for Your End Product

EBYTE’s certifications cover the module itself, not the final product that contains it. Depending on where you sell and what industry you target, you may still need to handle:

• End-product FCC certification. Embedding an FCC-certified module into your product grants you “modular approval” under certain conditions (U.FL antenna, listed cable type, listed enclosure). Read FCC Part 15.212 carefully before skipping full testing.
• Industry-specific standards. If your product goes into medical (IEC 60601), automotive (ISO 26262), or aviation (DO-160) environments, EBYTE’s generic industrial certifications are not enough — you will need additional testing.
• ESR-W02 ESP32 variant note. The ESP32-C3-based ESR-W02 is a “module with integrated MCU,” so FCC certification is slightly more complex than the Realtek-based ESR models. Consult EBYTE’s application note AN-019 for details.

For the complete list of current certifications and downloadable certificates, visit the EBYTE certification page.

Troubleshooting Serial-to-WiFi Retrofits

Issue 1: Garbled Serial Data on Transparent Bridge (60% of field failures)

Root cause: Baud rate mismatch between the legacy device and the ESR module. Most PLCs ship at 9600 or 19200 baud; if your ESR is still on the factory default of 115200, you will get nothing but garbage.

• Diagnose: Use AT+UART? to query the current baud setting on the ESR. Compare with the device datasheet or the DIP switch setting on the device itself.
• Fix: AT+UART=9600,8,1,0 (replace 9600 with the correct baud). Power cycle the module for the setting to take effect.
• Prevent: Add a baud rate auto-detection step at commissioning time. The ESR-12 can auto-sense baud rates 9600-115200 with AT+UARTAUTO=1.

Issue 2: WiFi Connected But TCP Socket Times Out (25% of field failures)

Root cause: The TCP remote address is correct, but the router between the ESR and the MES server has a firewall rule blocking port 502 (Modbus TCP) or your custom port.

• Diagnose: From a laptop on the same VLAN, run `telnet 192.168.200.10 502` — if it connects, the firewall is not the problem. Then run AT+CIPSTART=”TCP”,”192.168.200.10″,502 from the ESR’s UART to see the exact error.
• Fix: Ask IT to create an allow rule for the VLAN that your ESR modules are on, or switch to a known-open port like 8443 (HTTPS) and put a reverse proxy in front.

Issue 3: Intermittent Disconnections in Metal Enclosures (10% of field failures)

Root cause: Faraday cage effect. When an ESR-12 is inside a grounded metal cabinet (common for VFDs and power supplies), RF attenuation can drop RSSI below -75 dBm — the point at which WiFi reconnection starts.

• Diagnose: Enable the debug UART with AT+DBG=1. Log the RSSI reported during every connection attempt. Anything below -70 dBm will be unstable.
• Fix: Replace the PCB antenna with a U.FL external antenna, and mount the antenna on a non-metal panel of the cabinet, or on the ceiling wire above. Aim for RSSI of -55 dBm to -65 dBm minimum.

Issue 4: Modbus RTU CRC Errors After Retrofit (5% of field failures)

Root cause: RS485 bus termination. When you add an ESR module in transparent mode to a multi-drop RS485 bus, you change the bus topology and may need to move or split the 120 ohm termination resistors.

• Diagnose: Measure the bus impedance with an oscilloscope. A correctly terminated bus reads 120 ohms between A and B with all devices powered down.
• Fix: On a multi-drop bus, the termination should be at the two extreme ends of the bus, nowhere in the middle. Adding an ESR module as a middle drop means the terminations stay at the original end devices, not at the ESR.

Frequently Asked Questions