phx-simulink

Co-simulation between Simulink and a rigid-body physics scene involves mapping named object properties like positions, velocities, and forces to Simulink signals. This allows you to exchange control inputs and simulation outputs for closed-loop feedback.

Mapping physical object properties to Simulink ports requires configuring PhxModel blocks with unique object names and valid sizeable numeric property references. You can bind positions, orientations, velocities, forces, springs, and joints directly to Simulink signals for property-driven exchange.

Yes, you need a fixed-step simulation setting to run PHX co-simulation in Simulink. Configuring the sample time and substeps correctly is essential for safe feedback-loop design, preventing algebraic loops, and diagnosing kinematic-body timing issues.

The best way to apply runtime actions in a Simulink physics model is using the PHX Action block. It handles occasional imperative operations like runtime spawning, object removal, reparenting, and force application during the co-simulation.

Simulink and physics co-simulation validation fails when object names or property references are invalid, or when unsupported method ports are used. Algebraic loop errors and kinematic-body timing issues are typically resolved by using Memory blocks and configuring proper substeps.

Yes, you can render synthetic camera outputs from a physics scene into your Simulink model. During co-simulation configuration, you can set up the viewer, camera, and rendered-image output alongside your scene source and sample time settings.