Vibration test tailoring

When it makes sense

A standard profile does not match real use

Standard vibration profiles are written for many products at once. Tailoring makes sense when:

A standard profile tests your product too hard or too softly.
Real use lasts thousands of hours, and the test must finish in hours.
You must show that a test is equivalent to the loads in the field.

Process

From field data to a shaker test

One OpenEOL program runs the job, and each tab calls an open-source package. Your product and your shaker stay at either end.

Software

The open-source software behind it

Your test labRuns the test

Shaker and controllerRuns the tailored profile

OpenEOLRuns the program

Task engine Open sourceRuns each step and keeps the data together

GUI framework Open sourceTabs for Measure, Analyze, Generate and Report

Reports and database Open sourceProfile, drive file and report for each job

AnalysisFinds the equivalent test

FatigueDS Open sourceFatigue damage spectrum and extreme response spectrum

FLife Open source20 spectral methods for fatigue life

pyExSi Open sourceGaussian and non-Gaussian drive signals from a PSD

Profile synthesisShorter profile with the same damage

DriversRecord the field data

OpenEOL IO drivers Open sourceNI DAQmx or Dewesoft

The parts marked open source are code your team can read and change. FatigueDS, FLife and pyExSi come from the same team as OpenEOL, and the program is built for each project on top of them.

Related use cases

Other durability tests

Accelerated vibration fatigue testing

Resonance tests that track damping and stop at the first crack.

Details

Component endurance test rig

Cycles counted, with force, current and temperature logged on every cycle.

Thermoelastic stress analysis system

Full-field stress maps from an infrared camera.

Details