If you are using a LoRa module for point-to-point (P2P) communication or building your own private protocol, understanding and correctly configuring each parameter is the key to successful communication.

After reading this article, you will learn:

• How Should the LoRa Over-the-Air (PHY) Modulation and Packet Format Parameters Be Configured, and Why?

• The meaning of RF front-end parameters and how to tune them

• Chip-level control parameters: operating modes, clocks, power supply, calibration, and more

• A quick-reference "must-match" table and a list of common issues

Note: This article covers only LoRa (P2P/Private Protocol) parameters. If you need information on LoRaWAN protocol-layer parameters (e.g., ADR, DevEUI, join procedures), please refer to "LoRaWAN Protocol Layer Parameters".

Before starting configuration, verify that your device has selected PacketType = LoRa. The LR2021 supports multiple modulation types—including LoRa, LR-FHSS, FLRC, FSK/GFSK, OQPSK, and OOK. When using P2P LoRa communication, you must first switch to LoRa mode; all subsequent modulation and packet structure commands will then be interpreted in LoRa mode.

If you select the wrong PacketType (e.g., FLRC or GFSK mode), the chip will not interpret the SF, BW, and CR parameters in LoRa mode, The result is that the transmitted data cannot be decoded by the receiving end at all.

What Is the Air Interface?

"Air Interface" simply refers to the "language rules" that govern how signals are transmitted through the air.

Think of two people calling out to each other across a long distance. You need to agree not only on whether to speak Chinese or English (protocol type), but also on the speaking rate (data rate), how the tone changes (modulation method), and how to structure a sentence (packet format). All the conventions governing the entire path from the speaker's mouth to the listener's ear make up the "air interface".

In the context of LoRa, the air interface primarily refers to everything defined at the PHY (Physical Layer): modulation method (Chirp Spread Spectrum, CSS), spreading factor, bandwidth, coding rate, preamble format, and so on. For two devices to communicate, the air interface parameters must be a perfect match—just as two people must speak the same dialect at the same pace to understand each other.

What Is RF?

Radio Frequency (RF) refers to the range of electromagnetic wave frequencies suitable for wireless communication, typically from tens of kHz to hundreds of GHz.

If the "air interface" focuses on how signals are "encoded" and "packetizd", then "RF" focuses on how signals are "transmitted out" and "received back". This specifically includes:

• Carrier Frequency — the frequency band you operate on, such as 433 MHz, 868 MHz, or 2.4 GHz

• Transmit Power — how much the power amplifier is driven

• Receive Sensitivity — how the Low-Noise Amplifier (LNA) is configured

• Antenna Matching / RF Path — how the signal travels from the chip to the antenna

In short: the PHY layer controls "what is said" and "how it is encoded", while RF controls "how loud" and "through which speaker". Together, they form a complete wireless communication link.

For developers using G-NiceRF modules: If you are using an encapsulated module such as the LoRa2021 or LoRa2021F33-2G4, the RF circuitry (matching network, PA, LNA, antenna switch, etc.) has already been designed by the module manufacturer—you only need to configure the parameters via SPI. However, understanding the meaning of these parameters remains very important for debugging and troubleshooting.

PHY (Air Interface / LoRa Modulation and Packet Format) Parameters

This is the most critical part of the entire article. The PHY parameters determine whether two devices can successfully communicate with each other. Any mismatch in these parameters will lead to communication failure.

1. LoRa Core Modulation Parameters (BW / SF / CR / LDRO)

LoRa modulation is based on Chirp Spread Spectrum (CSS) technology. It has four core parameters:

(1) BW — Bandwidth

Bandwidth determines how wide the LoRa signal spreads across the frequency spectrum. Common options are 125 kHz, 250 kHz, and 500 kHz.

The LR2021 supports multiple bandwidth values in the Sub-GHz band, ranging from 7.8 kHz to 500 kHz. In the 2.4 GHz band, an even wider range of bandwidths is available.

The narrower the bandwidth, the better the receive sensitivity (the weaker the signal that can be detected), but the slower the transmission speed.

