Connectable advertising using timeslot api

RE: Connectable advertising using timeslot api

David Edwin — Tue, 05 Apr 2016 02:46:26 GMT

The TimeSlot Advertiser project for the S110 has been enhanced to support a Peripheral over the TimeSlot API. See github.com/.../Advertiser-With-and-Without-Timeslot . There are a few known issues but this is a working link layer role for the Peripheral.

This is currently only available for the nRF51 and the S110 softdevice, however it should be compatible with the S130 and the S132 on the nRF52. It has been tested only on the S110 and nRF51.

RE: Connectable advertising using timeslot api

drk_tg — Mon, 04 Apr 2016 13:35:28 GMT

Sending proper connectable payload isn't problem at all. When I'm sending those packet's I'm unable to connect to my device. Is there any option to combine those packets with softdevice without writing own link layer?

RE: Connectable advertising using timeslot api

drk_tg — Mon, 04 Apr 2016 09:53:34 GMT

I'm familiar with multiactivity example. There is no problem to send non-connectable advertising and periodic connectable advertising however I want to have full control at connectable advertisements (send a certain amount , change tx power after sending each one etc.). Is soft device generating any event after sending single advertising packet?

RE: Connectable advertising using timeslot api

Øyvind Karlsen — Mon, 04 Apr 2016 09:30:20 GMT

Hi,

I suggest that you take a look at using the Timeslot API. You can find documentation on infocenter, a tutorial on initial setup here and finally the multiactivity example.

EDIT: I misread your question as using Radio Notification earlier, the first paragraph was removed for this reason. Connectable advertisements in timeslots is possible.

Best regards,

Øyvind