Restrictions - Manual - TIA2ST - A CLI tool to import TIA Portal project data into a SIMATIC AX project. - TIA2ST - Convert parts of TIA Portal projects to ST code,tool

This chapter summarizes the restrictions which are limiting the import-db command:

1. TIA Portal version V18 or later is supported.

2. The "coupling DB" must be stored in non-retained (volatile) memory.
   Therefore, following attributes must be defined in the TIA Portal project in the settings of the "coupling DB":

   • "Optimized block access" must be set
   • "Only store in load memory" must not be set
   • Memory reserve (for "Download without reinitialization") should be set to zero.

   It must not contain any members in the retained or classic memory.

3. A "coupling DB" can contain following data types and arrays of these data types:

   • BOOL
   • signed and unsigned numeric types (e.g. INT, UDINT, LWORD)
   • float numbers REAL and LREAL
   • string types (e.g. CHAR, WCHAR, STRING, WSTRING)
   • long date/time types (e.g. LTIME, LDATE, LTIME_OF_DAY, LDATE_AND_TIME)
   • UDTs (User-defined Data Types)
   • Motion Control system data types like PD_TEL* and TO_Struct* if a Motion Control system library is referenced in the apax.yml file.
     Because a "coupling DB" must always be stored in volatile memory the tool switches automatically to the variants of telegram data types PD_TEL*_opt suitable for this memory area.

4. An instance DB (IDB) of an UDT (User-defined Data Types) or a FB is not supported.
   Such data blocks will be ignored automatically without notice.

5. At present, there is no support for the llvm target. As a result, unit tests via AxUnit-ST can only be executed on S7-PLCSIM (Advanced) or a real S7-1500 PLC. For both use the target is "1500".