nRF Connect Desktop - Always a long delay after connection before reading Device Name from GAP

[Dave_couling]

I've noticed when using the nRF Connect Software, after I connect to a perihperal, it immediately discovers services, but takes about 4 seconds to read the GAP Device name.  My connection parameters are quite fast,  10msec,  MTU244.  Curious as to why the delay.  I notice that the Software hangs and prevent me from writing/reading to a service until this GAP device name has been read.  This is not an issue using mobile Apps, but is a little annoying as I use nRF Connect alot for peripheral testing.  Anyone else see this issue?

DC

[Kenneth]

Are you by any chance enabling connection parameter update with slave latency enabled? Slave latency will delay discovery and reading characteristics.

Best regards,
Kenneth

[Dave_couling]

Yes, I have Slave Latency set.  To speed up discovery should I delay Parameter updates to ~1sec to allow for discovery to complete before PPCP handshaking to take over

[Kenneth]

Yes, that would be a good idea.