VISA or IVI drivers, example code?

Hello,
I have an Agilent DSO-X-2004A oscilloscope and I've downloaded two different set's of drivers that work. Here are the links to the drivers.
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=9E84674573AF6AB8E0440021287E6A...
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=A661BD7B892F06B2E0440021287E6A...
The first one is the Agilent 2000 3000 4000 X-Series drivers, that require only NI VISA-4.6
The second is the Agilent agx2k3k Oscilloscope drivers, that require NI VISA-4.6 or IVI Compliance 4.3
The second one has example codes, which are VERY helpful for me since I am new to LabVIEW. The first one does not have examples, but seems to have more thorough driver library with more scope options to set. Without the examples though, I will have a tough time. Can I find examples for those drivers somewhere?
When mixing blocks from different drivers, I get broken wires with the message "source is IVI session of class, sink is VISA session of class". Maybe if I could resolve that, I could mix the driver blocks.
Thanks
John

The answer is that both driver sets have example code in their .zip files. The first one (Agilent 2000 3000 X-Series) just didn't have the examples show up in the Instrument I/O palet, and the other one (agx2k3k) did. You can add the examples to the palet by following the instructions here:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/merging_vis_on_palette/
The question of which set to use is still open. The Agilent 2000 3000 X-Series drivers are "Certified LabVIEW Plug and Play (project-style) Instrument Drivers", and the agx2k3k dirvers are "Certified Multi-Enviornment IVI Instrument Drivers"
For a new user like myself, it's very hard to know the differences and how they may effect me down the road. Hopefully someone with more experience can chime in. 
- John

