1747 AENTR Software Migration
Summary
TLDRThis video tutorial guides users through modernizing hardware by migrating RSLogix 500 programs to Studio 5000 Logix Designer. It covers the use of the migration wizard in RSLogix 500 v12, which simplifies the process compared to the previous standalone utility. The script details steps like preparing the project, selecting the controller platform, and handling IO configurations. It also addresses challenges in transferring address comments and suggests a method to expedite the process using CSV files for large systems, ensuring a smooth transition to the new platform.
Takeaways
- π§ Modernizing hardware requires careful migration of RSLogix programs to a newer version.
- π RSLogix 500 version 12 introduced the 'Save as' feature to export programs as Logix Designer files.
- π A built-in migration wizard helps configure the new Logix Designer file after conversion.
- π Prior versions required a separate RS Logix Project Migrator utility for conversion.
- ποΈ Before conversion, it's recommended to clean up unused memory addresses or routines in RSLogix 500.
- π The migration process involves associating symbols in the Slick program with Alias tags in Logix Designer.
- πΎ The migration utility allows specifying the controller platform and processor type for the new configuration.
- β³ The migration process may take time to complete, requiring patience from the user.
- π A phased migration with the 1747 AENT retains existing IO while updating to new modules or using a wiring conversion system.
- π Address comments for data files transfer to the new tag structures in Logix Designer if 'Create Alias Tags' is unchecked.
- π If 'Create Alias Tags' is checked, the symbol name becomes the tag name with the original data address referenced in its Alias property.
- π For large systems, manually moving address comments to new IO points can be time-consuming and may benefit from using a CSV export and import method.
Q & A
What is the main focus of the video?
-The main focus of the video is on converting a Slick application file from RS Logix 500 to Studio 5000 Logix Designer.
What new feature is available in version 12 of RS Logix 500?
-Version 12 of RS Logix 500 includes the ability to select 'Save Program As' and then choose Logix Designer file (ACD) as the file type, initiating the migration wizard.
What utility was available prior to version 12 of RS Logix 500 for project migration?
-Before version 12, the RS Logix Project Migrator utility was available as a separate download from Rockwell's website.
What should be done before starting the conversion process in RS Logix 500?
-Before starting the conversion process, it is recommended to delete or remove unused memory addresses or routines in RS Logix 500.
What is the first step in converting a Slick application file to a Logix Designer file?
-The first step is to open the Slick application file in RS Logix 500 and then select 'Save As', changing the save file type to Logix Designer file (ACD).
What should you be aware of when the export tool is launched during the conversion?
-Be aware that it may take some time before the first configuration screen appears once the export tool is launched.
What processor type is used in the video example for conversion?
-In the video example, a 5069-L310ER processor is used for conversion.
What should you do if the processor type you are planning to use doesn't show up in the list?
-If the processor type you are planning to use doesn't show up in the list, you can change the processor type in Logix Designer once you have opened the converted file.
What does selecting 'Keep existing IO' during migration imply?
-Selecting 'Keep existing IO' implies that you will retain the existing I/O modules instead of replacing them with new ones.
What happens to the address comments during the conversion process?
-The address comments for bits, timers, counters, integers, and other data files are transferred to the tag structures representing the data table files if 'Create Alias Tags' was unchecked. If checked, the address comment is assigned to the new tag structure but bleeds through to the base tag.
Why might you need to manually copy input and output module descriptions after conversion?
-You might need to manually copy input and output module descriptions because the descriptions do not transfer automatically; placeholder tags are created instead, and the descriptions need to be moved manually or via a CSV file import.
How can you accelerate the task of transferring module descriptions for large systems?
-To accelerate the task, you can export the tags to a CSV file, manipulate the tag file in Excel, and then import the tags back into your application.
What is the final step after converting and adjusting tag descriptions in the video?
-The final step is to clean up any untranslatable or wrong instructions in the converted application.
Outlines
π§ Modernizing Hardware and Migrating RSLogix Programs
This paragraph discusses the process of modernizing hardware and migrating RSLogix programs. It highlights the introduction of a migration wizard in version 12 of RSLogix 500, which allows users to convert SLC application files to Studio 5000 Logix Designer files. The text explains the initial steps of opening the SLC application file, deleting unused memory addresses, and saving the file as a Logix Designer file. It also mentions the need to select the appropriate controller platform and revision version during the conversion process.
π₯ Exporting and Importing Tag Descriptions
This paragraph focuses on handling tag descriptions during the migration process. It explains that address comments for various data files transfer to the new tag structures. However, input and output module descriptions do not transfer and require manual copying or the use of a CSV file for batch updates. The text provides a step-by-step guide on exporting tags and logic comments to a CSV file, adjusting the file in Excel, and re-importing it to ensure all tag descriptions are correctly populated. It concludes by mentioning the need to clean up untranslatable or incorrect instructions after importing.
Mindmap
Keywords
π‘RSLogix 500
π‘Studio 5000
π‘Migration Wizard
π‘SLC Application File
π‘Controller Platform
π‘Ethernet Adapter
π‘Alias Tags
π‘IO Modules
π‘CSV File
π‘Tag Descriptions
Highlights
Modernize hardware by migrating RS Logix programs to Studio 5000 Logix Designer.
Convert SLC application files from RS Logix 500 to Studio 5000 Logix Designer.
RS Logix 500 version 12 introduces 'Save As' feature for Logix Designer files.
Migration wizard in RS Logix 500 version 12 allows configuration of Logix Designer files.
Prior to version 12, RS Logix project migrator utility was a separate download.
RS Logix 5 also has built-in migration utility in its latest version.
Start migration by deleting unused memory addresses or routines in RS Logix 500.
During conversion, decide if symbols in SLC program will be associated with alias tags in Logix Designer.
Specify controller platform and revision in the export tool during migration.
Keep existing IO during phased migration with 1747-AENT.
Converted SLC IO in Studio 5000 Logix Designer will have 'Enbridge' prefix with slot position.
Address comments for bits, timers, counters, and other data files transfer to tag structures in Logix Designer.
Placeholder tags for input and output modules are created during migration.
Manually copy comments from placeholder tags to actual IO points or use CSV export/import to accelerate the process.
Use Excel to manipulate exported tag files and re-import them to Logix Designer for quicker comment transfer.
Transcripts
if you modernize your Hardware you must
consider how to migrate your RS Logics
program in this video we're going to
convert a slick application file from RS
logixs 500 to Studio 5000 logixs
[Music]
designer one of the new features in
version 12 of RS logixs 500 is the
ability to select save program as has
and then select Logix designer file. ACD
as the file type this starts the
migration wizard that will allow you to
specify how your logic's designer file
will be configured once the conversion
is complete we'll dive deeper into those
details shortly prior to version 12 of
RS logixs 500 the RS Logix project
migrator utility was available as a
separate download from Rockwell's
website this utility worked well but did
not have all the configuration options
that the built-in utility has in version
12 of RS Logix 500 the latest version of
RS Logix 5 also has the built-in
migration utility available start by
opening the Slick application file in RS
logixs 500 before starting the
conversion delete or remove unused
memory addresses or routines in RS
logixs 500 then select save as change
the save as file type to logic's
designer file then decide whether or not
you're going to associate at symbols in
the Slick program assuming you had
symbols in your slick program with Alias
tags in Logix designer the export tool
is launched by hitting the save button
be aware that it may take some time
before the first configuration screen
appears once the export tool is launched
you'll specify the controller platform
because we're using an ethernet adapter
for a slick chassis a compact or control
Logics processor could be selected we're
going to use a 5069 l310 ER processor
it's not a big deal if the processor you
are planning to use doesn't show up in
the list you can change the processor
type in logics designer once you got the
converted file open finish this step by
selecting the revision you're planning
to use once again not a big deal if the
version you're planning to use isn't
available make sure to select an earlier
version if possible and then change it
once the ACD file is created doing a
phased migration with the 1747 aent
means you'll keep the existing IO
understand that update all IO is used
when you're going to do a rip and
replace with the allnew io modules or
use the wiring conversion system once
you've selected keep existing IO hit the
migrate button please be patient as it
may take a couple of minutes for the
conversion to complete once complete hit
the launch RS Logix 5000 button this
will open the converted application in
studio 5000 logic designer if you open
the controller tags you'll notice that
the Slick IO now has the prefix
Enbridge
1746 with slot position and I or o this
makes for an awfully long tag name once
you've added the actual IO Point
probably a good idea to change the
adapter name to something short like
rack one you'll be pleased to note that
the address comments for the bits timers
counters integers and other data files
did transfer to the tag structures that
represent the data table files this will
happen if create Alias tags was
unchecked if you selected checked Alias
tag the address comment is still
assigned to the new tag structure that
was the data table file but now the
symbol name is the tag name and that tag
name references the old data address in
its Alias 4 property and because the
address comment was transferred to the
Alias it bleeds through to the base tag
the result is that the 5,000 ladder
window looks pretty much the same as the
500 ladder window what you may have
noticed earlier is that the address
comments for the input and output
modules do not get transferred as it
states in the description for input zero
here is what happens a placeholder tag
was created for each module it is
labeled Legacy value and descriptions as
you can see all the descriptions ended
up in the placeholder tag but they have
to be moved to to the new IO Point
description within logic's designer you
can manually copy each comment from the
placeholder to the actual iio point this
could take hours or even days to
complete for large systems that use 32
point.io modules like this one one way
to accelerate this task is to export the
tags to a CSV file manipulate the tag
file in Excel and then import those tags
back into your application here's how
this works manually copy the tag
description to the first module input
description as we just did then copy the
last comment in that placeholder group
to the last input description on the
first module you got the first and you
got the last description you need to do
this for each module in that slick
system then go to tools export and
select tag and logic comments then
select export open the file adjust the
comment width and scroll down to the two
comments you just copied select the row
that has the last commment and come down
14 rows then select insert to verify you
have the correct number Select Point Z
in column F populate the column down to
14 now populate columns A and C into the
inserted space scroll down to the
placeholder with the descriptions and
copy the descriptions and then paste
them into the inserted rows save the CSV
file now go back to to logic designer
and select tools import and select tags
and logic comments select the CSV file
and then select import as you can see
all of the input module tag descriptions
populate correctly once all the comments
are straight we can start cleaning up
all the untranslatable wrong
instructions thanks for watching and if
you have any questions or concerns
please contact your local es& account
manager or automation
specialist
[Music]
Browse More Related Video
17. Migrate Active Directory from Windows Server 2008 R2 to Server 2022
Application Deployment in Oracle APEX with Data - Part 40
Set up a Mettler Toledo SLP33 to a 5032 IO-Link Master
How To Install & Setup Android SDK In Termux / Build Java Or Kotlin Projects
Migrate Active Directory Domain Controller From Server 2016 to Server 2019. (Part 1 of 2)
Steps to Apply for a Certificate of Origin (COO) via JSWIFT
5.0 / 5 (0 votes)