The "Association Indication" command always returns the code "0xFF"

I suspect one of the two has changed.

But I’m using the values from the response to the AS command, so the values are definitely valid. Also, I can connect via XCTU using the same commands and values.


Btw, I think I found a solution: use NR before the DJ command in the algorithm I described in the title of the thread. Now the connection is stable.

However, I encountered a new problem: the AS command keeps returning an error (see attached logs).

Logs with timestamps

You wrote here that NR command should be used before, but I do this step. Then I took a closer look and noticed that one AS command did not respond after 10 seconds of waiting (I marked this command in the logs). I observed this event at random times in 4 sessions.
Then I added a pause of 2 seconds after sending the NR command and never encountered this behavior with AS again.

  1. Can you please explain what it was?
  2. How to avoid such a long AS solution without pause? This is an empirical solution and I need a logical solution.
  3. Are there any flaws in my actions?