Indication- Server(Mobile Device) and Client(nRF51)

RE: Indication- Server(Mobile Device) and Client(nRF51)

Inspectron — Mon, 05 Oct 2015 11:19:12 GMT

Because I need the same solution for iOS. But I will try it on the Android Application. Thank you for the information with the reliable write.

RE: Indication- Server(Mobile Device) and Client(nRF51)

Hung Bui — Mon, 21 Sep 2015 12:48:40 GMT

I think it's a good solution. Just a workaround when Android doesn't have the call back for indication has been confirmed. I am not sure what's the case on iOS though.

But why do you want to have the server on the phone ? Why not having the server on the nRF51, then you can do a reliable write from the phone, which have more control over what is received on the nRF51. Have a look here.

RE: Indication- Server(Mobile Device) and Client(nRF51)

Inspectron — Mon, 21 Sep 2015 07:49:13 GMT

Hmm there is no call back when indication is confirmed? So I have a other solution in my mind. I could set up 2 characteristics. One for the data, which will give me information which button is pressed and is the button pressed or not. And the other characteristic would be like an ACK. Everytime I get a notification from the app, I would send on the other characteristic a notification, that the data is recieved.

I'm controling a motor with the app. I have a characteristic for moving up and one for moving down. up_write_handler is the function, which will be called when I get a notification from the mobile device.

RE: Indication- Server(Mobile Device) and Client(nRF51)

Hung Bui — Fri, 18 Sep 2015 12:42:12 GMT

Hi Inspectron,

On the nRF51 side, the difference when it's receiving notification or indication are small. The stack handle the ACKing for the application. So on the application it's almost the same, you receive BLE_GATTC_EVT_HVX. Only the type in ble_gattc_evt_hvx_t are different when you receive the event.

I don't think you will receive any call back on the app on the phone when the indication is confirmed (unlike on nRF51 side). But there is a call back when the notification/indication is sent (onNotificationSent ) have you used it ?

I don't quite understand "up_write_handler", what do you plan to do with that ?