• State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 89 subscribers
  • Views 1914 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 281621
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Trouble connection multiple times : Bonding, error: 133

c.tessierpiart

Hi, 

I am trying to integrate the CTS (Clock Time Service) within my application. My current application is heavily based on the BLE UART from SDK 17.1 and I tried to integrate parts of the exemple cts from the same SDK.

I don't have any trouble connecting once or twice but systematically, the third connection resulting in the following error : 

<info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Bonding, error: 133

As CTS needs bonding (or is it pairing) to work, the pairing method I use is very similar to the one in CTS.

Furthermore, I am trying to use an Apple smartphone with a custom application and the BLE service send the callback "Readin not permitted" and I think this issue is linked with the pairing problem.

Best Regards,

Charles

Parents
  • 0

    Hi Charles

    We will be short on staff during the Holiday period, and delayed replies must be expected. We will be back to full staff on January 3rd. Happy holidays and happy new year!

    When you say you're connecting multiple times, can you explain what you mean about that? Are you trying to connect to multiple devices, or do you connect, disconnect, and connect again to the same device and so on?

    Are you only testing with an Apple iPhone as a central? I'm asking because the 133 error generally is seen on Android devices. Can you provide a detailed explanation of how you cause this error to occur. You can also try using the nRFConnect application for iOS/Android to see if you can recreate the issue there, where you also can get debug information from the phone side.

    Best regards,

    Simon

Reply
  • 0

    Hi Charles

    We will be short on staff during the Holiday period, and delayed replies must be expected. We will be back to full staff on January 3rd. Happy holidays and happy new year!

    When you say you're connecting multiple times, can you explain what you mean about that? Are you trying to connect to multiple devices, or do you connect, disconnect, and connect again to the same device and so on?

    Are you only testing with an Apple iPhone as a central? I'm asking because the 133 error generally is seen on Android devices. Can you provide a detailed explanation of how you cause this error to occur. You can also try using the nRFConnect application for iOS/Android to see if you can recreate the issue there, where you also can get debug information from the phone side.

    Best regards,

    Simon

Children
  • 0 in reply to Simonr

    Hi,

    I may have been unclear with my issue. 

    I have two issues that will hopefully be solve by one thing. The major issue is when I connect and diconnect multiple times using an NRF52840 Dongle and NRF Connect. In that case I receive the 133 error message.

    The minor issue is when I test things with an Apple Device. When the Application rties to read a characteristic, it return a "Reading not permitted" message. As the Application is still very young, we did not test the same issue.

    What makes me hope that the two issues might be solved at once is that I botched a bit the merge part of the CTS and UART exemple. The former using Peer manager and the latter only doing a basic Advertising. 

Related