Get Softdevice schedule for connections

[Marius Heil]

Hello,

is it possible to get the schedule that is used internally to communicate with connected BLE devices? I have a bunch of data that I want to send to connected nodes and I want to send it as timely as possible. What is the recommended method to queue multiple packets so that they get sent out at the next connection event? I want to send multiple packets to Is it possible to configure the size of the application transmission buffer? I can not seem to find much documentation about this.

Marius

[Stefan Birnir Sverrisson]

Hi

Perhaps what you are looking for is the radio notification mechanism? With radio notifications, the softdevice will give the application an event before a BLE connection event and/or after a BLE connection event, see this thread which also includes an example. If you start the radio notification before starting advertising you will also get radio notification events before and/or after advertising events.

[Marius Heil]

Hello,

I know about the radio events, but how can I find out which connection will be processed in the radio event? If I have 4 connected peripherals, I must queue the right data for this peripheral. But how will I know at which time which peripheral is connected? I am working with the SD130, so I also have a central connected.

[Stefan Birnir Sverrisson]

Thank you for the clarification. I think I understand your question better now.

It is currently not possible to know what link is currently being serviced. I do however aggre with you that this would be a useful feature for the radio events, i.e. to include parameter that indicates which connection is about to be serviced. I have reported this as feature request for future softdevice version.

[Marius Heil]

Thanks a lot, that would be helpful. It would be nice to have the type of radio event: advertisement, scan, link establishment, and for connection events, probably the connection handle. Or maybe an interface that polls the current schedule. This would be great as well, getting a table like this: In 124 µs - connection event with conn_handle 2 in 2500 µs advertisement packet ....

[Stefan Birnir Sverrisson]

Thanks for your ideas. We will use them as input for the design of this feature.