Project tab
Project Name | Name of the PLC project |
Id | ID of the PLC project |
Project Path | Path to the location where the PLC project is stored |
Project Type | Project type |
Port | AMS port number of the runtime system |
Project Guid | GUID of the PLC project |
Encryption | Encryption of the boot project
|
Autostart Boot Project | After the TwinCAT runtime environment has been started, the PLC boot project is automatically loaded and started. The setting is transferred directly to the currently selected target system. The setting is not saved in the TwinCAT project. This option corresponds to the Autostart Boot Project command in the context menu of the PLC project node in the Solution Explorer. |
Symbolic Mapping | Symbolic mapping is enabled. |
Force Multi Instance | Option for logging in multiple instances of the PLC project enabled. |
Comment | Comment box |
Compiler Defines (available from TC3.1 build 4024) | |
Manual | Here you can define your own compiler definitions at System Manager level, which are passed on to the PLC project. The definitions are entered in the PLC project properties under the category compile as system compiler definitions. |
Implicit | The names of the selected project variants as well as all groups to which the project variant belongs are automatically set as a compiler definition and passed on to the PLC project. The definitions are entered in the PLC project properties under the category compile as system compiler definitions. Note: In order to activate this checkbox, the Defines for the variant management must be enabled. |
See also:
- Variant management: Concept: Integration in the PLC project
- Command properties (PLC project): Category Compile: System compiler definitions