Project Files of nRF24L01 PA LNA Library for Proteus V1.1 + Arduino Demo

nRF24L01+PA+LNA 2.4 GHz RF MODULE (PA +20 dBm, LNA, SMA ANTENNA) LIBRARY FOR PROTEUS - V1.1
Designed by The Engineering Projects
www.TheEngineeringProjects.com

IMPORTANT LINKS
Article (read it first - pictures, step by step, every feature explained):
  https://www.theengineeringprojects.com/2026/09/nrf24l01-pa-lna-proteus-library.html
Report a bug or suggest a feature (our forum):
  https://www.theengineeringprojects.com/forum/category/nrf24l01-pa-lna-proteus-library
The demo uses our TEP Serial Monitor Advance (included) instead of Proteus's
Virtual Terminal - its own article:
  https://www.theengineeringprojects.com/2026/10/serial-monitor-advance-proteus-library.html
Support us (the libraries are free):
  https://www.theengineeringprojects.com/donate

FILE STRUCTURE
NRF24PALNA-TEP-v1.1/
|-- Proteus Library Files/
|   |-- ArduinoV3TEP.IDX                              0.8 KB   its index -> LIBRARY folder
|   |-- ArduinoV3TEP.LIB                             95.6 KB   TEP Arduino UNO (demo) -> LIBRARY folder
|   |-- TEPNRF24PALNA.LIB                            92.3 KB   nRF24L01+PA+LNA Simple + Advance (2 devices) -> LIBRARY folder
|   |-- TEPSERIALMON.LIB                             11.1 KB   TEP Serial Monitor Advance -> LIBRARY folder
|-- Proteus Model Files/
|   |-- TEPNRF24L01.DLL                             344.5 KB   nRF24 model (shared with the nRF24L01 library) -> MODELS
|   |-- TEPSERIALMON.DLL                            978.0 KB   Serial Monitor model -> MODELS folder
|-- Proteus Simulation/
|   |-- NRF24PALNA-ArduinoUnoV3.pdsprj               23.9 KB   demo: UNO 1 + nRF24L01+PA+LNA Simple, UNO 2 + Advance
|   |-- PALNA_Receiver.hex                           28.1 KB   UNO 2 (receiver v1.1)
|   |-- PALNA_Transmitter.hex                        34.5 KB   UNO 1 (transmitter v1.1)
|   |-- TEPNRF24L01.DLL                             344.5 KB   copy of the model so the demo runs as is
|   |-- TEPSERIALMON.DLL                            978.0 KB   copy of the monitor model
|-- Arduino Code/
|   |-- PALNA_Receiver/PALNA_Receiver.ino             8.3 KB   sketch (source of the .hex)
|   |-- PALNA_Transmitter/PALNA_Transmitter.ino       9.8 KB   sketch (source of the .hex)
|   |-- libraries/RF24/                             778.8 KB   RF24 1.6.2 (GPL-2.0, LICENSE), 107 files
|-- README.txt                                      ~29.4 KB   this file
Total: 3.67 MB (unzipped). The C++ source code of the model is not included.

WHAT IS IT?
A simulation model of the long-range nRF24L01+PA+LNA module (the black board with
the SMA rubber-duck antenna: an nRF24L01+ chip plus an RFX2401C-type power
amplifier and low-noise amplifier) for Proteus 8. Your Arduino talks to it over
SPI exactly like to the real chip (it is an nRF24L01+): every register, every SPI
command, the FIFOs, Enhanced ShockBurst with auto-ACK and retransmissions, dynamic
payloads, ACK payloads, six RX pipes, the IRQ pin and the timing - it runs the
unmodified RF24 library. What the PA and LNA add is in the link budget: +20 dB of
transmit power, 8 dB better sensitivity, 12 dB of LNA gain in front of the chip
(the RPD sees the amplified signal), a 2 dBi antenna - and the receiver OVERLOADS
when a strong neighbour is too close (above -20 dBm at the antenna). Every TEP
nRF24L01 in a design (PA+LNA or plain) shares one simulated 2.4 GHz air; you
choose the DISTANCE between the radios (1 m ... 2 km). The part looks like the
real module: a long black board with the SMA connector and the rubber duck on its
top end, the nRF24L01+ chip, the RFX2401C PA / LNA and the crystal in the middle
and the 2 x 4 header (pins labelled) on its bottom end. While the simulation runs
a ring LED on the rubber duck and the lamp in its tip light orange while it
transmits and green while it receives, radio waves above the antenna ripple out
(sending) or in (receiving), and three LEDs show what happens: PWR (red, lit
while VCC is there), TX (orange, blinks for every packet sent) and RX (green,
blinks for every packet or ACK received). The LEDs are a TEP addition - the real
module has no LEDs.