LR2021 Note: The LR2021 supports a frequency offset tolerance of up to ±33% of the bandwidth, whereas previous generations such as the LR1121 typically limit this to ±25% BW. This means that even with a slightly less accurate crystal oscillator, the LR2021 is less susceptible to packet loss than its predecessors.

(2) SF — Spreading Factor

The spreading factor defines how many chirps are used to encode each symbol. The typical LoRa configuration range is SF5 to SF12.

The lower the SF, the higher the data rate but the poorer the sensitivity; the higher the SF, the better the sensitivity but the lower the data rate. Compared to a lower SF, transmitting the same amount of data at a higher SF requires a longer time-on-air, which means the modem operates for longer and consumes more energy.

The duration of a single symbol in time is (2^SF) / BW. For example: at SF=7 and BW=125 kHz, one symbol takes approximately 1.02 ms; at SF=12 and BW=125 kHz, one symbol takes approximately 32.77 ms.

The LR2021 features a multi-spreading-factor receiver, low noise figure, improved CAD, and achieves the best LoRa sensitivity of −141.5 dBm at SF12/125 kHz. Compared to the SX1262, the Sub-GHz sensitivity is improved by 4.5 dB, which translates to a greater communication range under equivalent conditions in real-world use.

Key Point: Signals at different SFs are orthogonal—an SF7 node cannot receive an SF12 signal. Therefore, the SF must be identical on both transmitter and receiver.

(3) CR — Coding Rate

During LoRa communication, cyclic Forward Error Correction (FEC) is used internally. A portion of the data in each over-the-air packet is used for error-correction decoding. The ratio of the payload length to the total data length transmitted over the air is the coding rate.

LoRa supports four coding rates: 4/5, 4/6, 4/7, and 4/8. A larger denominator means more redundancy, stronger interference resistance, but a lower effective data rate.

The complete data rate formula is: DR = SF × (BW / 2^SF) × (4 / CR_denominator) bps

(4) LDRO — Low Data Rate Optimization

LDRO is often overlooked, but becomes critical when a single symbol duration exceeds approximately 16 ms. Enabling LDRO optimizes demodulation for long symbols and improves robustness in low-data-rate scenarios. Both the transmitter and receiver must have the same LDRO setting.

Determination method: T_symbol = 2^SF / BW. If the result is ≥ 16 ms, LDRO must be enabled. Examples:

• SF=12, BW=125 kHz → T_symbol ≈ 32.77 ms → Must be enabled

• SF=7, BW=125 kHz → T_symbol ≈ 1.02 ms → Not required

Summary: BW, SF, CR, and LDRO together define the communication "language". There is no universally "best" configuration—optimal performance always requires balancing communication range, payload size, power consumption, and the wireless environment. In LoRa mode on the LR2021, the data rate can reach up to 125 kbps, a significant improvement over the SX1262's 62.5 kbps.

2. Packet Structure Parameters

Modulation parameters govern "how to transmit a single symbol," while packet parameters govern "how to assemble many symbols into a data frame."

On the LR2021, LoRa packet parameters are configured via the SetPacketParams(...) command, which includes the following five fields: PreambleLength, HeaderType (explicit or implicit), PayloadLength, CrcMode (CRC enable/disable), and InvertIQ (IQ inversion).

(1) Preamble

The preamble is at the very beginning of a data frame, consisting of a series of consecutive basic up-chirps.

Its purpose is to allow the receiver to:

• Signal Detection: First determine that "someone is transmitting"

• Frequency / Time Synchronization: Align clock and frequency offset

• AGC Stabilization: Give the receive gain circuit time to settle to an appropriate level

The PreambleLength value indicates the number of symbols in the preamble (the hardware additionally appends a sync word and SFD section). A typical value is 8 symbols. A larger value makes it easier for the receiver to detect the signal (suitable for long-range or low-SNR scenarios), but also increases time-on-air.

Interoperability Requirement: The minimum preamble detection length at the receiver must be ≤ the preamble length configured at the transmitter. In general, configuring both ends with the same value works fine.

(2) Header Mode (Explicit / Implicit)

LoRa has two header modes:

