-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how to support 8 pipes (on nRF5x devices) #201
Comments
There is still some reserved space in the network sys codes, so we could add a |
I've given this some thought and with the increase in code size etc, I'm not sure its a good idea. RF24Mesh will still compile and run on ATTiny, even though you can't do much with it, and I would like to keep it that way. I think on the third point, it might be kind of difficult to support a mixed network if some use differing amounts of pipes. It would be way easier to either have an nrf24l01 or nrf52840 network. |
So, what if all code that supports 8 pipes is |
That would work. It would be interesting to get it working with a mixed network but again not sure what it would take.On Jan 3, 2023, at 11:31 AM, Brendan ***@***.***> wrote:
It would be way easier to either have an nrf24l01 or nrf52840 network.
So, what if all code that supports 8 pipes is #ifdef out? That way the same lib cab be used for different networks.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
I think we have the first two items picked off, its just a matter of if we want to support mixed networks. I don't really want to lol. |
You already convinced me that mixed networks is a venture more risky than it is worth. I (& likely other long-time users) would be comfortable with an |
Concerning future ventures with the nRF5x ESB, I was thinking that 8 pipes shouldn't be too hard to support.
x <= 5
presumption about 6 pipesThe text was updated successfully, but these errors were encountered: