In While step type

how can i specify the condition in 'While' step value...?
say i maintain a counter variable in workflow container and i increment each time in 'container operation' step type.....
how shud i specify the value in comparison basis and comparison values in 'While' step type...?!?!
i got it in 'loop until ' step type with same case....

Hi Divya,
If i understood your question correctly, you are interested to know how to define your condition for 'While' / 'Loop Until' Step.
When we create a 'Loop Until' step, when you double click on 'Condition' creation area, you will go to 'Conditon Editor' where you can write your condition.
In the condition editor, you will be able to access all workflow container elements. Your conditon can be in the following format
&var1& &relational operator& &var2&
you can also mention some constant value for var2. In general var1, var2 can be anything from workflow container elements.
So, when your condition is met, loop will end and flow will follow to the next step after 'Loop Until' block. If your condition is not met, you will loop again.
In general, may be you can have 'Total_No_of_Iterations' container element to store the value how many times the loop should run and 'Iterator' to refer to loop count. When your 'Iterator' value equals to 'Total_No_of_Iterations', may be you can come out.
Hope this helps you to go ahead with Loop Until step in your workflow !!
Thanks and Regards
Krishna Mohan Dubbak
PS: your terms 'Comparison Basis' 'Comparison Values' are more relevant to 'Mutliple Condition' type. Please note that using Loop Until you can have only 2 possibilities either loop end or loop continue, you can not have any other option.
Reward points if this helps to solve your problem !!