• Explicit Header Mode: The default mode. A PHY Header is embedded in the packet. The Header is always transmitted with CR=4/8 and includes its own CRC. The receiver can read the payload length, coding rate, and CRC enable/disable status from the Header, without needing to know these parameters in advance.

• Implicit Header Mode: No Header is transmitted. Both transmitter and receiver must agree in advance on the payload length, CR, and CRC setting; otherwise, the receiver cannot correctly decode the packet.

When should implicit mode be used? When the data to be transmitted is very short (e.g., a few bytes of sensor values) and both ends have completely fixed parameters, you can omit the Header to save a small amount of time-on-air.

Interoperability Requirement: The Header mode must be identical on both ends. If one end uses explicit and the other uses implicit, packet decoding will fail.

(3) Payload Length

In explicit header mode, the Payload Length is automatically included in the Header and transmitted; the receiver parses it automatically.

In implicit header mode, both transmitter and receiver must manually configure the same length; otherwise, the receiver does not know how many bytes to read.

(4) CRC — Cyclic Redundancy Check

When enabled, the transmitter appends a 2-byte CRC checksum to the end of the payload. If the receiver's verification fails, the packet is flagged as a CRC error.

Strongly recommended: always enable CRC. Disabling CRC means you will not know if received data is corrupted.

Interoperability Requirement: The CRC setting must be identical on both ends. One end enabled and the other disabled will cause length parsing misalignment or false error reports.

(5) IQ Inversion

IQ inversion converts up-chirps into down-chirps (or vice versa). Its primary use is to differentiate the direction of uplink and downlink signals in LoRaWAN.

In P2P communication, both ends are typically configured with Standard IQ (no inversion).

Interoperability Requirement: IQ settings must match—unless you intentionally want to distinguish signals from different directions on each end.

3. What Information Does the Explicit Header Contain?

When using explicit header mode, the LoRa chip automatically inserts a PHY Header after the preamble and before the payload. It contains:

Field	Description
Payload Length	Number of bytes in this frame's payload
Coding Rate	The coding rate used for the payload
CRC Flag	Whether a CRC follows the payload

The preamble has no coding applied (since it is simply a series of up-chirps). The Header is always transmitted with CR=4/8.

Why does this affect interoperability? Because the receiver will first decode the Header using CR=4/8, and then use the CR value read from the Header to decode the subsequent payload. If BW and SF differ between the two ends, even the Header cannot be received, let alone the payload.

4. Network Identification and Synchronization (Sync Word)

At the end of the preamble, LoRa inserts several special chirp symbols to identify the "network identity"—this is the Sync Word.

The Sync Word is used to distinguish between different LoRa networks operating on the same frequency band. Any device configured with a specified Sync Word will discard incoming signals whose Sync Word does not match the defined value.

Sync Word formats across chip generations:

Network Type	SX127x / LR1121 / LR2021 (8-bit)	SX126x (16-bit)
Private Network	0x12	0x1424
Public Network (LoRaWAN)	0x34	0x3444

For P2P / private protocols, it is recommended to use 0x12 (LR2021 uses 8-bit format) to avoid interference with nearby LoRaWAN gateways.

Interoperability Requirement: Both ends must have the same Sync Word. If you need to interoperate with SX126x devices, configure the SX126x with the 16-bit standard value (0x1424/0x3444) and the LR2021 with the 8-bit standard value (0x12/0x34). The chip and official driver will handle the underlying conversion to ensure successful over-the-air communication.

5. CAD (Channel Activity Detection) Parameters

CAD (Channel Activity Detection) is a power-saving feature provided by LoRa chips for quickly detecting whether a LoRa signal is present on the current channel.

The LR2021's Fast CAD employs an intelligent adaptive threshold and early-termination mechanism, significantly reducing the power consumption and time required to detect an idle channel. This is a key improvement of the LR2021 over previous generations.

A typical CAD workflow:

1. The chip briefly activates the receiver and samples the signal over a number of symbol durations

2. It performs a correlation calculation on the sampled data to determine whether a LoRa preamble is present

3. It generates an interrupt to notify the MCU of the result (activity detected / not detected)

Key parameters include:

• cadSymbolNum: The number of symbols sampled per CAD operation (higher value = greater sensitivity, but longer duration)

