Hi,
Device: NRF53
I'm trying to send 3 notify packets in a 15ms connection internal but I can send 2.
I'm using Nrf connect and Zephyr. is there a limit or a define to set this.
Thank you for any guidance and help
Regards
Hi Neil
Looking at his sniffer trace I see that he sent longer packets (35 bytes, including the 3 byte attribute header).
Clearly this is long enough to loosen the timing enough so that you can upload more packets during the connection event.
If your end goal is to maximize throughput, rather than sending many small packets, this is a simple fix to the problem. Just ensure you use a characteristic that supports longer packets (the heart rate measurement characteristic does not).
Best regards
Torbjørn
Morning Torbjørn,
The end goal is to be able to send a minimum of 3 x160 byte packets every 15ms interval so this should be fine. My new issue is that the original project is on an older SDK version that the fix doesn't work on but the fix for that is to update the sdk to the latest.
Thanks for all your help.
Hi Neil
In that case the fix should probably not be needed, if you are sending 160 byte packets.
Migrating to a newer SDK should be less of a hassle now than it was in the old days (with the nRF5 SDK), but this depends on how complex your project is obviously.
The best of luck
Best regards
Torbjørn