PM_EVT_CONN_SEC_SUCCEEDED once when first connect but twice After this

[strengthstrong]

I use a bas service and a custom service for the sdk14.2 52832 master. PM_EVT_CONN_SEC_SUCCEEDED happens once after the first connection, but every connection on the second connection and behind it happens twice. I call pm_conn_secure on every service discovery, that is, I call twice, refer to the central hrs example. Cheng wrote, I do not understand is that the call will have a PM_EVT_CONN_SEC_SUCCEEDED event, or. . . Why is the first connection different from the one after it?

[FormerMember]

Do you see the same with the example ble_app_gls as well?

[strengthstrong]

no i dont see gls example , but  i  running  ble_hrs_c   ,this is  

[FormerMember]

Could you compare the way peer_manager is integrated in the your example and ble_app_gls, to see if you can find any difference?

[strengthstrong]

Like I said for ble_app_gls

[FormerMember]

The central example ble_app_rscs_c uses peer_manager, does PM_EVT_CONN_SEC_SUCCEEDED occurs twice there? If not, could you compare how peer_manager is set up in that example with how it is set up in your application?