IVI driver session In MAX

Hello,
I am confused with IVI drivers. I have two IVI drivers for the same instrument( one of them is newer). When I install the older one, I can see a driver session under drivers session category in MAX but when I install the new one, I do not have drivers session for the instrument in MAX. what is the problem?
Thanks,
Ela

HI,
That is Dc850W IVI-C driver. I got it from the vendor site
http://www.programmablepower.com/products/XTR/XTR_Downloads.htm
That is power supply, the older version is available in idnet, but it has some problems as well, but at least it works somehow!
Thanks,
Ela

Similar Messages

Resource Name, IVI Logical Name, Driver session on MAX

Inside MAX, we can set Device Name, Logical Names, and Driver Sessions. Can I setup those on LabWindows or LabView? or you have C# wrapper to do this?

Hi Gary,
Unfortunately there is no function in LabVIEW that does any IVI setup. All of the configurations for your driver sessions and logical names need to be set in MAX, and saved. So while you can change the driver session a logical name uses, you can only do this through MAX.
Kind regards,
Sheela Sujeeun
Applications Engineer
National Instruments UK

Can multiple Virtual Devices use the same IVI Driver Sessions?

I am using Switch Executive 2.0 and I'm having problems creating multiple Virtual Devices.
I have created a virtual device on a development computer that has no hardware connected to it. This virtual device uses specific drivers to simulate the devices. The problem I'm having is that when I create a second virtual device and try to add the same IVI Switches as the first Virtual device, I'm getting the following error:
An error has occurred while attempting to access the device deviceA_ivi.
Error -223116 occurred:
Internal Software error occurred in Switches software. Please contact National Instruments Support.
File name: .\source\mxsWrappers\tMXSObject.cpp
Line Number 192:
Status Code: -223116
Can someone please explain why?

Can you please elaborate on how did you create those simulated devices? Namely, what does your IVI configuration look like? What does the driver session for the logical name look like? What's the software module? What's the hardware module? What is the driver setup string, and what is the simulation mode for the device in question?
-Serge
Srdan Zirojevic

Updating Virtual Names in NISE Driver Session

I have created a Driver Session in MAX for my VXI Chassis Slot 3 cards. In this Driver Session on the "Virtual Names" tab, I am entering some virtual names that will correspond to the names on our Interface panel -- i.e. the panel of pins that the outside world sees. In other words, the default virtual name M0CH1COM may become SW1_CH1_COM -- or whatever. I plan to go and create a Virtual Device after this, and when I load the IVI switches for this driver session into the Virtual Device, I will see my virtual names in the IVI Channel column instead of the default physical names.
Suppose I have a great number of these virtual names to enter for a particular driver session, and at this point I only want to enter half of the virtual names into the Driver Session. Once I am convinced that our system is stable, then I will enter the rest of the virtual names into the Driver Session. Is there any way in NISE to get the "last half" of the virtual names from the Driver Session into the Virtual Device that I have created already? I can see where I would have built hardwires, routes, route groups, etc. in the existing Virtual Device, but I'm not sure I know of a way to get the updated Driver Session info into the existing virtual device?
A simpler case of this would be if someone just forgot to enter a virtual name or two into a driver session. They might get further down the road in development, and find that they overlooked a few virtual names. Is there any way for them to go back, enter in those new virtual names, and have the Virtual Device recognize these virtual names?
When I tried to do this -- I could not find a way to get the new virtual names to be recognized by the existing Virtual Device. The only way I found to make it work was to create a new virtual device -- and doing this will cause me to lose my "custom" info in the virtual device.
Any ideas?
Harv

