• State Not Answered
  • Replies 4 replies
  • Subscribers 74 subscribers
  • Views 2966 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 289138
Options

connect/disconnect reasons

PingISTL

Dear All

I am trying connect/disconnect function with the DK, it gives me some reason codes, my app is based on central_multilink, which I cannot find their meanings, could someone point me to the right direction please? some messages are shown below: some are connected and then disconnected, some doesn't connect at all.

Failed to connect to EF:A1:9A:8B:2E:F9 (public) (2)

Connected (1): AC:23:3F:56:1A:BF (public)

Disconnected: AC:23:3F:56:1A:BF (public) (reason 0x13)

Connected (1): 02:67:15:4B:4E:76 (public)

Disconnected: 02:67:15:4B:4E:76 (public) (reason 0x3e)

Disconnected: 02:67:15:4B:4E:76 (public) (reason 0x16)

 out of these, I only know the reason 0x16, which is disconnected by me.

Thank you.

Ping

Parents
  • 0

    Hi,

    Those are error codes defined by Bluetooth SIG and part of the Bluetooth specification. In particular:

    0x13 is "remote user terminated connection", and means the other device ended the connection (or stopped broadcasting packets.)
    0x16 is "connection terminated by local host", and means your device ended the connection (or stopped broadcasting packets.)
    0x3e is "connection failed to be established", and means the attempt to set up a connection failed.

    For a full list of these error codes, see the Bluetooth Core Specification, Volume 1, Part F Controller error codes. There is a short listing in section 1 Overview of error codes, and longer descriptions of the various codes in section 2 Error code descriptions.

    Please note that from the central point of view, the connection is considered established when a connection request has been successfully sent (e.g. as a response to a connectable advertising.) In other words the central considers the connection established without any confirmation from the peripheral. If the peripheral never replies, this will be seen from the central side as a successful connection where the peripheral timed out leading to disconnection, while from the peripheral's perspective there was no connection in the first place.

    Regards,
    Terje

Reply
  • 0

    Hi,

    Those are error codes defined by Bluetooth SIG and part of the Bluetooth specification. In particular:

    0x13 is "remote user terminated connection", and means the other device ended the connection (or stopped broadcasting packets.)
    0x16 is "connection terminated by local host", and means your device ended the connection (or stopped broadcasting packets.)
    0x3e is "connection failed to be established", and means the attempt to set up a connection failed.

    For a full list of these error codes, see the Bluetooth Core Specification, Volume 1, Part F Controller error codes. There is a short listing in section 1 Overview of error codes, and longer descriptions of the various codes in section 2 Error code descriptions.

    Please note that from the central point of view, the connection is considered established when a connection request has been successfully sent (e.g. as a response to a connectable advertising.) In other words the central considers the connection established without any confirmation from the peripheral. If the peripheral never replies, this will be seen from the central side as a successful connection where the peripheral timed out leading to disconnection, while from the peripheral's perspective there was no connection in the first place.

    Regards,
    Terje

Children
No Data
Related
Terms of service