On Wed, Aug 24, 2016 at 03:24:16PM -0700, Christopher Collins wrote: [...] > As the slave, you can update the connection by calling > ble_gap_update_params() > (http://mynewt.apache.org/develop/network/ble/ble_hs/ble_gap/functions/ble_gap_update_params/) > after the connection is established. Note: the NimBLE host API has > changed quite a bit lately, so if you are using 0.9.0 (instead of the > master branch), the API reference may be inaccurate.
There is something I forgot to mention. There's an outstanding bug which might bite you in this case. If the central device does not support the connection parameter update link-layer procedure, then the call to ble_gap_update_params() will fail. The host should then fall back to using the old L2CAP connection update procedure, but it does not. (this bug is filed: https://issues.apache.org/jira/browse/MYNEWT-347.) If you run into this issue, you can use the L2CAP update procedure by calling the following function: int ble_l2cap_sig_update(uint16_t conn_handle, struct ble_l2cap_sig_update_params *params, ble_l2cap_sig_update_fn *cb, void *cb_arg) Sorry for the annoyance! Chris
