LMS Test.

Lab Recorder Data Conversion

User manual

16A

Copyright Siemens Industry Software NV

 Table of Contents

Chapter 1 The LMS Test.Lab Recorder Data Conversion Tool workbook ................. 5

Chapter 2 Anatomy of the application (fake level) ....................................................... 7

Section 2.1 Anatomy of the application .................................................................. 7
Section 2.1.1 Anatomy of the application .................................................................. 7
Section 2.1.2 Home page ......................................................................................... 14
Section 2.1.3 Panes .................................................................................................. 18

Chapter 3 The LMS Configuration and Unit System .................................................. 29

Section 3.1 Concept of the LMS Configurations System ..................................... 29
Section 3.1.1 Write strategy..................................................................................... 31
Section 3.1.2 Read strategy ..................................................................................... 31
Section 3.2 Concept of the LMS Unit System ...................................................... 32
Section 3.2.1 Unit .................................................................................................... 32
Section 3.2.2 Label Unit .......................................................................................... 33
Section 3.2.3 Base Quantity..................................................................................... 33
Section 3.2.4 Quantity ............................................................................................. 33
Section 3.2.5 Quantity Case ..................................................................................... 33
Section 3.2.6 Unit Case ........................................................................................... 34
Section 3.2.7 Unit system ........................................................................................ 34
Section 3.3 Editing LMS Units ............................................................................. 34
Section 3.3.1 Versioning of LMS Unit System ....................................................... 34
Section 3.3.2 Main panel logic ................................................................................ 35
Section 3.3.3 Menu bar ............................................................................................ 36
Section 3.3.4 Unit Cases panel ................................................................................ 40
Section 3.3.5 Unit Rules panel................................................................................. 46

Chapter 4 Data and its management ........................................................................... 49

Section 4.1 Project data ........................................................................................ 49
Section 4.1.1 Projects .............................................................................................. 49
Section 4.1.2 Sections .............................................................................................. 51
Section 4.1.3 Runs ................................................................................................... 51
Section 4.1.4 Measurement annotation .................................................................... 51
Section 4.1.5 Other folders ...................................................................................... 52
Section 4.1.6 Documentation ................................................................................... 52
Section 4.2 Data management .............................................................................. 53
Section 4.3 Reading external file formats ............................................................. 53
Section 4.4 Importing TRP data ........................................................................... 54
Section 4.5 Exporting data .................................................................................... 54
Section 4.5.1 General export options ....................................................................... 55
Section 4.5.2 Format specific export options ........................................................... 55

16A 3
 Chapter 1 The LMS Test.Lab Recorder Data Conversion Tool workbook

Chapter 1 The LMS Test.Lab Recorder Data Conversion

Tool workbook
With this tool, you can convert the files that are produced by the LMS Recorder
(files with extensions .trp or .xtrp).

You can browse to the requested files, select them and convert them into
different throughput formats.
 You can import them into the Active LMS Test.lab project.
 You can export them to one of the supported external throughput formats
that are supported by Test.lab.

Note : This tool will not be able to read any other file format except for trp and
xtrp files. However, the tool allows you to open an existing project, and export
throughput data from the Test.Lab runs to one of the supported external
throughput formats

16A 5
 Chapter 2 Anatomy of the application (fake level)

Chapter 2 Anatomy of the application (fake level)

In This Chapter
Anatomy of the application ................................................7

Section 2.1 Anatomy of the application

Section 2.1.1 Anatomy of the application

This chapter describes the different key concepts that were used to build the
applications. The structure or anatomy of the application consists out of the
following elements:
Step 1
Windows caption: upper border of the application
Step 2
Header area: area for commonly used operations
Step 3
Workflow area: control flow of the application
Step 4
Worksheet area: functionality bundled in a workflow component
Step 5
State control area: control to guide a user through a process
Step 6
Message area: feedback area for a user
The different elements are illustrated in the next picture and described in more
detail in the next sections.

16A 7
 Chapter 2 Anatomy of the application (fake level)

Application anatomy with different elements

Section 2.1.1.1 Windows caption

The windows caption, which is standard Windows functionality, is the upper
border of the application. It contains the company logo, the application name,
the active project name and the active section name.

Section 2.1.1.2 Header area

The header area contains workbook and worksheet independent functionality.
The area consists of two parts:
 Project management fly out
 General functionality accessible through icons

8 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 2 Anatomy of the application (fake level)

Header area

Hovering over the project management zone makes the project management fly
out appear. The fly out contains the name of the active project, the sections
contained in the active project with the active section highlighted, user interface
to create a new section within the active project and a list of recently used
sections.

Project management fly out

General operations that are application independent are accessible through

icons.

General operations

Listed from left to right the functionality behind these icons are:
Step 1
Home page: access to general project management and general options
Step 2
Save: Save active project
Step 3
Save as: Save project with a user definable project name
Step 4
Report: generate report
Step 5
Help: opens application manual of active worksheet
The several topics are described in more detail further in the manual.

16A 9
 Chapter 2 Anatomy of the application (fake level)

Section 2.1.1.3 Workflow area

A Test.Lab application is a combination of different software modules
representing a process. A process typically includes different procedures that
need to be performed in a particular order. On its turn an individual procedure
can be built up of several steps. The order to perform the different procedures
and steps is visualized by the workflow area. A procedure is represented by a
major worksheet containing at least one minor worksheet. The combination of
different major worksheets is bundled in a workbook. The workflow in Test.Lab
is visually represented by a combination of arrows.

Workflow: combination of major and minor worksheets

The workbook displayed in the picture above contains three major worksheets:
Channel Setup, Measure and Navigator. The Measure worksheet includes three
minor worksheets: Measure, Zero Check and Shunt Check.

Navigating through the different sheets can be done by clicking on the desired
arrow. The little dots drawn under a major worksheet name represents the
number of minors contained in that major worksheet. Hovering over the major
worksheet will invoke a fly out including the minor worksheets. This user
interface control can also be used to switch worksheets.

10 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 2 Anatomy of the application (fake level)

Section 2.1.1.4 Worksheet area

A worksheet area contains worksheet dependent functionality. It is a collection
of panes that can be used to perform the specific steps included in a worksheet.

Worksheet area: collection of panes

All panes of a worksheet are bound to the same pane management rules. These
rules are:
 A pane can be minimized and restored or maximized and restored.

Double clicking on the pane header maximizes and restores a pane.

16A 11
 Chapter 2 Anatomy of the application (fake level)

 A minimized pane will appear at the right side of the application as a

vertically drawn tab.

 A pane can be docked or undocked. Default all panes are docked meaning
they are part of the visible worksheet layout. Undocking a pane lifts the
pane out of the worksheet layout. Typically this is used to put a pane on a
different screen or to maximize a pane. A user is guided when docking a
undocked pane by the docking manager. The docking manager will display
all relevant docking zones, either absolute or relative.

Docking manager

Section 2.1.1.5 Worksheet layout area

Pane layouts can be managed per worksheet. The worksheet layout area
includes more functionality such as: to delete, to rename or to create new
worksheet layouts. A worksheet layout also includes pane resizing, pane

12 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 2 Anatomy of the application (fake level)

undocking, pane repositioning and pane minimizing. New layouts appear as tabs
in the worksheet layout area. The default factory worksheet layout can always
be restored, e.g. for the measure worksheet this is the Scope layout. Created
layouts are available on application level, e.g. layouts made in the Acquisition
Setup application are available in the Time Data Acquisition application.
Layout changing can be disabled by checking the option ‘Fixed pane layout’ in
the drop down menu. When this option is active, all pane header options are
disabled.

Worksheet layout area

Section 2.1.1.6 State control area

