] frederickdudley 忍者ブログ

How to Read RSSI on Wireless Modules: A Practical Engineering Guide


Reading RSSI Correctly: Confirm the Metric Definition First

RSSI represents the received signal strength. Its detection bandwidth, sampling instant and output format are determined by the chip implementation. A module may return a raw register value or a converted dBm figure — before reading, check the conversion formula, valid range and measurement accuracy in the manual.

dBm denotes absolute power relative to 1 mW, while dB denotes a power ratio or gain. For example, −60 dBm is 30 dB higher than −90 dBm, corresponding to 1000 times the power — but it does not mean the communication distance increases 1000 times.

In actual debugging, RSSI can be read via AT commands, driver APIs or registers supported by the module, while recording timestamps, channels and operating modes. Distinguish between real-time RSSI, per-packet RSSI and averaged RSSI, and avoid mixing them. If only successfully received packets are counted, failed samples during link fading may be missed.

Evaluating Signal Strength: Focus on the Receive Margin

There is no universal "excellent / acceptable / poor" boundary for RSSI across radio technologies. Receiver sensitivity varies with modulation scheme, bandwidth, data rate, coding and target packet error rate, so the specification corresponding to the current configuration should be used as the baseline.

The receive margin can be estimated with the following relation:

Receive Margin (dB) = Measured RSSI (dBm) − Receiver Sensitivity (dBm)

For example, if the sensitivity in a certain mode is −100 dBm and the measured received power is −85 dBm, the margin is about 15 dB. This result indicates that the current received power is above the specification threshold, but does not by itself constitute a reliability guarantee. Margin design should also account for measurement error, body blocking, multipath fading and installation differences. Pay attention to the time distribution of RSSI and its low-percentile values, not just the average; the required margin should be determined by field testing and service requirements.

Distinguishing Strength from Quality: Combine SNR and Interference Analysis

RSSI does not directly represent demodulation quality. Some measurement definitions include noise or interference power, so a rising reading may also come from increased environmental interference. SNR represents the power ratio of signal to noise. Under the same bandwidth and the same measurement reference, it can be written as:

SNR (dB) = Signal Power (dBm) − Noise Power (dBm)

When interference exists, SINR better describes the signal relative to interference and noise:

SINR (dB) = Signal Power (dBm) − (Noise + Interference Power) (dBm)

Do not substitute arbitrary RSSI readings directly into the above formulas. Prefer quality indicators provided by the chip with clear definitions; their usable thresholds also depend on the modulation and coding. For example, some LoRa modes allow reception at negative SNR, so a unified standard should not be applied.

Verifying Reliability: Define PER, Retransmission and Latency Criteria

The Packet Error Rate (PER) describes the proportion of packets not correctly received under specified receiving conditions; the service packet loss rate focuses on whether application data is delivered within the agreed time limit. The two may differ due to retransmission, buffering and protocol processing. During testing, use numbered packets, specify the number of transmissions, packet length, transmission interval and statistical window, and de-duplicate repeated packets. When retransmission is enabled, in addition to the final delivery rate, record the first-transmission success rate and the number of retransmissions to identify the resource overhead behind reliability. Also record effective throughput, round-trip latency, and P95/P99 latency. For one-way latency, a trusted clock synchronization condition is required. Acceptance thresholds should correspond to service requirements — "connection is normal" alone is not a valid basis.

Engineering Troubleshooting: Locating Problems with Correlated Data

When RSSI is low and packet errors increase, first check the receive margin, antenna installation, feeder loss and propagation blocking. When RSSI is high but packet errors remain high, further check co-channel interference, receiver overload, parameter mismatch and power supply stability. These phenomena only provide directions for troubleshooting and cannot alone determine the root cause. Testing should be divided into controlled-condition verification and field verification: the former fixes RF parameters and, when necessary, reduces input power step by step with an attenuator; the latter covers the farthest points, obstruction, movement and interference periods, verifying both uplink and downlink separately.

Whether a link is usable ultimately depends on whether the delivery rate, latency and throughput meet requirements under the specified scenario, duration and load. RSSI is used to explain link status; service data is used to verify the communication result.

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

PR

2026/11/17 LoRa wirelss modem Comment(0)

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.

2. 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.

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.

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.


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

2026/11/17 LoRa wirelss modem Comment(0)

How Does Co-Channel Interference Occur in Wireless Communication? Causes, Troubleshooting and Mitigation

Overview

