IVI specific drivers usage in Teststand

Hi,
I am using Teststand 2.0.1 and i want to use some of the IVI specific drivers in my application. Can somebody guide me how to do that. Another clarification, if we use the IVI drivers which fall into any of the classes how do we achieve the interchangeability? Is it only through MAX that we achieve it.
Regards,
Siddu

Siddu 140,
I am not one of our TestStand supporters so I may not understand your core question exactly...but I'll give it a shot! We can keep track of our IVI drivers and IVI sessions in MAX as Aaron alluded to. You will have an IVI Drivers tab in your Configuration window in MAX where you can perform a variety of actions. From what I understand, once you have correctly configured your IVI Driver in MAX you can see it in TestStand. I have attached a ZIP file containing a text file of instructions and screenshots pertaining to the instructions that discuss how one configures IVI Drivers in MAX. Also the help window on the right-hand side of MAX when you select the IVI Drivers tab is a great resource (see also: National Instruments' IVI for more information).
With regards to the CAN driver there really isn't the concept of a CAN IVI driver. National Instruments provides a CAN driver for our CAN product line. More information on National Instruments CAN products can be found here: National Instruments' CAN.
I hope this information helps out and if you have any other questions please post back!
Craig H.
Attachments:
IVI Screenshots.zip ‏627 KB

Similar Messages

Delploying IVI-specific drivers

Whats the requirements for an IVI-specific driver to be listed in the Teststand-4.2.1 deployment tools Drivers and components list ? According to the windows software tool I've installed 6 IVI-specific drivers ( see picture)
but only 3 of them are listed in the deployment tool:

Markus,
you can only select drivers and components which are created by NI. Therefore, i assume the following things:
- You downloaded instruments drivers from ni.com. Even if you downloaded it there, the driver itself might not be created by NI.
- Since not all instrument drivers are from NI, they will not appaer as "NI component" in the deployment utility.
- If you would check the entry "NI Software" in the OS, the given three instrument drivers are also listed there, the other (missing) three are not.
I am not aware that you can change anything on this. If you want to distribute one of the other three instrument drivers not listed in the deployment utility, you will have to use "Custom Commands" to 'trigger off' installation of your drivers you supplied with the installer. To achieve this, add the installation package of the driver to the deployment kit and copy it to the target location using the installer settings. You can configure custom commands to launch the installers of the drivers.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

NI IVI Soft front panel compatibility with IVI-COM drivers

Does IVI soft front panels support IVI-COM instruments drivers ?
For example, I would like to use IVI-COM driver for Tektronix TDS5000 with TestStand...
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)

The IVI soft front panels that ship with the NI IVI Driver Toolset do not support calling IVI-COM drivers. The soft front panels support IVI-C drivers. On Instrument Driver Network there are IVI-C drivers for other Tektronix scopes.

Agilent's IVI-COM Drivers

Can TestStand call Agilent's IVI-COM Drivers and how to configurate them with NI MAX?
"Only a life lived in the service to others is worth living..." - Albert Einstein

Estonia,
At the very least, Agilent probably provides a dll interface to calling their driver. You could call those dll functions from TestStand using the C/C++ DLL adapter (or the Flexible DLL Adapter if you are using TestStand 2.0.1 or below). If they provide an ActiveX or COM interface (which sounds highly likely considering the name of IVI-COM) then you can use the TestStand ActiveX/COM adapter to call into these drivers.
NI MAX is the NI Measurement and Automation explorer. Because these drivers are not National Instrument's drivers there will not be an interface for them to be used within NI MAX.
Let us know if you have any other questions.
Regards,
Shannon R.
Applications Engineer
National Instruments

Installer with specific drivers

Hello to everyone,
I'm trying to build a installer for a measurement program I just wrote, wich only contians specific drivers for my hardware and LabVIEW runtime.
My goal is to find a solution without installing the whole NI-DAQmx 9.6. The solution should be as small as possible and not about 1,3GB plus the space for runtime. Is there generally a solution?
Does anybody has got experiences with this?
Thanks a lot!

You can always add a kudo here: http://forums.ni.com/t5/LabVIEW-Idea-Exchange/LabVIEW-App-Builder-Should-Determine-and-Minimize-Dist...
Might help, might not.
Using LabVIEW: 7.1.1, 8.5.1 & 2013

How to use/call IVI-C drivers in Visual Studio 2012

Hello,
i downloaded some IVI-drivers and saw that they all contain IVI-COM and IVI-C drivers.
I am trying now to call the IVI-C drivers in my Visual Studio 2012 but i cannot find any examples how to do this.
Can someone provide a simply example project to demonstrate how this would be done?
At the end this should become also a DLL.
Thanks a lot for help
BR

