This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

how to test a mesh SDK?

Hello, I studying nRF51 SDK for mesh. I have a nRF51822(PCA10028) is a Client, and three Server(two nRF52832-PCA10040, a nRF51822-PCA10028). I did the same way with Light Switch Demo. So, I controlled LED on the Client board, but I think it is a broadcasting not mesh. each server board can not controlled at the same position(distance). Is this mesh?? If i was wrong, how to do it? Also, how do you distinguish between mesh and broadcasting when testing a mesh?

Parents
  • Hi,

    This excerpt from the BLE Mesh SDK documentation on network topology might clear things up a bit:

    Bluetooth Mesh is a broadcast-based network protocol, where every device in the network sends and receives all messages to and from all devices within radio range. Source

    Also see this section about relaying:

    Bluetooth Mesh expands the range of the network by relaying messages. Any mesh device may be configured to act as a relay, and no dedicated relay devices are needed to build a network. Every device acting as a relay will decrement the Time To Live (TTL) value in received messages and forward them if the TTL is two or higher. This undirected relaying is referred to as message flooding and ensures a high probability of message delivery, without requiring any information on the network topology. The Mesh Profile Specification does not provide any routing mechanisms, and all messages are forwarded by all relays until the TTL value reaches zero. To avoid messages being forwarded by the same relays over and over, all mesh devices maintain a message cache. This cache is used for filtering out packets that the device has already handled. Source

    In the Light Switch example all the nodes are configured as relays.

    Does this answer your problem? If not, please add some more details about your application.

    Ketil

Reply
  • Hi,

    This excerpt from the BLE Mesh SDK documentation on network topology might clear things up a bit:

    Bluetooth Mesh is a broadcast-based network protocol, where every device in the network sends and receives all messages to and from all devices within radio range. Source

    Also see this section about relaying:

    Bluetooth Mesh expands the range of the network by relaying messages. Any mesh device may be configured to act as a relay, and no dedicated relay devices are needed to build a network. Every device acting as a relay will decrement the Time To Live (TTL) value in received messages and forward them if the TTL is two or higher. This undirected relaying is referred to as message flooding and ensures a high probability of message delivery, without requiring any information on the network topology. The Mesh Profile Specification does not provide any routing mechanisms, and all messages are forwarded by all relays until the TTL value reaches zero. To avoid messages being forwarded by the same relays over and over, all mesh devices maintain a message cache. This cache is used for filtering out packets that the device has already handled. Source

    In the Light Switch example all the nodes are configured as relays.

    Does this answer your problem? If not, please add some more details about your application.

    Ketil

Children
No Data
Related