• State Not Answered
  • Replies 3 replies
  • Subscribers 71 subscribers
  • Views 1936 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 100942
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

PIN Code timeout event

Manuel Urfer

Hi

I'm using the nrf51822 with Softdevice S110. I want to find out why a pairing has not worked, PIN-Code was wrong, PIN-Code timeout.

Which events I can use for that failures?

Parents
  • 0

    Sorry for the delay, but you will get a BLE_EVT_GAP_AUTH_STATUS event, with the auth_status field set to something else than BLE_GAP_SEC_STATUS_SUCCESS:

    • In the case of timeout, it will be set to BLE_GAP_SEC_STATUS_TIMEOUT.
    • In the case of wrong key entered, BLE_GAP_SEC_STATUS_CONFIRM_VALUE.
    • In the case of a cancel or too long or too short passkey, BLE_GAP_SEC_STATUS_PASSKEY_ENTRY_FAILED.

    The above was tested with an iPhone. Beware that there could be slight differences in the exact error codes used between different Centrals. MCP seems to for example use BLE_GAP_SEC_STATUS_PASSKEY_ENTRY_FAILED both for wrong key and wrong key format (i.e. too long or too short).

Reply
  • 0

    Sorry for the delay, but you will get a BLE_EVT_GAP_AUTH_STATUS event, with the auth_status field set to something else than BLE_GAP_SEC_STATUS_SUCCESS:

    • In the case of timeout, it will be set to BLE_GAP_SEC_STATUS_TIMEOUT.
    • In the case of wrong key entered, BLE_GAP_SEC_STATUS_CONFIRM_VALUE.
    • In the case of a cancel or too long or too short passkey, BLE_GAP_SEC_STATUS_PASSKEY_ENTRY_FAILED.

    The above was tested with an iPhone. Beware that there could be slight differences in the exact error codes used between different Centrals. MCP seems to for example use BLE_GAP_SEC_STATUS_PASSKEY_ENTRY_FAILED both for wrong key and wrong key format (i.e. too long or too short).

Children
No Data
Related
Terms of service