Data length update with pc-ble-driver-py library

RE: Data length update with pc-ble-driver-py library

Vidar Berg — Fri, 20 Dec 2019 09:25:45 GMT

Update: it should be fixed by https://github.com/NordicSemiconductor/pc-ble-driver-py/pull/149.

RE: Data length update with pc-ble-driver-py library

Vidar Berg — Wed, 18 Dec 2019 08:48:23 GMT

The task has been added to the current sprint, which ends January 7, but as there are a few holidays in the next couple of weeks, I'm not sure how much time they will get to spend on it. But were you able to get longer data packets as I did? You can use the debug output from the peripheral to confirm.

RE: Data length update with pc-ble-driver-py library

Imen — Tue, 17 Dec 2019 14:16:26 GMT

Any update on the data length problem? thanks

RE: Data length update with pc-ble-driver-py library

Vidar Berg — Thu, 05 Dec 2019 07:13:06 GMT

I will update the ticket when I have more details. Hopefully, it's an easy fix.

RE: Data length update with pc-ble-driver-py library

Imen — Wed, 04 Dec 2019 14:20:29 GMT

Thank you for confirming the problem, I will be very happy to know when it is resolved, thank you

Imen

RE: Data length update with pc-ble-driver-py library

Vidar Berg — Wed, 04 Dec 2019 14:12:29 GMT

Sorry, I thought v.0.11.4 was the latest, and I wasn't sure how you were able to use API v5 with that release. What I see now after updating to 0.14 is that the packet length gets correctly updated when receiving the request from the peer device, but the parameters reported to on_gap_evt_data_length_update() were still invalid like they were in your case.

I used the heart rate collector script for my test and only added on_gap_evt_data_length_update() function so I could log the DL parameters.

    def on_gap_evt_data_length_update(
        self, ble_driver, conn_handle, data_length_params
    ):
        print("Max rx octets: {}".format(data_length_params.max_rx_octets))
        print("Max tx octets: {}".format(data_length_params.max_tx_octets))
        print("Max rx time: {}".format(data_length_params.max_rx_time_us))
        print("Max tx time: {}".format(data_length_params.max_tx_time_us))

Result from one of the tests I di:

Max rx octets: 400
Max tx octets: 151
Max rx time: 0
Max tx time: 0

And the corresponding result from the ble_app_hrs peripheral SDK example running on the other side:

<debug> nrf_ble_gatt: Data length updated to 151 on connection 0x0.
<debug> nrf_ble_gatt: max_rx_octets: 151
<debug> nrf_ble_gatt: max_tx_octets: 151
<debug> nrf_ble_gatt: max_rx_time: 1320
<debug> nrf_ble_gatt: max_tx_time: 1320

I have not been able to figure out why the event parameters are not correctly forwarded from the Softdevice, but it looks like it might be a bug in the driver implementation. I have reported this as a bug internally.

Data Length Update Procedure

RE: Data length update with pc-ble-driver-py library

Imen — Tue, 03 Dec 2019 13:28:50 GMT

I am testing with SD API v5, I thought that it could work with a more recent release. I added the event in the library and the peripheral I am using logs the new values but the central returns random corrupted data everytime as you can see above

RE: Data length update with pc-ble-driver-py library

Vidar Berg — Tue, 03 Dec 2019 13:18:06 GMT

Hello Imen,

I tried installing the latest 0.11.4 release to replicate this, but it appears to only support SD API v3 for the 52 series. Are you testing with a different branch?

Regards,

Vidar

RE: Data length update with pc-ble-driver-py library

Imen — Tue, 03 Dec 2019 09:39:22 GMT

More details about trying to get data_length_update to work

Peripheral flashed on a nrf52832 with nRF5_SDK_15.3.0 ble_app_multirole_lesc exemple.

When I do a ble_gap_data_length_update() with all parameters set to BLE_GAP_DATA_LENGTH_AUTO “0” (or any other value), none error is returned and I get the right event on_gap_evt_data_length but with strange values that change after each try for on the pc-ble-driver-py:

Exemple with all parameter set to 0 (BLE_GAP_DATA_LENGTH_AUTO):

Result on the pc-ble-driver-py (nrf52832)

Max tx octets = 27 (ok)
Max rx octets = 483 (??)
Max tx times us = 256 (??)
Max rx time us = 0 (??)

Result on the JLink viewer connected to the peripheral nrf52832 with ble_app_multirole_lesc, I have the right parameters:

BLE_GAP_EVT_DATA_LENGTH_UPDATE: Data length update to 27 on connection 0x1

Max tx octets = 27 (ok)
Max rx octets = 27 (ok)
Max tx times us = 2120 (ok)
Max rx time us = 2120 (ok)

I get the parameters with following lines:

print("data_length_params max_tx_octets = " + str(data_length_params.max_tx_octets))

print("data_length_params max_rx_octets = " + str(data_length_params.max_rx_octets))

print("data_length_params max_tx_time_us = " + str (data_length_params.max_tx_time_us))

print("data_length_params max_rx_time_us = " + str (data_length_params.max_rx_time_us))

Other exemples call ble_gap_data_length_update() with BLEGapDataLengthParams(max_tx_octets=100, max_rx_octets=100, max_tx_time_us=0, max_rx_time_us=0):

On the Central with pc-ble-driver:

Max tx octets = 27 (ok)
Max rx octets = 1000 (??)
Max tx times us = 256 (??)
Max rx time us = 0 (??)

Other try:

Max tx octets = 27 (ok)
Max rx octets = 20850 (??)
Max tx times us = 0 (??)
Max rx time us = 29184 (??)

Other try:

Max tx octets = 14363 ((??))
Max rx octets = 192 (??)
Max tx times us = 0 (??)
Max rx time us = 0 (??)

With the JLink viewer connected to the peripheral nrf52832 with ble_app_multirole_lesc I have the good parameters:

BLE_GAP_EVT_DATA_LENGTH_UPDATE: Data length update to 27 on connection 0x1

Max tx octets = 27 (ok)
Max rx octets = 27 (ok)
Max tx times us = 912 (ok)
Max rx time us = 912 (ok)

Do you have any idea what makes the event get me different values everytime with the same config asked? I believe the problem comes form pc-driver-ble-py knowing that the peripheral gets the right values

Thanks, Imen