Bluetooth: Controller: Auxiliary Offset 510 us [@40.612 706 125]

RE: Bluetooth: Controller: Auxiliary Offset 510 us [@40.612 706 125]

Priyanka — Thu, 14 Nov 2024 08:04:43 GMT

Hi,

The fixed 330us offset is used for SDC scanner optimization.

-Priyanka

RE: Bluetooth: Controller: Auxiliary Offset 510 us [@40.612 706 125]

Tovms zhangsan — Wed, 13 Nov 2024 02:07:58 GMT

I just saw that the Auxoffset of the Zephyr open source Bluetooth Controller stack is larger than that of NCS, which gives me the feeling that a smaller one is more appropriate.

RE: Bluetooth: Controller: Auxiliary Offset 510 us [@40.612 706 125]

yuxuan.cai — Tue, 12 Nov 2024 11:50:31 GMT

Using a longer aux offset will, for instance, increase power consumption and block other radio activities. Is there a specific use case where a long aux offset is required?

RE: Bluetooth: Controller: Auxiliary Offset 510 us [@40.612 706 125]

Tovms zhangsan — Tue, 12 Nov 2024 11:42:21 GMT

What I mean is that what kind of considerations is the current ncs 330us based on, and why not use a larger offset?

RE: Bluetooth: Controller: Auxiliary Offset 510 us [@40.612 706 125]

yuxuan.cai — Tue, 12 Nov 2024 11:38:35 GMT

The Bluetooth Core Spec requires a minimum AUX Frame Space (T_MAFS) of 300 us (see Vol 6, Part B, 4.1.2 Minimum AUX Frame Space). It takes time to bring up the radio and this is the main consideration. Could you please elaborate a bit more about your question? Also, what are you trying to tell us with the screenshot?