Understanding LoRa Hardware Deep-dive technical reference on MCU platforms, frequency bands, antenna types, and GPS integration for LoRa mesh nodes. ESP32 vs nRF52840: Which Platform? Two microcontroller platforms dominate the LoRa mesh hardware landscape: Espressif's ESP32 family and Nordic Semiconductor's nRF52840 . Both are capable, both are well-supported by Meshtastic and MeshCore firmware, and both pair with the SX1262 radio. But they are optimized for fundamentally different use cases, and choosing the wrong one has real consequences. Platform Comparison at a Glance Feature ESP32 / ESP32-S3 nRF52840 Manufacturer Espressif Systems Nordic Semiconductor CPU cores Dual-core Xtensa LX6/LX7 (ESP32-S3) Single-core ARM Cortex-M4F CPU speed 240 MHz 64 MHz RAM 512 KB SRAM (+ external PSRAM on some boards) 256 KB SRAM Flash Typically 4 - 16 MB (external) 1 MB internal (+ optional external) WiFi Yes (2.4 GHz 802.11 b/g/n) No Bluetooth BLE 5.0 BLE 5.0 + Bluetooth Mesh Active current (typical) 80 - 240 mA 10 - 20 mA Deep sleep current 10 - 150 µA (varies by variant) 1.9 - 8 µA Supply voltage 3.0 - 3.6V 1.7 - 5.5V (natively tolerant) Operating temp range -40°C to +85°C (commercial grade varies) -40°C to +85°C Hardware crypto AES accelerator, SHA accelerator ARM TrustZone + hardware crypto engine USB native Yes (ESP32-S3, -S2, -C3) Yes Power Consumption: The Real Numbers For battery-powered mesh nodes, power consumption is frequently the deciding factor. Here are measured averages for a LoRa mesh node in active listening mode (radio on, MCU active, no WiFi): Condition ESP32-S3 nRF52840 Factor Difference Active (CPU + radio RX) 80 - 120 mA 15 - 20 mA nRF52840 uses ~5 - 6x less Light sleep (radio on) 2 - 5 mA 0.5 - 1 mA nRF52840 uses ~4x less Deep sleep (radio off) 10 - 100 µA 1.9 - 8 µA nRF52840 uses ~5 - 50x less Transmit (100 mW / +20 dBm) ~400 - 500 mA peak ~350 - 400 mA peak Similar (dominated by PA current) Practical implication: A node that spends 95% of its time in light sleep will consume roughly 3 - 5 mA on ESP32-S3 vs 0.6 - 1 mA on nRF52840. On a 2000 mAh 18650 cell, that is: ESP32-S3: ~400 - 650 hours (~17 - 27 days) nRF52840: ~2000 - 3300 hours (~83 - 137 days) This 4 - 5x difference is why nRF52840 is the correct choice for battery-powered or solar nodes, and the ESP32 is acceptable only when AC power is available. Sleep Modes Explained ESP32 Sleep Modes Active: Full operation, both cores running, radio on Modem sleep: WiFi/BT radio off, CPU running - not useful for mesh nodes since the LoRa radio is external Light sleep: CPUs paused, memory retained, peripheral clocks gated. ~0.8 mA total system (good for ESP32-S3 with LoRa radio in sleep) Deep sleep: Most of chip off, only RTC domain active. ~10 - 150 µA depending on wakeup configuration Hibernation: Only RTC timer active. ~5 µA but loses GPIO state Key limitation: the ESP32's sleep modes interact poorly with external peripherals. Bringing WiFi up from deep sleep takes 200 - 400 ms - during which messages can be missed. nRF52840 Sleep Modes System On (active): Full operation, up to 64 MHz CPU System On (idle): CPU halted, peripherals running - ~1 - 3 mA System On (low power): Aggressive clock gating - ~0.5 - 1 mA System Off: Only GPIO wakeup retained - ~1.9 µA typical The nRF52840's architecture allows the BLE radio and application code to be active simultaneously in time-division, with very efficient power management built into the SoftDevice BLE stack. WiFi: ESP32's Biggest Advantage The ESP32's integrated 802.11 WiFi is a genuine capability that the nRF52840 lacks entirely. This matters for: MQTT bridging: An ESP32 node can connect directly to a WiFi network and forward mesh messages to an MQTT broker without any additional hardware OTA firmware updates: WiFi-based OTA is reliable and convenient; no cable required Web configuration interface: Meshtastic's web UI is served over WiFi from the node itself NTP time sync: WiFi-enabled nodes can sync accurate time without GPS If your deployment scenario requires WiFi connectivity from the node itself - for example, a Meshtastic MQTT gateway or a node that serves as both a mesh device and a WiFi access point - the ESP32 is the better choice. BLE Capabilities Both platforms support BLE 5.0 and use it for phone-to-node configuration and message viewing via the Meshtastic and MeshCore apps. In practice, BLE performance is similar between the platforms. The nRF52840 additionally supports Bluetooth Mesh natively, but this is not used in current Meshtastic/MeshCore deployments. Community and Software Support Criterion ESP32 nRF52840 Meshtastic support Excellent - most boards are ESP32 Excellent - RAK4631, T-Echo, Station G2 all supported MeshCore support Good - T-Beam Supreme, Heltec V3 supported Excellent - RAK4631 is the primary MeshCore platform Community size Larger overall (ESP32 dominates maker ecosystem) Smaller but highly technical Documentation quality Extensive (Arduino, ESP-IDF, PlatformIO) Good (Zephyr RTOS, Nordic SDK, Arduino) Custom firmware development Easier (Arduino IDE widely used) Requires more expertise (Zephyr preferred) Decision Guide Use Case Recommended Platform Reason Solar or battery repeater nRF52840 4 - 5x better battery life is decisive Portable handheld (multi-day) nRF52840 Extended field battery life WiFi-connected gateway ESP32 Only platform with integrated WiFi Mains-powered room server ESP32 or Pi Power draw irrelevant; WiFi useful First node / beginner ESP32 More tutorials, more community support, cheaper Secure or production mesh nRF52840 ARM TrustZone hardware security Frequency Bands Explained Frequency Bands Explained: 915 MHz vs 868 MHz vs 433 MHz The single most common source of frustration for new LoRa mesh users - and the most easily avoided - is buying hardware on the wrong frequency band. A 868 MHz device purchased on AliExpress will not communicate with any 915 MHz nodes in a North American mesh network. This page explains the regulatory framework, how to identify what band your hardware is on, and why the problem occurs so frequently. Regional Frequency Band Reference Region Correct Band Frequency Range Regulatory Body Max Power (EIRP) United States 915 MHz 902 - 928 MHz FCC (Part 15, Subpart C) 30 dBm (1W) Canada 915 MHz 902 - 928 MHz ISED (RSS-210) 30 dBm Mexico 915 MHz 902 - 928 MHz IFT 30 dBm Brazil 915 MHz 902 - 928 MHz ANATEL 30 dBm Australia / New Zealand 915 MHz 915 - 928 MHz ACMA / RSM 30 dBm European Union 868 MHz 863 - 870 MHz ETSI (EN 300 220) 27 dBm (500 mW); duty cycle limits apply United Kingdom 868 MHz 863 - 870 MHz Ofcom (IR 2030) 27 dBm India 865 MHz 865 - 867 MHz DoT / WPC 27 dBm China (mainland) 470 MHz or 779 MHz 470 - 510 MHz / 779 - 787 MHz MIIT 50 mW Japan 920 MHz 920 - 928 MHz MIC 20 mW Korea 920 MHz 920 - 923 MHz NIA 10 mW Why You CANNOT Use EU Hardware on a US Network This is not a software restriction - it is a physical hardware limitation. Here is what happens: The SX1262 radio chip itself can technically tune to a very wide frequency range. However, the matching network (a set of inductors and capacitors) on the PCB between the chip and the antenna is designed and tuned at manufacture for a specific frequency band. A board built for 868 MHz has its antenna matching network optimized for 868 MHz. If you configure the firmware to transmit at 915 MHz, the mismatch between the matching network and the actual operating frequency results in: Significantly reduced transmit power (energy reflected back into the chip rather than radiated) Significantly reduced receiver sensitivity (the band-pass filter rejects the in-band signal) Possible damage to the PA (power amplifier) from reflected power over time In practice, a 868 MHz board configured for 915 MHz operation will transmit at substantially reduced power and may receive at −20 to −30 dB below specification. It effectively will not communicate reliably with other nodes. Additionally: Transmitting on a frequency outside your regional allocation is a regulatory violation. In the US, operating on 868 MHz with a standard LoRa node is not authorized by the FCC, and operating on 915 MHz with a CE-marked 868 MHz device violates its CE certification. Why AliExpress Listings Default to 868 MHz Most LoRa hardware manufacturers are based in China. Their largest international markets are the EU and UK, where 868 MHz is the standard band. When a generic AliExpress seller lists "LoRa32 development board" without a clear frequency specification, it is almost always 868 MHz because: 868 MHz is the more common export configuration for the European market Many sellers do not understand the regional band requirements and list boards without specifying frequency Products are often labeled simply "LoRa" with no frequency mentioned - defaulting to whatever batch was ordered (often 868 MHz) The price difference between 868 and 915 MHz versions is typically zero, so sellers don't bother distinguishing The rule: If the listing does not explicitly say "915MHz" or "915M", assume it is 868 MHz and do not buy it for North American use. How to Identify Your Hardware's Frequency Band Before Buying Check the product title for "915MHz", "915M", "US915", or "AU915" Check the product description for frequency specification Look at photos of the PCB - many boards have the frequency printed on the silkscreen near the antenna connector Check the seller's other listings - if they sell both 868 and 915 versions, make sure you selected the right one After Receiving PCB silkscreen: Look near the SMA/U.FL connector or on the module itself. Common markings: "915", "868", "433", or a product code like "SX1262-915" or "RAK4631-R". Module label: On RAK WisBlock modules, the part number suffix indicates band: "R" suffix = 915 MHz (e.g., RAK4631-R) Firmware frequency: If the device has already been flashed, connect via serial or BLE and check the configured region. In Meshtastic: Radio Config → LoRa → Region. The configured region should be US (or AU for Australia) for 915 MHz operation. RF spectrum verification (advanced): Using an RTL-SDR or similar receiver, you can observe the actual transmit frequency when the node sends a packet. This is the definitive test. The 433 MHz Band A third band - 433 MHz - is used in some regions (parts of Asia and occasionally Europe for specific applications). For North American community mesh networking, 433 MHz is not used. If you accidentally purchase a 433 MHz board, it is completely unusable in a 915 MHz mesh network - not just degraded, but transmitting and receiving on an entirely different part of the spectrum. Additionally, 433 MHz requires a physically larger antenna (approximately 17 cm for a quarter-wave whip vs 8 cm for 915 MHz). Frequency Band Identification Quick Reference What You See Interpretation US/Canada Compatible? "915MHz", "915M", "US915", "AU915" Correct band for North America/Australia Yes "868MHz", "868M", "EU868", "IN865" European band - wrong for North America No "433MHz", "433M", "AS433" Asian 433 MHz band - wrong everywhere for mesh No No frequency mentioned Assume 868 MHz unless confirmed otherwise Assume No - verify first RAK4631-R RAK notation: "-R" suffix = 915 MHz Yes RAK4631 (no suffix) RAK notation: no suffix = 868 MHz No PCB Trace vs External Antenna The antenna is the component that most dramatically affects the range and reliability of a LoRa mesh node - more than spreading factor, transmit power, or even the radio chip. Yet it is also the most commonly overlooked hardware detail, especially by beginners who assume the built-in PCB trace antenna is adequate for outdoor use. PCB Trace Antennas: What They Are A PCB trace antenna (also called a PCB antenna or on-board antenna) is a specific pattern etched directly into the copper layers of the circuit board. No separate component - it is part of the PCB itself. You can identify one by looking at a corner of the board where the copper traces form a meandered or serpentine pattern, often with a small keepout area around it where no other copper is present. PCB trace antennas are used because they cost essentially nothing to add during PCB manufacturing, they take up minimal volume, and they eliminate the need for an SMA/U.FL connector and cable. For products designed to be small and cheap - like the Heltec V3 or many ESP32 dev boards - they make sense as a baseline. Why PCB Antennas Are Inadequate for Outdoor Use The theoretical gain of a well-designed PCB trace antenna at 915 MHz is approximately 0 - 2 dBi - comparable to a short rubber duck. However, in practice, PCB antennas on development boards suffer from several additional problems: Proximity effects: A PCB trace antenna's tuning is affected by everything near it - your hand, a battery, the case material, the board itself. Moving the device changes the antenna's effective frequency and radiation pattern. Orientation sensitivity: PCB trace antennas typically have a highly directional radiation pattern. In a pocket or on a table, the null direction may be exactly toward the nodes you want to reach. No replaceable component: If the PCB trace antenna design is suboptimal (common on cheap dev boards), there is nothing to improve without adding an external connector. Body shielding: When carried in a pocket, the human body absorbs several dB of the already-weak signal from a PCB antenna. An external antenna on a cable can be positioned to avoid this. Gain Comparison Antenna Type Typical Gain Effective Range vs PCB Notes PCB trace antenna (dev board) 0 - 2 dBi Baseline Subject to proximity detuning Small rubber duck (included) 1 - 2 dBi ~1.1 - 1.3x Better than PCB in most orientations Quality 915 MHz rubber duck 2 - 3 dBi ~1.3 - 1.5x Taoglas, Linx brand options Quarter-wave whip + ground plane ~2.15 dBi ~1.3x Omnidirectional; DIY-constructable Fiberglass 3 dBi (915 MHz) 3 dBi ~1.5 - 2x Best for outdoor fixed nodes Fiberglass 5 dBi 5 dBi ~2.5 - 3x Narrower beam; use at elevation Fiberglass 8 dBi 8 dBi ~4 - 5x Very narrow beam; hilltop/tower only Yagi 10 dBi 10 dBi ~6 - 8x Highly directional; point-to-point only Range multipliers are approximate in ideal line-of-sight conditions. Real-world gains depend on terrain, obstruction, and link margin. Connector Types: SMA vs U.FL SMA (SubMiniature version A) SMA is a threaded RF connector found on most external antennas. Boards with an SMA connector (T-Beam, T-Echo, RAK WisBlock) can directly accept standard SMA-terminated antennas. There are two variants: SMA: Female connector on the antenna (outer thread, inner pin) plugs into the board's male SMA jack (inner socket, outer thread) RP-SMA (Reverse Polarity SMA): Used on WiFi routers and many US-market devices. The genders of the center conductor are swapped. A standard SMA antenna will NOT fit an RP-SMA connector without an adapter. Make sure your antenna matches your board's connector type. U.FL (also called IPEX or MHF1) U.FL is a tiny snap-fit coaxial connector used internally on boards when the antenna connector needs to be on a cable or module rather than soldered to the main PCB. The Heltec V3, some WisBlock modules, and many radio modules use U.FL. A U.FL connector board requires a U.FL to SMA pigtail cable (typically 10 - 15 cm) to adapt to a standard SMA antenna. This cable introduces approximately 0.3 - 0.5 dB of loss, which is a worthwhile tradeoff for a proper external antenna. When Is a PCB Antenna Acceptable? PCB antennas are adequate in these specific scenarios: Indoor testing at short range: Verifying that firmware flashed correctly, testing basic connectivity between nodes in the same room High-density indoor mesh: In a building with many nodes at close range (under 50 meters), PCB antenna limitations are less relevant Ultra-compact wearable or embedded device: If physical size constraints prevent any external component, a PCB antenna may be the only option - but accept the range limitation For any outdoor deployment, fixed repeater, or range-critical use, an external antenna is non-negotiable. Antenna Selection for Common Boards Board Built-in Antenna External Connector Recommended Upgrade Heltec WiFi LoRa 32 V3 PCB trace + spring wire U.FL (under rubber cap) U.FL - SMA pigtail + 3 dBi rubber duck LilyGO T-Beam Supreme None (SMA only) SMA male Quality 915 MHz 3 dBi rubber duck; fiberglass for fixed LilyGO T-Echo None (SMA only) SMA male (small form) Included rubber duck is adequate; upgrade for repeater use RAK4631 (WisBlock) None IPEX (U.FL) on module RAK base board provides SMA passthrough; use 3 - 5 dBi fiberglass for fixed nodes Station G2 None SMA male 3 dBi stubby for portable; fiberglass for fixed Cable Loss Warning If your antenna requires a coaxial cable run (for example, mounting an antenna on a roof while the radio is indoors), cable loss must be accounted for. At 915 MHz: RG-58: approximately 0.6 dB/meter - avoid runs over 3 meters RG-8X: approximately 0.35 dB/meter - usable up to ~10 meters LMR-400: approximately 0.14 dB/meter - suitable for long runs LMR-200: approximately 0.25 dB/meter - good for medium runs A 10-meter run of RG-58 costs you 6 dB - equivalent to running at one quarter the transmit power and completely erasing any gain advantage from a high-gain antenna. Use the lowest-loss cable practical for your installation. GPS Integration in LoRa Nodes GPS in a LoRa mesh node serves two primary purposes: precise location sharing with other mesh users (visible on the Meshtastic map or MeshCore position view), and network topology visualization. Whether you need GPS depends heavily on your use case - and whether you have it, you need to manage its substantial power draw carefully. Why GPS Matters for Mesh Networking Position sharing: Nodes with GPS broadcast their coordinates at regular intervals. Other mesh users can see your location on the map, which is critical for field teams, SAR operations, and event coordination. Network mapping: Community mesh maps (like Meshmap.net for Meshtastic) aggregate node positions to show coverage areas and network topology. GPS-equipped nodes contribute to this. Time synchronization: GPS provides a highly accurate time signal (UTC). Nodes without GPS and without WiFi may have clock drift over time, which can affect message timestamps and channel timing. Range testing: Knowing the exact GPS coordinates of both ends of a link allows accurate range measurement for antenna and placement experiments. Boards with Integrated GPS Board GPS Module Constellations Cold Start GPS Antenna Notes LilyGO T-Beam Supreme u-blox M10 (UBX-M10050) GPS, GLONASS, Galileo, BeiDou ~30 - 45s (open sky) External patch antenna included Best GPS performance of common boards LilyGO T-Echo Quectel L76K GPS, GLONASS, BeiDou ~45 - 90s (open sky) Integrated ceramic patch Compact, adequate for field use LilyGO T-Beam v1.1 (older) NEO-6M / NEO-M8N GPS only (NEO-6M) or GPS+GLONASS (M8N) 45 - 120s External patch antenna Older; M8N variant is better RAK WisBlock + RAK1910 u-blox MAX-7Q GPS, GLONASS ~60s Requires external patch antenna Module adds GPS to any WisBlock base RAK WisBlock + RAK12500 u-blox ZOE-M8Q GPS, GLONASS, Galileo, BeiDou ~26s Integrated ceramic patch Better performance than RAK1910 Adding GPS to Boards Without Boards like the Heltec WiFi LoRa 32 V3, Station G2, or basic ESP32 LoRa boards do not include GPS. You can add it via UART: Common Add-On GPS Modules Module Chip Interface Cost Notes GT-U7 / Neo-6M clone u-blox NEO-6M (often clone) UART (9600 baud default) $4 - $8 Ubiquitous, adequate for basic use; GPS only, no GLONASS Beitian BN-220 u-blox M8030 UART $12 - $18 GPS + GLONASS; compact; popular in FPV community Beitian BN-880 u-blox M8030 + HMC5883L compass UART + I2C $15 - $22 GPS + GLONASS + compass Grove GPS (Seeed) Air530 or u-blox UART via Grove connector $10 - $15 Plug-and-play with Grove system boards PA1010D (Adafruit) MediaTek MT3333 UART or I2C $14 - $20 Very small (25×25mm); good sensitivity UART Wiring for External GPS Connecting an external GPS module via UART to an ESP32 or nRF52840 board requires four wires: GPS Module Pin Connects To (MCU) Notes VCC 3.3V or 5V (check module specs) Most modern GPS modules are 3.3V; some accept 5V GND GND Common ground reference TX (GPS transmits) RX pin on MCU (e.g., GPIO 34 on T-Beam) GPS sends NMEA sentences to MCU RX (GPS receives) TX pin on MCU MCU sends configuration commands to GPS; not strictly required for basic operation In Meshtastic firmware, configure the GPS UART pins via the serial module settings or by editing the platformio.ini defines for your board variant. The default baud rate for most GPS modules is 9600; some support higher speeds (38400, 115200) for reduced latency. GPS Power Consumption GPS is one of the highest-power peripherals in a LoRa mesh node. Understanding its power draw is essential for battery life calculations: GPS Module Acquisition Current Tracking Current Standby / Sleep u-blox NEO-6M (clone) ~50 mA ~45 mA ~4 mA (power save mode) u-blox M10 (T-Beam Supreme) ~18 mA ~12 mA ~8 µA (deep sleep) Quectel L76K (T-Echo) ~25 mA ~20 mA ~0.5 mA (standby) u-blox ZOE-M8Q (RAK12500) ~22 mA ~18 mA ~15 µA (backup) Beitian BN-220 ~40 mA ~35 mA ~1 mA A GPS module drawing 20 mA continuously on an nRF52840 node that otherwise draws 2.5 mA completely changes the power budget. With GPS always on, the effective battery life drops by an order of magnitude on an already efficient node. Disabling GPS to Save Power For nodes where GPS is not needed - fixed repeaters, indoor nodes, nodes operated by users who are not location-sharing - GPS should be disabled: In Meshtastic Open Meshtastic app → Radio Config → Position Set GPS Mode to "Disabled" or "Not Present" Set Position Broadcast Interval to 0 (disable position broadcasting) The firmware will stop initializing the GPS UART and power-gate the GPS module if the board supports it In MeshCore GPS can be disabled in the node configuration. Boards without GPS will automatically operate without position features. Hardware Power Gating The T-Beam Supreme includes a software-controllable power switch for the GPS module via a GPIO pin. When GPS is disabled in Meshtastic firmware, this switch cuts power to the GPS entirely - achieving the 8 µA deep sleep current of the M10 rather than wasting its standby current. This is the correct way to save GPS power on the T-Beam. On boards without hardware GPS power gating (many DIY builds), you may need to add a P-channel MOSFET or a load switch IC between the 3.3V rail and the GPS module's VCC to enable software-controlled power off. GPS Accuracy and Placement Tips Sky view is everything: GPS requires line-of-sight to satellites. A node in a metal enclosure, inside a building, or under a dense tree canopy will have poor GPS accuracy or fail to acquire a fix. For outdoor fixed nodes, ensure the GPS antenna has clear sky view. Active vs passive antenna: The u-blox M10 on the T-Beam Supreme supports an external active patch antenna. Active antennas include a built-in LNA and provide better sensitivity in marginal conditions. The T-Beam's included antenna is passive - an active upgrade (check connector compatibility) can improve indoor fix times. AGPS (Assisted GPS): Some modules support AGPS, where the firmware downloads almanac and ephemeris data over WiFi to dramatically reduce cold start time to under 5 seconds. Meshtastic supports this on ESP32 boards with WiFi. Backup battery: GPS modules with a small backup coin cell retain almanac data between power cycles, reducing cold start from 45 - 90 seconds to a "warm start" of 5 - 15 seconds. The T-Beam Supreme includes this backup battery circuit. SX1262 vs SX1276: Why It Matters SX1262 vs SX1276: Why It Matters Nearly every mesh radio node sold today uses one of two LoRa radio ICs from Semtech: the older SX1276 or the newer SX1262. Both chips implement LoRa spread-spectrum modulation and are outwardly similar, but their performance characteristics and firmware support differ in ways that matter to operators making purchasing decisions. SX1276 -- The Legacy Chip The SX1276 was Semtech's flagship LoRa transceiver through most of the 2010s and became the default radio in the first wave of Meshtastic hardware. It supports 433, 868, and 915 MHz bands via separate variants. Key specs: Receive sensitivity: -137 dBm at SF12, BW125 Max output power: +17 dBm No Channel Activity Detection (CAD) in hardware Wider support across early Meshtastic board designs Boards using SX1276: T-Beam v0.7, v1.0, v1.1; Heltec LoRa 32 V1 and V2; original TTGO LoRa boards. SX1262 -- The Current Standard The SX1262 is Semtech's second-generation LoRa transceiver and is now the standard chip in all modern mesh hardware. Improvements over SX1276: Receive sensitivity: -148 dBm at SF12, BW125 -- 11 dB better than SX1276 Max output power: +22 dBm (vs +17 dBm) Hardware Channel Activity Detection (CAD) -- the chip can listen for LoRa preambles and avoid transmitting when the channel is busy, reducing packet collisions Lower TX and RX current draw Faster frequency switching Boards using SX1262: T-Beam v1.2 and Supreme; RAK4631 WisBlock (all variants); Heltec LoRa 32 V3; LILYGO T-Deck; T114; T3-S3. MeshCore Requirement This distinction has a practical consequence that operators must understand: MeshCore firmware requires SX1262 . The MeshCore project made a deliberate decision to drop SX1276 support to simplify the codebase and take full advantage of SX1262's CAD and sensitivity improvements. If you are building or buying hardware for MeshCore specifically, you must purchase SX1262-equipped boards. Meshtastic supports both chips and will continue to do so for compatibility with older hardware. Practical Range Impact The 11 dB sensitivity improvement of SX1262 is significant. In link-budget terms, 11 dB of additional receive sensitivity can translate to roughly 3-4x longer range in free-space conditions, or allow communication through obstacles that would block an SX1276 link. In dense urban environments the gain is less dramatic due to multipath fading, but elevated nodes in rural areas often see measurable range extensions with SX1262 hardware. Quick Reference: Which Board Has Which Chip Board Chip MeshCore Compatible T-Beam v0.7 / 1.0 / 1.1 SX1276 No T-Beam v1.2 / Supreme SX1262 Yes RAK4631 (all) SX1262 Yes Heltec V1 / V2 SX1276 No Heltec V3 SX1262 Yes T-Deck SX1262 Yes T114 SX1262 Yes T3-S3 SX1262 Yes When purchasing used or surplus hardware, always verify the board version before assuming SX1262. Many T-Beams sold on secondary markets are pre-v1.2 and carry the SX1276. Check the silkscreen on the radio module or the board revision printed near the USB port. T114 and T3-S3: New Hardware for 2025-2026 T114 and T3-S3: New Hardware for 2025-2026 LILYGO's 2024-2025 product refresh introduced two boards that are quickly becoming community favourites: the T114 and the T3-S3. Both pair an SX1262 LoRa radio with a modern microcontroller, but they target distinctly different use cases and operator needs. T114 -- Compact Infrastructure Node The T114 combines Nordic Semiconductor's nRF52840 with the SX1262 in a compact, screen-free form factor. It is clearly designed for infrastructure deployments rather than handheld use: MCU: nRF52840 (ARM Cortex-M4F at 64 MHz) Radio: SX1262 -- MeshCore and Meshtastic compatible Display: None (no screen) Connectivity: USB-C for power and programming; BLE for phone pairing Power: Leverages the nRF52840's exceptional sleep current -- suitable for solar deployments on very small panels Form factor: Smaller than a T-Beam; easy to fit in weatherproof enclosures The T114's lack of display is a feature, not an omission, for infrastructure roles. Removing the screen eliminates a significant power draw and a mechanical failure point. For a repeater node on a rooftop or inside a pelican case, there is nothing to see anyway. Community feedback has been overwhelmingly positive: operators report clean BLE pairing, reliable SX1262 performance, and excellent battery life. The one common complaint is that the small PCB can be finicky to solder antenna connectors to, so purchasing the version with a pre-soldered U.FL connector is recommended. Firmware support: Meshtastic ships official T114 firmware. MeshCore also supports the T114 with its nRF52840 build. T3-S3 -- The WiFi-Capable LoRa Node The T3-S3 pairs Espressif's ESP32-S3 with an SX1262 and is positioned as a direct competitor to the T-Beam Supreme in the WiFi-capable segment: MCU: ESP32-S3 dual-core at 240 MHz, 16 MB flash, 8 MB PSRAM Radio: SX1262 GPS: Optional GPS module header (u-blox-compatible footprint, same as T-Beam) WiFi: 802.11 b/g/n via ESP32-S3 -- enables MQTT bridging and web config USB-C: Yes, with native USB on ESP32-S3 (faster flashing, serial CDC without external chip) Form factor: Slightly more compact than T-Beam Supreme; no integrated keyboard The T3-S3 is particularly compelling as a WiFi MQTT gateway replacement for existing T-Beam deployments. Where the original T-Beam uses an older ESP32 with less RAM, the T3-S3's ESP32-S3 handles concurrent WiFi and LoRa tasks more reliably and has enough headroom for Meshtastic's full feature set -- including MQTT and web server simultaneously -- without the memory pressure that can cause instability on older ESP32 boards. Availability and Pricing (early 2026) Both boards are available directly from lilygo.cc , typically with 2-3 week shipping from Shenzhen Amazon listings exist for both boards (US warehouse stock, faster shipping, approximately 15-20% price premium) AliExpress offers the lowest prices but longest lead times T114: approximately $18-22 USD without GPS module; $25-30 with GPS add-on T3-S3: approximately $25-32 USD without GPS module Community Verdict Both boards have earned strong reputations in the mesh community since their wider availability in mid-2024. The T114 is now the default recommendation for solar repeater builds in the RAK4631's price range, particularly where MeshCore compatibility is required. The T3-S3 is the recommended ESP32 platform for new WiFi gateway deployments, preferred over the ageing T-Beam for its updated silicon, improved RAM headroom, and USB-C convenience. Operators upgrading from T-Beam v1.1 hardware should strongly consider the T3-S3 as the direct modern replacement.