Problems in using IVI instrument drivers

Hi all,
I have created seperate IVI instrument vi's for each functionality e.g. PSUinit.vi for initialization, PSUsetVoltage.vi for setting the voltage in power supply etc. But whenever i try to run these vis using a IVI logical name "PSU", they dont work and I endup getting errors like "PSU(1)" logical name not found.."PSU(2)"logical name not found etc.
Any suggestions on where am I making a mistake?

And how should I connect logical name?..should I use method 1 or method 2?..I guess I am getting problems due to this coz I havent actually closed the logical name instance in each vi..But I am not sure about it.
Also in plug & play drivers it doesnt matter which method (1 or 2) one follows and whether one has closed the instance or not. They still work but I think the same case is not valid for IVI.Is it true?
P.S Please find the attached image for method 1 & 2
Attachments:
ivi2.png ‏8 KB

Similar Messages

Problems in using Ivi driver ke230y in "IviDCPwr Measure [MSR].vi"

Hello all,
I have a problem in using IVI driver (ke230y) to control keithley2303 powersupply with LABVIEW 2013.
After I initialize and config ke2303 well and run to "IviDCPwr Measure [MSR].vi", it ocurrs errors. While lasting about 15 seconds and then reports errors as attached:
The code (attached) when I test with other powersupplies such as agilent66309d and keithley2306(with ivi driver ke230x), it runs well.
So I've no idear about this problem with keithley2303 powersupply, can you guys ever meet this problem and may reply for me to fix it.
thank you for your reading and help!
best wishes,
Phil
Solved!
Go to Solution.
Attachments:
error.jpg ‏36 KB
code.jpg ‏43 KB

I don't have the any driver's source code (such as ividcpwr.dll source code), how can I modify the specific driver through labwindows.
Follow your advice I use I/O trace to get trace as follows:
1 IviDCPwr_InitWithOptions ("ke2303", VI_FALSE, VI_TRUE, "", 0x0C913064) VI_SUCCESS 14:45:10.675
2 IviDCPwr_ConfigureVoltageLevel (ke2303, "CHANNEL1", 3.8) VI_SUCCESS 14:45:11.405
3 IviDCPwr_ConfigureCurrentLimit (ke2303, "CHANNEL1", 0, 3) VI_SUCCESS 14:45:12.104
4 IviDCPwr_ConfigureOutputEnabled (ke2303, "CHANNEL1", VI_TRUE) VI_SUCCESS 14:45:12.824
5 IviDCPwr_Measure (ke2303, "CHANNEL1", 1, 0) VI_ERROR_TMO 14:45:16.207
6 IviDCPwr_GetError (ke2303, -1073807339, 0, "") 0x00000037 14:45:32.991
7 IviDCPwr_GetError (ke2303, -1073807339, 55, "Primary Error: ..................") VI_SUCCESS 14:45:32.991
8 IviDCPwr_close (ke2303) VI_SUCCESS 14:45:33.847
I cannot see any GPIB command in the trace but some IviDCPwr functions.
Besides, if I know any bug (eg. some wrong GPIB command) in ividcpwr.dll, how can I modify it before I get it's source code.
Pls teach me anytime in your conveneince.
thanks!

Any Problem with Enumerations in Instruments Drivers

I noticed in the National Instruments driver standard guidelines whenever the mention of a control that would have different test-based options came up, a ring selector was recommended and not an enumeration... Is there any good reason to stick with ring selectors and not use enum?? For example, one of my drivers has 4 different channels CH1, CH2, CH3, CH4... An enumeration will work out nicely here because I can use format to value from a text based config file and will create the proper enumeration value that I want.
"CH1" (text) --> format to value --> CH1 (enum value)
Thanks for your help
Solved!
Go to Solution.

Are you referring to this document: http://zone.ni.com/devzone/cda/tut/p/id/3271 ? There's no explicit mention in there about not using an enumeration. I think the main point is to use some for of menu control to facilitate the selection of the function. In some cases a ring may be more convenient than an enum. For example, if a selection requires the actual value to be something other than the normal value of the control. Example, having the selection of "DC" would require sending a value of 101 to the instrument instead of 0. In this case a ring would be more convenient since you can set non-sequential values for the ring items.

