Problem 1: A lot of duplicated code. Duplicated code should be placed in a subVI and the subVI reused. It may even be possible to combine similar operations into For Loops where you loop over an array to repetitively do the same things to different pieces of data.
Problem 2: A lot of Express VI's. Express VI's make it easier to start a program, but they have some additional overhead that doesn't exist if you used lower level functions.
Problem 3: A lot of File writing in the loop. Writing data to a file is slower than execution of a program in CPU. With the multiple file writes going on, they are all going to compete for the same resources thus compounding the problem. You should use a producer/consumer archtitecture to pass the data to another loop that does the file writing by way of a queue. That will allow the producer loop to run faster. However, if the producer loop runs faster than the consumer can use the data, you will eventually run into problems.
Problem 4: You are creating a new DAQ task on every iteration of your loop. You never close a task. And you are doing this for multiple channels. Tasks should be created before the loop, used in a loop, and closed out after the loop is finished. Creating tasks takes time, and by creating them without closing them repetitively, you are eventually going to run out of resources and crash the computer. The numerous tasks should all be combined into a single task.
Problem 5: What is the purpose of the Collector Express VI's that are set to collect a single sample?
More ... ?
