LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Anybody experience difference in Labview program execution time on Asian Windows O/S?

I have written a Labview Program that uses GPIB to control an Agilent Spectrum Analyzer and Power Meter. It communicates with and controls the D.U.T. via Telnet. It was debugged here in Massachusetts under Windows 2000. Here the test takes ~ 43 seconds. In Thailand on an equivalent computer running Windows 2000 (Thai) the same test takes ~ 66 seconds. Time is measured by capturing start time and stop time from the O/S. Any clues to account for the difference? The time differential is the same in the development environment and the distribution environment.
0 Kudos
Message 1 of 3
(2,670 Views)
"RMK at Netopia" wrote in message
news:506500000008000000779D0000-1042324653000@exchange.ni.com...
> I have written a Labview Program that uses GPIB to control an Agilent
> Spectrum Analyzer and Power Meter. It communicates with and controls
> the D.U.T. via Telnet. It was debugged here in Massachusetts under
> Windows 2000. Here the test takes ~ 43 seconds. In Thailand on an
> equivalent computer running Windows 2000 (Thai) the same test takes ~
> 66 seconds. Time is measured by capturing start time and stop time
> from the O/S. Any clues to account for the difference? The time
> differential is the same in the development environment and the
> distribution environment.

Suggest you break the test down to its individual steps to see which part o
f
the test is changed. You may even find that it is the test equipment that
is taking longer.
0 Kudos
Message 2 of 3
(2,670 Views)
Test equipment removed from equation - not the problem. Significant time differential still exists. Will have to break into steps and time each.
0 Kudos
Message 3 of 3
(2,670 Views)