Using nRF52-DK, Is there an example of a Star topology?

[asha]

Hi,

We bought 3 nRF52-DKs (based on nRF52832 and PCA10040 V1.2.1). We compiled, built, and flashed the systems with several provided examples from nRF5_SDK_14.1.0_1dda907 including ble_central, ble_peripheral, and IoT examples like udp and coap. For the IoT examples we used Raspberry PI as a gateway to our cloud.

Now we would like to create a "star" network where one nRF52-DK is running ble_peripheral, another running IoT udp Client that is connected to cloud via the Raspberry PI, and another running IoT udp Server. I was trying to find and example on your website and I could not. Is there an example like this? Like below,

nRF52-DK peripheral -> nRF52-DK IoT udp client -> Raspberry PI->Cloud->nRF52-DK IoT udp Server

Or is there an example where one nRF52-DK is running ble_peripheral and another running IoT udp Client ? Like below,

  nRF52-DK peripheral -> nRF52-DK IoT udp client 

Any help/suggestions would be very much appreciated.

Thanks, Asha

[endnode]

Sorry but you are mixing layers in the way that there is no really good answer. By "Peripheral" you mean GAP Peripheral role as defined in BLE since v4.0? How that corresponds with IoT UDP client (which has nothing to do with BLE spec as there is nothing like this so I assume you run it somewhere on APP layer - and probably with several more SW layers in between)?

If you stay BLE world for a while then indeed star topology is basic use case of GAP Central device in the middle and whatever number (in older stacks typically up to 8, with today best stacks you should be able to operate 20 and more connections in parallel) of GAP Peripheral devices around it, there is examples\ble_central\ble_app_multilink_central example in nRF5 SDK an more.

[endnode]

To be precise I have no clue why you mix all that IoT and UDP and COAP into the game;) What is the purpose of the nRF52 DK in your demo/app? Should it connect over BLE directly with RPI (don't know if that supports BT LE out of the box) or should it only bridge some gap over BLE to another nRFx board and that is attached to RPi over some wires? In every case you can build your BLE app to bridge 5-50 meters and transport whatever data you need and then o higher layer get these data and upload/download them from /to "cloud" through some app running in your Linux box (let it be RPi) over whatever sexy protocol. This is how most of the "IoT" use cases can be solved easily (and actually should be solved from my point of view but I'm probably too old fashion).