11-30-2006 12:00 PM - edited 11-30-2006 12:00 PM
Message Edited by _Belle on 11-30-2006 12:01 PM
11-30-2006 01:27 PM
11-30-2006 02:58 PM
12-01-2006 08:20 AM
Hi Belle,
This does help and seems like it would work if only my meter would stop presenting me with a E17 Serial comms error: parity or framing. The computer and meter are set exactly the same (9600-N-8-1), so I can't seem to find the exact problem there.
The for loop cleans up the entire process dramatically. Before it was setting the vi attributes before each write, but now it sets the attributes, writes each command, and then reads. I only made one change by adding a wait command inside the for loop to give the meter a chance to perform each action. I attached the capture while running it, perhaps there is an error in there somewhere?
12-01-2006 08:56 AM
After reading the entire operators manual I discovered the source and description of my error.
E17, Transient Error Type: Serial communication error (Baud rate, parity, or data length mismatch between instrument and connected serial device) -
1) Check application software sets correct serial parameters.
2) Check baud rate, parity etc. set correctly.
Does LabVIEW in some way alter baud rate, data bits, parity, stop bits, or flow control? I am in full communication with the meter through MAX; this error only appears when I am trying to control it through LabVIEW.
12-05-2006 07:10 PM - edited 12-05-2006 07:10 PM
Message Edited by _Belle on 12-05-2006 07:10 PM