IN

Behavior / IN
Block Name: IN

Code File Location: VisualSim/actor/lib/IN

Block Overview

o It accept requests from Virtual Connections (Mux and OUT) and Virtual Machines.

o It connects blocks in a model without the use of wires or links.

o It is used to accelerate the model execution by reducing the number of links and ports in a model.

Description

This block accepts incoming Data Structures or tokens from any OUT/MUX/uEngine/Virtual_Machine blocks and sends a value on the output port. The single parameter called Destination_Name is composed of two parts- the name and the value to be output, separated by ".". The incoming transaction is accepted if the requesting destination matches the name subset of the Destination_Name. The output value is based on the value part of the Destination_Name.

Output Value

         1. If there is no "." following the name, then the incoming data structure is output.
         2. If there is a field name, then value in that field of the incoming data structure is output
         3. If there is a memory name, then the content of the memory is output.

The Destination_Name can consist of up to any number of concatenated strings to form the name.value combination.

The virtual connection can be matched within the current Block Diagram Editor window(Destination_Type is local) or from the entire model (Destination_Type is global).

View the Virtual Connection Example in the BDE to understand the usage.

Parameter	Explanation	Type	Example
Destination_Name	It is an unique destination name, which is linked to 'DEMUX', 'OUT', 'NODE', Virtual_Machine or uEngine' Blocks. Destination_Field has the following options: o Destination_Name - Sends the entire incoming Data Structure or Token value on the output port. o Destination_Name.field_Name - Sends only the field of the incoming Data Structure on the output port. o Destination_Name.memory_Name - Sends the value in a specific memory location on the output port. The entire Destination_Name can be a concatenation of any number of individual strings and parameters, separated by "+". Each value will be processed first as a parameter and then as a string. The values will be concatenated to a single string that will be used as the destination name.	String	Dest_or_Dest.Fld_or_Dest.Mem
Destination_Type	This can be local or global. Local means a connection within the current Block Dioagram Window. Global means the entire model. The matching sender must also be of type local or global for a match.	-	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: Free Qt Help documentation generator