TWO DEVICES IN ONE LIBRARY (search "PA+LNA" or "nRF24" in Pick Devices):
  nRF24L01+PA+LNA Simple    device NRF24PALNATEP     "nRF24L01+PA+LNA RF Transceiver Module - Simple"
                     On-Sheet Panel: the control panel is drawn on the
                     schematic next to the module (the v1.0 panel): mode,
                     channel / frequency, data rate, CRC, TX power (+20 dBm at
                     PA_MAX), the TX and RX addresses, SENT / FAILED / RECEIVED, TOO
                     WEAK / OVERLOAD, the last packet with its level, the DISTANCE
                     buttons and the predicted link budget. The red X in the panel
                     header closes it, the PANEL button on the board opens it again.
                     Your v1.0 designs keep working with this device.
  nRF24L01+PA+LNA Advance   device NRF24PALNAADVTEP  "nRF24L01+PA+LNA RF Transceiver Module - Advance"
                     Pop-Up Panel: only the module board on the schematic; at Run
                     a TEP pop-up window opens - the same look as the TEP Serial
                     Monitor (move it by its header, resize it, minimise it). The
                     tabs Radio and Test sit in the header; the gear and ? icons
                     open Settings and Help; the palette icon switches the theme:
                       Radio     the state banner, RADIO (channel, data rate, TX
                                 power = the chip's level + 20 dB PA, sensitivity,
                                 CRC, address width, auto-ACK and retries - what
                                 your sketch wrote), ADDRESSES AND PAYLOAD, TRAFFIC
                                 (sent / ACKed / lost, received, duplicates,
                                 retries, too weak / overload, the last level and
                                 RPD, the last packet) and DISTANCE (the eight
                                 buttons, the level at that distance and how far
                                 these settings reach)
                       Test      four test tools, all measured on the model: Link
                                 test, Throughput, Channel scan, Registers (see THE
                                 TEST TOOLS below)
                       Settings  theme (TEP Dark / Light), text size, open at Run,
                                 window size - remembered for your Windows user
                       Help      Help & Support like the TEP Serial Monitor: report
                                 a bug, suggest a feature, article, user guide,
                                 updates, donate, website, forum; Copy diagnostics
                                 (radio, registers, traffic, test results, the other
                                 radios) for a bug report
                     The OPEN PANEL button on the board opens the window again
                     after you close it.
Both devices use the same model, TEPNRF24L01.DLL - the TEP nRF24 family model,
shared with the nRF24L01 library (identical TEPNRF24L01.DLL in both packages, so
installing both is safe). PA+LNA and plain modules in one design talk to each
other (see MIXED DESIGNS).

NEW IN V1.1
* Two devices: nRF24L01+PA+LNA Simple (the panel on the sheet, close / open) and
  nRF24L01+PA+LNA Advance (pop-up window with the radio page, four test tools,
  settings and help) - see above.
* Board: the black board drawn long like the real module - the SMA connector and
  the rubber duck on the top end (v1.0: on a corner of a wide board), the 50 ohm
  trace down to the RFX2401C PA / LNA, the nRF24L01+ chip and the crystal, the
  2 x 4 header with its pin names on the bottom end. The 8 Proteus pins stay where
  v1.0 had them, so the wiring of a v1.0 design fits. A ring LED on the rubber
  duck and a lamp in its tip (orange = sending, green = receiving), radio waves
  above the antenna; new LEDs PWR / TX / RX (a TEP addition - the real module has
  none): PWR lights with VCC, TX blinks for every packet sent, RX for every packet
  or ACK received (each blink held 0.3 / 0.4 s so you see it); a PANEL / OPEN
  PANEL button and a SIMPLE / ADVANCE badge beside the LEDs.
* Model: every transmission (packet and ACK) now reaches the Received Power
  Detector of every radio listening on that channel, whatever its address or data
  rate (like the real RPD); the model records what the test tools show (packets
  with their retries and levels, the SPI commands, the channel activity). The
  DISTANCE buttons, the PA / LNA link budget, the overload and everything of v1.0
  are unchanged.
* The demo uses the TEP Serial Monitor Advance instead of Virtual Terminals - one
  monitor per Arduino (U3 = UNO 1, U4 = UNO 2) with quick buttons - and shows both
  styles: UNO 1 with the Simple device, UNO 2 with the Advance device.
* The demo sketches (v1.1) keep every v1.0 output line (retries, the RPD remark)
  and add Serial Monitor commands (SEND, PING, STATUS, CH, RATE, PA, AUTO, HELP)
  and a link line every 10 s; the transmitter now listens between its packets, so
  the receiver can send to it too (and answer PING with PONG).
* Version 1.1 everywhere; the C++ source code of the model is no longer included.

TEST STATUS
v1.0 was tested in Proteus 8.5 SP0 (30 Sep 2026) with the v1.0 demo (250 kbps,
channel 108, PA MAX): at 10 m every "Hello TEP #n" was acknowledged with 0 retries
and the receiver reported "signal > -64 dBm"; 1 km still worked as a weak signal
(-100 dBm against -102 dBm needed); 2 km failed (-109 dBm, too weak); both panels
at 1 m overloaded the receivers (-16 dBm into the LNA); back at 10 m the link
recovered at once.
v1.1 was tested in Proteus 8.5 SP0 (6 Oct 2026) with this package's demo: both
Serial Monitors and the Advance pop-up open at Run (no system caption row); the
black boards light PWR and blink TX / RX, the duck's ring and tip glow orange /
green. Node 2 receives at -44 dBm at 10 m (+57.6 dB). U2 (Advance): Test > Link
test at 500 m 6 / 6 ACKed at -92 dBm (+10 dB) while the table shows the plain
nRF24L01 failing beyond 50 m; Settings, Help, close and OPEN PANEL.
PC tests:
PC tests (one test suite for the whole nRF24 family): 1417 automatic checks on a
PC: 69 with the UNMODIFIED RF24 library driving two chip models bit by bit over
SPI (the v1.0 tests, unchanged: range per data rate with PA+LNA modules, overload
at 1 m and PA_LOW as the cure, RPD, a PA+LNA module talking to a plain one); 54 on
the v1.1 chip features (RPD from every carrier, the packet records, the SPI log,
the channel scan, the partner check, the throughput bench); 145 on the complete
Proteus model (the 38 of v1.0 unchanged + both devices of both libraries, the red
X and PANEL, OPEN PANEL, a v1.0 design, the duck's ring LED / tip lamp, the PWR /
TX / RX LEDs, the pop-up window without a caption row, its pages, the four tools
with measured numbers, Help links, diagnostics); 57 with the four REAL v1.1 demo
sketches running on two simulated UNOs at once (every v1.0 line, 1 km weak / 2 km
fail / 1 m overload, the commands, PING both ways, the link line); 1092 on the
rendered pop-up windows and boards (every page fits in TEP Dark and Light, at
Large text and 150 % DPI; every tool's hint lines fit; the header line fits
beside the tabs in every state; the LEDs lit / dark on the boards as they should
be).

