Accelerated vibration fatigue testing

Hold a part at resonance, track its natural frequency and damping, and stop the run at the first sign of a crack.

A pass or fail result hides how the part failed

Resonance testing runs many cycles fast, but a bare pass or fail result gives no damage history. Tracking through the run makes sense when:

What the rig uses
Part Accelerometer Shaker sensor cable analog samples trend results frequency and amplitude setpoint drive signal Signal conditioning IEPE or charge amplifier Data acquisition NI DAQmx or Dewesoft Industrial PC OpenEOL workflow Shaker controller closed loop drive Damping trend frequency and damping PLC and MES stop event and results Your part Station hardware
The part under test is yours. The shaker, its controller, the sensor chain and the industrial PC make up the rig.
How the test works
  1. Mount the part on the shaker, and sweep the frequency to find the natural frequency and the damping.
  2. Hold the part at resonance at the target stress amplitude.
  3. Track the natural frequency and the damping through the run.
  4. Stop the run when the natural frequency drops by the set amount, an early sign of a crack.
  5. Store the frequency and damping trend and the cycle count at the stop.
The open-source software behind it
Your lab or lineReceives the results
Quality database or report archiveResults and stop events over OPC UA, MQTT or SQL
OpenEOLRuns the rig
Task engine Open sourceRuns the sweep, the resonance run and the stop check as one sequence
GUI framework Open sourceOperator screens with live data and the result
Reports and database Open sourceFrequency and damping trend stored for each run
AnalysisTracks the run
Frequency response function Open sourceFinds the resonance peak and damping from the drive and response
Trend tracking Open sourcerolling() and moving_average() follow frequency and damping through the run
Resonance dwell and stop ruleHolds the stress amplitude at resonance and stops at the set frequency drop
DriversTalk to the hardware
OpenEOL IO drivers Open sourceNI DAQmx or Dewesoft for the sensors, Modbus or CANopen for the controller setpoint
Vendor runtimeRuns on the shaker controller and holds the real-time resonance dwell loop
Open-source OpenEOL analysis functions run inside the OpenEOL workflow, so your engineers can read and change every step. The dwell control and the stop rule are built for each project on top of them.
Other durability tests
We can help
Planning a resonance fatigue rig?

Get in touch.

janko.slavic@fs.uni-lj.si