Harv,
I guess this question is related to your previous post.
When you enter virtual channel names in the driver session, the IVI specific driver is supposed to pass these names to NISE. If this is the case, then NISE will show the virtual channels and not the physical channel names. The virtual channel names need to be created before importing a switch in a NISE virtual device.
If you forgot to name a few channels in the driver session and already created a NISE virtual device you will not be able to go back and give virtual channel names to the remaining channels.
Let's assume that your new driver has the exact same topology, connections, channel number etc than the old driver but some channel names are different. CH0 is now name Channel0 and CH1 is now Channel1.
What you could do is export you configuration into an xml file, open the xml file with a text editor (notepad), search for the CH0 and CH1 and replace them with Channel0 and Channel1 respectively. You also need to point to the new IVI specific driver. Now, Create a new NISE virtual device by importing the changed xml file. When you open this new NISE virtual device, it should see that the channels names (Channel0 and Channel1) correspond to the names in the new ivi specific driver and you should not have a problem using it. You would not have to redo your entire configuration.
This will work if ONLY the channel names have changed. If anything else have changed this would not work and you would have to create a new NISE virtual device.

Configure IVI Logical Name to use different Driver Session programmatically

Hi,
Is it possible to change the Driver Session associated with an IVI Logical Name in Labview ?
thanks,
Gary.

Hi Gary,
Unfortunately there is no function in LabVIEW that does any IVI setup. All of the configurations for your driver sessions and logical names need to be set in MAX, and saved. So while you can change the driver session a logical name uses, you can only do this through MAX.
Kind regards,
Sheela Sujeeun
Applications Engineer
National Instruments UK

Retrieving mapping from IVI logical name to full driver session name.

MAX, of course, lets you set up "Driver Sessions" with full names, and then "logical names" which are shortcuts to the full driver session. How can I retrieve the actual driver session that the logical name maps to? I can get the handle to the logcal name list via the IVI library, but I can't find any function that lets me retrieve further information about the logical name. Is this available in the "Configuration Server C API"?

What I want is, as I said, the mapping between the logical name and the session. This must be available, since the IVI drivers use it to go from a logical name to the attached session! One would think that it would be a single function call.
I'm doing this because in my program I can select which of a number of drivers (Newport motion controllers, in this case) a particular GUI control is attached to. The full session name is long, and there are - of course - sessions that have nothing to do with motion controllers. In the control list (a ring control) I use the logical names, which are shorter. However I want to also list the full session name elsewhere. Since I can't go from the session name to the logical name, that mapping isn't stored anywhere, I must go the other way around.
Ok, I think I figured it out. This could really be documented better!
Also, this whole thing could really be in the .ivi library configuration store section, which encapsulates a few of these calls, but not all of them.
//include section
#include <IviConfigServer.h>   //IVI configuration store
//done once at program startup. Note: this gets a copy, you don't have to dispose of ConfigStoreHandle afterwards.
static IviConfigStoreHandle ConfigStoreHandle = NULL;
Status = Ivi_GetConfigStoreHandle (&ConfigStoreHandle);
//This is the pain in the butt.
ViStatus Status;
IviLogicalNameCollectionHandle LogicalNameCollectionHandle = NULL;
IviLogicalNameHandle LogicalNameHandle = NULL;
IviSessionHandle SessionHandle;
ViChar       ControllerSessionName[MAX_Controller_Name_LEN];
ViChar       ControllerDescriptor[MAX_DESCRIPTOR_LEN];
ViChar       ControllerDescription[MAX_Controller_Name_LEN];
//get the configuration store logical name collection (what you see in MAX under "Logical Names")
Status = IviConfig_GetConfigStoreLogicalNameCollection (
    ConfigStoreHandle,
    &LogicalNameCollectionHandle);
//how many logical names are there in the collection?
Status = IviConfig_GetLogicalNameCount (
    LogicalNameCollectionHandle,
    &IVI_ItemCount);
