Exact sequence of Peer Manager events at time of pairing.

RE: Exact sequence of Peer Manager events at time of pairing.

Petter Myhre — Thu, 27 Apr 2017 14:39:29 GMT

Great! If I answered your question please consider accepting my answer by clicking the grey circle next to it.

RE: Exact sequence of Peer Manager events at time of pairing.

Ankit — Thu, 27 Apr 2017 14:12:28 GMT

I found the solution. it is fds which causes the peer-manager event miss. Now i perform fds_gc() after every peer-manager operation and it all works fine.

RE: Exact sequence of Peer Manager events at time of pairing.

Ankit — Thu, 27 Apr 2017 14:10:08 GMT

Hi,

My application is doing multiple thing at the same time like communication over BLE, data transfer over uart, and few sensor management.

So while pairing process is going on, if i do uart communication at the same time, i am receiving incomplete uart data. And this only happens when my central is busy doing peer-manager-data-update. So it is very important for me to get exact event that state that peer-manager has completed its work. So that i can start other stuff.

RE: Exact sequence of Peer Manager events at time of pairing.

Petter Myhre — Mon, 24 Apr 2017 12:49:09 GMT

What kind of problem? I don't understand. Why do you have to wait until the events are completed? I don't think you can tell Peer Manager not to update anything, I guess it is doing it for a reason. I'm not exactly sure what is updated in your case though?

RE: Exact sequence of Peer Manager events at time of pairing.

Ankit — Mon, 24 Apr 2017 12:12:40 GMT

Thanks Petter for responding.

I am getting these events. But after receiving PM_EVT_CONN_SEC_START event. I start data transfer over BLE causes problem in my communication. So i have to wait untill all peer manager events are completed.

Is there any way to tell peer manager that do not update anything. By doing so i do not want to receive PM_EVT_PEER_DATA_UPDATE_SUCCEEDED events multiple times.

RE: Exact sequence of Peer Manager events at time of pairing.

Petter Myhre — Mon, 24 Apr 2017 11:08:39 GMT

You should get:

PM_EVT_BONDED_PEER_CONNECTED - A connected peer has been identified as one with which we have a bond.
PM_EVT_CONN_SEC_START - A security procedure has started on a link, initiated either locally or remotely.
PM_EVT_CONN_SEC_SUCCEEDED - A link has been encrypted, either as a result of a call to @ref pm_conn_secure or a result of an action by the peer.

PM_EVT_PEER_DATA_UPDATE_SUCCEEDED - A piece of peer data was stored, updated, or cleared in flash storage.