MTS TestSuite TW Elite Test Design Guide 100-234-122 G be certain.
© 2014 MTS Systems Corporation. All rights reserved. Trademark Information MTS is a registered trademark of MTS Systems Corporation within the United States. This trademark may be protected in other countries.All other trademarks or service marks are property of their respective owners. Proprietary Software 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.
Table of Contents Table of Contents Preface Before You Begin.............................................................................................................................................7 Documentation Conventions............................................................................................................................7 Technical Support How to Get Technical Support..............................................................................................................
Table of Contents Resources Subtab...............................................................................................................................45 Test Definition Subtab........................................................................................................................47 Monitor Tab....................................................................................................................................................49 Review Tab Layout........................
Table of Contents Acquiring Data in Blocks Without Mode Switching.............................................................75 Acquiring Data in Blocks With Mode Switching...................................................................75 Setting Buffer Size.................................................................................................................75 Data Acquisition for Test-Run Displays................................................................................
Table of Contents Station Controls Panel......................................................................................................................107 Station Configuration Files..............................................................................................................108 TWE Startup.....................................................................................................................................109 Working with Limits..........................................
Preface Before You Begin Safety first! Before you use your MTS product or system, read and understand the 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.
Preface 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.
Preface Electronic manual conventions This manual is available as an electronic document in the Portable Document 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.
Technical Support How to Get Technical Support Start with your manuals The manuals supplied by MTS provide most of the information you need to use and maintain your equipment. If your equipment includes software, look for online help and README files that contain additional product information. Technical support methods MTS provides a full range of support services after your system is installed. If you have any questions about a system or product, contact Technical Support in one of the following ways.
Technical Support 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.
Technical Support — 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.
Technical Support • 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.
Introduction Topics: • • • About This Guide...............................................................................................................................16 Start TWE and Open the Example Test............................................................................................17 TWE Main Window............................................................................................................................
Introduction About This Guide The MTS TestSuite TW Elite Test Design Guide contains the information you need to begin customizing templates with the TW Elite (TWE) application. It includes the fundamental concepts of using the TWE application with MTS control software to create and run tests. This guide does not explain every TWE application feature. Its goal is to introduce the most important features of the application in the context of customizing tests.
Introduction Start TWE and Open the Example Test Install TWE in simulation Installation of TWE consists of running a self-extracting executable file. When running the MTS TestSuite InstallShield wizard, ensure you select “Insight/Criterion Simulation” when choosing the controller type. Note: The following startup procedure is for electromechanical systems. For servohydraulic systems, see TWE Startup (p. 109). Open the Example MTS EM Tension (Simplified) Test 1. Start the TWE application.
Introduction TWE Application Main Window TWE Main Window Description Number Item Description 1 Menu bar and Quick Access panel Provides menus and quick-access icons that allow you to perform tasks such as opening tests, opening tests from templates, and saving tests as templates. 2 Control panel Allows you to resolve interlocks; display fault status; view the direction in which the crosshead is moving; position the crosshead; and start, stop, and hold the test.
Introduction Number Item 4 Description Toolbox panel (not The contents of the Toolbox panel change depending on the subtab shown) selected in the Define tab: • When you select the Procedure subtab, the Toolbox panel contains components that pertain to test activities such as commands, data acquisition, test flow control, and program actions.
Introduction Main Window Toolbar TWE Application Main Toolbar Application Toolbar Description Number Item Description 1 Controller panel Allows you to reset interlocks. 2 Status panel Shows fault status information. This indicator is primarily for diagnosing system errors with MTS service personnel. 3 Direction panel Indicates when the crosshead/actuator is moving and in what physical direction. This relates to physical motion, regardless of whether feedback is increasing or decreasing.
Introduction About the Multi-Head Run Section Note: The Multi-Head option is a separately licensed feature. Note: Prerequisite: Only analog data is collected from the multiple active load cells in a multi-head frame. You must have National Instruments Data Acquisition (Ni-DAQ) hardware and software or an extensometer installed which will convert the analog data to digital signals.
Introduction Multi-Head Run Section Properties Multi-Head Run Section Properties Item Description Number of Active Load Cells Specify how many test-runs should be created. For example, if you are testing four specimens, enter 4. When the test run has ended, four test run files will be created. Default: 5 Click the Automatically Map Variables checkbox to have the system map variables, or click the Configure button to open the Map Variables window and manually map variables.
Introduction Item Description Note: If you select the Automatically Map option and then change the Number of Active Load Cells value, some variables will be created or removed. If you map variables manually, and then select Auto Map Variables, your manually created variables will be overwritten by the automatically-generated variables. Test Run Variables Specify variables that are not in the Common category.
Examine the Example Test Topics: • • • • • • About this Chapter.............................................................................................................................26 Design Flow.......................................................................................................................................26 Define Tab.........................................................................................................................................27 Monitor Tab..........
Examine the Example Test About this Chapter This chapter provides a detailed review of the example test provided with the TWE application. You will examine the test’s workflow, test activities, use of variables, and so on. Understanding how the example test was created with the TWE application and how the test appears in the interface will help you understand how to create tests of your own. Modify the Example Test (p. 81) provides a tutorial for modifying the example test for a different scenario.
Examine the Example Test Note: When operators use TWX, tests typically open to the Monitor tab so operators can review pretest variables before performing test runs. However, if the selected test has validation errors, the test opens to the Define tab so operators can use the Resource subtab to resolve resource conflicts. Monitor tab Use the Monitor tab to review pretest variables (inputs that typically apply to all of the test runs in the test) shown to the operator.
Examine the Example Test Outline View and the Find Feature Item Description 1 Outline button Tip The Find feature is particularly useful for locating activities nested within other activities. For instance, to locate the Go To + DAQ + Detection command activity in the example test, enter Go To and press return. The outline hierarchy expands to show the Go To + DAQ + Detection activity, and the activity is highlighted in the workflow.
Examine the Example Test Workflow of the Example Test All TW tests include the following sections: • Set Up • Run • Finish Set Up Section The Set Up section runs only once before the first test run. Since there are no activities in the Set Up section of the example test, the Set Up section is skipped and the Run section begins immediately.
Examine the Example Test Set Up Section of the Example Test. For More Information Modify the Example Test (p. 81) Run Section The Run section performs a test run when the operator clicks the Run button. After each test run, the Review tab appears, which shows test data in tables and charts. The Run section of the example test has been performed three times, so the Review tab includes data from three test runs.
Examine the Example Test Note: The following figure shows the top Parallel Path activity in the Run section expanded.
Examine the Example Test Run Section Description Number Description 1 Parallel Path activity: left branch. 2 Parallel Path activity: right branch (disabled). 3 If-Else activity (disabled). 4 Custom Message activity (disabled): “The Test is About to Start”. 5 Input Parameters activity. 6 Parallel Path activity in left branch of (1). 7 Custom Message activity: “Return to Zero”.
Examine the Example Test Program Command in the Example Test In the example test, program command is issued from the Go To + DAQ + Detection activity nested within the second Parallel Paths activity in the Run section. This is the only activity in the example test that applies forces to the specimen. Branches in the Parallel Activity Description of Branches in the Parallel Activity Item Description 1 Auto Offset and Go To + DAQ + Detection activities.
Examine the Example Test Item Description 5 Digital Input Detector activity: Handset Connected. For more information, see Path with the Digital Input Detector for the handset . Branches in the Parallel Paths Activity The nested Parallel Paths activity in the example test contains five parallel branches. All of the branches are terminal, meaning the completion of any of the paths ends all of the other paths.
Examine the Example Test About detector action resources Actions are test resources. By default, the only action available to the detectors in the example test is No Action. The MTS Insight controller also supports Program Hold, Program Stop, and Interlock actions, but these actions have been removed from the test because they are not used.
Examine the Example Test Go To Tab and Edit Variables Window DAQ tab The DAQ (data acquisition) tab is configured to continuously acquire timed load (force) and crosshead (length) data at a sample rate defined by the Data Acquisition Rate variable. It is also configured to map acquired data to array variables.
Examine the Example Test DAQ Tab, Trigger Properties Window, and Map Variables Window About mapping data to variables In all MTS templates created for TW, the Save data to variables? control is enabled by default. Mapping data to arrays significantly extends the functionality of TW.
Examine the Example Test When the detector is armed and the peak load value drops by the percentage defined by the Break Sensitivity variable, a break is detected. The action is set to No Action. This means if a break is detected, the detector trips and the Parallel Path activity ends. For many types of tensile tests, the test run completes when the specimen fails and the break detector trips.
Examine the Example Test Wait for Operator Action Tab and the “Next Segment” Button Shown on the Monitor tab Finish Section The Finish section runs: • Automatically, when the Maximum Test Runs variable equals the number of test runs performed, or • Manually, when the operator clicks the Run the Finish Section button on the Review tab toolbar. The Review tab appears automatically after each test run.
Examine the Example Test Run the Finish Section Button on the Review Tab Test-Run Display Subtab When you click on the Test-Run Display subtab of the Define tab, the center of the main window shows the designer view of the test-run displays used in the test. You can think of a test-run display as a readout device—like a meter or scope—that shows test signals or other information on the Monitor tab during test runs. The only test-run display used in the example test is the Array-Variable chart.
Examine the Example Test Variables Subtab and Variable Availability Property Variable Definition A variable is a place with a name in which you can store one or more values. Variable types and examples used in the test include: • Simple variables (also referred to as scalar variables) store either a value or a string. In the example test, the variable used to set the rate at which data is acquired is a simple variable.
Examine the Example Test • You could not use the array-variable chart on the Test-Run Display subtab, or any of the other test-run displays in the Variable Views category (or other test-run displays that use variables). You would only be able to use test-run displays in the Signal Views category, such as signal meter and signal scope. • The charts and tables in the Review tab, which are based on variables, would not contain useful information.
Examine the Example Test Access to the Variables Table and Editable Post-Test Variables Result attribute The Result attribute specifies the variables that appear in the Result table and Variables tables in the Review tab. In the example test, the Peak Load variable has the Result attribute, and appears on the Results table. Peak Load Variable on the Result Table Variables with both Results and Editable Post Test attributes Some variables include both Editable Post Test and Result attributes.
Examine the Example Test Reports Templates Subtab Default Test-Run Report template Use the default Test-Run Report template for generating reports for individual test runs. The example test does not include an activity in the workflow to generate a report for test runs. However, the operator could generate a report for test runs using the toolbar controls on the Review tab. Default Test Report template Use the default Test Report template for generating reports that apply to all the test runs in the test.
Examine the Example Test Using Python with MTS TestSuite Python is an interpreted, general-purpose, high-level programming language with an extensive resource library. You can use Python to create custom functions to extend the functionality of MTS TestSuite software. You can use Python for reading and writing to files, dynamic mathematical calculations, and manipulating variables.
Examine the Example Test Resources Tab Description Number Description 1 Connection indicator 2 Test resources 3 Controller resources 4 Resource management controls Controller identification The connection indicator (1) shows the controller configuration associated with the current test when TW is connected to a controller. In the example test, the controller configuration is labeled “C42.503 (Simulator)”.
Examine the Example Test Resources Subtab with Imported Resources Resource mapping A test resource is not required to have the same name as the equivalent controller resource. For instance, in the example test, the control mode test resource is labeled “Crosshead”, and the equivalent controller resource is labeled “_Extension”. However, if the names are different when TWE connects to the controller, you must map the test resource to the equivalent controller resource.
Examine the Example Test Note: All fields are read-only until you click the Edit button. Test Definition Subtab Formula Assistant File The Formula Assistant File provides a base set of system variables, calculations, and functions associated with a specific type of test. The example test uses a formula assistant file labeled “Electro-Mechanical Formula Assistant”. If you need to change the Formula Assistant File associated with a template, contact your MTS Field Service Engineer for assistance.
Examine the Example Test If you disable this control, the display remains on the Monitor tab after each test run instead of automatically switching to the Review tab. For More Information Changing the Specimen Geometry (p. 84) Monitor Tab Monitor tab view before the test starts Before the operator starts the test by clicking the Run button, the Monitor tab shows the pretest inputs the operator can change.
Examine the Example Test Edit Pretest Inputs Description of Variables Tab Number Description 1 Click this icon to display the Column Chooser. 2 Select Pretest in the Column Chooser 3 Pretest attribute appears in the table. Monitor tab view after the test starts After the operator starts the test, the Monitor tab shows test information on the test-run display included in the test design until the test run is complete. In the example test, the Array-Variable Chart is used, as shown.
Examine the Example Test Monitor Tab During a Test Run Review Tab Layout The Review tab displays after a test run ends showing test run statistics, charts, and so on.
Examine the Example Test Review Tab Description Number Item Description 1 Toolbar Provides icons that allow you skip to the activities in the Finish section of the test, revert and recalculate variables, generate and print reports, and configure and save the layout of the Review tab. 2 Test run results table Shows test results from individual test runs, allows you to compare one test run to another, and allows you to exclude (referred to as tagging) individual test runs from statistical computations.
Examine the Example Test Number Item Description 2 Run Finish Section button Runs the Finish section. You may also run the Finish section automatically by entering the desired number of test runs in the Maximum Test Runs variable, which has a default value of 9999. 3 Generate a report for Test Runs/Test buttons Generates reports that you can open using Microsoft Excel. You can generate reports that pertain to individual test runs or the test. You can choose pre-made or customize report templates.
Examine the Example Test Configure Autotag rules The Autotag feature allows you to create rules that determine when a test run is automatically tagged (excluded). The Autotag rules are applied as each test run is run or can be defined and applied post test. Tagging specimens manually You can manually tag (exclude) test runs by selecting the test runs in the Tagged column. Tagged test run data is not compiled in the Statistics table.
Examine the Example Test Chart Marker Variable Manipulation Description of Chart Marker Variable Manipulation Number Description 1 Right-click the M marker (Slope 2 Index variable) and select Edit Variable. 2 Use the Edit Variable window to review and edit the marker variable properties. 3 You can move the M marker by entering a new value in the Variables table or by selecting the Move Selected Marker in the marker right-click menu.
Examine the Example Test Calculated markers Calculated markers are typically derived from a calculation and are often used in a calculation. For example, the least squares calculation for the modulus line in the example test uses two calculated marker variables that appear on a chart. (Marker B, the Slope 1 Index variable; and Marker M, the Slope 2 Index variable). Using chart variables in test reports You can add, remove, and edit the markers on the chart. You can also use chart variables elsewhere.
Examine the Example Test Description of Four-Panel View of Review Tab Number Description 1 The Review Chart view in the four-panel view is the same Review chart shown in the one-panel view. It shows a chart of the active (highlighted) test run, in addition to the test runs selected (checked) in the Compare column. 2 The Review Chart for Multiple Runs view shows a chart of the selected (checked) test runs, in addition to the active (highlighted) test run, without markers.
Examine the Example Test Runtime Values Tab During a Test Run 58 | MTS TestSuite
Design Guidelines Topics: • • About this Chapter.............................................................................................................................60 Designing Tests.................................................................................................................................
Design Guidelines About this Chapter This chapter contains concepts, design considerations, and recommended practices for designing tests with TWE. For related procedural information and interface reference, see the MTS TestSuite TW Elite User Guide installed with the TWE application (Start > Programs > MTS TestSuite > Documentation > TW Elite User Guide). For a step-by-step tutorial for modifying the Sample Tension (Simplified) Test, see Modify the Example Test (p. 81).
Design Guidelines Step Activity Description 2 Modify the test Modify the test by enabling disabled activities within the template, changing Formula Assistant file options, adding resources, and editing the workflow. 3 Select and customize a Test Report template Create or modify the existing test report template by adding test variables, etc., from your test run to the template. Editing report templates requires the optional MTS Reporter Add-In for Microsoft Excel.
Design Guidelines File Type Icons Icon File Type MTS Templates—Only the templates for which you are licensed appear available in the MTS Templates folders. Templates that are licensed but not applicable to an application are grayed out. MTS supplied templates are installed by default in C:\Program Files\MTS Systems\MTS TestSuite\Templates. For 64-bit operating systems, the path is C:\Program Files (x86)s\MTS TestSuite\Templates. Custom Templates—Includes any test or template saved as a template.
Design Guidelines Modifying Tests Adding and Configuring Test Activities Test activity sequence Test activities execute from top to bottom as they appear on the Test Editor. To execute activities simultaneously, add Parallel Path activities to the test flow. You can also add While Loop, If-Else Condition, and Periodic Time Event activities to control the test flow.
Design Guidelines Error Indicator and Help for the Data Acquisition Activity Skipping command segments or stopping a test prematurely When you run a test, the Test-Run Display shows the progress of the test on a chart (such as the Array-Variable chart used in the sample test). While developing a test, it may not be practical to allow the entire command to play out while iterating between modifying and running a test. To speed up iterations, you can use the Wait for Operator Action activity.
Design Guidelines Considerations for Test Sections Set Up section The Set Up section is for activities you want the operator to perform before test runs begin, such as: • Entering values for test variables common to all test runs • Configuring the load train (setting up fixtures, and so forth.) • Entering the test name, specimen geometry, lot number, batch name, and so forth. The Set Up section runs only once per test, before the first test run. Run section The Run section performs test runs.
Design Guidelines Run the Finish Section Button on the Review Tab • You can enter a value for the Maximum Test Runs variable (Define tab > Variables subtab > Maximum Test Runs). When the number of test runs equals this value, the test will run the Finish section. By default, this value is set to 9999. Maximum Test Runs Variable on the Variables Subtab Internal Name and Display Name Internal Name Generally, this is a name that is used internally to the application or by a calculation.
Design Guidelines level do not have the same name. These strings are translated and will change based on language if it was saved in multiple languages (such as with templates). Configuring What is Displayed After Test Runs By default, the application shows the Review tab after each test run. This is set in the Test Definition subtab of the Define tab.
Design Guidelines (Signal("Run/Stop") != 0) This causes the While Loop activity to terminate if the stop state is present when the Run section ends. Pre-Allocating Multiple Test Runs If you are testing multiple specimens, you can improve the speed and reliability of your testing by pre-allocating test runs for each specimen. When you pre-allocate test runs, you can specify unique variable values for each specimen prior to running tests.
Design Guidelines Note: If the test definition is changed during test design (for example, variables, resources, and workflows are edited), any changes made will not be applied to existing pre-allocated test runs. In this case, the test designer must delete the existing pre-allocated test runs and pre-allocate new test runs. Working With Variables Variable Concepts A variable is a place with a name in which you can store one or more values.
Design Guidelines Using Variables in Activities MTS TestSuite applications allow you to define many of the individual properties of test activities as variables. Normally, when you enter a value for a property in an activity, you can change the value only when the test is stopped and the test procedure is unlocked. In this sense, the property is “fixed.” With the use of variables, you can associate a property of an activity with a variable.
Design Guidelines Variable Example Manipulating Variables in the Workflow The TWE application includes test activities you can use to manipulate variables in the workflow, as follows: • Assign Variables activity • Calculate Variables activity • Input Parameters activity • Read Variables to a File activity • Writer Variables to a File activity You can use these activities in a variety of ways to manipulate variables.
Design Guidelines Assigning Variable Availability Variables have the following Availability attributes: • Pretest • During Test • Editable Post Test • Result The Pretest, During Test, and Editable Post Test attributes specify when the operator can change the variable during the test. Pretest attribute Variables with this attribute can be edited before the test is initialized and the test runs begin. They appear on the Monitor tab and can be changed before the test is started.
Design Guidelines Recommended The application always performs calculations in base (system) units. To avoid unit-conversion errors when adding a calculation to a variable, create variables to hold constants used in the calculation. Assign the desired units to each variable and the application will convert the unit type to the base unit type when performing the calculation. For more information, see the MTS TW Elite User Guide.
Design Guidelines Description of Variable Tab Number Description 1 Search tool 2 Variable Actions button 3 Select Update Used By to display the Used By column Used By Table Column The Used By table column shows where and how many times each variable is used in the test. This is useful for: • Editing variables used by more than one activity. If a variable is used by multiple activities, you may want to create additional variables to manage the unintended changes. • Troubleshooting complex tests.
Design Guidelines • You will not be able to use any of the monitor displays in the Variable Views category (or other monitor displays that use variables). You will only be able to use monitor displays in the Signal Views category, such as the Signal Meter and Signal Scope. • The charts and tables in the Review tab, which are based on variables, will not contain useful information. • You will not be able to show test data in charts and graphs using the MTS Reporter Add-in for Excel.
Design Guidelines Data Acquisition for Test-Run Displays In the Test-Run Display Toolbox, the Cycle View category pertains only to data that is divided into blocks. This is an important consideration, because if you attempt to use one of these display devices to view data that is not blocked, the view will appear blank, because the device is waiting for the first block boundary.
Design Guidelines Settings that Affect Polarity Item Description 1 Upper and lower workspace selection. These buttons are only available on test systems equipped with dual workspaces. These buttons allow operators to easily switch between different test zones without manipulating the test resources or using a different test that has unique polarity settings for different workspaces.
Design Guidelines Configuring the settings that affect polarity When designing your test, use the following procedure to ensure that the settings that affect polarity are appropriate: 1. Import the resources that are required by your test. 2. If your load frame has upper and lower workspaces, select the desired workspace. 3. For each float signal, select the polarity that produces the desired output. 4. For each Float Signal, select the desired Effect of Increasing Extension.
Design Guidelines Automatic Saves and Experimentation When you run a test, the application performs an automatic save. If you make changes to a test that you want to delete after you ran a test, you will have to manually back out of the changes. Tip If you want to experiment with a test, perform a Save As operation. Rapid Design Iterations Running the Set Up section without starting a new test The Set Up section runs only once per test before the first test run.
Modify the Example Test Topics: • • • About this Chapter.............................................................................................................................82 Modifying Tests..................................................................................................................................82 Design Scenario................................................................................................................................
Modify the Example Test About this Chapter This chapter contains instructions for performing modifications to the Example MTS Tension (Simplified) Test supplied with the TWE application. While the modifications are unlikely to result in a test that you will use in your facility, the process of making the modifications will help you learn how to use the application. The example test is reviewed in detail in Examine the Example Test (p. 25).
Modify the Example Test • Add activities to the workflow • Change settings in the various tabs in the Configuration window (Preferences > Configuration) Methods used to modify the example test The procedure for modifying the example test includes most of these methods. The procedure does not include information about optional controls.
Modify the Example Test • The operator needs to view a video you created for installing the specimen in the fixture at the beginning of each test. You want this video to be shown only before test runs begin. Modifications to the Set Up section • Change the specimen geometry type. To do this, you will change the Area variable option of the Formula Assistant File from rectangular to round.
Modify the Example Test 3. Scroll down and notice that Width and Thickness are also variables in the Test Definition. You can also view the current calculation of the variable in the formula box of the Calculation panel. 4. Select Round from the Option list and click Apply. Notice that the Pi() formula to calculate a round area has automatically been populated for you. After you click Apply, the formula is replaced in both the Calculation and the Variables panels.
Modify the Example Test 5. Observe that the variables used for calculating a rectangular area (Width and Thickness) are automatically removed from the Variables panel, and the variable for Diameter is automatically added to the Variables panel. Adding an Input Variables Activity Overview This task adds an Input Parameters activity to the workflow and defines its properties. Procedure 1. Select Define>Procedure. In the Toolbox Panel, scroll to the Operator Entry category. 2.
Modify the Example Test 3. Enter the following information in the Properties Panel: Input Variables Activity Properties Property Value Display Name Enter “Enter Batch Name” Message Enter “Enter the batch name as it appears on the label on the box of specimens.” Variable List Note: Click the plus sign and use the Variable Selection window to add variables.
Modify the Example Test Moving and Enabling Run External Application Activity Overview This task moves the Run External Application activity from the Run section to the Set Up section, enables it, and configures it to run a pre-existing video file. 1. Click the workflow and expand the Run section. 2. Drag the disabled Run External Application activity from the Run section to the Set Up section, below the Input Parameters activity. 3. Click the Properties tab. 4.
Modify the Example Test • The test needs to ramp in displacement control at 3 mm/s not to exceed a 1 kN load level. • The test needs to slow down to minimize overshoot of the ending condition. Modifications to the Run section • Enable the Custom Message activity and add a message. • Modify the Test Rate variable from the Go To + DAQ + Detection activity. • Add a Termination Condition of 1 kN to the Go To + DAQ + Detection activity.
Modify the Example Test 4. Enter the following information in the Properties panel: Custom Message Activity Properties Property Value Display Name Enter “Stay Clear” Edit Message Enter “The test is about to begin. Stay clear of the test frame.” Runtime effect The TWE application shows the message during every test run after the operator clicks the Run button. The application does not perform the test run until the operator clicks OK.
Modify the Example Test 4. In the Properties panel, enter the following: Go To + DAQ + Detection Activity Properties Property Value Display Name Enter “Apply Program Command” Note: The controls that follow are in the Go To tab. Rate Right-click Rate and select Edit to display the Edit Variable window. In the Edit Variable window, change the Default Value to 3 mm/s. Termination Condition Enable (check) Value 1.
Modify the Example Test • Load becomes greater than 1.00 kN (Termination Condition) • Specimen failure is detected • One of the other branches of the Parallel Branch activity (such as a limit detection branch) completes The Brake Distance control provides control-mode braking, which slows the command to help avoid overshoot. The brake value is subtracted from the Termination Condition value to determine where control-mode braking starts. In this case, the Termination Condition is 1.
Modify the Example Test Runtime effect The TWE application automatically runs the Finish section, which contains the Run Report activity, when 24 test runs are complete. Enabling and Configuring the Run Report Activity Note: The following task requires e-mail address and server properties to be properly configured. These properties are set in Preferences > Configuration > E-Mail. Check with your e-mail administrator for the correct settings.
Modify the Example Test 3. Enable (check) the Send report to e-mail control. 4. Enter e-mail parameters as desired. Runtime effect When 24 test runs are complete and the TWE application runs the Finish section, a test report is generated using the default test report template (\Default Test Report.xltx.) The test report is saved to the Report Directory (Preferences > Configuration > E-Mail). A copy of the report is sent to the e-mail address entered in the Run Report activity.
Working with MTS FlexTest Resources Topics: • • • • • • • • Resource Basics................................................................................................................................96 Connecting to a Controller.................................................................................................................96 Creating a Desktop Shortcut That Includes a Controller...................................................................98 Station Configurations.................
Working with MTS FlexTest Resources Resource Basics With the TWE application, you create test designs which cause resources (such as valve drivers, control modes, sensors, digital inputs, and so on) to apply desired forces to your test specimen. For example, suppose you design a test to apply a tensile force to your specimen and receive a digital pulse when the specimen fails.
Working with MTS FlexTest Resources Note: When you create tests while the TWE application is connected to a controller, it is referred to as “online” test design. You can also perform “offline” test design (see Offline Test Design (p. 102).) Resources Tab Description of Resources Tab Number Item Description 1 Controller and station identification When TWE is connected to a controller, the window title shows the controller and station configuration associated with the current test.
Working with MTS FlexTest Resources Creating a Desktop Shortcut That Includes a Controller Quick access: Tools menu > Create Desktop Shortcut Note: This procedure only applies to MTS FlexTest controllers. There are two types of desktop icons. One opens just the MTS TestSuite application, and the other will open the controller and then open the MTS TestSuite application.
Working with MTS FlexTest Resources Station Configuration File and Station Resources Controller Resources A station configuration may include only a portion of the resources available to the controller. The complete inventory of resources available to your controller is defined by the hardware interface file (or .hwi file) installed with your controller software. The .
Working with MTS FlexTest Resources resource map saved in the test definition is an inventory of resources the TWE application expects to find the next time it connects to a station. You must either automatically or manually map the test resources to controller resources before you can load and run the test procedure on that station. Resources are stored with the test definition and validated against the available controller resources the next time the application connects to a station.
Working with MTS FlexTest Resources Mapping Resources Example If possible, import resources from an existing test Before you begin manually entering test resource names, check to see if any other tests exist that have been designed with the controller you intend to connect to. If there are, import the resources from that test first to save time. (Define tab > Resources subtab > Import Resources > Import resources from another test.
Working with MTS FlexTest Resources Offline Test Design You can design tests offline, that is, when disconnected from the controller, and then map resources when you connect to the controller. When you do this, you do not have to start the Station Manager application and open a station configuration before starting the TWE application. The general flow for designing tests offline is as follows: • Start the TWE application (without starting the Station Manager application or connecting to a station).
Working with MTS FlexTest Resources Resources That Allow Dimension Changes Float signals with fixed dimensions A float signal is a type of test resource that typically has a fixed dimension assignment. An example of a float signal is “Ch 1 Displacement” with a dimension of “Length”. Float signals that can change dimensions Some float signals can change their dimension during the test: • Channel Command • Channel Comp.
Considerations for Servohydraulic Systems Topics: • • Understand Software Concepts.......................................................................................................106 Using MTS TestSuite with Controller Software................................................................................
Considerations for Servohydraulic Systems Understand Software Concepts Designing tests for servohydraulic systems involves using MTS FlexTest controller software and MTS TestSuite software together to meet your test objectives. MTS controller software consists of MTS Series 793 applications, including the Station Builder and Station Manager applications. These applications allow you to map hardware to station configurations and maintain real-time control of the test station.
Considerations for Servohydraulic Systems Specimen installation and other station activities When you create tests with the TWE application, you typically minimize the Station Manager application to simplify your PC desktop.
Considerations for Servohydraulic Systems Number Item 5 Manual Command control 6 Span Setpoint control 7 Remote Setpoint Adjust control Other station activities you may perform with Station Manager You may perform some station activities pre-test or between tests, such as: • Check shunt calibration levels • Adjust tuning values You can only perform these activities with the Station Manager application.
Considerations for Servohydraulic Systems MTS TestSuite software includes the TWE application, which allows you to design and run tests, and the TWX application, which allows you to run tests only. MTS FlexTest Controller Software and MTS TestSuite Software TWE Startup 1. Click the Windows Start button on your desktop and select Programs > MTS 793 Software > Station Manager. 2. In the Open Station window, select a configuration file and then click Open. 3. Minimize the Station Manager application.
Considerations for Servohydraulic Systems For information that pertains to the Model 494.05 Handset, see the MTS Model 494.05 Handset manual (PN 100-194-691). For information that pertains to test frame controls, refer to the documentation that accompanies the equipment. Set Station Detector Limits About station and test detector limits You set detector limits with both the Station Manager and TWE applications. You set station limits with the Station Manager application.
Considerations for Servohydraulic Systems Station Manager Limits Summary Tab Each channel input includes a Limits tab where you can define detector limits and actions. Station Manager Inputs Limits Tab Station Controls access You can use the Detectors window to monitor and define detector limits and actions. Click the Detectors button on the Station Manager window’s Station Controls panel toolbar to view the Detectors window.
Considerations for Servohydraulic Systems Station Manager Detectors Window Reset Detectors To reset a detector that has tripped: 1. Determine the event that caused the detector to trip and fix the problem. 2. Click Reset on the Station Controls panel in the Station Manager application, or click Reset on the Station panel of the TestSuite TW application.
Considerations for Servohydraulic Systems Access Station Controls panel toolbar > Manual Command button. Station Manager Manual Command Window Description of Station Manager Manual Command Window Item Description Channel Selects the control channel. Click the Channel button to toggle between individual channels and groups. Control Mode Selects a control mode. Select Enable Manual Command to make a selected Control Mode for the Active Mode. Active Mode Shows the current control mode.
Considerations for Servohydraulic Systems Item Description Park Moves enabled channels to a predefined Park level prior to hydraulic shutdown. Ride Moves enabled channels to a predefined Ride level prior to test startup. Manually Position the Actuator This procedure is used for installing and removing specimens. 1. 2. 3. 4. If desired, set up the Scope window to view the actuator’s displacement and force signals.
Considerations for Servohydraulic Systems Note: If necessary, click the Manual Cmd text to open a window where you can change the slider-bar range. Applying Offsets to the Input Signal (optional) About offsets Offsets can be applied using the Station Manager application or in the test. Choose the method that works best for your test. The following procedures describe how to apply offsets using the Station Manager application.
Considerations for Servohydraulic Systems Note: If necessary, click the Manual Offset text to open a window where you can change the slider-bar range. Warning: Immediate and unexpected actuator response is possible when you apply a manual offset to your system. If the Current Value shown on the Offset/Zero tab is zero, a manual offset will cause the actuator to move to the new zero position. Sudden actuator movement can cause injury and equipment damage.
TW Elite for TestWorks 4 Users Topics: • • • • • • About this Chapter...........................................................................................................................118 Basic Concepts................................................................................................................................118 Terminology Differences..................................................................................................................119 Functional Differences......
TW Elite for TestWorks 4 Users About this Chapter If you are familiar with MTS TestWorks 4 software, this section will help you make the transition to TW Elite. It provides a side-by-side comparison of the concepts, terminology, and functionality of both applications. Basic Concepts TestWorks 4 and MTS TestSuite TW Basic Concepts TestWorks 4 MTS TestSuite TW You choose a method to test a collection of physical specimens referred to as a sample.
TW Elite for TestWorks 4 Users Terminology Differences TestWorks 4 and MTS TestSuite Terminology Differences TestWorks 4 Term Definition MTS Definition TestSuite TW Term Specimen (1) The physical part being tested. Specimen The physical part being tested. Specimen (2) A single instance of running a Test Run method. The data and results of a specimen are stored inside a sample file, along with other specimens that have been tested under this sample name.
TW Elite for TestWorks 4 Users TestWorks 4 Term Definition MTS Definition TestSuite TW Term controller and the container of collected data. that holds data is an array variable; and a combination of feedback selection, control algorithm, and tuning parameters is the control mode. A software channel is based on calculations from hardware channels or other software channels. Channel resources yield a stream of data at the system rate that always has a current value and can be measured.
TW Elite for TestWorks 4 Users TestWorks 4 Term Definition MTS Definition TestSuite TW Term Hold A test segment that moves the Dwell + DAQ crosshead in order to maintain + Detection a specified channel value. It may be set to stop at a specific point, or it may be set to run until a break is detected or a limit condition has been reached. A Data Collection task running in parallel with the Hold can be configured to acquire data.
TW Elite for TestWorks 4 Users Functional Differences TestWorks 4 and MTS TestSuite TW Behavioral Differences Function TestWorks 4 Behavior Performing File Operations You perform file operations for samples from You perform all file operations for the File menu. You perform file operations tests and templates from the File for methods from the Methods menu. menu.
TW Elite for TestWorks 4 Users Function TestWorks 4 Behavior MTS TestSuite TW Behavior references to other files (e.g., Report Templates). Working with Hardware Resources Working with Calculated Resources Acquiring Data When you add a hardware channel to a When you add a hardware resource method, the hardware channel automatically to a test, you must also do the includes a variable that is configured to following to acquire data: acquire data. • Add an array variable.
TW Elite for TestWorks 4 Users Function TestWorks 4 Behavior MTS TestSuite TW Behavior “***”. After a test run is complete, variable meters show the last value attained during the test run. Latched variable values are followed by a superscripted asterisk (e.g., “10*”). Calculated Channels with MTS FlexTest Controllers Calculations for calculated signals are Calculations for calculated signals performed in the application (TestWorks 4). must be performed in the controller (MTS FlexTest).
TW Elite for TestWorks 4 Users Function TestWorks 4 Behavior MTS TestSuite TW Behavior not been started was hollow, and it was filled status. Instead, the names of test runs in when the test run completed. that have not been run are italicized. When the test run completes, the text becomes normal (non-italics). Outer Loop Control Modes If you use advanced rate control in TW4, the outer-loop control mode is not maintained when transitioning from a GoTo activity to another activity in a test.
TW Elite for TestWorks 4 Users When converted to TW, TestWorks 4 methods that include either of these features require modification to perform as originally designed. To do this, you must modify the associated station configuration file (.cfg) with MTS FlexTest software. Important: Carefully consider desired system behavior and the effects of the changes you wish to make before modifying the station configuration.
Index Index .
Index manual mapping 100 manual offset feedback 115 manually apply input signal offsets 115 manually create resources 102 manually position actuator 114 manuals 11 mapping automatic 100 manual 100 mapping resources 47, 96 Message 87 MPE detector limits 110 MTS software controller 106 TestSuite 106 simultaneous activities 63 specimen installation 110, 114 Station Builder application and hwi files 99 station configuration file 108 station connect 96 station controls access 111 station detector settings 110 S
Index W Wait for Operator Action activity 64 129
Index 130
MTS Systems Corporation 14000 Technology Drive Eden Prairie, Minnesota 55344-2290 USA Toll Free Phone: 800-328-2255 (within U.S. or Canada) Phone:952-937-4000 (outside the U.S. or Canada) Fax 952-937-4515 E-mail: info@mts.com Internet: www.mts.
