I am evaluating Bluetooth Periodic Advertising with Responses (PAwR) using a NRF52840 Development Board. I am very satisfied with the development environment and the nRF Connect SDK including Zephyr!
I use the Bluetooth soft device stack and toolchain version v2.9.0.
One scenario I am looking at is the following:
1. A node is synced to a PAwR train that consists of (for example) 25 subevents in a period.
2. The node only subscribes to subevent 0 in this train.
3. At a random point in time the node wakes up and decides that it wants to subscribe to all 25 subevents.
When I am testing this scenario, it looks like the first subevent the node receives is always subevent 0.
I would like to know why the node seems to always wait until the next period before subscription of all subevents takes place.
Perhaps there is a logical reason as to why it is designed like this or perhaps my measurements are just wrong.
I look forward to get your input on this!