The state control is available in a worksheet that requires state control. The
possible actions relevant for a certain state are available as buttons. Non relative
actions are not available in the control. The most likely action is displayed as
the biggest button on the left with the blue color. The action buttons also
support keyboard actions when the state control area has the focus. Another part
of the state control area is the state feedback zone. Here information is
displayed of the current active state, the state transition or validity of the state
machine behind the state control. The right side can contain metrics specific for
a certain state. A handle on the at most right side can be used to make the state
control area bigger or smaller.

State control area example

Section 2.1.1.7 Message area

The message area is used as feedback zone for a user. This includes a history of

16A 13
 Chapter 2 Anatomy of the application (fake level)

messages displayed to the user, progress indication and a notification area

displaying general application status.

Section 2.1.2 Home page

The Home page is a general application independent page that is used for
general functionality like opening/creating a project, reporting settings and
application wide settings. The page can be accessed through the Header area by
clicking the home shaped icon.

Home page icon in the Header area

The offered functionality is grouped into tabs:

Home page tabs

The different functionality contained in the tabs are discussed in the following
sections.

Section 2.1.2.1 Open project

The Open project tab is used to open an existing project. A user can choose
between three views to list projects:

14 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 2 Anatomy of the application (fake level)

 All: complete list

 Favorites: projects marked as favorite
 Recent: recently opened projects
Next to these views a user has the possibility to browse to a project and open it
using the Browse… button.

The application supports a single document interface. This means that

maximally only one project can be open at any time. Opening a second project
will close the already opened project. Before closing a project the user will have
the possibility to save the project.

In all views a user can promote or demote a project as a favorite project by

using the star control. Gray/yellow colored icon means no favorite/favorite
project.

Section 2.1.2.2 New project

When the application is launched using a shortcut then only the Home page will
be available. No project will be opened automatically. This means that a user
has either to open a project using the functionality described in the open project
topic or has to create a new project. Creating a new project is done in the new
project tab by selecting a template file. Like projects, template are organized
according three views:
 All: complete list
 Favorites: projects marked as favorite
 Recent: recently opened projects
Next to these views a user has the possibility to browse to a template file and
open it using the Browse… button.

In all views a user can promote or demote a template as a favorite template by

using the star control. Gray/yellow colored icon means no favorite/favorite
template.

Section 2.1.2.3 Report

A description of the reporting options can be found in the reporting chapter.

Section 2.1.2.4 Add-ins

This tab contains an application specific list of all available add-ins. If licenses
are available, an add-in can be loaded. Changes to the add-ins are always saved
per application. Detailed information on the functionality of an add-in is given
in the application specific chapter.

16A 15
 Chapter 2 Anatomy of the application (fake level)

Section 2.1.2.5 Options

This tab contains the general settings that are valid over the complete
application. The settings are grouped into 5 categories:

Section 2.1.2.5.1 Displays

Two 2D display options can be set by using this option: frequency mode and
correction mode.

2D Frequency mode

It is possible to switch between Sample Frequency, Bandwidth and Span. The

bandwidth defines the maximum frequency that can be measured during an
acquisition. The span, which is set at 80% of the bandwidth, is the frequency
band that is unaffected by the cutoff filters. The sample frequency is twice the
bandwidth.

2D correction mode

The 2D Correction type is applied when showing data in displays.

Note: This option is not used for measurement.

Functions measured in Test.Lab, automatically get the 'correct' window

correction factor. This is annotated in the data properties and it is independent
of what is specified in the Options dialog.

Once a function is measured, you can view it in the display with the correction
factor specified by the 2D correction type (default is automatic). This changes
the way the data is displayed but does not change the data and its annotation.

The default method of correcting the effect of adding a window function, when
showing data in displays, can be selected.

Automatic refers to the fact that the software selects the best method. If the
spectrum format is PSD for example, the spectrum data will be energy
corrected. If not, it will be amplitude corrected.

Note: The default setting for the correction method is automatic.

Fixed Amplitude means that the data will always be amplitude corrected. Fixed
Energy means that the data will always be energy corrected. Not Corrected
means that no correction method or factor will be applied to the data. Original
means that any new data (based on previous acquisitions) will be corrected
using the same correction method that was applied to the original data.

16 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 2 Anatomy of the application (fake level)

Section 2.1.2.5.2 Project data

This option includes the project's specifications, the template folder and
throughput saving options.

Project Folder

A project folder is a file with the extension lms that contains all the data that
belong to the project. The location defined alongside represents the directory
where projects will be saved by default. Click the project entry, then enter a new
location in the input field or browse for one in order to change the location.

Project Template

A Project Template file is a file with the extension tpl that contains a starting
setup that will be used whenever a new project is created. The location defined
alongside represents the directory where this template will be searched for by
default. When a new project is created, then you can select which template to
use. Click the Project Template entry, then enter a new location in the input
field or browse for one in order to change the directory.

LDSF Saving Mode

Secured saving during acquisition: when this option is checked on, every 5s
during the acquisition, the throughput data will be saved to disk. If the
application would crash during the measurement, the LDSF file should be
intact, containing all the data except for max last 5s. Elaborated overview for
quick viewing: when this option is checked on, extra statistics about the LDSF
file will be saved that then will be used for quick overview of the complete
trace.

Section 2.1.2.5.3 Licensing

2.1.2.5.3.1 Get licenses from
This option refers to the specification of license server(s) and/or license file(s).
2.1.2.5.3.2 Timer options
This allows you to set a license curfew that returns all licenses at the specified
moment. At the curfew time, a warning is issued which allows the user to keep
the licenses. If five minutes expire without any reaction on the warning, all
applications are shut down and the licenses are returned. Optionally all projects
can be saved automatically. An administrator can force the curfew by using the
group folder mechanism to set the timer options.

The curfew time can be entered by placing the mouse pointer before a number
to-be-changed (mouse pointer becomes a vertical bar) and entering the number.
When placing the mouse pointer at the beginning of the curfew time, one can
enter a valid time by pressing 4 numbers consecutively (the ‘:’ will be skipped
automatically).

Note: The Timer option has no effect when measuring or processing.

Licensing and Timer changes will become valid after the application is

16A 17
 Chapter 2 Anatomy of the application (fake level)

restarted.

Section 2.1.2.5.4 Unit system

The Unit system indicates which unit system is active and used in the
application.

Section 2.1.2.5.5 Favorites

The favorite properties can be customized according to your needs.

Section 2.1.2.6 About

This tab includes information that can be used by our support organization and
copyright information.

Section 2.1.3 Panes

As stated before a worksheet consists of different panes. There are different

types of panes with their own specific functionality. Some panes are different
because they are named differently, but internally they use the same user
interface controls. For instance the Channels pane and Data Selection pane look
differently but internally the same user interface controls are used. The data that
is visualized is of course different but the user interface paradigm is actually the
same. So not all panes will have to be explained, only the different user
interface paradigms used inside the panes need some words. This might sound
very cryptic but in application specific chapters an overview will be given for
every worksheet. Every worksheet will be divided into panes and panes on their
turn into user interface controls. In the next sections all common user interface
controls will be described into detail.

Section 2.1.3.1 Data Source Control

The Data Source Control is a control used for navigating and displaying data.
The control consists of three parts:
 Breadcrumb: Is a navigation control. Conceptually it is the same control
that is used in the Windows Explorer.
 Tree view: Represents a hierarchical view on data. Typically it is used to
navigate through data. Also this control is inspired on the Window Explorer
tree view.
 List view or Pivot view: The third part has two faces: a list view or pivot
view. The list view is available in all data source controls while the pivot
table is only available in some of them.
Breadcrumb

This navigation control is an alternative for tree view navigation. It displays the

18 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 2 Anatomy of the application (fake level)

current path by showing all elements, aka breadcrumbs, of the path. The arrows
in between the elements can be used to navigate to another path. A user can also
edit the path manually. An example of a breadcrumb usage can be found in the
next picture.

