Skip to content
Automotive & Mobility

Software-defined vehicles need a software-defined toolchain

Bring AUTOSAR architectures, Simulink controllers, GT-SUITE powertrains, and ASAM OpenDRIVE / OpenSCENARIO scenarios into one workspace, then co-simulate, check safety margins, and export FMUs.

msx — automotive
$ msx autosar lint BrakeController.arxml
$ msx simulink to-modelica Suspension.slx --out=Suspension.mo
$ msx fmu DC_Motor motor.mo --fmi-version 3 --type cs
The challenge

What slows automotive & mobility teams down

01

Toolchain sprawl

Architecture, controls, plant, and scenario tools each speak their own format, so integrating them takes weeks.

02

Scenario coverage

Proving AV safety means running thousands of scenarios, not a handful of hand-picked test drives.

03

Vendor lock-in

Per-seat licenses limit who can run models, so CI and supplier collaboration suffer.

Reference workflow

One pipeline, end to end

  1. 1

    Architect

    AUTOSAR ARXML → SysML v2

  2. 2

    Integrate

    Simulink controllers + GT-SUITE plant

  3. 3

    Scenario

    OpenDRIVE roads, OpenSCENARIO maneuvers

  4. 4

    Deliver

    FMI 3.0 FMUs & SSP packages

Capabilities

What ModelScript does for you

AUTOSAR RTE simulation

Inspect and lint ARXML, project it to SysML v2, and simulate runnable scheduling.

Simulink → Modelica

Parse .slx / .mdl block diagrams and translate them to equation-based Modelica.

Scenario safety

Orchestrate OpenSCENARIO runs on OpenDRIVE roads with time-to-collision and RSS margin checks.

Co-simulation

Package FMUs with SSP and orchestrate multi-rate co-simulation.

Open-core toolchain that runs anywhere

Browser, CLI, VS Code, CI pipelines, or air-gapped Enterprise Appliances (AGPL-3.0 Core & Commercial Editions).

Open-Core under the GNU AGPL v3 License; Enterprise Edition (ee/) under the ModelScript Enterprise License. • Trademark Policy