This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

GAP Central Connection Establishment and Termination timeout

I would like to configure the connection timeout with the S130v1. This timeout is described in the following sequence diagram: infocenter.nordicsemi.com/.../group___b_l_e___g_a_p___c_e_n_t_r_a_l___c_o_n_n___m_s_c.html

Is this possible to configure it or do I have to add a software timer and cancel the pending request manually ?

If the central software is multi-link can the S130v1 manage multiple pending connection requests ? And is it possible to cancel only one pending connection request ?

Thanks for the help.

Parents
  • The connection timeout is one of the parameters to the connection function which starts that diagram, so you just set it.

  • Yes I knew what parameter you were looking for, but I thought just telling you it was there would let you find it fast enough :)

    I don't know the answer to the other question. Seems like you can't, why don't you try it, just ask it to connect to a device which isn't there, pick a random address of some sort and give it a long, long timeout, then try to connect to another one and see what happens. It's quite possible the stack will deal with multiple connections at one time, but is only able to be in the process of making one new connection at once.

    There is a parameter to the sd_ble_enable() which isn't very well explained, central_sec_count, which is the number of concurrent pairing procedures available, never quite figured out what that meant, wondered if bumping that up makes multiple concurrent pending connections work. Probalby not.

Reply
  • Yes I knew what parameter you were looking for, but I thought just telling you it was there would let you find it fast enough :)

    I don't know the answer to the other question. Seems like you can't, why don't you try it, just ask it to connect to a device which isn't there, pick a random address of some sort and give it a long, long timeout, then try to connect to another one and see what happens. It's quite possible the stack will deal with multiple connections at one time, but is only able to be in the process of making one new connection at once.

    There is a parameter to the sd_ble_enable() which isn't very well explained, central_sec_count, which is the number of concurrent pairing procedures available, never quite figured out what that meant, wondered if bumping that up makes multiple concurrent pending connections work. Probalby not.

Children
No Data
Related