Most engineers doing wireless development have encountered this scenario: the module tests perfectly in the lab, but on site it connects intermittently, the packet loss rate fluctuates, and switching to another channel "mysteriously" fixes it. In nine out of ten cases, the same invisible opponent stands behind it — co-channel interference.

How Co-Channel Interference Occurs

Radio waves in the air do not "recognize their owner". When two devices operating on the same frequency and channel transmit simultaneously, the receiving antenna picks up the vector superposition of both signals' energy. When the interference strength approaches or exceeds the desired signal, the receiver's demodulation threshold is raised and the error rate soars — this is the plain physical nature of co-channel interference.

There are three common sources. The first is other legitimate users within the band: on the 433MHz license-free band, metering terminals, remote controls and walkie-talkies all share the same "free road", and traffic jams naturally occur when there are too many vehicles. The second is improper self-networking planning: multiple networks in the same area using the same channel and address, or lacking a polling/scheduling mechanism, cause multiple nodes to "grab the microphone" at the same time. The third is the equipment's own electromagnetic leakage: broadband noise radiated by switching power supplies and motor brushes happens to fall within the receiving band, creating a situation of "our own people fighting our own people".

Another easily overlooked factor: most simple wireless modules lack "Listen Before Talk" (LBT) capability — they transmit without monitoring the channel first, so collisions are naturally unavoidable. Although spread-spectrum systems have strong interference resistance, they also fail when faced with sufficiently strong co-channel energy that "drowns" the spreading gain.

Common Troubleshooting Methods

The core idea of troubleshooting co-channel interference is: first prove that the problem lies in the air interface, then identify who the interferer is.

  1. Isolate the link factors. Separate the two modules with a shielded box or test them far apart. If communication becomes stable after shielding, air-interface interference can basically be confirmed; if the anomaly persists, first check the antenna, power supply and UART wiring — don't let interference take the blame.
  2. Look at the data, not feelings. Use the module's RSSI register or noise-floor readings for statistics: in a normal open environment, the 433MHz noise floor is generally below −110 dBm; if it routinely rises above −95 dBm, the air interface is "very busy". Recording packet loss rate over time is far more efficient than guesswork packet capture.
  3. Identify time-pattern features. Interference often has a "daily routine": park equipment starts and stops with working hours, and metering systems report concentrated on the hour. If packet loss clusters in specific periods, trace the devices active in those periods — following the time clue often hits the mark.
  4. Spectrum scanning for localization. When conditions allow, use a spectrum analyzer to observe band occupancy directly: stable full-height long packets usually come from continuously transmitting data radios, while regular short pulses may be remote controls or sensors. Without a spectrum analyzer, use the bisection method — power off suspicious devices in the area one by one and observe whether the noise floor drops sharply.

Common Mitigation Methods

  1. Plan frequencies first. When deploying multiple networks in the same area, stagger the channels and use the module's network ID and communication key for logical isolation, reducing "crashes" at the source.
  2. Trade spread spectrum for interference margin. The demodulation sensitivity of spread-spectrum modulations such as ChirpIoT and LoRa is far better than traditional narrowband FSK — at the same interference level, the desired signal can be demodulated even when "buried" much deeper. In essence, it trades data rate for reliability.
  3. Prefer lower air rates. Each step down in air data rate gains several dB of receiver sensitivity and a healthier link margin. For metering and remote-control scenarios with small data volumes, 2.4 kbps is often far more stable than 62.5 kbps.
  4. Mount the antenna properly. Raise the antenna as high as possible, away from metal obstructions and interference sources; if necessary, use a directional antenna to spatially avoid the interference direction. This move is often more effective than simply increasing transmit power — and it creates no new interference.
  5. Protocol-layer fallback. Enable ACK retransmission and packet-segment verification; under a master-slave architecture, let the central node schedule the transmit/receive timing uniformy to avoid multiple nodes transmitting simultaneously.

2026/11/17 LoRa wirelss modem Comment(0)

TI CC2652P Platform — E72-2G4M20S1E & Link72: Flagship Solutions for ZigBee 3.0 Self-Organizing Networks

Introduction

As ZigBee entered the 3.0 era, network scale and stability became the key measures of module capability. TI's CC2652P—a multi-function SoC with an integrated PA—provides strong support for large-scale self-organizing networks. EBYTE's E72-2G4M20S1E and Link72, built on this chip, are the representative products for ZigBee 3.0 mesh applications.

The Chip Core: What Is the CC2652P?

