LoRa Module (SX1262, 868 MHz / 915 MHz)

Frequency Band Compliance: EU vs. US vs. China

LoRa deployments use different frequency bands depending on region, and each band has separate regulatory requirements:

EU 863–870 MHz (EU868). Governed by ETSI EN 300 220 and ETSI EN 303 446 (LoRaWAN-specific). CE/RED certification is mandatory for sale in EU/EEA markets. Duty cycle restrictions apply: most sub-bands are limited to 1% duty cycle (36 seconds on-air per hour). CE/RED testing must include frequency hopping and power level verification.

US 902–928 MHz (US915). Governed by FCC Part 15.247 (frequency hopping spread spectrum). FCC certification is mandatory. The US915 band allows up to +30 dBm EIRP for certain channel configurations, but most modules are certified to +20 dBm to reduce antenna gain requirements and simplify product integration.

China 470–510 MHz (CN470). SRRC (State Radio Regulation Committee) approval required. Not interoperable with EU868 or US915 networks. If you are designing a product for multiple markets, specify a dual-band or wideband module that covers both 868 and 915 MHz bands — several SX1262-based modules support 150–960 MHz with hardware filtering.

Never assume a CE/RED certified 868 MHz module can be sold in the US as-is, or vice versa. Confirm the specific FCC or CE test report for the exact module variant you are ordering.

LoRaWAN Stack Firmware Options

LoRa (the physical layer modulation) and LoRaWAN (the MAC layer network protocol) are separate. When sourcing modules:

Bare SX1262 module (no stack). The module provides only the SX1262 chip with SPI interface. Your MCU must implement LoRaWAN stack (typically via StackForce LMIC or Semtech LoRaMac-node library). Full control, but requires firmware engineering resources.

Module with integrated MCU + LoRaWAN stack. Modules like the Ebyte E22, RAK4630 (nRF52840 + SX1262), or HELTEC HT-M01 combine the SX1262 with a host MCU and pre-flashed LoRaWAN stack. AT command interface available. Faster to integrate, but less flexible for custom MAC layer behavior.

Pre-certified module with stack. Murata CMWX1ZZABZ (STM32L082 + SX1276), RAK Wireless RAK3172, and similar modules come with both radio and LoRaWAN certification. These simplify end-product regulatory approval but cost 30–60% more per unit.

Confirm the factory can supply firmware source code or provide a signed firmware update path if you need custom MAC layer modifications.

Gateway Integration Testing

A LoRa end node must be validated against the gateway hardware used in your target deployment:

• For The Things Network (TTN) / The Things Industries: test join procedure (OTAA) with a real TTN gateway, verify uplink/downlink at the intended spreading factor
• For private LoRaWAN networks: test against the specific network server (ChirpStack, Actility, Kerlink) your customer uses — ADR (Adaptive Data Rate) behavior varies by server implementation
• Class A, B, and C timing windows: confirm the module firmware correctly implements the 1-second (RX1) and 2-second (RX2) receive windows per LoRaWAN 1.0.3/1.1 spec

Request factory test fixtures that simulate gateway responses. A module that passes OTA join in a lab environment may fail in field conditions with high network load or marginal RF signal.

Common Issues

SX1262 vs. SX1276 confusion. SX1262 and SX1276 are not pin-compatible and have different SPI register maps. Confirm which chip generation is in the module — some factory listings label both as “LoRa module” interchangeably.

Antenna connector reliability. U.FL connectors on LoRa modules used in vibrating industrial environments (machinery, vehicles) can intermittently disconnect. Specify IPEX MHF4 connectors with a locking mechanism or switch to modules with integrated whip or PCB antennas for harsh environments.