Agilent 34980A simulation using IVI-drivers in Teststand?

Hello! I am unable to simulate 34980A in TestStand and here are some results based on testing:
Agilent 34980A is linked to logical name SampleDmm. Simulate With: Specific Driver.
IviStepTypes.seq used with only DMM and Switch steps.
Using IviDMM IVI-C causes runtime-error in Ivi DMM Configure Single Point: Component Works IVI Control Error: The IVI Configure operation failed for logical name 'SampleDmm'. Details: Extension capability not supported by instrument driver. (Base)
Using IviDMM IVI-COM causes runtime-error in Ivi DMM Read Single Point: Component Works IVI Control Error: The IVI Read operation failed for logical name 'SampleDmm'. Details: Attribute ID not recognized. [IVI Error Code: BFFA000C] Source: TSIviStepTypes
Skipping Ivi DMM SFP -step removes that error but next one waits in Ivi DMM Configure Multi Point: Component Works IVI Control Error: The IVI Configure operation failed for logical name 'SampleDmm'. Details: Attribute or property not supported. [IVI Error Code: BFFA0012] Source: TSIviStepTypes
Skipping multi point steps helps until Ivi Switch Connect where another error hits: Component Works IVI Control Error: The Connect operation failed for logical name 'SampleDmm'. Details: No path was found between the two channels. [IVI Error Code: BFFA2011] Source: TSIviStepTypes
I find some similarities in forum post that involves HP 34401A and IVI .
According to IVI-C Class Driver Support for IVI-COM Specific Drivers the fault might be in 64 bit system (the note in the end). Is this the case? I can't use IVI-COM-drivers in 64bit system?
Example's default DMM Hewlett-Packard 34401A Digital Multimeter simulation works perfectly in unmodified example(it has IVI-C). It even shows simulated numbers in the SFP which is zero all the time with Agilent.
Has anyone succeeded to simulate 34980A properly in TestStand? Any knowledge about how to solve this thing? Any help is welcome. Thank you.
Setup:
-Teststand 5.1
-Windows 7 64bit
-IVI shared components 2.2.1
-Visa shared components 1.5 64bit
-Agilent IO libraries suite 16.3 Update 1
-Agilent 34980A IVI Driver 1.5.3
-MAX/Agilent 34980A published APIs:
-IviDmm 4.1 IVI-COM (IVI-C tried with less success)
-IviSwtch 4.0 IVI-C & IVI-COM

Some IVI drivers are designed to work in simulation mode, that is, the virtual instrument can be defined in MAX but no physical instrument is necessary to use the "instrument". If you turn off the simulate checkbox on the validate dialog box, TestStand will create the instrument session without simulation and the driver will attempt to talk to a physical instrument. If no physical instrument definition is available or if the address defined for that virtual instrument is incorrect, the above error can occur.
Scott Richardson (NI)
Scott Richardson
National Instruments

Problems at using Aglient 54624A

