RE: BLE UART simple authentication after connection made and disconnect if not passed, not pairing

Edvin — Tue, 18 Sep 2018 10:19:05 GMT

I see. It shouldn't be too difficult setting up a timer. Just remember to change from TIMER0 to one of the other timers if you copy from one of the example\peripheral\ examples, since the softdevice uses TIMER0.

Best regards,

Edvin

RE: BLE UART simple authentication after connection made and disconnect if not passed, not pairing

Alex — Mon, 17 Sep 2018 14:36:10 GMT

Thank you for helping out, what I ended up doing is actually incrementing counter variable in each time program hits it and measuring how many times CPU hits it in 1 seconds or so, since precise timing is not that important at this moment but rather just have general delay. That worked for now, I am going to revisit using timers attempt in couple days.

RE: BLE UART simple authentication after connection made and disconnect if not passed, not pairing

Edvin — Thu, 13 Sep 2018 11:53:57 GMT

Hello,

Can you please describe what happens when you try to add the timer? Do you get an error somewhere? Does it start advertising? Does the timer start, and do you get a timeout, or none of the above?

A typical scenario is that the peripheral examples uses the TIMER0 instance. That works well on it's own, but when you blend the SoftDevice into it to enable BLE, the TIMER0 is reserved for the softdevice, and it will cause an error.

Check your APP_ERROR_CHECK(err_code) calls. If any of them receive an err_code != 0, then the application will restart. I see that you use nRF51. What SDK do you use? SDK12.3.0?

Try to define DEBUG in your preprocessor defines, and set a breakpoint in the app_error_handler in app_error.c. If the application stops there, then you can get a pointer to which APP_ERROR_HANDLER that received the err_code != 0.

This being said, what you are trying to implement sounds pretty much like what pairing is already doing. It is ok to do what you describe, and if protecting your data is not important, you should be fine. But if a user does not write the passcode if the peripheral requires it, it will automatically disconnect, and start advertising again.

Even if a device is bonded, it is still possible to disable the whitelist during advertising, so that any device can connect to it. This is typically used in Bluetooth devices. The first time you connect to a device, you press a button with the bluetooth logo, and then you will find it. The next time, you can usually connect to it without pressing the button, because they are already paired.

Best regards,

Edvin