MATLAB: How to reduce signal clutter in the Simulink diagram

busclutterroutingsignalsimulink

How do I reduce signal clutter in my Simulink diagram? I have a number of signal lines, which makes my diagram hard to understand.

Best Answer

The possible options for reducing signal clutter are as follows:

1) Data stores blocks

2) GoTo/From blocks

3) Composite Signals (virtual bus, nonvirtual bus, mux)

To avoid any limitations, it is recommended to use composite signals (in particular buses) since these allow for the greatest flexibility and have the ability to scale to large, complex models. To compare the different composite signal techniques, you may refer to the following documentation page:

https://www.mathworks.com/help/simulink/ug/select-a-composite-signal-technique.html

Virtual buses will meet most modeling requirements for combining signals, and execute faster than nonvirtual buses in generated code. Additionally, the "In Bus" and "Out Bus" ports greatly reduce complexity in the diagram compared to repeated "Bus Selector" and "Bus Creators" blocks. Therefore, this is likely the best solution for large, detailed models.

Related Solutions

MATLAB: How to retrieve the name of a signal coming into a Bus Creator block in Simulink, when the signal is not propagated from a Subsystem, without having to update the diagram

The ‘SignalHierarchy’ property of the Outport of the bus can be used to extract the name of the children signals. Though the name of the Inport signals is not available before the model is updated, if the children signals of the Outport are accessed, then the name is visible even before the model is updated.

Here is an example on how to extract the name of the signal from the command line, by using the 'SignalHierarchy' property.

   busCreator = 'model2/Subsystem1/Bus Creator1';
   ph = get_param(busCreator,'PortHandles');
   sh = get_param(ph.Outport, 'SignalHierarchy')
   sh.Children(1).SignalName

MATLAB: How to name and display mux signals read on a real-time target scope

Mux signals are "Virtual Signals" and their labels cannot be displayed in a target scope. Instead, the key is to use a "Bus Creator" block instead of a "Mux" block.

Assume that you have two signals with different labels (signal labels can be adjusted by right-clicking on the signal, selecting "Properties" and typing the label into the "Signal name" field).

These two signals can be connected to a "Bus Creator" block to create a single bus signal.

When this bus signal is connected to a "Target Scope", the scope will display the individual labels of the two signals.

If you are not explicitly using a "Mux" block, but rather the signal originates from its source as a six-channel mux, then the procedure would be slightly more involved.

1) You would first have to separate the signal using a "Demux" block.

2) Then each individual signal should be passed through a unit gain block (i.e., "Gain" block with a gain value of 1) so that the virtual signals are converted to non-virtual signals.

3) Then the output signals of the gain blocks could be labeled as desired, before feeding them into a "Bus Creator" block.

4) When the bus signal is connected to a "Target Scope", all individual signal labels should be displayed on the scope of the target machine.

Best Answer

Related Solutions

MATLAB: How to retrieve the name of a signal coming into a Bus Creator block in Simulink, when the signal is not propagated from a Subsystem, without having to update the diagram

MATLAB: How to name and display mux signals read on a real-time target scope

Related Question