MTS Series 793 Utility Software

(1)

(2)

MTS Trademarks

MTS, be certain., Bionix, Echo, ElastomerExpress, FlatTrac, FlexTest, Just In Case, Landmark, Level Plus, MTS Acumen, MTS Criterion, MTS Echo, MTS EM Extend, MTS Exceed, MTS Insight, MTS Land-mark, MTS TestSuite, RPC, SWIFT, Temposonics, TestWare, TestWorks are registered trademarks of MTS Systems Corporation within the United States. Acumen, AdapTrac, Advantage, Aero ST, Aero-90, AeroPro, Criterion, cRPC, Exceed, First Road, Landmark, MAST, MicroProfiler, MPT, MTS Exceed, MTS Fundamentals, MTS TestSuite, ReNew, SilentFlo, TempoGuard, TestLine, Tytron, Vir-tual Test Lab, and VTL are trademarks of MTS Systems Corporation within the United States. These trademarks may be registered in other countries.

All other trademarks are the property of their respective holders.

Proprietary Software

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

Software Verification and Validation

MTS software is developed using established quality practices in accordance with the requirements detailed in the ISO 9001 standards. Because MTS-authored software is delivered in binary format, it is not user accessible. This software will not change over time. Many releases are written to be backwards compatible, creating another form of verification. The status and validity of MTS’ operating software is also checked during system verification and routine calibration of MTS hardware. These controlled cal-ibration processes compare the final test results after statistical analysis against the predicted response of the calibration standards. With these established methods, MTS assures its customers that MTS products meet MTS’ exacting quality standards when initially installed and will continue to perform as intended over time.

Manual Part Number Publication Date Release

100-147-132 R (English)

(3)

MTS Series 793 Utility Software 3

Technical Support

11

How to Get Technical Support 11

Start with your manuals 11

Technical support methods 11

Outside the U.S. 11

Before You Contact MTS 11

Know your site number and system number 11

Know information from prior technical assistance 12

Identify the problem 12

Know relevant computer information 12

Know relevant software information 13

If You Contact MTS by Phone 13

Identify system type 13

Be prepared to troubleshoot 14

Write down relevant information 14

After you call 14

Problem Submittal Form in MTS Manuals 14

Preface

15

Before You Begin 15

Safety first! 15

Other MTS manuals 15

Documentation Conventions 15

Hazard conventions 15

Other special text conventions 16

Special terms 16

(4)

4 MTS Series 793 Utility Software

Electronic manual conventions 16

Hypertext links 16

HWI-File-Editor Overview

17

About .hwi files 18

About the Hwi File Editor Application 18

Starting Hwi File Editor 18

Hwi File Editor Controls 19

About Multiple .hwi Files 22

Saving Multiple .hwi Files in a Controller Directory 23 Selecting .hwi Files in a Controller Directory 24

Create and Edit an HWI File

25

Create a New File 26

Create New hwi File for Single Box System 26

Hardware Resources 26

Hardware Resources Listed in .hwi File 26

About Detect Hardware Feature 26

Use Detect Hardware Feature 27

About .hwi Miscellaneous Hardware 27

Manually Add VME Board to .hwi File 27

Manually Add Mezzanine Card to .hwi File 28

Manually Add Transition Board to .hwi File 28

Configure Hardware Resource Settings 28

Valve Driver Settings 28

Digital Universal Conditioner (DUC) Settings 28

Analog Input Filter Settings 28

(5)

Optional Hardware Resource Name Changes 30

VME Board Address Settings 31

About Actuator Movement When the Servovalve is Clamped 31

Servovalve balance 31

Mechanical balance 31

Electrical balance 31

Inner-loop tuning 31

Where to Find Valve Balance Procedures 32

Mechanical valve-balance procedures 32

Electrical valve-balance and inner-loop tuning procedures 33

HWI Hardware Settings

35

About Hwi File Editor Default Settings 36

Edit Hwi Default Settings 36

Apply Hwi Default Settings 38

Export HWI Defaults 40

Import HWI Defaults 40

System Options Settings 41

System Options icon 41

VME Bus Board Settings 41

About Processor Boards 42

Reconfigure Processor Functions 43

Processor Hwi Settings 43

Model 493.50 ADDA II Board Settings 45

(6)

6 MTS Series 793 Utility Software Model 49x.43 Multibox I/O Board Settings 47

Model 49x.40 I/O Carrier Board HWI Settings 48

Model 494.41 Single-Station System Board Settings 50

Model 494.42 Single-Station System Board Settings 52

Model 494.44 Two-Station System Board Settings 56

Model 493.42 System Board Settings 58

Model 498.65 ADDA Board Settings 61

Model 498.70 Digital I/O Board Settings 62

Model 498.71 GRES II Board Settings 63

Model 493.40 I/O Carrier Mezzanine Cards 64

Mezzanine Card Compatibility 64

Model 493.1x Valve Driver Settings 65

Model 493.2x DUC Card Settings 66

How to Add Accelerometer Compensation to a Model 493.21B/493.25 DUC 66

How to Add a DI/O Load Washer to a Model 493.21B/493.25 DUC 67

How to Add a Serial Load Washer to a Model 493.21B/493.25 DUC 67

Model 493.45 Six-Channel A/D Card Settings 67

Model 493.46 Six-Output D/A Card Settings 68

Model 493.47 Encoder Card Settings 69

SSI/Gurley Encoder Application Settings 70

Model 493.48 Accelerometer Input Card Settings 72

Model 493.50 ADDA II Mezzanine Cards 72

Model 493.55/493.57 8-Channel A/D Card Settings 72

Model 493.56 8-Channel D/A Card Settings 73

Model 493.59x Encoder Card Settings 73

Model 494.40 I/O Carrier Mezzanine Cards 74

High Speed Data Acquisition Settings 74

(7)

How to Enable Acceleration Compensation on the Model 494.21 Card 79

How to Add a DI/O Load Washer to a Model 494.21 Card 79

How to Add a Serial Load Washer to a Model 494.21 Card 80

Model 494.25/494.26 DUC HWI Settings 80

Model 494.45 8-Input A/D Converter HWI Settings 81

