https://devzone.nordicsemi.com/f/nordic-q-a/6666/about-the-obstacle-which-is-at-the-time-of-gzll-communicationHi, I suffer from the phenomenon which can&#39;t sometimes maintain communication between the 32.8ms at Gazell communication at present. When not writing in SoftDevice, this phenomenon doesn&#39;t occur. The condition that I confirmed the upper problem anden-USTelligent Community 13Fri, 17 Jul 2015 08:41:35 GMThttps://devzone.nordicsemi.com/thread/23385?ContentTypeID=1Fri, 17 Jul 2015 08:41:35 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6feb666e-0681-4e52-a6b1-eabb1b260b01Susheel Nuguru<p>I am not sure if this is possible, but the expert in this is in vacation and we have kept this case open quite long. I have to close this is no response. Open a new one if you need.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/23384?ContentTypeID=1Thu, 30 Apr 2015 05:06:01 GMT137ad170-7792-4731-bb38-c0d22fbe4515:916ecfc3-a2e4-402e-9ae7-61f4e8a66c00Smura<p>I&#39;d like to communicate using Gazell. The parameter was changed because I&#39;d like to send and receive with speed as early as possible. It could be sent and received now by the early speed by changing the parameter. But SoftDevice has been just written in, the problem that the one which could be sent and received can&#39;t communicate during 32.8ms by some reasons generated data periodically.</p> <p>I&#39;d like to settle this problem. Is that possible? Or is it impossible?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/23383?ContentTypeID=1Fri, 24 Apr 2015 12:55:03 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bd142cb4-9cdd-4a3c-83df-1825292f23e6Susheel Nuguru<p>can you please explain clearer, I am unable to understand your description.</p><div style="clear:both;"></div>