The CC2652P is a multi-function wireless SoC from TI's SimpleLink™ series, carrying a 48 MHz ARM Cortex-M4F processor with a built-in power amplifier (PA). It supports ZigBee, Thread, BLE, and other protocols. Its processing power and integrated PA give it clear advantages in network scale and communication range.

Product Overview

  • E72-2G4M20S1E: A multi-function SoC wireless module based on the CC2652P, with a high-performance low-power processor and multi-protocol support for broad industrial applications.
  • Link72 (E72-2G4M20S1E): A ZigBee 3.0 self-organizing wireless module on the same chip, with powerful networking capability as its core selling point.

Key Highlight: 200-Node Networking

Link72's most striking feature is support for up to 200 devices in one network—a high level among ZigBee solutions, capable of large smart homes, building automation, and industrial transport scenarios. The unified ZigBee 3.0 protocol also makes cross-vendor interoperability smoother.

Key Features

  • Based on TI CC2652P with 48 MHz ARM Cortex-M4F;
  • ZigBee 3.0 self-organizing network with strong self-healing;
  • Up to 200 devices per network;
  • High performance and low power for long-term operation;
  • Detailed hardware and software design guidance for reliable deployment.

Applications

Link72 and E72-2G4M20S1E fit whole-home smart networking, building automation (unified management of lighting, HVAC, security), and industrial transport (equipment coordination and condition monitoring). The 200-node capability gives them a clear edge in large-scale deployments.

Conclusion

With its integrated PA and strong processing power, the CC2652P platform provides a flagship hardware foundation for ZigBee 3.0 mesh networking. The E72-2G4M20S1E and Link72—anchored by 200-node networking—are ideal choices for large-scale IoT self-organizing applications.

Spring Promotion banner

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

2026/11/05 wireless communication Comment(0)

TI CC2640 Platform — E72-2G4M02S2B & E72-2G4M05S1B: A Tale of Two BLE Modules

Introduction

As Bluetooth Low Energy (BLE) spreads across wearables, smart homes, and industrial sensing, TI's CC2640 has become a core choice for many Bluetooth modules. Within EBYTE's E72-2G4M series, the E72-2G4M02S2B and E72-2G4M05S1B are two BLE 5.1 low-energy modules based on the CC2640, representing two distinct positions in the BLE product line.

The Chip Core: What Is the CC2640?

The CC2640 is an ultra-low-power wireless MCU from TI's SimpleLink™ series with a dual-core architecture: an ARM Cortex-M3 main core handles application processing while a Cortex-M0 RF core manages wireless control. This division of labor keeps power low while delivering solid compute capability. Supporting the BLE 5.1 protocol, it is an ideal core for Bluetooth IoT devices.

Product Comparison

FeatureE72-2G4M02S2BE72-2G4M05S1B
Core Chip CC2640 CC2640
Protocol BLE 5.1 BLE 5.1
Key Strengths Ultra-low power, multi-role functionality High-precision crystal, dual-core processor
Communication Interface Various command operations and configurations Multiple communication interfaces
Operating Voltage — 1.8–3.8 V
Band 2.4 GHz ISM 2.4 GHz ISM

E72-2G4M02S2B Highlights

This module is known for ultra-low power and multi-role functionality. It supports AT command configuration, letting users set up and manage parameters through simple commands. Its high-speed transmission suits real-time-sensitive scenarios, such as sensor data backhaul in smart homes.

E72-2G4M05S1B Highlights

This module emphasizes a high-precision crystal and dual-core processing, with a wide operating voltage of 1.8–3.8 V, good interference immunity, and stable communication. Its rich communication interfaces make integration with various MCUs and sensors easy.

Applications

Both modules serve smart homes, industrial sensors, security systems, and wearables. BLE 5.1's extended range and higher data rates make them strong performers in low-power, long-battery-life devices.

Conclusion

With its dual-core architecture and ultra-low-power design, the CC2640 platform lays a solid foundation for BLE IoT devices. The E72-2G4M02S2B (multi-role) and E72-2G4M05S1B (high-precision crystal) together form an important part of EBYTE's BLE product line.

Spring Promotion banner

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

2026/11/05 LoRa wirelss modem Comment(0)

プロフィール
 
性別:
非公開
 
 
カテゴリー
 
 
 
最新記事
 
(11/17)
(11/17)
(11/17)
(11/05)
(11/05)
 
 
RSS
 
 
 
リンク
 
 
 
P R