@GerdW wrote:
Hi spalinowy,
@spalinowy wrote:
In my case, the reason was the lack of time for a response from the device. I added the appropriate waiting length and the problem was over.
The "lack of time" most often is not the reason, but the bad/missing implement of the communication protocol!
This excellent video explains how to solve serial communication correctly…
I agree. 99.9% of the time if you need to put a hardcoded wait in your communications to make it work, it indicates an incomplete understanding of the communications protocol.
Bill

(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the
CLAD Nugget.