...

Text files were used as a means of providing constant communication between the two VIs while running, as both can be changed and saved during each iteration, so that the data from the last iteration is exctractedextracted. This is the case for both text files.

Image Added

I recommend putting all your text files in a folder on the same drive as your LabVIEW codes (as shown above).

Response VI Text File, logfile.txt

Image Added

logfile.txt is the name of the data file produced by the Response VI, and namely contains the new valve position and the last recorded level in the tank. It also includes the enoch timestamp.

This text file is created in the Response VI and referred to in the Measuring VIs.

Only one logfile will ever be created once you have run the two programs successfully, as the new data is appended to the old data during each run. 

Measuring VI text file

Image Added

The measuring VI text file contains the date and timestamp, iteration number, new flow rate based on the valve position, the valve position recorded from the Response VI, and the new level created by the Measuring VI.

Development Text Files

Image Added

If either the Measuring VI or the Response VI do not already have a text file with data recorded saved on your computer, you will initially need to run with a development text file. This text file simply contains any number between 0 and 100 that will serve as the temporary Measuring VI text file containing the "level". With this as a replacement for the text file containing the new level data, you can run the two VIs and create a brand new logfile.txt. The next time you run the two VIs you can use logfile.txt with a new Measuring VI text file named after whatever your little heart desires. 

CoNgRatS oN maKiNG it To tHe EnD!!

Please indulge in this quality image of an inspirational kitten.     - E 

Image AddedThe End!