Hello nyc,
thank you for the PDF link that describes how to do this in C# and VB.Net.
I also found a PDF on the same site that shows how to do it in C++.
But the example is only how to create a console application.
But i need to to create a DLL.
Thanks
BR

Mac-specific drivers and other software for Windows

Mac-specific drivers and other software for Windows how can I download them with out the install cd?

Or for the same price you can order a new Snow Leopard disk. http://store.apple.com/us/product/MC573Z/A?mco=MTY3ODQ5OTY
That would give you Boot Camp 3.0 drivers. With Snow Leopard and Boot Camp 3.0 you can install Windows XP, Vista or Windows 7. With Lion and Boot Camp 4.0 you can only install Windows 7. If you install Lion with Boot Camp 3 and XP or Vista already on it it will work.

I am using the NI application note "Calling IVI-COM drivers from LabVIEW" I created an Automation Open and an Invoke Node, after wiring

the 2, the AN asked to right click the Invoke Node(this is step9) and choose initialize. However there is no intialize option on the pop up menu. Anything am I doing wrong? I am using Labview6 and I did add the "enableCustomInterface=True" in the INI-fileThank you for your help.
T Tall

the 2, the AN asked to right click the Invoke Node(this is step9) and choose initialize. However there is no intialize option on the pop up menu. Anything am I doing wrong? I am using Labview6 and I did add the "enableCustomInterface=True" in the INI-fileT Tall,
What's the number of the application note "Calling IVI-COM drivers from LabVIEW"? I'm unable to find what you're looking at.
Thanks,
--Bankim

How to load programmatically from CVI the specific sequence file in TestStand 3.1

I am trying to implement TestStand from Windows/CVI 3.1. I need to insert a specific sequence file in TestStand, with all other sequences unloaded. I used TSUI_ApplicationMgrCloseAllSequenceFiles() and TSUI_ApplicationMgrOpenSequenceFile(), but after Username/Password prompt, the TestStand loaded all the old sequences. How to eliminate this?

Hello,
I created a function that calls those two methods. When I made a simple CVI button and in a callback for it, I call my function, it does successfully close all open sequencefiles and then load the one I specified; however, it does not work when I call the function just before the call to RunUserInterface! I am very surprised by this and will be bringing it up with our R&D department. There is a simple work-around. Instead of closing all open sequencefiles at the beginning of the OI, close them at the end instead. I have modified the full-featured OI for you and tagged in the code where I made changes. This should do exactly what you want (you may want to change the code around to make it a little cleaner...I left more in code in than I needed for instructive purposes). Please let me know if you have any questions about this. Take care!
Regards,
Aaron B.
National Instruments
Attachments:
TestExec.c ‏55 KB

IviSwtch Compliance Test IVI Specific Driver in CVI crashing

I have problem with IviSwtch Specific driver. I have finished all code for this driver and try to test in CVI tool called "Test IVI Specific Driver". Structure and Function panel test runs without any error. Problem is with Compliance test which returns:
the driver could not be initialized through the class driver.
Compliance Test was halted.
Error returned: bffa0011
Error Message: Function or method not supported.
I tried to add exports to dll in according to this solution http://digital.ni.com/public.nsf/allkb/1DCA138862E75119862576C5006EA144
After doing this Compliance test just crashing and I have to close it down.
Does anybody met this kind of problem? I would be grateful for any help.
Regards
Tomasz
Solved!
Go to Solution.

>>The DLL version format is valid.
ERROR: The DLL version is inconsistent with the version in the header file.
All attributes have correct names.
All attributes have correct data types.
This error means the revision of the generated <driver_prefix>.dll does not match the Major and Minor version defined in header. This should not be a conern if you will not release the driver to customers and you take care of revision.
>>ERROR: The driver is not c>ompliant with the Inherent group because:
-The following Inherent attributes are not implemented:
INSTRUMENT_MANUFACTURER
INSTRUMENT_MODEL
It is hard to tell the root reason of this issue, but there might be something doesn't work in your code. How about post these attributions' definition? OR send your project to [email protected] I think NI could help to take a look into it.
Thanks,
Charles

DM -Specific functionalities /Usage of Dependent & Independent validations

Hi Experts ,
Please explain in detail about the Specific functionalities /Usage of Dependent & Independent validation of MR results .
Thanks ,
Harry.

Hello Harry,
You can find some detailed information on this topic at the following:
http://help.sap.com/saphelp_utilities472/helpdata/en/9f/03693582f4db60e10000009b38f889/frameset.htm
http://help.sap.com/saphelp_utilities472/helpdata/en/9f/03693582f4db60e10000009b38f889/frameset.htm
Kind Regards
Olivia