//For each logical name, find the corresponding session name
for (i = 1; i <= IVI_ItemCount; i++) {
    Status = IviConfig_GetLogicalNameItemByIndex (
           LogicalNameCollectionHandle,
            i,
            &LogicalNameHandle);
    //get the session name for this logical name
    Status = IviConfig_GetLogicalNamePropertyViString (
           LogicalNameHandle,
            IVICONFIG_VAL_LOGICAL_NAME_NAME,
            MAX_Controller_Name_LEN,
            ControllerDescriptor);
    //get the description for this logical name
    Status = IviConfig_GetLogicalNamePropertyViString (
           LogicalNameHandle,
            IVICONFIG_VAL_LOGICAL_NAME_DESCRIPTION,
            MAX_Controller_Name_LEN,
            ControllerDescription);
    //get the handle for the ession attached to this logical name
    Status = IviConfig_GetLogicalNameSessionReference (
           LogicalNameHandle,
            &SessionHandle);
    //get the name of the session (what I really wanted in the first place)
    Status = IviConfig_GetSessionPropertyViString (
           SessionHandle,
            IVICONFIG_VAL_CONFIG_COMPONENT_NAME,
            MAX_DESCRIPTOR_LEN,
            ControllerSessionName);

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

Agilent E364XA IVI driver does not support measurement of 2nd channel?

Hi,
just downloaded the IVI driver for Agilent programmabel power supplies E364xA. It's supposed to support also the E3646A, a dual power supply. In my case there are two of 'em, connected via GPIB. I've configured 'em in MAX and have set up logical names, driver sessions and hardware assets. The two driver sessions use the hpe364xa as software module, the hpe364xa_32.dll as module path and show a whole bunch of supported devices, amoung of is also mine. I've set up two virtual channel names each for both driver sessions (4 channels over all). I can set the output voltage of both channels properly, but cannot read the voltage back. Get always the voltage level for the 2nd channel of the device. Hav
e tried measuring both or just one channel, it always returns the voltage of ch2, either two times a very narrow level or just one result.
Any idea?
BTW, this happens both in LabVIEW 7.1 and in TestStand 3.0
Greetings from Germany!
Uwe Frenz

Hi,
the problem is that function does not set active channel. This function measure value from your last configured channel. For example: If you set volatge on channel 2, the measured value should be from this channel, if you set volatge on channel 1 before measurement, measured value should be from channel 1. :-(
I attached fixed source code and DLL. Please try it, and let me know if the problem is fixed. I don't have instrument so I cannot test it. My email is [email protected] . Thanks.
you should copy these files into [IVI] directory. The default path is C:\Program Files\IVI
hpe364xa_32.dll => [IVI]\bin
hpe364xa.h => [IVI]\include
hpe364xa.c => [IVI]\Drivers\hpe364xa
Zdenek
Attachments:
hpe364xa.zip ‏70 KB

How the IVI New Session.vi works with the ivi.ini?

Hi,all
Does anyone know how the IVI New Session.vi works with the configuration file ivi.ini?
And when the ivi application running, how the ivi calss driver refers to the right specific instrument drivers without changeing the program?
Thanks,
njzhw
人的生命是有限的，但知识是无限的！
南京众知维测试技术有限公司

Which VI or function are you referring to? There is neither an "IVI New Session.vi", nor a corresponding "Ivi_NewSession" function in C.
The Ivi Class Drivers determine which specific driver to use at run-time, by looking up the resource descriptor (a Logical Name, or Virtual Instrument) and determining the associated Instrument Driver. That configuration information is settable by the user through MAX (Measurement and Automation Explorer).
--Bankim
Bankim Tejani
National Instruments

Can I share Attributes/Variables between 2 different Class Driver Sessions?

I am designing a Simulator of Instrumentation following these steps:
1) re-programming, re-compiling, and re-building the DLLs from the advanced class simulation drivers included in IVI Driver Toolset 2.0 using LabWindows/CVI 7.0;
2) then i create a VI in LabVIEW 7.0 which calls an IVI Class Driver obtaining the desired simulated output data.
My problem is that I need to share variables between different DLLs in LabVIEW.
I want to simulate a circuit which consists of a battery and a resistor. I've got 2 instruments: a DC Power Supply and a Digital Multimeter.
The DC Power Supply acts as the battery providing a certain voltage level, and the Multimeter measures the Voltage and the Current in the resistor.
I've designed a VI in LabVIEW which uses 2 different sessions: one which calls the class driver IviDCPwr, and the other one which calls IviDmm.
I wish to be able to access the attributes from "nisDCPwr.c" in the file "nisDmm.c".
For example, to write a line like this:
Ivi_GetAttributeViReal64 (ViSession vi, ViConstString channelName, NISDCPWR_ATTR_MEASUREMENT_BASEV, 0, &reading));
inside the source code "nisDmm.c" of the advanced class simulation driver.
The problem is that the only ViSession accessible from nisDmm is the handle from the Digital Multimeter, but not from DC Power Supply.
Would this be possible? Is it "legal"?
I've tried another approach through the declaration of external variables, but unfortunately I get a run-time error in LabVIEW.
The only solution I've found is using auxiliary files going between, through the functions included in the Low Level I/O Library .
Nevertheless, the solution proposed above would result much more convenient, faster and safer in my application.
I hope everyone has understood my question, and anyone can help.
THANK YOU VERY MUCH FOR YOUR TIME!!!

