IVI drivers in labview 8.0.1

Similar Questions

• Clear explanation of the name of the channel on IVI Drivers

  Hello

  I'm using Labview 8.0 assessment to write a program which will include a 35 - 5 p Xantrex XDL DC Power Supply to automate a test. It has only one exit.

  I installed the drivers XDL and IVI Compliance Package. However, I'm still struggling with the name of 'channel' on the IVI Drivers.

  Can someone please clearly explain to me what is the name of the channel, why do I need and what I need to put my name to the channel to get my program to work?

  Thank you!

  Yes, I've read this discussion, but it does exactly what a channel name was, as I had an output "channel".

  I went back to my program just to give it a shot, I typed in the name of the channel in a digital 1 and it worked.

  I still don't know what it is, but at least it will communicate now.

• IVI drivers

  So I read through the VISA and IVI definition/intros, and it sounds like the listed on site IVI drivers of OR would be better to our application needs. It seems that every driver is supported in one or more of the following development environments: LabVIEW, LabVIEW/CVI, Measurement Studio or just of the .NET Framework. I would just like to interact with these drivers via c# in VS2010, but the drivers I need are not available in the .NET Framework.

  My question (s):

  Do I need to buy a subscription of Measurement Studio for VS2010 to use the Measurement Studio drivers? Can't I just use these in VS2010 without Measurement Studio?

  If I don't want to purchase Measurement Studio but want to continue to use these devices, the next best idea would directly communicate with the VISA layer for these devices?

  Thank you!

  Hi Geoff V.

  To answer your first question

  Do I need to buy a subscription of Measurement Studio for VS2010 to use the Measurement Studio drivers? Can't I just use these in VS2010 without Measurement Studio?

  My answer is NO! You could manipulate the managed to the native technology - PInoke code or something like that.

  Here's a simple example:

  [DllImport("IviFgen.dll", EntryPoint = "IviFgen_ConfigureOutputMode", CallingConvention = CallingConvention.StdCall)]
  public static extern int ConfigureOutputMode(System.Runtime.InteropServices.HandleRef Instrument_Handle, int Output_Mode);
  

  After that, just use the function declared in c#.

  Thank you

  Charles

• Cannot rename my PXI-4071 for something else that "PXI-4071" have the self-assessment work, and I can use the new name in the ivi drivers

  I tried to change the name of the PXI-4071 "DMM" that worked, but when I try to launch the "self-test" or open the app it Panel always fails.   This is also true if I pass the new name of the ivi driver.   Return to the name "PXI-4071" makes everything works again.   Note I managed to change the name of our PXI-2530 b 'SWITCH' and the name of our SMU-6363 to "MIO" and I could pass these names to their IVI drivers and they would work.

  I messed with alias VISA, IVI logical names, but nothing works unless it is called "PXI-4071.

  
  

• The IVI Drivers: RangeCheck of initialization option set to true: failed to get an out-of-range error

  Hello

  I'm new to IVI drivers (started using them last week) and I have a problem with the option of initializing RangeCheck.

  So get used to the IVI drivers, I used the example provided with the AgilentE36xx IVI - COM driver (on my computer, it is located in C:\Program Files\IVI Foundation\IVI\Drivers\AgE36xx\Examples\VS.NET\Cpp\Example1).

  I could do everything I wanted except get an error out-of-range, during the passage of an out-of-range value to a function. I put the RangeCheck init option to true, but I don't have any error in the simulation, nor with the connected equipment.

  Attached is the code (from the example of Agilent) but modified so that it should throw an out-of-range error when adjusting the tension on the following line: spOutput1-> VoltageLevel = 1000; ... why no error.

  Still, it runs correctly. Can someone tell me what I'm not doing correctly.

  Kind regards

  Roman

  Hello

  I posted the question on the Forum of Agilent.

  Here is the link to the post: http://www.home.agilent.com/owc_discussions/thread.jspa?threadID=33348&tstart=0

  The problem is now resolved. Thank you for your help.

  Kind regards

  Roman

• How to 'release' class IVI drivers in a MAX to bind a specific to a given class driver driver?

  Hi all
  I'm pilots to develop a family of instruments for which no IVI drivers are available.
  I want to manage these instruments as IVI devices in my test system
  I created a pilot of the new IVI class with the Wizard "Create Custom IVI class driver ' Labwindows/CVI, for my family of instrument
  Then, I created a specific new IVI driver with specific 'Create of IVI Driver' assistant, for one of the instruments of my family.
  In MAX, I created a Module of Instrument Driver software for my specific driver.
  In the published API tab, I can't add my new class driver API.

  Question: How can "publish" class IVI drivers to bind a specific to a given class driver driver?

  I use MAX 4.5 and 8.5 CVI

  Thank you for your help

  Hello Nveron,

  Looks like you will have to manually update the XML of IVI Configuration store to do two things:

  -Add your custom class as one of the published API

  
              IviCustom
              1
              0
              IVI - C
         

  -Add the API published to the software module

  
                  
                  
                  
   

  I just chose p678 as the idref to prevent conflict with the other existing idrefs.

  Let us know how it goes,

  NathanT

