dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorProgramming with CODESYSdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorCODESYS Development Systemdl-breadcrumb-item__separatorDownloading an Application to the PLCdl-breadcrumb-item__separatorGenerating boot applications
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Generating boot applicationsdl-permalink__symbolPermalink

A boot application is the application that is started automatically when the controller is switched on or started. For this to happen, the application on the controller must exist as a file ‎<application name>.app‎.

For each application that is running on the controller, a boot application can also be saved there.

By default, CODESYS generates the boot application automatically when an application is downloaded and transfers them to the PLC. The defaults for generating automatically are located in the “Boot application” category of the application “Properties”. When logging in with a changed application, you are still prompted whether or not to generate a new boot application.

In addition, you can create a (new) boot application at any time in online mode by clicking “Online  Create boot application”.

You can create and save a local copy of a boot application in offline mode as well. Then, you can copy this application to the controller with external tools. In this way, you transfer an application to the controller, even when there is no connection to CODESYS.

Generating boot applications on the controller automatically and explicitly

Requirement: Offline mode; the application is compiled without errors. The connection to the controller is configured and the controller is running. The application is active. The following steps demonstrate the options:

  1. Click “Online  Login”.

    The boot application file ‎<application name>.app‎ is created on the controller with the checksum of the boot application ‎<application name>.crc‎.

  2. Click “Online  Create Boot Application” explicitly.

    The files on the controller are replaced by new files.

  3. Log out.

  4. Change the application. Log back in to the controller.

    You are prompted whether an online change should be performed. You see the “Update boot application” check box in the same dialog box. This is cleared by default, but this can be changed in the “Boot Application” category of the application “Properties”.

  5. Keep the check box cleared and continue login.

    A new boot application file is not created.

  6. Log out. Close the project. Stop the controller. Restart the controller.

    The boot application that was created above is running on the controller.

You can save the encrypted boot application on the controller. These settings are defined in the “Application Build Options” category of the application “Properties”.

See also

Creating boot applications in offline mode

Requirement: Offline mode; the application is compiled without errors. You want to generate a boot application for an application and save it in the file directory for copying it later to the controller by using external tools (without CODESYS).

  1. Click “Online  Create Boot Application”.

    A dialog box opens for specifying a save location in the local file system.

  2. Click a save path and then click “Save”.

  3. If the application has changed since the last boot application was generated, then you are prompted to use a new code for the boot application. In this case, click “Yes”.

    The “Save as” dialog box opens.

  4. Select a directory and click “Save”.

    The boot application file <application name>.app is created in the given path.

    You are prompted whether or not the build information for the boot application is saved.

  5. Click “Yes”.

    The build information is saved to the project directory as a file named ‎<application name>.compileinfo‎. It is a requirement for a possible online change the next time the application is updated. Please note: Clicking “Build  Clean” deletes this file.