I’ve been diving into the world of Periodic Advertising with Responses (PAwR) using the nRF52833 chipset, and I must say, it’s been an enlightening journey. PAwR seems like a game-changer for low-power, high-efficiency communication in IoT devices. However, I’ve encountered some intriguing challenges that I’d love to discuss with the community.
First, I want to share my setup. I’ve been working with two devices: one acting as the PAwR advertiser and the other as a listener. The advertiser sends periodic subevents, and the listener is supposed to sync and receive these events. The goal is to ensure seamless communication between these devices while maintaining low power consumption.
Here’s where things get interesting. While the basic functionality works as expected, I’ve noticed some peculiarities. Occasionally, certain subevents are missed, which I understand can happen due to timing or interference. However, what’s puzzling is when multiple consecutive subevents are missing for extended periods, and then the sync resumes without any issues. This instability in the sync interval is something I’d like to explore further.
My main question is: Is it fully supported on the nRF52833 to perform PAwR while also synchronizing to another PAwR device as a listener (non-responder)? Are there any known limitations or timing conflicts that could explain the missing subevents? I’d appreciate any insights or guidance from those who might have encountered similar challenges.
Additionally, I’d love to hear about others’ experiences with PAwR. Have you faced similar issues? How did you resolve them? Are there any best practices or configurations that ensure more stable communication?
Let’s keep the conversation going! I’m excited to learn from the community and share my findings as I continue to explore the capabilities of PAwR with nRF52833.