Issues with characteristic values using the pc-ble-driver-py library

RE: Issues with characteristic values using the pc-ble-driver-py library

Scault — Thu, 05 Sep 2019 17:28:22 GMT

Thanks! The issues seem to be fixed!

RE: Issues with characteristic values using the pc-ble-driver-py library

tesc — Tue, 27 Aug 2019 12:01:39 GMT

Hi,

The issue has been fixed and the fix merged into master. For details and patch, see https://github.com/NordicSemiconductor/pc-ble-driver-py/pull/118

Regards,
Terje

RE: Issues with characteristic values using the pc-ble-driver-py library

tesc — Mon, 26 Aug 2019 15:14:28 GMT

Hi,

The team found an error in APIv2 serialization which may explain all of the issues described thus far in this thread. They are now working on a solution. The issue is only seen with APIv2.

Regards,
Terje

RE: Issues with characteristic values using the pc-ble-driver-py library

Scault — Thu, 22 Aug 2019 15:37:05 GMT

Thanks! I will investigate a bit more to see why we could be getting 36000+ bytes for our Heart Rate Measurement...

RE: Issues with characteristic values using the pc-ble-driver-py library

tesc — Thu, 22 Aug 2019 12:50:32 GMT

Hi,

We are consistently reproducing the Device Name read issue, and have isolated it to be in either pc-ble-driver or pc-ble-driver-py. (I.e. it is not a connectivity firmware issue, and not a UART issue.)

Regarding the values read from the Heart Rate Measurement characteristic, those should not be 36660+ bytes long. Via bluetooth.com you can find the format for the HRM value. Studying the log output, it seems the last few bytes of "Heart Rate Received" are corrupted as well. Looks to me like a "use after free" issue somewhere in either pc-ble-driver or pc-ble-driver-py. The team is looking into it.

Regards,
Terje

RE: Issues with characteristic values using the pc-ble-driver-py library

tesc — Mon, 19 Aug 2019 14:39:43 GMT

Hi,

Jørgen Holmefjord is currently out-of-office.

I have not (as of yet) been able to reproduce for received advertising data, but I have reproduced for listing the device name upon connection:

Nordic_HRM -> [78, 111, 114, 100, 105, 99, 95, 72, 82, 77]
New connection: 0
Device Name = Noïz·=?  ? status = BLEGattStatusCode.success

Clearly something is not right, and I am investigating further.

Regards,
Terje

RE: Issues with characteristic values using the pc-ble-driver-py library

Scault — Thu, 15 Aug 2019 19:27:55 GMT

I do see the corruption issue in your output in line 26. "TestDev" is the string of your device name but once the connection is established it is read as "Tes ·" - the last 4 characters are overwritten.

This is the output I get when testing against the HRS example in the SDK:

> python3 .\nus_collecter.py NRF51
        0 : COM3: 681802590
        1 : COM4: 683838020

