NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

running one VI-File on 2UUT parallel

Hello!

 

I want to run up to ten identical sequences parallel.

Is this possible? It yes, how?

 

All tries to run the sequences parallel failed! Smiley Indifferent

 

 

mfg michi

0 Kudos
Message 1 of 6
(3,559 Views)

Michi,

 

how did you try to run the parallel executions? Die you change the process model to either parallel or batch?

If you are talking about running the VIs concurrently for each socket: Did you set the VI to be reentrant?

 

hope this helps,

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 2 of 6
(3,555 Views)

Hello Norbert,

 

Yes, I changed the progress model to Batch.

 

Exactly. I want to run the VIs concurrently for each socket.

Where is this option to set the VI reetrant?

 

Thanks a lot,

Michi

0 Kudos
Message 3 of 6
(3,521 Views)

Hi Michi,

 

You can set a VI to be re-entrant in LabVIEW: File > VI Properties > Execution > Select re-rentrant radio button.

 

>> Sorry bump this thread, but I have a related question.....

 

I'm running a Batch process model, and running 2 different sequences (sequence is decided based on the TestSocket number) both sequences call the same VI that uses DAQmx VI's to read some analog inputs.

 

When running the Batch sequence, on a certain step, I get a returned value of zero from all of the analog inputs on this VI, which when run in single mode returns genuine voltage results (approx 44.5) The VI is NOT set to run re-entrant.

 

I had assumed, that if both sequences were to call the VI simultaneously, as the VI is not re-entrant, the sequence step to call it second would have to wait until  the first sequence step had completed, and the VI had finished running. It would then run the VI and get results from it.

 

Is this wrong? From the behaviour I've seen, it seems like one of the sequence steps calls the VI, finds it is running & returns zero values for all of the indicators - in this case I would need to use a Lock each time that VI is called?

 

Any ideas?

 

Thanks, 

 

Martin

0 Kudos
Message 4 of 6
(3,510 Views)

Martin,

 

i never saw this happen the way you describe it. At least, i cannot recall anything....

So is it possible for you to break this down into a very simple example and post it?

 

thanks,

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 5 of 6
(3,483 Views)

Hi Norbert, 

 

I tried & couldn't recreate this issue with a basic sequeunce, but with further trial & error on the main sequence. I found that a Lock function on the DAQ accessing VI solved my problem.

 

Thanks,

 

Martin 

0 Kudos
Message 6 of 6
(3,448 Views)