09-25-2012 08:59 AM
Hi JW-L3CE,
I'd like very much to supply the help. The 3.2 GB TDMS file is huge and I believe the data in such a huge TDMS file is valuable for you. Did you try to delete the .tdms_index file and then open the .tdms file again?
If it still doesn't work, now, the problem is how we can find a way to send the file from you to us for investigation and recovery. I'm not very sure whether the FTP sever of ni.com can hold this file, but please have a try:
1. Please zip your .tdms file and .tdms_index
2. Upload to ftp://ftp.ni.com/incoming
3. Reply here the name of your file
Please let me know if there's any problem if you can not upload the file. We can find out some other ways of I can contact our IT for help.
Yongqing Ye,
NI R&D
09-25-2012 09:14 AM
@YongqingYe wrote:
Hi JW-L3CE,
I'd like very much to supply the help. The 3.2 GB TDMS file is huge and I believe the data in such a huge TDMS file is valuable for you. Did you try to delete the .tdms_index file and then open the .tdms file again?
If it still doesn't work, now, the problem is how we can find a way to send the file from you to us for investigation and recovery. I'm not very sure whether the FTP sever of ni.com can hold this file, but please have a try:
1. Please zip your .tdms file and .tdms_index
2. Upload to ftp://ftp.ni.com/incoming
3. Reply here the name of your file
Please let me know if there's any problem if you can not upload the file. We can find out some other ways of I can contact our IT for help.
Yongqing Ye,
NI R&D
I can't seem to log in anonymously, or with my forum e-mail/password.
(using FireFTP within Invincea and logging into the link you provided)
09-25-2012 09:23 AM - edited 09-25-2012 09:23 AM
It is possible that the FTP client softeware is configured to use Active FTP instead of Passive FTP.
09-25-2012 09:24 AM
@YongqingYe wrote:
It is possible that the FTP client softeware is configured to use Active FTP instead of Passive FTP.
It's checked as passive.
09-25-2012 09:29 AM
OK. Could you please use Internet Explorer to open ftp.ni.com/incoming? And the page contains some instructions of how to use it.
And, maybe you can also try SmartFTP, http://www.smartftp.com/, I just tried it and it worked to connect to the FTP server.
09-25-2012 09:32 AM
@YongqingYe wrote:
OK. Could you please use Internet Explorer to open ftp.ni.com/incoming? And the page contains some instructions of how to use it.
And, maybe you can also try SmartFTP, http://www.smartftp.com/, I just tried it and it worked to connect to the FTP server.
I, unfortunately, don't have that luxury. We have this lovely software called Invincea which is a virtual machine and every other communication outside is blocked. So I'm stuck with firefox which can browse the ftp link, and FireFTP.
What login an I suppose to be using?
09-25-2012 09:36 AM
Anonymous is enough. Either Internet Explorer or SmartFTP (just goole it and download for free) should work. I tried it and I saw some big files there. Maybe a single 3.2 GB file cannot work, but some compression tool maybe can split the file into multiple smaller files and this can help us to receive the file from you.
09-25-2012 09:46 AM
@YongqingYe wrote:
Anonymous is enough. Either Internet Explorer or SmartFTP (just goole it and download for free) should work. I tried it and I saw some big files there. Maybe a single 3.2 GB file cannot work, but some compression tool maybe can split the file into multiple smaller files and this can help us to receive the file from you.
I tried. My company blocks any communications that don't originate from this software. SmartFTP and Internet Explorer simpy cannot get through.
It's not the file size. I can't even connect to the FTP server using FireFTP (which I'm stuck with)
Maybe I'll take it to an outside location. Funny how these crazy internet protection methods just force you to circumvent the system.
09-25-2012 09:50 AM
OK, no problem.
Thank you for your patience and please reply here and let me know when you complete uploading the file.
09-26-2012 08:55 AM - edited 09-26-2012 08:56 AM
Ok, I apologize. Our IT policies are rediculous. I'm still working on getting this file to you.
In the meantime, I figured out the the TDMS recovery VI above fixed the offset value. To this effect, I created the attached VI that checks all of the offset values. It works by incrementing through each TDMS segment using the offset value. if it doesn't find "TDSm" at the next position, it flags an error. My corrupted TDMS file passed. Not an offset problem. However, this doesn't check the data offset (a bit more difficult)
I also checked the first and last segment by appending them. The first appears to be metadata for the entire run. Appending them created a small TDMS file that contained 20 points. It opened fine.
My next step might be breaking this file into pieces.