Integrating RSLogix 500 into versiondog
versiondog supports programmable logic controllers working with the RSLogix 500 software (SLC™ 500 and MicroLogix™ product families) and enables the cyclic monitoring of devices designed using this development environment.
Network diagram
System requirements
| From versiondog version |
RSLogix 500 | |||
|---|---|---|---|---|
|
V 9.x |
V 10.x |
|||
| 3.2 | ✓ | |||
| 4.1 | ✓ | ✓ | ||
Other requirements
- The software RSLogix 500 Professional Edition (version 9.x or version 10.x) needs to be run on the computer on which the versiondog server is running. If the software is running on a different computer, you will require a versiondog Agent.
- Either RSLinx Classic (version 3.51 or higher) or FactoryTalk Linx (version 5.51 or higher) will need to be run on the computer on which the versiondog server is installed. FactoryTalk Linx was previously known as RSLinx Enterprise Edition. If the software is running on a different computer, you will require a versiondog Agent.
-
When upgrading FactoryTalk Linx, you will need to uninstall the RSLinx Classic software and enter the access path manually. This is located in Job configuration.
If you are using versiondog Agents when carrying out a FactoryTalk Link upgrade, you will need to be ensure that all Agent related tasks are carried by an administrator.
-
System requirements for RSLogix 500 can be found on Rockwell’s website.
Key features and functions
|
Integrated RSLogix 500 project tree |
✓ |
| SmartCompare for RSLogix 500 projects (version comparison) | ✓ |
| Automatically detection of differences between the program running on the device and the latest version on the server (Backup-detail comparison, version/backup - detail comparison) | ✓ |
| Detailed graphical comparison | ✓ |
| Support for RSLogix 500 multi projects | ✓ |
| Clear presentation of complete change history | ✓ |
| Automatic backup for disaster recovery | ✓ |
| Custom component type for RSLogix 500 | ✓ |
In this tutorial:
Last updated: 20 October 2020