can't set up NI-4070 DMM for use with IVI

[rjohnson]

Hi.

I'm just starting to use IVI drivers to control my instruments.   I've been able to successfully set up and use the HP34401A and the Fluke 45.

However I can not seem to get the NI-4070 to work.   I have been using the card successfully with the "nidmm.h" library functions, and it's working just fine.   And it is listed in MAX under both 

NI-DAQmx header, as NI PCI-4070 "Dev2"

and

PXI System header, as PXI3::13::INSTR (PCI-4070)

my problem is this:

when I try to create an IVI configuration for the NI-4070, there is no corresponding "Driver Session" for this instrument.   I have installed the latest v2.9 driver, which is supposed to be the latest IVI driver for this device.  

in case it matters, my environment is LabWindows/CVI v8.5.1 and NI MAX v4.5.0f0, on a WinXP machine.

this has had us puzzled for some time, and not sure how to proceed.   any advice will be greatly appreciated.

thanks

[NathanT]

Hello rjohnson,

       When using the IviDmm Class driver, you need to use the DAQmx name for your device in the driver session's hardware tab.  If NIDMM did not create a driver session for you, it is easy for you to create one by right clicking on "Driver Sessions", choosing "Create New" then add your hardware asset and choose the correct software module.  Make sure to save the changes so that they are applied to your IVI configuration.

Cheers,

NathanT

[rjohnson]

yeah, i had already done all that.

the problem, i've since found, was that the resource descriptor was wrong in the IVI Driver Session, Hardware tab... the dropdown menu gave the PXI System name as the only option for this device to be selected in the resource descriptor column.

I had to instead manually change it to match the logical name that I gave it in the NI DAQmx Devices.  which was terribly un-intuitive, considering that the DAQmx device name wasnt an available selection for the resource descriptor, but the incorrect PXISystem name was.

well, whatever, it works now.    here's posting the solution in case someone else wanders by with the same issue.