Receive Advertisement Packet in Mesh Beaconing Example

RE: Receive Advertisement Packet in Mesh Beaconing Example

SHawY — Sun, 05 Apr 2020 06:00:30 GMT

Hi Terje,

It works! Many thanks for help. I must misundertand the description and thought it's for advertising but not receiving...

RE: Receive Advertisement Packet in Mesh Beaconing Example

tesc — Fri, 03 Apr 2020 09:55:42 GMT

Hi,

The beaconing example, while documentation for "testing" states it prints all incoming packets and documentation for "RX callback" states it can receive all non-filtered packets, actually does use a filter on BLE_GAP_AD_TYPE_COMPLETE_LOCAL_NAME. The callback will only be called for packets with this advertising data type in them.

The filter is set in the function adv_start(), in main.c:

    /* Let scanner accept Complete Local Name AD Type. */
    bearer_adtype_add(BLE_GAP_AD_TYPE_COMPLETE_LOCAL_NAME);

The filter is employed for all packets before they get sent to the Scanner module, which again is responsible for calling the callback. You can read more about filtering in the Packet filtering API documentation.

I have reported documentation bugs internally, for updating Beaconing example documentation to reflect the behavior of the example, as well as clarify the behavior of the Scanner in relation to Packet filtering in the Scanner API documentation.

Regards,
Terje

RE: Receive Advertisement Packet in Mesh Beaconing Example

tesc — Wed, 01 Apr 2020 08:59:06 GMT

Hi,

I am able to reproduce. Looking into why this may be.

Regards,
Terje

RE: Receive Advertisement Packet in Mesh Beaconing Example

SHawY — Wed, 01 Apr 2020 01:28:08 GMT

Hi Terje,

I'm sure I'm using the unmodified files. Here's what I tried:

I create two advertiser which advertising User Data, the first one advertsing the Local Name as well.

When I enable either of them or both, only the one with Local Name can be found during scanning (ADDR: [a4:e8:6c:8a:31:45]: 0E094F6E65506C757320372050726F07161C1811223344)

