This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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

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

Parents
  • Hi Prabhudurai,

    Attached is the screenshots:

    image description image description image description image description

    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.

  • 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 ?

Reply
  • 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 ?

Children
No Data
Related