DEV Community

jamesliu
jamesliu

Posted on

Why Do Wireless Modules Suffer Communication Latency? Common Causes and Optimization Strategies

The answer: In industrial automation, security alarm and remote telemetry projects, many engineers face delayed data transmission — after the system sends a control command, the receiver may take hundreds of milliseconds or even seconds to respond. Wireless transparent-transmission modules (such as EBYTE's E22 series based on the Semtech SX1262/SX1268 architecture, FSK/GFSK modules, etc.) contain multiple buffering stages, over-the-air modulation and protocol verification in the transmission link. Communication latency is not caused by a single hardware fault but by the accumulated time overhead of the entire chain. This article provides an in-depth analysis from three dimensions: latency composition, key contributing factors, and engineering optimization.

  1. Breaking Down the Time Composition of Wireless Transmission Latency

The total latency T_total of a complete packet — from transmission by the TX-side MCU to completion of processing at the RX-side MCU — is the sum of four core time segments:
T_total = T_uart_tx + T_pack + T_air + T_uart_rx

Following the link order, the four components are:

UART transmission time (T_uart_tx / T_uart_rx): the time to move data between the MCU and the module's UART pins at the configured baud rate.
Packet-assembly delay (T_pack): when receiving the UART byte stream, the module firmware typically relies on a byte timeout to judge the end of a packet (e.g., no new input for 2–4 byte times is treated as packet completion).
Time on Air (T_air): the over-the-air RF modulation duration required for the RF chip to transmit the preamble, physical header, data payload and CRC.
Enter fullscreen mode Exit fullscreen mode
  1. Core Causes of High Communication Latency

Based on the link composition and field practice, the core causes of high latency concentrate in the following four areas.
2.1 Improper UART Baud Rate and Packing Timeout Settings

Many developers habitually keep a low 9600 bps UART baud rate. Taking a 100-byte transmission as an example:

At 9600 bps, one-way UART transfer alone takes 100 × 10 / 9600 ≈ 104 ms;
Accumulated on both TX and RX sides, pure UART time already exceeds 200 ms.
Enter fullscreen mode Exit fullscreen mode

In addition, some modules retain a long (e.g., tens of milliseconds) UART idle timeout by default for variable-length data compatibility, directly delaying the trigger point at which data is sent.
2.2 Air Data Rate Configured Too Low

In LoRa modulation, a high spreading factor (e.g., SF12) brings excellent sensitivity, but the spreading ratio greatly increases the per-symbol duration. Taking a single 64-byte packet as an example:

At a 2.4 kbps air rate, the time on air (T_air) including preamble is typically 250–350 ms;
Switching to a 62.5 kbps air rate, T_air needs only 10–20 ms.
Enter fullscreen mode Exit fullscreen mode

An overly conservative air-rate choice is the single largest physical factor causing long delays.
2.3 Channel Conflicts and Blind Retransmission

In point-to-multipoint or multi-master/multi-slave network topologies, if multiple nodes transmit on the same frequency without carrier sensing (LBT/CAD), radio collisions occur in the air, causing the receiver to drop packets directly on CRC errors. When the application layer times out waiting for an ACK, retransmission is triggered; retransmission waiting and backoff mechanisms degrade end-to-end latency by multiples.
2.4 Deep Sleep of Nodes and Wake-up Preamble Overhead (WOR Mechanism)

In systems using low-power radio wake-up (WOR, Wake On Radio), the receiver stays in a periodic sleep-listening state with a millisecond-level period. To ensure the receiver catches the signal when it wakes, the transmitter must first send a preamble longer than the receiver's sleep period (typically 500–2000 ms). This physical preamble duration is directly added to the first-packet latency of every communication.

  1. Engineering Optimization Strategies

For the above link bottlenecks, the following optimization strategies can be applied:
3.1 Optimize the UART Link: Faster Speed and Fixed-Length Packing

Increase the UART baud rate: within the limits of MCU capability and trace length, raising the baud rate from 9600 bps to 115200 bps or higher compresses the transfer time of a hundred-byte payload to under 10 ms.
Use hardware pins and fixed-length packets: if the module supports it, configure fixed-length triggering for packet assembly, or use the module's AUX/BUSY pin states for precise hardware triggering, eliminating the firmware's internal byte-idle timeout waiting.
Enter fullscreen mode Exit fullscreen mode

3.2 Fine-Match the Air Data Rate with the Link Budget

Do not apply the lowest air rate across the entire network indiscriminately.

Tiered tuning: for medium-short-range scenarios under 1 km, directly raising the air rate of modules such as the E22 series from 2.4 kbps to 9.6 kbps or 19.2 kbps cuts time on air by more than 70%.
Dynamic adaptation (ADR approach): use high rates for nearby nodes and low rates for far edge nodes, balancing coverage and overall throughput.
Enter fullscreen mode Exit fullscreen mode

3.3 Avoid Air-Time Congestion: Time-Division Scheduling and Data Trimming

Protocol lightweighting: streamline the application-layer payload, remove redundant fields, and use compact Hex/binary encoding instead of JSON or long strings to directly shorten time on air.
TDMA scheduling: the master station assigns communication time slots uniformly, and slave stations report in their own slots, avoiding blind collisions and retransmission storms.
Enter fullscreen mode Exit fullscreen mode

Conclusion

"Low latency" and "ultra-long range / ultra-low power" are inherently in tension due to physical laws. To solve module communication latency, you must measure segment by segment along the complete chain of "UART transfer → module packing → over-the-air modulation → protocol scheduling", and achieve low latency that meets the system's service boundaries by increasing the UART rate, raising the air data rate appropriately, and trimming the data frame length.
About EBYTE

Chengdu EBYTE Electronic Technology Co., Ltd. (EBYTE) is a high-tech enterprise integrating R&D, manufacturing and sales with a complete industry chain, focused on IoT communication applications. Its products cover a full range of communication equipment including LoRa, Sub-1G, Wi-Fi, Bluetooth, ZigBee, 4G, NB-IoT, GNSS satellite positioning, CAN bus modules, data radios, serial servers, industrial communication gateways, remote IO modules, industrial power supplies and antennas.

EBYTE uses imported original chips, high-quality capacitors and inductors, and industrial-grade high-precision crystal oscillators, delivering industrial-grade quality with excellent, stable and reliable performance. Its classic product lines — such as the E22 series built on the Semtech SX1262 — have obtained international authoritative certifications including FCC, CE and RoHS, and are exported to more than 50 countries and regions worldwide.

🌟 Tell us what you need. We'll send you the best deal

Shipping notice: For door-to-door / DDP service to the US, Canada, and Europe 👉 Shop on RobotShop

How to Order: 👉 Submit Your Request

🎓 Free Samples for University Students— University-Sponsorship Applications

Trial Modules at EBYTE

Top comments (0)