Professional Documents
Culture Documents
Simulink Intro
Simulink Intro
Simulink is an environment for multidomain simulation and Model-Based Design for dynamic and embedded systems. It provides an interactive graphical environment and a customizable set of block libraries that let you design, simulate, implement, and test a variety of time-varying systems, including communications, controls, signal processing, video processing, and image processing. Add-on products extend Simulink software to multiple modeling domains, as well as provide tools for design, implementation, and verification and validation tasks. Simulink is integrated with MATLAB, providing immediate access to an extensive range of tools that let you develop algorithms, analyze and visualize simulations, create batch processing scripts, customize the modeling environment, and define signal, parameter, and test data.
Key Features
y y y y y y y y y y
Extensive and expandable libraries of predefined blocks Interactive graphical editor for assembling and managing intuitive block diagrams Ability to manage complex designs by segmenting models into hierarchies of design components Model Explorer to navigate, create, configure, and search all signals, parameters, properties, and generated code associated with your model Application programming interfaces (APIs) that let you connect with other simulation programs and incorporate handwritten code MATLAB Function blocks for bringing MATLAB algorithms into Simulink and embedded system implementations Simulation modes (Normal, Accelerator, and Rapid Accelerator) for running simulations interpretively or at compiled C-code speeds using fixed- or variable-step solvers Graphical debugger and profiler to examine simulation results and then diagnose performance and unexpected behavior in your design Full access to MATLAB for analyzing and visualizing results, customizing the modeling environment, and defining signal, parameter, and test data Model analysis and diagnostics tools to ensure model consistency and identify modeling errors
You can construct a model by assembling design components, each of which could be a separate model.
y y y
Continuous and discrete dynamics blocks, such as Integration and Unit Delay Algorithmic blocks, such as Sum, Product, and Lookup Table Structural blocks, such as Mux, Switch, and Bus Selector You can customize these built-in blocks or create new ones directly in Simulink and place them into your own libraries. Additional blocksets (available separately) extend Simulink with specific functionality for aerospace, communications, radio frequency, signal processing, video and image processing, and other applications. You can model physical systems in Simulink. Simscape, SimDriveline, SimHydraulics, SimMechanics, and SimPowerSystems (all available separately) provide expanded capabilities for modeling physical systems, such as those with mechanical, electrical, and hydraulic components.
Options for connecting blocks in Simulink. You can connect blocks manually, by using the mouse, or automatically, by routing lines around intervening blocks and through complex topologies.
The Simulink user interface gives you complete control over what you can see and use onscreen. You can add your commands and submenus to the editor and context menus. You can also disable and hide menus, menu items, and dialog box controls.
Creating and Masking Subsystems 2:39 Create hierarchy and modularize system behavior using subsystems.
You can also segment your model into design components to model, simulate, and verify each component independently. Components can be saved as separate models by using model referencing, or as subsystems in a library. They are compatible with configuration management systems, such as CVS and ClearCase, and with any registered source control provider application on Windows platforms.
You can reuse the design components on multiple projects, easily maintaining audit and revision histories. Organizing your models in this way lets you select the level of detail appropriate to the design task. For example, you can use simple relationships to model high-level specifications and add more detailed relationships as you move toward implementation.