Sorry, I missed this reply.
I have fixed the issue by doing ordered commands on the tcp driver. I would imagine the same would work with the string driver (ie waiting for the code to return its feedback before processing new code).
Thanks for the very fast reply!
I have fixed the issue by doing ordered commands on the tcp driver. I would imagine the same would work with the string driver (ie waiting for the code to return its feedback before processing new code).
Thanks for the very fast reply!