RE: nRF Mesh

tesc — Thu, 09 Jul 2020 15:38:27 GMT

Hi,

1. Transition time and delay: Those are as defined in the Mesh Networking Specifications. Simply put, the state will be set after delay, and the state will "fade" from the current value to the new value over the transition time. With "delay" it is for instance possible to send several messages that all tell the receiving node to switch state at the same time, so that if any one of the messages goes through the node will change state at that time. Useful for instance if you have multiple light bulbs in a large hall, and want all of them to turn on or off at the same time.

2. The publish_timeout_cb member is a callback function that will get called every time the model is to do a periodic publication. Periodic publication is a feature where the model is configured to publish at a set interval. For reference on how this is used in code, see the documentation for the Simple OnOff model, which serves as a walk-through of how to implement a custom model.

3. The relay feature is core part of the stack, and is enabled in the default project configuration. In an nRF5 SDK for Mesh project, you enable it by defining MESH_FEATURE_RELAY_ENABLED as 1. This is in the default configuration file nrf_mesh_config_core.h. Defines from that file can be overridden in e.g. nrf_mesh_config_app.h. In Bluetooth mesh, packets automatically gets resent by relay nodes, so provisioning relay nodes into your network is basically all that is needed for packets to be sent through intermediary nodes when needed. There is one more thing to think about, and that is that each packet is sent with a time to live (TTL), which defines the maximum number of "hops" that the packet can take through the network. You can define a default TTL compile time, and in a live mesh network you can configure the TTL for each element's publications.

Regards,
Terje