Problem when client disconnection during Indication/confirmation phase.

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Anonymous
Not applicable

Currently using 20737tag with SDK2.0.1, we implement a mechanism by handset triggering a series of indication/confirmation
data exchange by calling bleprofile_sendIndication() in device. But unfortunately, once client tries to disconnect the link while
device is in wait state of confirmation signal after indication has been started. Then the new re-connection will fail to trigger
indication/confirmation machine again owing to that lower layer of device still recognizes as waiting of confirmation state.
Is there any BLE API to reset 737tag's indication/confirmation state machine or reset; otherwise it can be a problem like this.

0 Likes
1 Solution
asridharan
Employee
Employee
10 comments on KBA 5 comments on KBA First comment on KBA

In your connection_down() callback function, try this:

void application_conn_down(void)

{

     // ... all other connection down.

     extern void leatt_timeoutCallback( UINT32 );

     leatt_timeoutCallback(0);

}

View solution in original post

6 Replies