ble_app_hrs_c --scan stopped

[Mike]

I programmed nRF51822 with S120 softdevice and ble_app_hrs_c application to scan beacons. It works fine but have one problem.

• It scans beacons for about 10 seconds then stop scanning for about 10 seconds and repeat scanning.

What makes this kind of symptoms scanning-stop-scanning-stop every 10 seconds period.

[Mike]

I have captured beacon data at "on_ble_evt" S120 reply event for 10 seconds then no reply for 10 seconds, I tested with one nordic format beacon.

Symptom:

• using one beacon every second advertising.
• successfully scan beacon and send UART 10~11 times, it's about 10 seconds then halt
• After about 10 seconds again scan beacon and send UART.
• Repeat above situation.

Durig halt state, I advertise anothe beacon then it scan successfully so this symptom is related in scanning same beacon continueously.

[Roger Clark]

OK. So the code has not crashed, but the callback is no longer called for the first beacon, it only gets called for the second beacon which you turn on after 10 secs.

What do you do in your callback ?

[Mike]

...

#define SCAN_INTERVAL              0x00A0                             /**< Determines scan interval in units of 0.625 millisecond. */

#define SCAN_WINDOW                0x0050                             /**< Determines scan window in units of 0.625 millisecond. */

Above is default setting interval I used. I mean that in the case I advertise only one beacon, it scans 10 seconds and stop 10 seconds then repeat scan and stop. During scanning stopped if I advertise another beacon, it scans another beacon.

[Roger Clark]

Hi Mike

Ah. I thought it had completely stopped reporting the first beacon, and only the second beacon was being received.

But like Stefan says, if it starts receiving the first beacon again after a further 10 seconds, its a sort of time phasing issue which is happening