08-13-2014 12:41 PM
Yes... ALL the hardware is the same, I just have one USB cable that I plug into which ever computer is running the test.
The only variable is which computer is running the executable
08-13-2014 12:59 PM
Not sure why you are setting VISA buffer sizes, but according to the Help,
Set size slightly higher than the amount of data you expect to transmit or receive
08-13-2014 01:14 PM
The buffer size is specific to the instrument under test and how it does the file storage
08-13-2014 01:25 PM
@MikeMack747 wrote:
The buffer size is specific to the instrument under test and how it does the file storage
Yes, but this setting is for VISA on the PC.
08-13-2014 01:30 PM
It works fine on one PC but not the other. I'm wondering if it is a driver issue now
08-13-2014 01:44 PM
@MikeMack747 wrote:
It works fine on one PC but not the other. I'm wondering if it is a driver issue now
A driver issue?
You claimed that the hardware is identical except for the UBS-serial cable.
08-13-2014 01:51 PM
The hardware on the tester, the USB hub, the calibrated barometer, the CP2103 USB to RS232 converter, the IORelay card, and the unit under test are all identical. The difference is the computer running the executable. They are 2 different PC's.
08-13-2014 01:58 PM
The Status of the I/O Trace will tell you if any errors or warnings occurred during communication. Looking briefly at the file you attached, I see some timeout errors.
If the comptuers can be connected to the same network, you may also want to consider remote debugging of the executable to gain some insight on where the code is failing on the 64-bit computer. You can use the debugging tools on the development machine to monitor the executable on the target machine:
Remotely Debugging Executables in LabVIEW
08-13-2014 02:16 PM
That looks like the tool I need!
I will report back ASAP
08-13-2014 03:29 PM
The remote operation seems to cause quite a delay in the communications. Enough so that the instrument under test times out