Breadcrumb control of Data Selection pane in the Navigator sheet

In short the control provides the following functionality:

Step 1
Back and forward navigation
Step 2
Run-time history list
Step 3
Location navigation (breadcrumbs)
Tree view

This control is actually a standard Tree view control that is used to navigate
through a hierarchical structure. The Tree view control can be displayed or not
using a toggle button.

Breadcrumb control of Data Selection pane in the Navigator sheet

The Tree view highlights the selected item in the tree. This item will be used to
feed the List or Pivot view, which will be explained in the next topic. The
displayed item is consistent with the Breadcrumb control meaning both point to
the same item. Changing the path in a Breadcrumb will result in an update in the
Tree control and vice versa.

The content of the selected item in the Tree view and Breadcrumb can change
and currently there is no automatic update mechanism in the Data Source
control. Therefor a button is foreseen to update the Data Source control by using
a specific button (see box labeled with 5).

List view

The List view is displaying the contents of the item selected in the Tree control
and the Breadcrumb. All items directly contained in the selected item will be

16A 19
 Chapter 2 Anatomy of the application (fake level)

displayed as a list of items. Dependent of the type of element a specific icon

will be displayed in the List view. In the following picture the link between the
three controls is visually illustrated.

Data Source control of Data Selection pane in the Navigator sheet

The list of items can be configured by defining the desired columns. In all List
views the Name column will be available and it represents the name of an item.
Next to this a user is able to add or remove columns by using the Show
columns… and Remove this column entries in the list view header

Invoking the Show columns… will bring up this dialog box.

In this dialog box a user can:

20 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 2 Anatomy of the application (fake level)

 Change the number of fixed columns

 Limit the list of available columns by selecting a specific category
 Searching a specific property
 Add and remove columns
 Change the column order
The List view also contains functionality to increase the usability:
 Sorting a specific column: double click on a column header
 Grouping by a column: right click on a column header and select Group by
this column. Grouping can also be removed in the same context menu.
 Change order of column: by dragging an dropping the column header
 Copy/paste support
 Fill down support
The configuration of a List view can also be saved in a view. The view
functionality can be found in the toolbar of the Data Source Control.

Default List views in the Channel List

A view of a List view contains five elements:

 The displayed columns
 The order of the columns
 The width of the columns
 The sorting criterion
 The grouping criterion
So saving a view will save all of these settings with a unique name for the
instance of the Data Source Control. The management of views can be done
through the views entry in the toolbar. A view can be promoted to the toolbar to
increase the accessibility of a view. The maximum number of favorite views is
six.

In the channel list worksheet, views can also be linked to ‘node types’ or leaves
in the tree view, e..g. the CAN configuration node can be linked with the ‘CAN
dbc’ view. Besides the default views, customized views can be linked. The
linking of views to certain node types is possible via the node context menu or
via a button in the action bar, i.e. Link or Unlink. When a node type is selected,
the linked view will automatically be applied.

Pivot view

The pivot view is not available in all Data Source Controls. This view differs
from the classic List view in different ways:

16A 21
 Chapter 2 Anatomy of the application (fake level)

 The selected item in the Tree view and Breadcrumb is also used as starting
point but unlike the List view the Pivot view will make a deep view. A deep
view will gather all items starting from the selected item also including all
sub items until the deepest level. All items found will be used as input to the
Pivot view.
 The available items can be viewed in a specific manner using row and
column attributes combined with extra filters.

Pivot view in the Measure sheet: all data items found under Active run are used

The row attribute(s) can be selected from the available properties of the data
items. The values for these attributes will appear as rows in the Pivot view.

Row attributes: y axis unit and name are selected

22 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 2 Anatomy of the application (fake level)

The column attribute can be defined the same way as the row attribute with the
limitation that only one property can be chosen for the column attribute. The
different values of this property will be displayed as columns in the Pivot view.

Column attribute: function class is selected

Next to the row and column definition a user can also add filters to limit the
available data in the Pivot view. Default the row and column attributes are
added as available filtering criteria. But other filters can be added. This is done
in the filter entry.

Filters: name, y axis unit and function class are defined

16A 23
 Chapter 2 Anatomy of the application (fake level)

The filter will limit the displayed data in the Pivot view. Filtering on row and
column attribute can also be done using a specific handle.

The pivot cells indicate how many items are found corresponding the row
attributes, column attribute and the filters. In the current Pivot view only the
count is available.

Multiple cells can be dragged and dropped in a user picture, i.e. all
corresponding items will be dropped.

The columns header can be displayed vertically or horizontally.

The views concept is also available in the Pivot view. The selection of row
attributes, column attribute, filters and column header orientation can be saved
in a view. The view functionality can be found in the toolbar of the Data Source
Control.

Favorite views in the Data Selection pane of the Measure sheet

The management of views can be done through the views entry in the toolbar. A
view can be promoted to the toolbar to increase the accessibility of a view. The
maximum number of favorite views, sum of pivot and list views, is six.

24 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 2 Anatomy of the application (fake level)

Section 2.1.3.2 Property Control

A Property control consists of maximum two tabs: a dynamic and a static tab.
Every worksheet has one and only one pane containing a Property control. The
dynamic tab is linked to the items selected in a Data Source Control of another
pane in the same sheet. The static tab, which is not always available, typically
contains the control parameters that are specific for a worksheet.

Property control in Measure sheet: left side static tab and right side dynamic
tab

The static tab is actually nothing more than a list of parameters important for
controlling the worksheet process. Actually the parameter name and value are
displayed.

The dynamic tab is linked to the selected items in either a List view or Pivot
view.

Dynamic tab in Measure sheet: the properties of the selected items (3 traces)are
displayed

The dynamic or property tab visualizes the property name and value(s) of the
selected items. If the values of a certain property of the selected items are
identical, then this value is displayed. If there is a difference then the Multiple
values string is displayed. Editing a value will update the specific property for
all selected items.

16A 25
 Chapter 2 Anatomy of the application (fake level)

The way the data properties or control parameters are visualized can be
determined using the controls in at the top.

Step 1
Choice between categorized and alphabetical order. The name-value pairs of
properties and parameters are always grouped into categories. The categorized
order will display the name-value pairs according the defined categories. An
alternative order is the alphabetical order where the properties are displayed in
alphabetical order without categories.
Step 2
Choice between viewing all properties and the favorite properties. Properties
can be be promoted as a favorite using the functionality described in point 3 or
in the Home page – Options - Favorites.
Step 3
Customize properties for being a favorite or not and specify the number of
digits, if the property value is a decimal number.
Step 4
Search a property name in the listed properties.

Section 2.1.3.3 Display Control

The Display control is a control that is uniquely available in Displays panes.
This control contains two ways to use layouts. A first way is the classic user
definable layouts. A second manner is called preview layout. Both differ in the
number of interactions that are needed to operate the control.

In short a user definable layout has to be create by a user using the + icon.

26 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 2 Anatomy of the application (fake level)

Clicking the + icon will bring up a list of layouts where a user can choose from.
When the layout is loaded, a user has to manually drag and drop the data from a
Data Source Control into a display of a layout. More details on the typical
layout functionality and the different types of displays can be found in the
Documentation and Presentation chapter.

The second type of layout is the Preview layout. This layout is always presented
in the first tab of the layouts and is actually the default. The difference with the
user defined layouts is the automatic behavior of displaying data. As mentioned
in the Property control section, there is a link between the items selected in a
Data Source control and a Property control. As a matter of fact the selection
items are used as input for the Property control. When a Display control is
contained in a worksheet then these items are also used as input of the preview
layout. Depending on the type of selected data elements a user will
automatically have a layout including corresponding displays.

The next picture show the selected items, being the selected cells in the pivot
table and the resulting preview layout. The selection holds three kinds of data:
statistics, time and time at level data. For each type a dedicated display is
instantiated and the data is added to the appropriate display.