Similar Messages

  • Bug fix for NI Do-While step type?

    I'm using a group of add-on flow control step types from NI that implement common looping structures. However, the Do-While step results in an error -13 when you try to edit/configure an existing step.
    Has anyone else seen this, and more importantly, is there a fix for this?

    Hi Darin,
    I'm not sure if I have the exact same version of the Flow Control steptypes as you, but when I tried editing/configuring the Do-While step type several times over and over again I could not cause it to throw any error. Go to the following link and download what we have on our website and replace the steptypes that you have with these (I just downloaded the ones listed on this webpage and tested your scenario with them):
    http://sine.ni.com/apps/we/niepd_web_display.displ​ay_epd4?p_guid=B45EACE3E9AF56A4E034080020E74861&p_​node=DZ52236&p_submitted=&p_rank=&p_answer=&p_sour​ce=External
    Let us know if reinstalling the steptypes fixes the problem or not. If not, perhaps you could post a small example sequence that utilizes the steptypes you have so that we
    can check to see if they are the same version and try to reproduce the error with a sequence you generated. Thanks!
    Jason F.
    Applications Engineer
    National Instruments
    www.ni.com/ask

  • Workflow Builder step type 'Loop (While)' missing

    The step type 'Loop (While)' is missing in the workflow builder in both the SWDD and PFTC transactions.  This is happening is a WebAS 640 Support Pack 14 system and a WebAS 700 Support Pack 8 system.
    I have searched in SDN and OSS notes but could not find anything related.
    Are we missing some configuration setting or is this step no longer supported?  Thanks in advance for anyone who can provide some hint.

    How do you create the step?
    Did you try, cliking the cursor on the place you want the step to be, then click on the create button and then select the loop while (maybe your resolution is too small, so that you don't see it appearing)
    Kind regards, Rob Dielemans

  • Data Acquisition Step Type

    Hi, is there a step type to perform Data Acquisition and Basic comm control such as RS232 and GPIB within teststand ?
    This question was raised when I was training one of our Technicians today, he asked/suggested that having a step type which performs Data Acquisition and comm control would reduce there development time down dramatically, They have just started to use Teststand on small cycle test rigs as part of an evaluation stage. They have no experience with LabVIEW or CVI, they basically want a quick  and easy way to produce a test sequence with Data Acquisition and comm control.
    if there is anything like this at the moment can you possibly reply. If there is not,  is this a something which will be avaible in the future ?
    Message Edited by ds1638 on 12-09-2008 02:44 PM

    Data Acquisition usually refers to a DAQ board from NI so I think what you are looking for is a generic NI-VISA step type and a specific RS-232 step type. I have a NI-VISA step type that was originally written with LabVIEW 6.1 and for use with TestStand 2. I've atached that below. I don't have the .ini file handy and don't have time to recreate it but from the code, you should be able to see what needs to be added to the step properties. The basic step is a modified Pass/Fail Step.
    It's not that difficult to create your own custom steps. I've done a lot and it only takes a little while longer than doing a code module in LabVIEW or CVI. The extra time is in creating the edit step.
    I've got an RS-232 step type but part of it is product specific so it is proprietary and I can't post that. Look at the VISA example and the other examples of custom step types that are on the developer zone and see how far you get.
    Attachments:
    VISA IO.zip ‏188 KB

  • Java Step Types with Java Virtual Machine higher than java-6u16?

    Documentation of Java steps says, that these steps are tested with java version 6 update 16. I am talking about the java step types that can be found in directory <TestStand Public>\TestStand 2010\Examples\Java. 
    If I install another java version, e. g. java 7, step "Start JVM" will exit with an error "-4" and error message "Could not launch JVM.". While Debugging source code of JavaCall.dll, I figured the failing code line out:
    "fpCreateJVM(&jvm,(void**)&env,&vm_args);" is the execution of function "JNI_CreateJavaVM" and returns error code -4.
    Till now I could not find out, why the jvm does not start. I guess -4 means "Insufficient memory to create the JVM." (http://zone.ni.com/reference/en-XX/help/370052J-01/tssuppref/infotopics/java_steps_errors/)
    Has anyone an advice for me?

    This post gave me a hint: http://stackoverflow.com/questions/3400292/jni-enomem-from-jni-createjavavm-when-calling-dll-that-us...
    Though my development computer has enough ram, jvm is started within the Teststand process which offers limited memory. I changed JavaCall.c and added parameter "-Xmx64m" to the jvm creation call. Now it works with jre 7.
    Because memory space Teststand offers to the jvm is different on different computers, an implementation would be nice that checks how much memory is available and then passes the calculated <MEM> as parameter "-Xmx<MEM>m". Here is an example implementation: https://forums.oracle.com/forums/thread.jspa?threadID=1546540

  • Workflow-step type condition

    hai all.....
      I have got a problem while working with the step type 'condition' in workflow,i.e i want to check the values in internal table in my step type for example,whether the internal table is initial....please someone help me ..its very urgent...

    Hi Kasi,
    I can provide u a simple workaround for this...
    U can create another table within the workflow container of the same table type.
    name it as empty_<table>.
    Than within the condition step, u can simply compare the original table with the dummy empty_<table>.
    This should solve your issue
    Regards,
    Mahesh.

  • Step type 'condition' in workflow

    hai all.....
    I have got a problem while working with the step type 'condition' in workflow,i.e i want to check the values in internal table in my step type for example,whether the internal table is initial....please someone help me ..its very urgent...

    Hi Kiran,
    For the Operator 'NX' u need not enter any comparison value. U click on the condition in the condition step type . A window appears and u click on the internal table in expression 1 and the operator as 'NX' . It doesnt need a comparison value.
    Now u check this with the test data in the same window . U will have an icon in the bottom of window to enter test data and another icon to evalutate it . U check it with data and without data. It will work .
    In ur reply to Kasi , Ur answer is not at all related with what kasi asked for .U can check the initial property while the data is in workflow container itself . Instead u r passing the data from workflow container to task container and then to method container and then the processing has to take place in BO and again the reverse should take place .Which is Unnecessary .
    Regards,
    Scobby.
             Be Free To Award Points

  • When i run a sequence with ivi step types in simulation mode i get the error code number BFFA0015 - Types do not match.

    When i run the sequence with ivi step types in simulation mode i get the error Types do not mathc. The step that generates this error is an IviScope step type and is configured as a measurement. Th weird thing is that in real mode is working perfectly. I have three measure steps and i get the error in all of them. The exact error message is:
    UUT Result: Error, Error executing substep 'Post'. An exception occurred calling 'RunStep' in 'ISubstep' of 'TestStand Ivi Step Types 1.0 Type Library' An error occurred while executing the step. Component Works IVI Control Error: The IVI Read operation failed on channel '1' for logical name 'SampleScope'. Details: (1
    ) Types do not match. [IVI Error Code: BFFA0015] Source: TSIviStepTypes [Error Code: -30721, User-defined error code.]
    Can someone tell me how to fix this problem?. It seems to me that the simulation generates a diferent type of measurement of that generated in real mode.

    Update:
    The simulation driver appears to be raising the error. By switching to specific driver simulation the error does not occur. This may be a problem in either the class simulation driver or the specific driver.
    Scott Richardson
    National Instruments

  • Stationglobals in a Labview custom step type inside a new thread do not get updated

    Hi,
    I have a Custom Step type which I use to pass parameters to TestStand from a VI and vice-versa through some step fields. I run the VI inside a sequence in a new thread and expect the VI to update the parameters when I change them through the TestStand StationGlobals.
    For example, I have a waveform injection custom step. I want to continuously inject a signal while I do some measurements on it. So, I put this step type in a sequence and ran it in a new thread. 
    I pass the VI parameter 'Stop_Injection' through a step field as shown in image 1. And I expect the step field to get updated when the new thread is run continuously by passing the corresponding stationglobal in the Pre-expression of the custom step (image 2). But this fails to happen. The VI does not get updated.
    On the other hand, if I do not bother with the step field and directly pass the stationglobal (figure 3), it works perfectly. 
    Any idea why this is happening?
    I hope I was clear in my question.
    LabVIEW 8.6.1
    TestStand 4.1.1
    Message Edited by Changi on 08-06-2009 12:50 AM
    Attachments:
    1.JPG ‏92 KB
    2.JPG ‏42 KB
    3.JPG ‏91 KB

    Hi,
    In image 3 you are linked directly to the StationGlobal of which you are continually updating therefore seeing the changes.
    In the other you are only linked to the Step.Stop_Injection and are only updating this valve from the stationglobals once in the pre-expression. You are not changing the reference.
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • SWDD abends when dragging a step type into existing template

    Hello,
    The following steps cause an abend.  Has anyone seen this and found a fix?
    - Start transaction SWWD
    - drag a new step type into an existing workflow template
    - at the cursor a plus sign displays
    - upon releasing the mouse button the program abends
    I created an incident report in OSS.  While awaiting their response I thought I would ask the community.
    The abend listing is included in an attachment.
    Thanks
    Bruce

    Hi Bruce
    Solution: Note 1783103 - Short dump or system hanging during drag and drop in the workflow builder - Same abend message and steps. This note asks to Apply note 1769371 to solve the issue. Please note that the correction comes with SAP GUI 7.30 patch 2 ...  Ronen Weisz is correct in saying that the SAP GUI is the culprit here ;-)
    regards,
    modak

  • Fork step type.

    Hi Experts,
                     i am learning workflows. could you please explian me the significance of FORK step type with real time example so that i can understand it better.

    Hi,
    By using fork you execute several process in parallel.
    While creating Fork, you have to enter no of parallel branches and necessary branches.
    Parallel branches signifies that how many parallel branches you need to meet your requirement.
    Necessary branches. signifies that how many branches need to complete to move next step in worklfow.
    For example,
    You need 3 approval from 3 manager for your leave.
    Now create fork with 3 parallel branches and necessary branches 3.
    This signifies that after the completion of three branches workflow will process to next step.
    If you have made and necessary branches 1 then workflow will proceed to next step if any branch completed.
    Thanks and regards,
    SNJY

  • Does IVI Step Type support NI PXIe-4112?

    Hello, Guys
    I have a PXIe-4112 and four of PXI-4130. When I try to configure my PXIe-4112 with the PowerSupply IVI Step Type, an error occurred.
    An error occurred calling 'RunStep' in 'ISubstep' of 'zNI TestStand Ivi Step Types'
    An error occurred while executing the step.
    Component Works IVI Control Error: The IVI Configure operation failed for logical name '4112'.
    Details: Attribute or property not supported. Attribute: NIDCPOWER_ATTR_OVP_ENABLED, Channel: 0 [IVI Error Code:  BFFA0012]
    Source: TSIviStepTypes
    Surely I disabled the 'OVP Enabled' check box at the Edit IVI Power Supply Step Dialog. My system configuration is,
    IVI Compliance Package 4.6
    NI-DCPower 1.8.6
    NI TestStand 2012 SP1
    My PXI-4130s are working well with the IVI Step type. Does IVI Step Type support NI PXIe-4112? Or am I doing something wrong about it?
    Regards,
    Joonam
    CTA, CLA
    SuninCNS
    Solved!
    Go to Solution.
    Attachments:
    4112.png ‏17 KB

    Hi Joonam,
    The PowerSupply IVI step will not currently work with the 4112.  
    The 4112 does not support OVP.  If the NIDCPOWER_ATTR_OVP_ENABLED attribute is set to True, the error that you described is expected.  If it is set to False, no error should be generated.  However, an error is generated when it is set to false.  This is incorrect behavior in the driver and has already been documented under Corrective Action Report (CAR) #437105.  This issue will likely be rectified in a future version of NI-DCPower.
    The PowerSupply IVI step is hard-coded to set the attribute to true or false, based on the value of the check box in the Limit tab.  The workaround to this problem is to replace your PowerSupply IVI step with a step based on a code module that doesn't try to set the OVP_ENABLED attribute at all.
    I apologize for any trouble that this has caused you.  Let me know if you would like any further clarification.
    Regards,
    Jared R.
    Precision DC Product Support Engineer
    National Instruments

  • Show popup dialog at step type dropping to the sequence

    I have a LabVIEW step type with some module parameters and step's variables what needs to be setup to configure this step. Can I make it to display the popup dialog to enter the required values at the moment when I drop the step type to a new sequence?
    Examples: 1. I have TestID in steps variables what needs to be setup. Popup dialog is more convenient than going to Variables and searching for the TestID in tree. 
    2. I have one step type which does a different actions depending of the enum parameter in the LabVIEW module. This parameter is set to default in steptype. I'd like the step name in my sequence to be the value of the enum. Something like RunState.Step.TS.SData.ViCall.Parms["Configuration Update"].ArgVal in the step type Default Step Name Expression helps and displays the enum text as step name when I drop the step type in the sequence. But changing the Configuration Update parameter in this step to another value does not followed by changing the step's name, looks like the step type's Default Step Name Expression is evaluated only once when step is created from the step type.
    Sergey Kolbunov
    CLA, CTD
    Solved!
    Go to Solution.

    Thank you Doug, your advise works just perfect for the first case. OnNewStep, who may think about it? Is it documented somewhere?
    For the second case it is not so straightforward. I don't care so much about automatic update of the step name when it is already in a sequence, setting this name and the appropriate module's parameter at insert will be enough. Tool to update names is not a problem, I'm using such kind of tool to automatically update sequences when my step types got changed. I need the subject feature because I'm trying to create a custom sequence editor for end users with minimal knowledge of TestStand.
    Talking about second case, it's look like setting of module's parameter via expression does not work. Now I'm trying to set it using TestStand API in the OnNewStep substep.
    Now I have another problem. How to access the TestStand Adapter API automation server in LabVIEW? I'm trying to get Sequence Context ->Step ->Module ->Parameters but to get Parameters property of LabVIEWModule class the TestStand Adapter API server required while I see properties list for the Module class of the TestStand API server. It seems to be very easy to switch server in TestStand but how to do it in LabVIEW?
    Sergey Kolbunov
    CLA, CTD

  • Automatic update of Step Types

    I have developed a Step Type and I've used it in several sequences. After a time I've made some modifications on this Step Type. Now, when I open the sequences where my step type was, I don't have automatically the updated version. Is it possible to "compile" or "update" the sequences in order to avoid this problem?
    Thanks

    Angel -
    Most properties in a step type are default properties, that is the step type defines them and the instance step gets these value only when the step is first created. If you notice in the Step Type Properties dialog box most of the tabs say "default".
    If a step instance is loaded at the time you edit a step type property and you check the box at the bottom of the dialog box that says "apply to all instances", the changes to the step type will also be applied to the loaded steps. If a file is not loaded, the steps in that file will not see these changes.
    If you want to apply the step changes to the unloaded sequence files, you need to perform the above actions again while these other sequence files are loaded.
    Scott Richardson
    Scott Richardson
    National Instruments

  • Getting Sequence object from pre-step substep of Sequence Call based step type

    How to obtain reference to Sequence object from within pre-step substep of Sequence Call based custom step type?
    Given: new custom step type which based on NI Sequence Call step type. There is Pre-Step substep exist for this step type.
    How to get reference to Sequence object representing Sequence which will run?
    Although there is possible to examine SequenceAdapter and SequenceCallModule properties, it seems redundant since module (Sequence) is already loaded by TestStand ("NI TestStand Reference Manual. Table 3-4. Order of Actions that a Step Performs"   Action #6, while my code is running as Action #13).
    Thanks.
    Misha

    Could you explain what you want to do ?
    Why do you want to get the sequence object within a pre-step substep ?
    I give you some informations but I don't know if it's the better way to do what you want (because I don't know what you want to do with the sequence object).
    If the substep uses the ActiveX adapter :
    You can get the sequence object but you should save the object reference in a StationGlobals variable.
    And you should release the object reference within your sequence when you don't need it any more.
    If the substep uses another module adapter: 
    Get the step module, then the sequence name (module property).
    Then get the sequence object by the sequence name from the sequence file.
    Here are the paths to use for both methods :
    Sequence Name property path : Step.Module.SeqName
    Sequence Object path : RunState.SequenceFile.GetSequenceByName (seqname)

Maybe you are looking for