SAME PROGRAM/ALGORITHM BUT DIFFERENT BEHAVIOR

[linlin0904]

New to LabVIEW here, first time posting =D

I developed an automated measurement system [accuracy in ppm] by using GPIB as a communication media with all the instrument.

The algorithm works fine and the data collected are acceptable on my laptop (win10 32bit).

But when I built an executable file and run on a DESKTOP(win xp 32 bit), most of the measurement data collected were totally different. The algorithm is the same but how come there's so big difference on the results? I did use GPIB isolator to prevent ground loop.

Did anyone have idea about this issue?

Thank in advance.

linlin0904

[GerdW]

Hi linlin,

Did anyone have idea about this issue?

You should have an idea of the problem as you have all the information about the setup!

Do you get any errors? (Do you even log them?)

How do you define "totally different measurement data"? What is a "big difference"?

[aputman]

Do you use a lot of local variables?  When used improperly, local variables can create race conditions and produce unexpected results.

[altenbach]

What is the algorithm and how is it implemented?

[RTSLVU]

In my experience when executables run differently than the vi runs in the development environment there is a race condition someplace in the code. 

But without seeing your code we can only guess.

[linlin0904]

I use GPIB to collect the data from measuring instruments.

The "Big difference" I mentioning, is that ALL the setup and the environment for the control system is the same. The only difference between the them is that one of them program was running by win10 32bit(source code), another was running by win xp 32bit (exe file).

[linlin0904]

I used state machine, so there should not have any race condition?

[linlin0904]

And the data collected has big difference.

The instruments I using is nanovoltmeters and fluke ac, dc source

[RavensFan]

You could have replied all of those statements in a single message.  You can even go back and edit your message if not too much time as passed.

You still haven't defined what is a "big difference".  Give an example of what the numbers were before and what they are now.

And a state machine doesn't prevent race conditions.  While it is a common architecture and perhaps helps prevent race conditions, it doesn't mean you don't have any race conditions.

But without providing any code for us to look at, or any examples of good and bad data, I don't know what help you expect to get from the forums.

[AnalogKid2DigitalMan]

My hunch is that maybe this could be an electrical issue- even though you mentioned you used a GPIB isolator perhaps there are still unintended circuit pathways that are affecting your nanovolt scale readings. Laptops typically are floating from earth ground while desktop PC's are not.

EDIT: What is the make and model of your isolator, perhaps attach the manual for it and a sketch of your system wiring.

-AK2DM