Preview layout: link between Pivot view and Display control

16A 27
 Chapter 3 The LMS Configuration and Unit System

Chapter 3 The LMS Configuration and Unit System

In This Chapter
Concept of the LMS Configurations System......................29
Concept of the LMS Unit System ......................................32
Editing LMS Units .............................................................34

Section 3.1 Concept of the LMS Configurations System

In the LMS Configuration System, different files and settings that are relevant
for the LMS TEST applications, will be managed automatically by the software.
The system consists of 3 management levels :

16A 29
 Chapter 3 The LMS Configuration and Unit System

 Central or Factory level : this level will always be available and it contains
the LMS Factory files and settings. This level will be installed through the
install procedure and its content should never be updated manually.
 Group level (which is optional): this level can be enabled (optional) by the
user or administrator and it contains the configuration files and settings that
you want to share within a certain team.
 User level: this level will always be available and it contains all individual
configuration files and settings of a specific user.
For every level, a specific location (folder) needs to be defined. During
installation of the "LMS Configuration and Units Editor" tool, the administrator
has the possibility to define these locations for all users on that system.
You can change these locations for yourself with the command
"File->Configuration …". You will get the following dialog where you can
change it.

The typical configuration files which are managed by this system are :
 The Active Units system: ActiveUnitSystem.xml
 Tools->Options …. Settings: Configuration\Loader.cfg
 Column visibility of Time data selection:
Configuration\DynamicAttributes.txt
 Column visibility of Block processing:
Configuration\DataBlockProcessingVisibilityMap
 User attribute visibility: Configuration\UserAttributes.txt
 User attribute List types: Configuration\ListAttributes.txt
 Favorite Displays: Layout\SelectedLayoutFiles.txt
 Template for Documentation: Attachment Templates\MemoInventory.txt
The typical file types which are managed by this system are :

30 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 3 The LMS Configuration and Unit System

 Units files: *.lu5

 Project templates: Project Templates\*.tpl
 Time Data Selection Datasets: Dataset\*.tds
 Different Calculator Formulasets: FormulaSet\*.*FS
 Time Data Processing Processingsets: ProcessingSet\*.TPS
 Display layouts: Layout\*.lay
 Print formats: PrintFormats\*.doc(x)
 Column visibility files: GridFilters\*.txt
 Templates for Documentation: Attachment Templates\*.doc (html)

Section 3.1.1 Write strategy

When you are running one of the LMS Test applications (LMS Configuration
and Unit System tool, Test.lab), these applications will always write the
configuration files and settings on the User level.

Section 3.1.2 Read strategy

When you are running one of the LMS applications and when it needs a specific
setting (or file that contains that setting), then the following strategy will be
handled by default (File access priority = Local) :
Step 1
First the system will look on Local level. If it is found, it will be used.
Step 2
If it is not found, then the system will look on Group level. If it is found, it will
be used.
Step 3
If it is not found, then the system will use the Factory value which is always
available on central level.

Note: If File access priority = Group, then the system will first look on Group
and then on Local level.

When you are running one of the LMS applications and when you need a list of
available configuration files of a specific file type, then the following strategy
will be handled by default (File access priority = Local) :
Step 1
First the system will look which files are available on Local level. These are
always added to the list.
Step 2

16A 31
 Chapter 3 The LMS Configuration and Unit System

Then the system will look on Group level. These are added to the list, except
when a version of this file was already available on Local.
Step 3
Then the system will look on Central level. These are added to the list, except
when a version of this file is already available.

Note: If File access priority = Group, then the system will first look on Group
and then on Local level.

Section 3.2 Concept of the LMS Unit System

In the LMS Unit System, quantities are determined by their base quantity terms:
length, mass, time, angle, current, temperature, light, and mol. For the same
quantity multiple quantity cases can exist. One of these quantity cases is the
default quantity case, the others are defined by a number of unit rules. Each
quantity case maps with a set of unit cases. One of these unit cases is the default
unit case, the others are visible or invisible. A unit system (lu5) file contains all
the quantity cases, the unit rules, the lists of unit cases and their unit case status.

Section 3.2.1 Unit

Unit label:
 Linear conversion: scale factor, offset
User(si) = si * <scale factor> + <offset>
 Level conversion: log reference, log scale factor, log base, level string, flag
for power or linear unit.
Examples:
 Sound pressure’: unit label: “Pa”
scale factor: 1, offset: 0 Pa
log reference: 2e-5 Pa, log base: 10, log scale factor: 20, level string “dB
(2e-5)”, power: no
 ‘Temperature’: unit label: “deg C”
scale factor: 1, offset: -273.15 degC (0 K = -273.15 degC),
log reference: 1 degC, log base: 10, level scale factor: 20, level string “dB”,
power: no

32 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 3 The LMS Configuration and Unit System

Section 3.2.2 Label Unit

Same as unit, except no info about linear conversion (level conversion is

defined). Label units are weak units in the sense that they disappear when they
are used in computations together with other units. They are only meant for
associating user defined units with very specific semantics with the data.

Example:
 Label Unit Loudness
Unit label: "sones", Level label: "phones", Log reference: 0.0625, Log base:
2, Level scale factor: 10, Power: yes

Section 3.2.3 Base Quantity

 Base quantities: length, mass, time, angle, electric current, thermodynamic

temperature, luminous intensity, amount of substance
 See http://physics.nist.gov/cuu/Units/units.html
The reason to consider angle a base quantity is historical.

Section 3.2.4 Quantity

 Unique combination of Base Quantities:

rational powers for length, mass, time, angle, current, temperature, light, mol

can be all zero (for instance ratio)

 Multiple Quantity cases can exist for one Quantity (see later)
Example:
 Quantity acceleration: base quantity length = 1, base quantity time = -2

Section 3.2.5 Quantity Case

 Belongs to one Quantity: unique combination of rational powers for Base

Quantities
 A Quantity Case has a specific name.
 A Quantity Case is the default for the Quantity involved or can be defined
by a number of Unit Rules
Examples:

16A 33
 Chapter 3 The LMS Configuration and Unit System

 Quantity case Velocity: base quantiies: length=1, time -1, default

 Quantity case Speed: base quantities: length=1, time=-1, rules:
Distance*Time–1, Distance*Frequency

Section 3.2.6 Unit Case

 A Quantity Case has a related list (1 or more) of Units. We call this list of
Units belonging to the same Quantity Case the Unit Cases of this Quantity
Case.
 There is one and only one default unit case for each quantity case.
 Unit Case can be set to be visible or invisible. The default unit case has to
be visible.
 The unit labels of all Unit Cases belonging to one Quantity Case have to be
unique.
Example:
 Unit cases km and hm for quantity case Distance

Section 3.2.7 Unit system

 A unit system contains all the quantity cases, the unit rules, the lists of unit
cases and their unit case status.
 A unit system is not saved in the project database of the application, but in a
separate (lu5) file with a specific format. This unique unit system file is
accessible by each LMS Test application.
 The predefined unit system files: SI, Technical, English, ISO 1683-1983

Section 3.3 Editing LMS Units

The stand-alone LMS Configuration and Unit System tool can be used to create
and modify unit system (lu4 and lu5) files. The LMS Configuration and Unit
System tool is also used to select the active unit system file. This active unit
system is notified when the LMS Test application like Test.Lab is started. When
changing this active unit system the LMS Test application needs to be re-started
in order to be aware of this change.

Section 3.3.1 Versioning of LMS Unit System

LMS Unit System version 1.0.0 includes Factory unit system files of type ‘lu4’.

34 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 3 The LMS Configuration and Unit System

