Simulation Completed

Earthquake Simulation Table

Table system simulating earthquake effects with controlled movement.

Earthquake Simulation Table
Duration 10.2024 - 06.2025

Project timeline

Technical scope Not specified

Main tools and layers

System type Simulation

Project category and focus

Contribution role Design + development

Worked on mechanical motion generation, frequency/amplitude scenarios, motor driving and experimental observation flow. Contrib...

Used technologies

Technologies used in this project

Key technologies in this project are matched automatically from its technology list and category structure.

Simulation & Control
MATLAB Advanced Simulink Advanced ROS Intermediate FK/IK Intermediate Simscape Intermediate Gazebo Intermediate Trajectory Planning Intermediate
Details

Project overview

The earthquake simulation table is an educational and experimental mechatronics system concept aimed at observing structural response through controlled vibration inputs. Mechanical motion generation, motor driving, frequency/amplitude control and repeatable user scenarios are the main parts of the work. The aim is to move earthquake effect from abstract explanation into a measurable and observable experiment environment.

System perspective: The project was considered not as a single technical output, but together with requirements, data flow, user interaction, failure scenarios, maintainability and future extensibility. This makes both the engineering decisions and software architecture choices easier to understand.

Implementation detail: The content was expanded to explain not only the technologies used, but also how the problem was approached, which layers were separated, how data and control flow were considered, and which competency the project represents inside the CV.

Portfolio depth: This record highlights not only the technologies used, but also how the requirement was decomposed, how data or control flow was considered, what output is presented to the user and how the project can be extended later. This turns the project card from a short showcase into a readable case study that explains engineering decisions.

Case Study

The technical story from problem to outcome

Problem

Theoretical calculation alone may not be enough to understand earthquake effects. A controlled and repeatable test platform is needed to observe how different frequencies, amplitudes and motion profiles affect small scale models.

Solution

Vibration table logic, motor control and scenario based motion inputs were designed together.

Technical architecture

The mechanical table produces motion, the motor driver layer manages frequency/amplitude behavior and the user repeats experiments through scenario parameters.

Outcome

The project strongly demonstrates the relationship between control, mechanical design and experimental validation. The earthquake simulation table makes it possible to study the effect of different motion profiles on model behavior more clearly.

Architecture

Block-based system flow

01 / Input Input / need

Theoretical calculation alone may not be enough to understand earthquake effects. A controlled and repeatable test platform is needed to observe how different frequencies, amplitudes and motion profiles affect small scale models.

02 / Process Processing and control

The mechanical table produces motion, the motor driver layer manages frequency/amplitude behavior and the user repeats experiments through scenario parameters.

03 / Data Data / records

Vibration table logic, motor control and scenario based motion inputs were designed together.

04 / Output Output / interface

The project strongly demonstrates the relationship between control, mechanical design and experimental validation. The earthquake simulation table makes it possible to study the effect of different motion profiles on model behavior more clearly.

Live showcase

Demo, output and visual story

Before / current state

Theoretical calculation alone may not be enough to understand earthquake effects. A controlled and repeatable test platform is needed to observe how different frequencies, amplitudes and motion profiles affect small scale models.

After / improvement

The project strongly demonstrates the relationship between control, mechanical design and experimental validation. The earthquake simulation table makes it possible to study the effect of different motion profiles on model behavior more clearly.

Architecture diagram

The mechanical table produces motion, the motor driver layer manages frequency/amplitude behavior and the user repeats experiments through scenario parameters.

Featured output

The project strongly demonstrates the relationship between control, mechanical design and experimental validation. The earthquake simulation table makes it possible to study the effect of different motion profiles on model behavior more clearly.

Project inquiry

Contact about this project