How to Handle Connection Parameter update Error or Busy

[Locky]

Hi all,

I've have written a debug version of our application firmware to catch any and all error seen during operating. The most common one I see is NRF_ERROR_BUSY stemming from my Connection Parameter update. This usually occurs when the device is at the RF boundary where it is frequently Connecting/Disconnecting. Is there any consequence to simply ignoring this Error? I have a 2nd attempt Connection Parameter Update scheduled anyways (NEXT_CONN_PARAMS_UPDATE_DELAY).

I'm just making sure all error conditions are handled elegantly on this final release F/W. Thanks in advanced for the help guys.

P.S. I am currently using S110 7.1.0

-K

[Susheel Nuguru]

Hi Lucky,

If you get NRF_ERROR_BUSY for a Connection Perameter Update procedure, then that means that either previous same call has not yet been finished or there is a disconnect procudure in service. In any case you can safely ignore this ERROR and no cleanup would be needed.

/Aryan

[Carles]

Hi there,

To add to Aryan's response.

What SD are you using and, if you are using s120 or s130, do you have more than one connection active?

Carles