Extra FF character in serial communication

[Matt_McLaughlin]

Hi Manuel,

I have a couple of questions for you to see if we can narrow down when and why this issue is coming up.

You may want to send the commands using the VISA Interactive Control to check if command is called correctly if they are sent directly on an individual basis. Is this a particular command that causes this issue or will it occur with any command? You may want to set up a Loopback Test to test if the commands are being properly sent through the cable. Another troubleshooting idea would be to set the number of bytes to read to -1 and put a relatively large Wait in the portion of the code where the command is read.

These troubleshooting steps will help narrow down whether the error is occurring in the software, the cable, or the device itself.

I hope that helps!

[manmar]

I can't put hex characters in Nivisaic.
If I set the number of bytes to read to -1 the labview aborted  (** glibc detected *** labview: realloc(): invalid next size: 0x0e54ae98 ***).

Is not a particular command, just send 0102 0304 0506 07FF 0809 1011, in hex, and read in the other serial port 0102 0304 0506 07FF FF0809 10 in a Loopback test (an extra FF)

IF I added a delay of 50 ms or more, works fine.

[Matt_McLaughlin]

Hi Manuel,

Do you have an extra cable that you can try? If you haven't already you may want to check using another cable to confirm where this issue is coming from.

Thanks