• cadDetPeak / cadDetMin: Detection thresholds for adjusting the balance between sensitivity and false-alarm rate

• cadExitMode: Behavior after detecting a signal—can directly enter RX mode to receive, or simply generate an interrupt and return to standby

• cadTimeout: If no complete packet is received after entering RX, the timeout triggers an exit

The LR2021's Fast CAD feature enables "early termination"—if no signal is confirmed within the first few symbols, the chip can return to Sleep faster than traditional CAD, further saving power.

The most common CAD use cases include:

• Listen Before Talk (LBT): CAD is performed before transmitting; if the channel is occupied, wait before transmitting

• Power-Saving Listen: In scenarios that do not require continuous monitoring, periodic CAD replaces continuous RX to significantly reduce power consumption

RF (Radio Frequency / Analog Front-End) Parameters

Once the PHY parameters properly govern "how the digital signal is encoded," the RF parameters determine at what frequency and power the signal is transmitted from the antenna, and with what sensitivity it is received back.

1. Carrier Frequency and Channel Plan (RfFrequency / Channel Plan)

The carrier frequency is the center frequency occupied by the LoRa signal. The LR2021 is a true multi-band chip:

• LF port (Sub-GHz): 150 MHz – 960 MHz

• HF port: 2.4 GHz ISM band, L-band, and S-band satellite frequencies

• The LR2021 also natively supports the 1.9 GHz – 2.5 GHz band, enabling direct communication with Low Earth Orbit (LEO) satellites

Common terrestrial ISM (license-free) frequency bands:

• 433 MHz: China, parts of Asia

• 470 MHz: China

• 868 MHz: Europe (ETSI EN 300 220)

• 915 MHz: USA, Australia (FCC CFR 47 Part 15)

• 923 MHz: Southeast Asia, Japan

• 2.4 GHz: Global ISM band (newly supported by LR2021)

Important Reminder: The frequency you use must comply with the radio regulations of the country/region where the device is deployed. Like all devices using unlicensed ISM spectrum, the LR2021 must comply with regional spectrum access and usage restrictions, which typically include operating frequency band, maximum effective radiated power, and channel access (duty cycle). Interoperability Requirement: The frequency must be exactly identical on both ends.

2. Transmit Chain (TX RF)

(1) Transmit Power

The LR2021 has a transmit power range of +22 dBm to −10 dBm, with excellent energy efficiency.

Higher power → longer range → but faster battery drain, and may exceed regulatory limits. In practice, select an appropriate power level based on communication range requirements and regulatory limits.

High-Power Module Selection: If the standard +22 dBm is insufficient for your range requirements, consider the LoRa2021F33-2G4. This is a 2W high-power, high-data-rate multi-band wireless communication module based on the LR2021. It outputs 2W in Sub-GHz and 1W at 2.4 GHz, with an integrated FEM (PA+LNA). It is suitable for scenarios requiring ultra-long range coverage or penetration in challenging environments.

(2) PA Path Configuration

The power amplifier architecture of the LR2021 differs significantly from the SX1262. The LR2021 has independent Low-Frequency Power Amplifiers (PA LF) and High-Frequency Power Amplifiers (PA HF):

• PA LF: For the Sub-GHz band (150–960 MHz), up to +22 dBm

• PA HF: For the 2.4 GHz band, operating around 2445 MHz as shown in the datasheet

The LR2021's high performance is achieved under a simpler Direct-Tie architecture—indicating that the PA output can be directly connected to the antenna matching network without requiring an external RF switch.

PA configuration allows users to optimize for a specific output power and matching network. However, incorrect values may prevent the target output power from being achieved or may even damage the device.

(3) PA Ramp Time

The PA ramp time refers to the transition time for the power amplifier to go from off to reaching the target power. The LR2021's set_tx_params command can configure both power and RampTime (e.g., Ramp8u). Too fast causes spurious emissions (spectral leakage); too slow wastes preamble time. Generally, the default value is sufficient.

(4) Over-Current Protection (OCP)

OCP (Over Current Protection) prevents the PA from burning out the chip under extreme conditions (e.g., severe antenna mismatch). The LR2021 provides this protection mechanism.

