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.
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
In Experimental: BLE Relay Example.
1. Is that the relay BLE device able to received Peripheral's data and process the data? When forwarding the data to central.
2. Is those Peripheral devices should paring with Relay Device first? Finally step is relay device paring to central device? If yes that seen not a friendly to normal user.
3. Is that Relay device role is central device?
4. How many Peripheral device can be relay out to central? (MAX)
Hi,
The BLE Relay Example is a multirole example, where the relay acts both as central and as peripheral. It acts as central in order to scan for and connect to a heart rate sensor and to a running speed sensor. It acts as peripheral in order for a collector to connect to it. It relays the heart rate values and the running speed values from the sensors to the collector, without doing any calculations on them.
The relay example can connect to one heart rate sensor and one running speed sensor, and it can be connected to from a collector. Our heart rate sensor and running speed sensor examples connect to one central, which means they connect to one relay only.
If you need more connections than that then you must modify the example. For how to do multiple connections you may have a look at the multiperipheral eample and the (central) multi-link example. The current SoftDevices allows for up to 20 connections total.
Regards,
Terje
Hi, Tesc,
Thanks for you replay.
Actually, I hope my programming device can be as Role Central and Peripheral.
1. When device switch to Role as Peripheral, it could be connected with SmartPhone(Central) and communicate with iOS or Android App.
2. When device switch to Role as Central, I hope device can receiving data from Peripheral and also process the data in local device. I hope this device able to support more than two Peripheral.
I have finished Experimental: BLE Relay Example, this feature seen meet my request, and I have some question.
3. Is that the "running speed sensor" Example will not Advertising the Device Name "Nordic_RSC"? I cann't found on nRF Connect and Sniffer log. (SDK15.0.0)
4. Continuous the Q3, is that the "running speed sensor" Example propose to Hide the Device Name, something like invisible SSID, do not hope the Smart Phone can access into DUT.
5. If I hope we support more than two device, is that possible in this SDK, something like increase NRF_BLE_GATT_LINK_COUNT and add more services.
Hi,
The SDK supports multiple connections, yes. And you can do processing of information received over one connection before sending it on another connection. Also, the peripheral and central roles can work concurrently, which means you can stay connected both as peripheral and central at the same time. Please note that it requires programming from your part, i.e. we provide the SDK with APIs and documentation, and you use that in order to write your application code. We provide examples so that you have a starting point.
I do not quite understand your question 3. Are you wondering how to make sure the sensor connects to the relay and not to the smartphone or nRF Connect directly? Or are you trying an example but you cannot find it on smartphone or nRF Connect?
Regards,
Terje