Model 494.46 8-Output D/A Converter Card HWI Settings 82

Model 494.47 Dual UART/Encoder/External Clock HWI Settings 84

SSI/Gurley Encoder Application Settings 87

Model 494.49 Quad Encoder Interface HWI Settings 88

Model 498.65A-10 Eight-Channel Card Settings 89

Model 498.65A-11 D/A Card Settings 89

Model 498.65A-12 Encoder Card Settings 90

Transition Board Settings 90

Model 493.72 Digital I/O Transition Board Settings 91

Model 493.73 HPU Transition Board Settings 92

Model 493.74 HSM Transition Board 93

Model 494.74 HSM Transition Board 96

FlexTest IIm Chassis Settings 97

Miscellaneous Device Settings 98

Temperature Controller Settings 100

Remote Station Control (RSC) Settings 102

How to Add Remote Station Controls (RSC) 103

Model 494.05 Handset Settings 103

Model 494.05 Handset Hwi File Editor Settings 104

(8)

Modbus Interface Settings 105

About EtherCAT 106

About Read-Only HSMs 109

How to Configure a Read-Only HSM 109

Read-Only HSM Control Logic 110

Uninterruptible Power Supplies (UPS) 111

How to Set Model 493.40 I/O Carrier Address (FlexTest GT/SE, TestStar IIm) 113 How to Set ADDA II Board Address (FlexTest GT, TestStar IIm, FlexTest IIm) 113 How to set the Model 494.40 I/O Carrier Board Address 114

Controller Management Tool

115

Controller Options Description 116

For FlexTest SE controllers 116

For Aero ST controllers 116

Controller Attributes tab 117

User Files tab (FlexTest SE only) 119

License Keys tab (FlexTest SE only) 120

Regional Settings tab (FlexTest SE only) 120

Passwords tab (FlexTest SE only) 122

Using the Controller Management Tool 123

FlexTest SE multi Controller Considerations 123

FlexTest SE Version Checking 123

How to put a FlexTest SE Controller in the Service boot mode 124

How to Install or Update System Files on FlexTest SE Controllers 124

How to Update or Backup User Files on FlexTest SE Controllers 125

How to Register a FlexTest SE Controller for Automation 125

How to Unregister a FlexTest SE Controller 126

(9)

How to Configure a New Aero ST Multi Controller System 127

About Rebooting Aero ST Controllers with CMT 127

User File Access for Registered Controllers 127

Acumen System Setup

129

Acumen Hwi Setup 130

Acumen Hwi Settings 130

(10)

(11)

Technical Support

How to Get Technical Support

Start with your manuals

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

Technical support methods

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

Type of

Support Details

Web site www.mts.com > Contact Us (upper-right corner) > In the Subject field, choose To escalate a problem; Problem Submittal Form

E-mail Worldwide: [email protected] Europe: [email protected]

Telephone Worldwide: 1 800 328 2255 - toll free in U.S.; +1 952 937 4000 - outside U.S. Europe: +800 81002 222, International toll free in Europe

Outside the U.S.

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

www.mts.com > Global Presence > Choose a Region

Before You Contact MTS

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

Know your site 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.

(12)

Technical Support

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

Example system number: US1.42460

Know information from prior technical assistance

If you have contacted MTS about this problem before, we can recall your file based on the:

l MTS case number

l Name of the person who helped you

Identify the problem

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

l How long and how often has the problem occurred? l Can you reproduce the problem?

l Were any hardware or software changes made to the system before the problem started? l What are the equipment model numbers?

l What is the controller model (if applicable)? l What is the system configuration?

Know relevant computer information

For a computer problem, have the following information available:

l Manufacturer’s name and model number

l Operating software type and service patch information l Amount of system memory

l Amount of free space on the hard drive where the application resides l Current status of hard-drive fragmentation

(13)

For software application problems, have the following information available:

l The software application’s name, version number, build number, and (if available) software patch number. This information can typically be found in the About selection in the Help menu.

l The names of other applications on your computer, such as: l Anti-virus software

l Screen savers l Keyboard enhancers l Print spoolers

l Messaging applications

If You Contact MTS by Phone

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

l Site number l Email address l Name

l Company name l Company address

l Phone number where you can be reached

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

Identify system type

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

l Electrodynamic material test system l Electromechanical material test system l Hydromechanical material test system l Vehicle test system

l Vehicle component test system l Aero test system

(14)

Technical Support

Be prepared to troubleshoot

Prepare to perform troubleshooting while on the phone:

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

l Have the original operating and application software media available.

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

Write down relevant information

In case Technical Support must call you:

l Verify the case number.

l Record the name of the person who helped you. l 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 case number.

Problem Submittal Form in MTS Manuals

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

You can access the Problem Submittal Form at www.mts.com > Contact Us (upper-right corner) > In theSubjectfield, chooseTo escalate a problem; Problem Submittal Form

(15)

Preface

Before You Begin

Safety first!

Before you use your MTS product or system, read and understand the safety information provided with your system. Improper installation, operation, or maintenance can result in hazardous conditions that can cause severe personal injury or death, or damage to your equipment and specimen. Again, read and understand the safety information provided with your system before you continue. It is very important that you remain aware of hazards that apply to your system.

Other MTS manuals

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

You may also receive an MTS System Documentation CD. It contains an electronic copy of the manuals that pertain to your test system.

Controller and application software manuals are typically included on the software CD distribution disc (s).

Documentation Conventions

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

Hazard conventions

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

Danger:

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

Warning:

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

Caution:

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

(16)

Preface

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.

Note:

Notes provide additional information about operating your system or highlight easily overlooked information.

Recommended:

Recommended notes provide a suggested way to accomplish a task based on what MTS has found to be most effective.

Tip:

Tips provide helpful information or a hint about how to most efficiently accomplish a task.

Access:

Access provides the route you should follow to a referenced item in the software.

Example: Examples show specific scenarios relating to your product and appear with a shaded background.

Special terms

The first occurrence of special terms is shown in italics.

Illustrations

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

Electronic manual conventions

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

Hypertext links

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

(17)

HWI-File-Editor Overview

