Trouble analysing Mesh test results.

RE: Trouble analysing Mesh test results.

Bjørn Kvaale — Fri, 04 Jan 2019 13:30:40 GMT

Hi Jan,

That's a good question. You are correct that messages with a TTL of 0 or 1 do not get relayed (network.c, mesh sdk v3.0.0):

What kind of unicast messages are you sending? Are you using generic_onoff_client_set_unack() or generic_onoff_client_set()?

What retransmit count have you chosen for these connections? The standard one? I guess this count has remained constant throughout, correct?

How big is the payload you are sending? Can everything fit in a 11 byte packet?

Also, have you set this network up with the nRF Mesh application? Which mesh sdk version are you currently using?

RE: Trouble analysing Mesh test results.

Jan — Wed, 02 Jan 2019 14:52:03 GMT

Hi Bjørn,

Yes, the purple value is the average of both connections. Between node 0 and 2 was approx. 4 meters and 16 meters between node 1 and 3.

I do understand why the percentage goes up for Time to Live (TTL) values 2 and 3.

However, I don't understand why there is a difference between TTL 0 and TTL 1 for the "0 to 2" connection. Is there an explanation for this? Is there possibly a difference between receiving or sending a message with a TTL of 0 or 1?

Best regards,

Jan

RE: Trouble analysing Mesh test results.

Bjørn Kvaale — Wed, 02 Jan 2019 14:34:28 GMT

Hi Jan,

Is the total purple value the average between Node 0->2 & node 1->3? How far apart are nodes 0 & 2 & nodes 1 & 3? Could it be that node 0 is relaying some of the unicast messages via 1 or 3 to node 2 (hence the better results for TTL 2 & 3). It seems that there is a wall between nodes 0 & 2, so this may explain the better results (no wall between nodes 1->2 & 3->2).

Kind Regards,

Bjørn