About IV Index Of Mesh3.10

[listenYes]

Hi

In the SDK, Replay_Cache_Entries is assigned a value of 40, which means that Replay_Cache can only process 40 unicast messages.
That limits the maximum number of unicast in a network to 40.
Replay_Cache will not be emptied unless it is powered back on.

If a Node has 8 elements, there are 8 unicast. That network can only have 5 Nodes.
Is this a problem? ? ?

I don't think Replay_Cache should be used as a condition for the IV Index update.
Because the IV Index update condition is judged by the time.

[Marjeris Romero]

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

[BubDev]

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.

[Joakim Jakobsen]

Hi. 

I don't really understand your question. 

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

Best regards, 
Joakim