Object

• Object Id: The object ID used for identifying this instance in the TwinCAT system.
• Object Name: Name of the object used for displaying the instance in the Solution Explorer tree.
• Type Name: Type information (class name) of the instance.
• GUID: Module classes GUID.
• Class Id: Class ID of the implementation class (GUID and ClassId are usually identical).
• Class Factory: Refers to the driver, which provides the Class Factory that was used for the development of the module instance.
• Parent Id: Contains the ObjectID of the parent, if available.
• Init Sequence: Specifies the initialization states for determining the startup behavior of the interacting modules. See here for detailed description of the state machine.

Specifying the startup behavior of several TcCOM instances

TcCOM instances can refer to each other - e.g. for the purpose of interaction via data or interface pointers. To determine the startup behavior, the Init Sequence specifies states to be "held" by each TcCOM instance for all other modules.

The name of an Init Sequence consists of the short name of the TcCOM state machine. If the short name of a state (I, P, S, O) is included in the name of the Init Sequence, the modules will wait in this state, until all other modules have reached at least this state. In the next transition the module can refer to all other module instances, in order to be in this state as a minimum.

If, for example, a module has the Init Sequence "PS", the IP transitions of all other modules are executed, so that all modules are in "Preop" state.

This is followed by the PS transition of the module, and the module can rely on the fact that the other modules are in "Preop" state.

• Copy TMI to target: Generating the TMI (TwinCAT Module Instance) file and transferring it to the target.