{"id":8756,"date":"2019-03-25T15:27:43","date_gmt":"2019-03-25T20:27:43","guid":{"rendered":"https:\/\/blogs.mathworks.com\/simulink\/?p=8756"},"modified":"2019-03-25T15:27:43","modified_gmt":"2019-03-25T20:27:43","slug":"whats-new-in-r2019a","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/simulink\/2019\/03\/25\/whats-new-in-r2019a\/","title":{"rendered":"What&#8217;s New in R2019a?"},"content":{"rendered":"<p>MATLAB R2019a is available for download. Here are some of my favorite new features in the Simulink area.<\/p>\n<p><strong>Model Reference<\/strong><\/p>\n<p>Two major enhancements have been made to model referencing. The first enhancement is that referenced models can now be opened in the same canvas as the top model, which facilitates window management. The second enhancement is that it is now possible to use Bus Element Ports at the top level of a model. The great benefit of <a href=\"https:\/\/www.mathworks.com\/help\/releases\/R2019a\/simulink\/slref\/inbuselement.html\">Bus Element Ports<\/a> is that you do not need bus objects anymore at the model reference interface.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/blogs.mathworks.com\/images\/simulink\/2019Q1\/ModelRef.png\" alt=\"Model Reference\" \/><\/p>\n<p><strong>Schedule Editor<\/strong><\/p>\n<p>The Schedule Editor is a new tool that allows you to define partitions and in which order that should execute.<\/p>\n<p>Let's take the following simple model. By default, Simulink looks at the data dependency between components to determine in which order they should execute. In this case, it would do ssA, ssB, ssC and ssD.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/blogs.mathworks.com\/images\/simulink\/2019Q1\/schedEditorEx1.png\" alt=\"Schedule Editor\" \/><\/p>\n<p>Using the Schedule Editor, it is possible to make each of those subsystems a partition and to control in which order they should execute. For example, here I specify that the order should be ssC, ssB, ssA, ssD. Notice how the line between ssA and ssB is dashed, indicating that the chosen order results in a delay in the data going from ssA to ssB.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/blogs.mathworks.com\/images\/simulink\/2019Q1\/schedEditorEx2.png\" alt=\"Schedule Editor\" \/><\/p>\n<p><strong>New Solver: odeN<\/strong><\/p>\n<p>In R2019a, a new solver named <strong>odeN<\/strong> has been added to the list of variable-step solvers. Unlike most variable-step solvers, odeN does not do error control. It is particularly useful for models where the bottleneck for the step size is either a very fast discrete rate, or lots of zero-crossing events. In this type of model, the error control mechanism of other solvers is practically never used, making odeN more efficient.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/blogs.mathworks.com\/images\/simulink\/2019Q1\/odeN.png\" alt=\"odeN\" \/><\/p>\n<p><strong>Physical Signals Units Propagation<\/strong><\/p>\n<p>If you are a Simscape user, before R2018b you probably felt puzzled by situations like the one shown in the following image. Since unit propagation was not supported for physical signals, the unit of position coming from the motion sensor was lost at the PS Gain block. Since the units were lost, specifying millimeters had no effect and the original -0.1 meters was output even if millimeters were specified in the PS-Simulink block.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/blogs.mathworks.com\/images\/simulink\/2019Q1\/psUnits.png\" alt=\"Physical Units R2018b\" \/><\/p>\n<p>In R2019a, blocks from the Physical Signals section of the Simscape library now propagate units, and the PS-Simulink block is able to properly output -100mm<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/blogs.mathworks.com\/images\/simulink\/2019Q1\/psUnits19a.png\" alt=\"Physical Units R2019a\" \/><\/p>\n<p>Note that if you upgrade an existing model to R2019a, this change will not be applied automatically. You can use the <a href=\"https:\/\/www.mathworks.com\/help\/releases\/R2019a\/simulink\/ug\/consult-the-upgrade-advisor.html\">Upgrade Advisor<\/a> to view the impacted blocks and opt-in progressively.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/blogs.mathworks.com\/images\/simulink\/2019Q1\/PSGain.png\" alt=\"Physical Units R2019a - PS Gain\" \/><\/p>\n<p><strong>Toolstrip Tech Preview<\/strong><\/p>\n<p>Once you are done installing R2019a, I recommend that you go to the Simulink Preferences and enable the following option to try the tech preview of the Simulink Toolstrip:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/blogs.mathworks.com\/images\/simulink\/2019Q1\/slPrefs.png\" alt=\"Simulink Preferences\" \/><\/p>\n<p>Here is what the Simulation tab looks like:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/blogs.mathworks.com\/images\/simulink\/2019Q1\/slToolstrip1.png\" alt=\"Simulink Toolstrip\" \/><\/p>\n<p>We decided to make the toolstrip available as a tech preview because a few important features are not available yet. The most noticeable missing feature is the capability to customize it like how the current menu entries can be customized using <a href=\"https:\/\/www.mathworks.com\/help\/releases\/R2019a\/simulink\/ug\/registering-customizations.html\">sl_customization<\/a> files.<\/p>\n<p><strong>Now it's your turn<\/strong><\/p>\n<p>This list is just a small subset of the new Simulink features in R2019a. I recommend going through the <a href=\"https:\/\/www.mathworks.com\/help\/releases\/R2019a\/simulink\/release-notes.html\">release notes<\/a> to see the complete list.<\/p>\n<p>Let us know in the comments below if there are specific features you would like to be described in more details in this blog.<\/p>\n","protected":false},"excerpt":{"rendered":"<div class=\"overview-image\"><img decoding=\"async\"  class=\"img-responsive\" src=\"https:\/\/blogs.mathworks.com\/images\/simulink\/2019Q1\/slToolstrip1.png\" onError=\"this.style.display ='none';\" \/><\/div>\n<p>MATLAB R2019a is available for download. Here are some of my favorite new features in the Simulink area.<br \/>\nModel Reference<br \/>\nTwo major enhancements have been made to model referencing. The first... <a class=\"read-more\" href=\"https:\/\/blogs.mathworks.com\/simulink\/2019\/03\/25\/whats-new-in-r2019a\/\">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":[566],"_links":{"self":[{"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/posts\/8756"}],"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=8756"}],"version-history":[{"count":34,"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/posts\/8756\/revisions"}],"predecessor-version":[{"id":8832,"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/posts\/8756\/revisions\/8832"}],"wp:attachment":[{"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/media?parent=8756"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/categories?post=8756"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.mathworks.com\/simulink\/wp-json\/wp\/v2\/tags?post=8756"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}