Vehicle Dynamics Simulation Setup & Analysis
Automate vehicle dynamics simulation setup, solver config, and results analysis
What You Can Do
This skill automates the translation between physical vehicle specifications and numerical solver inputs, eliminating manual setup errors that cause convergence failures or unrealistic results. You can rapidly configure multi-body dynamics models with proper initialization parameters, solver settings, and validation checkpoints. The skill guides you through disciplined simulation architecture that catches setup issues before expensive solver execution begins.
Features
converts vehicle specifications (suspension geometry, tire properties, mass distribution) into platform-specific solver parameters
selects appropriate integrators, contact algorithms, and convergence tolerances based on simulation type (quasi-static, transient, parametric)
validates completeness of vehicle models (constraints, degrees of freedom, boundary conditions, load cases)
identifies root causes of failed simulations (ill-conditioned matrices, unrealistic initial conditions, stability issues)
systematizes post-processing workflows to extract vehicle handling metrics (understeer gradient, lateral acceleration response, tire slip angles)
establishes consistent model variations across baseline, sensitivity, and durability study configurations
generates simulation setup documentation that transfers across ADAMS, CarSim, LS-DYNA, and SIMPACK environments
structures simulation-to-test correlation testing for handling, durability, and control system validation
Example Output
Example 1: Steady-State Handling Simulation Setup
- Vehicle specification inputs: wheelbase 2.8m, track width 1.6m, CG height 0.55m, tire cornering stiffness 100 kN/rad
- Generated solver config: quasi-static analysis with 0.1s ramp to 4g lateral acceleration, friction coefficient 1.2, tire slip angle output at 1Hz
- Validation checklist: ✓ suspension constraints properly defined, ✓ tire model loaded with temperature effects, ✓ driver steering input ramped smoothly, ✓ convergence tolerance set to 1e-4
Example 2: Convergence Failure Diagnosis
- Symptom: ADAMS simulation diverges after 2s into transient maneuver
- Diagnostic output: detected ill-conditioned contact stiffness (ratio 1e7), recommended reducing normal force penalty coefficient from 5e5 to 5e4 Pa/m
- Corrected solver settings: HHT integrator with α=-0.05, reduced time step from 0.01s to 0.005s, compliance damping enabled
Example 3: Handling Metrics Extraction
- Raw simulation outputs: tire slip angles, lateral acceleration, yaw rate, steering wheel angle vs time
- Processed metrics: understeer gradient = 0.8 deg/g, lane change peak yaw rate = 18 deg/s, steady-state gain 0.92 rad/m
- Report format: comparison table against target values with pass/fail status
What's Included
- SKILL.md instruction file with complete simulation workflow phases:
- Vehicle Specification Template: structured checklist for translating physical requirements (suspension, tire, mass) into solver inputs
- Platform Configuration Guides: pre-configured solver settings for ADAMS, CarSim, LS-DYNA, and SIMPACK with decision trees for parameter selection
- Convergence Troubleshooting Flowchart: systematic diagnosis of failed simulations with recommended corrections
- Handling Metrics Calculation Worksheet: post-processing formulas and validation acceptance criteria for understeer gradient, lateral response, tire slip analysis
- Parametric Study Template: variable definition matrix for sensitivity studies and design sweeps
- Simulation-to-Test Correlation Checklist: validation protocols for correlating simulation predictions against physical test results
Who It's For
- Vehicle Dynamics Engineers — setting up baseline handling and durability simulations in MBD platforms
- Simulation Engineers — troubleshooting convergence issues and optimizing solver configurations
- Controls Engineers — validating control algorithms against vehicle dynamics simulation predictions
- Test Engineers — designing simulation-based validation matrices that correlate with physical testing
- Suspension Design Engineers — translating suspension geometry specifications into simulation models
Best For
- Baseline handling simulation model setup (steady-state, transient, maneuver testing)
- Convergence failure diagnosis and solver parameter optimization
- Parametric sensitivity studies across suspension, tire, and vehicle architecture variables
- Simulation-to-test correlation and validation matrix planning
- Multi-platform model migration and legacy simulation model updates
- Control system validation simulations for active safety and performance features
You might also like
You can validate AUTOSAR software architectures across multiple compliance dimensions—layer separation, component interfaces, port definitions, service interfaces, and communication semantics. The skill identifies structural violations, missing documentation artifacts, and compliance gaps early in the design phase, helping you catch issues before formal gates and functional safety audits. It generates architecture compliance reports and documentation needed for ISO 26262 functional safety reviews.
You can analyze multi-dimensional steering system performance including torque characteristics, self-alignment torque, steering angle feedback, road feel transmission, and torque vectoring effects. Extract actionable insights from simulation and test data to identify root causes of steering feel issues, then develop tuning recommendations for steering gear ratios, EPS algorithms, suspension geometry effects, and torque vectoring control strategies.
This skill helps you architect platform strategy by generating decision frameworks, prioritization matrices, and roadmap plans that account for developer ecosystem impact. You'll analyze tradeoffs between breaking changes, feature velocity, and technical debt to make confident platform decisions. It synthesizes developer feedback, competitive positioning, and business goals into actionable strategic outputs that your team can execute.
You can design complete AUTOSAR 4.x system architectures by automating component allocation across abstraction layers, modeling port interactions and service interfaces, and validating compliance with AUTOSAR standards. Claude helps you create standardized architecture documentation, detect circular dependencies and interface mismatches, and generate port interaction matrices—accelerating ECU architecture development while ensuring standards adherence.
You can analyze FEA thermal simulation data to identify motor hotspots, calculate heat generation from motor losses across operating points, evaluate competing cooling solutions quantitatively, and troubleshoot excessive temperature rise during dyno testing. The skill helps you validate thermal management design margins, assess motor lifetime degradation risk, and optimize cooling loop efficiency—enabling data-driven thermal design decisions before building prototypes.
You can efficiently diagnose complex NVH concerns by working through a structured framework that correlates customer symptoms with potential powertrain failures. This skill helps you narrow diagnostic possibilities, recommend targeted testing sequences, distinguish between component failures and tuning issues, and substantiate warranty claims with technical evidence.
You can evaluate simulation scenarios against functional safety and SOTIF requirements, identify untested edge cases and high-risk operational design domains, map failure modes to root causes, and generate traceability matrices linking requirements to validation results. This skill transforms raw simulation data into defensible technical documentation that demonstrates test completeness and readiness for real-world deployment.
You can pinpoint the exact source of sensor fusion failures—whether they stem from misaligned camera/LiDAR/radar extrinsic calibration, timestamp desynchronization, data validation gaps, or algorithmic issues. This skill decomposes multi-modal perception errors into sensor-specific contributions and generates quantifiable diagnostic reports that directly guide calibration and testing teams toward fixes rather than blind troubleshooting.