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

Similar Messages

  • 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

  • The type library information for 'TestStand IVI Step Types' was not found (Error code: -18351)

    Hi,
    I get the error in the message subject when I add an IVI-C step (no matter IVI Power Supply, IVI Dmm or others) and try to edit the step by pressing Ctrl+E (or double-click the step and click "Edit IVI Power Supply" for instance).
    I have installed 2 IVI-C libraries that I downloaded from 'NI idnet' both with IVI technology (namely agn330xa_MS.msi and agn6700_MS.msi). They can both be seen in Add/Remove programs under "NI IVI Specific Drivers" group.
    The error message says "Make sure the server is registered".
    Does anybody know what server is it complaining about and how can the registration be done?
    Regards,
    S. Eren BALCI
    www.aselsan.com.tr
    Attachments:
    error 18351.jpg ‏66 KB

    Hi ebalci,
    I believe this error is occurring because the ActiveX components that are used by the IVI step types are either not properly installed or not properly registered.  I would recommend first making sure that the IVI compliance package and NI-VISA are installed on the system.  If both of these are already installed, I would recommend running the TestStand Version Selector because this should re-register the ActiveX components used by the IVI step type.  The TestStand Version Selector can be found by going to the Start Menu>>Programs>>National Instruments>>TestStand 3.5.  You will need to select the version of TestStand you want to use and click the "Make Active" button.  I have also pasted links below to VISA and the IVI compliance package.  Hope this helps!
    NI-VISA
    IVI Compliance Package
    Pat P.
    Software Engineer
    National Instruments

  • Add an IVI Step Type

    I would like to use an iviRFSigGen with teststand (Currently using ver 2.0). Can I add a step type to do this or is there a step type already available to do this.

    Hi,
    We have a beta version of the custom step "IviRfSigGen".
    Unfortunately, it was not tested so well, it seems like starting exsample for you.
    Please see the attached zip. file and Your comments and suggestions are very welcomed.
    Br,Sergei
    "Only a life lived in the service to others is worth living..." - Albert Einstein
    Attachments:
    IviRFGen.zip ‏444 KB

  • Latest IVI Class Step Types in TestStand

    IVI instrument classes have recently been defined for RF Signal Generator, Spectrum Analyzer and Power Meter. There are IVI drivers for these classes available for download from the Instrument Driver network. However, TestStand3 does no contain step types for accessing these drivers. Does anyone know when NI plans to add support for these to TestStand? Has anyone created step types for these classes, or have an example of how to do this?

    David -
    There is no documentation on the low-level workings of the TestStand IVI step types. As with many of the step types that have source code, it is available as examples of developing a step type in various languages.
    The additional work to add the a new class to the TestStand IVI step types is not small, that is why to date we have not done it. The amount of work could be divided into the following areas:
    * Update the TsIviStepTypes to add the new class to the enumeration.
    * Create the new step type definition (subproperty structure) based on the IVI spec.
    * Upcate the TSIviStep and TSIviSFP code to allow you to edit and perform the work to process the expressions and initiate the various IVI class operations.
    * Add low level
    IVI class layer logic to talk to the IVI class driver. This piece was previously done in a VB ActiveX control written by the Measurement Studio group in NI.
    The last two items are the biggest and they would take some time. That is why I was suggesting creating specific Action steps that call into custom code modules to talk to IVI directly, that is, no edit dialog box, no SFP, etc.
    Scott Richardson (NI)
    Scott Richardson
    National Instruments

  • How do I make Step Types in the Type palette be "master" versions which all sequence files on a particular should use? (since this only seems to "half work")

    The situation I would like is to have a library of step types which sequence developers can use. Therefore if new step types need to be added, or existing ones modified - all that needs to be done is to roll out a new MyTypes.ini (for example), and the code modules/substeps.
    Scenarios:
    If I create types in MyTypes.ini (make sure "Attach to this file" is checked, so they get saved here). I can then create a sequence file using these step types. No problem so far.
    I can open the type palette, modify the step properties, and save. When I go back to my sequence file an asterisk appears (saying it needs to be saved, even if I have opened it from scratch). The properties have been updated to reflect what is in the Type Palette. Still no problem (Type versions are the same in the sequence file and type palette).
    This is where the problem appears:
    If I change a step type (in the Type Palette) from using a code module to using a Post-Step substep instead (changing the module adaptor to "None") - any instances do NOT update when you open sequence files. (The same happens vice versa also).
    Please note that the "Type version" listed in the sequence file DOES match that listed in the Type Palette - the properties are the same but the manner in which the code modules are called is DIFFERENT! This then can lead to to runtime errors if the old code module has been deleted for example.
    The only way around this is to open EVERY sequence file that contains an instance of the step type, and make sure that you have "Apply changes to all loaded instances of this type" checked in the step type properties dialog. This is is not a good solution since files could be missed, and is very time consuming if you have hundreds of sequence files!
    What I need is that the Type Palette on any particular station contains the MASTER copies of each type. These are loaded whenever a sequence file is loaded and NOT retreived from the sequence file. As discussed above this seems to work when you modify properties - but doesnt work fine if you change the way in which code modules are called.
    Am I doing something wrong or is this a limitation?

    I had a system recently containing seven sequence files, approx 20 subsequences in each, and around 10-20 steps in each sub-sequence. Every step (except for the NI non-code module types) was an instance of a step type.
    Each one of these steps had an Edit sub-step and a code module called through the code module adapter.
    In order to make these into "wrapped up" step types it was decided to move the code module to a Post-Step substep (as also done in the NI-IVI step types) - so that developers cannot fiddle with the code prototype or module.
    In order to do this I had to open all 7 of the sequence files, make the changes and then ensure that "Apply changes in this dialog to a loaded instances" was checked. This seems to sort of work, but some steps started causing Error 17502 (System Error) when you configure them (call the Edit substep). Over the course of the past few months I have had to effectively check every instance of a type to see if it works (deleting the step and replacing it when it doesnt). Other strange things happened like some of the step type instances now have the "None" (adapter) icon associated with them - but both still work.
    The idea of creating a type-def of a step type is a good one, but frustrating that it doesnt seem to fully work. Why should the sequence file also store a version of the step-type - which is what is effectively causing this problem - why not make it so that if you dont have the step types installed in the type palette - TOUGH! Message Edited by RichM on 03-15-2005 06:55 AM

  • 5112 in Teststand using IVI step

    I am trying to configure with options and set the 5112 to average but get an error. I also can not validate any of my niscope settings. The step seems to work when I execute it, and I only find out what is not supported when it fails.
    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 Configure operation failed for logical name 'niScope'.
    Details: Extension capability not supported by instrument driver. (AverageAcquisition)
    Source: TSIviStepTypes
    Please help.

    If you are running TestStand 2.0, you will need to upgrade to 2.0.1. You can get information about this at www.ni.com/upgrade. If you are currently using 2.0.1 then I need to know what version of NI-Scope and what version of the IVI engine.
    Michael

  • 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 modify a step type description?

    I need to modify the description of some custom step types. I saw how this is made in the Basic Ivi step types. What i want to do is to display the current selected operation for an ivi step type as is done in the basic Ivi step type. Isaw that this is done just evaluating the vriable instrOperation and depending on the value you guys insert a name corresponding to that value.
    I tried to do the same and modified a custom step's description in order to display the currently selected oparation. The problem is that i can't display any label...instead of the label i want to appear i get a "String not found in Table" message in the step's description. What table is this?...Do i need to make the changes i want in a table or i can just use some predefined labels?...this is because with simple words like FREQUENCY or INIT the description seems to work fine. What can i do to solve the problem?
    This is the description i have in the step:
    ResStr("IVI_STEP_TYPE", "IVI", "IVI") + " " + ResStr("IVI_STEP_TYPE", "Counter", "Counter") + ": " + ((Step.LogicalName=="") ? ResStr("IVI_STEP_TYPE", "UNSPECIFIED LOGICAL NAME", "UNSPECIFIED LOGICAL NAME") : LocalizeExpression(Step.LogicalName)) + ", " + ResStr("IVI_STEP_TYPE", ((Step.Operation==0) ? "CONF FREQUENCY" : ((Step.Operation==1) ? "MEASURE" : ((Step.Operation==2) ? "READ" : ((Step.Operation==3) ? "INIT" : ((Step.Operation==4) ? "STATUS" : ((Step.Operation==5) ? "ABORT" : ((Step.Operation==6) ? "FETCH" : ((Step.Operation==7) ? "PERIOD" : ((Step.Operation==8) ? "CONF. VERTICAL" : ((Step.Operation==9) ? "CONF. INPUT IMPEDANCE" : ((Step.Operation==10) ? "CONF. BANDPASS FILTER" : ((Step.Operation==11) ? "CONF. LOWPASS FILTER" : ((Step.Operation==12) ? "CONF. HIGHPASS FILTER" : ((Step.Operation==13) ? "UNCONFIGURE FILTER" : ((Step.Operation==14) ? "SECONDARY EVENT" : ((Step.Operation==15) ? "RISE TIME" : ((Step.Operation==16) ? "FALL TIME" : ((Step.Operation==17) ? "POSITIVE PULSE" : ((Step.Operation==18) ? "NEGATIVE PULSE" : ((Step.Operation==19) ? "CONF. INTERVAL X TO Y MEAS" : ((Step.Operation==20) ? "CONF. PHASE X TO Y MEAS" : ((Step.Operation==21) ? "MEASURE X TO Y" : ((Step.Operation==22) ? "CONF. EXT. START ARM" : ((Step.Operation==23) ? "CONF. IMM START ARM" : ((Step.Operation==24) ? "CONF. EXT. STOP ARM" : ((Step.Operation==25) ? "CONF.TIME STOP ARM" : ((Step.Operation==26) ? "CONF. DIGITS STOP ARM" : "INVALID OPERATION"))))))))))))))))))))))))))))
    and this is the description i get in some of the steps:
    Ivi Counter, "Sample Counter", String not found in table

    Eromero -
    The ResStr function retrieves a string from the TestStand language resource files. We call this a table. The funtion requires a category and tag value name. Review the Creating String Resource Files section in Chapter 3, page 6 of the User Manual for more details.
    So the strings that you are already referencing are in the IviStepTypes.ini file in the
    Components\NI\Language\English directory. You could add your new strings that you require to a sister file that you would create under the Components\User\Language\English directory, or you can remove the call to ResStr and just hardcode the string with your step type if you do not want the ability to translate the string for other languages.
    The call that is probably failing is:
    ResStr
    ("IVI_STEP_TYPE", ((Step.Operation==0) ? "CONF FREQUENCY" : ...
    Also, right now the call to ResStr("IVI_STEP_TYPE", "Counter", "Counter") is probably failing and just using the default value you supply in the call.
    Scott Richardson - NI
    Scott Richardson
    National Instruments

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

  • Does the advanced queue support setting the pay load type as array/table?

    Does the advanced queue support setting the pay load type as array/table?
    if yes, how to write the enqueue script, I tried to write the following the script to enqueue, but failed, pls help to review it . Thanks...
    ------Create payload type
    create or replace TYPE "SIMPLEARRAY" AS VARRAY(99) OF VARCHAR(20);
    ------Create queue table
    BEGIN DBMS_AQADM.CREATE_QUEUE_TABLE(
    Queue_table => 'LUWEIQIN.SIMPLEQUEUE',
    Queue_payload_type => 'LUWEIQIN.SIMPLEARRAY',
    storage_clause => 'PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 TABLESPACE USERS',
    Sort_list => 'ENQ_TIME',
    Compatible => '8.1.3');
    END;
    ------Create queue
    BEGIN DBMS_AQADM.CREATE_QUEUE(
    Queue_name => 'LUWEIQIN.SIMPLEQUEUE',
    Queue_table => 'LUWEIQIN.SIMPLEQUEUE',
    Queue_type => 0,
    Max_retries => 5,
    Retry_delay => 0,
    dependency_tracking => FALSE);
    END;
    -------Start queue
    BEGIN
    dbms_aqadm.start_queue(queue_name => 'LUWEIQIN.SIMPLEQUEUE', dequeue => TRUE, enqueue => TRUE);
    END;
    -------Enqueue
    DECLARE
    v_enqueueoptions dbms_aq.enqueue_options_t;
    v_messageproperties dbms_aq.message_properties_t;
    p_queue_name VARCHAR2(40);
    Priority INTEGER;
    Delay INTEGER;
    Expiration INTEGER;
    Correlation VARCHAR2(100);
    Recipientlist dbms_aq.aq$_recipient_list_t;
    Exceptionqueue VARCHAR2(100);
    p_queue_name VARCHAR2(40);
    p_msg VARCHAR2(40);
    p_payload LUWEIQIN.SIMPLEARRAY;
    BEGIN
    p_payload(1) := 'aa';
    p_payload(2) := 'bb';
    SYS.DBMS_AQ.ENQUEUE(queue_name => 'LUWEIQIN.SIMPLEQUEUE',enqueue_options => v_enqueueoptions, message_properties => v_messageproperties, msgid => p_msg, payload => p_payload);
    END;
    ------Get error
    Error starting at line 1 in command:
    DECLARE
    v_enqueueoptions dbms_aq.enqueue_options_t;
    v_messageproperties dbms_aq.message_properties_t;
    p_queue_name VARCHAR2(40);
    Priority INTEGER;
    Delay INTEGER;
    Expiration INTEGER;
    Correlation VARCHAR2(100);
    Recipientlist dbms_aq.aq$_recipient_list_t;
    Exceptionqueue VARCHAR2(100);
    p_queue_name VARCHAR2(40);
    p_msg VARCHAR2(40);
    p_payload LUWEIQIN.SIMPLEARRAY;
    BEGIN
    p_payload(1) := 'aa';
    p_payload(2) := 'bb';
    SYS.DBMS_AQ.ENQUEUE(queue_name => 'LUWEIQIN.SIMPLEQUEUE',enqueue_options => v_enqueueoptions, message_properties => v_messageproperties, msgid => p_msg, payload => p_payload);
    END;
    Error report:
    ORA-06550: line 17, column 3:
    PLS-00306: wrong number or types of arguments in call to 'ENQUEUE'
    ORA-06550: line 17, column 3:
    PL/SQL: Statement ignored
    06550. 00000 - "line %s, column %s:\n%s"
    *Cause: Usually a PL/SQL compilation error.
    *Action:                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    but when I use the following script to enqueue get error. Pls help to review. Thanks...
    DECLARE
    v_enqueueoptions dbms_aq.enqueue_options_t;
    v_messageproperties dbms_aq.message_properties_t;
    p_queue_name VARCHAR2(40);
    Priority INTEGER;
    Delay INTEGER;
    Expiration INTEGER;
    Correlation VARCHAR2(100);
    Recipientlist dbms_aq.aq$_recipient_list_t;
    Exceptionqueue VARCHAR2(100);
    p_queue_name VARCHAR2(40);
    p_msg VARCHAR2(40);
    p_payload LUWEIQIN.SIMPLEARRAY;
    BEGIN
    p_payload(1) := 'aa';
    p_payload(2) := 'bb';
    SYS.DBMS_AQ.ENQUEUE(queue_name => 'LUWEIQIN.SIMPLEQUEUE',enqueue_options => v_enqueueoptions, message_properties => v_messageproperties, msgid => p_msg, payload => p_payload);
    END;
    ------Get error
    Error starting at line 1 in command:
    DECLARE
    v_enqueueoptions dbms_aq.enqueue_options_t;
    v_messageproperties dbms_aq.message_properties_t;
    p_queue_name VARCHAR2(40);
    Priority INTEGER;
    Delay INTEGER;
    Expiration INTEGER;
    Correlation VARCHAR2(100);
    Recipientlist dbms_aq.aq$_recipient_list_t;
    Exceptionqueue VARCHAR2(100);
    p_queue_name VARCHAR2(40);
    p_msg VARCHAR2(40);
    p_payload LUWEIQIN.SIMPLEARRAY;
    BEGIN
    p_payload(1) := 'aa';
    p_payload(2) := 'bb';
    SYS.DBMS_AQ.ENQUEUE(queue_name => 'LUWEIQIN.SIMPLEQUEUE',enqueue_options => v_enqueueoptions, message_properties => v_messageproperties, msgid => p_msg, payload => p_payload);
    END;
    Error report:
    ORA-06550: line 17, column 3:
    PLS-00306: wrong number or types of arguments in call to 'ENQUEUE'
    ORA-06550: line 17, column 3:
    PL/SQL: Statement ignored
    06550. 00000 - "line %s, column %s:\n%s"
    *Cause: Usually a PL/SQL compilation error.
    *Action:                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • What does your account type does not support the view account feature mean?

    What does your account type does not support the view account feature mean?

    In reference to what? Where are you seeing this message - iTunes? Do you use a credit card for purchases in iTunes or do you download only free content?

  • Execution time of IVI Steps

    Hello,
    We have made some benchmarks to decide the usefulness of TestStand IVI steps versus Labview ones with a PXI 4070 ( DMM ).
    The Labview steps ( using also IVI access !!! ) are 30% faster than direct TestStand IVI steps.
    May someone help us to understand such difference ?
    Thanks a lot.

    Oliver -
    The TestStand step types have additional overhead because all the configuration information stored on the TestStand step must be evaluated and passed to the a VB component.  Because the TestStand execution is multi-thread apartment and the VB component must be single thread apartment, some marshalling of data is necessary via COM.  Lastly the VB component is not optimized as the IVI VIs that you are using.  The TestStand IVI steps are not intended for speed, more easy of use. Hope this helps. 
    Scott Richardson
    National Instruments

  • 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

  • How to typecast property object to step type?

    Hello!
    We are doing to tool in Labview which analyses our defined custom step types. For this, we want to query the step type object from the TestStand engine.
    Unfortunatly, the IEngine.GetTypeDefinition() method returns a property object. There is an old entry in the forums with the same problem. There was stated just to typecast the object, but it was an VB example. How can this type cast be done in LabView? Using the "To More specific class" node results in broken fires because this polymorphic vi does not support the data type TS.PropertyObject or TS.StepType. So how to aquire a reference to TS.StepType from the return value of IEngine.GetTypeDefinition()?
    Best regards,
    Helge

    Hi, you need to go to the connectivity palette and then to the activex palette. On there is a "to datatype". The top terminal requires the data type you want to convert to - you can use a reference constant and then point it at the appropriate type (right click it and go to select activex class). Here's snippet to work from
    Hope that helps
    Thanks
    Sacha Emery
    Systems Engineer (NIUK)
    Message Edited by SachaE on 04-23-2009 01:13 PM
    // it takes almost no time to rate an answer
    Attachments:
    cast propertyobject to steptype.JPG ‏18 KB
    example cast.vi ‏5 KB

Maybe you are looking for