• VI Initialize with OptionsString missing the resource name field when creating the IVI Driver Generator LabView 8.6

  Hello world

  We have just uploaded the latest LabView version 8.6 and there is a nice tool called generator of LabView LabWindows CVI Instruments drivers. Our driver of the instrument is an IVI driver that has a LabWindows CVI interface that uses the generation of LabView tool to create all the VI that could be used to talk to the underlying driver IVI hollow discovery of .fp, .sub and .h files. No mistake and screws more than 30 are generated automatically.

  There is an inconsistency in the Initialize function IVI driver. There is a VI Initialize driver without an input of OptionString parameter and there is a second VI with the OptionString parameter.

  Two of these screws should have a required entry field that is the ResourceName of the instrument, but this field is visible in the initialization of VI that has no OptionString input parameter and is not at all visible in other VI initialize that has an OptionString input parameter

  No idea why the second version of Initialize does not display the ResourceName parameter?

  Thank you

  Sorin

  Hey Sorin and Heather,

  I've just built your IVI driver and can see the question you come through.  What version of LabVIEW and the tool are you using?  I am looking into this further for trying to dig your problem a little more.   If you add the connector to the connector pane, the created VI meets the needs that the name of the resource exists, it's just not in the connector pane.  This can do a right-click on the icon in the upper right of the front panel and selecting display connector.  Select where on the VI wish you add the connector, and then select the name of the resource.

• Where to install third-party drivers for LabVIEW

  Hi, I have not used LabVIEW in several years.

  I downloaded many third party drivers and saved locally on my C:\.

  Where should I move these .lib files so that I can use their throught it works Palette?

  Is there a certain structure should I use when registering these?

  Also, what is the difference between user.lib & instr.lib files?

  I tried to find the folder as shown in the following tread but I can't seem to find the file:

  How to install my third-party instrument Drivers?

  It is what the recommended action:

  

  Can anyone help?

  Kind regards

  Seamus

  InStr.lib is for instrument drivers.  User.lib is your own private libraries.

  I'm guessing that you are on a 64 bit OS.  So you should look in C:\Program Files (x 86) \National Instruments\LabVIEW (20XX) \instr.lib

• Search for device drivers in LabView

  I try to install the device, via the Help menu of LabView drivers. I select the manufacturer and a key word, but I can't click ' search for > '. The button is grayed. What should I do to be able to click on this button?

  As far as I know all the drivers, you can download through this screen, you can also get NI.com directly:

  Driver search page

  It is a little less convenient that you must put yourself in the instr.lib folder and restart LabVIEW for them appears in the palettes, but it's better than no drivers at all.

• update drivers for LabVIEW 5.1.1 to 10.0 (or a compatible version)

  Hello!

  I can't read the files in the attachment (CCD drivers), because they are written in a version of LabVIEW (5.1.1) is not compatible with mine (10.0).

  Anyone know how to make them readable by my version?

  Thank you very much

  Eleonora

  Attached.

  In the future, please report this type of request in the Upconvert requests Thread. The link he is indicated in the announcements section on the first page of the LabVIEW forum.

• For Fluke 8846A IVI drivers

  I am not able to download the drivers for Fluke 8846 IVI. Help, please.

  You can also try a different browser, some customers have reported problems with some versions of Chrome.

• Agilent IVI drivers for 34410A multimeter

  I develop using LabWindows/CVI 2013 SP1.

  I downloaded the 32-bit version and 64-bit drivers IVI for Agilent 34410 A multimeter Agilent web page at the following address:
  http://www.home.Agilent.com/Agilent/software.JSPX?CKEY=1639470&LC=Eng&cc=us&NID=-11143.0.00&ID=16394...

  The files are:
  driver_ivi_matlab_Agilent34410_1_0_25_0_x86.msi
  driver_ivi_matlab_Agilent34410_1_0_25_0_x64.msi

  I develop on Win7 64 bit.  I create 32-bit applications CVI.

  What version of the IVI driver should install the x 86 or x 64?

  Thank you

  Kirk

  For a 32-bit application, the _x86 driver is the right thing to use.

  is there a reason why you are not using NIs IVI - C driver for this device (found at http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E9419659CE034080020E748... )?