3. Receive Chain (RX RF)

The RX RF is the RF receive path from the antenna to the chip's internal demodulator, responsible for amplifying and processing received signals.

The LR2021 features a multi-spreading-factor receiver, low noise figure, improved CAD, and achieves the best LoRa sensitivity of −141.5 dBm at SF12/125 kHz.

For most applications, the receive gain does not need to be manually adjusted—the chip's AGC (Automatic Gain Control) will automatically adjust the gain based on signal strength.

4. RF Front-End and Antenna / RF Path

The RF front-end is the circuit path between the chip and the antenna responsible for transmitting and receiving RF signals. It determines how the signal travels from the chip to the antenna and back.

The most significant change in the LR2021's RF front-end design is the adoption of a Direct-Tie architecture, which allows transmit and receive operations to share the same antenna port without requiring an external TX/RX RF switch.

Traditional designs (such as the SX1262) typically require an external RF switch to alternate between TX and RX, with some designs also requiring DIO2 to control the switch. The LR2021's front-end design is simpler, reducing component count, lowering insertion loss, and supporting a single front-end layout across multiple regions.

5. RF Testing and Regulatory Compliance

During product development and certification, the following test modes are commonly used:

• Continuous Wave (CW) Mode: The chip continuously outputs an unmodulated carrier signal, used to measure frequency accuracy and output power

• Continuous Preamble Mode: Continuously transmits preamble chirps, used to debug receive sensitivity

The LR2021 has better phase noise performance than the LR1121. When meeting stringent regional regulations such as Japan's ARIB standard, it is no longer necessary to reduce transmit power or add expensive filters as was previously required.

EIRP (Equivalent Isotropically Radiated Power) must comply with local regulations. For example, the EU 868 MHz band typically limits ERP to ≤ 14 dBm (approximately EIRP 16.15 dBm), and the US 915 MHz band limits EIRP to ≤ 30 dBm (with frequency hopping).

Radio Control and Power Parameters (Clock / Power / State Machine / Calibration)

The parameters in this section do not directly affect whether over-the-air communication succeeds, but they determine whether your device can conserve power, avoid unexpected dropouts, and whether calibration has been properly performed.

1. Operating Modes and State Machine

The LR2021's state machine is similar to the SX126x / LR1121 series. The main modes include:

Mode	Description	Notes
Sleep	Lowest power consumption; most circuits powered off	Sleep current of the G-NiceRF LoRa2021 module is no more than 2 μA
Standby_RC	RC oscillator running; configurable via SPI	Default mode after power-on reset
Standby_XOSC	High-accuracy crystal oscillator running	Slightly higher current than Standby_RC
FS	Frequency synthesizer active; PLL locked	Ready to transmit/receive
TX	Transmitting	Current depends on power level and frequency band
RX	Receiving	LR2021 features optimized low-power receive
RX_DC	Periodic receive (Duty Cycle)	Average current far lower than continuous RX

2. Timeout and Wait Strategies

TX Timeout

Transmit timeout: if transmission has not completed within the specified time (e.g., if the PLL fails to lock), the chip triggers a timeout interrupt. Typically, setting this to a few seconds is sufficient.

RX Timeout

An RX operation can automatically terminate after receiving one packet, be configured as duty-cycle mode, or run indefinitely, depending on application requirements. Specifically:

• In single-reception mode, the device automatically returns to the configured mode (Standby RC by default) after receiving a packet

• In single-reception mode with timeout, the device automatically returns after receiving a packet or after the given timeout expires

• In continuous mode, the device remains in RX until the host requests a mode switch

Symbol Timeout (LoRa Symbol Timeout)

This parameter means: after the chip detects the preamble, if no valid Header or data is received within the specified number of symbols, the current receive attempt is abandoned. Setting it too short reduces sensitivity; setting it too long wastes power.

3. Duty-Cycled RX (RxDutyCycle / Periodic Listen)

When your device does not need to constantly "listen" for messages, RxDutyCycle is a highly power-efficient alternative.

