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

Similar Messages

Know steps names of called sequence file using sequence call step type in TestStand

Hi,
I have a problem in accessing step names in called sequence file using "Sequence call"step type in TestStand 4.0.
I would list out all step names of called sequence file. Is it possible to do through C#.NET? If, yes, Please explain to me in detail with possible example.
Thank you,
regards
RKK

Hey RKK,
I want to first set your expectations for the forums. This is not a place for people to review and rewrite your code for you; this is a place for specific and general questions. I am not saying your question in this thread is inappropriate, because it is a good questions. We should just not post code and ask others to fix it here. If you are looking for this type of service we have alliance members that can help you write your TestStand Operator Interface (www.ni.com/alliance).
As for you question about getting the sequence names for a sequence file that is not the currently running sequence file, you will need to open a reference to that sequence files and then use the API calls that I mentioned in my previous posts. You can use the Enigine.GetSequenceFileEx function to open a reference to sequence file, and you will need to close the reference with the Engine.ReleaseSequenceFile function when you are done using it. After you have a reference to this external Sequence File, you can use the example dll and sequence I previously sent you. I also attach a new sequence file (SeqFile2.seq) plus an updated GetNames.seq to illustrate how to use the above mentioned functions. I hope this helps. Have a great day!
Best Regards,
Software Engineer
Jett R
Attachments:
GetNamesOfSequencesInFile.zip ‏52 KB

IviAcPwr step type in Teststand available ?

Hello,
Im'using Teststand 2010 & Labview 2011 and i was looking for step type working with IviACPwr class...
I found Dmm, Scope, Fgen, Power supply (DC) & Switch...
Could someone tell me if there is an update for IviACPwr step type ?
Thanks for help.
GG
Ivi coompliance package 4.4.0.
Solved!
Go to Solution.

There is not a built-in step type for IviAcPwr in TestStand.
CTA, CLA, MTFBWY

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.

Automatically Installing Custom Step Types in TestStand 4.2

We have developed Custom Step types that needs to be integrated in a deployed TestStand System (customized UI with TestStand RunTime Engine) . We can customize the palette manually and add the related INI file. We also understand that the information gets saved in Testexec.ini in Cfg folder @ C:\ProgramData\National Instruments\TestStand 4.2\Cfg. What I am curious is how this process can be automated.
Thanks

dug9000 wrote:
I just want to add to the above that there are very good reasons to use type palettes even in a deployment. Using a type palette in a deployment ensures that all of the sequences on the deployed machine will use the version of the type in the type palette file... Using type palettes is recommended as a way to control which type versions are being used and to keep types more organized and centralized.
Absolutely - that's exactly why we're doing it this way. Our customer is in a regulated industry, and we need to control their development environment configuration very tightly. Speaking of which, so when will there be VIPM (TestStand Edition)?
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

Insert a specified built-in or custom step type in Teststand using CVI

I try to build a step type . this step type specifies an adapter of DLL, which is developed under CVI. I want to use Teststand API functions in CVI to fulfill the following functions.
1, insert a specified built-in or custom step type into current sequence;
2, insert a specified built-in or custom step type into another sequence.
Thanks!
Jacky

Hi Jacky,
There is an example program called Programmatically Inserting a Step into a TestStand Sequence Using LabWindows/CVI and a KnowledgeBase called Programmatically Inserting a New Step in the Currently Executing Sequence that should answer your question.
Hope this helps!
Best Regards,
Jonathan N.
National Instruments

Where to place custom step types in teststand 4.1?

Hi,
I have placed custom step types like ieee ssh etc, in the folder c:/documents....../components/user folder.
But i could view them, when i use insert step in sequence editor.
Please let me know is there any other location for teststand 4.1?
Thanks in advance.
Kris.

This link shows you the default paths for TestStand 4.1
Regards
Ray Farmer
Regards
Ray Farmer

Introduction to the SCOPE Step Type in TestStand

Hello!
I am new in NI TestStand and like to add a "SCOPE" Step Type in a Test - Programm.
Can anyone give a short introduction how i can use this step type ?
at first, i set a frequency and the following step should appraise these frequency by the scope.
greetings
patrick
Solved!
Go to Solution.

Hi Patrick,
have you ever looked into the step Variable ?
Hope this helps
Juergen
Message Edited by j_dodek on 04-22-2008 04:09 AM
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=
Attachments:
SCREEN.jpg ‏174 KB
SCREEN1.jpg ‏147 KB

How to create programmatically a new step type in TestStand (to myTypes.ini)

I need to create a new step type to myTypes.ini file programmatically. I have tried to do it with following steps:
- Get reference to engine
- Load type palette files
- creating new step type (engine.NewSteptype() )
- Inserting new type using TypeUsageList.InsertType method. Problem with this is the first parameter. It excpects it to be in a form of PropertyObject, but engine.NewStepType returns it as a StepType object. If I try to use StepType.AsPropertyObject it returns an error.
How to convert StepType object to a PropertyObject?

