Signal Generators

cancel
Showing results for 
Search instead for 
Did you mean: 

age82xx instrument driver did not install properly

I'm using an Agilent E8254A Signal Gen and control using GPIB & LabVIEW. I extracted the .mnu and .dll files to the C:\Program Files\National Instruments\LabVIEW 7.1\instr.lib\age82xx directory. When I open my vi LabVIEW tries to load age82xx_32.dll, but the only file for this instrument is age8253.lib. I've tried installing the driver from both the ni.com and agilent.com sites. Where do I find the .dll?
0 Kudos
Message 1 of 7
(8,546 Views)
I just installed the ag82xx driver on my computer and I can find all the VIs under Functions Pallette>>Instrument I/O>> Instrument Drivers, all the functions should work for all the supported modules.

Check the download instructions at the download page and make sure you have all the requried files installed.

http://sine.ni.com/apps/we/niid_web_display.download_page?p_id_guid=E3B19B3E9340659CE034080020E74861
0 Kudos
Message 2 of 7
(8,532 Views)
The vi tool bar works and I can place them, but they won't run. Do you have age82xx_32.dll somewhere on you PC. Or age82xx.dll?

I am using LabVIEW 7.1 and have VISA 3.2 and IVI 2.2
0 Kudos
Message 3 of 7
(8,530 Views)
The LabVIEW version of this driver does not have a .dll file. This driver is written in LabVIEW and only have the menu files. All the files you need should be included in the age82xx folder stored in C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib

If you can see the driver functions in LabVIEW, that means the installation is successful. Please be more specific on which part didn't run, did you get an error? Did you configure the instrument correctly? Did you input the right resource name? We need more information to help you with this issue.
0 Kudos
Message 4 of 7
(8,517 Views)
I have the same problem - I downloaded the driver, unzipped it, and copied it to "C:\Program Files\National Instruments\LabVIEW 7.1\instr.lib\".  The new sub-VI's appeared in Instrument I/O -> Instr Drivers -> age82xx, and I could insert those sub-VI's into my project.  When I inserted "age82xx Initialize.vi" into a blank project, I got the following error message:

age82xx Initialize.vi
  Virtual Instrument
    - The subVI expected to be at "C:\Program Files\National Instruments\LabVIEW 7.1\instr.lib\DLLs\age82xx.llb\age82xx VXIPnp Error Converter.vi" was loaded from "C:\Program Files\National Instruments\LabVIEW 7.1\instr.lib\AGE82XX\AGE82XX.LLB\age82xx VXIPnp Error Converter.vi".


The Run button changed to the gray Show Errors button.  I clicked that button, and I got errors for three VI's:

age82xx VXIPnp Error Converter:
     Call Library Function Node: library not found or failed to load
age82xx Initialize.vi:
     Call Library Function Node: library not found or failed to load
     SubVI 'age82xx VXIPnp Error Converter.vi': subVI is not executable
My Project.vi:
     SubVI 'age82xx Initialize.vi': subVI is not executable


I double-clicked "age82xx Initialize.vi" in my block diagram to show the Front Panel, then hit Ctrl+E to show the block diagram for that sub-VI.  I found a "Call Library Function Node" in the middle of the block diagram and double-clicked it.  I got these properties:

Library Name or Path:
     age82xx_32.dll
Function Name:
     age82xx_init
Calling Conventions:
     stdcall (WINAPI)
Parameter:
     Status
Type:
     Numeric
Data Type:
     Signed 32-bit Integer
Function Prototype:
     long age82xx_init(CStr Resource Name, unsigned short int ID Query, unsigned short int Reset Device, unsigned long *Instrument Handle);


It looks like at least this sub-VI needs a DLL named "age82xx_32.dll".  I would guess that most of the other sub-VI's in this library do too.  However, I used the Windows file-search utility to look for "age82xx" in all subfolders on C:\, and didn't get a single DLL.


From the diagnostic info above, It looks like this driver does need that DLL.  The problem now is where to get it.

Hope this helps

<END>
0 Kudos
Message 5 of 7
(8,209 Views)
This particular LabVIEW driver is actually just an interface to the Agilent IVI-COM instrument driver.  In order to use this driver in LabVIEW, you must download both the age82xx driver listed under the LabVIEW 7 section, as well as the Agilent driver linked under Third Party Installation.

The Agilent installation will install the IVI Driver needed, while the age82xx LabVIEW 7 driver includes the menus and VIs. 

Jason S.
Applications Engineer
National Instruments
0 Kudos
Message 6 of 7
(8,204 Views)
I found the third-party download page (URL: http://adn.tm.agilent.com/index.cgi?CONTENT_ID=722) and downloaded and installed the Agilent driver.  I still had the same problem as before, so I searched again for "age82xx.dll".  This time, I found one in "C:\VXIPNP\WinNT\Bin".  I re-directed a sub-VI to use this directory, and the "not executable" error disappeared.  Since I didn't want to re-direct every sub-VI in the library to the new folder, I copied "age82xx.dll" to "C:\Program Files\National Instruments\LabVIEW 7.1\instr.lib\AGE82XX".  A different sub-VI found it immediately, so I re-directed the first one again so it also uses the copy.  I still get warnings about loading sub-VI's from different directories and saving re-compiled LabVIEW7.0 drivers, but at least these drivers can run now.  Thanks, Jason.
0 Kudos
Message 7 of 7
(8,186 Views)