How it works: The chip periodically switches between Sleep and RX. During each cycle, the chip briefly enters RX to perform a CAD-like detection. If a preamble is detected, it continues to receive the complete packet; otherwise, it immediately returns to Sleep.

In RX Duty Cycle mode, the device periodically enters RX mode to receive packets, then returns to Sleep mode.

Key parameters:

• rxPeriod: Duration of the RX phase in each cycle

• sleepPeriod: Duration of the Sleep phase in each cycle

These two timings need to be coordinated with the transmitter's preamble length: the transmitter's preamble must be long enough to guarantee that the receiver "wakes up" at least once during the sleepPeriod and can see the preamble.

4. Post-TX/RX Fallback Mode (RxTxFallbackMode)

SetRxTxFallbackMode defines which mode the chip returns to after successfully transmitting or receiving a packet.

Available options typically include:

• Return to Standby_RC (default)

• Return to Standby_XOSC

• Return to FS

If you need to immediately transmit or receive again, returning to FS saves the time needed for the PLL to re-lock; if you want to conserve as much power as possible, return to Standby_RC.

5. Clock System (XTAL / TCXO)

The LR2021 supports two high-accuracy clock sources:

• XTAL (Crystal Oscillator): Lower cost, moderate accuracy (more susceptible to temperature variations)

• TCXO (Temperature-Compensated Crystal Oscillator): Higher accuracy and better temperature stability, but higher cost

However, the LR2021 features a noteworthy improvement in the clock domain: the increased frequency offset tolerance means that a TCXO and large heatsink design are no longer mandatory. In other words, in many scenarios, a standard XTAL is sufficient, and the strong dependence on TCXO seen with the SX1262 is no longer required.

For extreme temperature environments or narrow-bandwidth applications, using a TCXO is still recommended to ensure frequency stability.

6. Power Supply and Regulation Strategy (SIMO / LDO)

One of the most significant differences between the LR2021 and its predecessors is the upgraded power management architecture:

The LR2021 chip integrates a high-efficiency SIMO DC-DC converter, eliminating the need for an external power management IC. SIMO (Single-Inductor Multiple-Output) is a more advanced DC-DC topology that can generate multiple output voltages from a single inductor simultaneously, further reducing BOM cost and PCB area.

• SIMO (Recommended): Higher efficiency and lower power consumption; the preferred power supply solution for the LR2021

• LDO: Simpler circuit but lower efficiency; typically used only when the external inductor required by SIMO is unavailable

7. Calibration and Error Handling

The LR2021 provides a comprehensive calibration mechanism. Modules typically calibrate the RC oscillator, PLL, ADC, image rejection, and more.

The LR2021 initialization flow includes a front-end calibration step, calib_fe. Calibration is generally executed once during power-on initialization. If a sudden increase in CRC error rate or a significant frequency offset is observed during operation, re-triggering calibration is worth considering.

8. Interrupt and Event Mapping (IRQ)

The LR2021 uses interrupts to notify the MCU of various events. Based on code examples, the LR2021's DIO pins can be mapped to multiple interrupt events. Common ones include: TX_DONE, RX_DONE, PREAMBLE_DETECTED, HEADER_VALID / HEADER_ERROR, CRC_ERROR, CAD_DONE, CAD_ACTIVITY_DETECTED, TIMEOUT, and others.

In addition, the LR2021 adds Ranging-related interrupt types such as RNG_EXCH_VLD, RNG_RESP_DONE, RNG_REQ_DIS, and RNG_TIMEOUT—these are part of the extended ranging functionality newly added in the LR2021.

Proper interrupt configuration avoids polling and reduces MCU power consumption.

Parameter Quick Reference

"Must-Match" Parameter Table (Both Ends Must Be Identical)

If the following parameters differ between the transmitter and receiver, communication will inevitably fail or produce errors:

