mesh publish issues under zephyr

RE: mesh publish issues under zephyr

AndyM — Thu, 05 May 2022 14:47:33 GMT

Started a new ticket for this with more details

https://devzone.nordicsemi.com/f/nordic-q-a/87626/mesh-duplicate-found-in-network-message-cache

This can one be closed

RE: mesh publish issues under zephyr

AndyM — Tue, 03 May 2022 17:49:49 GMT

Update 2

I've been playing with TTL and retransmit count and interval on the publishing nodes

Presently set as follows

count: 7, TTL: 10 and retransmit interval 300 ms, publish period 10 seconds

1 subscriber node , 2 publish nodes: 0x001c and 0x001d

When only 1 node is powered the messages are received by the subscriber without issues

With both nodes powered messages from node 0x001c reach the subscriber at expected intervals, but messages from 0x001d arrive irregularly and infrequently.

With both nodes publishing I see the following messages in the log

00> [00:19:17.349,548] <dbg> bt_mesh_net: bt_mesh_net_recv: rssi -68 net_if 0
00> [00:19:17.349,609] <dbg> bt_mesh_net: bt_mesh_net_decode: 29 bytes: 6858befe9733293e2e245f1f3e972c19533e6b05cabffdae9221544733
00> [00:19:17.349,639] <dbg> bt_mesh_net_keys: bt_mesh_net_cred_find:
00> [00:19:17.349,639] <dbg> bt_mesh_net: net_decrypt: NID 0x68
00> [00:19:17.349,670] <dbg> bt_mesh_net: net_decrypt: IVI 0 net->iv_index 0x00000000
00> [00:19:17.349,700] <dbg> bt_mesh_net: net_decrypt: Duplicate found in Network Message Cache
00> [00:19:17.349,700] <dbg> bt_mesh_net: bt_mesh_net_decode: Unable to find matching net for packet

All 3 nodes are about 15 cm apart

Any ideas?
Thanks

RE: mesh publish issues under zephyr

AndyM — Tue, 03 May 2022 01:14:29 GMT

Update

Even with TTL set to 100 in both publishers the packets from one of the nodes arrive inconsistently

Any suggestions are much appreciated.

RE: mesh publish issues under zephyr

AndyM — Mon, 02 May 2022 23:37:09 GMT

OK, answering my own question

It appears that the issue was due to low TTL that I set for publishing. It was set to 0 and sometimes to 5

I set it to 100 and now the subscriber node reliably sees all publishers. In my network topology multiple publisher nodes must reach a single subscriber node so it probably makes sense for the TTL to be set higher.. Any suggestions on the TTL size in my case are appreciated.