MUX
Behavior / MUX
Block Name: MUX
Code File Location: VisualSim/actor/lib/MUX
The MUX (multiplexor) block accepts remote connection requests from an "OUT" or "DEMUX" as the input and places the incoming Data Structure on the output port. It completes the connection from a 'OUT' or 'DEMUX' blocks by matching the list of values in the Destination_Name parameter value in this block with the corresponding values in the OUT or DEMUX blocks. The 'MUX' Block can contain several Destination_Names and can act as a collection of several virtual connection source blocks. The virtual connection can be matched within the current window or Block Diagram Editor (Destination_Type is local) or from the entire model (Destination_Type is global).
A basic multiplexer connector allows multiple sources to make a connection to the 'MUX" output port. The Use Model for the MUX Block is to model virtual connections within the model. This block matches Destination_Name of 'OUT', 'DEMUX' Blocks. Demo model
Parameter |
Explanation |
Type |
Example |
Destination_Names |
Destination_Names is linked to 'DEMUX', 'OUT', 'NODE', or uEngine' Blocks. This is a comma separated values of destination names. The Destination_Names can be a concatenation of any number of individual strings and parameters, separated by "+". |
String |
Name1, Name2, ... |
Destination_Type |
The relative destination mode operator. This is a string-valued attribute that defaults to "Local". The virtual connection can be matched within the current window or Block Diagram Editor (Destination_Type is local) or from the entire model (Destination_Type is global). This mode appends a local string value to the Destination_Name parameter. |
- |
Local |
Port |
Explanation |
Type |
output |
The incoming Data Structures sent from virtual connections, based on Destination_Name, are output through this port. |
General |
Created with the Personal Edition of HelpNDoc: Single source CHM, PDF, DOC and HTML Help creation