LMS Unit System version 2.0.0 includes new Factory unit system files of type
‘lu5’ and an upgrade of the LMS Configuration and Unit System tool. In these
new Factory unit system files, the name of the existing ‘MicroStrain’ quantity
cases into ‘Strain’ quantity cases has been changed. The new Factory unit
system files also contain extra quantity cases, extra unit cases, and a number of
improved unit parameters.

LMS Unit System version 2.1.0 includes extended Factory unit system files of
type ‘lu5’ and a minor upgrade of the LMS Configuration and Unit System tool.

LMS Unit System version 2.2.0 includes extended Factory unit system files of
type ‘lu5’.

Section 3.3.2 Main panel logic

The main panel consists:

 A single menu bar
 Two tabs, one for the units and one for the unit rules
 Checkboxes to manage the visibility in the Units tab
 Four action buttons in case of Units tab:
 Add Unit…
 Add Label…
 Edit…
 Delete…
 Two action buttons in case of Unit rules tab:
 Add…
 Delete…
The general concept is that all information in the tabs is read-only and that the
unit- or rule information can only be edited from a pop-up panel.

16A 35
 Chapter 3 The LMS Configuration and Unit System

Section 3.3.3 Menu bar

Section 3.3.3.1 File =>Configuration

You will get the following dialog which is used to change the user configuration
folder, the group configuration folder and the settings of the group
configuration.

Note: Please refer to the section about the concept of the LMS configuration.

Section 3.3.3.2 File => Select active unit system

This is menu is used the select the active unit system and open it in the LMS
Configuration and Unit System tool.

On File => Select active unit system…, a list is shown with all available unit
system files. Unit system files only appear once in the list and on selection, the
priority Local=>Group=>central is followed. An example of this logic is given
below:

36 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 3 The LMS Configuration and Unit System

Unit system file Location Unit system file Visibility status

Name

central Technical.lu5 Not visible, overruled by Group

Configuration

English.lu5 Visible

SI.lu5 Visible

ISO_1683_1983.lu5 Visible

GroupConfiguration Technical.lu5 Not visible, overruled by

UserConfiguration\user1

Company.lu5 Visible

UserConfiguration\user1 Ultimate.lu5 Visible

Technical.lu5 Visible

The above situation for user ‘user1’ will result in a list with the following four
items listed in alphabetic order:

Company.lu5 (GroupConfiguration)

English.lu5 (central)

SI.lu5 (central)

ISO_1683_1983.lu5 (central)

Technical.lu5 (UserConfiguration)

Ultimate.lu5 (UserConfiguration)

One of these six unit system files can be made active.

Section 3.3.3.3 File => Upgrade unit system

Section 3.3.3.3.1 Major upgrade

The latest versions of the LMS Configuration and Unit System tool can only
open ‘*.lu5’ unit system files."

Old unit system files of type ‘lu4’ can be imported and upgraded into type ‘lu5’
starting from a chosen unit system on the Central folder (Technical, SI, English,
or ISO 168301983):

16A 37
 Chapter 3 The LMS Configuration and Unit System

 The ‘MicroStrain’ quantity cases will be transformed into the ‘Strain’

quantity cases.
 Missing quantity cases with all their unit cases will be added.
 Missing unit rules will be added.
 Optionally (option 1, by default on), the unit parameters can be updated.
 Optionally (option 2, by default off), the missing unit cases of existing
quantity cases can be added.
After upgrade the modified unit system will be saved on the UserConfiguration
folder and it will be made active. Also a logging will be listed about:
 Added quantity cases
 Added unit cases
 Added unit rules
 Modifies unit cases (happens when option 1 is on)
 Ignored unit cases, being new unit cases of existing quantity cases which
have not been added (happens in case option 2 is off).

Section 3.3.3.3.2 Minor upgrade

In a similar way a minor upgrade of the unit system files can be performed
when needed. For instance 2.0.0 lu5 unit system files can be upgraded to 2.1.0
or 2.2.0 lu5 unit system files.

Section 3.3.3.4 File => Import dynamic units

The unit system files containing the newly created dynamic units are loaded
from the UserConfiguration folder (dynamic rules are not loaded). All dynamic
quantity cases and unit cases are added (read inserted) to the lists of units.

Dynamic quantity cases and dynamic unit cases can be recognized by the unit
case status ‘Dynamic’. The user can change this status into ‘Default’, ‘Case
default’, Visible, or ‘Invisible’ to make this case static. Only the static units will
be saved afterwards (see later).

Section 3.3.3.5 File => Save

When saving the current status, all units and rules will be saved with the same
filename as the one that was opened, but always on the UserConfiguration
folder. This implies that a file loaded from the Central or Group folder will be
saved with the same name on the UserConfiguration folder.

When dynamic quantity cases and/or unit cases have been imported, they will
not be saved unless they have been made static by the user (by changing the
Unit Case Status field).

Section 3.3.3.6 File => Save as…

When saving the current status, all units and rules will be saved with a filename
that needs to be specified by the user. For that purpose a flat list of all unit

38 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 3 The LMS Configuration and Unit System

system files is shown including an input field containing the name of the unit
system file that was opened originally. The unit system file is saved on the
UserConfiguration folder.

Section 3.3.3.7 File => Exit

When closing the application, a message box pops up to ask if the user wants to
keep the changes (only if changes have been made).

Section 3.3.3.8 Edit => Find

On Find, a panel pops up with an input field ‘Find what:’. For units, the user
defined string will be searched for in the Quantity Case Name and the Unit Case
Name. For rules, all Quantity Case Names will be part of the search.

With Find Next, the next row will be highlighted containing a hit. This row will
be in the center of the visible list or higher when the list is too short.

The direction can be specified ‘Down’ or ‘Up’.

Search conditions which can be specified:

 Match case
 Match whole word
 Wrap searches
Continue searching from the beginning list, after reaching its end, when
searching down, or the end after reaching the beginning, when searching up.

Section 3.3.3.9 Edit => Add unit…

This action maps on the Add Unit button in case of Unit panel. You may check
on it later.

Section 3.3.3.10 Edit => Add label…

This action maps on the Add Label button in case of Unit panel. You may check
on it later.

Section 3.3.3.11 Edit => Add rule…

This action maps on the Add Rule button in case of Unit rule panel. You may
check on it later.

Section 3.3.3.12 Edit => Edit…

This action maps on the Edit button. You may check on it later.

Section 3.3.3.13 Edit => Delete…

This action maps on the Delete button and deletes the selected rows after

16A 39
 Chapter 3 The LMS Configuration and Unit System

confirmation.

Section 3.3.3.14 View => Toolbar

The toolbar can be shown or not.

Section 3.3.3.15 View => Show

The items in this View => Show Menu map on the checkboxes of the Units tab.
The ‘Checked/Not Checked’ status of the checkboxes is reflected in the menu
bar pull down.

Section 3.3.3.16 View => Sort

The items in this View => Sort menu map on the radio buttons of the Units tab.
The ‘Checked/Not Checked’ status of these radio buttons is reflected in the
menu bar pull down: According to base quantities / According to name.

Section 3.3.3.17 Help => LMS Configuration and Unit System Help
Launches the help of the LMS Configuration and Unit System tool application.

Section 3.3.3.18 Help => About LMS Configuration and Unit System
tool
Shows the ‘About’ of the LMS Configuration and Unit System tools
application.

Section 3.3.4 Unit Cases panel

Section 3.3.4.1 Sorting of the Unit Cases

The unit cases can be sorted in two different ways depending on the chosen
sorting option set in the menu or set by radio buttons below the panel:
 Sorting according to base quantities
 Sorting according to name

Section 3.3.4.1.1 Sorting according to base quantities

In this case, the sorting is using the following priorities:
Step 1
First the regular unit cases, then the label units. The regular unit cases are sorted
according to:
Step 2
Base quantities: from lowest fractional power to highest

40 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 3 The LMS Configuration and Unit System

 Length
 Mass
 Time
 Angle
 Temperature
 Electric current
 Luminous intensity
 Mole
Step 3
Quantity Case Name (*): first default quantity case, then the static ones in
alphabetic order; case sensitive, then the dynamic ones in alphabetic order; case
sensitive.

Note: A set of compatible quantity cases belong to the same quantity when they
all have the same base quantity terms (Length, Mass, Time, Angle,
Temperature, Electric current, Luminous intensity, and Mole). One quantity
case of such a set is the Default quantity case. The corresponding default unit
has status ‘Default’ (standing for general default unit). The corresponding
default units of the other (not-default) quantity cases have status ‘Case default’
(standing for case specific default unit).

Step 4
Unit Case Status (**) in sequence:
 Default
 Case default
 Visible
 Invisible
 Dynamic

Notes: A Label Unit can only have Label Status Visible or Dynamic. The
Dynamic option for the Unit Case Status is only available in case of an
imported unit case. (The option is Dynamic after importing the unit case and
can be changed by the user into another option.)

Step 5
Unit Case Name: alphabetic order; case sensitive
3.3.4.1.1.1 Presentation of unit cases per Quantity
The sorting algorithm makes sure that all unit cases of the same quantity are
next to each other. These groups of unit cases belonging to the same quantity
are displayed with alternating background colors: white and light grey.

The font colours are also optimized: red for all dynamic info and green for all
dynamic info which has been changed into static (Default, Case default, Visible,
or Invisible) by the user.

16A 41
 Chapter 3 The LMS Configuration and Unit System

Section 3.3.4.1.2 Sorting according to name

In this case, the sorting is using the following priorities:
Step 1
First the regular unit cases, then the label units. The regular unit cases are sorted
according to:
Step 2
Quantity Case Name: alphabetic order; case sensitive
Step 3
Unit Case Status (*) in sequence:
 Default
 Case default
 Visible
 Invisible
 Dynamic

Note: A set of compatible quantity cases belong to the same quantity when they
all have the same base quantity terms (Length, Mass, Time, Angle,
Temperature, Electric current, Luminous intensity, and Mole). One quantity
case of such a set is the Default quantity case. The corresponding default unit
has status ‘Default’ (standing for general default unit). The corresponding
default units of the other (not-default) quantity cases have status ‘Case default’
(standing for case specific default unit). The default quantity case is the quantity
case for which the default unit case is the quantity default, called ‘Default’ and
not only the default unit case for the quantity case, called the ‘Case default’.

A Label Unit can only have Label Status Visible or Dynamic.

The Dynamic option for the Unit Case Status is only available in case of an
imported unit case. (The option is Dynamic after importing the unit case and
can be changed by the user into another option.)

Step 4
Unit Case Name: alphabetic order; case sensitive
3.3.4.1.2.1 Presentation of unit cases per quantity case
The sorting algorithm makes sure that all unit cases of the same quantity case
are next to each other. These groups of unit cases belonging to the same
quantity case are displayed with alternating background colors: white and light
grey.

The font colours are also optimized: red for all dynamic info and green for all
dynamic info which has been changed into static (Default, Case default, Visible,
or Invisible) by the user.

42 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 3 The LMS Configuration and Unit System

Section 3.3.4.2 Format of the Level String

The level conversions include the acoustic weighting applied on the data. The
LMS unit system allows managing this aspect globally. For this purpose the
characters ‘<’, ‘W’, and ‘>’ are used. Whatever is between < and > will be
shown when the weighting is not Linear. When the weighting is Linear nothing
is shown. The common example for [Pa] to [dB] is given below:

Level String Linear data A-weighted data

dB dB dB

dB<(W)> dB dB(A)

dB<[W]> dB dB[A]

dB<(W)> re 20e-6 dB re 20e-6 dB(A) re 20e-6

Section 3.3.4.3 Edit…/Add...Unit Cases panel

When editing a unit, all information is loaded in the Edit Unit panel. The user
can edit all fields and Apply consistency is checked on.

When adding a unit, the values of the active selection are taken over in case a
unit is selected (and not a label). If no such selection is made, all values are put
to the defaults.

The formats of the parameters in the panel are:

16A 43
 Chapter 3 The LMS Configuration and Unit System

Panel Parameters Input format and values Default values

Quantity Case Name String – Should not be empty ‘<to be defined>’

Fractional Powers Integer values –positive or All set to 1

negative, non-zero for the
denominator

Unit Case Name String – Should not be empty ‘<to be defined>’

Unit Case Status Combo-box – either Default, Default

Case default, Visible, Invisible,
or Dynamic
Only one Unit Case can be the
Default.

Scale Factor Strict positive double 1.0

Scale Offset Double 0.0

Level Label String – ‘<W>’ is used to dB<(W)>

manage the acoustic weighting

Reference for Level 0 Strict positive double 1.0

Linear or Power Combo-box – either Linear or Linear

Power

Logarithmic Base Strict positive double – in 10.0

practice limited to 10 or 2.

Logarithmic Scale Factor Strict positive double – in 20.0

practice limited to 10 or20.

Table: Panel Parameters for Edit Units panel

The consistency check will be the verification of the uniqueness of the quantity
case name and the unit case name for the given quantity case and the validation
of the input parameters according the table above.

Section 3.3.4.4 Edit…/Add... Labels panel

When editing a label, all information is loaded in the Edit Label panel. The user
can edit all fields and Apply consistency is checked on.

When adding a label, the values of the active selection are taken over in case a
label is selected (and not a unit). If no such selection is made, all values are put
to the defaults.

The formats of the parameters in the panel are:

44 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 3 The LMS Configuration and Unit System

Panel Parameters Input format and values Default values

Quantity Case Name String – Should not be empty ‘<to be defined>’

Label Name String – Should not be empty ‘<to be defined>’

Label Status Combo-box – either Default or Default

Dynamic

Level String String – ‘<W>’ is used to dB<(W)>

manage the acoustic weighting

Reference for Level 0 Strict positive double 1.0

Linear or Power Combo-box – either Linear or Linear

Power

Logarithmic Base Strict positive double – in 10.0

practice limited to 10 or 2.

Logarithmic Scale Factor Strict positive double – in 20.0

practice limited to 10 or20.

Table: Panel Parameters for Edit Labels panel

The consistency check will be the verification of the uniqueness of the quantity
case name and the label name and the validation of the input parameters
according the table above.

Section 3.3.4.5 Visibility Checkboxes of the Unit Cases tab

The Show options can be set in the menu or set by check boxes below the panel:

Section 3.3.4.5.1 Columns selection

 Show Base Quantity Powers: 8 columns with the base quantity powers will
be inserted after the visibility column. These columns will contain the
fractional powers as ratios, e.g.:’2/3’.
 Show Linear Conversion Parameters: inserts the linear conversion
parameters after the base quantity columns (if selected to be visible in the
list).
 Show Level Conversion Parameters: inserts the level conversion parameters
after the linear conversion parameters (if available) or after the base
quantity columns (if selected to be visible in the list).

Section 3.3.4.5.2 Rows selection

 Show All Visible Unit Cases: All Default and Visible items of the unit
system are displayed.
 Show All Unit Cases: All items of the unit system are displayed.
 Show Dynamic Unit Cases Only: Only the imported items, recognized by

16A 45
 Chapter 3 The LMS Configuration and Unit System

the ‘Dynamic’ Status type will be shown.

Section 3.3.5 Unit Rules panel

Section 3.3.5.1 Sorting of the Unit Rules

The Unit Rules are sorted in a fixed way. The user has no impact on it. The
sorting is using the following priorities:
 Resulting Quantity Case: alphabetic order; case sensitive
 Quantity Case 1: alphabetic order; case sensitive
 Fractional Power 1: from lowest fractional power to highest
 Quantity Case 2: alphabetic order; case sensitive
 Fractional Power 2: from lowest fractional power to highest

Section 3.3.5.2 Presentation of unit rules per resulting quantity case

The sorting algorithm ensures that all unit rules of the same resulting quantity
case are next to each other. These groups of unit rules belonging to the same
resulting quantity case are displayed with alternating background colors: white
and light grey.

Section 3.3.5.3 Edit…/Add... Unit Rules panel

When editing a rule, all information is loaded in the Edit Rule panel. The user
can edit all fields and on Apply consistency is checked.

When adding a Rule, the values of the active selection are taken over. If no
selection is made, all values are put to the defaults.

The formats of the parameters in the panel are:

Panel Parameters Input format and values Default values

Quantity Case Names Combo-box showing a saved Ratio

Quantity Case

Fractional Powers Integer values – positive or Both set to 1

negative

Table: Panel Parameters for Edit Rules panel

The list of resulting quantity cases is adapted in the combo-box depending on

the above selected quantity cases, operations or powers. All quantity case names
are listed in alphabetic order.

The calculation of this list of resulting quantity cases depends on the base
quantities obtained from the proposed unit calculation. All quantity cases that

46 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 3 The LMS Configuration and Unit System

have the matching base quantities will appear in the list.

Only multiplication is supported as operation between units. When the second

fractional power is negative, then the operation will become the division. An
example could be speed (length / time): the unit rule will be: ‘length * time-1’.

The consistency check will be limited to the verification of the uniqueness of

the rule.

16A 47
 Chapter 4 Data and its management

Chapter 4 Data and its management

In This Chapter
Project data .........................................................................49
Data management ...............................................................53
Reading external file formats .............................................53
Importing TRP data ............................................................54
Exporting data ....................................................................54

Section 4.1 Project data

This document concerns the management of data within Test.Lab. The

management of data via projects and templates is a crucial part of the
application. Projects form the basis of managing data. Templates can be used to
significantly reduce the time to create new projects which acquire a certain
setup.

Section 4.1.1 Projects

A project is a single entity that contains all the data that you require to be kept
together. It is a means of grouping a set of data that logically belong together.
This is typically the data relating to a particular test object. It could thus include
all sorts of data, such as measurement data, test and processing setups, geometry
and modal data.

Note: One project is not necessarily related to just one application.

You can use different applications with the same project and you can use a
single application with a number of different projects, though typically you
would not have the same project open in different applications at the same time.

Projects are automatically assigned a name that contains a sequential number

(ProjectX). The project can be renamed when being Saved.

Section 4.1.1.1 Opening a project within an application

On the Home page, referring to chapter Anatomy of the application, select the
Open Project tab. In this tab a project list view can be chosen. Search or browse
to the project to-be-opened, choose its favorite status via the star control and
open the project.

The default location to store and open projects needs to be identified during the

16A 49
 Chapter 4 Data and its management

Test.lab installation procedure. All the projects stored in this location can be
listed via the according project list view. This location can be changed in the
Home>Options>Project data tab.

Section 4.1.1.2 Opening a project directly

Using Windows Explorer, when you double-click the project file, it is opened
by the default application. This default is set during the Test.Lab installation
procedure.

You can also use the standard Windows functionality to open an existing project
with a different application.

First select the project in a Windows Explorer and right click the file.

In the popup menu, use the Open With... option to select the application that
you want to use to open the project. If you want to open your projects, using this
application by default, check the corresponding checkbox Always use the
selected program to open this kind of file.

Section 4.1.1.3 Project templates

Every project is based on a template that determines the initial setup and
settings for a new project. A project template can contain multiple test setups or
sections. Project template files have the extension .tpl.

Section 4.1.1.4 Using a template within an application

On the Home page, referring to chapter Anatomy of the application, select the
New Project tab. In this tab a project template list view can be chosen. Search or
browse to the project template to-be-opened, choose its favorite status via the
star control and open the project template.

The default location to store and use project templates from is

<C:\LMS\UserConfiguration\username\LMS Test.Lab RevisionNumber\Project
Templates>. All the project templates stored in this location can be listed via the
according project template list view. This location can be changed in the
Home>Options>Project data tab.

Section 4.1.1.5 Creating a template within an application

Step 1
Save the project settings with the Save As… button, give it a name and choose
the option to Save as type, the .tpl file extension. The settings of the project will
be saved without the measured data. Other data will not be removed.
Step 2
If you want that later on the template will be listed automatically in the list view
when creating a new project, you need to browse explicitly to the default
template location, before you push the save button.

50 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 4 Data and its management

Section 4.1.2 Sections

Sections are contained within projects. They are a means of organizing sets of
data that have been acquired under the same test conditions, analyzed using the
same parameters or derived using the same processing.

The channel setup and the measurement and processing parameters are part of
the Section. Activating a Section will cause these parameters to come into
effect.

When the application is started (or a new project), a single section within a new
project is created.

Additional sections can be created using the New Section... button, via a project
context menu or via the header area fly out menu. In this fly out menu Type a
name + Enter … creates a new active section. Active sections in the current
project can be switched or a recent active section across projects can be
activated.

There is always an active section (shown in the Active Section field in the
toolbar) and all operations performed using the menu and tool bar will be
executed on this active section. There is no possibility to have more than one
Active Section open at a certain time.

Note: All generated data is placed and saved in the active section.

Section 4.1.3 Runs

Runs are found within sections. They contain data from all measurement
channels that were acquired (or imported from .trp files) during the same
measurement sequence. Each time a new measurement is started a new run will
be initiated which will contain the acquired data.

Data is always saved in a run when the data acquisition is stopped. This data
must be removed if you do not want to keep it.

The setup used to measure a run is kept in it the section settings.

Section 4.1.4 Measurement annotation

During a measurement, a run is annotated with a number of properties. The

measurement annotation properties are provided by the user just before or just
after a measurement is done. You can edit these properties in different ways:

16A 51
 Chapter 4 Data and its management

Step 1
Edit Measurement annotation in the properties pane.
 Select a run of the active project in the Navigator Data Selection pane.
 You can now edit the measurement annotation via the properties pane.
Click on the value of a property to edit it.
 When you select multiple runs, you can edit a property of these runs at the
same time
 You must explicitly apply the changes you made via the <Apply> button on
the bottom of the properties pane
Step 2
Edit Measurement annotation in the List view.
 Select a section of the active project in the Navigator Data Selection pane.
 Add show columns with measurement annotation properties in the default
list view.
 You can now directly edit the measurement annotation of all the runs in the
list view
 Change cell by cell
 Copy/paste of values
 Fill down

Note: An administrator could set up a customer specific annotation model. As

the annotation model should be the same within the same group of users,
changing the annotation model must be done with care.

Start from the he default annotation model specified in

<installation-dir>\Central\Configuration\AnnotationModel.xml. You can deploy
the file to all users using the group/user configuration mechanism.

Section 4.1.5 Other folders

Other folders includes results of some processing on the measured data.

Section 4.1.6 Documentation

Documentation in the form of documents or pictures can be attached to projects

or sections. You can use the project context menu entry Add attachment… to
add a document to a project or a section.

52 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 4 Data and its management

Section 4.2 Data management

You have different operations available to organize the content of a project

yourself. The different operations are shown in the Organize context menu.

All project data can be copied (Ctrl+C). There are restrictions for the paste
(Ctrl+V) operation.

The most important restriction is that you cannot paste extra data in a
Run-folder, created by the RLDA application.

You can rename or delete (Delete key) Sections, Runs and all arbitrary folders.

You can create new folders on section level or on any previously created folder.

Note: The content of an RLDA created Run cannot be changed.

Section 4.3 Reading external file formats

This document describes the types of files that you can read directly from
within Test.lab.

The following throughput file types are supported :

 LDSF (.ldsf)
 TDF (.ix0)
 XDF (.xdf)
 MTS RPC III (.rsp)
 IST RigSys
 NI DIADEM DAT (.dat)
 NI DIADEM TDM (.tdm)
 LMSASCII
 nCode DAC (.dac)
 lexade
 SOMAT (.sie, .sif )
 KML
 NMEA
 ATFx
 MOOG
 Head
 MATLAB
Also data files that are generated by Lms Tecware are supported for reading.

16A 53
 Chapter 4 Data and its management

Section 4.4 Importing TRP data

Files that were measured with the standalone Recorder, namely .trp files (or
.xtrp files), cannot be read directly within Test.lab, to do further analysis. Only
some overview data is available with direct access.

You must import these files first explicitly within a Test.lab project, before you
can use the measured data for further analysis.

You can import a .trp file, with the context menu Import which will be available
on a selected TRP file. This operation will create a new run within the Active
Section and the TRP overview traces will be transformed into the standalone
measured channels.

Section 4.5 Exporting data

You can export the measured throughput data using the Export… button or via
the data file context menu.
Step 1

Open up the browser tree in the Navigator worksheet.

Step 2

Browse for the run (1 or more) you want to export and select them.
Step 3

Right click on the runs selection.

Step 4

Select Export… from the popup menu in the Navigator worksheet.

Step 5

Choose the file format you want for the data item.
Step 6

Specify the name and location where you want to save the data.
Step 7

Click OK.

54 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 4 Data and its management

Section 4.5.1 General export options

 Output Directory : You have the choice between two options for your
output directory folder
 You can put the exported file on the same folder as the input.
 You can put all exported files on the same folder. You can manually
indicate the folder in the edit field.
 File naming : You have the choice between two options for your generated
output filename
 The filename will be the same as the input. So only the extension will
change.
 All exported files will get the same prefix, extended with a sequential
number. You can manually indicated the prefix in the edit field

Section 4.5.2 Format specific export options

Section 4.5.2.1 MTS RPC III

 Mode : You have the choice between two options for your grouping of the
channels
 Grouped per input file.
 Grouped per sampling rate and input file
 Data : You have the choice between two options for your generated raw
data format
 Integer (2bytes)
 Float (4bytes)
 Two extra options are available :
 You can split longitude and latitude channels
 You can use minimum and maximum as full scale

16A 55
 Chapter 4 Data and its management

Section 4.5.2.2 IST RigSys

Section 4.5.2.3 NI DIADEM DAT

Section 4.5.2.4 NI DIADEM TDM

Section 4.5.2.5 LMS ASCII

Section 4.5.2.6 NCode DAC

Section 4.5.2.7 Lexade

Section 4.5.2.8 MOOG

Section 4.5.2.9 GPS

Recorded external GPS data, i.e. not recorded with the frontend integrated GPS
receiver, can be exported per Point id. The Point id needs to start with
“gps_external-gps-name:” to distinguish between multiple gps recordings.

Critical channels for GPS export are: Latitude, Longitude, Altitude and
NumberOfSatellites.

Section 4.5.2.10 KML (Keyhole Markup Language)

In this case, the GPS data in the throughput file will be exported to a KML file
that can be opened in Google Earth.

Filter settings:
 None: no filtering will be applied. All points that are available in the TDF
will be exported.
 Minimum time between points: you can reduce the number of points
exported by defining how much time there should be between 2 points in
the track. This way, you can reduce the size of the exported file.
 Minimum distance between points: you can reduce the number of points
exported by defining how much distance there should be between 2 points
in the track. This way, you can reduce the size of the exported file.

Section 4.5.2.11 NMEA (National Marine Electronics Association)

In this case, the GPS data in the throughput file will be exported to a NMEA.

Filter settings:
 None: no filtering will be applied. All points that are available in the TDF
will be exported.
 Minimum time between points: you can reduce the number of points
exported by defining how much time there should be between 2 points in

56 User manual LMS Test.Lab Recorder Data Conversion

 Chapter 4 Data and its management

the track. This way, you can reduce the size of the exported file.
 Minimum distance between points: you can reduce the number of points
exported by defining how much distance there should be between 2 points
in the track. This way, you can reduce the size of the exported file.

Section 4.5.2.12 HEAD

You have the option to choose between
 single sampling rate: all channels of the original file needs to have the same
sampling rate
 multiple sampling rate: channels of the original file can have multiple
sampling rate

Section 4.5.2.13 MATLAB

You have the following options :
 Save with single precision: Save with single or double precision
 Group similar blocks in a matrix: Group blocks or not
 Save in MKS units: Save in MKS or in user units
 HDF5 format: Save in HDF5 format or not

16A 57
 G
Index
General export options • 59
Get licenses from • 19
A GPS • 60
About • 20 H
Add-ins • 17
Anatomy of the application • 7 HEAD • 61
Anatomy of the application (fake level) • 7 Header area • 9
Help => About LMS Configuration and Unit
B System tool • 46
Base Quantity • 39 Help => LMS Configuration and Unit System
Help • 46
C Home page • 16
Columns selection • 51 I
Concept of the LMS Configurations System •
35 Importing TRP data • 58
Concept of the LMS Unit System • 38 IST RigSys • 60
Creating a template within an application • 54 K
D KML (Keyhole Markup Language) • 60
Data and its management • 53 L
Data management • 57
Data Source Control • 21 Label Unit • 39
Display Control • 32 Lexade • 60
Displays • 18 Licensing • 19
Documentation • 56 LMS ASCII • 60

E M
Edit => Add label… • 45 Main panel logic • 41
Edit => Add rule… • 45 Major upgrade • 43
Edit => Add unit… • 45 MATLAB • 61
Edit => Delete… • 46 Measurement annotation • 55
Edit => Edit… • 46 Menu bar • 42
Edit => Find • 45 Message area • 16
Edit…/Add... Labels panel • 50 Minor upgrade • 44
Edit…/Add... Unit Rules panel • 52 MOOG • 60
Edit…/Add...Unit Cases panel • 49 MTS RPC III • 59
Editing LMS Units • 40 N
Exporting data • 58
NCode DAC • 60
F New project • 17
Favorites • 20 NI DIADEM DAT • 60
File => Exit • 45 NI DIADEM TDM • 60
File => Import dynamic units • 44 NMEA (National Marine Electronics
File => Save • 44 Association) • 61
File => Save as… • 45 O
File => Select active unit system • 42
File => Upgrade unit system • 43 Open project • 17
File =>Configuration • 42 Opening a project directly • 54
Format of the Level String • 49 Opening a project within an application • 53
Format specific export options • 59 Options • 18
Other folders • 56

16A 59
 P W
Panes • 20 Windows caption • 8
Presentation of unit cases per Quantity • 47 Workflow area • 11
Presentation of unit cases per quantity case • Worksheet area • 12
48 Worksheet layout area • 14
Presentation of unit rules per resulting quantity Write strategy • 37
case • 51
Project data • 19, 53
Project templates • 54
Projects • 53
Property Control • 30
Q
Quantity • 39
Quantity Case • 40
R
Read strategy • 37
Reading external file formats • 57
Report • 17
Rows selection • 51
Runs • 55
S
Sections • 55
Sorting according to base quantities • 47
Sorting according to name • 48
Sorting of the Unit Cases • 46
Sorting of the Unit Rules • 51
State control area • 15
T
The LMS Configuration and Unit System • 35
The LMS Test.Lab Recorder Data Conversion
Tool workbook • 5
Timer options • 19
U
Unit • 38
Unit Case • 40
Unit Cases panel • 46
Unit Rules panel • 51
Unit system • 20, 40
Using a template within an application • 54
V
Versioning of LMS Unit System • 41
View => Show • 46
View => Sort • 46
View => Toolbar • 46
Visibility Checkboxes of the Unit Cases tab •
51

60 User manual LMS Test.Lab Recorder Data Conversion