About .hwi files 18

About the Hwi File Editor Application 18

Starting Hwi File Editor 18

Hwi File Editor Controls 19

About Multiple .hwi Files 22

Saving Multiple .hwi Files in a Controller Directory 23

(18)

HWI-File-Editor Overview

About .hwi files

Hwi files are text files that define the internal components—or resources—available to MTS Series 793 Controllers. Resource examples include conditioners, valve drivers, and digital inputs.

The text description of a resource in an .hwi file includes proximity information, such as the location of the slot in the chassis in which the resource is installed, and the rear-panel connectors through which it may be accessed.

Hwi files and Station Builder

You use the Station Builder application (one of the applications included with MTS 793.00 System Software) to define test stations by allocating some or all of the resources listed in the .hwi file.

Initial .hwi files are typically created at MTS

The .hwi file associated with a given controller is typically created at MTS according to the resources included with the controller. It may be necessary to edit this file if system resources are added, removed, or repositioned in the controller chassis.

About the Hwi File Editor Application

The Hwi File Editor is a utility used to create and edit hardware interface (.hwi) files.

Starting Hwi File Editor

The typical path to the Hwi File Editor is as follows:

Start > Programs > MTS 793 System Software > Service Tools

Note:

You can also launch the application by typing hwieditor from the command line.

Supported MTS Controllers

l FlexTest 40/60/100/200 l FlexTest IIm (498.xx)

l FlexTest GT/TestStar IIm (493.10) l FlexTest SE (493.02)

l TestStar IIs (493.01) l Aero ST (493.20)

Editing existing .hwi files with the Hwi File Editor

When you open an existing .hwi file with the Hwi File Editor, the Hwi File Editor minimizes the chance of introducing syntax errors when making changes.

(19)

an .hwi file, the Hwi File Editor has a fill-down function that automatically assigns proper channel numbers and resource names.

The Detect Hardware feature automatically detects VME and transition bus hardware and adds those resources to the current file opened in the Hwi File Editor application. This is the preferred method when you create a new .hwi file.

Changing .hwi files at customer sites

While the primary use of the Hwi File Editor is to create .hwi files for systems before they leave MTS, it can also be used to make modifications to .hwi files at customer sites.

For instance, if a system in the field adds new hardware because of a need for additional conditioning, the Hwi File Editor can be used to reflect those changes in the system’s existing .hwi file.

(20)

Number callout in graphic -Item

Description

1 - Menu File: Use the File menu commands to create, open, change, save, and print files. You can also exit the application from this menu.

Note:

Whenever you save an .hwi file that has been modified, a backup copy is automatically created. The backup filename will contain a date and time stamp in the filename. For example: FTIIM_YYYY-MM-DD_HH-MM-SS.HWI.

View: Use to show or hide the Toolbar and Status Bar.

Options: Use to rename resources or reconfigure processors.

Rename Resources: Selecting this option automatically renames resources to eliminate name conflicts. You should only select this option before you create a configuration using Station Builder. Once you assign a resource to a

configuration, renaming that resource in the .hwi file will invalidate the configuration file.

When you select this option, the Hwi File Editor renames all of the analog input/output, digital input/output (except on a GRES card), and HPU and HSM resources using syntax that includes the slot number and connector name in the resource name.

For example, a 493.25 DUC in the first mezzanine location on an I/O Carrier in slot 5 is named 493.25 DUC S5-J4. Conditioners and valve drivers assigned to A/Ds or D/As use the conditioner/driver model, chassis and connector. For example, a 497.22 dual DC conditioner in chassis 2, slot 10, and channel 1 is named 497.22 DDC C2-J1001.

After selecting this option, review the new names to make sure they are acceptable. When you create a station with these renamed resources (with Station Builder) and open that station (with Station Manager), the HPU and HSM resources will appear on the Station Manager panel as they are saved in the .hwi file.

You can use Station Builder to assign logical display names (such as load, displacement) to other types of resources when allocating those resources to create a test station.

Reconfigure Processors: For Controllers equipped with the Time History Playback (THP) option and two processors, this option allows you to change the way the processors are initialized.

Note:

(21)

MTS Series 793 Utility Software 21 in graphic

-Item

Description

has only one or three processors.

Detect Hardware: This option automatically detects VME and transition bus hardware and adds those resources to the Hwi File Editor tree view pane.

Help: Selecting the Electronic Documentation option displays the Hwi File Editor manual in the portable document file (PDF) format. Selecting the About Hwi File Editor displays a window identifying the Hwi File Editor’s release version and build number.

2 - Toolbar Provides quick access to common commands and windows.

3 - Tree view pane

Shows icons of selected controller components in an expandable hierarchical display.

The intended slot number for each board is shown in brackets after the resource (type) name.

Displays icons of selected controller components in an expandable hierarchical display.

Note:

You can right-click many of the tree-view icons to perform/set features. 4 - Controller

definition pane

Contains tabbed pages of various controller components and characteristics. You create an .hwi file by making selections in these tabbed pages.

Contains tabbed pages of various controller components and characteristics. You create .hwi files by making selections in these tabbed pages.

Note:

Some tabs contain fields that contain dimmed or “grayed out” values. These values are read only, and are provided only for reference.

Properties tab Controller Type: The Hwi File Editor applies to several types of MTS Series 793 Controllers. It is important to select the controller type that pertains to your controller before you make any further selections. The available hardware is dependent on the Controller Type.

Board tab Board Slot n: Allows you to select the desired VME board (the available boards vary with controller type) for the selected slot.

Chassis tab (FlexTest IIm only)

Chassis n: Allows you to select an Analog Chassis or Hydraulic Control Panel for the selected chassis.

(22)

Number callout in graphic -Item

Description

(FlexTest GT, TestStar IIm, Aero ST, FlexTest

60/100/200 only)

selected slot.

Miscellaneous tab

Use the drop-down lists in the Miscellaneous tab to add various external devices to the .hwi file. The devices listed here are not automatically added by the Hardware Detect option.

5 - Hwi text pane The selections you make in the tabbed pages of the controller definition pane are automatically reflected as text in this pane.

