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

[MARTIN FR]

Hello Everyone,

I have been working around BLE profiles for few months and i have made several tested for each service via MCP(android) everything works fine but now i switched to IOS(MCP) when i connect for the first time it is asking static passkey and then its get connected and bonded when it comes to writing values like for an example am using immediate alert service when i press the write button it is asking me to write the hexadecimal values so i wrote 0*01 for mild alert but nothing happens in the NRF51DK the same functionality if i do in Android it makes the LED ON the Developement board so i request anyone could you suggest me how to test the proxmity service and immediate alert service in the IOS MCP do i have to make some changes in the functionality of the program or please tell me what needs to be done

Thank you prabhu

[Hung Bui]

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.

[MARTIN FR]

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

[Hung Bui]

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.

[MARTIN FR]

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

[MARTIN FR]

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

[Hung Bui]

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 ?