Disconnected peripheral reconnects direct in iOS.

[Martin]

Hi, Got stuck on an issue that has come and gone and then working fine, and are now back again.

I use a nrf51 module with the led-button-service example (sdk 5.2). It's not using bondmgr, just scan for known or recently connected peripherals. I modified the example to have 4 characteristics and to wakeup each 60 seconds to sample ADC values. In the timer event I call start advertise, which is set to 6 seconds. After update-notify two of the characteristics value I disconnect from iOS (stop notifyValue on chars and cancel connection). I am using the iOS connect functions to restore state and connectPeripheral so it get started even i background mode.

Is there anything obvious I am missing?, I can see that the peripheral reconnects direct after I cancelConnection in iOS, and the only clue I got is that it does that for the same amount of time I have set the Advertising inteval to, in this case 6s.

Does the softdevice still advertise for connection attempt after it has passed the connected state? I have tried to stop advertise sd_ble_gap_stop(), but then it will not connect next time.

Thanks in advance!

[Hung Bui]

@Martin:

I'm not sure I understand the issue you are having now. If your device starts advertising after it gets disconnected, and if you try to reconnect in the app (as you mentioned run in background) then it will be connected again after you start advertising.

I suggest you try to record a sniffer trace to see what happens over the air. (Wireshark version 1.10 is recommended)