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

BLE RELAY EXAMPLE

hello support  team

nRF52 DK , Mesh 2.01

I am trying Experimental BLE RELAY example.

1. In first trial I am using 1 RELAY DK  all works well.

2.In second Trial I am using 3 RELAY DK  nothing happens at collector side

Any check list how can debug or check . nRF connect showing no services.

Parents
  • Hi,

    I am a little confused as to what example you are referring to. Are you testing the Experimental: BLE Relay Example from the nRF5 SDK v15.0.0? That is not a Bluetooth Mesh example, it is a Bluetooth Low Energy example. It sets up standard BLE connections, and I suspect if you power on several relays then there is nothing stopping them from connecting to each other in a loop, or something other weird. The reason for that is they simply search for a device with the correct BLE service and connects, and then there is no control of the resulting network topology when having multiple instances in the same area.

    If you want a Bluetooth Mesh network then you should have a look at the examples in the nRF5 SDK for Mesh v2.0.1 instead. Once two Mesh nodes are configured to talk to each other they can send messages over the Mesh network regardless of network topology.

    If you want a network based on BLE, then you must make sure that the relays connects correctly to each other. That means you most likely "hard code" the network topology, so that all communication follows the same path.

    It is hard to tell which one of the above solutions is best for your use case.

    Regards,
    Terje

Reply
  • Hi,

    I am a little confused as to what example you are referring to. Are you testing the Experimental: BLE Relay Example from the nRF5 SDK v15.0.0? That is not a Bluetooth Mesh example, it is a Bluetooth Low Energy example. It sets up standard BLE connections, and I suspect if you power on several relays then there is nothing stopping them from connecting to each other in a loop, or something other weird. The reason for that is they simply search for a device with the correct BLE service and connects, and then there is no control of the resulting network topology when having multiple instances in the same area.

    If you want a Bluetooth Mesh network then you should have a look at the examples in the nRF5 SDK for Mesh v2.0.1 instead. Once two Mesh nodes are configured to talk to each other they can send messages over the Mesh network regardless of network topology.

    If you want a network based on BLE, then you must make sure that the relays connects correctly to each other. That means you most likely "hard code" the network topology, so that all communication follows the same path.

    It is hard to tell which one of the above solutions is best for your use case.

    Regards,
    Terje

Children
Related