A Beginner's Guide to TestProfiler

Can an operator define the cycle count from the Test screen?

Yes. The field that defines the number of cycles supports expressions, so it can be linked to a specimen-number, sample-number, or choice input. This allows the operator to specify the cycle count from the Test screen rather than requiring the value to be fixed only in the method-programming screen.

Can one cyclic test include both tension and compression?

Yes. TestProfiler can apply both tensile and compressive loads to a specimen within a single cyclic step or through subsequent ramp steps. The specimen geometry and fixturing must support load reversal.

Can the cycle count be displayed during a test?

Yes. The Test screen can show a live cycle count for the current cyclic step, as well as a total cycle count across all cyclic steps.

Can the Test screen show which step is currently running?

Yes. Add Active zone as a live display on the Test screen to show which step is currently being performed.

How can I create a cyclic test with displacement that increases every five cycles?

You can do this in either of two ways:

Option 1: Create separate ramps with looping

Create a ramp up to 5 mm and a ramp down by 5 mm, then loop that sequence five times. Next, create ramps up to 10 mm and down by 10 mm and loop those five times. Continue in the same way for each displacement increment.

This is straightforward, but it may become cumbersome when the test includes many increments.

Option 2: Use a single cyclic step with events and variables

Use one cyclic step with an action every five cycles to increment the displacement endpoints. This requires: (1) linking the maximum and minimum position inputs to specimen-number inputs; (2) creating 'Variable Events' for cycle counts 5, 10, 15, and so on; and (3) assigning 'Set a Variable' actions to those events so that each action increments the displacement set point linked to the relevant specimen input.

For a more advanced setup, you can reduce the number of variable events by linking another specimen-number input to the cycle count and building a function that automatically increments the cycle value and the associated displacement endpoint for each new group of five cycles.

How do test speed and test duration affect the cyclic durability limits of a 6800 system?

A 6800 Series system can run a cyclic test for up to 10 days at 25°C, at a maximum frequency of 1 Hz, while operating at either 100% of rated speed with up to 50% of rated force, or 100% of rated force with up to 50% of rated speed.

Data capture note: For long-duration tests, choose a data capture rate that records the required detail without generating excessive data. A high capture rate over many days can consume temporary storage and memory while the test is running.

How many independent loops can a TestProfiler profile contain?

Looping can be enabled for any event’s action, so a profile can contain multiple independently configured loops. A common setup is to add a loop when one step ends, directing the sequence back to an earlier step for a specified number of repetitions, or loops. This is different from a single cyclic step, where the number of cycles is defined within that step and the motion cycles between two points. When looping between multiple steps, the minimum duration for each step is 2 seconds, corresponding to a maximum loop frequency of 0.5 Hz.

Can TestProfiler produce a sinusoidal or near-sinusoidal waveform on an Instron 5900 Series load frame?

No. Sinusoidal waveform profiles are not supported through TestProfiler on 5900 or 6800 Series static testing systems. The drivetrain, controller, firmware, and software are not designed for sinusoidal cyclic control. Low-cycle triangle loading and unloading are supported. For sinusoidal and other waveform test control, use an Instron fatigue testing system designed for dynamic testing.

What is auto-balance, and when should it be used?

The auto-balance step type in TestProfiler is similar to the auto-balance function available in the Test Control pre-test menu. It is most commonly used alongside a preload: a relatively small force is applied to the specimen to remove slack. Once preload is reached, the strain source’s displacement channel is generally balanced, or zeroed. This helps each test begin with a consistent starting force and eliminates slack.

Not every TestProfiler workflow requires an auto-balance step, but it is available when the test procedure calls for one.

Will adding TestProfiler affect my existing methods?

No. Existing standard methods, (i.e., tension, compression, flex) can continue to be used without impact. Purchasing the TestProfiler option adds access to additional test types for creating new methods.