The selections you make in the tabbed pages of the controller definition pane are automatically reflected as text in this pane.

About Multiple .hwi Files

You can create multiple .hwi files that contain different hardware settings and save them in the same controller directory. This allows you to create custom .hwi settings for different tests. Custom settings may include different input filtering settings, DUC settings, and external hardware settings.

(23)

MTS Series 793 Utility Software 23 Caution:

For proper operation, the hardware resources specified in a configuration (.cfg) file must match those in the .hwi file.

Changing the hardware resources in an .hwi file can cause the system load operation to fail.

When using multiple .hwi files with the same controller, make sure that your .hwi files all have identical hardware resources.

Saving Multiple .hwi Files in a Controller Directory

You can create multiple .hwi files that contain different hardware settings and save them in the same controller directory. This allows you to create custom .hwi settings for different tests.

1. Shut down any test and quit all Series 793 applications.

Caution:

2. Use the HWI File Editor application to create a new .hwi file with a new name and custom settings.

3. From the File menu, click Save As.

4. In the Save As window, select the new controller directory and click Save. The following window appears:

If you click Yes, the file is saved in the controller directory and the controller.793settings file is modified to point to the new .hwi file. The next time you start a controller application, it will use the new .hwi file.

If you click No, the file is saved in the controller directory but the controller.793settings file is not modified.

(24)

Note:

You can now use the Project Manager application to switch between the multiple .hwi files that you saved in the controller directory.

Selecting .hwi Files in a Controller Directory

You can use the Project Manager application to select different .hwi files for use with a controller.

1. Shut down any test and quit all Series 793 applications.

Caution:

2. Start the Project Manager application.

3. From the Tools menu, click Controller Settings. 4. In the controller list, click the Hwi file.

5. In the Hwi File text box, type the name of the .hwi file that you want to use.

6. Click OK.

The controller.793settings file is modified to point to the .hwi file. The next time you start a controller application, it will use the .hwi file that you defined above.

(25)

Create and Edit an HWI File

Create a New File 26

Hardware Resources 26

Configure Hardware Resource Settings 28

About Actuator Movement When the Servovalve is Clamped 31

(26)

Create and Edit an HWI File

Create a New File

Create New hwi File for Single Box System

Only qualified personnel should create or edit .hwi files.

Warning:

An incorrect .hwi file can result in improper system response and unexpected actuator movements.

Unexpected actuator movements may result in personal injury or damage to equipment.

Before operating your system, ensure the .hwi file you are using is valid for your situation.

1. From theFilemenu, clickNew.

2. Click theControllericon in the tree view pane.

3. Click thePropertiestab, and select aController Typefrom the drop-down list.

Hardware Resources

Hardware Resources Listed in .hwi File

The hardware resources listed in the .hwi file must exactly match the physical location and address settings for each board used in the system. There are two methods to add hardware resources to an .hwi file:

l Use the Detect Hardware feature to detect VME and transition bus hardware and add those resources to the current file opened in the Hwi File Editor application.

l Use the Hwi File Editor application to manually add hardware resources.

About Detect Hardware Feature

The Detect Hardware feature automatically detects VME and transition bus hardware and adds those resources to the current file opened in the Hwi File Editor application. This is the preferred method when you create a new .hwi file. The Detect Hardware feature will also remove hardware resources from an existing .hwi file if that hardware was physically removed from the chassis.

The Detect Hardware feature will not detect a Model 498.70 board, Model 497 chassis tab, or any hardware added through the Miscellaneous tab (such as temperature controllers, RSCs, and handsets). You must manually add those hardware resources for any system that uses those hardware types.

(27)

1. Open either a new or existing .hwi file.

2. From theOptionsmenu, clickDetect Hardware.

The detect hardware process adds and removes hardware resources based on what hardware was detected.

3. All detected hardware appears in the hardware resource tree. (Slot numbers for each board appear in brackets.)

4. Manually add any hardware that appears in theMiscellaneoustab (such as, temperature controllers, RSCs, and handsets).

About .hwi Miscellaneous Hardware

Any hardware listed in theMiscellaneoustab must be added manually using the HWI Editor application.

The Detect Hardware feature will not detect or add any hardware listed in theMiscellaneoustab.

Manually Add VME Board to .hwi File

The Hwi File Editor application includes a tree structure and drop-down lists that allow you to manually add hardware resources.

1. Select theControllericon in the tree view pane.

(28)

Manually Add Mezzanine Card to .hwi File

1. Select the Model 49x.40 I/O Carrier or Model 493.50 ADDAII board in the tree view pane. Empty I/O Carrier and ADDA II boards are not supported. At least one mezzanine card must be specified.

2. Click the Mezzanines tab, and select the mezzanine card type for each mezzanine location. You can also right-click a resource and select a mezzanine card from the pop-up menu.

Manually Add Transition Board to .hwi File

1. SelectControllerin the tree view pane.

2. Click theTransitiontab, and select the appropriate DIO, HPU or HSM transition boards for each transition slot.

Configure Hardware Resource Settings

Valve Driver Settings

Each valve driver has settings that may include valve mode (single/dual), current range, and clamp mode settings.

In addition, any combination card (Model 494.16 VD/DUC) must be configured as either a two-stage or three-stage valve driver.

Digital Universal Conditioner (DUC) Settings

Each DUC card requires a number of hardware settings that you must configure before attempting to use the system.

DUC Mode Settings (AC/DC)

Each DUC card must be configured as either an AC or a DC conditioner (Default=DC).

Bridge Type Settings

Model 494.xx DUCs include settings that define the bridge type (full, half, quarter).

Shunt Settings

Model 494.xx DUCs include settings that define where the shunt calibration resistor is applied.

Analog Input Filter Settings

Mezzanine cards that include analog inputs (DUCs, A/D Converter, Encoder, and conditioners) includes filter settings that you may want to change for custom applications.

(29)

Each Encoder card requires a number of hardware settings that you must configure before attempting to use the system.

Hydraulic Interface Settings

Various HSM, HPU, and system boards have hydraulic interface settings that you must define before attempting to run the system. These settings vary with each board and may include first on/last off, proportional-on/off solenoid operation, and proportional rate settings.