INSTALLATION (about 2 minutes)
1. Close Proteus. Extract the WHOLE ZIP to a normal folder (e.g. Desktop).
2. Copy everything in "Proteus Library Files" (TEPNRF24PALNA.LIB with both
   devices, TEPSERIALMON.LIB and the TEP Arduino UNO V3 library ArduinoV3TEP.LIB /
   .IDX used by the demo) to the LIBRARY folder of Proteus, for example:
     C:\Program Files (x86)\Labcenter Electronics\Proteus 8 Professional\LIBRARY
   (on some PCs: C:\ProgramData\Labcenter Electronics\Proteus 8 Professional\
   LIBRARY - use the folder that already holds Proteus's own .LIB files).
3. Copy TEPNRF24L01.DLL and TEPSERIALMON.DLL from "Proteus Model Files" to the
   MODELS folder (...\Proteus 8 Professional\MODELS).
4. Updating from v1.0: replace TEPNRF24PALNA.LIB (delete any TEPNRF24PALNA.IDX)
   and TEPNRF24L01.DLL. A v1.0 design keeps its v1.0 symbol: it runs with the new
   model (the v1.0 panel and its DISTANCE buttons, without the v1.1 board parts and
   the red X) - re-pick the part to get the v1.1 symbol. If you also use our
   nRF24L01 library, its TEPNRF24L01.DLL is the same file.
5. Start Proteus. In Pick Devices (P) search "PA+LNA": you get the Simple and the
   Advance device (category Peripherals > Wireless).

RUN THE DEMO
"Proteus Simulation\NRF24PALNA-ArduinoUnoV3.pdsprj" - keep the two .hex files and
the two DLLs beside the project. Both sketches: channel 108 (2508 MHz, above most
Wi-Fi), 250 kbps (the best sensitivity), PA MAX (+20 dBm).
  UNO 1 (ARD1): PALNA_Transmitter.hex, nRF24L01+PA+LNA Simple (U1) and Serial
  Monitor U3.
  UNO 2 (ARD2): PALNA_Receiver.hex, nRF24L01+PA+LNA Advance (U2) and Serial Monitor
  U4.
  1. Press Run. Both monitor windows open (9600 baud) and so does U2's pop-up.
     U3 shows "Sent: Hello TEP #1  -> ACK received, retries: 0" every second, U4
     "Received #1: Hello TEP #1  (signal > -64 dBm)" (-44 dBm at 10 m); the duck's
     ring and tip flash orange on U1 and green on U2, U1's TX and RX LEDs blink
     (its packet, the ACK back), U2's RX LED blinks. U1's panel shows RX -
     LISTENING between its packets: the v1.1 transmitter listens for node 2's
     messages (PING, SEND) between sends (v1.0 sat in STANDBY-I).
  2. U3 / U4 quick buttons: PING (the other node answers PONG - about 3.7 ms at
     250 kbps), STATUS, SEND Hello from node 1 / 2, HELP. Type your own: SEND
     <text>, CH 100 (then on the other monitor too), RATE 1M (both), PA LOW, AUTO
     OFF / ON (UNO 1).
  3. Click 1 km on U1's panel (or on U2's Radio page): still OK, "(weak signal)"
     (-100 dBm, 250 kbps needs -102 dBm). 2 km: "FAILED, no ACK" (-109 dBm). Back
     to 10 m. Now set BOTH to 1 m: the receivers overload (-16 dBm into the LNA) -
     type PA LOW on both monitors and it works again. Close U1's panel with its red
     X, open it with PANEL.
  4. U2 (Advance): open the Test tab:
       Link test: 10 packets, Run test - U1's next 10 packets with their level and
         retries; click 2 km during the test and watch the bars turn red.
       Throughput: 250 kbps / 1 Mbps / 2 Mbps, payload, auto-ACK, Run test.
       Channel scan: 5 s, Run test - the busy channels.
       Registers: what the sketch wrote, its SPI commands, U1 as its partner.
  5. Close U2's window and open it again with OPEN PANEL on the board.
Closed a monitor window? Click OPEN MONITOR on the monitor part.

WIRING (SPI, the same on both UNOs)
  Module VCC -> supply (+5 V in the simulation - a real module needs 3.3 V!),
  GND -> GND, SCK -> D13, MISO -> D12, MOSI -> D11, CSN -> D10, CE -> D9, IRQ
  open (active LOW, for interrupt-driven sketches).
  In the sketch: RF24 radio(9, 10);   // CE, CSN
  Serial Monitor RXD <- Arduino D1 (TX), Serial Monitor TXD -> Arduino D0 (RX),
  Serial Monitor GND -> ground. RXD2 is not needed for SPI radios: the monitor's
  second input watches a serial line, and the nRF24L01+PA+LNA has none (it talks
  SPI). Serial.begin(9600) in the sketches.
Pin order in Proteus: VCC GND SCK MISO MOSI CSN CE IRQ (the same as the TEP
nRF24L01 board; the real module's 2 x 4 header is GND VCC / CE CSN / SCK MOSI /
MISO IRQ).
REAL HARDWARE:
 * Supply 3.3 V (1.9 - 3.6 V), never 5 V. The PA+LNA module draws up to about
   115 mA while it transmits at PA_MAX - more than the UNO's 3.3 V pin can give:
   use a separate 3.3 V regulator (e.g. an nRF24 adapter board with an AMS1117)
   with a common GND.
 * Put a 10 - 100 uF capacitor across VCC and GND right at the module (the PA's
   current peaks make many modules fail with "no ACK" or reset without it).
 * Shielding: the PA of the unshielded modules can couple back into the chip and
   oscillate - use a module with a metal shield, or cover the PA / LNA area with
   insulating tape and then foil connected to GND; keep it away from the UNO.
 * Never transmit without the antenna screwed on (the PA can be damaged). Two
   PA+LNA modules on one desk: use RF24_PA_LOW or MIN - at PA_MAX the receiver's
   LNA overloads (the simulation shows it as OVERLOAD).

