Direct streaming to disk is much slower than the convinient one. Error 200560.

[Alexej_P]

Hi GerdW,

it is a problem - you will not be able to open it, it is in LV2010 32bit, Win7. In LV2015 I did not install NiDaqmx. I will look on another PC what they have in LV2014.

We are now in the process of reinstalling LabView and decide which version to choose. I remember that LV2016 run the program written in LV2014 (again from the LV examples) much slower (PXI high-speed digitizer).

It is not me who wrote that VI, it was National Instruments. I think that NI staff is the most experienced in the World in LabView.

Simulation is one thing, the reality is different.

[Alexej_P · Accepted solution]

Dear GerdW and others,

it was timeout settings in "wait until done". I set it to 101 sec and it run at 1Mss for 50 sec with no problems.

Sorry, it was really very stupid.

I will replace my complex "bad written" code of BN part by this simple code from "TDMS Logging - Log Data Only.vi"

The problem is solved. Sorry for disturbing you.

[GerdW]

Hi Alexej,

there is no problem to open your LV2010 VI with my LabVIEW version. The only problem is that NI renamed/replaced that example VI over the years and you refused to attach it right from the beginning.

And if you would have attached your VI immediately we also would have pointed you on this silly timeout value (as I noted in my previous message). You really should read messages more carefully...

[Alexej_P]

Hi GerdW,

I thought you asked me about my complex program with many VIs. It is too complex.

I realize now that I have chosen the wrong example to start. Now I am trying all TDMS examples and found the "TDMS Logging - Cont Log and Read Data". It is much better - it is a way I usually get data plus logging.

I am not a programmer but a scientist, I can't devote much time to programming. I am forced to do it - nobody will make it for me. I do everything myself - building setups, electronics and sensors, programming, evaluating data, writing articles.

I usually just find examples from Labview, test all of them for a maximum speed and modify for my purposes. I continuously modify my measuring program (started 15 years ago) trying to include everything and so it has grown into Frankenstein.

It should be rewritten completely but I have no time for it.

I tried to include everything possible - Hall sensors array with extrapolation on-the-fly, cycle averaging, filtering, RMS, ARV, DC, time averaging, Lock-in, BN, offset-drift compensation, compensation of the time delay between sampling and so on.

Sorry for disturbing you. 

[GerdW]

Hi Alexej,

---

@Alexej_P wrote:

I tried to include everything possible - Hall sensors array with extrapolation on-the-fly, cycle averaging, filtering, RMS, ARV, DC, time averaging, Lock-in, BN, offset-drift compensation, compensation of the time delay between sampling and so on.

Sorry for disturbing you. 

---

You forgot to mention the (old) LabVIEW version you are using.

All that stuff about which kind of sensor you are reading is not relevant when the problem seems to be solely the writing of data to a file…

You are not "disturbing", but when asked for relevant information you should attach a typical VI with typical data/settings when you have problems with this VI and its settings! (And don't forget to note the old LabVIEW version you are using: LV2010 is 10 years old now, so many things could have changed in the meantime. Names of examples VIs can be one of them.)