The drawing shows examples for the following hydraulic interface settings:

Number callout in

graphic -Item

Description

1 - HPU with HSM

Hydraulic Power Unit (HPU) with Hydraulic Service Manifold (HSM)

2 - HPU Only

Hydraulic Power Unit (HPU) only

3

-Controller

(30)

Number callout in

graphic -Item

Description

4 - HPU with HSM

This setting is available for the HPU transition and system boards (494.41, 494.42, 494.44, 493.42).

TRUE–indicates the system’s HPU supplies one or more HSMs.

FALSE–used for HPU only systems (makes HPU selection available in Station Builder). 5

-Connect to HPU

This setting is available for various HSM transition boards.

Off–indicate the HSM can be activated without an HPU activation.

HPU On–indicates that the HPU must be started (either manually or as “first on”) before you can activate an HSM.

HPU On w/ Tracking–Same function as HPU On, however HSM cannot be at a higher state than the HPU. For example, if HPU and HSM are set to high, and then HPU is set to low, the HSM will follow the HPU state and change to low. If HPU is set to off, HSM will follow and set to off.

Optional Hardware Resource Name Changes

If you change the name of a hardware resource, you may invalidate existing configuration files. This is because an existing configuration file depends on the names of the resources in the current .hwi file matching the names of the resources with which the configuration was created. (These are the names displayed in the Hardware Resources lists in the Station Builder application.)

If the names do not match, the configuration will not load into Series 793.00 System Software applications.

Resource naming convention

Hwi files typically use the following resource naming convention for valve driver and conditioner resources:

Convention: Resource model; Slot number; Connector number.

Example 1: 493.14 2SVD S5-J5.

Explanation: An MTS Model 493.14 2-Stage Servovalve Driver Board located in Slot 5 of the chassis whose output is available from Connector J5.

Example 2: 493.21B DUC S3-J4.

Explanation: An MTS Model 493.21B Digital Universal Conditioner Board located in Slot 3 of the chassis whose input is available at Connector J4.

(31)

If you use the Hardware Detect feature to add hardware resources, the board addresses are correct and no further action is required.

If you manually added the hardware resources to the .hwi file, you must make sure that the address setting in the .hwi file matches the physical address switch settings on the 493.40 I/O Carrier board, 494.40 I/O Carrier Board, and the ADDA II board.

About Actuator Movement When the Servovalve is

Clamped

If an unbalanced servovalve (two-stage or three-stage) is clamped by Series 793 software, it may act unpredictably. In addition, if a three-stage servovalve is clamped when its third stage is not properly tuned, it may act unpredictably.

Servovalve balance

To balance a servovalve, you must first perform a mechanical adjustment on the servovalve to achieve gross mechanical balance. You can then use the Series 793 software Valve Balance to perform an electrical adjustment to fine-tune the mechanical adjustment.

Mechanical balance

The mechanical adjustment must be performed before the electrical adjustment, and is typically performed at the following times:

l At system installation

l When a new servovalve is installed in an existing system l If the servovalve cannot be electrically balanced

l At regular service intervals

Electrical balance

The electrical adjustment is performed with the Valve Balance control, which adjusts the electrical input to the servovalve to compensate for minor mechanical imbalances. When the valve-balance adjustment is complete, there should be no (or minimal) hydraulic fluid flow when the servovalve output signal is at null.

Note:

The electrical adjustment is typically performed much more frequently than the mechanical adjustment.

Inner-loop tuning

In addition to mechanical and electrical valve-balance adjustments, three-stage servovalves also have inner-loop tuning controls that may affect clamping behavior. The inner loop is similar to a

(32)

The inner control loop resides inside the test system’s primary, or outer control loop. So in addition to the pilot spool, three-stage servovalves include a third stage (or main) spool, that is driven by the pilot spool.

The inner loop (like the outer loop), has gain and rate controls that can be adjusted to optimize

performance. The inner-loop is tuned at system installation, and requires periodic fine tuning when the outer-loop becomes sluggish.

Number callout in graphic Item

1 Feedback

2 Outer Loop

3 Inner Loop

4 Hydraulic Service Manifold (HSM)

5 Hydraulic Power Supply

6 Control Signal

7 493.15 Valve Driver

8 Program Command

The innerloop (proportional) gain and rate (derivative) adjustments are the same types of adjustments as the proportional and derivative gain adjustments of the outer-loop tuning controls.

Where to Find Valve Balance Procedures

Mechanical valve-balance procedures

For two-stage servovalves, the mechanical valve balance procedure is included in the Series 252 Servovalve Product Manual (PN 011-182-906), which is typically included in the system

(33)

the LVDT mechanical null for the third-stage spool. These procedures are included in the Series 256 Servovalve Product Manual (PN 011-209-602), which is typically included in the system

documentation set.

Electrical valve-balance and inner-loop tuning procedures

Electrical valve balance procedures and inner-loop tuning procedures for three-stage servovalves are included in the Series 793 Tuning and Calibration manual (PN 100-147-134).

(34)

(35)

HWI Hardware Settings

About Hwi File Editor Default Settings 36

Edit Hwi Default Settings 36

Apply Hwi Default Settings 38

Export HWI Defaults 40

Import HWI Defaults 40

System Options Settings 41

VME Bus Board Settings 41

Model 493.40 I/O Carrier Mezzanine Cards 64

Model 493.50 ADDA II Mezzanine Cards 72

Model 494.40 I/O Carrier Mezzanine Cards 74

Model 498.65A-10 Eight-Channel Card Settings 89

Model 498.65A-11 D/A Card Settings 89

Model 498.65A-12 Encoder Card Settings 90

Transition Board Settings 90

FlexTest IIm Chassis Settings 97

Miscellaneous Device Settings 98

How to Set Model 493.40 I/O Carrier Address (FlexTest GT/SE, TestStar IIm) 113

How to Set ADDA II Board Address (FlexTest GT, TestStar IIm, FlexTest IIm) 113

(36)

HWI Hardware Settings

About Hwi File Editor Default Settings