Enter your choice: 0
Serial port used: COM3
HMIdesk_17490245 -> [72, 77, 73, 100, 101, 115, 107, 95, 49, 55, 52, 57, 48, 50, 52, 53]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
RSI_BLE_SIMPLE_PRIVACY -> [82, 83, 73, 95, 66, 76, 69, 95, 83, 73, 77, 80, 76, 69, 95, 80, 82, 73, 86, 65, 67, 89]
RSI_BLE_SIMPLE_PRIVACY -> [82, 83, 73, 95, 66, 76, 69, 95, 83, 73, 77, 80, 76, 69, 95, 80, 82, 73, 86, 65, 67, 89]
HRM-Pro:6507Ý  -> [72, 82, 77, 45, 80, 114, 111, 58, 54, 53, 48, 55, 221, 0]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
HMIdesk_174903A2 -> [72, 77, 73, 100, 101, 115, 107, 95, 49, 55, 52, 57, 48, 51, 65, 50]
nRF5x Mesh Light -> [110, 82, 70, 53, 120, 32, 77, 101, 115, 104, 32, 76, 105, 103, 104, 116]
HMIdesk_17490245 -> [72, 77, 73, 100, 101, 115, 107, 95, 49, 55, 52, 57, 48, 50, 52, 53]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
HMIdesk_17490116 -> [72, 77, 73, 100, 101, 115, 107, 95, 49, 55, 52, 57, 48, 49, 49, 54]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
HMIdesk_17490147 -> [72, 77, 73, 100, 101, 115, 107, 95, 49, 55, 52, 57, 48, 49, 52, 55]
HMIdesk_17490245 -> [72, 77, 73, 100, 101, 115, 107, 95, 49, 55, 52, 57, 48, 50, 52, 53]
nRF5x Mesh Light -> [110, 82, 70, 53, 120, 32, 77, 101, 115, 104, 32, 76, 105, 103, 104, 116]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
nRF5x Mesh Light -> [110, 82, 70, 53, 120, 32, 77, 101, 115, 104, 32, 76, 105, 103, 104, 116]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
HMIdesk_174903A2 -> [72, 77, 73, 100, 101, 115, 107, 95, 49, 55, 52, 57, 48, 51, 65, 50]
HMIdesk_1749013B -> [72, 77, 73, 100, 101, 115, 107, 95, 49, 55, 52, 57, 48, 49, 51, 66]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
UAT-3393 -> [85, 65, 84, 45, 51, 51, 57, 51]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
HMIdesk_17490245 -> [72, 77, 73, 100, 101, 115, 107, 95, 49, 55, 52, 57, 48, 50, 52, 53]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
HMIdesk_17490116 -> [72, 77, 73, 100, 101, 115, 107, 95, 49, 55, 52, 57, 48, 49, 49, 54]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
GFIÝÝ   -> [71, 70, 73, 221, 221, 0, 0]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
HMIdesk_174903E5 -> [72, 77, 73, 100, 101, 115, 107, 95, 49, 55, 52, 57, 48, 51, 69, 53]
nRF5x Mesh Light -> [110, 82, 70, 53, 120, 32, 77, 101, 115, 104, 32, 76, 105, 103, 104, 116]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
Forerunner 945 -> [70, 111, 114, 101, 114, 117, 110, 110, 101, 114, 32, 57, 52, 53]
HMIdesk_174903E5 -> [72, 77, 73, 100, 101, 115, 107, 95, 49, 55, 52, 57, 48, 51, 69, 53]
nRF5x Mesh Light -> [110, 82, 70, 53, 120, 32, 77, 101, 115, 104, 32, 76, 105, 103, 104, 116]
HUB_BLE -> [72, 85, 66, 95, 66, 76, 69]
Nordic_HRM -> [78, 111, 114, 100, 105, 99, 95, 72, 82, 77]
New connection: 0
Read Response event - Connection: 0, 3 = [78, 111, 114, 100, 105, 99, 220, 121, 158, 99]
Device Name = NordicÜyc status = BLEGattStatusCode.success
Heart Rate Received: [22, 180, 141, 1, 140, 1, 139, 1, 138, 1, 137, 1, 136, 1, 135, 1, 221, 221, 221, 221]
Heart Rate Received: [22, 190, 132, 1, 131, 1, 130, 1, 129, 1, 128, 1, 127, 1, 126, 1, 221, 221, 221, 221]
Heart Rate Received: [22, 200, 123, 1, 122, 1, 121, 1, 120, 1, 119, 1, 118, 1, 117, 1, 221, 221, 221, 221]
Heart Rate Received: [22, 210, 99, 1, 98, 1, 97, 1, 96, 1, 95, 1, 94, 1, 93, 1, 221, 221, 221, 221]
Heart Rate Received: [22, 220, 90, 1, 89, 1, 88, 1, 87, 1, 86, 1, 85, 1, 84, 1, 221, 221, 221, 221]
Heart Rate Received: [20, 230, 81, 1, 80, 1, 79, 1, 78, 1, 77, 1, 76, 1, 75, 1, 221, 221, 221, 221]
Heart Rate Received: [20, 240, 57, 1, 56, 1, 55, 1, 54, 1, 53, 1, 52, 1, 51, 1, 221, 221, 221, 221]
Heart Rate Received: [20, 250, 48, 1, 47, 1, 46, 1, 45, 1, 44, 1, 43, 1, 42, 1, 221, 221, 221, 221]
Heart Rate Received: [21, 4, 1, 39, 1, 38, 1, 37, 1, 36, 1, 35, 1, 34, 1, 221, 221, 221, 221]
Heart Rate Received: [21, 14, 1, 15, 1, 14, 1, 13, 1, 12, 1, 11, 1, 10, 1, 221, 221, 221, 221]
Closing

