TTL - Hop Count

RE: TTL - Hop Count

Joakim Jakobsen — Tue, 21 May 2019 06:37:28 GMT

That is correct.

You can use both a group address or a unicast address for this. When using a group address you can have several nodes subscribing to the given address, i.e the message can be sent to several nodes. Using a unicast address will send the message to one specific node.

Best regards,
Joakim

RE: TTL - Hop Count

Brijesh — Tue, 14 May 2019 11:37:42 GMT

ok so u mean that the health model shud also be assigned a publish address so that it can publish its health status to a specific node.

RE: TTL - Hop Count

Joakim Jakobsen — Tue, 14 May 2019 08:35:29 GMT

Hi.

This should be explained well in the Mesh Specification:

"Health messages are used to monitor states that determine the physical condition of a node."

Note that there is a difference between the health messages and heartbeat messages;
https://devzone.nordicsemi.com/f/nordic-q-a/43625/mesh-heartbeat-vs-health

Best regards,
Joakim

RE: TTL - Hop Count

Brijesh — Fri, 10 May 2019 04:28:55 GMT

so the health model will be useless . Can u please tell me in layman terms what is a health model used for.. I read it sends out some heart beat messages bt i didnt understand to who, does it send that.

RE: TTL - Hop Count

Joakim Jakobsen — Tue, 07 May 2019 09:00:29 GMT

Hi.

The message you send will be broadcasted to all the nodes in range. The message will then be relayed by all of the relay nodes that receives it.
So if you have one node that fails, the other relay nodes should be able to relay the message and find another route to the gateway.

However, if the TTL is set to a minimum (with the shortest path in mind) and any other route has more hops than the TTL allows, then the Mesh will not be able to relay the message to it's destination.

Best regards,
Joakim.