Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

MAX and IVI-COM driver for Agilent Infiniium scopes

Hallo;
I've installed the IVI-COM driver from Agilent for the Agilent Infiniium Scope 54833A.  If I open the Physical Names tab  for that driver ( under IVI drivers->Advanced->Instrument Driver Software Modules ->Agilent Infiniium) MAX 3.3.1.3004  just freezes. Is there a workaround for that problem ?
0 Kudos
Message 1 of 5
(4,130 Views)

As I know the NI-MAX 3.3 had a bug that it hangs up when you access Physical/Virtual Name mapping page.  The problem occured only when the IVI driver contains Range capability on Physical/Virtual Names as iteration.  Simple non-iterative mapping did  not have the problem.

On my PC, the latest NI-MAX 4.0 fixed the problem.  I believe the latest NI-MAX 4.0 comes with NI-VISA 3.4, LabWindows/CVI 8.0, or LabVIEW 8.0.

0 Kudos
Message 2 of 5
(4,119 Views)
I've installed VISA 3.4.1 now. But MAX 4.0.0.3010 still shows the problem.
0 Kudos
Message 3 of 5
(4,107 Views)
What version of NI IVI Compliance Packege are you using?  You can check the version at the following registry.
HKLM\Software\National Instruments\IVI\CompliancePackage\CurrentVersion
 
My CompliancePackage is 2.3 and the NI-MAX 4.0 operation did show the repeated Physical Names without errors.  What I checked is our Kikusui4800 IviDCPwr IVI-COM driver, where tons of physical channel names are shown in the Physical Names tab using a range iteration in the XML.  NI-MAX 3.3 did have the prblem with it but 4.0 does not.
 
If possible, I will try the Agilent's IVI-COM driver that you are using.  Can you tell me the URL where I can download the driver?  Otherwise, can you attatch the IVI Configuration Store XML file? The file is normally IviConfigurationStore.XML located in the ProgramFiles/IVI/Data directory.
0 Kudos
Message 4 of 5
(4,099 Views)
Upgrading to IVI Compliance Package 2.3 fixed the problem.  
0 Kudos
Message 5 of 5
(4,083 Views)