RE: GAP CONNECT MAX INTERVAL PARMTERS ERROR(errCode = 7)

Edvin — Wed, 06 Jun 2018 06:08:04 GMT

Glad it worked out. You must have a conn_sup_timeout > 2 * max_conn_interval. If not, missing even one packet will cause the link to be lost, which is probably why it is a requirement in the BLE specification.

RE: GAP CONNECT MAX INTERVAL PARMTERS ERROR(errCode = 7)

Corey — Tue, 05 Jun 2018 20:44:50 GMT

Hi, Edvin

Thanks for your help, increase the conn_sup_timeout can slove this problem.

RE: GAP CONNECT MAX INTERVAL PARMTERS ERROR(errCode = 7)

Edvin — Tue, 05 Jun 2018 13:54:13 GMT

Hello,

The problem is that the CONN_SUP_TIMEOUT is too short in your connection parameter settings.

If you look in the file ble_gap.h, you will see some constraints from line 711:

* @note If both conn_sup_timeout and max_conn_interval are specified, then the following constraint applies:
* conn_sup_timeout * 4 > (1 + slave_latency) * max_conn_interval
* that corresponds to the following Bluetooth Spec requirement:
* The Supervision_Timeout in milliseconds shall be larger than
* (1 + Conn_Latency) * Conn_Interval_Max * 2, where Conn_Interval_Max is given in milliseconds.

A bit confusing, but we have two constraints here. It seems that your slave_latency = conn_latency = 0.

1st condition: conn_sup_timeout * 4 > max_conn_interval.

2nd condition: conn_sup_timeout > (1 + 0) * max_conn_interval*2 = 2*max_conn_interval.

These constraints might seem a bit contradicting, but I assume (not 100% sure) that slave_latency = 0 counts as "not specified", and hence, the 2nd condition applies. Hence, you can't have a conn_sup_timeout < 2 * max_conn_interval.

So try to increase the conn_sup_timeout (to e.g. 4000 = 4 sec).

Best regards,

Edvin