nRF24 / RF24Mesh

OSI Layer 7 Mesh Networking for RF24Network & nrf24L01+ & nrf52x devices
http://nrf24.github.io/RF24Mesh
GNU General Public License v2.0
422 stars 153 forks source link

250kbps Mesh: Long time to connect #118

Closed rumbero71 closed 5 years ago

rumbero71 commented 7 years ago

I am trying to build up a mesh of sensors where battery consumption and -to some lesser extent- range are of the essence. Mains-powered repeating nodes are possible but to maintain a decent WAF, there should be few and they should be hidden. First of all I set up the mesh with 1MBps. All went well but range was quite poor, about 4 meters with and 5 meters without a wall. Reducing the speed to 250KBps extended the range to a more or less acceptable level, about 7 meters including walls. However, I realized that the nodes took about a minute to connect to the mesh, even when placed right besides the master node. Once connected all was fine. Is there any way to reduce the time needed for connect, any best practices for doing this ?

chriskelman commented 7 years ago

I have had variable success with these devices - when they work they are brilliant.

I find my mesh network (multiple Arduino based sensor stations with nRF24+aerial modules) will manage on Max Rate up to around 70m with immediate connection to the (Raspberry Pi) base station, even when via a 'relay' station. I have used YAGI antennae on some more distant stations with good results.

However at other times, seemingly randomly, various sensor stations will either not connect at all or take a very long time to handshake. Quite often on my system, the base-station network node allocation does not work properly and several sensor stations will end up with the same (base-station) ID, which makes accurate data recording difficult.

I have used various sources of nRF24 modules, most recently from a supplier who guarantees that they use original Nordic chips.

Maybe the combination of counterfeit and original chips is the problem - although I have tried using all original chips without much improvement in reliability.

So, I wish you the best of luck - the technology is tantalising but I have not convinced myself that it is reliable enough to persevere with on my next project.

Hopefully there is someone much smarter than me in this group with some suggestions for my (and your) problems!


From: rumbero71 notifications@github.com Sent: 11 March 2017 07:17:28 To: TMRh20/RF24Mesh Cc: Subscribed Subject: [TMRh20/RF24Mesh] 250kbps Mesh: Long time to connect (#118)

I am trying to build up a mesh of sensors where battery consumption and -to some lesser extent- range are of the essence. Mains-powered repeating nodes are possible but to maintain a decent WAF, there should be few and they should be hidden. First of all I set up the mesh with 1MBps. All went well but range was quite poor, about 4 meters with and 5 meters without a wall. Reducing the speed to 250KBps extended the range to a more or less acceptable level, about 7 meters including walls. However, I realized that the nodes took about a minute to connect to the mesh, even when placed right besides the master node. Once connected all was fine. Is there any way to reduce the time needed for connect, any best practices for doing this ?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/TMRh20/RF24Mesh/issues/118, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKyWpndUzYOch1pDhmEmHmP0_2BL68L8ks5rka_YgaJpZM4MZ0cj.

Avamander commented 7 years ago

Well the easiest way to ensure better transmission distance is using high-power transceivers. You can also try other channels to avoid interference from other 2.4GHz signals and place more nodes between others to repeat. There's not much else you can do. Lowering transmission speed might not be the best as you can see.