what hex value to be written on the the MCP (immediate alert service) for IOS

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

Hung Bui — Fri, 29 Apr 2016 13:45:35 GMT

Prabhudurai: I don't know what else I can help you here. I don't have other advice beside what I suggested before. You need to understand what happens when the device doesn't want to bond and disconnect. Sniffer trace should be provided. Please provide the hex file that you used to test. Also please do nrfjprog --readcode filename.hex and provide me the filename.hex, after you have bonded with the iOS device.

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

MARTIN FR — Wed, 27 Apr 2016 14:08:11 GMT

Thank you so much for your kind reply yes you were right after the first bond then i disconnected and trying reconnect with theNRF51DK device but it wont function or receive any information from the IPhone NRFMCP and NRF TOOLBOX , but its completely oppoiste it is working very well on the android phone NRFMCP/NRF TOOLBOX, am also thinking in the same way how can i store the bonded information do i need to add any external functions or what should i do for that issue?

I have also tried the proxmity example on the NRFTOOLBOX by using IOS its got connected for the first bond after disconnecting for the first time and while reconnecting again the device is not at all functioning and moreover all the examples are like that for the first time it is asking for pairing then we need to delete or erase the bond inforamtion for future connectivity could you please try on your side with your iphone you too were facing the same issue like me for reconnectivity

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

Hung Bui — Wed, 27 Apr 2016 13:45:34 GMT

Hi Prabhudurai,

We need to find a way to debug this properly.

As I understand, after the first bond. You disconnect, and then you connect again but the device won't work. Could you explain clearly step by step ?

My suspicion is that bond information was not stored properly, so that when you re-bond the iPhone tried to encrypt the link with the old bond information but the nRF51 reject it. You need to run in debug mode and check if bond information is stored and re-used.

Could you clarify you see the same issue with the stock example in the SDK ? Have you tried to test with nRFToolbox app ?

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

MARTIN FR — Wed, 27 Apr 2016 10:17:47 GMT

could you please tell me how to erase the bonded information after every disconnect event on IOS

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

MARTIN FR — Wed, 27 Apr 2016 08:37:28 GMT

actually when i reconnect it is getting connected but not bonded if i write 0x01 on the immediate alert service nothing happening on the device side where if i delete the erase bond information on the bluetooth side and then its working very well sorry i cannot able to use sniffer trace because i do not have two devices along with me i just have only one NRF51DK

where in the Andoird it getting connected automatically and works very well no need to delete the bond information its due to apple settings or there is somethign wrong in my software

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

Hung Bui — Wed, 27 Apr 2016 08:34:47 GMT

Could you tell me what happens when you reconnect ? Have you check if the number of bonded central exceed the DEVICE_MANAGER_MAX_BONDS number ? A sniffer trace could give more information.

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

MARTIN FR — Wed, 27 Apr 2016 08:22:50 GMT

Thank you so much for your kind reply and i am also managed to do proxmity app work but there is a one real big problem with IOS it is getting connected only for the first time properly and then every time i have to select the erasebond information in the bluetooth settings manually and then i have click connect option in the NRFMCP or NRFTOOLBOX then only it is working could you please tell me how can i do erase bond inforamtion for IOS by using software i do not wnat to erase bond manually could you suggest me some possible methods for doing via software

NOTE;for andorid its working very well

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

Hung Bui — Wed, 27 Apr 2016 08:11:50 GMT

Hi Prabhudurai,

Attached is the screenshots:

After that the LED3 on the nRF51 DK light up.

Please provide us a sniffer trace capturing packets when you are testing. Also please run in debug mode and check if there is any write event.

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

MARTIN FR — Tue, 26 Apr 2016 12:46:48 GMT

YES i have tested ble_prox_app on SDK 9 using IOS its getting connected and then am not able to do anything like immediate alert service in android device am able to see no alert, mild alert, high alert option whereas in the IOS NRF MCP am just seeing 0X __ (some value has to be written) i tried with 0x01 to send the mild alert signal to NRF51DK but nothing happens on the NRF51DK but normally it has to enable the LED 3 right for mild alert could you please share with me some screen shots how you tested the PROX exmaple ON IOS

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

Hung Bui — Tue, 26 Apr 2016 12:36:56 GMT

Hi, What do you mean by "not even connected" ? In the question you mentioned that you managed to bond ? Have you tested with the default example in the SDK ? In our default example we don't have static passkey.

To erase bond, go to bluetooth setting, click on the (i) icon and click Forget this device.

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

MARTIN FR — Tue, 26 Apr 2016 08:42:18 GMT

hello could you please provide some screen shots your IOS testing because for me its not even get connected in the IOS side

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

Hung Bui — Wed, 16 Mar 2016 16:21:04 GMT

Hi Prabhudurai,

I simply write 0x01 to the characteristic with write command. You can delete bond by go to iOS Setting then to Bluetooth setting , then click forget this device.

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

MARTIN FR — Wed, 16 Mar 2016 12:29:44 GMT

Thanks for your reply am using latest IPHONE 6 and in the Andorid(MCP) i am able to see the delete bond information option whereas in the IOS(MCP) am able to see the connect option only could you please tell me where can i find those erase bond information on the IOS and also in the IOS it used to get connect automatically everytime after the first time connection was made without asking static passkey could you give me some more informations how you tested and what values you wrote on the IOS(MCP) it would be really useful if you can share with the screen shots or some pictures please

RE: what hex value to be written on the the MCP (immediate alert service) for IOS

Hung Bui — Wed, 16 Mar 2016 12:23:32 GMT

Hi prabhu,

It worked fine on my side. Could you double check ? Please make sure you erase bond on both sides before testing. A sniffer trace would reveal what could be wrong.