Skip to main content
HyperLynx AMS schematic in Xpedition Designer above a system model containing an FMI block, from Siemens EDA's FMI co-simulation article

FMI Co-Simulation in HyperLynx AMS and PartQuest Explore: Electrical, Mechanical and Thermal Models in One Run

GSAS Editorial · · 5 min read

HyperLynx AMS supports FMI co-simulation from its 2510 release: it can export and import Functional Mock-up Units (FMUs), so a circuit modelled on the PCB schematic can co-simulate with models from other FMI-compatible tools, such as a Simcenter Amesim mechanical model.

A power converter depends on its control loop. A stepper motor responds to the drive electronics feeding it. A phone board heats up differently depending on which chip is working hardest. Real products cross domains, and the simulation tools that model each domain usually do not talk to each other.

Siemens EDA has closed part of that gap in HyperLynx AMS, its analog/mixed-signal simulator. A June 2026 Siemens article describes how HyperLynx AMS now exchanges models through the Functional Mock-up Interface (FMI), so a circuit modelled on the PCB schematic can run in the same simulation as a model built in another FMI-compatible tool. This post summarises what changed and where it is useful. The original article is linked under References.

HyperLynx AMS schematic and an FMI block in a system model

What FMI is

FMI is an open, tool-independent standard that lets different simulation environments exchange data and run as one system. It defines a standard API and a container format, the Functional Mock-up Unit (FMU), which packages a model so one tool can export it and another can import it.

Siemens describes FMI 2.0 as the industry’s prevalent version as of 2025, and notes that over 270 tools across disciplines support FMI. The public list is maintained at fmi-standard.org/tools.

There are two kinds of FMU, and the difference decides how you run a co-simulation:

FMU typeHow it runs
StandaloneFully self-contained. The importing tool runs the co-simulation on its own.
Tool-couplingA communication bridge. Both the exporting and the importing tool run at the same time.

Because an FMU can be a black box, a domain expert can hand a working model to a colleague in another discipline without that colleague learning the originating tool, and without exposing the model’s internals. For teams working with suppliers or across business units, that IP boundary matters as much as the technical link.

What HyperLynx AMS added in 2510

HyperLynx AMS simulates analog and mixed-signal circuits using SPICE, VHDL-AMS, Verilog-A/AMS and IBIS models, and it is tightly integrated with the PCB design flow: simulation models are assigned directly in the design schematic, which Siemens says reduces errors and time. See our HyperLynx overview for the wider AMS feature set.

From the 2510 release, HyperLynx AMS supports both FMU export and FMU import. Siemens says this lets HyperLynx AMS co-simulate with hundreds of other FMI-compatible tools.

Two worked examples from Siemens

Siemens’ article walks through two demonstrations.

Electromechanical. The electrical subsystem driving a stepper motor is modelled in HyperLynx AMS, and the mechanical system is modelled in Simcenter Amesim. HyperLynx AMS exports a tool-coupling FMU, Amesim imports it, and the two subsystems simulate together.

Thermal-electrical. A standalone FMU exported from Simcenter Flotherm, Siemens’ CFD tool for electronics thermal management, is imported into PartQuest Explore, where an electrical model reproduces a smartphone’s real-world usage. The co-simulation shows each chip’s power dissipation driving its temperature: in Siemens’ example, the RF chip cools during offline gaming while the processor heats up.

Where this pays off

The value of FMI is in the questions a single-domain simulation cannot answer:

  • Motor drives and actuators. Does the drive electronics still behave when the mechanical load is realistic rather than an ideal resistor?
  • Power conversion with digital control. Does the converter stay stable when the controller model, not an idealised loop, closes the feedback?
  • Thermally coupled boards. How do dissipation and temperature move together across a real usage profile, rather than at one worst-case operating point?

These are common questions for the EV, industrial automation and consumer-electronics programmes that Indian hardware teams build and support.

Working with GSAS

GSAS supports the Siemens EDA portfolio in India, HyperLynx included, with local application engineers who work alongside your team on model setup and simulation flows. If you want to set up HyperLynx AMS models on one of your own circuits, talk to us. GSAS has offices in Bengaluru, Hyderabad, Chennai, Pune, Mumbai and Delhi NCR.

References

Interested in Siemens EDA tools?

Talk to our application engineers for personalized tool recommendations.

Frequently asked questions

Which HyperLynx AMS release added FMI support?
Siemens introduced FMI support in the HyperLynx AMS 2510 release, covering both FMU export and FMU import.
What is the difference between a standalone FMU and a tool-coupling FMU?
A standalone FMU is fully self-contained, so the importing tool runs the co-simulation on its own. A tool-coupling FMU acts as a communication bridge, so both the exporting and the importing tool must run at the same time.
Which FMI version is most widely used?
Siemens describes FMI 2.0 as the industry's prevalent version as of 2025, with over 270 tools across disciplines supporting the standard.

Stay in the Loop

Get monthly compliance updates, product insights, and engineering best practices delivered to your inbox.