Why is S132 BLE GATT Notification bandwidth spec'd as 16kbps not 24kbps?

RE: Why is S132 BLE GATT Notification bandwidth spec'd as 16kbps not 24kbps?

John C — Wed, 06 Dec 2017 16:55:24 GMT

Thank you for this explanation.

RE: Why is S132 BLE GATT Notification bandwidth spec'd as 16kbps not 24kbps?

Petter Myhre — Wed, 06 Dec 2017 16:44:57 GMT

In terms of radio time you will fit 3 packets pairs (one full, one empty) in 2.5 ms, but the 2.5 ms will not be utilized completely for transmitting/receiving. In it you also have scheduling of timing events, processing of potential radio traffic, switching/re-configuring of radio hardware, and so on.

Also, after two packets pairs have been exchanged the SoftDevice will check if it is able to exchange a complete packet pair (both ways), if not it, will not try.

The numbers in the spec are measured values, so this is what you should expect to see. If you see something else, please let us know.

RE: Why is S132 BLE GATT Notification bandwidth spec'd as 16kbps not 24kbps?

John C — Wed, 06 Dec 2017 13:23:43 GMT

Yes, I did mean 16kbps (edited question to fix). Thanks for checking, these details are important to us as we will be pushing on the limits.

RE: Why is S132 BLE GATT Notification bandwidth spec'd as 16kbps not 24kbps?

Petter Myhre — Wed, 06 Dec 2017 12:57:35 GMT

I'm assuming you mean 16kbps. Your calculation looks correct. I will check with the developers. Will get back to you.