NRF24L01+ (2.4GHz Radio Transceiver)

The NRF24L01+ is a tiny, cheap 2.4 GHz radio module that any board can talk to over a plain 5-wire SPI connection — no Wi-Fi chip needed.

Connectivity13 blocksMicroPythonC++

The NRF24L01+ is a tiny, cheap 2.4 GHz radio module that any board can talk to over a plain 5-wire SPI connection — no Wi-Fi chip needed. Think of it as a walkie-talkie chip you bolt onto any microcontroller: two boards, each with one of these modules, can send short text/number messages back and forth over open air.


1. Real-World Uses

NRF24L01+ is a favorite for hobby robotics and remote-control projects because it's cheap, works on almost any board (even ones with no Wi-Fi/Bluetooth chip at all, like an Arduino Uno), and reaches farther than Bluetooth:

  • RC robots and cars — a joystick-equipped "controller" board sends steering/throttle commands to a "receiver" board on the robot.
  • Garden/farm sensor links — sending readings back from a sensor board placed further away than Wi-Fi or Bluetooth could reliably reach (up to 100m, or 1km with a PA/LNA long-range antenna version).
  • Simple two-board demos on non-wireless boards — since it just needs SPI pins, this is one of the only ways to get an Arduino Uno (which has no built-in Wi-Fi/Bluetooth) talking wirelessly to another board.

2. Pinout & SPI Interface

  • Operating Voltage: 3.3V VCC (5V tolerant logic pins).
  • Pin Configuration:
    • CE (Chip Enable): Digital output pin (TX/RX mode switch).
    • CSN (Chip Select Not): SPI CS pin.
    • SCK, MOSI, MISO: SPI Bus pins.
    • IRQ (Interrupt Request): Optional active-LOW interrupt pin (asserts on RX_DR), only needed for the IRQ-driven receive block near the end of this list.

[!IMPORTANT] Decoupling Capacitor Required: The NRF24L01+ draws significant current spikes (~160mA) during RF transmission, causing voltage brownouts on boards with insufficient power regulation. This is the most common cause of random communication failures and module unresponsiveness. Fix: Solder a 10µF to 100µF electrolytic capacitor across the VCC and GND pins of the module (+ leg to VCC, – leg to GND). Without this, packet loss and non-responsive behaviour are common even at short range.


3. Supported Blockly Blocks (13 Blocks)

Drawing the blocks…

4. Simulator Behavior

[!IMPORTANT] Same inert-but-crash-free category as the rest of Chapter 7 — with one block that genuinely hangs rather than just doing nothing. OMS's nrf24l01 MicroPython stub makes .any() always return False and .send() always raise OSError("DL") (the same "no ACK, nobody's listening" failure a real board would report with no peer nearby — already handled by this extension's own try/except, so it doesn't crash your program):

  • Send Raw Text / Send Typed String/Number/Value all "succeed" silently (the exception is caught internally) but never actually transmit anywhere.
  • Data Available? always returns false; Receive Raw Text always returns an empty string.
  • On String/Number/Value Received and On IRQ Data Received never fire — nothing ever arrives.
  • Wait for Data will hang your simulated program forever — its while not ...any(): sleep loop never exits, since .any() never becomes True. This is a real, meaningful difference from every other "inert" block in this chapter: those just silently do nothing, this one blocks all further execution. Avoid this block when testing in the Circuit Simulator. All blocks generate fully correct, real code for actual hardware — NRF24L01+ projects need two real boards with real modules to test properly, not the Simulate button.
NRF24L01+ (2.4GHz Radio Transceiver) — OMS Parts