m

be certain.

MTS Model 793.10 MultiPurpose TestWare® and

Series 793 Application Software
User Information and Software Reference for Model 793.10
MultiPurpose TestWare and the following:
- Model 793.11 Profile Editor™
- Model 793.12 Trend Monitoring
- Model 793.14 Fatigue Monitoring
- Model 793.71 Time History Playout
- Model 793.72 THP with Acquisition

100-147-131 H
 Copyright information © 2011 MTS Systems Corporation. All rights reserved.

Trademark information MTS, FlexTest, RPC, Temposonics, and TestWare are registered trademarks of
MTS Systems Corporation; MPT, Station Builder, Station Manager, and TestStar
are trademarks of MTS Systems Corporation within the United States. These
trademarks may be protected in other countries.

Microsoft and Windows are registered trademarks of Microsoft Corporation. All

other trademarks or service marks are property of their respective owners.

Proprietary information Software use and license is governed by MTS’s End User License Agreement
which defines all rights retained by MTS and granted to the End User. All
Software is proprietary, confidential, and owned by MTS Systems Corporation
and cannot be copied, reproduced, disassembled, decompiled, reverse
engineered, or distributed without express written consent of MTS.

Software validation and MTS software is developed using established quality practices in accordance
verification with the requirements detailed in the ISO 9001 standards. Because MTS-
authored software is delivered in binary format, it is not user accessible. This
software will not change over time. Many releases are written to be backwards
compatible, creating another form of verification.

The status and validity of MTS’s operating software is also checked during
system verification and routine calibration of MTS hardware. These controlled
calibration processes compare the final test results after statistical analysis
against the predicted response of the calibration standards. With these established
methods, MTS assures its customers that MTS products meet MTS’s exacting
quality standards when initially installed and will continue to perform as intended
over time.

Publication information MANUAL PART NUMBER PUBLICATION DATE MTS 793 SOFTWARE RELEASE
100-147-131 H July 2011 Version 5.35A or later

MTS MultiPurpose TestWare®

 Technical Support 7

Preface 13

Conventions 14

Chapter 5 About MultiPurpose TestWare 17

Application Overview 18
The MultiPurpose TestWare Interface 21
MPT Procedure Editor 36

Chapter 6 Performing Common Tasks 43

Chapter 7 MPT Options Editor 61

Chapter 8 Working with MPT Processes 83

Chapter 9 Working with MPT Variables 105

Variable Editor 115

Chapter 10 Working with MPT Specimens 125

MPT Specimen File Types 134

MPT Specimen Loading Examples 143

MTS MultiPurpose TestWare® Contents 3

Chapter 11 Creating a Practice Test Procedure 153

Chapter 12 Command Processes 179

Segment Command Process 181

Cyclic Command Process 186
Dwell Command Process 195
Profile Process 198
External Command Process 211
Sweep Command Process 220
Signal Based Command Process 226
Profile with ALC Process 233
Cyclic with ALC Process 241
Model 793.71/72 Time History Output Process 247
Road Surface Output Process 261

Chapter 13 Data Acquisition Process Descriptions 271

Peak/Valley Acquisition Process 279

Timed Acquisition Process 284
Max/Min Acquisition Process 289
Level Crossing Acquisition Process 296
High Speed Timed Acquisition Process 301
Cyclic Acquisition Process 310
Fatigue Process 319
Time History Input Process 331
Trend Process 336

Chapter 14 Event Process Descriptions 345

Data Limit Detector Process 346

Digital Input Detector Process 353
Operator Event Process 359

4 MTS MultiPurpose TestWare®

 Peak/Valley Change Detector Process 364
Program Event Process 373
Periodic Time Event Process 377
Failure Detector Process 382

Chapter 15 External Control Process Descriptions 387

Digital Output Process 388

Temperature Control Process 393

Chapter 16 Other Process Descriptions 399

Program Control Process 400

Group Process 405
MPT Calculation Process 408
Operator Information Process 410
Start Application Process 420
Send Mail Process 426
Set Controller Value Process 430
Auto Offset Process 436
Data Display Process 440

Chapter 17 Trend and Fatigue Monitoring Applications 457

Model 793.12 Trend Monitoring Application 458

Model 793.14 Fatigue Monitoring Application 465

Chapter 18 Model 793.11 Profile Editor 473

Profile Editor 476

Creating Profiles 487
Design Considerations 495
Transitions 514

MTS MultiPurpose TestWare® Contents 5

 How to Play Out Profiles 519
Profile Editor Controls and Displays 521

Appendix 19 Default Templates 553

Appendix 20 Excel File Converter 557

Appendix 21 MPT Shortcuts 561

Index 567

6 MTS MultiPurpose TestWare®

Technical Support
How to Get Technical Support
Start with your The manuals supplied by MTS provide most of the information you need to use
manuals and maintain your equipment. If your equipment includes software, look for
online help and README files that contain additional product information.

If you cannot find answers to your technical questions from these sources, you
can use the internet, e-mail, telephone, or fax to contact MTS for assistance.

Technical support MTS provides a full range of support services after your system is installed. If
methods you have any questions about a system or product, contact Technical Support in
one of the following ways.

www.mts.com The web site provides access to our technical support staff by means of an online
form:

www.mts.com > Contact MTS > Service & Technical Support button

E-mail [email protected]

Telephone MTS Call Center 800-328-2255

Weekdays 7:00 A.M. to 5:00 P.M., Central Time

Fax 952-937-4515
Please include “Technical Support” in the subject line.

Outside the U.S. For technical support outside the United States, contact your local sales and
service office. For a list of worldwide sales and service locations and contact
information, use the Global MTS link at the MTS web site:

www.mts.com > Global MTS > (choose your region in the right-hand
column) > (choose the location closest to you)

MTS MultiPurpose TestWare® Technical Support 7

Before You Contact MTS
MTS can help you more efficiently if you have the following information
available when you contact us for support.

Know your site The site number contains your company number and identifies your equipment
number and system type (such as material testing or simulation). The number is typically written on a
number label on your equipment before the system leaves MTS. If you do not know your
MTS site number, contact your sales engineer.

Example site number: 571167

When you have more than one MTS system, the system job number identifies
your system. You can find your job number in your order paperwork.

Example system number: US1.42460

Know information from If you have contacted MTS about this problem before, we can recall your file
prior technical based on the:
assistance
• MTS notification number

• Name of the person who helped you

Identify the problem Describe the problem and know the answers to the following questions:

• How long and how often has the problem occurred?

• Can you reproduce the problem?

• Were any hardware or software changes made to the system before the
problem started?

• What are the equipment model numbers?

• What is the controller model (if applicable)?

• What is the system configuration?

8 Technical Support MTS MultiPurpose TestWare®

 Know relevant For a computer problem, have the following information available:
computer information
• Manufacturer’s name and model number

• Operating software type and service patch information

• Amount of system memory

• Amount of free space on the hard drive where the application resides

• Current status of hard-drive fragmentation

• Connection status to a corporate network

Know relevant For software application problems, have the following information available:
software information
• The software application’s name, version number, build number, and (if
available) software patch number. This information can typically be found
in the About selection in the Help menu.

• The names of other applications on your computer, such as:

– Anti-virus software

– Screen savers

– Keyboard enhancers

– Print spoolers

– Messaging applications

If You Contact MTS by Phone

A Call Center agent registers your call before connecting you with a technical
support specialist. The agent asks you for your:

• Site number

• Name

• Company name

• Company address

• Phone number where you can be reached

If your issue has a notification number, please provide that number. A new issue
will be assigned a unique notification number.

MTS MultiPurpose TestWare® Technical Support 9

 Identify system type To enable the Call Center agent to connect you with the most qualified technical
support specialist available, identify your system as one of the following types:

• Electromechanical material test system

• Hydromechanical material test system

• Vehicle test system

• Vehicle component test system

• Aero test system

Be prepared to Prepare to perform troubleshooting while on the phone:

troubleshoot
• Call from a telephone close to the system so that you can implement
suggestions made over the phone.

• Have the original operating and application software media available.

• If you are not familiar with all aspects of the equipment operation, have an
experienced user nearby to assist you.

Write down relevant In case Technical Support must call you:

information
• Verify the notification number.

• Record the name of the person who helped you.

• Write down any specific instructions.

After you call MTS logs and tracks all calls to ensure that you receive assistance for your
problem or request. If you have questions about the status of your problem or
have additional information to report, please contact Technical Support again and
provide your original notification number.

Problem Submittal Form in MTS Manuals

Use the Problem Submittal Form to communicate problems with your software,
hardware, manuals, or service that are not resolved to your satisfaction through
the technical support process. The form includes check boxes that allow you to
indicate the urgency of your problem and your expectation of an acceptable
response time. We guarantee a timely response—your feedback is important to
us.

10 Technical Support MTS MultiPurpose TestWare®

 Access the Problem Submittal Form:

• In the back of many MTS manuals (postage paid form to be mailed to MTS)

• www.mts.com > Contact Us > Problem Submittal Form button (electronic

form to be e-mailed to MTS)

MTS MultiPurpose TestWare® Technical Support 11

12 Technical Support MTS MultiPurpose TestWare®
Preface
Before You Begin
Safety first! Before you use your MTS product or system, read and understand the Safety
manual and any other safety information provided with your system. Improper
installation, operation, or maintenance can result in hazardous conditions that can
cause severe personal injury or death, or damage to your equipment and
specimen. Again, read and understand the safety information provided with your
system before you continue. It is very important that you remain aware of
hazards that apply to your system.

Other MTS manuals In addition to this manual, you may receive additional manuals in paper or
electronic form.

You may also receive an MTS System Documentation CD. It contains an

electronic copy of the manuals that pertain to your test system, such as:

• Hydraulic and mechanical component manuals

• Assembly drawings

• Parts lists

• Operation manual

• Preventive maintenance manual

Controller and application software manuals are typically included on the

software CD distribution disc(s).

MTS MultiPurpose TestWare® Preface 13

Conventions

Conventions
Documentation Conventions
The following paragraphs describe some of the conventions that are used in your
MTS manuals.

Hazard conventions Hazard notices may be embedded in this manual. These notices contain safety
information that is specific to the activity to be performed. Hazard notices
immediately precede the step or procedure that may lead to an associated hazard.
Read all hazard notices carefully and follow all directions and recommendations.
Three different levels of hazard notices may appear in your manuals. Following
are examples of all three levels.

Note For general safety information, see the safety information provided with
your system.

DANGER

Danger notices indicate the presence of a hazard with a high level of risk which,
if ignored, will result in death, severe personal injury, or substantial property
damage.

WARNING

Warning notices indicate the presence of a hazard with a medium level of risk
which, if ignored, can result in death, severe personal injury, or substantial
property damage.

CAUTION

Caution notices indicate the presence of a hazard with a low level of risk which,
if ignored, could cause moderate or minor personal injury or equipment damage,
or could endanger test integrity.

Notes Notes provide additional information about operating your system or highlight
easily overlooked items. For example:

Note Resources that are put back on the hardware lists show up at the end of
the list.

Special terms The first occurrence of special terms is shown in italics.

14 Preface MTS MultiPurpose TestWare®

 Conventions

Illustrations Illustrations appear in this manual to clarify text. They are examples only and do
not necessarily represent your actual system configuration, test application, or
software.

Electronic manual This manual is available as an electronic document in the Portable Document
conventions File (PDF) format. It can be viewed on any computer that has Adobe Acrobat
Reader installed.

Hypertext links The electronic document has many hypertext links displayed in a blue font. All
blue words in the body text, along with all contents entries and index page
numbers, are hypertext links. When you click a hypertext link, the application
jumps to the corresponding topic.

MTS MultiPurpose TestWare® Preface 15

Conventions

16 Preface MTS MultiPurpose TestWare®

Chapter 5
About MultiPurpose TestWare
Contents About MTS MultiPurpose TestWare (MPT) 18
About MPT Test Procedures 18
About MPT Processes 19
Default Test Procedure Locations 19
Test Procedures in Projects 20
About the MPT User Interface 21
About the MPT Control Panel 25
MPT Control Panel Toolbar 26
MPT Test Progress Panel 28
MPT Specimen Panel 29
MPT Power Panel 31
MPT Channel Counters Panel 32
MPT Sequence Counters Panel 33
About Process Specific Panels 34
MPT Run/Stop/Hold Panel 35
About the MPT Procedure Editor 36
MPT Procedure Editor Menu 37
Group Menu 37
Display Menu 37
Tools Menu 38
MPT Procedure Editor Toolbar 38
Procedure Table 40
Process Palette 42

MTS MultiPurpose TestWare® About MultiPurpose TestWare 17

Application Overview

Application Overview
About MTS MultiPurpose TestWare (MPT)
MTS Model 793.10 MultiPurpose TestWare is an advanced test design
application available to MTS 793 Controllers.

With MultiPurpose TestWare, you can:

• Create complex test designs that include command, data acquisition, event
detection, and external control instructions.

• Generate programs based on profiles created with a text editor application, a

spreadsheet application, or the Model 793.11 Profile Editor application.

• Acquire and monitor real-time trend or fatigue data.

About MPT Test Procedures

With MultiPurpose TestWare, you create test procedure (.000) files. A test
procedure contains two types of information:

• Process information, which defines your processes (command, data

acquisition, signal monitoring, and so forth) and the sequence in which each
process runs.

• MPT application information, which includes test unit and dimension

assignments, the behavior of hold and resume functions, the data file format,
and so on.

To create procedures You create procedures by linking together processes that represent individual test
activities, such as ramping the actuator or acquiring peak/valley data.

To run procedures You run test procedures with the run, stop, and hold controls on the Station
Controls panel in the Station Manager application.

For more information For information on how to create a procedure, see “Creating a Practice Test
Procedure” on page 153.

For more information about how to run test procedures, see“How to Run a
Procedure” on page 48.

18 About MultiPurpose TestWare MTS MultiPurpose TestWare®

 Application Overview

About MPT Processes

When you create tests with the MPT application, you use MPT processes like
building blocks to define test actions such as sending command signals,
performing data acquisition, and responding to test events.

A complete MPT test normally consists of a number of MPT processes linked

together and saved as an MPT procedure.

Process categories Processes are grouped on the palette in the following categories:

• Command Processes send commands to a servovalve or external controller

to apply forces to the physical specimen.

• Data Acquisition Processes acquire sensor data from the physical

specimen.

• Event Processes monitor test signals and perform actions when specified
conditions are met.

• External Control Processes control external controllers or logic devices.

• Other Processes perform miscellaneous functions.

Default Test Procedure Locations

In MTS 793 software version 3.5x or earlier, the default location of test files is:

C:\MTS software product name (for example, “FTGT”)\MPT\Procs

In MTS 793 software version 4.0 or later, the default location of test files is:

C:\MTS 793\Projects\Project name (for example, “Project 1”)\MPT\Procedures

MTS MultiPurpose TestWare® About MultiPurpose TestWare 19

Application Overview

Test Procedures in Projects

A Project is a folder that contains or references files that are used and generated
by MTS 793 applications. When you start Station Manager, you select a Project.
MultiPurpose TestWare inherits the Project selected for Station Manager. The
current Project determines the location of MultiPurposeTestWare test procedures.

By default, Projects contain test procedures in the Procedures subfolder. You can
use the Project Manager application to change the location of test procedures.

For more information about the Project Manager and Projects, see the MTS 793
Control Software manual (PN 100-147-130), and the MTS 793 Controller
Overview manual (PN 100-162-928).

20 About MultiPurpose TestWare MTS MultiPurpose TestWare®

 The MultiPurpose TestWare Interface

The MultiPurpose TestWare Interface

About the MPT User Interface
When you have an existing station configuration open with the Station Manager
application, then select MultiPurpose TestWare from the Applications menu,
the display changes and appears as shown.

• The MPT control panel provides access to all the functions needed to create,
edit, and run procedures for the current station configuration.

• The run, stop, and hold controls pertain to procedures.

• Also, if the current procedure includes an Operator Event process, a special

panel appears in the initial display.
Note When you select MPT this way, you can create, edit, and run
procedures. You can also select an ‘edit only’ instance of MPT
(Applications > MultiPurpose TestWare (Edit Only)) to run one
procedure while editing other procedures.

MTS MultiPurpose TestWare® About MultiPurpose TestWare 21

The MultiPurpose TestWare Interface

MPT control panel The MPT control panel appears in the application area of Station Manager, as
shown.

MPT Procedure Editor button Station Controls

Displays the Procedure Editor and You run MPT procedures with
Process Palette, as shown on the the run, stop, and hold
next page. controls.

MPT toolbar

MPT application button

When you launch MPT this
button appears in the
applications control panel.
You can quickly select
among launched
applications with the buttons
in this panel.

Channel Counters
Channel Counters display
the cumulative count of
segments applied to
specific channels.

Sequence Counters
Sequence counters display
current and target counts for
processes. Individual process
counters are arranged
according to the process icons
on the Procedure Editor. Group
process counters are indented
to show nesting.

22 About MultiPurpose TestWare MTS MultiPurpose TestWare®

 The MultiPurpose TestWare Interface

Procedure Editor The Procedure Editor contains a table on which you build MPT test procedures
by selecting, assigning parameters to, and sequencing individual test processes.
Test processes represent individual test activities.

The contents of the currently selected nesting level is displayed in the procedure
table pane. If a nested group process is selected, the general parameters for the
group are shown in the active process parameters pane.

Double-clicking on a parameter in the navigation pane or procedure table will

maximize the active process parameters pane. The contents of pane (default
view) and the expanded window are both editable. Minimizing or closing this
window restores the default view.

Procedure Editor
(default view)
The Procedure
Editor contains a
table on which you
build MPT test
procedures.

Navigation Pane
Provides a tree view
of the processes in
the procedure table
pane.

Status and progress

indicators for
processes lets you
watch the progress
of the test
(not shown):
A blue arrow indicates that the process is
executing.
A red “X” indicates that the process is disabled.
A green arrow indicates that the process is Active Process Parameters Pane
configured to issue a done signal immediately The parameters for the currently selected
without performing its programmed activity. process appear in this pane.

MTS MultiPurpose TestWare® About MultiPurpose TestWare 23

The MultiPurpose TestWare Interface

Process Palette The processes available are displayed on the Process Palette. Individual
processes are arranged on the palette by type. You can double-click a process on
the Process Palette to copy an instance of it to the procedure table, or you can use
the drag-and-drop method.

Process Pallete
Individual processes are
arranged on the palette by type.

You can double-click a process

on the Process Palette to copy
an instance of it to the table on
the Procedure Editor, or you can
use the drag-and-drop method.

24 About MultiPurpose TestWare MTS MultiPurpose TestWare®

 The MultiPurpose TestWare Interface

About the MPT Control Panel

With the MPT control panel you can:

• Access common controls from the toolbar (including the MPT Procedure
Editor, the place where you build procedures)

• Monitor the test’s status and counter information (channel, sequence, and
run time counters)

• Create and rename MPT specimens

The MPT control panel

includes a toolbar that
performs actions (like
unlocking procedures) and
provides access to editors
(like the MPT Procedure
Editor and the MPT
Specimen Editor) and the
MPT Specimen Log.

For more information For more information about setting MPT control panel preferences, see “MPT
Options Editor Control Panel Tab” on page 79.

MTS MultiPurpose TestWare® About MultiPurpose TestWare 25

The MultiPurpose TestWare Interface

MPT Control Panel Toolbar

The buttons that comprise the MPT control panel toolbar provide quick access to
common commands and windows.

MPT Control Panel Toolbar (part 1 of 2)

ITEM DESCRIPTION

Displays the Open Procedure window, saves the current procedure, or displays
the Save Procedure As window.
You can use the Open Procedure window functions to navigate to, select, and
open an existing procedure. You can use the Save Procedure As window
functions to save the current procedure as a new file with a specified name and
location.
Note If you select Save Procedure for a procedure that has never been
save, the application displays the Save Procedure As window. With
this window you can name the procedure and save it to the location
you desire.

Creates a new MPT specimen for the procedure that is currently loaded. The
new folder is immediately visible in the Specimen panel.

Displays the MPT Specimen Editor . You can use the MPT Specimen Editor to
create and edit multiple MPT specimens.

Displays the MPT Specimen Log which contains messages that pertain to the
current MPT specimen.

Displays the MPT Options Editor. With the MPT Options Editor, you can
customize the MPT interface to suit your needs by defining control options and
preferences.

Displays the MPT Procedure Editor, the place where you create and edit
procedures consisting of MPT test processes.
Note To edit a selected procedure on the MPT Procedure Editor, you must
first be in the Edit mode.

Resets the current procedure to the beginning. Pressing run after pressing reset
restarts the procedure from the beginning.
Note After the procedure completes, you must click Reset before you can
run the procedure again on the same MPT specimen.

26 About MultiPurpose TestWare MTS MultiPurpose TestWare®

 The MultiPurpose TestWare Interface

MPT Control Panel Toolbar (part 2 of 2)

ITEM DESCRIPTION

Changes between edit and execute test modes. To change (toggle between)
modes, click the edit /execute mode button.
Edit mode You must be in edit mode to create or make changes to your procedure.
Note You cannot switch to edit mode if the procedure is running or holding.

You must be in the execute mode to run your test. The procedure automatically
switches to execute mode if you click run on the Station Controls panel.
Note When you change to execute mode, the MPT application becomes the
controlling application of the control channels used in the procedure.
Execute mode You cannot use the Station Managermanual command controls on
the control channels used in the procedure.

Quits the MultiPurpose TestWare application.

For more information See “MPT Specimen Editor” on page 131.

See “About the MPT Procedure Editor” on page 36.

See “Edit mode” on page 27.

MTS MultiPurpose TestWare® About MultiPurpose TestWare 27

The MultiPurpose TestWare Interface

MPT Test Progress Panel

The Test Progress panel displays the elapsed run time of the test that is in
progress and indicates if the test is currently paused.

MPT Test Progress Panel

ITEM DESCRIPTION
Run Time Displays the elapsed time of the current test (the elapsed run time does not
include time spent in hold or stop states).
You can turn the Run Time display on-and-off and select a display format
using the Control Panel tab of the MPT Options Editor.
To access the Run Time menu when the procedure is locked and reset, right-
mouse click with the cursor positioned over the Run Time counter to display.
Select the Reset menu item to reset the Run Time counter to zero.
Paused Indicates when the procedure has been paused by a Program Control process.
The paused state is not the same as the hold state.
• When the test is holding, you must click the run button to resume the test.

• When the test is paused, the test must be resumed by another Program
Control process (set to Program Resume).

For more information See “MPT Options Editor Control Panel Tab” on page 79.

For more information about pausing a test with the Program Control process, see
“About the Program Control Process” on page 400.

28 About MultiPurpose TestWare MTS MultiPurpose TestWare®

 The MultiPurpose TestWare Interface

MPT Specimen Panel

The Specimen panel displays the current MPT specimen selection and the
Procedure Name and Procedure State associated with the selected specimen. In
addition, you can use this panel to navigate to other MPT specimens displayed in
the Specimen list.

MPT Specimen Panel (part 1 of 2)

ITEM DESCRIPTION
Specimen Displays the MPT specimen that is linked to the procedure.
You can select the desired MPT specimen from the Specimen list or click
to create a new MPT specimen.

Use the up and down scroll arrows to select an available MPT specimen from
the list. You can rename the selected MPT specimen (if you are in edit mode)
by typing over the folder name in the Specimen box.
Note New MPT specimens that are created using the new specimen icon are
assigned names that are based on a default root name (for example,
“spec”) with an incremental number suffix. The default root can be
changed with the Project Manager application.

Note To cut, copy, paste, or delete the displayed MPT specimen name,
right-mouse click on the current MPT specimen name and select the
desired right-mouse menu item.

MTS MultiPurpose TestWare® About MultiPurpose TestWare 29

The MultiPurpose TestWare Interface

MPT Specimen Panel (part 2 of 2)

ITEM DESCRIPTION
Procedure Name Displays the name of the current procedure selection. The procedure name is
established when you save the procedure.
Procedure State Displays the current state of the procedure, which may be one of the following:
• Reset—The test is at the beginning but has not been started.

• In Progress—The test has started but is not yet completed.

• Done—The test has been completed.

Note To run the procedure on the same MPT specimen again, press Reset.
Otherwise, create a new MPT specimen for the next instance of
running the same procedure.

• Error—An error has occurred (you must click Reset to run the test
again).

For more information For more information about MPT specimens, see “Working with MPT
Specimens” on page 125.

30 About MultiPurpose TestWare MTS MultiPurpose TestWare®

 The MultiPurpose TestWare Interface

MPT Power Panel

The Power panel displays the hydraulic supply pressure required to run the
selected test.

MPT Power Panel

ITEM DESCRIPTION
To Run Displays the hydraulic pressure required to run the control channels in the
current procedure (hydraulic pressure options are High, High/Low, Off/
Interlocked, or Off).
Note Power status applies only to control channels. If a procedure does not
contain control channels, the power status has no effect on the
procedure. For instance, if you remove hydraulic power from a
procedure that does not include control channels, the procedure is still
valid.

You can specify the required hydraulic pressure for the control channels of the
current procedure using the Execution tab of the MPT Options Editor.
Note You must be in edit mode to change settings on the Execution tab.

The High selection applies to most testing situations. High requires you to
operate MPT with high hydraulic pressure applied to the station’s Hydraulic
Service Manifolds (HSM).
The Off/Interlocked and Off selections are typically used while you are
learning the application software or running test simulations.
The Off/Interlocked selection disregards active interlocks for the sake of
allowing you to run the test unhindered.

For more information See “MPT Options Editor Execution Tab” on page 62.

MTS MultiPurpose TestWare® About MultiPurpose TestWare 31

The MultiPurpose TestWare Interface

MPT Channel Counters Panel

The Channel Counters panel displays the running total of completed command
channel cycles or segments during test execution.

MPT Channel Counters Panel

ITEM DESCRIPTION
Channel Counters Displays a running total of the cycles or segments that have been run during
the test for each command channel specified in the procedure.
The Channel Counters panel displays all channels that are selected for use
during a test. A channel does not have to be used in every process to be
displayed.
You can specify the Channel Counters display format using the Control
Panel tab of the MPT Options Editor. You must be in edit mode to change the
Control Panel settings.
To access menu items that pertain to Channel Counters position the cursor
over the Channel Counters display and perform a right-mouse click. When
you do this, the Reset Counters and Set Counters... menu items appear
(provided that the procedure is locked and in the reset state). The Reset
Counters selection resets all active channel counters to zero. With the Set
Counters... selection you can manually set each channel counter to a user
specified value.

For more information See “MPT Options Editor Control Panel Tab” on page 79.

32 About MultiPurpose TestWare MTS MultiPurpose TestWare®

 The MultiPurpose TestWare Interface

MPT Sequence Counters Panel

The Sequence Counters panel displays process counters for each specified
counter using the selected process counter format.

MPT Sequence Counters Panel

ITEM DESCRIPTION
Sequence Counters Displays individual process counters. You can specify the counter type using
the General tab of each process parameters window.
• If you specified a Fixed counter, the counter label and counter are
displayed for the duration of the procedure.

• If you specified a Transient counter, the counter label and counter are
displayed only while the process is active.

For more information For more information about using counters, see “About Counters” on page 49.

MTS MultiPurpose TestWare® About MultiPurpose TestWare 33

The MultiPurpose TestWare Interface

About Process Specific Panels

Process specific panels display only when certain processes are selected from the
Process Palette and are configured specifically to display at or during run time.
Examples of some of these displays are shown below.

Profile Counter Panel

Note Applies to Time History

Output, Time History
Input, and Road
Surface Output
processes only.

Process Status Panel

Operator Events Panel

For more information For more information about these panels, see “About MPT Processes” on page
84.

34 About MultiPurpose TestWare MTS MultiPurpose TestWare®

 The MultiPurpose TestWare Interface

MPT Run/Stop/Hold Panel

The run/stop/hold panel controls run, stop, and hold test activities for the current
application. When you select MultiPurpose TestWare from the Applications
menu, it becomes the controlling application and “MPT” appears on this panel.

MPT Run/Stop/Hold Panel

ITEM DESCRIPTION

Starts the procedure. When you click this button, the run indicator blinks while
the procedure transitions from the current state to the “run” state. Once the run
state is achieved the indicator remains constant unless additional transitions or
program induced pauses occur. Additional blinks may occur depending on the
duration of the transition or pause.

Suspends all active command and data acquisition processes.

Note Active limit detector and digital input processes remain active.

When you click hold, the hold indicator blinks while the procedure transitions
from the current state to the “hold” state. Once the hold state is achieved, the
indicator remains constant. To resume the run state from the hold state, click
run.
Note The hold button may be disabled if Ignore Hold Event is selected on
the MPT Options Editor window Execution tab.

Stops the procedure. When you click stop, the stop indicator blinks while the
procedure transitions from the current state to the “stop” state. Once the stop
state is achieved, the indicator remains constant.

MTS MultiPurpose TestWare® About MultiPurpose TestWare 35

MPT Procedure Editor

MPT Procedure Editor

About the MPT Procedure Editor
The MPT Procedure Editor is where you create procedures by combining and
defining the parameters of individual test processes available on the Process
Palette.

To display the MPT Procedure Editor, click on the icon in the MPT
toolbar.

The MPT Procedure

Editor includes the
menu, toolbar,
procedure table,
navigation pane, and
active process
parameter information
pane.
You create procedures
by populating the
procedure table with
test processes from the
Process Palette.

“Simulation” appears in the status bar when you run the “Demo”
(demonstration) System Loader program.

36 About MultiPurpose TestWare MTS MultiPurpose TestWare®

 MPT Procedure Editor

MPT Procedure Editor Menu

The following menus are available on the MPT Procedure Editor window:

• Group Menu

• Display Menu

• Tools Menu

• MPT Procedure Editor Toolbar

Note When viewing the output files generated by the Print Procedure, Print
Preview, and Print to File selections, items preceded by an asterisk (*)
have been changed since the procedure was last opened or saved.

Group Menu
Use the Group menu commands to restore, navigate through, and control
specific Group table functions.

Group Menu
ITEM DESCRIPTION
Procedure Restores the main procedure table if it has been minimized or hidden.
Next Opens the Group table for the selected group process.

Note This command is only available when you select a Group process
icon.

Previous Displays the parent procedure table for the current Group table.

Note This command is only available when you are in a Group table.

Display Menu
Use the Display menu commands to:

• Change between the test edit mode and test execution mode.

• Display the Process Palette.

• Display the MPT Specimen Log

MTS MultiPurpose TestWare® About MultiPurpose TestWare 37

MPT Procedure Editor

Tools Menu
Use the Tools menu commands to display various editors used to customize the
MPT environment and/or the current procedure.

Tools Menu
ITEM DESCRIPTION
Specimen Editor Displays the MPT Specimen Editor.
Unit Set Editor Displays the Unit Set Editor.
Options Editor Displays the Options Editor.

MPT Procedure Editor Toolbar

The buttons that comprise the MPT Procedure Editor toolbar provide quick
access to common commands and windows.

MPT Procedure Editor Toolbar (part 1 of 2)

ITEM DESCRIPTION

Deletes the process (or processes) selected in the active procedure table.

Opens the next group table. This button is only active if there are multiple
group tables available.

Opens the previous group table. This button is only active if there are multiple
group tables available.

Displays the Process Palette. You can select processes from the palette to copy
to the MPT Procedure Editor, or you can drag and drop processes from the
palette to the MPT Procedure Editor.

Displays the MPT Options Editor. With the MPT Options Editor, you can
select control options and preferences for the current procedure.

Displays the MPT Variables Editor.

Displays the MPT Specimen Editor. You can use the MPT Specimen Editor to
create and edit multiple MPT specimens.

38 About MultiPurpose TestWare MTS MultiPurpose TestWare®

 MPT Procedure Editor

MPT Procedure Editor Toolbar (part 2 of 2)

ITEM DESCRIPTION

Displays the MPT Specimen Log for the current MPT specimen.

Changes between edit and execute test modes. To change (toggle between)
modes, click the edit /execute mode button.
Edit mode You must be in edit mode to create or make changes to your procedure.
Note You cannot switch to edit mode if the procedure is running or holding.

You must be in execute mode to run your test. The procedure automatically
Execute mode switches to execute mode if you click Run on the Station Controls panel.
Note When you change to execute mode, MPT takes control of the various
resources used in the procedure, such as control channels, digital
output channels, and so on. You cannot use these resources with
Station Manager until you unlock the procedure and attain the edit
mode.

Trash can. Processes are not stored in the trash can as they are in the Windows
Recycling Bin. They are deleted immediately after you drag them to the trash
can icon.

For more information See “Process Palette” on page 84.

See “About the MPT Options Editor” on page 62.

See “MPT Specimen Editor” on page 131.

MTS MultiPurpose TestWare® About MultiPurpose TestWare 39

MPT Procedure Editor

Procedure Table
You use this pane to organize and synchronize the processes that make up your
test.

Access From the MPT Procedure Editor pane, the access paths are:

File > Open (or New) Procedure

Or

Group > Procedure

Process Type Name Start Trigger Interrupt Trigger

Navigation
Pane

Active
Process
Parameters

40 About MultiPurpose TestWare MTS MultiPurpose TestWare®

 MPT Procedure Editor

Procedure Table
ITEM DESCRIPTION
Process indicators Indicate the status of the adjacent process. Indicators have the following
meanings:
The process is enabled and active.

The process has been disabled.

The process is enabled, but configured to run zero times.

Type Displays the individual process icons that you have selected. You can double-
click an icon to open the associated process parameters window. In addition, if
you right-click on an icon you can open the parameters window associated
with the process, open a new process (or group) table, enable or disable the
process, and delete the process.
Start Specifies the triggers or events that cause this process to start.
Interrupt Specifies the triggers or events that interrupt this process.
Procedure is done Specifies the triggers or events that cause the end of the procedure.
when

MTS MultiPurpose TestWare® About MultiPurpose TestWare 41

MPT Procedure Editor

Process Palette
Use the Process Palette to select test processes by using their representative
icons.

Access From the MPT Procedure Editor window, the access paths are:

Display > Process Palette

Or:

Note Some processes

are optional and
appear on the
Process Palette
only when
purchased
separately.

The Process Palette contains the icons of processes that you can add to the
procedure table to build a procedure.

For more information See “How to Add Processes to the Procedure Table” on page 85.

42 About MultiPurpose TestWare MTS MultiPurpose TestWare®

Chapter 6
Performing Common Tasks
Contents How to Start MultiPurpose TestWare 44
How to Display the MPT Procedure Editor 44
How to Create a New Procedure 44
Considerations for Test Design and Execution 45
How to Open a Procedure 47
How to Save a Procedure 47
How to Preview a Procedure 47
How to Print a Procedure 47
How to Run a Procedure 48
About Counters 49
Types of Counters 49
How to Display Counters and Status Panels 51
About the Clear Counters on Reset Function 53
About Working with Unit Assignment Set Editor 55
About the MPT Specimen Log 57

MTS MultiPurpose TestWare® Performing Common Tasks 43

How to Start MultiPurpose TestWare

How to Start MultiPurpose TestWare

From Station Manager To start the MultiPurpose TestWare application, you must first start the Station
Manager application and open a station configuration.

Once the configuration file is open, on the Station Manager Applications menu,
click MultiPurpose TestWare to display the MPT control panel.

You can run existing procedures from the MPT control panel. If you want to edit
or create new procedures, you need to access the MPT Procedure Editor.

From other MTS From the Station Desktop Organizer Start Applications menu: click Station
applications Manager, open a station configuration, and on the Applications menu, click
MultiPurpose TestWare.

On the Project Manager tool bar: click the Station Manager icon, or from the
Applications menu, click Station Manager. Then on the Applications menu,
click MultiPurpose TestWare.

For more information For more information, see “About the MPT Procedure Editor” on page 36.

How to Display the MPT Procedure Editor

On the MPT control panel toolbar, click .

How to Create a New Procedure

When you start MPT a new (undefined) procedure is automatically created. To
create a new procedure any time MPT is active, from the MPT Procedure Editor,
select the File menu, then click New Procedure.

Even so, if you follow along and create a less complex version of the test
procedure, or even if you just review the pages without using your software, you
still benefit by learning the fundamentals of creating test procedures.

Note The hardware resources and label names provided in this section are for
illustration purposes only. Your hardware resources and label names
typically vary with the hwi file and station configuration file you use.

For more information If you would like to review a sample test design, see “Creating a Practice Test
Procedure” on page 153.

44 Performing Common Tasks MTS MultiPurpose TestWare®

 Considerations for Test Design and Execution

Considerations for Test Design and Execution

Undesirable latencies One consideration of test procedure design is the potential for undesirable
in test procedures latencies between test activities. There is, of course, a certain amount of latency
between test activities due to intra-system communication which cannot be
avoided. Latencies beyond this though, may be undesirable for some tests,
especially if your test involves rapid switching between test activities of short
durations. The way you design test procedures and manage the execution of test
procedures can minimize unwanted latencies.

Design tests to If your command waveform is all in the same control mode, it is best to design
minimize undesirable your test using a Profile file, and run the Profile file with the MPT Profile
latencies process.

You create a Profile file with a spreadsheet application or the MTS Model 793.11
Profile Editor application. A Profile file consists of a series of segments. When
MPT runs the segments within a Profile file they are not vulnerable to delays (as
compared to executing a series of individual MPT command processes). MPT
queues multiple rows of the Profile file to the segment generator simultaneously,
and if you specify multiple passes, the output proceeds with the next pass without
delay.

Other considerations Many tests, of course, require control mode changes in the command waveform.
to minimize In this case, you must choose individual MPT command processes as required,
undesirable latencies and assign triggers to link their execution.

Triggering from one MPT process to the next occurs on the Microsoft Windows
workstation, which makes them vulnerable to undesirable latencies due to other
activity on the workstation. Likely candidates include networking, video drivers
without adequate hardware acceleration, and other communication with the
controller, including running other test stations simultaneously.

To reduce unwanted latencies in this scenario, minimize operations involving the

Microsoft Windows operating system while your test is running.

Avoid the use of third MTS also recommends that you avoid running third-party software applications,
party software including virus-checking software, when running any of the MTS 793 software
applications. Testing has revealed that some third-party software can consume
the majority of the PC is available processing power. These applications, if run
along with MTS 793 software applications, may cause communication with the
controller to cease. Ultimately, this causes the station and applications on it to
terminate.

MTS MultiPurpose TestWare® Performing Common Tasks 45

Considerations for Test Design and Execution

Design elements that You can inadvertently design an MPT procedure that can lock up your system.
may lock up your The cause is generally from:
system
• Requesting too much data acquisition or command generation, or

• Setting up a group process to repeat continuously when it does not contain

command or data acquisition processes. To understand this, think of
processes in these categories:

– Command and Data Acquisition—These processes initiate activity

within the machine, and wait for it to complete.

– Immediate Action (Digital Output and Program Control)— These

processes execute an action and complete immediately.

– Detectors (Digital Input and Data Limit)—These processes complete

immediately if their condition is initially met.

Note If you create a repeating group process that contains only “Immediate
Action” and “Detector” processes, care must be taken so that the
detectors do not complete and repeat a number of times in quick
succession without waiting for some other test activity. For example, if a
data limit is set up in a repeating group with no other actions, and the
data value always causes a limit detect, the system may lock up.

For more information See “About Sequencing Processes” on page 87.

46 Performing Common Tasks MTS MultiPurpose TestWare®

 How to Open a Procedure

How to Open a Procedure

1. From the MPT control panel (or from the MPT Procedure Editor), click the
Open Procedure icon. Alternately, from the MPT Procedure Editor, click
the File menu, then click Open Procedure to display the Open Procedure
window.

2. Double-click the desired procedure, or click the desired procedure once,

then click the Open button.

How to Save a Procedure

From the MPT Procedure Editor, click the Save Procedure icon, or click the File
menu and select the desired save option.

Alternately, from the MPT control panel, on the toolbar, click the Open
Procedure icon’s pull down menu, then select the desired save option.

Note MultiPurpose TestWare automatically appends “.000” to the file name

you type. If you do not want to include the .000 extension, type a period
(.) at the end of your file name.

How to Preview a Procedure

From the MPT Procedure Editor, select the File menu, then click Print Preview
to view your procedure on-screen. Items preceded by an asterisk (*) have been
modified since the procedure file was open.

How to Print a Procedure

From the MPT Procedure Editor, select the File menu, then click Print
Procedure.

Click Print to File to save the procedure to a text file.

MTS MultiPurpose TestWare® Performing Common Tasks 47

How to Run a Procedure

How to Run a Procedure

Running a procedure begins with station preparation and physical specimen
installation, both tasks that you accomplish with the Station Manager application.

The following steps assume you have already done the following:

• Created a configuration file with Station Builder, and tuned control channels
and calibrated sensor/conditioner pairs

• Opened Station Manager and selected the configuration file

• Applied hydraulic pressure to the station

• Installed the physical specimen into the test fixturing

• Set station limits

• Set up readout devices to monitor station signals

• Opened MultiPurpose TestWare

• Selected a procedure

1. Create or select an MPT specimen

Before you can run a procedure, you have to either create a new specimen or
select an existing MPT specimen for the test.

The term “MPT specimen” refers to a directory of information associated

with a specific execution of a procedure—not the physical specimen being
tested.

Your test data, as well as the procedure you ran, messages generated during
the test, recovery information, and so forth, is captured in the MPT
specimen you create for this test.

A. To create a new MPT specimen:

On the MPT control panel toolbar, click and a new MPT

specimen appears in the list box (for example, (“spec01,” “spec02,”
and so forth.). Rename the new MPT specimen as desired.

B. To select an existing MPT specimen:

On the MPT control panel toolbar, select an existing MPT specimen

from the Specimen list box.

48 Performing Common Tasks MTS MultiPurpose TestWare®

 About Counters

2. Start your test.

On the Station Controls panel click the run button to start the test. Look at
and listen to your test station after you start the test. If everything seems
normal, you can let your test run to completion.
Note After the completion of a test you have to press the reset button or create
a new MPT specimen to run subsequent tests.

About Counters
When you create a procedure with MPT, you define the parameters of each
process in the procedure, including counter parameters.

In procedures, counters are linear tools used to indicate test progress and
facilitate recovery. It is important to understand counters and to realize that how
you define a counter can affect your test outcome and, as a result, the data that is
generated from the test.

Note Counters are not the only tools provided by the MPT application to
indicate test progress. The MPT Procedure Editor displays special
symbols when individual processes are active.

The various types of counters available for procedures are displayed on the MPT
control panel, provided the MPT control panel has been configured to display
them.

For more information See “About the MPT Control Panel” on page 25 for more information.

See “Procedure Table” on page 40 for more information about process indicators.

Types of Counters
The most prominent counters on the MPT control panel are the Run Time
counter, the Channel Counters, and the Sequence Counters.

There are also specialized counters that display only in association with specific
types of processes, such as:

• Profile counters, that appear only with the Profile Command and Profile
with ALC processes

• Status counters, that appear only with the Time History Input, Time History
Output, and Road Surface Output processes

MTS MultiPurpose TestWare® Performing Common Tasks 49

Types of Counters

Run time counter The Run Time counter displays the elapsed time of the current test since the last
time it was reset.

Channel counters Channel Counters display a cumulative count of segments or cycles that have
been applied to a specific channel since the start of the test.

Sequence counters Sequence Counters display the progress of individual processes within the test.
They can be especially useful for procedures that contain nested groups, because
you can configure them to show test progress within the nested structure of the
procedure.

This sample procedure includes a group process labeled “Cooling

Cycles,” which contains four nested processes (with indented
label names, “Trigger at 75C,” and so forth).
Name displays the assigned process label.
Current displays the current value of the counter.
Target displays the assigned number of times the process should
run (or repeat).

Profile counters Note Applies only to Profile and Profile with ALC processes.

Profile Counters display counters that increment according to special markers

that profile designers put in profiles.

Status counters Note Applies only to Time History Output, Time History Input, and Road
Surface processes.

50 Performing Common Tasks MTS MultiPurpose TestWare®

 How to Display Counters and Status Panels

Status counters display Elapsed Time (or Distance) and Total Time (or Total
Distance) counters, and a Percent Completed status bar.

• Elapsed Time displays the time since the process started. Distance displays
the distance traveled since the process started, which is calculated from the
Vehicle Speed entry on the process’ Status tab.

• Total Time displays the anticipated total time required to complete the
process (this does not include any other processes that may be part of the
test). Total Distance displays the anticipated total distance required to
complete the process, calculated from the Vehicle Speed entry on the
process’ Status tab.

• The Percent Completed status bar displays the percentage relationship of

the elapsed time (or distance) versus the total time (or distance) for the
process (the status bar updates according to the update rate of the test,
typically every 10 seconds or so).

How to Display Counters and Status Panels

You can choose to show or hide the various types of counters and status panels on
the MPT control panel when running tests.

Note The Run Time Counter, Channel Counters, and Sequence Counters
display by default.

Display Channel and To display Channel Counters and Sequence Counters:

Sequence Counters
1. Open the MPT Options Editor and select the Control Panel tab.

2. Locate the Counters panel.

3. Check the boxes as desired to show or hide the counters and to choose their
display format. By default these counters are displayed.

To display the Run Time counter:

1. Open the MPT Options Editor and select the Control Panel tab.

2. Locate the Test Progress panel.

3. Check the box as desired to show or hide the Run Time counter.

Display Status panels To display Status panels:

1. Open the relevant process on the procedure table (Time History Input, Time
History Output, and Road Surface Output) and select the Status tab.

MTS MultiPurpose TestWare® Performing Common Tasks 51

How to Display Counters and Status Panels

2. Check the Show Status Panel at Run Time box as desired. By default
status panels are not displayed.
Note If you enable the Show Status Panel at Run Time box, you have the
option of having the status panel display the distance traveled by the
vehicle, for which you type a nominal vehicle speed for the distance
calculations.

Profile Counters To display profile counters, you must include a Profile Command or Profile with
ALC process in your procedure that uses a profile that includes the keyword
“Action.”

Display individual The Sequence Counters panel displays by default, but each counter that populates
processes on the the Sequence Counters panel must be enabled for display individually. To do
Sequence Counters this you must open each process on the procedure table to display its Parameters
window, select the General tab, then select the desired Counter Type option.
panel
The Counter Type options are:

• None—The counter label and counter are not displayed on the Sequence
Counters panel.

• Transient—The counter label and counter are only displayed on the

Sequence Counters panel when the process is active. When the process
ends, transient counters disappear.

• Fixed—The counter label and counter are displayed on the Sequence

Counters panel for the duration of the test.

For more information For more information, see “Action and Counter Syntax” on page 498.

For information about changing default settings, see “How to Customize the
Default Template” on page 553.

52 Performing Common Tasks MTS MultiPurpose TestWare®

 About the Clear Counters on Reset Function

About the Clear Counters on Reset Function

With the Clear Counters on Reset check box (found on the Specimen tab of the
MPT Options Editor), you can choose whether run time, channel counters, and
profile counters:

• Clear when you reset the test (default setting), or

• Continue to increment after reset

Note Sequence Counters are always cleared on reset as this counter is used
in the recovery process.

Reset counters manually If the Clear Counters on Reset control is disabled and you want to manually
reset counters, you can:

• Select a new specimen (before resuming or between tests), or

• Right-click to reset each type of counter individually (applies to run time

counters, channel counters, and profile counters)

Use the right-mouse On the MPT control panel, position the cursor over the run time counter
menu for run time (ensuring the procedure is locked and reset), and click the right-mouse button to
counters display the Reset menu. With the Reset menu, you can reset the counter.

MTS MultiPurpose TestWare® Performing Common Tasks 53

About the Clear Counters on Reset Function

Use the right-mouse On the MPT control panel, position the cursor in the channel counter panel
menu for channel (ensuring the procedure is locked and reset) and click the right mouse button. The
counters Reset menu appears, which includes Reset Counters and Set Counters...
selections.

With the Reset Counters selection you can

manually reset the channel counters to zero.

With the Set Counters... window you can

manually set counter values.

Use the right-mouse On the MPT control panel, position the cursor over the profile counter panel
menu for profile counters when the counters are active and click the right-mouse button to display the
Reset Counters button. With the Reset Counters button, you can manually reset
the counters to zero.

Note The procedure does not have to be in the reset state to use the Reset
Counters button for profile counters. You can reset profile counters on-
the-fly, while the test is running.

54 Performing Common Tasks MTS MultiPurpose TestWare®

 About Working with Unit Assignment Set Editor

About Working with Unit Assignment Set Editor

Use the Unit Assignment Set Editor to create and modify unit assignment sets
(UAS). Unit assignment sets define the units of measurement that are available
for each dimension used in procedures.

Access From the MPT Procedure Editor windows the access path is:

Tools > Unit Set Editor

Note To use a UAS other than the default UAS, use the Unit Selection Tab of
the MPT Options Editor. To change the default UAS selection, use the
Project Manager application, or change the selection in the Station
Options window (Station Manager > Tools > Station Options > Unit
Selection).

Unit Assignment Set Editor (part 1 of 2)

ITEM DESCRIPTION

Displays the Unit Assignment Set Open window. With this window you can
Open select the appropriate unit assignment set and to complete the open function by
selecting the Open button.

Saves any changes to the selected unit assignment set.

Save

Displays the Unit Assignment Set Save As window. With this window you can
Save As view and edit the selected UAS Name and to complete the save function by
selecting the Save button.

Deletes the selected unit assignment set.

Delete

UAS Name Displays the name of the unit set currently selected.
UAS File Displays the file name of the unit set currently selected.

MTS MultiPurpose TestWare® Performing Common Tasks 55

About Working with Unit Assignment Set Editor

Unit Assignment Set Editor (part 2 of 2)

ITEM DESCRIPTION
Comment Displays a comment about the selected UAS. We recommend you describe the
characteristics of the unit set you create.
Dimension and Units Displays the dimensions and corresponding units used by the system software.
When you click a dimension name, the units assigned to the current set are
highlighted. To change a setting, click the dimension, and then click the
desired units.
Note You can quickly find an item in the Dimensions or Units list boxes
with the keyboard by typing the first letter of the desired item until it is
displayed. For example: To select the engineering force unit kN, type
the letter ‘k’ repeatedly until kN is highlighted in the list box.

Standard unit sets CGSSET - Centimeters-Grams-Seconds—Defines a set of units that is based

upon centimeters, grams, and seconds.

ENGSET - U.S. Engineering Units—Defines a set of units that contains

customary U.S. engineering units. It provides force-related units in “kip,” and
length-related units in “in.”

ENGSETSM - U.S. Engineering Units (small)—Defines a set of units that

contains customary U.S. engineering units. It provides force-related units, in
“lbf,” and length-related units in “in.”

SISET - SI (Systeme International d’Unites)—Defines a set of units that

contains customary international (metric) units. It provides force-related units in
“kN,” and length-related units in “mm.”

SISETSM - SI (Systeme International d’Unites) - small—Defines a set of

units that contains customary international (metric) units. It provides force, and
force-related units in “N,” and length-related units in “mm.”

SYSDEF - System Units Definition—Contains a copy of the units that are used
in the hardware and software to represent test values of interest.

56 Performing Common Tasks MTS MultiPurpose TestWare®

 About the MPT Specimen Log

About the MPT Specimen Log

Use the MPT Specimen Log to display a record of test events in the Message
Logs window.

Access From the MPT Procedure Editor window, the access paths are:

Display > Specimen Log

Or:

MPT control panel >

The MPT Specimen Log records selected station and test events as they occur.

Note The MPT Specimen Log is displayed on the Message Logs window,
which can also display Station Log information (by selecting Station
Log in the Log list).

Events that can be logged include file events, resource conflicts, hydraulic status
changes, station state changes, detector activity, hardware over temperature
conditions, and full-scale changes.

Counter data is saved to the MPT Specimen Log automatically and manually .

Auto-archive function The MPT application automatically saves your MPT Specimen Log when it
accumulates at least 1000 log entries. When log entries are saved to the log file,
they are cleared from the MPT Specimen Log display.

Specimen log file The default name for the current MPT Specimen Log file is specimen .log.
naming

MTS MultiPurpose TestWare® Performing Common Tasks 57

About the MPT Specimen Log

Archived log files are named specimen000.log, specimen001.log,

specimen002.log, and so forth, up to specimen500.log.

Note The maximum number of log files that can be saved for a particular test
is 500.

Once you reach 500 log files, additional log files overwrite the oldest log files in
order (typically archiving restarts at specimen 000.log).

When a log file is saved (either manually or automatically), a log entry is made
noting the archival. This entry includes a time/date stamp and information about
where the file was saved. This entry becomes the first entry in the current log.

CAUTION

The MPT software can unexpectedly quit if you run out of disk space when
saving log files.

Quitting while a test is in progress can result in a loss of data.

If you think your test may generate an excessive number of MPT Specimen Log
entries, you should filter the messages written to the MPT Specimen Log with the
MPT Options Editor.

If the MPT application shuts down as a result of log files exhausting disk space,
you must remove some of the MPT Specimen Log files from your disk before
you restart the system software.

Message Logs Window (part 1 of 3)

ITEM DESCRIPTION

Displays the Open Message Log File window where you can open any
archived or saved message log file (.log) you wish to view.

Saves message log entries to a log file.

If you click the Save icon and no log entries are selected, all of the
messages in the MPT Specimen Log are saved to file and the entire log is
cleared.
If you click the Save icon and one or more log entries are selected, all of
the messages up to and including the last selected message are saved to
file and cleared from the log.

58 Performing Common Tasks MTS MultiPurpose TestWare®

 About the MPT Specimen Log

Message Logs Window (part 2 of 3)

ITEM DESCRIPTION

Closes the selected MPT Specimen Log and removes the log from the Log
list.

Opens the Message Log Print window.

With the Message Log Print window you can set certain print parameters
(such as Print Range and Print Filters), access the Print Setup window,
and initiate printing of the selected message log.

Displays the Message Log Print To File window. With the Message Log
Print To File window you can save your log as a text (.txt) file.

Adds your message entry to all active logs.

Note User entries are sent to all active logs (Station log, Basic
TestWare log, MPT Specimen log); user entries are not affected
by filtering attributes.

Deletes user-entered messages from the message log.

Note You can only delete user-entered messages.

Copies the selected Message Log entries to the clipboard.

Enables all the display options or allows individual display option enable/
disable functions.
If you click on the enable icon, all display functions (Date/Time, Severity,
Source) are enabled.
If you click on the down arrow, the individual display functions appear. If
you click on a function, the function state changes between enabled and
disabled. If a check mark appears next to the function, that function is
enabled.
Log Displays the current log file. Use the down arrow to display other log files
that are available.
Log File Displays the path to the current log file.

MTS MultiPurpose TestWare® Performing Common Tasks 59

About the MPT Specimen Log

Message Logs Window (part 3 of 3)

ITEM DESCRIPTION
Scroll to new entry Disables or enables the MPT Specimen Log scrolling function. This
function allows the message log to automatically shift (scroll) to display
new entries as they occur.
Note By default, the Scroll to new entry box is enabled.

If you select Scroll to new entry, new log entries appear at the bottom of
the log as they occur. The log scrolls down automatically to ensure that the
latest entry is displayed.
If you clear the Scroll to new entry, the application adds new log entries
to the bottom of the log as they occur, but the log does not automatically
scroll down to the latest entry. New entries may not be visible unless you
manually scroll to the bottom of the log. With this selection you can
review the contents of the log without the window ‘jumping’ to the bottom
of the display each time a new log entry arrives.

For more information See “About Counters” on page 49.

For information about filtering MPT Specimen Log entries, see “MPT Options
Editor Specimen Tab” on page 73.

60 Performing Common Tasks MTS MultiPurpose TestWare®

Chapter 7
MPT Options Editor
Contents About the MPT Options Editor 62
MPT Options Editor Execution Tab 62
About Setpoint Use with MPT Test Procedures 66
About Command Hold and Stop Behaviors 67
About Data Acquisition Resulting From Command Stop Behavior 68
About Command Stop Behaviors and Automatic Setpoint Adjustments
69
About Transition States 70
MPT Options Editor Specimen Tab 73
MPT Options Editor Recovery Tab 74
About Test Recovery 75
MPT Options Editor Specimen Log Tab 77
MPT Options Editor Control Panel Tab 79
MPT Options Editor Properties Tab 80
MPT Options Editor Unit Selection Tab 81

MTS MultiPurpose TestWare® MPT Options Editor 61

About the MPT Options Editor

About the MPT Options Editor

Use the MPT Options Editor to set preferences that are saved with the
procedure.

Saving option When you create a new procedure, it contains default settings for all of the
preferences controls in the Options Editor, such as preferences for the data file format,
command hold behavior, unit assignment set, and so forth. You can change these
default settings by modifying the “default.000” file.

For more information See “Default Templates” on page 553.

MPT Options Editor Execution Tab

Use the Execution tab on the MPT Options Editor to specify options related to
the execution of your test.

Access From the MPT control panel or MPT Procedure Editor window, the access path
is:

> Execution tab

Or, from the MPT Procedure Editor window, an alternate path is:

Tools > Options Editor > Execution tab

62 MPT Options Editor MTS MultiPurpose TestWare®

 MPT Options Editor Execution Tab

Options that are controlled from the Execution tab include:

• How the system responds when Hold is selected on the run, stop, hold
panel.

• Whether or not a test can be resumed if it has been stopped, but it has not
completed.

• Whether or not the Station Manager Span and Setpoint controls can affect
your procedure.

• What hydraulic state is required for the control channels in the procedure to
run.

• What happens to the command when the test is put in hold or stopped.

• Whether the application displays confirmation messages when actions that

affect test resumption occur.

Execution Tab (part 1 of 3)

ITEM DESCRIPTION
Hold State Support Specifies how the Hold button on the Run/Stop/Hold panel operates.
Enable Hold—Clicking Hold puts the test in a hold state.
Ignore Hold Event—Hold is disabled and, if selected, has no effect.
Treat Hold As Stop—Hold operates identically to Stop.
Resume Test After Stop Specifies whether or not you can resume a test after it is stopped.
Note This applies whether the test is stopped by an interlock, a
program control process, or the Stop button on the Run/Stop/
Hold panel.

If the enable option is not selected and a test is stopped, you must click the
Reset button or select a new MPT specimen before you can run the
procedure again.

MTS MultiPurpose TestWare® MPT Options Editor 63

MPT Options Editor Execution Tab

Execution Tab (part 2 of 3)

ITEM DESCRIPTION
Required Power Specifies the hydraulic pressure setting required by the control channels in
a procedure to start and continue running.
Note Power status applies only to control channels. If a procedure does
not contain control channels, the power status has no effect on
the procedure. For instance, if a procedure without control
channels has a power status of High and hydraulic power is
removed from the station, the procedure is still valid.

The selections are High, High/Low, Off, and Off/Interlocked.

The High selection applies to most testing situations; it requires you to
operate MPT with high hydraulic pressure applied to the station’s
Hydraulic Service Manifolds (HSM).
The Off and Off/Interlocked selections are typically used while you are
learning the application software or running test simulations.
Off/Interlocked disregards active interlocks for the sake of allowing you
to run the test unhindered.
Command Hold Behavior Specifies how command processes behave when the procedure transitions
to the hold state.
Command Stop Behavior Specifies how command processes behave when the procedure transitions
to the stop state.
Setpoint Enables or disables the Station Manager application’s Setpoint control on
the Setpoint and Span window.
Enable—Allows the operator to change the Setpoint slider on the
Setpoint and Span window while the test is running.
Note The Disable and Reset option does not apply to the External
Command process.

Disable and Reset—Prevents the operator from changing the Setpoint

slider on the Setpoint and Span window while the test is running.

64 MPT Options Editor MTS MultiPurpose TestWare®

 MPT Options Editor Execution Tab

Execution Tab (part 3 of 3)

ITEM DESCRIPTION
Span Enables or disables the Station Manager application’s Span slider on the
Setpoint and Span window and the Master Span slider on the Station
Controls panel.
Enable—Allows the Span and Master Span sliders to affect the test
procedure command.
Note The Disable and Reset option does not apply to the External
Command process.

Disable and Reset—Prevents the Span and Master Span sliders from
affecting the test procedure command. The procedure plays out at 100%
span.
Confirm actions that may Enables or disables this confirmation function.
affect resuming the test
When enabled (as indicated by a check mark in the box), this function
causes query windows to pop up. The intent of these windows is to point
out the potential loss of data and stimulate additional thought about the
possible effects of your actions.
An example of a query message is as follows:
“Reset will discard test progress in the current specimen. Do you really
want to reset?”

For more information For more information, see “MPT Run/Stop/Hold Panel” on page 35.

For additional information about Command Stop Behavior, see “About

Command Hold and Stop Behaviors” on page 67.

For more information, see “About Setpoint Use with MPT Test Procedures” on
page 66.

MTS MultiPurpose TestWare® MPT Options Editor 65

About Setpoint Use with MPT Test Procedures

About Setpoint Use with MPT Test Procedures

General There are many reasons that you may or may not want the operator to have the
considerations ability to change the Station Manager application’s setpoint control while the test
procedure is running.
In general, you typically want to prevent the operator from changing the setpoint
when performing tests that include control mode switches. So when you are
creating test procedures that perform control mode switches, select Disable and
Reset for the Setpoint control.

Differences between The Setpoint Enabled setting on the MPT Options Editor applies to the
Setpoint Enabled and execution of the entire test procedure. The Relative Endlevels setting available
Relative Endlevels in the Command tab of some command processes applies only to the execution
of the associated process.

Setpoint Enabled is typically used in applications where the test designer wants
to give the operator control of the reference level while the test is in progress.
These applications also typically run the entire test in a single control mode.

"Relative Endlevels" instructs that specific process to interpret its endlevels

relative to the segment generator's command when the process begins. This does
not give the operator the ability to change the reference point dynamically. It is
often used after a modeswitch. For example, ramp in load control to particular
load, then switch to displacement and ramp 3 mm relative to where the actuator
is.

Setpoint Enabled and Relative Endlevels are independent features, and are rarely
used at the same time.It is possible to use both of these features together; their
effect is additive.

Consideration for dual If you want to run your test procedure on a station that has a dual compensation
compensation control control mode, you need to be aware of the compensation type selected for the
modes control mode.

If the compensation type is Amplitude Control Only, do not disable the Station
Manager application’s setpoint with this control (that is, select Enable; do not
select Disable and Reset).

The reason is because a mode switch into a dual compensation control mode with
this type of compensation puts an offset into the setpoint (the offset provides a
“bumpless” mode switch). If you disable the setpoint (with the MPT Setpoint
control), you cannot remove the offset.

66 MPT Options Editor MTS MultiPurpose TestWare®

 About Command Hold and Stop Behaviors

If you want to run your test procedure on a station that has a dual compensation
control mode in which the compensation type is Mean and Amplitude Control,
you may disable the setpoint without any adverse effect.

For more information about how the setpoint control is affected by dual
compensation control modes, see the 793 Control Software manual (PN 100-147-
130).

About Command Hold and Stop Behaviors

The Command Hold Behavior and Command Stop Behavior functions allow
you to specify how an active MPT command process behaves when a procedure
transitions to the hold or stop states.

The following selections are the same for each control:

• Stay at Level—The waveform holds/stops at the current level.

• Ramp to Mean—The waveform ramps to mean.

• Ramp to Zero—The waveform ramps to zero.

• Taper to Mean—The waveform tapersto mean.

• Taper to Zero—The waveform tapers to zero.

The transition times for all ramp and taper functions are specified using the
Command Options tab on the Station Manager’s Channel Options window. The
default transition time is two seconds.

For more information about specifying command options, see the MTS 793
Control Software manual.

Special consideration If the procedure ends normally, and the Command Stop Behavior is set to
Ramp to Mean or Taper to Mean, the signal may not respond as you expect.
When a procedure ends normally (without being manually held or stopped), all of
its processes end normally, and then the Command Stop Behavior is run. In
these situations, Ramp to Mean and Taper to Mean settings behave like a “stay
at level” setting, and the Taper to Zero setting behaves like a “ramp to zero”
setting. The Ramp to Zero setting works as expected.

MTS MultiPurpose TestWare® MPT Options Editor 67

About Data Acquisition Resulting From Command

About Data Acquisition Resulting From Command Stop Behavior

When a test is stopped by an operator, MPT continues to acquire data through all
subsequent transition periods.

Example Suppose you are running a procedure with a cyclic waveform, and wish to
acquire data on all the command cycles. The procedure requires 100 command
cycles and 100 data acquisition cycles, where 1 cycle=1 second.

You push the Stop button during the test, and it takes 3 seconds to taper to zero.
Those 3 cycles count as command and data acquisition cycles.

Then you push the Start button. It takes 5 seconds for the system to taper back up
to full amplitude. Those 5 cycles also count as command and data acquisition
cycles.

When the test reaches its “natural” done state (after 100 cycles,) it performs 100
command cycles and 100 data acquisition cycles, 8 of which are tapered.

Note It is important to realize that, because of the 8 tapered cycles, some data
points (those that are smaller than the specified sensitivity) might be
missed if you are taking peak/valley data.

Operator hits Test stops, Waveform is back Test is

Stop button then restarts up to full amplitude done

Start

Entering Stop Taper to Level

Counts as 3 command and Counts as 5 command and
Test is
data acquisition cycles data acquisition cycles
stopped

68 MPT Options Editor MTS MultiPurpose TestWare®

 About Command Stop Behaviors and Automatic

About Command Stop Behaviors and Automatic Setpoint Adjustments

Note When you enable Setpoint, the Return to Zero and Taper to Zero
functions operate relative to the Setpoint, not to absolute zero.

If you enable Setpoint and Span and set Command Stop Behavior to Stay at
Level, you may find that Setpoint increases unexpectedly if you stop, unlock,
reset, and restart the test. This also applies if remove and then turn hydraulics on.
The reason for this is that, using the previously described conditions, Setpoint
automatically shifts by the amount of offset present when the procedure was
stopped.

Example Suppose you run a procedure in which you run a ±10 mm cyclic command from a
mean level of 20 mm. You enable Span and Setpoint and select a Command
Stop Behavior of Stay at Level. You set Span to 100% and Setpoint to 0 mm.
When the actuator is at 20 mm, you stop the test. This causes the actuator to stop
and hold at 20 mm. Then you unlock the procedure and resume the test. In this
situation, the Setpoint value automatically increases to 20 mm, causing the
actuator to travel to mean level of 40 mm before resuming the ±10 mm cyclic
waveform.

Avoiding automatic To avoid this behavior and run the test relative to the original Setpoint, select a
Setpoint adjustments Command Stop Behavior of Ramp to Zero or Taper to Zero. This way, when
you unlock MPT, the commanded level is equal to the current Setpoint value.

Example Suppose you run a procedure similar to the one in the previous example, except
you select a Command Stop Behavior of Ramp to Zero. When the actuator is
at 20 mm, you stop the test. This causes the actuator to ramp to 0 mm at the
system ramp rate. Next, you unlock the procedure and resume the test. In this
situation, the Setpoint value remains 0 mm, and the actuator ramps at the same
rate back to 20 mm before executing the ±10 mm cyclic waveform.

Making manual If the desired combination of Setpoint and Command Stop Behavior for your
Setpoint adjustments situation results in a Setpoint shift, you have to manually adjust the Setpoint to
the desired position before you restart a test.

MTS MultiPurpose TestWare® MPT Options Editor 69

About Transition States

About Transition States

Of the seven test states in MPT, there are four Entering and Exiting states:
Entering Stopped, Exiting Stopped, Entering Hold, and Exiting Hold. These
states could be described as “transition states”; that is, when MPT is leaving one
state and entering another, such as changing from a Running state to a Holding
state. Sometimes these transitions are instantaneous, but they still exist.

How long the test remains in a transition state depends on the test parameters you
have chosen, using two separate windows: the Execution tab on the MPT
Options Editor and the Command Options tab on the Station Manager’s
Channel Options window.

MPT Execution tab Use the MPT Execution tab to select the following Command Hold and
Command Stop Behaviors:

• Stay at Level

• Ramp to Mean

• Ramp to Zero

• Taper to Mean

• Taper to Zero

Station Manager Use the Station Manager Command Options tab to set the times for these
Command Options tab behaviors:

• Taper Times

• Ramp Times

• Begin/End Times

• Setpoint/Span Times

See the MTS 793 Control Software manual (PN 100-147-130) for more
information.)

Example The Entering Hold state lasts as long as it takes the system to move from the
Running state to the Holding state. If you chose Stay at Level, the Entering Hold
state would be instantaneous. If you chose Ramp to Mean or Taper to Mean,
then this state would exist for a longer time because time is needed to transition
from the current level to the level state.

70 MPT Options Editor MTS MultiPurpose TestWare®

 About Transition States

The amount of time the test remains in a state also results from the time you have
specified on the Station Manager Command Options tab:

• If you select a Ramp option for Command Hold Behavior or Command

Stop Behavior in MPT, the Ramp Times you specify in Station Manager
Command Options are used. When you click Hold or Stop while a test is
running, the test assumes a transition state during the ramp. If you click Run
to resume the test, the test also assumes a transition state during the ramp.

• If you select a Taper option for the Command Hold or Stop Behavior, the
Taper Times you specify in Station Manager Command Options are used.
When you click Hold or Stop while a test is running, the test assumes a
transition state during the taper. If you click Run to resume the test, the test
also assumes a transition state during the taper.

• If you select a tapered waveform in a Cyclic Command, Profile, or Profile

with ALC process in MPT, the Begin/End Times you type in Station
Manager are used. Those tapers appear only at the very beginning and the
very end of the waveform generated by these processes. These tapers do not
occur in a transition state because they are considered part of the test (the
tapered cycles are counted).

The following diagram shows a test with a Sine Tapered waveform, Ramp to
Mean on hold, and Taper to Zero on stop. It also shows each of the program states
within the test:

MTS MultiPurpose TestWare® MPT Options Editor 71

About Transition States

Click
Run

Program States

Click Click Click

Run Click Run Click Run
Hold Stop

User Actions

For more information See “About Command Hold and Stop Behaviors” on page 67 for more
information.

72 MPT Options Editor MTS MultiPurpose TestWare®

 MPT Options Editor Specimen Tab

MPT Options Editor Specimen Tab

Use the Specimen tab to determine the storage mode and format of the data that
is written to MPT specimens when you run procedures.

Access From the MPT control panel or MPT Procedure Editor window, the access path
is:

> Specimen tab

Or, from the MPT Procedure Editor window, an alternate path is:

Tools > Options Editor > Specimen tab

Specimen Tab (part 1 of 2)

ITEM DESCRIPTION
Data File Data File functions control how data is added to the data file and data format.
In addition, it controls the type of time stamp that is used in association with
the data.
Mode Append—Causes new data to be added to the end of data files.
Mode Overwrite—Clears the MPS specimen data file (and user-specified
files) when you start a new test run (that is, when you click Run after the test
has been reset), which causes new data to write over existing data in data files.
Format Plain—Writes space-delimited data. This is the most useful format for
direct printouts.

Format Lotus—Writes comma-delimited data with text strings in double

quotes (sometimes referred to as the CSV format). Use this format when you
plan to import data files into Lotus 1-2-3™.
Format Excel—Writes tab-delimited data. Use this format when you plan to
import data files into Microsoft Excel.
Time Stamp—Selects which signal is used to timestamp data records in the
data files. Time is the elapsed time from run to reset. Running Time is the
time from run to reset minus the time attributed to the Hold or Stop functions.

MTS MultiPurpose TestWare® MPT Options Editor 73

MPT Options Editor Recovery Tab

Specimen Tab (part 2 of 2)

ITEM DESCRIPTION
Specimen Log Append—Causes new messages to be added to the end of the MPT Specimen
Log file.
Overwrite—Clears the MPT Specimen Log when you start a new test (that is,
when you click Run after the test has been reset), which causes new messages
to write over existing messages in the MPT Specimen Log file.
Clear Counters on Enables and disables the clear function for the Run Time, Channel Counters,
Reset and Profile Counters (it does not affect the Sequence Counters).
When enabled, the affected counters are cleared (reset to zero) whenever you
click the Reset button.
When disabled, the affected counters are not cleared (reset to zero) when you
click the Reset button.
Not resetting the counters can affect various test related functions. For
example, it can affect counter related limits (not resetting may cause you to
exceed a segment or cycle related limit). Counter resets are sometimes used to
indicate the start of a new test in your data file. Without the resets, multiple
iterations of a test may be viewed as one long test.

MPT Options Editor Recovery Tab

Use the Recovery tab to determine how often the application saves a “snapshot”
of the test state and status.

Access From the MPT control panel or MPT Procedure Editor windows, the access path
is:

> Recovery tab

Or, from the MPT Procedure Editor window, an alternate path is:

Tools > Options Editor > Recovery tab

74 MPT Options Editor MTS MultiPurpose TestWare®

 About Test Recovery

The snapshots of the test state and status can be used to restart a test that was
interrupted by an event (for example, a power failure or interlock).

Recovery Tab
ITEM DESCRIPTION
Recovery Settings Enable saving recovery status—Enables the recovery feature and specifies
how the progression of the test state and status is saved.
Note MTS recommends you leave this feature enabled unless you have
strong reasons to disable it.

Upon program state change—Saves the test status whenever the run, stop, or
hold buttons are clicked on the Station Controls panel (including interlocks).
At least every—Saves the test status at a regular time interval (user specified).

About Test Recovery

When you enable the recovery feature, the application updates a recovery file
(saved in the MPT specimen) at the intervals you specify.

Snapshot intervals can be set using the program state changes (includes Run to
Stop or Stop to Run state changes, including interlocks) and time intervals that
you specify.

You can use a recovery file to restart a test even if the test was running during the
last snapshot. You cannot restart tests if they have completed or have been reset.

What is saved Information saved to the recovery file includes:

• A copy of the procedure. (It is possible to edit a procedure, then run it

without saving it. In this situation, the test status contains the information
used in the execution, not the original procedure.)

• The active group and individual processes. It also identifies how much of
each process is complete.

• The current program state (Run, Hold, Stop). When recovering a test, if the
program was running or holding, the test is restored in the Stop state.

• The state of the sequence counters and the channel counters.

MTS MultiPurpose TestWare® MPT Options Editor 75

About Test Recovery

What is not saved When you recover a test, the test status is restored to the point where the last
snapshot was taken.

• If the test is stopped by an uncontrolled event (such as power failure or

application failure), any data not saved to disk at the point of the shutdown
is lost.

• If data was being transferred from the data buffer to the computer, data that
had not been transferred is lost.

DIO settings are not restored during the MPT recovery process. For information
about DIO settings, see the MTS 793 Control Software manual.

Recovery accuracy There are two measures of “accuracy” associated with a saved test status:

• How old is the snapshot? If the snapshot is taken one minute before the test
stops, many additional cycles may be applied to the MPT specimen that the
test status would not know about.

• How consistent is the snapshot? If the snapshot is taken while the test is
running, each active process is checked in sequence. This results in test
status data that is taken at slightly different times.

Recovery Review the following characteristics of the test recovery feature to understand
considerations the advantages and disadvantages of recovering a test under different
circumstances.

• Recovering a test that was saved periodically provides test status data that is
relatively accurate in relation to the point where the test stopped. The
shorter the period, the closer the test status is to the point of failure.
However, saving a test does require additional processor time. If the
autosave rate is too fast, the accuracy of the data acquisition processes (data
output and communication between processes) can be adversely affected.

• Each autosave action overwrites the test status. If the system experiences an
uncontrolled shutdown, (power fails) while the system is saving the test
status, test status recovery is probably not possible.

• The test status maintains a copy of the procedure when entering the Execute
mode in MPT.

76 MPT Options Editor MTS MultiPurpose TestWare®

 MPT Options Editor Specimen Log Tab

MPT Options Editor Specimen Log Tab

Use the Specimen Log tab on the MPT Options Editor to filter the messages
written to the MPT Specimen Log. You can also specify what items are
displayed in the Message Logs window.

Access From the MPT control panel or MPT Procedure Editor window, the access path
is:

> Specimen Log tab

Or, from the MPT Procedure Editor window, an alternate path is:

Tools > Options Editor > Specimen Log tab

If your test generates an excessive number of messages, you should filter what
messages are written to the log to avoid exhausting disk space.

For instance, you can change the Source filter from All Applications to This
Application Only to keep Station Manager messages out of the MPT Specimen
Log.

Specimen Log Tab (part 1 of 2)

ITEM DESCRIPTION
Message Capture Controls the severity level and source of the information that is written to the
MPT Specimen Log.
Minimum Severity sets the severity level that must be reached before a
MultiPurpose TestWare writes a message to the Specimen Log file. There are
five levels:

• Diagnostic—Writes Diagnostic, Information, Warning, Error, and

Fatal Error messages.

• Information—Writes Information, Warning, Error, and Fatal Error

messages; does not write Diagnostic messages.

• Warning—Writes Warning, Error, and Fatal Error messages; does not

write Diagnostic and Information messages.

• Error—Writes Error and Fatal Error messages; does not write

Diagnostic, Information, and Warning messages.

MTS MultiPurpose TestWare® MPT Options Editor 77

MPT Options Editor Specimen Log Tab

Specimen Log Tab (part 2 of 2)

ITEM DESCRIPTION

• Fatal Error—Writes only Fatal Error messages; does not write

Diagnostic, Information, Warning, and Error messages.

Source—Selects the information source from which the log is built.

• This Application Only—Records messages from the MPT application

only.

• All Applications—Records messages from other sources, such as the

Station Manager application.
Archive Auto Deletion Important Enabling this control may result in the inadvertent deletion of
specimen log entries. The Specimen Log is unlikely to exceed
the internal limit of 500 Specimen Log files for a given MPT
specimen (unless your procedure is generating an excessive
number of messages). Therefore, MTS recommends that you
disable this control if you routinely use new MPT specimens from
test-to-test. Disabling this control ensures that you are able to
recover relevant log data for your MPT specimens in the future.

This control enables or disables the auto deletion function and sets the deletion
interval in days.
The Specimen Log archive has an internal limit of 500 Specimen Log files,
with each file containing approximately 1000 messages. Once 500 archived
files are accumulated and a new archive file is generated, the oldest archive file
is automatically deleted to make room for the newest archive file.

The Archive Auto Deletion control lets you program when archived files are
deleted in terms of days (within the internal limit of 500 archived files).
To enable the Archive Auto Deletion function, click in the Delete Older Than
checkbox such that a check mark appears in the box. If the check mark appears
in the box, the function is enabled.
Set the deletion interval using the scroll arrows to change the number of days
displayed. The scroll arrows are only active if the Archive Auto Deletion
function is enabled.

78 MPT Options Editor MTS MultiPurpose TestWare®

 MPT Options Editor Control Panel Tab

MPT Options Editor Control Panel Tab

Use the Control Panel tab to specify what information is displayed on the MPT
control panel.

Access From the MPT control panel or MPT Procedure Editor window, the access path
is:

> Control Panel tab

Or, from the MPT Procedure Editor window, an alternate path is:

Tools > Options Editor > Control Panel tab

Control Panel Tab (part 1 of 2)

ITEM DESCRIPTION
Test Progress Enables and disables the Run Time portion of the Test Progress panel on the
MPT control panel. You can also change the Run Time panel display format.
Run Time—Enables/disables the Run Time display. If Run Time is disabled,
the Run Time display does not appear on the Test Progress panel
Display Format—Changes the Run Time display format. The format options
are HH:MM:SS (hours:minutes:seconds) and cumulative time units.
Specimen Enables and disables the Procedure Name and Procedure State portion of the
Specimen panel.
If the Procedure Name or Procedure State is disabled, the respective display
does not appear on the Test Progress panel.
Procedure Name—Displays the name of the current procedure.
Procedure State—Displays the current procedure state.

MTS MultiPurpose TestWare® MPT Options Editor 79

MPT Options Editor Properties Tab

Control Panel Tab (part 2 of 2)

ITEM DESCRIPTION
Station Status Enables and disables the Power panel on the MPT control panel.
If Power is disabled, the Power panel does not appear on the MPT control
panel.
Counters Enables and disables the Channel Counters and Sequence Counters. In
addition, it controls the counter display format.
Channel Counters—Displays the Channel Counters when enabled
Sequence Counters—Displays the Sequence Counters when enabled
Display Format—Controls the Channel Counters and Sequence Counters
display format. The format options are:
• Cycles - Displays the total number of cycles that have been run.

• Segments - Displays the total number of segments that have been

run.

For more information See “MPT Test Progress Panel” on page 28.

See “MPT Channel Counters Panel” on page 32.

See “MPT Sequence Counters Panel” on page 33.

MPT Options Editor Properties Tab

Use the Properties tab to type information that is saved with the procedure.

Access From the MPT control panel or MPT Procedure Editor window, the access path
is:

> Properties tab

Or, from the MPT Procedure Editor window, an alternate path is:

Tools > Options Editor > Properties tab

80 MPT Options Editor MTS MultiPurpose TestWare®

 MPT Options Editor Unit Selection Tab

You can type a process summary, identify the procedure, describe the test, or
write instructions to the test operator. This information appears in the Print
Preview window.

Properties Tab
ITEM DESCRIPTION
File Name Displays the name and path of the current procedure selection.
Description Type a description or other information about the procedure here.
Author Type the author’s name here.

MPT Options Editor Unit Selection Tab

Use the Unit Selection tab on the MPT Options Editor to assign a different unit
assignment set to the current procedure.

Access From the MPT control panel or MPT Procedure Editor window, the access path
is:

> Unit Selection tab

Or, from the MPT Procedure Editor window, an alternate path is:

Tools > Options Editor > Unit Selection tab

Unit Selection Tab (part 1 of 2)

ITEM DESCRIPTION
UAS Comment Displays a description of the selected unit assignment set.
Selection list Displays a list of the defined unit assignment sets. The currently selected set is
shown.

MTS MultiPurpose TestWare® MPT Options Editor 81

MPT Options Editor Unit Selection Tab

Unit Selection Tab (part 2 of 2)

ITEM DESCRIPTION
Use Station Unit Note By default, this control is enabled in the default template. To disable
Assignment Set this control for new procedures, you must disable it in the default
template.

When enabled for existing procedures: Causes the procedure to acquire the
current default UAS selection. If this box was disabled when you opened a
procedure and you enable it while editing the procedure, you will see the units
in your procedure change from the UAS assigned when you opened the
procedure to the UAS set in the registry. The new UAS assignment are not
permanent until you save the procedure. If you close without saving, the UAS
assignment reverts to the set assigned when you opened the procedure.
When enabled for new procedures: Causes new procedures to open with the
UAS selection set in the registry.
When disabled for existing procedures: With this control, you can select and
edit any UAS and assign it to the current procedure. When you save your
procedure, your specific UAS selection is saved with your procedure. If
keeping a specific UAS assignment linked to your procedure is important to
you, this is a good choice.
When disabled for new procedures: Causes new procedures to open with the
UAS selection set in the registry. If you want all new procedures to open with a
specific UAS that is independent of the station configuration UAS, change the
UAS selection in the default template.
Edit... Opens the Unit Assignment Set Editor. Using this editor, you can create new or
edit existing unit assignment sets.

For more information See “About Default Templates” on page 553.

82 MPT Options Editor MTS MultiPurpose TestWare®

Chapter 8
Working with MPT Processes
Contents About MPT Processes 84
Process Palette 84
How to Add Processes to the Procedure Table 85
How to Select Processes in Procedure Tables 86
How to Delete Processes from the Procedure Window 86
About Cutting, Copying, and Pasting Processes 87
How to Cut/Copy, and Paste a Process or Group of Processes 87
How to Quick Copy and Paste Selected Processes in the Same Window
87
About Sequencing Processes 87
About “Buffer Full” Signals 89
About “Trigger” Signals 90
Process Sequence Example 93
About Editing Trigger Signals 94
How to Set/Edit the Interrupt Signal 95
How to Specify/Change the Procedure Done Signal 95
Example of Sequencing a Single Process 96
Example of Sequencing Multiple Processes 97
About Sequencing Group Processes 98
How to Open the Group Table 99
Group Process Naming Conventions 99
About Group Process Interrupts 100
How to Disable Processes 103

MTS MultiPurpose TestWare® Working with MPT Processes 83

About MPT Processes

About MPT Processes

When you create tests with the MPT application, you use MPT processes like
building blocks to define test actions such as sending command signals,
performing data acquisition, and responding to test events.

A complete MPT test normally consists of a number of MPT processes linked

together and saved as an MPT procedure.

Process Palette
Your MPT process icons are displayed on the Process Palette.

Process categories Processes are grouped on the palette in the following categories:

• Command Processes send commands to a servovalve or external controller.

• Data Acquisition Processes acquire sensor data from the physical

specimen.

• Event Processes monitor test signals and perform actions when specified
conditions are met.

• External Control Processes control external controllers or logic devices.

• Other Processes perform miscellaneous functions.

84 Working with MPT Processes MTS MultiPurpose TestWare®

 How to Add Processes to the Procedure Table

How to Add Processes to the Procedure Table

The first and most basic step you must perform to create a test procedure is to add
processes to your procedure table.

There are three ways to add a process to the procedure table:

1. Click the desired process icon on the Process Palette, and then click Add
Process on the Edit menu of the MPT Procedure Editor.

By default, the process icon is inserted below any existing process icons in
the table. To insert a process in the procedure table, click the icon you want
to insert the new process above, then add the new process.

2. Drag the process icon from the Process Palette to your procedure and group
table.The process will be inserted at the insertion line.

Insertion
Line

3. Double-click the desired process icon on the Process Palette. The process
will be inserted after the last selected process on the table.

MTS MultiPurpose TestWare® Working with MPT Processes 85

How to Select Processes in Procedure Tables

How to Select Processes in Procedure Tables

You may want to select process icons in your procedure table to copy or delete
them. You can select process icons the same way you would select files in
Windows operating system software.

Select a single process Left-click a process on a procedure table to select it.

icon
Note The icon appears highlighted when selected.

Select multiple process Hold down the Ctrl key, and then left-click each icon you want to select.
icons individually

Deselect processes Deselect processes by holding down the Ctrl key and left-clicking.

Select a range of Left-click the first process icon, hold down the Shift key, then click the last
process icons process icon in the desired range.

How to Reposition Processes in a Procedure Table

To reposition a process icon, left-click and drag it to the desired position on the
table. The insertion line moves with the cursor, and indicates where the process
will be placed when you release left-click control on the mouse.

How to Delete Processes from the Procedure Window

You can delete processes from your procedure table several ways:

In the procedure table, click the process icon or icons you desire to delete to
highlight them, and perform one of the following:

1. Click on the MPT Procedure Editor toolbar.

2. On the Edit menu, click Delete Process.

3. Drag the process icon or icons to the trash can located on the upper right
hand corner of the MPT Procedure Editor.

4. Click the right-mouse button and select Delete from the menu.
Note You cannot undo a delete operation.

86 Working with MPT Processes MTS MultiPurpose TestWare®

 About Cutting, Copying, and Pasting Processes

About Cutting, Copying, and Pasting Processes

You can cut, copy, and paste processes on the same procedure table, or from one
procedure table to another.

Note When you copy a process icon, or a group of process icons, the
parameters of the original processes are retained, but the sequencing
information may not be. You may have to reassign Start and Interrupt
signals.

How to Cut/Copy, and Paste a Process or Group of Processes

1. Select the process or processes you want to copy and paste.

2. On the Edit menu, click Copy Process or Cut Process.

3. Open the procedure table where you want to place the copied processes.

4. Select the process before which you want to paste the processes on the
clipboard.

5. On the Edit menu, click Paste Process.

How to Quick Copy and Paste Selected Processes in the Same Window
1. Click the process or processes you want to copy.

2. Press and hold the Ctrl key, and then drag the selected processes. Use the
insert line to paste the copied process in the desired position.
Note To copy and paste processes between tables in separate MPT
applications, you must use the Copy Process and Paste Process
commands on the Edit menu. Dragging and dropping processes does
not work in this situation.

About Sequencing Processes

You must link the processes in your MPT procedure together so that they start
and stop at the desired times. To do this, you select among various types of
trigger signals for each process to control the execution of the process within the
test procedure.

MTS MultiPurpose TestWare® Working with MPT Processes 87

About Sequencing Processes

In your procedure or group table:

• Use the trigger signals available in the Start control to determine when each
process starts.

• Use the trigger signals available in the Interrupt control if you want to
specify a test event that interrupts the process.

• Use the trigger signals available in the Procedure (or Group) is done when
control to determine when the procedure ends.

Procedure start and All signal lists in your main procedure table include the <Procedure>.Start and
interrupt signals <Procedure>.Interrupt signals.

If you set the Start or Interrupt control to <Procedure>.Start, the process starts
or interrupts when the procedure starts.

Note In group tables, the controls are labeled <Group>.Start and

<Group>.Interrupt, and they pertain to the start and interrupt of that
particular Group process.

Done signals When an individual process ends, it generates a “done” signal. These done
signals are labeled process name.Done in your Start, Interrupt, and Procedure
is done when lists.

For example, if you created a segment command process named Ramp Up, the
done signal that appears in your signal lists would be labeled Ramp Up.Done.

Each process automatically generates a done signal when the process completes
its programmed function, or when it is interrupted by another signal. Process
done signals are typically used to specify the start of another process and/or the
end of your procedure.

Special process signals In addition to done signals, some data acquisition processes can also send out a
“buffer full” signal (indicating when the data buffer is full), and some event
processes can send out a “trigger” signal (indicating when the process is
triggered).

A buffer full signal or trigger signal can also be used to specify the start of
another process, the end of the test, or to interrupt other processes.

Fan-in and fan-out You can select more than one signal in each Start, Interrupt, and Procedure is
processes done when list to create a “fan-in” process. The process (or procedure) responds
if any of the selected signals is detected.

88 Working with MPT Processes MTS MultiPurpose TestWare®

 About “Buffer Full” Signals

Conversely, you can use the <Procedure.Start>, or a single done, buffer full, or
trigger signal to start, interrupt, or end several other processes. This is referred to
as a “fan-out” process.

Note There is a slight time delay between processes that start with a common
trigger signal (for example, two processes using the <Procedure.Start>
trigger signal). The process positioned the highest on the Procedure or
Group table starts first. When using data acquisition and command
processes in parallel, position the data acquisition process higher on the
table than the associated command process.

How to end a procedure The procedure table has a Procedure is done when control located at the bottom
of the window.

If you specify a signal in this list, when the specified signal is received, all active
processes in this window are interrupted and the procedure ends. You can use this
control to ensure that your procedure ends properly.

Note If you leave this control blank, the procedure stops when all of its child
processes are done.

For more information For information on ending a Group process, see “How to Disable Processes” on
page 103.

For more information about how sequencing processes affects test procedures,
see “About Sequencing Processes” on page 87.

About “Buffer Full” Signals

Some acquisition processes can generate buffer full signals when the data buffer
fills. These buffer full signals are labeled process name.Buffer Full in your
Start, Interrupt, and Procedure is done when lists.

For example, if you created a timed acquisition process named Acquire Time
Data, the buffer full signal that appears in your signal lists would be labeled
Acquire Time Data.Buffer Full.

Note You define the size of the buffer on the Destination tab of the acquisition
process’ Parameters window.

Cyclic acquisition processes can generate buffer full signals when data has been
acquired for the number of cycles or segments specified on the Data Storage tab
in the Cyclic Acquisition Parameters window.

MTS MultiPurpose TestWare® Working with MPT Processes 89

About “Trigger” Signals

When buffer full If you do not specify the number of samples to acquire for the acquisition
signals are sent process, the process continuously samples and generates a buffer full signal
every time the buffer fills, until the process ends.

If you specify the number of samples to acquire, the process sends a buffer full
signal every time the buffer fills until the requested number of samples are
acquired.

Special uses You can use a data acquisition buffer full signal to start and interrupt other
processes in your test.

For example, if you configure your data acquisition process to discard data when
the buffer fills (instead of saving it), the acquisition process can continuously
send buffer full signals to other processes without using up disk space.

About “Trigger” Signals

Note This document refers to trigger signals as various types of signals that
you can use to control the sequence of process execution within a test
procedure. These signals include <procedure (group)>.start, <procedure
(group)>.interrupt, process name.done, process name.buffer full, and
process name.trigger. For the sake of clarity, it is important to keep in
mind that the process name.trigger signal referred to in this section is
just one of the various types of trigger signals available to you when
designing test procedures.

Some processes can generate trigger signals when they detect the specified event.
These trigger signals are labeled process name.Trigger in your Start, Interrupt,
and Procedure is done when lists.

For example, if you created a digital input process named Input Monitor, the
trigger signal that appears in your signal lists would be labeled Input
Monitor.Trigger.

When trigger signals You can configure these processes to trigger once or to trigger continuously.
are sent When a process is set to trigger once, it generates a trigger when the specified
condition is met, and then generates a done signal. When a process is set to
trigger continuously, it continues to send triggers each time the specified
condition is met, and does not generate a done signal.

Note If you set up a process to trigger continuously, then the process will not
generate a done signal until it is interrupted. You should specify an
“Interrupt” signal or a “Procedure/Group is done when” signal to end a
continuously triggered process.

90 Working with MPT Processes MTS MultiPurpose TestWare®

 About “Trigger” Signals

Trigger signal example The following sample procedure makes use of a trigger signal.

In this example:

• The Peak/Valley Change Detector process (labeled Detect P/V) is set to

trigger continuously. (It generates a trigger signal whenever it detects a peak
or a valley outside the specified tolerance band.)

• The Detect P/V.Trigger is used to start the peak/valley acquisition process

(labeled Kathy’s DAQ), which acquires a specified amount of peak/valley
data and then stops.

With this configuration, this procedure acquires batches of peak/valley data as it

detects specified changes in the feedback’s peaks and valleys. Data is acquired
only when the Detect P/V process issues a trigger signal, rather than in a
continuous stream.

Since its job is to continually monitor feedback, the Detect P/V process never
generates a done signal. Because of this, you typically do not use the Detect P/
V.Done signal to start or interrupt any other process.

We use the Kathy’s Fatigue.Done signal to interrupt the Detect P/V process (and
generate a Detect P/V.Done signal). This prevents the test item from running
indefinitely.

MTS MultiPurpose TestWare® Working with MPT Processes 91

About “Trigger” Signals

Procedure diagram The diagram below illustrates the connections between the processes used in the
trigger signal example. The diagram illustrates how the trigger signal is used.

Detect P/V Start

Start Detect P/V.Trigger

<Procedure>.Start Detect P/V.Done

<Procedure>.Interrupt Kathy’s Fatigue.Done

Kathy’s DAQ.Done <Procedure>.Start

Kathy’s Fatigue.Done <Procedure>.Interrupt

Interrupt
Interrupt
Kathy’s Fatigue.Done
Kathy’s Fatigue.Done
Detect P/V.Done
Kathy’s DAQ.Done
Detect P/V.Trigger
<Procedure>.Start
<Procedure>.Start
<Procedure>.Interrupt
<Procedure>.Interrupt
Kathy’s Fatigue
Start
<Procedure>.Start
<Procedure>.Interrupt
Kathy’s DAQ.Done
Detect P/V.Done Interrupt
Detect P/V.Trigger none Note To simplify this illustration, some
Kathy’s DAQ.Done of the signals normally available
in this scenario are not shown.
Detect P/V.Done
Detect P/V.Trigger
<Procedure>.Start
<Procedure>.Interrupt

92 Working with MPT Processes MTS MultiPurpose TestWare®

 Process Sequence Example

Process Sequence Example

Assume when you start your test you want the program to ramp up, cycle for
some time, ramp down, and then end.

You would sequence your processes to run in the following order:

• The “Ramp Up” Segment process should start when the procedure starts.

• The “Cycle” Cyclic process should start when the “Ramp Up” process is
done.

• The “Ramp Down” Segment process should start when the “Cycle” Cyclic
process is done.

• The Procedure should end when the “Ramp Down” Segment process is
done.

The following procedure table illustrates this:

MTS MultiPurpose TestWare® Working with MPT Processes 93

About Editing Trigger Signals

About Editing Trigger Signals

Procedure and group tables that are populated with processes contain three areas
where you can edit trigger signals:

• The Start box

• The Interrupt box

• The Procedure (or Group) is done when box.

MPT selects default trigger signals for the Start box. The Interrupt and
Procedure (or Group) is done when boxes are blank by default.

Display a trigger list Even if it is blank, each box contains a hidden trigger signal list. To display the
list, double-click the box.

Select a trigger and When the trigger signal list is displayed, you can select any individual trigger
hide the list signal in the list by double-clicking it. This replaces whatever the box had in it
before with the current selection, and then close the list.

Note You can also select a trigger signal (and hide the list) by highlighting the
trigger signal in the list and pressing Enter.

Remove a trigger and To remove the current trigger signal from a box, double-click the box to display
hide the list the boxes’ trigger signal list, then double-click the same trigger signal in the list.
This clears the box and hides the list.

Select multiple trigger To select multiple trigger signals in a list, you can hold down the Shift key to
signals in a list select a range of trigger signals, or hold down the Ctrl key to select a trigger
signals arbitrarily. When you select multiple signals, the process performs the
action (start the process, interrupt the process, end the procedure or group) when
it receives any of the selected signals.

94 Working with MPT Processes MTS MultiPurpose TestWare®

 How to Set/Edit the Interrupt Signal

How to Set/Edit the Interrupt Signal

1. To specify the interrupt signal(s), double-click the Interrupt list box to
display the signal list.

2. In the signal list, hold the Ctrl key and click each signal you want to
interrupt the procedure. (If you select multiple signals, the procedure
interrupts when any of the selected signals are received.)

3. Press Enter.

If you want to clear your interrupt signal selections:

1. Double-click the signal name to display the signal list.

2. In the signal list, hold the Ctrl key and click each signal you want to remove
from the list.

3. Press Enter.
Note You can deselect all of the signals highlighted and close the list by
double-clicking any of the individual selections highlighted in the list.

How to Specify/Change the Procedure Done Signal

1. To specify the procedure done signal(s), double-click the Procedure is done
when box to display the signal list.

2. In the signal list, hold the Ctrl key and click each signal you want to end the
procedure. (If you select multiple signals, the procedure ends when any of
the selected signals are received.)

3. Press Enter.

If you want to clear your procedure done signal selections:

1. Double-click the signal name to display the signal list.

2. In the signal list, hold the Ctrl key and click each signal you want to remove
from the list.

3. Press Enter.
Note You can deselect all of the signals highlighted and close the list by
double-clicking any of the individual selections highlighted in the list.

MTS MultiPurpose TestWare® Working with MPT Processes 95

Example of Sequencing a Single Process

Example of Sequencing a Single Process

The procedure shown contains one Segment Command process named
“Cheryl’s Ramp.” The diagram that follows illustrates the signals available to
start and interrupt Cheryl’s Ramp.

Window with Segment process named “Cheryl’s Ramp”

Interrupt list

Start list

Signals received by and sent from “Cheryl’s Ramp”

To start Cheryl’s Ramp, you select a signal in the When Cheryl’s Ramp has completed what it
Start list. When you first create a test procedure, the has been programmed to do, it sends a
application selects a signal for you. For instance, the “Done” signal displayed as “Cheryl’s
<Procedure>.Start signal is automatically assigned to Ramp.Done.” You can use this signal to start
the first process on the procedure table. or interrupt other processes.

Cheryl’s Ramp
Start
Test Cheryl’s
Start Ramp.Done

You can interrupt Cheryl’s Ramp

Interrupt with any of the signals listed in the
Interrupt list. When a process is
interrupted, it immediately attains its
“done” state, and sends out a done
signal.

96 Working with MPT Processes MTS MultiPurpose TestWare®

 Example of Sequencing Multiple Processes

Example of Sequencing Multiple Processes

The window below contains three processes. The diagram that follows illustrates
the signals selected and available for each process.

Window with Three Processes

Signals received by and sent from processes

Kathy’s DAQ
Start
Kathy’s Ramp.Done
<Procedure>.Start
<Procedure>.Interrupt
Kathy’s Ramp Kathy’s Fatigue.Done Interrupt
Start
<Procedure>.Start Kathy’s Fatigue.Done
<Procedure>.Interrupt Kathy’s Ramp.Done
Kathy’s DAQ.Done <Procedure>.Start
Kathy’s Fatigue.Done <Procedure>.Interrupt
Interrupt
none Kathy’s Fatigue
<Procedure>.Start Start
<Procedure>.Interrupt Kathy’s Ramp.Done
Kathy’s Fatigue.Done <Procedure>.Start
Kathy’s DAQ.Done <Procedure>.Interrupt
Kathy’s DAQ.Done Interrupt
Note To simplify this illustration, some of the none
signals normally available in this
<Procedure>.Start
scenario are not shown.
<Procedure>.Interrupt
Kathy’s Ramp.Done
Kathy’s DAQ.Done

MTS MultiPurpose TestWare® Working with MPT Processes 97

About Sequencing Group Processes

About Sequencing Group Processes

A Group process is basically a sub-procedure that runs within your main MPT
procedure (or within another Group process). You sequence a group process to
run the same way you sequence other processes in your procedure table. The
navigation pane displays nested group processes in a tree view.

Set the Group

process’ Start
and Interrupt
signals in the
procedure table.

Sequence processes In addition to sequencing the Group process, you must also sequence processes
within a group defined in your Group process.

In your group table, you can set the Group process Start and Interrupt signals
the same way do for other processes. When you open the group table, the Start
and Interrupt signal lists include the <Group>.Start and <Group>.Interrupt
signals.

If you set a process’ Start or Interrupt control to <Group>.Start, the process

starts or interrupts when the group process starts. If you set the Start or
Interrupt control to <Group>.Interrupt, the process starts or interrupts when
the group process is interrupted.

End a group process The Group process procedure table has a Group is done when control located at
the bottom of the window.

If you specify a signal in this list, when the specified signal is received all active
processes in this group are interrupted and the Group process ends.

You can configure a Group process so that the processes it contains run normally
even when the Group process is interrupted.

For more information See “About Group Process Interrupts” on page 100.

98 Working with MPT Processes MTS MultiPurpose TestWare®

 How to Open the Group Table

How to Open the Group Table

Method 1 Click the Group process icon in your procedure table, then click on the
MPT toolbar.

Method 2 Right-click on the Group process icon and select Open Table from the menu.

To return to the previous procedure (or group) table, click .

Group Process Naming Conventions

You can add a Group process to the main procedure table or to another Group
processes (making a group within a group).

The title bar of the Group process window displays where the group is relative to
the main procedure table.

• For example, if your main procedure contains a group process, the group
process title bar would read—Procedure/Group Name.

• If your group contained another group, the title bar for the second group
process would read—Procedure/Group Name/Group Name.

This is an example of how the naming conventions work:

Two separate Group

processes have been added
to this procedure table.

We named the first Group

process “Group1.”

MTS MultiPurpose TestWare® Working with MPT Processes 99

About Group Process Interrupts

We named the second Group

process “Group2.”

About Group Process Interrupts

Normal interrupt Group processes have an interrupt terminal. By default, all of the processes inside
a Group process are interrupted when the Group process is interrupted, and the
Group process generates a done signal immediately. You can change this
behavior by creating a user-defined interrupt.

User-defined interrupt You can connect the interrupt terminal of a Group process to the start or interrupt
terminals of any of the processes inside the Group process. When you do this,
you are creating a user-defined interrupt.

When you create a user-defined interrupt, only the active processes inside of the
Group process that are connected to the Group process’ interrupt terminal are
affected when an interrupt occurs. The other processes in the Group process are
not affected, and run normally.

Repeat counts in A Group process never performs a repeat count when it is interrupted. When a
interrupted groups Group process is interrupted, the processes inside the Group complete their
activities according to how they are connected to the Group process’ Interrupt
terminal.

Normal interrupt The following examples illustrate the differences between a normal interrupt and
versus user-defined a user-defined interrupt on a Group process.
interrupt
Note The end effect of user-defined interrupts may be difficult to predict in
complex procedures. It is good practice to perform a test run of your
procedure in the simulation mode before actual testing.

Suppose we have a Group process that contains a Cyclic process and a Segment
process, and that the Group receives an interrupt while the Cyclic process is
active.

100 Working with MPT Processes MTS MultiPurpose TestWare®

 About Group Process Interrupts

If neither the Cyclic or Segment processes have an interrupt selected, the

following things occur when the Group is interrupted:

• The Cyclic process ends immediately.

• The Segment process ends immediately.

• The Group process ends immediately.

Trigger
Normal Interrupt
to a Group
Group Process
Process
When the Group
process is
Cyclic Segment
interrupted, the the
Group ends
Start Done immediately.

Interrupt

User-defined interrupt Suppose we start with the same scenario, but in this case, the Cyclic process’
example interrupt is set to <Group>.Interrupt.

MTS MultiPurpose TestWare® Working with MPT Processes 101

About Group Process Interrupts

In this case, when the Group is interrupted, the following things happen:

• The Cyclic process ends immediately.

• The Segment process runs normally.

• When the Segment process is done, the Group process ends.

Trigger User-Defined
Interrupt to a
Group Group Process
Process When the Group
process is
Cyclic Segment interrupted, the
Cyclic process
Start Done ends immediately,
but the Segment
process runs
normally.

Interrupt

102 Working with MPT Processes MTS MultiPurpose TestWare®

 How to Disable Processes

How to Disable Processes

You can disable a process in the following ways:

1. On the General tab in the process Parameters window, clear Process

Enabled.

This prevents the process from starting and generating any signals used to
start or interrupt another process. If you disable a command process this
way, all subsequent command processes are disabled. When you do this, the
process appear swith a red “X” in the left margin of the Procedure (or
Group) table.

2. On the General tab of the process’ Parameters window, type zero.

This method starts the process, but immediately sends out the process
“done” signal to other processes. This method works best if you want to
disable a command process without disabling all subsequent command
processes. When you do this, the process appears with a downward pointing
green arrow in the left margin of the Procedure (or Group) table.

3. On the procedure table, select the process, right-click the mouse, then click
the Enable selection to uncheck it. When you do this, the process appears
with a red “X” in the left margin of the Procedure (or Group) table.

MTS MultiPurpose TestWare® Working with MPT Processes 103

How to Disable Processes

104 Working with MPT Processes MTS MultiPurpose TestWare®

Chapter 9
Working with MPT Variables
Contents About MPT Variables 106
About Variable Operation 107
About Creating Variables with Multiple Associated Parameters 108
About Variables and the Operator Information Process 109
About Calculated Variables 112
Test Design Considerations for Adding Calculations to Variables 113
About Control-Mode Variables 114
About the Variable Editor 115
About Calculations and the Variables Editor 118
About Creating and Editing Variables 119
How to Create, Edit, Assign, and Unassign Variables with the Right-Click
Method 120
How to Create a Variable with the Make Tool 121
How to Add a Calculation to a Variable with the Variable Editor 122
How to Add a Calculation to a Variable with the Calculation Process 123

MTS MultiPurpose TestWare® Working with MPT Variables 105

About MPT Variables

About MPT Variables

The MPT Variables feature is a keyed option that equips the MultiPurpose
TestWare software with the following:

• A Variables Editor on the MPT Procedure Editor toolbar

• A Variable View selection in the Diaplay menu of the MPT Procedure

Editor menu

• An MPT Calculation process in the MPT Process Palette

• An enhanced Operator Information process in the MPT Process Palette

Benefits of using the With MPT variables, you can select individual parameters of test processes to be
variables feature viewed and changed while the test is running. Without MPT variables, you must
define test process parameters while the test is stopped.

This feature provides the following additional benefits:

• You can create variables and assign them to test process parameters.

• You can change selected calculation parameter values that are used in
equations defined in the Station Manager application.

• You can use the enhanced Operator Information process to view variables
and change variable values manually.

• You can use the MPT Calculation process to change variable values for
different passes. This allows you to create test procedures that are very
compact compared to test procedures that accomplish the same result but are
designed without variables.

• You can use the variable values stored in the specimen directory for post-test
analysis.

106 Working with MPT Variables MTS MultiPurpose TestWare®

 About Variable Operation

About Variable Operation

“Fixed” parameters Normally, when a procedure is running, you must stop the test and unlock the test
procedure before you can change any of the values in its processes. In this sense,
the parameter value is “fixed.”

For example, suppose you add a Cyclic Command process to a test procedure and
select a Segment Shape of Sine with a frequency of 10Hz. To change the
frequency after the test has started, you must stop the test, unlock the test
procedure, open the Cyclic Command Process dialog, and change the value.

Variable parameters With variable parameters, you can change parameter values without opening the
associated process definition dialogs. When you change a variable value, all
parameters associated with the variable are changed to the same value
simultaneously.

For example, suppose you create a variable named “VarFrequency,” and assign it
to the frequency parameter of a Cyclic Command process and a Segment
Command process. Now, with the procedure unlocked, you change the
“VarFrequency” value from 1 to 2 Hz. The frequency parameter in both the
Cyclic Command and Segment Command processes change to 2 Hz
simultaneously.

While the test is running, you can use an Operator Information or an MPT
Calculation process to change the value of the VarFrequency variable. When the
VarFrequency variable changes, the Cyclic Command and Segment Command
processes will use the new frequency value the next time they are triggered.

MTS MultiPurpose TestWare® Working with MPT Variables 107

About Creating Variables with Multiple Associated

About Creating Variables with Multiple Associated Parameters

The value of the variables feature is best illustrated when you control multiple
associated parameters with a single variable.

An example of using the For example, suppose you create a test procedure that includes several command
Variable Editor processes that all use the same frequency. Rather than entering a frequency value
for each process separately, you could associate all the frequency parameters
with a “Frequency” variable. Then, between tests (with the test stopped and the
test procedure unlocked) you could use the Variable Editor to change the
frequency value of all the processes at the same time without opening any of their
individual dialogs.

The Variable Editor allows you to

create and set variable values. In
this example, frequency is defined
as a Real Number variable, and
the value is set to 10Hz.
In the cyclic command process
labeled “Precycle 1”, the
frequency variable value is shown
in the highlighted field in the
Command tab. Highlighted fields
are not editable.

108 Working with MPT Variables MTS MultiPurpose TestWare®

 About Variables and the Operator Information

About Variables and the Operator Information Process

By adding an Operator Information process to a test procedure, you can change
selected variable values while the test is running.

When the test procedure is running and the Operator Information process is
triggered, it displays a run-time window. This window may require the operator
to verify or change the information specified by the test designer and click OK to
continue the test. All variable values are written to the test procedure data file.

As the test designer, you can choose the type of information displayed in the run-
time window, including predefined variables. You can choose which variables the
operator can change in the window.

You can control when the operator has the ability to change variables by
strategically placing Operator Information processes in the test procedure, or by
nesting them in a repeating Group process.

An example using the For example, suppose you create a test procedure that includes the following:
Operator Information
• A Group process that runs three times
process with Variables
• Within the Group process, a Cyclic Command process that starts when the
Group process starts, and an Operator Information process that starts when
the Command process is done.

• Within the Cyclic Command process, you select frequency as a variable.

• Within the Operator Information process, you select frequency as a variable

to be displayed on the execution window, and you select frequency to be
editable.

MTS MultiPurpose TestWare® Working with MPT Variables 109

About Variables and the Operator Information

When you run the test, a run-time window that allows the operator to enter a
frequency will appear each time the Operator Information process is triggered.
This allows the operator to change the variable value without stopping or
unlocking the test procedure.

In this example, the

Operator Information
process labeled “Frequency
Query” allows the operator
to assign a unique
frequency to the other
command processes without
stopping the test.
This capability was created
by selecting (highlighting)
the Frequency variable in
the Included list, and then
selecting the Editable check
box.

110 Working with MPT Variables MTS MultiPurpose TestWare®

 About Variables and the Operator Information

You use the Variable Editor to associate

parameters to variables. In this example,
the frequency parameter is associated to
a variable whose initial value is set to
10Hz.
You set the variable value to be editable
in the Variable tab of the Operator
Information process window (not
shown).

Each time the Operator Information

process is triggered (three times in this
example), it displays a run-time window
that allows the operator to edit the initial
value set in the Variables Editor.

If the operator entered 1, 5, and 2 in

each successive run-time window, it
would result in a scope trace that looks
like this.

MTS MultiPurpose TestWare® Working with MPT Variables 111

About Calculated Variables

About Calculated Variables

You can modify the value of any numeric variable with a calculation. For
example, suppose you have a two channel system in which:

• Channel 1 load is associated with the variable “VarLoad 1,” which you have
intialized to a value of 10kN.

• Channel 2 is associated the calculated variable “VarLoad 2,” which you

have defined as “VarLoad 2 = VarLoad 1 x 2”.

This defines Channel 2 load as two times the value of Channel 1 load.

Two methods to apply There are two methods you can use to add a calculation to a variable:
calculations
• You can use the “Calculated” checkbox in the Variables Editor for a selected
numeric variable.

• You can add a Calculations process from the process palette to your test
procedure.

Calculated checkbox in the

Variables Editor

Calculations process in the

Process Palette

112 Working with MPT Variables MTS MultiPurpose TestWare®

 Test Design Considerations for Adding Calculations

Test Design Considerations for Adding Calculations to Variables

The method you use to add a given calculation to a variable has test design
implications.

Calculations created When you use the Variable Editor to add a calculation to a variable:
with the Variable Editor
• The calculation is applied to the associated variable before the first process
in the test procedure is run.

• The calculation is applied to the variable only once during the execution of
the test procedure, regardless of where the variable is used in individual test
processes.

• Each time a calculated variable is queried for its value, the expression is
evaluated. Because current values may change during the execution of a
test, the result may be unpredictable. Because of this, it is good practice to
create test procedures that maintain a “fixed” relationship between
variables, as opposed to creating test procedures in which variable values
change dynamically.

Calculations created In contrast, when you use the MPT Calculation process to add a calculation to a
with the MPT Calculation variable, the calculation is applied to the associated variable whenever the MPT
process Calculation process is triggered. This means that:

• Any test process that uses the variable but runs before the MPT Calculation
process will not have the calculation applied, and

• The expression is evaluated only when the MPT Calculation process is

triggered.

• The calculation is reapplied to the variable each time the associated MPT
Calculation process is triggered, so that the change to the variable value is
cumulative.

MTS MultiPurpose TestWare® Working with MPT Variables 113

About Control-Mode Variables

About Control-Mode Variables

A control-mode variable is an enumeration variable that can be used to change
the control-mode parameter in multiple processes. After a control-mode variable
is assigned to a process’s control-mode parameter, any change to that variable
changes that process’s control mode.

This variable selection is manually set using the list in the Variable View window
or the Variables Editor when the test is not running. Control-mode variables do
not change during run time.

Supported processes The following processes support the use of variables to change the control mode:

• Cyclic Process

• Segment Process

• Dwell Process

• Sweep Process

• Cyclic ALC Process

Assign control-mode To assign a control-mode variable to a process, right-click in the process’s

variables Control Mode list and assign a control-mode variable.

Change control modes When the test is not running, use the Variable View window or the Variables
Editor to change the control-mode variable selection.

Any process control-mode parameter that uses that variable will change to reflect
the new control-mode variable selection.

A control-mode variable cannot be changed when the test is running.

114 Working with MPT Variables MTS MultiPurpose TestWare®

 About the Variable Editor

Variable Editor

About the Variable Editor

You use the Variable Editor to create, modify, delete, and organize variables.

Variable categories. Organizes Variable parameter assignment.

variables according to your Displays the parameters with
preference. You can rename which the variable is associated.
categories as desired.

Variable type. You select

the variable type when you
create the variable.The
variable type pertains to
the associated data.

Variable name. By default,

the variable name
describes the variable
type. You can rename
variables as desired.
“Make” tool. You use this tool to Variable type control Add and Delete
create and associate the variable (used when adding variable controls.
with the parameter. a variable).

Variable categories Variable categories help you organize variable types. When you open the
Variable Editor, “category 1” is available by default.

To use variables, you are not required to add or rename categories. However,
doing so may help you differentiate variable types. For example, you may want
to create one category that pertains to command variables and another that
pertains to data acquisition variables.

Categories are saved and restored with the test procedure, and are available in the
print preview display.

MTS MultiPurpose TestWare® Working with MPT Variables 115

About the Variable Editor

Variable types The variable type determines the type of data associated with the variable. You
must select the appropriate data type when you create a variable, as follows:

TYPE DESCRIPTION
Real Variables associated with real numbers.
Examples: frequency, end level, segment
count.
Integer Variables associated with integers. Example:
number of times a process runs.
Enumeration Variables associated with lists. Examples:
segment shape, compensator.
Boolean Variables associated with Boolean logic (true/
false).
String Variables associated with strings.

Make tool The Make tool creates and associates variables with parameters. By dragging the
Make tool from the Variable Editor window to the desired parameter in the
parameter definition window, you create and associate the variable to the
parameter at the same time.

Default variable naming When you use the Make tool to create a variable, the default variable name is
conventions associated the parameter name in the process definition window.

When you use the Add button to create a variable, the default variable name is
the name of the selected variable type.

116 Working with MPT Variables MTS MultiPurpose TestWare®

 About the Variable Editor

Example of variables in
the Variable Editor

In this example, “category

1” is renamed “Command”,
and include four variables;
two Enumeration (list) type
variables, and two Real
(number) type variables.

By default, variables are

named “variable 1”,
“variable 2,” and so forth.
The default Enumeration
variable names have been
renamed “Segment
Shape” (for the selection
In this example “Sine” is selected as
of segment shape) and
the initial value of the “Segment
“Adaptive Compensators”
Shape” enumeration type variable.
(for the selection of
adaptive compensators).

MTS MultiPurpose TestWare® Working with MPT Variables 117

About Calculations and the Variables Editor

About Calculations and the Variables Editor

“Calculated” checkbox You can use the Variable Editor to make a calculated variable by selecting the
and the Expression “Calculated” checkbox. When you do this, the initial value or currently applied
Editor calculation appears in the calculation pane. To build or modify an expression,
click on the Build Expression icon to display the Expression Editor window.

The Calculated checkbox is

available for Numeric and Real
type variables. Select this
checkbox to build
mathematical expressions that
may or may not include
variables.

Click the calculations button to

display the Expression Editor.

The Expression Editor

provides a method to combine
standard mathematical
operators and functions with
station signals.

Important!
Remember that each line in
expression pane must end
with a semicolon (“;”).

Values that can be

used in expressions.

118 Working with MPT Variables MTS MultiPurpose TestWare®

 About Creating and Editing Variables

About Creating and Editing Variables

To create and edit variables, you must use the Variable Editor. You can access the
Variable Editor directly from the MPT toolbar, or from a menu you can access by
right-clicking on process parameter fields.

When you right-click a

parameter field... ...a menu appears that allows you to create,
assign, unassign, and edit variables.

When you create a variable, the fields in the process parameter window
associated with the variable are highlighted (default is blue).

You cannot directly edit the values in highlighted fields. To edit the read only
value displayed in a parameter field, you must use the Variable Editor.

Parameters that have

variables assigned to them
appear highlighted.

When you right-click on a parameter in

which a variable can be assigned, the
Variable menu appears.

MTS MultiPurpose TestWare® Working with MPT Variables 119

How to Create, Edit, Assign, and Unassign

How to Create, Edit, Assign, and Unassign Variables with the Right-Click Method
How to create variables 4. Open the desired process window.
Note If the Variable menu does not appear when you right-click a parameter
box, variables are not available for that parameter.

5. Right-click the desired parameter box to display the Variable menu.

6. Select Make variable in, then select the desired category.

Note When a variable is assigned to a parameter, the parameter box appears
highlighted. To change the value of a variable (highlighted parameter),
you must right-click the variable and select Edit assigned variable, or
use the Variable Editor.

How to edit variables 1. Open the desired process window.

2. Right-click the desired variable (highlighted parameter box) to display the

Variable menu.

3. Select Edit assigned variable to open the Variables Editor.

4. Enter or select the new variable value.

How to change variable 1. Open the desired process window.

assignments
2. Right-click the desired variable (highlighted parameter box) to display the
Variable menu.

3. Select Assign variable.

4. Select the desired variable category and new variable you want to assign.

How to unassign 1. Open the desired process window.

variables 2. Right-click the desired parameter box to display the Variable menu.

3. Select Unassign variable.

Note When you unassign a variable, the associated parameter box will no
longer appear highlighted, which allows you to change the value of the
parameter directly in the process window.

120 Working with MPT Variables MTS MultiPurpose TestWare®

 How to Create a Variable with the Make Tool

How to Create a Variable with the Make Tool

1. Open the desired process window and the Variable Editor window. Position
the windows so you can see both.

2. Click the Make Tool on the Variable Editor window.

3. Drag the Make Tool to the desired parameter in the process window. If the
parameter is valid, the Make Tool pointer displays a square within the
pointer. If the selection is not valid, the Make Tool pointer displays a circle
with a slash.

In this example:
- A Numeric type variable has
been added to the variable
category named “Group Loop 3X”.
- The Numeric variable has been
named “Absolute End Level 1”.
- The Make Tool is positioned over
the Absolute End Level 1
parameter in the Cyclic Command
window. The pointer display
indicates a valid selection.

Make Tool pointer displaying valid

selection. An invalid selection
displays a circle with a slash.

Make Tool rubber band connecting

Make Tool to Make Tool pointer.

Make Tool in “seeking” mode

MTS MultiPurpose TestWare® Working with MPT Variables 121

How to Add a Calculation to a Variable with the

How to Add a Calculation to a Variable with the Variable Editor

1. From the MPT Tools menu, click Variable Editor.

2. In the tree view, expand the category icons as required and click (highlight)
the desired variable.
Note Calculations can be applied only to Real and Integer type variables.

3. Select the Calculations checkbox.

4. Click the calculations icon to display the Expression Editor.

Note For information about calculations, refer to the “Calculated Signals”
section in the MTS 793 Control Software manual (PN 100-147-130).

5. Build the calculation as desired and click Apply. If the calculation is valid,
the Expression Editor displays “success”. If the calculation is not valid, the
Expression Editor displays “error”.
Note Remember to type a “;” (semi-colon) after the espression before clicking
Apply.

122 Working with MPT Variables MTS MultiPurpose TestWare®

 How to Add a Calculation to a Variable with the

How to Add a Calculation to a Variable with the Calculation Process

1. If necessary, click the MPT Procedure Editor icon to display the Procedure
Editor.
Note The Calculation process is available only if your system is equipped with
the optional MPT Variables feature.

2. Drag a Calculation process from the Process Palette to the Procedure Editor
table.

3. Click the Calculation process on the Procedure Editor table to display

Calculation Process parameters.

4. Click the Variables tab, and move the desired variables from the Available
to the Included list.
Note Click the Calculation tab, then click the desired variable in the Signals
list. For information about calculations, refer to the “Calculated Signals”
section in the MTS 793 Control Software manual (PN 100-147-130).

5. Build the calculation as desired and click Apply. If the calculation is valid,
the Expression Editor displays “success”. If the calculation is not valid, the
Expression Editor displays “error”.
Note Remember to type a “;” (semi-colon) after the expression before clicking
Apply.

For more information See “Data Destination” on page 275.

MTS MultiPurpose TestWare® Working with MPT Variables 123

How to Add a Calculation to a Variable with the

124 Working with MPT Variables MTS MultiPurpose TestWare®

Chapter 10
Working with MPT Specimens
Contents About MPT Specimens 127
About Assigning MPT Specimens 127
About Creating and Linking MPT Specimens 127
How to Create and Link a New MPT Specimen with the Control Panel
128
How to Create and Link a New MPT Specimen with the Specimen Editor
129
How to Link an Existing MPT Specimen to a Different Procedure 129
About Runing Multiple Tests Against the Same MPT Specimen 130
MPT Specimen Editor 131
About MPT Files 134
About Specimen.dat Files 135
How to Create User-Specified.dat Files 137
About Specimen.log Files 138
About Specimen.mpp Files 138
About Specimen.mps Files 139
About Specimen.prm Files 139
About Loading MPT Specimens 140
About the Load Specimen Window 140
About the Load Procedure Selections 141
About the Restore Procedure State Selections 142
Procedure Has Not Been Run Against the MPT Specimen 144
Procedure Has Been Run Against the MPT Specimen 145
Procedure Has Been Run Against the MPT Specimen, and the MPT
Specimen Relinked to Another Procedure 146
Procedure Has Been Run Against the MPT Specimen, Modified, and
Saved 148

MTS MultiPurpose TestWare® Working with MPT Specimens 125

 Procedure Has Been Modified and Run Against the MPT Specimen
Without Being Saved 149
Procedure Has Been Modified, Run Against the MPT Specimen, and
Saved 151

126 Working with MPT Specimens MTS MultiPurpose TestWare®

 About MPT Specimens

About MPT Specimens

An MPT specimen contains a number of files associated with the execution of a
specific procedure.

The default location for your MPT specimen files is:

• C:\MTS 793\Projects\Project Name\MPT\Specimens

During the test, the MPT application writes test-generated data files to the
selected MPT specimen. These files include log files, data acquisition files, test
recovery files, and so forth.

For more information For detailed information on the files saved in the MPT specimen, see “About
MPT Files” on page 134.

About Assigning MPT Specimens

You must link a new or existing MPT specimen to a procedure before you can
run it. Once an MPT specimen has been linked to a particular procedure, that
procedure is available to the MPT specimen on the MPT control panel.

You can create new MPT specimens with the MPT control panel and the MPT
Specimen Editor. You may want to use a new MPT specimen to collect data for
a particular test run in a unique location.

For more information For more information on creating and linking MPT specimens, see “About
Creating and Linking MPT Specimens” on page 127.

For more information, see “About Loading MPT Specimens” on page 140.

About Creating and Linking MPT Specimens

You can use the MPT control panel or the MPT Specimen Editor to create MPT
specimens and link procedures to them.

Using the MPT control The MPT control panel is designed to create new MPT specimens one at a time,
panel or as needed, in less structured testing environments.

For example, suppose you want to modify a procedure (with an existing MPT
Specimen) and run it against a new MPT specimen. On the MPT control panel,
you could simply click the New Specimen button, name the MPT specimen, and
then click Run on the Station Controls panel. The new data, test log entries,
recovery information, and so on, is now directed to the new MPT specimen,
instead of the previous MPT specimen.

MTS MultiPurpose TestWare® Working with MPT Specimens 127

How to Create and Link a New MPT Specimen with

MPT specimens are automatically linked to the current procedure when you click
Run.

Using the Specimen The MPT Specimen Editor is designed for preparing a batch of MPT specimens
Editor and linking them with one or more procedures for future testing. The MPT
Specimen Editor is especially useful for test administrators who want to
predefine a number of MPT specimens for a test operator so he or she can run a
succession of tests.

For example, as a test administrator, you could create a number of new MPT
specimens and link them all to your procedure. This way, the test operator could
simply select the desired MPT specimen on the MPT control panel (which loads
the linked procedure) and run the test. When the test completes, the operator
could select the next MPT specimen, and could run the test again. The operator
could perform this for each predefined MPT specimen.

For more information For a description of the MPT control panel controls and indicators, see “About
the MPT Control Panel” on page 25.

For a description of the MPT Specimen Editor controls and indicators, see
“MPT Specimen Editor” on page 131.

How to Create and Link a New MPT Specimen with the Control Panel
To create an MPT specimen with the MPT control panel:

1. Click on the MPT control panel toolbar.

2. In the Specimen box, rename the new MPT specimen as desired.

To link the MPT specimen to a procedure file:

When you click Run on the Station Controls panel, the MPT specimen is
automatically linked to the loaded procedure.

128 Working with MPT Specimens MTS MultiPurpose TestWare®

 How to Create and Link a New MPT Specimen with

How to Create and Link a New MPT Specimen with the Specimen Editor
To create an MPT specimen with the MPT Specimen Editor:

1. Click New on the MPT Specimen Editor. An MPT specimen is added to

the MPT specimen list.

2. In the box above the MPT specimen list, rename the new MPT specimen as
desired and press the Enter key on the keyboard.

To link the MPT specimen to a procedure file:

1. Click Procedure Path/File Name.

2. Click the desired procedure file in the Select procedure file window.
Note If the procedure is new, make sure you save it to ensure that it appears in
the list of procedures in the Select procedure file window.

How to Link an Existing MPT Specimen to a Different Procedure

Note This procedure pertains to MPT specimens linked to procedures that
have already been run.

With the Control Panel 1. Open the procedure you want to which you wish to link your MPT
specimen.

2. In the Specimen list on the MPT control panel, click the MPT specimen you
want to link.

3. In the Load Specimen window that appears, click Currently Loaded

Procedure.

With the Specimen 1. Open the MPT Specimen Editor.

Editor
2. In the MPT specimen list, click the MPT specimen you want to link.

3. Click Procedure Path/File Name.

4. Click the desired procedure file in the Select procedure file window.
Note If the procedure is new, make sure you save it first to ensure that it
appears in the list of procedures in the Select procedure file window.

When you select the MPT specimen in the MPT control panel, MPT
displays the Load Specimen window.

MTS MultiPurpose TestWare® Working with MPT Specimens 129

About Runing Multiple Tests Against the Same MPT

5. In the Load Specimen window, click Procedure assigned to the Specimen.

For more information For more information on loading procedures, see “About Loading MPT
Specimens” on page 140.

About Runing Multiple Tests Against the Same MPT Specimen

You may want to run a procedure against an MPT specimen more than once, or
you may want to run different tests against the same MPT specimen. In either
case, it is important to note how the data files in your MPT specimen are affected
when you do this.

By default, if you run another test against your MPT specimen, the MPT
application:

• Appends new test information to the existing data file and log file .

• Writes over the information in the procedure snapshot file and dynamic state
snapshot file with the new test information.
Note You can configure whether new data overwrites or appends to the
previous data with the MPT Options Editor.

For more information For more information about the using the MPT Options Editor, see “About the
MPT Options Editor” on page 62.

See “About Specimen.dat Files” on page 135.

See “About Specimen.log Files” on page 138.

See “About Specimen.mpp Files” on page 138.

See “About Specimen.mps Files” on page 139.

130 Working with MPT Specimens MTS MultiPurpose TestWare®

 MPT Specimen Editor

MPT Specimen Editor

Use the MPT Specimen Editor to create, edit, and delete MPT specimens.

Access From the MPT control panel and the MPT Procedure Editor, the access path is:

Or:

Tools > Specimen Editor

MPT specimens store a number of files associated with running a procedure.

Before you can run your procedure, you must specify a new or existing MPT
specimen for the test.

MPT Specimen Editor (part 1 of 3)

ITEM DESCRIPTION
MPT specimen list Displays the MPT specimens saved in the selected MPT Specimen Directory.
Note While in the execute mode, if you click an MPT specimen that is
currently loaded in the MPT control panel the application disables the
specimen list and most controls. To make the controls available, you
must use the up and down arrows to switch to an available MPT
specimen.

Status Displays access and data status of the MPT specimen.

In the first box, the MPT specimen access status is displayed:
• Available—You can edit the MPT specimen.

• Unavailable—You cannot edit the MPT specimen because it is currently

assigned to another instance of the MPT application.

• Current—The MPT specimen is currently assigned on the MPT control

panel. You can edit but not delete this specimen.

In the second box, the MPT specimen data status is displayed:

• Empty—The MPT specimen does not contain test information.

• Has Data—The MPT specimen contains test information.

MTS MultiPurpose TestWare® Working with MPT Specimens 131

MPT Specimen Editor

MPT Specimen Editor (part 2 of 3)

ITEM DESCRIPTION

Displays the procedure associated with the selected MPT specimen.

Procedure Path/
File Name To choose a new procedure:
• Type the path to the desired procedure followed by the procedure name,
or

• Click the Procedure Path/File Name button and use the Select Procedure
File window to link a different procedure to your current MPT specimen.

By default, the Procedure Path/File Name box includes the placeholder

“<Procedure Folder>”, which specifies the path: C:\MTS 793\Projects\current
Project\MPT\Procedures.
This means typing ”<Procedure Folder>\sample test.000”
is the same as typing the full path
“C:\MTS 793\Projects\current Project\MPT\Procedures\sample test.000”.
In fact, if you type a full path and the application recognizes that part of the
path matches the current specification of a placeholder, it substitutes the
placeholder.
Likewise, if you click the Procedure Path/File Name button and use the
browser to locate a file that has a path that matches the current specification of
a placeholder, the placeholder appears in the Procedure Path/File Name box.
Comment Type comment information that is saved in the MPT specimen.
New Creates a new MPT specimen.
Note The new MPT specimen is empty and is not linked to a procedure.

Copy Creates a new MPT specimen based on the selected MPT specimen.
The new copy includes all attributes of the original MPT specimen, including
procedure association, comments, and MPT specimen directory.
Note Test data and status are not copied.

Delete Deletes the selected MPT specimen.

132 Working with MPT Specimens MTS MultiPurpose TestWare®

 MPT Specimen Editor

MPT Specimen Editor (part 3 of 3)

ITEM DESCRIPTION

Specifies the directory where your MPT specimens are saved for the current
Specimen MPT session.
Directory Path
To choose a new directory, click the Specimen Directory Path button and use
the MPT Specimen Directory Path window to select a new directory.
Changes made to the MPT Specimen Directory Path window apply only to the
current MPT session. The directory path reverts to the default directory path
when MPT is reloaded.
To change the default MPT specimen directory path, use the Project Manager
application to change the Project Settings (see Project Manager information in
the Series 793 Control Software manual, part number 100-147-130).
Name Template Specifies the default label applied to MPT specimens you create.
Note The default MPT specimen name is “spec”. When you create new
MPT specimens, their default labels are “spec01,” “spec02,” “spec03,”
and so forth.

To change the default MPT specimen name, type a name in the Name
Template box. The new name applies to the current MPT session. If you want
to make this new name the new default name, click Set Default. Changes are
effective immediately. The name template may also be changed with the
Project Manager application.
Note It is good practice to add a space after your name entry. This makes
additional instances of the name easier to read; for example, “dogbone
01, dogbone 02, dogbone 03,” versus “dogbone01, dogbone02,
dogbone03.”

For more information For more information about placeholders, see “About placeholders” on page 203,
and “Installed 793 Files” in the 793 Controller Overview manual (PN 100-162-
928).

MTS MultiPurpose TestWare® Working with MPT Specimens 133

MPT Specimen File Types

MPT Specimen File Types

About MPT Files
The number of files (and the content of each file) in an MPT specimen depends
on several things, including:

• The number of times a test was run against the MPT specimen

• The runtime state of the procedure when the test was closed

• Whether or not you have specified user-defined data files

• The processes in the procedure

In most cases, after you run a test, a typical MPT specimen contains the
following files:

• Specimen.dat—is an MPT specimen data file that contains data acquired by

the data acquisition processes defined in your procedure. If you configured a
data acquisition process to write data to a user-specified data file, the file
you specified appears in the MPT specimen.

• Specimen.log—is a record of the test events that occurred while the

procedure was running.

• Specimen.mpp—is a recovery file used to restore the procedure to the same

state it was the last time the test was run

• Specimen.mps—is a recovery file used to restore the runtime state of the

procedure

• Specimen.prm—is a file that contains the name of the procedure currently

linked to the MPT specimen. This file also contains any comments entered
with the MPT Specimen Editor.

• Specimen.lck—is a temporary control file used to prevent instances of

MPT on different stations from simultaneously accessing the same MPT
specimen.

For more information See “About Specimen.dat Files” on page 135.

See “How to Create User-Specified.dat Files” on page 137.

See “About Specimen.log Files” on page 138.

See “About Specimen.mpp Files” on page 138.

134 Working with MPT Specimens MTS MultiPurpose TestWare®

 About Specimen.dat Files

See “About Specimen.mps Files” on page 139.

See “About Specimen.prm Files” on page 139.

About Specimen.dat Files

The Specimen.dat file contains data acquired by the data acquisition processes in
your procedure.

Each time you run a procedure against an MPT specimen (that is, each time you
press run after pressing reset), newly acquired data overwrites or is appended to
the current data in the Specimen.dat file. The specimen data file may contain data
from more than one test if more than one test has been run against the same MPT
specimen.

Note You can configure whether new data overwrites or appends to the
previous data with the MPT Options Editor.

If you configure a data acquisition process to write data to a user-

specified data file, then it will not write data to the Specimen.dat file.

Sample MPT specimen The following data file was created by a Peak/Valley Acquisition process that
data file monitored the displacement feedback and acquired data on the time and
displacement feedback signals.

This text string specifies the file format.

MTS MultiPurpose TestWare® Working with MPT Specimens 135

About Specimen.dat Files

How to format the data You can configure the MPT application to format the data written to the
in the MPT specimen Specimen.dat file in one of three ways:
data file
• Plain—test data is space-delimited. This option provides the most useful
output when viewing the test data in an application such as Notepad or
Microsoft Word.

• Lotus—test data is comma-delimited, with text strings enclosed in

quotation marks (this is sometimes referred to as the CSV format). This
option formats the data for use with Lotus 1-2-3.

• Excel—test data is tab-delimited. This option formats the data for use with
Microsoft Excel.

You specify the data file format on the Specimen tab of the MPT Options
Editor.

If you plan to use the Excel File Converter, the data must be tab-or comma-
delimited.

How to parse the MPT The first line of the data file is a text string that includes information such as the
specimen data file decimal separator, column separator, time formats, date formats, and so forth.
This header may be used if you plan to parse the data file with a custom
application.

A typical header looks like this:

MTS793|MPT|ENU|1|0|.|/|:|1|0|0|A

The format of this header line is as follows:

MTS793|progName|sLanguage|version|iDelim|sDecimal|sDate|sTime|iCountry|iDate|iTime|sCode
Where:
progName=MPT or BTW
sLanguage= Natural language (standard three-character abbreviation)
version=Version of this format string
iDelim=Data delimiter: 0 for space (plain), 1 for comma (Lotus), 2 for tab (Excel)
sDecimal=International decimal separator
sDate=International date separator
sTime=International time separator
iCountry=International country value
iDate=International date format
iTime=International time format
sCode=Character Set Code: A for ANSI, O for OEM (currently always A)

136 Working with MPT Specimens MTS MultiPurpose TestWare®

 How to Create User-Specified.dat Files

For more information For more information, see “How to Create User-Specified.dat Files” on page
137.

For more information, see “MPT Specimen Panel” on page 29.

For more information, see Appendix 20, “Excel File Converter”.

How to Create User-Specified.dat Files

You can isolate the data acquired by any specific data acquisition process (or a
set of processes) by configuring the process to write to the data file that you
specify rather than the default Specimen.dat file.

To configure the process to write to a user-specified data file:

1. In the data acquisition process parameters window, click the Destination

tab.

2. In the Destination list, click User-specified data file.

3. In the User Data File box, type a name for your data file. (A dat extension is
added to the name you type.)

MTS MultiPurpose TestWare® Working with MPT Specimens 137

About Specimen.log Files

About Specimen.log Files

The Specimen.log file contains the contents of the MPT Specimen Log. This file
is generated during the test, and it includes logged file events, station state
changes (Run/Hold/Stop), program state changes (Starting, Running, and so on)
and MPT counter values.

By default, this file is cumulative; that is, new information is added when you
perform new tests against the same MPT specimen.

Changing the data You can change this behavior with the MPT Options Editor as follows:
acquired in the
• Use the Specimen Log Overwrite/Append controls on the Specimen tab.
specimen.log file
• Use the Minimum Severity and Source controls on the Specimen Log tab.

About Specimen.mpp Files

The Specimen.mpp file is a recovery file used to restore the procedure settings
used the last time the test was run. Whenever you click Run on the Station
Controls panel, the MPT application updates the mpp file with the current test
settings regardless of whether the settings are saved or not.

This way, if you modify and run your test, but you forget to save your changes
when you close the test, you can restore the modifications the next time you run
the test.

Note This file is created only when test recovery is enabled with the MPT
Options Editor.

For more information For more information, see “MPT Options Editor Recovery Tab” on page 74.

For information on restoring unsaved test settings, see “About Loading MPT
Specimens” on page 140.

138 Working with MPT Specimens MTS MultiPurpose TestWare®

 About Specimen.mps Files

About Specimen.mps Files

The Specimen.mps file is a recovery file used to restore an interrupted test at (or
close to) the point it was at when it was interrupted.

This way, if your test is interrupted before it completes (due to a power outage,
interlock, or accidental stop) you can resume the test from where it was
interrupted rather than restarting from the beginning of the test.

The MPT application updates this file according to the settings on the MPT
Options Editor. Each update includes the test program state, the current counter
values, and the status of each active process in the procedure.

Note By default, the MPT application updates the mps file each time the
program state changes, and at 60-second time intervals.

For more information See “MPT Options Editor Recovery Tab” on page 74.

For information on resuming an interrupted test from the point of interruption,

see “About Loading MPT Specimens” on page 140.

About Specimen.prm Files

The Specimen.prm file contains the name of the procedure linked to the MPT
specimen, along with any comments typed in the Comment box of the MPT
Specimen Editor.

When you open an MPT specimen and proceed to load the Procedure assigned
to the Specimen, the MPT application loads the procedure defined in this file.

The procedure named in this file refers to the last saved version of the procedure
linked to the MPT specimen.

Note Even if you do not type information in the Comment box on the MPT
Specimen Editor, the entry “Comment=\” still appears in the
Specimen.prm file.

For more information For information on loading MPT specimens and restoring procedures with the
MPT control panel, see “About Loading MPT Specimens” on page 140.

MTS MultiPurpose TestWare® Working with MPT Specimens 139

About Loading MPT Specimens

About Loading MPT Specimens

If you select an MPT specimen that MPT has associated with a procedure with
more than one version (where the snapshot in the MPT specimen is different than
the version saved by the user), MPT displays the Load Specimen window.

Note If you load an MPT specimen that has not been run and you have not
linked a procedure to it (via the MPT Specimen Editor), then the MPT
Load Specimen window will not appear.

When MPT displays the Load Specimen window, you should make your
selection carefully. If you select a procedure without understanding the
consequences, you may limit your options later.

For example, assume you choose an MPT specimen on the MPT control panel
and you load a test other than the one that is currently assigned to that MPT
specimen. In this case, once you click Run, you would not be able to retrieve the
recovery information created for the original procedure.

For more information See “About the Load Specimen Window” on page 140.

About the Load Specimen Window

Depending on the past usage of an MPT specimen, the Load Specimen window
include some or all of these options:

• Currently loaded procedure

• Procedure linked (or assigned) to the MPT specimen

• Procedure snapshot from last run

• Most recently saved version

Each option is followed by a path name and time stamp to help you determine
which procedure to load.

Note The time stamp reflects when the procedure was last saved by the
operator. It may be helpful to think of the time stamp as the test version
number.

If the procedure you select in the Load Specimen window has been run against
the selected MPT specimen, you can retrieve it in either its Reset state or its
Saved state.

For more information See “About the Restore Procedure State Selections” on page 142.

140 Working with MPT Specimens MTS MultiPurpose TestWare®

 About the Load Procedure Selections

To see how these selections are used in specific situations, see “MPT Specimen
Loading Examples” on page 143.

For more information, see “About the Load Procedure Selections” on page 141.

About the Load Procedure Selections

The following sections describe the options available in the Load Specimen
window:

Currently loaded This option uses the procedure currently open in the MPT Procedure Editor.
procedure When you click Run on the Station Controls panel, the selected MPT specimen
is linked to the current procedure.

Note If the currently loaded procedure has been modified but has not been
saved, “modified” is displayed after the time stamp. If the procedure has
never been saved, then it will not display a time stamp.

Procedure linked (or This option loads the procedure that is currently linked to the MPT specimen.
assigned) to the MPT This procedure is recorded in the .prm file in the MPT specimen.
specimen
Note If the referenced procedure file has been deleted or moved, this selection
is dimmed, and “not found” is displayed after the file name.

Procedure snapshot This option loads a copy of the last procedure run against the MPT specimen.
from last run This procedure is recorded in the .mpp recovery file in the MPT specimen.

You should select this option if you want to load the procedure and restore the
settings exactly as they were the last time you ran the test. This option can be
used in conjunction with the saved state selection to recover an interrupted test

If the procedure was modified without being saved before it was run, “modified”
is displayed after the time stamp. This means the snapshot version of the
procedure run against the MPT specimen contains modifications that may not be
present in the saved version of the procedure.

Most recently saved This option loads the most recently saved version of the procedure.
version
This option appears only if the saved procedure has been modified since it was
saved and is different from the linked procedure.

For more information For more information on the recovery file, see “About Specimen.prm Files” on
page 139.

For more information on the recovery file, see “About Specimen.mpp Files” on
page 138.

MTS MultiPurpose TestWare® Working with MPT Specimens 141

About the Restore Procedure State Selections

See “About the Restore Procedure State Selections” on page 142.

About the Restore Procedure State Selections

If test recovery is enabled, the MPT application records the state and run-time
status of the test as specified on the Recovery tab of the MPT Options Editor.
This data is recorded in the mps recovery file in the MPT specimen.

In the Load Specimen window, when you select a procedure that has run against
the current MPT specimen, you can use the Restore procedure state to control
to reset or restore the procedure state.

One or more of the following options are available:

• Reset—restores the selected procedure to its starting state, with counters

reset to zero.

• Saved state: Done—restores the procedure in its done state, and includes a
record of counter values as they were when the test was complete.

• Saved state: In progress—restores the procedure back to the point the test
was stopped, and includes a record of the test’s counter values, hydraulic
status, and so on, at that time. This is the appropriate selection if you wish to
recover a test; that is, you have selected the snapshot procedure and wish to
resume the test at, or close to, the point it was interrupted.

• Saved state: Error—brings the procedure back to the point at which it was
stopped by an error condition (there may be a corresponding entry in the log
file that reveals more information).

For more information For more information on the recovery file, see “About Specimen.mps Files” on
page 139.

142 Working with MPT Specimens MTS MultiPurpose TestWare®

 MPT Specimen Loading Examples

MPT Specimen Loading Examples

The following examples are provided to help you choose the right procedure
when you load an existing MPT specimen on the MPT control panel.

The following scenarios are shown:

• “Procedure Has Not Been Run Against the MPT Specimen” on page 144

• “Procedure Has Been Run Against the MPT Specimen” on page 145

• “Procedure Has Been Run Against the MPT Specimen, and the MPT
Specimen Relinked to Another Procedure” on page 146

• “Procedure Has Been Run Against the MPT Specimen, Modified, and
Saved” on page 148

• “Procedure Has Been Modified and Run Against the MPT Specimen
Without Being Saved” on page 149

• “Procedure Has Been Modified, Run Against the MPT Specimen, and
Saved” on page 151

The windows shown for these scenarios do not show all possible combinations;
the windows that MPT displays for you depends on your situation.

MTS MultiPurpose TestWare® Working with MPT Specimens 143

Procedure Has Not Been Run Against the MPT

Procedure Has Not Been Run Against the MPT Specimen

Suppose you use the MPT Specimen Editor to create a new MPT specimen
named Sample 1 and link it to procedure “def.000.” Then you open procedure
“abc.000” from the File menu and select MPT specimen Sample 1 on the MPT
control panel. When you do this, a window appears with the following selections:

MPT Load Specimen window for specimen Sample 1

DIALOG ITEM DEFAULT

Which procedure do you wish to select?

Currently loaded procedure: (abc.000) No
Procedure assigned to the Specimen: (def.000) Yes

Restore procedure state to:

Reset Yes
Saved state: No

Note If the Saved state selection is disabled (grey), it means the procedure
linked to the MPT specimen has not been run against the MPT specimen
(as in this scenario), or that the procedure has been run, but its recovery
feature has been disabled.

Currently loaded If you choose this selection and then run the test, MPT unlinks the MPT
procedure specimen from procedure “def.000” and links it to procedure “abc.000.” The
MPT specimen now contains information (test data, log entries, and so on) from
procedure “abc.000.”

Procedure assigned to This is the default selection. If you choose it and then run the test, MPT replaces
the MPT specimen the procedure currently in memory, “abc.000,” with the procedure you linked to
the MPT specimen with the MPT Specimen Editor, “def.000.”

Restore procedure state In this case, procedure “def.000” has never been run against the MPT specimen,
so MPT has not created an mps file or an mpp file in the MPT specimen yet.
Therefore, the Saved state selection is disabled, and Reset is the only option
available. Reset causes the procedure to begin at its starting point, with counters
reset to zero.

144 Working with MPT Specimens MTS MultiPurpose TestWare®

 Procedure Has Been Run Against the MPT

Procedure Has Been Run Against the MPT Specimen

Suppose you load procedure “def.000” into memory, and run it unmodified on
MPT specimen Specimen 1. Then you load procedure “abc.000” from the File
menu, and select MPT specimen Specimen 1 from the MPT control panel. When
you do this, a dialog appears with the following selections:

MPT Load Specimen dialog for specimen Sample 1

DIALOG ITEM DEFAULT

Which procedure do you wish to select?

Currently loaded procedure: (abc.000) No
Procedure assigned to the Specimen: (def.000) Yes

Restore procedure state to:

Reset No
Saved state: Done Yes

Currently loaded If you choose this selection and then run the test, MPT unlinks the MPT
procedure specimen from procedure “def.000” and links it to procedure “abc.000”. The
MPT specimen now contains information (test data, log entries, and so on) from
different procedures (“abc.000” and “def.000”). Choosing this selection prevents
you from recovering status information stored in the specimen about the
execution of “def.000”.

Procedure assigned to This is the default selection. If you choose it and then run the test, MPT replaces
the MPT specimen the procedure currently in memory, “abc.000”, with the procedure linked to MPT
specimen, “def.000”. This is the saved version of the procedure. In this scenario,
this version is the same as the version that MPT automatically saved to the mpp
file when the procedure was last run.

Restore procedure While the procedure “def.000” was being run, MPT recorded the progress or
state to state of the execution of the test at intervals defined in the Recovery tab of the
Options Editor. MPT saves this information in the mps file, where it is
continually updated until the test is complete or in its Done state.

The Saved state selection in the Restore procedure state to box displays the
last saved state stored in the mps file. In this case the test ran to completion, so
the last saved state is Done. Done brings the procedure back to its done state, and
includes information such as counter values as they were when the test was
complete; in contrast, Reset brings the procedure back to its starting point, with
counters reset to zero.

MTS MultiPurpose TestWare® Working with MPT Specimens 145

Procedure Has Been Run Against the MPT

Example Suppose that in this scenario the test was interrupted while it was being run. In
this case the Saved state selection would display In progress instead of Done.

The State state: In progress status shows the procedure was run against the
MPT specimen, but was stopped before the test was complete. When a procedure
is stopped in progress, MPT saves the state of the procedure when it was stopped
in the mps file.

If the test had been inadvertently interrupted and you wished to resume the test at
(or close to) the point of interruption, you would choose this Saved state
selection.

Procedure Has Been Run Against the MPT Specimen, and the MPT Specimen
Relinked to Another Procedure
Suppose you load procedure “def.000” into memory, and run it unmodified on
MPT specimen Sample 1. Next, you use the MPT Specimen Editor to link
procedure “ghi.000” to MPT Specimen Sample 1. Then you load procedure
“abc.000” from the File menu, and select Sample 1 in the MPT control panel.
When you do this, a window appears with the following selections:

MPT Load Specimen window for specimen Sample 1

DIALOG ITEM DEFAULT

Which procedure do you wish to select?

Currently loaded procedure: abc.000 No
Procedure assigned to the Specimen: ghi.000 No
Procedure snapshot from last run: def.000 Yes

Restore procedure state to:

Reset No
Saved state: Done Yes

Currently loaded If you select this and then run the test, MPT unlinks the MPT specimen from both
procedure the procedure it was last run against, “def.000,” and from the procedure you
linked to it with the MPT Specimen Editor, “ghi.000.” MPT links the MPT
specimen to the procedure currently in memory, “abc.000”.

146 Working with MPT Specimens MTS MultiPurpose TestWare®

 Procedure Has Been Run Against the MPT

The MPT specimen now contains information (test data, log entries, and so on)
from two different procedures (“def.000” and “abc.000”). Choosing this selection
prevents you from recovering status information stored in the specimen about the
execution of “def.000.”

Procedure assigned to If you choose this and then run the test, MPT unlinks the MPT specimen from the
the MPT specimen procedure that it was last run against, “def.000,” and link it to procedure
“ghi.000.” The MPT specimen now contains information (test data, log entries,
and so on) from different procedures (“ghi.000” and “def.000”). Also, choosing
this selection prevents you from recovering status information stored in the
specimen about the execution of “def.000.”

Procedure snapshot This is the default selection. If you choose it and then run the test, MPT replaces
from last run the procedure currently in memory, “abc.000,” with procedure “def.000” as it
was last run against the MPT specimen. This selection dissociates the MPT
specimen from the procedure you linked to it with the MPT Specimen Editor,
“ghi.000.”

When the operator clicked the Run button on the Station Controls panel to run
“def.000” (as it was last run on the MPT specimen), MPT recorded the current
state of the procedure and stored it in the mpp file. So even though you linked a
new procedure to the MPT specimen with the MPT Options Editor, the mpp file
contains a copy of the procedure as it was last run against the MPT specimen,
called a snapshot.

Restore procedure You can choose the state to which the specimen is restored. In this case the saved
state to state is Done, so selecting the saved state brings the procedure back to its done
state, and includes information such as counter values as they were when the test
was complete. Selecting Reset brings the procedure back to its starting point,
with counters set to zero.

The Saved state information is stored in the mps file. If the test had been
inadvertently interrupted and you wished to resume the test at (or close to) the
point of interruption, you would choose this selection.

MTS MultiPurpose TestWare® Working with MPT Specimens 147

Procedure Has Been Run Against the MPT

Procedure Has Been Run Against the MPT Specimen, Modified, and Saved
Suppose you load procedure “def.000” into memory, and run it unmodified on
MPT specimen Sample 1. Next, you modify this procedure and save your
changes. Then you load procedure “abc.000” from the File menu, and select
Sample 1 in the MPT control panel. When you do this, a window appears with
the following selections:

MPT Load Specimen window for specimen Sample 1

DIALOG ITEM DEFAULT

Which procedure do you wish to select?

Currently loaded procedure: abc.000 No
Procedure assigned to the Specimen: def.000 No
Procedure snapshot from last run: def.000 Yes

Restore procedure state to:

Reset No
Saved state: Done Yes

Currently loaded MPT unlinks the MPT specimen from procedure “def.000” and links it to
procedure procedure “abc.000”. If you do this and run the test, the MPT specimen contains
information (test data, log entries, and so on) from different procedures
(“abc.000” and “def.000”). Choosing this selection prevents you from being able
to recover status information about the execution of “def.000.”

Procedure assigned to MPT replaces the procedure currently in memory, “abc.000,” with the procedure
the MPT specimen linked to MPT specimen, “def.000.” This version of the procedure includes
modifications not present when the procedure was last run, because the operator
modified and saved it after it was run.

Procedure snapshot This is the default selection. If you choose it and then run the test, MPT replaces
from last run the procedure currently in memory, “abc.000,” with procedure “def.000” as it
was last run against the MPT specimen. This is the version of the procedure that
MPT automatically saved to the mpp file when the test was run. In this case, the
procedure was modified and saved after the test was run, so the current version of
the procedure includes modifications not present in the mpp file.

148 Working with MPT Specimens MTS MultiPurpose TestWare®

 Procedure Has Been Modified and Run Against the

Restore procedure Since the MPT specimen was last run against the modified version of “def.000,”
state to you can choose the state to which it restores. In this case the saved state is Done,
so selecting the saved state restores the procedure to its done state, and includes
information such as counter values as they were when the test was complete.
Selecting Reset restores the procedure to its starting point, with counters set to
zero.

The Saved state information is stored in the mps file. If the test had been
inadvertently interrupted and you wished to resume the test at (or close to) the
point of interruption, you would choose this selection.

In this scenario, if you select the Procedure assigned to the Specimen and select
the Restore procedure state to: Saved State options, then the runtime state is
restored to a different procedure than the one that was running when it was saved.

If changes to the procedure included adding, removing, or renaming processes,

however, the runtime state may not restore completely, and a warning message is
displayed.

Procedure Has Been Modified and Run Against the MPT Specimen Without Being
Saved
Suppose you load procedure “def.000” into memory, modify it without saving
your changes, and then run it against MPT specimen Sample 1. Next, you load
procedure “abc.000” from the File menu, and select Sample 1 in the MPT
control panel. When you do this, a window appears with the following selections:

MPT Load Specimen window for specimen Sample 1

DIALOG ITEM DEFAULT

Which procedure do you wish to select?

Currently loaded procedure: abc.000 No
Procedure assigned to the Specimen: def.000 No
Procedure snapshot from last run: def.000 (modified) Yes

Restore procedure state to:

Reset No
Saved state: Done Yes

MTS MultiPurpose TestWare® Working with MPT Specimens 149

Procedure Has Been Modified and Run Against the

Currently loaded MPT unlinks the MPT specimen from procedure “def.000” and link it to
procedure procedure “abc.000.” If you do this and run the test, the MPT specimen contains
information (test data, log entries, and so on) from different procedures
(“abc.000” and “def.000”). Also, choosing this selection prevents you from
recovering status information stored in the specimen about the execution of
“def.000”.

Procedure assigned to MPT replaces the procedure currently in memory, “abc.000,” with the procedure
the MPT specimen linked to MPT specimen, “def.000.” This version of procedure “def.000” does
not include the modifications present when it was last run against the MPT
specimen. It is the version last saved by the operator.

Procedure snapshot This is the default selection. If you choose it and then run the test, MPT replaces
from last run the procedure currently in memory, “abc.000,” with the procedure “def.000” as it
was last run against the MPT specimen.

This version of procedure “def.000” includes the modifications present when it

was last run against the MPT specimen. MPT automatically saved a copy of the
modified procedure to the mpp file when the test was last run.

The “modified” flag means MPT noted a difference between the version of the
procedure saved by the operator and the version that MPT saved to the mpp file
when the test was run. This means the procedure was modified but not saved by
the operator when run against the MPT specimen. MPT automatically saves the
modified version in the mpp file when the operator presses the Run button on the
Station Controls panel. This selection lets you retrieve the modified version of
the procedure as it was run against the MPT specimen.

Restore procedure Since the MPT specimen was last run against the modified version of “def.000,”
state to you can choose the state to which it restores. In this case the saved state is Done,
so selecting the saved state brings the procedure back to its done state, which
includes information such as counter values as they were when the test was
complete. Clicking Reset brings the procedure back to its starting point, with
counters set to zero.

The Saved state information is stored in the mps file. If the test had been
inadvertently interrupted and you wanted to resume the test at (or close to) the
point of interruption, you would choose this selection.

150 Working with MPT Specimens MTS MultiPurpose TestWare®

 Procedure Has Been Modified, Run Against the MPT

Procedure Has Been Modified, Run Against the MPT Specimen, and Saved
Suppose you load procedure “def.000” into memory, modify it without saving
your changes, then run it against MPT specimen Sample 1. Then, after you have
run, you save the modified procedure. Next, you load procedure “abc.000” from
the File menu, and select Sample 1 in the MPT control panel. When you do this,
a window appears with the following selections:

MPT Load Specimen window for specimen Sample 1

DIALOG ITEM DEFAULT

Which procedure do you wish to select?

Currently loaded procedure: abc.000 No
Procedure assigned to the Specimen: def.000 No
Procedure snapshot from last run: def.000 (modified) Yes

Restore procedure state to:

Reset No
Saved state: Done Yes

Currently loaded If you choose this and then run the test, MPT unlinks the MPT specimen from
procedure procedure “def.000” and link it to procedure “abc.000.” The MPT specimen
contains information (such as test data and log entries) from two different
procedures (“abc.000” and “def.000”). Also, choosing this selection prevents you
from recovering status information stored in the specimen about the execution of
“def.000”.

Procedure assigned to If you choose this and then run the test, MPT replaces the procedure currently in
the MPT specimen memory, “abc.000,” with the procedure linked to MPT specimen, “def.000.”

In this scenario, this version of procedure “def.000” includes the modifications

present when it was last run against the MPT specimen, because these changes
were saved after the test was run. So in this case, the saved version of procedure
“def.000” is identical to the version saved in the mpp file. However, since MPT
cannot tell if additional changes have been made before it was saved, it displays
both options.

Procedure snapshot This is the default selection. MPT replaces the procedure currently in memory,
from last run “abc.000,” with procedure “def.000” as it was last run against the MPT
specimen.

MTS MultiPurpose TestWare® Working with MPT Specimens 151

Procedure Has Been Modified, Run Against the

This version of procedure “def.000” includes the modifications present when it

was last run against the MPT specimen. A copy of the modified procedure was
automatically saved to the mpp file when the test was last run.

The “modified” flag means MPT noted a difference between the version of the
procedure saved by the operator and the version MPT saved to the mpp file when
the test was run. In this case, even though the modified flag is present, both
versions are identical because the modified version was saved by the operator
after the test was run.

Restore procedure Since the MPT specimen was last run against the snapshot version of “def.000,”
state to you can choose the state to which it restores. In this case the saved state is Done,
so selecting the saved state brings the procedure back to its done state, which
include information such as counter values as they were when the test was
complete. Clicking Reset brings the procedure back to its starting point, with
counters set to zero.

The Saved state information is stored in the mps file. If the test had been
inadvertently interrupted and you wish to resume the test at (or close to) the point
of interruption, choose this selection.

152 Working with MPT Specimens MTS MultiPurpose TestWare®

Chapter 11
Creating a Practice Test Procedure
This section describes how to create a practice test procedure. Performing this
exercise familiarizes you with the MultiPurpose TestWare application
environment. By the time you are finished you should have a good sense of how
the various elements of a test procedure fit together.

It is good practice to set your control software to the simulation mode (using the
Demo System Loader) and follow along, using one of the default configuration
files included with your system or one that you have created yourself.

You may not be able to create the sample procedure precisely as instructed
because your system may be supplied with different hardware resources than
used to create the practise test procedure.

Even so, if you follow along and create a less complex version of the test
procedure, or even if you just review the pages without using your software, you
still benefit by learning the fundamentals of creating test procedures.

Note The hardware resources and label names provided in this section are for
illustration purposes only. Your hardware resources and label names
typically vary with the hwi file and station configuration file you use.

The following tasks are described in this section:

• “Plan Your Test” on page 154

• “Determine Which Processes Are Needed” on page 156

• “Add Processes to the Procedure Table” on page 161

• “Sequence Your Processes” on page 163

• “Set Process Parameters in the Procedure Table” on page 166

• “Set Process Parameters in the Group Table” on page 172

• “Select Procedure Options” on page 176

MTS MultiPurpose TestWare® Creating a Practice Test Procedure 153

Plan Your Test

Plan Your Test

To plan your test, you should:

• Identify test objectives and significant test information.

• Review the test environment.

The following sample test objectives are used throughout this section to show
how they affect the selection, triggering, and definition of individual processes in
the sample test.

1. Identify the test objectives.

For this sample test, we want to:

A. Ramp to 3000 N in force control.

B. Apply a sinusoidal force input of ±1000 N at 1 Hz, for 100 cycles to

fatigue the physical specimen.

C. Return to 0 N in force control.

During the test, we also want to:

A. Acquire peak/valley data while the physical specimen is being

fatigued.

B. Activate and deactivate an external fan to keep the physical specimen’s

temperature between 50–75ºC.

154 Creating a Practice Test Procedure MTS MultiPurpose TestWare®

 Plan Your Test

C. Monitor the physical specimen’s internal breakwire for continuity, and

stop the test if it severs, or if the detected error level indicates imminent
failure of the specimen.

The sample test

design as it may
be sketched out.

2. Review the test environment.

The test environment includes the physical specimen, test frame, and
sensors. Their dimensions and capacities are important considerations in the
test setup. The test environment for the sample test is as shown.

Test Frame

5 kN Load Cell
(force sensor)

+75 mm
extension
Specimen
100 mm
Calibrated
Midstroke 150 mm

Compression Platen -75 mm

retraction
Piston Rod
Actuator with 150 mm
Stroke and Internal LVDT
(displacement sensor)

MTS MultiPurpose TestWare® Creating a Practice Test Procedure 155

Determine Which Processes Are Needed

Determine Which Processes Are Needed

A process is a “mini-program” that performs a specific test activity. You use
processes like building blocks to construct a procedure.

To complete this task, you must determine which processes on the Process
Palette are needed to accomplish the test objectives.

1. Determine which processes are needed to ramp and fatigue the physical
specimen.

This test requires three command processes:

• A Segment Command process to ramp the applied force to the mean

level from which cyclic forces are applied.

• A Cyclic Command process to apply cyclic forces to the physical

specimen to fatigue it.

• A Segment Command process to return the applied force to zero.

2. Determine which processes are needed to acquire data.

This test requires a Peak/Valley Data Acquisition process

to acquire peak/valley data as the physical specimen is being fatigued.

3. Determine which processes are needed to monitor continuity.

This test requires a Digital Input Detector process to monitor the physical
specimen continuity using a breakwire.
Note In this example the Station Manager Error detectors, rather than an MPT
process, are used to monitor structural failure of the physical specimen.

156 Creating a Practice Test Procedure MTS MultiPurpose TestWare®

 Determine Which Processes Are Needed

How these processes The following illustrates Steps 1 - 3.

work

The Cyclic Command process cycles

the physical specimen to fatigue it.

The first Segment The second Segment

Command process Command process returns
applies a mean force to the applied force to zero.
the physical specimen.

Time
The Peak/Valley Data Acquisition
process acquires peak/valley data while
the physical specimen is being fatigued.

The Digital Input Detector process

detects if and when the breakwire
severs while the physical specimen is
being fatigued.

4. Determine which processes are needed to control the fan.

This test requires a Group process to provide the logic for switching the
cooling fan on-and-off. The Group process contains four individual
processes:

• A Data Limit Detector process to monitor the physical specimen’s

temperature and trigger the next process when the temperature reaches
75°C.

• A Digital Output process to turn the fan on to cool the physical

specimen.

• Another Data Limit Detector process to monitor the physical

specimen’s temperature and trigger the next process when the
temperature drops to 50°C.

• Another Digital Output process to turn the fan off. Finally, to create
continuous fan control during the test, we should specify that when the
fourth process in the group is done, the first process begins again.

MTS MultiPurpose TestWare® Creating a Practice Test Procedure 157

Determine Which Processes Are Needed

Example of a group The following illustrates Step 4.

process at work

The Group process holds the

individual processes used to control
the cooling fan.

1 2 3 4

On Off
75°
50°

1. The first Data Limit 2. The first Digital Output 3. The second Data 4. The second Digital
process detects when process sends out a Limit process Output process turns
the physical specimen’s pulse that turns the fan detects when the the fan off when the
temperature reaches on when the physical physical specimen’s physical specimen’s
75°C. specimen’s temperature temperature drops temperature drops to
reaches 75°C. to 50°C. 50°C, then the Group
process starts over
with the first Data Limit
process.

Put it all together All of the processes required to perform the activities in the sample test sketch
are shown below in the process diagram.

158 Creating a Practice Test Procedure MTS MultiPurpose TestWare®

 Determine Which Processes Are Needed

Note The process diagram below shows the procedure as a function of time
(from left to right), because it is easy to visualize that way. On the MPT
Procedure Editor you assign the order in which processes run by
assigning start and interrupt triggers to each process. Because of this,
the order of the processes on the MPT Procedure Editor, which are
arranged in a single column, may not determine the order in which they
run.

=
We converted the information in the sample test This diagram illustrates the sample test sketch in
sketch into the process diagram illustrated to the terms of MPT processes. This graphic is used in
right. the margins of the following sections to illustrate
adding and sequencing processes in the practice
test procedure.

Basic activities Once you have identified the processes needed for a test, you need to perform the
required to build a test following activities to build the practice test procedure:
procedure
• Add the necessary processes to the procedure table

• Sequence the processes with start and interrupt triggers

• Set the parameters of the individual processes

• Select test procedure options

The method used to The practice test procedure created in the following pages performs these basic
build the practice test activities from top-to-bottom. That is, you begin by adding processes to the
procedure procedure table, and finish by setting test procedure options.

MTS MultiPurpose TestWare® Creating a Practice Test Procedure 159

Determine Which Processes Are Needed

An alternate method— An alternative method for building test procedures involves separating the test
building and testing procedure into functional layers and adding, sequencing, and setting the
functional layers parameters for all of the processes within each layer before building the next
layer.

As an exercise, you could build the sample procedure this way.

For instance, rather than adding all the processes required for the test to the
procedure table, at first add only the command processes. This defines the
command layer of the procedure. Next, sequence and set the parameters for the
command processes, and run the procedure to ensure that the command layer is
functional.

Next, add the data acquisition layer to the command layer. To do this, add,
sequence, and set the parameters for the data acquisition process. Then run the
procedure to ensure that both layers are functional. You can check the data stored
in the MPT specimen (created when you run the test) to ensure that you are
getting the type of data you expect.

Finally, add, sequence, and set the parameters of the processes used to control the
cooling fan.

Note The advantage of building procedures in functional layers increases with

the complexity of the procedure. Using this method in reverse is also an
effective method for debugging procedures.

Station configuration The practice test procedure in this section requires a station configuration with
requirements for the resources that support the test objectives and specific MPT processes used.
practice test
procedure If you want to perform the practice test procedure on your workstation as shown
in this manual, you should create a station configuration before continuing on to
the next task.

To do this, use the Station Builder application to create a station configuration

with the following attributes:

• A control channel with force and displacement control modes

• An auxiliary data channel named “Temperature Monitor”

• A digital input channel named “Continuity Monitor”

• A digital output channel named “Fan Switch”

The practice test procedure uses these specific channel resources for setting
process parameters. For information about creating station configuration files,
see the 793 Control Software manual (PN 100-147-130).

160 Creating a Practice Test Procedure MTS MultiPurpose TestWare®

 Add Processes to the Procedure Table

Otherwise, you can still benefit by reading about how to create the practice test
procedure without performing the activities on your workstation.

Add Processes to the Procedure Table

To complete this task, perform the following:

• Select MultiPurpose TestWare and display the MPT Procedure Editor.

• Add processes to the procedure table.

• Add processes to the group table.

1. Access MultiPurpose TestWare.

A. Select the simulation mode by launching the Demo System Loader

application (Start > Programs > MTS 793 Software > Tools > Demo
System Loader).

B. Launch the Station Manager application.

C. Select MultiPurpose TestWare from the Applications menu.

D. Click the procedure table icon to display the procedure table and
Process Palette.

2. Add the first process to the procedure table.

This step adds the first

process to the procedure
table.

A. Drag the icon from the Process Palette to the procedure table.

B. Click the Segment Command process name in the procedure table and
rename it “Ramp to Mean”.

MTS MultiPurpose TestWare® Creating a Practice Test Procedure 161

Add Processes to the Procedure Table

3. Add the remaining processes to the procedure table.

This step adds the

remaining processes to the
procedure table.

A. Add a Cyclic Command process to the procedure table and name it

Fatigue Part.

B. Add a Segment Command process to the procedure table and name it

Return to Zero.

C. Add a Peak/Valley Acquisition process and name it Acquire Peak/

Valley Data.

D. Add a Digital Input Detector process and name it Monitor Continuity.

E. Add a Group process and name it Fan Control.

4. Add the necessary processes to the group process window.

This step adds processes

to the group table (to
control the fan).

A. Click the group process icon on the MPT procedure table.

B. Click on the MPT Procedure Editor toolbar. This is how you

display the group table associated with the group process icon.

C. Add a Data Limit Detector process to the Procedure/Fan Control

window and name it Trigger at 75C.

D. Add a Digital Output process and name it Switch Fan On.

162 Creating a Practice Test Procedure MTS MultiPurpose TestWare®

 Sequence Your Processes

E. Add a Data Limit Detector process and name it Trigger at 50C.

F. Add a Digital Output process and name it Switch Fan Off.

Sequence Your Processes

To complete this task, perform the following:

• Select Start and Interrupt triggers for each process on the procedure and
group table.

• Select a Procedure is done when trigger for the procedure table.

• Select a Group is done when trigger for the group table.

This task determines the sequence in which the processes run. With the exception
of the first process in the procedure, the default Start trigger for each process is
the done trigger generated by the previous process. The default Interrupt trigger
is blank.

Note There is a slight time delay between processes that start with a common
trigger signal (for example, two processes using the <Procedure > Start>
trigger signal). The process positioned the highest on the Procedure or
Group table starts first.

1. Specify Start triggers for each process in the procedure table.

This step changes the default

sequence of some of the
processes in the procedure.

A. If you are still in the Group table, click on the MPT toolbar to
return to the main procedure table.

MTS MultiPurpose TestWare® Creating a Practice Test Procedure 163

Sequence Your Processes

B. Observe that the Start trigger for the Ramp to Mean process is
<Procedure>.Start. This is the default start trigger, which causes this
process to start when the procedure starts.

C. Set the Start trigger for the Fatigue Part process to Ramp to
Mean.Done. This is the default.

D. Set the Start trigger for the Return to Zero process to Fatigue
Part.Done. This is the default.

E. Change the Start trigger for the Acquire Peak/Valley Data process to
Ramp to Mean.Done. This causes this process and the Fatigue Part
process to start almost simultaneously.

F. Change the Start trigger for the Monitor Continuity process to Ramp
to Mean.Done. This causes this process and the Fatigue Part process
start almost simultaneously.

G. Change the Start trigger for the Fan Control process to Ramp to
Mean.Done. This causes this process and the Fatigue Part process to
start almost simultaneously.

2. Specify the Interrupt triggers for processes in the procedure table.

A. Change the Interrupt trigger for the Fatigue Part process to Monitor
Continuity.Done. This ends the Fatigue Part process if the Monitor
Continuity process triggers due to a severed breakwire.

B. Change the Interrupt trigger for the Acquire Peak/Valley process to

Fatigue Part.Done. This ends the Acquire Peak/Valley Data process
when the Fatigue Part process finishes. In other words, data
acquisition stops when cycling stops.

C. Change the Interrupt trigger for the Fan Control process to Fatigue
Part.Done. This ends the Fan Control process when the Fatigue Part
process finishes.

164 Creating a Practice Test Procedure MTS MultiPurpose TestWare®

 Sequence Your Processes

3. Specify a “Procedure is done when” trigger.

Set the Procedure is done when trigger to Return to Zero.Done. This ends
the procedure when the Return to Zero process ends.

This is the Procedure is done

when control. When the trigger
we select for this control is
received, the procedure
terminates. In this case, we are
choosing the Return to
Zero.Done trigger.
This means the procedure
terminates when the Return to
Zero process generates a done
trigger.The procedure can
terminate prematurely if one of
the defined interrupts occur, that
is, if the Fatigue Part process
receives a done trigger from the
Monitor Continuity process.

4. Specify Start triggers for each process in the Group table.

A. Click the Group process icon on the procedure table.

B. Click on the MPT Procedure Editor toolbar.

C. Observe that the Start trigger for the Trigger at 75C process is
<Group>.Start. This causes this process to start when the Group
process starts.

D. Observe that the Start trigger for the Switch Fan On process is
Trigger at 75C.Done.

E. Observe that the Start trigger for the Trigger at 50C process is Switch
Fan On.Done.

F. Observe that the Start trigger for the Switch Fan Off process is
Trigger at 50C.Done.

5. Specify a “Group is done when” trigger.

Leave the Group is done when box blank. The Group process
automatically ends when all the processes within it ends.

MTS MultiPurpose TestWare® Creating a Practice Test Procedure 165

Set Process Parameters in the Procedure Table

Note This Group is done when trigger selection ends Group process activity,
but may leave the fan in a running condition at the end of test. There are
a number of ways to design the procedure to ensure that the fan stops
when the test stops, but to minimize complexity they are not included in
this example.

For more information For information on how to choose specific Start and Interrupt triggers for
individual processes, see “About Sequencing Processes” on page 87.

Set Process Parameters in the Procedure Table

To complete this task, make selections in the parameters pane for each process in
the Procedure and Group tables.

1. Define the first Segment Command process (Ramp to Mean).

Segment Command
(Ramp to Mean)

A. In the procedure table, click the Segment Command (Ramp to Mean)

process icon.

B. In the Segment Command parameters pane, click the Channels tab.

Move all the channels you want to generate the command on to the
Included list. Move all the others to the Available list.

C. Click the Command tab. Select and type the parameters needed by the
test, as follows:

• Segment Shape: Ramp for a Time of 3 Seconds.

• Channel: 10kN Actuator

• Control Mode: Force

• Absolute End Level: 3000 N.

D. Click the General tab and observe the default selections.

166 Creating a Practice Test Procedure MTS MultiPurpose TestWare®

 Set Process Parameters in the Procedure Table

2. Define the Cyclic Command (Fatigue Part) process.

Cyclic Command
(Fatigue Part)

A. In the procedure table, click the Cyclic Command (Fatigue Part)

process icon.

B. In the Cyclic Command parameters pane, click the Channels tab.

Move all the channels you want to generate the command on to the
Included list. Move all the others to the Available list.

C. Click the Command tab. Type and select the parameters needed for the
test, as shown:

• Segment Shape: True Sine, at a Frequency of 1.00 Hertz.

• Count (enabled): 100 Cycles

• Channel: 10kN Actuator

• Control Mode: Force

• Absolute End Level 1: 4000 N

• Absolute End Level 2: 2000 N

D. Click the General tab and type information as desired.

MTS MultiPurpose TestWare® Creating a Practice Test Procedure 167

Set Process Parameters in the Procedure Table

3. Define the second Segment Command process (Return to Zero).

Segment Command
(Return to Zero)

A. In the procedure table, click the Segment Command (Return to Zero)

process icon.

B. In the Segment Command parameters pane, click the Channels tab.

Move all the channels you want to generate the command on to the
Included list. Move all the others to the Available list.

C. Click the Command tab. Type and select the parameters needed for the
test, as follows:

• Segment Shape: Ramp, for a Time of 2 Seconds

• Channel: 10kN Actuator

• Control Mode: Force

• Absolute End Level: 0.0 N

D. Click the General tab and observe the default selections.

168 Creating a Practice Test Procedure MTS MultiPurpose TestWare®

 Set Process Parameters in the Procedure Table

4. Define the Peak/Valley Data Acquisition process (Acquire Peak/Valley).

Peak/Valley Acquisition
(Acquire Peak/Valley)

A. In the procedure table, click the Peak/Valley Acquisition (Acquire

Peak/Valley Data) process icon.

B. In the Peak/Valley Acquisition parameters pane, click the Signals tab.

Move all the signals you want to take data on to the Included list.
Typical selections for a test like this might include Time, 10kN
Actuator Force, and 10kN Actuator Displacement.

C. Click the Acquisition tab. Type and select the parameters needed for
the test, as follows:

• Master Signal: 10kN Actuator Displacement

• Sensitivity: 3.0 mm

D. Click the Destination tab. Type and select the parameters needed for
the test, as follows:

• Buffer Size: 16000

• Data Header: Doc Data

• Destination: Specimen

• Buffer Type: Circular

E. Observe the default settings for the Output Units and General tabs.

MTS MultiPurpose TestWare® Creating a Practice Test Procedure 169

Set Process Parameters in the Procedure Table

5. Define the Digital Input process (Monitor Continuity).

Digital Input Detector

(Monitor Continuity)

A. In the procedure table, click the Digital Input Detector (Monitor

Continuity) process icon.

B. In the Digital Input Detector parameters pane, click the Inputs tab.
This process monitors the digital input channel (Continuity Monitor).

C. Move the Continuity Monitor to the Included list and ensure that all
other resources are in the Available list.

D. Click the Input Table tab. For the Digital Input labeled Continuity
Monitor, select the High/Low Option.

E. Click the Settings tab. Type and select the parameters needed for the
test, as follows:

• Trigger Mode: Trigger Once

• Process triggers when: Any selected input detects its specific event

• Log Message As: Information.

F. Observe the default settings on the General tab.

170 Creating a Practice Test Procedure MTS MultiPurpose TestWare®

 Set Process Parameters in the Procedure Table

6. Define the Group (Fan Control) process.

Group
(Fan Control)

A. In the MPT Procedure Editor, click the Group (Fan Control) process
icon.

B. Click the General tab. Instead of using the default settings, type and
select the parameters needed for the test, as follows:

• Name: Fan Control

• Process Enabled (enabled)

• Execute Process: 1000000 Times

• Counter Type: Fixed

• Counter Label: Cooling Cycles

Note By default, a Group process executes once. It completes when all of the
processes in the group are done. By typing a large number in the
Execute Process box, we are essentially instructing this Group process
to loop continuously.

For more information For information on the parameter window controls, see “Segment Command
Parameter Descriptions” on page 182, “Cyclic Command Parameter
Descriptions” on page 191 “Peak/Valley Acquisition Parameter Descriptions” on
page 280, and “Digital Input Detector Parameter Descriptions” on page 354.

MTS MultiPurpose TestWare® Creating a Practice Test Procedure 171

Set Process Parameters in the Group Table

Set Process Parameters in the Group Table

1. Display the procedure table that pertains to the group process.

A. Click the Group process icon on the MPT procedure table.

B. Click on the MPT Procedure Editor toolbar.

2. Define the Data Limit Detector process (Trigger at 75C).

Data Limit Detect

(Trigger at 75C)

A. In the group table, click the Data Limit Detector (Trigger at 75C)
process icon.

B. Click the Signals tab. Move the Temperature Monitor to the Included
list and ensure that all other signals are in the Available list.

C. Click the Limits tab. Type and select the parameters needed for the
test, as follows:

• Signal: Temperature Monitor

• Upper Limit (enabled): 75.0 degrees C.

• Lower Limit (disabled)

D. Observe the default settings on the Settings, Limit Table, and General
tabs.

172 Creating a Practice Test Procedure MTS MultiPurpose TestWare®

 Set Process Parameters in the Group Table

3. Define the Digital Output (Switch Fan On) process.

Digital Output
(Switch Fan On)

A. In the group table, click the Digital Output (Switch Fan On) process
icon.

B. Click the Outputs tab and move the Fan Switch resource to the
Included list.

C. Click the Output Table tab. In our sample test scenario, the cooling
fan power supply is controlled by a microswitch. This microswitch
applies 110 V to the fan when it is set high, and removes 110 V from
the fan when it is set low (or cleared). So for this process, the
appropriate setting is Set, which means set high.

D. Use the default settings on the Settings and the General tab.

MTS MultiPurpose TestWare® Creating a Practice Test Procedure 173

Set Process Parameters in the Group Table

4. Define the second Data Limit Detector process (Trigger at 50C).

Data Limit Detector

(Trigger at 50C)

A. In the group table, click the Data Limit Detector (Trigger at 50C)
process icon.

B. Click the Signals tab and move the Temperature Monitor resource to
the Included list, as shown below.

C. Click the Limits tab. Type and select the parameters needed for the
test, as follows:

• Signals: Temperature Monitor.

• Upper Limit (enabled): 50 degrees C.

• Lower Limit (disabled)

D. Observe the default settings on the Settings, Limit Tables, and

General tab.

174 Creating a Practice Test Procedure MTS MultiPurpose TestWare®

 Set Process Parameters in the Group Table

5. Define the second Digital Output process (Switch Fan Off).

Digital Output
(Switch Fan Off)

A. In the group table, click the Digital Output (Switch Fan Off) process
icon.

B. Click the Outputs tab. Move the Fan Switch resource to the Included
list.

C. Click the Output Table tab. In our test, the cooling fan power supply is
controlled by a microswitch. This microswitch applies 110 V to the fan
when it is set high, and removes 110 V from the fan when it is set low
(or cleared). So for this process, the appropriate setting is Clear, which
turns off the fan.

D. Use the default settings on the Settings and General tabs.

6. Close the Group table and return to the main MPT Procedure Editor.

MTS MultiPurpose TestWare® Creating a Practice Test Procedure 175

Select Procedure Options

Select Procedure Options

You can use the MPT Options Editor to set MPT preferences. The settings are
saved with the procedure.

For our test, we need to specify the following application preferences:

• The counter display on the MPT control panel

• The hydraulic state required to run tests

• The file format for data files generated by the MPT application

• A description of the procedure

1. On the MPT toolbar, select the Options Editor icon.

2. Specify how the you want the counters to appear on the MPT control panel.

A. Click the Control Panel tab.

B. In the Counters box, click Sequence Counters and Channel

Counters.

C. In the Display Format box, click Cycles.

3. Specify the Hydraulic State required to run the test.

A. Click the Execution tab.

B. In the Required Power list, select Off.

Note Since this program is for simulated testing, click Off. This way, you can
only run the test when hydraulic pressure is disabled.

4. Set the file format for MPT data files.

Click the Specimen tab. Complete the tab as follows:

• Data File Mode: Append

• Data File Format: Excel

• Data File Time Stamp: Time

• Specimen Log: Append

• Clear Counters on Reset (enabled)

5. Type a description of the procedure.

A. Click the Properties tab.

176 Creating a Practice Test Procedure MTS MultiPurpose TestWare®

 Select Procedure Options

B. Type text as desired in the Description box to describe the procedure.

6. If desired, run the procedure in the simulation mode.

As stated at the beginning of the exercise, the benefit of creating this sample
procedure was to gain familiarity with the MultiPurpose TestWare
application environment. If you desire, you can run your procedure in the
simulation mode to gain experience with executing procedures.
Note To run your sample test procedure, select Demo System Loader before
you launch Station Manager to ensure that your system is in the
simulation mode (Start > Programs > 793 System Software > Tools >
Demo System Loader).

For more information See “How to Create a New Procedure” on page 44.

MTS MultiPurpose TestWare® Creating a Practice Test Procedure 177

Select Procedure Options

178 Creating a Practice Test Procedure MTS MultiPurpose TestWare®

Chapter 12
Command Processes

Command Process Types

ICON PROCESS NAME DESCRIPTION
Segment Command Produces a monotonic command signal.
Process

Cyclic Command Process Produces a cyclic command signal.

Dwell Command Process Produces a dwell command signal.

Profile Process Produces a command signal based on the contents of a “profile”

created with a text editor or the Profile Editor application.
External Command Enables a command signal from an external program source.
Process

Sweep Command Process Produces a command signal that sweeps between two frequency
values.
Signal Based Command Allows you to generate command based on signal values specified in
Process a predefined lookup table. The lookup table is contained in a tab-
delimited text file which defines the relationship between command
and signal values.
Profile with ALC Process * Produces an ALC compensated command signal based on the
contents of a “profile” created with a text editor or the Profile Editor
application.
Cyclic with ALC Process * Produces an ALC compensated cyclic command signal.

Model 793.71/72 Time Produces a command signal based on an MTS RPC II or RPC III time
History Output Process * history file. This process can also perform time history data
acquisition synchronized with the command.
Road Surface Output Produces a command signal that controls multiple station channels
Process * with an MTS RPC II, RPC III, or RPC Pro Road Surface file.
*Process not included with all systems.

MTS MultiPurpose TestWare® Command Processes 179

 Note If a command process includes both normal (high-rate) and low rate
channels, the channels will start and stop together. However, they may
not stop at the same level. They may be off in phase as much as one
low-rate tick.

180 Command Processes MTS MultiPurpose TestWare®

 Segment Command Process

Segment Command Process

About the Segment Command Process
The Segment Command process defines a monotonic function that begins at the
current level and moves to the end level you specify.

Note This process supports relative end levels and absolute end levels.

End level

Start level
Frequency,
Time, or Rate

MTS MultiPurpose TestWare® Command Processes 181

Segment Command Process

Segment Command Parameter Descriptions

Command tab
Command Tab (part 1 of 2)
ITEM DESCRIPTION
Segment Shape Specifies the segment shape.
Time/Frequency/Rate Specifies how fast the segment runs.
The following methods are supported:
• Time specifies the time to run one segment.

• Frequency specifies the time to run a two-segment cycle (even though a

single segment runs).

• Rate specifies a constant rate between the starting level and the end level.
Rate is typically used with a ramp segment.
Note You cannot use Rate for a command process applied to multiple
channels. If you do, an error message will appear when the procedure
is locked.

Adaptive Enables command compensation during the command process. The Adaptive
Compensators Compensators list includes all compensators available on at least one channel
selected in the Channels tab. It is important to know which compensator is
available for each channel in your station configuration because when this
process is run, compensation will occur only on the channels for which it was
enabled.

Note A special annotation appears if the compensator is not available on all

channels. For example, “AIC (1 of 3)” implies that the AIC
compensator is only supported on one of the three included channels.

Important The use of the AICX compensator can introduce large delays
between generated command and command to the actuator.
The delay is dependant on the tuning of AICX and is two times
the value of the Impulse Response.

Do Not Update Disables the counters. When enabled, the Channel Counters do not increment
Counters for this process and the counter totals are unaffected.
Relative End Level Makes the end level relative.
Channel Specifies the channel.

182 Command Processes MTS MultiPurpose TestWare®

 Segment Command Process

Command Tab (part 2 of 2)

ITEM DESCRIPTION
Control Mode Specifies the control mode or control-mode variable.
Absolute End Level/ Defines the segment end level:
Relative End Level
• Absolute End Level is relative to setpoint.

• Relative End Level is relative to the starting command value (the value
when the process begins).

Channels tab Displays the channels available to this process. Use the arrow keys to move
desired channels from the Available list to the Included list.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information See “Segment Shapes” on page 188.

MTS MultiPurpose TestWare® Command Processes 183

Segment Command Process

How to Define a Segment Command Process

1. Drag the icon from the Process Palette to your group or procedure
table.

2. Click the process icon in your procedure table or in the navigation pane.

3. Click the Channels tab.

4. Move the channels that you want to use to generate the command onto the
Included list. Move all other channels to the Available list.

5. Click the Command tab.

6. In the Segment Shape list, click the segment shape.

7. Select the Time, Rate, or Frequency dimension; set the units of

measurement; and then type a value.

8. Optional—In the Adaptive Compensators list, click a compensator.

9. Optional—If you do not want channel counters to increment when this

process runs, click Do Not Update Counters.

10. Optional—If you want to define a relative end level, select the Relative
End Levels check box.

11. In the Channel list, click your desired channel.

12. In the Control Mode list, click the desired control mode or right-click to
assign a control-mode variable.

13. In the End Level box, set the units of measurement, and then type an end
level value.

14. Repeat steps 11 - 13 for each channel you want to command with this
segment process.

15. Click the General tab.

16. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

17. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

18. In the Execute Process box, type the number of times you want the process
to run.

19. Optional—In the Counter Type list, click a counter type.

184 Command Processes MTS MultiPurpose TestWare®

 Segment Command Process

20. Optional—If you enabled a counter, type a Counter Label.

21. Set the desired Start and Interrupt triggers for the process in the procedure
table.

MTS MultiPurpose TestWare® Command Processes 185

Cyclic Command Process

Cyclic Command Process

About the Cyclic Command Process
The Cyclic Command process defines a cyclic command by assembling two
single segments and repeating them continuously for a specified number of
cycles.

When a cyclic command starts, it always moves first to End Level 1, and then to
End Level 2.

Sine, ramp, and square Sine, ramp, and square commands use the first segment of the cyclic command to
start levels bridge any difference between the current level and the cyclic command End
Level 1 that you specify. This transition segment is counted as the first segment

CAUTION

A high-speed transition segment can result in an unwanted spike (or bump)

in your command signal.

Unwanted command-signal spikes can damage the physical test specimen.

To avoid spikes in the command signal, use a segment command process to

bridge processes where end levels and start levels differ greatly. If a process end
level is not near the start level of your cyclic command process, the process uses
the first segment to move all the way from the current level to the start level at the
transition speed that you specify.

True sine start levels True sine commands start at the mean level, which is the midpoint between the
End Level 1 and End Level 2 you specify. The system begins a true sine cyclic
process by stepping from the current level to the mean level. (This step does not
count as a segment.)

Once at the mean, the command travels through End Level 1 at the specified
rate. When using a true sine command, you should design your procedure so that
the system is at or very near its mean level before the true sine process begins.
You can include a segment command process that ramps from the current level to
the mean level. If you do not, your system may experience a step (or jolt)
between processes. The more difference there is between the current level and
the true sine command’s mean level, the greater the step.

186 Command Processes MTS MultiPurpose TestWare®

 Cyclic Command Process

Cycles and segments You can repeat cycles or segments. Two segments create one cycle. Repeating a
full cycle first goes to End Level 1 and ends at End Level 2. Repeating a
segment can end at End Level 1 or End Level 2 (depending on whether the
count value is odd or even).

The conventional way to

End level Frequency = 5Hz
define the duration of a
cyclic command is by
frequency or time. Start level

Time = 0.1second

End level 2 = 5 kip

Rate = 5 kip/1 second

End level 1 = 0 kip

Repeating Cycles and Segments

Note The end levels selected in processes such as Segment Command or

Cyclic Command can be set to values greater than the full scale preset in
Station Manager. The command will attempt to reach the specified end
level; however, the feedback will become saturated before reaching the
specified end level and will cause a hydraulic interlock.

End levels The two end levels specify the amplitude of the cyclic waveform. When two test
command processes with different end levels are sequenced, the transition
between them is accomplished at the rate and segment shape of the following
process. This provides a smooth transition between test commands.

MTS MultiPurpose TestWare® Command Processes 187

Cyclic Command Process

Example Assume a cyclic command completes its process at End Level 2 (in this case, +2
cm). The next Cyclic Command process is defined as End Level 1 = –1 cm and
End Level 2 = +1 cm. The transition segment bridges the two commands from
the +2 cm level to the –1 cm level at the time, rate, or frequency of the second
process.

Segment Shapes
Each of the following examples uses the following parameters: Frequency (Hz)
1, Count (segments) 6, Level 1 (mm) 2, Level 2 (mm) 4, with a starting level of
0.0.

Square
L2 4.0000

L1 2.0000

0.0000
0.3000 0.9000 1.5000 2.1000 2.7000 3.3000
Time (sec)

Ramp
L2 4.0000

L1 2.0000

0.0000
0.3000 0.9000 1.5000 2.1000 2.7000 3.3000
Time (sec)

Sine
L2 4.0000

L1 2.0000

0.0000 0.3000 0.9000 1.5000 2.1000 2.7000 3.3000

Time (sec)

188 Command Processes MTS MultiPurpose TestWare®

 Cyclic Command Process

Tapered wave shapes You specify the beginning and ending taper times on the Command Options tab
in the Station Manager’s Channel Options window before you run the profile.

The Begin time formats the leading edge and the End time formats the trailing
edge.

Square tapered This square wave tapers from 0% to 100% amplitude at the beginning of its
execution, and from 100% to 0% at the ending of its execution.

L1 4.0000

2.0000

L2 0.0000
2.0000 4.0000
Time (sec)

Ramp tapered This ramp wave tapers from 0% to 100% amplitude at the beginning of its
execution, and from 100% to 0% at the ending of its execution.

L1 4.0000

2.0000

L2 0.0000
2.0000 4.0000
Time (sec)

Sine tapered This sine wave tapers from 0% to 100% amplitude at the beginning of its
execution, and from 100% to 0% at the ending of its execution.

L1 4.0000

2.0000

L2 0.0000
2.0000 4.0000
Time (sec)

MTS MultiPurpose TestWare® Command Processes 189

Cyclic Command Process

True sine tapered This true sine wave tapers from 0% to 100% amplitude at the beginning of its
execution, and from 100% to 0% at the ending of its execution.

L1 4.0000

2.0000

L2 0.0000 2.0000 4.0000

Time (sec)

190 Command Processes MTS MultiPurpose TestWare®

 Cyclic Command Process

Cyclic Command Parameter Descriptions

Command tab
Command Tab (part 1 of 2)
ITEM DESCRIPTION
Segment Shape Specifies the segment shape.
Time, Frequency, Rate Specifies how fast each segment runs.
The following methods are supported:
• Time specifies the time to run one segment.

• Frequency specifies the time to run a two-segment cycle.

• Rate specifies a constant rate between the starting level and the end
levels.
Note You cannot use Rate for a command process applied to multiple
channels. If you do, an error message will appear when the procedure
is locked.

Note The rate of the first segment can be faster than the other segments if it
must transition from a distant end level.

Count Specifies how many times the waveform will be repeated.

Note If you clear the Count box, the waveform will repeat continuously.

Adaptive Enables command compensation during the command process.

Compensators
Important The use of the AICX compensator can introduce large delays
between generated command and command to the actuator.
The delay is dependant on the tuning of AICX and is two times
the value of the Impulse Response.

Do Not Update Disables the counters. When enabled, the Channel Counters do not increment
Counters for this process and the counter totals are unaffected.
Relative End Levels Defines the segment end level:
• Absolute End Level is relative to setpoint.

• Relative End Level is relative to the starting command value (the value
when the process begins).
Channel Specifies the channel.
Control Mode Specifies the control mode or control-mode variable.

MTS MultiPurpose TestWare® Command Processes 191

Cyclic Command Process

Command Tab (part 2 of 2)

ITEM DESCRIPTION
Absolute End Level 1/ Defines the end level value for the first segment.
Relative End Level 1

Absolute End Level 2/ Defines the end level value for the second segment.
Relative End Level 2

Phase Lag Specifies the phase relationship of the waveform generated by this process
from channel to channel. Phase Lag is disabled if Rate is specified for the
process.
Note Phase Lag is relative to the channel that has the smallest degree of
phase. The Phase Lag of each channel is referenced to the lowest
Phase Lag defined in the channels.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

Channels tab Displays the channels available to this process. Use the arrow keys to move
desired channels from the Available list to the Included list.

For more information See “Segment Shapes” on page 188.

192 Command Processes MTS MultiPurpose TestWare®

 Cyclic Command Process

How to Define a Cyclic Command Process

1. Drag the icon from the Process Palette to your group or procedure
table.

2. Click the process icon in your group or procedure table, or in the navigation
pane.

3. Click the Channels tab.

4. Move all the channels you want to generate the command on to the
Included list. Move all the others to the Available list.

5. Click the Command tab.

6. In the Segment Shape list, click the segment shape.

7. Select Time, Rate, or Frequency, set the units of measurement, and then
type a value.

8. Select the Count check box. Set the units (cycles or segments), and then
type the number of times the cyclic command is to repeat. For continuous
cycling, clear the Count check box.
Note The Execute Process value multiplies the Count in the Command
parameters. If the Execute Process parameter is set to 10 and the
Command Count is set to 5, a total of 50 cycles will occur.

9. Optional—In the Adaptive Compensators list, click a compensator.

10. Optional—If you do not want channel counters to increment when this
process runs, click Do Not Update Counters.

11. Optional—If you want to define a relative end level, select the Relative
End Levels check box.

12. In the Channel list, click your desired channel.

13. In the Control Mode list, click the desired control mode or right-click to
assign a control-mode variable.

14. Set the units of measurement for the end levels, then type values for End
Level 1 and End Level 2.

15. Optional—In the Phase Lag box, type a value.

16. Repeat steps 12 through 15 for each channel you want to command with this
process.

MTS MultiPurpose TestWare® Command Processes 193

Cyclic Command Process

17. Click the General tab.

18. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

19. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

20. In the Execute Process box, type number of times you want the process to
run.

21. Optional—In the Counter Type list, click a counter type.

22. Optional—If you enabled a counter, type a Counter Label.

23. Set the desired Start and Interrupt signals for the process in the group or
procedure table.

194 Command Processes MTS MultiPurpose TestWare®

 Dwell Command Process

Dwell Command Process

About the Dwell Command Process
The Dwell Command process is a single segment designed to hold your
command at a static level for a specified amount of time.

When you define a Dwell Command process you must specify the duration of
the command as a time or a frequency:

• Time specifies the amount of time to run the single dwell command
segment.

• Frequency specifies the frequency of a command cycle (two-segments).

Since a dwell command is a single segment, the actual dwell command hold
time is half of the frequency setting. (For example, a frequency setting of 2
Hz holds the command for 0.25 seconds.)

Dwell Command Parameter Descriptions

Command tab
Command Tab
ITEM DESCRIPTION
Time/Frequency Specifies how fast the segment runs. Options are:
• Time—specifies the time to run one segment.

• Frequency—specifies the time to run a two-segment cycle.

Do Not Update Disables the counters. When enabled, the Channel Counters do not increment
Counters for this process and the counter totals are unaffected.
Channel Specifies the channel.
Control Mode Specifies the control mode or control-mode variable.

MTS MultiPurpose TestWare® Command Processes 195

Dwell Command Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

Channels tab Displays the channels available to this process. Use the arrow keys to move
desired channels from the Available list to the Included list.

196 Command Processes MTS MultiPurpose TestWare®

 Dwell Command Process

How to Define a Dwell Command Process

1. Drag the icon from the Process Palette to your group or procedure
table.

2. Click the process icon in your group or procedure table, or in the navigation
pane.

3. Click the Channels tab.

4. Move the channels that you want to use to generate the command onto the
Included list. Move all the others to the Available list.

5. Click the Command tab.

6. Select Time or Frequency, set the units of measurement, then type a value.

7. Optional—If you do not want channel counters to increment when this

process runs, click Do Not Update Counters.

8. In the Channel list, click your desired channel.

9. In the Control Mode list, click the desired control mode or right-click to
assign a control-mode variable.

10. Repeat steps 8 and 9 for each channel you wish to control.

11. Click the General tab.

12. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

13. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

14. In the Execute Process box, type the number of times you want the process
to run.

15. Optional—In the Counter Type list, click a counter type.

16. Optional—If you enabled a counter, type a Counter Label.

17. Set the desired Start and Interrupt signals for the process in the group or
procedure table.

MTS MultiPurpose TestWare® Command Processes 197

Profile Process

Profile Process
About the Profile Process
The Profile process generates a command based on a profile file (or just profile
for short) created with a text editor, spreadsheet application, or the MTS Profile
Editor application. The MPT application supports Block-Arbitrary and Phase
profile formats.

A profile is basically a spreadsheet that defines a particular command segment

(or a series of segments) in each row. As the controller plays out the profile, it
starts by playing the segment or cycle defined in the first row, then the second
row, then the third row, and so forth.

Note A single profile often contains the command content of an entire

procedure.

When you create a profile, you must define the segment shape, end levels values,
time between end levels, and count for the command in each row.

User-defined actions The profile process supports counters and user-defined actions. Counters appear
and counter names on the MPT control panel when the process is running and are incremented after
the corresponding row in the profile has played out.

User-defined actions defined with the Station Manager application are triggered
after the corresponding row in the profile has played out.

Counters and actions are specified on specific rows (with specific syntax) in
profiles.

Special consideration While running a procedure containing a phase profile, if you stop and unlock the
when running phase procedure, the resulting cycle counts on the dependent channels may not be exact
type profiles when you resume the procedure. The profile process determines where to restart
based on the master channel. If the other channels are on a different segment
because of phase differences, the Channel Counters on the MPT control panel
will be different by that amount.

198 Command Processes MTS MultiPurpose TestWare®

 Profile Process

About Working with Dimensions

When you use the Profile Editor application to assign dimensions (force,
displacement, and so forth) to the end levels in a profile, you should be aware
that they must map to the dimensions of the control modes included in the station
configuration on which you wish to play out the profile.

Because of this, it is good practice to be aware of all of the instances in which

dimension selections affect your ability to play out profiles, such as:

• You use the Profile Editor application to create command files (profiles) by
typing the end-level values you desire the actuator to achieve during the
course of the profile. To make end-level values meaningful, you must
specify dimension and unit types (for example, displacement and
centimeters).

• You use the MPT application to play out profiles you create with the Profile
Editor application. When you open the MPT application against a station
configuration, it inherits the resources of the station, which include the
control mode dimensions selected for the control modes in the station, as
defined with the Station Builder application.

• You use the MPT Profile Command process to import profiles, and to map
the logical channels in your profile (referred to as profile channels) to the
physical channels in your station configuration.
Note The MPT application does not require the names of profile channels to
be the same as the names of station channels. You can arbitrarily map
any profile channel to any station channel. You can also map one profile
channel to multiple station channels.

• You also use the Profile Command process to select the control mode of a
profile channel. For this to work (if the dimension used to define the end
levels of the profile is a standard engineering dimension, such as force or
length), the dimension must match one of the control mode dimensions
available to the current station configuration.

Example Suppose you use the Station Builder application to create a station configuration
with one channel that uses the force dimension for a force control mode, and the
length dimension for a displacement control mode.

In addition, you use the Profile Editor application to create a profile in which you
select the length dimension to define end levels for a channel you named
Channel 1.

To play out the profile file you created, open the Station Manager application and
select a configuration file containing the appropriate resources for your test.

MTS MultiPurpose TestWare® Command Processes 199

Profile Process

Next, select the Multipurpose TestWare application, then open the MPT
Procedure Editor (it will appear with a blank procedure table displayed). You can
create a new test procedure or open an existing procedure. The procedure must
contain the Profile Command process. Once the procedure is loaded, you then
select the profile file you created. This is done by double clicking the Profile
Command processes icon on the procedure table. The Profile Command
Parameters window will appear.

On the Command tab, click the Profile Path/File button and select the desired
profile file. An error message may appear to tell you the channel has not been
mapped. Click OK, and then click the Mapping tab.

On the Profile Channel pull down menu, select the desired channel and
complete the remaining fields. Complete the remaining tabs on the Profile
Command Parameters window. Finally, using the run button on the station
controls panel, run the profile.

About Using Normalized Dimensions

If you create a profile using a normalized dimension, such as ratio, percentage,
unitless, or volts, you can select any of the control modes available to the station
configuration when selecting the control mode for the profile channel.

When you do this, you define the full-scale value of the normalized dimension by
selecting one of the control modes and its associated engineering dimension
available in the Control Mode list on the Mapping tab, along with a unit type
and a Level Multiplier value. MPT converts all end level values in the profile to
command levels accordingly.

Example Suppose you create a station configuration that uses the force dimension for a
force control mode, and the length dimension for a displacement control mode. In
addition, suppose you create a profile in which you select the volts dimension to
define end levels.

Next, you start MPT against the station configuration, and with the Profile
process, on the Command tab, you select the profile you have created. On the
Mapping tab, you select a Profile Channel. In this scenario, both displacement
and force will be available in the Control Mode list.

Suppose you select displacement, and type a value of 5 cm in the Level

Multiplier box. This will cause all of the end level values in the profile to be
converted to displacement values. For volts, the full-scale value equals 10 volts,
which MPT will play out as 5 cm. So in this case, if the first end level values in
the profile are 2 volts and 9 volts, they will be played out as 1 cm and 4.5 cm.

200 Command Processes MTS MultiPurpose TestWare®

 Profile Process

Using the same profile, suppose you change the Control Mode selection to
force, and type a Level Multiplier value of 100 N. This will cause all of the end
levels in the profile to be converted to force values. In this case, MPT will play
out 10 volts as 100 N. So if the first end level values in the profile are 2 volts and
9 volts, they will be played out as 20 N and 90 N.

Full-scale values of
normalized dimensions DIMENSION FULL-SCALE VALUE

Ratio 1:1

Percentage 100%

Unitless 1.0

Volts 10V

Using normalized You can use any of these normalized dimensions to define a control mode in a
dimensions to define station configuration. If you do this, and then attempt to play out a profile that
control modes also uses a normalized dimension, MPT will treat it as a standard dimension
when you define a Profile process.

Example Suppose you create a station configuration that uses volts as a dimension for a
volt control mode, which is associated with a conditioner that is cabled to a
displacement sensor with a full-scale displacement of ±200 cm.

Next, you create a profile in which you select the volts dimension to define end
levels.

Then you start MPT against the station configuration, and with the Profile
process, on the Command tab, you select the profile you have created.

On the Mapping tab, you select a Profile Channel, and note that volts is
available in the Control Mode list, and that the Level Multiplier box displays
100%.

In this scenario, if the first end level values in the profile are 1 V and 9 V, they
will be played out as 20 cm and 180 cm. If you change the Level Multiplier
value to 50%, MPT would play out these values as 10 cm and 90 cm.

For more information For additional information on profiles in general and syntax requirements for
profiles, see “General Profile Syntax Requirements” on page 496.

For information on creating profiles with the Profile Editor application, see
Chapter 18, “Model 793.11 Profile Editor”

MTS MultiPurpose TestWare® Command Processes 201

Profile Process

Profile Command Parameter Descriptions

Command tab
Command Tab
ITEM DESCRIPTION
Profile Path/File Specifies the profile file to be used. You may type a placeholder and file name,
or type a full path. You may also use the browser.
Total Passes Specifies how many times the profile will be played out.
Note If you clear the Total Passes box, the waveform will repeat indefinitely.

Frequency Multiplier Scales the segment rate type (time/rate/frequency) specified in the profile. If
set to 100%, the profile will play out as defined in the profile. If set to 50%, the
profile will play out at half speed. If it is set to 200%, the profile will play out
at twice the speed.
Adaptive Enables command compensation during the command process.
Compensators
Note To use the ALC compensator with your profile, you must define a
Profile with ALC Process instead.

Important The PVC compensator resets after the process plays out each
row of the profile, which may cause a lag in in compensation.

Important The use of the AICX compensator can introduce large delays
between generated command and command to the actuator.
The delay is dependant on the tuning of AICX and is two times
the value of the Impulse Response.

If your system is equipped with the manual compensation feature, a Manual

selection will also be available in the list.

Note Manual compensation will be available only if the “Manual

Compensation (MPT Profile Process)” feature is enabled during
installation.

About selecting Profile, Profile with ALC, Time History, and Road Surface processes all
referenced files reference external program files. Profile and Profile with ALC processes
reference profile (.blk) files. Road Surface and Time History processes reference
either drive (.drv) or sequence (.seq) files.

202 Command Processes MTS MultiPurpose TestWare®

 Profile Process

When defining these processes, you must specify the desired external program
file in the process’ Command tab. To do this you may:

• Use the browser to locate the file

• Type a placeholder and file name, or

• Type a full path

About placeholders The placeholder for profile, time history, and road surface files is “<Profile
Files>”. By default, the placeholder “<Profile Files>” specifies the path: C:\MTS
793\Projects\current Project\Profiles.

This means typing ”<Profile Files>\Profile1.blk”

is the same as typing the full path
“C:\MTS 793\Projects\current Project\Profiles\Profile1.blk”.

In fact, if you type a full path and MultiPurpose TestWare recognizes that part of
the path matches the current specification of a placeholder, it will substitute the
placeholder.

Likewise, if you use the browser to locate a file that has a path that matches the
current specification of a placeholder, the placeholder will appear in the
browser’s entry field.
Note In addition to the <Profile Files>, there are also <Project>, <Controller>,
and <System> placeholders. For more information about the information
associated with these placeholders, see “Installed 793 Files” in the 793
Controller Overview manual (PN 100-162-928).

Saving procedures that When you save a procedure that includes a placeholder, the placeholder is
include placeholders archived in the procedure file. When you reload the procedure (even if on a
different controller), the archived placeholder is reinterpreted based on the
current placeholder’s specification.

Editing placeholder Placeholders are specified in the Project Settings file of the current Project. You
specifications can edit placeholder specifications with the Project Manager application.

For instance, the default specification for the <Profile Files> placeholder is
C:\MTS 793\Projects\current Project\Profiles. If you want to store your profiles
in the D drive, you can change the <Profile Files> specification to D:\MTS
793\Projects\current Project\Profiles.

To edit the <Profile Files> placeholder specification, start the Project Manager
application and go to Tools > Project Settings > MultiPurpose TestWare > Profile
Folder.

MTS MultiPurpose TestWare® Command Processes 203

Profile Process

For more information about editing Project Settings files, see the MTS 793
Control Software manual (PN 100-147-130).

Compatibility between In MTS 793 software version 3.5x and earlier, the default location of profile, time
version 4.0 and earlier history, and road surface files is: C:\MTS software product name\profiles.
versions In MTS 793 software version 4.0 or later, the default location of these types of
files is: C:\MTS 793\Projects\Project name\Profiles

By default, when you upgrade to version 4.0 from an earlier version, your
existing profile, time history, and road surface files are moved to a Project, along
with a reference to their original file locations.

When MultiPurpose TestWare loads a procedure that was saved in an earlier

version, it looks for path names that reference the original location, and then
changes them to reference the new location.

204 Command Processes MTS MultiPurpose TestWare®

 Profile Process

Mapping tab
Mapping Tab
ITEM DESCRIPTION
Channel Displays all station control channels.
Profile Channel Selects the profile channel that will be played out on this station channel.
You must map the logical channels in your profile to the control channels in
your station configuration. You can arbitrarily map any profile channel to any
station channel, or you can map a single profile channel to multiple station
channels. If you leave any station channel unmapped, no profile will be played
out on that channel.
If you gave the profile channels the same name(s) as the station channels, they
will automatically be mapped to the station channel with the matching name. A
profile channel will appear in the Profile Channel list box next to its
corresponding (station) Channel.
Each Profile Channel list box will contain all the profile channels with units
that can be played out by any control mode for the station channel. For
example, a profile channel that measures length will not map to a station
channel with a temperature control mode.
If the profile was created with normalized dimensions then you can select any
of the control modes available to the station channel when defining the control
mode of the profile channel.
Control Mode Specifies the control mode for the selected station channel.
Level Reference Introduces a mean level offset to the selected station channel.
Level Multiplier Scales the end level values of the profile. The Level Multiplier will function
for both engineering units and “normalized units.”
Note For normalized units, the Profile Command process uses the Level
Multiplier value as the full scale.

MTS MultiPurpose TestWare® Command Processes 205

Profile Process

Actions tab
Action Tab
ITEM DESCRIPTION
Name Displays the name of the action in the profile.
Action Displays the action, as defined by the Station Manager’s Event-Action editor,
to be triggered when the associated action name (for example, <Start> and
<Stop>) is encountered by the profile.

File Summary tab

File Summary Tab
ITEM DESCRIPTION
Profile Channel Displays all available profile channels.
Units Displays the unit of measurement for the end level dimension.
Maximum Displays the maximum value for the channel.
Note This may be zero if the profile was not created using the MTS Profile
Editor application.

Minimum Displays the minimum value for the channel.

Note This may be zero if the profile was not created using the MTS Profile
Editor application.

Station Channels Displays the station control channels where the profile will be played out.
Note This box is blank if you have not mapped the profile channel to a
station channel on the Mapping tab.

206 Command Processes MTS MultiPurpose TestWare®

 Profile Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information For information on creating profiles with the Profile Editor application, see
Chapter 18, “Model 793.11 Profile Editor”.

See “How to Use the Manual Command Feature” on page 209.

MTS MultiPurpose TestWare® Command Processes 207

Profile Process

How to Define a Profile Command Process

1. Drag the icon from the Process Palette to your group or procedure
table.

2. Click the process icon in your group or procedure table, or in the navigation
pane.

3. Click the Command tab.

4. Click the Profile Path/File button to open the Select profile file window.
Click the desired profile, and then click Open.
Note If the channel names in the profile do not match the channel names in
your station configuration, MPT will display the following message:

“The profile process was unable to map all the file channels to station
channels. Please check the ‘Mapping’ page.”

5. Select the Total Passes check box, and then type a value.

6. Optional—In the Frequency Multiplier box, set the units of measurement,

and then type a value.

7. Optional—In the Adaptive Compensators list, click a compensator.

8. Click the Mapping tab.

9. Use the Profile Channel lists to map the desired profile channel to each
station channel. (Station channel names are listed in the left column.)

10. For each station channel, select a Control Mode and optionally, a Level
Multiplier, and Level Reference.

11. Click the File Summary tab and verify your channel settings.

12. Optional—Click the Actions tab to map station actions to file actions.

13. Click the General tab.

14. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

15. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

16. In the Execute Process box, type the number of times you want the process
to run.

208 Command Processes MTS MultiPurpose TestWare®

 Profile Process

Note The Execute Process value multiplies the Total Passes in the
Command parameters. If the Execute Process parameter is set to 10
and the Total Passes is set to 5, a total of 50 passes will occur.

17. Optional—In the Counter Type list, click a counter type.

18. Optional—If you enabled a counter, type a Counter Label.

19. Set the desired Start and Interrupt signals for the process in the group or
procedure table.

20. Optional—If the Profile process is equipped with manual compensation,

adjust the Setpoint and Span sliders in the manual compensation panel as
desired while the process is running.

How to Use the Manual Command Feature

Note Manual compensation will be available only if the “Manual Compensation
(MPT Profile Process)” feature is enabled during installation.

With the manual compensation feature you can manually adjust the setpoint and
span of the selected channel while the Profile process is running.

How to apply manual To choose the manual compensation feature, you select Manual in the Adaptive
setpoint and span values Compensators list on the Command tab of the Profile process. When you select
to a profile this feature, a Manual Compensation panel appears (under the Sequence
Counters panel) when the test procedure is locked. MPT ramps from current
levels to manual adjustment levels according to the Setpoint and Span times
specified in the Command Options tab of the Channel Options window in
Station Manager.

MTS MultiPurpose TestWare® Command Processes 209

Profile Process

Setpoint and Span sliders

appear in the manual
compensation panel when
you lock the test
procedure. You can adjust
the values when the
Profile process is active.

You can adjust slider

parameters by double-
clicking the Setpoint and
Span labels on the manual
compensation panel.

Note Only one Profile process with manual compensation may run at a time.

Note Setpoint and Span controls (defined in the MPT Options Editor) must be
disabled while the manual compensation feature is running. You must
select Disable and Reset for both controls or MPT will generate an error
when the procedure is locked.

Adjusted values applied The values of the manual slider adjustments are normally reset when the process
to repeats is done. However, the manual adjustment values are temporarily stored during
the current session, and are automatically reapplied to repeats of the Profile
process. So once you adjust the Setpoint and Span sliders of an active profile
process, you can expect MPT to reapply your values to repeat instances of the
Profile process within the current run of the test procedure.

Adjusted values not Once the test procedure has been unlocked or reset, the manual adjustment values
saved for recovery are lost and are not restored as part of normal test procedure recovery. (Manual
adjustment values are not saved to the specimen.mps file.)

210 Command Processes MTS MultiPurpose TestWare®

 External Command Process

External Command Process

About the External Command Process
The External Command process accommodates program inputs from an external
programmer or controller.

Before you can use an External Command process, you must:

• Connect the external command source to your controller.

• Use Station Builder to allocate an analog input resource (for the command
input signal).

• Adjust the command input signals with the Station Manager application.

• When you define an External Command process, you must define which
channel(s) the process will control.

External Command

Soft Start

You may configure the process to ramp from The process tapers to external
the end level of the previous command command amplitude.
process to the external command setpoint,
or you may configure the process to begin at
current command level.

MTS MultiPurpose TestWare® Command Processes 211

External Command Process

About Starting External Commands

If the external command is not running when MPT starts the External Command
process, your test will stop responding.

To ensure that your external program is running when it is needed, do one of the
following:

• Start your external program source before you start your MPT procedure.
This ensures that the external command is running when the External
Command process starts and limits unwanted bumps in your command
signal.

• If your external programmer supports digital input and output signals,

configure a Digital Output to start the external program, and a Digital Input
Detector Process to start the External Command process.

Considerations for WARNING

using the External
Command process Using the External Command process can result in unexpected actuator
movement.

Unexpected actuator movement may injure personnel and damage

equipment.

Consider the possibility of unexpected actuator movement when designing or

executing a test that includes an External Command process.

The External Command process, when used in combination with a specific type
of control mode and MPT option, may cause the system to “bump” (perform an
immediate step adjustment) when triggered. This occurs as the system reacts to
the offset component of the program in the External Command process.

Specifically, this may occur when the External Command process is used in a
station that uses one of the following control modes:

• A Dual Compensation control mode in which the Compensation Type is

Amplitude Control Only,

• A Cascaded PIDF control mode in which the Cascade Type is Amplitude

Control Only,

212 Command Processes MTS MultiPurpose TestWare®

 External Command Process

and when the MPT Setpoint option (MPT Options Editor > Execution >
Setpoint) is set to Disable and Reset. (This will not occur if the MPT Setpoint
option is set to Enable.)

About Stopping External Command Processes

Typically, you will use an MPT Data Limit Detector Process or Digital Input
Detector Process to end the External Command process.

• You can use a Data Limit Detector Process to interrupt the External
Command process after a specified time period or when specified signal
limits are reached.

• If your external programmer can issue a signal when the program is

complete, you can use a Digital Input Detector Process to interrupt the
External Command process.

• You can stop the External Command process manually by clicking the stop
control on the Station Controls panel. This stops the process and the
procedure.

• You can resume the External Command process by clicking the run control
on the Station Controls panel.

When the External Command process stops or is interrupted, you may

configure it to remain at its current level, or to taper to the setpoint specified on
the Scaling tab. If a setpoint is not specified on the Scaling tab, the signal tapers
to the system setpoint.

If you click Run after holding the command, the process will either ramp to the
specified setpoint and then taper up to the defined amplitude (if Enable Ramp is
selected), or taper directly up to the defined amplitude (if Enable Ramp is not
selected).

MTS MultiPurpose TestWare® Command Processes 213

External Command Process

About Setpoint/Span Settings

You can also define a different setpoint and span to be used while the external
command process plays out.

You should understand how setpoint and span settings on the different Station
Manager and MPT windows affect one another.

• Scaling tab External Command Parameters window, MPT application.

The Change Setpoints and Change Spans check boxes let you override the
system setpoint and span values while the process is being run.

• Setpoint and Span window, Station Manager application.

This window contains the system setpoint (Setpoint slider) and span (Span
slider) values that the External Command process overrides while the
process is being run.

• Command Options tab, Channel Options window, Station Manager

application.

The value in the Setpoint entry box determines the default rate at which the
controller ramps to the setpoint value entered in the External Command
Parameters window. Likewise, the Begin control determines the rate at
which the controller ramps the external program to the span value entered in
the External Command Parameters window.

• Execution tab, MPT Options Editor, Span and Setpoint controls, MPT
application.

The Span and Setpoint controls determine whether you can edit the setpoint
and span values entered in the Station Manager Span and Setpoint window
while the External Command process is being run.

214 Command Processes MTS MultiPurpose TestWare®

 External Command Process

About Overriding System Setpoint and Span

With the External Command process, you can temporarily override the default
system span and setpoint values, even if you select Disable and Reset for the
Span and Setpoint controls on the Execution tab of the MPT Options Editor.

To do this, enable the Change Setpoints and/or Change Spans check boxes in
the Scaling tab of the External Command Parameters window, and type span and
setpoint values in the associated entry boxes. This causes the span and setpoint
values you type to overwrite system span and setpoint values when MPT
executes the External Command process.

The precise way MPT performs the override depends on whether you select
Disable and Reset or Enable:

• If you select Disable and Reset, the controller will set span at 100% and
setpoint at zero as it plays out the procedure until it begins to play out the
External Command process. At that point the controller switches to the
External Command process setpoint and span values. When the process is
done, the setpoint reverts to zero, and the span reverts to 100% for the
remainder of the procedure. With this selection, you cannot make
adjustments to the Setpoint and Span sliders while the test is running.

• If you select Enable, the controller will use the system setpoint and span
values as it plays out the procedure until it begins to play out the External
Command process. At that point, the controller switches to the External
Command process setpoint and span values and uses them for the remainder
of the procedure. With this selection, you can make adjustments to the
Setpoint and Span sliders while the procedure is running.

MTS MultiPurpose TestWare® Command Processes 215

External Command Process

External Command Parameter Descriptions

Scaling tab
Scaling Tab (part 1 of 2)
ITEM DESCRIPTION
Enable Ramp If selected, the process will ramp to the specified setpoint before beginning to
taper to the specified amplitude.
If not selected, the process will begin to taper to the specified amplitude from
the current level.
Ramp Time If Enable Ramp is selected, Ramp Time specifies the amount of time the
command ramps from the starting level of the process to the specified setpoint.
If you set the Ramp Time to zero, the controller will use the Setpoint/Span
time specified on the Station Manager Channel Options Command Options
tab.
Adaptive Enables command compensation during the command process.
Compensators
Important The use of the AICX compensator can introduce large delays
between generated command and command to the actuator.
The delay is dependant on the tuning of AICX and is two times
the value of the Impulse Response.

Change Setpoints Enables the Setpoint control.

If disabled, the Setpoint will remain unchanged.
Change Spans If enabled, the process will play out whatever percentage of full scale
amplitude is entered in the Span box of this window.
If disabled, the process will play out whatever percentage of full scale
amplitude that is specified for the system span value. The system span value is
set in Station Manager. (Pressing the Span Setpoint button on the Station
Controls panel displays the Setpoint and Span window.)
Enable Soft Stop If selected, the process will ramp to the specified setpoint before stopping.
If not selected, the process will stop at the current level.
Channel Specifies the channel for which the controls on this tab apply.
Control mode Specifies the control mode. Only control modes that have the same dimension
as the channel’s external input signal are available.

216 Command Processes MTS MultiPurpose TestWare®

 External Command Process

Scaling Tab (part 2 of 2)

ITEM DESCRIPTION
Setpoint Defines the setpoint value for the selected channel.
The value entered in the setpoint box will overwrite the system setpoint value
when the process becomes active.
Span Defines the span value for the selected channel.
The value entered in the Span box will overwrite the system span value when
the process becomes active.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

Channels tab Displays the channels available to this process. Use the arrow keys to move
desired channels from the Available list to the Included list.

Note Only channels in station configurations that have an external command

signal defined in Station Builder are available to this process.

MTS MultiPurpose TestWare® Command Processes 217

External Command Process

How to Define an External Command Process

1. Drag the icon from the Process Palette to your group or procedure
table.

2. Click the process icon in your group or procedure table, or in the navigation
pane.

3. Click the Channels tab.

4. Move the channels that you want to use to generate the command onto the
Included list. Move all other channels to the Available list.

5. Click the Scaling tab.

6. If desired, select Enable Ramp. In the Ramp Time box, set the units of
measurement, and then type a value.

7. Optional—In the Adaptive Compensators list, click a compensator.

8. Optional—If you want the external command to use a different setpoint than
the one specified in Station Manager, select the Change Setpoints check
box.

9. Optional—If you want the external command to use a different span than
the one specified in Station Manager, select the Change Spans check box.

10. In the Channel list, click your desired channel.

11. In the Control Mode list, click your desired control mode.

12. If you selected Change Setpoints, define the new setpoint value and units
in the Setpoint box.

13. If you selected Change Spans, type a span value for the external command
in the Span box.

14. If desired, select Enable Soft Stop.

15. Repeat steps 10 - 13 for each channel you wish command with the External
Command process.

16. Click the General tab.

17. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

18. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

218 Command Processes MTS MultiPurpose TestWare®

 External Command Process

19. In the Execute Process box, type the number of times you want the process
to run.

20. Optional—In the Counter Type list, click a counter type.

21. Optional—If you enabled a counter, type a Counter Label.

22. Set the desired Start and Interrupt signals for the process in the group or
procedure table.

MTS MultiPurpose TestWare® Command Processes 219

Sweep Command Process

Sweep Command Process

About the Sweep Activity
With the Sweep activity you can sweep a command waveform between two
frequency values in a linear or logarithmic progression at a constant amplitude.

Example: Frequency
sweep from 0.5 Hz to 15
Hz at sweep rate of 5 Hz/
sec.

Sweep Activity

When a sweep command starts, it always moves first to End Level 1, and then to
End Level 2.

Sine, ramp, and square Sine, ramp, and square commands use the first segment to bridge any difference
start levels between the current level and the End Level 1 that you specify. This transition
segment is counted as the first segment.

CAUTION

A high-speed transition segment can result in an unwanted spike (or bump)

in your command signal.

Unwanted command-signal spikes can damage the physical test specimen.

To avoid spikes in the command signal, use a Ramp activity to bridge where end
levels and start levels differ greatly. If an activity end level is not near the start
level of your cyclic command, the activity uses the first segment to move all the
way from the current level to the start level at the transition speed that you specify.

220 Command Processes MTS MultiPurpose TestWare®

 Sweep Command Process

Cycles and segments You can repeat cycles or segments. Two segments create one cycle. Repeating a
full cycle first goes to end level 1 and ends at end level 2. Repeating a segment
can end at end level 1 or end level 2 (depending on whether the count value is
odd or even).

The conventional way to

End level Frequency = 5Hz
define the duration of a
cyclic command is by
frequency or time. Start level

Time = 0.1second

End level 2 = 5 kip

Rate = 5 kip/1 second

End level 1 = 0 kip

Note The end levels can be set to values greater than the full scale. The
command will attempt to reach the specified end level; however, the
feedback will become saturated before reaching the specified end level
and will cause a hydraulic interlock.

End levels The two end levels specify the amplitude of the waveform. When two test
command activities with different end levels are sequenced, the transition
between them is accomplished at the rate and segment shape of the following
activity. This provides a smooth transition between test commands.

Example Suppose you run a Sweep activity that completes a cyclic command at End
Level 2 (in this case, +2 cm). Next, suppose you run another Sweep activity in
which End Level 1 = –1 cm and End Level 2 = +1 cm. The transition segment
bridges the two commands from the +2 cm level to the –1 cm level at the time,
rate, or frequency of the second activity.

MTS MultiPurpose TestWare® Command Processes 221

Sweep Command Process

Sweep Command Parameter Descriptions

Command tab
Command Tab (part 1 of 2)
ITEM DESCRIPTION
Segment Shape Specifies the segment shape.
Sweep Type Specifies how the sweep progresses:
• Linear—steps the sweep linearly by the Sweep Rate between Frequency
1 and Frequency 2.

• Logarithmic—steps the sweep logarithmically by the Sweep Rate

between Frequency 1 and Frequency 2.
Sweep Rate Specifies the rate at which the sweep progresses.
Sweep Count Specifies how many times the sweep will repeat.
Note If you clear the Count box, the sweep will repeat continuously.

Frequency 1 Defines the starting sweep frequency.

Frequency 2 Defines the ending sweep frequency.
Adaptive Enables command compensation during the command process.
Compensators
Important The use of the AICX compensator can introduce large delays
between generated command and command to the actuator.
The delay is dependant on the tuning of AICX and is two times
the value of the Impulse Response.

Relative End Levels Defines the segment end level:

• Absolute End Level is relative to setpoint.

• Relative End Level is relative to the starting command value (the value
when the process begins).
Channel Specifies the channel.
Control Mode Specifies the control mode or control-mode variable.
Absolute End Level Defines the end level value for the first segment in the channel.
1/Relative End
Level 1

222 Command Processes MTS MultiPurpose TestWare®

 Sweep Command Process

Command Tab (part 2 of 2)

ITEM DESCRIPTION
Absolute End Level Defines the second end level value for the second segment in the channel.
2/Relative End
Level 2

Phase Lag Specifies the phase relationship of the waveform generated by this process
from channel to channel. Phase Lag is disabled if Rate is specified for the
process.
Note Phase Lag is relative to the channel that has the smallest degree of
phase. The Phase Lag of each channel is referenced to the lowest
Phase Lag defined in the channels.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

Channels tab Displays the channels available to this process. Use the arrow keys to move
desired channels from the Available list to the Included list.

For more information See “Segment Shapes” on page 188.

MTS MultiPurpose TestWare® Command Processes 223

Sweep Command Process

How to Define a Sweep Process

1. Drag the icon from the Process Palette to your group or procedure
table.

2. Click the process icon in your group or procedure table, or in the navigation
pane.

3. Click the Channels tab.

4. Move all the channels you want to generate the command on to the
Included list. Move all the others to the Available list.

5. Click the Command tab.

6. In the Segment Shape list, click the desired segment shape.

7. In the Sweep Type list, click Linear or Logarithmic.

8. If desired, select the Sweep Count check box and type the number of times
you want the sweep to repeat. For continuous sweeps, clear the Sweep
Count check box.
Note The Execute Process value multiplies the Sweep Count in the
Command parameters. If the Execute Process parameter is set to 10
and the Sweep Count is set to 5, a total of 50 sweeps will occur.

9. Type a value and unit type for Frequency 1., then type a value for
Frequency 2.
Note This process can run ascending or descending sweeps.

10. Optional—In the Adaptive Compensators list, click a compensator.

11. Optional—If you want to define a relative end level, select the Relative
End Levels check box.

12. In the Channel list, click your desired channel.

13. In the Control Mode list, click the desired control mode or right-click to
assign a control-mode variable.

14. Set the units of measurement for the end levels, then type values for End
Level 1 and End Level 2.

15. Optional—In the Phase Lag box, type a value.

16. Repeat steps 12 through 15 for each channel you want to command with this
process.

224 Command Processes MTS MultiPurpose TestWare®

 Sweep Command Process

17. Click the General tab.

18. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

19. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

20. In the Execute Process box, type the number of times you want the process
to run.

21. Optional—In the Counter Type list, click a counter type.

22. Optional—If you enabled a counter, type a Counter Label.

23. Set the desired Start and Interrupt signals for the process in the group or
procedure table.

MTS MultiPurpose TestWare® Command Processes 225

Signal Based Command Process

Signal Based Command Process

About the Signal Based Command (SBC) Process
This process uses a user-defined lookup table to generate a channel command
based on the value of a lookup signal. Lookup tables are defined in a tab-,
comma-, or space-delimited text file that lists the command values for specific
lookup-signal values.

Configuration SBC process settings allow you to define the lookup-table file path, which
lookup table/lookup signal will generate the command for each channel, and the
control mode for each channel.

Note The SBC process does not support compensation.

Test execution During the test, the SBC process reads the lookup signal, locates the
corresponding signal value in the lookup table, and applies the command defined
for that signal value. Command values for lookup-signal values that are between
user-defined data points are linearly interpolated as shown in the graph below.

If the lookup-signal value is outside the values specified in the lookup table, the
command will hold. For example, in the plot below, a lookup-signal value of 145
degrees would result in a command of 15.224 kN.
Command (kN)

Lookup Signal = Gear Angle (degrees)

226 Command Processes MTS MultiPurpose TestWare®

 Signal Based Command Process

Signal Based Command (SBC) Process Example

In the example below, the SBC lookup table defines the load command for
various landing gear angles. As the landing gear angle (lookup signal) changes,
the SBC process locates that lookup-signal value in the lookup table and applies
the command defined for that lookup-signal value.

Lookup Signal
(controller input)

MultiPurpose TestWare with Load

Actuator Cell Gear
Signal Based Command Process Angle

Servovalve Load
Command Feedback
SBC Lookup Table

S
Signal Based PIDF
Error Controller
Command

MTS MultiPurpose TestWare® Command Processes 227

Signal Based Command Process

Signal Based Command (SBC) Lookup-Table File Requirements

File format The SBC process supports tab-, comma-, and space-delimited text files that
contain lookup tables. The lookup-table file must follow the format shown below.

• The file can contain any number of lookup tables.

• Each table can contain up to 257 rows (two rows minimum).

• The header information, column layout, and keyword spelling must exactly
match the example shown below. No additional text is allowed.

• The number of tables designated in the header (Tables=) must match the
number of tables in the lookup-table file.

Tables= Important The bold entries are required keywords that

defines the number of tables must be typed exactly as shown.
in the lookup-table file
(2 in this example). FileType=SBC_Lookup_Table
Description=Gear Angle vs. Gear Load Command
Table(X)= Tables=2
defines the table number and the
title that appear in the Lookup
Table list in the SBC process Table(1)=Landing_1 (100%)
Mapping tab.
Lookup Command
deg kN
Lookup column
defines various lookup-signal values. 125 15.224
120 15.483
Command column
defines the resulting command value 115 15.334
for each lookup-signal value. ... ...
5 64.054
Defines the units used for the 0 67.613
lookup signal and the resulting Table(2)=Landing_2 (50%)
command output.
Lookup Command
Note The unit value must be
defined in the Unit deg kN
Assignment Test Editor 125 7.612
and must match the
units defined in the 120 7.742
configuration file.

228 Command Processes MTS MultiPurpose TestWare®

 Signal Based Command Process

Signal Based Command (SBC) Process Parameter Descriptions

Note The SBC process does not support compensation.

CAUTION

A high-speed transition time can result in an unwanted spike (or bump) in

the command signal.

Unwanted command-signal spikes can damage the test specimen.

To avoid spikes in the command signal, use a transition time that smoothly
transitions the channel commands to the initial SBC command level.

Command tab
Command Tab
ITEM DESCRIPTION
Lookup Table Path/File Click to display the Open Lookup Table window and select a user-defined text
file containing the lookup data.
Transition Time Specifies the time the process takes to transition the channel commands to the
initial level. If zero is specified, the transition profile will not be executed.
Duration Time Specifies the amount of time that the process remains active.
• Select the Duration Time check box and enter the amount of time that the
process remains active.

• Clear the Duration Time check box to set the duration time to “Indefinite.”

MTS MultiPurpose TestWare® Command Processes 229

Signal Based Command Process

Mapping tab The Mapping tab allows you to specify SBC parameters for each control channel.

Mapping Tab
ITEM DESCRIPTION
Lookup Table Use the Lookup Table list to specify the lookup table that will supply the
command for that channel. The names that appear in the Lookup Table list are
defined in the Table(x)=table name heading associated with each lookup table.
A lookup table appears in a channel Lookup Table list if the following is true:
• That channel includes a control mode that uses the same units defined in the
lookup table’s Command column.

• The station configuration contains at least one signal that uses the same units
defined in the lookup table’s Lookup column.
Note Click the File Summary tab for a listing of each lookup table defined in the
lookup-table file.

Lookup Signal Use the Lookup Signal list to define the signal used by the selected lookup table.
This signal’s units must match the signal units defined in the lookup table.
Control Mode Defines the control mode used for the channel.

File Summary tab Displays a summary of the lookup-table file selected in the Command tab.

Click View to view and/or edit the lookup-table file in a text viewer.

The summary includes:

• The names of each lookup table defined in the lookup-table file.

• Lookup and Command units.

• The number of data points defined in each lookup table.

230 Command Processes MTS MultiPurpose TestWare®

 Signal Based Command Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

How to Create a Signal Based Command (SBC) Process

1. Drag the SBC process icon from the Process Palette to a Group or
Procedure table.

2. Click the SBC process icon in the Group or Procedure table.

3. Set the desired Start and Interrupt signals for the process in the Group or
Procedure table.

4. Click the General tab.

A. In the Name box, type a name for this process. (You can also name the
process in the Procedure table.)

B. Select the Process Enabled check box. (If this box is cleared, the
process will not run.)

C. In the Execute Process box, type the number of times you want the
process to run.

D. Optional—In the Counter Type list, click a counter type.

E. Optional—If you enabled a counter, type a Counter Label.

MTS MultiPurpose TestWare® Command Processes 231

Signal Based Command Process

5. Click the Command tab.

A. Click Lookup Table Path/File to define the file path for the text file
that includes the lookup tables for the SBC process.

B. Enter the Transition Time (the time it takes to ramp the command to
the current SBC command level).

CAUTION

A high-speed transition time can result in an unwanted spike (or bump) in

the command signal.

Unwanted command-signal spikes can damage the test specimen.

To avoid spikes in the command signal, use a transition time that smoothly
transitions the channel commands to the initial SBC command level.

C. Select the Duration Time check box and enter the amount of time that
the process remains active. Clear the Duration Time check box to set
the duration time to “Indefinite.”

6. Click the Mapping tab and define SBC parameters for each control channel.

A. Assign a Lookup Table (or “Not Used”) to each control channel.

B. Assign a Lookup Signal to each channel.

C. Assign a Control Mode to each channel.

232 Command Processes MTS MultiPurpose TestWare®

 Profile with ALC Process

Profile with ALC Process

About the Profile with ALC Process
The Profile with ALC process works the same as the Profile process. You must
use the Profile with ALC process if you want to play out a profile and use ALC
(arbitrary end-level compensation).

Note The Profile with ALC process is optional. You must type a special key
code during installation to enable this process.

About ALC Arbitrary end-level control (ALC) compensation is an adaptive compensation

compensation technique that improves the tracking accuracy of MPT. ALC compensates for
peak and valley errors by building (and continually updating) a matrix of
amplitude compensation factors.For detailed information about the ALC
compensator, see the MTS 793 Control Software manual.

Profile with ALC Parameter Descriptions

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

MTS MultiPurpose TestWare® Command Processes 233

Profile with ALC Process

Command tab
Command Tab
ITEM DESCRIPTION
Profile Path/File Specifies the profile file to be used. You may type a placeholder and file name,
or type a full path. You may also use the browser.
Total Passes Specifies how many times the profile will be played out.
Note If you clear the Total Passes box, the waveform will repeat indefinitely.

Frequency Multiplier Scales the segment rate type (time/rate/frequency) specified in the profile. If
set to 100%, the profile will play out as defined in the profile. If set to 50%, the
profile will play out at half speed. If it is set to 200%, the profile will play out
at twice the speed.
Adaptive Enables command compensation during the command process.
Compensators
To use the ALC compensator with your profile, you must define a Profile with
ALC Process process instead.
If your system is equipped with the manual compensation feature, a Manual
selection will also be available in the list.

Note Manual compensation will be available only if the “Manual

Compensation (MPT Profile Process)” feature is enabled during
installation.

234 Command Processes MTS MultiPurpose TestWare®

 Profile with ALC Process

Mapping tab
Mapping Tab
ITEM DESCRIPTION
Channel Displays all station control channels.
Profile Channel Selects the profile channel that will be played out on this station channel.
You must map the logical channels in your profile to the control channels in
your station configuration. You can arbitrarily map any profile channel to any
station channel, or you can map a single profile channel to multiple station
channels. If you leave any station channel unmapped, no profile will be played
out on that channel.
If you gave the profile channels the same name(s) as the station channels, they
will automatically be mapped to the station channel with the matching name. A
profile channel will appear in the Profile Channel list box next to its
corresponding (station) Channel.
Each Profile Channel list box will contain all the profile channels with units
that can be played out by any control mode for the station channel. For
example, a profile channel that measures length will not map to a station
channel with a temperature control mode.
If the profile was created with normalized dimensions then you can select any
of the control modes available to the station channel when defining the control
mode of the profile channel.
Control Mode Specifies the control mode for the selected station channel.
Level Reference Introduces a mean level offset to the selected station channel.
Level Multiplier Scales the end level values of the profile. The Level Multiplier will function
for both engineering units and “normalized units.”
Note For normalized units, the Profile Command process uses the Level
Multiplier value as the full scale.

MTS MultiPurpose TestWare® Command Processes 235

Profile with ALC Process

Actions tab
Action Tab
ITEM DESCRIPTION
Name Displays the name of the action in the profile.
Action Displays the action, as defined by the Station Manager’s Event-Action editor,
to be triggered when the associated action name (for example, <Start> and
<Stop>) is encountered by the profile.

File summary tab

File Summary Tab
ITEM DESCRIPTION
Profile Channel Displays all available profile channels.
Units Displays the unit of measurement for the end level dimension.
Maximum Displays the maximum value for the channel.
Note This may be zero if the profile was not created using the MTS Profile
Editor application.

Minimum Displays the minimum value for the channel.

Note This may be zero if the profile was not created using the MTS Profile
Editor application.

Station Channels Displays the station control channels where the profile will be played out.
Note This box is blank if you have not mapped the profile channel to a
station channel on the Mapping tab.

236 Command Processes MTS MultiPurpose TestWare®

 Profile with ALC Process

Matrix tab Note This tab is enabled only if ALC has been selected as the Adaptive
Compensator on the Command tab.

Matrix Tab (part 1 of 2)

ITEM DESCRIPTION
Compensation Matrix Names the matrix used by the ALC compensator.
Name
ALC matrix files are saved in the Specimen directory. The default ALC matrix
file is default.mat. If you want to use an existing matrix, copy the mat file into
the Specimen directory, and then type the matrix file name in the
Compensation Matrix Name box.
Initial Gain Specifies the amount of initial gain applied to the signal. The default is 100%,
or no magnification.
Enable Frequency Attempts to run the test at a faster rate than specified in the selected profile.
Compensation
For example, if the profile specifies that the end levels be achieved using a
frequency of 0.2 Hz, the application may actually achieve these end levels at
0.5 Hz. The maximum rate increase is specified on the ALC tab in the
Compensators tab in the Station Setup window in Station Manager.
Note This option is available only if you have specified a single-channel
profile.

MTS MultiPurpose TestWare® Command Processes 237

Profile with ALC Process

Matrix Tab (part 2 of 2)

ITEM DESCRIPTION
Verify Loaded Matrix Specifies whether you want the application to compare the matrix parameters
Parameters entered on this Matrix window with the parameters currently loaded in the
controller’s real-time.
If you choose “No, Use Loaded Parameters.” the application will disregard
any file saved on disk that matches the entered name and use the matrix
parameters currently loaded in the controller’s real-time.
If you choose ”Yes, Reload if No Match.” the application will compare the
matrix parameters entered in this Matrix window with the parameters currently
loaded in the controller’s real-time. If the parameters do not match, the
application will redefine the real-time matrix using the parameters currently
entered in this Matrix window. In this case the application will also compare
the entered parameters with those stored in any file in the current Specimen
directory that uses the entered name. If they match, the matrix values from the
disk file will be down-loaded into the real-time matrix. If not, the real-time
matrix values will be reset to indicate no correction values are present.
To use a saved compensation matrix for the current test, you must copy (using
Windows operating software) the desired matrix file into the current Specimen
directory before you type the desired matrix name (as it appears in the
Specimen directory) and definition parameters in this window. If the name or
other parameters do not match precisely, or if the desired matrix does not exist
in the current Specimen directory, the application will create a new real-time
matrix with the entered name.
Number of Cells Specifies the number of cells in each axis of the matrix (16, 32, or 64), which
determines the resolution of the correction (the higher the number, the greater
the resolution).
Channel Selects the channel to which the compensation ranges apply. Compensation
ranges must be entered for each channel used by the profile.
Upper Compensation Specifies the upper range value and associated units of the compensation
Range matrix for the selected channel.
Lower Compensation Specifies the lower range value and associated units of the compensation
Range matrix for the selected channel.
Time Between Matrix Selects the time interval between matrix saves. If you Hold the test, the timer
Saves for saving the matrix also holds.
Note If you want the matrix to be saved only at the end of the test, type a
time longer than the profile.

238 Command Processes MTS MultiPurpose TestWare®

 Profile with ALC Process

Tracking tab
Tracking Tab
ITEM DESCRIPTION
Channel Lists the channel(s) to which the ALC compensation will apply.
Missed Peak Specifies the difference between the commanded peak and the actual peak
Reference achieved that you want the application to detect.
Missed Peaks Displays the total number of missed peaks (also stored in the log file). This
value is saved as part of the run-time state of the process (in the mps file), and
can be restored accordingly.
When you reset the procedure, the ALC missed peaks values displayed on the
Tracking tab are not immediately reset to zero. However, when you run the test
again the process will start counting (and displaying) from zero.

For more information For more information, see “About Specimen.mps Files” on page 139.

How to Define a Profile with ALC Process

1. Drag the icon from the Process Palette to your group or procedure
table.

2. Click the process icon in your group or procedure table, or navigation pane.

3. Click the Command tab.

4. Click the Profile Path/File button to open the Select profile file window.
Click the desired profile, and then click Open.
Note If the channel names in the profile do not match the channel names in
your station configuration, MPT will display the following message:

“The profile process was unable to map all the file channels to station
channels. Please check the ‘Mapping’ page.”

5. Select the Total Passes check box, and then type a value.

6. In the Frequency Multiplier box, set the units of measurement, and then
type a value.

7. Click the Mapping tab.

8. Use the Profile Channel lists to map the desired profile channel to each
station channel. (Station channel names are listed in the left column.)

MTS MultiPurpose TestWare® Command Processes 239

Profile with ALC Process

9. For each station channel, select a Control Mode and optionally, a Level
Multiplier, and Level Reference.

10. Click the Command tab.

11. In the Adaptive Compensators list, select the ALC compensator.

12. Optional—click the Actions tab, and map station actions to profile actions.

13. Click the File Summary tab and verify your channel settings.

14. Click the Matrix tab and type a Compensation Matrix Name.

15. Optional—Select the Enable Frequency Compensation check box.

16. Under Verify Loaded Matrix Parameters, select whether or not you want
the application to verify the loaded matrix parameters.

17. Under Matrix Parameters, configure your ALC matrix.

18. Optional—If you want the matrix to be saved, select the Time Between
Matrix Saves check box, and then type a save interval.

19. Click the Tracking tab.

20. Set the units and type a value for the Missed Peak Reference for each
channel.

21. Click the General tab.

22. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

23. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

24. In the Execute Process box, type the number of times you want the process
to run.

25. Optional—In the Counter Type list, click a counter type.

26. Optional—If you enabled a counter, type a Counter Label.

27. Set the desired Start and Interrupt signals for the process in the group or
procedure table.

240 Command Processes MTS MultiPurpose TestWare®

 Cyclic with ALC Process

Cyclic with ALC Process

About the Cyclic with ALC Process
The Cyclic with ALC process works the same as the Cyclic process. You must
use the Cyclic with ALC process if you want to program a cyclic command and
use ALC (arbitrary end-level compensation).

Note The Cyclic with ALC process is optional. You must type a special key
code during installation to enable this process.

About ALC Arbitrary end-level control compensation is an adaptive compensation technique

compensation that improves the tracking accuracy of MPT.

ALC compensates for peak and valley errors by building (and continually
updating) a matrix of amplitude compensation factors.

For detailed information on the ALC compensator, see the MTS 793 Control
Software manual.

Cyclic with ALC Parameter Descriptions

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

MTS MultiPurpose TestWare® Command Processes 241

Cyclic with ALC Process

Command tab
Command Tab
ITEM DESCRIPTION
Profile Path/File Specifies the profile file to be used. You may type a placeholder and file name,
or type a full path. You may also use the browser.
Total Passes Specifies how many times the profile will be played out.
Note If you clear the Total Passes box, the waveform will repeat indefinitely.

Frequency Multiplier Scales the segment rate type (time/rate/frequency) specified in the profile. If
set to 100%, the profile will play out as defined in the profile. If set to 50%, the
profile will play out at half speed. If it is set to 200%, the profile will play out
at twice the speed.
Adaptive Enables command compensation during the command process.
Compensators
To use the ALC compensator with your profile, you must define a Profile with
ALC Process process instead.
If your system is equipped with the manual compensation feature, a Manual
selection will also be available in the list.

Note Manual compensation will be available only if the “Manual

Compensation (MPT Profile Process)” feature is enabled during
installation.

Channels tab Displays the channels available to this process. Use the arrow keys to move
desired channels from the Available list to the Included list.

242 Command Processes MTS MultiPurpose TestWare®

 Cyclic with ALC Process

Matrix tab
Matrix Tab (part 1 of 2)
ITEM DESCRIPTION
Compensation Matrix Names the matrix used by the ALC compensator.
Name
ALC matrix files are saved in the Specimen directory. The default ALC matrix
file is default.mat. If you want to use an existing matrix, copy the mat file into
the Specimen directory, and then type the matrix file name in the
Compensation Matrix Name box.
Initial Gain Specifies the amount of initial gain applied to the signal. The default is 100%,
or no magnification.
Enable Frequency Attempts to run the test at a faster rate than specified in the selected profile.
Compensation
For example, if the profile specifies that the end levels be achieved using a
frequency of 0.2 Hz, the application may actually achieve these end levels at
0.5 Hz. The maximum rate increase is specified on the ALC tab in the
Compensators tab in the Station Setup window in Station Manager.
Note This option is available only if you have specified a single-channel
profile.

Verify Loaded Matrix Specifies whether you want the application to compare the matrix parameters
Parameters entered on this Matrix window with the parameters currently loaded in the
controller’s real-time.
If you choose “No, Use Loaded Parameters.” the application will disregard
any file saved on disk that matches the entered name and use the matrix
parameters currently loaded in the controller’s real-time.
If you choose ”Yes, Reload if No Match.” the application will compare the
matrix parameters entered in this Matrix window with the parameters currently
loaded in the controller’s real-time. If the parameters do not match, the
application will redefine the real-time matrix using the parameters currently
entered in this Matrix window. In this case the application will also compare
the entered parameters with those stored in any file in the current Specimen
directory that uses the entered name. If they match, the matrix values from the
disk file will be down-loaded into the real-time matrix. If not, the real-time
matrix values will be reset to indicate no correction values are present.
To use a saved compensation matrix for the current test, you must copy (using
Windows operating software) the desired matrix file into the current Specimen
directory before you enter the desired matrix name (as it appears in the
Specimen directory) and definition parameters in this window. If the name or
other parameters do not match precisely, or if the desired matrix does not exist
in the current Specimen directory, the application will create a new real-time
matrix with the entered name.

MTS MultiPurpose TestWare® Command Processes 243

Cyclic with ALC Process

Matrix Tab (part 2 of 2)

ITEM DESCRIPTION
Number of Cells Specifies the number of cells in each axis of the matrix (16, 32, or 64), which
determines the resolution of the correction (the higher the number, the greater
the resolution).
Channel Selects the channel to which the compensation ranges apply. Compensation
ranges must be entered for each channel used by the profile.
Upper Compensation Specifies the upper range value and associated units of the compensation
Range matrix for the selected channel.
Lower Compensation Specifies the lower range value and associated units of the compensation
Range matrix for the selected channel.
Time Between Matrix Selects the time interval between matrix saves. If you Hold the test, the timer
Saves for saving the matrix also holds.
Note If you want the matrix to be saved only at the end of the test, type a
time longer than the profile.

Tracking tab
Tracking Tab
ITEM DESCRIPTION
Channel Lists the channel(s) to which the ALC compensation will apply.
Missed Peak Specifies the difference between the commanded peak and the actual peak
Reference achieved that you want the application to detect.
Missed Peaks Displays the total number of missed peaks (also stored in the log file). This
value is saved as part of the run-time state of the process (in the mps file), and
can be restored accordingly.
When you reset the procedure, the ALC missed peaks values displayed on the
Tracking tab are not immediately reset to zero. However, when you run the test
again the process will start counting (and displaying) from zero.

244 Command Processes MTS MultiPurpose TestWare®

 Cyclic with ALC Process

How to Define a Cyclic with ALC Process

1. Drag the icon from the Process Palette to your group or procedure
table.

2. Click the process icon in your group or procedure table, or navigation pane.

3. Click the Channels tab.

4. Move the channels that you want to use to generate the cyclic command
onto the Included list. Move the other channels to the Available list.

5. Click the Command tab.

6. In the Segment Shape list, click the segment shape.

7. Select Time, Rate, or Frequency, and set the units of measurement, and
then and type a value.

8. Select the Count check box. Set the units (cycles or segments), and then
type the number of times the cyclic command is to repeat. For continuous
cycling, clear the Count check box.

9. In the Adaptive Compensators list, click ALC.

10. Optional—If desired, select the Do Not Update Counters check box.

11. Optional—If you want to define a relative end level, select the Relative
End Levels check box.

12. Select a Channel.

13. In the Control Mode list, click the desired control mode or right-click to
assign a control-mode variable.

14. Select the units for the end levels, then type values for End Level 1 and End
Level 2.

15. Type a Phase Lag.

16. Repeat steps 12 - 15 for each channel you want to command with this
process.

17. Click the Matrix tab and type a Compensation Matrix Name.

18. Optional—Select Enable Frequency Compensation.

19. Choose whether you want the application to verify the loaded matrix
parameters.

MTS MultiPurpose TestWare® Command Processes 245

Cyclic with ALC Process

20. Under Matrix Parameters, configure your ALC matrix.

21. Optional—If you want the matrix to be saved, select the Time Between
Matrix Saves check box, and then type a save interval.

22. Click the Tracking tab and type a Missed Peak Reference amount and
corresponding units.

23. Click the General tab.

24. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

25. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

26. In the Execute Process box, type the number of times you want the process
to run.

27. Optional—In the Counter Type list, click a counter type.

28. Optional—If you enabled a counter, type a Counter Label.

29. Set the desired Start and Interrupt signals for the process in the group or
procedure table.

246 Command Processes MTS MultiPurpose TestWare®

 Model 793.71/72 Time History Output Process

Model 793.71/72 Time History Output Process

About the Time History Output Process
Note This process will not operate properly on a station configuration that uses
the decimal clock mode in its associated hardware interface file. For
proper operation, this process requires a station configuration that uses
a binary clock mode. For more information, see the MTS 793 Software
Utility manual (PN 100147132).

The Model 793.71 Time History Output process drives one or more channels in
your station with an RPC (RPC II, RPC III, or RPC Pro) Time History file (with
extension drv or seq).

The Model 793.72 Time History Output with Acquisition process can also
simultaneously digitize and store one or more channels of analog test response
data in the RPC file format. The digitized data will have the same sampling rate
as the drive file, and the number of points sampled for the channel will match the
drive file. This digitized file can be used to measure the system’s transfer
function or iterate to a desired response signal. It can also be used with the RPC
suite of software applications.

Note The Time History Output process (Model 793.71) is optional. You must
type a special key code during installation to enable this process. The
purpose of this process is to drive station channels with time history files,
and includes Command, Mapping, Actions, Status, and General tabs.
This process offers an optional data acquisition feature (Model 793.72)
which also requires a special key code during installation. The data
acquisition feature adds Acquisition and Trend tabs to this process. All
tabs are documented in this section.

MTS Series 793 Software supports both short integer and floating point time
history files. To change these settings:

1. Open the Project Manager application.

2. Click Tools > Project Settings.

3. Select MultiPurpose TestWare in the category pane.

4. Click Time History Output Process Data Format in the values pane.

MTS MultiPurpose TestWare® Command Processes 247

Model 793.71/72 Time History Output Process

5. Select one of the following from the dropdown menu:

Follow Input The response file format will follow the drive time history file.
Float The response file will be written in floating point data format.
Short Integer The response file will be written in short integer data format.

About Time History Output and Controller Rates

Time History rates supported by the controller are dependent on the system rate
specified in your controller’s hardware interface file:

SYSTEM RATE (HZ) FILE RATE (HZ)

1024 1024, 512, 409.6*, 256, 204.8, 128, 102.4
2048 2048, 1024, 512, 409.6, 256, 204.8, 128, 102.4
4096 2048, 1024, 512, 409.6, 204.8
* This sampling rate (409.6 Hz) is not supported by Series 494 hardware,
and is not recommended. When using this sampling rate with a 1024 Hz
system rate, the function generator and RPC data acquisition may not
stay synchronized after a hold and resume. There can be an additional
phase shift between the drive and response after each hold and resume.

The up-sampling filters are designed to begin cutting off the signal at 35% of the
sampling rate and to be 60 dB down at 65% of that rate. When a time history is
entered into this process, the software will check the signal’s sampling rate and
determine whether it can be supported. If not, an error message will be generated.

After being digitized, the signals are run through a digital filter whose cutoff is
40% of the requested sampling frequency, and then down-sampled to the
requested sampling rate.

248 Command Processes MTS MultiPurpose TestWare®

 Model 793.71/72 Time History Output Process

Time History Output Status Window

Note This panel appears only if the user enables the Show Status Panel at
Runtime option on the Status tab.

During a test, the Time History Output (or Input) Status panel displays on the
MPT control panel. The status panel appears when you lock the procedure.

MTS MultiPurpose TestWare® Command Processes 249

Model 793.71/72 Time History Output Process

Time History Output Parameter Descriptions

Command tab
Command Tab (part 1 of 3)
ITEM DESCRIPTION
Drive File Selects an RPC II, RPC III, or RPC Pro drive file (drv or seq) to play out to the
station.
When you have selected a file, the application:
• Verifies that it is a file that it can read (RPC format).

• Reads in the file header.

• Ensures that the number of channels in the file is not greater than the
number of channels in the station.

• Ensures that the sampling rate is supported.

Note Playout of RPC drive files at 128 Hz requires a system rate of 1024
Hz.

Note For controllers equipped with MTS Series 494 hardware, playout of
RPC drive files at 409.6 Hz requires a system rate of 2048 Hz or 4096
Hz. Controllers equipped with MTS Series 494 hardware do not
support playout of RPC drive files as 409.6 Hz with a system rate of
1024 Hz.

If any of these steps fail, a message will display the problem. If no problem
exists, the application will attempt to map the file’s channels to the station’s
channels. Next, the application will check for channel conflicts.

250 Command Processes MTS MultiPurpose TestWare®

 Model 793.71/72 Time History Output Process

Command Tab (part 2 of 3)

ITEM DESCRIPTION

You may make limited changes to the contents of an RPC time history file
between the time its name is entered here and when it is actually used during
the execution of a procedure. MPT will compare the file header at execution
time to its contents during the definition phase. If it detects any differences in
any of the following parameters, an error status will be returned and the test
will be terminated:
• RPC File Type

• Number of channels

• Points per group

• Sampling rate

• Channel full scales

• Channel descriptors

• Channel units

• Channel mapping
Passes Specifies the number of passes the drive file will play out each time the process
runs, as specified on the General tab.
This function differs from the Execute Process value on the General tab. The
difference is that the Time History Output process will come to a complete
halt and then re-initialize and restart for each Execute Process count specified
in the General tab. This creates a delay between the end of one count and the
beginning of another.
Passes entered here do not result in a delay because the application simply
reads data from the beginning of the already opened file and queues it in real
time, which eliminates any delay.
Relative Time Signal If selected, the process reads the current command value on each channel when
the process runs. These commands are added to each point in the time history
as it is read from its file, and the modified command is played out. With this
feature, you can preload a channel and then play out the time history relative to
that preloaded value. If not checked, the time history is played out as it is
stored in the disk file.

MTS MultiPurpose TestWare® Command Processes 251

Model 793.71/72 Time History Output Process

Command Tab (part 3 of 3)

ITEM DESCRIPTION
Drive has an offset When enabled and relative mode is not selected, the process will start by
ramping to the first command point in the time history, and end at the last
command point in the time history, without returning to zero.
When enabled and relative mode is selected, the process will start by ramping
to the first command point in the time history, and will end by returning to the
starting point after the last specified pass is completed.

Note The command signal will not return to zero (or to the starting point in
relative mode) between files in the sequence, but will transition directly
between the last command point of one drive file and the first
command point of the following drive file.

Status Displays messages about channel mapping and full-scale status after the
application checks the mapping and unit selections on the Mapping tab. These
messages are updated each time you modify the channel, mode, or unit
selection on the Mapping tab.
The application will ensure that no two file channels are mapped to the same
station channel. When the check is complete, the application will display either
“Invalid Channel Map” or “Valid Channel Map.” The process cannot be run
with an invalid channel map.
If the mapping is valid, the application checks full scales of each channel in the
file against the range of the selected control mode for each channel. The
message “Full Scales Outside Limits” or “Full Scales In Limits” will display
the results. If the mapping is bad, the outside limits text will display.
Since an RPC time file does not necessarily have data near its full scale, the
command may not actually exceed the channel’s limits when the drive file is
played out. However, the message is intended to warn you the potential exists
for driving a channel outside its limits.

252 Command Processes MTS MultiPurpose TestWare®

 Model 793.71/72 Time History Output Process

Mapping tab Important If you map an RPC Pro drive file (.seq) channel to a station channel
that supports mode switching, and the drive file units for that
channel are "%" (indicating normalized units), the file will not play
out.

Mapping Tab (part 1 of 2)

ITEM DESCRIPTION
File Channel/ File Channel selects the file channel’s number. The Descriptor and Full Scale
Descriptor/Full Scale values are updated with the file header values for the selected file channel. The
values are updated as you change the selected file channel. When you change
the file channel selection, the application shows the currently selected station
channel, control mode, and units to be used so that the data can be converted
into the station channel’s system units.
Station Channel Selects the station channel associated with the selected file channel. When a
drive file is read, the application looks to see if the file channel’s descriptor
matches the name of a station channel. If it does, the application maps that file
channel to the matching station channel.
Control Mode Selects the control mode associated with the selected station channel. By
default, for each file channel the application selects the first control mode
available for the associated station channel. This defines the dimension of the
signal. By default, the units for the selected control mode’s signal will be the
calibrated units defined in Station Manager. However, when the application
parses the requested drive file’s header, if the application finds that the
channel’s unit descriptor matches one of the units available for that dimension,
the application will select those units.
Channel Units Selects the units associated with the selected file channel.

MTS MultiPurpose TestWare® Command Processes 253

Model 793.71/72 Time History Output Process

Mapping Tab (part 2 of 2)

ITEM DESCRIPTION
Enable AIC Enables the Adaptive Inverse Control (AIC) compensation method for all
Compensators control channels that will support it. This box is available when the file has
been entered, a valid channel map exists, and at least one of the selected
channels supports AIC Compensation (which is done in Station Builder—see
the Edit Control Channels section for Station Builder in the MTS 793 Control
Software manual).
Note This compensation method will not optimize signals with frequency
content above 128Hz. Therefore, this process will not allow AIC to be
enabled if the sampling rate of the time histories exceed 256Hz.

Important The use of the AICX compensator can introduce large delays
between generated command and command to the actuator.
The delay is dependant on the tuning of AICX and is two times
the value of the Impulse Response.

Status Displays messages about channel mapping and full-scale status after the
application checks the mapping and unit selections on the Mapping tab. These
messages are updated each time the user modifies the channel, mode, or unit
selection in the Mapping tab.
The application will ensure that no two file channels are mapped to the same
station channel. When the check is complete, the application will display either
“Invalid Channel Map” or “Valid Channel Map.” The process cannot be run
with an invalid channel map.
If the mapping is valid, the application checks full scales of each channel in the
file against the range of the selected control mode for each channel. The
message “Full Scales Outside Limits” or “Full Scales Inside Limits” will
display the results. If the mapping is bad, the outside limits text will display.
The valid/invalid channel map message and full scale in/outside limits
messages reflect the validity of the channel mapping and the comparison of
each file channel’s full scale versus the station channel’s full scale.

254 Command Processes MTS MultiPurpose TestWare®

 Model 793.71/72 Time History Output Process

Actions tab
Action Tab
ITEM DESCRIPTION
Name Displays the names of the time triggers in the time history file.
Each time trigger name references a specific identification number (multiple
triggers can reference the same identification number). The identification
number locates a particular point in the data at which an associated system
action should occur. The Time History Output process displays all of the
unique time trigger names in the time history file (or in all of the time histories
of a road surface file).
The name of each time trigger is assigned by MTS RPC software. You can
refer to the assigned time trigger names when assigning actions to them.
Action Use the Action list to assign a Station Manager action or action group to each
time trigger in the sequence. When MPT runs a Time History Output process
and trips a time trigger, it initiates the action sequence.

Note Default actions (Indicate, Station Power Off, Interlock, Program

Interlock, Program Stop, and Program Hold) are not available. You
must assign custom actions (created with Station Manager’s Event-
Action Editor) specifically created for the time triggers. A typical
custom action would be to set or clear a digital output.

MTS MultiPurpose TestWare® Command Processes 255

Model 793.71/72 Time History Output Process

Acquisition tab Note This tab appears only if you have purchased the data acquisition option
of the Time History Output process (Model 793.72).

Acquisition Tab
ITEM DESCRIPTION
Number of Channels Specifies the number of channels on which data is acquired and formatted. The
default number is zero.
Directory Specifies the directory in which the response file (.rsp) will be saved. With the
Specify File Destination selection, you can specify a path for the response
file. The Use Specimen Directory selection saves the response file in the
specimen directory. The default name of the response file is “new.rsp”—type
the desired file name in place of “new.”
Response File The process stores digitized response test data in a response file. If the
(file icon) Directory selection is Specify File Destination, the Response File file icon
will be active. Click the file icon to open the Select response file window. Use
the window to select a current response file, save a new response file, and
specify the path.
Output File Channel Specifies the output file channel.
Station Signal Specifies the station signal associated with the selected output file channel.
Channel Descriptor Specifies a descriptor for the selected output file channel that will be stored in
the files header. The default entry is the station signal name.

Note If you are executing a Time History Output process that includes data
acquisition, and you hold and resume a test, there will be slight
differences between the digitized response and the response you would
have seen if the test had run without holding.These differences should
not be statistically significant.

256 Command Processes MTS MultiPurpose TestWare®

 Model 793.71/72 Time History Output Process

Trend tab Note This tab appears only if you have purchased the data acquisition option
of the Time History Output process (Model 793.72).

Trend Tab
ITEM DESCRIPTION
Support Trend Enables MPT to acquire and store trend response data. This data can be used
Response Files by the RPC III application to show changes that occurred in the specimen over
the course of the test.
Passes Per Trend Specifies the number of passes the drive file will play out before a trend
Response response file is stored.
Trend Response File Specifies the root of trend response file names.
Name Root
Trend response files are stored in the same folder as the response file defined
on the Acquisition tab. When the first response file is saved, it is named your
root name000.rsp. Subsequent response files are named your root
name001.rsp, your root name002.rsp, your root name003.rsp, and so on.

Status tab
Status Tab
ITEM DESCRIPTION
Show Status Panel at Check this box to make a status panel appear in the MPT control panel when
Run Time this process runs. The status panel displays the progress of the process
execution. If you do not enable the Show Distance Traveled checkbox, the
status panel will display process progress in terms of Elapsed Time, Total
Time (target time), and Percent Completed.
Show Distance Check this box to make the status panel display process progress in terms of
Traveled/Vehicle Distance, Total Distance (target distance), and Percent Completed.
Speed
Checking this box enables the Vehicle Speed control.
Vehicle Speed Lets you enter a velocity for the vehicle. The distance displayed on the status
panel is calculated from the process’ running time.

MTS MultiPurpose TestWare® Command Processes 257

Model 793.71/72 Time History Output Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

How to Define a Time History Output Process

1. Drag the icon from the Process Palette to your group or procedure
table.

2. Click the process icon in your group or procedure table, or navigation pane.

3. In the parameters window, click the Command tab.

4. Click the Drive File button to open the Select drive file window. Click the
desired drive file, and then click Open.

5. In the Passes box, type of number of passes you want the drive file to make.

6. Optional—Select Relative Time Signal if you want to enable a relative

(instead of absolute) time signal.

7. Optional—Select Drive has an offset if you want the process to run the
offset in the drive file.

8. Click the Mapping tab.

258 Command Processes MTS MultiPurpose TestWare®

 Model 793.71/72 Time History Output Process

9. Use the File Channel and Station Channel lists to map the drive file
channels to the appropriate station channels. Set the Control Mode and
Channel Units as needed.

10. Optional—Select Enable AIC Compensators.

Note The Acquisition and Trend tabs apply only if you have the data
acquisition option for the Time History Output process.

11. Click the Status tab.

12. Optional—Select Show Status Panel at Run Time if you want the Time
History Output Status Window to display when this process is active.

13. Click the Acquisition tab.

14. In the Number of Channels list, type the number of channels you want to
take data on and press Enter.

15. Use the Directory control to specify the directory in which the response file
(.rsp) will be saved. With the Specify File Destination selection you can
specify a path for the response file. The Use Specimen Directory selection
saves the response file in the specimen directory.

16. If you have selected Specify File Destination in the previous step, you can
click the Response File file icon to open the Select response file window.
Use this window to select the file and directory in which you wish to save
response data.

17. In the Channel 1 Signal list, click the signal to be monitored. (You can type
a descriptor in the Channel Descriptor box.)

18. In the Output File Channel list, click the first channel.

19. Perform steps 17 and 18 for any additional channels.

20. Click the Trend tab.

21. Optional—Select Support Trend Response Files if you want to store trend
data for use with the RPC application.

If you select Support Trend Response Files:

A. In the Passes Per Trend Response box, type the number of passes you
want to play out before you save trend data.

B. In the Trend Responses File Name Root box, type the root name for
your trend response files.

22. Click the Actions tab.

MTS MultiPurpose TestWare® Command Processes 259

Model 793.71/72 Time History Output Process

23. Optional—Map station actions to drive file sequences.

24. Click the General tab.

25. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

26. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

27. In the Execute Process box, type the number of times you want the process
to run.

28. Optional—In the Counter Type list, click a counter type.

29. Optional—If you enabled a counter, type a Counter Label.

30. Set the desired Start and Interrupt signals for the process in the group or
procedure table.

260 Command Processes MTS MultiPurpose TestWare®

 Road Surface Output Process

Road Surface Output Process

About the Road Surface Output Process
Note This process will not operate properly on a station configuration that uses
the decimal clock mode in its associated hardware interface file. For
proper operation, this process requires a station configuration that uses
a binary clock mode. For more information, see the MTS Series 793
Software Utility manual (part number 100-147-132).

The Road Surface Output process lets you drive a station with RPC III and
RPC Pro Road Surface files (files with extensions drv or seq)

Note The Road Surface Output process is optional. You must type a special
key code during installation to enable this process.

About Road Surface Files

A Road Surface file is a file that you create with RPC software. It consists of a
list of time history files and other Road Surface files. Each file can have a
different number of channels.

Creating road surface A Road Surface file is created by the RPC RSURF program or RPC Pro. It lets
files you enter up to 30 file names in one Road Surface file. The order in which files
are listed determines the order in which they are played out. For example, if files
A, B, and C are entered in the list in alphabetical order and each file has two
passes, the files are played out as follows:

Pass 1 of each file

AABBCC ROAD1.DRVRS
Road Surface file

Pass 2 of each file

MTS MultiPurpose TestWare® Command Processes 261

Road Surface Output Process

With RSURF you can nest files up to four levels. The following diagram shows
two levels of nesting. Files A, B, and C make up a Road Surface file named
“ROAD1.DRVRS.” The level 2 drive Road Surface file,
“NESTEDROADS.DRVRS”, contains four passes of ROAD1.DRVRS.

.
ROAD1.DRVRS Road Surface file
is played out four times

Pass 1 of Pass 2 of Pass 3 of Pass 4 of

Road Road Road Road
Surface file Surface file Surface file Surface file

AABBCC AABBCC AABBCC AABBCC

NESTEDROADS.DRVRS drive road surface

You can nest a Road Surface file inside three other Road Surface files to produce
a complex Road Surface file of drive files. For example, in the following
diagram, R4.DRVRS is nested in Road Surface files R3.DRVRS, R2.DRVRS,
and R1.DRVRS:

R1.DRVRS

A.DRIV R2.DRVRS

R2.DRVRS C.DRIV
R3.DRVRS R4.DRVRS
B.DRIV R3.DRVRS R4.DRVRS A.DRIV

D.DRIV E.DRIV D.DRIV

F.DRIV

Road Surface Output Status Panel

During a test, the Road Surface Output Status panel displays on the MPT
control panel. The status panel appears when you lock the procedure. Also, the
sequence counter on the MPT control panel displays all files within the drv file,
and indicates the active file.

262 Command Processes MTS MultiPurpose TestWare®

 Road Surface Output Process

Road Surface Output Parameter Descriptions

Command tab
Command Tab (part 1 of 2)
ITEM DESCRIPTION
Road Surface File Note Playout of RPC drive files at 128 Hz requires a system rate of 1024 Hz.

Note For controllers equipped with MTS Series 494 hardware, playout of
RPC drive files at 409.6 Hz requires a system rate of 2048 Hz or 4096
Hz. Controllers equipped with MTS Series 494 hardware do not
support playout of RPC drive files as 409.6 Hz with a system rate of
1024 Hz.

Selects an RPC III or RPC Pro Road Surface file to play out.
When you have selected a file, the application:
• Verifies that it is a file it can read.
Important If you map an RPC Pro drive file (.seq) channel to a station
channel that supports mode switching, and the drive file units for
that channel are "%" (indicating normalized units), the file will not
play out.

• Reads in the file.

• Reads in the headers of all time history files specified in the Road Surface
file and any nested road surface files.

• Ensures that the number of channels in each drive file is not greater than
the number of channels in the station.

• Ensures that the sampling rate is supported.

• Ensures that the sampling rate and the channel calibrations (values and
units) are consistent between all drive files.

If any of these steps fail, a message will display the problem. If no problem
exists, the application will attempt to map the file’s channels to the station’s
channels. Next, the application checks for conflicts.
Passes Selects the number of passes the Road Surface file will play out each time the
process runs, as specified on the General tab.

MTS MultiPurpose TestWare® Command Processes 263

Road Surface Output Process

Command Tab (part 2 of 2)

ITEM DESCRIPTION
Relative Time Signal If selected, the process reads the current command value on each channel when
the process runs. These commands are added to each point in the time history
as it is read from its file. and the modified command is played out. With this
feature you can preload a channel and then play out the time history relative to
that preloaded value. If not checked, the time history will be played out as
stored in the disk file.
Drive has an offset When enabled and relative mode is not selected, the process will start by
ramping to the first command point in the time history, and end at the last
command point in the time history, without returning to zero.
When enabled and relative mode is selected, the process will start by ramping
to the first command point in the time history, and will end by returning to the
starting point after the last specified pass is completed.

Note The command signal will not return to zero (or to the starting point in
relative mode) between files in the sequence, but will transition directly
between the last command point of one drive file and the first
command point of the following drive file.

Status Displays messages about channel mapping and full-scale status after the
application checks the mapping and unit selections on the Mapping tab. These
messages are updated each time the user modifies the channel, mode, or unit
selection on the Mapping tab. The application will ensure that no two file
channels are mapped to the same station channel. When the check is complete,
the application will display either “Invalid Channel Map” or “Valid Channel
Map.” The process cannot be run with an invalid channel map.
If the mapping is valid, the application checks full scales of each channel in the
file against the range of the selected control mode for each channel. The
message “Full Scales Outside Limits” or “Full Scales in Limits” will display
the results. If the mapping is bad, the outside limits text will display.
The valid/invalid channel map message and full scale in/outside limits
messages reflect the validity of the channel mapping and the comparison of
each file channel’s full scale versus the station channel’s full scale.

264 Command Processes MTS MultiPurpose TestWare®

 Road Surface Output Process

Mapping tab
Mapping Tab (part 1 of 2)
ITEM DESCRIPTION
File Channel/ File Channel selects the file channel’s number. The Descriptor and Full Scale
Descriptor/Full Scale values are updated with the file header values for the selected file channel. The
values are updated as you change the selected file channel. When you change
the file channel selection, the application shows the currently selected station
channel, control mode, and units to be used so that the data can be converted
into the station channel’s system units.
Station Channel Selects the station channel associated with the selected file channel. When a
drive file is read, the application looks to see if the file channel’s descriptor
matches the name of a station channel. If it does, the application maps that file
channel to the matching station channel.
Control Mode Selects the control mode associated with the selected station channel. By
default, for each file channel the application selects the first control mode
available for the associated station channel. This defines the dimension of the
signal. By default, the units for the selected control mode’s signal will be the
calibrated units defined in Station Manager. However, when the application
parses the requested drive file’s header, if the application finds that the
channel’s unit descriptor matches one of the units available for that dimension,
the application will select those units.
Channel Units Selects the units associated with the selected file channel.

MTS MultiPurpose TestWare® Command Processes 265

Road Surface Output Process

Mapping Tab (part 2 of 2)

ITEM DESCRIPTION
Enable AIC Enables the Adaptive Inverse Control (AIC) compensation method for all
Compensators control channels that will support it. This box is available when the file has
been entered, a valid channel map exists, and at least one of the selected
channels supports AIC Compensation (which is done in Station Builder—see
the Edit Control Channels section for Station Builder in the MTS 793 Control
Software manual).
Note This compensation method will not optimize signals with frequency
content above 128Hz. Therefore, this process will not allow AIC to be
enabled if the sampling rate of the time histories exceed 256Hz.

Important The use of the AICX compensator can introduce large delays
between generated command and command to the actuator.
The delay is dependant on the tuning of AICX and is two times
the value of the Impulse Response.

Status Displays messages about channel mapping and full-scale status after the
application checks the mapping and unit selections on the Mapping tab. These
messages are updated each time the user modifies the channel, mode, or unit
selection in the Mapping tab.
The application will ensure that no two file channels are mapped to the same
station channel. When the check is complete, the application will display either
“Invalid Channel Map” or “Valid Channel Map.” The process cannot be run
with an invalid channel map.
If the mapping is valid, the application checks full scales of each channel in the
file against the range of the selected control mode for each channel. The
message “Full Scales Outside Limits” or “Full Scales Inside Limits” will
display the results. If the mapping is bad, the outside limits text will display.
The valid/invalid channel map message and full scale in/outside limits
messages reflect the validity of the channel mapping and the comparison of
each file channel’s full scale versus the station channel’s full scale.

266 Command Processes MTS MultiPurpose TestWare®

 Road Surface Output Process

Actions tab
Action Tab
ITEM DESCRIPTION
Name Displays the names of the time triggers in the time history file.
Each time trigger name references a specific identification number (multiple
triggers can reference the same identification number). The identification
number locates a particular point in the data at which an associated system
action should occur. The Time History Output process displays all of the
unique time trigger names in the time history file (or in all of the time histories
of a road surface file).
The name of each time trigger is assigned by MTS RPC software. You can
refer to the assigned time trigger names when assigning actions to them.
Action Use the Action list to assign a Station Manager action or action group to each
time trigger in the sequence. When MPT runs a Time History Output process
and trips a time trigger, it initiates the action sequence.

Note Default actions (Indicate, Station Power Off, Interlock, Program

Interlock, Program Stop, and Program Hold) are not available. You
must assign custom actions (created with Station Manager’s Event-
Action Editor) specifically created for the time triggers. A typical
custom action would be to set or clear a digital output.

Status tab
Status Tab
ITEM DESCRIPTION
Show Status Panel at Check this box to make a status panel appear in the MPT control panel when
Run Time this process runs. The status panel displays the progress of the process
execution. If you do not enable the Show Distance Traveled checkbox, the
status panel will display process progress in terms of Elapsed Time, Total
Time (target time), and Percent Completed.
Show Distance Check this box to make the status panel display process progress in terms of
Traveled/Vehicle Distance, Total Distance (target distance), and Percent Completed.
Speed
Checking this box enables the Vehicle Speed control.
Vehicle Speed Lets you type a velocity for the vehicle. The distance displayed on the status
panel is calculated from the process’ running time.

MTS MultiPurpose TestWare® Command Processes 267

Road Surface Output Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

How to Define a Road Surface Output Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in your procedure table or navigation pane.

3. Click the Command tab.

4. Click the Road Surface File button to open the Select Road Surface file
window. Click the desired drive file, and then click Open.

5. In the Passes box, type the number of passes you want the drive file to
make.

6. Optional—Select Relative Time Signal if you want to enable a relative

(instead of absolute) time signal.

7. Optional—Select Drive has an offset if you want the process to execute the
offset in the drive file.

8. Click the Mapping tab.

268 Command Processes MTS MultiPurpose TestWare®

 Road Surface Output Process

9. Use the File Channel and Station Channel lists to map the drive file
channels to the appropriate station channels. Set the Control Mode and
Channel Units as needed.

10. Optional—Select Enable AIC Compensators.

11. Click the Actions tab.

12. Optional—Map station actions to drive file sequences.

13. Click on the Status tab.

14. Optional—Select Show Status Panel at Run Time if you want the Road
Surface Output Status Panel to display when this process is active.

15. Click the General tab.

16. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

17. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

18. In the Execute Process box, type the number of times you want the process
to execute.

19. Optional—In the Counter Type list, click a counter type.

20. Optional—If you enabled a counter, type a Counter Label.

21. Set the desired Start and Interrupt signals for the process.

MTS MultiPurpose TestWare® Command Processes 269

Road Surface Output Process

270 Command Processes MTS MultiPurpose TestWare®

Chapter 13
Data Acquisition Process Descriptions
Use data acquisition processes to acquire sensor data from the physical specimen
during testing.

You must sequence this process in parallel with command processes. Meaningful
data cannot be acquired unless the command process is performing an action that
can be measured.

Data Acquisition Process Types

ICON PROCESS NAME DESCRIPTION
Peak/Valley Acquisition Records the peak/valley data for each cycle execution.
Process

Timed Acquisition Process Records data at user-specified time intervals.

Max/Min Acquisition Process Records data at the highest peak and lowest valley during the life
of the process.
Level Crossing Acquisition Records data each time the selected signal changes by a specified
Process amount.
High Speed Timed Records bursts of data at a high rate.
Acquisition Process

Cyclic Acquisition Process Records timed, level crossing, interleaved timed and level
crossing, or peak/valley data from cyclic feedback.
Fatigue Process Accumulates cycles in a histogram, then calculates damage based
on the data on that histogram. The damage number is also sent to
the Fatigue Monitoring application.
Time History Input Process Acquires and digitizes multiple channels of analog test response
data in the RPC III file format.
Trend Process Calculates statistical values on time series data. The values are then
stored to disk. It is also sent to the Trend Monitoring application.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 271

 Note There is a slight time delay between processes that start with a common
trigger (for example, two processes using the <Procedure>.Start trigger).
The process positioned the highest on the Procedure or Group table
starts first. When using data acquisition and command processes in
parallel, position the data acquisition process higher on the table than the
associated command process.

About Buffers
When you set up data acquisition, you specify the signals for which data is
acquired and the method of buffering.

Each type of buffer offers different operational characteristics:

• The buffer size specifies the maximum number of data elements the buffer
will store before data is written to disk. (A data element includes the data
from each selected signal.) You can set the buffer size between 1 and 16,000
data elements (default is 1024).

• Acquiring and saving data at fast rates can cause the computer to become
sluggish (slow to respond to selections). If the acquisition rates are too fast,
data over-run can occur. If this happens, the test stops and a message is
logged.

• Linear buffers can generate a Process.Buffer Full signal when the controller
acquires enough data elements to fill the specified buffer size. You can use
this buffer full signal to start or interrupt other processes in the procedure.

Linear buffer A linear buffer records data until it is full, then saves the data to disk. The size of
the buffer determines how much data is acquired before it is written to disk. Data
is continuously saved to disk until the process ends or is stopped. When the
process ends, any data in the buffer is sent to disk. The only limit is the size of
your hard drive.

Circular buffer A circular buffer records data continuously. When the buffer is full, new data
overwrites the oldest data. This type of buffering saves data to disk when the test
is stopped, when the process reaches its preset count, or when the process ends.
The circular buffer is useful for acquiring data just before some crucial event
(such as specimen failure), where data is not required for the whole test.

272 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

Data File Header
The first line of the data file includes information like the decimal separator,
column separator, time formats, date formats, and so forth.

A typical header looks like this:

MTS793|MPT|ENU|1|0|.|/|:|1|0|0|A
The format of this header line is as follows:

MTS793|progName|sLanguage|version|iDelim|sDecimal|sDate|sTime|iCountry|iDate|iTime|sCode
Where:
progName=MPT or BTW
sLanguage= Natural language (standard three-character abbreviation)
version=Version of this format string
iDelim=Data delimeter: 0 for space (plain), 1 for comma (Lotus), 2 for tab (Excel)
sDecimal=International decimal separator
sDate=International date separator
sTime=International time separator
iCountry=International country value
iDate=International date format
iTime=International time format
sCode=Character Set Code: A for ANSI, O for OEM (currently always A)

MPT generates a header for each data file buffer when the Write First Data
Header Only check box is disabled (unchecked). When the check box is
enabled, MPT suppresses all but the initial header.

Important You can use the Write First Data Header Only check box to
specify whether or not headers are written to the buffer subsequent
to the initial header. This option is provided as an aid to data
sorting and analysis and is only provided for the Peak/Valley,
Timed, Level Crossing, Cyclic Acquisition, and High Speed
Acquisition processes.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 273

How to Trigger a Process When the Buffer Is Full
By using the trigger or buffer full signal from one data acquisition process to start
another data acquisition process, you can acquire test data in very selective ways.

Example Suppose you want to create a procedure that will acquire 10 points of peak/valley
data every 100 cycles and store the data in a separate file in the Specimen. To do
this, you could create a procedure with a Level Crossing Data Acquisition
process, a Cyclic Command process, and a Peak/Valley Data Acquisition
process, as follows:

In this scenario, to ensure that the test ends properly, click Generate
Cycles.Done in the Procedure is done when box, or Generate Cycles.Done in
the Count Cycles process’ Interrupt box.

Here is how you would set up the processes:

1. Level Crossing Acquisition process (named “Count Cycles”):

– Master Signal: Ch 1 Count

– Level Increment: 1 cycle

– Total Samples: Continuous

– Buffer size: 100

– Destination: Discard data

2. Set up the Cyclic Command process (named “Generate Cycles”) to

generate 1000 cycles of the desired shape and at the desired amplitude and
frequency.

3. Peak/Valley Data Acquisition process (named “Acquire Data”):

– Master Signal: As desired

– Sensitivity: Appropriate for Master Signal (for example, 3mm)

– Total Samples: 10

– Signals: As desired

– Buffer size: 10

– Destination: User-specified data file

– User Data File: As desired

274 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 When you run this test, the Peak/Valley Data Acquisition process will be
triggered by the Count Cycles.Buffer Full signal generated by the Level Crossing
Data Acquisition process every 100 cycles, and will acquire 10 points of peak/
valley data. The data will be stored to the file (in the Specimen) entered in the
User Data File box on the Destination tab of the Peak/Valley Data Acquisition
Parameters window.

Data Destination
You set how your acquired data is saved on the Destination tab. The options are:

• Specimen data file

Acquired data is written to the specimen.dat file saved in your MPT

specimen.

MPT specimens are located in your MPT Specimens folder (MPT >
Specimens > spec01, spec02, and so forth).

• User-specified data file

Acquired data is written to the data file you specify (filename.dat) in the
MPT specimen.

• Discard data

Acquired data is written to the buffer, but is not saved to disk. Typically, this
option is used to trigger another process when the current acquisition
process fills its buffer.

For more information See “How to Trigger a Process When the Buffer Is Full” on page 274.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 275

About Station Signals
The following signals are available to the MultiPurpose TestWare acquisition
processes.

Note All time related signals (Time, Rollover Time, Running Time, and
Rollover Running Time) start from zero when you press the Run control
to start the test.

Station Signals (part 1 of 2)

ITEMITEM DESCRIDESCRIPTIONPTION

Time Records the time reference signal derived from the controller’s internal clock
which increments continually.
Note It is not practical to monitor the Time signal for some types of data
acquisition processes (for example, Peak/Valley).

Rollover Time Records the time reference signal derived from the controller’s internal clock
which resets every hour. Like the Time signal, this signal is not practical to
monitor for some types of data acquisition processes.
Running Time Records the accumulated time of the test program, which begins when you
press Run, and ends when the program stops automatically, or when you press
Hold or Stop. Pressing Run after pressing Stop or Hold causes this value to
resume incrementing.
Rollover Running Time

Similar to Rollover Time except it increments only while the station test state
is not in the stopped state.
Date Date is an integer number of days since Jan 0, 1900. Time of Day is a fraction
of a day since midnight. Both signals are float values that can be imported into
Time of Day Microsoft Excel, formatted as separate date and time columns, and added
together to form one date/time column. Both signal values correspond to time
stamps in the station log.
(Controller) System
Tick Count
Records the accumulated number of system ticks (updates) generated by the
controller (or multiple controllers in a multi-controller configuration) from the
time the Sysload application is started in the current session
System Tick Count is typically a large unitless integer. It can be used as a
reference if you acquire signals from other controllers. It can also be useful for
synchronizing acquired data for off-line plotting when using spreadsheet
applications, such as Microsoft Excel.

276 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Station Signals (part 2 of 2)
ITEMITEM DESCRIDESCRIPTIONPTION

Interlock, Run/Stop, Records the binary state of the control, in which 1 = on, and 0 = off (in the case
Hold, Program of Run/Stop, 1 = Run and 0 = Stop).
Interlock, HSM On,
HSM High The value reveals the state of the associated control when data is acquired. In
the case of Run/Stop and Hold signals, the values may not change state since
acquisition occurs only while the program is being run. These signals may be
useful in calculated signals.
(channel) Integer Records the number of segments played out in the selected channel.
Count
Note This signal measures the same value as (channel) Count, however, it
has greater resolution at higher segment counts (for instance, counts
greater than 16 million segments).

Note The count for a time history output increments once for each point in
the associated time history file.

(channel) Output Records the signal that goes to the valve driver.
(channel) Sensor Records various types of sensor feedback signals in engineering units. Force
signals and Displacement are typically sensor signals.
(channel) Count Records the number of segments played out in the selected channel.
Note This signal is displayed as a floating point number. Its resolution
decreases significantly at higher segment counts (for instance, counts
greater than 16 million segments).

(channel) Error Records the control mode error signal in engineering units. This signal shows
the difference between the Channel Name Command and the Channel Name
Control Mode Name signals.
(channel) Abs. Error Records the absolute value of the Error signal in engineering units. Absolute
means negative becomes positive and positive remains positive. This signal is
always positive.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 277

 Time and Rollover Time and Running Time signals are useful for recording the duration of tests.
Time signals They may also be useful for providing a time reference for data acquisition for
tests of short duration. However, as the length of a test increases, their suitability
as a time reference for data acquisition decreases. This is because Time and
Running Time are floating point numbers, and their resolution decreases as they
increase in value.

For instance, when the Time signal runs continuously for approximately six
months (224, or 16,777,216 seconds), its resolution drops to one second—which
is far too course to be used as a time reference at typical data acquisition rates.

To obtain a time reference with suitable resolution for longer tests, use Rollover
Time or Running Rollover Time. These signals are also floating point numbers,
but they rollover (reset to zero) every hour (3600 seconds). This maintains a high
resolution with respect to typical data acquisition rates. However, because
Rollover Time and Running Rollover Time reset to zero every hour, they lose
reference to where they occur within the test.

It is possible to obtain a composite time reference that has the desirable

characteristics of both Time and Rollover Time. To do this, select both types of
signals for the data acquisition process (Time and Rollover Time), run the test,
then open the data file in a spreadsheet application, such as Microsoft Excel.

Next, use the spreadsheet application’s math functions to derive a new column
derived from the Time and Rollover Time values in each row, as follows:

composite time = INT(Time/3600) x 3600 + Rollover Time

Where INT (Microsoft Excel syntax) rounds down the result of Time divided by
3600 to the nearest integer.

278 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Peak/Valley Acquisition Process

Peak/Valley Acquisition Process

About Peak/Valley Process
The Peak/Valley Acquisition process records the output of all selected signals
when the software detects a peak or valley in the master signal you specify.

When you define a Peak/Valley Acquisition process, you must define the master
signal, the sensitivity, the signals you will record data on, the data destination, the
buffer type, and the output units.

Acquired Data Points

Sensor
Signal

Time

Sensitivity A sensitivity value specifies how much the master signal must change to detect a
peak or valley:

• Setting the sensitivity too low may cause signal noise to be recognized as
peaks and valleys.

• Setting the sensitivity too high may cause low amplitude signals to be
missed.

Detected
Peaks

Sensitivity =

Detected
Valleys

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 279

Peak/Valley Acquisition Process

Peak/Valley Acquisition Parameter Descriptions

Acquisition tab
Acquisition Tab
ITEM DESCRIPTION
Master Signal Specifies the signal that is monitored by the peak/valley detector.
Sensitivity Defines how much the signal must change before a level is considered a peak
or valley.
Total Samples Specifies the number of samples the process will acquire before it completes.
Note If disabled, samples will be taken as long as the process is active.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

Signals Tab Selects signals from which this process acquires data. Use the left and right
arrows to move desired signals from the Available list to the Included list.

Note The order of the signals in the Included list determines the order of the
columns of data in your data file. Use the up and down arrows to arrange
signals in the desired order.

280 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Peak/Valley Acquisition Process

List Filter With the List Filter, you can pare the list of Available signals according to text
you type in the entry box. Type text that describes the signal(s) you wish to
display.

For example, typing force displays all signals that include “force” in their labels.
You can also type a part of a signal description to display a signal type. For
example, to display displacement signals, you can type disp rather than
“displacement”.

Destination tab
Destination Tab
ITEM DESCRIPTION
Buffer Size Specifies the maximum number of data elements the buffer will store before
data is written to the disk.
Data Header Includes a label that describes the data on each buffer that is written to a file.
Destination Specifies where data is saved:
Specimen data file—the process writes buffers of data to the MPT
specimen.dat file in the Specimen.
User-specified data file—the process writes buffers of data to a separate data
file in the Specimen (yourname.dat).
Discard data—the process will not write data to the Specimen.
User Data File Specifies the name of the file where data is saved. This lets you create separate
data files in the MPT specimen. This control is enabled only when you have
selected User-specified data file in the Destination list above.
Buffer Type Specifies the buffer type.
Write First Data Header Specifies if the data header is written for each buffer or suppressed after the
Only first header is written. If disabled (unchecked), a data header is written for each
buffer.
Note This feature is not recommended for procedures with multiple data
acquisition processes writing data to the same data file.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 281

Peak/Valley Acquisition Process

Output units tab

Output Units Tab
ITEM DESCRIPTION
UAS Specifies the unit assignment set that will be applied to acquired data.
Select Other Displays other existing unit assignment sets from which you can choose a
UAS. This button is enabled only when you select the Other Unit Assignment
Set option.
Edit Opens the Unit Assignment Set Editor so you can modify a unit assignment
set.

For more information See “About Buffers” on page 272.

See “About Station Signals” on page 276.

How to Define a Peak/Valley Acquisition Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in the procedure table or navigation pane.

3. In the parameters window, click the Acquisition tab.

4. In the Master Signal list, click the signal you want to monitor with this
process.

5. In the Sensitivity box, set the units, and then type a value.

6. Optional—If you want to specify the number of samples to be acquired,

select the Total Samples box. Otherwise it will acquire data as long as the
process is active.

7. Click the Signals tab.

8. Move all the signals you want to monitor to the Included list. Move all the
others to the Available list.
Note The order of the signals in the Included list determines the order of the
columns of data in your data file.

9. Click the Destination tab.

10. Type the Buffer Size and type a description of the data file in the Data
Header box.

282 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Peak/Valley Acquisition Process

11. In the Destination list, click the destination for the acquired data. (If you
click User-specified data file, type a file name in the User Data File box.)

12. In the Buffer Type list, click the buffer type.

13. Optional—If desired, enable Write First Data Header Only checkbox.
This feature aids data sorting and analysis.

14. Optional—Click the Output Units tab.

Change the unit assignment set if you want. Each data acquisition process
can use a different unit assignment set.

15. Click the General tab.

16. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

17. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

18. In the Execute Process box, type the number of times you want the process
to run.

19. Optional—In the Counter Type list, click a counter type.

20. Optional—If you enabled a counter, type a Counter Label.

21. Set the desired Start and Interrupt signals for the process in the procedure
table.

For more information See “Data Destination” on page 275.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 283

Timed Acquisition Process

Timed Acquisition Process

About the Timed Acquisition Process
The Timed Acquisition process records the output of all selected signals at the
specified time interval or sample rate.

When you define a Timed Acquisition process, you can define the time between
samples (shown below) or type a sample rate frequency.

Data Points
Data Points

Time Intervals

Timed Acquisition Parameter Descriptions

Acquisition tab
Acquisition Tab
ITEM DESCRIPTION
Time Between Points Specifies the time interval between data acquisitions.
Note When you type a time increment, the MPT application may change
your entry slightly to reflect your controller’s clock rate.

Sample Rate Specifies the sample rate frequency for data acquisition.
Note MPT may change the entered frequency slightly to reflect the
resolution of your controller’s system clock rate. For instance, if you
type in “1000 Hz” and press the enter key, MPT may change the
number to 1024 Hz.

Total Samples Specifies the number of samples the process will acquire before it completes.
Sampling Duration Specifies the length of time the process will attempt to acquire data.
Continuous Sampling Causes the process to acquire samples continuously until it is interrupted.

284 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Timed Acquisition Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

Signals tab Selects signals from which this process acquires data. Use the left and right
arrows to move desired signals from the Available list to the Included list.

Note The order of the signals in the Included list determines the order of the
columns of data in your data file. Use the up and down arrows to arrange
signals in the desired order.

List Filter With the List Filter, you can pare the list of Available signals according to text
you type in the entry box. Type text that describes the signal(s) you wish to
display.

For example, typing force displays all signals that include “force” in their labels.
You can also type a part of a signal description to display a signal type. For
example, to display displacement signals, you can type disp rather than
“displacement”.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 285

Timed Acquisition Process

Destination tab
Destination Tab
ITEM DESCRIPTION
Buffer Size Specifies the maximum number of data elements the buffer will store before
data is written to the disk.
Data Header Includes a label that describes the data on each buffer that is written to a file.
Destination Specifies where data is saved:
Specimen data file—the process writes buffers of data to the MPT
specimen.dat file in the Specimen.
User-specified data file—the process writes buffers of data to a separate data
file in the Specimen (yourname.dat).
Discard data—the process will not write data to the Specimen.
User Data File Specifies the name of the file where data is saved. This lets you create separate
data files in the MPT specimen. This control is enabled only when you have
selected User-specified data file in the Destination list above.
Buffer Type Specifies the buffer type.
Write First Data Header Specifies if the data header is written for each buffer or suppressed after the
Only first header is written. If disabled (unchecked), a data header is written for each
buffer.
Note This feature is not recommended for procedures with multiple data
acquisition processes writing data to the same data file.

Output units tab

Output Units Tab
ITEM DESCRIPTION
UAS Specifies the unit assignment set that will be applied to acquired data.
Select Other Displays other existing unit assignment sets from which you can choose a
UAS. This button is enabled only when you select the Other Unit Assignment
Set option.
Edit Opens the Unit Assignment Set Editor so you can modify a unit assignment
set.

For more information See “About Buffers” on page 272.

286 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Timed Acquisition Process

See “About Station Signals” on page 276.

How to Define a Timed Acquisition Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in the procedure table or in the navigation pane.

3. In the parameters window, click the Acquisition tab.

4. Set the timed data acquisition interval and units using Time Between Points
or type a Sample Rate frequency.
Note When you enter a time increment, the MPT application may change your
entry slightly to reflect your controller’s clock rate.

Note MPT may change the entered sample rate frequency slightly to reflect
the resolution of your controller’s system clock rate. For instance, if you
type in “1000 Hz” and press the enter key, MPT may change the number
to 1024 Hz.

5. If you want to:

• Cause the process to acquire samples continuously until it is

interrupted, select Continuous Sampling (default selection).

• Specify the number of samples to be acquired, select the Total

Samples, then type the number of samples desired.

• Specify the length of time the process will attempt to acquire data,
select Sampling Duration, then type the time over which you wish to
acquire data.

6. Click the Signals tab.

7. Move all the signals you want to monitor to the Included list. Move all the
others to the Available list.
Note The order of the signals in the Included list determines the order of the
columns of data in your data file.

8. Click the Destination tab.

9. Type the Buffer Size and type a description of the data file in the Data
Header box.

10. In the Destination list, click the destination for the acquired data. (If you
click User-specified data file, type a file name in the User Data File box.)

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 287

Timed Acquisition Process

11. In the Buffer Type list, click the buffer type.

12. Optional—If desired, enable Write First Data Header Only checkbox.
This feature aids data sorting and analysis.

13. Optional—Click the Output Units tab.

Change the unit assignment set if you want. Each data acquisition process
can use a different unit assignment set.

14. Click the General tab.

15. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

16. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

17. In the Execute Process box, type the number of times you want the process
to run.

18. Optional—In the Counter Type list, click a counter type.

19. Optional—If you enabled a counter, type a Counter Label.

20. Set the desired Start and Interrupt signals for the process in the procedure
table.

For more information See “Data Destination” on page 275.

288 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Max/Min Acquisition Process

Max/Min Acquisition Process

About the Max/Min Acquisition Process
The Max/Min Acquisition process records the maximum and minimum values of
selected signals during a test.

You can configure this process to monitor selected signals for their maximum
and minimum values. When the maximum and minimum values are detected,
they are compared to the maximum and minimum values currently stored for the
associated signals. If the new values exceed the stored values, they replace the
stored values.

You can also configure this process to monitor a master signal for maximum or
minimum values. When the maximum and minimum values are detected, the
process samples the values of the other selected signals. When data is written to
disk, the master signal values are absolute maximum and minimum values, while
the other selected signals reflect their values at the time the master signal’s
maximum and minimum values were detected.

Keep in mind that this process writes data to disk when:

• The procedure ends normally.

• The procedure is stopped.

• The process is interrupted.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 289

Max/Min Acquisition Process

Max/Min Acquisition Parameter Descriptions

Acquisition tab
Acquisition Tab
ITEM DESCRIPTION
Master Signal Specifies the signals that are monitored by the max/min detector.
When you select All Included Signals (default), the process monitors all
included signals for their maximum and minimum values (as selected). When
detected, the process compares them to the maximum and minimum values
currently stored. If the new values exceed the stored values, they take their
place.

When you select an individual master signal, the process monitors the signal
for its maximum and minimum values (as selected). When detected, the
process samples the values of the other included signals. When data is written
to disk, the master signal values are absolute maximum and minimum values,
while the other included signals reflect their values at the time the master
signal’s maximum and minimum values were detected.
Maximum Values Causes the process to monitor the master signal selection for maximum values.
Minimum Values Causes the process to monitor the master signal selection for minimum values.

290 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Max/Min Acquisition Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

Signals Tab Selects signals from which this process acquires data. Use the left and right
arrows to move desired signals from the Available list to the Included list.

Note The order of the signals in the Included list determines the order of the
columns of data in your data file. Use the up and down arrows to arrange
signals in the desired order.

List Filter With the List Filter, you can pare the list of Available signals according to text
you type in the entry box. Type text that describes the signal(s) you wish to
display.

For example, typing force displays all signals that include “force” in their labels.
You can also type a part of a signal description to display a signal type. For
example, to display displacement signals, you can type disp rather than
“displacement”.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 291

Max/Min Acquisition Process

Destination tab
Destination Tab
ITEM DESCRIPTION
Buffer Size Specifies the maximum number of data elements the buffer will store before
data is written to the disk.
Data Header Includes a label that describes the data on each buffer that is written to a file.
Destination Specifies where data is saved:
Specimen data file—the process writes buffers of data to the MPT
specimen.dat file in the Specimen.
User-specified data file—the process writes buffers of data to a separate data
file in the Specimen (yourname.dat).
Discard data—the process will not write data to the Specimen.
User Data File Specifies the name of the file where data is saved. This lets you create separate
data files in the MPT specimen. This control is enabled only when you have
selected User-specified data file in the Destination list above.
Buffer Type Specifies the buffer type.
Write First Data Header Specifies if the data header is written for each buffer or suppressed after the
Only first header is written. If disabled (unchecked), a data header is written for each
buffer.
Note This feature is not recommended for procedures with multiple data
acquisition processes writing data to the same data file.

Note Buffer settings, Discard Data options, and Write First Data Header Only
options are not available for the Max/Min Acquisition process.

Output Units Tab

Output Units Tab
ITEM DESCRIPTION
UAS Specifies the unit assignment set that will be applied to acquired data.
Select Other Displays other existing unit assignment sets from which you can choose a
UAS. This button is enabled only when you select the Other Unit Assignment
Set option.
Edit Opens the Unit Assignment Set Editor so you can modify a unit assignment
set.

292 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Max/Min Acquisition Process

For more information See “About Buffers” on page 272.

See “About Station Signals” on page 276.

More About the Max/Min Acquisition Process

The data recorded by the Max/Min Acquisition process is the minimum and
maximum values detected since the process was first activated, no matter how
many times the test is stopped. If the test stops (for any reason) before it has run
to completion, the data recorded will still be the highest and lowest values
detected throughout the entire run portion of the test.

If you want the max/min values for a phase of the test, use a different Max/Min
Acquisition process for each phase. Or, you could put a Max/Min Acquisition
process in a repeated Group process. Design it so the Group process ends every
time a stop occurs, using a Program Event process.

A Group process is set up

to run indefinitely. A large
number in the Execute
Process box causes the
Group process to loop
indefinitely until the
procedure is finished.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 293

Max/Min Acquisition Process

A Program Event process (within the Group process) monitors the test for a Stop event.

A Max/Min Acquisition process (within the The Group process will be done when the Program
Group process) will record max/min values Event process signals that it has detected a Stop. The
detected from the time you click Run until you Group process will run indefinitely, recording max/min
press Stop, or until the test is completed. values whenever a Stop is detected, until the procedure
is completed.

How to Define a Max/Min Acquisition Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in the procedure table or in the navigation pane.

3. Click the Acquisition tab.

4. Optional—Select a Master Signal, and then select whether you want to

monitor the master signal for Maximum or Minimum values.

5. Click the Signals tab.

6. Move all the signals you want to monitor to the Included list. Move all the
others to the Available list.
Note The order of the signals in the Included list determines the order of the
columns of data in your data file.

7. Click the Destination tab.

8. Type a description of the data file in the Data Header box.

9. In the Destination list, click the destination for the acquired data. (If you
click User-specified data file, type a file name in the User Data File box.)

294 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Max/Min Acquisition Process

10. Optional—Click the Output Units tab.

Change the unit assignment set if you want. Each data acquisition process
can use a different unit assignment set.

11. Click the General tab.

12. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

13. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

14. In the Execute Process box, type the number of times you want the process
to run.

15. Optional—In the Counter Type list, click a counter type.

16. Optional—If you enabled a counter, type a Counter Label.

17. Set the desired Start and Interrupt signals for the process in the procedure
table.

For more information See “Data Destination” on page 275.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 295

Level Crossing Acquisition Process

Level Crossing Acquisition Process

About the Level Crossing Acquisition Process
The Level Crossing Acquisition process records data each time the selected
master signal changes by a specific amount.

When you define a Level Crossing Acquisition process, you must define the
level increment at which data is collected.

Data Points
Level Increments

Data Points

Data is recorded each time the signal moves by the

specified level increment

Level crossing Assume you want to collect data every time the displacement changes 2
acquisition example millimeters. You would select the displacement feedback signal as your master
signal, and set the Level Increment to 2 mm.

Now, data will be recorded when the master signal reaches 2 mm, 4 mm, 6 mm,
and so on.

Note You should not set the level increment below the level of any signal
noise.

296 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Level Crossing Acquisition Process

Level Crossing Acquisition Parameter Descriptions

Acquisition tab
Acquisition Tab
ITEM DESCRIPTION
Master Signal Selects a signal that determines when data is acquired.
Level Increment Defines how much the signal must change before acquiring data.
Total Samples Specifies the number of samples the process will acquire before it completes.
Note If disabled, samples will be taken as long as the process is active.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

Signals Tab Selects signals from which this process acquires data. Use the left and right
arrows to move desired signals from the Available list to the Included list.

Note The order of the signals in the Included list determines the order of the
columns of data in your data file. Use the up and down arrows to arrange
signals in the desired order.

List Filter With the List Filter, you can pare the list of Available signals according to text
you type in the entry box. Type text that describes the signal(s) you wish to
display.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 297

Level Crossing Acquisition Process

For example, typing force displays all signals that include “force” in their labels.
You can also type a part of a signal description to display a signal type. For
example, to display displacement signals, you can type disp rather than
“displacement”.

Destination tab
Destination Tab
ITEM DESCRIPTION
Buffer Size Specifies the maximum number of data elements the buffer will store before
data is written to the disk.
Data Header Includes a label that describes the data on each buffer that is written to a file.
Destination Specifies where data is saved:
Specimen data file—the process writes buffers of data to the MPT
specimen.dat file in the Specimen.
User-specified data file—the process writes buffers of data to a separate data
file in the Specimen (yourname.dat).
Discard data—the process will not write data to the Specimen.
User Data File Specifies the name of the file where data is saved. This lets you create separate
data files in the MPT specimen. This control is enabled only when you have
selected User-specified data file in the Destination list above.
Buffer Type Specifies the buffer type.
Write First Data Header Specifies if the data header is written for each buffer or suppressed after the
Only first header is written. If disabled (unchecked), a data header is written for each
buffer.
Note This feature is not recommended for procedures with multiple data
acquisition processes writing data to the same data file.

298 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Level Crossing Acquisition Process

Output units tab

Output Units Tab
ITEM DESCRIPTION
UAS Specifies the unit assignment set that will be applied to acquired data.
Select Other Displays other existing unit assignment sets from which you can choose a
UAS. This button is enabled only when you select the Other Unit Assignment
Set option.
Edit Opens the Unit Assignment Set Editor so you can modify a unit assignment
set.

For more information See “About Buffers” on page 272.

See “About Station Signals” on page 276.

How to Define a Level Crossing Acquisition Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in the procedure table or navigation pane.

3. In the parameters window, click the Acquisition tab.

4. In the Master Signal list, click the signal you want to monitor with this
process.

5. In the Level Increment box, set the units of measurement, and then type a
value.

6. Optional—If you want to specify the number of samples to be acquired,

select the Total Samples box. Otherwise it will acquire data as long as the
process is active.

7. Click the Signals tab.

8. Move all the signals you want to monitor to the Included list. Move all the
others to the Available list.
Note The order of the signals in the Included list determines the order of the
columns of data in your data file.

9. Click the Destination tab.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 299

Level Crossing Acquisition Process

10. Type the Buffer Size and type a description of the data file in the Data
Header box.

11. In the Destination list, click the destination for the acquired data. (If you
click User-specified data file, type a file name in the User Data File box.)

12. In the Buffer Type list, click the buffer type.

13. Optional—If desired, enable Write First Data Header Only checkbox.
This feature aids data sorting and analysis.

14. Optional—Click the Output Units tab.

Change the unit assignment set if you want. Each data acquisition process
can use a different unit assignment set.

15. Click the General tab.

16. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

17. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

18. In the Execute Process box, type the number of times you want the process
to run.

19. Optional—In the Counter Type list, click a counter type.

20. Optional—If you enabled a counter, type a Counter Label.

21. Set the desired Start and Interrupt signals for the process in the procedure
table.

For more information See “Data Destination” on page 275.

300 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 High Speed Timed Acquisition Process

High Speed Timed Acquisition Process

About the High Speed Timed Acquisition Process

The High Speed Timed Acquisition process records short bursts of conditioned
sensor data. This process is typically used in tests where it is triggered and then
quickly interrupted by other processes, so that it is only active for short periods of
time.

Note Unlike other data acquisition processes, this process is not designed to
acquire data for the duration of a test, or for even long periods of time
within a test.

Sensor signals Sensors signals for this process are only available from the following
conditioners: Models 493.21B and 493.25 conditioners and Models 494.25,
494.26, and 494.16 conditioners whose HWI settings are configured for high-
speed data.

Important When designing a test procedure, do not try to collect data on the
same signal with more than one High Speed Data Acquisition
process. Concurrent High Speed Data Acquisition processes which
collect data on the same signal will not operate properly.

Sample rates When you define a High Speed Timed Acquisition process, you must define the
time between samples, or the sample rate. This determines how the process
acquires data when it is active.

• You can acquire data at periodic intervals.

• Data is recorded in the units specified by the selected unit assignment set.

• You can specify how many samples are taken, and when the samples are
acquired.

• If a number of samples is not specified, samples are taken as long as the

process is active.

Sample rate and The following tables show the relationship between the number of signals you
sampling duration can select and the maximum potential sample rate at which the process can
limitations acquire data.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 301

High Speed Timed Acquisition Process

Keep in mind that the actual sample duration (and number of points acquired) is
limited by the processor speed, the number of signals being sampled, the number
and type of other processes running concurrently, and so forth. If MPT cannot
store data as fast as it is acquired, an acquisition overrun will occur, and the test
will stop (data acquired up to that point will be saved).

Note If an acquisition overrun occurs, the test can be resumed without being
reset.

493 hardware sample The following sample rates apply to series 493 hardware (models 493.21B and
rates 493.25):

• 6144 System Rate:

MAXIMUM SAMPLE RATE MAXIMUM NUMBER OF SIGNALS

6144 23
12288 11
24576 5
49152 2
• 4096 System Rate:

MAXIMUM SAMPLE RATE MAXIMUM NUMBER OF SIGNALS

4096 35
8192 17
12288 11
16384 8
24576 5
49152 2

302 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 High Speed Timed Acquisition Process

494 hardware sample The following sample rates apply to series 494 hardware (models 494.25, 494.26,
rates and 494.16):1

• 6144 System Rate:

MAXIMUM SAMPLE RATE MAXIMUM NUMBER OF SIGNALS

6144 29
12288 14
24576 7
30720 5
61440 2
• 4096 System Rate:

MAXIMUM SAMPLE RATE MAXIMUM NUMBER OF SIGNALS

4096 44
8192 22
12288 14
20480 8
24576 7
40960 4
61440 2
• 3072 System Rate:

1. To make signals available, each Series 494 conditioner’s Analog Input HWI
Editor properties must have the High Speed Data setting set to True.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 303

High Speed Timed Acquisition Process

MAXIMUM SAMPLE RATE MAXIMUM NUMBER OF SIGNALS

3072 59
6144 29
12288 14
15360 11
24576 7
30720 5
• 2048 System Rate:

MAXIMUM SAMPLE RATE MAXIMUM NUMBER OF SIGNALS

2048 89
4096 44
6144 29
8192 22
10240 17
12288 14
15360 11
20480 8
24576 7
30720 5
• 1024 System Rate:

304 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 High Speed Timed Acquisition Process

MAXIMUM SAMPLE RATE MAXIMUM NUMBER OF SIGNALS

1024 179
2048 89
3072 59
4096 44
5120 35
6144 29
8192 22
10240 17
12288 14
15360 11

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 305

High Speed Timed Acquisition Process

High Speed Timed Acquisition Parameter Descriptions

Acquisition tab
Acquisition Tab
ITEM DESCRIPTION
Time Between Points Specifies the time interval between which the process acquires data.
Sample Rate Specifies the rate at which the process acquires data. The maximum sample rate
depends on the system rate, the number of signals that you are sampling, and the
type of hardware used to condition the signal.

For a table with the maximum sample rates for various hardware, number of signals,
and system rates, see the About High Speed Timed Acquisition Process section.

Note MPT will change the number you enter to reflect the resolution of your
controller’s system clock rate. For instance, if you type in “12000” (Hz) and
press the Enter key, MPT will change the number to “12228” (Hz).

Total Samples Specifies the number of samples the process will acquire before it completes.
Sampling Duration Specifies the length of time the process will attempt to acquire data.
Continuous Sampling Causes the process to acquire samples continuously until it is interrupted.

Signals tab Selects signals from which this process acquires data. Use the left and right
arrows to move desired signals from the Available list to the Included list.
Sensors signals for this process are only available from the following
conditioners: Models 493.21B and 493.25 conditioners and Models 494.25,
494.26, and 494.16 conditioners whose HWI settings are configured for high-
speed data.

Note The order of the signals in the Included list determines the order of the
columns of data in your data file. Use the up and down arrows to arrange
signals in the desired order.

List Filter With the List Filter, you can pare the list of Available signals according to text
you type in the entry box. Type text that describes the signal(s) you wish to
display.

For example, typing force displays all signals that include “force” in their labels.
You can also type a part of a signal description to display a signal type. For
example, to display displacement signals, you can type disp rather than
“displacement”.

306 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 High Speed Timed Acquisition Process

Note If the Time signal is selected, data is generated, not sampled. The Time
signal value always starts at zero.

Destination tab
Destination Tab
ITEM DESCRIPTION
Buffer Size Specifies the maximum number of data elements the buffer will store before data is
written to the disk.
Data Header Includes a label that describes the data on each buffer that is written to a file.
Destination Specifies where data is saved:
Specimen data file—the process writes buffers of data to the MPT specimen.dat
file in the Specimen.
User-specified data file—the process writes buffers of data to a separate data file
in the Specimen (yourname.dat).
Discard data—the process will not write data to the Specimen.
User Data File Specifies the name of the file where data is saved. This lets you create separate data
files in the MPT specimen. This control is enabled only when you have selected
User-specified data file in the Destination list above.
Buffer Type Specifies the buffer type.
Write First Data Header Specifies if the data header is written for each buffer or suppressed after the first
Only header is written. If disabled (unchecked), a data header is written for each buffer.
Note This feature is not recommended for procedures with multiple data
acquisition processes writing data to the same data file.

Output Units tab

Output Units Tab
ITEM DESCRIPTION
UAS Specifies the unit assignment set that will be applied to acquired data.
Select Other Displays other existing unit assignment sets from which you can choose a UAS.
This button is enabled only when you select the Other Unit Assignment Set option.
Edit Opens the Unit Assignment Set Editor so you can modify a unit assignment set.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 307

High Speed Timed Acquisition Process

Note Discard Data options are not available for the High Speed Acquisition
process.

Note The default buffer size is 16384, the range is from 1024 - 16384.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information See “About Buffers” on page 272.

See “About Station Signals” on page 276.

For a table showing the maximum sample rates for various hardware, number of
signals, and system rates, see “About the Timed Acquisition Process” on page
284.

How to Define a High Speed Timed Acquisition Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in the procedure table or navigation pane.

3. In the parameters window, click the Acquisition tab.

4. In the Time Between Points box, set the units of measurement and type a
value. Or, select Sample Rate, and specify the rate at which the system will
acquire data.

308 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 High Speed Timed Acquisition Process

5. In the Sample Duration box, specify the length of time you wish the system
to acquire data. Or, select Total Samples, and specify the number of
samples you wish the system to acquire.

6. Click the Signals tab.

7. Move all the signals you want to monitor to the Included list. Move all the
others to the Available list.
Note The order of the signals in the Included list determines the order of the
columns of data in your data file.

8. Click the Destination tab.

9. Type the Buffer Size and type a description of the data file in the Data
Header box.

10. In the Destination list, click the destination for the acquired data. (If you
click User-specified data file, type a file name in the User Data File box.)

11. In the Buffer Type list, click the buffer type.

12. Optional—If desired, enable Write First Data Header Only checkbox.
This feature aids data sorting and analysis.

13. Optional—Click the Output Units tab.

Change the unit assignment set if you want. Each data acquisition process
can use a different unit assignment set.

14. Click the General tab.

15. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

16. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

17. In the Execute Process box, type the number of times you want the process
to run.

18. Optional—In the Counter Type list, click a counter type.

19. Optional—If you enabled a counter, type a Counter Label.

20. Set the desired Start and Interrupt signals for the process in the procedure
table.

For more information See “Data Destination” on page 275.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 309

Cyclic Acquisition Process

Cyclic Acquisition Process

About the Cyclic Acquisition Process
The Cyclic Acquisition process acquires timed, level crossing, interleaved timed
and level crossing, or peak/valley data from cyclic feedback. You can specify the
segments or cycles from which the process acquires data arbitrarily, or in linear
or logarithmic progressions.

The Cyclic Acquisition process monitors sensor feedback that results from
cyclic command. This process acquires data from feedback according to one of
the following:

• Equal changes in time that you specify (time data)

• Equal changes in amplitude that you specify (level crossing data)

• Both changes in time and amplitude (interleaved timed and level crossing
data)

• Signal reversals which occur outside of a sensitivity level that you specify
(peak/valley data)

Sample uses You could use this process to sample the load feedback resulting from a long
cyclic fatigue test according to a logarithmic progression, and simultaneously
acquire level crossing and timed data from each sampled cycle.

The process saves all data pertaining to an individual cycle in the buffer, and then
writes the entire cycle’s data to the data file in one block. By default, the process
writes data to the specimen.dat file in the MPT specimen. If desired, the process
will write data to a user-defined data file within the MPT specimen.

Disabling the relative If you clear the Relative Cycle or Segment Counts check box, the process will
count feature not acquire data on specified cycles that have occurred before the process was
active.

For instance, suppose you begin a procedure with a Cyclic Command process
that cycles the specimen one hundred times at a small amplitude to precondition
the specimen before acquiring data.

Next, you use another Cyclic Command process to apply one million cycles to
the specimen at a much larger amplitude, and simultaneously acquire data from
the feedback with a cyclic acquisition process.

310 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Cyclic Acquisition Process

In this case, the cyclic acquisition process will not trigger until after cycle 100.
So if you specified a logarithmic progression of 1, 2, 5, 10, and so on, the cyclic
acquisition process would skip all of the cycles performed during
preconditioning (1, 2, 5, 10, 20, 50, and 100), and begin acquiring data at cycle
200.

If you had enabled the Relative Cycle (or Segment) Counts, the process would
trigger at cycle 101 of the test. The process would count cycle 101 of the test as
cycle 1 of its logarithmic progression. This is because cycle 101 of the test is the
first cycle performed relative to when the cyclic acquisition process is triggered.

Considerations when By default, the process stores the data it acquires from each cluster in its buffer,
acquiring cycle and then writes the content of its buffer to the data file when it is finished
clusters acquiring data on the cluster.

On a slow test, the process may take a long time to fill its buffer for a given
cluster. As the buffer fills, the data in the buffer will be lost if something
interrupts the progress of the test (for example, power failure, uncontrolled
shutdown, and so on) before the buffer fills completely.

The number of points the process acquires for a given cluster is open-ended and
may become quite large, depending on the test frequency and acquisition
intervals. For optimal results, some systems may require memory upgrades to
accommodate this situation.

When acquiring data, the process fills its buffer by receiving small buffered
chunks of data from the controller. Before the process can write this buffered data
to its data file, the process buffer must fill completely. Because of timing and size
differences between the controller buffer and process buffer, the process may
take up to thirty seconds before it writes data to its data file once its buffer is full.

Note The process will not issue its Process.Buffer Full signal until it has written
data to its data file.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 311

Cyclic Acquisition Process

Cyclic Acquisition Parameter Descriptions

Data Storage tab
Data Storage Tab (part 1 of 2)
ITEM DESCRIPTION
Master Channel Specifies the channel whose segment/cycle counter determines when data is
acquired.
Note Master Channel is not related to the signal used for level crossing or
peak/valley acquisition within the cycle.

Data Storage Pattern Specifies the pattern at which data is collected. The selections are:
• Logarithmic (1,2,5)—Pattern is: 1, 2, 5, 10, 20, 50, 100, 200, 500, 1000,
2000, 5000, and so forth, up to and including the maximum cycle stored.

• Logarithmic (1,2,3,4,5,6,7,8,9)—Pattern is 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 20,

30, 40, 50, 60, 70, 80, 90, 100, 200, 300, 400, 500, 600, 700, 800, 900,
1000, and so forth, up to and including the maximum cycle stored.

• Linear—Pattern is: n, 2n, 3n, and so on. You set the n value with the
Linear Data Interval control. Example: If you choose 200 as the
interval, the pattern is 200, 400, 600, and so forth, up to and including the
maximum cycle stored.

• User Defined—Use the cycles you specify in the Store Data At list.
Relative Cycle or Determines whether the cycle/segment count starts when this process starts or
Segment Counts when the procedure starts.
If you want the cycle/segment count to start when this process starts, select
Relative Cycle or Segment Counts.
If you want the cycle/segment count to start when the procedure starts, click to
clear Relative Cycle or Segment Counts.
Linear Data Interval Specifies the multiplier used to generate the data acquisition cycle or segment
sequence.
Note This control is available when you set the Data Storage Pattern to
Linear.

Example: If you choose 100 as the interval, the cycle sequence is 100, 200,
300, and so forth, up to and including the maximum cycle stored.
Maximum Cycle Stored Specifies the maximum cycle/segment count that data is collected on.

312 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Cyclic Acquisition Process

Data Storage Tab (part 2 of 2)

ITEM DESCRIPTION
Store Data At Displays which cycles or segments the process collects data on.
Note The entire list of cycle numbers may not be displayed.

If the Data Storage Pattern is User Defined, you must type the cycles or
segments you want to collect data on. Segments must be defined as a list of
positive integers. Cycles can be defined as a list of positive integers or integers
and half cycles (1.5).
Store Data For Specifies how many cycles or segments the process acquires data for when it
detects a cycle in the Store Data At list.
You can select from 0.5 (one segment) to 1000 cycles. The default value is 1.0
cycle.

Acquisition tab
Acquisition Tab (part 1 of 2)
ITEM DESCRIPTION
Acquisition Method Specifies how data is acquired.
Timed—acquires data at a user-specified time interval.
Level Crossing—acquires data when the selected Level Crossing signal
changes a specific amount.
Interleaved Timed and Level Crossing—acquires both Timed and Level
Crossing data.
Peak/Valley—acquires data when a peak or valley is detected in the specified
Peak/Valley signal.
Time Between Points Specifies the time interval at which the process acquires data.
Note MPT may change the number you enter slightly to reflect the resolution
of your system clock rate. For instance, if you type in “0.003” (3
milliseconds) and press the Enter key, the number may change to
“0.0029.”

Level Crossing Signal Selects the signal the process monitors for level changes.
Level Crossing Specifies how much the signal must change before the process acquires data.
Increment

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 313

Cyclic Acquisition Process

Acquisition Tab (part 2 of 2)

ITEM DESCRIPTION
Peak/Valley Signal Selects the signal the process monitors for peak and valley levels.
Peak/Valley Sensitivity Defines how much the signal must change before a level is considered a peak
or valley.

Signals tab Selects signals from which this process acquires data. Use the left and right
arrows to move desired signals from the Available list to the Included list.

Note The order of the signals in the Included list determines the order of the
columns of data in your data file. Use the up and down arrows to arrange
signals in the desired order.

List Filter With the List Filter, you can pare the list of Available signals according to text
you type in the entry box. Type text that describes the signal(s) you wish to
display.

For example, typing force displays all signals that include “force” in their labels.
You can also type a part of a signal description to display a signal type. For
example, to display displacement signals, you can type disp rather than
“displacement”.

Destination tab
Destination Tab (part 1 of 2)
ITEM DESCRIPTION
Buffer Size Specifies the maximum number of data elements the buffer will store before
data is written to the disk.
Data Header Includes a label that describes the data on each buffer that is written to a file.
Destination Specifies where data is saved:
Specimen data file—the process writes buffers of data to the MPT
specimen.dat file in the Specimen.
User-specified data file—the process writes buffers of data to a separate data
file in the Specimen (yourname.dat).
Discard data—the process will not write data to the Specimen.
User Data File Specifies the name of the file where data is saved. This lets you create separate
data files in the MPT specimen. This control is enabled only when you have
selected User-specified data file in the Destination list above.

314 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Cyclic Acquisition Process

Destination Tab (part 2 of 2)

ITEM DESCRIPTION
Buffer Type Specifies the buffer type.
Write First Data Header Specifies if the data header is written for each buffer or suppressed after the
Only first header is written. If disabled (unchecked), a data header is written for each
buffer.
Note This feature is not recommended for procedures with multiple data
acquisition processes writing data to the same data file.

Note Buffer settings are not available for the Cyclic Data Acquisition process.

Output units tab

Output Units Tab
ITEM DESCRIPTION
UAS Specifies the unit assignment set that will be applied to acquired data.
Select Other Displays other existing unit assignment sets from which you can choose a
UAS. This button is enabled only when you select the Other Unit Assignment
Set option.
Edit Opens the Unit Assignment Set Editor so you can modify a unit assignment
set.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 315

Cyclic Acquisition Process

General Tab
ITEM DESCRIPTION
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information See “About Buffers” on page 272.

See “About Station Signals” on page 276.

316 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Cyclic Acquisition Process

How to Define a Cyclic Acquisition Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in the procedure table or the navigation pane.

3. In the parameters window, click the Data Storage tab.

4. In the Master Channel list, click the channel you want to monitor with this
process.

5. Choose a Data Storage Pattern, and then type a value in the Maximum
Cycle Stored box.

For a linear pattern, type a value in the Linear Data Interval box. For a
user-defined pattern, type arbitrary values in the Store Data At box.

6. Optional—Select Relative Cycle or Segment Counts.

If you want the process to start acquiring data from cycles relative to when
the process starts, select Relative Cycle or Segment Counts.

If you want the process to start acquiring data from cycles relative to the
beginning of the procedure, click to clear Relative Cycle or Segment
Counts.

7. Optional—In the Store Data For box, type the number of cycles you want
to collect data for each Store Data At entry.

8. Click the Acquisition tab.

9. Choose an Acquisition Method.

• For Timed data, type a value in the Time Between Points box.

• For Level Crossing data, click a signal in the Level Crossing Signal
list, and type a value in the Level Crossing Increment box.

• For Interleaved Timed and Level Crossing data, type a value in the
Timed Between Points box, click a signal in the Level Crossing
Signal box, and type a value in the Level Crossing Increment box.

• For Peak/Valley data, click a signal in the Peak/Valley Signal list and
type a value in the Peak/Valley Sensitivity box.

10. Click the Signals tab.

11. Move all the signals you want to record data on to the Included list. Move
all the others to the Available list.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 317

Cyclic Acquisition Process

Note The order of the signals in the Included list determines the order of the
columns of data in your data file.

12. Click the Destination tab.

13. Type a description of the data file in the Data Header box.

14. In the Destination list, click the destination for the acquired data. (If you
click User-specified data file, type a file name in the User Data File box.)

15. Optional—If desired, enable Write First Data Header Only checkbox.
This feature aids data sorting and analysis.

16. Optional—Click the Output Units tab.

Change the unit assignment set if you want. Each data acquisition process
can use a different unit assignment set.

17. Click the General tab.

18. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

19. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

20. In the Execute Process box, type number of times you want the process to
run.

21. Optional—In the Counter Type list, click a counter type.

22. Optional—If you enabled a counter, type a Counter Label.

23. Set the desired Start and Interrupt signals for the process in the procedure
table.

For more information See “Data Destination” on page 275.

318 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Fatigue Process

Fatigue Process
About the Fatigue Process
The Fatigue process accumulates cycles in a histogram and calculates a damage
number (in the form of a statistical value) based on the histogram content.

Note The MPT Fatigue process calculates damage numbers using the same
algorithms as the Advanced Editing and Analysis feature of the MTS
RPC III™ product.

Periodically, the histogram and damage numbers are saved to disk, and sent to the
Fatigue Monitoring application via a proprietary data exchange protocol.

With the Fatigue Monitoring application, you can monitor the fatigue data in a
real-time, graphical format.

For more information See “Model 793.14 Fatigue Monitoring Application” on page 465.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 319

Fatigue Process

About Rainflow Counting and Histograms

Rainflow counting Rainflow counting is a method of concisely representing the cyclic content of a
signal. It is used to reduce large amounts of data to a more usable form by
creating one-pass histograms from drive or response signals. Strain ranges for
closed stress-strain hysteresis loops are recorded, and then fatigue life predictions
can be made using the strain range and the associated number of closed cycles.

The following example illustrates rainflow counting of a simple strain time

history using the Range histogram method. The associated stress-strain response
is also shown.

Histogram types Rainflow-counted histograms provide a means for summarizing the cycles that
are identified by rainflow counting. A histogram is created by using data
compression to reduce large amounts of data into blocks of information (bins).
Each histogram bin contains a cumulative count for data occurrences within a
specified bin range.

The Fatigue process provides three histogram types: RangeMean, Range, and
MaxMin.

A description of each type appears below. For purposes of illustration, the local
stress/strain hysteresis response is used to show the methods for creating
histograms.

320 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Fatigue Process

RangeMean histogram The RangeMean histogram identifies the range and the mean of each cycle
identified by the rainflow-counting method. The following example illustrates
the method for creating a RangeMean histogram.

Strain ( ε) Range ( ε)
-4 -3 -2 -1 0 1 2 3 4 0 1 2 3 4 5 6 7 8
-4
A -3
B -2
C FG

Mean ( ε)
D -1
E 0
AD
D 1
BC
2
F DE
G 3
A
Time

Range Mean
(FG) (DE)

The closed cycles and their associated range and mean are:

• BC—Range of 1; Mean of 1.5

• DE—Range of 3; Mean of 2.5

• FG—Range of 1; Mean of –1.5

• AD—Range of 8; Mean of 0.0

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 321

Fatigue Process

MinMax histogram The MinMax histogram identifies the rainflow-counted cycles by the identified
maximum/minimum value. The following example illustrates the method for
creating a MinMax histogram.

Strain ( ε) Maximum ( ε)
-4 -3 -2 -1 0 1 2 3 4 -4 -3 -2 -1 0 1 2 3 4
-4
AD
A -3
-2

Minimum ( ε)
B
C FG
-1
D
E 0
D 1
BC DE
2
F
G 3
A 4
Time

Strain Time History

When using the MinMax method, all the histogram counts must fall in the upper-
right triangle of the histogram because the maximum value must be greater than
the minimum value. The closed cycles and their associated minimum and
maximum are:

• BC—Minimum of 1; Maximum of 2

• DE—Minimum of 1; Maximum of 4

• FG—Minimum of –2; Maximum of –1

• AD—Minimum of –4; Maximum of 4

322 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Fatigue Process

Range histogram This method identifies cycles only by the cycle range. The following example
illustrates the method for creating a Range histogram:

Strain ( ε)
-4 -3 -2 -1 0 1 2 3 4
Cycle
A Count
0
B 1
C 2 BC, FG
D 2
3

Range ( ε )
E 1 DE
4
D
5
F 6
G 7
A 1 AD
Time 8

Range Range
(FG) (DE)

Strain Time History

The closed cycles and their associated range values are:

• BC—Range of 1

• DE—Range of 3

• FG—Range of 1

• AD—Range of 8

Bins Changing the bin size, lower range, upper range, or number will cause the other
numbers to change in order to maintain the following relationship:

Bin Size = (--------------------------------------------------------------------------

Upper Range – Lower Range )-
Number of Bins

Bin size The bin size specifies the distance between each histogram bin boundary for the
selected channel.

Lower range The lower range specifies the lower boundary of the histogram.

Upper range The upper range specifies the upper boundary of the histogram.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 323

Fatigue Process

Number of bins The number of bins specifies the number of bins between the upper and lower
range.

For more information For more information about histograms, rainflow-counting, and bins, see the
RPC III Reference Manual.

Fatigue Process Parameter Descriptions

Fatigue tab
Fatigue Tab
ITEM DESCRIPTION
Range Specifies the type of histogram data desired.
Data File Name Names the file where the fatigue data will be stored. The data file is saved in
the MPT specimen, with a “.dat” extension.
Smart Limits Automatically calculates limits based on the first pass of acquired data.
Upper Limit (+%) Defines the upper and lower limit for the damage number in terms of
Lower Limit (–%) percentage.
Limit Action Specifies the action performed when either of the specified limits are
exceeded. Options include:
None—Limit is disabled.
Warning—A warning message is issued and a message is written in the MPT
Specimen Log.
Stop—The process stops and a message is written in the MPT Specimen Log.
Trigger—The process sends a trigger that can be used to start another process.
Note Since smart limits are established during the first pass of data, limit
checking is not in effect until after the first pass of data.

324 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Fatigue Process

Signals tab
Signals Tab
ITEM DESCRIPTION
Signals Displays the signals which can monitored by the Fatigue process.
Units Displays the signal units.
Sensitivity Defines the Sensitivity for the peak/valley detector.
Note The units are the same as the full scale units.

Lower Range Specifies the lower boundary of the histogram.

Upper Range Specifies the upper boundary of the histogram.
Bin Size Specifies the distance between each histogram bin boundary for the selected
channel.

Note The units are the same as the full scale units.

Number of Bins Specifies the number of bins between the upper and lower range.
Material Assigns a material to the current signal.
Exp. Life Specifies a value for the specimen life expectancy (the number of tests the
specimen will survive before breaking).
Note If you do not know it, leave it at 1.0. This value is used by the Fatigue
Monitoring application to display the Percentage of Lifetime instead
of the damage.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 325

Fatigue Process

Monitoring tab
Monitoring Tab
ITEM DESCRIPTION
Time Interval (secs) Specifies the time interval between data transfers (which occur once every
pass).
Data is acquired from each included signal (the signals checked in the “Signals
tab”). The acquired data is peak-picked and sent to the Rainflow counter. At
the end of a pass, the acquired damage numbers are stored to the data file and
transmitted to the Fatigue Monitoring application. If the Fatigue Monitoring
application is not running, a warning message is written to the MPT Specimen
Log.
Note The Fatigue Monitoring application is started automatically if you click
Reset on the MPT control panel after a new Specimen has been
selected.

Data Transfer Mode Specifies whether the data is processed once, or processed periodically when a
set number of seconds has elapsed.
Send data once, then terminate—The data will be processed once (useful if
you want the statistics monitored only during part of your command signal),
then the Fatigue process will terminate.
Send data continuously—The data will be processed and sent to the Fatigue
Monitoring application every x seconds until the Fatigue process terminates.

326 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Fatigue Process

Settings tab
Settings Tab
ITEM DESCRIPTION
Material Library Specifies a materials library file, which defines the materials available to each
channel. The default is the RPC III materials library supplied with the Fatigue
process.
Damage Model Selects the damage model you will use for all fatigue processes.
RPC III provides both strain life and generic stress life damage models.
The Local Strain-life Approach (LSA) damage model selections include the
following:
• BASIC—strain-life approach to fatigue analysis (zero mean stress).

• MORROW—strain-life approach to fatigue analysis (mean stress

correction applied).

• SWT (Smith-Watson-Topper)—strain-life approach to fatigue analysis

(mean stress correction applied).

The Generic Stress Life (GSL) models include:

• GSL—generic stress life approach, no mean correction

• GSL_MEAN—generic stress life approach, mean correction

Note The selected damage model may influence the available materials.
Only materials that contain valid data for the selected damage model
will appear in the list shown in the Materials tab.

Default Number of Specifies the number of bins you will use for all new fatigue processes (the
Bins default is 64).
Note If the default number of bins is changed, the value is also changed on
the Signals tab for all corresponding signals.

Default Material Specifies the material that will be the default for all new fatigue processes that
are created.
Note If the default material is changed, the value is also changed on the
Signals tab for all corresponding signals.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 327

Fatigue Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information See “About Buffers” on page 272.

See “About Station Signals” on page 276.

For a information on each type, see “About Rainflow Counting and Histograms”
on page 320.

About Setting Up a Test to Acquire Fatigue Data

To acquire fatigue data during your test, you should define a Group process that
includes the Fatigue process and your command process.

You should sequence your test so that:

• In the group process, the Fatigue process starts when the command process
starts.

• When the command process ends, the Fatigue process is terminated.

• When the Fatigue process ends, the Group process ends.

In this setup, each execution of the Group process yields one point of data
(which is not enough to create a fatigue plot). To acquire enough data points for
your plot, you can set the number of times the Group process runs equal to the
number of passes you desire (typically greater than one hundred).

328 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Fatigue Process

Note You can use the Trend process in parallel with the Fatigue process to
acquire trend data.

How to Define a Fatigue Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the Fatigue process icon in the procedure table or in the navigation
pane.

3. In the parameters window, click the Fatigue tab.

4. Choose a Range, and type a Data File Name.

Note If you have multiple Fatigue processes within one procedure in
sequence, be sure to type a unique file name for each process.
Otherwise, all data will be written to the same data file.

5. Under Smart Limits, type Upper Limit and Lower Limit values, and then
set the Limit Action.

6. Click the Settings tab and specify the Materials Library, Damage Model,
Default Number of Bins, and Default Material.

7. Click the Signals tab, and select the box next to each signal you want to
acquire fatigue data from.

8. For the selected signals, type the desired values for the Sensitivity, Lower
Range, Upper Range, Bin Size, Number of Bins, Material, and Exp. Life
(life expectancy).

9. Click the Monitoring tab, type a Time Interval, and then select the Data
Transfer Mode.

10. Click the General tab.

11. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

12. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

13. In the Execute Process box, type the number of times you want the process
to run.

14. Optional—In the Counter Type list, click a counter type.

15. Optional—If you enabled a counter, type a Counter Label.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 329

Fatigue Process

16. Set the desired Start and Interrupt signals for the process in the procedure
table.

Important tips If your procedure will run for a long time, make sure the Windows virtual
memory paging file is large enough (MTS recommends 250 MB). To access the
Windows paging file: Start > Settings > Control Panels > System.

In the Fatigue Process Parameters window, make sure the Fatigue process is
enabled and the Execute Process value is set to one (on the General tab).

Because the Fatigue process parallels a command process, it will run as long as
the command process is executing. However, it is possible to specify the Fatigue
process’ run time within the Fatigue process:

1. Click the Monitoring tab.

2. Specify a Time Interval.

3. Select Send data once, then terminate.

Note If you choose Send data continuously on the Monitoring tab, the
Fatigue process will not stop on its own, and therefore, will not repeat
according to the Execute Process value you enter on the General tab.

For more information See “Data Destination” on page 275.

330 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Time History Input Process

Time History Input Process

About the Time History Input Process
The Time History Input process acquires and digitizes multiple channels of
analog test response data in the RPC III file format.

MTS Series 793 Software supports both short integer and floating point time
history files. To change these settings:

1. Open the Project Manager application.

2. Click Tools > Project Settings.

3. Select MultiPurpose TestWare in the category pane.

4. Click Time History Input Process Data Format in the values pane.

5. Select one of the following from the dropdown menu:

Float The response file will be written in floating point data format.
Short Integer The response file will be written in short integer data format.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 331

Time History Input Process

Time History Input Parameter Descriptions

File tab
File Tab
ITEM DESCRIPTION
Show Status Panel at Displays the Time History Input Status panel during the test.
Run Time

Create Trend Enables MPT to acquire and store trend response data. This data can be used
Response File by the RPC application to show changes that occurred in the specimen over the
course of the test.
Directory Specifies the directory in which the response file (.rsp) will be saved. With this
Specify File Destination, you can specify a path for the response file. The Use
Specimen Directory selection saves the response file in the specimen
directory.
Response File The process stores digitized response test data in a response file (.rsp). If the
(file icon) Directory selection is Specify File Destination, the Response File file icon
will be active. Click the file icon to open the Select response file window. Use
the window to select a current response file, save a new response file, and
specify the path.
Note This selection only appears when the Create Trend Response File
checkbox is cleared.

Trend Response Files Specifies the root of trend response file names.
Root Filename
Trend response files are stored in the same folder as the response file. When
the first response file is saved, it is named your root name000.rsp. Subsequent
response files are named your root name001.rsp, your root name002.rsp, your
root name003.rsp, and so on.
Note This selection only appears when the Create Trend Response File
checkbox is selected.

Sampling Rate Specifies the rate at which the controller samples response feedback.
Points per Frame Specifies the number of data points the controller samples per subdivision of
the digitized data.
Frames to Sample Specifies the number of subdivisions of the digitized data in which the
controller samples.
Sampling Time (Sec) Specifies the total time (in seconds) during which the controller samples data
from response feedback.

332 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Time History Input Process

Channels tab
Channels Tab
ITEM DESCRIPTION
Number of Channels Selects the number of channels on which data is acquired and formatted.
Output File Channel Switches between Output File Channels.
Station Signal Defines the station signal associated with the selected output file channel.
Channel Descriptor Specifies the Output File Channel descriptor used in the response file header.
Note The default name is the Station Signal name.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information See “About Buffers” on page 272.

See “About Station Signals” on page 276.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 333

Time History Input Process

How to Define a Time History Input Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in the procedure table or in the navigation pane.

3. In the parameters window, click the Channels tab.

4. In the Number of Channels list, type the number of channels you want to
take data on and press Enter.

5. In the Output File list, click the first channel.

6. In the Channel 1 Signal list, click the signal to be monitored. (You can type
a descriptor in the Channel Descriptor box.)

7. Perform steps 5 - 6 for any additional channels.

8. Click the File tab.

9. Optional—If desired, enable the Show Status Panel at Run Time control.

10. Use the Directory control to specify the directory in which the response file
(.rsp) will be saved. With the Specify File Destination selection, you can
specify a path for the response file. The Use Specimen Directory selection
saves the response file in the specimen directory.

11. If you have selected Specify File Destination in the previous step, you can
click the Response File file icon to open the Select response file window.
Use this window to select the file and directory in which you wish to save
response data.

12. In the Sampling Rate list, click the desired sampling rate.

13. In the Points per Frame list, click the desired number of data points the
controller samples per subdivision of the digitized data.

14. In the Frames to Sample box, type the desired number of subdivisions of
the digitized data in which the controller samples.

15. In the Sampling Time (Sec) list, type the total time (in seconds) during
which the controller samples data from response feedback.

16. Click the General tab.

17. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

334 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Time History Input Process

18. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

19. In the Execute Process box, type number of times you want the process to
run.

20. Optional—In the Counter Type list, click a counter type.

21. Optional—If you enabled a counter, type a Counter Label.

22. Set the desired Start and Interrupt signals for the process in the procedure
table.

For more information See “Data Destination” on page 275.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 335

Trend Process

Trend Process
About the Trend Process
The Trend process collects signal data and calculates five statistical trend values:
Minimum, Maximum, Mean, RMS, and Standard Deviation.

Periodically, the trend values are saved to disk, and sent to the Model 793.12
Trend Monitoring Application via a proprietary data exchange protocol.

With the Trend Monitoring application, you can monitor the trend data in a real-
time, graphical format.

For more information For more information about trend monitoring, see “Model 793.12 Trend
Monitoring Application” on page 458.

About Data Handling

Data is acquired for each included signal (the channels with a check mark next to
their names). At the end of a pass, the acquired statistical values are stored to the
data file and transmitted to the Trend Monitoring application. If the Trend
Monitoring application is not running, a warning message will be written to the
MPT Specimen Log.

Limits that are changed by the Trend Monitoring application during the
procedure will be transferred back to the Trend process and used for the limit
check.

Note The Trend Monitoring application is started automatically if you click

Reset on the MPT control panel after a new Specimen has been
selected.

Note Smart Limits apply to the full calibrated range of the sensor, that is, from
the lower calibration value to the upper calibration value.

Smart Limits are calculated after the first complete pass. This means that limit
checking is effectively disabled until after the first pass has run to completion. If
you need limit checking during the first pass as well, use the Trend tab to type
absolute limit values and adjust the limits as soon as the Trend Monitoring
application shows the data for the first pass.

If a smart limit is based on the data value, and the data value is too small (<0.01%
of range), limits based on full scale will be used instead.

336 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Trend Process

Example You could monitor strain levels in a critical component of the physical specimen.
You could also monitor shock absorber temperatures to ensure that the shock
absorbers do not overheat during a drive test. You can monitor statistical trends to
determine if the response signal matches your expectations.

The data on the selected signal channels are acquired independently on each
channel, and five statistical values (Minimum, Maximum, Mean, RMS, Standard
Deviation) are calculated. Depending on the settings in the Trend process, the
data is stored and processed every x seconds, or when the process’ end terminal
triggers; that is, when a Group process is repeated. The data is then stored to disk
in ASCII text format as tab-separated values and can be read directly by
spreadsheet programs such as Microsoft™ Excel®. The data file is stored in the
Specimen directory.

The data is also sent to the Trend Monitoring application (via a proprietary data
exchange protocol) which displays the statistics on-line and allows for limit
setting during the procedure; limit changes are transmitted back to MPT which
does the actual limits checking.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 337

Trend Process

Trend Parameter Descriptions

Trend tab
Trend Tab
ITEM DESCRIPTION
Data File Name Names the file where the trend data is stored.
Note Trend files are stored in your MPT specimen with a “.dat” extension.

Limit Unit Selection Specifies the units for the trend data limits.
Use Smart Limits Automatically calculates limits during the procedure based on the first pass of
acquired data.
Note Smart Limits apply to the full calibrated range of the sensor, that is,
from the lower calibration value to the upper calibration value.

Note If you select Use Smart Limits, the Signals Limits boxes (on the
Signals tab) are disabled. Limits that are changed during the test by
the Trend Monitoring application are transferred back to the MPT
Trend process.

% Based on Defines the reference of the data value on which the limit % is based.
Full Scale—Uses the full scale value as the reference value.
Data Value—Uses the first-pass value as the reference value.
Upper Limit (+%) Defines the lower and upper limit for each statistical value.
Lower Limit (-%)

Limit Action Specifies the action performed when either of the specified limits are
exceeded. Options include:
None—Limit is disabled.
Warning—A warning message is issued and a message is written in the MPT
message log.
Stop—The process stops and a message is written in the MPT Specimen Log.
Trigger—The process sends a trigger that can be used to start another process.

338 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Trend Process

Signals tab
Signals Tab
ITEM DESCRIPTION
Signal Names Displays the available channels which can be monitored by the Trend process.
Select the box next to the signal name if you want the Trend process to monitor
it, and then type the upper and lower limits for the five statistical values.
Note The upper limit, lower limit, and limit action boxes are disabled if you
selected Use Smart Limits on the Trend tab.

Min/Max/Mean/RMS/ For each statistical value, this table defines the lower and upper limits and
STD Low, Up, Action associated action.
Note Note that the values are interpreted according to the Limit Unit
Selection on the Trend tab.

Monitoring tab
Monitoring Tab
ITEM DESCRIPTION
Time Interval (secs) Specifies the time interval between data transfers (which happens once every
pass).
First, choose a suitable time interval (for example, 120 seconds; thus, a pass
would be two minutes in length).
Data Transfer Mode Specifies whether the data is saved and sent once, or saved and sent each time
the specified Time Interval elapses.
Send data once, then terminate—The data will be saved and sent once at the
end of the first Time Interval. (This setting is useful if you want the monitor
statistics only for a part of the test.)
Send data continuously—The data will be saved and sent continuously in the
Time Interval specified until the Trend process is done or interrupted.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 339

Trend Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information See “About Buffers” on page 272.

See “About Station Signals” on page 276.

About Setting Up a Test to Acquire Trend Data

To acquire trend data during your test, you should define a Group process that
includes the Trend process and your command process.

Note Your command process is typically a Profile or Time History Output

process.

Typical trend tests are sequenced so that:

• When the command process starts, the Trend process starts.

• When the command process ends, the Trend process is terminated.

• When the Trend process ends, the Group process ends.

One pass of this Group process will yield only one point of data for each
statistical value, which is not enough to create a trend plot. To acquire more
points, you must set the number of times the Group process runs equal to the
number of command process passes you desire (this is typically greater than one
hundred).

340 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Trend Process

Note If desired, you can use the Fatigue process in parallel with the Trend
process to acquire fatigue data.

How to Define a Trend Process

1. Drag the icon from the Process Palette to your procedure or group
table.

2. Click the process icon in the procedure or group table, or in the navigation
pane.

3. Click the Trend tab. Type a Data File Name, select the Limits Units and, if
you want, enable the Smart Limits.

4. Click the Signals tab.

5. Select all the signals that you want to acquire data from by selecting the
check box to the left of the signal name.

6. For each selected signal, and for each statistical value, type the desired
values for the upper and lower limit and the limit action. (This step applies
only if Smart Limits are disabled.)

7. Click the Monitoring tab and select a Time Interval (typically set to 0) and
Data Transfer Mode.

8. Click the General tab.

9. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

10. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

11. In the Execute Process box, type number of times you want the process to
run.

12. Optional—In the Counter Type list, click a counter type.

13. Optional—If you enabled a counter, type a Counter Label.

14. Set the desired Start and Interrupt signals for the process in the procedure
table.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 341

Trend Process

Important hints • If your procedure runs for a long time, make sure the Windows virtual
memory paging file is large enough (MTS recommends 250 MB). To access
the Windows paging file controls: Start > Settings > Control Panels >
System

• On the General tab, make sure the Trend process is enabled and the
Execute Process value is set to one. Because the Trend process parallels a
command process, it will run as long as the command process is executing.
However, it is possible to specify the Trend process’ run time within the
Trend process, as follows:

- Click the Monitoring tab.

- Specify a Time Interval.

- Select Send data once, then terminate.

Note If you choose Send data continuously on the Monitoring tab, the
Trend process will not stop on its own, and therefore, will not repeat
according to the Execute Process value you enter on the General tab.

• If you change limits during the procedure (using the Trend Monitoring
application) the new limits are transferred to MPT and are displayed in the
Signals tab in the MPT Trend Parameters window. Thus, if you store the
procedure after running, these settings will be saved as well.

For more information See “Data Destination” on page 275.

About Smart Limits

• If you press Reset and start the procedure over, Smart Limits will not be
calculated again.

• If you change the Specimen, Smart Limits will be calculated again (even if
you load a previously run procedure).

• As mentioned above, if you change limits during the procedure, the new
limits will be stored with the procedure if you decide to save the procedure
after a run. However, if Smart Limits are enabled when you save, they will
be calculated again at run time, thus effectively disabling the previously
saved limits. (You may decide you want to disable Smart Limits before
running the procedure.

Example Suppose you want to run a sine wave for 20,000 cycles and you want trend to be
calculated every 1,000 cycles.

342 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

 Trend Process

To achieve this, use a Group process with a repeat count of 20. (If you want to
repeat a Trend process, you must put it into a Group process paralleled by a
command process, or use the Timed Mode.

Inside the Group process, you will have the Cyclic command process (in this
case, a sine wave running for 1,000 cycles) and the Trend process running in
parallel. The Start signal for both processes should be Group.Start. The Group is
Done signal should be Trend.Done (assuming the name of your Trend process is
“Trend”). The Interrupt signal for the Trend process should be Cyclic.Done.

About RMS, Standard Deviation, and Asymmetric Full Scales

RMS and Standard Deviation are always positive numbers (greater than or equal
to zero). Given a range of –10 mm to –5 mm, RMS then would be in the range of
5 through 10, and Standard Deviation would be 0 through 10. This is important to
remember when typing limit values, either as engineering units or as percentages.
The Smart Limits controls in the Trend tab takes these physical relationships
into account and checks user input accordingly.

Another idiosyncrasy occurs when working with temperature channels, and using
Celsius within MPT and Fahrenheit in the output unit assignment set. In this case
the lower limit for Standard Deviation defaults to 0º C; however, this equals 32º
F. Because the Standard Deviation for slowly changing signals (such as
temperature) is close to zero, in this scenario the lower limit for Standard
Deviation (32º F) would very likely be tripped after the first pass. The best way
to avoid this situation is to use the same unit assignment set within MPT and as
output unit assignment set.

MTS MultiPurpose TestWare® Data Acquisition Process Descriptions 343

Trend Process

344 Data Acquisition Process Descriptions MTS MultiPurpose TestWare®

Chapter 14
Event Process Descriptions
You use event processes to monitor test signals and issue event signals when
conditions you specify are met.

Event Process Types

ICON PROCESS NAME DESCRIPTION
Data Limit Detector Monitors one or more signals for sensor limits you specify.
Process

Digital Input Detector Detects digital transition states from external devices.
Process

Operator Event Process Enables operator interaction during the test. (For example,
Operator events can display buttons the operator must click to
continue the test).
Peak/Valley Change Detects changes in the peak and valley amplitudes of cyclic
Detector Process waveforms.
Program Event Process Triggers other processes based on user-defined changes in the
test state.
Periodic Time Event Triggers other processes based on user-defined time events.
Process

Failure Detector Process Triggers other processes based on user-defined changes in the
physical specimen’s response.

MTS MultiPurpose TestWare® Event Process Descriptions 345

Data Limit Detector Process

Data Limit Detector Process

About Data Limit Detector Process
The Data Limit Detector process monitors signals for the limits you specify.
When any (or all) of the monitored signals exceed their limits, the process ends
and generates a done signal. The done signal from this process is often used to
trigger other processes.

You can configure the Data Limit Detector process to respond to a specific
segment count, amount of time, or sensor signal value.

When you define a Data Limit Detector process, you select the signals you wish
to monitor, set limits on those signals, choose how detector messages are logged,
and choose what action, if any, you want to invoke when the defined limits are
detected.

Example Assume we want our program to:

• Ramp up to end level 1 at a specified rate (Ramp 1).

• Ramp down to end level 2 at a different rate once the output reaches end
level 1 (Ramp 2).

We can use a Data Limit Detector process to trigger the ramp down process
once our end level 1 is reached.

Data Limit Detector process

Start=<Procedure>.Start
Interrupt=none
Ramp 2 process
Start=Ramp 1.Done
Interrupt=none

Ramp 1 process
Start=<Procedure>.Start
Interrupt=Data Limit Detector.Done

346 Event Process Descriptions MTS MultiPurpose TestWare®

 Data Limit Detector Process

About Limit Modes

This process supports relative limits (starting when the process begins) and
absolute limits (from a zero reference).

Example Assume the test command ramps from 1 cm to 4 cm. An absolute limit value of 2
cm ends the process at 2 cm. A relative limit ends the process at 3 cm (2 cm
relative to 1 cm).

4 2 cm relative

cm 2
2 cm absolute
1

Data Limit Detector process begins

How to Use Actions with Processes

The Station Manager includes an Event-Action Editor that lets you create user
defined actions that you can link to test events.

The user defined actions that you create with the Station Manager, in addition to
some built-in actions (Interlock, Station Power Off, Program Interlock, Program
Stop, and Program Hold) are now available in the Action list boxes in the Data
Limit Detector, Digital Input Detector, and Program Control processes.

How to create actions To define actions with the Station Manager Event-Action Editor (in the Tools
when MPT is running menu), you must have the Configuration access level selected. To select the
Configuration access level, you must quit MultiPurpose TestWare, and any
other applications that may be running, such a Basic TestWare. Once you have
quit the applications, you can select the Configuration access level and define
actions as desired with the Event-Action Editor. Then, before you relaunch
MultiPurpose TestWare, you must select any other access level other than
Configuration.

The user defined actions you have defined will appear in the Action list boxes in
the Data Limit Detector, Digital Input Detector, and Program Control processes.

MTS MultiPurpose TestWare® Event Process Descriptions 347

Data Limit Detector Process

Data Limit Detector Parameter Descriptions

Limits tab
Limits Tab
ITEM DESCRIPTION
Signal Displays the signals that may be monitored for limit detection. Only signals
moved to the Included column on the Signals tab appear in this list.
Upper/Lower Limit Enables the upper and lower limit controls, which allow you to specify
associated limit detector values.
Note If you want to temporarily disable a defined limit (for example, for a test
run), uncheck the associated checkbox.

Signals tab Selects the signals that this process monitors. Use the left and right arrows to
move desired signals to the Included list.

Settings tab
Settings Tab (part 1 of 3)
ITEM DESCRIPTION
Limit Mode Specifies whether the process limit values are absolute or relative to the signal
value at the start of the process.
Process completes Select Any selected signal exceeds its limit to end the process when any
when signal exceeds its limit.
Select All selected signals exceed their limits to end the process once all
signals have exceeded their limits at some time during the process.

348 Event Process Descriptions MTS MultiPurpose TestWare®

 Data Limit Detector Process

Settings Tab (part 2 of 3)

ITEM DESCRIPTION
Log Message As Assigns a severity level to the message (in ascending levels of severity:
Diagnostic, Information, Warning, or Error) and makes the message
available to the MPT Specimen Log.
If the Station Manager Station Log and the Basic TestWare Test Log are
configured to accept messages from all sources, then MPT makes the message
available to them also.
Note Unlike Station Manager and Basic TestWare, MPT does not generate
messages with a severity level of Fatal Error.

Each type of log will accept the message only if it has been configured to store
messages with the assigned severity level.
For instance, if the MPT Specimen Log is configured to accept messages with
a minimum severity level of Warning, and you assign Information as the
severity level for this message, then this message will not be recorded in the
MPT Specimen Log. In that instance the MPT Specimen Log would accept
messages having only Warning and Error severity levels.
You can specify the minimum severity level that each type of log will accept.
To do this:
• For MultiPurpose TestWare, select the MPT Options Editor, then
select the Specimen Log tab.

• For Station Manager, select Tools, then select Station Options, then
select the Station Log tab.

• For Basic TestWare, select Test Setup, then select the Test Log tab.

MTS MultiPurpose TestWare® Event Process Descriptions 349

Data Limit Detector Process

Settings Tab (part 3 of 3)

ITEM DESCRIPTION
Action Specifies the action that occurs when the process completes.
None The process ends without generating a message or performing an action.
Station Power The process removes hydraulic power from the station. The test can be
Off resumed after you reset interlocks and reapply hydraulic power to the station.
Interlock The process triggers a hydraulic interlock and shuts down the hydraulic power
supply. The test can be resumed after you reset the interlock, reactivate
hydraulic power.
Program The process triggers a program interlock. The test can be resumed after you
Interlock reset the interlock.
Program Stop The process stops the test. This action functions the same as clicking the Stop
button on the Station Controls panel.
Program Hold The process suspends the test until you click the Run button on the MPT
control panel. This action functions the same as clicking the Hold button on
the Station Controls panel.

Limit table tab The Limit Table tab displays all the limits defined in this process. You can edit
any data limit value in this window. To enable a limit, select the check box next
to the signal name. To disable a limit, clear the check box next to the signal name.

350 Event Process Descriptions MTS MultiPurpose TestWare®

 Data Limit Detector Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information See “About Limit Modes” on page 347.

How to Define a Data Limit Detector Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in your procedure table or in the navigation pane.

3. Click the Signals tab.

4. Move all the signals you want to monitor to the Included list. Move all the
others to the Available list.

5. Click the Limits tab.

6. For each signal you want to monitor:

A. In the Signal list, click the desired signal.

B. Set the units of measurement and type a value for the Upper Limit
and/or a Lower Limit.
Note If you want to disable an upper or lower limit, clear the Upper Limit/
Lower Limit check box.

MTS MultiPurpose TestWare® Event Process Descriptions 351

Data Limit Detector Process

7. Click the Settings tab.

8. Under Limit Mode, set the limit mode.

9. Under Process completes when, set when the process ends.

10. Optional—Enable (check) the Log Message As control and select the type
of message you wish to generate.

11. Optional—Select an action.

12. Click the Limit Table tab.

13. Verify and, if needed, edit limit values on this tab.

14. Click the General tab.

15. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

16. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

17. Optional—In the Counter Type list, click a counter type.

18. Optional—If you enabled a counter, type a Counter Label.

19. Set the desired Start and Interrupt signals for the process in the procedure
table.

352 Event Process Descriptions MTS MultiPurpose TestWare®

 Digital Input Detector Process

Digital Input Detector Process

About the Digital Input Detector Process
The Digital Input Detector process monitors digital input signals. When any (or
all) of the monitored signals are received, the process ends and generates a done
signal. The done signal from this process is used to trigger other processes.

When you define a Digital Input Detector process, you define the digital inputs
you want to monitor, the required signal state, the trigger mode, how messages
are logged, and what action, if any, you want the process to perform when it
receives a monitored signal.

You must know what is connected to each digital input and what type of input is
expected. See the Cabling chapter in the MTS 793 Controller Hardware manual
for information about digital input connections.

How to set signal With the Options list (on the Input Table tab), you can specify what input signal
options state is required to trigger the detector process.

The following states are supported:

ITEM DESCRIPTION
None Disables the input.
High/Low Detects transitions from a logic high state to a
logic low state.
Low/High Detects transitions from a logic low state to a
logic high state.
Either Detects any transition from high-to-low or low-
to-high.
Channel Low Detects the logic low state.
Channel High Detects the logic high state.

MTS MultiPurpose TestWare® Event Process Descriptions 353

Digital Input Detector Process

Design considerations If the signal is high when the process begins:

• The High/Low selection will cause the process to trigger when the signal
becomes low.

• The Low/High selection will cause the process to trigger when the signal
becomes low, then transitions to high.

• The Either selection will cause the process to trigger when the signal
becomes low.

• The Channel Low selection will cause the process to trigger when the
signal becomes low.

• The Channel High selection will cause the process to trigger immediately.

If the signal is low when the process begins:

• The High/Low selection will cause the process to trigger when the signal
becomes high, then transitions to low.

• The Low/High selection will cause the process to trigger when the signal
becomes high.

• The Either selection will cause the process to trigger when the signal
becomes high.

• The Channel Low selection will cause the process to trigger immediately.

• The Channel High selection will cause the process to trigger when the
signal becomes high.

Digital Input Detector Parameter Descriptions

Input Table tab
Input Table Tab
ITEM DESCRIPTION
Digital Inputs Displays the input signals being monitored by this process.
Options Defines the type of signal event the process is looking for.

Inputs tab Selects the signals that will be monitored by the Digital Input Detector process.
Move signals to the Included list if you want to monitor them with this process.

354 Event Process Descriptions MTS MultiPurpose TestWare®

 Digital Input Detector Process

Settings tab
Settings Tab (part 1 of 2)
ITEM DESCRIPTION
Trigger Mode Trigger Once causes the process to generate a trigger and a done signal when
the specified digital event occurs.
Trigger Continuously causes the process to generate a trigger signal when the
specified digital event occurs. When you make this selection, the process will
only terminate upon an interrupt or when its parent group or procedure ends.
Process triggers when Select Any selected input detects its specified event to end or trigger the
process when any one of the inputs is detected.
Select All selected inputs detect their specified events to end or trigger the
process when all selected inputs are detected.
Log Message As Assigns a severity level to the message (in ascending levels of severity:
Diagnostic, Information, Warning, or Error) and makes the message
available to the MPT Specimen Log. If the Station Manager Station Log and
the Basic TestWare Test Log are configured to accept messages from all
sources, then MPT makes the message available to them also.
Note Unlike Station Manager and Basic TestWare, MPT does not generate
messages with a severity level of Fatal Error.

Each type of log will accept the message only if it has been configured to store
messages with the assigned severity level. For instance, if the MPT Specimen
Log is configured to accept messages with a minimum severity level of
Warning, and you assign Information as the severity level for this message,
then this message will not be recorded in the MPT Specimen Log. In that
instance the MPT Specimen Log would accept messages having only
Warning and Error severity levels.
You can specify the minimum severity level that each type of log will accept.
To do this:
• For MultiPurpose TestWare, select the MPT Options Editor, then
select the Specimen Log tab.

• For Station Manager, select Tools, then select Station Options, then
select the Station Log tab.

• For Basic TestWare, select Test Setup, then select the Test Log tab.

MTS MultiPurpose TestWare® Event Process Descriptions 355

Digital Input Detector Process

Settings Tab (part 2 of 2)

ITEM DESCRIPTION
Action Specifies one of the following detector actions:
None The process ends without generating a message or performing an action.
Station Power The process removes hydraulic power from the station. The test can be
Off resumed after you reset interlocks and reapply hydraulic power to the station.
Interlock The process triggers a hydraulic interlock and shuts down the hydraulic power
supply. The test can be resumed after you reset the interlock, reactivate
hydraulic power, and apply hydraulic power to the station.
Program The process triggers a program interlock. The test can be resumed after you
Interlock reset the interlock.
Program Stop The process stops the test. This action functions the same as clicking the Stop
button on the Station Controls panel.
Program Hold The process suspends the test until you click the Run button on the Station
Controls panel. This action functions the same as clicking the Hold button on
the Station Controls panel.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information See “How to set signal options” on page 353.

356 Event Process Descriptions MTS MultiPurpose TestWare®

 Digital Input Detector Process

For more information about triggers, see “About Sequencing Processes” on page
87.

For more information on Actions, see “How to Use Actions with Processes” on
page 347

How to Define a Digital Input Detector Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in your procedure table or in the navigation pane.

3. Click the Inputs tab.

4. Move all the signals you want to monitor to the Included list. Move all the
others to the Available list.

5. Click the Input Table tab.

6. For each digital input signal listed, click the signal option in the Options
list.

7. Click the Settings tab.

8. Under Trigger Mode, set the trigger mode.

9. Under Process triggers when, set when the process triggers.

10. Optional—Enable (check) the Log Message As control and select the type
of message you wish to generate.

11. Optional—Select an action.

12. Click the General tab.

13. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

14. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

15. In the Execute Process box, type number of times you want the process to
run.
Note Repeating the process will have no effect if you selected Trigger
Continuously in step 8.

16. Optional—In the Counter Type list, click a counter type.

17. Optional—If you enabled a counter, type a Counter Label.

MTS MultiPurpose TestWare® Event Process Descriptions 357

Digital Input Detector Process

18. Set the desired Start and Interrupt signals for the process in the procedure
table.

358 Event Process Descriptions MTS MultiPurpose TestWare®

 Operator Event Process

Operator Event Process

About the Operator Event Process
The Operator Event process allows the operator to affect test progress through
the use of custom buttons on a special control panel. It is useful for reminding the
operator of particular test events or hazards.

Sample uses include:

• Prompting the operator before the test begins.

• Prompting the operator to perform an action before continuing the test.

• Triggering the beginning of a data acquisition process.

• Holding a test indefinitely.

When you define an Operator Event process, you must define the button ID, the
button label, a message to the operator, the trigger mode, and how the event
messages are logged.

The MPT control panel can display up to four operator event buttons and
messages simultaneously. This means only four Operator Event processes can
be active at any one time.

If your operator events will not run simultaneously, you can use the same button
for multiple Operator Event processes. The button label and message will
change to coincide with the next active Operator Event process.

Operator Event Suppose a portion of the test you are designing results in a noise hazard for the
example operator.

You could configure an Operator Event process (labeled Warning!) to hold the
test just before the hazardous portion begins. This would give the operator time
to acknowledge the warning and put on ear protection. Once the operator is
ready, he or she could click the Warning! button to resume the test.

MTS MultiPurpose TestWare® Event Process Descriptions 359

Operator Event Process

Operator Event Parameter Descriptions

Settings tab
Settings Tab
ITEM DESCRIPTION
Button ID Selects one of four operator event buttons.
Button Label Assigns a label to the button that appears on the MPT control panel (10-
character maximum).
Description Assigns the operator event message that is displayed next to the operator event
button on the MPT control panel.
You may type as much text as you like in the Description box, but the MPT
control panel can display only one line of text, so type the information you
want the operator to see first at the beginning of your message (you can resize
the MPT control panel to expand the viewing area, but it will still display only
one line).
When you enable the Log Message As control (on the Options tab), the entire
text in the Description box is entered in the MPT Specimen Log when the
process completes or triggers.
Also, pressing Enter (on the keyboard) when typing in the Description box
causes the cursor to return to the next line in the box (analogous to a carriage
return). However, when the message is displayed in the MPT control panel, a
space will appear wherever the Enter key was pressed so that the text appears
on one line. When displayed in the Message Log or Print Preview displays,
however, the message will appear as entered in the Description box.

360 Event Process Descriptions MTS MultiPurpose TestWare®

 Operator Event Process

Options tab
Options Tab
ITEM DESCRIPTION
Trigger Mode Trigger Once causes the process to generate a trigger and a done signal when
the specified operator event occurs.
Trigger Continuously causes the process to generate a trigger signal when the
specified operator event occurs. When you make this selection, the process
will only terminate upon an interrupt or when its parent group or procedure
ends.
Log Message As Assigns a severity level to the message (in ascending levels of severity:
Diagnostic, Information, Warning, or Error) and makes the message
available to the MPT Specimen Log.
If the Station Manager Station Log and the Basic TestWare Test Log are
configured to accept messages from all sources, then MPT makes the message
available to them also.
Note Unlike Station Manager and Basic TestWare, MPT does not generate
messages with a severity level of Fatal Error.

Each type of log will accept the message only if it has been configured to store
messages with the assigned severity level.
For instance, if the MPT Specimen Log is configured to accept messages with
a minimum severity level of Warning, and you assign Information as the
severity level for this message, then this message will not be recorded in the
MPT Specimen Log. In that instance the MPT Specimen Log would accept
messages having only Warning and Error severity levels.
You can specify the minimum severity level that each type of log will accept.
To do this:
• For MultiPurpose TestWare, select the MPT Options Editor, then
select the Specimen Log tab.

• For Station Manager, select Tools, then select Station Options, then
select the Station Log tab.

• For Basic TestWare, select Test Setup, then select the Test Log tab.

MTS MultiPurpose TestWare® Event Process Descriptions 361

Operator Event Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information For more information about triggers, see “About Sequencing Processes” on page
87.

362 Event Process Descriptions MTS MultiPurpose TestWare®

 Operator Event Process

How to Define an Operator Event Process

1. Drag the icon from the Process Palette to your procedure table or the
navigation pane.

2. Click the process icon in your procedure table or in the navigation pane.

3. Click the Settings tab.

4. In the Button ID list, click the button you want to use.

5. In the Button Label box, type in the button label that appears on the MPT
control panel.

6. In the Description box, type the message you want to display on the MPT
control panel.

7. Click the Options tab.

8. Under Trigger Mode, set the trigger mode.

9. Optional—Enable (check) the Log Message As control and select the type
of message you wish to generate.

10. Click the General tab.

11. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

12. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

13. In the Execute Process box, type number of times you want the process to
run.
Note Repeating the process will have no effect if you selected Trigger
Continuously in step 8.

14. Optional—In the Counter Type list, click a counter type.

15. Optional—If you enabled a counter, type a Counter Label.

16. Set the desired Start and Interrupt signals for the process in the procedure
table or the navigation pane.

MTS MultiPurpose TestWare® Event Process Descriptions 363

Peak/Valley Change Detector Process

Peak/Valley Change Detector Process

About the Peak/Valley Change Detector Process
The Peak/Valley Change Detector process monitors signals for peak and valley
changes.

In its default state, this process begins by detecting the amplitudes of the first
peak and valley, which it uses as reference levels to establish the tolerance band.

• If the process is set to trigger once, when the process detects a peak or valley
outside of the tolerance band, the process generates a trigger signal (its
“done” signal) and ends.

• If the process is set to trigger continuously, when the process detects a peak
or valley outside of the tolerance band, the process generates a trigger
signal, and then automatically establishes new reference levels for the
tolerance band. The process will keep triggering and establishing new
reference levels until the process is interrupted.

The trigger and done signals from the Peak/Valley Change Detector process are
used to trigger other processes.

If desired, you can override automatic detection of reference levels and use the
reference levels you specify. If you specify reference levels, the process will use
them for the duration of the test.

This process automatically

establishes peak and valley Peak
reference levels (indicated by the
dots). The reference levels become
the basis for the tolerance range Valley
(shown in grey).
If a peak or valley occurs outside of
the tolerance band, the process The detector triggers
generates a trigger signal and ends when a peak or valley
or establishes new reference occurs outside tolerance.
levels.
If desired, you can type your own
reference values to be used
throughout the test.

364 Event Process Descriptions MTS MultiPurpose TestWare®

 Peak/Valley Change Detector Process

Sensitivity A sensitivity value specifies how much the signal must change to detect a peak or
valley. It can be used to keep the process from seeing signal noise as a new peak
or valley.

• Setting the sensitivity too low may cause signal noise to be recognized as
peaks and valleys.

• Setting the sensitivity too high may cause low amplitude signals to be
missed.

Determines when a peak Detected

or valley is detected. Peaks

The sensitivity setting is

the amount the signal Sensitivity
must change before it is
considered a new peak
or valley. Detected
Valleys

Tolerance The tolerance band specifies how much a peak or valley must deviate from the
associated reference levels before the process generates a trigger signal.

For example, if the established peak value is +5 cm, and the tolerance is set to
±0.25 cm, the process will not generate a trigger signal unless the peak value
registers greater than +5.25 cm or less than +4.75 cm.

Peak

Tolerance Bands

Valley Detector Triggers

Enable after On the Options tab, you can use the Enable After command to specify how
many feedback cycles will occur before the process begins to monitor the
selected signal. This allows the signal to “settle-in” or stabilize before it is
monitored.

If you select a channel for the Channel Reference on the Command tab, the
process will begin counting cycles after the tapering is complete.

For example, if you specify 6 cycles, and the waveform begins with a taper that
includes 2 cycles, the process will begin monitoring peaks and valleys on cycle 9.

MTS MultiPurpose TestWare® Event Process Descriptions 365

Peak/Valley Change Detector Process

If you do not use Channel Reference, the process will begin counting cycles
immediately after the number of cycles you specify. For instance, if you specify 6
cycles, and the waveform begins with a taper that includes 2 cycles, the process
will begin monitoring for peaks and valleys on cycle 7.

In either case, if you press stop and then run on the Station Controls panel, the
process will begin the count over.

Reference values On the Options tab, if you select Default under Reference Values, the first peak
and valley detected by the process become the reference levels for the tolerance
band.

Note The process will not generate a trigger signal based on the first peak or
valley.

On the Options tab, if you select User-specified under Reference Values, you
type the upper and lower level values for the tolerance band. This is a useful
feature if it is possible that the first peak and valley used to establish the
reference values could be unusually large or otherwise irregular. With User-
specified reference values, the controller uses your preset reference values and
compares them with the very first peak or valley, (at the start of the process or
after the process resets itself after issuing a trigger). Because of this, in the
Trigger Continuously mode, the process may generate more triggers if you use
user-specified reference values than if you use default reference values.

366 Event Process Descriptions MTS MultiPurpose TestWare®

 Peak/Valley Change Detector Process

Peak/Valley Change Detector Process Example

Suppose you want to acquire a cycle of data each time the peaks or valleys of an
input signal change by a specified amount. Further, suppose you define a Peak/
Valley Change Detector process with the following parameters:

• Trigger continuously

• Tolerance: ±50 lbs

• Sensitivity: 5 lbs

Strain Command

Force Signal

100 lbs (±50 lbs) Bands

Trigger Data Acquisition Processes

The test command cycles between ±0.0001 strain and you are monitoring a force
signal.

Each time the peaks or valleys on the force signal change more than ±50 lbs, the
process generates a trigger signal that starts a data acquisition process.

The data acquisition process would use the Peak/Valley Change Detector
process as its start trigger. A single data acquisition process could be run multiple
times with this change detector.

Note It is good practice to specify a number of cycles to run before you begin
monitoring to allow a “settling in” period.

MTS MultiPurpose TestWare® Event Process Descriptions 367

Peak/Valley Change Detector Process

Peak/Valley Change Detector Parameter Descriptions

Settings tab
Settings Tab
ITEM DESCRIPTION
Signal Selects the signal you will monitor with the Peak/Valley Change Detector
process.
Sensitivity Defines how much the signal must change before it is considered a peak or
valley.
Tolerance Defines a tolerance band for the peaks and valleys. If a peak or valley occurs
outside the tolerance band, the process triggers.

Options tab
Options Tab (part 1 of 2)
ITEM DESCRIPTION
Enable After Specifies how many segments or cycles will occur before the process begins to
monitor the selected signal.
Reference Values Specifies how the upper and lower reference values are established.
Trigger Mode Trigger Once causes the process to generate a trigger and a done signal when a
peak or valley occurs outside the tolerance band.
Trigger Continuously causes the process to generate a trigger signal when a
peak or valley occurs outside the tolerance band. The process will keep
triggering until the process is interrupted.

368 Event Process Descriptions MTS MultiPurpose TestWare®

 Peak/Valley Change Detector Process

Options Tab (part 2 of 2)

ITEM DESCRIPTION
Log Message As Assigns a severity level to the message (in ascending levels of severity:
Diagnostic, Information, Warning, or Error) and makes the message
available to the MPT Specimen Log.
If the Station Manager Station Log and the Basic TestWare Test Log are
configured to accept messages from all sources, then MPT makes the message
available to them also.
Note Unlike Station Manager and Basic TestWare, MPT does not generate
messages with a severity level of Fatal Error.

Each type of log will accept the message only if it has been configured to store
messages with the assigned severity level.
For instance, if the MPT Specimen Log is configured to accept messages with
a minimum severity level of Warning, and you assign Information as the
severity level for this message, then this message will not be recorded in the
MPT Specimen Log. In that instance the MPT Specimen Log would accept
messages having only Warning and Error severity levels.
You can specify the minimum severity level that each type of log will accept.
To do this:
• For MultiPurpose TestWare, select the MPT Options Editor, then
select the Specimen Log tab.

• For Station Manager, select Tools, then select Station Options, then
select the Station Log tab.

• For Basic TestWare, select Test Setup, then select the Test Log tab.

MTS MultiPurpose TestWare® Event Process Descriptions 369

Peak/Valley Change Detector Process

Command tab
Command Tab
ITEM DESCRIPTION
Channel Reference Selects the command channel associated with the feedback signal that you
want to monitor. If you select None, which is the default, the Cycle Time Out
control is disabled.
Use this feature if your procedure includes tapered waveforms. With the
command channel, MPT can identify and avoid monitoring the transitions that
occur during tapered cycles.
Cycle Time Out Note This feature is enabled only if you select a channel in the Channel
Reference box.

Counts cycles from the beginning of the process, including cycles in tapers. If
the process does not detect a peak or valley during the specified number of
cycles (or segments), it issues a trigger.
If you type a zero, the process will issue a trigger immediately.
If you press Stop and then Run on the Station Controls panel, the process will
start counting over again.
Note This feature can be used to detect a malfunction; for example, if a test
is run when the Master Span (on the Station Controls panel) is set
very low.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.

370 Event Process Descriptions MTS MultiPurpose TestWare®

 Peak/Valley Change Detector Process

General Tab
ITEM DESCRIPTION
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information For more information about triggers, see “About Sequencing Processes” on page
87.

How to Define a Peak/Valley Change Detector Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in your procedure table or in the navigation pane.

3. Click the Settings tab.

4. In the Signal list, click the signal you want to monitor.

5. In the Sensitivity box, set the units, and then type a value.

6. In the Tolerance box, set the units, and then type a value.

7. Click the Options tab.

8. Optional—If you want to delay the Peak/Valley monitoring process for a

number of cycles to allow for a “settling in” period, type a value in the
Enable After box.

9. Under Reference Values, select Default or User-specified.

If you select User-specified Reference Values, type the desired Upper and
Lower Reference values.

10. Under Trigger Mode, set the trigger mode.

11. Optional—Enable (check) the Log Message As control and select the type
of message you wish to generate.

MTS MultiPurpose TestWare® Event Process Descriptions 371

Peak/Valley Change Detector Process

12. Optional—Click the Command tab, click a Channel Reference signal and
type a Cycle Time Out value.

13. Click the General tab.

14. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

15. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

16. In the Execute Process box, type number of times you want the process to
run.
Note Repeating the process will have no effect if you selected Trigger
Continuously in step 10.

17. Optional—In the Counter Type list, click a counter type.

18. Optional—If you enabled a counter, type a Counter Label.

19. Close the parameters window, and set the desired Start and Interrupt
signals for the process in the procedure table.

372 Event Process Descriptions MTS MultiPurpose TestWare®

 Program Event Process

Program Event Process

About the Program Event Process
The Program Event process is typically used to trigger other processes in
response to a change in the test state.

There are seven test states that can generate a trigger and/or done signal in the
Program Event process:

• Running—the state in which the procedure is controlling the machine and

playing out a waveform.

• Entering Hold—the transition state between Running and Holding.

• Holding—the state in which the test is suspended (the actuator is not

moving), but the test can be continued by clicking the Run button.
Note This process sees a “paused” state in the same way that it sees a
Holding state. That is, as the run indicator on the Station Controls panel
blinks while “paused,” this process will see the following sequence of
transitions: Running>Entering Hold>Holding>Exiting Hold>Running.

• Exiting Hold—the transition state between Holding and Running. It will

typically complement what is done in the Entering Hold state.

• Entering Stopped—the transition state between Running/Holding and

Stopped.

• Stopped—the Stopped state. Once in this state, the actuators are fully
stopped. If appropriate, the test can be continued by clicking the Run
button, but it will not start up by itself.
Note The only MPT command process that will run during a Stopped state is
the Digital Output process.

• Exiting Stopped—the transition state between Stopped and Running. It

typically complements what is done in the Entering Stopped state.

Behavior with Stopped Most processes stop or suspend themselves when MPT enters a Stopped or
and Holding states Holding state. When a Program Event process detects one of these states, the
process that is triggered will typically see that MPT is stopped or holding and
refuse to do anything. Because it is common to use a Program Event process to
trigger a Digital Output process that turns off an external device when the test is
stopped, the Digital Output process is designed to function in a Stopped or
Holding state.

MTS MultiPurpose TestWare® Event Process Descriptions 373

Program Event Process

How to detect When a procedure or group process is done, MPT sends out an Interrupt signal to
transitions after a all of the active child processes. Program Event processes cannot detect Entering
Done Interrupt Stopped and Stopped transitions that occur after a Done Interrupt.

For more information See “About Transition States” on page 70.

Program Event Parameter Descriptions

Settings tab
Settings Tab
ITEM DESCRIPTION
Select program Selects the program event(s) you want to monitor. You can choose as many
event(s) to monitor program events as you want.
To select more than one event, hold the Ctrl key down while clicking the
desired events. To select a range of events, click the first event in the range,
then hold the Shift key down and click the last event in the range.
Trigger Mode Trigger Once causes the process to generate a trigger and a done signal when a
program event occurs.
Trigger Continuously causes the process to generate a trigger signal when a
program event occurs. The process will keep triggering on program events
until the process is interrupted.

374 Event Process Descriptions MTS MultiPurpose TestWare®

 Program Event Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information For more information about triggers, see “About Sequencing Processes” on page
87.

MTS MultiPurpose TestWare® Event Process Descriptions 375

Program Event Process

How to Define a Program Event Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in your procedure table or in the navigation pane.

3. Click the Settings tab.

4. Hold the Ctrl key and click the program events you want to monitor.

5. Under Trigger Mode, set the trigger mode.

6. Click the General tab.

7. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

8. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

9. In the Execute Process box, type number of times you want the process to
run.

Note Repeating the process will have no effect if you selected Trigger
Continuously in step 5.

10. Optional—In the Counter Type list, click a counter type.

11. Optional—If you enabled a counter, type a Counter Label.

12. Set the desired Start and Interrupt signals for the process in the procedure
table.

376 Event Process Descriptions MTS MultiPurpose TestWare®

 Periodic Time Event Process

Periodic Time Event Process

About the Periodic Time Event Process
With the Periodic Time Event process, you can schedule arbitrary and repetitive
times at which the process will produce a trigger, or a series of triggers. You can
use these time based triggers to invoke an event, such as triggering another
process, actuating an external device, and so forth.

When you define a Periodic Time Event process, you can specify periodic trigger
times, the trigger mode, and whether or not the process writes a message to the
message log when it invokes a trigger event.

Note To produce a trigger the Periodic Time Event process must be active at
the time you wish the trigger event to occur, so it is important to keep that
in mind when designing your test.

Note The Periodic Time Process will not trigger immediately after the test
starts, regardless of the process settings. The minimum amount of time
required for the process to trigger after the test starts is approximately
one minute.

Periodic Time Event Suppose you need to start warming up a temperature chamber before a technician
example arrives at your facility, so that it has achieved and stabilized at the desired
temperature by the time the technician begins testing. Further, suppose the
technician is scheduled to perform tests at 8:00AM on Mondays, Wednesdays,
and Thursdays beginning in March and continuing through May.

In this case you could use a Periodic Time Event process to trigger a Temperature
Control process hours before the technician arrives on the days and in the months
testing is scheduled.

MTS MultiPurpose TestWare® Event Process Descriptions 377

Periodic Time Event Process

Periodic Time Event Parameter Descriptions

Settings tab You may type in any of the entry boxes or choose from the selection list. To
display the selection list of an entry box, double-click on the box, or position the
cursor in the edit field of the desired box and press the up or down arrow keys.

Each box may be empty (meaning any value), may contain a single value, or may
contain a list of values separated by commas. Each value may be a single value or
a range of values (two separate values joined by a dash). For example: 1-3, 5, 7,
8-13, 19 means 1 through 3, or 5, or 7, or 8 through 13, or 19.

While running or holding, the process checks the time (clock and calendar time)
at which it begins and then periodically at one-minute intervals.

After approximately the first minute after the test starts, the process triggers
when the current time matches the schedule criteria.

Settings Tab
ITEM DESCRIPTION
Minute Accepts values from 0 to 59.
Hour Contains selections displayed in 12 or 24 hour format based on the regional
settings of the operating system. Accepts value entries in either the 12 or 24
hour format.
Day of Week Contains selections displayed according to the regional settings of the
operating system. Accepts entries in English or local language.
Day of Month Accepts values from 1 to 31.
Month of Year Contains selections displayed according to the regional settings of the
operating system. Accepts entries in English or local language.

378 Event Process Descriptions MTS MultiPurpose TestWare®

 Periodic Time Event Process

Options tab
Options Tab
ITEM DESCRIPTION
Trigger Mode Trigger Once causes the process to generate a trigger and a done signal when
the specified event occurs.
Trigger Continuously causes the process to generate a trigger signal when the
specified event occurs. When you make this selection, the process will only
terminate upon an interrupt or when its parent group or procedure ends.
Trigger For Duration is the same as the Trigger Continuously control except
you can specify the duration in which the process remains active. When
selected, the End After control is enabled. With the End After control, you
can specify the time the process ends in relation to its first trigger.
Log Message As Assigns a severity level to the message (in ascending levels of severity:
Diagnostic, Information, Warning, or Error) and makes the message
available to the MPT Specimen Log.
If the Station Manager Station Log and the Basic TestWare Test Log are
configured to accept messages from all sources, then MPT makes the message
available to them also.
Note Unlike Station Manager and Basic TestWare, MPT does not generate
messages with a severity level of Fatal Error.

Each type of log will accept the message only if it has been configured to store
messages with the assigned severity level.
For instance, if the MPT Specimen Log is configured to accept messages with
a minimum severity level of Warning, and you assign Information as the
severity level for this message, then this message will not be recorded in the
MPT Specimen Log. In that instance the MPT Specimen Log would accept
messages having only Warning and Error severity levels.
You can specify the minimum severity level that each type of log will accept.
To do this:
• For MultiPurpose TestWare, select the MPT Options Editor, then
select the Specimen Log tab.

• For Station Manager, select Tools, then select Station Options, then
select the Station Log tab.

• For Basic TestWare, select Test Setup, then select the Test Log tab.

MTS MultiPurpose TestWare® Event Process Descriptions 379

Periodic Time Event Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information For more information about triggers, see “About Sequencing Processes” on page
87.

380 Event Process Descriptions MTS MultiPurpose TestWare®

 Periodic Time Event Process

How to Define a Periodic Time Event Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in your procedure table or in the navigation pane.

3. Click the Settings tab.

Note Double-clicking an entry box displays its selection list.

4. Type or select desired values in the Minute, Hour, Day of Week, Day of
Month, and Month of Year entry boxes.

5. Click the Options tab.

6. Under Trigger Mode, set the trigger mode. If Trigger for Duration is
selected, set the End After time.

7. Optional—Enable (check) the Log Message As control and select the type
of message you wish to generate.

8. Click the General tab.

9. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

10. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

11. In the Execute Process box, type number of times you want the process to
run.
Note Repeating the process will have no effect if you selected Trigger
Continuously in step 6.

12. Optional—In the Counter Type list, click a counter type.

13. Optional—If you enabled a counter, type a Counter Label.

14. Set the desired Start and Interrupt signals for the process in the procedure
table.

MTS MultiPurpose TestWare® Event Process Descriptions 381

Failure Detector Process

Failure Detector Process

About the Failure Detector Process
The Failure Detector process is a detector process which monitors signals for
occurrence failure events (peak or valley values), determines whether the failure
events meet the criteria for specimen failure, and if so, completes the process.

Failure Detector Parameter Descriptions

Settings tab
Settings Tab
ITEM DESCRIPTION
Failure Event

% of Specifies the percentage of the monitored signal’s maximum or minimum

value that represents specimen failure. When the monitored signal reaches this
level the process ends.
event type Selects the type of event the process looks for in the monitored signal. For
(Maximum or example, if you select maximum, a maximum or peak level will trigger the
Minimum) process.
Selects the input signal for which the process monitors your failure criteria.
monitored signal

Initial Value Specifies whether the process monitors the value of the selected signal relative
to zero (Absolute), or relative to the value of the signal when the Failure
Detector process started (Relative).
Sensitivity Specifies how much the monitored signal must change before a level is
considered a maximum event (peak) or a minimum event (valley).

382 Event Process Descriptions MTS MultiPurpose TestWare®

 Failure Detector Process

Options tab
Options Tab (part 1 of 2)
ITEM DESCRIPTION
Log Message As Assigns a severity level to the message (in ascending levels of severity:
Diagnostic, Information, Warning, or Error) and makes the message
available to the MPT Specimen Log.
If the Station Manager Station Log and the Basic TestWare Test Log are
configured to accept messages from all sources, then MPT makes the message
available to them also.
Note Unlike Station Manager and Basic TestWare, MPT does not generate
messages with a severity level of Fatal Error.

Each type of log will accept the message only if it has been configured to store
messages with the assigned severity level.
For instance, if the MPT Specimen Log is configured to accept messages with
a minimum severity level of Warning, and you assign Information as the
severity level for this message, then this message will not be recorded in the
MPT Specimen Log. In that instance the MPT Specimen Log would accept
messages having only Warning and Error severity levels.

You can specify the minimum severity level that each type of log will accept.
To do this:
• For MultiPurpose TestWare, select the MPT Options Editor, then
select the Specimen Log tab.

• For Station Manager, select Tools, then select Station Options, then
select the Station Log tab.

• For Basic TestWare, select Test Setup, then select the Test Log tab.

MTS MultiPurpose TestWare® Event Process Descriptions 383

Failure Detector Process

Options Tab (part 2 of 2)

ITEM DESCRIPTION
Action Specifies the action that occurs when the process completes.
None The process ends without generating a message or performing an action.
Station Power The process removes hydraulic power from the station. The test can be
Off resumed after you reset interlocks and reapply hydraulic power to the station.
Interlock The process triggers a hydraulic interlock and shuts down the hydraulic power
supply. The test can be resumed after you reset the interlock, reactivate
hydraulic power, and apply hydraulic power to the station.
Program The process triggers a program interlock. The test can be resumed after you
Interlock reset the interlock.
Program Stop The process stops the test. This action functions the same as clicking the Stop
button on the Station Controls panel.
Program Hold The process suspends the test until you click the Run button on the MPT
control panel. This action functions the same as clicking the Hold button on
the Station Controls panel.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

384 Event Process Descriptions MTS MultiPurpose TestWare®

 Failure Detector Process

Data Destination You set how your acquired data is saved on the Destination tab. The options are:

• Specimen data file

Acquired data is written to the specimen.dat file saved in your MPT

specimen.

MPT specimens are located in your MPT Specimens folder (MPT >
Specimens > spec01, spec02, and so forth).

• User-specified data file

Acquired data is written to the data file you specify (filename.dat) in the
MPT specimen.

• Discard data

Acquired data is written to the buffer, but is not saved to disk. Typically, this
option is used to trigger another process when the current acquisition
process fills its buffer.

How to Define a Failure Detector Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in your procedure table or in the navigation pane.

3. Click the Settings tab.

4. Define your desired specimen failure criteria with the Failure Event, Initial
Settings, and Sensitivity controls.

5. Click the Options tab.

6. Optional—Enable (check) the Log Message As control and select the type
of message you wish to generate.

7. Optional—Select the desired action you wish to occur if the specimen

condition matches your failure criteria and the process completes.

8. Click the Destination tab.

9. The default selection for this process is Discard data.If you want to acquire
data instead, click the destination for the acquired data in the Destination
list. If you click User-specified data file, type a file name in the User Data
File box. Type a description of the data file in the Data Header box.

10. Click the General tab.

MTS MultiPurpose TestWare® Event Process Descriptions 385

Failure Detector Process

11. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

12. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

13. In the Execute Process box, type number of times you want the process to
run.

14. Optional—In the Counter Type list, click a counter type.

15. Optional—If you enabled a counter, type a Counter Label.

16. Set the desired Start and Interrupt signals for the process in the procedure
table.

386 Event Process Descriptions MTS MultiPurpose TestWare®

Chapter 15
External Control Process Descriptions
You use external control processes to send signals to external controllers or logic
devices.

External Control Process Types

ICON PROCESS NAME DESCRIPTION
Digital Output Process Controls digital outputs.

Temperature Control Programs and/or controls an external temperature controller.

Process

MTS MultiPurpose TestWare® External Control Process Descriptions 387

Digital Output Process

Digital Output Process

About the Digital Output Process
The Digital Output process invokes the controller to issue digital signals that
can be sent to external switches and logic devices.

Note Before you configure a Digital Output process to signal an external

device, ensure that the signal values listed below are compatible with the
device.

The following signal options are available with the Digital Output process:

• None—The process does not send a digital signal, but the done signal can
still be used to start and interrupt other processes.

• Set—The process generates a logic high signal (+12 V DC).

• Clear—The process generates a logic low signal (0 V DC).

• Toggle—The process inverts the current state (from low-to-high or high-to-

low).

• Pulse—The process inverts the current state with a pulse signal, holds the
inverted state for the time specified in the Pulse Width control, then returns
to the original state.
Note Once the controller issues the pulse, the pulse will not be affected by the
stop or hold controls on the Station Controls panel.

Most of the time, processes stop or suspend themselves when MPT enters a
stopped or holding state. This is not true of the Digital Output process.

A Digital Output process will still function when MPT enters a Stopped or
Holding state. It is common to use a Program Event process to trigger a Digital
Output process (to turn off an external device) when the test is stopped or held.

388 External Control Process Descriptions MTS MultiPurpose TestWare®

 Digital Output Process

Keep in mind When you are configuring a Digital Output process for use in your procedure,
keep in mind:

• You must allocate a digital output resource in the station configuration file
that can be controlled by the Digital Output process. For more information,
see the MTS 793 Control Software manual (PN 100-147-130).

• You should choose an output signal option that is compatible with the
external device connected.

• Outputs assigned for a Digital Output process cannot be manually triggered

from Station Manager while MPT is in the execute mode.

• When the Digital Output process ends, the state of the external device will
remain in the current state until a new station is opened or until another
Digital Output process changes that state.
Note Use the Pulse option if you want to return the output to its initial state
when the process is done.

MTS MultiPurpose TestWare® External Control Process Descriptions 389

Digital Output Process

Digital Output Parameter Descriptions

Output table tab
Output Table Tab
ITEM DESCRIPTION
Digital Outputs Lists the digital outputs included on the Outputs tab.
Options Defines the type of digital signal that will be sent to the external device:
• None–The process does not send a digital signal, but the done signal can
still be used to start and interrupt other processes.

• Set–The process generates a logic high signal (+12 V DC).

• Clear–The process generates a logic low signal (0 V DC).

• Toggle–The process inverts the current state (from low-to-high or high-

to-low).

• Pulse–The process inverts the current state with a pulse signal, holds the
inverted state for the time specified in the Pulse Width control, and then
returns to the original state.

If you choose the Set, Clear, or Toggle selections, the process generates a done
trigger as soon as it sends the selected digital signals to the external device. If
you select the Pulse selection, the process does not generate the done signal
until the pulse width time has expired and those outputs return to their original
state.

Outputs tab Selects the digital output signals that this process will control. Use the arrow keys
to move the desired signals from the Available list to the Included list.

Settings tab
Settings Tab
ITEM DESCRIPTION
Pulse Width Specifies the duration of the pulse the controller sends to the external device.
You may select a time in the range of 100 milliseconds to 2 seconds with an
increment of 10 milliseconds.
Note This control is enabled only if you have a digital output signal using the
Pulse option.

390 External Control Process Descriptions MTS MultiPurpose TestWare®

 Digital Output Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

MTS MultiPurpose TestWare® External Control Process Descriptions 391

Digital Output Process

How to Define a Digital Output Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in your procedure table or in the navigation pane.

3. Click the Outputs tab.

4. Move all the signals you want to send digital signals to the Included list.
Move all the others to the Available list.

5. Click the Output Table tab.

6. Select an option for each digital output signal listed.

Note If you select Pulse for any signal, you must specify a Pulse Width on the
Settings tab.

7. Click the General tab.

8. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

9. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

10. In the Execute Process box, type number of times you want the process to
run.

11. Optional—In the Counter Type list, click a counter type.

12. Optional—If you enabled a counter, type a Counter Label.

13. Set the desired Start and Interrupt signals for the process in the procedure
table.

392 External Control Process Descriptions MTS MultiPurpose TestWare®

 Temperature Control Process

Temperature Control Process

About the Temperature Control Process
The Temperature Control process provides setpoint programming to external
temperature controllers cabled to your test system.

Depending on how your hardware is configured, you may be able to:

• Use temperature feedback from a single thermocouple to maintain a

specified temperature tolerance for a specified amount of time.

• Use temperature feedback from multiple thermocouples to ensure that the

desired temperature “soaks into” the specimen.
Note Typically, one thermocouple is placed in the chamber, and a second
thermocouple is attached to the physical specimen.

When you define a Temperature Control process, you must specify the desired
end level (temperature), a transition time to the specified temperature, and the
amount of time you want to maintain that temperature.

Note The external temperature controller must be properly cabled to your

controller in order for this process to work correctly. For cabling
information, see the Controller Setup or Programmer Setup manual that
accompanied your test system.

High and low The Model 793.00 System Software supports normal and “low-rate”
rate channels programming channels. Since temperature controllers do not require frequent
setpoint updates, they are often configured as low-rate channels.

By default, low-rate channels operate at a command rate of 25.6 Hz (1 Hz for

Eurotherm temperature controllers connected to the TestStar IIs J51 serial-port
interface). For more information on low-rate channels, see the MTS 793 Control
Software manual that accompanied your test system.

Note If a process includes both normal (high-rate) and low rate channels, the
channels will start and stop together. However, they may not stop at the
same level. They may be off in phase as much as one low-rate tick.

How to program Since low-rate channels do not require as much processing power, you can
multiple channels with program a temperature controller on a low-rate channel and a servovalve on a
your controller normal-rate channel at the same time.

MTS MultiPurpose TestWare® External Control Process Descriptions 393

Temperature Control Process

Controller options with Depending on the type of external controller you are programming, the
your controller Temperature Control process may be configured differently. See the following
sections for special considerations.

Eurotherm controllers Some controllers support a special cabling configuration for Eurotherm
temperature controllers. When a Eurotherm temperature controller is connected
to your system, special Temp Output 1 and Temp Input 1 resources must be
added to your hwi file.

When configured this way, the Temperature Control process sends temperature
commands to the Eurotherm controller through the J51 serial connector at 1 Hz,
and receives temperature feedback (for data acquisition) through the same
connector at 0.5 Hz (EI-BISYNCH protocol). In the Temperature Control
process parameters window, you can set a Control Tolerance and a Dwell
Period. If your configuration includes an additional analog input resource for an
external temperature conditioner, you can also set the Monitor Tolerance.

Other controllers with If the programming channel is configured as Program with Feedback, the
Program with Feedback process sends the MPT end level command to the temperature controller, and can
monitor temperature feedback to maintain a Control Tolerance and a Dwell
Period.

If your configuration includes an additional analog input resource for an external

temperature conditioner, you can also set the Monitor Tolerance.

Note The Control Tolerance and Monitor Tolerance features require

independent feedback channels.

Note In most cases, Program with Feedback channels are configured as

low-rate channels.

Other controllers with If the programming channel is configured as Program Only, the process sends
Program Only the MPT end level command to the temperature controller, which maintains the
control loop. In this scenario, you cannot set a Control Tolerance, Monitor
Tolerance, or limits on temperature feedback.

Note In most cases, Program Only channels are configured as low-rate

channels.

394 External Control Process Descriptions MTS MultiPurpose TestWare®

 Temperature Control Process

Temperature Control Parameter Descriptions

Command tab
Command Tab (part 1 of 2)
ITEM DESCRIPTION
Rate Type Specifies the method with which the controller ramps the temperature to the
specified end level.
The following rate types are supported:
• Time specifies the time to run one segment.

• Frequency specifies the time to run a two-segment cycle (even though a

single segment runs).

• Rate specifies a constant rate between the starting level and the end level.
Note You cannot use Rate for a process applied to multiple channels. If you
do, an error message will appear when the procedure is locked.

Dwell Period Specifies the amount of time the temperature feedback must stay within
tolerance before the process terminates. The dwell period begins as soon as the
temperature enters the specified control tolerance range.
Note If the temperature strays outside of the tolerance range during the
dwell period, the dwell period resets. The dwell period starts over
when the temperature reenters the tolerance range.

If you choose a dwell period of zero, the process will terminate as soon as the
temperature feedback becomes within tolerance.
If your station configuration supports the monitor feature, then the dwell
period applies to both the control tolerance and monitor tolerance ranges.
Channel Specifies the channel to which the window applies.
End Level Specifies the desired temperature—that is, the temperature you want the
controller to achieve (and maintain if a dwell period is specified).
Control Tolerance Specifies the amount the control temperature feedback may vary from the
specified End Level during the Dwell Period.
This feature requires feedback from the temperature sensor associated with the
current channel—that is, the feedback used by the external temperature
controller to achieve closed-loop control.

MTS MultiPurpose TestWare® External Control Process Descriptions 395

Temperature Control Process

Command Tab (part 2 of 2)

ITEM DESCRIPTION
Monitor Signal Specifies the temperature feedback signal associated with the monitor feature.
This feedback comes from a second temperature sensor in the enclosure, which
is conditioned by its own conditioner. This feedback is independent of the
feedback used by the external temperature controller to achieve closed-loop
control.
Monitor Tolerance Specifies the amount the monitor temperature feedback may vary from the
specified End Level during the Dwell Period.
If you use the monitor feature, the Temperature Control process monitors the
feedback associated with the Control Tolerance and the feedback associated
with the Monitor Tolerance concurrently. If either feedback strays outside of
its tolerance range the dwell period starts over.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

Channels tab Displays the channels available to this process. Use the arrow keys to move
desired channels from the Available list to the Included list.

396 External Control Process Descriptions MTS MultiPurpose TestWare®

 Temperature Control Process

How to Define a Temperature Control Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in your procedure table or in the navigation pane.

3. Click the Channels tab.

4. Move all the channels you want to program with this process to the
Included list. Move all the others to the Available list.

5. Click the Command tab.

6. Set the rate type (Time, Rate, or Frequency), set the units of measurement,
and then type a value.

7. In the Dwell Period box, set the units of measurement for the dwell period,
and then type a value.

8. In the Channels list, click each temperature control channel in succession.

9. In the End Level box, set the units of measurement for the end level, and
then type a value.

10. In the Control Tolerance box, type a value.

11. Optional—In the Monitor Signal list, click the channel you want to monitor
temperature feedback on (this signal should be from an independent
temperature sensor).

12. Optional—In the Monitor Tolerance box, type a value.

13. Repeat steps 8 through 12 for each temperature control channel.

14. Click the General tab.

15. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

16. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

17. In the Execute Process box, type number of times you want the process to
run.

18. Optional—In the Counter Type list, click a counter type.

19. Optional—If you enabled a counter, type a Counter Label.

MTS MultiPurpose TestWare® External Control Process Descriptions 397

Temperature Control Process

20. Set the desired Start and Interrupt signals for the process in the procedure
table.

398 External Control Process Descriptions MTS MultiPurpose TestWare®

Chapter 16
Other Process Descriptions
You use other processes to perform a variety of miscellaneous functions.

Other Process Types

ICON PROCESS NAME DESCRIPTION
Program Control Process Performs user-defined program actions such as Program Hold,
Program Resume, Interlock, and user defined actions.
Group Process Defines a process sub-group that may contain one or more other
processes.
MPT Calculation Process Modifies the value of numeric variables through the use of
mathematical expressions.

Operator Information Enables operator data entry (to be written to a data file) during
Process the test.
Start Application Process Launches another application and passes user-defined arguments
to that application.
Send Mail Process Send e-mail with a predefined message and a specimen log
attachment.

Set Controller Value Sets calculation parameters and variable values that can replace
Process existing values defined with the Station Manager application.

Auto Offset Process Zeros input signals that are not being used for the active control
mode.

Data Display Process Plots data signals on-screen during the test.

MTS MultiPurpose TestWare® Other Process Descriptions 399

Program Control Process

Program Control Process

About the Program Control Process
The Program Control process can be used to generate a message and/or perform
a specified action. Once the process performs the specified action, the process
ends.

Note Generally, you use a detector process to start a Program Control

process.

Logging Program If desired, you can save generated messages to the message logs.
Control messages
Note When logging messages via the Program Control process, messages
from the process may appear in the log before the “Running” message
that pertains to the procedure.

Program Control Suppose you wish to add a new capability to your existing procedure in which
process example the message “‘Failure Threshold Attained” is issued to the message log if
displacement feedback reaches 2 cm.

To do this, you would add a Data Limit Detector process and a Program Control
process to your procedure.

You would configure the Data Limit Detector process to monitor displacement
feedback and attain its done state if displacement feedback equals 2 cm.

You would sequence the Program Control process to start when the Data Limit
Detector process is done.

Then you would configure the Program Control process by selecting the
Message Only action, and typing “Failure Threshold Attained” in the message
entry box.

When you run a test with the modified procedure, the message “Failure
Threshold Attained” will log if displacement feedback reaches 2 cm.

400 Other Process Descriptions MTS MultiPurpose TestWare®

 Program Control Process

Program Control Parameter Descriptions

Action tab
Action Tab (part 1 of 3)
ITEM DESCRIPTION
Action Specifies the action that occurs when the process completes.
None The process ends without generating a message or performing an action.
Message Only The process writes a message to the MPT Specimen Log. (You define the
content of the message in the Message box.)
Program Hold The process suspends the test until you click the Run button on the Station
Controls panel. This action functions the same as clicking the Hold button on
the Station Controls panel.
Program Stop The process stops the test. This action functions the same as clicking the Stop
button on the Station Controls panel.
Program Similar to the Program Hold action, but the test must be resumed by a
Pause Program Resume action from another Program Control process.
Program Resumes a test paused by a Program Pause action.
Resume

Procedure The process stops the test and generates an error. The procedure goes to the
Error error state and cannot be resumed. To run the procedure again, click the Reset
button, then click the Run button on the Station Controls panel.
Station Power The process removes hydraulic power from the station. The test can be
Off resumed after you reset interlocks and reapply hydraulic power to the station.
Interlock The process triggers a hydraulic interlock and shuts down the hydraulic power
supply. The test can be resumed after you reset the interlock, reactivate
hydraulic power, and apply hydraulic power to the station.
Program The process triggers a program interlock. The test can be resumed after you
Interlock reset the interlock.

MTS MultiPurpose TestWare® Other Process Descriptions 401

Program Control Process

Action Tab (part 2 of 3)

ITEM DESCRIPTION
Log Message As Assigns a severity level to the message (in ascending levels of severity:
Diagnostic, Information, Warning, or Error) and makes the message
available to the MPT Specimen Log.
If the Station Manager Station Log and the Basic TestWare Test Log are
configured to accept messages from all sources, then MPT makes the message
available to them also.
Note Unlike Station Manager and Basic TestWare, MPT does not generate
messages with a severity level of Fatal Error.

Each type of log will accept the message only if it has been configured to store
messages with the assigned severity level.
For instance, if the MPT Specimen Log is configured to accept messages with
a minimum severity level of Warning, and you assign Information as the
severity level for this message, then this message will not be recorded in the
MPT Specimen Log. In that instance the MPT Specimen Log would accept
messages having only Warning and Error severity levels.
You can specify the minimum severity level that each type of log will accept.
To do this:
• For MultiPurpose TestWare, select the MPT Options Editor, then
select the Specimen Log tab.

• For Station Manager, select Tools, then select Station Options, then
select the Station Log tab.

• For Basic TestWare, select Test Setup, then select the Test Log tab.

402 Other Process Descriptions MTS MultiPurpose TestWare®

 Program Control Process

Action Tab (part 3 of 3)

ITEM DESCRIPTION
Message Defines the content of the message written to the log.

Include Counters* Includes counter information with the message written to the message log.
Note This option can be used to periodically log counter information.

* If the Program Control process is configured to include counters and log on a transition state change,
your log will contain two similar messages each time the state changes. This occurs because all
state transitions are automatically logged with counter information. Keep in mind that the automatic
logs are displayed as Information, while the Program Control logs are displayed in the severity level
you specify (Information, Warning, Error, or Diagnostic). This allows you discern between these log
entries if desired.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

For more information For more information on Actions, see “How to Use Actions with Processes” on
page 347.

MTS MultiPurpose TestWare® Other Process Descriptions 403

Program Control Process

How to Define a Program Control Process

1. Drag the icon from the Process Palette to your procedure table.

2. Click the process icon in your procedure table or in the navigation pane.

3. Click the Action tab.

4. In the Action list, click the action for this process.

5. Optional—If you want to write a message to the log when this process
triggers, select the Log Message As check box and click Diagnostic,
Information, Warning, or Error in the list.

6. Type the message that you want to send to the various message logs when
the process triggers.Select Include Counters if desired.

7. Click the General tab.

8. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

9. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

10. In the Execute Process box, type number of times you want the process to
run.

11. Optional—In the Counter Type list, click a counter type.

12. Optional—If you enabled a counter, type a Counter Label.

13. Set the desired Start and Interrupt signals for the process in the procedure
table.

404 Other Process Descriptions MTS MultiPurpose TestWare®

 Group Process

Group Process
About the Group Process
The Group process is basically a sub-procedure that runs within your main
procedure (or within another group process). On the procedure table, you can
double-click the Group process icon to display the Group Parameters window.

The Group table looks similar to the procedure table. You add processes to it in
the same manner.

For more information For information on sequencing Group processes, see “About Sequencing
Processes” on page 87.

How to Move In and Out of a Group Process Window

When you click a Group process icon on a table and click the Next Group Table
button on the MPT toolbar, a new Group table appears. You can also right-click
on a Group process icon on a table and select Open Table to make a new table
appear.

To move back to a Group process’ parent table, click the Previous Group Table
button on the toolbar:

Next Group Table

Previous Group Table

MTS MultiPurpose TestWare® Other Process Descriptions 405

Group Process

Group Process Parameter Descriptions

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

406 Other Process Descriptions MTS MultiPurpose TestWare®

 Group Process

How to Define a Group Process

1. Drag the icon from the Process Palette to your group or procedure

table.

2. Click the Group process icon in your group or procedure table, and then
click on the MPT Procedure Editor.

3. Add processes to your Group table. Make sure to set the parameters for each
process included in your group.

4. Set Start and Interrupt signals for each process in your group. Also, set the
Group is done when signal.

5. Click on the MPT Procedure Editor to return to the parent table.

6. Double-click the Group process icon in your group or procedure table.

7. Click the General tab.

8. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

9. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

10. In the Execute Process box, type number of times you want the process to
run.

11. Optional—In the Counter Type list, click a counter type.

12. Optional—If you enabled a counter, type a Counter Label.

13. Close the parameters window, and set the desired Start and Interrupt
signals for the process in the group or procedure table.

MTS MultiPurpose TestWare® Other Process Descriptions 407

MPT Calculation Process

MPT Calculation Process

About the MPT Calculations Process
Note The MPT Calculation process is available only if the controller is
equipped with the Variables feature (keyed option).

Note The MPT Calculation process does not pertain to calculated station
signals, or to the Calculation Editor in the Station Manager application.
The MPT Calculation process pertains only to variable parameters in
MultiPurpose TestWare.

The MPT Calculation process modifies MultiPurpose TestWare process

parameters that have been assigned to variables. With the MPT Calculation
process, you can modify variable values by applying constants, operators, and
mathematical operators. For example, if you assign the “Count” parameter of a
Cyclic Command process to be variable, you can use the MPT Calculation
process to modify “Count” so that “Count” = “Count” x 2.

Two methods to add In addition to the MPT Calculation process, you can also change variable values
calculations to variables by assigning calculations to parameters with the Variable Editor. The method you
use to add a given calculation to a variable has test design implications.

Using the Variable Editor When you use the Variable Editor to add a calculation to a variable, the
calculation is applied to the associated variable before the first process in the test
procedure is run. Also, the calculation is applied to the variable only once during
the execution of the test procedure, regardless of where the variable is used in the
individual test processes.

Using the MPT In contrast, when you use the MPT Calculation process to add a calculation to a
calculation process variable, the calculation is applied to the associated variable whenever the MPT
Calculation process is triggered. This means that:

• Any test process that uses the variable but runs before the MPT Calculation
process will not have the calculation applied, and

• The calculation is reapplied to the variable each time the associated MPT
Calculation process is triggered, so that the change to the variable value is
cumulative.Calculations process user interface

408 Other Process Descriptions MTS MultiPurpose TestWare®

 MPT Calculation Process

How to Define the MPT Calculation Process

1. Drag the icon from the Process Palette to your Group or Procedure
table.

2. Click the process icon in your Group or Procedure table.

3. Click the Variables tab, select the variables you wish to apply calculations
to in the Available list, then click > to move the selected variables to the
Included list.

4. Click the Calculation tab.

5. Build a mathematical expression as desired using

• The desired variables in the Signals list,

• Mathematical operators (+, -, and so on), and

• Mathematical functions in the Functions list.

Ensure you end each line in the expression pane with a semi-colon (“;”).

6. Click the General tab.

7. In the Name box, type a name for this process. (You can also name the
process in the Procedure table.)

8. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

9. In the Execute Process box, type number of times you want the process to
run.

10. Optional—In the Counter Type list, click a counter type.

11. Optional—If you enabled a counter, type a Counter Label.

Set the desired Start and Interrupt signals for the process in the Group or
Procedure table.

MTS MultiPurpose TestWare® Other Process Descriptions 409

Operator Information Process

Operator Information Process

About the Operator Information Process
The Operator Information process requires the operator to type and enter
information at a specific time during the test. The information can be archived
along with other data during the test.

Some examples of the types of things a test designer can do with the Operator
Information process include:

• Control the test flow by prompting the operator for information at any time
during the test.

• For tests that include varibles, prompt the operator during the test to change
variable values and automatically resume the test.

• Provide information about the physical specimen with the data file.

• Prompt the operator for specific information, such as:

– Operator ID

– Batch number

– Workstation number

– Part number

– Operator comments

When an Operator Information process is triggered, it displays a window that

requires the operator to enter the type of information specified by the test
designer. As the test designer, you can choose whether the information is non-
editable, or whether specific information, comments, or values must be typed
when the window appears.

When the operator types the required information in the window and clicks OK,
the information is output to a test data file.

410 Other Process Descriptions MTS MultiPurpose TestWare®

 Operator Information Process

Operator Information Suppose you want to define an Operator Information process that requires the
process example operator to type information about the physical specimen condition before the
data acquisition phase of the test starts. You also want to save this information to
a data file labeled “Surface Condition.”

Perform the following steps to define the Operator Information process:

1. On the Parameters tab, click the Add button to create Item1 in the Items
list. In the Type list, click String.

2. In the Label box, type Enter Surface Condition, and then press Enter.

3. Click the Destination tab.

A. In the Destination list, click User-specified data file.

B. In the User Data File box, type Surface Condition, and then press
Enter.

Process output Now, the test will pause when the Operator Information process starts, and the
Operator Information runtime window will appear. The data entry box will be
labeled Enter Surface Condition.

When the test is run, the operator will type the condition of the physical
specimen.

When the operator finishes typing the information and clicks OK, the
information is written to a separate file (named Surface Condition) that is stored
in the MPT specimen, and the procedure resumes with the next process.

For more information See “About Variables and the Operator Information Process” on page 109.

MTS MultiPurpose TestWare® Other Process Descriptions 411

Operator Information Process

Operator Information Parameter Descriptions

The Variables tab is available only

if the controller is equipped with
the variable feature (keyed option).

The Upgrade to Variables control

on the Parameters tab is available
only if the configuration includes
parameters that have not been
converted to variables.

Variables tab
Variables Tab (part 1 of 2)
ITEM DESCRIPTION
Show Parameters Page Displays or hides the Parameters page. If you do not use non-variable
parameters with this process, use this control to hide the page for
convenience.

412 Other Process Descriptions MTS MultiPurpose TestWare®

 Operator Information Process

Variables Tab (part 2 of 2)

ITEM DESCRIPTION
Available/Included The Available list displays the variable parameters that you can assign
to the Operator Information process. The Included list displays the
variable parameters that can be used by the Operator Information
process.
Editable Note Enabling the Editable control does not automatically make all
the variables in the included list editable. Enabling the
Editable control applies only to the variables selected
(highlighted) in the Included list.

When enabled (checked) for the selected variable parameters in the

Included list, allows you to edit variable values when displayed in the
variable run-time display.

Parameters tab
Parameters Tab (part 1 of 3)
ITEM DESCRIPTION
Upgrade to Variables Note This control is available only if the controller is equipped with
the variables feature (keyed option), and if the test procedure
includes non-variable parameters.

Note When upgrading a Real or Integer parameter to a variable, the

Inclusive attribute is automatically enabled for the parameter’s
range. That is, the specified Minimum and Maximum limit
values are automatically included within the parameter’s
range.

Converts the parameters currently assigned to the Operator

Information process to variables.
Items Displays the Operator Information process toolbar and your current
items.

Creates a new item.

Add/Add after selection
When the Items list is empty, this button is labeled “Add”. Once an
item has been added, it changes to “Add after selection.” If you select
an item and then click this button, a new item will be added after the
selected item.

Adds a new item before the selected item.

Add before selection

MTS MultiPurpose TestWare® Other Process Descriptions 413

Operator Information Process

Parameters Tab (part 2 of 3)

ITEM DESCRIPTION

Deletes the selected item.

Delete selection

Moves the selected item up one position.

Move selection up

Moves the selected item down one position.

Move selection down

Label Specifies the item label at run time.

When you select an item, its label appears in the Label box. To rename
an item, type the new name and then press Enter.

414 Other Process Descriptions MTS MultiPurpose TestWare®

 Operator Information Process

Parameters Tab (part 3 of 3)

ITEM DESCRIPTION
Type Specifies the type of information that will be displayed in the
Operator Information window:
String—Can be any arbitrary text string.
Real—Can be any real number (includes decimal expressions, such as
1.2) within the defined range. If you select Real, the dimension boxes
are enabled (see below).
Integer—Can be any number (zero, 1, 2, and so on) within the defined
range.
List—A list of items from which the operator can select. This
selection allow the designer to create a custom list for the operator.
Attribute None—Operator can edit or delete the default entry.
Non-Editable—Operator cannot edit text.
Non-Blank—Operator must type information. The entry cannot be
blank.
Default Value Specifies a default value displayed in the Operator Information data
entry box.
Note The operator can change units when entering data, but MPT
writes the data to the data file in the units selected here.

Dimension Specifies the dimension for the Default Value.

(Real Type only)

Minimum/Maximum Enables the minimum/maximum limit to be enforced at runtime.

(Real and Integer Types only)
Note If the operator tries to type a value outside the limits, the
displayed value will revert to the last valid limit value.

Inclusive When selected, includes the specified minimum/maximum limit value.

(Real and Integer Types only) If this checkbox is cleared, the value you type can be close to but
cannot equal the limit value.

Selections This is identical to the Items toolbar. With it you can create, delete,
(List Type only) and choose selections available for the custom list.
Description Edits the default list names generated by the Selections toolbar.
(List Type only)

Note Buffer settings and header options are not available for this process.

MTS MultiPurpose TestWare® Other Process Descriptions 415

Operator Information Process

Destination tab
Destination Tab
ITEM DESCRIPTION
Buffer Size Specifies the maximum number of data elements the buffer will store before
data is written to the disk.
Data Header Includes a label that describes the data on each buffer that is written to a file.
Destination Specifies where data is saved:
Specimen data file—the process writes buffers of data to the MPT
specimen.dat file in the Specimen.
User-specified data file—the process writes buffers of data to a separate data
file in the Specimen (yourname.dat).
Discard data—the process will not write data to the Specimen.
User Data File Specifies the name of the file where data is saved. This lets you create separate
data files in the MPT specimen. This control is enabled only when you have
selected User-specified data file in the Destination list above.
Buffer Type Specifies the buffer type.
Write First Data Header Specifies if the data header is written for each buffer or suppressed after the
Only first header is written. If disabled (unchecked), a data header is written for each
buffer.
Note This feature is not recommended for procedures with multiple data
acquisition processes writing data to the same data file.

416 Other Process Descriptions MTS MultiPurpose TestWare®

 Operator Information Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

How to Define an Operator Information Process without Variables

1. Drag the icon from the Process Palette to your group or procedure
table.

2. Click the process icon in your group or procedure table, or in the navigation
pane.

3. Click the Parameters tab, and then click to create an item.

4. In the Label box, type the text you want to appear when the runtime
window is displayed.

5. In the Type list, click the item type, and then click the Attribute.

6. In the Dimension list, click the dimension (real types only).

7. In the Selections panel, add, arrange, and label custom list items (list types
only).

8. In the Default Value box, type a default value.

9. Enter Minimum and Maximum values (real and integer types only).

MTS MultiPurpose TestWare® Other Process Descriptions 417

Operator Information Process

10. Repeat steps 3 - 9 for each item you want to define.

11. Click the Destination tab.

12. Type a description of the data file in the Data Header box.

13. In the Destination list, click the destination for the acquired data. (If you
click User-specified data file, type a file name in the User Data File box.)

14. Click the General tab.

15. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

16. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

17. In the Execute Process box, type number of times you want the process to
run.

18. Optional—In the Counter Type list, click a counter type.

19. Optional—If you enabled a counter, type a Counter Label.

20. Set the desired Start and Interrupt signals for the process in the group or
procedure table.

How to Define an Operator Information Process with Variables

1. Drag the icon from the Process Palette to your Group or Procedure
table.

2. Click the process icon in your Group or Procedure table.

3. Click the Variables tab, and use the arrow keys to move the desired
variables from the Available list to the Included list.
Note If you need to create variables (if variables are not available in the
Variables page), use the Variables Editor to create variables for use with
this process.

4. If you want the operator to have the ability to edit variable values in the run-
time window, select (highlight) the desired variables in the Included list and
enable the Editable control.
Note Enabling the Editable control does not automatically make all the
variables in the included list editable. Enabling the Editable control
applies only to the variables selected (highlighted) in the Included list.

418 Other Process Descriptions MTS MultiPurpose TestWare®

 Operator Information Process

5. If available, click the Parameters tab and define parameters as desired.

6. Click the Destination tab.

7. Type a description of the data file in the Data Header box.

8. In the Destination list, click the destination for the acquired data. (If you
click User-specified data file, type a file name in the User Data File box.)

9. Click the General tab.

10. In the Name box, type a name for this process. (You can also name the
process in the Procedure table.)

11. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

12. In the Execute Process box, type number of times you want the process to
run.

13. Optional—In the Counter Type list, click a counter type.

14. Optional—If you enabled a counter, type a Counter Label.

15. Set the desired Start and Interrupt signals for the process in the Group or
Procedure table.

For more information For information about creating variables with the Variable Editor, see:

• “How to Create, Edit, Assign, and Unassign Variables with the Right-Click
Method” on page 120

• “How to Create a Variable with the Make Tool” on page 121

MTS MultiPurpose TestWare® Other Process Descriptions 419

Start Application Process

Start Application Process

About the Start Application Process
With the Start Application process, you can launch another application with
arguments when the Start Application process is triggered.

Start Application Suppose you want to create a test in which the procedure automatically displays
Example data when the test is complete. With the Start Application process, you can
invoke the Notepad application to display the specimen data file that contains the
data acquired during the test, as shown below.

Using variables with the If your test procedure includes variables, you can use the Start Application
Start Application process to pass variable values to the target application. You do this by adding the
process desired variables to Start Application process’ argument parameter.

420 Other Process Descriptions MTS MultiPurpose TestWare®

 Start Application Process

Start Application Parameter Descriptions

Settings tab
Settings Tab (part 1 of 3)
ITEM DESCRIPTION
Application to Run Specifies the application that the process will launch.
• To run an application registered by Microsoft or available in the system
path, you do not have to specify a full path. For example, if you want to
select Microsoft Excel, you can simply type “excel”.

• To run other applications, type the full path to the application in this box,
or browse for the application to find its path.
Arguments Specifies an input or parameter that will be passed to the selected Application
to Run when the process is triggered. The argument may be anything
appropriate for the application, like a file name, folder name, variable, and so
forth.
The Argument list includes predefined placeholders that will be substituted
with actual information when the process runs. Selecting a placeholder will
insert it into the argument at the current position.
Argument placeholders include:
• MPT Specimen–specifies the current MPT specimen directory.

• Procedures Directory–specifies the procedures directory path defined in

the Project Manager application.

• Profiles Directory–specifies the profiles directory path defined in the

Project Manager application.

• Configurations Directory–specifies the configurations directory path

defined in the Project Manager application.

• Station Name–specifies the station name defined in the Project Manager

application.

MTS MultiPurpose TestWare® Other Process Descriptions 421

Start Application Process

Settings Tab (part 2 of 3)

ITEM DESCRIPTION
Arguments (continued) Argument Syntax Requirements:
When you type arguments directly, you must observe standard command line
syntax.
• You must type a space between multiple arguments. For example, if you
enter two arguments such as: “<V#Variable1> <V#Variable2>” you must
add a space must between the two arguments.

• If path placeholder results in path with spaces, you must add quotes to the
argument. For example, "<Specimen Directory>\myfile.dat" will require
the user to type the quotes if the path defined by <Specimen Directory>
has space(s) in it.
Variable Name Use the selections in the Variable Name submenu to create an argument that
passes the value of the variable(s) to the selected Application to Run when the
process is triggered.
To add a variable to the argument: in the Argument list, click Variable Name
and select a variable from the submenu.
Note Multiple variables must be separated by a space.

Note This control is available only if the controller is equipped with the
variables feature (keyed option).

Default Path Specifies the default path to the selected argument. Define the default path by
typing the desired path in the entry box, by browsing to the desired location, or
by selecting one of the predefined directory locations in the Default Path list,
as shown below:

You can also use the Default Path text box to define the Application to Run
path if the path was not defined in the Application to Run text box.

422 Other Process Descriptions MTS MultiPurpose TestWare®

 Start Application Process

Settings Tab (part 3 of 3)

ITEM DESCRIPTION
Wait for application to When enabled, the process will wait until the application has completed before
complete completing (before it sends out its “done” trigger).
When disabled, the process will complete immediately after starting the
specified application.
Resume Options Defines how the process will resume when the procedure has been stopped and
unlocked while waiting for the selected application to complete.
Start application and wait for it to complete–causes the process to restart the
application and complete when the application has completed.
Proceed as if application has completed–causes the process to complete
immediately.
Prompt operator for resume option–displays a message which causes the
operator to either:
• Restart the application

OR

• Proceed as if the application has completed.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

MTS MultiPurpose TestWare® Other Process Descriptions 423

Start Application Process

Start Application Process Example

To display the contents of the “specimen.dat” file in the current MPT specimen
directory:
1. Type “notepad” in the Application to Run text box.

2. Define the argument: “<MPT Specimen>\specimen.dat” in the Arguments

text box.

A. In the Arguments list, click MPT Specimen.(MPT Specimen will

appear between angle brackets in the entry box).

B. Add a back slash character followed by the file name: “specimen.dat”.

You could also type “<MPT Specimen>\specimen.dat” in the Arguments text

box.

424 Other Process Descriptions MTS MultiPurpose TestWare®

 Start Application Process

How to Define the Start Application Process

1. Drag the icon from the Process Palette to your group or procedure
table.

2. Click the process icon in your group or procedure table, or in the navigation
pane.

3. Click the Settings tab.

4. Select the Application to Run, Argument, and Default Path as desired.

5. Optional—If the test procedure includes variables whose values you wish to
pass to the application, select Arguments submenu, then select the desired
variable in the Variable Name submenu.

6. Optional—Select Wait for the application to complete and a Resume

Option.

7. Click the General tab.

A. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

B. Select the Process Enabled check box. (If this box is cleared, the
process will not run.)

C. In the Execute Process box, type number of times you want the
process to run.

D. Optional—In the Counter Type list, click a counter type.

E. Optional—If you enabled a counter, type a Counter Label.

8. Set the desired Start and Interrupt signals for the process in the group or
procedure table.

MTS MultiPurpose TestWare® Other Process Descriptions 425

Send Mail Process

Send Mail Process

About the Send Mail Process
The Send Mail process allows you to send e-mail with a predefined message and
recent log entries attached. You can configure this process to send e-mail
notifications as desired processes complete to monitor the progress of a test
procedure.

An application called mtssendmail.exe runs in the background to send the e-mail

messages.

Important You may need to consult with your network administrator or

Information Technology department to properly configure this
process.

Send Mail Parameter Descriptions

Compose Mail tab Enter e-mail addresses of recipients, the e-mail subject, and message body text.
You can also choose to attach log entries to the generated e-mail, and limit the log
size.

Limit Log Size Options

Limit Log Size by Check this box to limit the size of the log file attached to the e-mail.
There are four criteria for limiting the log size.
Most Recent Run Includes all log entries from the most recently run procedure.
Entry Count Attaches the most recent entries (maximum 200).
Character Count Limits the log based on the number of characters (maximum 8 KB).
Time Span Limits the time period up to the 10 previous days.

Note Log entry attachments cannot exceed 8KB.

Use the Send Mail Now button to test that the process works properly.

426 Other Process Descriptions MTS MultiPurpose TestWare®

 Send Mail Process

Servers tab Configure server settings on this tab. You may need to contact your network
administrator or IT department to configure this tab.

Servers Tab
ITEM DESCRIPTION
Maximum Wait Time Define the maximum time the process will wait for the server to respond without
producing an error (maximum of 60 seconds).
Server Name Select a server from the list. You can also edit the server display name in this field.
Add Click to add a new server.
Delete Click to delete the server displayed.
SMTP Server Enter the Simple Mail Transfer Protocol name or server IP address.
Return e-mail Enter the address that will appear in the “From” field of the generated message. This
must be a valid e-mail address permitted by your SMTP server.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed in the Procedure or Group process window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only when the
process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the MPT
control panel.
Note If this box is blank, the process name is used as the counter label.

MTS MultiPurpose TestWare® Other Process Descriptions 427

Send Mail Process

How to Define the Send Mail Process

1. Drag the icon from the Process Palette to your Group or Procedure
table.

2. Click the process icon in your Group or Procedure table.

3. Click the Servers tab.

4. Enter the amount of time (up to 60 seconds) that the process will wait for the
e-mail to send in the Maximum Wait Time field.

5. Select the name of the server that the process will access to send the e-mail
in the Server Name field. Use the Add and Delete buttons as needed when
configuring this field.

6. Enter the SMTP Server address.

7. Enter an e-mail address in the From field.

8. Click the Compose Mail tab.

9. In the Recipients tab, enter the e-mail address(es) of the intended recipients,
separated by semicolons.

10. In the Subject tab, enter text that will appear as the subject line of the
generated e-mail.

11. In the Message Body field, enter text that will appear as the body of the
generated e-mail.

12. Optional—select Attach Most Recent Log Entries to add recent log entries
as attachments to the generated e-mail.

Select a limiting factor for the attached log entries: Most Recent Run,
Entry Count, Character Count, Time Span.

13. Optional—Click Send Mail Now to test the process.

14. Click the General tab.

15. In the Name box, type a name for this process. (You can also name the
process in the Procedure table.)

16. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

17. In the Execute Process box, type the number of times you want the process
to run.

428 Other Process Descriptions MTS MultiPurpose TestWare®

 Send Mail Process

18. Optional—In the Counter Type list, click a counter type.

19. Optional—If you enabled a counter, type a Counter Label.

20. Set the desired Start and Interrupt signals for the process in the Group or
Procedure table.

MTS MultiPurpose TestWare® Other Process Descriptions 429

Set Controller Value Process

Set Controller Value Process

About the Set Controller Value Process
This process can change calculation parameter and calculation variable values
defined in the Station Manager application. You set initial calculation parameter
and calculation variable values with the Calculation Editor.

Typical uses include:

• Changing Station Manager calculation parameter values in calculated input

equations used for control feedback or data acquisition, or changing
calculated output equations used to drive a valve or other output resource.

• Changing Station Manager calculation variable values to execute

conditional calculations

Assigning new values When you select a calculation parameter or variable, you can set a new value
using one of the following methods:

• By entering a new calculation parameter or variable value in its associated

Value to Set text box.

OR

• By assigning an MPT variable in the Value to Set text box that defines the
parameter or variable value.
Note The calculation parameter and variable values set in Station Manager
will not change to new values until the Set Calculation Parameter
process is triggered.

Optional—use an Operator Information or MPT Calculation process to

change the variable value during the test.

430 Other Process Descriptions MTS MultiPurpose TestWare®

 Set Controller Value Process

Process execution When the process is triggered, the calculation parameter and variable values you
set within the process override their associated values defined in the Station
Manager application.

After the process runs:

• Calculation parameter values in the Station Manager application will remain

at the current value and are saved with the parameter set unless you choose
not to save changes when you exit Station Manager.

• Calculation variable values in the Station Manager application will remain

at the current value, but are not saved with the parameter set when you exit
Station Manager.
Note The calculation parameter access level set in the Station Manager
application does not apply to the Set Controller Value process.

Set Controller Value Process Example

A typical application for this process is where a calculation defined in the Station
Manager application calculates strain. In this application, calculation parameters
used in the strain calculation may change for different specimens.

The MPT procedure can use the Set Controller Values process to push new
calculation parameter values down into the Station Manager calculation.
Calculation parameter values can be manually entered or, if a variable is
assigned, changed at various points in the procedure.

MTS MultiPurpose TestWare® Other Process Descriptions 431

Set Controller Value Process

Set Controller Value Process Parameter Descriptions

Calc Parameters and
Calc Variables tabs
Calc Parameters and Calc Variables Tabs
ITEM DESCRIPTION

Available/Selected The Parameters page lists all the calculation parameters defined in the Station
Manager application.
The Variables page lists all the calculation variables defined in the Station
Manager application.
Use the arrow keys to move the desired items from the Available to the Selected
list. The items in the Selected list will appear on the Values page, where you can
set their values.

Values tab
Values Tab
ITEM DESCRIPTION
Calc. Parameter Lists all the calculation parameters and variables defined in the Station Manager
application and selected in the Parameters and Variables pages.
Set Value Allows you to enter the calculation parameter or variable value that will be used
in place of the associated value set in Station Manager. You can enter a new value
directly or assign an MPT variable.

432 Other Process Descriptions MTS MultiPurpose TestWare®

 Set Controller Value Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed in the Procedure or Group process window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only when
the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the MPT
control panel.
If this box is blank, the process name is used as the counter label.

How to Define the Set Controller Value Process

WARNING

Small calculation parameter changes can produce large control-loop

changes, resulting in violent actuator movement.

Violent actuator movement can result in injury and equipment damage.

Use care when changing calculation parameters.

Note To use this process, you must have calculation parameters and/or
calculation variables defined in the station configuration file. You define
calculation parameters and calculation variables with the Equation Editor
in the Station Manager application.

1. Drag the Set Controller Value process icon from the Process Palette
to a Group or Procedure table.

2. Click the Set Controller Value process icon in the Group or Procedure
table.

MTS MultiPurpose TestWare® Other Process Descriptions 433

Set Controller Value Process

3. Set the desired Start and Interrupt signals for the process in the Group or
Procedure table.

4. Click the General tab.

A. In the Name box, type a name for this process. (You can also name the
process in the Procedure table.)

B. Select the Process Enabled check box. (If this box is cleared, the
process will not run.)

C. In the Execute Process box, type the number of times you want the
process to run.

D. Optional—In the Counter Type list, click a counter type.

E. Optional—If you enabled a counter, type a Counter Label.

5. Click the Calc Variables tab.

A. Select the desired calculation variables in the Available list.

B. Use the arrow keys to move the selected items from the Available list
to the Selected list. These items in the Selected list will appear in the
Values page.

6. Click the Calc Parameters tab.

A. Select the desired calculation parameters in the Available list.

B. Use the arrow keys to move the selected items from the Available list
to the Selected list. These items in the Selected list will appear in the
Values page.

7. Click the Values tab, and define new values for calculation parameters and
variables.

Enter a new calculation parameter or variable value.

To enter a new calculation parameter or variable value—in the Value to

Set text box, type the new value.

To enter an MPT variable as a new calculation value—right-click in the

Value to Set text box, click Assign Variable, and select an MPT variable.

The text box changes color to indicate that an MPT variable is assigned to
that calculation parameter.

434 Other Process Descriptions MTS MultiPurpose TestWare®

 Set Controller Value Process

8. Optional—If an MPT variable is assigned in the Value to Set text box, use
one of the following methods to change the value of a variable:

• Use an Operator Information process where an operator can redefine a

variable based on test or specimen requirements.

• Use a calculation to define the variable. Calculations can be added to a

variable using the Variable Editor or a Calculation Process.

For more information For more information about changing the variable assigned to the Set Calculation
Parameter process:

See “About the Variable Editor” on page 115.

See “MPT Calculation Process” on page 408.

See “Operator Information Process” on page 410.

MTS MultiPurpose TestWare® Other Process Descriptions 435

Auto Offset Process

Auto Offset Process

About the Auto Offset Process
The Auto Offset process allows you to zero input signals that are not being used
for the active control mode. The process completes after all selected signals have
been zeroed. If a selected signal is active when the process is triggered, an error
will be logged.

Auto Offset process Suppose you want to run a sweep test on a pliable specimen in force control. As
example the specimen becomes more compliant, displacement will increase, so you may
want to apply an offset to displacement after each pass.

• You can achieve this by adding a Sweep Command process and Auto
Offset process to a Group process. Configure the test so that the Auto
Offset process triggers after each pass of the Sweep Command. As
displacement increases, the signal will be continually zeroed.

436 Other Process Descriptions MTS MultiPurpose TestWare®

 Auto Offset Process

About Feedback Signal Offset

The Auto Offset control in the Station Manager application zeros the output of
the conditioner without shifting the electrical zero reference of the conditioner.
An auto offset can be applied to the current control feedback with station
pressure applied.

For example, suppose your LVDT output is 1 cm when the actuator is at its null,
midstroke position. You can compensate for this positive LVDT output by
offsetting the feedback signal –1 cm. The actual displacement value (Current
Value) is now zero.

Usable range Because the range centers around the calibrated electrical zero of the sensor, an
offset limits the usable range in the direction you shift it. For example, in a ±2 cm
range, offsetting the signal -1 cm from its zero position results in control ranges
of +1 cm on the positive side and –3 cm on the negative side.

Controller/Application
Conditioner
Sensor Conditioner Digital
Voltage Voltage Signal
Gain A/D

Electrical Zero* Offset

*Electrical zero is only available on certain The offset applies to the feedback signal.
types of conditioners. You specify the offset in engineering units.

Offset considerations Consider these items before offsetting a feedback signal:

• Offset alters the feedback signal used by the digital (PIDF) controller and is
included in the closed-loop control calculations.

• Offset cannot be used to clear interlocks tripped by signal saturation.

• Offset is limited to ±½ the current full-scale range.

• The usable range is limited in the direction that zero is offset.

MTS MultiPurpose TestWare® Other Process Descriptions 437

Auto Offset Process

Auto Offset Parameter Descriptions

Signals tab Displays the channels available to this process. Use the arrow keys to move
channels from the Available list to the Included list.

Settings tab Allows you to select how the process will respond to an error. Stop the test and
report the error is selected by default. You can change it to Log the error and
continue the test.

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed in the Procedure or Group process window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only when the
process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the MPT
control panel.
Note If this box is blank, the process name is used as the counter label.

438 Other Process Descriptions MTS MultiPurpose TestWare®

 Auto Offset Process

How to Define the Auto Offset Process

1. Drag the icon from the Process Palette to your Group or Procedure
table.

2. Click the process icon in your Group or Procedure table.

3. Click the Signals tab.

4. Move all signals which you want to apply the offset from the Available list
to the Included list.
Note Applying an offset to an active signal will generate an error. Depending
on the error handling method you select, the process can stop, or
continue by skipping the signal.

5. Click the Settings tab.

6. Select the Error Handling method:

• Stop the test and report the error (default).

• Log the error and continue the test.

7. Click the General tab.

8. In the Name box, type a name for this process. (You can also name the
process in the Procedure table.)

9. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

10. In the Execute Process box, type the number of times you want the process
to run.

11. Optional—In the Counter Type list, click a counter type.

12. Optional—If you enabled a counter, type a Counter Label.

13. Set the Start and Interrupt signals for the process in the Group or
Procedure table.

MTS MultiPurpose TestWare® Other Process Descriptions 439

Data Display Process

Data Display Process

About the Data Display Process
The Data Display process acquires data on the signals you specify, and then
plots the data on-screen during the test.

With this process, you can view events as they occur on multiple data channels.
This process acquires data each time a selected signal changes a specified
amount. This process must run in parallel with a command process; it cannot
acquire data unless the command process is performing an action that it can
measure.

Note The Data Display process does not store data to a disk. The data that is
acquired is used for display only.

Within a single Data Display process, you can define any number of plot
configurations, each of which can be enabled or disabled for the test. When the
test starts, a plot window (similar to the Station Manger Scope window) appears
on-screen for each enabled plot configuration.

Plot Window Example

440 Other Process Descriptions MTS MultiPurpose TestWare®

 Data Display Process

Data Display Parameter Descriptions

Plots tab This window lets you create, delete, and rearrange plots using its toolbar icons.

Note To save the position of the plot window(s), you must save the procedure
(’position’ refers to the location of the plot on your PC monitor). If you
move the plot window from its default position and close the procedure
without saving, the plot window will appear in its default (or last saved)
position.

Plots Tab
ITEM DESCRIPTION
Plots Displays the Data Display process toolbar and your current plots.

Creates a new plot.

Add/Add after
selection When the Plots list is empty, this button is labeled “Add”. Once an item has
been added, it changes to “Add after selection.” If you select a plot and then
click this button, a new plot will be added after the selected item.

Adds a new plot before the selected item.

Add before
selection

Deletes the selected plot.

Delete selection

Moves the selected plot up one position.

Move selection
up

Moves the selected plot down one position.

Move selection
down

Plot Title Specifies the plot window title.

Plot Enabled Displays the plot when the test is run.
Note Only plots that are enabled are displayed on-screen during the test.

Data display plot setup This window lets you customize the axes for each plot. Characteristics for each
tab plot are defined separately. Plot characteristics are specified on four tabs: X-Axis,
Y1-Axis, Y2-Axis, and Options.

MTS MultiPurpose TestWare® Other Process Descriptions 441

Data Display Process

Click each tab to access a different set of plot parameters.

Plot Setup Tab (part 1 of 7)

ITEM DESCRIPTION
Plot Specifies the plot being configured.
X-Axis Subtab Determines settings for the horizontal or x-axis.
Signal Specifies the signal for the x-axis of the plot.
Show Values Displays the selected signal values in a table in the Plots window.
Zero Offset Note This control is most useful for continuously increasing signals, such as
time, segment count, and so forth.

Determines the starting point:

• Absolute: Plotted data begins where the output begins

• Relative: Plotted data begins at zero

Example: Suppose the Test Procedure includes a Cyclic Command process that
precycles the specimen for 30 seconds prior to starting another Cyclic
Command process that applies test cycles to the specimen, and a parallel Data
Display process that displays a plot of the test cycles. In this scenario, if Zero
Offset is set to Absolute and the x-axis signal is time, the plot will begin at 30
seconds, leaving a gap from 0 to 30 seconds on the plot. If Zero Offset is set to
Relative, the plot will begin at 0 seconds.
Units Specifies the units for the x-axis.
Initial Sets the initial x-axis maximum and minimum values. The plots will
Minimum/ automatically rescale if necessary.
Maximum

Y1/Y2 Axis Subtabs Determines the settings for the left and right vertical axes. Selections for the
Y2-Axis are the same as the Y1-Axis.
List Filter Lists categories of signals you can plot, based on dimension. For example, if
you select Length, the Signals of Dimension list will contain only signals with
a length dimension. The List Filter ensures that the signals you select to plot
on a given axis share the same dimension.

442 Other Process Descriptions MTS MultiPurpose TestWare®

 Data Display Process

Plot Setup Tab (part 2 of 7)

ITEM DESCRIPTION
Signals of Displays signals on the plot with unit dimensions matching the current List
Dimension/ Filter selection.
Included on
Plot Use the > to move individual signals, or the >> to move all signals, from the
Signals of Dimension list to the Included on Plot list as desired.
Note Only signals with the same dimension can be plotted on the same
axis.

Signal Displays the signals that were added to the Included on Plot list.

Note This control, and those listed below it, are not displayed until you move
a signal to the Included on Plot list.

Show Values Shows or hides the selected signal values in a table below the plot (in the plot
window).
Units Specifies the units for the Y1 or Y2 axis.
Initial Sets the Y1 or Y2 axis initial maximum and minimum values. The plot will
Minimum/ autoscale if necessary.
Maximum

MTS MultiPurpose TestWare® Other Process Descriptions 443

Data Display Process

Plot Setup Tab (part 3 of 7)

ITEM DESCRIPTION
Options Subtab Lets you define visual characteristics of the plot and buffer size, and choose
which data is displayed.
Show Grid Hides or displays the grid in the plot window.
Show Legend Hides or displays the legend in the plot window.
Transpose X/Y Transposes the X and Y1 axes.
Axis
Note This option is disabled if both the Y1 and Y2 axes are used.

Buffer Size Sets the size of the display buffer, which ranges between 4096 and 16,384.
Note When the buffer is filled, room for new data in the buffer is based on
the Decimation Option (data is deleted according to the current
Decimation Option).

444 Other Process Descriptions MTS MultiPurpose TestWare®

 Data Display Process

Plot Setup Tab (part 4 of 7)

ITEM DESCRIPTION
Decimation Decimation refers to discarding a portion of the data in the display buffer when
Option it fills. Each option controls the flow of data through the display buffer in a
unique way, and creates a corresponding type of display on the plot.
Each option follows the same general process:
• The buffer fills with data

• The data is decimated (reduced) according to the option selected

• The retained data is shifted to the front of the buffer to form a contiguous
block

• The process is repeated

Every Other Point—This option causes the buffer to accept acquired data
until it fills, perform a decimation of every other point, shift data, and repeat.
This option decreases the resolution of the initial data as a function of the
number of times the buffer fills.
First pass: When the buffer fills for the first time, it accepts every point of
acquired data until the buffer is full, then performs a decimation by discarding
every other point in the buffer. The retained points are shifted to the front of the
buffer to form a contiguous block, leaving the back half of the buffer empty
and ready to receive new data.
Second pass: The buffer fills the second time as before until full, then performs
another decimation and data shift.
Subsequent passes: The process is repeated in subsequent passes in the same
way until stopped.

MTS MultiPurpose TestWare® Other Process Descriptions 445

Data Display Process

Plot Setup Tab (part 5 of 7)

ITEM DESCRIPTION

Reduced Rate—This option causes the buffer to accept acquired data until it
fills, perform a decimation of every other point, shift data, accept new data at
one-half the rate used on the previous pass (every point on the first pass, every
second point on the second pass, every fourth point on the third pass, and so
forth), and repeat. This option results in data resolution that is constant
regardless of the number of times the buffer fills.
First pass: When the buffer fills the first time, it accepts every point of
acquired data until the buffer is full, then performs a decimation to the entire
buffer by removing every other point. The retained points are shifted to the
front of the buffer to form a contiguous block, leaving the back half of the
buffer empty and ready to receive new data.
Second pass: When the buffer fills the second time, it accepts every other point
of acquired data until the buffer is full, then performs a decimation to the entire
buffer by removing every other point. The retained points are shifted to the
front of the buffer as before.
Third pass: When the buffer fills the third time, it accepts every forth point of
acquired data until the buffer is full, then performs a decimation to the entire
buffer by removing every other point. The retained points are shifted to the
front of the buffer as before.
Subsequent passes: The process is repeated until stopped, with the factor used
by the buffer to accept new data doubling with each subsequent pass, and the
decimation always removing every other point in the buffer.

446 Other Process Descriptions MTS MultiPurpose TestWare®

 Data Display Process

Plot Setup Tab (part 6 of 7)

ITEM DESCRIPTION

Discard Oldest Points—This option causes the buffer to accept acquired data
until it fills, perform a decimation that discards the oldest points in the buffer,
shift data, and repeat. If the selected signal is something that is always
increasing such as time, the result is a scrolling effect. This method of
discarding points prevents the plot from redrawing on any given update cycle if
the number of points acquired is relatively small.

First and subsequent passes: On any given pass, the buffer accepts every point
of acquired data until the buffer is full, then performs a decimation by
discarding the oldest points in the buffer. The retained points are shifted to the
front of the buffer to form a contiguous block, leaving the back half of the
buffer empty and ready to receive new data.

The number of points discarded is the greater of the number of points that have
been acquired per update (internally determined time) or 10% of the buffer
size.

As the old points are discarded, new points are acquired. The number of points
acquired is dependent on the acquisition rate (which varies depending on the
acquisition signal and increment value).

MTS MultiPurpose TestWare® Other Process Descriptions 447

Data Display Process

Plot Setup Tab (part 7 of 7)

ITEM DESCRIPTION

Keep 10 Points Per Decade—This option causes the buffer to accept acquired
data until it fills, perform a decimation that retains ten points per decade of
data, shift the data, and repeat.
Unlike the other decimation options, this method does not discard points
retained from previous passes, and is especially suited to viewing trends in
peak/valley data.
First pass: Suppose the buffer initially fills with 4096 points of data. In this
case:

• 10 Points are retained in the first decade (1-10)

• 10 Points are retained in the second decade (11-100)

• 10 Points are retained in the third decade (101-1000)

• 6 Points are retained in the forth decade (1001-10,000)

In this example, the buffer retains 36 points on the first pass and discards the
remainder. Only 6 points are retained from the forth decade because the buffer
holds only 4096 points, and the next point scheduled for retention is outside of
the points stored in the buffer. After the decimation, the retained points are
shifted to the front of the buffer to form a contiguous block.

Second and subsequent passes: In subsequent passes, the buffer iterates

between filling and decimating points until the 4 remaining points in the fourth
decade are retained. After that, the buffer begins acquiring 10 points in the fifth
decade, and so forth.

The passes continue on in the same manner until the process is stopped.
Because the interval between each desired point is logarithmic, fewer points
are retained with each successive pass.

448 Other Process Descriptions MTS MultiPurpose TestWare®

 Data Display Process

Acquisition tab This window lets you select the method with which the process acquires data to
plot.

Acquisition Tab (part 1 of 2)

ITEM DESCRIPTION
Acquisition Method:

Peak/Valley The Peak/Valley Acquisition Method acquires data on dependent signals

when the software detects a peak or valley in the specified master signal. When
selected, the application:

• Permits only channel count signals to display on the x-axis (the signal list
on the X-Axis subtab of the Plot Setup tab will display only channel
count signals).

• Displays two traces per selected y-axis signal (selected on the Y1-Axis
and Y2-Axis subtabs of the Plot Setup tab); one displays peaks, the other
displays valleys.

• Selects logarithmic scaling on the x-axis by default. You can change the
scaling in the Properties window (right-click on the plot to access the
Properties window).

Acquired Data Points

Sensor
Signal

Count

When you select the Peak/Valley Acquisition Method, you must define the
master signal and sensitivity.
Master Signal Selects a signal that determines when data is acquired.
Sensitivity Specifies how much the master signal must change to detect a peak or valley.
Setting the sensitivity too low may cause signal noise to be recognized as peaks
and valleys. Setting the sensitivity too high may cause low amplitude signals to
be missed.

MTS MultiPurpose TestWare® Other Process Descriptions 449

Data Display Process

Acquisition Tab (part 2 of 2)

ITEM DESCRIPTION
Acquisition Method:

Level Crossing The Level Crossing Acquisition Method acquires data each time the selected
master signal changes by a specific amount.

Data Points
Level Increments

Data Points

Data is acquired each time the signal moves by the

specified level increment

When you define a Level Crossing Acquisition Method, you must select the
master signal and define the level increment at which data is acquired.
Master Signal Selects a signal that determines when data is acquired.
Note When you select Time you get timed data acquisition, when you select
any of the feedback signals you get level-crossing data acquisition.

Level Increment Defines how much the signal must change before acquiring data. Initially a
default level increment is displayed, which for Time is 50 mSec, for Count is
1 segment, and for feedback signals such as Actuator Displacement is a
percentage of the signal’s full scale value. Type the desired level increment and
select appropriate units. The level increment must be greater than zero.

450 Other Process Descriptions MTS MultiPurpose TestWare®

 Data Display Process

General tab
General Tab
ITEM DESCRIPTION
Name Specifies the process name displayed on the Procedure or Group process
window.
Process Enabled Enables the process. (Clear this box to disable the process.)
Execute Process Specifies the number of times the process will be run.
Counter Type Enables a process counter.
Options are None, Transient, or Fixed. Transient counters are displayed only
when the process is active. Fixed counters are displayed throughout the test.
Counter Label Names the counter.
When you run the test, this name appears under Sequence Counters on the
MPT control panel.
Note If this box is blank, the process name is used as the counter label.

MTS MultiPurpose TestWare® Other Process Descriptions 451

Data Display Process

Additional Plot Properties

Accessing the When you right-click on the plot a menu will appear with two selections,
Properties and Print Properties and Print, as shown below.
menu

If you select Print, the Page Setup window will appear (you can also access this
window by selecting Print from the Options menu). Complete the desired
selections and click OK. The plot will be sent to the printer.

If you choose Properties, the Chart Properties window will appear.

Chart Properties Axis These windows (not shown) allow you to define various properties of the x and y
and Chart Properties axes, as well as colors and fonts for each plot. The selections in these windows
General Tabs take effect on the plot when you press OK.

Zooming Options You can zoom in on a plot’s axis by pressing the Shift key while holding down
the left mouse button, and then moving the mouse to the area of interest and
releasing the button.

You can zoom in on a part of the trace by pressing the Ctrl key while holding
down the left mouse button, and then moving the mouse to the area of interest
and releasing the button.

Return to default To return to the default plot display, press “r.” This will remove all interactive
scaling and zooming.

452 Other Process Descriptions MTS MultiPurpose TestWare®

 Data Display Process

How to Work with the Data Display Process

Data Display This process is used to view data. The data will not be saved to disk.
characteristics
• Plots can be enabled and/or disabled.

• Plot settings can be saved.

• The plot will appear when the procedure is locked. Likewise, it will
disappear when the procedure is unlocked.
Note To save the position of the plot window(s), you must save the procedure
(’position’ refers to the location of the plot on your PC monitor). If you
move the plot window from its default position and close the procedure
without saving, the plot window will appear in its default (or last saved)
position.

1. Drag the icon from the Process Palette to your group or procedure table.

2. Click the process icon on the table or in the navigation pane.

3. Click the Plots tab.

4. Select an existing plot or create a new plot.

A. Select an existing plot—Highlight the desired plot.

B. Create a new plot—Click one of the add plot buttons .

5. Type a name for the plot in the Plot Title box.

6. Click the Plot Enabled check box to enable the plot. (If the box is not
checked the plot will be disabled.)

7. Click the Acquisition tab.

8. Select an Acquisition Method.

9. If you select the Peak/Valley Acquisition Method:

A. Select a Master Signal from the pull down menu.

B. Select a Units type for the Sensitivity.

C. Type the desired value for the Sensitivity.

If you select the Level Crossing Acquisition Method:

A. Select a Master Signal from the pull down menu.

MTS MultiPurpose TestWare® Other Process Descriptions 453

Data Display Process

B. Select a Units type for the Level Increment.

C. Type the desired value for the Level Increment.

10. Click the Plot Setup tab.

11. Click the X-Axis tab.

12. Select the desired Signal.

13. Check the Show Values check box if you want the values to be displayed on
the plot.

14. Select the desired Zero Offset setting.

15. Select the desired Units.

16. Type the desired Initial Minimum and Initial Maximum values.

17. Click the Y1-Axis tab.

18. In the List Filter box, select the desired dimension category.

19. Double-click the individual signals you want to appear on the Y1-Axis.

20. For each signal included on the plot, define the Line Color and Line Style
controls as desired, and enable the Show Values control as desired.

21. Click the Y2-Axis tab.

22. In the List Filter box, select the desired dimension category.

23. Double-click the individual signals you want to appear on the Y2-Axis.

24. For each signal included on the plot, define the Line Color and Line Style
controls as desired, and enable the Show Values control as desired.

25. Click the Options tab.

26. Check the Show Grid box if you want the grid to appear on the plot.

27. Check the Show Legend box if you want the legend to appear on the plot.

28. Check the Transpose X/Y Axes if you want to exchange the position of the
axes.

29. Type the desired buffer size.

30. Select the desired Decimation Option.

31. Click the General tab.

454 Other Process Descriptions MTS MultiPurpose TestWare®

 Data Display Process

32. In the Name box, type a name for this process. (You can also name the
process in the procedure table.)

33. Select the Process Enabled check box. (If this box is cleared, the process
will not run.)

34. In the Execute Process box, type number of times you want the process to
run.

35. Optional—In the Counter Type list, click a counter type.

36. Optional—If you enabled a counter, type a Counter Label.

37. Set the desired Start and Interrupt signals for the process in the group or
procedure table.

Defining additional 1. Right-click on the plot. The Chart Properties window will appear.
chart properties
2. Click the Axis tab.

3. Select the desired Axis you wish to format.

4. Check the desired Auto formatting boxes and type corresponding values for
each.

5. Click Save Defaults if you want to save these settings as default settings.

6. Click the desired colors and font selections on the General tab.
Important The Graph Area Color and the Background Color must be
different colors. Your text will not appear if they are the same color.

MTS MultiPurpose TestWare® Other Process Descriptions 455

Data Display Process

456 Other Process Descriptions MTS MultiPurpose TestWare®

Chapter 17
Trend and Fatigue Monitoring Applications
Contents Model 793.12 Trend Monitoring Application 458
Model 793.14 Fatigue Monitoring Application 465

MTS MultiPurpose TestWare® Trend and Fatigue Monitoring Applications 457

Model 793.12 Trend Monitoring Application

Model 793.12 Trend Monitoring Application

Contents About the Trend Monitoring Application 458
Trend Monitoring Control Panel 459
Trend Monitoring Window 460
Limit Settings Window 463
Numerical Data Window 464

About the Trend Monitoring Application

The Trend Monitoring application plots trend data (received from an MPT Trend
process) in real-time. While the Trend process is running, you can use the Trend
Monitoring application to adjust limits in real-time.

Note Limit changes are transmitted back to the MPT application which does
the actual limit-checking.

When you run a procedure that contains a Trend process, the Trend Monitoring
Control Panel appears minimized on the Windows taskbar. To display the Trend
Monitoring Control Panel and the rest of the Trend Monitoring windows, click
the icon on your Windows taskbar.

458 Trend and Fatigue Monitoring Applications MTS MultiPurpose TestWare®

 Model 793.12 Trend Monitoring Application

Trend Monitoring Control Panel

With the Trend Monitoring Control Panel, you can choose which procedure for
which to display trend information. It also includes a toolbar with which you can
open trend data files and quit the Trend Monitoring application.

Trend Monitoring Control Panel

ITEM DESCRIPTION

Displays the Open Trend Data File window:

You use this window to open an existing trend data file and display its
contents. If a data file has been opened before, the display will be updated to
show the new trend data.

Quits the Trend Monitoring application.

Note If data has already been received, a message will prompt you to
confirm the Exit command.

Active Procedures Specifies a procedure to display.

MTS MultiPurpose TestWare® Trend and Fatigue Monitoring Applications 459

Model 793.12 Trend Monitoring Application

Trend Monitoring Window

The Trend Monitoring window consists of your trend plot, a channel selection
box, and a toolbar. If you are running a new procedure, the Procedure File View
displays. If you open an existing data file, the Data File View displays.

The current statistical values and the actual limit settings are displayed on the
data plot. If you are creating a new process, the system will plot only the first
channel in the list by default

Note If just one statistical value has been plotted, and you have specified
limits, the limits are also displayed on the plot. If multiple values are
plotted, the limits are not displayed.

Data File View

Increase/Decrease User-Defined Marker

X/Y Min and Max

Note A left mouse-click on the trace will display it coordinates.

460 Trend and Fatigue Monitoring Applications MTS MultiPurpose TestWare®

 Model 793.12 Trend Monitoring Application

Controls The Trend Monitoring main window controls are described in the following
table.

Trend Monitoring Window

ITEM DESCRIPTION

Displays the Numerical Display window.

Displays the Limit Settings window.

Shows or hides the channel selection information.

Active Process Selects the process or file to view. You can have multiple processes or multiple
files per window.
Channel Selection Specifies the statistical value plotted for that signal. Up to five different values
(Min, Max, Mean, RMS, Std.) can be plotted at the same time.
• Clicking the button at the head of a column selects the top six values in
that column.

• Clicking on the channel name selects all statistical values for this channel.
(Note that the scaling of the Y-axis on the plot changes to percentage of
full scale if more than one value is selected.)

• If you want to select values randomly, press the Ctrl key while clicking
on the check boxes.

MTS MultiPurpose TestWare® Trend and Fatigue Monitoring Applications 461

Model 793.12 Trend Monitoring Application

Context menu Other commands are available on the Trend Monitoring application context
menu. To access the menu, right-click the trend plot.

Trend Monitoring Context Menu

Item DESCRIPTION
Set Marker Places a graphic marker on your plot window. After you enable the Set
Marker control, click on the desired location of the desired trace to place the
Reset Marker(s) marker at that location.
Reset Zoom Returns a zoomed plot to the default view.
Edit Markers—Opens the Marker Editor window that can be used to specify
marker attributes
Legends—Opens the Legend Editor window that can be used to specify
legend attributes.
Trace Colors—Opens the Trace Colors Editor window that can be used to
specify the color for each signal trace.
Print Actual Size—Prints the window as is.
Fit to Page—Scales and prints the window on a single page.
Copy to Clipboard—Copies the window to the clipboard.

Zooming data If you want to zoom in on plot data, hold the shift key, and drag a selection box
around the area of interest. To reset the display, right-click the plot, and then click
Reset Zoom.

For more information See “Numerical Data Window” on page 464.

See “Limit Settings Window” on page 463.

462 Trend and Fatigue Monitoring Applications MTS MultiPurpose TestWare®

 Model 793.12 Trend Monitoring Application

Limit Settings Window

All limit adjustments are made within this window. For each channel, you can
select Lower Limit, Upper Limit, and Limit Action.

Example of signals displayed in the Limit Settings window.

Limit Settings Window

ITEM DESCRIPTION

Prints the current limit settings in a tabular form.

Applies the selected action to all channels, and redisplays the Trend
Monitoring window.

Active Process Selects the desired process or file.

Upper/Lower Limit For a data file: Displays the limit values.
For a procedure file: Displays editable limit values. To edit them, double-click
a value, then type the new value. Press the Enter key to accept changes.
Limit Action For a data file: Displays the action settings.
For a procedure: Displays editable action settings. To change a setting, double-
click it. A list appears with the following options:
None—Limit is disabled.
Warning—A warning message is issued and a message is written to the MPT
Message Log.
Stop—The process stops and a message is written in the MPT Message Log.
Trigger—The process triggers another process.
Status bar Displays the name, dimensions, and full scale of the selected channel.

MTS MultiPurpose TestWare® Trend and Fatigue Monitoring Applications 463

Model 793.12 Trend Monitoring Application

Numerical Data Window

This Numerical Data window shows the current or past values for all statistical
data for one pass. This view is updated with the data of a new pass only when the
last pass is displayed. If you use the pass slider to look at a previous pass, this
view will not change when new pass data is received. You can use the slider
again or click on the pass number field to display the latest pass.

Red or purple numbers in the numerical data boxes indicate that these values are
outside the defined limits. Red denotes “upper limit tripped” and purple denotes
“lower limit tripped.

Numerical Data Window

ITEM DESCRIPTION

Prints the current limit settings in a tabular form.

Pass Selects the pass for which you want to display data.
To show numerical data for a particular pass, type the desired pass number, and
then press return.
Active Process Selects the desired process or file.
Statistical Values Displays the name, full scale and dimensions of the selected channel.
Status bar Prints the current limit settings in a tabular form.

464 Trend and Fatigue Monitoring Applications MTS MultiPurpose TestWare®

 Model 793.14 Fatigue Monitoring Application

Model 793.14 Fatigue Monitoring Application

Contents About the Fatigue Monitoring Application 465
Fatigue Monitoring Control Panel 465
Fatigue Monitoring Window 467
Limit Settings Window 463
About Best Case/Worst Case 471
Numerical Data Window 464

About the Fatigue Monitoring Application

The Fatigue Monitoring application plots fatigue data (received from an MPT
Fatigue process) in real-time. While the Fatigue process is running, you can use
the Fatigue Monitoring application to adjust data limits in real-time.

When you run a procedure that contains a Fatigue process, the Fatigue
Monitoring Control Panel appears minimized on the Windows taskbar. To
display the Fatigue Monitoring Control Panel and the rest of the Fatigue
Monitoring windows, click the icon on your Windows taskbar.

Fatigue Monitoring Control Panel

With the Fatigue Monitoring Control Panel, you can choose which procedure
for which to display monitoring information. It also includes a toolbar with
which you can open fatigue data files and quit the Fatigue Monitoring
application.

Note When you run a test that includes a Fatigue process, the Fatigue
Monitoring application runs in a minimized state.

MTS MultiPurpose TestWare® Trend and Fatigue Monitoring Applications 465

Model 793.14 Fatigue Monitoring Application

Fatigue Monitoring Control Panel

ITEM DESCRIPTION

Opens the Open Fatigue Data File window.

You use this window to open an existing fatigue data file and display its
contents. If a data file has been opened before, the display will be updated to
show the new fatigue data.

Quits the Fatigue Monitoring application.

Note If data has already been received, a message will prompt you to
confirm the Exit command.

Active Procedures Specifies a procedure to display.

466 Trend and Fatigue Monitoring Applications MTS MultiPurpose TestWare®

 Model 793.14 Fatigue Monitoring Application

Fatigue Monitoring Window

The Fatigue Monitoring window consists of your fatigue plot, a channel selection
box, and a toolbar. If you are running a new procedure, the Procedure File View
displays. If you open an existing data file, the Data File View displays.

The current damage values and limit settings are displayed on the data plot. If you
are creating a new process, the system will plot only the first channel in the list
by default.

Note If just one fatigue value has been plotted, and you have specified limits,
the limits are also displayed on the plot. If multiple values are plotted, the
limits are not displayed.

Procedure File View

User-Defined Marker
Increase/Decrease
X/Y Min and Max Note A left mouse-click on the trace will display it coordinates.

MTS MultiPurpose TestWare® Trend and Fatigue Monitoring Applications 467

Model 793.14 Fatigue Monitoring Application

Controls The Fatigue Monitoring main window controls are described in the following
table.

Fatigue Monitoring Window

ITEM DESCRIPTION

Displays the Numerical Display window.

Displays the Limit Settings window.

Shows or hides the channel value information.

Active Process Selects the process or file to view. You can have multiple processes or multiple
files per window.
Lifetime Data Displays “percentage of lifetime” instead of damage number.
Channel Selection Specifies the damage value plotted for a particular signal. Up to six different
values can be plotted at the same time.
• Clicking the Pass/Acc. button at the head of a column selects the top six
values in that column.

• Clicking on the channel name selects all damage values for this channel.

• To select values randomly (for example, Channel 1 BC Pass and Channel

2 WC Acc), press the Ctrl key while clicking on the check boxes.

468 Trend and Fatigue Monitoring Applications MTS MultiPurpose TestWare®

 Model 793.14 Fatigue Monitoring Application

Context menu Other commands are available on the Fatigue Monitoring application context
menu. To access the menu, right-click the fatigue plot.

Fatigue Monitoring Context Menu

Item DESCRIPTION
Set Marker Places a graphic marker on your plot window. After you enable the Set
Marker control, click on the desired location of the desired trace to place the
Reset Marker(s) marker at that location.
Reset Zoom Returns a zoomed plot to the default view.
Edit Markers—Opens the Marker Editor window that can be used to specify
marker attributes
Legends—Opens the Legend Editor window that can be used to specify
legend attributes.
Trace Colors—Opens the Trace Colors Editor window that can be used to
specify the color for each signal trace.
Print Actual Size—Prints the window as is.
Fit to Page—Scales and prints the window on a single page.
Copy to Clipboard—Copies the window to the clipboard.

Zooming data If you want to zoom in on plot data, hold the shift key, and drag a selection box
around the area of interest. To reset the display, right-click the plot, and then click
Reset Zoom.

For more information See “Numerical Data Window” on page 464.

See “Limit Settings Window” on page 463.

MTS MultiPurpose TestWare® Trend and Fatigue Monitoring Applications 469

Model 793.14 Fatigue Monitoring Application

Limit Settings Window

All limit adjustments are made within this window. You can select a best case
(BC) and worst case (WC) for each signal as follows:

• Upper Limit (Pass)

• Lower Limit (Pass)

• Limit Action (Pass)

• Upper Limit (Accumulated)

• Limit Action (Accumulated)

Example of signals displayed in the Limit Settings window.

Limit Settings Window (part 1 of 2)

ITEM DESCRIPTION

Prints the current limit settings in a tabular form.

Applies the selected action to all channels, and redisplays the Fatigue
Monitoring window.

Active Process Specifies the current process or file.

Upper/Lower Limit For a data file: Displays the limit values.
values for channels
For a procedure file: Displays editable limit values. To edit them, double-click
a value, then type the new value. Press the Enter key to accept changes.

470 Trend and Fatigue Monitoring Applications MTS MultiPurpose TestWare®

 Model 793.14 Fatigue Monitoring Application

Limit Settings Window (part 2 of 2)

ITEM DESCRIPTION
Limit Action For a data file: Displays the action settings.
For a procedure file: Displays editable action settings. To change a setting,
double-click it. A list appears with the following options:
None—Limit is disabled.
Warning—A warning message is issued and a message is written to the MPT
Specimen Log.
Stop—The process stops and a message is written in the MPT Specimen Log.
Trigger—The process triggers another process.
Status bar Displays the name, full scale and dimensions of the selected channel.

About Best Case/Worst Case

The terms “worst case” and “best case” refer to the methods MPT uses to analyze
each histogram bin. Each histogram bin has an associated cycle count that
increments whenever a data value occurs within the bin boundaries. Therefore,
when analyzing the damage content of a histogram, the MPT analysis assumes a
maximum or minimum bin value for each cycle that is counted. The bin size
(resolution) affects the best case/worst case answers. The larger the bin size, the
larger the potential for errors in the damage calculations. In general, assuming
maximum values for a bin results in a maximum damage (worst case) scenario.
Likewise, assuming minimum values for a bin results in a minimum damage
(best case) scenario.

Worst case “Worst case” assumes that the cycles in the bin have the largest range and tensile
mean (for strain life and generic stress life damage models) and that the cycles
“hang” from the bounding hysteresis loop in a way that yields the maximum
(tensile) mean stress (for strain life damage models only).

Best case “Best case” assumes that the cycles in the bin have the smallest range and tensile
mean (for strain life and generic stress life damage models) and that the cycles
“hang” from the bounding hysteresis loop in a way that yields the minimum
(tensile) mean stress (for strain life damage models only).

MTS MultiPurpose TestWare® Trend and Fatigue Monitoring Applications 471

Model 793.14 Fatigue Monitoring Application

Numerical Data Window

The Numerical Data window displays the current or past values for all damage
data for one pass. This view is updated with the data of a new pass only when the
last pass is displayed. If you use the pass slider to look at a previous pass, this
view will not change when new pass data is received. You can use the slider
again or click on the pass number field to display the latest pass.

Red or purple numbers in the numerical data boxes indicate that these values are
outside the defined limits. Red denotes “upper limit tripped” and purple denotes
“lower limit tripped.”

Numerical Data Window

ITEM DESCRIPTION

Prints the current limit settings in a tabular form.

Pass Selects the pass for which you want to display data.
To show numerical data for a particular pass, type the desired pass number, and
then press return.
Active Process Specifies the desired process or file.
Status bar Displays the name, full scale and dimensions of the selected channel.

472 Trend and Fatigue Monitoring Applications MTS MultiPurpose TestWare®

Chapter 18
Model 793.11 Profile Editor
About the Profile About the Profile Editor 476
Editor About Profiles 478
About Working with Profiles 481
About Profile Types 483
Block-Arbitrary Profiles 483
Phase Profiles 484
About Profile Properties 485
About Profile Constants 486
How to use the Profile How to Start the Profile Editor 487
Editor About Working with the Station Configuration File 487
Using Shortcuts 488
How to Create New Profiles 488
How to Open Existing Profiles 489
How to Set Preferences 489
How to Create Block Arbitrary Profiles 490
How to Create Phase Profiles 491
How to Assign Profile Properties 492
How to Assign Profile Constants 492
How to Assign Actions 493
How to Analyze Profiles 494
Design Considerations Profile Design Considerations 495
General Profile Syntax Requirements 496
Header Data Syntax 497
Action and Counter Syntax 498
Channel Header Syntax 499
Channel Data Syntax 500

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 473

 Block-Arbitrary Profile Example 503
Graphical Preview Channel 1 504
Graphical Preview Channel 2 504
Phase Profile Example 505
Graphical Preview Channels 1 and 2 506
About Cycle and Segment Behavior 506
About Working with Dimensions 508
About Using Normalized Dimensions 510
Using Normalized Dimensions to Define Control Modes 512
How to Preview Profiles 513
About Adding Transitions 514
About Generating Transitions 514
About Working with Automatic Transitions 516
About Working with Manual Transitions 517
About Using Profile Editor 519
How to Play Out Profiles 519
About Setting Up Profiles in MPT 520
User Interface About Profile Editor Main Window 521
Menu Bar 522
Toolbar 523
File Menu 524
New Profile Settings Window 525
Channel Grid Display 525
About Wave Shapes 529
How to Define Taper Times 532
Print Preview Window 533
Print Preview Toolbar 533
Profile Summary Window 534
Channel Setup Window 536
Channel Constants Window 539

474 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Actions Window 541
Channel Menu 542
Tools Menu 542
About Graphical Preview Window 543
Options Editor – Graphical Preview Tab 543
Analyze Window 548
Window Menu 550
Help Menu 551

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 475

Profile Editor

Profile Editor
About the Profile Editor
With the Profile Editor application you can create and edit files that contain
specifications for custom and/or arbitrary waveforms. These files are called
profiles.

This chapter describes the basic concepts and key features of the MTS Profile
Editor application. It also describes how the Profile Editor application is used
with the other MTS software applications.

The Profile Editor application is equipped with a graphical previewing tool.

With this tool, you can examine the waveform that the profile specifies to
determine if it accurately represents the end results you desire.

The Profile Editor application checks the active profile for potential design
errors. If the application detects an error, it displays a message detailing the
problem. All errors must be resolved before you can save the profile.

476 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor

Note The Profile Editor’s graphical display will not display the tapered
waveforms. To view tapered wave shapes, use the Scope in the Station
Manager application.

Note how the Channel 2 plot stretches to achieve the desired phase relationships
between each row of channel data. For instance, the Phase Lag of Row 2 of
Channel 1 is 0 degrees, while the Phase Lag for the same row on Channel 2 is
180 degrees.

This means that for Row 2, the channel data of Channel 2 lags Channel 1 by
180 degrees, as noted in the figure.

The Graphical Preview

shows the 180 degree
phase shift specified in
Row 2.

If desired, you could view the Channel 1 and Channel 2 plots on separate axes
by selecting the Multiple Plot option on the Graphical Preview tab of the
Options Editor.

Sample Block-Arbitrary Profile

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 477

Profile Editor

Row 0 2 3 4 5 6

Row 1
2 3 4 5 6

This is the plot of the sample profile. (The row and segment numbers
have been added to show how they relate to the profile. The vertical
gray bar denotes where one row stops and the next row begins.)
The Graphical Preview window appears when you select Show Graph
on the Tools menu, or when you click the button on the toolbar.

For more information See “About Graphical Preview Window” on page 543.

About Profiles
A profile is an ASCII text file that defines a series of command elements in a
spreadsheet-style (or grid-style) format.

A profile grid contains a number of rows, with each row defining a single
command element. Command elements may be a single segment or series of
segments (cycles). Each segment or cycle is defined by its waveshape, end levels,
rate type (time, frequency, or rate), and count.

478 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor

A single profile can (and often does) contain the command content of an entire
procedure.

Sample Profile Grid

Profile output example This example is based on the Sample Profile Grid.

• Row 0 specifies a ramp waveform shape, 3 segments, 3 seconds per

segment, Level 1 of -10 mm, and Level 2 of 7 mm.

• Row 1 specifies a ramp waveform shape, 3 segments, 4 seconds per

segment, Level 1 of 3 mm, and Level 2 of 6 mm.

• Row 2 specifies a ramp waveform shape, 3 segments, 5 seconds per

segment, Level 1 of 4 mm, and Level 2 of -8 mm.

With the Profile Editor application you can create and edit files that contain
specifications for custom and/or arbitrary waveforms. These files are called
profiles.

This chapter describes the basic concepts and key features of the MTS Profile
Editor application. It also describes how the Profile Editor application is used
with the other MTS software applications.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 479

Profile Editor

The file is read in sequence (row by row) to produce a waveform:

Row 0 Row 1 Row 2

Seg. 1 3 Seg. 2 3 Seg. 3 3 Seg. 1 4 Seg. 2 4 Seg. 3 4 Seg. 1 5 Seg. 2 5 Seg. 3 5
sec. sec. sec. sec. sec. sec. sec. sec. sec.

Transition segment Transition segment from Transition segment from

from zero to Row 0 end level to Row 1 end level to
Row 0, Level 1 Row 1, Level 1 Row 2, Level 1

Note The first segment of each row is always a “transition” segment from the
end level in the previous row to Level 1 in the current row. At the
beginning of the procedure, the first segment is a transition from the
current level to Level 1 in Row 0.

About Creating Profiles

You create profiles by typing values into a grid, which defines custom or
arbitrary waveforms.

Certain elements of the profiles you create must match the same elements in the
station configurations (which you created with the Station Builder application)
on which you intend to play out the profiles. For instance, a profile’s control
modes, sensor ranges, and unit types must be compatible with the station
configuration, or you will not be able to run the profile on your test system.

480 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor

About Playing Out Profiles

To play out a profile, you must first import it into the Profile process of an MPT
test procedure. Then you run the test procedure with the run, stop, and hold
controls on the Station Manager’s Station Controls panel.

For more information For more information about how to run test procedures, see “About MPT Test
Procedures” on page 18.

Default Profile Locations

In MTS 793 software version 3.5x or earlier, the default location of profiles is:

C:\MTS software product name (for example, “FTGT”)\profiles

In MTS 793 software version 4.0 or later, the default location of profiles is:

C:\MTS 793\Projects\Project name (for example, “Project 1”)\Profiles

Profiles in Projects
A Project is a folder that contains or references files that are used and generated
by MTS 793 applications. When you start Profile Editor, you select a Project.
The current Project determines the location of profiles.

By default, Projects contain profiles in the Profiles subfolder. You can use the
Project Manager application to edit the Project Settings file to change the
location of profiles.

For more information about the Project Manager and Projects, see the MTS
Series 793 Control Software manual (part number 100-147-130), and the MTS
Series 793 Controller Overview manual (part number 100-162-928).

About Working with Profiles

When you start the Profile Editor application you can either create a new profile
or open an existing profile.

Each profile contains one channel grid for each channel in the profile. You create
profiles by selecting properties or typing values for each cell of a channel grid.
When the profile is played out, this information is read in sequence to produce a
waveform.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 481

Profile Editor

Profiles are saved in the ASCII format.

You can also specify how you want the profile to be viewed and stored by
selecting preferences in the Options Editor window.

Channel grids You create profiles by selecting properties or typing values for each cell in a
channel grid. When the profile is played out, this information is read in sequence
to produce a waveform.

The cells in each row of a channel grid can contain the following information:

• Timing—Frequency, Time, and for block-arbitrary profiles, Rate

• Count—Segments or Cycles

• Shape—Square, Ramp, Sine, True Sine, Square Tapered, Ramp Tapered,

Sine Tapered, or True Sine Tapered

• End levels—Level 1 and Level 2

• Phase—phase lag between channel data (phase-type profiles)

• Action—counters and user-defined actions

Profile properties You can select properties for each channel grid in the profile in the Channel
Setup window. Your selections will be reflected in the name of the channel grid,
and in the labels of the columns in the channel grid.

The properties that can be selected are:

• Name (channel name)

• Timing (Frequency, Time, and for block-arbitrary profiles only, Rate)

• Dimension

• Level Units

• Count Units (segments or cycles)

482 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor

About Profile Types

You can create two types of profiles with the Profile Editor:

• Block-Arbitrary

• Phase (for multichannel systems only)

Both types use the same basic structure. However, in addition to the properties
contained in block-arbitrary profiles, with phase profiles you can change the
phase relationship between channels.

Block-Arbitrary Profiles
A block-arbitrary profile can control multiple channels, with each channel
running independently.

A block refers to a command with two end levels and a cycle count, frequency,
and shape that defines the way the signal should fluctuate between those end
levels. An arbitrary segment refers to direct movement from one end level to
another end level.

A block-arbitrary profile can consist of a group of single segments or blocks of

repeating segments (cycles) for each channel. Each segment can have a different
shape, rate, number of repeats, and amplitude.

This is an example of a
two-channel block-
arbitrary profile plot.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 483

Profile Editor

About segments The first segment in a row begins at the current level and travels to level 1.
Subsequent segments in the row travel from one level to the next.

2 3 4
1
Row 0
Row 1
2 3
1

About cycles The first cycle in a row begins at the current level, travels to level 1, then travels
back to level 2. Subsequent cycles in the row travel from level 2 to level 1 and
back to level 2. If a row has a cycle count of 0.5, the cycle begins at the current
level and travels just to level 1.

Phase Profiles
Like a block-arbitrary profile, a phase profile can also control multiple channels,
and may consist of a group of single segments or blocks of repeating segments
(cycles) for each channel. Each segment is defined with the same components
(shape, time base, count, and amplitude) as a block-arbitrary profile.

However, unlike a block-arbitrary profile, phase profiles can specify a phase lag
in each row of the channel grid. The phase lag of each row in a channel is
referenced to the lowest phase lag defined in the profile. In other words, each row
in each channel is checked to find the lowest phase value. Then each channel
uses that value as the phase reference for playing out that row. The segment
shape, time base, and count must be the same for each channel. Each row of
channel 1 data defines these characteristics for all channels in a phase profile.

484 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor

With a phase profile, you do not specify the timing of channels independently.
Instead of specifying frequency and count for each channel, you specify them
only for the first channel. Then you specify the relationships of the other
channels to the first channel with a phase parameter.

Two-channel Phase Profile Plot

About Profile Properties

When using the Channel Setup window, you can select properties for each
channel grid in your profile. Your selections will be reflected in the name of the
channel grid, and in the labels of the columns in the channel grid.

Assign Profile Each channel in the profile needs to have properties assigned individually. The
properties properties determine how the profile will be played out.

The properties that you assign for each channel are:

• Name (channel name)

• Timing (Frequency, Time, and for Block-Arbitrary profiles only, Rate)

• Dimension

• Level Units

• Count Units (segments or cycles)

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 485

Profile Editor

Assign Profile You can set parameters of each channel grid to be constant for each row in that
constants channel.

When you assign a parameter as a constant you enter a set value for all rows of a
channel grid. Any parameter you select as a constant will be hidden from view on
the channel grid.

About Profile Constants

When using the Channel Constants window, you can assign certain parameters to
be constant for each row in the channel grid. Any parameter you select as a
constant will be hidden from view on the channel grid.

You can assign any of the following constants:

• Timing

• Count

• Shape (Square, Ramp, Sine, True Sine, Square Tapered, Ramp Tapered,
Sine Tapered, True Sine Tapered)

• Level1 (value)

• Level2 (value)

• Action

486 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

Creating Profiles
How to Start the Profile Editor
From the desktop From the desktop: Start > Programs > MTS controller product name (for
example, “MTS FlexTest GT”) > Applications > Profile Editor

From MTS applications • On the Project Manager tool bar, click the Profile Editor icon, or from the
Applications menu, click Profile Editor.

• From the Station Manager Applications menu, click Profile Editor.

• From the Station Desktop Organizer Start Applications menu, click Profile
Editor.

About Working with the Station Configuration File

Although the Profile Editor is a stand-alone application, it is important that some
elements of the profile match equivalent elements in the station configuration.

For instance, when you use Profile Editor to assign dimensions (force,
displacement, and so forth) to end levels in a profile, they should map to the
control mode/feedback dimensions in the station configuration.

When attempting to play out a profile, MultiPurpose TestWare will be unable to

recognize control modes in the station configuration unless they have the same
dimensions as equivalent control modes in the profile.

If equivalent control modes in the station configuration and profile have different
dimensions, you will not be able to map profile channels to station channels.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 487

Creating Profiles

Using Shortcuts
You can use a shortcut to automatically load a specific profile when you start the
Profile Editor application.

Shortcut command To create a shortcut, first specify the application (profedit), then the desired
line options.

To view a list of available Profile Editor command-line options, type profedit /

Help from the command line. These options are also described in the following
table.

Note If the parameter name contains spaces (for example, test 257.000), the
name must be enclosed in quotation marks (“test 257.000“).

Profile Editor Command-Line Options

DESCRIPTION OPTION EXAMPLE
Profile filename /Profile /Profile Test2.blk
Display the Profile Editor /Help
command-line
options

Command line profedit /Profile “C:\ftiim\my profiles\1 chan.blk”

example

How to Create New Profiles

Note It is good practice to save often while you are creating a profile. If
something unexpected happens it can save you a lot of rework.

1. Open the Profile Editor application. In the New Profile Settings window,
type a File Name, and click OK. The application will display an empty
channel grid.

2. On the Channel menu, select Add for as many additional channels as

desired for your profile. Each time you add a channel, the Profile Editor
application will display a new channel grid.

3. On the Edit menu, select Setup and define the Channel Setup window for
each channel grid.

488 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

4. On the Edit menu, select Constants and define the Channel Constants
window for each channel grid.

5. Type channel and row properties in each cell of each channel grid.

6. On the Tools menu, select Options Editor. Click the Graphical Preview
tab and select preferences as desired.

7. On the Tools menu, select Show Graph to display your profile.

8. On the Tools menu, select Analyze. The application will scan your profile
for potential errors and display the results.

9. Resolve any reported errors by correcting the entries in the channel grids,
and then display and analyze the profile until it is correct.

10. On the File menu, select Save Profile to save your profile.

How to Open Existing Profiles

1. Open the Profile Editor application and click OK in the New Profile
Settings window. An empty channel grid appears.

2. On the File menu, select Open Profile.

3. Use the Open Profile window to select an existing profile. The profile’s
completed channel grids will be displayed (replacing the empty channel
grid).

How to Set Preferences

1. On the Tools menu, select Options Editor.

2. On the Graphical Preview tab, set the desired preferences for viewing
profile plots.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 489

Creating Profiles

How to Create Block Arbitrary Profiles

This section contains step-by-step instructions for creating a simple two-channel
block-arbitrary profile.

1. Start the Profile Editor.

Path: Start > Programs > FlexTest (or TestStar) > Applications > Profile
Editor

The Profile Editor main window and New Profile Settings window will
appear.

2. Select the profile type and display a channel grid.

A. Type a name for the profile in the File Name box.

B. Select BlockArbitrary as the file type.

C. Type a description if you want and click OK. An empty channel grid
labeled Channel 1 will appear.

3. Add a channel.

A. On the Channel menu, click Add to add one channel to your profile.

B. The Channel 2 channel grid will appear.

4. Assign properties.

5. Assign constants.

6. Type the profile channel data.

A. Type the profile data for each channel on each channel grid. Beginning
with the first cell in the left column, type in each value.

B. Press the Tab key to move to the next cell.

Note When you type a value into a cell, it will take effect when you press the
Enter or Tab keys, click on another cell, or bring focus to another
window (such as another channel grid).

7. Preview the profile.

8. Analyze the profile.

For more information See “How to Assign Profile Properties” on page 492.

See “How to Assign Profile Constants” on page 492.

490 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

See “How to Preview Profiles” on page 513.

See “How to Analyze Profiles” on page 494.

How to Create Phase Profiles

This section contains step-by-step instructions for creating a simple two-channel
Phase-type profile (this applies only to multichannel systems). You will:

• Select channel properties and constants.

• Define channel levels by typing data into channel grids.

• View the profile plot using the Show Graph feature.

1. Start the Profile Editor application:

Path: Start > Programs > FlexTest (or TestStar) > Applications > Profile
Editor

2. Name the profile and display a channel grid.

A. Type a name for the profile in the File Name box.

B. Click Phase as the file type.

C. Type a description if you want and click OK. An empty channel grid
labeled Channel 1 will appear.
Note Phase-type profiles include a Phase Lag column in the channel grid.

3. Add a channel.

A. On the Channel menu, click Add to add one channel to your profile.

B. The Channel 2 channel grid will appear.

Note Channel 2 is slaved to Channel 1 and includes only level and phase
columns.

4. Assign properties.

5. Assign constants.

6. Type the profile channel data.

A. Type the profile data for each channel on each channel grid. Beginning
with the first cell in the left column, type in each value.

B. Press the Tab key to move to the next cell.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 491

Creating Profiles

Note When you type a value into a cell, it will take effect when you press the
Enter or Tab keys, click on another cell, or bring focus to another
window (such as another channel grid).

7. Preview the profile.

8. Analyze the profile.

For more information See , “How to Assign Profile Constants,” on page 492.

See , “How to Assign Profile Properties,” on page 492.

See, “How to Analyze Profiles,” on page 494.

See, “How to Preview Profiles,” on page 513.

How to Assign Profile Properties

1. Click the Channel 1 channel grid to bring it to focus.

2. On the Edit menu, select Setup.

3. Complete the Channel Setup window.

The properties you select here will show up in the channel grid column
headings.

4. Click OK when you are finished.

5. Repeat these steps for all additional channels.

How to Assign Profile Constants

1. Click the Channel 1 channel grid (to bring it into focus).

2. On the Edit menu, select Constants for the Channel 1 grid.

3. Select the desired properties.

4. Click OK when you are finished.

5. Repeat steps 1-3 for all remaining channels.

Note At least one of the properties needs to remain as a variable.

492 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

How to Assign Actions

Define actions 1. On the Edit menu, select Actions.

2. On the Actions window, add the actions and/or counters required for your
profile.

You can type the name of a predefined action, either user-defined or system
actions, such as those displayed in the Station Manager Event-Action Editor
Action Lists. Be sure to type the exact name of the action and that
delimiters mark each entry (for example, <Digital Output 1>). These action
entries are not case-sensitive.

You can also choose to add “generic” action markers (for example,
<Action1>) to your Actions window action list. These actions must be
mapped to either user-defined or system actions in the MPT Profile Process
(Actions tab). See the MPT section for more information about this
mapping procedure.

3. Close the Actions window.

Single row assignment Actions can be assigned to a single row or all rows of a profile’s channel grid (as
a constant).

1. On the Profile Editor Edit menu, select Constants.

2. Click the Action box to remove the check, allowing assignment of an action
to each row of the channel grid.

Select from actions or counters previously specified in the Actions window.

You can select None to leave the cell empty. Actions are triggered after the
corresponding row in the profile has played out.

Counters, displayed on the MPT control panel while the process is running,
are incremented after a corresponding row in the profile has played out.

Assigned as a constant An action (or counter) assigned as constant is triggered (or incremented) after
each row in the channel grid.

1. On the Profile Editor Edit menu, select Constants.

2. Ensure that the Action box is checked, this allows assignment of an action
as a constant for all rows of the channel grid.

3. Select the action (or counter) required as a constant.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 493

Creating Profiles

How to Analyze Profiles

1. On the Tools menu, select Analyze.

2. The Profile Editor application will scan the profile and discover flat spots in
the channel data. If any flat spots exist, a message will appear.

494 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

Design Considerations

Profile Design Considerations

There are several design considerations you need to keep in mind when creating a
profile file:

• The selected resources

The Station Manager application and the MultiPurpose TestWare

application must be opened with a configuration file that is compatible with
the profile file.

• The selected dimension

– With standard engineering dimensions, you need to ensure that one of

the profile file dimensions matches one of the control mode dimensions
available in the station configuration.

With normalized dimensions, you can select any of the control modes available
in the station configuration.

The MPT Profile Command and Profile with ALC processes support block-
arbitrary profiles and phase profiles.

You can create a profile using one of the following tools:

• A text editor

• A spreadsheet application

• The MTS Model 793.11 Profile Editor application

Block-arbitrary profiles A block-arbitrary profile defines a particular command segment (or a series of
segments) for each channel. Each segment can have a different shape, rate, repeat
count, and amplitude.

A block-arbitrary profile can define several channels of data since there is no

interaction between the data channels.

Phase profiles A phase profile also defines a particular command segment (or a series of
segments) for each channel. However, the segment shape, time base and count
must be the same for each channel.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 495

Creating Profiles

A phase profile can define several channels of data. Each row of segment data
can have Phase Lag defined for it. The Phase Lag of each channel is referenced to
the lowest Phase Lag defined in a channel.

For more information See “Block-Arbitrary Profile Example” on page 503.

See “Phase Profile Example” on page 505.

General Profile Syntax Requirements

If you create a profile using the Profile Editor application, the syntax of the
profile is managed automatically by the Profile Editor application.

If you are creating a profile with an external spreadsheet or text editor

application, you should review the following profile syntax requirements before
you start:

• Profiles should be saved with a blk extension so the default file filter in
MPT will recognize them.

• You must separate profile entries with a space or a tab (when using a text
editor).

• Blank lines between rows may be used to improve readability.

• The profile must start with the header data definition, then with channel and
command data definitions for each succeeding channel defined in the
profile. (Header data, Channel 1 data, Channel 1 command data, Channel 2
data, Channel 2 command data, and so forth.)

• Keywords are not case-sensitive.

• Do not leave a space between the keyword and the equals sign (=).
However, you can insert a space after the equals sign to improve readability.

• Use header keywords (FileType, Date, and so on) only once.

• Use channel keywords (level, frequency, and so on) only once for each
channel definition.

496 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

Header Data Syntax

The following is an example of proper header data syntax:

FileType= Block-Arbitrary

Date= Fri Aug 12 07:55:44 2000

Description= this is a sample test profile

ActionList= <DO 1 on>, <DO 1 off>, counter1, “counter 2”

Channels= 1

KEYWORD SUGGESTIONS COMMENTS

FileType= Block-Arbitrary or Phase This required entry must be first.

Date= Last modified date and time This optional entry can be in any form. It can be
omitted.

Description= User-defined description of the This optional entry can be in any form (quotation
file marks are not needed) on one line. It can be
omitted.

ActionList= See Action and Counter Syntax. This optional entry applies if you have actions or
counters associated with your profile. It can be
omitted.

Channels= Number of channels in profile This required entry must be followed by channel
and channel data definitions for each channel in
the profile.

For more information “Action and Counter Syntax” on page 498.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 497

Creating Profiles

Action and Counter Syntax

Observe the following syntax requirements when adding actions or counters to a
profile file.

• Actions and counters are defined by the keyword Action. This attribute may
be a constant value or a column of values.

• If the Action column is the last column in the file, the action value may be
left blank. If the Action column is not the last column, the user must specify
the empty string (“ ”) as a placeholder (any other string will be interpreted as
a unique counter name).

• If the string contains embedded spaces, then counter names must be

enclosed in quotes (“ ”) . If the name is one word, the quotes are not
necessary.

• Action names must be delimited by a left angle bracket (<) and a right angle
bracket (>). The Profile process will use these delimiters to distinguish
between event actions and counters. If the delimiters are missing, these
strings will be interpreted as new counters. If the delimiters are used for a
counter, the process will interpret the name as an event action. Neither of
these syntax errors will generate an error, but they may cause unexpected
results.

• The keyword ActionList= must be in the file header if any actions are
defined. It must include all event action names defined in the file; counter
names are optional. The names must be separated by a comma. This list
cannot exceed 256 characters without containing a space. MTS recommends
separating items in the list with a comma (required) and a space.

Example with counters FileType= Block-Arbitrary

and actions Date= Wed_Jul 05 15:11:32
ActionList= <DO on>, <DO off>, “Counter 1”, Counter2
Channels= 1

Channel(1)= Channel 1
Frequency= 1 Hz
Count= 1 segments
Shape= Sine
Level2= 0.0 mm

498 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

Level1 Action
mm
5.0000 <DO Off>
-5.0000 “Counter 1”
8.0000
-8.0000
2.000 Counter2
-2.000
5.0000
-5.0000
1.0000
-1.0000 <DO On>

Channel Header Syntax

Following the header data definition, you must define the first control channel.
After the channel definition, you must define the channel data for that channel.

The following is an example of proper channel data syntax:

Channel(n)= channel name

Max= maximum value and units

Min= minimum value and units

Channel Header Syntax

KEYWORD COMMENTS SUGGESTIONS
Channel(n)= Names the channel; n is the This is a required entry and must be first. The
channel number channel name is not case-sensitive.

Max= Placed in the file by the Profile This is an optional entry that specifies the
Editor and displayed on the File maximum output for the channel. It can be
Summary tab; useful for omitted.
determining an appropriate
range with which to control the
channel.

Min= See “Max=”. This is an optional entry that specifies the

minimum output for the channel. It can be
omitted.

Dimension= Placed in the file by the Profile This is an optional but recommended entry. It
Editor to determine the can be omitted.
dimension of a given unit.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 499

Creating Profiles

Channel Data Syntax

Following the channel definition, you must define the command data for that
channel.

Channel data attributes can be entered two ways—as constants or as individual

values. Constants are declared before any individual parameters are listed, and
they require the equal sign (=) to be appended to the end of its keyword. Any
keyword can be defined as a constant. The following is one example of the
command data syntax where one keyword is defined as a constant. Each row of
data defines a command element.

The following is an example of proper command data syntax:

Shape= Sine

Frequency Count Level1 Level2

Hz Cycles mm mm

10 100 5 -5

5 150 10 0

1 0.5 0 0

500 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

Channel Data Syntax

KEYWORD RANGE COMMENTS
Frequency, Time, Undetermined This entry is required. Only one of these three
or Rate* can be specified. Rate must reflect the rate of
change of the Level dimension.

Count Greater than 0 This optional entry specifies the number of

repeats. The units can be segments or cycles,
and the value must be greater than 0. If this
option is omitted, the command will run once.

Shape Ramp, Sine, Square, TrueSine, This entry is optional. When not assigned as a
SquareTapered, RampTapered, constant, each segment can have a different
SineTapered, or shape. The default is Sine.
TrueSineTapered

Level1 Undetermined This entry is required.

Level2 Undetermined This entry is required for more than one

segment.

Phase Lag† 0–360° This optional entry specifies the phase lag for
phase profiles. The default is 0.

* Rate is not supported by phase profiles.

† Phase lag is not supported by block-arbitrary profiles.

Rate type A rate type determines the time base of the waveform. Three types of rate
expressions (keywords) are supported.

• FREQUENCY (Hz, cps)

• TIME (msec, sec, minutes, and so on)

• RATE (units per time; for example, kips/sec)

A constant rate type of TIME= 2.5 sec assigns 2.5 seconds to each row of
segment data. When a constant is defined, the related column (Frequency/Rate/
Time) is not allowed. A variable rate type identifies a column of time values,
where each row can have a different time base.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 501

Creating Profiles

Count The count lets you repeat a cyclic waveform a specific number of times. The
COUNT keyword can repeat segments or cycles.

• 1 cycle = 2 segments

• A cycle count of 0.5 is the same as a single segment.

• Repeating a segment an even number of times ends at Level 2.

• Repeating a segment an odd number of times ends at Level 1.

The count can be set to a constant such as COUNT= 1 SEGMENTS. This runs
each Level 1 parameter once. It is useful for profiles that issue a series of
arbitrary end levels. In this case the values in Level 2 are not used.

Note The True Sine segment shape always starts and stops at its mean level,
and will cause a step if the previous row did not end at its mean level.

Shape The waveshape defines how to go from the current end level to the next end
level. The SHAPE keyword can define a waveshape as a constant at the
beginning of the channel (SHAPE= RAMP), or it can define a column of data to
assign a shape to each row.

Level data The level data defines the end level of the rows. The file requires a Level 1 value
for each row. If a Level 2 value is included, multiple segments are being specified
(cycles). Cycles run from the current level to Level 1, then to Level 2.

Note The first segment of each row is always a “transition” segment from the
end level in the previous row to the Level 1 value in the current row. At
the beginning of the procedure, the first segment is a transition from the
current level to Level 1 in Row 0.

Phase lag The Phase file type is the same as the Block-Arbitrary file type, except that phase
relationships between channels can be specified. When Phase is used, the
following requirements must be observed:

• The waveform rate, shape, and count must be the same for all phased
channels. They must be defined with the first channel.

• The phase of one channel is compared to another; the higher value lags the
lower value.

• Each row of data defines a waveform. The first segment of each of the
waveforms is stretched to achieve the phase lag.

For more information See “Rate type” on page 501.

See “Count” on page 502.

502 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

See “Shape” on page 502.

See “Level data” on page 502.

See “Phase lag” on page 502.

Block-Arbitrary Profile Example

Header data Filetype= Block-Arbitrary

Date=10-Dec-00

Description= Two Channel Test

Channels= 2

Channel 1 header Channel(1)= Right Front

Frequency= 1 Hz

Shape= TrueSine
Channel 1 data
Level1 Level2 Count

in in segments

5 -5 10

10 -10 20

Channel 2 header Channel(2)= Left Front

Frequency= 2 Hz

Shape= Ramp

Channel 2 data
Level1 Level2 Count

lbf lbf segments

5000 -5000 15

10000 -10000 20

2000 -200 20

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 503

Creating Profiles

Graphical Preview Channel 1

Graphical Preview Channel 2

504 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

Phase Profile Example

Header data FileType= Phase

Date= 10-Dec-00

Channels= 2

Channel 1 header Channel(1)= Left Front

Frequency= 1 Hz

Shape= Sine

PhaseLag= 0 deg

Channel 1 data
Count Level1 Level2

segments mm mm

4 5 -5

4 8 -8

4 5 -5

4 2 -2

Channel 2 header Channel(2)= Right Front

Channel 2 data
Level1 Level2 PhaseLag

mm mm deg

2 -2 0

5 -5 90

2 -2 180

8 -8 90

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 505

Creating Profiles

Graphical Preview Channels 1 and 2

About Cycle and Segment Behavior

Cycle behavior The first cycle in a row begins at the current level, travels to level 1, then travels
to level 2. Subsequent cycles in the row travel from level 2 to level 1 and back to
level 2. If a row has a cycle count of 0.5, the cycle begins at the current level and
travels just to level 1.

Row 0

1 2

0.5 Row 1

506 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

Segment behavior The first segment in a row begins at the current level and travels to Level 1.
Subsequent segments in the row travel from one level to the next.

Row 0 2 3 4
1

2 3
1
Row 1

Segment behavior with The first segment assigned to each row is always a “transition” segment from the
Segment Count of 1 end level in the previous row to the Level 1 value in the current row. Thus, if you
specify a Count of 1 segment, the Level 2 values will be ignored.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 507

Creating Profiles

The illustration shows that since the first segment in each row is a transition from
one row to the next with a count of one segment, Level 2 values are ignored.
Because only one segment has been assigned to each row, that segment is used to
transition between rows.

For more information See “Level data” on page 502.

For a more detailed discussion of segment behavior, see page “Profile output
example” on page 479.

About Working with Dimensions

When you use the Profile Editor application to assign dimensions (force,
displacement, and so forth) to the end levels in a profile, you should be aware
that they must map to the dimensions of the control modes included in the station
configuration on which you wish to play out the profile.

508 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

Because of this, it is good practice to be aware of all of the instances in which

dimension selections affect your ability to play out profiles, such as:

• You use the Profile Editor application to create command files (profiles) by
typing the end-level values you desire the actuator to achieve during the
course of the profile. To make end-level values meaningful, you must
specify dimension and unit types (for example, displacement and
centimeters).

• You use the MPT application to play out profiles you create with the Profile
Editor application. When you open the MPT application against a station
configuration, it inherits the resources of the station, which include the
control mode dimensions selected for the control modes in the station, as
defined with the Station Builder application.

• You use the MPT Profile Command process to import profiles, and to map
the logical channels in your profile (referred to as profile channels) to the
physical channels in your station configuration.
Note The MPT application does not require the names of profile channels to
be the same as the names of station channels. You can arbitrarily map
any profile channel to any station channel. You can also map one profile
channel to multiple station channels.

• You also use the Profile Command process to select the control mode of a
profile channel. For this to work (if the dimension used to define the end
levels of the profile is a standard engineering dimension, such as force or
length), the dimension must match one of the control mode dimensions
available to the current station configuration.

Example Suppose you use the Station Builder application to create a station configuration
with one channel that uses the force dimension for a force control mode, and the
length dimension for a displacement control mode.

In addition, you use the Profile Editor application to create a profile in which you
select the length dimension to define end levels for a channel you named
Channel 1.

To play out the profile file you created, open the Station Manager application and
select a configuration file containing the appropriate resources for your test.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 509

Creating Profiles

Next, select the Multipurpose TestWare application, then open the MPT
Procedure Editor (it will appear with a blank procedure table displayed). You can
create a new test procedure or open an existing procedure. The procedure must
contain the Profile Command process. Once the procedure is loaded, you then
select the profile file you created. This is done by double clicking the Profile
Command processes icon on the procedure table. The Profile Command
Parameters window will appear.

On the Command tab, click the Profile Path/File button and select the desired
profile file. An error message may appear to tell you the channel has not been
mapped. Click OK, and then click the Mapping tab.

On the Profile Channel pull down menu, select the desired channel and
complete the remaining fields. Complete the remaining tabs on the Profile
Command Parameters window. Finally, using the run button on the station
controls panel, run the profile.

About Using Normalized Dimensions

If you create a profile using a normalized dimension, such as ratio, percentage,
unitless, or volts, you can select any of the control modes available to the station
configuration when selecting the control mode for the profile channel.

When you do this, you define the full-scale value of the normalized dimension by
selecting one of the control modes and its associated engineering dimension
available in the Control Mode list on the Mapping tab, along with a unit type
and a Level Multiplier value. MPT converts all end level values in the profile to
command levels accordingly.

Example Suppose you create a station configuration that uses the force dimension for a
force control mode, and the length dimension for a displacement control mode. In
addition, suppose you create a profile in which you select the volts dimension to
define end levels.

Next, you start MPT against the station configuration, and with the Profile
process, on the Command tab, you select the profile you have created. On the
Mapping tab, you select a Profile Channel. In this scenario, both displacement
and force will be available in the Control Mode list.

Suppose you select displacement, and type a value of 5 cm in the Level

Multiplier box. This will cause all of the end level values in the profile to be
converted to displacement values. For volts, the full-scale value equals 10 volts,
which MPT will play out as 5 cm. So in this case, if the first end level values in
the profile are 2 volts and 9 volts, they will be played out as 1 cm and 4.5 cm.

510 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

Using the same profile, suppose you change the Control Mode selection to
force, and type a Level Multiplier value of 100 N. This will cause all of the end
levels in the profile to be converted to force values. In this case, MPT will play
out 10 volts as 100 N. So if the first end level values in the profile are 2 volts and
9 volts, they will be played out as 20 N and 90 N.

Full-scale values of
normalized dimensions DIMENSION FULL-SCALE VALUE

Ratio 1:1

Percentage 100%

Unitless 1.0

Volts 10V

Using normalized You can use any of these normalized dimensions to define a control mode in a
dimensions to define station configuration. If you do this, and then attempt to play out a profile that
control modes also uses a normalized dimension, MPT will treat it as a standard dimension
when you define a Profile process.

Example Suppose you create a station configuration that uses volts as a dimension for a
volt control mode, which is associated with a conditioner that is cabled to a
displacement sensor with a full-scale displacement of ±200 cm.

Next, you create a profile in which you select the volts dimension to define end
levels.

Then you start MPT against the station configuration, and with the Profile
process, on the Command tab, you select the profile you have created.

On the Mapping tab, you select a Profile Channel, and note that volts is
available in the Control Mode list, and that the Level Multiplier box displays
100%.

In this scenario, if the first end level values in the profile are 1 V and 9 V, they
will be played out as 20 cm and 180 cm. If you change the Level Multiplier
value to 50%, MPT would play out these values as 10 cm and 90 cm.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 511

Creating Profiles

Using Normalized Dimensions to Define Control Modes

CAUTION

In the Level Units list, selecting the scientific notation can affect test
integrity.

Selecting the scientific notation display feature can result in the loss of
original level values.

The Profile Editor can display only five significant digits to the left of the decimal
point and only four significant digits to the right of the decimal point for level
values. If your selection moves the original level value beyond four digits, the
original value will be lost.

Select the unity If you click unity in the Level Units list, the decimal position of each level value
dimension (Level1, Level2) shifts so that a value displayed as 100% changes to 1.0. This
affects only the display, not the subsequent command value.

Select the unitless If you click Unitless in the Dimension list, the Level Units list displays (none)
dimension by default, which means 1 equals the full-scale value, as determined by the MPT
Level Multiplier value. For example, if profile Level1 equals 2 and the MPT
Level Multiplier equals 4 cm, then the command for Level1 equals 8 cm.

How to select scientific In addition to the (none) selection, the Level Units list offers four scientific
notation notation display selections for Unitless Dimensions:

• e-03

• e-06

• e+03

• e+06

These selections do not affect the command levels at which the MPT application
plays out the profile—they simply alter the display of the level values by shifting
their decimal points. The notation value determines how much the decimal
values shift.

For example, suppose profile Level1 equals 10000 with a Level Units selection
of (none), and that the MPT Level Multiplier value equals 3 mm. In this case, the
command value of Level1 equals 30000 mm. If you change the Level Units
selections to e+03, the Level1 value will be displayed as 30, but will still have a
command value of 30000 mm.

512 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

How to Preview Profiles

On the Tools menu, select Show Graph. This displays the plot of your profile.

Note If a profile has an extremely high number of channels, rows of data, or counts, the
system may take a few minutes longer to plot and display the graph.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 513

Creating Profiles

Transitions

About Adding Transitions

The first segment (or the first half of the first cycle) in a row travels from the
current level to level 1. It has special significance because it is the portion of the
waveform that makes the transition between the rows of the channel grid.

It is useful to understand how the Profile Editor application displays transitions,

and how to add segments to modify the behavior of transitions.

1 2
Row 0

Row 1
0.5

About Generating Transitions

Note The following information applies only to Sine, Ramp, and Square wave
shapes. True Sine and tapered wave shapes always start and stop from
their mean level.

It is useful to understand how MPT generates transitions between rows, and how
to add segments to modify the transitions. The first segment (or the first half of
the first cycle) in a row travels from the current level to the Level 1 value. It has
special significance because it is the portion of the waveform that makes the
transition between the rows of the profile.

514 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

This MTS Profile Editor example shows how MPT automatically generates the
transition segments between the rows of the sample profile (Row 0, Segment 1
and Row 1, Segment 1).

2 3 4 5 6

1
Row 0

2 3 4 5 6

1
Row 1

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 515

Creating Profiles

About Working with Automatic Transitions

The following example shows how the Profile Editor application automatically
displays the transition segments in the sample profile (row 0, segment 1 and row
1, segment 1).

2 3 4 5 6

1
Row 0

2 3 4 5 6

1 Row 1

516 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Creating Profiles

About Working with Manual Transitions

Sometimes you may want to change the characteristics of row transitions without
affecting the rest of the profile. To do this, you must manually add transition
segments to replace automatically generated transition segments.

This profile is similar to the automatic transition profile, but two rows have been
added to create two “editable” transition segments. To keep the number of
segments the same, the rows that previously specified six segments (previously
rows 0 and 1, now rows 1 and 3) now specify five segments. Also, each row’s
level 1 and level 2 values have been reversed.

1 2 3 4 5
R0 Row 1
1

1 2 3 4 5
1
R2 Row 3

R = Row

The plot appears identical to the automatic transition plot, but now the transition
segments can be edited.

The following profile is similar to the previous profile, but the frequency values
of the added transition segments have been changed.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 517

Creating Profiles

The plot shows the new frequencies of the added transition segments.

1 2 3 4 5

Row 0 Row
1

1 2 3 4 5
1 Row 2 Row 3

518 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 How to Play Out Profiles

How to Play Out Profiles

About Using Profile Editor
You are not required to open any other MTS control software applications
(System Loader, Station Manager, or MultiPurpose TestWare) to use the Profile
Editor application to create and view profiles. You can, however, use the Station
Manager and MultiPurpose TestWare applications to play out profiles created in
the Profile Editor application.

You must have prior knowledge of what profile files are and how to create
profiles.

The Profile Editor application can run on a stand-alone PC to create the

necessary profile files or in conjunction with the Station Manager and
MultiPurpose TestWare applications.

How to Play Out Profiles

1. After you have created a profile, use the Station Manager application to
open the station configuration you wish to run your profile against.

2. Open the MPT application (with the Station Manager application running in
the background) and create a test procedure file that contains a Profile
Command process. Think of the Profile Command process as a container
that enables the profile to interact with the processes in the test procedure.

3. Import the profile file (typically with a blk extension) into the Profile
Command process, map the profile channels to the station channels. If
desired, apply a level offset to shift the end-level command and level
multiplier to scale the end-level commands.

4. Add other processes to the test procedure, such as data acquisition processes
(though you can create a test procedure that contains only the Profile
Command process).

5. Run the test procedure with the MPT application, which will apply the
values in the profile to your test system.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 519

How to Play Out Profiles

About Setting Up Profiles in MPT

MPT Profile Command The Profile Command process is an MPT command process that controls
process actuator movement. The Profile Command process generates commands based
on the contents of an imported file, such as profiles created by the Profile Editor
application (though you can create profiles with other applications, such as a text
editor or a spreadsheet application).

When you open the MPT application, a blank procedure table will appear when
you select the Procedure Editor. You then drag and drop the process you wish to
include for the test. You can start multiple processes nearly simultaneously by
selecting the same Start signal for each of the processes.

The Profile Command process icon is located on the MPT Process Types palette
in the Command section. You drag and drop a copy of the icon onto the test
procedure table, and it will become part of that test procedure. When you double-
click the Profile Command process icon on the procedure table, the Profile
Command Parameters window will open. You then import the desired profile into
the test procedure.

Once all the parameters have been selected for the procedure, save the file, and
then run the procedure using Station Control panel. For more information about
the MPT application and the Profile Command process see the MPT section of
this manual.

520 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

Profile Editor Controls and Displays

About Profile Editor Main Window
When you open the Profile Editor application in the New Profile Settings
Window will appear, with a blank channel grid in the background.

Menu Bar

Toolbar

Channel Grid

Example of a Phase
Channel Grid.

For more information For a complete description of the Profile Editors windows and controls, see
“New Profile Settings Window” on page 525

About the Menu Bar—see page 522

About the Toolbar—see page 523

About the Channel Grid—see page 525

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 521

Profile Editor Controls and Displays

Menu Bar

793 Application
Cascade Software
New Profile
Open Profile Tile Additional
Setup Arrange Icons Documentation
Save Profile
Save Profile As Constants Toolbar About
Print Actions Status Bar
Print Preview Cut
Print Graph Copy Show Graph
Printer Setup Paste Options Editor
Summary Insert Rows Analyze
Exit Delete Rows
Add
Remove
Show

The Menu Bar has commands for managing the Station Manager application.
The toolbar has some of the more frequently used commands.

For more information About the File menu, see “File Menu” on page 524.

About the Edit menu, see “Edit Menu” on page 535.

About the Channel menu, see “Channel Menu” on page 542.

About the Tools menu, see “Tools Menu” on page 542.

About the Window menu, see “Window Menu” on page 550.

About the Help menu, see “Help Menu” on page 551.

522 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

Toolbar

View Print Profile

Save Profile Options Editor
New Profile Show Graph
Open Profile Help

The toolbar buttons provide quick access to common commands and windows.

Profile Editor Window Toolbar

ITEM DESCRIPTION
Open Profile Displays the Open Profile window.
Note You can select the default directory in which the Profile Editor
looks for profiles with the Project Manager application. See the
MTS 793 Control Software manual (PN 100-147-130).

New Profile Creates a new profile.

Save Profile Saves the current profile.
Print Preview Displays the Print Preview window.
Print Preview Prints the current profile.
Options Editor Displays the Options Editor window.
Show Graph Displays a graphical view of the current profile.
Help Displays on-line help.

For more information See “Options Editor – Graphical Preview Tab” on page 543.
See “How to Preview Profiles” on page 513 for more information.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 523

Profile Editor Controls and Displays

File Menu

File Menu
ITEM DESCRIPTION
New Profile Displays the New Profiles window.
Open Profile Displays the Open Profiles window, which allows you to open existing
profiles.
Save Profile Saves the current profile file. If you are saving for the first time, the Save
Profile As window appears, which you use to name your profile file and set its
path.
Save Profile As Displays the Save Profile As window.
Print Prints a hard copy of the current profile.
Print Preview Displays the Print Preview window.
Print Graph Prints a hard copy of the current profile’s graphical preview.
Printer Setup Displays the Print Setup window.
Note This window varies with the print driver you are using.

Summary Displays the Profile Summary window.

Exit Quits the Profile Editor application.

524 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

New Profile Settings Window

Path File > New Profile...

Use the New Profile Settings window to name the file and specify a profile type.
The information in this window can be viewed in the Profile Summary window.

New Profile Settings Window

ITEM DESCRIPTION
File Name Names the profile file.
File Type Specifies if the profile is a block-arbitrary or a phase type. A phase profile is
similar to a block-arbitrary profile, except that with a phase profile you can
assign a phase lag between rows of channel data.
Description Shows any description that has been typed.

Channel Grid Display

Access File > New Profile...> OK

Use the channel grid to type channel values and select properties. You can edit,
scroll, cut, and paste cells, and insert and delete rows. The profile type, either
block-arbitrary or phase, determines the file format and row properties.

You can also select actions and counters previously specified in the Actions
window.

If you define a property as a constant, its associated column will not appear on
the table. You define constants in the Channel Constants window.

You can change the units of each column in the Channel Setup window.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 525

Profile Editor Controls and Displays

Note If you type values that will result in flat spots or discontinuities in the
profile, you will be warned about it when you select Analyze on the
Tools menu.

Channel Grid (part 1 of 3)

ITEM DESCRIPTION
Frequency/Time/Rate Specifies the amount of time that will elapse between each segment or cycle.
This may be specified as frequency (Hz), time (seconds), or rate (units/sec).
Rate is not available for phase profiles.
Count Specifies the number of cycles or segments run in the row.
Shape Specifies the way in which the actuator makes transitions between end levels.
Square—Creates square waves that travel between end levels L1 and L2.
Ramp—Creates triangle waves that travel between end levels L1 and L2.
Sine—Creates sine waves that travel between end levels L1 and L2.
True Sine—Creates sine waves that travel between the mean of end levels L1
and L2.
Square Tapered—Creates square waves that taper up from 0% to 100%
amplitude at the beginning, travel between end levels L1 and L2, and taper
down from 100%-0% at the end.
Ramp Tapered—Creates triangle waves that taper up from 0-100% amplitude
at the beginning, travel between end levels L1 and L2, and taper down from
100%-0% at the end.
Sine Tapered—Creates sine waves that taper up from 0%-100% amplitude at
the beginning, travel between end levels L1and L2, and taper down from
100%-0% at the end.
True Sine Tapered—Creates sine waves that, starting from the mean of the
amplitude, taper up from 0%-100% amplitude at the beginning, travel between
end levels L1and L2, and taper down from 100%-0% at the end, returning to
mean.

526 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

Channel Grid (part 2 of 3)

ITEM DESCRIPTION
Level1 (L1) For the first segment in a row, level 1 specifies the first target of the actuator.
Subsequent segments travel from one level to the next.
Level2 (L2)
Rows with even segment counts always end at level 2.
Rows with odd segment counts always end at level 1.
For the first cycle in a row, level 1 specifies the midpoint of the cycle, and the
actuator continues to level 2 to complete the cycle. Subsequent (whole) cycles
travel from level 2 to level 1 and back to level 2. (True Sine waveforms
continue on to the mean level.)
If a row has a cycle count of 0.5, the cycle begins at the current level and
travels to level 1. Rows with whole cycle counts always end at level 2. Rows
with half cycle counts (0.5, 3.5, and so forth) always end at level 1.
Action (Optional) Select from actions or counters previously specified in the Actions window.

Actions are triggered after the corresponding row in the profile has played out.
Counters, displayed on the MPT control panel while the process is running, are
incremented after a corresponding row in the profile has played out.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 527

Profile Editor Controls and Displays

Channel Grid (part 3 of 3)

ITEM DESCRIPTION
PhaseLag Determines the phase of the slave channel to the master channel in degrees.
This value is relative to the value entered for the master channel. For instance,
(Phase profiles only; if the master channel has a phase value of 10 degrees and the slave channel has
applies only to a phase value of 45 degrees, the phase between the two channels is 35 degrees.
multichannel systems)

Example:
In the plot below, the Channel 2 waveform is slaved to the Channel 1 waveform, and varies
in phase according to the values in the Channel 2 profile.

Ch
Ch 2

For more information See “Edit Menu” on page 535.

See “Analyze Window” on page 548.

528 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

See “How to Define Taper Times” on page 532.

See “How to Assign Actions” on page 493.

About Wave Shapes

The Profile Editor application supports various program wave shapes. Wave
shapes dictate the way the actuator makes transitions between end levels. The
waveforms created by the shape selections are as follows. Each example uses the
following parameters: Frequency (Hz) 1; Count (segments) 6; Level 1 (mm) 2;
Level 2 (mm) 4.

Square—Creates square waves that travel between end levels L1 and L2.

L2 4.0000

L1 2.0000

0.0000
0.3000 0.9000 1.5000 2.1000 2.7000 3.3000
Time (sec)

Ramp—Creates triangle waves that travel between end levels L1 and L2.

L2 4.0000

L1 2.0000

0.0000
0.3000 0.9000 1.5000 2.1000 2.7000 3.3000
Time (sec)

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 529

Profile Editor Controls and Displays

Sine—Creates sine waves that travel between end levels L1 and L2.

L2 4.0000

L1 2.0000

0.0000 0.3000 0.9000 1.5000 2.1000 2.7000 3.3000

Time (sec)

True Sine—Creates sine waves that travel between the mean of the end levels L1
and L2.

L1 4.0000

L2 2.0000

0.0000 0.3000 0.9000 1.5000 2.1000 2.7000 3.3000

Time (sec)

Square Tapered—Beginning at its mean, the waveform tapers from 0% to 100%

amplitude at the beginning of its execution, and from 100% to 0% at the ending
of its execution.

L1 4.0000

2.0000

L2 0.0000
2.0000 4.0000
Time (sec)

530 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

Ramp Tapered—Creates triangle waves that travel at 100% amplitude between

end levels (L1 and L2).Beginning at its mean, the waveform tapers from 0% to
100% amplitude at the beginning of its execution, and from 100% to 0% at the
ending of its execution.

L1 4.0000

2.0000

L2 0.0000
2.0000 4.0000
Time (sec)

Sine Tapered—Creates sine waves that travel at 100% amplitude between end
levels (L1 and L2). Beginning at its mean, the waveform tapers from 0% to 100%
amplitude at the beginning of its execution, and from 100% to 0% at the ending
of its execution.

L1 4.0000

2.0000

L2 0.0000
2.0000 4.0000
Time (sec)

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 531

Profile Editor Controls and Displays

True Sine Tapered—Creates sine waves that travel at 100% amplitude between
the mean of the end levels (L1 and L2). Beginning at its mean, the waveform
tapers from 0% to 100% amplitude at the beginning of its execution, and from
100% to 0% at the ending of its execution.

L1 4.0000

2.0000

L2 0.0000 2.0000 4.0000

Time (sec)

For more information See “How to Define Taper Times” on page 532.

How to Define Taper Times

The beginning and ending taper times of tapered wave shapes are specified on the
Command Options tab of Station Manager’s Channel Options window (Tools >
Channel Options > Command Options). Begin formats the leading edge and End
formats the trailing edge of all tapered waveforms in the profile.

4
3
1
2
2 1

532 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

Print Preview Window

Access Toolbar > Print Preview Icon

This window displays an on-screen preview of the profile printout. A toolbar

facilitates access and display of profile changes.

Asterisks (*) identify items that have been changed since the profile was opened.
In addition, you can highlight these changes by selecting Enable Change
Highlighting on the Print Preview toolbar.

Print Preview Toolbar

Enable/Disable Change Highlighting

Refresh Print
Previous Change
Next Change

Print Preview Toolbar

ITEM DESCRIPTION
Next Change Goes to the next change on the Print Preview window.
Previous Change Goes to the previous change on the Print Preview window.
Refresh Allows you to see current profile changes without closing and reopening the
Print Preview window. The current change(s) are highlighted.
Enable/Disable Allows you to enable or disable highlighting of profile changes.
Change Highlighting

Print Prints the profile.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 533

Profile Editor Controls and Displays

Profile Summary Window

Access File > Summary...

Use the Profile Summary window to view information about the current profile,
and to edit the profile description. The information in this window is a summary
of the information entered in the New Profile Settings window.

Profile Summary Window

ITEM DESCRIPTION
File Name Shows the name of the profile.
Last Modified Displays the last date the profile was changed.
File Type Specifies the type of profile assigned to the profile (either phase or block-
arbitrary).
Description Shows any description that has been entered.
Channels Lists the channel names associated with the profile.

534 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

Edit Menu
With the Edit menu you can define the characteristics of each channel, which
includes defining constants and the units for each channel property; and adding/
deleting actions or counters. You can also cut, copy, paste, and delete cells or
rows of cells in the channel grid. In addition, you can insert one new row of cells
at a time.

Edit Menu
ITEM DESCRIPTION
Setup Displays the Channel Setup window.
Constants Displays the Channel Constants window.
Action Displays the Action window.
Cut Removes the information in the selected cells or rows (either single or multiple
rows) and stores it in memory.
Copy Stores the information in the selected cells or rows (either single or multiple
rows) in memory.
Paste Writes information stored in memory to the selected cells or rows (either single
or multiple rows).
Insert Rows Creates a new row above the selected row.
Delete Rows Deletes the selected row or rows from the channel grid.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 535

Profile Editor Controls and Displays

Channel Setup Window

Access Edit > Setup...

Use the Channel Setup window to name the channel, specify the timing type and
dimension of each channel, and assign units to each profile property.

Note The default set of units is selected on the Unit Selection tab of the
Station Options in the Station Manager application, or with the Project
Manager application.

Channel Setup Window (part 1 of 4)

ITEM DESCRIPTION
Name Names the channel. Type a name in the box (maximum 30 characters).
Timing Specifies how the timing property is expressed. You can select one of the following:
• Frequency (Hz)

• Time (sec)

• Rate (level units/sec) (block-arbitrary profiles only)

Dimension Displays the dimension for the end levels, such as:
• Force

• Length

• Temperature

• Volume

The dimension defines the control mode in which the level commands will be
performed. For instance, if you select Force for the Dimension, then the level
commands (level 1, level 2) will be played out in force control. The Dimension list
includes four normalized dimensions:
• Percent

• Unitless

• Volts

• Ratio
A normalized dimension is not associated with a specific control mode and is not
assigned engineering units; although it does have a unit. When you select normalized
dimensions you define the dimension and units for the level commands when you
define the profile parameters in the MPT application.

536 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

Channel Setup Window (part 2 of 4)

ITEM DESCRIPTION
Level Units Displays the unit of measurement for the selected dimension, such as:
• in

• lbf

• kN

• deg_C

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 537

Profile Editor Controls and Displays

Channel Setup Window (part 3 of 4)

ITEM DESCRIPTION
Count Units Assigns Cycles or Segments as the cyclic units. One cycle equals two segments.

Cycles The first cycle in a row begins at the current level, travels to level 1, then travels back
to level 2. Subsequent whole cycles in the row travel from level 2 to level 1 and back
to level 2. If a row has a cycle count of 0.5, the cycle begins at the current level and
travels to level 1.
• Rows with whole cycle counts always end at level 2.

• Rows with half cycle counts (0.5, 3.5, and so forth) always end at level 1.

Row 0
1 2

Cycle Example
0.5 Row 1

Segments The first segment in a row begins at the current level and travels to Level 1.
Subsequent segments in the row travel from one level to the next.
• Rows with even segment counts always end at level 2.

• Rows with odd segment counts always end at level 1.

538 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

Channel Setup Window (part 4 of 4)

ITEM DESCRIPTION

Row 0 2 3 4
1

2 3
Segment Example 1
Row 1

For more information For more information, see “Design Considerations” on page 495.

For more information see, “About Using Normalized Dimensions” on page 510.

Channel Constants Window

Access Edit > Constants...

Use the Channel Constants window to define parameters as constants. When you
select a parameter as a constant, you can assign a characteristic for that parameter
that will be constant for all the rows in the channel. When you designate a
constant, its associated column is removed from the channel grid. When you do
not select a parameter as a constant, you will have to define it in each row on the
channel grid.

• In most cases you should complete the Channel Setup window, to name the
channel and assign units to each profile property, before you complete the
Channel Constants window.

• Leave at least one property as a variable. The application will not permit
you to assign all properties as constants.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 539

Profile Editor Controls and Displays

Channel Constants Window (part 1 of 2)

ITEM DESCRIPTION
Timing Defines a constant time base for the execution of each end level. This may be a
rate, frequency, or a time, depending on the selection in the Channel Setup
window.
Count Specifies how many times levels 1 and 2 are repeated before moving on to the
next profile entry.
Shape Assigns an element shape for the entire profile. The choices are:
Square—Creates square waves that travel between end levels L1 and L2.
Ramp—Creates triangle waves that travel between end levels L1 and L2.
Sine—Creates sine waves that travel between end levels L1 and L2.
True Sine—Creates sine waves that travel between the mean of end levels L1
and L2.
Square Tapered—Creates square waves that taper up from 0% to 100%
amplitude at the beginning, travel between end levels L1 and L2, and taper
down from 100%-0% at the end.
Ramp Tapered—Creates triangle waves that taper up from 0-100% amplitude
at the beginning, travel between end levels L1 and L2, and taper down from
100%-0% at the end.
Sine Tapered—Creates sine waves that taper up from 0%-100% amplitude at
the beginning, travel between end levels L1and L2, and taper down from
100%-0% at the end.
True Sine Tapered—Creates sine waves that, starting from the mean of the
amplitude, taper up from 0%-100% amplitude at the beginning, travel between
end levels L1and L2, and taper down from 100%-0% at the end, returning to
mean.
Note The Profile Editor’s graphical display will not display the tapered wave
shapes. To view tapered wave shapes, use the Scope in the Station
Manager application.

Level1 Defines level 1 to be a constant value.

Level2 Defines level 2 to be a constant value.

540 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

Channel Constants Window (part 2 of 2)

ITEM DESCRIPTION
Action Assigns an action or counter as a constant for all rows of a channel grid.
PhaseLag Assigns the channel to a constant phase lag. This is available only if Phase is
selected in the New Profile Settings window.

For more information See “Channel Setup Window” on page 536.

See “How to Define Taper Times” on page 532 for more information.
See “How to Assign Actions” on page 493

Actions Window
Access Edit > Actions...

Use the Actions window to add, delete, or name an action or counter.

The action(s) and counter(s) selected here can be assigned as constants for all
rows on a channel grid or can be assigned to each row on a channel grid.

Actions Window
ITEM DESCRIPTION
Action Displays and allows you to rename the currently selected action or counter.
If you type the name of a predefined action (as defined with the Station
Manager Event-Action Editor), you must be sure to type the exact name of the
action. If you fail to do this, the action must be mapped to either user-defined
or system actions in the MPT Profile Process (Actions tab).
Note You must use delimiters (for example, <ramp1>) when naming
actions.

Add Add an action or counter to the displayed list.

Delete Delete an action or counter from the displayed list.
Type Selecting Action lets you add or delete actions on the displayed list.
Selecting Counter lets you add or delete counters on the displayed list.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 541

Profile Editor Controls and Displays

Channel Menu
With the Channel menu you can add and remove channels from the profile. You
can also select which channel will “have focus.”

Channel Menu
ITEM DESCRIPTION
Add Adds a channel to the profile.
Remove Deletes a channel from the profile.
Note The master channel of a phase file cannot be removed.

Show Brings focus to one of the channel windows (making it the “active” window).

Tools Menu
Use the Tools menu commands to:

• Display a Graphical Preview for the x-y plot of the current profile.

• Choose preferences for viewing profile plots and selecting directories.

• Analyze the current profile for possible design errors.

Tools Menu
ITEM DESCRIPTION
Show Graph Displays the Graphical Preview window.
Options Editor Displays the Options Editor window.
Analyze Checks the profile for potential design errors. If the application detects an
error, it displays a message detailing problems, that you should be aware of
before you save the profile. All the errors must be resolved before you can save
the profile.

For more information For more information see “Analyze Window” on page 548.

542 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

About Graphical Preview Window

Access Tools > Show Graph

The Graphical Preview window displays an x-y plot of the current profile. You
can examine the waveform defined by your profile before you save it or run a test
with it.

Note When using the Graphical Preview window be aware that the display will
not automatically be updated when you make changes to the profile.
Click the Graphical Preview button to update the graphic with the
changes made to the profile.

Options Editor – Graphical Preview Tab

Access Tools > Options Editor > Graphical Preview

Use the Graphical Preview tab to customize the plots displayed in the Graphical
Preview window.

For instance, if your profile has multiple channels, you can graph each channel
separately. If your profile has the same units, you can overlay them on a single
plot (you can display up to two unit types on the same graph).

Graphical Preview Tab Window (part 1 of 5)

ITEM DESCRIPTION
Available Channels Lists the channels that may be selected for plotting.
Channels to Plot Lists the channels that will be plotted in the Graphical Preview window.
Note To display the plot, select Show Graph on the Tools menu.

Channel Display Determines the number of plots generated by channel data.

Single Plot Displays all channel waveforms generated by a multiple channel profile on the
same plot.
Multiple Plots Displays each channel waveform generated by a multiple channel profile on a
separate plot.
Note When you select the Multiple Plots option you will have to scroll down
the Graphical Preview window to view all available plots.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 543

Profile Editor Controls and Displays

Graphical Preview Tab Window (part 2 of 5)

ITEM DESCRIPTION

Single Plot example

Multiple Plot example

544 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

Graphical Preview Tab Window (part 3 of 5)

ITEM DESCRIPTION
X Axis Defines the characteristics of the x axis (the bottom of the graph). The x axis
displays time.
X Auto Scale Enables the x axis to automatically change its maximum or minimum setting to
accommodate channel data.
Min/Max Specifies the scale of the x axis. Any part of the plot that exceeds the scale is
not shown.
Left Y Axis Defines the characteristics of the left y axis (the left side of the graph). The left
y axis displays a channel-level unit (which you selected in the Channel Setup
window).
Y 1 Auto Scale Enables the left y axis to automatically change its maximum or minimum
setting to accommodate channel data.
Min/Max Specifies the scale of the left y axis. Any part of the plot that exceeds the scale
is not shown.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 545

Profile Editor Controls and Displays

Graphical Preview Tab Window (part 4 of 5)

ITEM DESCRIPTION
Right Y Axis Defines the characteristics of the right y axis (the right side of the graph). The
application displays the right y axis when you display multiple channels with
different dimensions on the same plot, as shown in the example below (N on
the right y axis, and mm on the left y axis), or the same dimension with
different units.
• The left axis displays a channel-level unit.

• The right axis displays a different unit than the left y axis.

• The x axis displays time.

Y 2 Auto Scale Enables the right y axis to automatically change its maximum or minimum
setting to accommodate channel data.
Min/Max Specifies the scale of the right y axis. Any part of the plot that exceeds the
scale is not shown.

546 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

Graphical Preview Tab Window (part 5 of 5)

ITEM DESCRIPTION
Grid Lines When selected, displays grid lines on the graph.

Refresh Updates the plot in the Graphical Preview window to reflect current profile
values and current selections on the Graphical Preview tab in the Options
Editor window.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 547

Profile Editor Controls and Displays

Analyze Window
Access Tools > Analyze

Use the Profile Messages window to determine if there are flat spots in the
profile and their locations.

Analyze Description (part 1 of 2)

ITEM DESCRIPTION
Analyze Causes the application to check the profile for potential design errors. If the
application detects an error, it displays a message detailing problems that you
should be aware of before you save the profile. All the errors must be resolved
before you can save the profile.
This feature checks the current profile for the following:
• If there are no segments between block specifications

• If the data in level 1 of a segment is the same as level 1 of a block in the

next row, creating a “flat spot”

• If the data in level 1 of a segment does not match the data in level 1 or
level 2 of a block in the next row

• If any row has an incomplete specification

Example:
Suppose you created the sample profile shown, and then select Analyze on the
Tools menu.

548 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

Analyze Description (part 2 of 2)

ITEM DESCRIPTION

The application would detect that the Level 1 values in Rows 0 and 1 were
equal, as are the Level 1 values in Rows 2 and 3. This would cause flat spots in
the profile, as shown on the plot.

Flat spots may be undesirable. As a result, the application would display

information in the Profile Messages window.

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 549

Profile Editor Controls and Displays

Window Menu
Use the Window menu commands to change the appearance of the application
on your desktop.

Window Menu
ITEM DESCRIPTION
Cascade Displays all the open Profile Editor windows so that they overlap one another
in a diagonal pattern with their title bars showing.
Tile Displays all the open Profile Editor windows side-by-side, with each taking up
the same amount of space.
Arrange Icons When child windows are minimized, arranges their icons in a straight row at
the bottom of the Profile Editor window.
Toolbar Hides or displays the toolbar. To display the toolbar, select Toolbar on the
menu. This displays the toolbar and places a check mark by Toolbar on the
menu. To hide the toolbar, select Toolbar on the menu again to remove the
check mark.
Status Bar Hides or displays the status bar. To display the status bar, select Status Bar on
the menu. This displays the status bar and places a check mark by Status Bar
on the menu. To hide the status bar, select Status Bar on the menu again to
remove the check mark.
Window list Lists the open Profile Editor windows and channels. A check mark will be
displayed next to the item that currently has focus (the active window).

550 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 Profile Editor Controls and Displays

Help Menu
With the Help menu you can display version information about the Profile Editor
application and online documentation.

Help Menu
ITEM DESCRIPTION
Series 793 MPT and Opens the MTS Series 793 MPT and Application Software manual in the
Application Software Portable Document File (PDF) format.
Additional
Documentation

About Profile Editor Displays version information about the Profile Editor application

MTS MultiPurpose TestWare® Model 793.11 Profile Editor 551

Profile Editor Controls and Displays

552 Model 793.11 Profile Editor MTS MultiPurpose TestWare®

 About Default Templates

Appendix 19
Default Templates
About Default Templates
When you create a new test procedure with the MPT application, it inherits the
process layout and MPT Options Editor settings defined by the default
procedure template (default.000).

Note As shipped from MTS, the default procedure template does not include
process information, that is, the default procedure table is blank.

In some instances, you may want to change the default template to suit your
particular test environment.

If the default template is not found, the MPT application will use the built-in
template to define new procedures.

For more information See “Template Error Messages” on page 554.

How to Customize the Default Template

You can change the settings and processes defined by the default template to suit
your particular test environment.

1. In Station Manager, from the Applications menu, select MPT.

2. From the MPT file icon pull-down menu, click Open Procedure.

3. In C:\MTS 793\MPT\Procedure Templates, right-click the default.000 file,

and then click Properties.

4. In the Properties window, clear the Read Only check box, and then click
OK.

5. In the Open Procedure window, double-click the default.000 file to open it.

6. On the MPT control panel toolbar (or the MPT Procedure Editor), click the
MPT Options Editor icon. Customize the settings on each tab as desired.
(These settings will be used by new tests.)
Note When shipped, the default.000 file does not contain process
information—that is, the procedure table is blank. If you add processes to
the default.000 file, new test procedures will open with those processes
preloaded in the procedure window.

MTS MultiPurpose TestWare® Default Templates 553

How to Use Multiple Default Templates

7. From the MPT file icon pull-down menu, click Save Procedure to save the
customized default template. This new customized template will be used
when creating any new procedures.

8. Close the file.

9. From the MPT file icon pull-down menu, click Open Procedure.

10. In the Open Procedure window, right-click the default.000 file, and then
click Properties.

11. In the Properties window, select the Read Only check box, and then click
OK. This protects the new custom template from being inadvertently
changed.

How to Use Multiple Default Templates

You may create multiple unique default templates for your testing needs.
However, each template must be named default.000, and must be stored in a
separate directory—you cannot save more than one default.000 file in a given
directory.

1. Open your current default template (default.000).

2. Modify the default template as desired.

3. From the MPT file icon pull-down menu, click Save Procedure As.

4. Use the Save Procedure As window to save the file to a different directory,
with the label default.000. (All default templates must be named
default.000.)

Template Error Messages

MPT displays various error messages if it cannot locate a default template file.

The built-in template If MPT cannot locate the default template, it will display a default error message,
and create a procedure based on its built-in template.

The built-in template uses factory-set preferences that cannot be changed.

If the default template has been deleted, you can create a new procedure with the
desired attributes and save it as “Default.000.”

554 Default Templates MTS MultiPurpose TestWare®

 Template Error Messages

When you start MPT The following message is displayed when you start the MPT application and
MPT cannot find a default.000 file:

The default template file File 'Name.000' does not

exist. MPT will use its built-in template.

When you click OK, MPT will use its own built-in template to open a test
procedure.

When you select New The following message appears in the event you open a test procedure, select
after opening a New from the File menu, and the MPT application cannot find a default.000 file
procedure in the path specified for template files:

The default template is not available.

Do you wish to create a new procedure? (If not, the

current procedure will be retained.)

If you click Yes, MPT will open a new test procedure using the built-in template.

If you click No, MPT will remain in the current procedure.

When you select New The following message appears in the event that you edit a test procedure without
while editing a saving, click New from the File menu, and the MPT application cannot find a
procedure default.000 file in the path specified for template files:

The current procedure has been modified.

Do you wish to save it before creating a new

procedure? (The default template is not available.)

If you click Yes, MPT will save your changes to the current test procedure, and
open a new test procedure using the built-in template.

If you click No, MPT will close the current test procedure without saving your
changes, and open a new test procedure using the built-in template.

MTS MultiPurpose TestWare® Default Templates 555

Template Error Messages

556 Default Templates MTS MultiPurpose TestWare®

 About The MTS Excel File Converter

Appendix 20
Excel File Converter
About The MTS Excel File Converter
The MTS Excel File Converter is a utility that optimizes MPT data files for
viewing with Microsoft® Excel.

When this utility is installed and enabled, Microsoft Excel can interpret
MultiPurpose TestWare (and Basic TestWare) data files more intelligently than it
normally interprets text files.

For example, the MTS Excel File Converter can be used to:

• Permit loading an unlimited number of rows of data—up to the memory

capacity of your system. (Microsoft Excel has a limit of 65,535 rows of data
on each sheet.) The converter splits the data into multiple sheets.

• Scan the data file for certain labels and use smart processing to determine
when data should be written to a new worksheet. (This keeps your data
organized more efficiently.)

• Enable .dat, .t31, and .f31 files to be browsed and opened directly from the
Microsoft Excel Open window.

Compatible data file The Excel File Converter works best with tab-delimited data files (Excel format).
formats If you want to use the Excel File Converter, you should make sure your data files
are written in the Excel format.

Comma-delimited data files (Lotus format) can be processed by the converter,

but the format of the resulting spreadsheet may not be desirable. Space-delimited
data files (Plain format) will not be processed by the converter.

Note Files in "Lotus" format will be read in, but the format of the resulting
spreadsheet may not be desirable. If your Windows operating system’s
regional settings specify that decimal points should be commas (as is
typical in parts of Europe) the "Lotus" format will not be readable. Use
the "Excel" format whenever possible.

For more information For more about MPT data files, see “About Specimen.dat Files” on page 135.

MTS MultiPurpose TestWare® Excel File Converter 557

How to Install the Excel File Converter

How to Install the Excel File Converter

The Excel File Converter is included with the Model 793.00 System Software.
During the system software installation, you will asked if you want to install the
MTS Excel File Converter.

If you did not install it during the main software installation, insert the Model
793.00 System Software disc into your CD-ROM drive and follow these steps:

1. Follow this path using Windows NT Explorer:

Your CD-ROM drive > Excel Converter > Setup.exe

The following message appears:

Do you wish to install the MTS Excel converter onto

your system?

2. Click Yes.

3. In the Select Directory window, specify the location for the MTS Excel File
Converter utility, and then click Next.

4. Click OK to acknowledge a successful installation.

How to Set Excel File Converter Options

Specify your Excel File Converter options to customize your data files in some
useful ways.

1. Start the Microsoft Excel application. (A new spreadsheet will appear.)

2. On the Microsoft Excel Tools menu, click MTS Converter Options.

3. Select options as desired.

Option descriptions Enabled—This check box must be checked to enable the File Converter.

Smart Processing—If this box is enabled, the File Converter looks for certain
labels. When it finds one of these labels, and there is not the required number of
rows left in the current sheet, it will start filling a new worksheet. These are the
labels it looks for, along with their respective numbers of rows:

• Data Acquisition—4,000 rows

• Dynamic Characterization—2,000 rows

• Static Deflection—1,200 rows

558 Excel File Converter MTS MultiPurpose TestWare®

 How to Use the Excel File Converter

Note Smart processing will recognize German or French equivalents, based

on the regional settings of your Windows operating system setting.

One Test Per Sheet—If this box is enabled, each time the File Converter detects
a new test within a data file, it will cause that test data to start filling a new Excel
sheet.

How to Use the Excel File Converter

1. On the Microsoft Excel File menu, click Open.

2. In the Files of type list, click MTS Data Files (*.dat; *.t31; *.f31).

3. Locate the desired data file, and click Open. The data file should appear in a
new worksheet. If the Excel Text Import Wizard window appears, see the
troubleshooting section.

Excel File Converter Troubleshooting

If the Excel Text Import Wizard window appears when you open a .dat file,
ensure the following:

• The Excel File Converter is installed properly. If not, reinstall it.

• The Excel File Converter is enabled. If not, enable it.

• Your data file format is tab- or comma-delimited. If not, the file is

incompatible with the Excel File Converter. Make sure you generate all new
data files in the Excel format.

MTS MultiPurpose TestWare® Excel File Converter 559

Excel File Converter Troubleshooting

560 Excel File Converter MTS MultiPurpose TestWare®

Appendix 21
MPT Shortcuts
You can use an MPT shortcut to perform a number of tasks automatically when
you start the MPT application.

For instance, you can use MPT shortcuts to:

• Automatically load a specific procedure

• Automatically load a specific specimen

• Launch MPT as an editor (edit only mode)

• Automatically display the MPT Procedure Editor when MPT is launched

• Connect to a specific station

• Connect to a specific test system

To specify the MPT shortcut parameters, you must create an MPT shortcut, and
then edit the shortcut command line.

MTS MultiPurpose TestWare® MPT Shortcuts 561

Shortcut Command Line

Shortcut Command Line

Note The syntax of the shortcut command lines are critical. If you do not use a
supported shortcut command line, the shortcut will not work.

Parameter and prefix descriptions are listed as follows:

PARAMETER PREFIX EXAMPLE

Load a Procedure file /Procedure*, or /P /P default.000

Load a Specimen /Specimen*, or /Sp /Sp spec03

Launch MPT as an Editor (no /EditOnly

execution)

Launch the Procedure Editor /Editor [x:y:w:h:style] mpt /editor

with MPT 400:400:300:300:StyleMinimized
Connect to a Station /Station*, or /St /St station1.cfg

Connect to a System /System*, or /Sy /Sy 148.150.203.191

Controller Name /Controller name /Controller 001

Display the MPT command-line /Help, or /H
options

* If the parameter name contains spaces (for example, test 257.000), the name must be enclosed in
quotation marks (“test 257.000“).

Command line When you are editing the command line, keep in mind:
practices
• The order of the parameters is not important.

• Prefixes can be spelled out or abbreviated in the command line.

• The prefix and the parameter must be separated by a space.

• If the parameter name contains a space (for example, my first test.000), it

must be enclosed in quotation marks.

• The option names can be abbreviated to anything which is unique.

562 MPT Shortcuts MTS MultiPurpose TestWare®

 Shortcut Command Line

About the /EditOnly The /EditOnly option will launch MPT as an editor only. When you use this
command option, the MPT Specimen Log and Edit/Execute toolbar buttons will be
disabled. MultiPurpose TestWare is not embedded in Station Manager in this
mode. Since it is not embedded, it can be run on a different PC or as a second
copy of MPT, and so forth.

About the /Editor [...] The /Editor [...] option will launch MPT in the embedded mode with the
command Procedure Editor already displayed. The syntax of the optional arguments
(x:y:w:h:style) that specify the initial size and placement of the Procedure Editor
window are as follows:

• “x” specifies the x-coordinate of the upper left-hand corner of the window

• “y” specifies the y-coordinate of the upper left-hand corner of the window

• “w” specifies the width of the window in pixels

• “h” specifies the height of the window in pixels

• “style” specifies whether the window is maximized or minimized

An example of the full specification is:

“mpt /editor 400:400:300:300:StyleMinimized”

About argument Any of these arguments may be omitted, but the “:” must remain as a placeholder
commission if an argument is omitted in the middle of the string. Arguments at the end can be
omitted.

If an argument is omitted, the application will use a default value. For example,
suppose you are not sure what size you want the Procedure Editor window to be,
but you are sure you want it to appear in the upper left corner. In this case, you
would type:

“mpt /editor 10:10”

Likewise, suppose you want the Procedure Editor window to appear in the
default location, but you want its size to be smaller than its default size. It this
case, you would type:

“mpt /editor ::200:200”

About invalid values Also, if you type x or y coordinate values that are not valid for your screen
(values that would place part or all of the Procedure Editor window off the
screen), MPT will override your values so that the window appears fully on your
screen.

MTS MultiPurpose TestWare® MPT Shortcuts 563

How to Create an MPT Shortcut

Likewise, if you inadvertently type negative values for width or height, MPT will
use the default (positive) values for width and height instead of the negative
values.

How to Create an MPT Shortcut

Before you can edit the shortcut command line, you need to create a MPT
procedure shortcut.

1. Start Windows Explorer.

2. Open the folder where your system software is installed.

3. Open the ntbin folder.

4. Right-click the mpt.exe icon, and then click Create Shortcut. This creates
a shortcut file in the ntbin folder.

5. Drag the shortcut icon to your desktop.

6. Optional—Right-click the shortcut icon, and then click Rename. Rename

the shortcut, and then press Return.

564 MPT Shortcuts MTS MultiPurpose TestWare®

 How to Edit the Shortcut Command Line

How to Edit the Shortcut Command Line

Edit the shortcut command line to define your desired procedure parameters.

1. Right-click the shortcut icon you created on your desktop, and then click
Properties.

2. In the Properties window, click the Shortcut tab.

3. In the Target box, type your command line.

Note There must be a space between mpt.exe and your command line
addition.

4. Click OK.

Type your command line

here. Be sure to put a
space between mpt.exe
and the start of your
command line.

Click OK.

Test your shortcut To test your shortcut command line, make sure the Station Manager application is
started and the proper configuration file is open. Then double-click your shortcut
icon.

MTS MultiPurpose TestWare® MPT Shortcuts 565

How to Edit the Shortcut Command Line

566 MPT Shortcuts MTS MultiPurpose TestWare®

Index

Symbols block-arbitrary profiles 495

example 503
buffer full signals 88
how to trigger a process with a buffer full signal 274
"Make" tool 115 buffers, about 272

A C
Absolute Error signal in DAQ processes 277 Calculated checkbox 112
action Calculated Variables 112
channel grid 527 Calculations process 112
action constants 493 Channel Constants
actions 541 Count 540
assigning 493 description 540, 541
selecting 493 Level 1 540
activities level 1 & 2 527
Cyclic Command 186 Level 2 540
Sweep 220 Phase Lag 541
Add and Delete variable controls 115 Shape 540
Adding Calculations to Variables 113 Timing 540
ALC Channel Counters 22
Profile with ALC process 233 channel data syntax in profiles 500
ALC compensation 233 channel grid
Analyze action 527
option example 548 count 526
profiles 476 description 525, 526
Application Controls panel Frequency/Time/Rate 526
MultiPurpose TestWare 22, 23 information contained in 482
arbitrary segment 483 wave shapes 526
ASCII format 482 Channel menu 542
assigning Channel Setup
action constants 493 constants, assigning 486
actions 493 count units 538
profile constants 486 description 536
profile properties 485 Dimension 536
asymmetric full scales (Trend process) 343 Level Units 537
auto offset 437 Name 536
Auto Offset process 436 Timing 536
Auto Scale 545 Chart Properties
automatic transitions 516 Axis tab 452
command data syntax 500
command line practices 562
B command line, editing the MPT shortcut 561
commands
cyclic 186
ramp 186
bin size 323 sine 186
block arbitrary profiles square 186
description 483 true sine 186
sample 477 Compose Mail tab 426

MTS MultiPurpose TestWare® Index 567

Control Panel 22, 23 discontinuities, channel values resulting in 526
control panel 23 Display menu 37
controller rates supported by the Time History Output done signals 88
process 248 Drive has an offset 252, 264
control-mode variables 114 Dwell process 195
count how to define 197
channel grid 526 parameter descriptions 195
unit types 538
Count signal in DAQ processes 277
counter syntax in profiles 498
creating E
Block-Arbitrary profile 490
Phase profile 491
creating a profile using a normalized dimension 200, 510 Edit menu 37
creating actions when MPT is running 347 actions 541
cycle and segment description 538 description 535
cycle behavior in profiles 506 editing the command line 562
cycles - working with 484 EditOnly command 563
cycles vs. segments 187, 221 end levels
Cyclic Acquisition process 310 Cyclic Command activity 221
parameter descriptions 312 ending a procedure 89
Cyclic Command activity Error signal in DAQ processes 277
cycles and segments 187, 221 Excel (data format) 136
end levels 187, 221 Excel file converter 557
start levels 186, 220 execution icon 23
Cyclic Command process External Command process
parameter descriptions 222 setpoint and span settings 214
Cyclic with ALC process starting 212
how to define 245 stopping 213
parameter descriptions 241

F
D
Failure Detector process 382
data acquired in the specimen.log file 138 Failure Event 382
Data Display process fan-in process 88
Plots tab 441, 442 fan-out process 88
data files Fatigue process 319
using the Excel file converter 557 how to define 329
data handling (Trend process) 336 setting up a test to acquire fatigue data 328
Data Limit Detector process 346 File menu 37, 38
Default Profile Locations 481 New Profile Settings 525
default template (procedure) 553 Profile Summary 534
defining flat spots
parameters as constants 539 analyze 548
taper times 532 channel values resulting in 526
design Frequency/Time/Rate channel grid 526
errors 542
design elements that may lock up your system 46
designing tests to minimize undesirable latencies 45
Digital Input Detector process 353 G
parameter descriptions 354
Digital Output process
parameter descriptions 390 Graphical Preview
dimensions example 478
channel setup 536 grid lines 547
working with 199, 508 Group menu 37
disabled icon 23

568 Index MTS MultiPurpose TestWare®

Group process 405 Integer Count signal in DAQ processes 277
about interrupts 100 Interlock signal in DAQ processes 277
how to move between the group and the main procedure Interrupt (control) 41
windows 405 interrupt signals 88
start and interrupt signals 88

L
H
latencies in test procedures 45
Help menu 38 level 1 & 2 527
High Speed Timed Acquisition process Level Crossing Acquisition process 296
parameter descriptions 306 Level Units 537
histogram limit modes, about 347
types 320 Limit Settings window
histograms Trend Monitoring application 463
MinMax 322 Load Specimen window 140
range 323 locking up your test system 46
rangemean 321 lookup table 228
histograms, about 320 Lotus (data format) 136
Hold button 35 low rate channels (temperature controller) 393
enabling and disabling 63
Hold signal in DAQ processes 277
how to
add a channel 490, 542 M
analyze profiles 494, 548
assign an action 493
assign profile constants 492 manual transitions 517
assign profile properties 492 Max/Min Acquisition process 289
create a new profile 488 how to define 294
create a phase profile 491 parameter descriptions 294
create a Specimen file 48 menus
create a specimen file 48 Display menu 37
create block arbitrary profiles 490 Edit menu 37
create channel values and properties 525 File menu 37, 38
customize a plot 543 Group 37
define constants 539 Help menu 38
define taper times 532 Tools menu 38
edit profile descriptions 534 Window menu 38
name profiles 525 MinMax histogram 322
open existing profiles 489 MPT
preview profiles 513 Options Editor 153
select channel focus 542 shortcuts 561
select profile types 525 toolbar 38
select wave shapes 526 MPT profile process 520
set preferences 489 MPT shortcuts 561, 564
set up a channel 536 Multiple Plots 543
use scientific notation 512 MultiPurpose TestWare
use unity 512 Data Display process 441, 442
HSM High signal in DAQ processes 277 Station Manager, starting in 22, 23
HSM On signal in DAQ processes 277
hydraulics, required state 31, 64
N
I name template (specimen) 133
New Profile Settings window 525
indicators, process 41 normalized dimensions 200, 510

MTS MultiPurpose TestWare® Index 569

Numerical Data window 464, 472
P
O parameters
Cyclic Acquisition process 312
Cyclic Command process 222
offset considerations 437 Cyclic with ALC process 241
open existing profiles 489 Digital Input detector process 354
Operator Event process 359 Digital Output process 390
how to define 363, 381, 385 Dwell process 195
parameter descriptions 360 High Speed Timed Acquisition process 306
Operator Information process Max/Min Acquisition process 294
how to define 409, 417, 418 Operator Event process 360
parameter descriptions 412 Operator Information process 412
Options Editor 153 Peak/Valley Acquisition process 280
Preview tab Peak/Valley Change Detector process 368
Auto Scale 545 Profile with ALC process 233
Available Channels 543 Program Control process 400
Channel Display 543 Road Surface Output process 263
Channels to Plot 543 Segment process 182
description 543 Send Mail process 426
grid lines 547 Set Calculation Parameter process 432
Left Y-Axis 545 Signal Based Command process 229
Max/Min 545 Temperature Control process 395
Multiple Plots 543 Timed Acquisition process 284
Refresh button 547 Trend process 338
Right Y Axis 546 pass-through icon 23
Single Plot 543 Peak/Valley Acquisition process 279
X Axis 545 how to define 282
Output signal in DAQ processes 277 parameter descriptions 280
overriding system setpoint and span 215 Peak/Valley Change Detector process 364
how to define 371
parameter descriptions 368
phase lag 528
Phase profiles
description 528
phase profiles 484, 495
plain (data format) 136
Plot
additional properties 452
Chart Properties
Axis tab 452
Setup tab
Y1, Y2 axis 442
Plots tab 441, 442

570 Index MTS MultiPurpose TestWare®

Preview tab
Auto Scale 545 R
Available Channels 543
Channel Display 543
Channels to Plot 543 rainflow counting, about 320
description 543 ramp
grid lines 547 tapered wave shape 540
Left Y-Axis 545 tapered wave shapes 526
Max/Min 545 understanding channel grids 482
Multiple Plots 543 wave shapes 526
Options Editor 543 waveform 540
Refresh button 547 ramp command 186
Right Y Axis 546 ramp tapered wave shape 189
Single Plot 543 ramp wave shape 188
X Axis 545 range histogram 323
print preview rangemean histogram 321
toolbar 533 recovery
Print Preview toolbar 533 enabling test 63
Procedure is done when (control) 41 Recovery tab 74
procedure template reducing unwanted latencies 45
customizing 553 Refresh button 547
procedures repeating Group process 46
done signals 88 required hydraulic state 31, 64
specifying the end 89 restore procedure settings 138
start and interrupt signals 88 restoring an interrupted test 139
process indicators (procedure window) 41 resuming a test 63
Process Types Palette 84 Right Y Axis 546
processes 84 RMS (Trend process) 343
fan-in and fan-out 88 road surface files, creating 261
profile Road Surface Output command process 261
analysis message example 549 Road Surface Output process
constants assigning 486 parameter descriptions 263
properties 482 Road Surface Output Status window 262
properties assigning 485 rollover Running Time 276
selecting actions 493 Rollover Time 276
spreadsheet description 526 RPC files, playing out 247
summary information 525 Run button 35
Profile Editor application 529 Run/Stop signal in DAQ processes 277
Profile process 198 running third party software 45
how to define 208 Running Time 276
Profile Summary description 534
Profile with ALC process 233
how to define 239
parameter descriptions 233
S
Profiles in Projects 481
Program Control process 400
how to define 404 scientific notation 512
parameter descriptions 400 segment
Program Event process description 538
how to define 376 working with 484
Program Interlock signal in DAQ processes 277 segment behavior in profiles 506
Project definition 20 segment command process
Project Manager application 20 how to define 184, 186
Properties tab 80 Segment process
parameter descriptions 182
segment shapes 188
segments vs. cycles 187, 221
selecting a specimen 48
selecting actions 493
selecting default units 536

MTS MultiPurpose TestWare® Index 571

Send Mail Now button 426 Station Manager
Send Mail process 426 controls and displays 521
Sensor signals 277 main menu 521
Sequence Counters 22 Print Preview toolbar 533
sequencing processes toolbar 523
example 93 Station signals 276
Set Controller Value process 430 Status and progress indicator 23
set profile preferences 489 stopping an External Command process 213
set taper times 532 Sweep activity 220
setpoint System Tick Count 276
external command process 214
overriding 215
shapes 540
shortcut command line 562 T
shortcuts, MPT 561
Signal Based Command process
about 226 taper time defining 532
signal based command process tapered wave shapes 189
creating 231 Temperature Control process
example 227 parameter descriptions 395
lookup table file 228 templates
parameters 229 See default template (procedure)
signals See name template (specimen)
buffer full 88 test data 48
done 88 test procedure design and execution considerations 105
start and interrupt 88 test procedures
trigger 88 how to open 47
sine how to preview 47
channel grid 482 how to print 47
wave shape 526 how to save 47
waveform 540 test recovery
sine command 186 how to enable 63
sine tapered wave shape 189 test specimen 48
sine wave shape 188 Time 276
single plot 543 Time History Input process 331
smart limits (Trend process) 342 Time History Output process 247
SMTP Server control 427 how to define 258
span Time History Output Status window 249
External Command process 214 Timed Acquisition process 284
overriding 215 how to define 287, 308
Specimen parameter descriptions 284
definition 48 timing
selecting a file 48 Channel Constants 540
Specimen.mpp file 138 Channel Setup 536
Specimen.mps file 139 toolbar 38
Specimen.prm file 139 print preview 533
square Station Manager 523
tapered wave shape 526, 540 Tools menu 38
wave shapes 526 analyze example 548
waveform 540 description 542, 548
square command 186 transition states 70
square tapered wave shape 189 transitions
square wave shape 188 automatic 516
Start (control) 41 description 514
start levels manual 517
Cyclic Command activity 186, 220 Trend Monitoring application
start Profile Editor 490 Limit Settings window 463
start signals 88
starting an External Command process 212

572 Index MTS MultiPurpose TestWare®

Trend process working with
about data handling 336 cycles 484
about RMS, variance, and asymmetric full scales 343 dimensions 199, 508
about smart limits 342 segments 484
how to define 341 transitions 514
parameter descriptions 338
setting up a test to acquire trend data 340
trigger signals 88
using (example) 91 X
true sine command 186
true sine tapered wave shape 190, 222
true sine wave shape 526 x axis 545
true sine wave shapes 540 x-y plot 543
true sine waveform 540 x-y plot of profile 542, 548, 549

U Y
UAS Editor 153 y axis 546
Unit Assignment Set Editor 153 Y1, Y2 Axis subtab 442
unit sets, standard 56
unitless 512
unity 512
usable range 437
using Profile files to minimize latencies 45

V
Variable categories 115
Variable type control 115
variables
control-mode 114
Variables Editor 112
variance (trend process) 343
virus-checking software 45

W
wave shapes 188
ramp 188
ramp tapered 189, 526, 540
sine 188
sine tapered 189
square 188
square tapered 189, 526, 540
tapered 189
true sine 526, 540
true sine tapered 190, 222, 526, 540
Window menu 38
Windows® workstation issues 45

MTS MultiPurpose TestWare® Index 573

574 Index MTS MultiPurpose TestWare®
m
MTS Systems Corporation
14000 Technology Drive
Eden Prairie, Minnesota 55344-2290 USA
Toll Free Phone: 800-328-2255
(within the U.S. or Canada)
Phone: 952-937-4000
(outside the U.S. or Canada)
Fax: 952-937-4515
E-mail: [email protected]
Internet: www.mts.com

ISO 9001 Certified QMS