SINAMICS converters: Creating jobs

In versiondog , you have the option to execute jobs according to a schedule. These check as to whether a program matches the last checked in on the device or whether the newest version has been implemented on the device. It is also possible with versiondog to use jobs to create a backup of a device.

The following needs to be taken into account for Siemens SINAMICS converter device uploads:

• One mandatory requirement for an upload is an S7 project, in which the SINAMICS devices are integrated.
• The VDogMasterservice or Agent must be started from the command line as application (not as service).

To do this, enter one of the following commands (depending on your use case):

Example for the server:

"C:\Program Files (x86)\vdogServer\VDogMasterService.exe” /at:s /rd:D:\vdServerArchive /app

Example for the Agents:

"C:\Program Files (x86)\vdogAgents\VDogCompareAgent.exe" /at:s /rd:D:\vdAgentArchive /app "C:\Program Files (x86)\vdogAgents\VDogUploadAgent.exe" /at:s /rd:D:\vdAgentArchive /app

Before VDogMasterservice or the agents can be started as an application, you have to end the service of VDogMasterService or the agent services (VDogUploadAgent and VDogVCompareAgent), for example: using the task manager. Afterwards, the services should also be deactivated in Windows so that it doesn't start up again once the computer has been restarted. You can automate the process of running as an application by adding a batch file to the Autostart folder.

 

• The upload works both with the editors SIMOTION MICROMASTER STARTER and SIMOTION SCOUT.
• The upload and comparison must be done with the same editor that was used to create the project.
• SIMOTION MICROMASTER STARTER or SIMOTION SCOUT must be installed and licensed on the computer on which the upload is executed.
• Both programs cannot be installed on one computer at the same time. If the user has both project types, then upload and compare agents must be used.
• It is not possible to execute multiple upload jobs for SINAMICS at the same time.
• During the restore process, the AppLogfile.txt file will be moved into the directory in addition to the S7 project. This is generated by SIMOTION MICROMASTER STARTER / SIMOTION SCOUT and contains detailed information about the upload.
• No upload can be performed for devices of the type IO-Device.

How to configure jobs for Siemens SINAMICS converters:

1. Start the AdminClient and open the jobs module.
   
2. In the Project tree, select the Simatic S7 component.
3. In the menu tab, click on Create or drag & drop the components into the Jobs section.
4. Check in the section job configuration, if the upload type Sinamics 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, please refer to jobs in the tutorial AdminClient.
   
6. Configure the Sinamics settings.
   1. Under Project, select from the drop-down menu the SINAMIC project. This step is only required if more than one SINAMIC project is present in the component.

The backup that you create is identical to the SINAMICS project. You can use the result to carry out a detailed comparison as well as a disaster recovery and edits.

If a DCC plan folder is versioned and checked in the offline project and not copied to the SINAMICS converter (the folder is therefore not available online), the DCC plan folder will appear after execution of the backup job for the new version of the data stored in the new backup.

Configuring a timeout

When uploading large amounts of data, a timeout may occur despite the default time being preset at 30 minutes. This timeout can be adjusted globally for all upload types or for each upload type separately. To adjust the maximum time for job execution according to the upload type, proceed as follows:

1. Start the AdminClient and open the Jobs module.
2. In the menu, click on Global job settings.
3. The Upload specific configuration window will then open.
4. Select the upload type in the navigation bar on the left.
5. Select the Use specific timeout for this upload type checkbox.
6. In the Maximum time for job execution field, enter the time period in minutes. The maximum possible value is 540 minutes.

If you do not select the Use specific timeout for this upload type checkbox, the next time you change the global timeout, the value set here will be overwritten by the global one.

Alternatively, you can adjust the timeout via the INI file Classes.ini . (Go to the path in the server or agent archive:..\VD$A\Configuration\Upload\Classes.ini).

The value entered in the Upload type specific configuration window will then be copied into the INI file.

FAQ: Why does a SINAMICS upload job still end with the error message cancelled due to timeout even though the editor is correctly installed? For the SINAMICS upload job to run without errors, the following requirements must be met: For the connection between editor and device, the interface in the editor must be set correctly. The editor must have established an online connection with the device at least once. To FAQ list

 

Configuring a timeout

When uploading large amounts of data, a timeout may occur despite the default time being preset at 30 minutes. This timeout can be adjusted globally for all upload types or for each upload type separately. To adjust the maximum time for job execution according to the upload type, proceed as follows:

1. Start the AdminClient and open the Jobs module.
2. In the menu, click on Global job settings.
3. The Upload specific configuration window will then open.
4. Select the upload type in the navigation bar on the left.
5. Select the Use specific timeout for this upload type checkbox.
6. In the Maximum time for job execution field, enter the time period in minutes. The maximum possible value is 540 minutes.

If you do not select the Use specific timeout for this upload type checkbox, the next time you change the global timeout, the value set here will be overwritten by the global one.

Alternatively, you can adjust the timeout via the INI file Classes.ini . (Go to the path in the server or agent archive:..\VD$A\Configuration\Upload\Classes.ini).

The value entered in the Upload type specific configuration window will then be copied into the INI file.

---