Software Migration: RSLogix to Studio5000

Summary

This tutorial guides users through the process of migrating a Slick or PLC 5 application from RS Logix 500 to Studio 5000 Logix Designer. It covers key steps such as saving the program as a Logix Designer ACD file, configuring the controller platform, handling I/O migrations, and managing tag descriptions. The video also addresses the need for manual updates or CSV imports to transfer I/O comments efficiently. Viewers are encouraged to clean up the program and seek assistance from local specialists if needed. This concise guide ensures a smooth migration while retaining crucial data and configurations.

Takeaways

• 😀 RS Logix 500 version 12 introduces a built-in migration utility for converting Slick or PLC 5 code to Studio 5000 Logix Designer.
• 😀 The migration tool allows you to convert Slick application files to Logic Designer files by selecting 'Save Program As' and choosing the ACD file type.
• 😀 Prior to version 12, the RS Logix Project Migrator was a separate download, but version 12 integrates the migration utility into the software.
• 😀 Before migrating, it's essential to clean up the Slick application by removing unused memory addresses or routines.
• 😀 The migration tool can replace legacy hardware with updated IO modules, like switching to the 5069 processor, and allows you to select the revision you're using.
• 😀 Analog combo modules in Slick (which don't have direct equivalents in 5069) should be replaced with placeholder tags during migration.
• 😀 After migration, you can replace placeholder tags with the corresponding IO channels in the 5069 system.
• 😀 The migration tool supports options to handle chassis configurations and IO module replacements, making the process smooth for hardware updates.
• 😀 Post-conversion, address comments for various elements, like timers and integers, transfer correctly to the new tag structures in Logic Designer.
• 😀 You can accelerate the process of copying tag descriptions by exporting them to a CSV file, adjusting them in Excel, and re-importing them into the new system.
• 😀 Once all the descriptions are properly transferred, the last step involves cleaning up untranslatable instructions or errors that may appear after the migration.

Q & A

What is the purpose of this tutorial?

This tutorial aims to demonstrate how to migrate an RS Logix 500 application file to Studio 5000 Logix Designer, using the built-in migration tool in RS Logix 500 version 12 and later.

What should be done before starting the migration process?

Before starting the migration, it's important to remove any unused memory addresses or routines in the RS Logix 500 file to ensure a smooth conversion process.

What is the role of the migration wizard in the process?

The migration wizard, triggered when you save the file as a Logix Designer file, guides you through the configuration of the migrated application, ensuring it is set up correctly in Studio 5000.

What controller platform is used in this tutorial for the migration?

In this tutorial, the 5069 processor is used as the controller platform for the migration, but other processors can be selected as needed.

What does the 'Update All IO' option do during migration?

The 'Update All IO' option helps migrate the existing IO configuration by automatically selecting replacement IO modules. It simplifies the migration of hardware by updating all IO points at once.

What should be done for analog input-output combo modules during migration?

For analog combo modules that don't have an equivalent in the 5069 range, you should select 'Create Placeholder Tags.' These tags can be replaced later with the corresponding channels on the 5069 IO modules.

Why might the migration process take some time?

The migration process may take some time because the utility needs to convert and map all the configurations, IO settings, and other data to the new Studio 5000 project structure.

What happens to the address comments for bits, timers, and counters after the migration?

After the migration, address comments for bits, timers, counters, and other data files are transferred into the tag structures in Studio 5000, helping maintain the logical structure of the program.

What is the significance of Alias tags in this migration?

If Alias tags are selected during migration, the address comments from the RS Logix 500 program are transferred into the Alias properties, which helps keep the address mapping intact while changing the tag names in the new project.

How can users speed up the process of transferring input/output module descriptions?

Users can export the tags and comments to a CSV file, manipulate them in Excel, and then import the updated file back into Studio 5000. This method accelerates the task of transferring descriptions for each module.

What is the next step after successfully migrating the project to Studio 5000?

After the migration is complete, users should verify that all address comments are correctly assigned and then clean up any untranslatable or incorrect instructions before continuing with development or testing.