Difference b/w virtual and non virtual bus?

hey, can anyone explain me the difference b/w virtual and non virtual bus? if possible, give a real life example for better understanding.

Answer 1

[Guy Rouleau]

A virtual bus is just a visual representation in the Simulink editor. It makes your model look nicer and easier to manage when you have many signals. It does not affect how the signal is stored in memory.

With a nonvirtual bus, the data is stored as a structure in a contiguous piece of memory. Because of that, nonvirtual have more constraints.

Consider nonvirtual bus only if you have code generation constraints requiring it.

[Aditya gandi]

Can you provide any real life examples to support your statements?

[Corey Lagunowich]

Virtual buses are so-named because they don't have a "real-life" equivelent. They are for graphical convenience and improve model readability. Non-virtual buses can be likened to bundled wire harnesses in an automobile, where each individual wire carries a different signal, but all the wires are wrapped together and are routed together through the car.

Answer 2

[Kaustubha Govind]

A bus signal is simple a structure signal containing numeric elements. When a bus signal has a Simulink.Bus object associated with it, it becomes a non-virtual bus. See the blog post Nonvirtual Bus Signals for a more detailed explanation. The documentation on Types of Composite Signals also is a good reference.

AFAIK, there is no "real world" example - the difference is only in how Simulink treats the signals.

[Guy Rouleau]

A little precision... virtual buses can have a an associated bus object. This is not required, but can be be used for validation or initialization.

Non-virtual buses need a bus object.

[Kaustubha Govind]

Ah! There's something new I learned today. :)