Ticket Created
over 4 years ago

WERETECH-8478

messages from BTLE GATT server truncated at 20 bytes

All messages from a BTLE GATT server are truncated at 20 bytes.

The server can be tested against a different client and the full payload is visible (in my case 150 bytes).

This issue is reported by other users as well (see https://forums.garmin.com/developer/connect-iq/f/q-a/196823/bluetooth-low-energy-mtu-size-for-characteristics)

As 20 bytes is the default MTU size, I guess this bug might be MTU size related.

5458292
Parents
  • over 4 years ago

    My understanding is that the payload should be split across multiple packets if it exceeds the size of the MTU.  However, this is my first foray into BLE, so my understanding may be very worng..

Comment
  • over 4 years ago

    My understanding is that the payload should be split across multiple packets if it exceeds the size of the MTU.  However, this is my first foray into BLE, so my understanding may be very worng..

Children
  • over 4 years ago in reply to Michael

    I have word back from my team and they are hoping to get a little more info:

    "Can we confirm the specific format and type of message being sent? Can we capture the desired behaviour using nRF Connect app on Android and send us some annotated logs?"

    Wondering if either of those are something you might be able to grab?

    Thanks,

    Coleman