Now I am working on a program with vee. The main function is to conduct several tests,for every test parts will be compared with the specified spec value. I now use the "comparator" and it will return the result of this test part.Because it should be say the sample is passed only after all the test parts return the pass result,but I don‘t know how to realize this.So is here someone can suggest how to realize the function?
Hi Stan，
The comparator have three output pins , "Passed" "Failed" and "Failures". When the result is passed ,the "passed" pin output the "1" and there is no output on "failed" pin,and the "failed" pin output the "0" and there is no output on "passed" pin,so the question is how to collect the results into array,there will be no respons when I use "concatenator" that input pin no value.
The "native" way to combine two data streams like you have into a single one is the JUNCTION object. In your case the output of the JUNCTION will be a one or zero which you can then collect as desired.
Stan
Hi stan,
Similar problems when I want to output data from different thread into one alphanumebric/of course I will clear previous data before new data input.Is there any way to work in VEE？
Again- the JUNCTION object will do what you are asking.
HOWEVER, there is no need to clear the display before adding a new value since the Alphanumeric can only have a single value anyhow. That is, whatever input you send overwrites the last input. The CLEAR input would be more appropriate in the corner case where you intentionally want to show a blank display.
Stan
Have a few minutes, so...
It sounds like your real aim is to be able to perform a series of tests, presumably as chosen by users, then at some point evaluate the tests and see if all have passed. With that in mind, here's a few hints that might help you design your program:
(1) This may be a good fit for the Sequencer. It is a minimal test executive that allows one to execute arbitrary functions and branch based on the results of those functions. The intent is to have your various tests written as UF's and have them controlled by the sequencer. An advantage of this approach is that you'll have a good record of all the test results.
##### OR #####
using the structure with multiple OK buttons that you have been looking at, a flag is probably in order
(2) If at the end all you care about is a global Pass /Fail then set a flag (scoped variable) such as "allPassed" to TRUE in your initialization. After each test AND the flag with the pass/fail for each test. That way any failed test will set allPassed to FALSE. When all tests are done you'll have your pass/fail in this flag
(3) At the end you very well may want to know WHICH tests have failed or passed. If so create a vector flag: "allPassed" as an array. Then start with allPassed = FALSE and set each of the elements to TRUE if that test passes, as in
Then a global pass/fail is simply "product(allPassed)" and if you then want to see which tests have failed you have that info also.
Note that any of these alternatives will work equally well with or without a comparator. Just write your test with some sort of pass/fail result.
<soapbox>
Design your program before coding it! In this case decide what actions are needed, what results you want, which structure you'll be using, etc. THEN start coding.
</soapbox>
Stan
Hi Stan，
You assumption is right.The test I want to perform has four parts.So I start them with multiple OK button.Normally the test will follow the order T1-T2-T3-T4，so I add another “OK” button to put the 4 functions in series.When I am running the combined test,if I found one part have abnormal results I can restart this part only.After I tried your ideas there is no problem with the pass/fail judgment,but still have some problem in output the data/test results to front panel.What I want to do is when combined tests running,after one part finished, the data of this part output to the front panel. If the data is not good I will run the seperated test of this part and update the data into the same alphanumeric.So there will be two data flow into this alphanumeric.I thought to use UO or UF but it seems only alphanumeric on "Main Detail"can "go to the panel".I dont know if it can be realized by "JCT" because it breaks the tree structure ,maybe I will try tomorrow.
Sounds to me like a flag is the way to go. That way there's no propagation issues since each section can independently access the flag. This is pretty much exactly why scoped variables were introduced in the first place. Similarly for the displayed data- use a scoped variable. The thing to watch out for is that since propagation still exists you need to be careful that your scoped variable matches what you think it should be at any given time in your program.
Stan
Hi stan,
Thank you for your advise.
You mention scoped variable for the displayed data, the problem for me now is after I displayed the data in one thread ，how to active the same alphanumeric again in other thread.
Two (of many) possible solutions:
(1) have the display in ALL of the subthreads:
Put the display between your Until Break and the various OK buttons so that the display is refreshed after each subthread is done.
(2) have the display in NONE of the subthreads
For a more sophisticated and controllable approach, put the data display in a UF and call that function whenever/wherever you wish to display your data. That way no sequencing issues. It sounds like you have a very basic need so a UF with an alphanumeric on its panel would probably do what you want. Look at the "battleship" game under examples to get ideas of how to programmatically exercise UF's.
Stan
Howdy. Looks like maybe noone else is ready to give an answer, so...
If you have a bunch of tests that have pass/no pass outputs from comparators, which it sounds like you have, then a very simple answer to decide if all the tests pass is to collect the results into an array (A) and then take the product (product(A). If the product is true then all the tests have passed. Why? well each failed test returns a FALSE and VEE follows the C standard of FALSE is equivalent to 0 (zero). Which means that product is equivalent to a logical AND. Hence if any of the tests fails it has a zero result and the overall product is zero. If all pass the overall product is TRUE. So collect your outputs and feed to an IF/THEN/ELSE with product(A) as the argument and you are done.