Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

niFgen_32.DLL

Where is the location of this dll. I running compliance package 3.3. The Call Function node spits out an error....although the 5412 PXI is connected.

""""

-1073807343

niFgen Initialize.vi<ERR>Insufficient location information or the requested device or resource is not present in the system.

If the resource descriptor is an IVI name, it must match the entry in the IVI Configuration Store in a case sensitive manner.

"""

0 Kudos
Message 1 of 6
(5,106 Views)
0 Kudos
Message 2 of 6
(5,098 Views)

now that I've located the dll, why would I continue to get the error messsage mentioned above. See the attached pics.

Download All
0 Kudos
Message 3 of 6
(5,086 Views)
What version of niFgen are you using? That initialize front panel does not look correct. The resource name should be a IVI Session type control and it should have an arrow on the right side to select from available resources. It looks like yours is a string. The version on my system that came with LabVIEW 2009 is 2.6.3.
0 Kudos
Message 4 of 6
(5,074 Views)

Running fgen version 2.3. Yes the labview code that calls the dll is old stuff probably LV6 or LV5. Not allowed to change that now. They use an alias name to call the pxi.

 

Here's a parallel issue, I had problems with NI-dmm too. I upgrade to ni-dmm 2.9 and the fgen (niFgen_32.dll) problem is now gone.

 

My problem with dmm persist. I started when I replaced the 4070dmm pxi with a 4071dmm. Since then the nidmm_32.dll spits out an error. If it matters, I'm using compliance IVI package 3.3... that support the 4071 card.

0 Kudos
Message 5 of 6
(5,066 Views)
OK, problem solved. I did not remove the "old" (grayed out) device (dmm4070) in NI-DAQmx in MAX. What a pain in the butt, just because I swapped out PXI cards. The driver update was probably needed anyhow.
0 Kudos
Message 6 of 6
(5,048 Views)