HELP: convert instruments' drivers to Labview 6.0?
Anyone can help me to convert the drivers from labview 7.1 to 6.0? Or anyone can tell me how to do that. I appreciate your help . Thanks! send emails to [email protected]
Have a nice day!
Attachments:
hp8753x.zip 832 KB
Here it is.
Attachments:
hp89400_6.zip 1194 KB
Similar Messages
-
Help convert from 7 to labview 6.1
Hi,
Could anyone help me to convert the code to labview 6.1
Thankyou very much
Attachments:
ag663xxa.zip 503 KBYou can try creating a 6.1 driver yourself. All the IVI drivers are simple wappers around a Call Library Node Function into the DLL created in LabWindows/CVI. The LabVIEW driver is created from the Tools>Instrumentation>Import CVI Instrument Driver selection. Download the CVI driver and install it. The converter will require some files installed in the \VXIpnp\WinNT (.fp) and \VXIpnpWinNT\bin (.dll) folders.
-
Need help in converting old LabVIEW instrument drivers to new version.
Hello,
I just rented a Tektronix DG2020A data generator. I did not find any instrument drivers for the DG2020A on the Instrument Driver Network, although there are drivers for DG2040 that could be used to some extent. With the instrument, I also received a floppy with example programs. This does include LabVIEW drivers for the DG2020A. However, when I tried to load the VIs, I received an error message that the VI version 3.1 is too old to be converted to 7.1. Can someone at NI help with the conversion? It would be very useful.
Thanks.There is a driver available for the DG2020 on NI's site. Models supported are the DG2020, DG2030, and DG2040. Available in both 7.x and 8.x.
-
Why does visa write hang with Labview 2009 instrument drivers.
I'm having an issue with a code package that I'm running. The pacakge is very complex and was written by someone other than me. It runs fine while using the labview 8.5 drivers, however, when the 2009 instrument drivers are install there is a visa write call to an instrument where the software will hang up at the VISA write VI. I tried setting the timeout attribute but that makes no difference. I would expect that if the visa write did not work, that it would time out with an error instead of hanging up.
Some additional information. The instrument is an EPM which is on a GPIB bus with other instruments. When I place the EPM2000 on a serparate bus this problem goes away, but I want to be able to operate on the same GPIB bus.
Has anyone experienced a similar problem? What can I try to help troubleshoot the problem. I tried opening NI Spy but that shows no activity going on.Hi Steve,
My apologies, when you said instrument drivers I assumed you were refering to the individual drivers for your instrument. Were you refering to the VISA drivers? If so, the latest version of these is 5.1.1 which can be downloaded here: http://joule.ni.com/nidu/cds/view/p/id/2659/lang/en.
Also are you able to communicate with this device using the test panels in Measurement & Automation Explorer? There is also a tool called NI IO Trace (or it may still be called NI-SPY in 2009) that can be opened from MAX that monitors all GPIB commands sent and received on the machine. Getting a log of the commands when the hang occurs may help to diagnose it.
It is possible this issue could be caused by opening and closing the VISA reference frequently in the code such as in a loop iteration. Is this is case in your code?
Justin D
Applications Engineer
National Instruments
http://www.ni.com/support/ -
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 -
hi, can someone help me how can i connected my multimeter to my pc with rs232, because my computer can´t recognize the device, i mean the multimeter, is a multimeter keithley serie 2400, and i already downloaded all the drivers for labview even the VISA
Marco,
Here are some suggestions:
1) Check the manual the Keithley manual to see how to configure the RS-232.
On some models you need set Factory defaults to USER and turn on the RS-232.
Also there may be a setting for SCPI which you want on (probably on by default).
2) On your PC - open Device Manager. See if a COM port exists and is functional.
You must get this working before continuing.
You can set the COM port parameters by right clicking and selecting Properties.
(On some PCs the onboard ports can be disabled in the BIOS)
3) If step two was OK, open MAX (Measurement and Automation eXplorer).
On the left side, click on Devices and Hardware.
Click on Serial and Parallel.
Go to the COM port you found in Device Manager.
Open a VISA Test Panel.
Now I don't have one I can look at right now, so this is general idea:
Configure the COM port to match the Keithley settings (should be OK if step 2 worked)
Go to the (I think) Input Output tab (you want to send a command)
The command string input should already have a *IDN? entered, if not, type it in.
Click on the Query button to send the command and check the response.
If you get an ID string back (Company name, Model, FW Version ...) then it works.
(Disregard an error saying it did not get enough charcters back.)
I hope this helps,
steve
Help the forum when you get help. Click the "Solution?" icon on the reply that answers your
question. Give "Kudos" to replies that help. -
Est ce qu'on peut utilisé les NI visa et instruments drivers dans un seul diagramme labview
Bonjour,
Est ce qu'on peut utilisé les NI visa et instruments drivers dans un seul diagramme labview c'est à dire pour communiquer avec un instrument de mesure il est ce que il faut la communication avec lui o utilisant visa ouvrier et/ou le VIs qui fait la reste de tel instrumentHi ghabri,
I am not entirely certain that I understand your question as a whole, but I will do my best to answer your question in French.
Oui tu peut utiliser les fonctions de NI-VISA et les instrument driver VIs dans un seul diagramme LabVIEW. Les instrument drivers sont seulement les subVIs qui contiennent les fonctions de NI-VISA. Les instrument drivers utilisent les fonctions de VISA dans leur VIs pour programmer quelques fonctions qui sont specifique pour cet instrument. Donc, tu peux utiliser les fonctions NI-VISA tant que tu n'utilise pas ces fonctions dans une maniere qui va faire un conflit avec les instrument driver subVIs.
I hope that this answers your question. I would recommend posting this in the French discussion forums for better support in French:
http://forums.ni.com/t5/Discussions-de-produit-de-NI/bd-p/4170
Regards,
James D.
Applications Engineer
National Instruments -
I also do not see any support for Keithley 2420 Sourcemeters.
Hi Kristen,
If you search www.Keithley.com you will find an instrument driver for the 2420 device. Go to the "downloads" section and search for 2400.
I am not sure what you mean by Audioprecision instruments. If you had a specific driver in mind, I would check with the instrument manufacturer. Often times they develop and support the drivers since they know the instruments far better.
If you do not see the driver on their website, please submit a request at http://zone.ni.com/idnet97.nsf/instrumentdriverrequest/ and with the instrument manufacturer.
We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
If you would like to try developing your own instrument driv
er (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at:
http://www.ni.com/devzone/idnet/development.htm
Hope this helps out!
Best Regards,
Aaron K.
Application Engineer
National Instruments -
I am running Windows 98 on a laptop. AFter downloading the drivers for LAbVIEW 5.x and trying to open the VI tree in LabVIEW 5.0, I obtain the error message for about three of the VIs. One of them is the initialization VI.
I tried the same driver in Labview 6.1 and Win2K and didn't get any errors. One possible solution might be to use the IVI driver for the TDS754D. The command set should be almost identical, but if the driver queries for the model number it might complain.
-
How do I install instrument drivers in folders other than inst.lib?
I am trying to use an instrument driver I found from NI.com and I am having some issues with it. I want to put it into a source controlled location (that isn't checked in yet) but it appears that it wasn't built to allow it to be put anywhere other than the inst.lib folder. Are all instrument drivers written like this?
I got the LV2012 version below.
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=0203928FCCB74C96E0440003BA7CCD...
When I move it to our source controlled location I get "Warning: has been deleted, renamed or moved on disk" error messages. All I did was unzip the files from the zip file I downloaded to the source control folder. Is there a way to "install" these files to the source control folder instead of the inst.lib folder and have it work without an error message?
I just wanted to check this before I spend a lot of time making the library and project find the files.
Thanks.JoeWork wrote:
Would putting an "inst.lib" folder under source control help if it isn't part of the absolute path that the library is looking for?
Nope. They are looking in the special instr.lib folder inside of the LabVIEW folder.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines -
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,
Siddu1. 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. -
HP 54501A - Instrument Driver for LabView v.7 or v.8
Hi all,
I'm looking for HP 54501A - Instrument Driver for LabView v.7 or v.8. I have NI gpib/usb controller installed, but cannot control the scope via Labveiw.
The link I found at NI web site within drivers section seems to be broken so I couldn't download it!
Please, anyone, suggest/help!The link you were given works for me. You can try it again. The given link brings you to a page where the CVI and LabVIEW drivers are listed. the direct link to the LabVIW driver is http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E9455659CE034080020E748... .
-
Are drivers for LabView 5.1 only supported by the later models, 6.x and 7.x?
Thanks in advance for your help.
I'm confused by your question. Are you talking about hardware drivers (NI-DQ, NI-GPIB) or instrument drivers? You should be able to use current hardware drivers with older version of LabVIEW and you can (in most cases) use older hardware drivers with new versions of LabVIEW. For instrument drivers, NI only maintains LabVIEW 6 and 7 versions on it's Instrument Driver Network but I'm pretty sure maintains an archive of older versions if they exist. If you have a specific instrument driver that you need, make a request on this forum. NI might be able to provide an older version or someone can save it to a previous version. One or two probably won't be a problem but numerous requests might be a little out of line. At some point, you might want to consider a
n upgrade. There have been numerous improvements since 5.1 and upgrading is usually not a major problem. -
Where do you put instrument drivers and DLLs?
Recently I have been using instrument drivers to communicate with the test equipment. I have just been putting these drivers into the isntr.lib folder on the C drive. However, in the lab we have multiple PC's, so every time I start using a new driver I need to go around to each PC and install the same driver. This is a tedious process, and was wondering what everyone else does in this situation...
Is there any reason not to just store these drivers on the network? Since we are on this topic, I have also wondered the same thing about DLLs that some of my applications need to run, is there any good reason not to put these on the network too?
Is it okay to store LabVIEW native drivers on the network, such as DAQmx? And how about OpenG libraries?
Thanks so much for all your help
-AnthonyI've also been using Subversion for years and MS Visual Source Safe before that). Here's what I would recommend:
Install Subversion (http://tortoisesvn.tigris.org/) on all the computers.
Create an identically-named root directory to check out files to on all the computers (I use Source Code).
Create a subdirectory within Source Code called Drivers.
Whenever you need to update/add driver files, check them all IN to Subversion from your desktop computer.
Check out the entire Driver subdirectory onto the target computers. That will update any changed files.
While you're at it, you could create other subdirectories as well: DLLs, Utility VIs, OpenG, etc.
Greg
Certifed LabVIEW Developer -
How to add instrument driver on labview in Mac
Hi,
I used to use Labview on windows and there was a menu in Tools >> Instrumentation >> Find Instrument Drivers and then I was able to find the driver for the instrument I was working on and install.
However, since I've been using labview on mac, there is no such menu. It only takes you to the website where I can search and download the instrument driver in a zip file, but then I'm not sure how to install the downloaded instrument driver on the Labview in Mac.
Can someone give me a hint?
Thanks,Unzip and move the folder to instr.lib.
Maybe you are looking for
-
Just set up Apple TV on home network. Works fine for NetFlix but we can't stream I Tune libruary or digital photos thru it to our home TV as because of my wife's work we bypass COX and access the internet thru a VPN offered by her employer. Was told
-
I purchased an Epson EX71 projector last night and cannot figure out how to connect it to my Mac Pro. Do I need a special mac adaptor? I want to display photos and dvds from my computer on it. Also, the cord is too short, are extensions available? TI
-
In Notification make breakdown ticked default
Hi in breakdown maintenance i want to tick breakdown in malufunction data, but can i make breakdown box ticked as bydefault. how to do that setting? Regards Nishj
-
How to access HTTP Header from within Web service?
Hello, Is there a way to access HTTP header variables like CONTENT_TYPE, CONTENT_LENGTH from within Web Logic web service. I was able to get the HTTP header variable from within Apache AXIS services by calling context.getProperty(HTTPConstants.MC_HTT
-
I wanted to put some special character (it's in my country language) by using Unicode-UTF8 but I couldn't. Can u show me how to do this? What is the Unicode font? Is it "Arial"?.......Help me please