About IV Index Of Mesh3.10

RE: About IV Index Of Mesh3.10

Joakim Jakobsen — Wed, 11 Mar 2020 13:19:03 GMT

Hi.

I don't really understand your question.

Please take a look at the documentation for more information:
REPLAY_CACHE_ENTRIES

Best regards,
Joakim

RE: About IV Index Of Mesh3.10

BubDev — Mon, 09 Mar 2020 13:02:28 GMT

Hello,

Im a little confused on your response. "And not all elements in a node sends unicast messages". Are you talking about clients models? Does this mean I can only have 40 client models talking to each unicast address? What about if I send an acknowledged message to a group that has more than 40 devices in it? I will get a status message from all of the unicast addresses immediately filling up the replay cache.

RE: About IV Index Of Mesh3.10

Marjeris Romero — Wed, 04 Sep 2019 09:30:49 GMT

Hi,

You can increase the REPLAY_CACHE_ENTRIES number when scaling up your mesh network. But keep in mind that the upper limit of the number of nodes in your network will be limited by the size of flash on the nRF52.

And not all elements in a node sends unicast messages, it will depend on your application. If you only use one unicast address in a node with 8 elements you can have up to 40 nodes if your replay cache entries is set to 40. If you use all 8 unicast addresses in a node then you can only have 5 nodes if replay cache entries is set to 40, and if you want to have more nodes you need to increase its value.

Best regards,

Marjeris