Hello Siddu,
The functionality of the IVI step types are meant merely to simplify coding. Page C-2 of the TestStand Manual states that:
"IVI step types complement, but do not replace, the instrument
configuration and measurement operations you perform in code modules
that you write using LabVIEW, Measurement Studio, Microsoft Visual
Basic, or other tools. Although IVI step types are the easiest way to
configure and acquire data from IVI class instruments, you must use code
modules to control instruments under the following circumstances:
- When you need to precisely specify the instrument driver calls to
ensure optimal performance.
- When you need to call specific driver functions that an IVI class does
not support.
- When your instrument does not conform to an IVI class or does not
have an IVI driver.
- When you need to interleave your instrument control operations with
other code that must reside in a single code module."
The DLL adapter is certainly not the only way to work with Custom drivers. You should be able to access your instrument from any whichever type of code module you are developing in (ie: LabVIEW, CVI, C++, C# or VB.NET, etc). If your custom driver falls into the category of one of the standard drivers, you can still use the built in step types, but otherwise, you will have to write the code in your Application Development Environment (ADE) of choice and call it from TestStand. Sorry for the mix-up and not addressing this specific question sooner.
Regards,
Aaron B.
National Instruments