View Full Version : Does anybody get Teensy 3 working with NRF24L01+?

01-15-2013, 06:05 PM
I'm using this library with Teensy 3.0 and a NRF24L01+: http://playground.arduino.cc/InterfacingWithHardware/Nrf24L01

I checked the code, and it doesn't seem system dependent because it uses SPI interface. The code that I'm using is the ping_server and ping_client example. The only difference is I'm setting up CSN and CE like this:

Mirf.cePin = 9;
Mirf.csnPin = 10;

For testing purpose I used 2 arduino Uno with the same code to make sure everything was wired correctly. Now, I'm moving my ping_server to the Teensy, it compiles and uploads ok. But I can't get the packets on it.

Maybe something that I'm missing?

I used this pins:
SS (CSN) = 10
MOSI = 11
MISO = 12
SCK = 13
CE = 9

And connecting as the following image: http://arduino-info.wikispaces.com/file/view/24L01Pinout-800.jpg/243330999/24L01Pinout-800.jpg

On uno it works, on teensy it doesn't.

Any ideas?

Thanks :D

01-16-2013, 05:57 PM
I think I made some progress.

My client station sends a char to the server station it is always 'A'. I'm still testing with 2 arduino uno boards, and it is working with then. Moving the "receiver" (server) to teensy.

I realized that the Mirf library uses:


With this I received random chars but at least the address (registers) read on:
RX_ADDR_P1 = 73

Are correct. If I try to change the MODE it goes wrong, so I'm assuming, I need MODE0. But I receive random chars.

Changing to: SPI_CLOCK_MASK gives me random chars too.
Changing to any SPI_CLOCK_DIV I receive random chars as well.

I tried to go with a lower clock too (24mhz) but I get the same behavior. Ideas? :/

When you're using Teensy SPI does it enable pullup resistor by default? If yes, what is it value?

01-16-2013, 10:02 PM
Are you using the module from Sparkfun? Or is it from some other source?

01-16-2013, 11:56 PM
Hello Paul,

I'm using nrf24l01+ from a ebay seller but I believe it is basically the same.

Any idea to sparkfun ones? I could try the idea, maybe it will help me.

01-17-2013, 04:37 AM
I think I got this working. I will run some more tests by tomorrow and post here an update.

For now, I can say that I'm using on MirfHardwareSpiDriver.cpp


Tested with: SPI_2XCLOCK_MASK (default value) and SPI_CLOCK_DIV4 and SPI_CLOCK_DIV2.

I think it was an issue with the data rate.

PS: I'm using Mirf library with SPI one. Maybe I forget any modifications that I did. Will try with a fresh ide tomorrow.

01-17-2013, 02:02 PM
That is bizarre. Today I'm testing the examples sketches of Mirf library, ping_client and ping_server. Yesterday it wasn't working. Now it is without any bigger changes. The only change that I made was setup the cePin and csnPin
Mirf.cePin = 9;
Mirf.csnPin = 10;

I thought that it could be the wires, but after all connections I tested then with a multimeter (continuity test?) and everything was ok. So I have no idea what changed. Maybe some neighbor or homie has something that works on the same specific channel or some kind of interference.

So if somebody has an idea what could had changed. Let me know, then I can run more tests and figure out what is going on.

05-18-2013, 04:32 PM
Hello matheusbrat,
did you manage to get a working library for the nRF24L01+ on Teensy 3.0 ? It would be really great if you could share it.
If you need some testers for your ideas and betas, i have 2 Teensy 3.0, 4 arduinos and 8 RF24 modules.

I tried the RF24t.zip you posted in another post, but no success.


05-18-2013, 04:59 PM
Hey benkuper,

I was working on a library to node communications on top of NRF24L01+. My protocol work on top of maniacbugs RF24 library.

The NRF24L01+ library that I was using can be found:

