@StevenCellist Well, if the while loop runs too fast for your eyes, then of course you can slow it down by sleeping longer. And the radio.print details only print once after configuration and before the while loop. So after the printdetails, it is the while loop that causes trouble. I think we need to look at the python library to see if we can isolate some relevant sections to narrow down the trouble making guy.

Oh I understand why my time.sleep(100) seemed to stop the program.. In Arduino, the delay is in milliseconds so I thought 100 ms would be a good delay, but I now remember that in Python that would be 100 seconds hahah

I thought my program didn't function anymore when I added the delay

Have you tried using the radios yourself yet? I am curious if you have the same problem

Ha, so you have made some progress. My toys only arrived yesterday. I have not open the package yet. Usually I need to make a test plan before trying it, might take a couple of days, so in the mean time you very likely find more careless mistakes. I have not played this nRF24 before. My only experience is RF12 which is 433MHz. So I need to read the datasheet before I read the programs.

Now I have inserted the python library into my learning notes below. I skimmed it and found it, as I mentioned some days ago, very structured, so it should be "easy" to do some troubleshooting. This file now has the python library full listing at the beginning. penzu.com/p/3979e91f

My understanding of libraries is still very small so I don't expect myself to find anything that could cause the trouble but I will read through it when I have some spare time

I did get a warning on my B+ model actually about one of the pins already being in use, but it continued anyway

Which seemed very odd to me since I do not have any other program running

Ah, usually libraries created by the hackers and developers are newbie scary, very messy, and in C/C++ and need to be complied. But if it is a python library, then it is usually 10 times easier to hack. Anyway, don't bother to look at the library for now. Let me take some time to study it and let you know later what I think about it. By the way, I remember the nRF24 GitHub says how to set up for SPI, using source code.

This is what I am worrying, because my Rpi4B has spidev already built in the os, so using the GitHub's spidev setup instructions might crash something. Anyway, I will not tried it. One more thing, I guess you are using two Rpi's. I am a lazy guy and my test plan is as follows: (1) test first nRF24 module on SPI0.0, send mode, (2) test second nRF24 module on SPI1.0 receive mode,

(3) test both modules "at the same time", sequentially (looping), or concurrently (multi-threading multi-processsing). If no luck in (3) then I will try (4) using two Rpi's. It is a over-ambitious project, so I have only 50% confidence! :( PS - Don't try hard to catch up me, I would prefer you to just watch what I am doing, and perhaps ask question along or later. I am going very slowly now, so you need to be patient! :)

That's cool! I have used multiple spidevs before so I should be able to quite follow it but we'll see