As I said many times, I spend a good part of my life debugging and editing Simulink models. Anything that can save me a couple of clicks or can make the model more readable and understandable at first look has significant impact for me.<\/p>\n
To give you an overview of the improvements made to the Simulink Editor in R2020a, I put together the following animation where you should notice:<\/p>\n
- \n
- Flexible Port Placement:<\/strong> It is now possible to move ports to any side and in any order. This is possible for Subsystem, Subsystem Reference, Model block and Stateflow<\/li>\n
- Port Name Propagation:<\/strong> Notice that when I connected the output named \"Voltage\" from block1 to block2, the newly created port on Block2 was automatically named \"Voltage\" too.<\/li>\n
- Block name on any side of blocks:<\/strong> With flexible port placement, we thought it was a must to also allow placing the block name on any side of blocks<\/li>\n
- Display port number:<\/strong> When I create a new connection from Block3 to Block2, the label is \"1\". We think it is more useful than the default port name \"In1\". As soon as you rename the Inport\/Outport block, we automatically begin to display the port name.<\/li>\n
![\"Editor](\"https:\/\/blogs.mathworks.com\/images\/simulink\/2020Q2\/EditorEnhancements.gif\")
<\/p>\nSimulink Profiler<\/strong><\/p>\n
Another activity where I spend a lot of my time is helping users figure out if their Simulink models could run faster. For that, I have a set of tools I heavily depends on: Performance Advisor<\/a>, MATLAB Profiler<\/a>, Solver Profiler<\/a>, sldiagnostics<\/a>, and of course the Simulink Profiler<\/a>.<\/p>\n
One complaint I often heard from users about the Simulink Profiler in previous versions is that it was too \"engine-oriented\" and was not exposing results in the way users see their models.<\/p>\n
In R2020a, we heard you and we decided to completely re-design the Simulink Profiler. The results are now displayed in-canvas and are organized following the model hierarchy; here is an example where I profiled the Lane Following Control with Sensor Fusion and Lane Detection example<\/a> from the Automated Driving Toolbox<\/a><\/p>\n
![\"Simulink](\"https:\/\/blogs.mathworks.com\/images\/simulink\/2020Q2\/profilerSmall.png\")
<\/a><\/p>\nClick to enlarge<\/a><\/em><\/p>\n
This new profiler offers bi-directional navigation between the model and the profiler report, and if you have the property inspector opened and select a block in the list, you will get additional information on this block's individual methods. For those who will miss the previous profiler, no worries- there is a way to toggle between the new model hierarchy view and an execution view that is ordered in a way similar to the previous profiler HTML report.<\/p>\n
64-bit integer data types<\/strong><\/p>\n
Before R2020a, if you needed to deal with fixed-point types larger than 32 bits, you needed a license for the Fixed-Point Designer<\/a>. In R2020a, Simulink and Stateflow now supports 64-bit integer data types.<\/p>\n
![\"64-bit](\"https:\/\/blogs.mathworks.com\/images\/simulink\/2020Q2\/64bitInteger.png\")
<\/p>\n<\/p>\n Simulink Compiler<\/strong><\/p>\n
The Simulink family has a new product: Simulink Compiler<\/a>.<\/p>\n
I am not going to say too much in this post because I have a post dedicated to Simulink Compiler coming soon, but in short, it allows you to share Simulink simulations as standalone executables. We support most formats supported by MATLAB Compiler<\/a>, plus generating a standalone Functional Mockup Unit<\/a>.<\/p>\n
I recommend visiting the product page<\/a> for more details.<\/p>\n
Now it's your turn<\/strong><\/p>\n
Visit the R2020a release notes<\/a> and let me know in the comments below if there are features you would like me to describe on this blog.<\/p>\n","protected":false},"excerpt":{"rendered":"
<\/div>\nR2020a is here... Time to highlight my favorite new Simulink features!\u201d
\nEditor Enhancements
\nAs I said many times, I spend a good part of my life debugging and editing Simulink models. Anything that... read more >><\/a><\/p>\n","protected":false},"author":41,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[16],"tags":[597],"_links":{"self":[{"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/posts\/9459"}],"collection":[{"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/users\/41"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/comments?post=9459"}],"version-history":[{"count":15,"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/posts\/9459\/revisions"}],"predecessor-version":[{"id":9493,"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/posts\/9459\/revisions\/9493"}],"wp:attachment":[{"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/media?parent=9459"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/categories?post=9459"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/tags?post=9459"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}} - Port Name Propagation:<\/strong> Notice that when I connected the output named \"Voltage\" from block1 to block2, the newly created port on Block2 was automatically named \"Voltage\" too.<\/li>\n