I have a large program using many variables and lots of TDM data archiving. I am not using TDMS at this point and maybe I should. As an example, I take ~800 samples with two 4224 DAQs for a total of 1600 samples. This is stored in an array. When archived to disk, it gets added to other data for a large write. As a result of the mixing, each TDM write is 50 Channels wide X 800 repeats = 40000 data writes. This takes ~ 2 minutes to complete the write process. I have previously opened up a record and then store all the data via calling a "write" subvi in a for loop. The write subvi is the one that stores 50 channels EACH time it is called. After the data is stored, I close the record. OK, TDMS would probably make this a lot faster. The write process is my last part of the test I made. After that, it just more or less does some simple housekeeping and ghen exits.
My real question is: When it is doing its housekeeping (simple closings, resetting DIOs, etc). I have this WHITE SCREEN OF "BUSY" with nothing showing on the screen. It is 100% white. Nothing is harmed, no data impacted, no changes to the program. It is just like LV is taking a break or real busy doing something.....like maybe cleaning its own house before returning to normal.
I use the same housekeeping routines during exit for at least 8 other tests and this does not happen. The main difference between the other tests and the problem child is storing the mux data in the array and the extensive writes.
