How do I resolve data type conflicts in the PLC project?

If inputs, outputs, parameters or state variables of a Simulink model are changed, the corresponding data types in the TwinCAT module generated from it also change. After the update, the data types have the same name but a different GUID. The type system of the TwinCAT development environment (XAE) can manage several data types of the same name with different GUID. However, a PLC project is not allowed to have several data types with the same name.

Especially after a module instance has been updated via "Reload TMC", several data types of the same name may exist in the type system, of which typically only the type related to the currently instantiated module class should be used. In some cases the user has the specify manually which of the data types should be available in the PLC project, particularly if PLC function blocks generated by the TE1400 are used.

To this end, the data type editor can be started via the context menu of the type to be used in the table SYSTEM > Data types:

By adding Datatype Hides, you can selectively exclude obsolete data types from being used in PLC projects: