If I have to pass data between different steps ( only labview vis) within same Main sequence, is it right using LabVIEW globals, rather than TestStand globals?
in one step, I will be writing data to the Global.
In a later step, I will be reading the global to access that data.
Example sequence:
I am more comfortable with using Labview globals than Teststand variables. Labview is the only adapter in my sequence.
Hi all
I have slightly modified the SequentialModel.seq file so I can loop on Preuutloop Callback & have skipped "Handle Termination"
although in a rare instance it gave me this error
highlighted in png file
You only need to write the cluster of references once in your action engine. Then all you have to do is read it. So you have to make two "actions" (cases) write and read (use an enum) and store the date in a shift register.
I believe i found a solution.
cs_s.png / ts_s.png
If it is just within one sequence, then I would use the TestStand variables. The reason is because you are limiting your possible reuse of those VIs by using the global. If you pass in the value, you have a better chance of being able to reuse the VI.
Hello All,
Working in TestStand 2013, and came across a situation with DMM measurements, in which several values would be acceptable for the limit comparison. For example, if I am making a resistance measurement, and I expect it to be a very high value, say greater than 1M, I would insert that as the lower limit. However, there are also certain situations when I may see the result of "NaN" at the meter. For the purposes of the test, any number greater that 1M would be acceptable, but a result of NaN would also be acceptable. In an effort to keep the code modular and reusable for many instances, I am curious if there is a way in TestStand to compare the test result against two values at the same time, (i.e. >1M OR =NaN). Please advise. Thanks.
GSinMN
In some perspective, yes, it would limit the reusability.
But in a case, where this global has to be used in a " write once -read many time" way, I feel that it is easier with Labview global. If we use TestStand variable, every time this vi is called in a step, we have to connect the variable to the vi input terminal (which I find a little time consuming, to open the variable browser and selec the variable).
Also I want to know if there is any peformance/efficiency difference in the execution.
My solution was to store the thread reference. At any step, I can retrieve the current context. This is only valid within a thread, but meets my needs. I could also pass something at a higher level, but that would require knowing which thread I am interested in anyways.
The in or out tag from a LV VI gets added to the parameter name
any method to remve it
%5B = [
[In]
[Out]
InspectorGadget
Do you want to share with the rest of us what you did to resolve this, so others in similar situation could have a look?
Also, what problems do you have running asynchronous VIs in TestStand?
Well the primary problem was that the CUEUE was not shared between 2 vi's in runtime, when I put them in a project they then share the same memory I guess.
Question still remains, when starting a sequence asynchr why does the sequence waits at the end of the sequence while the asynchr VI is running.
put this as your low limit:
Step.Result.Numeric == NAN ? NAN : 1000000
Hope this helps,
hi
In case of a step failure (pass /fail for eg) I would like to give number & then mention the number in a text file where the reason & soln will be specified (similar to labview)
I know the eg for numeric test where it shows the limits & its clear to the operator the Value is out of limits but in case of a pass /fail its different
pass/fail can have multiple boolean Inputs with [AND] [OR] logic. & therefore its essential to specify the cause.
is there a tried tested method to acheive this or I have to make my custom step for the same...
had it been so comfortable if Teststand had also a Failed status Line (Failcode, status, source) on the lines of "error" ist easy to keep track of events & docementing also
Excellent. Never used the "Conditional" operator before. Now I know how. Thanks.
GSinMN
Hi Myriam,
Problem solved. This system was built out of network control, so IT had to make some changes to users login. I don't have all the details, but is working now. Thanks for your help,
tstand
After some testing and strange behavior, I have corrected what I previously submitted. I added a function to get the file size, in bytes, so that I could tell the read command how much data to read. The strange behavior is that, after the read, my script data, most of the time, contained some extra garbage at the end of the script data. This would happen more often than not. The cause could be that I have not set something up correctly in TestStand. I always welcome someone educating me and pointing out my mistakes. My solution was to add a post-expression to the read command which would only accept the left most "number of bytes equal to the file size" thus truncating the garbage at the end.
You cannot create a variable of a step type. Step types can only be used to create steps.
What is your goal? Maybe there is a better way to accomplish what you want.
If you are looking to dynamically change the limit set you need to use other types like NI_LimitMeasurmeent or an array of those.
Regards,
Thanks for the info..
hi,
its fine now
I just used a container for the Current_Element .
I kinda jumbled up , hence thought as the array is of type MeasurementTest
I shld be using the same type for the variable which is going to hold the element
regards,
akshay
