Implementation of the sample

The PLC page adopted by TcCOM Sample 01. The function block registered there as TcCOM module offers the object ID allocated to it as an output variable.
It is the C++ module’s task to make the offered interface of this function block accessible.

A C++ project with a Cycle IO module is assumed.

1. In the TMC editor, create an interface pointer of the type I_Calculation with the name Calculationn). Later access occurs via this.
Implementation of the sample 1:

2. The Data Area Inputs have already been created by the module wizard with the type Input-Destination. Here in the TMC editor you create an input of the type OTCID with the name oidProvider, via which the Object ID will be linked from the PLC later. Implementation of the sample 2:

3. All other symbols are irrelevant for the sample and can be deleted.

The TMC-Code-Generator prepares the code accordingly.
In the header of the module some variables are created in order to carry out the methods calls later.
Implementation of the sample 3:

In the actual code of the module in CycleUpdate() the interface pointer is set using the object ID transmitted from the PLC. It is important that this happens in the CycleUpdate() and thus in real-time context, since the PLC must first provide the function block.
When this has taken place once, the methods can be called.
Implementation of the sample 4:

In addition, as can be seen above, the interface pointer is cleared when the program shuts down. This happens in the SetObjStateOS method.

4. Now build the C++ project.

5. Create an instance of the module.

6. Connect the input of the C++ module to the output of the PLC.
Implementation of the sample 5:

The project can be started. When the PLC is running, the OID is made known through the mapping to the C++ instance. Once this has occurred, the method can be called.