Student Notes · 2 Hours · Simulink Onramp Modules 10–11 · Certificate
This is the final Simulink session. Today you complete the Simulink Onramp, earn your MathWorks Simulink Onramp certificate, and consolidate everything built across Sessions 05–08 into a Simulink-to-EV concept map you keep for the rest of the programme.
The certificate is a real, shareable MathWorks credential — earned by completing the Module 11 assessment. Treat it as a professional milestone.
The assessment covers Modules 1–11. Confirm each before starting Block B.
Model-Based Design (MBD) is the workflow used by every major automotive OEM to develop, verify, and deploy vehicle software. Simulink is the tool at the centre of that workflow. Understanding where the skills you have built sit in the real engineering process gives the work its meaning.
| Stage | What happens | Your Simulink skill that covers it |
|---|---|---|
| 1 — Concept & Spec | Engineering requirements defined: power, voltage, torque, speed targets | Block parameters — every Gain value traces to a real spec (Kt, gear ratio, 2π/60) |
| 2 — Simulink Model | System built as a block diagram with subsystem hierarchy | Sessions 05–08: blocks, signals, Gain, subsystems, named ports, hierarchy levels |
| 3 — Simulation & Verification | Model run against drive cycles; Scope output checked against specification | Scope literacy — reading amplitude, transient, and steady-state behaviour |
Group synthesis exercise. The output is your permanent EV reference sheet for the rest of the programme.
As a group, complete the Simulink concept map in Section 06 below. Map every Simulink concept from Sessions 05–08 to a concrete EV engineering application. Aim for at least 10 rows. Every row must name a specific block type, parameter, or hierarchy concept — not just "Simulink".
Sketch the complete Simulink signal chain on the whiteboard: Throttle → Battery Pack subsystem → Motor Controller subsystem → Motor subsystem → Wheel Speed. Label every signal line with its name and units. Show at least one internal block inside the Motor Controller subsystem (e.g. the RPM_to_RadPerSec block you built). Every block must be named with its Simulink block type.
Click any cell to edit it. Add rows for your own concepts. Enter your name, then save the completed map as a PNG image.
| Simulink Concept | Session | Real EV Application |
|---|
Across Sessions 05–08 you have gone from placing your first block to building a named, hierarchical, reusable Simulink model that mirrors the structure of real OEM powertrain simulations. The RPM→rad/s subsystem you built is not a training exercise — it is the exact conversion present in every real motor controller implementation.
The certificate you earned today is the entry credential for Model-Based Design work. The blocks, signals, parameters, and hierarchy you understand are the building blocks of every production EV simulation model, at any scale.