HOW THE RADIOS TALK (the model)
A packet arrives when the receiver is powered, listening (PRIM_RX = 1, CE high,
130 us settled), on the same channel, data rate, address width and CRC length,
with a matching enabled pipe address and payload size, its RX FIFO not full - and
the link budget is OK: level = the chip's TX power (RF24_PA_MIN -18 / LOW -12 /
HIGH -6 / MAX 0 dBm) + 20 dB PA + 2 dBi + 2 dBi (two PA+LNA modules) - path loss
(free space up to 1 m, then exponent 2.8: 68 dB at 10 m, 96 dB at 100 m), against
the sensitivity (chip: -94 dBm at 250 kbps, -85 at 1 Mbps, -82 at 2 Mbps; with the
LNA 8 dB better: -102 / -93 / -90 dBm); above -20 dBm at the antenna the receiver
is OVERLOADED. The link uses the LARGER of the two radios' DISTANCE settings. RPD =
1 when the level after the 12 dB LNA is above -64 dBm. The demo (PA MAX, 250 kbps):
-44 dBm at 10 m (RPD 1), -100 dBm at 1 km (OK, 2 dB margin), -109 dBm at 2 km (too
weak), -16 dBm at 1 m (overload); it reaches about 1.1 km. At 1 Mbps it reaches
about 540 m, at 2 Mbps about 420 m.
MIXED DESIGNS: a PA+LNA module and a plain nRF24L01 can talk (same channel, rate,
address); the plain one hears the PA+LNA module much further than the PA+LNA
module hears the plain one's ACKs - at 250 m and 250 kbps the plain module
receives (-86 dBm) but its ACK is too weak on the way back (-106 dBm): the sender
retries 15 times and reports a failure while the receiver stores the packet once
(the duplicates are dropped, as on the real chip).

