Main Content

Files Generated by Simulink PLC Coder

The Simulink® PLC Coder™ software generates Structured Text code and stores it according to the target IDE platform. These platform-specific paths are default locations for the generated code. To customize generated file names, see Specify Custom Names for Generated Files.

PlatformGenerated Files

3S-Smart Software Solutions CoDeSys 2.3

current_folder\plcsrc\model_name.exp — Structured Text file for importing to the target IDE.

3S-Smart Software Solutions CoDeSys 3.3

current_folder\plcsrc\model_name.xml — Structured Text file for importing to the target IDE.

3S-Smart Software Solutions CoDeSys 3.5

current_folder\plcsrc\model_name.xml — Structured Text file for importing to the target IDE.

B&R Automation Studio® IDE

The following files in current_folder\plcsrc\model_name — Files for importing to the target IDE:

  • Package.pkg — (If test bench is generated) Top-level package file for function blocks library and test bench main program in XML format.

In the main folder (if test bench is generated):

  • IEC.prg — Test bench main program definition file in XML format.

  • mainInit.st — Text file. Test bench init program file in Structured Text.

  • mainCyclic.st — Text file. Test bench cyclic program file in Structured Text.

  • mainExit.st — Text file. Test bench exit program file in Structured Text.

  • main.typ — Text file. Main program type definitions file in Structured Text.

  • main.var — Text file. Main program variable definitions file in Structured Text.

Beckhoff® TwinCAT® 2.11

current_folder\plcsrc\model_name.exp — Structured Text file for importing to the target IDE.

Beckhoff TwinCAT 3

current_folder\plcsrc\model_name.xml — Structured Text file for importing to the target IDE.

KW-Software MULTIPROG® 5.0

current_folder\plcsrc\model_name.xml — Structured Text file, in XML format, for importing to the target IDE.

Phoenix Contact® PC WORX™ 6.0

current_folder\plcsrc\model_name.xml — Structured Text file, in XML format, for importing to the target IDE.

Rockwell Automation® Studio 5000 IDE: AOI

current_folder\plcsrc\model_name.L5X — (If test bench is generated) Structured Text file for importing to the target IDE using Add-On Instruction (AOI) constructs. This file is in XML format and contains the generated Structured Text code for your model.

Rockwell Automation Studio 5000 IDE: Routine

current_folder\plcsrc\model_name.L5X — (If test bench is generated) Structured Text file for importing to the target IDE using routine constructs. This file is in XML format and contains the generated Structured Text code for your model.

In current_folder\plcsrc\model_name (if test bench is not generated), the following files are generated:

  • subsystem_block_name.L5X — Structured Text file in XML format. Contains program tag and UDT type definitions and the routine code for the top-level subsystem block.

  • routine_name.L5X — Structured Text files in XML format. Contains routine code for other subsystem blocks.

Rockwell Automation RSLogix™ 5000 IDE: AOI

current_folder\plcsrc\model_name.L5X — (If test bench is generated) Structured Text file for importing to the target IDE using Add-On Instruction (AOI) constructs. This file is in XML format and contains the generated Structured Text code for your model.

Rockwell Automation RSLogix 5000 IDE: Routine

current_folder\plcsrc\model_name.L5X — (If test bench is generated) Structured Text file for importing to the target IDE using routine constructs. This file is in XML format and contains the generated Structured Text code for your model.

In current_folder\plcsrc\model_name (if test bench is not generated), the following files are generated:

  • subsystem_block_name.L5X — Structured Text file in XML format. Contains program tag and UDT type definitions and the routine code for the top-level subsystem block.

  • routine_name.L5X — Structured Text files in XML format. Contains routine code for other subsystem blocks.

Siemens® SIMATIC® STEP® 7 IDE

current_folder\plcsrc\model_name\model_name.scl — Structured Text file for importing to the target IDE.

current_folder\plcsrc\model_name\model_name.asc — (If test bench is generated) Text file. Structured Text file and symbol table for generated test bench code.

Siemens TIA Portal IDE

current_folder\plcsrc\model_name\model_name.scl — Structured Text file for importing to the target IDE.

Generic

current_folder\plcsrc\model_name.st — Pure Structured Text file. If your target IDE is not available for the Simulink PLC Coder product, consider generating and importing a generic Structured Text file.

PLCopen XML

current_folder\plcsrc\model_name.xml — Structured Text file formatted using the PLCopen XML standard. If your target IDE is not available for the Simulink PLC Coder product, but uses a format like this standard, consider generating and importing a PLCopen XML Structured Text file.

Rexroth IndraWorks

current_folder\plcsrc\model_name.xml — Structured Text file for importing to the target IDE.

OMRON® Sysmac® Studio

current_folder\plcsrc\model_name.xml — Structured Text file for importing to the target IDE.