SET_COMMAND_RESPONSE TIMER_ACK

[majid]

Originally Posted by sblair

There are no requirements on the controller here so it may continue to ask for other PIDs besides the one it has been ACK_TIMER on.

hmm

so the responder need to be a sort of multitasking, continue responding commands and doing previously queued commands,

but I expect controller not to ask previously queued command again before required time elapsed

anyway I implemented queue and problem seems fixed,
there is no annoying "COMMUNICATION WARNING ... " message any more
just a progress bar appears with "SENDING" caption and then dissapears automatically.