Dear all,
Are there any vi llb for "Aglient 54624A" which can use RS-232?
i ve' download the instrument driver from Instrument Driver Network, but it's seems can work in RS-232(since the driver haven't told that it can work in RS-232?)
p.s. I've download some examples from Aglient's official website, but it seems can't find the sub-vi s can anybody tell me why?
here is one of the example attach.
Attachments:
example1.vi ‏296 KB

Hi,
Those subVIs that are missing are the instrument drivers for Agilent 54624A. I tried downloading the GPIB instrument drivers and it didn't work. It seems like the program you downloaded from Agilent is referring to ag5462xx Initialize.vi and so forth. Whereas, the IVI instrument drivers are named ag5462x Initialize.vi and so forth. You will have to check with Agilent (where you got the example from), and see if they have any RS-232 based instrument drivers. If not, you can try using the regular GPIB based IVI drivers. You'll have to change your code a little bit to accomodate this.
A.S.
Anu Saha
Academic Product Marketing Engineer
National Instruments

Error -1073807339 when using IVI (setup in MAX) to initialize instrument

I'm using LabVIEW 2014 and the most recent version of the Measurement & Automation Expert (MAX) to communicate with an Agilent 33500B series function generator with IVI drivers on a Windows 8.1 computer. (I also see this problem when trying to communicate with an Agilent oscilloscope). I've used the MAX to create an IVI logical name and tied the name to the appropriate driver session following the instructions in: http://www.ni.com/white-paper/4594/en/. In LabVIEW, I have created the IVI instrument, tied it to the appropriate logical name, initialize the instrument, and then close the session. When I run this program, the Initialization block runs (resetting the parameters on the function generator) AND THEN I get the following error:
"Error -1073807339 occurred at IviFgen Initialize With Options.vi
Possible reason(s):
Primary Error: (HEX 0xBFFF0015) TImeout expired before operation completed.
Complete call chain:
IviFgen Initialize With Options.vi
IviFgen Initialize.vi
<myfilename>.vi
I read in the documentation that I should not simultaneously initialize with options in LabVIEW and in MAX, so I am using the Initialize block which still calls Initialize With Options. The same error occurs when I:
1. Uncheck all the options in MAX and run the code
2. Uncheck all the options in MAX and replace the LabVIEW Initialize block with Initialize With Options and run the code
3. Add a Wait block between the initialization and the close blocks and run the code.
However, I am able to communicate with the function generator when I use the VISA Test Panel (opened in the MAX) and send it a VISA command. I am also able to communicate with the function generator if I use the VISA I/O blocks instead of the IVI blocks in LabVIEW.
Is it really a timeout issue? If so, how do I change the timing? If not, what is going on?
Thanks.

sagha wrote:
According to the MAX they are correct (IVI driver for the Agilent 33519B downloaded from the NI website). When I run the IVI Initialize block any frequency, amplitude, offset, etc. settings on the function generator are reset to the default values. So, something is being sent to the instrument.
However, I've also tried adding the General Error Handler block right after the Initializaiton block to cancel the -1073807339 error. Then, I add the IviFgen Configure Standard Waveform [STD] block to set the function generator frequency. The program throws an error that looks like a resource problem:
"Error -1074130544 occurred at IviFgen IVI Error Converter.vi
Possible reason(s):
The session handle is not valid.
Complete call chain:
IviFgen IVI Error Converter.vi
IviFgen Configure Standard Waveform [STD].vi
<myViName.vi>
What could be the reason for an invalid session handle? I've followed the NI tutorials on setting up IVI instruments in MAX and in LabVIEW.
Okay, this is new information. Nothing in your previous posts mention that the initialztion did anything at all besides return the timeout error. The invalid session handle is because you closed the session.
I'm having trouble following your descriptions.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Using IVI drivers in LabView 5.1.1

Hi,
We have a set of IVI drivers ( class specific and custom specific ) developed in LabWindows/CVI 7 and IVI Compliance package 2.2 version. We want to use these drivers in a new application in LabView 5.1.1 version. I want to use the class specific drivers through the IVI class drivers in LabView 5.1.1 so as to cater for the interchangeability aspect configuring the logical names in MAX. Finally I would be creating an Installer with executable and distributing it.
I want to clarify few issues.
1. Please let me know whether I need to install any other software's apart from NI DAQ, IVI compliance package 2.2 and the Installer in the User PC. Does the IVI engine, Tool set, Class drivers for LabView 5.1.1 come with the compliance package?
2. Does MAX 2.1 support IVI drivers, interchangeability through class drivers and compliance package 2.2 or should I use MAX 3.0 for best results?
3. When I import a IVI driver (developed using IVI compliance package 2.2) to LabView 5.1.1 and try to use the functions there are some problems in the functions. As per the IVI specifications 3.2, functions GetErrorInfo and ClearErroInfo are changed to GetError and ClearError. But it shows error in the functions at those points and we have to go to IVI Error Converter.vi and change the configuration of the library node and direct it to the GetError function. Do we have an alternative to avoid this process?
It would be of great help if somebody can clear these issues.
Thanks & Regards,
Siddu

1. The IVI Compliance Package (ICP) 2.2 installs the IVI Engine and Class Driver support for LabVIEW 7.0 and 7.1. It does not install Class Drivers for LabVIEW 5.1.
2. ICP 2.2 requires MAX 3.0 to get the IVI interchangeability provider in MAX.
3. LabVIEW 5.1 was released before the official IVI specifications 3.2 were approved. Prior to 3.2, the function names were GetErrorInfo and ClearErrorInfo. Those changed to GetError and ClearError. The LabVIEW wrapper generation tool that shipped with LabVIEW 5.1 is not aware of these changes. Therefore, my suggestion is to upgrade to a later version of LabVIEW so that you will have support for the current IVI specifications and class drivers.

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

I contiue to get the error message registry settings used by itunes drivers for importing and burning CD's and DVD's are missing. Please reinstall itunes. Reinstalling itunes does not fix the problems

I continue to get the error message registry settings used by itunes drivers for importing and burning CD's and DVD's are missing. Please reinstall itunes. Reinstalling itunes does not fix the problems

I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
iTunes for Windows: "Registry settings" warning when opening iTunes

How to include Instrument drivers in Lab-view apps builder

Hi,
I am using Labvier 7,1, I have managed to use the Application builder for a simple program, but have problems with a larger program that includes P & P instrument drivers (for GPIB)
I can create an installer, but when I try & install it, I get a great number of errors, all relating to being unable to find all the vi for the Instrument driver functions.
I tried several variations, including support files, & including the instrument driver dll's from C:\vxipnp\winnt\bin\
this time I got app f.ailed to start , needs VISA32. dll was not found.
I had expected there to be a standard way of using applications Builder to include GPIB p & P Instrument drivers, guess I'm nieve, being a newbe. Any help will be greatly appreciated
Mikesub

The app builder prior to 8.x was only designed to install the application you created. The actual instrument driver VIs should be included in the app but the IVI driver itself (the low level dll) is not. You should really include the installer for the IVI driver and not just the dlls. This is the .msi file that is on the instrument driver download page. If you are getting an error about VISA32, then it sounds like VISA was not installed either. I usually install VISA and NI-GPIB from the CD that comes with the GPIB board and I do this when I install the board into the computer. However, you can also include these installers with your app as well. On the Installer Settings tab, click the Advanced button. You have the option there of 'Run executable after installation'. The simplest thing to do is to create a .bat file that will call the other installers you include with the distribution. Don't forget that you also need the IVI Compliance Package so include that installer as well.

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

How to use IVI Driver in Labwindows

I want to use IVI drivers in LabWindows/CVI, but I don't know how! I know that it necessary to load the class driver. But how can I include the specific driver??? It is possible to add functions into a class driver? And what I have to do when the instrument should change?
Thanks for your help!!!

Hi Chris,
If your goal is to create an interchangeable application, you do have to use a class driver. National Instruments provides Measurement and Automation Explorer (MAX), a Graphical User Interface for configuring IVI. MAX is usually installed with one of NI's Application Development Environments such as LabVIEW or Measurement Studio, or with one of NI's hardware product drivers such as NI-488.2 or NI-DAQ.
The IVI configuration utility allows you to interchange instruments without recompiling or relinking your application source code by configuring logical names. The user defines which specific instrument he wants to associate with a logical name and IVI takes care of the rest. If at a later time, the user decides to swap the instrument and use a diff
erent one, all he has to do is change the entry in the configuration utility so the logical name points to a different specific instrument driver (driver session).
So, the important point is that you have to have both, IVI class and specific driver installed on your system, and then you need to configure them in MAX. MAX 3.0 now has a built-in help to guide you through the configuration process. In the case that you still do not have MAX 3.0, you can find an application note about the IVI configuration in MAX 2.x on NI's Developer Zone: http://zone.ni.com/devzone/devzone.nsf/webproducts/E2947DB2FF0DD9FE862569FD006EB939?opendocument.
As for the adding functions into the class driver, the answer is no, that is not possible. You can certainly use the specific driver functions in the application which is written using the class driver functions but then your application will not be completely interchangeable in the future. However, this way you will just isolate a small portion of y
our code that you will need to change later on when you decide to change the instrument.
I hope this makes sense.
Regards,
Vesna Jadric
Instrument Drivers/IVI

Best way to distribute LabVIEW Instruments Drivers.

Hello,
I'm trying to stick to the standards described just there:
Developing LabVIEW Plug and Play Instrument Drivers
Instrument Driver Development Tools and Resources
Instrument Driver Guidelines
However, I cannot see clearly what is the best way to distribute the LabVIEW Instruments Drivers, except that I need to be compliant with those standards to be on the IDNET (Instrument Drivers Network).
Here is a couple of questions I'm not really sure about their answers:
Is it okay to use a .NET dll and to make some calls?
Is it fine to hide the Block Diagram? With passwords in the Drivers
Can we put prevent the modification
In my situation several devices (or let's say modules can controlled through one communication medium), so basically I might have one instrument drivers for several things.,,
May I use some OOD? In order to control the equipment with methods and set some properties and encapsulate the communication stuff in classes, some equipments could be consider are inherited from others (more recent for instance), or this is totally prohibited by the guidelines above?
What is the most suitable Specification Build type: Packet Library or other? If packed library, how to handle the early version created issue when opening the lib with newer version of LabVIEW then?
How to deal with the copyright thing, do I need to copy and paste the copyright on both the Front Panel and on the Block Diagram?
Is this copyright enough: "Copyright (c) <Company Name>. All rights reserved"?
Solved!
Go to Solution.

Ehouarn wrote:
Hello,
I'm trying to stick to the standards described just there:
Developing LabVIEW Plug and Play Instrument Drivers
Instrument Driver Development Tools and Resources
Instrument Driver Guidelines
However, I cannot see clearly what is the best way to distribute the LabVIEW Instruments Drivers, except that I need to be compliant with those standards to be on the IDNET (Instrument Drivers Network).
Here is a couple of questions I'm not really sure about their answers:
Is it okay to use a .NET dll and to make some calls?
Is it fine to hide the Block Diagram? With passwords in the Drivers
Can we put prevent the modification
In my situation several devices (or let's say modules can controlled through one communication medium), so basically I might have one instrument drivers for several things.,,
May I use some OOD? In order to control the equipment with methods and set some properties and encapsulate the communication stuff in classes, some equipments could be consider are inherited from others (more recent for instance), or this is totally prohibited by the guidelines above?
What is the most suitable Specification Build type: Packet Library or other? If packed library, how to handle the early version created issue when opening the lib with newer version of LabVIEW then?
How to deal with the copyright thing, do I need to copy and paste the copyright on both the Front Panel and on the Block Diagram?
Is this copyright enough: "Copyright (c) <Company Name>. All rights reserved"?
Not sure about 1) but 2) and 3) are definitely a no go if you want your library to be distributable through the ID network. The standard only allows for DLLs in that are really developed in C but would require you to also distribute the C code as far as I understand.
OOP may not be a problem.
Packed Library is definitely not something you want to do. They only work in the LabVIEW version in which they were created. You will hate the moment you decided to go with packed libraries as requests come in for other LabVIEW versions and your drivers are bashed on all discussion forums as being a pain in the ass to use.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Who can help me using IVI powersupply in Teststand!

Hi there,
I'm newly in working with Teststand and IVI drivers and
have a little simple question.
I have a step to configure the powersupply.
The logical name is "SamplePowerSupply", the operation
is "configure". If I change to the "Validate IVI Configuration" form, uncheck the simulate checkbox
and press the button "Init" I get the following errormessage:
....returned an error: -1073807343 ... Insufficient location information or the requested device or resource is not present in the system (-31619).
But in MAX I see my powersupply and it seems to work correct.
Thanks for any answer !!
Mr.Pe

Some IVI drivers are designed to work in simulation mode, that is, the virtual instrument can be defined in MAX but no physical instrument is necessary to use the "instrument". If you turn off the simulate checkbox on the validate dialog box, TestStand will create the instrument session without simulation and the driver will attempt to talk to a physical instrument. If no physical instrument definition is available or if the address defined for that virtual instrument is incorrect, the above error can occur.
Scott Richardson (NI)
Scott Richardson
National Instruments

Problems in using IVI instrument drivers

Similar Messages

Maybe you are looking for