nRF52 DK - 20ms non connectable advertising interval

RE: nRF52 DK - 20ms non connectable advertising interval

Maximilian Wiens — Tue, 23 May 2017 07:34:18 GMT

Accordingly to the Bluettoth 5.0 specification (Vol. 6, Part B, 4.4.2.2.1) there is no 100ms restriction for "advertising non-connectable" anymore.

RE: nRF52 DK - 20ms non connectable advertising interval

Igor — Tue, 23 May 2017 05:04:02 GMT

Hi everyone. Limitation of 100 ms in the "advertising non-connectable" mode is relevant for the Bluetooth 5.0 specification?

RE: nRF52 DK - 20ms non connectable advertising interval

RK — Wed, 27 Jul 2016 07:52:59 GMT

nope doesn't matter at all what chipset you use - in order to conform to the BTLE spec no device advertising non-connectably (or scannable) can advertise faster than once every 100ms.

I assume as part of the certification process for Nordic (and everyone else's) bluetooth stack there's a test that the stack rejects invalid parameters like that.

RE: nRF52 DK - 20ms non connectable advertising interval

Maximilian Wiens — Wed, 27 Jul 2016 07:49:49 GMT

So it turns out, accordingly to the bluetooth spec, that the advertising intervall smller than 100ms is only available for the connectable devices, doesnt matter which chip/brand I choose?

RE: nRF52 DK - 20ms non connectable advertising interval

RK — Wed, 27 Jul 2016 07:40:27 GMT

From the bluetooth spec (Vol 6, Part B, section 4.4.2.2 )

The advInterval shall be an integer multiple of 0.625 ms in the range of 20 ms to 10.24 s. If the advertising event type is either a scannable undirected event type or a non-connectable undirected event type, the advInterval shall not be less than 100 ms

so "it does not work" because the stack will return you an error message when you try to set a non-connectable advertising interval of less than 100ms and the code will jump right to the error handler. The softdevice doesn't allow you to set parameters which are outside the bluetooth spec.