Company Events Academic Community Support Solutions Products & Services Contact NI MyNI

The TDM Data Model

LabVIEW 2013 DataFinder Toolkit Help

Edition Date: June 2013

Part Number: 372745E-01

»View Product Info

The TDM format is designed to capture and manage all the important information surrounding a measurement or simulation, assuring that the data is self-explanatory, reusable, and requires no additional explanation to recreate the conditions under which it was captured.

The TDM data model defines 3 hierarchy levels: Root objects, Group objects, and Channel objects. Each file has a single root object, and any number of group and channel objects. For example, in one file you can save the original data in group 1 named “raw data”, and create a second group called “analyzed results” to separate the analyzed results from the original data. Within each group the measurement or simulation data is saved in channels which are waveforms or 1D arrays of numeric, date/time or string data types.

Each of the three levels has a set of predefined properties. You can add an unlimited number of freely definable properties of data type string, numeric, integer, and time. For example, you may want to save the sensor id as a property associated with each channel, and save the UUT number at the root level.

The following characters are not supported for custom property names throughout the whole TDM platform:

., :, ,, ;, ', \, @, <, >, #, [, ], %, (, ), {, }, |, *, ?, =, !, ", ^, $, &, +, -, /, and a space

These characters may be replaced with "_" in the property name.

Also the following property names are reserved and may not be used for creating custom properties on file level:
author, channelgroups, children, datestring, datetime, description, environment, external_references, id, instance_attributes, mime_type, name, objecttype, parent, registercomments, registertxt1, registertxt2, registertxt3, timestring, title, version, version_date.

Additionally the DataFinder has the following property names reserved on file level:
createTime, dataPluginName, fileName, folder, indexStatus, modifyTime.

The following property names are reserved and may not be used on group level:
channels, children, description, equipments, external_references, id, index, instance_attributes, measurement_begin, measurement_end, measurement_quantities, mime_type, name, objecttype, parent, registertxt1, registertxt2, registertxt3, root, sequences, submatrices, submatrices, test, units_under_test, version, version_date.

The following poperty names are resevered and may not be used on channel level:
average, channel, children, datatype, deletebehaviour, description, dimension, displaytype, empty, external_references, flagkey, group, groupindex, id, implicit_increment, implicit_start, instance_attributes, internal_params, internal_res1, internal_res2, interpolation, is_scaled_by, length, lengthmax, local_columns, maximum, measurement, mime_type, minimum, monotony, name, novaluekey, number, objecttype, parent, quantity, rank, registerint1, registerint2, registerint3, registerint4, registerint5, registerint6, registertxt1, registertxt2, registertxt3, registerval1, registerval2, registerval3, registerval4, registerval5, registerval6, representation, scales, sourcedatafilename, sourcedatafilepath, sourcegenparam1, sourcegenparam2, sourcehandle, sourceinstancekey, sourcename, sourceparentname, sourcerepresentation, sourcetype, sourcevalue, standard_deviation, status, type_size, unit, unit_string, valuetype, version, version_date, waveform.


 Was this document helpful?  submit
  Helpful Not Helpful