connection interval setup issue

RE: connection interval setup issue

KoFuKu — Thu, 19 Apr 2018 14:34:34 GMT

Hi TH_HT,

How do you use this code? Are you able to use your code for dynamic change in connection parameters or you are setting connection parameters only once in initialization.

I am looking for solution to change connection parameters when i need a fast data transfer and then back to connection parameters for low power.

EDIT1: Ok. I guess you call this function twice. Once as gap_conn_param_update(1) and second time as gap_conn_param_update(0). I tried this and it works, but i have naw a few bugs.

Can you tell me what is the best time to do connection parameters change.

RE: connection interval setup issue

TH_HT — Fri, 02 Mar 2018 10:21:04 GMT

We expect less than 500ms for reaction time.

So, what is the suggestion min interval?

RE: connection interval setup issue

Turbo J — Fri, 02 Mar 2018 09:58:59 GMT

Counter question: What reaction time (for conn param change) would be acceptable in your application? Just devide this by 6 to 10 and use that as connection interval.

RE: connection interval setup issue

TH_HT — Fri, 02 Mar 2018 09:40:59 GMT

Thanks for your help.

I understand, but if i using the short interval in the first place, the power consumption will be high.

How does the min & max interval work?

RE: connection interval setup issue

Turbo J — Fri, 02 Mar 2018 09:37:10 GMT

If you need a quick change, don't use a long interval like 1 second in the first place. The negotiation will need a few roundtrips using the long interval before it can take effect, see "Peripheral Connection Parameter Update" message chart in the softdevice api documents link.

RE: connection interval setup issue

TH_HT — Fri, 02 Mar 2018 02:39:19 GMT

Yes, setup again after a few seconds, will success.

And another question is, from 1000ms to 7.5 ms connection interval, from setup to setup success, it will be take more than 6s(Please refer the below log). In our project, we need the quick response if we setup the connection interval from 1000ms to 7.5ms.

Please help how to optimize the response delay.

[00279475] <error> app: Updating connection parameters as low power mode..

[00279475可能是电话号码，是否拨号?] <info> app: sd_ble_gap_conn_param_update(): min=0x320, max=0x320.

[00279535] <info> app: on_conn_params_update: params_ok=1..

[00279535] <info> app: on_conn_params_update: evt_type=1..

[00282240] <error> app: Updating connection parameters as fast mode..

[00282240] <info> app: sd_ble_gap_conn_param_update(): min=0x6, max=0x6.

[00289541] <info> app: on_conn_params_update: params_ok=1..

[00289541] <info> app: on_conn_params_update: evt_type=1..

[00301776] <error> app: Updating connection parameters as low power mode..

[00301776] <info> app: sd_ble_gap_conn_param_update(): min=0x320, max=0x320.

[00301830] <info> app: on_conn_params_update: params_ok=1..

[00301830] <info> app: on_conn_params_update: evt_type=1..

[00326941] <error> app: Updating connection parameters as fast mode..

[00326941] <info> app: sd_ble_gap_conn_param_update(): min=0x6, max=0x6.

[00334836] <info> app: on_conn_params_update: params_ok=1..

[00334836] <info> app: on_conn_params_update: evt_type=1..

[00346476] <error> app: Updating connection parameters as low power mode..

[00346476] <info> app: sd_ble_gap_conn_param_update(): min=0x320, max=0x320.

[00346532] <info> app: on_conn_params_update: params_ok=1..

[00346532] <info> app: on_conn_params_update: evt_type=1..

[00349291] <error> app: Updating connection parameters as fast mode..

[00349291] <info> app: sd_ble_gap_conn_param_update(): min=0x6, max=0x6.

[00356540] <info> app: on_conn_params_update: params_ok=1..

[00356540] <info> app: on_conn_params_update: evt_type=1..

[00368827] <error> app: Updating connection parameters as low power mode..

[00368827] <info> app: sd_ble_gap_conn_param_update(): min=0x320, max=0x320.

[00368886] <info> app: on_conn_params_update: params_ok=1..

[00368886] <info> app: on_conn_params_update: evt_type=1..

RE: connection interval setup issue

Turbo J — Sat, 24 Feb 2018 10:27:39 GMT

Infocenter sums error NRF_ERROR_BUSY up nicely: "Procedure already in progress or not allowed at this time [...]" - so your only hope is to start the conn param update again in a few seconds.