Corruption can be seen on lines 15, 55, and 72.

RE: Issues with characteristic values using the pc-ble-driver-py library

Jørgen Holmefjord — Thu, 15 Aug 2019 09:14:56 GMT

I tried reproducing this on a similar environment, but I'm not able to see this issue. Did you test with the HRS example from the SDK? Have you made any modifications to the pc-ble-driver-py libraries?

This is the output when I run the sample you posted above when testing against SDK HRS example:

>python nus_collector.py NRF51
        0 : COM58: 683716957
        1 : COM10: 681512033
        2 : COM57: 683088727

Enter your choice: 1
Serial port used: COM10
BBC micro:bit [vigav] -> [66, 66, 67, 32, 109, 105, 99, 114, 111, 58, 98, 105, 116, 32, 91, 118, 105, 103, 97, 118, 93]
BBC micro:bit [gaput] -> [66, 66, 67, 32, 109, 105, 99, 114, 111, 58, 98, 105, 116, 32, 91, 103, 97, 112, 117, 116, 93]
BBC micro:bit [vigav] -> [66, 66, 67, 32, 109, 105, 99, 114, 111, 58, 98, 105, 116, 32, 91, 118, 105, 103, 97, 118, 93]
BBC micro:bit [vigav] -> [66, 66, 67, 32, 109, 105, 99, 114, 111, 58, 98, 105, 116, 32, 91, 118, 105, 103, 97, 118, 93]
BBC micro:bit [gaput] -> [66, 66, 67, 32, 109, 105, 99, 114, 111, 58, 98, 105, 116, 32, 91, 103, 97, 112, 117, 116, 93]
BBC micro:bit [vigav] -> [66, 66, 67, 32, 109, 105, 99, 114, 111, 58, 98, 105, 116, 32, 91, 118, 105, 103, 97, 118, 93]
BBC micro:bit [vigav] -> [66, 66, 67, 32, 109, 105, 99, 114, 111, 58, 98, 105, 116, 32, 91, 118, 105, 103, 97, 118, 93]
LE-Nighthawk -> [76, 69, 45, 78, 105, 103, 104, 116, 104, 97, 119, 107]
BBC micro:bit [vigav] -> [66, 66, 67, 32, 109, 105, 99, 114, 111, 58, 98, 105, 116, 32, 91, 118, 105, 103, 97, 118, 93]
BBC micro:bit [vigav] -> [66, 66, 67, 32, 109, 105, 99, 114, 111, 58, 98, 105, 116, 32, 91, 118, 105, 103, 97, 118, 93]
LE-Nighthawk -> [76, 69, 45, 78, 105, 103, 104, 116, 104, 97, 119, 107]
BBC micro:bit [vigav] -> [66, 66, 67, 32, 109, 105, 99, 114, 111, 58, 98, 105, 116, 32, 91, 118, 105, 103, 97, 118, 93]
BBC micro:bit [vigav] -> [66, 66, 67, 32, 109, 105, 99, 114, 111, 58, 98, 105, 116, 32, 91, 118, 105, 103, 97, 118, 93]
TestDev -> [84, 101, 115, 116, 68, 101, 118]
BBC micro:bit [vigav] -> [66, 66, 67, 32, 109, 105, 99, 114, 111, 58, 98, 105, 116, 32, 91, 118, 105, 103, 97, 118, 93]
BBC micro:bit [vigav] -> [66, 66, 67, 32, 109, 105, 99, 114, 111, 58, 98, 105, 116, 32, 91, 118, 105, 103, 97, 118, 93]
New connection: 0
Read Response event - Connection: 0, 3 = [84, 101, 115, 0, 0, 0, 183]
Device Name = Tes   · status = BLEGattStatusCode.success
Heart Rate Received: [20, 250, 227, 0, 228, 0, 229, 0, 230, 0, 231, 0, 232, 0, 233, 0, 0, 0, 0, 0]
Heart Rate Received: [20, 240, 237, 0, 238, 0, 239, 0, 240, 0, 241, 0, 242, 0, 243, 0, 0, 0, 0, 0]
Heart Rate Received: [20, 230, 5, 1, 6, 1, 7, 1, 8, 1, 9, 1, 10, 1, 11, 1, 0, 0, 117, 116]
Heart Rate Received: [20, 220, 14, 1, 15, 1, 16, 1, 17, 1, 18, 1, 19, 1, 20, 1, 0, 0, 112, 113]
Heart Rate Received: [20, 210, 23, 1, 24, 1, 25, 1, 26, 1, 27, 1, 28, 1, 29, 1, 0, 0, 117, 116]
Heart Rate Received: [22, 200, 47, 1, 48, 1, 49, 1, 50, 1, 51, 1, 52, 1, 53, 1, 0, 0, 117, 116]
Heart Rate Received: [22, 190, 56, 1, 57, 1, 58, 1, 59, 1, 60, 1, 61, 1, 62, 1, 0, 0, 112, 113]
Heart Rate Received: [22, 180, 65, 1, 66, 1, 67, 1, 68, 1, 69, 1, 70, 1, 71, 1, 0, 0, 117, 116]
Heart Rate Received: [22, 170, 89, 1, 90, 1, 91, 1, 92, 1, 93, 1, 94, 1, 95, 1, 0, 0, 112, 113]
Heart Rate Received: [22, 160, 98, 1, 99, 1, 100, 1, 101, 1, 102, 1, 103, 1, 104, 1, 0, 0, 103, 97]
Closing

