Tech news in 3 minutes

Ceva Targets PC Gaming Audio Market With RealSpace Elevate for Windows

20 d ago

As systems grow more complex across science and engineering, computer simulation becomes increasingly vital for design, analysis, and verification. Traditional monolithic simulation uses a single tool, but many real-world systems are multidisciplinary—combining mechanics, electronics, software, and thermal effects. Co-simulation addresses this by allowing multiple simulation tools to exchange data at regular intervals, enabling unified system-wide simulation. This requires tools to adhere to common standards, such as the Functional Mock-Up Interface (FMI). The FMI standard is a free, tool-independent, open standard for co-simulation. FMI 2.0, widely adopted as of 2025, is used by Siemens tools including HyperLynx AMS, PartQuest Explore, Simcenter Amesim, and Twin Activate. Over 270 FMI-compatible tools exist across disciplines. An FMI interface consists of an API, a Functional Mock-Up Unit (FMU)—a containerized model for deployment—and an interface description. One tool exports an FMU, which the importing tool integrates with its own model. The FMU block appears graphically with input/output ports; data exchange occurs at a defined communication time-step. Two examples demonstrate FMI co-simulation with Siemens tools. First, an electromechanical co-simulation: HyperLynx AMS (HL AMS) models an electrical subsystem driving a stepper motor, exports an FMU, and co-simulates with Simcenter Amesim’s mechanical model (gear reducer, winch, mass). Results show the mass moving as expected with a 1 ms time-step. Second, a control system co-simulation: HL AMS models a power converter, and a controller designed in Twin Activate is exported as an FMU and integrated for co-simulation. These implementations open broad co-simulation capabilities, enabling specialists to work across domains without deep expertise in other tools, and allowing black-box models to protect intellectual property.