Multipurpose Elite Test Design Guide 100-229-376 F 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 37 5.1.0 Installing MTS TestSuite Simulation Software.............................................................................38 5.2.0 Creating Ramp and Cycle Test......................................................................................................38 5.2.1.0 Ramp and Cycle Test Design Overview.........................................................................38 5.2.2.0 Opening a Station Configuration and Starting the MPE Application............................
6.2.3.0 Creating a Profile............................................................................................................75 6.2.4.0 Creating Controller Resource Actions that Map to the Profile......................................76 6.2.5.0 Starting the MPE Application and Creating a New Test Shell.......................................78 6.2.6.0 Adding a Profile Activity...............................................................................................78 6.2.7.
8.5.0 Command....................................................................................................................................111 8.6.0 Data Acquisition..........................................................................................................................113 8.7.0 Event Detectors...........................................................................................................................116 8.8.0 External Control.............................................
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 38.
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 • Adjust commands settings (such as ramp and taper times). This is done using the Channel Options tool in the Station Manager application. • • Access the values of calculation parameters and variables. This is done using the Calculation Editor in the Station Manager applicationr. Set limit levels and actions for detectors. • Position the actuator to install the specimen. • Apply offsets.
3.0 Designing a Test Test execution with the MPX application Similar to the MPE application, the MPX application can be used to run tests. However, the MPX application cannot create or modify tests. In order to create or modify tests, you must use the MPE application. Considerations for automatic background saves It is important to keep in mind that when you start a test run, the application automatically saves the current state of the test.
3.0 Designing a Test Note:When control is provided by a handset, the application controls will be locked and overlaid by the handset exclusive control icon: Description of Model 494.05 Handset Item Description 1 Programmable display 2 Hydraulics indicator 3 Exclusive control 4 Interlock indicators 5 Thumbwheel (manually positions the actuator when Manual Command is enabled) 6 Manual command 7 Interlock reset/override 8 Program Run/Stop/Hold controls 9 Hydraulics off 3.2.7.
3.0 Designing a Test 3.2.8.0 Generating a Report Using the Excel Reporter Add-In Note: To generate a report using the Excel Reporter Add-In, you must have purchased a separate license for the Reporter Add-In product. It also requires the installation of Microsoft Excel software or another suitable Microsoft Excel reader. 1. 2. 3. 4. Open a report template in Excel (MTS templates are located in C:\MTS TestSuite\Report Templates). Click the MTS TestSuite Report tab in the ribbon.
4.0 Working with Resources Topics: • • • • • • • Resources..............................................................................................................................................30 Starting MPE and Connecting to a Controller........................................................................................30 Station Configurations...........................................................................................................................32 Controller Resources......
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 “MTS FlexTest 40”, and the station configuration name is “2 chan.cfg”. 2 Resources Tab Access On Explorer, click Resources.
4.0 Working with Resources 4.3.0 Station Configurations A station configuration is a discrete file that lists all or a portion of the hardware resources in your physical station. You create and modify station configurations with the MTS Series 793 controller software. MTS typically provides a station configuration when you receive your system. Station Configuration The Station Configuration file lists some or all of the hardware resources in your test system.
4.0 Working with Resources The Hardware Interface file represents all of the hardware resources available to your test system. When you connect to a station with MPE, the Controller Resources shown on the Resources tab pertain only to the connected controller. Note: You use the Station Builder application (one of the applications included with MTS Series 793 controller software) to define station configuration files by allocating some or all of the resources listed in the .hwi file. 4.5.
4.0 Working with Resources In this case, MPE is unable to automatically map the new controller resources to the test resources, and shows validation error icons. To resolve the errors, you must manually map the controller resources to the test, as shown. Resource Validation Errors Resource validation errors appear as red icons on the Resources tab.
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.7.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 “Ch 1 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.......................................................................................38 Creating Ramp and Cycle Test..............................................................................................................38 External Commands..............................................................................................................................55 External Command Considerations........................
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 MTS FlexTest 40 controller. 2. In the Open Station window, select the “2 Chan.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 Note: Some of the property values you need to enter for this sample test may already be present as default values. 1. Click on the Procedure tab, and scroll to the Ramp activity in the Toolbox list. 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.
5.0 Creating Tests 5.2.5.0 Adding a Cycle Activity Use this task to add a Cycle activity to the procedure and define its properties. During the test, the Cycle activity applies a sinusoidal command relative to the mean level. 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.
5.0 Creating Tests Property Value Compensator No Compensator Channel List Ch 1 Control Mode Displacement 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.
5.0 Creating Tests Second Ramp Activity Properties Property Value Display Name Return to Zero Timing Type Time Time 2 sec Ramp Shape Ramp Compensator No Compensator Channel List Ch 1 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 Selecting a Y Signal 6. Select Ch 1 Displacement and click OK. 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.
5.0 Creating Tests Signal Scope Monitor with 12 mm Y Axis Maximum 10. Click the Preview subtab inside the Test-Run Display tab to view an example of the Signal Scope monitor display. 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.
5.0 Creating Tests Property Value Domain Generic 5. Click OK. 6. Observe the Setup Variables window, and click OK. 7. Observe the Signal Scope. The test is not running yet, so the signal trace is flat. 8. To start the test, click the Run button (green arrow) on the Test control panel. 9. Observe the test run on the Signal Scope. The signal trace ramps to a mean level of 4 mm, performs five cycles with a true sine waveshape to relative end levels of 6 mm and 2 mm, and returns to zero.
5.0 Creating Tests Relative End Level 1 with a Non-Variable Value 4. Click the icon and observe that it toggles (changes) its appearance. The Variable icon contains empty brackets. Also, note that the property value (2 mm) has cleared. The property is now ready to be assigned to a variable. Relative End Level 1 Ready for Variable 5. Click the Relative End Level 1 entry box and select .
5.0 Creating Tests Property Value Description None Type Number Dimension Length Unit mm Default Value 2.00 Notes This sets the initial value of End Level 1 to 2 mm, which is the same value you entered on the Properties tab when you originally defined the Cycle activity. However, now the End Level 1 value changes whenever the operator changes the variable value.
5.0 Creating Tests 1. Click the Procedure tab and scroll to the Operator Entry category in the Toolbox panel. 2. Drag the Input Variables activity to the Procedure workspace and place it before the topmost Ramp activity. Test Procedure with New Input Variables Activity 3.
5.0 Creating Tests 5.2.11.0 Adding Parallel Paths and a Data Acquisition Activity Use this task to add parallel paths to the procedure. Parallel paths allow concurrent test activities, which in this task are the Cycle and Data Acquisition activities. For this exercise, you move the existing Cycle activity within the parallel path, add a Data Acquisition activity, and designate the terminal path. The terminal path determines when all other paths terminate.
5.0 Creating Tests b) In the Terminal Paths group of the Properties panel, select the Cycle check box. This causes the Data Acquisition activity to end when the Cycle activity ends. The Parallel Path container is now set up and ready to accept test activities. 4. Add the existing Cycle activity to the Parallel Path container by dragging the Cycle at Mean activity from its current position to the area labeled “Drop Activities Here” in the Cycle path. 5. Add a Data Acquisition activity.
5.0 Creating Tests Property Signal List Value Note: Click the Signal List plus sign and use the Signals Selection window to select the following signal options: Ch 1 Displacement Ch 1 Force Ch 1 Output Buffer Size 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.
5.0 Creating Tests 8. Make additional changes to the test and run as desired. 9. Turn off power to the HSM and HPU, then exit the MPE and Station Manager applications. 5.3.0 External Commands Your controller can process programming received from an external controller or function generator while maintaining all other closed-loop control functions. You can incorporate externally generated programming when creating tests with the MultiPurpose Elite application. 5.3.1.
5.0 Creating Tests MPE features used to create this test • External Command activity • External Command activity properties used: • • Ramp • Soft Stop • Change Span • Change Setpoint Signal Scope monitor display monitor with two Y axes Control software features used to create this test • Station Builder application: Calculated Inputs • Station Manager application: • Calculation Editor • Channel Options window (Command Options tab) • Setpoint and Span window 5.3.2.
5.
5.0 Creating Tests 5.3.3.0 Simulating an External Command Input in the Station Configuration This task opens a station configuration file (or station) with the Station Builder application and adds a calculated input. The purpose of this task is to simulate an external command input for the sample test, which you run in simulation.
5.0 Creating Tests 3. A parameter mismatch message window appears. Disregard and click OK. After saving your parameter changes, the mismatch is resolved the next time the Station Manager application is opened. 4. On the toolbar, select an access level of Configuration. 5. On the Tools menu, select the Calculation Editor. 6. In the left pane, click Ch 1 External Command. Note: You can copy the text in the next step from the PDF of this document and paste it in the Calculation Editor entry tab. 7.
5.0 Creating Tests Property Value Resume 3.0 s Leave the Begin/End and Setpoint/Span times at their default of 2.0 seconds. 3. On the File menu, click Save Parameters. 5.3.6.0 Showing the Station Manager Application Setpoint and Span Controls This task shows the Station Manager application Setpoint and Span window. The Setpoint control adjusts the command signal mean. The Span control adjusts the command signal’s multiplier.
5.0 Creating Tests 5.3.8.0 Adding an External Command Activity This task adds an External Command activity to the procedure and defines its properties. During the test, this activity modifies and plays out the simulated external command source. 1. In the Toolbox panel, scroll to the External Command activity. 2. Drag the External Command activity icon and drop it in the work area over the “Drop Activities Here” text. 3.
5.0 Creating Tests Property Value Effect stopping (Station Manager: Tools > Channel Options > Command Options > Ramp Times). Note: If you enable the Soft-Stop control, the command tapers to setpoint in 3 seconds (Station Manager: Tools > Channel Options > Command Options > Taper Times). Control Mode Displacement Signal Ch 1 External Command Setpoint 4.0 mm Span 50% Changes the Setpoint and Span values to 4.0 mm and 50% when the External Command activity starts.
5.0 Creating Tests 5. If necessary, click to expand the Traces panel. Then click the Signal List icon (...) next to the Y Signal property. 6. Select Ch 1 External Command and click OK. Note: By default, time is the parameter used for the X-axis, which is desired for the sample test. 7. Click to expand the Y Axis panel. 8. Select the Minimum check box, and set the value to -3 mm. 9. Select the Maximum check box, and set the value to 10 mm. 10.
5.0 Creating Tests Property Value Effect Note: The At Start/Stop property does not apply to the initial instance in which the External Command activity is started. The initial command behavior is determined by the Enable Ramp property of the External Command activity. Setpoint Enable Span Enable Enables the Setpoint and Span controls in the Station Manager application while the MPE application runs the test. 5.3.11.
5.0 Creating Tests Signal Scope Example 8. In the Setpoint and Span window, observe that Span is set to 100% and Setpoint is set to 0 mm. Setpoint and Span Window Pre-Test Observation 9. To start the test, click the Run button (green arrow) on the Program Control panel. 10. Observe the test as it plays out on the Signal Scope. The trace for displacement feedback: • Ramps from zero to setpoint (4.0 mm) in one second. • Tapers to a span setting of 50% in 2 seconds. 11.
5.0 Creating Tests Setpoint and Span Window Post-Test Observation Note: You set the properties for the initial ramp, taper to Setpoint, and Setpoint and Span values in the MPE application. When you begin the test, the command ramps to the new setpoint, and then tapers to the new span.
5.0 Creating Tests 5.3.12.0 Stop the Test Procedure and Observe the Response This task stops the test and shows signal traces on the Signal Scope. 1. To stop the test, click the Stop button (red octagon) on the Test control panel. 2. Observe the test as it plays out on the Signal Scope. The trace for displacement feedback ramps to Setpoint (4.0 mm) in 3 seconds. 3. Observe that the Station Manager Span remains at 50% and setpoint remains at 4.0 mm. Station Manager Span and Setpoint 5.3.13.
5.0 Creating Tests Setpoint and Span Window 4. Observe the Signal Scope. The trace for displacement feedback changes from 4 mm to 6 mm immediately. Signal Scope Displacement Results 5. 6. 7. 8. 9. Make any additional changes to the test and run as desired. Click Stop to stop the test. Click the Stop Procedure (lock) icon to stop the Procedure activity. Exit the MPE application. Turn off power to the HSM and HPU, then exit the Station Manager application.
5.0 Creating Tests 5.4.0 External Command Considerations 5.4.1.0 External Command Activity The External Command activity accommodates program inputs from an external programmer or controller. Before you can use an External Command activity, you must: 1. Connect the external command source to your controller. 2. Use the Station Builder application to allocate an analog input resource for the command input signal. 3. Adjust the command input signals with the Station Manager application. 4.
5.0 Creating Tests 5.4.4.0 Overriding System Setpoint and Span With the External Command activity, you can temporarily override the default system span and setpoint values, even if you selected Disable for the Span and Setpoint controls on the MPE Command Settings tab (MPE > Test Definition > Command Settings).
6.0 Creating Advanced Tests Topics: • • Introduction............................................................................................................................................72 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 both MTS TestSuite MP and the Station Manager application should attempt to perform the test(s) contained in this chapter.
6.0 Creating Advanced Tests • 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 84. 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 78 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 76. 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.................................................................................................................................96 Setting Station Limits and Install the Physical Specimen......................................................................97 Use Manual Command to Install the Specimen.....................................................................................99 Apply Offsets to the Input Signal (optional).............
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 Setting Station Limits and Install the Physical Specimen To install the physical specimen into the test frame, you must position the actuator. To do this, you may use one or more of the following, depending on your system: • The Manual Command panel in the Station Manager application • The Model 494.05 Handset • Test frame controls This section describes how to install the specimen with the Manual Command panel and other Station Manager application features.
7.0 MTS Controller Software Note: After the specimen is installed, you will have to reset the detector limits to levels that are compatible with your test. 7.2.2.0 Access and Set Detector Settings The Station Manager application provides multiple locations where you can monitor and set detector limits and actions. Station setup access The Station Setup window includes Limit Detectors and Error Detectors panels with tabs where you can define detector limits and actions.
7.0 MTS Controller Software If the event that caused the detector to trip is within the detector limits, the detectors and any action assigned to that detector will be reset and returned to the normal (untripped) state. If the event that caused the detector to trip is still true, the detector will trip and any action assigned to that detector will occur again. For more information on station limits, see Access and Set Detector Settings on page 98.
7.0 MTS Controller Software Manual Controls Window Manual Controls Window Item Description Channel Selects the control channel. Click the Channel button to toggle between individual channels and a Master Command Group. Control Mode Selects a control mode. Select the Enable Manual Command check box to make a selected control mode the Active Mode. Active Mode Shows the current control mode. Manual Cmd Applies the manual command to the actuator.
7.0 MTS Controller Software Item Description Ride Moves enabled channels to a predefined Ride level prior to test startup. 7.3.2.0 Manually Position the Actuator to Install and Remove Specimens This procedure is used for installing and removing specimens. 1. If desired, set up the Scope window to view the actuator’s displacement and force signals. 2. On the Station Manager window’s Station Controls panel toolbar, click the Manual Command button. 3.
7.0 MTS Controller Software Note: If necessary, click the Manual Cmd text to open a window where you can change the slider-bar range. 7.4.0 Apply Offsets to the Input Signal (optional) 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. Note: You can also apply offsets to channel inputs and auxiliary inputs that are conditioned by hardware.
7.0 MTS Controller Software 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. Never apply a manual offset to a sensor being used by the active control mode while station power is on. 1. 2. 3. 4. 5. Select an access level of Operator or above.
7.0 MTS Controller Software 7.5.1.0 Adding Existing Hardware Resources to a Station Configuration If you want to add hardware resources (such as a digital input signal) to a test, use the Station Builder application to add the hardware resource to the station configuration file used by that test. Warning: Changes to the station configuration file can result in unexpected system operation, including unexpected or sudden actuator movement. Sudden actuator movement can cause injury and equipment damage.
8.0 Appendix A: MPE for MPT Users Topics: • • • • • • • • • • • About This Appendix............................................................................................................................106 Major Concepts....................................................................................................................................106 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 .
compensator ALC 84 Compensator property cycle activity 44 external command activity 61 profile activity 79 ramp activity 42, 45 configuration file 40 Considerations for selecting compensators 35 Control Mode property cycle activity 44 external command activity 62 ramp activity 42, 45 controller add new hardware 104 controller resources 30, 32 counter syntax 87 counter syntax example 87 create profile 75, 92 custom help runtime display 23 custom message window activity 23 Custom Waveform+DAQ 114 cycle 111 Cy
F failure detector 117 Fatigue Monitoring 116 feedback auto offset 102 manual offset 102 File property profile activity 78 float signals 36 Font Size property digital IO indicator monitor display 82 Format Type new variable property cycle activity 50 Frequency Multiplier property profile activity 79 Frequency property cycle activity 43 G generate report 27 generate test report 28 geometry specimen selection property 47, 64, 83 H handset 97 handset exclusive control 27 hardware add to controller 104 hardwa
modify a test without saving changes automatic saves background saves 26 monitor display digital IO indicator 81 signal scope 40, 62, 80 variable meter 81 monitor displays signal scope 45 MPE command settings 63 detector limits 97 MPT / MPE differences 106 MPT vs MPE DAQ 113 MTS controller software 96 MTS software controller 96 key concepts 96 TestSuite 96 Multipurpose Elite (MPE) 16 MultiPurpose TestWare 106 N name specimen selection property 47, 64, 83 New Test 19 New Test from Existing Test 19 New Test
profile (continued) waveform 80 Profile Action property profile activity 79 profile activity 72, 73 Profile command 112 Program Control 119 properties absolute end level ramp activity 42, 45 add cancel button input parameter activity 51 add rules input parameter activity 51 advanced cycle activity 43 at hold/resume application command settings 63 at start/stop application command settings 63 browse to matrix file ALC profile activity 85 buffer size data acquisition activity 54 change setpoint external comma
properties (continued) relative end level 2 cycle activity 44 relative end levels 40 resume ramp time station manager command options 60 resume taper time station manager command options 59 setpoint application command settings 64 external command activity 62 signal digital IO indicator monitor display 82 external command activity 62 signal list data acquisition activity 54 span application command settings 64 external command activity 62 start ramp times station manager command options 59 start taper time
Set Calculation Parameter 120 Set Control Event 119 Set Controller Value 120 set digital output 117 setpoint override 70 Setpoint property application command settings 64 external command activity 62 Signal Based command 112 Signal List property data acquisition activity 54 Signal property digital IO indicator monitor display 82 external command activity 62 signal scope monitor display 40, 45, 62, 80 simultaneous activities 19 sine wave calculation for external command 58 soak time 117 span override 70 Span
test run generate report in Microsoft Excel 28 generate report in MP 27 test variables 22 Testrun Log 110 tests hold 25 start 25 stop 25 TestSuite controller software 96 Time History Input 115 Time History Output 112 Time History Sequence Output 112 Time property ramp activity 42 Timed Acquisition 114 Timing Type property cycle activity 43 ramp activity 42, 45 Total Passes property profile activity 78 Trend Monitoring 115 trigger continuously mode 116 Trigger List property data acquisition activity 53 trigg
100-229-376 F
