RSLogix 500: Creating jobs for SLC 500 or MicroLogix

How to save to a SLC 500 or a MicroLogix in versiondog :

  1. Start the AdminClient and open the Jobs module.
  2. In the Project tree, select the RSLogix500 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 RSLogix 500 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 settings in the RSLogix 500 settings section

  7. Image: Job Configuration, RSLogix 500 Settings section

    1. The RSLogix 500 project’s RSS file should have been automatically selected. This is located under Project. If this is not the case, select this file from the drop-down list.
    2. In Communications path, enter the gateway data. The way to do this is dependant on the software that you are using (RSLinx or Factory Talk Linx):
    3. If you updated RSLogix Enterprise Edition via FactoryTalk Linx, you will need to enter the communications path manually:

      Proceed as follows:

      1. Open the FactoryTalk Linx Browser tool and right click on the project. This will in turn open the project’s configuration.
      2. Here, copy the path of the device path. This can be, for example, RSLinx Enterprise!Ethernet\ (The RSLinx Enterprise! part of the path is optional.)
      3. Enter the path into the communications path field. This is located in the job configuration.

      If you are using RSLinx Classic and are using it on the same machine as your versiondog server,

      Proceed as follows:

      1. In order to select the path to the PLC, click on Search in Communications path.
      2. Communications path will open. Select the PLC of the job that you want to save.
      3. Click on save and test the job by clicking on Execute selected jobs once.

      If you are using RSLinx Classic and are not using it on the same machine as your versiondog server:

      Proceed as follows:

      1. Enter the path to the PLC manually. The path can be found in RSLinx. The path has the following format: xxx!yyy.
        • xxx is the name of the computer running RSLinx Classic.
        • yyy is the name of the configuration for the PLC in RSLinx Classic.
        • Do not forget the Separator !between both parts of the path.


      1. Open RSLogix 500.
      2. Double click on Controller properties in the project tree.
      3. Open Controller communications.
      4. Copy the text Comms path.
      5. Enter the text into the section access path. This is located in the job configuration in the AdminClient.

      6. Image: RSLogix 500 Editor, Dialog Controller Properties

    4. If the project is password protected, enter the necessary password in the Controller Password section.
    5. To be able to process password protected projects, the editor needs to be opened in English.

    6. By clicking on Warn when forced values are active, you can decide if you want to have a warning displayed when forced values are active in your project.
    7. A displayed warning can be useful. This can, for example, be useful when using manual control at your facilities and there is the chance that the forced values could be overseen.

  8. Click on save and test the job by clicking on Execute selected jobs once.

The job result (Backup) can be used for a detailed comparison, a disaster recovery and further processing.

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.
  7. 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 the upload freeze when I upload a password protected RSLogix 500 project?

versiondog remotely steers the editor when uploading a project and enters the password when required. It may be necessary to run versiondog under the system account and with the option Allow data exchange between service and desktop(user interactivity) activated.

Proceed as follows:

  1. Open the Windows start menu.
  2. In the search field, enter Execute and then click Enter.
  3. In the text field Open, enter services.msc.
  4. Double click on VDogMasterService / VDogUploadAgent.
  5. Go to the Log On tab.
  6. If required, incorporate the following settings from the screenshot below:
  7. Image: Properties of <service>, Login tab

  8. In the Windows Registry, in the path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows, change the value for the entry NoInteractiveServices to 0.
  9. Restart the service VDogMasterService / VDogUploadAgent.

To FAQ list