Parameter	Description	Consequence of Mismatch
Frequency	Carrier frequency (including band selection)	Complete communication failure
BW	Bandwidth	Complete communication failure
SF	Spreading Factor	Complete communication failure (different SFs are orthogonal)
CR	Coding Rate	In explicit header mode, Header may decode but Payload decoding fails; in implicit mode, complete failure
LDRO	Low Data Rate Optimization	Symbol demodulation failure
Sync Word	Sync Word (LR2021 uses 8-bit format)	Receiver discards packets
Header Mode	Explicit / Implicit	Receiver fails to decode packets
Payload Length (implicit header)	Effective payload length	Receiver reads incorrect data length
CRC	CRC enable/disable	Length or checksum errors
IQ Inversion	IQ inversion setting	Complete communication failure
Preamble Length	Preamble length	If too short, receiver cannot synchronize
PacketType	Modulation type (LoRa / FLRC / FSK...)	Complete communication failure

Special Note: Since multiple modulation types exist (LoRa, FLRC, FSK, etc.), confirming that both ends have matching PacketType is the very first step. If one end uses LoRa and the other uses FLRC, communication is impossible.

"Range / Rate / Power" Three-Objective Recommended Configurations

The following recommended configurations are based on the performance characteristics of the LR2021 (Sub-GHz LoRa mode):

Scenario	SF	BW	CR	LDRO	TX Power	Characteristics
Long Range	12	125 kHz	4/8	ON	+22 dBm	Sensitivity −141.5 dBm; lowest rate; very long time-on-air
Balanced	9	125 kHz	4/5	OFF	+14 dBm	Suitable for most IoT scenarios; moderate range
LoRa High-Speed	7	500 kHz	4/5	OFF	+14 dBm	Leverages the LR2021's LoRa 125 kbps upper limit
Low Power	7	125 kHz	4/5	OFF	+2 dBm	Used with RxDutyCycle; suitable for battery-powered sensors

If you need a higher data rate (e.g., image or audio transmission), the LR2021's FLRC mode can achieve up to 2.6 Mbps in Sub-GHz. G-NiceRF conducted field testing at Shenzhen OH Bay, starting near the Ferris wheel and performing range testing across the Qianhai Bay. For detailed data, please refer to: LoRa2021 Module Real-World Range and PDR Test Report (FLRC vs LoRa).

If you want a comprehensive understanding of how power consumption influences LoRa module selection, refer to: How to Choose the Right LoRa Module Based on Power Consumption.

Common Issues Checklist

Issue	Cause & Solution
Both ends cannot receive each other at all	Check that frequency, BW, SF, and PacketType are consistent; check Sync Word; confirm antenna is connected and the correct frequency-band port (LF / HF) is selected
Signal is received but all CRC errors	Check that CR, CRC enable/disable, and IQ inversion settings are consistent; investigate frequency offset issues
Garbled data in implicit header mode	Confirm that Payload Length, CR, and CRC settings are exactly the same on both ends
Frequency not compliant, regulatory issues	Confirm ISM band regulations for the deployment country; pay attention to EIRP limits and duty cycle restrictions
Severe packet loss at long range / high SF	Confirm LDRO is enabled; increase preamble length; check frequency offset (LR2021 has better tolerance, but still requires attention)
Packet loss during RxDutyCycle	Confirm that the transmitter's preamble length ≥ 2 × (sleepPeriod / symbol_time) + margin
High power consumption	Confirm SIMO is used instead of LDO; check whether RX or XOSC remains active when not needed
Can SX1262 and LR2021 interoperate?	Yes. As long as both ends have PacketType = LoRa and all PHY parameters are consistent. Note the Sync Word format (both use 16-bit)
Insufficient range at 2.4 GHz	2.4 GHz has higher propagation loss than Sub-GHz; at equal power, range is shorter. Try increasing SF or switching to Sub-GHz

LoRa Module Selection

If you are still in the selection phase and unsure which LoRa module to use, you can browse G-NiceRF's LoRa module product line (with datasheets and example code), or contact customer support directly for more comprehensive information.

FAQ

Q1: Can the LR2021 interoperate with SX1262 / LR1121?

Yes. The LR2021 is designed to be backward-compatible with earlier LoRa devices, ensuring seamless LoRaWAN compatibility. In P2P LoRa mode, as long as both ends have PacketType = LoRa and the BW, SF, CR, LDRO, Sync Word, frequency, and other parameters are perfectly matched, interoperation is possible. Note that SX127x / LR1121 / LR2021 all use the 8-bit Sync Word format and are mutually compatible; if interoperating with SX126x, the Sync Word format must be correctly configured.

