From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
LabVIEW
Append a string data to txt. file
Or open the file once, then without closing it, write to it consecutively. Pass the reference in a shift register. Close when done writing. This way the end position will be remembered and strings will be concatenated.
It depends on your application what's best: sometimes [open\write\close] is better, sometimes open\[write]\close...
Search LabVIEW like a graph! What does the while loop do? (Nothing)
What does the for loop do? (Almost nothing)
You can replace the for loop, build array, array to spreadsheet string and concatenate by just a concatenate. The for loop, build array, array to spreadsheet string don't do anything except add a new line to the DATA1 string.
Why use a build array to go from 1D to 2D, and a for loop to go from scalar to 1D? The 2D array is not needed at all, but if you need it, just use two build arrays after each other. Or even better: an Initialize Array.
Now this all could be a placeholder for future work of course, but at the moment you have more redundant code then useful code.
The read will do the trick (set the pointer to the end). But it's a rough way to do it. At some point someone (future you) will think it doesn't do anything and delete it. At least comment why it's there.
With a Set Position, it will be clearer and potentially faster. The read might just really allocate memory and copy the data, you shouldn't depend on a compiler to remove that action...
wiebe@CARYA wrote:
The read will do the trick (set the pointer to the end). But it's a rough way to do it. At some point someone (future you) will think it doesn't do anything and delete it. At least comment why it's there.
With a Set Position, it will be clearer and potentially faster. The read might just really allocate memory and copy the data, you shouldn't depend on a compiler to remove that action...
Completely agree here. There is a lot that happens to "Read" a file. Just setting the file position is a lot less work for your application and is more clear what is happening.
@Vinaygowda wrote:
but placing the read option inside the loop it may keep memory like position of file I feel.
please correct me if I am I wrong
Yes, it does that. Indeed, it 'works'. Nothing wrong with that argument.
But it does more then you need, it might actually allocate memory, and a file read and data copy. This could become a problem if the file gets large. The read might take more and more time, as the file grows. Definitely not something you should want.
The Set Position on the other hand, has the same effect, but without the cost of the read. And it communicates to others (future you) what it does and why.
You only have to do it once, after opening the file:
Open
Set Position
For each value
Write
Close
As reads and writes will also set the position...
And of course the express VI "Write to Measurement File.vi" does this as an option, but I don't really recommend those express VIs, as they tend to need replacement sooner or later.