<t:          0>, main.c,  218, ----- Bluetooth Mesh Beacon Example -----
<t:      12870>, main.c,  224, Initialization complete!
<t:      17601>, mesh_app_utils.c,   65, Device UUID (raw): 83C4140939D7514483FD76458708046C
<t:      17605>, mesh_app_utils.c,   66, Device UUID : 0914C483-D739-4451-83FD-76458708046C
<t:      17616>, main.c,  253, Bluetooth Mesh Beacon example started!
<t:     113982>, main.c,   87, RX [@3478019]: RSSI: -86 ADV TYPE: 0 ADDR: [8a:08:6c:8d:cd:c0]: 0709534D492D4D31031900000201060F1695FE3120A1011D8A086C8DCDC00D
<t:     175528>, main.c,   87, RX [@5356307]: RSSI: -86 ADV TYPE: 0 ADDR: [8a:08:6c:8d:cd:c0]: 0709534D492D4D31031900000201060F1695FE3120A1011D8A086C8DCDC00D
<t:     299087>, main.c,   87, RX [@9127103]: RSSI: -88 ADV TYPE: 0 ADDR: [8a:08:6c:8d:cd:c0]: 0709534D492D4D31031900000201060F1695FE3120A1011D8A086C8DCDC00D
<t:     360440>, main.c,   87, RX [@10999283]: RSSI: -89 ADV TYPE: 0 ADDR: [8a:08:6c:8d:cd:c0]: 0709534D492D4D31031900000201060F1695FE3120A1011D8A086C8DCDC00D
<t:     362671>, main.c,   87, RX [@11067431]: RSSI: -64 ADV TYPE: 4 ADDR: [50:9c:36:34:2d:58]: 09094D4A5F48545F563105030F180A180916FFFFD65F151E817F
<t:     428411>, main.c,   87, RX [@13073674]: RSSI: -72 ADV TYPE: 4 ADDR: [50:9c:36:34:2d:58]: 09094D4A5F48545F563105030F180A180916FFFFD65F151E817F
<t:     483872>, main.c,   87, RX [@14766208]: RSSI: -88 ADV TYPE: 0 ADDR: [8a:08:6c:8d:cd:c0]: 0709534D492D4D31031900000201060F1695FE3120A1011D8A086C8DCDC00D
<t:     516380>, main.c,   87, RX [@15758347]: RSSI: -63 ADV TYPE: 6 ADDR: [a4:e8:6c:8a:31:45]: 0E094F6E65506C757320372050726F07161C1811223344
<t:     525718>, main.c,   87, RX [@16043348]: RSSI: -66 ADV TYPE: 6 ADDR: [a4:e8:6c:8a:31:45]: 0E094F6E65506C757320372050726F07161C1811223344
<t:     535036>, main.c,   87, RX [@16327704]: RSSI: -61 ADV TYPE: 6 ADDR: [a4:e8:6c:8a:31:45]: 0E094F6E65506C757320372050726F07161C1811223344
<t:     544388>, main.c,   87, RX [@16613116]: RSSI: -63 ADV TYPE: 6 ADDR: [a4:e8:6c:8a:31:45]: 0E094F6E65506C757320372050726F07161C1811223344
<t:     545312>, main.c,   87, RX [@16641227]: RSSI: -87 ADV TYPE: 0 ADDR: [8a:08:6c:8d:cd:c0]: 0709534D492D4D31031900000201060F1695FE3120A1011D8A086C8DCDC00D
<t:     563025>, main.c,   87, RX [@17181865]: RSSI: -67 ADV TYPE: 6 ADDR: [a4:e8:6c:8a:31:45]: 0E094F6E65506C757320372050726F07161C1811223344
<t:     572322>, main.c,   87, RX [@17465615]: RSSI: -67 ADV TYPE: 6 ADDR: [a4:e8:6c:8a:31:45]: 0E094F6E65506C757320372050726F07161C1811223344
<t:     581784>, main.c,   87, RX [@17754364]: RSSI: -78 ADV TYPE: 6 ADDR: [a4:e8:6c:8a:31:45]: 0E094F6E65506C757320372050726F07161C1811223344
<t:     591204>, main.c,   87, RX [@18041864]: RSSI: -69 ADV TYPE: 6 ADDR: [a4:e8:6c:8a:31:45]: 0E094F6E65506C757320372050726F07161C1811223344
<t:     600830>, main.c,   87, RX [@18335615]: RSSI: -73 ADV TYPE: 6 ADDR: [a4:e8:6c:8a:31:45]: 0E094F6E65506C757320372050726F07161C1811223344
<t:     607049>, main.c,   87, RX [@18525331]: RSSI: -87 ADV TYPE: 0 ADDR: [8a:08:6c:8d:cd:c0]: 0709534D492D4D31031900000201060F1695FE3120A1011D8A086C8DCDC00D
<t:     610275>, main.c,   87, RX [@18623857]: RSSI: -63 ADV TYPE: 6 ADDR: [a4:e8:6c:8a:31:45]: 0E094F6E65506C757320372050726F07161C1811223344
<t:     619532>, main.c,   87, RX [@18906358]: RSSI: -63 ADV TYPE: 6 ADDR: [a4:e8:6c:8a:31:45]: 0E094F6E65506C757320372050726F07161C1811223344
<t:     628911>, main.c,   87, RX [@19192608]: RSSI: -63 ADV TYPE: 6 ADDR: [a4:e8:6c:8a:31:45]: 0E094F6E65506C757320372050726F07161C1811223344

RE: Receive Advertisement Packet in Mesh Beaconing Example

tesc — Mon, 30 Mar 2020 13:20:16 GMT

Hi,

Going back to what output to expect from the example, this is the log I get when testing here (with a few BLE devices in the area):

<t:          0>, main.c,  218, ----- Bluetooth Mesh Beacon Example -----
<t:      13970>, main.c,  224, Initialization complete!
<t:      18734>, mesh_app_utils.c,   65, Device UUID (raw): 073D03C4720B6745AB6E06D305F13C5E
<t:      18737>, mesh_app_utils.c,   66, Device UUID : C4033D07-0B72-4567-AB6E-06D305F13C5E
<t:      18748>, main.c,  253, Bluetooth Mesh Beacon example started!
<t:      33706>, main.c,   87, RX [@1028329]: RSSI: -82 ADV TYPE: 4 ADDR: [c6:54:7a:9b:36:f8]: 0B0972757769646F20424C45
<t:     133396>, main.c,   87, RX [@4070477]: RSSI: -92 ADV TYPE: 4 ADDR: [b7:34:ba:c7:52:04]: 020A0A1B094C452D426F736520436F6C6F7220494920536F756E644C696E6B
<t:     192247>, main.c,   87, RX [@5866604]: RSSI: -81 ADV TYPE: 4 ADDR: [d2:9e:a7:a1:41:2c]: 020A080E094C452D72657365727665645F43
<t:     314305>, main.c,   87, RX [@9591431]: RSSI: -89 ADV TYPE: 4 ADDR: [b7:34:ba:c7:52:04]: 020A0A1B094C452D426F736520436F6C6F7220494920536F756E644C696E6B
<t:     605565>, main.c,   87, RX [@18480001]: RSSI: -84 ADV TYPE: 4 ADDR: [76:7b:a7:a1:41:2c]: 020A0816094C452D426F736520467265652048656E72696B6B65
<t:     769199>, main.c,   87, RX [@23473756]: RSSI: -82 ADV TYPE: 4 ADDR: [d2:9e:a7:a1:41:2c]: 020A080E094C452D72657365727665645F43