Calling IVI/Visa drivers from TestStand

I want to call directly to IVI or Visa driver DLLs using the DLL Flexible Prototype Adapter (because not every instrument in the world is a power-supply, dmm, scope, function-generator or switch). So far, straightforward. But when an error happens, I want it to automatically call the XXXX_error_message() function, to set the Step.Result.Error.Msg string.
The Flexible Prototype Adapter won't do that by itself. I was thinking of adding that functionality to it (making what I would call an "IVI/Visa Driver Adapter"), but I can't find the source code for the adapter. Is it not included with TestStand? I've been amazed by how much source code is included, maybe I'm just missing this one. Is it even possible to write user-defined
step adapters?
- Ron

I had a brainwave, a fairly elegant solution to my problem that doesn't involve modifying the DLL Flexible Prototype Adapter.
I knew Post Expressions wouldn't cut it, but it just occurred to me to use a Post substep. It works well. So, now I just need to create a custom step type for each instrument driver I'll use, and add a Post substep that calls a bit of code like this:
void __declspec(dllexport) TX_TEST Handle_age1962_error(ViStatus error_code, char error_message[] )
if( error_code != 0 ) {
age1962_error_message( VI_NULL, error_code, error_message );
Just make the Post substep call that using the DLL Flexible Prototype Adapter:
Handle_age1962_error( Step.Result.Error.Code, Step.Result.Error.Msg )
Now the run-time
errors returned by the age1962 driver will have nice human-readable message strings associated with them. And it's a whole lot easier than writing a wrapper and step-type for every single instrument function.
- Ron

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

Why can't I deploy the NI-DAQmx 8.5 drivers with a Teststand installer?

When I include the NIDAQmx 8.5 drivers with the deployment, it automatically checks off that I have to include Labview 7.1 runtime, which causes them to prompt me for the November 2005 driver CD. I insert this CD and get the errors saying that the Windows SDK function could not find the specified file (error code 12) and that the specified files are not found. The build is then quickly aborted and I'm left with seemingly no options. I need to include the DAQmx drivers with the build but I can't see how to without the LV 7.1 runtime.
I am running Teststand 4.0 and Labview 8.2.1
Thanks very much in advance.
-Matt

Thank you very much for your response.
I have tried your suggestions, but I believe the problem is not specifically the DAQmx 8.5 drivers. It seems to have to do with the fact that when I select the drivers to be included in the deployment, Labveiw 7.1.1 runtime engine is checked off and grayed out, because it says it is required by the DAQmx 8.5 drivers. Please see the attached screenshot for detailed information.
Your suggestion about downloading the runtime engines seemed like a viable solution, but unfortunately there are many versions but not the one I need. The only 7.1.1 version available says it's for Mac OS, and I'm running Windows XP. Again, I have the actual CD it's asking for (Driver CD from November 2005) but it doesn't seem to satisfy the deployment.
Any further suggestions would be greatly appreciated. This is something I will need now and going forward in the future with Labview/Teststand deployments for my company since we rely heavily on the DAQmx drivers.
Thank you very much.
-Matt
Attachments:
Deployment Screenshot.PNG ‏73 KB

IVI-C vs. IVI-COM Drivers

I have recently downloaded an IVI-C Instrument specific driver from NI's website. For my application, I need a COM layer to communicate with other software that I am developing. If the driver that I had found would have been an IVI-COM driver, all of my problems would have been solved. However, this not being the case, I need some direction. Would it be easier to take the IVI-C driver and create a wrapper on top of it that would be a COM layer? Or should I attempt to rewrite the driver as an IVI-COM driver. Keeping in mind that I have very little experience developing drivers, my first inclination is to use the driver as is, and create another layer. However, if someone has any more knowledge that they could add to this, please d
o so. There must be an easy way to accomplish this, and it must have been done before. Any help is greatly appreciated.
Attachments:
tkawg5x0.c ‏249 KB

Actually, I did some more research and it turns out that the IVI foundation does have a COM spec. However creating an IVI-COM driver is not a trival ask as I had mentioned before so I stand by what I said regarding creating a wrapper.
I wanted to point out that National Instruments offers IVI ActiveX controls to provide a more Visual Basic-friendly programming interface than using standard instrument driver DLLs.
These IVI ActiveX controls as well as VC++ wrappers for IVI classes come with Measurement Studio Full Development System (FDS). For more info, go to:
http://www.ni.com/mstudio

IVI specific drivers usage in Teststand

Similar Messages

Maybe you are looking for