BLE_GAP_EVT_DATA_LENGTH, BLE_GATT_EVT_DATA_LENGTH, and ATT MTU size

RE: BLE_GAP_EVT_DATA_LENGTH, BLE_GATT_EVT_DATA_LENGTH, and ATT MTU size

Edvin — Tue, 24 Sep 2019 09:25:03 GMT

I wasn't able to locate the example you are speaking of. SDK12.0.0 doesn't contain the throughput example.

The only thing I notice that has changed from the earlier examples til the latest one is that you have data length extension which could only be turned on and off before, which you can now set the length of. Is that what you are asking?

RE: BLE_GAP_EVT_DATA_LENGTH, BLE_GATT_EVT_DATA_LENGTH, and ATT MTU size

rolandash — Mon, 23 Sep 2019 15:33:44 GMT

Edvin

You are correct. I looked into source code of

nrf_ble_gatt_data_length_set, and it actually increased options and BLE_GAP_EVT_DATA_LENGTH_UPDATE still available.

I am not sure which version of SDK exactly I was compared, probably v12.0 I think. If you look into the implementation of data_len_cmd and you should find the difference.

I think my question still focus on what is the difference between BLE_GATT_EVT_DATA_LENGTH and BLE_GAP_EVT_DATA_LENGTH. Are they intended to replace each other?

In many occurrence in Nordic document now just use the phrase "data length", and one does not know which "data length" it is talking about.

RE: BLE_GAP_EVT_DATA_LENGTH, BLE_GATT_EVT_DATA_LENGTH, and ATT MTU size

Edvin — Mon, 23 Sep 2019 12:15:25 GMT

Hello,

From what SDK do you compare the SDK15.2.0 with?

Well. The point of drivers and libraries is that the user shouldn't have to work down on the bare metal. That being said, I don't think any possibilities has been removed in the throughput example. I actually think that some more options are added.