THE TEST TOOLS (nRF24L01+PA+LNA Advance, Test tab) - what they really do
Every tool runs on the live model with your sketch and shows one "Good for:"
line plus one line on how it measures.
  Link test     Records the next 10, 20 or 50 packets THIS radio sends or hears
                (the sketch's real traffic): for each the retries (ARC), ACKed /
                lost (MAX_RT after 15) / no ACK asked, the level at the receiver,
                and whether the receiver stored it, heard it too weak, overloaded
                or dropped it as a duplicate. The DISTANCE buttons are on the tool,
                so you can move the radios while it runs. Below: the link budget at
                your data rate and PA level for a pair of plain modules and a pair
                of PA+LNA modules at every distance (at 250 kbps / PA_MAX: the
                PA+LNA pair OK up to 1 km, OVERLOAD at 1 m; the plain pair only to
                50 m). Example (the demo, U2): 5 packets ACKed at -44 dBm, 3 lost at
                2 km (-109 dBm, 16 attempts each), 2 more at 1 km (-100 dBm, OK).
                No packet for 15 s stops it.
  Throughput    Two model radios in a private test air (your design never hears
                them), at this radio's DISTANCE and PA level, stream 100 packets
                like RF24's writeFast() (the TX FIFO kept full, CE high): measured
                packets / s, payload bytes / s, the time per packet (130 us
                settling + the packet's bits + the ACK), plus a table of all three
                data rates with auto-ACK on and off. Measured at 10 m, 32 bytes:
                250 kbps 535 / 692 packets/s (17.1 / 22.1 kB/s), 1 Mbps 1511 / 2179
                (48.3 / 69.7 kB/s), 2 Mbps 2132 / 3350 (68.2 / 107.2 kB/s) with /
                without ACK (the PA and LNA do not change the speed, only the
                reach; two PA+LNA modules 1 m apart at PA_MAX: overload, 0 packets/s).
                A real UNO adds its SPI time. Below: your sketch's own traffic of
                the last 5 s.
  Channel scan  Listens on all 126 channels for 1, 5 or 10 s: every packet and
                ACK of the TEP radios in the design, the strongest level at this
                radio per channel and how often it was above -64 dBm after the LNA
                (RPD), with the Wi-Fi channels 1 / 6 / 11 drawn for reference (there
                is no Wi-Fi in the simulation) and a list of the busy channels and
                who uses them. (The radio's own ACKs are not counted.)
  Registers     The registers read live as R_REGISTER would (CONFIG, EN_AA,
                EN_RXADDR, SETUP_AW, SETUP_RETR, RF_CH, RF_SETUP, STATUS,
                OBSERVE_TX, RPD, the addresses, RX_PW, FIFO_STATUS, DYNPD, FEATURE)
                with their meaning, the SPI counters, the Arduino's last SPI
                commands (time, command, data, duration; identical commands in a
                row folded - RF24's available() polls FIFO_STATUS) and THE OTHER
                RADIOS: does each match this one (channel, data rate, CRC, address
                width, address, payload size, level here)?

THE DEMO SKETCHES ON THE SERIAL MONITOR (PALNA_Transmitter / PALNA_Receiver v1.1)
  SEND <text>             a message to the other node now (up to 31 characters)
  PING                    the other node answers PONG - prints the round trip
  STATUS                  channel, frequency, data rate, PA level, CRC, chip OK,
                          addresses, counters
  CH <0-125>              radio channel (type it on both monitors)
  RATE <250K|1M|2M>       data rate (both)
  PA <MIN|LOW|HIGH|MAX>   transmit power (PA LOW when the modules are close)
  AUTO <ON|OFF>           (transmitter) the Hello TEP message every second
  HELP                    the command list
Monitor quick buttons in the demo: PING, STATUS, SEND Hello from node 1 / 2, HELP.
Node 1 sends to address 00001 and listens on 00002 between its packets; node 2
listens on 00001 and sends to 00002.

EXPECTED MONITOR OUTPUT (from the PC test of the real sketches)
U3 (UNO 1, transmitter):
  TEP nRF24L01+PA+LNA Transmitter Demo v1.1
  Radio ready: channel 108, 250 kbps, PA MAX, address 00001
  Type HELP in the Serial Monitor for the commands
  Sent: Hello TEP #1  -> ACK received, retries: 0
  Sent: Hello TEP #2  -> ACK received, retries: 0
  PING: PONG from node 2 after 3.7 ms
  Received from node 2: Over and out
  Sent: Hello TEP #31  -> FAILED, no ACK          (2 km, or both at 1 m)
U4 (UNO 2, receiver):
  TEP nRF24L01+PA+LNA Receiver Demo v1.1
  Listening: channel 108, 250 kbps, address 00001
  Received #1: Hello TEP #1  (signal > -64 dBm)
  Received #5: Hello TEP #5  (weak signal)        (1 km)
  Link (10 s): 10 received (0 above -64 dBm), 0 sent
  Received #22: PING  (signal > -64 dBm)
    -> PONG sent back

PROPERTIES
The module has no user properties: the sketch sets channel, data rate, power and
addresses over SPI (as on the real chip), and the DISTANCE is chosen on the panel
(10 m at every Run). The panel style is chosen by the device (Simple / Advance).
The Advance window settings (theme, text size, open at Run, size) are on its
Settings page. The demo's Serial Monitors: BAUD 9600, THEME TEPDARK, AUTOOPEN
YES, QUICK1-4 as above (see the Serial Monitor's article for all its properties).

LINKS.INI (OPTIONAL)
The Help page cards of the Advance device open web pages. To point them
somewhere else without a new DLL, put a text file named links.ini next to
TEPNRF24L01.DLL with lines KEY=URL, for example:
  ARTICLE=https://www.theengineeringprojects.com/...
Keys: WEBSITE, FORUM, BUG_REPORT, FEATURE_REQUEST, ARTICLE, USER_GUIDE,
UPDATE_CHECK, DONATE. Only http:// and https:// links are used; lines starting
with # are comments. Cards whose link is not published yet say "Link coming soon".
(The links.ini next to TEPNRF24L01.DLL is shared by the nRF24L01 and the PA+LNA
Advance devices - the DLL is the same file.)

TROUBLESHOOTING
* "nRF24L01 not responding - check the SPI wiring and power": check SCK D13,
  MISO D12, MOSI D11, CSN D10, CE D9 and VCC / GND, and that TEPNRF24L01.DLL is in
  MODELS (and beside the project).
* "FAILED, no ACK" with the modules close together: OVERLOAD - the panel / Radio
  page says so; use PA LOW (or more
…