My first glance here shows that TDM is an XML format. For a first step, the XML file loader I have written here, in conjunction with a suitable XSL file, might work without needing to do XOP programming.

--
J. J. Weimer
Chemistry / Chemical & Materials Engineering, UAH

Note that, from the licensing agreement that one must "sign" to download the DLL, you have to agree to this clause (emphasis mine):

2. Grant of License; Obligations. NI grants you a limited, non-exclusive right to download, use and distribute the TDM DLL pursuant to the terms and conditions of this Agreement. You may use the TDM DLL in your product in order for the product to access (i.e., read and write) TDM and/or TDMS files. If your application reads TDM files using the TDM DLL, you must support writing TDM files as well. If your application reads TDMS files using the TDM DLL, you must support writing TDMS files as well. You may distribute the TDM DLL as part of your product with such limitations as set forth below.

Does having a .dll mean, writing a TDM/TDMS loader/generator procedure/XOP is out of the question for Mac OS? Or does it mean, we just have to work a bit harder at it?

(not that I am intending to write something, just that I was struck with the question as a preface)

--
J. J. Weimer
Chemistry / Chemical & Materials Engineering, UAH

I just saw this post in regards to TDMS support in Igor. I am the Product Manager for TDMS and would be more than happy to talk with you integrating the DLL in your product. Please feel free to email me if I can help in any way. caroline.tipton@ni.com

Thanks
Caroline Tipton
Data Management Manager
National Instruments

Hi,

I recorded some data in SignalExpress 3.0, installed the TDM.xop, Igor 6.1 and tried uploading the file into IGOR but got the following error/output:

Loading "Voltage.tdms" from "F:UCLA Programming:TDMS Conveter:Sample Data:"
Created root:Voltage
Numeric variable datetime renamed to datetime0 because of a name conflict.
Numeric variable DateTime renamed to DateTime0 because of a name conflict.
Numeric variable DateTime renamed to DateTime0 because of a name conflict.
Numeric variable DateTime renamed to DateTime0 because of a name conflict.
Numeric variable DateTime renamed to DateTime0 because of a name conflict.
Numeric variable DateTime renamed to DateTime0 because of a name conflict.
DIAdem library error from routine during TDMLoadData: An invalid argument was passed to the library.

-Max

According to the NI documentation, the only built-in channel properties in TDM are the channel name and the channel description. Although the documentation does not mention it, I have a recollection of discovering the "unit_string" was also a standard channel property and TDMLoadData uses it to set the wave data units.

My understanding is that any other channel properties are user-defined. I'm not aware of any established conventions such as "wf_increment". At least none were mentioned in the NI documentation when I wrote TDMLoadData.

The TDM XOP loads user-defined properties into the wave note. The TDM Help file explains how to extract the user-defined properties from the wave note and use them for whatever purpose. To see this, execute:

DisplayHelpTopic "TDMLoadData"

and read the section entitled "Channel Properties".

Using the technique explained there, you should be able to do what you want.