This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

CC2541 can't update S120 connection parameters

Hi Guys,

I'm doing a test between CC2541 and Nordic NRF51822. The CC2541 work as a peripheral role. NRF51822 as central role. But CC2541 can update another CC2541 that work as central role.

I didn't see any packet LL_CONNECTION_UPDATE_REQ on sinffer's capture message. Does this problem is a known problem? And any body have a solution?

Thanks!

Parents
  • I am sorry that I don't really get what you meant in "The BLE S120 will not send the packet when doing scan. And I saw the packet was sent after 50ms that I set as default connection interval. After I set the connection parameters when establish the connection and not scan when send data."

    How the connection parameter is set in BLE is that, the central set the connection parameter (interval, timeout, slave latency) when it sends the connect request (when the connection is established). If there is no change, this connection parameter will be used all the time. The central and only the central can change this connection parameter by sending the LL_CONNECTION_UPDATE_REQ.

Reply
  • I am sorry that I don't really get what you meant in "The BLE S120 will not send the packet when doing scan. And I saw the packet was sent after 50ms that I set as default connection interval. After I set the connection parameters when establish the connection and not scan when send data."

    How the connection parameter is set in BLE is that, the central set the connection parameter (interval, timeout, slave latency) when it sends the connect request (when the connection is established). If there is no change, this connection parameter will be used all the time. The central and only the central can change this connection parameter by sending the LL_CONNECTION_UPDATE_REQ.

Children
No Data
Related