Cannot Simulate NI PCI-4070 DMM

[Steve1]

The simulated 4070 DMM that was imported from the computer with the 4070 card does not work as a simulated device.

Installed on the simulation computer is DAQ8.0, and NI-DMM. The simulated SCXI1000, and 1127 modules functions work when tested in MAX but when self test is clicked for the simulated 4070 card the error is "The specified device is not present or active in the system. The device may not be installed on this system, may be unplugged or may not be installed correctly".

How can get the 4070 to be simulated?

Thanks,

Steve

[Mark_S1]

NI DMMs do not support DAQmx simulation so the simulated PCI-4070 created by the import step is incorrect.  The correct way to simulate the PCI-4070 is using NI-DMM and IVI.  You can use niDMM_InitWithOption, or if you don't want to change your program, create an IVI simulated device in MAX and use that device in your program.

Mark

[Broken_Arrow]

I would like to bump up this old topic, because I am also having trouble simulating a 4072, in my case a PXI-4072.

Under INI drivers in MAX, I'm seeing the nisDMM items under Simulation, but when I try to Create New... NI-DAQmx Simulated Device... none of the DMM's are in the list of devices to select.

Mark S. said "NI DMMs do not support DAQmx simulation" ?, and then goes on to describe that it can be simulated in IVI. So, I'm a bit confused.

Thanks,

Richard

Message Edited by Broken Arrow on 11-26-2007 12:19 PM

[kirsch]

By DAQmx simulation, Mark means that you can create a Simulated Device in MAX and then use it through the API. This is not supported in the current NI-DMM driver.

In order to use IVI simulation, this is what you do: replace niDMM Initialize with niDMM Initialize With Options. This VI  (function) takes in an extra Option String parameter. Wire "Simulate=1,DriverSetup=Model:4072;BoardType:PXI" and run your VI normally. This will use a simulated device instead of a real, physical device. When using IVI simulation, you don't need to go to MAX to configure anything beforehand.

Hope this helps make things clearer.

[Broken_Arrow]

Thanks Marcos.

Yes, I tried that, with bad results - it said the device didn't exist. (I don't think it had "Model:4072" number in it, so I'll try again). Also, I'm not sure what to do with the PXI Slot setting (i.e. the resource name) because if it's a Simulated device, don't you still have to give it a slot number?

Also, what does that string look like sans emotocon? ( )

I'll keep plugging away, thanks.

[kirsch]

The emoticon should actually be a colon followed by the letter P (as in PXI).
As for the Resource Name, you can use anything. In reality, non-simulated devices get a default that looks something like "PXI1Slot3" but you can rename them to anything in MAX (this does not apply to legacy devices like the 4060 though).

Marcos

[Broken_Arrow]

That did it! Works great. 125mV out of thin air.

It was bad text in my input string. I didn't realize it had so many possibilities besides the default "Simulate=0,RangeCheck=1,QueryInstrStatus=0,Cache=1" that gets created when you create a constant from it.

Thanks again.

[JGibson5]

I'm a newbie to Labview and NAQmx, and have the same error for all the simulated devices in MAX as the one mentioned by Steve at the beginning of this thread.  I've tried importing the configData.nce but the file wasn't found.  I'm at Labview version 8 and DAQmx version 8.3.  Thanks for any help.

[Dennis_Knutson]

Have you read the entire thread? You do not have the ability to simulate an NI DMM with DAQmx. You program an NI DMM with the NI-DMM software. If you want to simulate the DMM, then you have to use IVI. You also need to have the IVI compliance package installed. That, I believe, comes on the NI-DMM driver CD that came with the instrument. You can also download both from the Support link above.

Once you have the correct software installed, opne MAX and right click on IVI. The help will walk you through the process.

[JGibson5]

My original problem started with a PCI 6221 and 6229 not any DMMs, and I noticed it for all the simulated devices I can create in MAX.  I'm guessing my problem is not exactly the same as Steve's although I have the same error message.