Is it possible to configure a device as a standard BLE server and a PAwR node? Other PAwR limitations?

[rbmarcus]

I am currently working on two separate sample repositories: one for a standard 1:1 BLE connection with a mobile phone and another for a PAwR node that transmits data alongside other nodes to a Nordic MCU acting as a gateway. My goal is to eventually merge these two repositories into a single functional program capable of handling both tasks.

Before proceeding further with development, I want to evaluate the limitations of PAwR and have a few key questions:

1. Is it possible to enable both standard BLE and PAwR functionality on a single device at runtime? Ideally, the device would automatically switch between modes based on the connected client, without requiring manual intervention.

2. If both modes are supported, can they operate concurrently? Specifically, can the device participate in a PAwR train while simultaneously maintaining a 1:1 connection with another device?

3. Are there potential issues with running multiple PAwR trains in the same location? For example, if one gateway setup cannot accommodate the required number of nodes due to bandwidth limitations, would adding a second gateway and PAwR train nearby lead to packet collisions?

[Hung Bui]

Hi Rbmarcus, 

I would suggest you to take a look at our samples in the nRF Connect SDK. I also have a blog here that maybe useful for you:  Periodic Advertising with Responses (PAwR): A practical guide 

Regarding your question: 

1&2: A device should be able to do both at the same time. As far as I can see there is no problem doing multiple roles PAwR and ordinary BLE connection. 

3. It shouldn't be a problem. The APs (Access Point) will transmit at different channel and at different times. The challenge is when you want to connect the two APs or try to make them work as one single network. There is no definition in PAwR on how you connect multiple AP.