Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

How do I configureiDMM to work in Teststand 4 (IVI)?

Solved!
Go to solution
I'm trying to use TS IVI-C Dmm step validation and configuration using Agilent 34401A. I check that NI latest compatibility package it installed and latest IVI driver from Agilent as well. I configure the driver Ag34401 in MAX but not sure what to put in physical name and Configurable setting  tabs if any. I set a driver session and logical name but I'm not sure if input for virtual name or initial setting needed. Under Labview code the driver behave normally both in simulation mode and real mode. In TS Edit IVI Dmm it will work in simulation mode. When I try to work with the 34401 DMM it will init and change status to remote but will fail configuration or reset.I attach the NI spy errors file.

The compatibility test found many issues with the Ag34401.dll but I'm not sure if it means the driver has some problems.

 

Compliance TestClass: DMMSpecific Instrument: Ag34401Module Path: c:\Program Files\IVI\Bin\Ag34401.dllTest Date: 04-10-2009, 11:19:42   Compliance Test Summary: The driver is compliant with the Inherent capability group.  The driver is compliant with the following IviDmm groups:             IviDmmMultiPoint            IviDmmTriggerSlope            IviDmmDeviceInfo            IviDmmAutoZero ERROR: The driver is not compliant with the following IviDmm groups:             IviDmmBase            IviDmmACMeasurement            IviDmmFrequencyMeasurement            IviDmmSoftwareTrigger            IviDmmAutoRangeValue            IviDmmPowerLineFrequency The driver does not implement the following IviDmm groups:             IviDmmTemperatureMeasurement            IviDmmThermocouple            IviDmmResistanceTemperatureDevice            IviDmmThermistor Please help by supplying instruction or example. The TS example  for IVI is not working for the same reasons mentioned above. Thank you.Elik
0 Kudos
Message 1 of 5
(4,163 Views)
I've never used the IVI driver for this instrument but one thing you could try is the NI driver.
Message 2 of 5
(4,149 Views)

Thank you that sort it out. The NI works better then the Agilent driver.

Elik

Message 3 of 5
(4,144 Views)
That doesn't surprise me.Smiley Happy
0 Kudos
Message 4 of 5
(4,141 Views)
Solution
Accepted by topic author Elik

What did surprize me that it did not show up while coding in Labview. Everything was working fine until I've tried TS IVI-C.

Thanks anyway.

0 Kudos
Message 5 of 5
(4,139 Views)