Driver labview 7.0 34401a

Where could I find the labview 7.0 driver for the multimeter hp 34401a, GPIB? the driver on this website is for labview 8.0 and isn't working with version 7.0.
thank you

The driver is included with your version of LabVIEW but if you want the latest version, go here and select the Plug and Play LabVIEW version. Do not select the Plug and Play (project style) driver. Projects were introduced with LabVIEW 8.

Similar Messages

  • Driver labview per controllore di temperatura ThorLabs Ted 200

    Salve.
    Volevo sapere dove trovare i driver di labview necessari per pilotare la temperatura a cui il controllore di temperatura della Thor labs Ted 200 deve funzionare. Il Controllore viene pilotato tramite la tensione applicata tramite cavo bnc all'ingresso R1.
    Grazie dell'attenzione e Cordiali Saluti
    Andrea

    reposted: http://forums.ni.com/t5/LabVIEW/labview-driver-for-temperature-controller-ThorLabs-Ted-200/td-p/1840...

  • PXI 7332, UMI 7772, P70530 Drive LabView example

    I am using the following equipment in a single axis motion control setup.
    PXI 7332, UMI 7772, P70530 Drive, NEMA 34 stepper motor, wiithout an endcoder.
    I am able to operate the motor sucessfully using the Motion Assistant. I have used the generate code option but having trouble turing that into a simple VI.
    Essentially I would like to create a simple VI to control the motor, and send it number of steps and direction information,
    Any suggestions for a sample VI that is out there?
    Thanks
    Kevin

    Hi Kevin,
    You might try taking a look at some of the example vi's from LabVIEW's Example Finder.  Go to Help » Find Examples... When that window pops ups, double-click Toolkits & Modules in the folder list, then double-click NI Motion Assistant.  I'm guessing the "Straight Line Move.vi" or "Blended Move.vi" would be most helpful to you, but you could read the descriptions of each example listed for a little bit more information about what the examples are doing.

  • Reading Max/Min/Av​g with labview from agilent 34401a

    Hi,
    I'm using Labview drivers I've downloaded from the ni.com
    website to control an agilent 34401A digital multimeter.  All I'm trying to do right now is read
    min/max/avg measurements after putting the device into a DC current mode,
    configuring it for min/max measurements, and then pausing for a couple
    seconds.  The program successfully puts
    the multimeter into the correct modes, but always returns 0 for each
    measurement.  Could you take a look at
    the program to see if you find a simple mistake on my part? It should be
    attached to this message.  Thanks very
    much.
    Attachments:
    AVGMAXMIN.vi ‏421 KB

    I don't have the instrument or manual handy but is it possible that the instrument is waiting for a series of trigger to actually take a series of measurements. do you see the display changing? You can try setting a breakpoint at the min/max function and manually trigger the instrument to see if that makes a difference. Also, you don't need the sequence structure at all. Most of the time, sequence structures just serve to make your programs harder to read and debug. Use dataflow for controlling execution order like in the picture I've attached.
    Message Edited by Dennis Knutson on 07-07-2006 02:51 PM
    Attachments:
    No Sequence Structure.JPG ‏31 KB

  • Creating application with odbc driver LabVIEW 8.0

    Hi,
    I've looked through a lot of examples and tried out a lot of them, I still can't get this right. I have a login vi which connects to a MySQL database via an ODBC driver to authenticate a user, if username & password are right user is sent to another vi. This works well on my computer. I am trying to build an executable/installer to run this on another computer that has LabVIEW 8.0 installed but not the ODBC drivers.  I followed examples and included the MDAC files in my application (executable file), and the .udl file I created. I then included the file in my installer. When i run my application in another computer I get the error 'Data source name not found and no default driver specified in DB Tools Open Connec (string).vi'.
    1. What more must I add cause I thought adding MDAC and the udl file was enough.
    2. Just to confirm: do I add the MDAC in support files in Executable file builder or do I add the files in Installer builder?
    3. If I need to include the odbc driver in the application, at what stage (where?) do I do that?
    Please do not refer me to help files Applicationi Builder files for versions 7.0 and less because the setup is different and I just got confused.
    Please help.
    Thanx.
    ntfan

    Hey ntfan,
        Here is a paragraph taken from the Database Connectivity Toolkit ReadMe file. 
    Distributing Stand-Alone Applications and DLLs
    When
    you use components from the Database Connectivity Toolset to build a
    stand-alone application or a DLL with the Application Builder, you must
    install MDAC to the target computer if it is not already installed
    along with the appropriate support files. A build script is included in
    the Database Connectivity Toolset to help you include all these
    components. Refer to chapter 6 of the Database Connectivity Toolset
    User Manual for more information.
        Are you using a build script as described above?
    Brian B
    Field Sales Engineer
    Tennessee/Southern Kentucky
    National Instruments

  • Convert Instrument drive LabVIEW 2012 to LabVIEW 2009

    Hi . now we user Ver. 2009 and we need to use Instrument driver (support  at Ver.2012)
     How we can do?
     http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=24352

    down load file .
    Attachments:
    espec_climatic_chamber.zip ‏1121 KB

  • Driver labview pour wattmetre agilent E4419B

    J'ai acheté recemment une sonde série E9300  pour un wattmetre E4419B de Agilent. Ce wattmetre était jusqu'à présent utilisé sous labview 8.6 avec des sondes type HP8481.La différence entre les 2 sondes est qu'il fallait précedemment charger une table de calibritation alors que la table est intégrée à la nouvelle sonde.
    Pour que cela fonctionne, j'ai mis à jour le firmware du wattmetre, version A2-09-01. Cela fonctionne en manuel, quelque soit les sondes.
    J'ai chargé les nouveaux VI labview série E441.. et cela semble fonctionner pour la nouvelle sonde E9300. Mais ces VI ne fonctionnenent pas avec les anciennes sondes série 8481... et les anciens programmes labview ne sont plus pris en charge par la nouvelle version agilent. ily a un signal d'erreur au niveau du Vi de chargement des tables de calibration.
    Un VI a-t'il été dévelloppé pour faire fonctionner les sondes série 8481, v8486 et w8486 avec la version A2-09-01 du wattmetre agilentE4419B ?

    Translation from french
    I recently bought a probe set for E9300 Agilent E4419B power meter. This meter was previously used in labview 8.6 with standard probes HP8481.La difference between the two probes is that we had previously calibritation load a table while the table is incorporated into the new probe.
    For this to work, I updated the firmware of the power meter, version A2 09-01. It works manually, regardless of the probes.
    I loaded new E441 series labview VI .. and it seems to work for the new sensor E9300. But the VI does not fonctionnenent with old 8481 series probes ... labview and old programs are no longer supported by the agilent new version. ago has an error signal at the Vi loading calibration tables.
    A VI Did he were dévelloppé to operate probes Series 8481 v8486 and W8486-A2 version with 09-01 Wattmeter agilentE4419B?
    French Board

  • Driver/LabVIEW version conflicts

    I am tasked with deploying a major upgrade/rewrite of an inhouse developed LabVIEW .exe program to a test system that is located at our facility a long distance away (different country) and I won't be onsite to perform/debug the install. Currently it is running a version 8.2 "EXE" and LabVIEW RTE, NI-VISA 3.4.1, DAQmx 8.0.0f0 and MAX v4.0.0.3010. My new program is in LabVIEW v2011sp3, MAX 5.1, DAQmx 9.3.5, NI-CAN 2.7.3. My question is whether installing these updates will cause the existing test system not run, which not a desirable state as it is running production testing and I expect that the software/hardware integration will take longer as I will not be onsite and I haven't had the target hardware here to debug my code on.  Any thoughts or experience in this regard will be helpful. In the last several years I haven't had a similar issue, most of my projects have been either new, or updates in the same version.
    As always, thank you in advance.
    Putnam
    Certified LabVIEW Developer
    Senior Test Engineer
    Currently using LV 6.1-LabVIEW 2012, RT8.5
    LabVIEW Champion

    If they are running on a PC, and they are in a country that is reasonably easy to import stuff, then I would just ship them a spare PC with DAQ card and your version of the software already installed.  Then they can swap back and forth between PCs.  Bonus points if you ship a KVM switch to make the process easier on them.  If you're on any other hardware it might be cost prohibative to replicate.
    If you can accurately replicate their installation locally then you can try putting the two versions of software side-by-side and seeing what happens.  It wouldn't be the first time things worked beyond the published NI charts.
    If you can recreate your code in LabVIEW 2009 then you can run DAQ-mx 9.1.1 and both versions are supported.  Once you work out any issues you can move to a more modern version of LabVIEW.  Depending on how complex the code is this might be cost prohibative.
    If there is another identical installation somewhere more accessable then you could use that location as a proving ground prior to deploying your code to the location we're discussing.
    Just a few ideas to think through.

  • Convert Keithley 2400 Driver for Labview 8

    Hello. I need someone to convert the Keithley Driver (labview 5.1) for me to use in labview 8.6. I can only use the earlier version of the driver since my program was written based on this driver.
    Thank you in advance.
    Attachments:
    Ke24xx.LLB ‏3508 KB

    There you are...
    Best regards
    chris
    CL(A)Dly bending G-Force with LabVIEW
    famous last words: "oh my god, it is full of stars!"
    Attachments:
    Ke24xx_8.5.1.zip ‏884 KB

  • Driver non compatible avec ma version LabVIEW

    Bonjour,
    J'ai un driver LabVIEW de la carte Amplicon PCI-215 compatible avec les versions LabVIEW 6.0, 6.1, 7.0, 8.0 mais pas avec la version que j'ai (LabVIEW 2010). Du coup je n'arrive pas à lancer le fichier Setup.exe du driver pour l'installer.
    Pouvez-vous m'aider s'il vous plait à résoudre ce problème ?
    Merci

    Bonjour Salma,
    Merci d'avoir posté sur le forum National Instruments.
    Le fait de pouvoir lancer ou non le Setup.exe de l'installeur de ton driver
    n'a rien à voir avec LabVIEW. Généralement, cela vient du fait que tu ais
    changé d'OS. Vérifie que ton driver est bien supporté sur ton OS.
    Une fois qu'il est installé il est tout à fait possible de récupérer les VIs
    d'une version antérieure de LabVIEW (8.0 par exemple) et de les mettre au bon
    endroit pour qu'ils apparaissent dans LabVIEW 2010. Un petit MassCompile sur le
    répertoire sera nécessaire.
    Benjamin R.
    R&D Software Development Manager
    http://www.fluigent.com/

  • NI Motion Assistant LabVIEW Code Generation Error

    Hello, the following is my current setup:
    NI PCI-7334 motion control board
    NI UMI 7774 splitter board
    3 x NI P70530 Drives
    3 x NI CTP12ELF10MAA00 Stepper Motors
    3 x Power supply units for drives
    LabVIEW 2010
    NI Motion Assistant 2.6
    Motion and Automation Explorer 4.7
    I have built a three axis motion system that I am trying to configure with labview. After verifying that everything was set up correctly, I opened MAX, updated the firmware to my motion control board, and intitialized the controller. Since then, I have created many basic programs using the Motion Assistant Software to test the movement of my device. Everything works fine while using the Motion Assistant software (I have three axis movement, multidirectional control, and can perform various straight line and arc moves). My problems begin when I try to use the code generation feature.
    When trying to use the code generation feature to output a labview diagram, I run into a problem where a dialog box pops up and says "Find the vi named ...."
    Some examples of the names that come up are: Configure Vector Space.flx, Vector Space To Control.flx, Motion Error Handler.flx.
    To be clear the program in Motion Assistant that I am trying to export to LabVIEW code is composed of two individual steps. One that tells X,Y, and Z motors to move forward 25 revolutions, and one step that tells them to move backwards 25 revolutions.
    I have made many other programs in Motion Assistant that run fine, but I always receive similar errors when trying to use the code generation feature to export to LabVIEW. Is there something that I can do to solve my problem?
    Thank you for your help.

    Hi Joe,
    I am using Ni-Motion Assistant 2.6, Ni-Motion 8.1, and Motion and Automated Explorer version 4.7.
    The code I posted is supposed to tell Axis 1 to move 40 revolutions at 400 rpm. It works fine in Ni-Motion Assistant but when I try to generate a LabVIEW diagram I receive the following error, "Find the VI named 'Motion Error Handler.flx'". I have had it search my directory, as well as the disk that I installed both LabVIEW and Ni-Motion but no luck. Thanks for your help.
    Attachments:
    1111.vi ‏9 KB
    1 axis movement.zip ‏8 KB

  • In-browser LabVIEW MathScript Online Evaluation is now in beta...

    MathScript Online Evaluation Beta is Live!
    http://www.ni.com/mathscript >> Test Drive LabVIEW MathScript Today
    National Instruments LabVIEW MathScript adds math-oriented, textual programming to NI LabVIEW. You can use the MathScript Online Evaluation to test your scripts in MathScript before you purchase or download the LabVIEW development system.
    Free online utility generally compatible with widely used m-file script syntax 
    Easy-to-use interactive script prototyping environment 
    Streamlined algorithm development for Math, Signal Processing, and Control Design
    http://www.ni.com/mathscript for more information

    I already owned 10 copies of MathScript as part of the NI Developer Suite.  All ten Serial Numbers were, and are now, currently on SSP.
    MathScript was taken away from me as part of the LabVIEW 2009 Upgrade.
    Everybody that owns Developer Suite and MathScript and has a current SSP has had their MathScript taken away from them as part of LavVIEW 2009 upgrade.
    They will need to repurchase MathScript again.
    Shame on you NI.  This is appalling and horrific. 

  • Can I have both LabVIEW 8.5.1 and 8.6 on the same computer

    Is there some limitations.. What are the known problems...
    Does it mean, for instance, VISA is now the version with 8.6, and that I have to validate all my existing VIs in 8.5.1 once I install 8.6 on the same computer.
    Thanks
    [email protected]

    Hi Rhaj,
    If you are concerned about driver/LabVIEW compatibility across different LabVIEW versions, you can always check the readme files to see which LabVIEW versions are supported by the driver.  To reiterate what Dennis said, don't install multiple versions of drivers, but you can have as many LabVIEW versions as you wish on one computer. 
    Cheers, 
    Marti C
    Applications Engineer
    National Instruments
    NI Medical

  • Can anyone give me a LabView program to do impedance spectroscopy (capacitance-frequency) with a HP4284 LRC interfaced to a probe station?

    I am trying to measure the frequency dependent dielectric function of some polymer systems.  Our group has a HP4284 LCR meter interfaced to a probe station, however we lack the LabView code to perform frequency dependent capacitance measurements (i.e. electrical impedance spectroscopy).  Any help is much appreciated.  Cheers!
    -Kwami

    First, study the manual and learn how to do a measurement manually. Then, download the driver (LabVIEW Tools>Instrumenation>Find Instrument Drivers), install the project style driver. Next, look at the LabVIEW examples for it (Help>Find Examples>Hardware Input and Output>Instrument Drivers>LabVIEW Plug and Play). Study the functions in the driver with Context Help turned on. Look at the block diagrams to see what commands in the manual each function implements. Decide which functions/commands are necessary to duplicate your manual test.

  • Stop running LaBVIEW at the specific time

    Hello....I am newbie in LabVIEW...I want to use the LabVIEW software to analysis the data get from the real time experiment...Besides that, i want to save the data in the notepad file with the file termination at the specified interval time using Write to measurement file (block diagram)....
    My problem : how can i stop the collecting data in the notepad file at the specific time???...for example, i want to take the data only for 30 minutes in the real time experiment with file termination interval is 10 minutes.....so, only 3 data is saved in notepad file.h..
    Here, I attached the LabVIEW program that I already modified and combined with PIco 3206 (Driver LabVIEW)
    so.....somebody can help me????
    plizzzz.......
    Attachments:
    PS3000_Block_1_Unit_7.1.llb ‏532 KB

    Just use the Elapsed Time Express VI in your loop to see how much time has elapsed since the loop started. When that time has exceeded 1800 seconds, stop the loop. Or to do three 10 minute intervals, wait until 600 seconds has elapsed, then set the Reset input to true and write to file. Repeat three times and stop the loop.
    The installed LabVIEW help for this VI should link to an example that can help you get started.
    Jarrod S.
    National Instruments

Maybe you are looking for