Creating jobs

versiondog allows you to create jobs and make regular checks to see whether any changes were made to the program running on the device. You can also use jobs to schedule routine backups of the program.

1. Start the AdminClient and open the Jobs module.
2. In the Project tree, select the KUKA KR C4component.
3. In the menu tab, click on Createor drag-and-drop the components into the Jobs section.
4. In the Job configurationsection, check whether the upload type KUKA Robotis being displayed.
5. Make sure the desired settings are in place for the following sections: General, Notification, Upload and compare, and Create a version automatically after job run. The Notificationand Create a version automatically after job runsections are only displayed if the necessary settings have been implemented. For more information on configuring these general sections, see the Module: Jobs, located in the AdminClienttutorial.

1. Configure the KUKA robot settingssection. 1. In Type, select KRC4. 1. Enter the Device name / IP address that you want to create a job for. !!! note If the UNC path is KukaRobot5Backupversiondog, then you will need to enter KukaRobot5. 1. In Path to the project, enter the name of the shared folder in which you wish to store your backups.

   Note

   If the UNC path to the shared folder is called KukaRobot5Backupversiondog, then the “Backup” (without ) must be entered. 1. In Subdirectory, enter the name of the subdirectory in which you wish to store backups.

   Note

   If the UNC path to the share is called KukaRobot5Backupversiondog, then versiondog (without ) must be entered here. If the UNC path is KukaRobot5Backup (without a subdirectory), this field will remain empty. 1. In User, enter the name of the domain, user, or computer that you wish to use to access the network share. 1. In Password, enter the password. 1. In Fail if project is older than, specify a time period that is allowed to occur before a warning is generated due to a backup not being created.

2. In the Advanced section, you will find the old upload method with NetworkConnectivity and other options:

Additional options

Use the Sleep interval between data packets (in ms) and Maximum size of data packets (in KB) settings to limit network traffic.

The process of creating a backup using NetworkConnectivity

1. versiondog creates a trigger file and stores this in the configured network archive share.
1. **NetworkConnectivity**places a new backup of the version on the robot and deletes the trigger file from the network share.
1. **NetworkConnectivity**places a ZIP archive in the backup directory.
1. versiondog copies the ZIP archive to the server archive.
1. versiondog deletes the old ZIP archive in the backup archive (optional).
1. In **Limit the backup count on the robot**, specify how many backups should be retained on the robot. When the max number of backups is reached the oldest backup will be deleted.
1. In **Trigger file resource**, enter the name of the network share in which you want the trigger file for **NetworkConnectivity** to be created.
1. In **Trigger file path**, enter the subdirectory and the file name under which you wish to create the trigger file for **NetworkConnectivity**.
1. In **Create backup via NetworkConnectivity**, specify whether you want to keep the newly created backup on the robot or on the versiondog server.
1. When you activate **Create backup via NetworkConnectivity**, the backup of the program running on the robot will generated by **NetworkConnectivity**.
1. In **Keep the newly created backup on the robot**, specify whether you want to retain the newly created backup after the job execution or whether you want to delete it.

1. Save the job and execute it.

Jobslist, you can use drag-and-drop to apply comparator settings to other jobs.–8<– “Timeout.md”

Related Topics

• AdminClient -> Job configuration
• Integrating robots
• AdminClient -> INI files