Advertisement packet missed for a while from ble tag

[paul0208]

Hi,

I am testing the advertisement packet scanner based from nRF5_SDK_17.0.2_d674dde\examples\ble_central\ble_app_uart_c.

At current stage, I can receive the advertisement packets from BLE peripherals including my BLE tag.

I found that the advertisement packet from my BLE tag are not received at BLE_GAP_EVT_ADV_REPORT event for a while(about 50 sec) and  after that adv packet are received about 50 secs and then no adv... from my tag while other adv packet received well.

At this time, my cellphone appl. made by Nordic receives the all adv packets which are lost at my scanner.

My tag sends adv packet every 5 secs. 

Scanner scanner is set to scan interval == scan window.

What is the problem?

BR

Paul

[paul0208]

scan interval and scan window are set to 625msec

[Kenneth]

Have you tried to change scan window and scan interval? What timeout have you set when scanning? For instance you can set timeout to 0 to scan infinitely. Do you have other BLE channels while scanning here?

Best regards,
Kenneth

[paul0208]

Hi, Kenneth.

Yes, I am just scanning.

Same results with my custom board and nRF52-DK. I will test 5sec window and interval and let you know.

I cannot block other devices I don't know which device send the adv packets, TV and ... 

I put LED blink in BLE_GAP_EVT_ADV_REPORT event state, I can see many LED blinking while my tag beacon are missing.

If I set window and interval to 5sec, is any problem to scan 3 broadcasting channels? Because my scanner has to scan a bunch of my ble tag(has unique UUID, 5sec broadcasting) simultaneously.

BR

Paul 

[paul0208]

Hi, Kenneth.

It was from my mistake.

SCAN_WINDOW define was a half of INTERVAL.

sdk_config.h file's location was wrong.

No missing adv packet from my BLE tag.

BR

Paul

[Kenneth]

Hi Paul,

There isn't much magic here, in general the softdevice will scan as configured (in other words it will scan one frequency for the configured window size, and then scan the next frequency (out of the 3) on next scan interval). The "dead" spots here will be if you have any other BLE activity also on-going that may interfere with this operation, flash erase or write operations, and/or if you are doing active scanning with many peers in the area, since active scanning will request scan response packets from the individual peers (indirectly blocking other devices during this operation (typically ~1ms).

Best regards,
Kenneth

[paul0208]

Hi, Kenneth,

Then, is it better for set small size window and interval now? It works.

I will use two nRF52 modules to scan BLE tag's adv packet simultaneously.

BR

Paul

[Kenneth]

paul0208 said:

It was from my mistake.

SCAN_WINDOW define was a half of INTERVAL.

I didn't see this reply until now.

Usually setting scan window = interval to small values like 5ms is a good idea if you are also doing other BLE activity, since that will schedule the scanning tight in between the other BLE activity. If you are only scanning, then you may as well set scan window = interval = 1seconds.

Kenneth