And here it is in C++:
TS::IEnginePtr mEngine;
SAFEARRAY * typeList;
TS::TypeUsageListPtr typeUseage;
TS:tepTypePtr stepObj;
mEngine = engine;
mEngine->LoadTypePaletteFiles();
typeList=mEngine->GetTypePaletteFileList();
TS:ropertyObjectFilePtr *rgelems;
SafeArrayAccessData(typeList,(void**)&rgelems);
typeUseage = rgelems[0]->TypeUsageList;
stepObj=mEngine->NewStepType();
TS:ropertyObject *property = stepObj->AsPropertyObject();
property->PutName("TestMe");
typeUseage->InsertType(property, 0, TS::TypeCategory_StepTypes);
rgelems[0]->IncChangeCount();
rgelems[0]->SaveFileIfModified(true);
SafeArrayUnaccessData(typeList);

Unsupported Ivi Class Driver

We developed a new ivi class driver (for counters) and everything works well, the problem comes when we try to use the ivi tool step type to acces functions such as Reset, selftest Get/Set attributes etc. When we use this functions we get the following 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 operation failed for logical name 'SampleCounter'.
Details: The session handle is invalid or refers to a session that is not from a supported IVI class driver.
Source: TSIviStepTypes
The strange thing is that the functions Close and init with options in ivi to
ols work very well..so what's the problem with the functions reset, selftest, etc..
With this functions we can't even access the generic driver code because the error shows up before we can get to the code in debbigging mode. Any ideas?.

eromero,
I sounds like there's either an error in the configuration for SampleCounter, or that the IviStepTypes only support the DMM, Scope, Switch, FGen, and DCPwr class drivers.
If you could send/post your ivi.ini file and your driver, I'd be happy to check it out and see if there's a configuration issue. If you don't want to post it to DevZone, you can e-mail it directly to [email protected]
As for why the init and close functions work, but not the others, I will investigate further.
One option to get your application to work is to not use the IviStepTypes. You can still use the driver using C function calls directly through the DLL. This will still work, but may not give you all of the features
of the step types.
Thanks,
Bankim Tejani
Instrument Drivers/IVI
National Instruments

Custom Step Type SubSteps Bug ?

Hi,
I'm having what I think is a bug. I'm doing a custom step type in teststand 4.2 and I can't put the pre-step substep before the post-step. I also know that TestStand are not executing them correctly since my pre-step create an object and the two post-step uses this object to set informations.
Please look at the picture below

Hi Crusader,
Though the Pre-Step is being listed after the Post-Step substeps in your image, it will execute before them because of its very nature as a Pre-Step. As per the TestStand Reference Manual, the Pre-Step substep will execute immediately before the module, and the Post-Step substep will execute immediately after the module.
The Move Up and Move Down buttons on the dialog are meant to function only when you have multiple substeps of the same type, in which case order of operation becomes important. For example, if you were to highlight one of your Post-Step substeps, these buttons would make themselves available.
Derrick S.
Product Manager
NI DIAdem
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

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

Error when editing IVI Scope Step in TestStand 3.1

When I open the edit box for an IVI Scope Step in TestStand 3.1 I get the following error: Method '~' of object '~' failed (-2147417851). I get the same error again when I click on the Logical Name dropdown box in the edit window. I have an IVI logical name of 'TekScope' in MAX that was created when I installed the IVI drivers for a Tektronix DPO7000.
Software Installed: TestStand 3.1, NIMax 4.3, NI IVI Compliance Package 3.2, Windows XP Pro. SP2
It seems that TestStand is unable to communicate with MAX. I don't think it is a version compatibility problem because I had the same problem when using MAX 3.1.1.

Nick,
Thanks for the reply. This problem went away when I opened the IVI example sequence that is installed along with TestStand. It has not repeated since. I can now access my defined 'TekScope'.
I am having a problem getting the IVI code to run in simulation mode. I modified the TestStand 3.1\Examples\IVI\IviStepTypes.seq file to change the Fileglobals.ScopeLogicalName value to TekScope which is the scope name in the dropdown box for edit IVI tools. I then selected the scope steps and selected Run Selected Steps. I get the following error:
An exception occurred calling 'RunStep' in 'ISubstep' of 'TestStand Ivi Step Types'
An error occurred while executing the step.
IVI Error: The IVI instrument failed to initialize for logical name 'TekScope'.
Details: TekScope_InitWithOptions returned an error: -1074134964 (0xbffa004c). The option string parameter contains an entry with an unknown option value.
Source: TSIviStepTypes
-1074134964; User-defined error code.
In MAX the TekScope.DriverSession - Simulate With setting is nisScope, Driver Setup is blank.

Error from IVI switch step in Teststand

We have the following issue when using Teststand. A reboot sometimes clears the problem, but other times it requires many reboots.
When starting our test sequence, we undertake a Disconnect All using the IVI Step type to ensure the switches are all disconnected.
We then get the following message:
An error occurred while executing the step. Unexpected Error: Switch Executive failed to initialize for virtual device 'Joyswitch'
Details: Joyswitch_init returned an error -1074118644 (0x%3)
Source: TSIviStepType
Any help would be gratefully appreciated
I have attatched the actual run-time error.
Attachments:
Switch_Exec_error.jpg ‏122 KB

The suggestion to try the validate option under MAX for Switch Executive would be a good idea. The error that you are seeing appears to be coming back from the IVI driver.
Question that come to mind are:
- You say that the Disconnect All fails, but does a Connect work?
- What hardware and IVI driver is the Joyswitch using?
- It appears that you are using TestStand 3.0, but what version of the Switch Executive are you using?
Scott Richardson (NI)
Scott Richardson
National Instruments

Latest IVI Class Step Types in TestStand

Similar Messages

Maybe you are looking for