Mask & Limit Testing Express vi

Hello,
i have a problem with the Mask & Limit Testing vi. I want to connect the upper and lower limits at the terminals outside the vi. The limits are signals like this:
0            10
200        30
30000    200
The first column is the time in ms the second for example the length in mm.
How must i connect this limit data?
greetings Schwede

Are you trying to test the data to one limit, then to the second, then to the third?  Or are you trying to build two waveforms and then test to them?
The first is solved by setting up the limits as constants in the Express VI and then wiring in the constants.
The second is much more difficult as the waveforms need to match in dt and array length.  I think that can be accomplished easier than Jeff is doing it, but I would like a better idea before I spend the time to come up with an example.
So, several steps with constant levels or a single step with a complex level mask?
Thanks,
Bob Young
Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
DISTek Integration, Inc. - NI Alliance Member
mailto:[email protected]
Attachments:
mask_and_limit.vi ‏67 KB

Similar Messages

  • Problem to define limits in Mask & Limit Testing vi

    With Labview 8.0 I can not longer define limit mask by draging points on Define Signal mask screen.
    I used Mask & Limit Testing express vi before with Labview 7.1 and was able move points with cross mouse cursor to define limits envelope around tested signal.
    With new labview this feature is disabled and I have to manualy enter X,Y cordinates for each point.

    I have reported this issue to R&D for further investigation, we hope to see it resolved in a future revision of LabVIEW.  Sorry for the inconvenience.
    (ID # 3V09NT1W)
    Since I'll likely be the person fixing this, I went ahead and investigated this and found the cause of the problem, so I can provide a better workaround too.
    One of the VIs used in this dialog has a very easy-to-make mistake in it.  It's a little embarassing, though at least I can say I didn't write the original VI in this case. 
    If you open the following VI:
    vi.lib\express\express shared\ex_TableUpdateTable.vi
    The "graph relative coords orig" refnum going into the top two property nodes is wired incorrectly.  Visibly it's impossible to tell this until you click once on the wire between the two property nodes.  Notice that it is coming from the input to the first node, not the output of the first node.  Delete this wire and re-wire it from the output of the first one.  This will force the write to happen after the read.
    Interestingly, the VI did not change at all between 7.1 and 8.0, this race condition just got compiled / clumped differently which caused the write to happen before the read in 8.0.
    Message Edited by Jeff B on 03-01-2006 11:11 AM

  • Mask and Limit Testing Express VI

    Hello.
    Im a bit new at looking at limit testing signals. Im using the Mask and Limit Testing Express VI to mask a signal I acquired previously. See attached VI.
    My problem is that we would like to load the limit mask at run time using a file of some sort.
    At the moment I am un-able to get any sort of mask loaded using the limit inputs to the Mask and Limit Testing Express VI. Does anybody know how I might do this?
    Thanks in advance
    Chuck
    Attachments:
    Limit Test (SubVI) example.vi ‏724 KB
    Limit Type.ctl ‏5 KB

    Hi and thanks for getting back so soon
    True the upper and lower inputs are not connected because I wanted to show a working (all be it without an external mask) VI
    the problem is I can't get the upper and lower inputs working in any form If I connect the inputs.  So I guess my question should be,
    How do I wire the upper and lower inputs to produce a working mask with the data supplied?
    Then how do I use a file to provide the mask data.
    Sorry for my lack of clarity and I hope this helps.
    Chuck

  • Cannot call "mask and limit testing" inside a loop

    Calling "mask and limit testing" in a loop doesn't work. The problem
    is that the Upper Limit and Lower Limit are initialized only the first
    time the VI is called. All waveforms are tested against the same
    limits even if different limits are passed at each iteration. Is there
    a way to use this VI in a loop?
    Thanks!
    Martin
    Attachments:
    test_limits_testing.vi ‏193 KB

    Dear Martin,
    Thank you for contacting National Instruments. I would like to apologize for the delay in responding to your support request.
    From the information you have provided, it sounds like you are running your VI and experiences issues with the lower and upper mask refreshing after subsequent iterations of the FOR loop.
    The �Mask and Limit Testing� Express VI is not intended to function inside a loop; however, you can fortunately modify this Express VI to perform the desired action. To do so, please follow these instructions:
    1) Open the Block Diagram for your �test_limits_testing.vi� file
    2) [Right Click] on the �Mask and Limits Testing.vi� Express VI
    a. Select [Open Front Panel]
    b. When prompted to convert to a standart subVI, choose [Convert]
    3)
    [Right Click] on the �subMaskLimitTesting.vi� Express VI
    a. Select [Open Front Panel]
    4) From the toolbar, select [Window] >> [Show Block Diagram]
    5) You should see two subVI�s named �MatchDT� (white icons with black text)
    a. Wire a [True] Constant to the �Reset 2� input terminal for each of the �MatchDT� subVI�s
    i. To do this, right click each input terminal and select [Create]>>[Constant]
    ii. Make sure the constant value is set to [T] for �true�
    6) Save and Close the subVI�s
    7) Re-run your �test_limits_testing.vi� file, and the masking limits should re-initialize upon each loop iteration
    You have successfully customized the VI to function within a loop.
    I hope this helps! Please don�t hesitate to let me know if there�s anything else I can help with or clarify. Have a great day!
    Kind Regards,
    Joe Des Rosier
    National Instruments

  • Mask and limit testing

    Hello, 
    When i am trying to use the Mask and Limit testing I am getting " Unable to View Properties"  could you please tell me what will be issue on this.
    Thanks
    KJD
    Attachments:
    Mask and limit testing.png ‏56 KB
    Mask and limit testing.png ‏56 KB

    I would say off hand that the express VI is corrupted.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Multiple Numeric Limit Test - Evaluate Post and Status Expression

    We have a Multiple Numeric Limit Test where the limits for one of the measurements is a function of one of the other measurements.
    In the Post-Expression there are two expressions that set the low and high limit based on one of the readings.
    But the comparison does not seem to be using the calculated limits.
    The report file shows the correct calculated Low and High Limits, and shows the measured reading as being in between the Low and High limit, but fails that measurement. I feel the Status Expression is using the default limits that are out of range.
    The post expression looks like this
    Step.Result.Measurement[2].Limits.Low=Step.NumericArray[1]*1.9,
    Step.Result.Measurement[2].Limits.High=Step.NumericArray[1]*2.1
    In Table 3-4 "Order of Action that a Step Performs", Evaluate Post-Expression (Action #15) is before Evaluate Status Expression (Action #16), but it seems that is not the case.
    Or am I changing the wrong Low and High Limits. Am I just changing the Limits used in the report file and not the limits used for comparison?
    Again the correct low and high limits are in the report but not used for comparison. 
    Thanks

    Digging into the NI step type for Multiple Numeric Limit Test, I find that the comparison is done at Post-Step substep which is before my Post Expression is evaluated to set the correct limits.
    So I have added code to my VI module to set the limits after taking the measurements but before returning to TestStand.

  • Execution order of Multiple Numeric Limit Test?

    What is the execution order of "Multiple Numeric Limit Test" in TestStand 2010?
    I am using a custom steptype of Multiple Numeric Limit Test. I want to manipulate the input parameter. How can I do that. I am not interested in making a new steptype. I am writing in Post-Expressions and the data is manipulated as they should but it is not evaluated. I is evaluated before the Post-Expressions executes.
    For example I am writing: Step.NumericArray[0]= Step.NumericArray[0]*1000/(2.5-Step.NumericArray[0])
    The execution order when looking at the TS manual at page 3-13 is Evaluate Post-Expression before Evaluate Status expression. But it is not what I see. I have also tryed using the more simple Numeric Limit Test and it works as I expect it to according the manual.
    Anyone knows about any workaround for that?

    Hi Ray
    Thanks for your reply
    I have tried writing what you are suggesting: Step.Result.Measurement[0].Data= Step.Result.Measurement[0].Data*1000/(2.5-Step.Result.Measurement[0].Data)
    Still it evaluates the step before the post-Expression. When I am looking at the variables at runtime the Step.Result.Measurement[0].Data is having the correct value but it seems to evaluate the step before the Post-Expressions.
    Any other suggestions?

  • Overriding Result Status of a (Multiple) Numeric Limit Test

    I want to be able to change the pass/fail status of a numeric limit test from a CVI DLL, whilst still displaying the numeric results in the report. I have tried ResultStatus, StatusExpression and many others but they all seem to do nothing or get replaced by the result of the numeric limit evaluation. Is there a method of supressing the numeric limit evaluation or prefferably performing the individual comparisons but overriding the overall result.
    TIA,
    Dave

    You would have to do the overriding in TestStand. On your Test Step, open the Properties page and go to the Expressions tab. At the bottom you will see the Status Expression box. This is where the limits are compared to the measured value to determine pass/fail. You could modify the code here to have Step.Result.Status be either "passed" or "failed". The actual numeric value measured would not be changed.
    - tbob
    Inventor of the WORM Global

  • Notice -- Fix for Multiple Numeric Limit Test Status in TestStand 2.0.1

    Dear TestStand Customer:
    National Instruments is committed to product quality and customer
    satisfaction. As part of our commitment, we want to ensure your success
    with our products by delivering industry-leading support and immediate
    information regarding issues potentially affecting you. We discovered an
    issue in TestStand 2.0.1 that may affect the integrity of some test
    results. This issue affects TestStand users meeting both of the following
    criteria:
    1. You are using sequence files with instances of the multiple numeric
    limit test that were saved in TestStand 2. 0.
    2. You have recently upgraded these sequence files from TestStand 2.0 to
    TestStand 2.0.1.
    For the complete problem overv
    iew, please visit
    http://digital.ni.com/express.nsf/express?openagent&code=exjaxg
    In order to immediately remedy this problem on current TestStand 2.0.1
    installations, download the corrective patch at
    http://digital.ni.com/express.nsf/express?openagent&code=exjaxg To prevent
    this issue from occurring in future installations of TestStand 2.0.1
    development and deployment systems, we are creating a new TestStand CD,
    version 2.0.1f1, which we plan to send to all existing TestStand 2.0.1 and
    Developer Suite Test Edition customers with TestStand 2.0.1 during the next
    two to three weeks. If you have a TestStand 2.0.1 CD, please replace it with
    the new TestStand 2.0.1f1 CD.
    Thank you for your patience and understanding in this matter. We remain
    committed to your success and will continue to inform you of any issues
    potentially affecting you in the future. If you have any questions, please
    call me at (512) 683-5880 or email me at mailto:[email protected]
    Best re
    gards,
    Richard McDonell
    TestStand Product Manager
    National Instruments
    (512) 683-5880 Office
    (512) 683-5569 Fax
    mailto:[email protected]

    This issue has been resolved in TestStand 3.0. For more information on TestStand 3.0, please visit ni.com/info and enter "teststand3".
    Regards,
    Richard McDonell
    NI TestStand Product Manager
    National Instruments

  • Property Loader and Multiple Numeric Limit Test

    Hi!
    I'm trying to export the limits of all numeric limit tests im my sequence.
    I've no idea what i'm doing wrong, but i fail with exporting the limits of the multiple numeric limit tests. There are only the limits of the "normal" numeric limit tests in my export.
    Could someone please explain me how to export also the limits of the multiple numeric limit test?
    (TS 2013)

    when defining what to export, it is usually easiest/cleanest if you can explicitly define all multiple numeric step measurements as explicit indixes? For example if your MNL step has 2 measurements defined, you'd want to export 4 additional matches...
    Step.Result.Measurement[0].Limits.Low
    Step.Result.Measurement[0].Limits.High
    Step.Result.Measurement[1].Limits.Low
    Step.Result.Measurement[1].Limits.High
    ...and so on for more indexes....
    note how the pattern is different from the regular
    Step.Limits.*
    by default when you try to export using the '>' buttons for MNL steps, TestStand will usually try to help by generating an incomplete/invalid expression of:
    Step.Result.Measurement[?].Limits
    which it expects you as the user to fix before proceeding, however the '?' is often overlooked, because it's so small!
    some people prefer to simply export the entire Step.Result.Measurement.* to the file because they'd prefer not to define array indexes, but this will log the explicit XML for the container values, which may not be as easy for end users to work with... your mileage may vary. Good luck!
    -Elaine

  • Multiple numeric limit test

    Hi,
    I have a mutiple numeric limit test. I want to modify the measurement set in the test based on my needs. How to access the measurement set property of the test.
    when I do the export of the property using the property loader utility, the data is in avery difficult format to read.
    Can you suggesst some alternative?
    Regards
    Gopal

    Hi Gopal,
    Besides using the Property loader step, you could use an expression to access the measurement set. To do this, right-click on the step and go to Properties>>Expressions, and the measurements are under Step>>Result>>Measurement. I hope this helps. Let me know if you have any questions.
    Regards,
    Ebele O.
    National Instruments

  • Display all measurements in Multiple Numeric Limit Test using UI SeuqenceView Control

    Hi, I found only the total result in Multiple Numeric Limit test can be show in UI SequenceView Control. How can I display more detail information in it?
    For example, If I want to display like this:
    Mulitple Numeric Limit test                       FAIL
    Measurement1                                        PASS
    Measuremtnt2                                         FAIL
    Is it possible in UI sequenceview control?
    Thanks in advance

    You might be interested in this community example: Recursive Expression in TestStand.
    It is possible (though not traightforward) to loop in an expression using recursion.  The example above shows how to use recursion in an expression to list all of the limits of a multiple numeric limit step.  This is similar to what you want to do with measurements.
    I honestly think you're better off with Doug's suggestion to hard-code a maximum number of measurements to display as using recursion in expressions is not easy.
    Josh W.
    Certified TestStand Architect
    Formerly blue

  • Multiple Numeric Limit Test - Accessing only the failed tests

    I would to access only the failed tests in a multiple numeric limit test.  The specific information I want to access is the measurement value, low limit, high limit, and comparator type.  I need to access these pieces of information during runtime from a Message Popup, therefore i have to use the Message Expression field in the "Text and Buttons" tab of the Message Popup step to access this information.
    [DL]

    Hi,
    PostStepFailureCallback is the one you want to start with. The only difference is where you get the data from the Step.Results.
    For the Limits etc you will need to look in the Measurement property. Also, beware that you are dealing with an array of data.
    Regards
    Ray Farmer

  • Is there any differnce between the Numeric Limit Test source code from TestStand 3.0 to TestStand 3.1? How to get the source code for the Numric Limit Test for both the versions?

    I need to know the differnece between the Numeric Limit Test between the TestStand version 3.0 to 3.1. If there is any differnec in the source code how to find it out? If somebody has the code can you share it?
    Thanks,
    Jeyan

    Hi,
    I don't believe there are any differences between the two versions. But you can check the source code for the Numeric Limit Test in TestStand\Components\NI\StepTypes\CommonSubsteps. But the main part of the step is the Code Module and this bit the users supplies this.
    What has prompted this question?
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • The "Edit Numeric Limit Test" help page is wrong

    The last four limit types incorrectly say "and" where they should say "or" in the limit comparison.  The software gives the correct information in the status line just below the limit type editing screen, only the help file is incorrect.

    David@Work -
    Thanks a ton for reporting this!  I went ahead and documented this for fix in a future version of the software, and I also documented that the Multiple Numeric Limit Test documentation is incorrect, as well.
    For your reference, this was reported to R&D #118475 for further investigation and fixing. 
    Thanks again for your feedback!
    Derrick S.
    Product Manager
    NI DIAdem
    National Instruments

Maybe you are looking for