what is causing our unexpected disconnections?

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

cross mob
Anonymous
Not applicable

We have a central that alternately connects to 2 peripherals.

Sometimes, just after it attempts to connect, there is no connUp callback, just "bleprofile_connDown stop Idle Timer" and then the connDown callback, and no callback for connUp/encrypt/bond.

Our LOOP is essentially:

Start scan and get Bluetooth address of each peripheral.

Callback fine timer to STOP SCAN and

start connection "blecm_CreateConnection".

[ >>> DISCONNECTION SOMETIMES OCCURS HERE <<< ]

Callback for connUp

Callback for encrypt

Callback for bond

send write-request
and

receive multiple notifications.

blecm_disconnect(BT_ERROR_CODE_CONNECTION_TERMINATED_BY_LOCAL_HOST)

Callback for connDown

Select next peripheral and

REPEAT LOOP

0 Likes
1 Solution
Anonymous
Not applicable

This was caused by unexpected

bleprofile_connDown stop Idle Timer"   (see subsequent question about this).

This question

View solution in original post

0 Likes
1 Reply
Anonymous
Not applicable

This was caused by unexpected

bleprofile_connDown stop Idle Timer"   (see subsequent question about this).

This question

0 Likes