PINCODE

RE: PINCODE

duckduck — Fri, 23 Sep 2016 07:00:45 GMT

Hi Pål Håland

For BLE, i know that it is possible to generate the passeky from the S130, but why can't i chose to be static if my device does not have any display or keypad. I did saw some example on the UART static passkey example before. Hope you can clarify this point. Thanks...

RE: PINCODE

Gabriel — Wed, 02 Jul 2014 17:04:12 GMT

Thats awesome! Thank you for the update.

RE: PINCODE

Pål Håland — Wed, 02 Jul 2014 08:10:04 GMT

With the latest softdevice www.nordicsemi.com/.../S110-SoftDevice-v7.0 you will be able to set a static passkey.

By using the API call sd_ble_opt_set() with the structure ble_gap_opt_passkey_t, then the passkey display event will come with the passkey you set.

RE: PINCODE

Ole Morten — Fri, 30 Aug 2013 07:38:16 GMT

If you can live with not using a passkey, and have a button or similar as input, I suggest that you go to bonding mode only when you press the button, and at all other times use advertising with whitelisting (or don't advertise at all, if you have no bonding information). This will ensure

that you can only connect to a new device after having pressed the button (possibly for a certain length or pattern), and
that no other device can connect to it, once it has been bonded with one Central.

The usage of whitelisting and bonding, through the SDK's bond manager is shown for example in the ble_app_proximity for nrf6310.

RE: PINCODE

Gabriel — Fri, 30 Aug 2013 05:27:54 GMT

Hi again , trying to summarize,

I need some way to authorize the pairing from the peripheral side. Imagine that you have a device and only want a specific smartphone to connect to it, this is my case. So if it is not possible to do it with a passkey because the device dont have a keyboard, it could be possible by holding a button or something similar?

My device has to buttons which could be use for pairing.

RE: PINCODE

Gabriel — Thu, 29 Aug 2013 09:21:59 GMT

Thank you very much for the answer.

I see that is much more complicated than I was thinking. Could you recommend me another way to do something similar? The peripheral to "authorize" the central on the first connection.

RE: PINCODE

Ole Morten — Thu, 29 Aug 2013 07:43:51 GMT

With BLE, it isn't really possible to use a passkey for bonding as long as one of the devices doesn't have a keyboard or display. Table 2.4 in the Bluetooth Core Specification, Volume 3, Part H, section 2.3.5.1 shows which bonding methods are doable depending on the I/O capabilities of the devices in question.

It could in principle be possible to implement something similar to a passkey in the application, but this could easily become quite complicated, and isn't something I'd normally recommend.

(Just for completeness: If you have complete control over both ends, you could in principle set both devices to be KeyboardOnly, in which case the table would give Numeric comparison as the method. This means that the user is supposed to enter the same passkey on both devices, and this could in principle then be done by having a static passkey label on one of them and asking the user to enter this on the other device. However, most Central devices (smartphones, tablets, PCs) don't give you such control over the I/O capabilities, making this impossible for most practical use cases.)

RE: PINCODE

Gabriel — Thu, 29 Aug 2013 06:54:36 GMT

Hi,

I have a nRF51 peripheral with no Display nor keyboard and a mobile phone. I want when the mobile try to connect to the nRF this one ask to the phone for a pincode for bonding. Then if the phone is bonded and try to connect, will not be ask for the pincode.

I think that this is a common feature in Bluetooth connections, I could be wrong...

Thanks!!

RE: PINCODE

Pål Håland — Thu, 29 Aug 2013 05:26:01 GMT

Hi, can you elaborate what you are trying to achieve?

Is it to pair the phone with the peripheral? Does the peripheral have a display or keyboard? In Bluetooth low energy the pairing pin will be a 6 digit key. It will be generated by the device that have the display, and can not be fixed.