Why do I need to call niDMM initiate inside the loop?

[joseospina]

Hi,

I'm trying to take DMM measurements continuoulsy.

By configuring the triggers to immediate and the sample and trigger count to 0 i would expect the DMM to start filling its buffer continuosly at its maximum rate, without ever getting back to the "idle state".

However, what I'm finding in practice is that I must call niDMM Initiate once again after taking each measurement.

Why is this occuring?

Does this mean that fetching the DMM will stop its multipoint acquisition process?

I attach two VI, one calling niDMM Initiate after each fetch and one which dont call it . From what I have understood i expected both to work, instead, only one of them do...

Could you give me some insight on the source of the different bahavior?

PS. I'm calling the trigger configuration because I will like to use an external trigger for the sample trigger in the future.

[LiciaP]

Hi,

DMM Initiate simply initiates acquisition, so it should not be used again in the loop.

I actually could not reproduce your issue (tough with a simulated DMM at the moment), both VIs run. What exactly do you mean saying that the VI without a second initiate doesn't work? Do you get some errors?

Try have a look at LabVIEW examples for DMM (in Example Finder, under Hardware Input and Output=> Modular Instruments=> DMM), in particular the ones for multipoint measurements and see if they work for you.

Bye!

Licia