Related Reading: Semtech LoRa Chip Comparison and Upgrade Guide (SX1276 / SX1262 / LR1121 / LR2021)

Q2: How do I choose between LR2021's FLRC mode and LoRa mode?

The LR2021 integrates LoRa, FLRC, and other modulation protocols, providing developers with excellent communication system engineering flexibility. A simple selection principle:

• Need maximum range and lowest power consumption (typical IoT sensors): use LoRa mode

• Need higher data rate (images, audio, OTA upgrades, within 1.8 km range): use FLRC mode

• FLRC offers higher bandwidth/throughput, supporting image transmission, voice segment upload, and larger payload updates

Q3: How do I choose SF, BW, and CR?

Simple rules of thumb:

• Longer range → Increase SF, decrease BW

• Higher speed → Decrease SF, increase BW

• Better interference resistance → Increase CR

• Lower power consumption → Use lower SF with an appropriate TX power level

Q4: What is the appropriate Preamble length?

LoRaWAN defaults to 8 symbols. In P2P communication without RxDutyCycle, 8 symbols is also sufficient. If using periodic listening, the preamble must be extended based on the sleep period to ensure the receiver can see enough preamble when it "wakes up" during sleep.

Q5: When should I use implicit header mode vs. explicit header mode?

• Explicit Header (Default Recommended): Flexible; the receiver automatically learns the payload length and CR. Suitable for most scenarios.

• Implicit Header: Saves a few symbols of time-on-air. Suitable for scenarios where the payload length is fixed and power/speed savings are critical. When using implicit header, any parameter change must be synchronized on both ends.

Q6: Does the LR2021 still require a TCXO?

The increased frequency offset tolerance of the LR2021 means that a TCXO and large heatsink design are no longer mandatory. For most scenarios, a standard XTAL is sufficient. However, if your deployment environment experiences extreme temperature variations or uses very narrow bandwidth, a TCXO remains the safer choice.

Q7: Should I use SIMO or LDO for the LR2021?

Prefer SIMO. The LR2021 integrates a high-efficiency SIMO DC-DC converter with higher efficiency and lower power consumption. Only fall back to LDO when there is insufficient PCB space for the inductor required by SIMO.

Q8: Is IQ inversion necessary in P2P communication?

Generally not. Both ends should use Standard IQ. IQ inversion is primarily used by LoRaWAN to distinguish uplink from downlink. If your P2P system needs to differentiate "signals from the base station" from "signals from the terminal," you can configure one end with Standard and the other with Inverted.

Q9: Can the LR2021's 2.4 GHz LoRa and Sub-GHz LoRa interoperate?

No. They operate on completely different frequencies, and the RF paths are also different (LF vs HF port). Even with identical modulation parameters, a frequency mismatch prevents reception.

Q10: What is the LR2021's Extended Ranging feature?

This is a new cLoRa Module (P2P Private Protocol) Parametersapability of the LR2021. The LR2021 introduces a new extended ranging variant that performs a second exchange (using a different chirp configuration), which can eliminate the frequency bias offset caused by device motion speed or temperature changes. This not only improves ranging accuracy but also provides relative velocity estimation. If your P2P application has ranging requirements, this is a noteworthy new capability.

Q11: Can I customize the Sync Word to distinguish multiple P2P networks?

Theoretically yes, but in LoRa, 0x1424 (private) and 0x3444 (public) are the two values that produce the greatest discrimination. Using other values may increase false positives. If you genuinely need to distinguish multiple networks, a better approach is to use different frequencies or add a network ID field at the payload level for software-based filtering.

Products and purchases:

1. G-NiceRF® Lora2021 Product Page: https://www.nicerf.com/lora-module/lora2021.html

2.G-NiceRF® Lora2021F33-2G4 Product Page: https://www.nicerf.com/lora-module/lora2021f33-2g4.html

3. Official G-NiceRF® store (AliExpress): https://aliexpress.ru/item/1005010632473860.html?gatewayAdapt=glo2rus&sku\_id=12000053034776653