The Hwi Defaults feature allows you to change the default HWI settings for most VME- and transition-bus hardware. When Show HWI Defaults is selected, Hwi Default settings appear in an editable resource tree that appears above the Controller resources.

To change Hwi Default values, edit the hardware properties pages in the HWI Defaults tree. Once you edit the default settings, you can:

l Apply the new default settings to hardware resources in the current hwi file.

l Use the Export HWI Defaults function to save the settings to a file and change the HWI File Editor application defaults.

l Use the Import HWI Defaults function to import default settings from a file and change the HWI Editor application defaults.

Edit Hwi Default Settings

You can apply default Hwi settings to new and existing controller hardware.

1. On the View menu, click Show HWI Defaults. When Hwi Defaults are displayed, Hwi Default settings appear in an editable tree structure located above the Controller resources.

(37)

2. Change the default HWI Settings in the HWI Defaults tree.

You can also use the Import HWI Defaults function to change the default settings based on a previously exported HWI Defaults file.

Note:

When you import a previously created Hwi Default file, the Hwi Editor application will use those default values for any subsequent .hwi files that you create.

3. Once the default settings are changed, you can apply the settings to the controller resources.

Note:

Optional–Use the Export HWI Defaults function to save the default setting in a file. The export function also changes the Hwi Editor application defaults. The Hwi Editor application will use the exported default values for any subsequent Hwi files that you create.

(38)

Apply Hwi Default Settings

Hwi Default values can be universally applied to all the hardware resources in the controller tree or selectively applied to specific hardware resources. Use one of the following methods to apply Hwi defaults to existing hardware

l Right-click the Controller icon and click Apply HWI Defaults.

HWI defaults are applied to all the hardware resources used in the Controller tree.

l Right-click the I/O Carrier icon and click Apply HWI Defaults. HWI defaults are applied to the hardware resources in the I/O carrier.

l Right-click a hardware resource in the Controller tree and click Apply HWI Defaults. The HWI default settings are only applied to that hardware resource.

In this example, the default HWI values will only be applied to the selected 494.26 hardware resource.

(39)

l Right-click a specific hardware resource in the HWI Defaults tree and click Apply HWI Defaults.

The HWI default is applied to any instance of that particular hardware resource that appears in the Controller tree.

In this example, the default values for the 494.16 VD/DUC will be applied to all instances of the 494.16 in the Controller tree.

(40)

Use one of the following methods to apply Hwi defaults to new hardware that you add to an Hwi file:

l On the Options menu, click Detect Hardware. Any hardware detected will use the default Hwi settings.

l Manually add hardware to the Controller tree. Any new hardware that is added will use the default Hwi settings.

Export HWI Defaults

Default Hwi values can be exported to a file for future use. After HWI Defaults are exported, the Hwi Editor application will use those default values for any subsequent Hwi files that you create.

Note:

Hwi Default files use a “.hwidef” file extension.

Use one of the following methods to export an HWI Defaults file that includes all the default settings from the Hwi Defaults tree view:

l On the File menu, click Export HWI Defaults. OR

l Right-click the HWI Defaults icon and click Export HWI Defaults. OR

l Right-click the Controller icon and click Export HWI Defaults.

Import HWI Defaults

Previously exported Hwi Defaults files can be imported. After HwiDefaults are imported, the Hwi Editor application will use those default values for any subsequent Hwi files that you create.

Note:

Hwi Default files use a “.hwidef” file extension.

Use one of the following methods to import a previously exported Hwi Defaults file.

l On the File menu, click Import HWI Defaults. OR

l Right-click the HWI Defaults icon and click Import HWI Defaults. OR

(41)

System Options icon

Velocity Limiter: When enabled (true), limits actuator movement to a maximum of 10 mm/sec. when displacement is commanded from the RSC or handset. This feature provides compliance to CE requirements. When Velocity Limiter=True, the manual command control is locked.

Interlocks: When the Hwi File Editor reads existing .hwi files, this value represents the number of interlock chains in the file. If you are creating a new .hwi file, enter the desired number of interlock chains.

VME Bus Board Settings

VME Board FlexTest IIM (498.xx) FlexTest GT, Teststar IIM (493.10) Aero ST (493.20) FlexTest SE (493.02) FlexTest 40 (494.04) FlexTest 60/100/200 (494.06/.10/.20)

Processor X X X X X X

Model 493.40 I/O Carrier

X X X

Model 494.40 I/O Carrier

X X

Model 493.50 ADDA II

X X X

Model 49x.43 Multi-Box I/O X Model 498.71 GRES II X Model 498.71 GRES III

X X X

Model 498.65 ADDA X Model 498.70 Digital I/O X

(42)

VME Board FlexTest IIM (498.xx) FlexTest GT, Teststar IIM (493.10) Aero ST (493.20) FlexTest SE (493.02) FlexTest 40 (494.04) FlexTest 60/100/200 (494.06/.10/.20) Model 493.42 System Board X Model 494.41 System Board X Model 494.44 System Board X

About Processor Boards

Each controller requires one or more processor boards that are installed in the VME chassis. Each processor board includes at least one CPU (core).

Core functions

Each core performs predefined CPU functions such as, Supervisor (SUP), Digital Signal Processing (DSP), and Time History Playback (THP). The function(s) assigned to each core depends on the number of processor boards and the types of options installed.

One processor board

The single core performs SUP and DSP functions.

Two processor boards

By default, the core in Processor [1] performs the SUP and optional THP functions, while the core in Processor [2] performs the DSP function.

Note:

If necessary, use the Reconfigure Processors option window to reconfigure the core functions for existing two-processor systems.

Three processor boards

The core in Processor [1] performs the SUP function (and THP if the Hybrid Simulation option is installed), and the core in Processor [2] performs the DSP function.

The core in Processor [3] performs the THP function (if that option is installed) or the hybrid simulation (SIM) function (if that option is installed).

Dual-Core Processor

Although these boards occupy one slot, they contain two cores that perform different CPU functions:

(43)

MTS Series 793 Utility Software 43 Note:

Controllers can only have one dual-core processor with no other processor boards.

Reconfigure Processor Functions

For controllers with the Time History Playback (THP) option and two processors, this option allows you to change the way the processors are initialized.

