Showing results for 
Search instead for 
Do you mean 

LMS Test.Lab: Templates

by Siemens Experimenter Siemens Experimenter on ‎05-09-2017 08:57 AM - edited 2 weeks ago



0.png

Have a test that you perform over and over again? Tired of setting up a project with the same settings every time?

 

Templates are the solution!

 

In LMS Test.Lab, templates are used to store custom test settings. When a template is opened, all settings will be loaded – the user can jump right into measuring without having to re-setup the test.

 

Creating a template:

 

First, open (or create) a project with the appropriate settings for the test.

 

After selecting the settings and configuration for the test (channel setup, DSP, tracking, processing, displays, etc.), save it as a template.

 

File -> Save As Template….

 

Figure 1: Saving a project as a template.Figure 1: Saving a project as a template.

NOTE: Saving an existing project as a template will save the settings of a project without saving the data.

 

A project template file has the extension .tpl. This contains the starting setup that is used when a new project is created.

 

To open a template:

  1. Open the LMS Test.Lab software
  2. File -> New
  3. Select the template from the list

Figure 2: Select the template from the list to open it.Figure 2: Select the template from the list to open it.

A new project will be created and all settings will be loaded.

 

Save the project and then start recording data! All the settings should be appropriate.

 

Note that pressing the upper left white icon for new project , there is no template choice given.  The default project template called "BlankProject" will be used automatically. To use something other than the default template, the "File -> New" selection must be used.

 

Creating a template shortcut:

 

To open templates even faster, create a template shortcut.

 

When saving the project as a template there is an option to “Create template shortcut on Desktop”.

 

Figure 3: Creating a template shortcut.Figure 3: Creating a template shortcut.

 

Figure 4: Template shortcut on desktop.Figure 4: Template shortcut on desktop.

Click on the icon to launch. The software will open and load the settings stored with the template.

 

Lock it down!

 

Worried someone will tinker with your template?

 

Lock it down with parameter locking.

 

Parameter locking allows the user to de-activate buttons and fields in Test.Lab so they cannot be changed.

 

Figure 5: Deactivate fields that should not be changed.Figure 5: Deactivate fields that should not be changed.

To lock parameters, go to Tools -> Add-ins and turn on Parameter Locking (no tokens required).

 

Figure 6: Turn on Parameter Locking from the Add-ins menu.Figure 6: Turn on Parameter Locking from the Add-ins menu.

To lock a parameter (such as a drop down menu or a fill-in field), right click on it and select the “Property Dialog” menu.

 

Check on the “Read Only” box to lock the parameter.

 

There are also options to change visual properties of the field such as font and color.

 

Figure 7: Locking a field. Right click on the field and select “Property dialog”. Check on the “Read Only” field in the Edit Box Properties pop-up window.Figure 7: Locking a field. Right click on the field and select “Property dialog”. Check on the “Read Only” field in the Edit Box Properties pop-up window.

When a field is locked it will appear greyed out.

 

Figure 8: The “Count” field is now deactivated.Figure 8: The “Count” field is now deactivated.

When all the desired parameters are locked, save as a Task Shortcut.

 

Go to File -> Save as Task Shortcut.

 

Figure 9: Save as Task Shortcut…Figure 9: Save as Task Shortcut….

A task shortcut is similar to a template, but in addition to just saving settings, it also saves locked parameter settings, add-in activity, and workbook configuration.

 

When saving as a Task Shortcut, three files are created:

  • Project template (.tpl): saves default parameters of the project and locked fields
  • Workbook configuration (.cfg): contains visual configurations and add-ins that have been activated
  • Task Icon (.tsk): this icon uses template and configuration files to call the application in which the task has been created.

 

All three of these files must be stored together.

 

TIP: If storing all three of these files on the desktop is too cluttered, store them in another location and create a shortcut of the task icon on the desktop.

 

When opening the task shortcut, the template with the settings, locked parameters, add-ins, and any visual changes will be loaded.

 

Enjoy the efficiency of not re-creating test settings!

 

Questions? Contact us. 

 

Related Test.Lab links: 

LMS Test.Lab Display links:

Contributors