Multipurpose Elite Test Design Guide For MTS Acumen™ Electrodynamic Test Systems 100-268-627 B be certain.
© 2013 MTS Systems Corporation. All rights reserved. Trademark Information MTS, FlexTest, RPC, and TestWare are registered trademarks and MTS Acumen, MTS TestSuite, Station Builder, and Station Manager are trademarks of MTS Systems Corporation within the United States. These trademarks may be protected in other countries. All other trademarks are the property of their respective owners.Microsoft and Windows NT are registered trademarks of Microsoft Corporation.
Contents 1.0 Technical Support 7 1.1.0 How to Get Technical Support........................................................................................................7 1.2.0 Before You Contact MTS................................................................................................................7 1.3.0 If You Contact MTS by Phone........................................................................................................9 1.4.0 Problem Submittal Form in MTS Manuals.............
5.0 Creating Tests 39 5.1.0 Installing MTS TestSuite Simulation Software.............................................................................40 5.2.0 Creating Ramp and Cycle Test......................................................................................................40 5.2.1.0 Ramp and Cycle Test Design Overview.........................................................................40 5.2.2.0 Opening a Station Configuration and Starting the MPE Application............................
7.0 MTS Controller Software 83 7.1.0 Software Concepts.........................................................................................................................84 7.1.1.0 Key Concepts about Using MTS TestSuite and Controller Software............................84 7.2.0 Adding Station Resources.............................................................................................................85 7.2.1.0 Adding Existing Hardware Resources to a Station Configuration....................
1.0 Technical Support 1.1.0 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.
Know your site number and system number The site number contains your company number and identifies your equipment type (such as material testing or simulation). The number is typically written on a 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.
• Keyboard enhancers • Print spoolers • Messaging applications 1.3.0 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.
• 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. 1.4.
2.0 Preface 2.1.0 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.
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. Other special text conventions Important: Important notices provide information about your system that is essential to its proper function. While not safety-related, if the important information is ignored, test results may not be reliable, or your system may not operate properly.
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.
3.0 Designing a Test Topics: • • Introduction............................................................................................................................................16 Test Design WorkFlow...........................................................................................................................
3.0 Designing a Test 3.1.0 Introduction About this chapter This chapter contains information about the MPE and Station Manager software, basic test design principles, how tests are executed, and how information about test results is made available. If you already feel comfortable with these test design principles and are ready to begin creating a basic ramp and cycle test, see Creating Ramp and Cycle Test on page 40.
3.0 Designing a Test Step Activity Description 2 Start the MPE application and select a new test With your station open, use the MPE application. 3 Add test activities and define their To create a test file, drag test activity icons onto the properties Procedure tab. 4 Add monitor display devices and Add monitor display devices, such as Signal Scope, define their properties so you can monitor test progress.
3.0 Designing a Test Important: You must leave the Station Manager application open, but you can minimize it so it does not appear on your screen. MTS TestSuite MPX is the intended operator interface. Do not make configuration changes in the Station Manager application without training from MTS. 5. Open MPE or MPX by double-clicking its icon on your desktop; or from the Start menu, go to All Programs > MTS TestSuite. The MP main window opens. You can now open a test.
3.0 Designing a Test Note: MTS TestSuite projects are independent of the underlying controller, and are not related to MTS controller projects or the MTS Project Manager application. 3.2.2.0 Creating Tests Overview From the File menu, you can create new tests as follows: Creating New Tests File Menu Option Description New Test Creates a new test that does not contain test data and has an undefined workflow. When the workflow is defined, it can be extracted by saving the test as a template.
3.0 Designing a Test Cycle Activities Properties Error indicators assist definition Red error icons appear next to activity property fields where information is missing or incorrect.
3.0 Designing a Test Error Indicators 3.2.3.1.0 Deleting and Disabling Test Activities If you want to remove a test activity from the test procedure, you can either delete the test activity or disable the test activity. When you delete the activity, the activity is permanently removed from the test procedure. This action cannot be undone, and you will have to either recreate the test activity or revert to a previously-saved version of the test that contains the activity.
3.0 Designing a Test 3.2.3.2.0 Variables Overview Typically, 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. This allows you to change the variable value without selecting the activity.
3.0 Designing a Test • The MPE application uses variables to simplify test creation and modification, allow operator interaction in the test flow, and facilitate monitor display. • The MTS TestSuite Reporter Add-In for Microsoft Excel uses variables to capture test data for test reports. • The various MTS Analyzer applications use variables to create “what if” scenarios using specimen variables and data from test runs.
3.0 Designing a Test 3.2.4.0 Working with Test-Run Display Devices When you start the test, you can see real-time test information on the Test-Run Display panel. Add monitor display devices To add monitor display devices to your test, click the Test-Run Display tab and drag monitor display devices from the toolbox to the work area. When you do this, error icons on the device icon and Error list guide you to define required properties.
3.0 Designing a Test Caution: Improperly or carelessly modifying the settings in the Station Manager application can result in unexpected actuator movement. Unexpected actuator movement can result in injury to personnel or damage to the equipment and the specimen. Only expert-level users attempt to perform activities using the Station Manager application. Every major function that can be performed in the Station Manager application can be also performed in MPE.
3.0 Designing a Test If you inadvertently run a modified test and have to undo the changes you made to the test before you ran it (and the application automatically saved it), you must do so manually. 3.2.6.0 Test Design Considerations 3.2.6.1.0 Consider Your Station Setup When you are designing or running a custom test, it is important to consider the following components of your station setup or you may receive unintended test results.
3.0 Designing a Test Offsets If an offset is applied to the station, the test will respect that offset and run assuming the offset position is “zero”. For example, if the station has an offset of 2 mm axial displacement, and the test commands the actuator to ramp to zero, the actuator will ramp to 2 mm axial displacement. Caution: If you run a test that assumes an offset that does not exist on the station, you may receive unintended test results, which may result in unexpected actuator movement.
3.0 Designing a Test Recommended: It is important to understand how detector actions affect system operation. In most cases, MTS recommends using the C-Stop Interlock action for detectors during system setup and test design for MTS Acumen systems. Resetting a C-Stop Interlock action Once a C-Stop Interlock action is triggered, you must click Interlock Reset before you can switch out of stable displacement, use Manual Command controls, or resume or run a test. 3.2.6.3.
3.0 Designing a Test 6. The system will launch another instance of Microsoft Excel and show the newly generated report file.
4.0 Working with Resources Topics: • • • • • Resources..............................................................................................................................................32 Starting MPE and Connecting to a Controller........................................................................................32 Resource Mapping.................................................................................................................................34 Offline Test Design...........
4.0 Working with Resources 4.1.0 Resources With the MPE application, you create test designs that cause controller resources to apply desired forces to your test specimen. Controller resources include control channels, control modes, sensors, digital inputs, and so on. For example, suppose you design a test to apply a tensile force to your specimen and receive a digital pulse when the specimen fails.
4.0 Working with Resources Display of MPE Application Resources Number Function Description 1 Controller and Station When MPE is connected to a station, the window title Identification shows the controller and station configuration associated with the current test. In this example, the controller name is “Acumen Simulation - MTS FlexTest 40”, and the station configuration name is “FT40_station1_Simulation.cfg”. 2 Resources Tab Access On Explorer, click Resources.
4.0 Working with Resources 4.3.0 Resource Mapping A resource map aligns test resources with controller resources. When you create a test while MPE is connected to a controller and save the test, MPE saves the resource map with the test definition. The resource map saved in the test definition is an inventory of resources the MPE application expects to find the next time it connects to a controller.
4.0 Working with Resources Resource Validation Errors Resource validation errors appear as red icons on the Resources tab. Validation errors occur when you connect to a controller and MPE cannot locate controller resources that match test resource requirements in the test definition. In this example, the names of the test resource control modes are “Disp 1” and “Load 1”.
4.0 Working with Resources Creating resources manually If no existing tests are available to import resources from, you must add them to your test manually. (Resources tab > Add Resource > resource type). When you add a resource, you must enter a Display Name, an Internal Name (spaces not permitted), and where applicable, a Dimension.
4.0 Working with Resources 4.5.0 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 “Axial Displacement” with a dimension of “Length”. Float signals with dynamic dimensions Some float signals can change their dimension during the test: • Channel Command • Channel Comp.
5.0 Creating Tests Topics: • • Installing MTS TestSuite Simulation Software.......................................................................................40 Creating Ramp and Cycle Test..............................................................................................................
5.0 Creating Tests 5.1.0 Installing MTS TestSuite Simulation Software Installation of the simulation software consists of launching two separate self-extracting executables, one for the MTS TestSuite application and one for the MTS Series 793 Simulation software. These files are available on CD-ROMs or download sites.
5.0 Creating Tests • Acquires time data while cycling. • Ramps back to zero. • Shows test signals on a Signal Scope monitor as the test runs.
5.0 Creating Tests MPE features used to create this test • Ramp activity • Cycle activity • Data Acquisition activity • Input Parameters activity • Parallel Path activity • Relative End Levels property • Variable properties • Signal Scope monitor display 5.2.2.0 Opening a Station Configuration and Starting the MPE Application Use this task to open a station configuration file (or station) with the Station Manager application, and then start the MPE application.
5.0 Creating Tests Note: If you are prompted to select a controller, select the “Acumen Simulation - MTS FlexTest 40” controller. 2. In the Open Station window, select the “FT40_station1_Simulation.cfg” configuration file and then click Open. Note: The controller and configuration file you selected in the previous two steps are used for creating and running tests using the simulation and this test design guide.
5.0 Creating Tests 2. Drag and drop the Ramp activity on the “Drop Activities Here” text in the work area. Adding a Ramp Activity 3. Define Ramp activity properties: a. Enter the following values as necessary: Ramp Activity Properties Property Value Display Name Ramp to Mean Timing Type Time Time 2 sec Ramp Shape Ramp Compensator No Compensator Channel List Axial Control Mode Displacement Absolute End Level 4 mm 5.2.5.
5.0 Creating Tests 1. Drag a Cycle activity below the Ramp activity. Adding a Cycle Activity 2. Define Cycle activity properties: a. Ensure that the Cycle activity is selected. b. Enter the following values as necessary: Cycle Activity Properties Property Value Display Name Cycle at Mean Timing Type Frequency Frequency 1 Hz Wave Shape True Sine Number of Cycles 5 Advanced...
5.0 Creating Tests Property Value Relative End Level 1 2 mm Relative End Level 2 -2 mm Phase Lag N/A 5.2.6.0 Adding a Second Ramp Activity Use this task to add a second Ramp activity to the procedure. During the test, the second Ramp activity ramps command to zero. 1. On the Procedure workspace, right-click the existing Ramp activity and select Copy. Then, right-click below the Cycle activity and select Paste. Copying and Pasting Existing Ramp Activity 2. Define Ramp activity properties: a.
5.0 Creating Tests Property Value Timing Type Time Time 2 sec Ramp Shape Ramp Compensator No Compensator Channel List Axial Control Mode Displacement Absolute End Level 0 mm 5.2.7.0 Adding a Signal Scope Monitor In this task, you add a Signal Scope to the test. The Signal Scope is graphical, real-time display of your test data. When running the test, the Signal Scope simulates a conventional oscilloscope.
5.0 Creating Tests Note: By default, Time is the parameter used for the X axis, which is desired for the sample test. 7. In the Properties panel, expand the Y Axis panel. 8. Select the Maximum check box. 9. Set the Maximum value to 12 mm. This accommodates the amplitude of the end-level values of the Cycle at Mean activity. Setting the Y Axis Maximum Signal Scope Monitor with 12 mm Y Axis Maximum 10.
5.0 Creating Tests 5.2.8.0 Checking the Test Procedure In this task, you run the test to check its design thus far. Note: The test design process is iterative; therefore, it is a recommended best practice to build your test procedure incrementally. 1. Ensure that the station has power. Access the Hydraulic Power Unit (HPU) by clicking the arrow in the lower right corner of the Power pane. Set the HPU to high. If the interlock indicator appears red on the System panel, click Reset.
5.0 Creating Tests Test Run on Signal Scope 5.2.9.0 Adding Variables In this task, you replace the currently fixed end-level values of the Cycle activity with variable values. After you define an Input Parameters activity, the operator can enter variable values that define the cycle end levels before running the test. 1. Click the Procedure tab. 2. Click the Cycle activity in the Toolbox panel. 3. Observe the Relative End Level 1 property.
5.0 Creating Tests Relative End Level 1 Ready for Variable 5. Click the Relative End Level 1 entry box and select . Note: If a preexisting variable was available for this property, it would appear in the list with . 6. Observe the New Numeric Variable window, and enter the following as necessary: New Numeric Variable Window Properties Property Value Notes Category Variables Identifier EndLevel1 This is the internal name of the variable. It cannot contain spaces.
5.0 Creating Tests Property Value Notes You provide the operator the capability to change the variable value while the test is running by enabling the Editable During Test property, and adding the Input Parameters activity. Calculation Disabled Availability During Test Format Type Fixed Digit Type Decimal Digits 3 Use Range Disabled This allows the variable value to change during the test (when the test is locked). 7. Click OK. 8.
5.0 Creating Tests Test Procedure with New Input Variables Activity 3. In the Properties panel, enter the following as necessary: Input Variables Activity Properties Property Value Display Name Enter Relative Cycle End Levels Message Enter End Level 1 and End Level 2 values for the Cycle activity, then click OK. Variable List Note: Click the plus sign and use the Variable Selection window to add variables. End Level 1, End Level 2 Rules None Add Cancel Button Disabled 5.2.11.
5.0 Creating Tests 1. Add a Parallel Paths activity to the test flow. a) Click the Procedure tab and scroll down to the Test Flow Control category in the Toolbox panel. b) Drag the Parallel Paths activity icon to the Procedure workspace and drop it after the first Ramp activity. Test Procedure with New Parallel Paths Activity 2. Name each path in the Parallel Paths activity. a) In the Parallel Paths container, click the path branch on the right side.
5.0 Creating Tests DAQ and Cycle Activities Added to Parallel Paths Activity 6. In the Properties panel, enter the following as necessary: Data Acquisition Activity Properties Property Value Display Name Acquire Time Data Trigger List Note: Click the Trigger List plus sign and use the Data Acquisition Trigger Properties window to set the value.
5.0 Creating Tests Property Buffer Size Value Note: Click the Advanced button to set the buffer size. 100 count 5.2.12.0 Running the Test Procedure In this task, run the completed test procedure. 1. Ensure that the station has power by setting the HPU to high. If an interlock indicator is lit on the Power panel, click Reset. Next, click the Low and then High buttons on the HSM. 2. Click the New Test Run icon in the tool bar. 3.
5.0 Creating Tests Now that you have created and run a basic test, you can open one of the more complex test designs that came with your MTS Acumen system, such as the MTS Acumen Tension test. To open this test, click the Open Test icon and select MTS Acumen Tension. When the test is opened, click Procedure in the Explorer tab to examine the test procedure.
6.0 Creating Advanced Tests Topics: • • Introduction............................................................................................................................................60 Working with Profiles.............................................................................................................................
6.0 Creating Advanced Tests 6.1.0 Introduction About this chapter This chapter contains step-by-step instructions for creating advanced tests with the MPE application. Creating advanced tests may require using the Station Manager application. Important: Only expert users that are familiar with the specific MTS Acumen implementation of the Station Manager application with MTS TestSuite MP should attempt to perform any of the test(s) contained in this chapter.
6.0 Creating Advanced Tests • Report Template • External File The application provides default base directory settings that can be viewed or modified from the Preferences > Configuration > Settings > Project tab. References to the base directories are shown in the application as , , , and . References to base directories are treated as relative file paths.
6.
6.0 Creating Advanced Tests Profile Controls 6.2.3.0 Creating a Profile This task creates a profile. A profile is a document that defines a custom waveform using special formatting and syntax. The purpose of this task is to create a profile for the sample test, which runs in simulation. You use the Profile activity to reference the information in this sample profile when you set up and run the test.
6.0 Creating Advanced Tests Note: For the next step, you can copy the sample profile text from the PDF of this document and paste it into a Notepad document rather than entering the text manually. Be sure to enter the text exactly as shown. Since spaces within the file may result in errors, align the columns as shown by replacing the spaces with tab characters after pasting the text into a Notepad document. 2.
6.0 Creating Advanced Tests Note: The controller and configuration file you selected in the previous two steps are used for creating and running tests using the simulation and this test design guide. When you use other stations connected to actual systems, you may need to select other controllers or configuration files tailored to the station that you are working with. 3. 4. 5. 6. 7. 8. On the toolbar, select an access level of Configuration. Enter the password for the Configuration access level.
6.0 Creating Advanced Tests 6.2.5.0 Starting the MPE Application and Creating a New Test Shell This task creates a new empty test shell and opens the Procedure workspace. When you start the MPE application, it automatically connects to your station. Note: The MPE application typically offers more than one method to select existing or create new test files. You can click toolbar icons, make menu selections, or use the right-click menu. 1. 2. 3. 4.
6.0 Creating Advanced Tests Property Value Frequency Multiplier 100% Effect/Explanation Compensator No Compensator Arbitrary end level control is available for the Profile activity. For more information about ALC see Using ALC with the Profile Activity on page 72. Channels Ch 1 and Ch 2 Channels 1 and 2 are shown. Channel 1 has a control mode of Displacement, a Level Reference of 0 mm, and a Level Multiplier of 100%. Channel 2 is not used.
6.0 Creating Advanced Tests Property Value Effect/Explanation column is blank until you create a counter. Pass Counter Pass Counter To make a variable to support a counter: • Click the list icon below “Variable”. • Select . • In the New Numeric Variable window, observe the default values for the new “Pass Counter” variable, and then click OK. • Observe the Pass Counter counter below the Variable column. The Pass Counter increments each time the sample profile plays out.
6.0 Creating Advanced Tests 12. Select the Minimum check box, and set the value to 0 sec. 13. Select the Maximum check box, and set the value to 20 sec. 6.2.8.0 Adding a Monitor Display to Track Profile Passes This task adds a Variable Meter to the test. During the test, the Variable Meter increments each time the profile plays out. The Variable Meter uses the variable you created in Adding a Profile Activity on page 66 to track the “Pass Counter” keyword in the profile. 1. Click the Test-Run Display tab.
6.0 Creating Advanced Tests Digital IO Meter uses the corresponding “Turn on light” and “Turn off light” actions you created in Creating Controller Resource Actions that Map to the Profile on page 64. The keywords are placed in the profile so that the Digital IO Indicator lights only while the square wave portion of the custom waveform plays out. Using this concept, you can cause the Digital IO Indicator to light during the test as desired. 1. Click the Test-Run Display tab. 2.
6.0 Creating Advanced Tests Specimen Selection Properties 5. 6. 7. 8. Property Value Name Specimen-1 Geometry Generic Domain Generic Click OK. Observe the Setup Variables window, and click OK. To start the test, click the Run button (green arrow) on the Test control panel. Observe the test as the profile plays out on the display monitor. • On the Signal Scope, the trace shows displacement command playing out a composite waveform of sine, square, and ramp wave shapes.
6.0 Creating Advanced Tests 6.2.11.0 Considerations for Profile Design You can create a profile using one of the following tools: • A text editor • A spreadsheet application When creating profiles, be aware of: • The selected resources The Station Manager application and the MPE application must be opened with a configuration file that is compatible with the profile file.
6.0 Creating Advanced Tests ALC Compensator Settings Item Description Browse to and Use the Browse button to browse to and select Select the Matrix File the Matrix file. Matrix Source Specifies whether you want the application to use the matrix parameters entered in the Matrix window or the parameters currently loaded in the controller real-time.
6.0 Creating Advanced Tests Item Description Note: This option is available only if you have specified a single-channel Profile or Cycle activity. Channels Selects the channel to which the compensation ranges apply. Compensation ranges must be entered for each channel used by the Profile or Cycle activity. Upper Range Specifies the upper range value and associated units of compensation matrix for the selected channel.
6.0 Creating Advanced Tests FileType= Block-Arbitrary Date= Fri May 12 07:55:44 2010 Description= this is a sample test profile ActionList= , , counter1, “counter 2” Channels= 1 Header Data Syntax 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.
6.0 Creating Advanced Tests ActionList= , , “Counter 1”, Counter2 Channels= 1 Channel(1)= Channel 1 Frequency= 1 Hz Count= 1 segments Shape= Sine Level2= 0.0 mm Level1 Action mm 5.0000 -5.0000 “Counter 1” 8.0000 -8.0000 2.000 Counter2 -2.000 5.0000 -5.0000 1.0000 -1.0000 6.2.11.6.0 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.
6.0 Creating Advanced Tests Keyword Comments Suggestions Dimension= Placed in the file by the Profile Editor to determine the dimension of a given unit. This is an optional but recommended entry. 6.2.11.7.0 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.
6.0 Creating Advanced Tests Keyword Range Comments Level1 Undetermined This entry is required. Level2 Undetermined This entry is required for more than one segment. 0–360° This optional entry specifies the phase lag for phase profiles. The default is 0. 2 Phase Lag Rate type A rate type determines the time base of the waveform.
6.0 Creating Advanced Tests 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.
6.0 Creating Advanced Tests Note: The MPE 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. • Use the Profile activity to also select the control mode of a profile channel.
6.0 Creating Advanced Tests Using normalized dimensions to define control modes You can use any of these normalized dimensions to define a control mode in a station configuration. If you do this, and then attempt to play out a profile that also uses a normalized dimension, MPE will treat it as a standard dimension when you define a Profile activity.
7.0 MTS Controller Software Topics: • • Software Concepts.................................................................................................................................84 Adding Station Resources.....................................................................................................................
7.0 MTS Controller Software 7.1.0 Software Concepts Designing tests involves using MTS 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.
7.0 MTS Controller Software 7.2.0 Adding Station Resources Controller hardware resources are the physical components (such as conditioner cards) installed in the controller chassis. A test station is a collection of the hardware resources required to run a particular test. This information is defined in a station configuration file. Station configuration files are created using the Station Builder application.
7.0 MTS Controller Software 7.2.2.0 Adding New Hardware to a Controller If you need to add physical hardware components to your controller chassis, contact MTS.
8.0 Appendix A: MPE for MPT Users Topics: • • • • • • • • • • • About This Appendix..............................................................................................................................88 Major Concepts......................................................................................................................................88 Control Panel and Options.....................................................................................................................
8.0 Appendix A: MPE for MPT Users 8.1.0 About This Appendix If you are familiar with MTS MultiPurpose TestWare (MPT) software, this appendix will help you make the transition to the MTS TestSuite Multipurpose Elite (MPE) application. It provides a side-by-side comparison of the concepts, terminology, and functionality of both applications. 8.2.0 Major Concepts MPT Process or Term MPE Activity or Term Comments Test Procedure (*.
8.0 Appendix A: MPE for MPT Users MPT Process or Term MPE Activity or Term Comments acquired data, routing results to runtime displays and reports, and in-test decision-making. MPE supports the following actions, and MPT does not support them: • • • Array variables Putting acquired data into variables Activities that can make decisions based on variables The calculation engines are very different (see next item, Calculations).
8.0 Appendix A: MPE for MPT Users MPT Process or Term MPE Activity or Term Comments No equivalent Resources In MPT, processes directly access the station resources (channels, signals, actions, and so on). This is conceptually simple; however, it leads to problems when trying to move a test from one station to another. MPE introduces the concept of a Test Resource. All the other parts of the Test Definition reference the Test Resource, which is defined as part of the test.
8.0 Appendix A: MPE for MPT Users MPT Process or Term MPE Activity or Term Comments No equivalent Specimen, MPT does not have an equivalent to the MPE concept of a Specimen Specimen. Geometry, Domains In MPE, a Specimen is information about the physical thing being tested. It indicates the geometry type and various physical characteristics of the article under test. Specimens are useful when you need one test design to work for specimens of different geometry types (for example, round vs. rectangle vs.
8.0 Appendix A: MPE for MPT Users Feature Comments MPE does not have an analogous capability. It can be simulated with some work using the Log Message activity. Option on how to support Hold Not implemented in MPE. Hold is always allowed. Option on whether Run After Stop is allowed Not implemented in MPE. Resume from Stop is always allowed. Option to NOT clear Implemented in MPT, but not in MPE. channel counters on RESET.
8.0 Appendix A: MPE for MPT Users Feature Comments Reset the current test MPT supports this feature, and MPE does not support it. This requires you to create run and start the test a new test run and delete the old one. over again. Monitor workflow progress. In MPT, it is convenient to watch indicators within the workflow editor to see which processes are active at any one time. This is helpful to test designers debugging their tests.
8.0 Appendix A: MPE for MPT Users MPT Process or Term MPE Activity or Comments Term Dwell Command Dwell Functionally equivalent. The MPE activity has the following enhancements: • • Profile Command, Profile Profile Command with ALC Functionally equivalent. • • • External Command External Command More flexible termination criteria (MPT only has duration). “Dwell at Current Value” is the only MPT implementation.
8.0 Appendix A: MPE for MPT Users MPT Process or Term MPE Activity or Comments Term MPE supports PRO SEQUENCE but does not support the old RDSURF files. Segment, Cyclic, Dwell, Sweep Ramp, Cyclic, Dwell, Sweep MPE does not support assigning a control mode selection to a variable. MPT allows a single process to be used for different control modes (selected by a variable). This requires the activity to retain mode-specific information for each control mode (not just the selected one).
8.0 Appendix A: MPE for MPT Users MPT Process or Term MPE Activity or Comments Term Peak/Valley Acquisition DAQ The MPE Data Acquisition activity covers this capability. Additionally, it supports: • • • • • Timed Acquisition DAQ The MPE Data Acquisition activity covers this capability.
8.0 Appendix A: MPE for MPT Users MPT Process or Term MPE Activity or Comments Term There is a lot of overlap, but each can do things that the other cannot do easily. MPE cannot easily perform the following capabilities, but has the ability to use an arbitrary calculation for cycle filtering to make up for these limitations. • • Have the cycle selection algorithm work on a relative cycle count. Specify that multiple cycles should be stored at each desired interval.
8.0 Appendix A: MPE for MPT Users MPT Process or Term MPE Activity or Comments Term • • Fatigue Monitoring Not available MPE and MPT both have a Trend Limits Table for setup, runtime, and results. MPE can also select a subset of signals and statistics of interest. MPT has a Numerical Data table for runtime and results. Similarly, MPE has a Cycle Statistics table that can show Trend data at runtime and results tables that show global maximum/minimums and statistics for each pass.
8.0 Appendix A: MPE for MPT Users MPT Process or Term MPE Activity or Term Comments To replicate the MPT single process in MP, the designer must create one runtime control, three activities and tie them together with one variable. Peak/Valley Change Peak-Valley Detector Change Detector These are equivalent, except for the trigger continuously mode. Program Event State Change Detection These are equivalent, except for the trigger continuously mode.
8.0 Appendix A: MPE for MPT Users 8.9.0 Performance Feature Comments Runtime Latencies MTS TestSuite inter-activity latencies are slower than MPT inter-process latencies. 8.10.0 General MPT Process or Term MPE Activity or Term Comments All processes All activities Both products support disabling portions of the workflow.
8.0 Appendix A: MPE for MPT Users 8.11.0 Other MPT Process or MPE Activity or Term Term Program Control Comments Set Control Event These functions are equivalent, except for the following features: • MPT has the ability to log the counters (channel counters, sequence counters, and profile counters) along with the message that gets logged. • In MPT, Pause State is a modified Hold state that is initiated by the application, and from which the application can automatically resume.
8.0 Appendix A: MPE for MPT Users MPT Process or MPE Activity or Term Term Comments • Start Application Run External Application The MPE activity supports data entry rules and enhanced validation that the MPT process does not support. Functionally equivalent with the following differences: • MPT has more placeholders available when specifying the location of the application to run or the parameters passed to the application.
Index A Absolute End Level property ramp activity 44, 47 action syntax examples 75 activities assign variables 23 calculate variables 23 custom message window 23 cycle 42, 45, 50 data acquisition 42, 54 error indicators 20 input parameter 50 input parameters 23, 42 input variables 52 launch external application 23 parallel path 42, 54 profile 60, 66 ramp 42, 44, 46 add a variable 23 Add Cancel Button property input parameter activity 53 add controller hardware 86 add test variables 51 add variable procedure
Cyclic command 93, 95 D data acquisition data acquisition 42 data acquisition activity add to parallel path 53 data acquisition 54 data acquisition processes 95 Data Display 102 data limit detector 98 Data Sample Rate 97 de-energize station 25 Default Value new variable property cycle activity 51 Description new variable property cycle activity 51 Digit Type new variable property cycle activity 52 digital input detector 98 digital IO indicator 69 digital output 99 Digits new variable property cycle activit
L N Label Font Size property variable meter monitor display 69 launch external application activity 23 Level Crossing Acquisition 96 limit detection 98 logging 101 Logging Counters 91 Lower Range property ALC profile activity 74 name specimen selection property 49, 71 New Test 19 New Test from Existing Test 19 New Test from File 19 New Test from Template 19 new test shell 43, 66 new variable properties availability cycle activity 52 calculation cycle activity 52 category cycle activity 51 default value c
P parallel path add data acquisition activity 53 parallel path activity add cycle activity 53 parallel path test flow control activity 54 Parallel Paths 101 Pass Counter property profile activity 68 peak-valley change detector 99 Peak/Valley acquisition 96 performance 100 Periodic Time Event activity 99 Phase Lag property cycle activity 46 phase profiles 72 PRO SEQUENCE 95 procedures add variable 50 create new test shell 43, 66 profile activity properties 66 base directories 60 block-arbitrary 72 counter pr
properties (continued) profile action profile activity 67 ramp shape ramp activity 44, 47 relative end level cycle activity 50 relative end level 1 cycle activity 46 relative end level 2 cycle activity 46 relative end levels 42 signal digital IO indicator monitor display 70 signal list data acquisition activity 55 test action profile activity 67 time ramp activity 44 timing type cycle activity 45 ramp activity 44, 47 total passes profile activity 66 trigger list data acquisition activity 55 turn off light p
station connect 32 station configuration open file 42 Station Manager configuration 42 Event Action editor 64 test execution 24 station resources digital output 1 name property 65 digital output 1 property turn off light 65 name property turn off light 65 turn on light 65 turn on light name property 64 stop tests 25 Sweep command 94, 95 syntax action and counter 75 channel data 77 channel header 76 header data 74 profile requirements 74 system panel c-stop interlock 27 T temperature control 99 test create
Variable property profile activity 67 variable meter monitor display 69 variables add 23 edit 23 Variables Editor 22 W Wave Shape property cycle activity 45 waveform count 78 level data 79 phase lag 79 rate type 78 shape 78 special considerations 79 while loop 99 Z Zeroing Time 102 Multipurpose Elite Test Design Guide 109
Multipurpose Elite Test Design Guide
100-268-627 B