Is there an IviSwitch step type?

I would like to use the built-in IVI step types that comes with TestStand 2.0, to control my IVI instrument drivers. I am going to use several switching drivers, and I noticed there are IVI step types for DMM, Scope, Function Generators and DC Power supplies. Is there a step type for the IVI Switch class drivers?

This will be available in TS 2.0.1 (free upgrad to TS 2.0) in a couple of months.

Similar Messages

  • Can I create a global custom step type, available for all sequence files through a single copy?

    I would like to create a custom step type and make it available to any (new or existing) sequence file, without having to copy/paste it every time, to avoid maintenance problems...

    Hi Andre,
    You need to create the custom step type in the station view rather in the sequence file view.
    There's a step type button near the Users Button.
    Click on this button then proceed in creating the custom step type as you would have done in the sequence file.
    If you are using TS 1.0.x then the new step type will be added to the types palette.ini.
    If you are using TS 2.0 then will be able generate a new group ini file to hold your custom step types.
    Regard
    Ray Farmer
    Regards
    Ray Farmer

  • Is there a limit to step types? "Insert step" doesn't show all step types.

    Hello,
    I am observing a weird behavior with TestStand 2.0. As soon as the number of step types that i created goes beyond 60, I can't see some of the steps in the "Insert Step" pop up dialog. It doesn't show the arrows at the top and bottom, as usually, and only shows 53 options to pick, even though there should be 61 items. If remove the step type I created last, I get all of the step types available to be selected. On the other hand, if I open the same files in version 4.1, all of the types are shown. Is there something I can do with version 2.0 to get over this issue?
    Thanks,
    Sam.

    Sam,
    I tried replicating this issue in TestStand 2.1 and saw a similar problem, though not exact.  I had enough step types to make two columns in the Insert Step pop-up dialog, but some of the steps before it broke into a new column did not show up.  I could still access those though using the arrow keys.  After using the mouse pointer to highlight a step type, you can use the arrow keys to navigate down into the part of the list that isn't shown on the screen and hit enter to insert the step.  If you know exactly where your step should be in the list, you can select it and insert it, but other than that, there's no other way around it.  As you noted, this was a bug in TestStand 2.0/2.1 and it was resolved in a later version, so this is no longer a problem with current versions of TestStand.
    Eric B.
    National Instruments

  • 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

  • Creating a step type "launcher" that would insert the appropriate built-in or custom step type at edit time

    Hi everybody,
    I'm looking for tips, pointers,directions... to be able to perform this operation in TS 4.0 sequence Editor, if it's even possible...
    I'm managing a test system with a "home-made" virtual instruments abstraction Layer complementary to IVI classes for instruments which do not have classes defined, customizing the sequence editor accordingly for developpers of my department.
    So basically when the instrument is IVI, the developper uses the built-in IVI step-type type and when it is not, he uses the the custom step types that I developped for this particular class of instruments.  
    However there are classes where I do have both IVI and specific drivers available and I do need to use both in the test sequence.
    For example let's say there are two sources of DC power available in the testbench, one being a programmable IVI compliant DC power supply, and the other one composed of fixed "blocks" of DC power supply managed by externals relays and you need to use them both in the test sequence.
    What I would like to be able to do in the sequence editor is inserting the appropriate step type at edit time just by selecting the source of power supply (by a ring or enum for eg), and if the first ressource is selected, it inserts IVI step type, and if the second ressource is chosen, it inserts the appropriate custom step type.
    Any Ideas on how to accomplish this ?
    Regards,
    Cyril
    Cyril Bouton
    Active LabVIEW Developper
    Solved!
    Go to Solution.

    Hello Cyril,
    Here is an idea that could be done:
    You could create a dynamic step by having a step that holds all the properties for both configurations (the superset of the necessary variables) and an extra one that indicates which 'mode' the step is in.  Then you create the main Edit substep in whichever language you desire.  That substep window will then have a box/dropdown/etc. at the top you can use to choose between modes A & B.  When the user changes the value, you would dynamically change the rest of the window to contain the appropriate properties for mode A or B.  You then copy the property values in that window to the Step properties, and copy the mode to your variable and you can run the step in that mode.  When the step then runs, it checks the mode variable, and depending on its value, it will run the step in mode A or B.
    Now we could add a dialog that allows us to choose when we put a step down but we should still allow the user to change later via the Edit substep we create.
    I don't think we can create something that inserts a completely different step, but we can have one step that has the ability to do both and we can pick which one we execute.  Also note we still don't have the ability to edit the Panels for a step, so we have to use a new window that we call from our Edit substep to complete the step.
    Hope this helps.
    Regards,
    Olivier L. | Certified LabVIEW Developer

  • How can I include multiple limits in the sequence file documentat​ion for custom step type?

    Hi,
    I have a custom Step Type that contains Measurements property under Results. Its type is Array of NI_LimitMeasurement.
    I would like to see the values in the sequence file documentation like NI_MultipleNumericLimitTest type.
    Is there any trick to do that?
    Thanks,
    Andras

    Hi Andras,
    I have made  a slight change to the sequencefile 'docgen_txt.seq'.
    In the Sequence 'Step Doc' is a section which handles MultipleNumericLimit step type. There is a precondition check on the step 'Add Multiple Numeric Limits' if the step is of type 'NI_MultipleNumericLimit'. As your step type is based on the MultipleNumeric Limit type, I have just removed this precondition and just relied on the existence of Parameters.Step.Result.Measurement. Equally you could add a new section in this sequence to handle your Custom Step Type which is only called when the precodition match your type name.
    Now when you run the DocGen tool it handles your custom step type.
    Find attached my modified sequencefile 'docgen_txt.seq'.
    Just copy the contents of '..\National Instruments\TestStand 3.5\Components\NI\Tools\DocGen' to the User folder. Then place the attached file in the User\Tools\DocGen overwritting the version that is in that folder.
    Then launch TestStand and try it out on your sequence file.
    If you are using the html version, then you will have to make the same change into Step Doc sequence of the docgen_html sequence file.
    Hope this helps
    Regards
    Ray Farmer
    Message Edited by Ray Farmer on 05-19-2007 05:28 PM
    Regards
    Ray Farmer
    Attachments:
    docgen_txt.seq ‏184 KB

  • How to insert a new step type into a submenu?

    Hi!
    I'm inserting a step type into the MyTypes.ini file with c++.
    With the code below I managed to put it into a menu (in the step type menu editor it is called "Group").
    But I want a sub menu.
    How can I put it into a sub menu (in c++)?
    Who can help me? Thanks in advance!!!
    Here is the code:
    property->PutName("StepTypeName");
    typeUseage->InsertType(property, 0, TS::TypeCategory_StepTypes);
    stepObj->PutMenuGroupName("StepTypeMenuGroup");

    TSNewbie,
    There is no API method to edit those groups. I can only suggest to use the Step Type Menu Editor to create the group you want and make it a submenu. Then when you call stepObj->PutMenuGroupName("SubMenuGroup") the step type will be in that submenu.
    I apologize if this isn't the answer you are looking for.
    Ronald Byrd (NI)

  • Why do I get error -17500 when calling a batch file using the call executable step type?

    I am calling a batch file using the call executable step type. If the path to the batch file contains a space I get error -17500 and a message stating there was an error in "Post". For example the path to the batch file is "c:\TestWin\Test Files\...\Program.bat" When I run this I get the above mentioned error, however if I change my directory structure so the path is now "c:\TestWin\TestFiles\...\Program.bat" it runs fine. I use the browse feature to find my batch file so it is not me typing in a path incorrectly. I have removed the batch file and I get a different error stating that it couldn't find the file so it appears that for my error it can find the file but can't run it. I am
    sure that this has something to do with the fact that batch files are written in DOS but really don't want to resort to changing my directory structure on all my test stations. Is there any way to fix this problem so I can leave a space in my path?

    It appears I have figured it out. This was on another computer so I was unaware of how they used their computer. I like you got it to work in the temp directory and in fact got the program.bat file to work as long as I put it under the temp directory, but when I switched out to my TestWin directory it wouldn't work, so I removed everything from the directory except the batch file it self and it work. What I found out after adding files in one at a time is that the person had a file called "Test" with no file extension in there "c:\TestWin\" directory. Removing this file made it work. Putting the file back broke it. So it appeares that when teststand was running it followed the path saw a space and attempted to grab the "Test" file instead of bro
    wsing into the "Test Files" directory. If you create a file in your temp directory called "temp" with no file extension you will see the same problem. Thank you for your help.

  • Need to assign Role into step type mail in recipent type

    Hi Experts,
      I need to assign role to  for step type send mail recipent type . but in drop down there is not any role option to assign . to achive this i created organization  then position and assing job to that position then assigne to role under that job . after all in recipent type i assigned  with job . but when i execute workflow i am getting error . even i dirctally assign role to position and then assigne that position to recipent type. when executing my workflow i am getting error .
    but if a assigne user to position or job my workflow working properlay.  is there any proble to assing Role to Job or position.
    please let me know is there any  extra thing i need to take care when i assign  Role to position or Job .
    point will rewarded for right answer.

    Hello,
    Get the users assigned to the role into a container element in the previous step of 'SendMail' step and use the same as the recipient of the Sendmail step.
    This would be a better and easy option as Arghadip said.
    Hope this will help.
    Regards,
    Samson

  • User Decision step type

    Hi,
    I have developed a WF for 'Notification of Absence'. In this, a leave request is sent for approval.
    When the leave request is Rejected, the creator has to make a decision (User Decision step type used) as to 'Withdraw' or 'Update' the request. But in the inbox of the creator, there is no option for "Withdraw' and 'Update'. What could be the reason for this? Am i missing something?
    Thank you for your time.
    Ajay

    Hi AD,
    are you trying to process anything else after the Decision Step in your WF definition ?
    If yes, then what are you trying to process after it
    If no, then try what JMB said, GUI problem, I doubt that but you can try as you need to resolve it.
    Did you try removing the buffer ?
    Hope it helps.
    Aditya

  • "Disable tracing" as part of custom step type behavior

    Hi !
    Currently writing custom step types based on sequences (my step type's default adapter is a sequence), I would like to set the "disable tracing" right in my step type definition.
    The problem is that this option isn't visible in the 'Default Run Options" tab... The only way I found to do this is using Pre and Post Expression to set 'ThisContext.Tracing = True /False'.
    But I don't like the fact to use Pre/Post Expressions in my step type (I would prefer to let it blank for end users).
    Is there any way to achieve this without using Expressions ?
    Solved!
    Go to Solution.

    Here a printscreen on the properties available for my custom step... No TS container...
    Am I missing something ?
    Attachments:
    Step Prop.png ‏15 KB

  • Add-on step types for TestStand?

    I am almost certainly reinventing some wheels with Teststand by creating some basic test types.
    For example, I just wrote a custom step type for taking an analog measurement from a DAQmx instrument. Surely someone has done this before, and surely someone will want to do it again. There's nothing proprietary about code that simple, and I'd be happy to give it away if there was a place to post it.
    Two questions:
    1. Is there an open-source repository for sharing custom step types?
    2. Are there add-ons for purchase with canned step types beyond those which come with TestStand?
    -Arthur

    Hi Jigg, 
    I looked at Averna.com, and I don't see any add-ins available on their website. It looks like they offer services mostly. 
    It's a good point about TS projects being so varied and customized. However, if custom step types are well architected, as the built-in step types are, then they ought to be reusable by others. 
    You're right also that I can accomplish my DAQmx steps easily using an Action step with the LV adapter. My motivation for the custom step is to improve the interface for setting up such an action. In particular, when using an IO channel in TS, I have to manually type in a text string for the DeviceName value, whereas I'd like to choose from a list of global names (e.g. with the global channel list control in LV). I can get this affect by using an Enum in a wrapper VI, which maps to an array of channel constants; but this is fragile if the available channels are changed (e.g. added, removed or renamed in MAX).
    Additionally, a custom step type is better than a step template for my purposes, because I can propagate changes in the step type to instances of steps throughout the test. This is incredibly valuable to me during development and debugging. It saves me time when I want to update a step that I've used many times throughout a test sequence. Although TS isn't itself a programming language, I find that I expect it to share certain traits with programming languages to facilitate development, such as type abstractions and a strict enforcement of congruency between types and instances. But I digress....
    Thanks for your suggestions.

  • Step Type not updating properly with LabVIEW

    I have a custom steptype that reads the information from the step properties.  I also want this VI to be used as a stand alone.  So I read the sequence context handle to determine if I am running in TS or standalone.  This works fine.  Because it is a stand alone I have a cluster of all the variables the I will need input.  This is where the problems start.  I noticed that when I define the step type in TS that I load the prototype.  I choose to use the default values for the cluster input because I will read the real values inside the VI.  When I "EDIT" (ctrl-E) the step it works fine.  However at runtime I notice that occasionally the default value is used instead of the real data stored in the step type.  I assume there is a race condition for when my variables are loaded.  I assumed that when TS loads the prototype it will load the default values, then my LabVIEW TS properties will read and set the values of my VI.  What I am seeing is that about every other time my LV will read the steps and update the value correctly then other times TS will overwrite the values with the default after I have read them.  Some other wierd fluke I would notice that the variables would be updated in a similar but different named cluster.  This I haven't be able to reliably reproduce.  It is almost as if the references to the controls would get confused and switch to another control temporarily.
    One fix that I have done is to not use the default value but pass the actual step value.  See attached pix.  This is tedious because some of my steps are large.  This is not flexible.  Some of my variables I would like to point to different locations, such as a FileGlobal instead of step.XXX.
    Has anyone seen this before?  When does LabVIEW actually write the data from TS into the VI?  It appears that I am having a race condition between me updating the variables by reading the step values and when TS is loading the prototype.
    I am using LV 7.1 and TS 3.5.
    Thanks.
    Attachments:
    default.jpg ‏120 KB
    step.jpg ‏137 KB

    Hey Taylored_Solution,
    I'd love to try to help you out with this issue you're having, but I'll be honest - I'm finding it a little hard to follow what's going on.
    Have you been able to isolate this behavior to only one single VI (the one you're currently working on), or, is this behavior reproducible in multiple VIs? 
    I ask because if it's reproducible in multiple VIs (a new VI), would you mind giving me sort of "step-by-step" to follow so that I can try to reproduce and decipher the behavior you're currently seeing?
    If it's isolated to the VI you're working on and not easily reproducible, can you create a copy of your VI, remove everything not-pertinent to the behavior you're seeing, and post a very simple example so that other users can take a look and weigh in?
    Derrick S.
    Product Manager
    NI DIAdem
    National Instruments

  • What do I need to set in order for each instance of the step type in the sequence to act individually?

    I'm not able to change parameters on one step without it changing the parameters on another instance of the step within the same sequence.  Is there something in the step type properties that I need to set to change this?
    For instance, I have created a custom step called "Battery PWR" that the user can insert into a sequence, hit the "edit" button, set a control in a GUI to 12V and hit an "Okay" button so that the post-step condition causes the power supply voltage to change.  Then, later in the sequence I want the user to be able to insert the same custom step, hit the edit button, set the control to 0V and hit an "Okay" button so that the post-step conditition causes the power supply to go to 0V.  The problem is, when the user edits one of the steps, it causes the other step to change to the same value.
    I know that this has a simple fix, just can't seem to find it.

    I answered my own question.  I was reading and writing to a file global instead of the step parameters, so I was basically overwriting my variables each time I edited the step.  I'm obviously a novice TestStand user.

  • Programatically show/hide step types in the Steps pane

    When a user on a new Teststand Development bench syncs to a central repository of custom Teststand components and supporting LabVIEW code, I would like to expose only custom step types saved in myTpes.ini in the steps pane. None of the standard step types should be available unless the use explicitly opens an existing sequence file that contains them. I believe this can be done through the API when Teststand launches, but I don't know where to look for the appropriate API methods. For example, is there a methods to load or unload a specific type palette to or from memory? Any help would be much appreciated.

    Hi Charlie,
    As of right now, there does not appear to be a way to programmatically change step type menu items from visible to hidden via the TestStand API.  Someone has posted a product suggestion for this type of functionality to be made available in a later version of the software, however.  You can view it here.  I would recommend giving this idea kudos in order to boost its chances of being implemented in a future release.
    Hope this helps!
    Regards,
    Stephanie R.
    National Instruments
    Stephanie R.
    National Instruments

Maybe you are looking for