Does a DAQmx Occurence Config vi exist?

[PacMan]

I am replacing Traditional DAQ calls with DAQmx calls. I need to replace the DAQ Occurence Config vi, but can't find a equivalent on in the DAQmx pallette. Does any replacment VI exist?

[rolfk]

---

@PacMan wrote:
I am replacing Traditional DAQ calls with DAQmx calls. I need to replace the DAQ Occurence Config vi, but can't find a equivalent on in the DAQmx pallette. Does any replacment VI exist?

---

As far as I know, no! Occurrences were not ported over, probably because they don't fit as easily into the DAQmx architecture. Also Occurrence support in Traditional DAQ while potentially interesting, was very limited and not improved over at least one whole major release number of NI-DAQ.

You could probably get away with simulating a DAQmx occurrence using lower level functions or the much more functional analog or digital trigger support in DAQmx.

Rolf Kalbermatter

[Jason_S]

The hardware timed loop in LabVIEW 7.1 can usually perform the same functionality that you might get from using occurences with traditional DAQ. Check it out.

Jason

[BoxTrooper]

In DAQmx you can configure and use the DAQ timing or triggering as a source to drive other things such as to time a timed loop or to set an external occurance or notify or queue. Look under the sub-pallet "DAQmx Advanced Task Options" to see what inter-related control you can weave.

[DavidMaidman]

Hi,

I have been looking in to a similar problem as this original post. I am upgrading some applications that use Traditional DAQ to DAQmx and have come across the DAQ Occurrence Config.vi. In this application it is being used to 'send the VI to sleep' until the acquisition task is complete allowing LabVIEW to execute other VIs. Once the acquisition completes the VI 'wakes up' and continues.

I have taken a look in to the "DAQmx Advanced Task Options" sub palletes but can't see anything that does the job.

In DAQmx I know that a VI pauses at the analogue input read until the number of samples requested are available (r a timeout occurs), is this strictly the same?

Any pointers are appreciated 

[DavidMaidman]

Looked in to this further and have come to the conclusion that the DAQ Occurrence Config.vi is no longer needed in this instance as the DAQmx read VI seams to have the functionality automatically built in to it

[PacMan]

Thanks.  I found that I could use the DAQmx calls and essentially duplicate the Trad DAQ occurence by using Edge Triggering on the DAQ device.