Creating jobs

Requirements

A valid installation of STEP 5

• On the computer on which the versiondog server is installed, or (if this is not possible)
• On a computer that can be accessed by the versiondog server applications via an agent.

To create jobs for S5 controllers:

1. Start the AdminClient and open the Jobs module.
2. In the Project tree, select the Schneider S5 component.
3. In the menu tab, click on Create or drag-and- drop the components into the Jobs section.
4. Check in the section Job configuration, if the upload type SIMATIC S5 is being displayed.
5. Make sure the desired settings are in place for the following sections: General, Notification, Upload and compare, Create a version automatically after job run. The Notification and Create a version automatically after job run sections are only displayed if the necessary settings have been implemented. For more information on configuring the general sections, see Jobs in the tutorial AdminClient.

6. Configure the SIMATIC S5 settings section

   1. For the S5 Program path, select the project file (S5D) for which you want to execute the job

      You can only select project files that have been checked-in in the selected component. If only one project file is present, then this will be selected automatically.

   2. Select the Access path you want to use for communication with the controller.

      Information regarding possible access paths and other related options can be found under: Configuring the access path for S5 devices

7. Configure the section Access path details

   Depending on the Access path you have chosen, other information fields may be available. Information regarding possible access paths and other related options can be found under: Configuring the access path for S5 devices

8. Configure the Backup section.

   1. If required, specify which blocks should not be included in the upload and compare for this job.

9. Configure the section Advanced.

   1. Specify how many repeats to carry out if the upload of a block fails.

      This may occur if the controller tries to access a block while a job is being executed and the block is locked as a result. Saving is however still possible if the block has been unlocked during a retry. Values between 0 and 5 are possible. If the block cannot be accessed during any of the repeat attempts, then the job will be aborted and an error message displayed.

   2. If necessary, change the sleep interval between data packets to reduce the network load caused by the job.

      Values between 0 and 5000 ms are possible.

10. Save the job and execute it.

 

You can make further settings for jobs of this upload type in the AdminClient by using the Global Job Settings dialog as well as the INI files.

 

Related topics:
About versiondog -> Term Jobs
AdminClient -> Job configuration
Configuring the access path
AdminClient -> Adding additional job settings
INI files configuration

---