Central S120 and Authenticate

RE: Central S120 and Authenticate

Frederic — Wed, 19 Feb 2014 14:23:55 GMT

Ok, thanks a lot :) The whitelist was the problem.

RE: Central S120 and Authenticate

Ole Morten — Wed, 19 Feb 2014 10:10:21 GMT

Could it be that the proximity application is already bonded to some other Central? If so, it will advertise with a whitelist for 30 s upon start, in which period it will be impossible for any other than the already bonded Central to connect.

If this is the case, you can either delete bond information from the proximity device, or modify the code of it so that it doesn't use whitelisting. Deleting bond information can be done by holding button 1 when powering on the kit.

RE: Central S120 and Authenticate

Frederic — Tue, 18 Feb 2014 17:47:47 GMT

My current application is based on the BLE Heart Rate Collector Example for nrf6310 board. For testing I have now deleted everything except for the connection manager. The connection manager is configured for auto connect on match and the policy is CONN_MNGR_CONNECT_POLICY_DEV_NAME. The name to search for is Nordic_Prox.

For testing i just want to establish a connection to the proximity peripheral. The problem is that i get several connection (CONN_MNGR_CONN_COMPLETE_IND) and disconnection events (CONN_MNGR_DISCONNECT_IND). The disconnection event reason is always BLE_HCI_CONN_FAILED_TO_BE_ESTABLISHED (0x3E). After about 3 to 5 disconnect events the connection is established permanently and the advertising LED from proximity server stop flashing.

To establish a connection, it can take up to 30 sec. Thats a little bit long for a BLE device. What reasons are there why I get so often the event BLE_HCI_CONN_FAILED_TO_BE_ESTABLISHED?

RE: Central S120 and Authenticate

Ole Morten — Tue, 18 Feb 2014 15:39:16 GMT

I'm not quite sure I understand what you mean. Can you please check the reason field of the disconnect event struct, to see what kind of disconnect you get?

Also, if possible, I think it would be helpful if you could share the complete application you're working with. Can you either edit your original question here, and attach it there, or if you don't want to share it here in the open, please open a support case and include it there?

RE: Central S120 and Authenticate

Frederic — Tue, 18 Feb 2014 15:23:23 GMT

The problem is that I get back a disconnect event after the connect event. In addition, the advertising LED is still flashing after i get the connect event. But after a while the LED will stop flashing. When I press the connect button in the Master Control pane the advertising LED stop flashing immediately. Therefore, I think there is a basic problem when establishing a connection with central stack. But so far i can't finde my mistake.

RE: Central S120 and Authenticate

Ole Morten — Mon, 17 Feb 2014 14:30:43 GMT

There are currently no SDK example showing how to do bonding in the Central role, so to do this, you'll have to refer to the MSCs available as part of the S120 documentation. After initially bonding once, sharing keys, this MSC shows how you'd reuse those previously exchanged keys on subsequent connections.

Your general flow seems reasonable for a first time bond. As you can see in ble_err.h and nrf_error.h, the error code 0x3001 translates to BLE_ERROR_INVALID_CONN_HANDLE, indicating that you supply an invalid connection handle to the ble_db_discovery_start() function. Could that be the problem?

RE: Central S120 and Authenticate

Frederic — Mon, 17 Feb 2014 09:32:16 GMT

no one can help?

RE: Central S120 and Authenticate

Frederic — Fri, 14 Feb 2014 19:10:06 GMT

Now i use the ble_central_bondmngr.c for bonding process.

With the connection manager i search for the proximity service. I get the event CONN_MNGR_CONN_COMPLETE_IND. After this event i get a CONN_MNGR_DISCONNECT_IND event and then a CONN_MNGR_CONN_COMPLETE_IND event again and so on... With master control panel all works great.