Scan+Advertise vs Connected+Broadcasting | Cypress Semiconductor
Scan+Advertise vs Connected+Broadcasting
I understand a few stipulations for simultaneously scanning and advertising, and also broadcasting while in a connected state, such as while connected, broadcasts must be non-connectable, undirected advertisements, however, while scanning, advertisements can be of any type. Also, as far as API calls, starting advertisements must happen before starting up scanning. I do have some related questions involving the connected/broadcasting function that isn't mention in the docs though, if anyone can help:
1. I noticed that there is no "NON_CONNECTABLE_DIRECTED_ADV". The non-connectable portion is understandable, but what if, for example, I wanted a connected device's broadcast to only reach a specific non-connected device? How would that be accomplished?
2. If directed broadcasting isn't possible, do these broadcast advertisements have a scan response packet?
If so, does filtering apply? I figured that if I can't direct the advertisement, I could filter the scan response packet from everything but the defined devices.
3. This one relates to both Scanning/Advertising and Connected/Broadcasting: Can you dynamically update these advertisements using CyBle_GapUpdateAdvData while scanning or connected, or would you need to be in a disconnected, or non-broadcasting, state, update, then restart?