All Posts

If you write scripts in MATLAB, you know this: the MATLAB editor is the worst. What’s Wrong with MATLAB Editor? No autocomplete suggestions.  While typing code, you get no smart help. (You would need to remember what arguments are accepted for a given function) You cannot use AI models like Codex or CoPilot across multiples files No color options for keywords.  (Which is boring) Hard to navigate.  Moving through large scripts is difficult. The Better Way: Use VS Code VS Code

A ModelMindWorks Utility for Subscribers Estimating the real effort behind a Simulink model is one of the biggest challenges in MBD projects. Hidden subsystems, logic depth, and HIL components make manual estimation slow and inaccurate. To help engineering teams move faster, ModelMindWorks  offers this exclusive Model Complexity Analyzer  as a utility. What this tool helps you answer How complex is my model? How many sprints will this take? Where are the hotspots? Is refactor

Have you ever opened a Simulink model and been greeted by an endless forest of Bus Selector blocks, with wires weaving across the canvas...

Many of you who use Stateflow, might already be familiar with the symbols pane, but I guarantee that there is something for you too, please stick with me while I brush up the symbols pane for who are new to it. It's that small window that pops up on the left side of a Stateflow chart, showing all the interfaces in that chart. You can open the Symbols pane inside the Stateflow chart by clicking the button highlighted above (Modeling tab > Design Data > Symbols Pane). Symbols p

I'm a person who uses Simulink approximately 20 hours per week. The below shortcuts did wonders to me in terms of increasing the productivity and not fidgeting much. Here are a few that quietly change the way you build and navigate models. Press Esc  and Enter to Navigate Subsystems Press Esc to step back out of the subsystem .Its smoother than double clicking on the hierarchy and lets you explore the model hierarchy seamlessly. Press Esc to go to the parent subsystem Ctrl +

If you’ve been using Simulink for a while, you’ve probably built models full of Enabled, If-Action, or Atomic Subsystems.They’re familiar, flexible, and widely used , but not always the most efficient choice. There’s another option that quietly outperforms them in many cases: Function-Call Subsystems. Many modelers overlook them, assuming they’re only for library developers or those who work heavily with Stateflow. But when used effectively, Function-Call Subsystems can make

Ever hit Run  on your Simulink model… and then had enough time to make coffee, scroll Instagram, and maybe rethink your life choices?...

Everyone is talking about the new dark mode  in MATLAB R2025a but while that grabbed attention, some truly powerful features quietly...

Most of us dread handling variants in Simulink models, especially when we want to test different input sources or send signals to...