Are there any examples of how to setup a Scan Response while
advertising? Apple, for example, recommends putting the Local Name and
TX Power in the scan response to free up space. See section 3.4 of
https://developer.apple.com/hardwaredrivers/BluetoothDesignGuidelines.pdf
The big benefit here is that you can advertise the local name in the
scan response, freeing up enough room in the main advertising packet for
a 128-bit UUID if necessary, since primary services should always be
advertised in the main payload. Most of the mobile apps from Nordic
require that the Nordic BLE UART service's 128-bit UUID is advertised,
for example, which doesn't leave a lot of space for other things.
It's no problem to dig into the code and figure this out, I just wanted
to ping the list first to see if this was possible today before
committing some resources to it.
Kevin
PS: One other note with reference to the design guidelines from Apple:
many Apple devices are very specific about the timing requirements
(Section 3.5, 3.6, etc.) and devices that don't respect the limits may
not appear even if they are within the core specification limits. It
might be worth adding a section to the documentation on controlling the
key timing values (advertising interval, connection interval, etc.).
We're just looking into some of the details now that we have a basic app
running with DIS and Nordic UART, and I'm happy to contribute some
documentation in markdown as we track these details down, but it might
be worth considering having something easy to use in the core API to
control the various timing values in one central location.
- Scan Response and Timing Kevin Townsend
-
