RE: Missing Advertisements from Mesh proxy node

tesc — Wed, 25 Sep 2019 12:11:54 GMT

Hi,

Sorry for the delayed answer on this one!

With Bluetooth mesh and GATT Proxy, you do get quite a bit of radio activity already, and so any concurrent BLE activity will affect mesh operation and vice versa. One way to figure out how much time you get for beacon RX, as well as get a better understanding of what radio activity is going on, is to use a BLE Sniffer.

In order for a scanner to detect your beacon, it must scan on the same channel and on the same time as the beacon transmits. Depending on advertising interval and scan interval, you may end up in a situation where scan windows and advertising events are "in sync" but "out of phase". Information on the scan parameters for the observer is therefore useful with regards to deciding the advertising parameters for the beacon. You can read more about scanner timing and advertiser timing in the SoftDevice Specification. Do note, however, that Bluetooth mesh uses the timeslot API for ADV bearer based operations.

The SoftDevice currently only have max one advertising set. That means you are likely to get into trouble if you have copied the advertising functions from examples/common/src/mesh_adv.c and both the old and new functions are used from the application. If you are to send multiple beacons concurrently you may find that you need to set the advertising data for every advertising event.

Regards,
Terje