Doesn't anyone have an answer?
Or any proposal?
Or even a clue?
THANKS!

Performing a Vi_Lock in an IVI Driver

I am using the Tektronix AWG520 IVI-C Driver. Here is the scenario of events: I call the Initialize function to obtain a vi session. It appears that this vi session is "owned" by the driver now. As soon as I attempt to write anything to the instrument through GPIB commands using that vi session, I get an error message saying that the session is invalid. I am assuming this is because the IVI driver is either not releasing the vi session or is releasing a sort of masked vi session. Does anyone know if this is the case? I have tried a couple of things to get this result: The first thing I tried was writing an identify function that would use the function vi_write to write the *IDN? query to the instrument. This did not wor
k. Now I am trying to do something simpler, by just trying to send the vi_lock command to the instrument. I get the same error that the vi session is not valid. Is there any possible way to get around these "problems" with the IVI driver? Any help in this matter is greatly appreciated! Thanks in advance.
Attachments:
tkawg5x0.c ‏280 KB

Hi,
It seems that your are trying to use the IVI session handle to perform I/O operations. An IVI session is initialize using the Ivi_SpecificDriverNew function. From the function help:
"Note: This function does not create a VISA session to any instrument resources. If you use VISA to communicate to the instrument, you must create a VISA session yourself and set the IVI_ATTR_IO_SESSION attribute to that value. Otherwise, you can use the IVI_ATTR_IO_SESSION attribute to hold a handle to whatever communications resource you use."
Look at the callback functions as a reference for instrument I/O. First the session is locked and then the IO VISA handle is obtained using Ivi_IOSession. This function returns the VISA handle stored in IVI_ATTR_IO_SESSION.
The driver needs to initialize this attribute with a valid I/O handle (usually VISA).
The tkawg5x0_IviInit function in this driver initializes the attribute by calling viOpen.
Hope this helps.
DiegoF.
National Instruments

Using IVI driver for Keithley 6485

