Chris_v:
But why the 7?
The seven is just a value that would never be set by available, so it can be used to detect
a malfunction of the "retrieve the pipe where the packet was received" process.
As it is a local variable it should have an explicit initialization, as there is no automatic initialization.
Which value would you use?
Chris_v:
"(Oh, there is a packet, lets read two packets and suppose the first came from TX 1,
which can not send anything because nobody listens to its pipe address,
then TX 2 data gets overwritten by junk because there is most likely only one packet available.)"describes what my codes does, right?
Yes. The strategy seems not very sensible IMHO.
Chris_v:
"The addresses are still invalid for usage in pipe 1 and 2 to 5."I do not understand why you use "still" and also why are invalid.
Also, why do you say "1 and 2 to 5" and not "1 to 5.
I elaborated on "00001", "00002" being illegal in the pipe 1 and one (or more) of the pipes 2 to 5 setup,
but ok, I will try to explain it again.
The NRF24L01 has two 5 byte RX registers holding the full addresses used for pipe 0 and pipe 1.
There are four 1 byte RX registers holding only the LSB of the address, the upper part comes from pipe 1.
If you only want to use two pipes, you are free to use any address you like, just use pipes 0 and 1.
If you want to use more than two pipes you are forced to use at least one of the 1 byte registers,
pipe 1 has to be used anyway because it supplies the base for the short registers.
So you have to use (at least 2) addresses that only differ in the lowest byte.
If you use strings for the addresses, the lowest byte is the first.
"00001" and "00002" for example only differ in the last byte, which makes them unuseable.
"10000" and "20000", "1Node" and "2Node", or "A<---" and "B<---" would work.
We talked about this before, and after requesting your current code you presented bad group addresses,
that made me use "still".
Did you understand the code snipped I provided to you?