https://devzone.nordicsemi.com/f/nordic-q-a/48952/nrf52-and-bluez-dlen-set-to-27-by-defaultHi, We are developing sensors with the nRF52840. We send data packets of approx. 160 bytes with 25 Hz. We interact with a PC (Ubuntu - bluez 5.48) which works with one sensor totally fine. But if we use a second one it gets always the wrong MTU sizeen-USTelligent Community 13Tue, 25 Jun 2019 15:36:09 GMThttps://devzone.nordicsemi.com/thread/194712?ContentTypeID=1Tue, 25 Jun 2019 15:36:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3b7c85e4-67de-4ded-833e-2f660f03b5c8Constantin<p>Okay found the issue. It was the GAP_LENGTH in combination with BT4.0 dongle. It seems that there are only few dongles and laptops supporting BLE4.2 available.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/194634?ContentTypeID=1Tue, 25 Jun 2019 11:48:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d340bf4d-1756-4e8c-ba11-34089f1ce046bjorn-spockeli<p>HI Constantin,&nbsp;</p> <p>are you able to capture a trace of the on air data packets using the <a href="https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Sniffer">nRF Sniffer v2</a>? By looking at the on air date we should be able to see if the correct dlen is communicated to bluez or not.&nbsp;</p> <p>Best regards</p> <p>Bj&oslash;rn</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/194544?ContentTypeID=1Tue, 25 Jun 2019 08:21:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2ba403e5-3c39-4530-a96a-330d369abe83Constantin<p>The errors prompted by btmon are:</p> <p>unexpected start frame followed by&nbsp;unexpected continuation</p><div style="clear:both;"></div>