Architecture

In the figure below, the TwinCAT HMI Process Library is shown in relation to the other TwinCAT components. This information is more comprehensive than in the System architectures chapter. It does not include all TwinCAT components, but it gives an idea of the TwinCAT HMI Process Library's operation and interactions.

The TwinCAT HMI Process Library is an extension of TwinCAT HMI. TwinCAT HMI Engineering and TwinCAT HMI Server must be used respectively to develop and run projects which use the library.

The TwinCAT HMI Process Library gets events from TwinCAT EventLogger, which is why it needs these components:

• TwinCAT HMI EventLogger to show events in HMI and get events from the EventLogger
• (optional) TwinCAT EventLogger library at PLC level to generate and get events from the EventLogger
• TwinCAT EventLogger Service on a Runtime to handle events at OS level

The TwinCAT HMI Process Library can draw charts using the TwinCAT Scope functionality. To do this, it needs the following options:

• TwinCAT HMI Scope
• TwinCAT Scope View on the Engineering side to create and configure charts
• TwinCAT Scope Server Service to handle the Scope data at OS level

TwinCAT MTP Runtime is optional. It provides standardized FBs for technological equipment. If it is used, two more components should be added:

• TwinCAT MTP Runtime itself
• (optional) TwinCAT Controller Toolbox to implement the PID controller that TwinCAT MTP Runtime uses. Other FBs implementing PID functionality can also be used.

The TwinCAT HMI Process Library can be used to create local HMIs for systems which are controlled by POL/DCS. The image below shows the architecture a system like this:

For more information, see the TE8400 | TwinCAT 3 MTP Engineering and TF8400 | TwinCAT 3 MTP Runtime documentation.