Documentation issue status

Version

Changes

2.6.x

Overview:

  • Export the TwinCAT 3 configuration as a Functional Mock-up Unit (FMU) and integrate it into Simulink® using the FMU import feature; see the overview “Example 2a: SiL Simulation of system components”.
  • A more detailed description of the typical workflow and integration paths in TwinCAT 3 Engineering.

System requirements on the engineering PC and the runtime PC have been updated; see Installation.

Initial setup of the software updated.

NEW: TwinCAT Library in Simulink® > TwinCAT Event Block

Additions to Overview table of all configuration parameters

Additions to Available placeholders

Application of modules in TwinCAT:

  • Manual analysis of exceptions (without source code): Starting with TwinCAT 3.1.4024.22 (XAR), it is possible to access the TwinCAT Task Dump, depending on the exception settings.
  • Fine-grained live debugging in C++ source code updated

Examples updated

Addition of Third-party components

2.5.x

Examples: “Try out created TwinCAT objects yourself”: New ZIP file for Build 4026

2.4.1

Examples: “Try out created TwinCAT objects yourself”: ZIP file for Build 4026 added

2.4.x

NEW: Pack’N Go function, see Build on a system without MATLAB® (Build Agent)

TwinCAT File Writer: new parameter “Close opened file on Pause”

General information:

  • TwinCAT OS (x64): platform to be selected for execution with the TwinCAT Usermode Runtime
  • The same TwinCAT major build is required on both the runtime and engineering systems, see System requirements.

2.3.x

To set up driver signing using the Software Protection UI, see Setting up driver signing.

2.2.x

TwinCAT 3.1 Build 4026

  • Brief information on installation
  • Updating the system requirements

Convert Simulink® model into TwinCAT object: New sample (see end of chapter) to deepen your knowledge

Revised/extended table of configuration parameters

NEW: Build for different platforms

NEW: Automatic updating of objects in a TwinCAT project

Revisions in section Online Change of TcCOM

NEW: Instruction Set Extensions

Revised/extended table of available placeholders

NEW: Post deploy callback function, see Working with Callbacks.

New code samples for referencing a static module instance or dynamic instantiation and referencing from the PLC, see Applying the TcCOM Wrapper FB.

New: The Simulink® Coder™ can translate a Simulink® string into the data type std::string, for details see FAQ/Using Simulink® Strings.

FAQ/troubleshooting on the topic “DataExchange modules cannot be loaded”.