02-09-2017 07:49 AM
You don't have a manual and you only got emails with the command and response codes. You do have their software and from the sound of it, their software works.
If it was me, I would use some type of serial port sniffer and see what actual commands/responses are generated (including termination characters) with their "working" software to position the traverse. Otherwise, you and we would be just guessing.
02-09-2017 07:58 AM
Hi Arun,
They don't have a proper manual, or a software; they use a code they wrote in C, which in itself is not at all user-friendly, and very clunky. The response codes were obtained by directly emailing them about the hardware.
Ask them again - that's what I would do!
Can you (or "they") provide the C source code so any programmer could read how "they" send commands and how "they" receive the answer of the hardware? This would help too…
02-10-2017 05:48 AM
UPDATE: I fixed it! Code's working now.
BytesAtPort was the right way to go after all. I had tried a second Read loop earlier which failed, but that was because I forgot to reset it. Anyway, thanks for your suggestions, GerdW. And jamiva, that was a great suggestion; I hadn't thought of that. Although it didn't tell me any more than what I knew about what the communication codes were, I was able to see how the delays worked, so thanks.