Comparing it to the log that you provided earlier, I see that the line numbers for corresponding log outputs do not match. Can you double check that you are using the unmodified example from the <SDK folder>/examples/beaconing/ folder? (With unmodified main.c in the src folder of that folder.)

Regards,
Terje

RE: Receive Advertisement Packet in Mesh Beaconing Example

SHawY — Mon, 30 Mar 2020 04:11:29 GMT

Yes I tried... No problem receiving advertisements through nRF Connect for iOS, could discover them both.

RE: Receive Advertisement Packet in Mesh Beaconing Example

tesc — Fri, 27 Mar 2020 10:23:33 GMT

Hi,

There should not be any such restriction for the scanner in the beaconing example, no. It should detect all advertisements on the same phy as the mesh stack is running.

It may be an issue on the sender side. Have you checked to see if you receive advertisements through nRF Connect? (Either a separate session of nRF Connect for desktop, or using nRF Connect for iOS or Android.)

Regards,
Terje

RE: Receive Advertisement Packet in Mesh Beaconing Example

SHawY — Thu, 26 Mar 2020 00:24:04 GMT

Hi Terje,

Much thanks for explainations. I created two advertisers in nRF Connect which advertising the same Service Data. The only different is one with Complete Local Name and the other didn't - and the scanner can only print the packet which advertising with the name. That's why I wonder if it is necessary. Do you have any idea about this?

The purpose using coded phy is trying to extend the range as much as possible in my senario. Maybe I need more test to see if it's necessary...

RE: Receive Advertisement Packet in Mesh Beaconing Example

tesc — Mon, 23 Mar 2020 10:20:06 GMT

Hi,

With the callback from the mesh stack (registered with nrf_mesh_rx_cb_set) you will only get advertisements on the same phy as the mesh is running on. That means if you look for "normal" advertisements using 1Mbit and the mesh stack runs on coded phy you will not find those normal advertisements. The mesh stack calls the callback on all advertisements that it detects, there is no requirement of e.g. name.

As mentioned in that other thread, on-air time for coded phy messages is eight times longer than for 1Mbit. This means two things: First, the chance of an advertisement packet arriving fully within a scan window is smaller. Second, the chance of a packet getting lost to noise/interference may increase (despite of the added error correction,) depending of the type of noise. Thus, which phy is best depends on the use case and RF environment.

The mesh stack uses all available time for scanning. That is, when it does not need to send a packet it will scan. Values used by the mesh stack are BEARER_SCAN_INT_DEFAULT_MS and BEARER_SCAN_WINDOW_DEFAULT_MS, which are defined along with other parameters in <sdk root folder>/mesh/bearer/api/nrf_mesh_config_bearer.h. All of those can be overridden by defining them as preprocessor defines, so there is no need to change the mesh stack files for using other values.

Regards,
Terje

RE: Receive Advertisement Packet in Mesh Beaconing Example

SHawY — Sun, 22 Mar 2020 22:42:32 GMT

Hi Terje,

I have changed back to default mode and now I can find other advertisements. However I found that only beacon with name can be found - I also tried create different advertiser in nRF Connect App and got the same result. Do I have to advertise the name to find them?

I also tried implement the nRF5 SDK scanner with mesh stack. You are right I got problems with time-division multiplexing. It would be better if the rx_cb could work properly. Is there anywhere I can change the scan window and interval for beaconing example?

I modified long range according to this. It could works with the light switch example.

RE: Receive Advertisement Packet in Mesh Beaconing Example

tesc — Fri, 20 Mar 2020 12:52:25 GMT

Hi,

Bluetooth mesh is actually only running on the 1Mbit mode from Bluetooth 4.2, and does not use neither 2Mbit nor long range features from Bluetooth 5. The advertising packet callback that you use for scanning while simultaneously running Bluetooth mesh, must use the same phy as used for the mesh protocol.

While it is possible to use the scanner from the nRF5 SDK together with the mesh stack from nRF5 SDK for Mesh, it is not recommended as it means radio time is then time-division multiplexed between mesh stack and BLE stack. (Only one of the stacks has access to the radio at any given point in time.)

