01-26-2006 04:13 AM
01-28-2006 01:49 AM
Not sure if this is related to your problem, but avoid reading the serial port with zero chars in : add a case structure (1, default) around the read operation.
01-30-2006 01:43 AM
Hello CC,
I don´t think, that the zero characters are the problem. I think, it is the problem that the beginning of the read in does not start at a defined value (start bit) but somewhere in the transfer. The question is how to get defined start conditions for the com ports.
01-30-2006 01:59 AM
01-30-2006 02:54 AM
01-30-2006 02:56 AM
01-30-2006 03:01 AM
I used VISA events in two projects and in the beginning I also had such problems.
I'll search my source control for the vis according to this topic and post them as soon as possible. Or at least a picture of it (LV7.0 can't save the vis for LV6i).
Thomas
01-30-2006 03:25 AM
01-30-2006 03:27 AM
@ Thomas
Thank you!
@ Graziano
Yes, that´s the problem! when I first used one while-loop with one com-port the VI worked fine and there were no problems. Then, when I added the second while-loop and the second com-port (realized with a USB-->RS232 converter) the error occured.
I don´t no, if this will happen "This may occur mainly because you are "writing on the cable" at same time from the 2 ends. This causes the bytes to be confused, and you get framing error (it happened to me...)" but how could this checked? The cable is ok.
01-30-2006 07:13 AM