Leaderboard

I'm sure others will chime in on their opinions. But some of the benefits I know of are... Direct DMA streaming from channels to disk including channel scaling and settings (my understanding is this happens without CPU intervention). Small file size with combination of binary and XML data. Reading TDMS data is quite easy using the TDMS palette, and you don't need to read the whole file to get the data you need. Grab the group, and channel and display it on a graph. Data is found based on names not column or row indexes. You can concatenate TDMS files using a binary copy function (copy /b in command line) and channel data will be appended. Using properties of the File/Group/Channel helps with organization and header data. Can be opened in Excel with a free add-on. (and looks decent where things like column width and font style on import, that you don't get on open in ASCII) Can store just about any data type. http://lavag.org/top...in-a-tdms-file/ Works nativly in DIAdem for automated report generation (not much experience with this when needed I have written my own in LabVIEW) Can be opened in Matlab (not much experience with this either but I heard there are drivers) Comes with a half way decent file viewer, which can be modified to your needs. I started using TDMS files for storing development and debug data. Then I started putting the actual data for what I was doing in there. Now when a test completes I can take that TDMS file, and generate a more formal looking report from it. This way there is a nice looking report with the data we care about at the end, but we still have the TDMS file which will contain all raw data. But when it comes down to it use what works for you. TDMS maybe overkill, or you might not feel comfortable using it, and that's fine. For me it works well, but it might not be right for every system.

Hello, I recently used TDMS files in a customer application and for that purpose I made VIs to write/read clusters containing parameters to/from TDMS file. These VIs are basically *copies* of the Read Variant Key.vi and Write Variant Key.vi from the OpenG Variant Configuration File palette so I thought it would be a good idea to add it to OpenG. Hopefully it could help someone. PS: haven't tested these VIs extensively (with all possible data types in LabVIEW) but they do work fine with big clusters containing 1D and 2D arrays. Read Property Key from TDMS File.vi Write Property Key to TDMS File.vi

Can y'all point me to a post somewhere describing the race condition with the Copy from Folder to Folder VI? I own the libraryn VIs, so I wanted to investigate to see if something is CAR-worthy.