Similar Messages

  • 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

  • IVI driver examples

    Does anyone have actual code examples using IVI drivers. (I'm not picky
    about which class driver your using nor which dev environment -- LabView,
    LabWindows, C++, VB)
    Thanks in advance for your assistance.
    Dean
    [email protected]

    Dean wrote:
    > Does anyone have actual code examples using IVI drivers. (I'm not picky
    > about which class driver your using nor which dev environment -- LabView,
    > LabWindows, C++, VB)
    >
    > Thanks in advance for your assistance.
    >
    > Dean
    > [email protected]
    Dean,
    Have you looked at the driver library on NIs web site.
    There are a number of ivi drivers there for different pieces of hardware.
    Most of them should have an application example.
    Hope this is what you are looking for.
    Kevin Kent

  • Run cleanup utility, then all ivi drivers in the measurement & automation explorer are deleted,

    Hello I have the following problem,
    I run the cleanup utility, then all ivi drivers in the measurement & automation explorer are deleted.
    when I want to add for example a new driver session then that is not possible to click on "create new".
     What is the problem?
    regards samuel

    Cedric,
    In this case its the usb-serial adapter that is likely the cause of the issue.  As mentioned in this KB it is likely that MAX doesn't know how to recognize the third-party adapter.  You may want to refer to this KB that talks about making VISA calls to third-party devices as it may be useful.
    John B.
    Applications Engineer
    National Instruments

  • Has anyone got the Comsoft Profinet example code working??

    Hello!
    I have a cRIO Profinet card and I'm attempting to get the example code working.
    I have followed the instructions in GettingStarted_cRIO_PN_IO_Device.pdf
    I have created an empty project with just the 9023 and 9113 present, and copied the 3 items from the example project cRIO PN IO-Device (LV 2012) as per the documentation.
    When I try to compile I get the error shown attached.  I cannot view the error as the VI is password protected.
    In 5 years of working with cRIO using many different c-series modules from NI and 3rd parties I have never come across a password protected example Vi - this is very disappointing!  I don't see how it will be possible to use the card without being able to access this VI, and clearly it is impossible to use it without this VI as they are unwilling to share its functionality.
    Has anyone got this working on anything other than a 9104 (which the example uses?)  Does anyone know the password?  Is it possible to use the card without using this example code?
    I will be communicating with a Siemens PLC (acquiring a load of U16s and logging on the cRIO at 20ms intervals).
    Many thanks for any input, or any experiences of using this card.
    Aaron
    LabVIEW/RT/FPGA 2012
    NI-RIO 12.0.1
    cRIO 9023 controller and 9113 chassis with COMSOFT PN module in slot 1.
    Attachments:
    PN_error.png ‏44 KB
    PN_error2.png ‏20 KB

    Just for the record, I am using the CRIO-PN with cRIO-9081 and cRIO-9068 integrated chassis successfully.
    LabVIEW (RT/FPGA) 2013 SP1.
    I didn't use the higher level ComSoft example code directly, as the VIs use so many control/indicators that the FPGA usage is sky high. I rewrote them to pass the I/O data via DMA FIFOs.

  • Simple example code to connect to SQL server 2002

    Hi,
    I found a good website a while back which showed step by step how to connect to a sql server DB using JDBC, a re-install of windows means I cant find it again. I have searched the web, but to no avail. Basically I need to find a step by step guide to using java to access data within MS SQL server 2000. It needs to include details about where to download suitable drivers etc. and example code so that I can originally test my connection before diving much deeper.
    Any help much appreciated.

    Hi:
    here is the code that you can use it to test your connect if you use MS sql 2000 free driver. Others, you need to make little change on
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver"); and
    con = .......... parts
    goog luck !
    import java.sql.*;
    public class Connect{
    private java.sql.Connection con = null;
    private final String url = "jdbc:microsoft:sqlserver://";
    private final String serverName= "localhost";
    private final String portNumber = "1433";
    private final String databaseName= "pubs";
    private final String userName = "xxxxx";
    private final String password = "xxxxx";
    // Informs the driver to use server a side-cursor,
    // which permits more than one active statement
    // on a connection.
    private final String selectMethod = "cursor";
    // Constructor
    public Connect(){}
    private String getConnectionUrl(){
    return url+serverName+":"+portNumber+";databaseName="+databaseName+";selectMethod="+selectMethod+";";
    private java.sql.Connection getConnection(){
    try{
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    con = java.sql.DriverManager.getConnection(getConnectionUrl(),userName,password);
    if(con!=null) System.out.println("Connection Successful!");
    }catch(Exception e){
    e.printStackTrace();
    System.out.println("Error Trace in getConnection() : " + e.getMessage());
    return con;
    Display the driver properties, database details
    public void displayDbProperties(){
    java.sql.DatabaseMetaData dm = null;
    java.sql.ResultSet rs = null;
    try{
    con= this.getConnection();
    if(con!=null){
    dm = con.getMetaData();
    System.out.println("Driver Information");
    System.out.println("\tDriver Name: "+ dm.getDriverName());
    System.out.println("\tDriver Version: "+ dm.getDriverVersion ());
    System.out.println("\nDatabase Information ");
    System.out.println("\tDatabase Name: "+ dm.getDatabaseProductName());
    System.out.println("\tDatabase Version: "+ dm.getDatabaseProductVersion());
    System.out.println("Avalilable Catalogs ");
    rs = dm.getCatalogs();
    while(rs.next()){
    System.out.println("\tcatalog: "+ rs.getString(1));
    rs.close();
    rs = null;
    closeConnection();
    }else System.out.println("Error: No active Connection");
    }catch(Exception e){
    e.printStackTrace();
    dm=null;
    private void closeConnection(){
    try{
    if(con!=null)
    con.close();
    con=null;
    }catch(Exception e){
    e.printStackTrace();
    public static void main(String[] args) throws Exception
    Connect myDbTest = new Connect();
    myDbTest.displayDbProperties();

  • Are IVI drivers supported on RT?

     I have a PXI-4060 DMM on a remote system.  I have been trying to initialize the DMM but have had no success using the IVI drivers.  I have set up a Logical Name that is linked to the Driver Session for the 4060, but these are setup in MAX under the host system, not the remote system.  I have been unable find drivers for that DMM other than the IVI drivers and if they aren't supported on the RT system, how do I use the 4060 DMM on a remote system?
    My cfg is:
    IBM laptop running WinXP w/LV 7.1
    PXI-1045 chassis w/LV RT and multiple components that all work fine except the DMM
    I have the latest drivers/software for everything that I'm aware of (DAQ, IVI, Visa, etc)
    Scott

    Hi Richard,
    Thank you. I ran that test and there are no Visa's running describing any of the PXI instruments.  I've attached a screenshot of the results sitting on top of what I'm seeing in Max.  For the Visa's, the 6 GPIB's are for HP6610xA power supplies and the serial's are for an 8-port serial card (plus the 2 on the 8187 controller), which is a PXI card (8421).  When I'm trying to initialize the DMM I am running on the targeted system as shown so I should only need the descriptor after the IP address (PXI3::15), correct?  As noted from the error description above, the vi is looking for a "DAQ::" descriptor and I don't see anything like that in Max.
    Hope this helps with the diagnosis,
    Scott
    Attachments:
    VISA Find 4060.bmp ‏2305 KB

  • Error when using example code

    Hi all,
    im trying to create a program for communication over a LAN network with a spectrum analyser.
    when i use a standard example code i get errors like this one:
    [Linker error] undefined reference to `viOpenDefaultRM@4'
    did i made a fault in linking?

    DAV C++ uses a GCC based compiler. The VISA DLL is compiled with MSVC. This will cause a problem with the calling convertions used and expected.
    Basiclly the visa DLL uses 'viOpenDefaultRM' but the GCC expects viOpenDefaultRM@4, and thus can't find it in the DLL. You can solve this manually.
    The basic steps are:
    1. Generate a .def file from the DLL for example with pexports.
    2. correct the .def file so all the functions have the correct decorations as expected by GCC.
    3. Create a new import library,
    For more infomation see this post about the same issue with NI-DAQmx
    An other option would be to use the Visual Studio 2005 express editions?
    And in some configuration you will need to buy a license to use NI-VISA: http://www.ni.com/visa/license.htm
    Hope this helps
    Karsten

  • Followup on IVI drivers

    Hi,
    Thanks all for the help on IVI drivers.
    I want to develop a simple interface for a scope. I want to use IVI class
    drivers (the "green" drivers?) so that I am as hardware independant as
    possible. I have a simple example using the scope class drivers that I am
    happy with right now.
    I have drivers for my current scope, from lecroy. When I install these
    drivers, to
    $labview_path/instr.lib/lcwpxxx
    I don't get any files with a .dll extension. I can use instrument specific
    ("blue", right?) drivers from this set-up.
    I think I must have a .dll to be able to install a driver in max, then
    install a virtual instrument, then install a logical name?
    Is there something I can do to make this driver work?
    Thanks,
    Chad

    Thanks, that was the right place to look.
    "Dennis Knutson" wrote in message
    > Check your VXIpnp\Bin folder for the .dll. I believe you should also
    > have a separate folder for the instrument under VXIpnp if it was
    > installed correctly.

  • Labview - LIN Goepel 3072 - Example code

    Is there example code for managing with Labview the LIN communications with the Goepel card PXI3072?
    I've bought the card to Goepel (it's indicated on the NI web) but I've only one sample and the manual guide, I'm searching on the forums but I don't find additional support.
    If someone can help me ...
    Thanks,

    Hi Ihb,
    You should have found some examples along with the Drivers provided in the CD which comes along with the card. If not, you can contact Goepel and they can provide them.
    Also, using the card is not that difficult. As long as your header command construction is ok, you should not have problems since this is the basic foundation for sending commands to the card.
    Regards,
    Ashm01

  • Choice between VISA and GPIB drivers

    I have a waveform generator with a GPIB port. I would like to build my own VIs. Can someone suggest which driver (VISA or GPIB or IVI) would be preferable and what are the differences in terms of ease among these drivers?

    Hello Craig,
    I have an Agilent 33220A frequency generator for which I have already found drivers from the Instrument Driver Network. I am a beginner in LABVIEW and am in the process of improving my skills in communicating with instruments. So far, I have been communicating with other instruments using VISA and a serial port.
    While going through LABVIEW HELP, I realized that VISA, GPIB and IVI drivers can be used for communicating with a GPIB instrument port. This being the case, I would like to know which of the above-mentioned drivers is preferable?
    Thanks
    Ram

  • Question on the example code 8253eventcount.c

    Hi.
    I saw the example code 8253eventcount.c before in the NI-DAQ6.9.x. That is very useful.But i still confuse that "Do i need to set up each clock pulse duration?". From the program, it seems that the counting process solely depends on the function NIDAQDelay(sec).....
    By the way, if i am now using an old version of NI-DAQ6.8.5, How can i update some calculated voltages for each 1ms. Although i have read and followed the procedures in the user mannual of lab-pc+,but, i am still not sure how to program the counterA2 with appropriate update interval. Could anyone give me an example code? It seems that no examples are given in the version of NI-DAQ6.8.5.
    I am now using lab-pc+ with Ni-daq6.8.5 by using c++ and win
    dows95 as my working platform.Please help me in anyway! Thanks!
    Attachments:
    Lab_PC+_AO.cpp ‏2 KB

    The NIDAQDelay() is only in there to control how often the program checks the current count on the counter. If it is set to 1 seconds, it will read the counter every one second and return how many counts have been read since the start. If you take that function out, the program will check the counter as fast as it can which will tie up your CPU.
    As to your question about calculated voltages, can you be more specific as to what your application is and what you are trying to do, I'm a little confused.
    Brian

  • Acrobat 7.0 ActiveX Object example code in Lookout

    Help folks!
    I'm trying to set up the Adobe Acrobat 7.0 Browser Document ActiveX Object under Lookout 6.0 but it doesn't work. My goal is to display a pdf document by lookout.
    What should I set by Property Browser...?
    What should I set by Property Pages...?
    What should I set by Value Property:?
    What means the term "Property" in this kind of objects?
    Is there an example code I can get?
    Any suggestion will be appreciated.
    Thanx.

    I don't know of a FREE ActiveX control for MS Word.  However, if you have MS Word installed on the same computer, you can use MS Internet Explorer ActiveX Control to view Word documents. 
    But before we do that, we have to make sure that MS Word is set to open documents in the "same window."  This basically opens a DOC file in Internet Explorer itself rather than launching a new MS Word window and then opening the DOC file in it.  To set this (if it isn't already):
    1. Launch Windows Explorer. 
    2. From the Tools menu, select "Folder Options"
    3. Click the "File Types" tab. 
    4. From the listing of "Registered File Types," select "Microsoft Word Document," (you can get to it fast by typing "DOC"); click Advanced. 
    5. Click the "Browse in same window" check box -- this toggles whether a Word document is launched outside of Internet Explorer. 
    6. Click OK to close the dialog boxes. 
    NOTE:  if the DOC still opens in a new MS Word window (and not IE), go back and toggle the check-box. 
    In Lookout, use the Lookout Webbrowser control (which is nothing but MS IE Control).  Specify the file path to the DOC file as the URL.  I am attaching a process file which does this using a TextEntry object. 
    Hope this helps.
    -Khalid
    PS:  not sure when this changed but we can't directly attach .L4P files to a post.. what a pain!  Please take a minute to add your weight to this request: 
    http://forums.ni.com/ni/board/message?board.id=130​&message.id=2142
    Message Edited by Khalid on 12-28-2005 02:55 PM
    Attachments:
    doc_process.zip ‏4 KB

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

  • My multimeters don't function properly with ivi drivers

    I have 4 Keithley MM in my setup. I am using the ke2000.dll ivi drivers for all my meters. I have also labeled each meter MM1..MM4, however when I make a call using MM1, MM3 is the one being control? How can I configure MAX properly to avoid this or is it unavoidable?

    Did you download the driver from the National Instruments web site, or did you get it from Keithley?
    Which GPIB board do you have?
    If you are using NI IVI driver or board, you should post this question to the GPIB forum to find out how to configure the driver in MAX.
    Zvezdana S.

Maybe you are looking for