Using default DAQmx read, read all, (default -1) returns NOTHING, no data, no samples
The inconsistency shown here is that wiring, say for an example 1000 into the DAQmx read, will result in retrieving the first 1000 samples from when the DAQmx was started.
Excellent, works as published...
Now wire -1 or nothing (-1 default) into the DAQmx read, this will result in retrieving NOTHING...
VI as documented: " If the task acquires samples continuously and you set this input to -1, this VI reads all the samples currently available in the buffer."
Note: This effects ALL remote DAQ device, i.e. USB, Ethernet, cDAQ, ...etc, including simulation works fine and actual does NOT...
Over 3 weeks with NI support confirmed, and I quote: "it is actually expected behavior"
Don't you love it when simulation works different then the real deal, plus words like "available in the buffer" mean differently when asking for ALL .vs. requesting a defined amout???
Granted this is just a very basic example, just proof...