One sender with multiple receiver
It is possible to connect 10 devices to 1? I 'll need to communicate with many nRFA24L01 (Maybe more than 10 devices), is that possible?
One sender with multiple receiver
It is possible to connect 10 devices to 1? I 'll need to communicate with many nRFA24L01 (Maybe more than 10 devices), is that possible?
Shure.
Let all 10 nodes deliver their data to the 1.
Whandall:
Let all 10 nodes deliver their data to the 1.
Doesn't the OP want to send from 1 to 10?
@Kakaroto, if you just need one-way communication make all your nodes listen on the same address and turn off the auto-acknowledgement feature on all the devices.
If you need two-way communication things are a little more complex and we need to know more about your project. What sort of things are the 10 nodes, and how often is communication required.
I understand "one central node collecting data <-> many nodes gathering data".
Whether the nodes are polled or share a single delivery channel is not connected to
acknowledgements or acknowledgement payloads.
Collisions can be detected and fixed by software retries.
If you have to gather the data with a guaranteed latency, polling would be better,
if the gatherers would like to sleep, a shared channel would be better.
It depends on the application.
Check out this project unless you want to do all the code as an exercise.
Should get you up and running quickly to test at least....
Whandall:
I understand "one central node collecting data <-> many nodes gathering data".Whether the nodes are polled or share a single delivery channel is not connected to
acknowledgements or acknowledgement payloads.
Collisions can be detected and fixed by software retries.If you have to gather the data with a guaranteed latency, polling would be better,
if the gatherers would like to sleep, a shared channel would be better.It depends on the application.
With respect, I wonder if that is meaningful for a newbie?
The words you have in quotes are not from the Original Post.
And my comment about disabling the autoAck featiure was to prevent all 10 RX nodes sending an ACK at the same time which would just garble everything and prevent the Tx from recognizing a valid ACK. That sort of multiple collision cannot IMHO be solved by retries. I suspect you are thinking of a different approach from what I suggested.
...R
Robin2:
And my comment about disabling the autoAck featiure was to prevent all 10 RX nodes sending an ACK at the same time which would just garble everything and prevent the Tx from recognizing a valid ACK. That sort of multiple collision cannot IMHO be solved by retries. I suspect you are thinking of a different approach from what I suggested.
That is only a problem if the clients use the same address for listening.
With non-slave nodes all have different addresses and send to the address of the master.
Ack works perfectly with that setup and collisions can be handled with software.
Whandall:
That is only a problem if the clients use the same address for listening.
Which is what I suggested in Reply #2.
Let's wait until we hear from the OP before we try to solve all the problems.
...R