08-15-2011 04:34 AM
Hi All,
I have an interesting observation to make, whilst trying to debug / resolve issues with my cRIO's (2 9074 units) I resorted to creating data files which were saved to the cRIO hard drives, used FT Protocols to transfer the files from cRIO A to cRIO B, then used the FTP to transfer all the files to my NAS drive.
Now I know that this isn't exactly a good way of doing this, but I have been having some real issues.
Anyway, what I have noticed is that the files which come from cRIO A are always corrupt, where as the files which come from cRIO B are not. The two file save methods are the same, identical, so it must be something to do with the fact the files go through the FTP process twice. I have swapped the units over to no avail, has anyone experienced anything similar??
Cheers,
Dom
08-17-2011 05:15 AM
Hi Dom,
Thanks for posting this, it certainly sounds like an interesting issue.
So just to clarify, you are logging a data file on each cRIO (A & B), transferring the file on A by FTP to B and then finally transferring both files by FTP from B across to your NAS?
Could you possibly provide the project files and vi's for both cRIOs so I can look at how this is configured and attempt to replicate the issue?
Many Thanks.
08-17-2011 08:06 AM
Hi Paul,
This is the case (Although I am also investigating 2 or 3 different methods of implementing the same thing).
I have attached the program, you will need to sort some sort of GPS feed, or comment out the code, but I use the GPS to set up the file system so there might be a bit of rework before you can check it properly.
Dom
08-18-2011 06:30 AM
Hi Dom,
From looking through your code I've found something which may be part of the problem. Due to the differing character manipulation which can occur when transferring data via FTP in the ASCII format, it would be more ideal to perform all the transfers in raw binary. This could be causing the file corruption you are seeing from the first cRIO.
It might be worth giving this a try and seeing if the same issue continues to crop up.
Let me know if this helps.
08-18-2011 07:53 AM
I'm not sure I understand,
The files are being written as binary files using the "write to Binary File" vi.
Are you suggesting I convert the data to binary, before sending it to the Write to Binary File vi?
Dom
08-18-2011 08:07 AM
Within your File Removal vi, you configure the file specifications cluster with a false boolean value which then sets up the FTP Store Vi's to transfer as ASCII rather than binary. If you change this to true in all your file specifications to ensure all the FTP transfers occur as pure binary it will eliminate any character manipulation issues which may be corrupting your data upon it reaching the NAS.
Let me know if this helps.
08-18-2011 09:26 AM
Hi Paul,
I did what you suggested but ended up with the same error, 116.
Cheers,
Dom
08-19-2011 04:10 AM
Discussion continued on this post.