Sadly, my Teensy has gone (died) and the shipping costs are kind of prohibitive. I will be back working on teensy when I find somebody to bring the teensy from US to Brazil for me.

Anyway, if you need some help, please drop me a line. I will be glad to help.

Best regards,

05-18-2013, 07:05 PM
Wow, you are very fast !
Thanks for your answer and sharing your lib, i didn't get to find it elsewhere.

This looks very promising !
I tried to get it working, i see that with 2 arduinos there is a connection made (however i can't understand what actually happens).

Could you explain how your library works ? (or if you did some doc, i can read it before)

When i try to replace the station arduino with a teensy, i get nothing in the Serial console and the communication stops working, same result with Teensy as master and Arduino as station...
I am wondering if i got the wiring right on the Teensy, could you help me with that and explain what is your wiring ?
Currently my wiring is (on the Teensy 3.0):
-SCK on the pin 13
- MOSI (DIN) on the pin 12
- MISO (DOUT) on the pin 11
- CSn on the pin 10
- CE on the pin 9
- 3.3V on the 3.3V pin of the Teensy
- GND on the AGND pin of the Teensy

is it right ?

Thanks for the help, have a nice day !

05-18-2013, 08:53 PM
Well the easy way to use is just to get the librf24 outisde of my project and use the RF24 (from maniacbugs) examples.

My library is supposed to have a master station listening to connections when stations connects, it sends a message on a reserved channel, it has a protocol to distribute the ID. When other stations connects there are some logic to decide how will be that nodes parent. and the node can just communicate directly to own parent/own childs. It will create a network. All this to be a network where nodes can connect without any user configuration (to be easy to use by non tech users). The idea in the future is to have multiple types of stations. Where you can just turn it on and start using (it will need a master and to be inside a range of other connected peer).

There is no documentation for now, sorry. I'm trying to find more time to put on this project but right now it is hard to find it.

Looking inside RF24 library constructor on https://github.com/x-warrior/RF24SH/blob/master/librf24/arduino/RF24.cpp
You can see that RF24(ce, csn)

And on https://github.com/x-warrior/RF24SH/blob/master/GenericStation.cpp you can see that I use
radio(9, 10)

So SCK, MOSI, MISO, CSN, CE, 3.3V seems right. But the GND, I'm not sure about what the AGND means. If I record correctly I used the GND pin.

As I told you, I can't go much further than what I still remember since I don't have a teensy right now.

If you have some arduinos around, I recommend to start using the library inside arduino and getting then to communicate, with arduino there is a lot of debug messages. Teensy version doesn't. It was kind of tricky to get mine working.


05-28-2013, 08:59 PM
Hello again
I kept trying and trying without any [positive] result...

I managed to port the printf code to Serial.print so i got the printDetails() function working (tested on Arduino Uno, RedBoard and Fio, all working as expected, Teensy is outputing correctly) but the Teensy is hard to crack :)

I tried mutiple wirings, got back to the original one. I don't know if it comes from the library or the hardware, but when i test the "Getting Started" code, the Teensy (in Receive role) keeps sending "Got payload.. sent response" messages, even when it's the only module connected..

I tried to reproduce this behavior on arduino to see if it came from a wiring problem, and i manage to get this behavior by unplugging one of the following cables (tested one by one) : ground / CE / CSN

The most weird thing is that now that i got some info from the library for Teensy, i tested some plugging / unplugging / swapping pins on the Teensy, and the infos change ! But nothing that makes sense (even if it seems stable, i.e. same cable plugged/unplugged twice = same result).
For instance, i got some times Data rates at 1Mbps or 2Mbps (without changing anything on the code, just plugging / unplugging and rebooting the Teensy), got CRC either on 8bit, 16bit or disabled depending on which cable has been unplugged, etc..

The only thing that makes really sense is the model name : on arduinos, the model name is output correctly ONLY if all the wiring is good and the setup is working (so i can see "nRF24L01+" when it's working instead of "nRF24L01" when it's not working).
On the Teensy, i never managed to get the "nRF24L01+" on the output, so i'm assuming if i can get this model name to get the tiny "+" in the output, it will be good sign..