Note:

This option will be grayed-out if your controller is not equipped for THP, or has only one or three processors.

1. From the Options menu, click Reconfigure Processors.

The Reconfigure Processors window shows how your controller is currently configured.

2. If necessary, change the processor setting.

Default Setting: The Shared SUP/THP on 1 and DSP on 2 default setting is recommended for configuring new controllers.

Existing Settings: Some existing systems may require the “SUP on 1 and shared DSP/THP on 2” OR “Shared SUP/DSP on 1 and THP on 2” settings.

Important:

If an existing HWI file uses one of the other settings, do not change the setting.

(44)

Item Description

Processor circuit board icon Processor properties

Address: Describes the proximity of the circuit board within the chassis. This value is generated during initialization, and should be changed only if the value read in from an existing .hwi file is wrong.

Slot: Specifies which slot the circuit board occupies in the chassis. More than one function (such as SUP, DSP, THP, or SIM) may occupy the same slot.

Application Attribute: Not applicable

# of Cores: (applies to dual-core processors only): If a dual-core processor (such as the 7100) is used, set the number of cores to two. All other single-core

processors should be set to one.

Note:

This setting cannot be changed if you use the HWIDetect Hardware

feature.

Core icon Each processor board includes at least one core that represents the CPU on that board.

Function icon Under eachCoreicon areFunctionicons that specify what functions are performed by the CPU (core).

Name: shows the function assigned to that CPU (core). The function(s) assigned to each core depends on the number of processor boards and the types of options installed.

SUP= Supervisor

DSP= Digital Signal Processing

THP= Time History Playback

SIM= Hybrid Simulation (option)

Processor Number: Not applicable

Interrupt Level: Not applicable

SIM Function icon (optional)

The hybrid simulation (SIM) function for internal models is an option that requires a license key. Once the license key is installed, you must add the SIM function to the appropriate processor core.

To configure a processor to run the Hybrid Simulation (SIM) option:

1. Right-click the processorCoreicon and clickAdd Simulation Function.

2. Click the SIMFunctionicon and define the number of input and output ports.

(45)

Hybrid Simulation is set up by MTS personnel only. This is described in an internal MTS document.

Reflective memory icon optional)

Some options, such as Hybrid Simulation (external model), require a reflective memory module that is mounted on the processor card.

To add reflective memory to a processor, right-click theDSP Functionicon and clickAdd Reflective Memory.

Note:

Input/Output Port icons (optional)

Input and output ports are user-defined portions of memory associated with:

l Reflective memory (external simulation model). When you add reflective memory to the DSP core function, you will see a port icon for each import and export port specified in theReflective Memoryproperties.

OR

l The memory on a processor board that is running the hybrid simulation (SIM) function (internal simulation model). The input/output port icons appear when you add the hybrid simulation (SIM) function to a processor and define the number of input/output ports.

Note:

Model 493.50 ADDA II Board Settings

(46)

493.50 ADDAII circuit board icon

When the optional Model 493.50 ADDA II board is being used, the .hwi file describes this board and the A/D, D/A, DSPAD, and encoder mezzanine cards that are

installed on it.

The following ADDA II mezzanine cards can be installed:

l Model 493.55 8-A/D (8-Channel) l Model 493.56 8-D/A (8-Channel) l Model 493.57 8-A/D (8-Channel) l Model 493.59-1 U2 Absolute l Model 493.59-3 U2 Incremental l Model 493.59-5 U2 Temposonics III

Each mezzanine card can be assigned to one of the four ADDA II board rear panel connectors. Each mezzanine card definition is followed by four or eight signal definitions.

The analog I/O definitions provide A/D channels and D/A channels for analog inputs and outputs from the 498 Analog In transition boards.

The channel numbers for the analog inputs represent the available analog-to-digital converters following the list of AC and DC conditioner signals.

The channel numbers for the analog outputs represent the available digital-to-analog converters following the list of valve command signals.

Properties tab

Address: Describes the proximity of the circuit board within the chassis. This value is generated during initialization, and should be changed only if the value read in from an existing .hwi file is in error.

Slot: Specifies which slot the circuit board occupies in the chassis.

Clock Type: Master/Dependent.

For Master Clocks

System Rate: 1024, 2048, 4096 and 6144 Hz (binary).

Note:

The System Rate must be an integer multiple of the Medium System Rate.

Medium System Rate: Must be an integer multiple of the Low System Rate.

Note:

The Low System Rate is always set at 25.6. The Medium System Rate is typically 256.

(47)

Mezzanines tab

Mezzanine: describes the mezzanine cards that are installed on the ADDA board.

Model 498.71 GRES II Board Settings

This card is compatible with FlexTest IIm controllers.

498.71 GRES II circuit board icon

The Model 498.71 GRES II board supports both the Remote Station Controller (RSC) and the temperature controller. It must be added to your system when using either of these components before the components are installed in the chassis. The GRES II board communicates to the RSC or temperature controller via a serial transition card located to the rear of the chassis.

Address: Describes the proximity of the circuit board within the chassis. This value is generated during initialization, and should be changed only if the value read in from an existing .hwi file is in error.

Clock Type: Master, Dependent.

For Master Clocks

Clock Mode: Decimal, Binary.

Digital Input/Output icons

Name: Describes this resource as it will appear in Station Builder resource lists when opened against an .hwi file.

Changing this name may invalidate existing station configurations.

Channel: Not applicable.

Model 49x.43 Multibox I/O Board Settings

(48)

49x.43 Multi-box I/O circuit board icon

System Rate: 512, 1024, 2048, 4096 and 6144 Hz (binary).

Note:

Model 49x.40 I/O Carrier Board HWI Settings

These settings are for the Model 493.40 and 494.40 I/O Carrier boards.

The Model 493.40 board is compatible with Aero ST, FlexTest GT, FlexTest SE, and TestStar IIm controllers. The Model 494.40 board is compatible with FlexTest 40/60/100/200 controllers.

Note:

When a 494.40 I/O carrier board is plugged in to a chassis, but the .hwi file does not include the I/O board, the system load will generate a hardware interlock that you cannot clear.

