pass Labview results to Teststand while runtime

[nishkpani]

Hi all, 

I am using LabView to sweep across frequency for some tests. I am trying to call a Teststand sequence in the LabView for checking teh limit of each value calculated. I need to integrate this Sequence call within the LabView. I am not sure how to do this. Kindly let me know if you have any ideas. 

Nish

[~jiggawax~]

It seems that you are using the applications incorrectly.  Generally TestStand is the top layer and it calls your LabVIEW VIs.

The layers would look like this:

TestStand->LabVIEW->Instrument Driver->Instrument

There is a great document titled Using LabVIEW with TestStand here: http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0CCYQFjABahUKEwjd29aJvfTIAhXDoogK...

I recommend reading that.  Especially Chapter 1.

Regards,

[nishkpani]

I think I did not do a good job explaining my problem. I have a Labview code, to which i can do limited edits. I need to review the results calculated by the code as they are being generated ( during runtime). The results need to be checked for limits and if failed need to take some error action else go to the next section of the VI. For this reason I was thinking if there was a possibility to call a sequence in teststand and updating the values asynchronously. 

[Dennis_Knutson]

That seems backwards to me as well. I would have the VI just do a measurement and TestStand evaluate the result. Then call a separate VI(s) based on that.

[~jiggawax~]

Is the VI/LabVIEW Code originally called from TestStand?  Or is it an executable that you want to call a TestStand sequence from?

I am one of the biggest advocates you will find for TestStand and so it pains me to say this, but if you are doing what I think you are doing then you are better off not using TestStand and just doing the evaluation in LabVIEW.

However, if you are doing it correctly then you will break your code up into smaller modules and use TestStand to sequence through the modules and do the analysis along the way.  I would also be as bold to say that looping, in this case, should be done in TestStand as well.

[Mathis_B]

Hi Nish,

It sounds to me that you are having a problem similar to one I encountered some time ago. In my case I had a custom user interface which was a built executable while TestStand was using code modules in devlopment mode. The effect is that you have two instantiations of LabVIEW (run-time vs development mode) which don't share the same memory management. Thus references like queue references, DVRs, etc were not valid in the other instantiation and didn't work. For my specific application it was necessary to get that to work which I did by creating a TCP/IP server/message broker which was launched in the instance where all references were created/valid. The other instance would use these references by sending TCP/IP messages to this message broker which would forward it to the correct queues, etc. It would then wait for a reply, which at the least would be the error state of the module you were interfacing with.

Best Regards

Mathis