06-13-2007 10:08 AM
06-13-2007 09:28 PM
06-14-2007 11:57 AM
Thanks, that improved the performance of this vi by about two orders of magnitude. The application is now much more stable.
@Ravens Fan wrote:I think moving the open file, move to end of file, and close file out of the loop would certainly help. These functions could be associated with or built into your "determine new file" VI. Since the file paths get passed into the loops, you could pass them through with shift registers so that you can close them after the loops end.One other thing to look at is your initialize array and insert into array functions. I believe insert into array is one of the costlier functions. Build array would be better. And initializing a much larger array and using replace array subset is better yet. But if you wind up with more elements than you had originally initialized for, you will have to use build array to enlarge it. I would recommend searching the Labview forum for insert into array, build array, and replace array subset for threads that do a better job explaining the differences and advantages of each.
06-14-2007 12:18 PM
06-15-2007 06:41 AM
I could acces the files in safe mode. Once I got them all (around 500 files) moved over to the pc, everything worked again. Also newly created files were visible via ftp. So it was pretty much the amount of files that was the problem.
@Ravens Fan wrote:I don't know the answer to that. But the file I/O functions still work on that directory? Try a small VI to see if you can copy them to another directory and FTP to that. And use some file delete functions to empty out that directory and try FTP'ing to it again. That will show whether the issue is related to the files contained within it.