You mention that you have no problem using long range with other examples, which other examples have you successfully used long range on?

Regards,
Terje

RE: Receive Advertisement Packet in Mesh Beaconing Example

SHawY — Thu, 19 Mar 2020 20:55:17 GMT

Hi Terje,

Thanks for answering. I'm using nRF52840 DK (the PCA10056 v1.1.0) ,nRF5 SDK for Mesh 4.0 and nRF Connect for Android v4.24.1. My device is OnePlus 7.

I have modified the RADIO_POWER to POS8DBM and RADIO_MODE to RADIO_MODE_NRF_62K5BIT in order to enable long range.

I flashed another board with beaconing example, I notice that they can find each other and the advertisement packet contain the name"Nordic Semi Mesh". So actually it's advertising but I don't know why the App can't find it...

Update: I change the RADIO_MODE back to default RADIO_MODE_BLE_1MBIT and now the App can find the node. So this is the reason for discovering but the node still can't scan for other advertising packets. And I'm not quite understand why there's no problem using long range radio mode with other example but not the beaconing. Any help with that?

RE: Receive Advertisement Packet in Mesh Beaconing Example

tesc — Thu, 19 Mar 2020 15:17:19 GMT

Hi,

I have now tested the examples/beaconing/ example from the nRF5 SDK for Mesh v4.0.0, on an nRF52840 DK (the PCA10056 v1.0.0) and it works just as in the descriptions here. I get prints for advertising packets scanned from several other devices, and the device itself advertises as "Nordic Semi Mesh" as seen from nRF Connect for Android.

What board are you using?
What version of the nRF5 SDK for Mesh?
Have you done any modification to the example?
What version of nRF Connect, and on which device?

Regards,
Terje

RE: Receive Advertisement Packet in Mesh Beaconing Example

SHawY — Wed, 18 Mar 2020 21:23:37 GMT

Hi Terje,

Here's what I got after I flash the example,

<t: 0>, main.c, 225, ----- Bluetooth Mesh Beacon Example -----
<t: 13436>, main.c, 231, Initialization complete!
<t: 18239>, advertiser.c, 323, advertiser_enable
<t: 18241>, prov_bearer_adv.c, 408, PB-ADV: context at 0x20002F64 added to bearer
<t: 18246>, mesh_app_utils.c, 65, Device UUID (raw): D5663AB3804DC24FB36A7B17B215CC75
<t: 18249>, mesh_app_utils.c, 66, Device UUID : B33A66D5-4D80-4FC2-B36A-7B17B215CC75
<t: 18257>, net_beacon.c, 368, net_beacon_enable
<t: 18263>, main.c, 260, Bluetooth Mesh Beacon example started!

And nothing print else while actually there are several ble device advertsing nearby. Until I turn on a mesh node I got this:

<t: 7783267>, net_beacon.c, 419, SNB RX ID: 54D021362603E40E ivu: 0 kr: 0 IV: 0
<t: 7783275>, main.c, 87, RX [@237524360]: RSSI: -20 ADV TYPE: 2 ADDR: [98:fe:b7:55:a6:eb]: 172B010054D021362603E40E00000000C1ABE802E7AEC2C7
<t: 8102924>, net_beacon.c, 419, SNB RX ID: 54D021362603E40E ivu: 0 kr: 0 IV: 0
<t: 8102932>, main.c, 87, RX [@247279514]: RSSI: -23 ADV TYPE: 2 ADDR: [98:fe:b7:55:a6:eb]: 172B010054D021362603E40E00000000C1ABE802E7AEC2C7
<t: 8454414>, net_beacon.c, 419, SNB RX ID: 54D021362603E40E ivu: 0 kr: 0 IV: 0
<t: 8454422>, main.c, 87, RX [@258006141]: RSSI: -24 ADV TYPE: 2 ADDR: [98:fe:b7:55:a6:eb]: 172B010054D021362603E40E00000000C1ABE802E7AEC2C7

The example should also advertise it's name("Nordic Semi Mesh") according to the instruction but I can't find such node in nRF Connect App.

RE: Receive Advertisement Packet in Mesh Beaconing Example

tesc — Wed, 18 Mar 2020 12:03:32 GMT

HI,

The Beaconing example should print info for all packets received, as is. This is done in main.c with the function rx_cb, which is a callback function that gets registered by the line "nrf_mesh_rx_cb_set(rx_cb);" in mesh_init() also in main.c.

What does the output that you do get look like? Can you share it?

Regards,
Terje