Paddleboard considerations for the Model 494.40 I/O Carrier

To avoid system-load errors, the Model 494.40 I/O carrier that connects to the paddle board (a circuit board with ribbon cables that connect the VME bus to the transition bus) must be configured as follows:

l The paddle board must connect to the 494.40 with the lowest VME address. l The 494.40 board must be configured as Clock type=Master.

(49)

49x.40 I/O Carrier circuit board icon

Describes each Model 49x.40 I/O Carrier board installed in the Chassis and their installed mezzanine cards. Each I/O Carrier board can support up to four mezzanine cards.

The first I/O Carrier board in slot three (typical) provides the master clock (Clock Type=Master) for all other I/O Carrier boards. If a GRES III board is added (typically in Slot 10), the clock type for this I/O Carrier board must be changed to Clock

Type=Dependent.

For FlexTest SE and FlexTest 40 controllers, the System Board provides the master clock (Clock Type=Master) for the system, so all I/O Carrier boards must be set to Clock Type= Dependent.

49x.40 Properties tab

Address: Describes the proximity of the circuit board within the chassis. This address setting must match the address switch settings on the 49x.40 board.

Note:

The Detect Hardware feature automatically detects the correct address setting from the board and enters it in the .hwi file.

Application Attribute: an editable string that can be queried by a controller application.

Clock Type: Master/Dependent.

For Master Clocks (Clock Type = Master):

Clock Mode: Binary/Decimal.

Note:

Changing the clock mode (from binary to decimal or from decimal to binary) on systems with Series 494 hardware affects the calibration of AC conditioners which can result in inaccurate readings. If you want to run in a different clock mode, you must calibrate the transducer/AC conditioner pair in the new clock mode and run your tests in the same clock mode.

System Rate: 512 (single-box Aero systems), 1024, 2048, 4096 and 6144 Hz (binary).

Note:

49x.40 Mezzanines

(50)

tab

Model 494.41 Single-Station System Board Settings

The Model 494.41 board is used with FlexTest 40 controllers.

Item Description 494.41 System Board circuit board icon

The System Board defines digital and analog inputs and outputs, and hydraulic power unit (HPU) and hydraulic service manifold (HSM) functionality.

Properties tab

Slot: 4.

Slot 4 in the FT-40 chassis is reserved for the system board.

Low System Rate: 25.6. Digital

Input/Digital Output icons

Name: Describes this resource as it will appear in Station Builder resource lists when opened against an .hwi file. The name includes the connector number (for example: “Dig In 1-J54”).

Analog Output icons

Connector: Both Analog Outputs are available on the “DA Output” connector (located on the front of the 494.04 chassis).

Changing this name may invalidate existing station configurations. Hydraulic

Interface icon (HPU)

Connector: J25.

HPU with HSM: True: Indicates the system’s HPU supplies HSMs. False: used for HPU only systems (allows HPU selection to be available to Station Builder).

First On: True: Indicates that the first HSM turned on activates the HPU.

False: Setting First On and Last Off to False allows the HPU to turn on independent of HSM power.

(51)

without pressing the HPU buttons.

Last Off: True: Causes the last HSM turned off to turn off the HPU.

The First On/Last OFF settings are only available if the HPU with HSM setting is True.

Visible: True: Indicates whether or not the HPU button is visible on the control panel. Changing Visible to False turns off the HPU button display on the Station Manager window, provided both First On and Last Off are True.

The Visible setting is only available when both the First On and First Off settings are set to True.

Hydraulic Interface icon (HSM)

Connector: J28

Name: Describes the hardware resource as it will appear in Station Builder resource lists.

Type: Solenoid, Proportional, On/Off Solenoid.

If you select On/Off Solenoid, only two HSM control buttons (Off/On) will appear on the Station Manager Station Controls panel. For the other types, three HSM control buttons will appear (Off/Low/High).

If you select Proportional, you configure the proportional output with the controller software. The output signal can be ramped from 20 mA (minimum) to 700 mA (maximum) which corresponds with 50 psi (0.4 MPa) and 3000 psi (21 MPa). By default, low pressure is factory set at 750 psi (5.25 MPa) and high pressure is set at 3000 psi (21 MPa).

Low Percent: 25. HSM low pressure setting as a percentage of full-scale.

High Percent: 100. HSM high pressure setting as a percentage of full-scale.

HSM Rate: Slow = 4 seconds. Fast = 2 seconds.

Time to achieve low pressure from zero pressure = (Low Percent value) x (HSM Rate value).

Time to achieve high pressure from low pressure = (High Percent value x HSM Rate value) - (Time to achieve low pressure).

Example: If Low Percent value = 25, High Percent value = 100, and HSM Rate = Slow (4 seconds):

(52)

Time to achieve low pressure = 0.25 x 4 = 1 second.

Time to achieve high pressure = (1 x 4) - (1) = 3 seconds. Interlock

Interface icon

Connector: J43,J29.

Assign to Interlock: Set to 1.

Gate Interlock: True or False, True = the controller responds to the gate interlock signal on pins 3 and 4 of J29. (Default=True.) False=J29 pins 3 and 4 are reserved for Program Stop interlock.

Caution:

Failure to enable the gate interlock option on systems that can operate in Slow (low-flow) mode can result in unexpected actuator movement when switching the system from Slow mode to Fast mode.

Unexpected actuator movement can result in injury to personnel or damage to the equipment.

Enable the gate interlock option for systems that include a Slow (low-flow) mode for specimen installation.

Model 494.42 Single-Station System Board Settings

The Model 494.42 board is used with FlexTest 40 controllers.

494.42 System Board circuit board icon

The System Board defines digital and analog inputs and outputs, and hydraulic power unit (HPU) and hydraulic service manifold (HSM) functionality.

Properties tab

Slot:4.

Slot 4 in the FT-40 chassis is reserved for the system board.

System Rate:1024, 2048, 4096 and 6144 Hz (binary).

Medium System Rate:Must be an integer multiple of the Low System Rate.

Low System Rate:25.6.

Digital Name:Describes this resource as it will appear in Station Builder resource lists when opened against an .hwi file. The name includes the connector number (for example: