Instrument driver import for 2010

The instrument driver import plug-in is not available for 2010 yet. The work-around is obvious (import in 2009> copy>mass-compile) but a bit frustrating.
Jeff

Hi Brian
You're right. The 55292a usb expansion Module is from Agilent Technologies. It can house the Agilent 10887A calibrator board (ISA Slot) for the interferometer hp 5519A. Because we want to use this interferometer with a pc that has no ISA slot, we bougth that expansion module (3 years ago). Unfortunately the cd from agilent has no driver for this device. There's only a program on it. The other point is, that Agilent sold this device to another company and this company sold me this drivers (I think there are no others).
The problem is now, that Agilent don't support the device at all. The other company won't support the drivers running in LabView and national Instruments (Germany) also told me that they won't support me in this case.
But you were right about the COM library I think. I now can see the methods from the drivers, but they are grayed out (except two of them, see attachement).
Thanks for your offer to have a look at the dll. The problem is, that I had to buy this drivers and think the company wouldn't be happy to see me share them here... Can I send them by email to you? My adress is: [email protected]
Thank you very much for your help!
Attachments:
55292a.jpg ‏41 KB

Similar Messages

No longer able to import CVI Instrument Driver in LabView 2010

Hello,
I used to be able to download the Import CVI Instrument Driver Wizard in LabView 2009, but there is no wizard for 2010?
I also tried importing the driver with the shared library import, but then Binary, Slides and Rings do not come up with their values i.e. if my slide in CVI has 3 positions :
Description      Value
Item 1                 1
Item 2                 2
Item 3                 3
or if my Binary has
Description      Value
On                        1
Off                        0
they do not import the description into LabView 2010?
I tried copying the directories created by the 2009-wizard to the directories of 2010 i.e.:
from     C:\Program Files\National Instruments\LabVIEW 2009\resource\CVIFpConv
to          C:\Program Files\National Instruments\LabVIEW 2010\resource\CVIFpConv
and
from     C:\Program Files\National Instruments\LabVIEW 2009\project\_DriverCtoLV
to         C:\Program Files\National Instruments\LabVIEW 2010\project\_DriverCtoLV
and the wizard loads and runs until I specify a .fp file and then I get the error in the jpeg attached. When I try to open the block diagram (FC_RFL_Initialize.vi), it says you need a password to view it, so that stops my debugging.
Attachments:
Error using Instrument Driver Import Wizard in LabView 2010.JPG ‏88 KB

HI,
I downloaded the wizard and when I tried to import a driver I got this message shown below...(labview 2010)
Thanks...Ness
Attachments:
Error message.JPG ‏140 KB

I would like to know which instrument driver works for the Tektronix TDS 544A

I am trying to use TDS544A with CVI and downloaded the driver for TDS 540 and it didnt seam to work... should it? If not, which one will???

Hello,
Well, it appears that you are correct in that it must be somewhat different since you are getting the errors you described. Since that is the case and we don't have an instrument driver for that particular instrument, I would recommend one of two things. Try to modify the existing instrument driver to send the commands that your instrument expects, or make regular Visa calls to communicate with your instrument.
Also, I would encourage you to submit a request for the specific instrument driver you are interested in. I cannot guarantee when or if it will be created, but they will evaluate what can be done and get back to you. You can submit that request here:
http://zone.ni.com/idnet97.nsf/instrumentdriverrequest/
Good luck
with your Application!
Regards,
Steven B.
Applications Engineering
National Instruments

LabView 2010 - CVI Driver Import Wizard

I have previously downloaded and used the driver import wizard to create LabView VIs from a CVI driver. Specifically with Labview 8.x and 2009.
However the latest version of the wizard (v1.3) will not install with LabView 2010 and there isn't a newer one to download w- So the question is, does anyone know if there is an intention to update this wizard so I can use it with LV 2010 ?
Thanks

Hi,
I am having the same problem. Please let me know if this has been resolved yet.
I tried copying the following directories to labview 2010:
from     C:\Program Files\National Instruments\LabVIEW 2009\resource\CVIFpConv
to          C:\Program Files\National Instruments\LabVIEW 2010\resource\CVIFpConv
and
from     C:\Program Files\National Instruments\LabVIEW 2009\project\_DriverCtoLV
to         C:\Program Files\National Instruments\LabVIEW 2010\project\_DriverCtoLV
and the wizard loads and runs until I specify a .fp file and then I get the error in the jpeg attached. When I try to open the block diagram (FC_RFL_Initialize.vi), it says you need a password to view it, so that stops my debugging.
Attachments:
Error using Instrument Driver Import Wizard in LabView 2010.JPG ‏88 KB

Instrument driver for Tektronix TDS 640A

Is there an instrument driver available for the tektronixs TDS 640A. The Labview version is 5.1.

Here you can find Instrument Drivers: http://zone.ni.com/idnet97.nsf/browse/ but the most drivers are for LabVIEW 6 or higher. So you should update your LabVIEW-Version.
National Instruments Germany

Instrument driver for Hewlett Packard E3631A

Is there an instrument driver available for te Hewlett Packard E3631A?

oh, sorry for that, all intrument driver for LV5.1 can only download from the Cd, there is no more in the NI website. i attached one for you
Attachments:
HPE363XA.LLB ‏980 KB

Instrument Driver (66319B)

Hi all,
i need assistance on locating an instrument driver for model no: 66319B , Power supply unit from Agilent Technologies.
Currently using labview 8.0.
Thank you.

Exactly why do you think that the driver is not supported with
LabVIEW 8? Installing the 7.1 version should allow it to be opened and
saved. Do you get an error message or something else when you try to
open it?
Since it's an IVI driver, you can also create a 8.0 version directly. Look at the link here
about the instrument driver import wizard. All of the available LabVIEW
drivers for this instrument have used this wizard to create them.
Download just the CVI driver to do this.

Teststand call cvi instrument driver

I'm new to working with instrument drivers in TestStand. I'm trying to use TestStand to call a CVI instrument driver dll (for Agilent N5767 power supply), and then perform a specific function (init, set voltage, set current, etc.) All of the instruments in my test bench are connected via LAN, and they are configured in NI MAX too. I thought it was pretty straight forward, but I'm obviously missing something. Attached is the simple TS 3.1 seq file with the steps I'm trying perform.
Attachments:
N5700_on_off.seq ‏20 KB

Hi Bkoch1,
Please elaborate on the problem you are experiencing. I am able to open the sequence file you have attached and view your steps and on the surface, this seems like it should work just fine. What indications are you experiencing that it does not work fine? Have you tried setting breakpoints and using the Watch Window to monitor variables to ensure that they are being passed into the DLL? Please explain what the problem is and try to narrow down where the problem occurs and we would be happy to help you.
Regards,
Jackie
DAQ Product Marketing Engineer
National Instruments

Anybody has thermonics T-2500's instrument driver?

Has anybody developed the instrument driver (GPIB)
for Thermonics T-2500?

Hi,
Unfortunately, I was unable to locate a driver for your instrument at either thermonics website or at www.ni.com/idnet. I would like you to submit a request for this driver 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 driver (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
We also have a syndicate of third party vendors that specialize in National Instruments' products and services. Some of the
vendors specialize in driver development. I would suggest contacting one of the Alliance members at:
http://www.ni.com/alliance
An instrument driver is a collection of functions that implement the commands necessary to perform the instrument�s operations. In short, someone read the instrument user manual and implemented some of the functionality in a program for the end user. Instrument drivers are not necessary to use your instrument. They are merely time savers to help you develop your project so you do not need to study the manual before writing a program.
There are example VI's in LV on Instrument Connectivity. If you go to the Help menu >> Examples.. >> I/O, you will see a couple and Examples.. >> Fundamentals for File and String manipulation. I would suggest tweaking them to suit your application. Also the specific command that your instrument responds to can be found from it's manual.
Some useful resources for your application are
ni.com > NI Developer Zone >
Development Library > Instrument Connectivity
http://search.ni.com/?col=alldocs&layout=TechResources&ql=a , to search examples and knowledge bases
Hope this helps!
Aaron K.
Application Engineer
National Instruments

Import CVI Instrument Driver failure

Using the "LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers" utility, I successfully converted (wrapped) an IVI-COM instrument driver for use with LabVIEW 8.2.1. However, I have a customer who insists on using LabVIEW 6.0. When I attempt to use the "Import CVI Instrument Driver" tool of version LabVIEW 6.0, I get a crash: Failure: "funcmenu.cpp", line 1873. (Specifically, the error occurs after pressing "OK" to the "CVI Function Panel Converter" dialog and selecting the DLL.) The pop-up suggests to navigate to www.ni.com/failure for assistance in resolving the problem, but when the proper data is entered in that web page, it errors also.
1. Is it possible to do what I'm attempting to do?
2. Any ideas on what is causing my problem?
Thanks

The import tool for CVI drivers only supported IVI-C with LabVIEW 6. If there is no IVI-C driver available, you might be able to write C wrappers around the IVI-COM functions or manually write all of the ActiveX calls to the IVI-COM driver.

Import CVI instrument driver in 8.0

I have CVI instrument driver which just has some c funstions and it does not communicate to any instrument.
It always worked for me in 7.1.
After getting 8.0 and I had to download and install LabVIEW Interface Generator for LabWindows-CVI. It did not work.
I get following error.
The following instrument driver VI(s) cannot be created. This may indicate that the function in the CVI function panel (.fp) file is not consistent with VXIpnp and IVI standards. For example, the function has user-defined data types or has a duplicate function name in the .fp file.
But this works in 7.1.
What do I have to select in Class group?
Which step am I doing wrong?
LabVIEW Interface Generator for LabWindows-CVI is different from 7.1's built in generator.
Sheetal
Thanks.
CVI 2010
LabVIEW 2011 SP1
Vision Builder AI 2011 SP1

I've been playing some more and here is where I'm at.
I
downloaded DriverCtoL.exe from ftp.ni.com. I
forget where exactly I got it and I can’t find it again. I run the program and
it installs the tool/convert cvi to vi command. When I run the command and find
the 2533.fp file it asks for, I get and error message.
“Error
-43990 occurred at Not a valid function panel file.
Verify that
the function panel file is valid and attempt the conversion again.”
Is there
another way to convert the cvi to vi? Or, what step am I doing wrong?

"Import CVI Instrument Driver" doesnt work when parameter is viSession pointer

Why does "Import CVI Instrument Driver" menu selection generate a LLB that has VIs which have not been generated correctly when a VI function parameter returns a ViSession pointer. The only one generated correctly was "initialize", however, "autoConnectToFirst" was not. They both have similar prototypes in the .FP file. When I look at the block diagram of the init VI, there is a "IVI New Session" control, but in "autoConnectToFirst", there isn't. Therefore the session returned in Labview is 0, but the session returned in C (through debugging) is a valid session.

The strict answer to "Why?" is because we only implemented the special initialization code for the Initialize function. "autoConnectToFirst" is optional in VPP 3.2, and we chose not to implement it as a special case.
You'll just need to fix the Call Library Node in your VI wrapper to use the proper prototype. I'm not sure how best to handle the "IVI New Session" call; it really expects both a name and viSession, and "autoConnectToFirst" doesn't seem to return the name of the resource it chose. The "IVI New Session" function is what tells LabVIEW how to connect the VISA (or IVI) resource names with your viSession. You could call "VISA Find Resource" to get the first name and see if it's a supported device; this is supposed to match what "autoConnectToFirst" does.
Along those lines, you might be better off implementing "autoConnectToFirst" yourself in LabVIEW. I.e., call "VISA Find Resource", and loop through the results calling your "Initialize" function until you don't get an error.
Let me pull up a soapbox for a moment...
There's a common misconception that "Import CVI Instrument Driver" creates a perfect LabVIEW wrapper around a VXIpnp WIN or IVI-C driver with no manual intervention. The reality is that you will almost always have to do some manual fixups of the converted driver.
In LabVIEW 7, we improved the converter somewhat, and converting an IVI-C driver is now a three-step process: pre-processing the IVI-C driver, importing into LabVIEW, and then doing some programmatic fixups of the results. The resulting wrapper is better than earlier versions of LabVIEW, but it's not uncommon that you will still have to manually fix something up to make it a good, usable wrapper.
That's why we consider "Import CVI Instrument Driver" to be a tool for instrument driver developers. If a vendor creates an instrument driver for an instrument in C, it doesn't make sense for each end user to have to create the LabVIEW wrapper, including all the manual fixups.
Of course, if a vendor wants the best LabVIEW connectivity, they should write a LabVIEW-based driver. But if they're going to only write C- or COM-based drivers, they should create and distribute high-quality LabVIEW wrappers and not force end users to figure out how to do it on their own.
My two cents.
Brian

Importing Instruments Driver from LabWindows/CVI

Does anybody have got wintools_32.dll library ?
I need it to convert LabWindowc/CVI Wintools Instrument Driver to Labview.
Could you send it to me?
Romek.
[email protected]

Hi!
Thanks for your answer.
Exactly, I've tried to import LabWindows/CVI instrument driver to Labview.
This Instrument driver I've found here:
http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?p_guid=B45EACE3F04956A4E034080020E74861&p_node=DZ52176&p_submitted=N&p_rank=&p_answer=&p_source=External
During import procedure i was asked about wintools_32.dll library.
Personally I am interested in System Tray icons functionality of this driver.
I'm not sure that wintools_32.dll is Labwindows/CVI library, but i've searched Microsoft Windows pages with no results.
Regards.
Romek.

I have the G Drive 1 TB (GEN4 1TB) external drive purchased in 2010. I need to connect to my new MacBook Pro. I'm using the external drive for media storage of my video editing projects. Will a 800fw to thunderbolt adapter cable work?

I have the G Drive 1 TB (GEN4 1TB) external drive purchased in 2010. I need to connect to my new MacBook Pro. I'm using the external drive for media storage of my video editing projects. Will a 800fw to thunderbolt adapter cable work? I understand that using a USB port connection is not fast enough for video editing. I read somewhere the G Drives don't connect well to MacBook Pro.
thanks
larry

I doubt this can be relocated or moved so you might want to just repost in the macbook pro area.
MacBook Pro
https://discussions.apple.com/community/notebooks/macbook_pro
https://discussions.apple.com/community/mac_os?view=discussions
Can you afford a new Thunderbolt case and cable? any case with FW800 is going to be slow 72MB/sec and less, and any new 1TB drive is capable of 75MB/s minimum up to 125MB/sec.
Thunderbolt storage can of course when setup properly reach 100's of MB higher using multiple drives.
Use what you have for a system backup or for secondary backup storage.
you might be able to take the drive - most cases allow you to open and swap drives - and use this:
G-Technology 1TB G-DRIVE mini High-Speed Portable Hard Drive
or this:
http://store.apple.com/us/product/HB137VC/A/g-technology-4tb-g-raid-professional -high-performance-dual-drive-hard-drive?fnode=5f

Hi, Can anyone recommended software to import dvd to iMovies. I need to import about a dozen homemade DVD's and edit them into a single DVD comprising the 'best bits'. How best can I do this. I have an external hard drive available for the job

Hi, Can anyone recommended software to import dvd to iMovies. I need to import about a dozen homemade DVD's and edit them into a single DVD comprising the 'best bits'. How best can I do this. I have an external hard drive available for the job

You need to convert the VOB files in the TS-Folder of the DVD back to DV which iMovie is designed to handle. For that you need mpegStreamclip:
http://www.squared5.com/svideo/mpeg-streamclip-mac.html
which is free, but you must also have the Apple mpeg2 plugin :
http://store.apple.com/us/product/D2187Z/A/quicktime-mpeg-2-playback-component-f or-mac-os-x
(unless you are running Lion in which case see below))
which is a mere $20.
Another possibility is to use DVDxDV:
http://www.dvdxdv.com/NewFolderLookSite/Products/DVDxDV.overview.htm
which costs $25.
For the benefit of others who may read this thread:
Obviously the foregoing only applies to DVDs you have made yourself, or other home-made DVDs that have been given to you. It will NOT work on copy-protected commercial DVDs, which in any case would be illegal.
And from the TOU of these forums:
Keep within the Law
No material may be submitted that is intended to promote or commit an illegal act.
Do not submit software or descriptions of processes that break or otherwise ‘work around’ digital rights management software or hardware. This includes conversations about ‘ripping’ DVDs or working around FairPlay software used on the iTunes Store.
If you are running Lion or later:
From the MPEG Streamclip homepage
The installer of the MPEG-2 Playback Component may refuse to install the component in Lion. Apple states the component is unnecessary in Lion onwards, however MPEG Streamclip still needs it. See this:
http://support.apple.com/kb/HT3381
To install the component in Lion, please download MPEG Streamclip 1.9.3b7 beta above; inside the disk image you will find the Utility MPEG2 Component Lion: use it to install the MPEG-2 Playback Component in Lion. The original installer's disk image (QuickTimeMPEG2.dmg) is required.
The current versions of MPEG Streamclip cannot take advantage of the built-in MPEG-2 functionality of Lion. For MPEG-2 files you still need to install the QuickTime MPEG-2 Playback Component, which is not preinstalled in Lion. (The same applies to Mountain Lion even though that has it preinstalled.) You don't have to install QuickTime 7.

Instrument driver import for 2010

Similar Messages

Maybe you are looking for