Error -200279 How to fix it ?

[77maxmustermann]

Good morning Fox!

Im using a Ni usb 6003 which is attached to a function generator and to my pc.

The purpose of this programm is to show its signal and save it.

Sadly I've been getting this Error -200279

I have been fiddling with the samples rate and samples to read and that still hasnt fixed my problem

Any idea how to fix this error:

Any idea how to fix it ?

you'll find a picture + the labview program attached to this.

Thanks for taking the time to read my post.

[GerdW]

Hi Max,

I have been fiddling with the samples rate and samples to read and that still hasnt fixed my problem

Any idea how to fix this error:

Read more samples more often…

I can't open your VI (due to its LabVIEW version), but from your image I guess you are using the DAQAssistent.

• Configure the ExpressVI to read "continuously" requesting N/10 samples for a samplerate of N samples/s.
• Get rid of that additional wait in your loop: DAQmx is setting your loop iteration rate!
• Use AutoCleanup from time to time…
• Use "plain" DAQmx functions instead of the ExpressVI (that will help you in the long run…)
• Use the DAQmx option to have the DAQmx driver save measurement data directly to a TDMS file.
• Sometimes it helps to decouple DAQ from data saving using a producer-consumer approach.

Good morning Fox!

Welchen Fuchs grüßt du da?

[77maxmustermann]

hey it's you again ! thanks for helping me last time

I'm already using continious samples 100 samples / 1k Hz

I'll get rid of the wait function.

Heres a picture of the program as you couldn't open it

[77maxmustermann]

Getting rid of it made it worse :x. I'd get the error almost at the start.

By the way when I use sample on demand or don't save I don't get the problem

[GerdW]

Hi Max,

what about my comments on cleaning up and getting rid of the wait function?

Edit:

By the way when I use sample on demand or don't save I don't get the problem

This shows your 2nd ExpressVI is too slow.

What about my comments on using producer-consumer or have DAQmx save a TDMS file on its own?

Both is shown in the examples that came with your LabVIEW installation!

[77maxmustermann]

I did get rid of the wait function that's what I meant by making it worse :[.

What did you mean exactly by cleaning up :] ?

[GerdW]

Hi Max,

I did get rid of the wait function that's what I meant by making it worse :[.

See message above.

What did you mean exactly by cleaning up :] ?

AutoCleanup

[77maxmustermann]

My bad didn't notice you edited your comment

I'm still a newbie with labview what did you meant exactly with "plain" Daqmx function?

and sadly Icant save the data in TDML or save it directly from the DAQ.

This program is only a prototype Im using the find a solution for the problem.

My real program needs to safe 5-6 signals in the same Excel file using Write measurement to file

[GerdW · Accepted solution]

Hi Max,

I'm still a newbie with labview what did you meant exactly with "plain" Daqmx function?

Read this.

You should have taken some tutorials by now…

and sadly Icant save the data in TDML or save it directly from the DAQ.

Why not?

LabVIEW comes with example VIs - they explain that feature!

My real program needs to safe 5-6 signals in the same Excel file using Write measurement to file

Some notes:

• Excel can also read TDMS files. (NI installs an import filter…)
• You can save data to TDMS and create a converter to a (real) Excel file as a separate tool.
• The amount of signals is irrelevant for your question.
• To save data to Excel is a slow process: it is not recommended to do this inside a DAQ loop…

[77maxmustermann]

Kudos, using Excel was one of the causes as you said. now it crashes 4 minutes after the program starts instead of 20 seconds.

"The amount of signals is irrelevant for your question"

It is relevant as you told me to directly save the signal from the daq assistant meaning that each signal will be saved in different TDML. I want every thing to be saved in the same file.