I am trying to learn how to use IVI drivers. I installed IVI drivers for two instruments, an HP34401A and a Keithley 6485. I was able to get the HP to work in simulation mode (I don't have the hardware). I am also trying to get the 6485 working in simulation mode. The attached vi was provided by Keithley. I configured a logical name in MAX, but this name doesn't show up as an option when I edit the "logical name" control on the front panel. I changed the Initialize vi to Initialize with Options and added a command string control to set the mode to simulation, manually entered the correct name in the control, and ran the program. No error was indicated in the Initialize vi. After the configuration vi runs, however, the following error was flagged:
Error -1074135023 occurred at IviDmm IVI Error Converter.vi
Possible reason(s):
Primary Error: (Hex 0xBFFA0011) Function or method not supported.
Elaboration: FunctionId: 46, FunctionName: ConfigureMeasurement
Complete call chain:
     IviDmm IVI Error Converter.vi
     IviDmm Configure Measurement.vi
     KE6485_ZeroChk_LV86.vi
This error is being generated by IviDmm Configure Measurement.vi, which is apparently installed NI code. Specifically, the error appears to be thrown when Call Library Function Node is invoked and IviDmm.dll is called. I wasn't able to track down any further info as to the meaning of these error codes.
Thanks for your assistance.
Attachments:
KE6485_ZeroChk_LV86.vi ‏14 KB

Hello,
3rd party devices will show in MAX only when that device is listed at a specific place within your computer's registry. Non-NI hardware may not show up in MAX.
As far as the logical name is concened, unfortunately, you will have to contact Keithley to get a better understanding of their code.
You could download our IVI driver from the link below as you might have better luck with it. You can find any of our 3rd party drivers at www.ni.com/idnet.
Keithley 6485
http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=238
Regards,
Shawn S. | NIC
Instrument Driver/IVI PSE
National Instruments

My hard drive is about maxed out, what are my options

I have a MacBook that is about 5 years old. My hard drive is about maxed out. Trying to determine if it is worth trying to get a larger hard drive, whether I just go to a portable hard drive (a bit of a pain since I travel so much) or something else. Don't think I can even upgrade to Mountain Lion because of lack of hard drive space. I love my Mac, but am looking at possibly going to an iPad for travel as the Mac is heavy and I have to carry two computers (work and personal). Considered buying a new Mac, say an Air, but don't have that kind of cash to drop for it.
Would appreciate any opinions out there? If I upgrade the hard drive, what kind of money are we talking about?
PeterH

For a new hard drive try Newegg.com http://www.newegg.com/Store/SubCategory.aspx?SubCategory=380&name=Laptop-Hard-Dr ives&Order=PRICE
Or OWC for regular hard drives and SSDs http://eshop.macsales.com/shop/hard-drives/2.5-Notebook/
Here are instructions on replacing the hard drive in a MacBook with a removable battery. http://creativemac.digitalmedianet.com/articles/viewarticle.jsp?id=45088
To transfer your current hard drive I like the free application SuperDuper. It makes a bootable copy of everything on your hard drive http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html You'll need a cheap SATA external hard drive case. Put the new drive in the case then format and partition the new drive and clone your old drive to the new one. Check that it's set up right by booting up from the external drive. Then replace your old hard drive with the new one and put your old one in the external case.
Here's a cheap SATA external hard drive case on Amazon http://www.amazon.com/Vantec-NexStar-2-5-Inch-External-Enclosure/dp/B002JQNXZC/r ef=pd_cp_pc_0
If you don’t have the tools to open up the MacBook OWC has a set for $5
http://eshop.macsales.com/item/OWC/TOOLKITMHD/

How to add the "Voltage Calibration"in the DCpower for IVI drive??

How to add the "Voltage Calibration"in the DCpower for IVI drive??

To gather more information concerning the use of IVI there is a very comprehensive page of Class Specifications for IVI Class Instruments:
www.ivifoundation.org
This resource covers all IVI calls for each class of instruments and should provide you wiht valuable information. For an additional overview of IVI and its relationship to NI products, you can also visit our Resource Library:
ni.com>>Resource Library>>Instrument Drivers
Best Regards,
Chris D
Applications Engineer
National Instruments

Generate a '2 output instrument' directive to IVI driver

Hi,
I have a Tektronix AWG420 which I didn't find drivers for anywhere; however I did find an IVI driver for the AWG5x0 family in the NI drivers' zone.
As the command set for these instruments is almost identical I tried using it, and it works great with my applications for Channel1 if I turn of the 'ID query' at initialization.
However, as the driver doesn't recognize that I have a 2-output instrument I can't communicate with Channel2.
Does anyone know how can I give directives to the driver that this is a 2-output instrument?
Thank a lot,
malosh

Unless you want to buy LabWindows/CVI and modify the driver (orf ind someone to do it for you), I think your only option is to use tkawg5x0 Write Instrument Data to send the unsupported commands. This (and a read function) are on the Utility Functions>Instrument I/O palette.
Since doing this makes your program instrument specific and you lose most of the reasons for using IVI, you could always write a native LabVIEW driver or use the Instrument I/O Assistant instead of the IVI driver.

IVI driver session In MAX

Similar Messages

Maybe you are looking for