System
License

Licenses may be excluded from the project under the following conditions:
Number | Context | Exclusion option |
|---|---|---|
TC1200 | PLC project | / |
TF2000 | TwinCAT HMI | Remove manually from the license list and do not use a TwinCAT HMI server. Not recommended, as PlasticApplication is primarily designed for TwinCAT HMI. |
TF5000 | Electric NC axes | Removing NC task under MOTION. |
TF5050 | Electric NC transformer axes | Removing NC transformer axes from the PLC. |
TF5810 | Hydraulic axes | Remove the hydraulic axes from the PLC. The Tc3_PlasticBaseApplicationElectric library avoids a required reference |
TF8540 | Temperature control | Remove the instance of |
TF8550 | Plastic HMI Controls | Remove manually from the license list and do not use any Plastic NuGet packages in the HMI. |
TF8560 | Plastic technology functions | Remove all TF8560 axes and machine data components. The license can only be avoided if individual FBs of
|
Tasks

The four created tasks follow the following strategies:
- AdministrativeTask - General control tasks of medium priority
- Standard cycle time: 10 ms
- Calling the HMI <> PLC Recipe communication
- Storage and loading routines
- Communication commissioning tool of hydraulic axes
- Cyclic processing of application routines like: manual functions, process sequence, etc…
- MotionTask - Real-time critical routines
- Standard cycle time: 2 ms (= NC task)
- Cycle methods of the motion axes
- Internal control mechanisms
- TemperatureTask - Inertial temperature control
- Standard cycle time: 25 ms
- Calling the temperature control
- SimTask -Simulation
- Standard cycle time: 2 ms
- Calling the cycle methods of the simulation
Notice | |
Correct cycle time for temperature control The cycle time of the temperature control should be asynchronous to the frequency of the AC supply voltage. A synchronous cycle time promotes instability of the control! |
Real time

In principle, systems from TwinCAT 3 platform level 50 Performance Plus are the minimum requirement for the PlasticApplication. The PLC tasks can be split according to the number of cores and the single core performance of the CPU. For development systems, the project configuration can be adopted; for end devices, the following configurations have been tested in the field:
CP/ IPC / CX | BMM | IMM | EXTR | TEMP |
|---|---|---|---|---|
✅ | ||||
🆗
| ✅ | |||
❌ | 🆗 - Not for new projects | ✅ | ||
✅ - Recommended without restrictions
🆗 - Recommended with restrictions
❌ - Not recommended
Type system

The Type System contains the used EventClasses. These EventClasses contain the respective events that are used in the Plastic Application.