• State Verified Answer
  • Replies 2 replies
  • Subscribers 87 subscribers
  • Views 531 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 272912
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF52811 s112 timeslot API for central purposes

Vojislav

Hi,

We have an issue with custom devices in the field that have nRF52811, with s112 programmed. To sort out our issue we need to connect to the nRF52811 that is an advertising and send some commands over NUS to reset the main CPU on the same device. For this to work, we need to reprogram the nrf52811 so it can scan and connect to the devices that have NUS UUID in the advertising packet. 

Problem:
We understand well that S112 is not meant for central role devices, but still, do you think there is a workaround for it, even with some custom API calls, "raw sampling" or similar?

I found this issue opened not that long ago that states scanning on the S110 could be done using timeslot API, so my question is can we also leverage the same API for something more, like connecting to the peripheral device?
https://devzone.nordicsemi.com/f/nordic-q-a/66644/using-peripheral-only-softdevice-with-timeslot-api-for-central-purposes

Best regards,
Vojislav

cc

Parents
  • +1

    Hi Vojislav,

    There is a working example in the very old SDK where we could demonstrate that you can implement an observer using the timeslot API. But implementing the central (that is adding connected feature) using timeslot to this observer is not a trivial job. There are so many timing with connected roles and procedures that needs to be implemented that it will take some time for you to implement it. And I do not know anyone within Nordic who has tried to do that. I would not recommend you to take that path. How big is the application? if it is very small then probably using S140 is the only easier option that i can think of.

Reply
  • +1

    Hi Vojislav,

    There is a working example in the very old SDK where we could demonstrate that you can implement an observer using the timeslot API. But implementing the central (that is adding connected feature) using timeslot to this observer is not a trivial job. There are so many timing with connected roles and procedures that needs to be implemented that it will take some time for you to implement it. And I do not know anyone within Nordic who has tried to do that. I would not recommend you to take that path. How big is the application? if it is very small then probably using S140 is the only easier option that i can think of.

Children
Related
Terms of service