Error-200077 at DAQmx

[Kevin_Price]

Two suspects I see:

1. Due to the inherent latency of the USB bus, I wouldn't expect *any* USB device to be able to be used as a Timing Source.

2. I don't generally use Timed Loops, but when I've dabbled it seems that the Timed Loop structure wants sole control over the resource that's used as a Timing Source.  I think you might get a conflict from having ctr0 used both as a Timing Source and also in another task.

I'm not 100% sure about either thing, but those are my "educated guess" suspicions.

An alternative to the Timing Source and Timed Loop might be to setup a DAQmx Event that you can service in an event structure with a regular While loop.  Again, not 100% what kind of "event" you would need so not sure it'll be a viable option.

-Kevin P

[hblin94]

Do you mean where it is gone wrong when running? As follows?

[GerdW]

Hi hblin,

Do you mean where it is gone wrong when running? As follows?

Kind of…

From your image it seems the error is generated before the DAQmxRead function.

You need to debug earlier upstream the DATAFLOW!

[RavensFan]

Actually that is showing a different error number now.

[hblin94]

I'm sorry, I don't know much about LabVIEW debugging. But, do you mean this?

[hblin94]

I pressed the "continue" button and then pressed the "Pause" button, which shows the error.

[GerdW]

Hi hblin,

so that DigitalCounter(Edge) is not supported by your hardware (or the combination with those other tasks).

What do you want to achieve with this DAQmx task?

[Elson9988]

Hi,

This error is occurring because:

1. USB multifunction I/O devices do not support hardware timed single point acquisition

2. Only PCI/PXI/PCIe/PXIe DAQ devices can support Hardware-Timed Single Point Sample Mode (HWTSP). 

For a complete list of supported and unsupported device, please refer to our documentation:

http://www.ni.com/product-documentation/54449/en/#toc4

In HWTSP, samples are acquired or generated continuously using hardware timing without a buffer. Because samples must be continuously acquired/updated and processed on a point-by-point basis, you need to use a fast, deterministic bus. The inherent latency of the USB bus itself does not provide enough determinism to allow this output mode, therefore it is not supported.