{"id":109,"date":"2010-11-19T21:24:17","date_gmt":"2010-11-19T21:24:17","guid":{"rendered":"https:\/\/blogs.mathworks.com\/seth\/2010\/11\/19\/bus-signals-past-present-and-future\/"},"modified":"2010-11-19T21:24:17","modified_gmt":"2010-11-19T21:24:17","slug":"bus-signals-past-present-and-future","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/simulink\/2010\/11\/19\/bus-signals-past-present-and-future\/","title":{"rendered":"Bus Signals: Past, Present and Future"},"content":{"rendered":"

\"Blogger,By Guy Rouleau<\/a>

\r\n\r\nThe first time I used buses in Simulink, it was version 3.0 (R11). Bus signals and the way we use them in Simulink have evolved over time. In this post I want to give you a historical tour of how the bus has changed since R11. To start, in R11 I'm not even sure I should call it a bus. Why? Let's look at the Signal & Systems section of the R11 Simulink Library Browser:<\/p>\r\n\r\n

\"Simulink<\/p>\r\n\r\n

If you have good eyes, you probably noticed there is a Bus Selector<\/a> block in R11, but no Bus Creator<\/a> block. At that time, the way to create a bus was using the Mux<\/a> block.<\/p>\r\n\r\n

\"Creating<\/p>\r\n\r\n

Since that time, buses and muxes are slowly moving away from each other. To illustrate this, I went through the Archived MathWorks Documentation<\/a>.<\/p>\r\n\r\n

R13sp2<\/strong>
\r\n\r\nThis is the oldest documentation available in the archive. The Bus Creator<\/a> is now available.<\/p>\r\n\r\n

R14sp2<\/strong>
\r\n\r\nA new diagnostic is introduced: Mux blocks used to create bus signals<\/a>. Setting this diagnostic to error enforces what is called strict bus behavior<\/em>. To help users receiving errors when enabling this diagnostic, a Model Advisor check<\/a> and the function slreplace_mux<\/a> is introduced.<\/p>\r\n\r\n

R2007a<\/strong>
\r\n\r\nNow the differences become more significant:\r\n\r\n