Possible race condition during simultaneous connection of two peripherals?

[tinytrex]

I suspect a possible race condition happening during NUS service discoveries. I have two peripherals that are advertising and have DIS, Battery and the NUS service enabled. After the central connects to one of the peripherals I am immediately enabling the scan on the central to connect to the next peripheral. It seems if a new connection is initiated before all the services of the recently connected peripherals are discovered, the central misses discovering all the services of the current device. For example, sometimes I see NUS service was discovered only on the second connection. Its an observation from logs and not a claim. If I introduce a certain delay before initiating the scanning on the central device after the first connection has been established, everything seems to be fine. I am looking for suggestions.

[Joakim Jakobsen]

Hi. 

Maybe you could take a look at this previous thread: 
https://devzone.nordicsemi.com/f/nordic-q-a/52022/how-to-know-when-database-discovery-is-finished

 

It seems if a new connection is initiated before all the services of the recently connected peripherals are discovered

 I think this is the issue, and you need to make sure that all the services is discovered before initiating the new connection. Ref. the thread i linked above. 

Regards, 
Joakim

[tinytrex]

Thanks Jo, The issue is resolved for me.