Agilent 33220 USB Application and Runtime Engine

[Marc10k]

Hello

Ich used the example codes from NI for the Agilent 33220 function generator "Getting Started.vi". It works fine on my computer with LabView 7.1. But when I run it on another computer without LabView installed, it wont work. I have installled the iolibs suite 14 from Agilent and the drivers for vxipnp and ivicom on the other computer. I also generate an Installer.
I am not really sure with options I have to choose for the Installler. Do I need the Active-X server? What are the correct settings in the installer options or settings? Or is there other important settings I forgot about?

Cheers

Marcus
 

[Marc10k]

I forgot to mention that I get the following error message when I start the exe on the other computer after installing it.
Error 1073807343 occurs at VISA: opening ag33xxx - initalize.vi -> ag33xxx - getting started.vi
possible errors: VISA (HEX: BFFF0011) not enough information about memory or device or resource not available in system.
I am using the german version of LabView so the text might be a bit different than on the english version.

Marcus

[Makoto]

The error code 0xBFFF0011 is a VISA error - VI_ERROR_RSRC_NFOUND.  I believe it is a VISA problem.  Does the target PC insall Agilent IO Libs Suite 14 alone, without installing NI-VISA?  Multiple VISA versions from different vendors can't be installed at a time, otherwise similar errors may occur.  Try to operate the VISA Assistant utility from Agilent that comes with the IO Libs Suite 14, such as sending a simple "*IDN?\n" query on the real VISA address such as "GPIB0::<address>::INSTR".

Also if your app passes a Logical Name for the IVI driver's "Initialize.vi" call, instead of passing a real VISA address, you must properly configure the Logical Name, so that it can be redirected to a real VISA address through the Driver Session, Software Module, and Hardware Asset configuration.

このメッセージは　08-31-2005 01:16 AMに Makoto が編集しています。

[Marc10k]

Hi

It was a driver problem. I reinstalled the io libs and then it worked.
After deinstallation of my exe from the target computer it seems to me that it deletes some important files. When I installed the application again the porblems occurs again. A new installation (repair) of the io libs works fine.

Marcus