From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
11-16-2016 06:45 AM
We're gathering data from TestStand and currently placing it within the db. No schema per se. The original developers just used the default settings. I'd like to switch over to tdm (or tdms) and use DIAdem to analyze the data and possible also generate the reports. As we don't have vast amounts of data that requires streaming, the tdm would be fine. There will however be a large number of files in multiple folders.
Is there any difference from the DIAdem perspective whether to use tdm or tdms files?
11-16-2016 07:10 PM
Handling of TDM and TDMS files in DIAdem is comparable. It depends on the situation respective use case, which of the two is "better" suited.
LabVIEW and/or TestStand can better handle TDMS files, such that in your specific situation TDMS might be the format of choice.
11-17-2016 02:02 AM
Hi dgdi,
like already mentioned in the last post, it shouldn't matter much, but there are some significant differences between the file formats, which you find listed here:
TDM versus TDMS - LabVIEW 2013 Help - National Instruments
http://zone.ni.com/reference/en-XX/help/371361K-01/lvconcepts/fileio_tdms_tdm/
The main difference is that TDM only supports Windows OS while TDMS also works on other operating systems, which becomes important when you want to include platforms like the cRIO hardware.
Buttomline: I would recommend TDMS, when you can live with the fact that you can't delete Data from the file with LabVIEW, you have to use DIAdem for that.
Best, Niko