Simulink
Simulink model-based design conventions for simulation, code generation, and verification
Details
Language / Topic
MATLABCategory
framework
Compatible Frameworks
simulink
Rules
balanced
- Use `Library Browser` subsystems for reusable block groups and link library blocks with `Simulink.Block.link` — never copy-paste blocks across models.
- Set `SolverType` to `Fixed-step` and choose the solver explicitly (e.g., `ode4`) for real-time target deployment — variable-step solvers are for simulation only.
- Use `Inport`/`Outport` blocks at the top level and name them descriptively — they define the model's interface for simulation, code generation, and SIL/PIL testing.
- Use `Model` reference blocks instead of subsystems for large sub-models to enable incremental code generation and independent team development.
- Apply `Simulink.Signal` objects and `Simulink.Parameter` objects for signals and parameters that require code generation metadata (storage class, identifier).
- Use `Model Advisor` to check modeling guidelines compliance before code generation — resolve all MAAB and IEC 61508 rule violations.
- Enable `Strict Indexing` and `Array bounds checking` in the Configuration Parameters to catch index out-of-bounds errors during simulation.