BLE scan does not timeout

RE: BLE scan does not timeout

AmrutaZende — Thu, 10 Jan 2019 12:33:27 GMT

Thanks.

RE: BLE scan does not timeout

tesc — Thu, 10 Jan 2019 12:31:39 GMT

Hi,

Unfortunately I do not know the dates, but the team is currently working on updated versions of pc-ble-driver-py. Updated version of pc-ble-driver-js is most likely to come next after that.

Regards,
Terje

RE: BLE scan does not timeout

AmrutaZende — Thu, 10 Jan 2019 06:14:43 GMT

Is there any expected date by which pc-ble-driver-js will be available?

RE: BLE scan does not timeout

tesc — Wed, 09 Jan 2019 09:05:22 GMT

Hi,

Yes, pc-ble-driver v4.0.0 is out, but pc-ble-driver-js is not yet updated.

Regards,
Terje

RE: BLE scan does not timeout

AmrutaZende — Wed, 09 Jan 2019 03:50:03 GMT

Is this release out yet?

RE: BLE scan does not timeout

tesc — Thu, 29 Nov 2018 10:10:16 GMT

Hi,

The team responsible for pc-ble-driver and pc-ble-driver-js is notified of the issue, but we have not been able to reproduce this exact issue yet.

There will be a new release of pc-ble-driver soon, with stability fixes that may also solve this issue. After that there will also be a new release of pc-ble-driver-js, using the new version of pc-ble-driver.

Unfortunately, for now it seems you need to reset the device when this kind of error state happens.

Regards,
Terje

RE: BLE scan does not timeout

AmrutaZende — Wed, 21 Nov 2018 12:56:00 GMT

This issue can be reproduced using NRF52840 dongle and NRF connect app (latest version 2.6.1) on a Windows 10 machine with 32 bit architecture.

Steps to reproduce.

T = 0 sec: Start scan, advertising devices are listed

T = 3 sec: Stop scan, clear the seen devices

T = 6 sec: Start scan,, advertising devices are listed

T = 9 sec: Stop scan, clear the seen devices

T = 12 sec: Start scan,, advertising devices are listed

T = 15 sec: Stop scan, clear the seen devices

T = 18 sec: Start scan,, advertising devices are listed

T = 21 sec: Stop scan, clear the seen devices

...... repeat this for a few minutes .....

leave the device running NRF connect for a few minutes

Repeat the start-scan, stop-scan sequence again. The stop scan will not be responsive at one point of time. Thereafter if you do a start scan/stop scan, you'll see following error.

Error occurred while starting scan. Errcode: NRF_ERROR_INTERNAL (0x3)

Received status with code 4 Unknown value, message:'Error sending packet to target.'

Find below the log file generated by NRF connect app.

devzone.nordicsemi.com/.../2018_2D00_11_2D00_20T10_5F00_18_5F00_37.286Z_2D00_log.txt

RE: BLE scan does not timeout

Prashant Ambardekar — Wed, 21 Nov 2018 11:03:36 GMT

We have seen this issue on another 32 bit Windows 10 machine.

RE: BLE scan does not timeout

Prashant Ambardekar — Wed, 21 Nov 2018 06:38:22 GMT

Thanks for looking into this.

It does not fail at the same time each time. In this state scan stop also fails. I added an event listener for scanTimedOut and here are new logs

[2018-11-21 11:43:28.046] [info] Starting BLE scan
[2018-11-21 11:43:31.115] [info] ###NRF_Log: 1: GAP_EVT_TIMEOUT time:2018-11-21T06:13:31.116Z connHandle:65535 src:2 srcName:bleGapTimeoutSrcScan << This is from logMessage event
[2018-11-21 11:43:31.119] [info] #### Scan timed out << This is from scanTimedOut event listener
[2018-11-21 11:43:34.275] [info] Starting BLE scan
[2018-11-21 11:43:37.525] [info] ###NRF_Log: 1: GAP_EVT_TIMEOUT time:2018-11-21T06:13:37.527Z connHandle:65535 src:2 srcName:bleGapTimeoutSrcScan
[2018-11-21 11:43:37.525] [info] #### Scan timed out
[2018-11-21 11:43:40.506] [info] Starting BLE scan
[2018-11-21 11:43:43.745] [info] ###NRF_Log: 1: GAP_EVT_TIMEOUT time:2018-11-21T06:13:43.747Z connHandle:65535 src:2 srcName:bleGapTimeoutSrcScan
[2018-11-21 11:43:43.745] [info] #### Scan timed out
[2018-11-21 11:43:46.725] [info] Starting BLE scan
[2018-11-21 11:43:49.795] [info] ###NRF_Log: 1: GAP_EVT_TIMEOUT time:2018-11-21T06:13:49.797Z connHandle:65535 src:2 srcName:bleGapTimeoutSrcScan
[2018-11-21 11:43:49.795] [info] #### Scan timed out
[2018-11-21 11:43:52.995] [info] Starting BLE scan
[2018-11-21 11:43:56.025] [info] ###NRF_Log: 1: GAP_EVT_TIMEOUT time:2018-11-21T06:13:56.027Z connHandle:65535 src:2 srcName:bleGapTimeoutSrcScan
[2018-11-21 11:43:56.025] [info] #### Scan timed out
[2018-11-21 11:43:59.226] [info] Starting BLE scan
[2018-11-21 11:44:02.307] [info] ###NRF_Log: 1: GAP_EVT_TIMEOUT time:2018-11-21T06:14:02.307Z connHandle:65535 src:2 srcName:bleGapTimeoutSrcScan
[2018-11-21 11:44:02.307] [info] #### Scan timed out
[2018-11-21 11:44:05.466] [info] Starting BLE scan

#### No time out event for above scan. All subsequent start scans fail

[2018-11-21 11:44:11.686] [info] Starting BLE scan
[2018-11-21 11:45:26.496] [error] Adapter error: {
"message": "Error occured when starting scan",
"description": {
"errno": 17,
"errcode": "NRF_ERROR_BUSY",
"erroperation": "starting scan",
"errmsg": "Error occured when starting scan. Errorcode: NRF_ERROR_BUSY (0x11)\n"
}

In this state, stop scan also fails with error

[2018-11-21 11:45:29.696] [info] COMM_BLE: Stopping BLE scan
[2018-11-21 11:45:29.736] [error] Adapter error: {
"message": "Error occured when stopping scanning",
"description": {
"errno": 8,
"errcode": "NRF_ERROR_INVALID_STATE",
"erroperation": "stopping scan",
"errmsg": "Error occured when stopping scan. Errorcode: NRF_ERROR_INVALID_STATE (0x8)\n"
}
}

Looks like the adapter has gone into a state where

- Start scan fails with NRF_ERROR_BUSY

- Stop scan fails with NRF_ERROR_INVALID_STATE

Please note that my stop scan is guarded by if(adapter.scanning == true). This evaluates to true in this state but stop scan still fails.

regards,

-Prashant.

RE: BLE scan does not timeout

tesc — Tue, 20 Nov 2018 12:49:32 GMT

Hi,

I could not find any known occurrences of this, and I am not convinced it is due to the scan not timing out. It may for instance be that the connectivity device has entered a bad state, somehow, or that there has been an USB error of some description.

Does it fail at around the same time each time, or is it some times down towards ten minutes before it breaks and other times up towards twenty minutes or more?

Does indeed handling the NRF_ERROR_BUSY error code by doing a scan stop followed by a retry solve the issue?

Regards,
Terje