master initiated Connection Parameter Change

RE: master initiated Connection Parameter Change

Petter Myhre — Thu, 24 Aug 2017 14:05:52 GMT

The issue in the thread I linked to is that the central doesn't respond to the CPU Request from the peripheral, and because of this the peripheral disconnects after 65 seconds. There is still communication during those 65 seconds. Would it be possible for you to do a sniffer trace of the connection so we can see what is happening on air?

RE: master initiated Connection Parameter Change

Ken — Thu, 24 Aug 2017 13:10:41 GMT

I did review that ticket. That is not our problem. Data is actively being sent between devices right up until the disconnect. I removed the comm_param library from the code and the system runs as expected. Downside is that the peripheral can no longer request connection parameter updates.

It would be nice to understand why the connection is dropping after the 65 seconds when the master sets new connection parameters

RE: master initiated Connection Parameter Change

Petter Myhre — Thu, 24 Aug 2017 09:06:37 GMT

Ok :) Did you have a look at the thread I linked to?

RE: master initiated Connection Parameter Change

Ken — Wed, 23 Aug 2017 20:29:52 GMT

Had an error in the post. We are running nRF52832 with S132.

Initial post updated

RE: master initiated Connection Parameter Change

Petter Myhre — Wed, 23 Aug 2017 12:08:00 GMT

You shouldn't use S132 with the nRF51xxx, you should use S130. The S132 is for the nRF52832. Which version of the SoftDevice and SDK are you using? You issue sounds very familiar to this.