Missing "Step Result Property" when configure multiple numeric limit database statement

In the NI article "Creating a TestStand Database Schema from Scratch" (http://www.ni.com/white-paper/6484/en/), it mentioned option "Apply To: Step Result Property" for statement "MEAS_NUMERIC_LIMIT". But I could not find "Step Result Property" in TestStand 4.2.1 as shown below:
Is there a workaround for this issue?
Thanks

Step Result is for operating on the step result itself if the required criteria is met, so this can occurs only once per step result. Property Result is evaluated on all subproperties of the step result and is processed if the required criteria is met, so this could occur more than once per step result.
Scott Richardson
National Instruments

Similar Messages

  • Dynamically configure multiple numeric limit test measurements

    I seek to dynamically (programatically) configure a multiple numeric limit test such that I may set / increase / change the number of measurements in the step during execution. For example, I'd like to setup the step for 5 measurements:
    M1, M2, M3, M4, M5 with limits 4<=x<=13.
    I'll set the result data to {1,2,3,4,5}.
    I can successfully set:
    MyMultipleNumLimTestStep.ExpectedNumMeas = 5
    MyMultipleNumLimTestStep.NumericArray (Number of elements to 5)
    MyMultipleNumLimTestStep.DataSourceArray (Number of elements to 5)
    MyMultipleNumLimTestStep.Result.Measurement (Numer of elements to 5)
    Following that, I can access the individual measurement property objects (by offset) and set the Name, Limits.Low, Limits.High, etc...
    During execution, I can view the step variables to see the values getting set correctly.
    BUT, in the report, I only see measurement name, status and the measurement value. NOT the units, limits, comparison type.
    Step
    Status
    Measurement
    Units
    Limits
    Low Limit
    High Limit
    Comparison Type
    AmpMatchTest
    Failed
    Measurement:
    M1
    Failed
    1.000
    M2
    Failed
    2.000
    M3
    Failed
    3.000
    M4
    Passed
    4.000
    M5
    Passed
    5.000
    Take note, prior to execution, I have no entries defined in the Limits tab of the step settings for this step. If I were to define, say, two steps and run again:
    Step
    Status
    Measurement
    Units
    Limits
    Low Limit
    High Limit
    Comparison Type
    AmpMatchTest
    Failed
    Measurement:
    M1
    Failed
    1.000
    dB
    4
    13
    GELE(>= <=)
    M2
    Failed
    2.000
    dB
    4
    13
    GELE(>= <=)
    M3
    Failed
    3.000
    M4
    Passed
    4.000
    M5
    Passed
    5.000
    If I define >5 entries, my code will limit the result to 5. Any ideas?
    Thanks,
    Derek

    Hi jigg.
    I also need to configure a multiple numeric limit test programatically. Unfortunately your solution seems not to work (in Teststand 2013). Also with your code I get limits and comparsion entries in the report only for the first measurement. This is the one already existing in the step configuration.
    Step
    Status
    Measurement
    Units
    Limits
    Low Limit
    High Limit
    Comparison Type
    Dynamic Call
    Passed
    Measurement:
    AllParts
    Passed
    1
    1 = Pass
    1
    EQ(==)
    Another Part
    Passed
    1
    Part 20
    Passed
    1
    Part 2
    Passed
    1
    Part 1
    Passed
    1
    If I add a second measurement in the step, this one is shifted (like expected) and shows the limits and comparsion in the report.
    Step
    Status
    Measurement
    Units
    Limits
    Low Limit
    High Limit
    Comparison Type
    Dynamic Call
    Failed
    Measurement:
    AllParts
    Passed
    1
    1 = Pass
    1
    EQ(==)
    Another Part
    Passed
    1
    Part 20
    Passed
    1
    Part 2
    Passed
    1
    Part 1
    Passed
    1
    Measurement 1
    Failed
    0
    1 = Pass
    1
    EQ(==)
    What is special with the preconfigured measurements, compared to the programatically created test? Any help is very appreciated.
    Thanks
    --rainer

  • 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

  • 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

  • Import/export properties of multiple numeric limit steps

    Hello
    I have a question to the property loader and the import/export tool in TestStand 3.5.
    When I want to export the limits of a sequence with multiple numeric steps with the import/export tool, I press the Limits button to include the limits into the 'selected' field of the properties tab. But for the multiple numeric step the limits are included not for all indices but only once with an question mark instead of an index (Result.Measurement[?].Limits.Low, Result.Measurement[?].Limits.High, Result.Measurement[?].Limits.Comp).
    The property loader step acts the same way. 
    What can I do ?
    Thanks
    Olli

    Hi Olli,
    For the multiple numeric limit test, you will need to individually specify which numeric limits you want to export. Lets suppose you have 3 sets of limits for your multiple numeric limit test. If you wanted to export the first set, you would use the syntax
    Step.Result.Measurement[0].Limits.Low
    Step.Result.Measurement[0].Limits.High
    You will need to do this for each set of limits you have in your array. Simply replace the "?" with the index of the element in the array.
    Hope this helps!
    Best Regards,
    Jonathan N.
    National Instruments

  • NI_LimitMeasurement in multiple numeric limit test results ?

    Hi,
    I'm setting up a database where I will store my teststand results. I've seen that the default "multiple numeric limit test" stores as first result an entry with type_name = "Array of NI_Measurement[0..n]" (n being the number of values returned by this step).
    What's the goal of storing this in the database ? Is it only used to know how many results have been returned by the step ?
    Regards,
    Alex

    Dear SG3,
    I've a written a simple TestStand sequence which executes a single "Multiple Numeric Limit Test" returning 2 random values :
    The results are stored in my database using the default "MySQL Insert (NI)" schema. When I look for what has been written to the database, there are 2 steps results in the "STEP_RESULT" table. The first one is the MainSequence Callback. The second one is my "Multiple Numeric Limit Test" step.
    If I then display the corresponding results of this step that are in the "PROP_RESULT" table, here is what I get :
    There are 3 entries in this table. The first one is named "Measurement" from type "Array of NI_LimitMeasurement[0..1]". The two other entries are my generated random numbers.
    What is the purpose of the first entry ?
    Regards,
    Alex

  • Custom Step From Multiple Numeric Limit Test | Hiding Limit Tab

    Hi All,
    I am trying to create a Custom step from Multiple Numeric Limit Test. The custom step by itself poplulates the Limits value from the measurement. So I am planning on hiding the Limits Tab in the step settings. Can someone guide me on how to do this ?
    Thanks,
    Prasaanthan
    Solved!
    Go to Solution.

    Prasaanthan,
    if you do not need the Edit Substep at all, you can delete it from the substep list.
    Keep in mind that TS gains a lot by using very focused modules. So including a module which does two things (taking measurements, populating limits) might beckfire one day result in "difficult to manage" applications.
    hope this helps,
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • 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?

  • Multiple Numeric Limit Test Names

    How do I get the names of the Measurements of Multiple Numeric Limit from inside the VI that is doing the test.
    I wish to edit them to reflect the measurement that I am making.
    I can find and change the name of the step, but can't see where the name of the measurements are.
    Thanks
    Omar

    Hello Omar.
    Your VI can do this by
    (1) Get the number of array elements contained in "Step.Result.Measurement".
    (2) Get each array elements property "Name".
    The attached VI was saved with LabVIEW 7.1.
    Regards, Guenter
    Attachments:
    HowTo get MeasurementNames (in LabVIEW) of a MultipleNumericLimitStep.zip ‏20 KB

  • 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

  • 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.

  • Custom Looping Multiple Numeric Limit Test SequenceFilePostStepFailure

    Hi
    I am using a custom loop on Multiple Numeric Limit Test. The SequenceFilePostStepFailure callback is called each time the loop fails and called again when the step fails.
    I want to do something (not relevant for this question) when it is looping and something else when the step fails. How do I know the difference? Is there any flag to look for?
    I have tried looking at several variables under RunState but haven’t found the right one. Is there one?
    Thanks in Advance
    Kim

    Kim,
    Try Runstate.Caller.Step.Looptype you can compare this to NoLooping.  If NoLooping then the step doesn't loop.  You can also use Runstate.Caller.Step to get a Step object and then just use the API calls to manipulate it.  You can read about it in the TS help.  To get the loopindex try: Runstate.Caller.Loopindex.
    Both should be ran in the SequenceFilePostStepFailure Callback.
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~

  • Multiple Numeric Limit Hide "Unused" Outputs In Test Report

    Hello,
    I have a question relating to Multiple Numeric Limit Test and output report in ascii txt format:
    Sample Measurement, this is what I see in the txt file:
     Measurement[74] :
                  Limits:
                     Low:             4.75
                     High:            5.25
                     LowExpr:         ''
                     HighExpr:        ''
                  Units:              V
                  Comparison Type:    GELE (>= <=)
                  CompExpr:           ''
                  UseCompExpr:        False
                  Data:               5
                  Status:             Passed
    Is there anyway I can hide or "not include" the unused portion of the output?  In this case I don't need LowExpr, HighExpr, CompExpr and UseCompExpr.  It will make the report cleaner and easier to navigate...essentially this:
     Measurement[74] :
                  Limits:
                     Low:             4.75
                     High:            5.25                                 
                  Units:              V
                  Comparison Type:    GELE (>= <=)
                  Data:               5
                  Status:             Passed
    Regards,
    Mike
    Solved!
    Go to Solution.

    I see the following when I create a new multinumeric limit test:
    Multiple Numeric Limit Test:   Failed
         Measurement:
            Measurement[0] (Measurement 0):
               Limits:
                  Low:             9
                  High:            11
               Comparison Type:    GELE (>= <=)
               Data:               0
               Status:             Failed
            Measurement[1] (Measurement 1):
               Limits:
                  Low:             9
                  High:            11
               Comparison Type:    GELE (>= <=)
               Data:               0
               Status:             Failed
    I think it's supposed to work exactly like you are wanting it to. Perhaps there is some issue with how the step involved was created or modified or converted. Can you reproduce this problem with a newly created and specified step? Also, please specify what version of TestStand you are using.
    -Doug

  • 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

  • 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

Maybe you are looking for

  • How to create a record for table PLAF with order type 'NB'.

    How to create a record for table PLAF with order type 'NB'(standard purchase order). who can tell me the T-code or some usefull information? Thanks.

  • Problems with Vista and nano

    Nano seem to hang up my startup menu. If I unplug the ipod windows boots. When I plug it in after booting it seems OK. Itunes will not allow me to dump music from the ipod to library keeps giving me a not authorized message even though I have gone th

  • Oracle 8i Installation Repair Fails

    I have Oracle 8i installed on my Windows XP Pro laptop. I start the listener service manually. I hadn't used it for a couple of months and tried to start my listener and it failed. So I tried to uninstall/reinstall Oracle (since none of the other Ora

  • The performance of synchronous scenarios?

    Hi gurus, We are planing to implement the integration between SAP and WMS(Warehouse management system) . The customer wants all the scenarios (Purchase Order, goods received,...) to be synchronous. Although it's good from the functional point, I thin

  • BRING BACK DROP SHADOW IN TEXT

    Bring back the option to apply a drop shadow effect to text immediately!