I'm currently evaluating the Shorter Connection Intervals feature of BT 6.2, and its use for low-latency HID applications. I have seen the updated HID mouse sample (https://nrfconnectdocs.nordicsemi.com/ncs/latest/nrf/samples/bluetooth/peripheral_hids_mouse/README.html) has SCI support, with a minimum of 750us connection interval. What I find strange in this sample is that the mouse data is split into 2 reports of 3 bytes each. Is this because the reduced interval limits the payload size? It would be great if the formula to calculate the effective GATT notification payload size was made available, so developers can understand the necessary tradeoffs between connection interval (or frame space if relevant) and usable payload size.
The bt_gatt_notify_cb() method returns -ENOMEM if the payload size exceeds what the MTU allows, is there a similar mechanism for SCI imposed limitations, or is the MTU adjusted to match the SCI parameters?
Thanks in advance.