• IVI drivers - OK to use SetValue rather than the specific functions of Config

  It is a general question of IVI driver, although I am currently using c# with the supplied agesani driver by NOR.

  The IVI specifications provide many methods for configuration of devices (for example, ConfigureLevel, ConfigureAcquisition, etc.).  The IVI specification also requires that all drivers provide support for configuration of attributes through SetValue.

  Configurations, the question: can be done through SetValue, or is it necessary to use specific methods to "configure"?

  Thank you... and my apologies if this lame question.  Always learn from IVI.

  Hello Dasher,

  It is possible to set all the attributes in writing through SetAttribute functions, but this is not the recommended approach.  Configuration methods have been designed to set the related attributes in a logical manner.  Sometimes an attribute must be configured before other attributes.  The configuration functions should be considered.  If you use SetAttribute functions directly, you will probably have to learn more about how the instrument works and responds to commands.

  See you soon,.

  NathanT

• You looking for LabVIEW Keysight/Agilent/HP 6634 B drivers

  Hi all

  I tried seraching everywhere but I can't find drivers for labview for power supply Keysight/Agilent/HP 6634 B. The only ones I can find are for the 6xxxA series, but not the series of 6xxxB.

  If anyone has or knows where to find them, I would be very grateful!

  Thank you

  You are in error. This is indeed the driver LabVIEW, class IIA type. If you don't like that this driver calls dll, as I wrote above, you could simply create your own driver following the information of the SCPI, located in your device manual package...

  If you want to use the driver, follow these steps:

  1. Download and install the package corresponding to your version of LV IVI: http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/n8:3, ssnav:ndr / sb / - nigenso4-...
  2. Restart the PC
  3. Install the driver of the IVI of the site: http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E947E659CE034080020E748... (direct link to the exe: http://sine.ni.com/apps/utf8/niet_download_id.log_ids?p_profile_id=1270941&p_doc_id=E3B19B3E947E659C... )
  4. Enjoy:

  

• LabVIEW 7.1 IVI - C Wrappers and VISA property node do not work together?

  Hello world

  I want to use the property node VISA with LabVIEW 7.1 Wrapper of two companies different well known instrument, Rodhe-Schwarz and Agilent Technologies.
  The two companies releasead their IVI - C for NI LabVIEW 7.1 drivers version NI Instrument Driver network and they are ready to be installed and used.

  I found a bug manifested that the LabVIEW 7.1 version that the bug is not present in whhen versions 8.0 LabVIEW or LabVIEW 8.6 than these IVI LabVIEW of LabVIEW 7.1 wrappers are used.

  Everyone could exeperience this bug if they have LabVIEW 7.1 installed and are trying to use the version of LabVIEW 7.1 of these wrappers which are published in NI Instrument Driver Network under the links below.

  Agilent ag81150ni IVI Driver for LabVIEW 7.1 install from here. Used in simulation that by definition simulate = 1

  http://sine.NI.com/apps/UTF8/niid_web_display.download_page?p_id_guid=55798957B1A633BDE0440003BA7CCD...

  Rodhe Schwarz rsngpt IVI Driver for LabVIEW 7.1 install from here. Used in simulation that by definition simulate = 1

  http://sine.NI.com/apps/UTF8/niid_web_display.download_page?p_id_guid=E3B19B3E91D6659CE034080020E748...

  After the installation of these two complete drivers close LabVIEW 7.1, if it was open, and then restart LabVIEW 7.1. You can see two new ready to be used as LabVIEW 7.1 IVI drivers in the LabVIEW Instrument Driver pallet wrappers in a LabVIEW 7.1 VI test.

  Open a new white VI and of the use of the Instrument Driver Palette two VI known, initialized with Options.vi and Close.vi adding them on the block diagram, connect all THMs. Accept all default settings except simulate parameter which must be defined as = 1 simulation.

  The two VI run OK mode of simulation without errors.

  Now select a property in the advanced Panel of VISA node and press this node between 'Initialize them with Options' and 'Close' VI and make all necessary in-out connections and error.

  Run these two simple screws of simulation

  1. When I run pilot Rodhe Schwarz IVI the property node going OK until the end. No error
  2. Whne I run Agilent IVI driver the property node is always out of the error Code 7.

  Question is why they behave different with regard to the property of node when it is used with the LabVIEW 7.1 envelopes? BTW, the failing VI of wrappers Agilent LabVIEW 7.1 works very well in labVIEW 8.0 and 8.6. That means that this problem is limited only the version of LabVIEW 7.1.

  I posted the same question on the set of LabVIEW and nobody chose their interest in there so I decided to post here. As this question is also linked to IVI, VISA drivers, it is possible the person of this group to get a clue about this annoying behavior.

  I've attached screenshots of the PNG files that show the difference of different behavior of VISA property between these two drivers node.

  ScreenTestShots.zip (152 kb)

  Thank you

  Sorin