I'm very lost and very sad !!
The nRF24L01+ combined with Teensy is a really tiny and powerful solution for our project, and we don't really wan't to have to go to Fio or Xbee...

Thanks again,


05-29-2013, 03:57 AM
I got mine to work with the Teensy3.

I am basically using the library RF24Network (https://github.com/maniacbug/RF24Network). Just comment out all the printf related commands in the library files and it works like a charm. I got one to send and another to receive.

It should be straight forward, but feel free to drop me a message if it still doesn't work for you.

05-29-2013, 05:50 AM

That is what I did on mine. Maybe on my work on my library I changed something and I don't remember.


Can you try to do the same as Kian? And have you tried the NRF24L01+ on arduino too? Is it working? I remember that one of mine was 'burned' or something (it wasn't working)

05-29-2013, 09:30 AM
Hello Kian and matheus ,

Thanks for that i will try it today !

Maybe you can upload or send me some photos of a working setup/wiring with the Teensy ? Because i'm not really sure i connect it properly with the Teensy 3.

On arduino, i got them working on Uno, Redboard and Fio without too much problem, so i'm pretty sure the rf modules are not burned down.

Edit : just to be sure, as i got only one teensy for now (i will get more later in the month), a setup with one teensy+rf24 as receiver/sender and an arduino+rf24 as sender/receiver should work, right ? Or is there a need for the 2 rf24 to be connected to the same hardware family ?

Edit 2 : Actually, i got the RedBoard and the Fio working in one way but not the other, tested with all combinations possible : changing modules, changing roles, same result ! the Redboard (Uno fork from Sparkfun) can send data to the Fio, and the Fio receive it. But the data sent back by the Fio is never received by the Redboard. i can see that the printDetails are not the same on the Redboard and Fio (the TX address is different, even if the code is the same).

I'll try and tell you what i got.

Thanks again,

05-29-2013, 12:30 PM
So, i tested the RF24Network lib, as well as the RF24.
I took the time to modify both in order to get more info, and especially the printDetails() function working.
With the teensy on one side, and the redBoard on the other side, nothing is working...

I attached the modified library with the printDetails() working, and a screenshot of my setup.
The Left window (COM9) is the Redboard showing a working init of the RF24 (model = nRF24L01+) and the right window (COM8) is the Teensy3 not working (model = nRF24L01, CRC Length=Disabled, PA Power =PA_MIN... where it should be nRF24L01+, CRC Length = 16Bit and PA Power = PA_HIGH)



Is it possible for you to test this lib with your teensy and tell me what you get in the printDetails ? i added in the helloworld_rx / tx a small code, since it's not possible to see the Serial.print from the setup with the Teensy. You just have to send "d" from the Serial Monitor and it will print the details.



05-30-2013, 03:03 AM
Hi Ben,

I am using this nrf24l01 chip:


And the connecting to my teensy3 is as follows:

Teensy3 -> nrf24l01
Gnd 1. GND
Pin 9 3. CE
Pin 10 4. CSN
Pin 13 5. SCK
Pin 11 6. MOSI
Pin 12 7. MISO
no connected 8. IRQ

Here are my codes for the receiver:

#include <RF24Network.h>
#include <RF24.h>
#include <SPI.h>
#include "printf.h"

// nRF24L01(+) radio attached using Getting Started board
RF24 radio(9,10);

// Network uses that radio
RF24Network network(radio);

// Address of our node
const uint16_t this_node = 0;

// Address of the other node
uint16_t other_node = 1;

byte inByte;

// Structure of our payload
struct payload_t
uint16_t nodeID;
boolean mode;

void setup(void)
// printf_begin();

network.begin(/*channel*/ 90, /*node address*/ this_node);

void loop(void)
// Pump the network regularly

if (Serial.available())
inByte = Serial.read();

payload_t payload = { inByte, 1 };

RF24NetworkHeader header(/*to node*/ other_node);

bool ok = network.write(header,&payload,sizeof(payload));

if (ok)

// Is there anything ready for us?
while ( network.available() )
// If so, grab it and print it out
RF24NetworkHeader header;
payload_t payload;
Serial.print("Received from ");
Serial.print(" Mode: ");


05-30-2013, 09:45 AM
Mat and Kian, you are the best !
Indeed, i had a wiring problem ! and maybe a software problem too...
So now i got the Teensy printing the good model number and communicating ! well, almost :)

I still have a problem but it seems to be from the Redboard.

I made some tests and each one is getting me to the same result : All the tests are with the sketch you posted above, which seems to work both for the sender and receiver - just swapping the this_node and other_node variables -, right ?
Redboard -> Fio : Fio receives the messages, but Redboard marks "failed" (i guess Fio didn't sent the acknowledgment)
Fio -> Redboard : Redboard doesn't receive and Fio marks "failed"
Redboard -> Teensy : Teensy receives the messages, but Redboard marks "failed" (same as Fio)
Teensy -> Redboard : Redboard doesn't receive and Teensy marks "failed"

I did these tests twice, so i could switch the rf24 modules from the boards. Same result no matter which module is connected to which board.

But there is hope :)

To finish, some questions :
- Currently, the two module are very close to each other, since i'm working on my laptop with both boards connected so there is less than one meter between the modules. Is it potentially a problem ?
- Some times, when the setup is working and i can send data from the Redboard to the Teensy, some packets are not received. Sometimes it's one among many, but sometimes the fail rate is really high (like half packets are not received). Is there something to get better results ?
- When a packet is received, the Teensy logs multiple lines for the same message : with your sketch, when i press one letter and send it to the Redboard serial, the Teensy shows that :
Received from 122 Mode: 1
Received from 122 Mode: 1
Received from 122 Mode: 1
Received from 122 Mode: 1
Received from 122 Mode: 1

The first time i tested your sketch, i received only one message, then 4 message in the row, then 5 (like above). Is it a behavior your had or still have ?

Thanks for this amazing support, when this is all done i will be glad to show you my project and add you to the "thank you very much" part !


05-30-2013, 10:28 AM
Yes, you just need to swap the numbers in the variables "this_node" and "that_node".

I don't think you should have a problem with the range of the modules. I have tested them and they work up to more than 10m.

My results so far are pretty consistent and fairly reliable. I don't have the issue with receiving multiple messages. The failure rate in transmission is probably less than 5%. But I am using a nrf24l01+ with power amplifier and external antenna as the receiver. So it might have contributed to a better reception.

My codes are exactly taken from the examples: RF24Network/examples/helloworld_tx with minor modifications. U should load in the example TX and RX codes and work from there.

06-03-2013, 03:16 PM
Hello there, making good progress with this !

I've got more teensy 3.0 to play with, so i got my hands on it.

I've got 2 Teensy 3.0 talking just fine on one direction, but never the other way, even when changing roles..
I think it's got something to do with the RX and TX addresses. When the TX address is also the RX Address n0 of the second, the message is well sent and well received, but otherwise there seems to be a problem. (like when the TX address is the RX Address n1 of the receiving teensy).

On the picture, the left window (port 8) is the teensy that receives well but can't send right, and on the right (port 22) is the teensy that send ok but doesn't receive anything.
We can see that TX-ADDR of teensy-right = RX ADDR 0 of teensy-left --> works ! whereas TX-ADDR of teensy-left = RX ADDR 1 of teensy-right -> fail !


I know that these addresses are set up with the "this_node" and "other_node" parameters, but how can i test them further and force them to a chosen, "fixed" value so i can digg further ?

Thanks in advance,


06-03-2013, 09:53 PM
This sounds cool for about $4/each.

I wouldn't mind creating a bluetooth->RF relay base station, so that a tablet or phone could connect and then control something over a longer distance with RF.

For bluetooth($8), ($8 for 2x RFN), and a couple of t3's you could be controlling/communicating with something quite far with your tablet's accelerometer, voice-command, etc.

06-30-2013, 10:45 PM
I'm actually working on a full compatible version of maniacsbug RF24 library that works with arduino/due/Teensy3 with printf support (thanks to stevec for his solution). I hope to test it tomorrow so I can post in github.
I think that RF24Network library has been developed for one server and many clients and apparently it's based on RF24 that it's more flexible. I've used mirf but looks like it missed some error check and it's less reliable.

07-01-2013, 03:53 PM
Fantastic sumotoy !
Where are you with that ?

07-01-2013, 08:45 PM
I will test with Teensy 3 tonight, already tested the Arduino side and works, hope to post a link later. I want to keep the full compatibility so I'm find a way to modify examples as less it's possible, but unfortunately actually some small change it's needed. I just added an option in the config file to disable completely, during compilation, any printf call so the final code will be much smaller and a new function that test chip without use any printf.
Maniacsbug done excellent work for this chip but probably he's quite busy and it's not updated recently. I found many forks and loosed a lot of time to figure out timing issues since this chip come in 3 different variations and there's an unknown quantity of compatible ones.
I buy 5 of this cards (+ variation) for less than 1 dollar each just 1 week ago...

07-02-2013, 05:44 PM
Very cool,
i' looking forward to test it !

08-20-2013, 04:21 AM

Hello! Is anyone still interested in these NRF24L01+ modules with the Teensy3? The pricing of these is very, very intriguing and people seem to love them from a technical standpoint because of their ease of use and special features. The most interesting (and recently updated) software I have seen for the Teensy is here (https://github.com/x-warrior/RF24SH), but he doesn't say if its for the Teensy2 or Teensy3 (maybe it doesnt matter?)

Paul, what is your recommendation for a low-cost zigbee-esque, xbee replacement type solution?

08-20-2013, 04:40 AM
Frenchy... are you looking for the Zigbee protocols, or just 802.15.4 simple messages where you don't even have to have a PAN coordinator (it's an option). Zigbee is all about mesh routing at the network layer. XBee series 1 are non-Zigbee; series 2 are zigbee-only.
Digimesh is a good alternative to Zigbee - works better.

Most simple RF comms in hobby-land can be done with series 1 and no zigbee- far simpler. And series 1 has the built-in firmware to do I/O and data acquistion, recurring, without an attached microprocessor at the sensor end.
there is no equivalent to the XBee as above, where you have that firmware free, already written.
The XBee Pro modules have 60mW vs. 2mW for the non-Pro. But a gain antenna on one or both ends of the link can offset. Battery life is limited by the receiver rather than transmitter - except when you use a very chatty protocol like Zigbee.

Atmel's 802.15.4 is the product previously known as Meshnetics. Not well documented/supported, IMO. Perhaps OK for high volume OEMs.

Anaren has modules, using TI's CC2530, but they are hardware only. you're DIY for all firmware, and serial port/SPI interface is a problem for small quantities.

This is in the context of 2.4GHz. In the US, there are a few 802.15.4 and more yet proprietary modules for 902-928 unlicensed. In the EU, that has to be 868MHz.

08-20-2013, 05:31 AM
Thanks for the answer and the question! Honestly I was not looking for the Zigbee protocols nor 802.15.4 at the time of my inquiry...

Stage1 = I was just thinking about a low latency way to wirelessly send sensor info from Teensy3/RF to RaspberryPi/RF. An immediate application that I would like to build very soon is a Teensy3 with a microphone inside of a timpani drum sending amplitude information at a reasonable rate with *hopefully* 10ms latency. I was hoping a general purpose 2.4GHz serial link would suffice. Those NRF24L01+ modules can be had for approx US$2 which makes for a nice wireless serial link at a pricepoint way below the Zigbee stuff. Regarding battery, I can afford to run one power cable into the Timpani...therefore no battery necessary....what I wanted to avoid, however, was various signal cables going in and out (I will be sending other low latency data back to the timpani also).

Stage2 = I think you are bringing up a good point though... after I get one node talking, it is only a matter of time before I want a network of nodes talking. Something tells me Zigbee's meshability will be very bad for guaranteed low latency traffic. Also, I was reading that the NRF24L01+ supports multiple pipes of data, so this might be worth me looking into for several low latency serial links.

I need to spend some time with the NRF24L01+ datasheet to understand the possibilities/limitations better.

08-20-2013, 05:38 AM
I have a Raspberry PI - so you're planning to put an Xbee it the RPi's serial port? I fiddled with that once. In my job, I did a very large/complex Python program (not on the RPi, but similar python).

If you have point to point links, no relay/repeater (meshing), then I'd suggest avoiding the complexity of Zigbee and just use the XBee binary API and a star topology. Don't even need a PAN coordinator; all nodes can be end nodes. And use the 64 bit addresses rather than the DHCP-like 16 bit addresses.

meaning you need one A/D sample every 10mS? In 2.4GHz, there is a lot of wifi you'll be competing with, in most spots.

08-23-2013, 04:57 PM

Hello! Is anyone still interested in these NRF24L01+ modules with the Teensy3? The pricing of these is very, very intriguing and people seem to love them from a technical standpoint because of their ease of use and special features. The most interesting (and recently updated) software I have seen for the Teensy is here (https://github.com/x-warrior/RF24SH), but he doesn't say if its for the Teensy2 or Teensy3 (maybe it doesnt matter?)

Paul, what is your recommendation for a low-cost zigbee-esque, xbee replacement type solution?

Hey Frenchy,

I'm the one that is coding the RF24SH library. It is for Teensy 3 version, RPi, Arduino . Sorry about the lack of information. I just received your e-mail and replied it, now I'm checking the Teensy forums. Since my Teensy 'burned' I'm not able to test it anymore.

Recently I add to RF24SH, a variable message size using templates, more complex examples... for now, I'm kind of stopped thinking how to move forward with it, there is a lot of problems on a tree network that is hard to solve with small amount of memory.

The RF24SH library, has the RF24 library adapted to Teensy, RPi and Arduino, so if you need something simpler you could extract the RF24 library from RF24SH and use it directly.

Best Regards,

08-23-2013, 05:25 PM
Thank you for your reply! I will check your modified RF24 library again on Monday. Can you tell me, did you comment out all of the diagnostic printf statements or did you change them to use some other serial print method which Teensy3 understands? Thanks!

08-23-2013, 05:42 PM
Yes, I commented all teensy 3 rf24 printfs. Sorry.

Gunnar Oledal
07-17-2015, 04:16 PM
Latest Teensy libraries have printf available.
Call it with

So. Using the maniacbug RF24 library is as easy as doing a find & replace of printf to Serial.printf


11-05-2016, 11:18 PM
Assay the library RF24 (https://github.com/TMRh20/RF24) at teensy 3.6 and there is no communication between the transmitter-receiver.

code transmitter(teensy 3.6)

#include <SPI.h>
#include <nRF24L01.h>
#include <RF24.h>

RF24 radio(9, 10);

const byte rxAddr[6] = "00001";

void setup()

SPI1.beginTransaction(SPISettings(8000000, MSBFIRST, SPI_MODE0));

radio.setRetries(15, 15);


void loop()
const char text[] = "Hello World";
radio.write(&text, sizeof(text));


code receiver(arduino mega)

#include <SPI.h>
#include <nRF24L01.h>
#include <RF24.h>

RF24 radio(7, 8);

const byte rxAddr[6] = "00001";

void setup()
while (!Serial);

radio.openReadingPipe(0, rxAddr);


void loop()
if (radio.available())
char text[32] = {0};
radio.read(&text, sizeof(text));


The problem is that it does not displays nothing in my serial port.

11-06-2016, 12:01 AM

You probably need to provide a little more information. Like how do you have the RF24 hooked up to your Teensy 3.6? Your program looks like it is doing some initializing of SPI1, but have no idea of that library directly support SPI1 or not ...

Also unclear from your description if your Arduino mega receiver has worked to talk to a another one or not...

11-06-2016, 12:08 AM
KurtE just use the spi0 and works fine.
In spi1 why not working;

11-06-2016, 12:32 AM
Because in the library there would have to be stuff in place that would allow it to call SPI1.transfer instead of SPI.transfer...

Unfortunately there is no base class for SPI and SPI1 that allows you to pass in which one you wish to use, so code has to be setup to handle it.

For example as I mentioned in my Well Monitoring thread, I hacked up the radiohead library for the RFM95 to allow me to do it...

Likewise earlier I made a new library for myself (SPIN), which created an abstract SPIN class and then made subclasses for the main SPI, SPI1 and SPI2 and then made a version of ILI9341_t3 library which allowed me to pass in a SPIN object so I could use any of the busses...

Hope that helps.


11-06-2016, 10:30 AM
I understood KurtE,thank you very much.

03-16-2017, 12:06 PM
This code works on the arduino uno but not on the teensy 3.2 The OLD Display works. Do you have any suggestions? The RF24 is from Maniabug

#include <SPI.h> // Comes with Arduino IDE
#include <RF24.h> // Download and Install (See above)
#include <Wire.h>
#include <Adafruit_GFX.h>
#include <Adafruit_SSD1306.h>
#define OLED_RESET 4
Adafruit_SSD1306 display(OLED_RESET);
RF24 myRadio (9, 10); // "myRadio" is the identifier you will use in following methods
byte addresses[][6] = {"1Node"}; // Create address for 1 pipe.
float dataReceived; // Data that will be received from the transmitter
float temperature;
void setup() /****** SETUP: RUNS ONCE ******/
display.begin(SSD1306_SWITCHCAPVCC, 0x3c); // initialize with the I2C addr 0x3C (for the 128x64)
myRadio.begin(); // Start up the physical nRF24L01 Radio
myRadio.setChannel(108); // Above most Wifi Channels
myRadio.setPALevel(RF24_PA_MAX); // Uncomment for more power
myRadio.setDataRate(RF24_250KBPS); // Fast enough.. Better range
myRadio.openReadingPipe(1, addresses[0]); // Use the first entry in array 'addresses' (Only 1 right now)
void loop(){
if ( myRadio.available()) // Check for incoming data from transmitter
myRadio.read( &dataReceived, sizeof(dataReceived) ); // Get the data payload (You must have defined that already!)
temperature = dataReceived;
display.setCursor(20, 0);
display.setCursor(20, 7);
display.println("in degrees C");
display.setCursor(40, 20);

03-21-2017, 12:37 PM
@OE8PCK - I see you've posted essentially the same question 3 times on 3 different thread, all within a several hours of each other. Which should I try to answer? And which get left unanswered for people to find in the future? I'm going to post this same reply on all 3 locations. Please, if you reply, keep it all on 1 thread, ok?

First, look at this thread where a similar problem was recently solved.


The code originally written for Arduino Uno prints all the info too quickly, before you can open the Arduino Serial Monitor. Read that thread for the solution, and more followup about things needed to make this really work communicating between 2 boards.

03-21-2017, 01:06 PM

@OE8PCK - I see you've posted essentially the same question 3 times on 3 different thread, all within a several hours of each other.

OE8PCK or matheusbrat ?

03-24-2017, 09:33 AM

OE8PCK or matheusbrat ?

Sorry for the confusion