DEMUX
Full Library / Defining_Flow / Virtual Connection / DEMUX
Block Name: DEMUX
Code File Location: VisualSim/actor/lib/DEMUX
o Send to multiple destination from a single source. OUT block has a fixed destination name.
o Enable complex model routing where the destination can be in a field of type string or integer.
The DEMUX block accepts data on the single input port and routes the data structure or token to 'IN', 'MUX', 'NODE', Virtual_Machine or 'uEngine' blocks. The destination name is provided in a field of the incoming data structure which is listed in field_select.. The name can be of type integer or string. Depending on the type, the block matches the list in Destination_Names (string) or Destination_Names_Integer (Integer). Due to processing requirements, values are required on both rows, though only one of them need to be used. If the destination name is not in one of these lists, a error is reported.
The MUX can accept data from multiple OUT and DEMUX bubbles. The matching can be done in the same window (local Destination_Type) or in the entire model (Global Destination_Type). Local is within the same window while Global applies to any block within the model matching the name. Demo model
Parameter |
Explanation |
Type |
Example |
Field_Select |
Field name containing the destination address. |
String |
Field_Name for example -> input.dest = "abc" or input.dest = 1 |
Destination_Names |
A list of comma separated string with names of destinations that match a IN, MUX, NODE, Script Blocks. The incoming Data Structures can be sent to any of them. |
String |
Name1, Name2, ... . for example -> abc,abc1 |
Destination_Name_Integers |
A list of comma separated integers. The corresponding names in the Destination_Names provides the list of destination names that match a IN, MUX, NODE, Script Blocks. The incoming Data Structures can be sent to any of them. For each destination_names map to the destination_name_integers |
String |
1, 2, ... |
Destination_Type |
This specifies whether the Destination_Name is of type local or global. Local is used when there can be multiple instances of the current window in a model. Global is used when the connection is made to outside of this window and can be to a central location. |
- |
Local/Global |
Port |
Explanation |
Type |
Input |
This is a default input port. This port accepts Data Structures to send to destination connections. |
General |
Created with the Personal Edition of HelpNDoc: Free EPub producer