RE: Issues with characteristic values using the pc-ble-driver-py library

Scault — Mon, 12 Aug 2019 14:26:30 GMT

I am running Windows 10 and using Python 3.7.3. I am using pc-ble-driver version 0.12.0 which was installed through PyPi.

I have not tested this on another PC - it may not be feasible for me to do so, but I will look into it.

RE: Issues with characteristic values using the pc-ble-driver-py library

Jørgen Holmefjord — Mon, 12 Aug 2019 13:53:42 GMT

Sorry for the late reply.

Can you provide the following details about your environment?

Which OS are you running on?
Which Python version are you using?
Which pc-ble-driver-py version do you use?
Did you install through PyPi, or build from source?

I will try to replicate your setup as close as possible to try to reproduce this issue. By the way, did you test this on another PC as well?

RE: Issues with characteristic values using the pc-ble-driver-py library

Scault — Tue, 16 Jul 2019 21:51:54 GMT

Here's a trace of the on-air communication between the peripheral and the pc-ble-driver-py device:
ble-trace.pcapng

I did notice that the ADV_IND packets from the peripheral contain the correct advertising data including device name.

RE: Issues with characteristic values using the pc-ble-driver-py library

Jørgen Holmefjord — Tue, 16 Jul 2019 15:48:54 GMT

Can you provide a sniffer trace of on-air communication between the peripheral and the pc-ble-driver-py device? You can use nRFSniffer v2 to capture that. I have not seen this issue with the HRS collector example from GitHub and the stock HRS example from the SDK.

RE: Issues with characteristic values using the pc-ble-driver-py library

Scault — Tue, 16 Jul 2019 15:44:01 GMT

Yes, I have tried the Heart Rate Collector example in the repository and the same behaviour occurred.

RE: Issues with characteristic values using the pc-ble-driver-py library

Jørgen Holmefjord — Tue, 16 Jul 2019 15:33:45 GMT

Have you tried out the Heart Rate Collector example application found in the official pc-ble-driver-py repository? Do you see the same behavior with this application?

RE: Issues with characteristic values using the pc-ble-driver-py library

Scault — Fri, 05 Jul 2019 16:59:22 GMT

I am testing against a custom device that implements both FTMS and HRS. The device receives HR data from a heart rate monitor and re-transmits it over BLE along with its own FTMS data.

I am seeing the name corruption issue on other peripherals as well, not just the custom device.

Here is an example of the HRS data issue:

TesÝÝÝÝ -> [84, 101, 115, 221, 221, 221, 221]
New connection: 0
Read Response event - Connection: 0, 29 = [119, 44, 84, 143, 17, 144, 53, 19, 186, 102, 66, 192, 0, 0, 170, 12]
Device Name = Tes   ] status = BLEGattStatusCode.success
Read Response event - Connection: 0, 3 = [84, 101, 115, 0, 0, 0, 93]
Heart Rate Received: [23, 9, 48, 12, 0, 128, 248, 79, 72, 119]...
Data Length: 36664

