MTU negotiation not effective? #14
Labels
conclusion: invalid
Issue/PR not valid
topic: code
Related to content of the project itself
type: imperfection
Perceived defect in any part of project
Hi
I am using v1.1.0 of the library with a Nano 33 Iot (NINA w10) and Android API 26. When I request a larger MTU on central:
bleQueue.requestMtu(256);
I get an apparent success:
I then write this MTU to the peripheral and use the nearest lower power of 2 (I tried various values, all the same):
However, the byte[] data received on central via:
final byte[] data = characteristic.getValue();
has data.length: 34
I found a variable
_maxMtu
inutility/ATT.cpp
set to the conventional 23:ArduinoBLE/src/utility/ATT.cpp
Line 89 in 30e2cac
but changing this has no observable effect.
Is this a user, device or code issue?
EDITED TO UPDATE:
It was a user issue:
BLECharacteristic dataCharacteristic(DATA_CHARACTERISTIC_UUID, BLERead | BLEIndicate, origMTUsize);
The text was updated successfully, but these errors were encountered: