Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
If two devices lose a connection after the supervisor timeout set in lel2cap_sendConnParamUpdateReq() expires, what should be done to fix it? Should I expect that an attempt to reconnect will work? I am trying to determine if I should use a low supervisor timeout and then quickly try to reestablish communication again OR set a long supervisor timeout and let the devices keep trying to talk with each other for as long as possible.
I have the connection parameters currently set to lel2cap_sendConnParamUpdateReq(6, 6, 0, 50) so that the central and peripheral can communicate to one another quickly. But is there anyway to get a callback when one of the communication slots every 7.5ms is clobbered by noise or congestion? How can I tell from the application how many of these 7.5ms communication slots are getting lost?
Once a disconnect occurs due to devices going out of range, how can I quickly reconnect when they come back into range?
What is the min and max allowable values for the supervisor timeout, the fourth parameter in the above function?