Heart Rate Received: [32, 9, 125, 9, 0, 136, 84, 0, 114, 0]...
Data Length: 36663

Heart Rate Received: [20, 9, 96, 13, 0, 128, 192, 53, 83, 3]...
Data Length: 36667

Heart Rate Received: [32, 9, 125, 9, 0, 136, 84, 0, 114, 0]...
Data Length: 36663

Heart Rate Received: [23, 9, 48, 12, 0, 128, 57, 0, 16, 0]...
Data Length: 36664

Heart Rate Received: [32, 9, 125, 9, 0, 136, 84, 0, 114, 0]...
Data Length: 36663

Heart Rate Received: [23, 9, 48, 12, 0, 128, 57, 0, 16, 0]...
Data Length: 36664

Heart Rate Received: [32, 9, 125, 9, 0, 136, 84, 0, 114, 0]...
Data Length: 36663

Heart Rate Received: [23, 9, 48, 12, 0, 128, 57, 0, 16, 0]...
Data Length: 36664

Heart Rate Received: [32, 9, 125, 9, 0, 136, 84, 0, 114, 0]...
Data Length: 36663

Heart Rate Received: [23, 9, 48, 12, 0, 128, 57, 0, 16, 0]...
Data Length: 36664

Heart Rate Received: [32, 9, 125, 9, 0, 136, 84, 0, 114, 0]...
Data Length: 36663

Heart Rate Received: [23, 9, 48, 12, 0, 128, 57, 0, 16, 0]...
Data Length: 36664

Heart Rate Received: [17, 9, 208, 14, 0, 136, 8, 105, 85, 3]...
Data Length: 36806

Heart Rate Received: [32, 9, 125, 9, 0, 136, 84, 0, 114, 0]...
Data Length: 36663

Heart Rate Received: [23, 9, 48, 12, 0, 128, 57, 0, 16, 0]...
Data Length: 36664

Heart Rate Received: [32, 9, 125, 9, 0, 136, 84, 0, 114, 0]...
Data Length: 36663
Closing

The above results should be displaying a heart rate of 73 bpm. Upon using nRF Connect, the correct value can be seen.

I also tried testing the HR data with a standard BLE heart rate monitor and the expected data can be seen (in the format specified by org.bluetooth.characteristic.heart_rate_measurement.xml).

Note: the device name corruption can also be seen in this device.

MYZONE-0001586252 -> [77, 89, 90, 79, 78, 69, 45, 48, 48, 48, 49, 53, 56, 54, 50, 53, 50]
New connection: 0
Read Response event - Connection: 0, 22 = [144, 90, 227, 175, 48, 234, 141, 232, 246, 150, 100, 70, 92, 0, 2, 27]
Read Response event - Connection: 0, 3 = [77, 89, 90, 79, 78, 69, 45, 48, 48, 48, 49, 53, 56, 54, 50, 221, 221, 221, 221]
Device Name = MYZONE-00015862ÝÝÝÝ status = BLEGattStatusCode.success
Heart Rate Received: [22, 74, 27, 3, 107, 3, 148, 3, 169, 3, 112, 3, 3, 3, 31, 3, 221, 221, 221, 221]
Heart Rate Received: [22, 75, 61, 3, 45, 3, 1, 3, 12, 3, 12, 3, 54, 3, 78, 3, 221, 221, 221, 221]
Heart Rate Received: [22, 74, 26, 3, 2, 3, 149, 245, 111, 116]
Heart Rate Received: [1, 0, 28, 0]
Heart Rate Received: [22, 75, 26, 3, 2, 3]
Heart Rate Received: [110, 0, 1, 1]
Heart Rate Received: [22, 75, 26, 3]
Heart Rate Received: [1, 0, 255, 255]
Heart Rate Received: [22, 75, 59, 0, 67, 0]
Heart Rate Received: [22, 75, 26, 3]
Closing

RE: Issues with characteristic values using the pc-ble-driver-py library

Jørgen Holmefjord — Fri, 05 Jul 2019 09:27:55 GMT

Hi,

Which device are you testing this against? Are you running the HRS example from the SDK? Are you seeing this name issue with other peripherals as well, or only this device?

Could you give an example of the HRS data issue? The data should only contain the bpm value.

Best regards,
Jørgen