Home Blog Page 68

ViewSE – v10: What’s New In FactoryTalk View Site Edition (P41)


Today we discuss the new features that come with FactoryTalk View Site Edition 10.0 in Episode 41 of The Automation Podcast.


Watch the Podcast:


Listen to the Podcast:


Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

ViewSE – v10: What’s New In FactoryTalk View Site Edition


Late last month Rockwell released version 10.0 FactoryTalk View Site Edition, and below I’ll summarize its new features:

New Features:

  • TrendPro support for Alarms and Events traces
  • RecipePro+ integration with FactoryTalk Security
  • RecipePro+ List control for downloading and uploading recipes
  • Multi-monitor support (up to six,) and /M Display command parameter to specify monitor
  • Redundancy now copies HMI project files from the primary server to the secondary server after redundancy is setup
  • Replication between active and standby servers now supported when active server is the secondary server, and without the need to restart server
  • Replication now automatically saves online project edits to both active and standby servers
  • New functions: PrimaryServerStatus(), SecondaryServerStatus()
  • New switchover command to switch the active server in a redundant server pair
  • Redundancy expanded to support (1) 80 Client sessions simultaneously connected, (2) 50 FactoryTalk ViewPoint web client sessions, and (3) 1,000,000 tags across 10 redundant HMI servers
  • New commands to allow users to interact with the active alarm events from buttons outside of Alarm and Event summary
  • New AE_Remark command allows users to log a user-defined message into the Alarm and Event history database
  • Embedded Web Browser control provides capability to display web pages from an HMI application
  • HTTPS Protocol product policy support for secure communication when enabled

Enhanced features

  • Added support for pass-through login from ThinManager to launch FactoryTalk View SE clients
  • Redesigned workflow of FactoryTalk View SE Client Wizard
  • Improved built-in on-screen keyboard layout with custom text support
  • Support added for deleting and removing multiple components at a time
  • Property Panel and Object Explorer now automatically doc on right side of the main window
  • Added support for dynamically specified local message files, and writing triggered message to string tags
  • New shortcut to create Signature Button object added to toolbar and menu
  • New support for $ symbol in the command syntax (must use a backslash \ when tag name includes $, so use \$tag3 for $tag3 in commands
  • New display statistics functions including (1) Number of security functions used, (2) Number of referenced images, (3) Number of imported images
  • Installation Wizard can now record and playback installation operations
  • FactoryTalk View File Viewer tool now supports reading running data log files and RecipePro files (.rcpf)


Corrected Anomalies

  • Button text is again resized when displays are resized
  • Navigation history is now cleared when a user logs out and then logs in
  • CurrentComputerHasGroup() now always returned correct result
  • AE_DisabledCount(), AE_NormalShelvedCount(), and AE_NormalSuppressedCount() now return correct numbers of alarms
  • ME Recipe 2 Enhanced ActiveX control now loads recipes correctly.
  • Multistate indicator now shows states correctly
  • Using VBA to automatically logout a user no longer crashes clients.
  • Security functions CurrentUserHasGroup() or CurrentComputerHasGroup() now work correctly with other functions or tags in an expression
  • On-screen keypad now shows the correct maximum value
  • The text object can now read String variable tags which include “N:”
  • Displays now opened in correct order when using both the /ZA command and VBA code

For a complete list of Corrected and Know Anomalies, see the official product release notes.


Find out more about ViewSE 10.0

If you would like to view the FactoryTalk View Site Edition 10.0 release notes, head over to Rockwell’s Product Versions webpage and search on and then select FactoryTalk View.

Once all the versions are listed, click on the document icon as shown below:


If you’d like to listen to a discussion of the above, check out Episode 41 of The Automation Podcast below:



So, what do you think of the new features in ViewSE 10.0?

Will you jump on 10.0 right away because of one of the added features?

You can share your thoughts and opinions by clicking on the “post a comment or question” link below.

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

ViewSE – v9: What’s New In FactoryTalk View Site Edition – A look back (P40)


We take a look back at the new features came with FactoryTalk View Site Edition 9.0 in Episode 40 of The Automation Podcast.


Watch the Podcast:


Listen to the Podcast:


Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

ViewSE – v9: What’s New In FactoryTalk View Site Edition – A look back

Late last month Rockwell released version 10 of FactoryTalk View Site Edition, and in tomorrow’s article I’ll take a look at it’s new feature.

But today I want to go back and take a look at what was new in version 9 since I didn’t have access to it when it was released last year:

New Features:

  • New trend object, Trend Pro with ad-hoc, drag and drop trending. Supports ViewSE Datalog and FTHistorian Data
  • Improved recipe management added to RecipePro+ allowing all functions during runtime without a View Studio license
  • New RecipePro+ commands, including RecipeProEdit and RecipeProDownload
  • New Hyperlink animation available for use on most objects supporting “Touch” animation
  • New Alarms and Event functions, including: AE_DisabledCount(), AE_InAlmShelvedCount(), AE_InAlmSuppressedCount(),
    AE_NormalShelvedCount(), and AE_NormalSuppressedCount()
  • Logix Designer tag extended properties support, including .@Min, .@Max, .@Description, .@EngineeringUnit, .@State0, and .@State1 (format = TagName.@ExtendedProperty)
  • Data communication inhibit feature to inhibit shortcut communications to reduce network load and system load time when shortcut targets are disconnected

Enhancements:

  • Streamlined installation
  • New operating system support for Windows 10 Enterprise and Professional
  • Dynamic decimal places
  • Printing screen to PDF using ScreenPrint or PrintDisplay command
  • Screen statistics including total referenced tags and the total used expressions
  • Security functions CurrentUserHasCode, CurrentUserHasGroup, and CurrentComputerHasGroup enhanced to support string tags and tag placeholders

Corrected Anomalies:

  • FactoryTalk View File Viewer Utility “convert datalog to .csv file” feature now working
  • FactoryTalk View SE client screens no longer hang for up to 40 seconds loading some graphic displays
  • Records can now be purged from the database successfully
  • Pop-ups can now appear on a second monitor in a two horizontal monitor system
  • Trends now display data correctly with daylight saving enabled
  • Sub-menus of PlantPAX PF755 faceplate now display correctly
  • Replication no longer fails due to startup of SQL Express
  • Parameters as trend pens for historian data now display correctly
  • FTView installation no longer removes the Arial Bold font from the operating
    system

Find out more about ViewSE 9.0

If you would like to view the FactoryTalk View Site Edition 9.0 release notes, head over to Rockwell’s Product Versions webpage and search on and then select FactoryTalk View.

Once all the versions are listed, click on the document icon as shown below:


If you’d like to listen to a discussion of the above, check out Episode 40 of The Automation Podcast below:



So, what did you think of the new features in ViewSE 9.0?

Did you migrate to it last year, or did you stay with 8.2?

You can share your thoughts and opinions by clicking on the “post a comment or question” link below.

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

The New Features Of FactoryTalk View Machine Edition 10.0 (P39)


We take a look at the new features of the recently released FactoryTalk View Machine Edition 10.00.01 in Episode 39 of The Automation Podcast.


Watch the Podcast:


Listen to the Podcast:


Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

What’s New In FTViewME 10.0?

Last week Rockwell released version 10.00.01 of FactoryTalk View Machine Edition, and below I’ll summarize the new and enhanced features that were added:

New Features:

  • Built-in “audit trail” log feature provides report of operator inter-actions with graphic objects
  • Developers can now allow operators to export audit, diagnostics, alarm history logs to CSV file at runtime
  • Developers can now enable “dynamically specified” local message files, as well as trigger messages to be written to a string tag
  • Using the Installer interface, installation choices and actions can now be recorded on one PC, and then played back on another.
  • Help files are now provided in HTML5

Enhancements:

  • Version 5.00, 5.10, and 6.00 runtime applications can now be opened and converted using v10 on a 64-bit operating system.
  • FT View Machine Edition Station now shows the software version in the title bar of the startup dialog box
  • The CSV Data Log Tamper Detection Utility installation files are now included with FTView installation files
  • The Property Panel and Object Explorer now are automatically docked to the right of the main window
  • Multiple components can now be deleted and removed at a time.
  • KEPServer version 5.21 support added

Corrected Anomalies

  • DataStorePlus ActiveX no longer deletes all old CSV data log files when system date changes from December 31, 2016 to January 1, 2017.
  • Runtime applications no  longer stop loading after the recipe load operation by a Recipe 2 Enhanced ActiveX control
  • Acknowledging (or remote acknowledging) alarms no longer changes alarm message fonts

Find out more about ViewME 10.00.01

If you would like to view the FactoryTalk View Machine Edition 10 release notes, head over to Rockwell’s Product Versions webpage and search on and then select FactoryTalk View.

Once all the versions are listed, click on the document icon as shown below:


If you’d like to listen to a discussion of the above, check out Episode 39 of The Automation Podcast below:



So, what do you think of the new features in ViewME 10.00.01?

Will you jump on 10 right away because of the new features?

Share your thoughts and opinions by clicking on the “post a comment or question” link below.

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

The New Features Of FactoryTalk View Machine Edition 9.0 (P38)


We take a look back at the new features came with FactoryTalk View Machine Edition 9.0 in Episode 38 of The Automation Podcast.


Watch the Podcast:


Listen to the Podcast:


Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

FTView ME 9.0: A look back

Just last week Rockwell released FactoryTalk View Machine Edition version 10.00.01 (word on the street is the initial release was pulled so a patch could be included.)

Before we take a look at what’s new with v10 (which we’ll do in tomorrow’s article,) I wanted to first take a look back to see what was new in v9 since I didn’t cover it (as my license didn’t include access to v9) when it was released at the beginning of 2017.

New 9.0 Features:

  • New alarm identifier property to identify an alarm message
  • New Pop-up Input Color Setting for keypad, keyboard, and character inputs
  • Persistant version and language setting when creating a runtime file (as oppose to always using defaults)
  • If you may any changes to the RSLinx Enterprise config, a message will ask if you’d like to save those changes
  • New hyperlink animation option ti display a file (PDF, etc), a web page, or launch a program (only certain drawing objects support  hyperlink animation)
  • Logix Designer tag extended properties “Read” support (TagName.@ExtendedProperty)
  • Data communication “Shortcut” inhibit allows missing devices to be inhibited to help reduce load time and network load

Enhancements in 9.0:

  • PanelView Plus 7 Standard applications expanded to allow up to 25 On Top displays, 25 Replace displays, and 500 alarms
  • Up to five graphic displays can be selected to open when an application starts
  • FactoryTalk View installation now much more automated
  • New OS support for Windows 10 Professional and Enterprise
  • New support for KEPServer version 5.19


Corrected Anomalies in 9.0:

  • Fixed issue where ME Chart control could cause View Studio may stop
    responding
  • Copying and pasting an ME Chart control could cause View Studio to stop responding.
  • Unsaved information or local messages may not be included in runtime applications
  • PanelView Plus 6 stops responding and displays “Unloading application”
  • An .med fil restored from a runtime using a later version of View Studio can’t be opened or imported in the earlier version of View Studio
  • Design time application names not showing in Existing tab
  • Importing applications in View Studio may result in the error, “…was created with a newer version… and cannot be imported into this version…”
  • Installation of FactoryTalk View removes the Arial Bold font from OS.

Find out more about ViewME 9.0

If you would like to view the FactoryTalk View Machine Edition 9.0 release notes, head over to Rockwell’s Product Versions webpage and search on and then select FactoryTalk View.

Once all the versions are listed, click on the document icon as shown below:



If you’d like to listen to a discussion of the above, check out Episode 38 of The Automation Podcast below:



So, what did you think of the new features in ViewME 9.0?

Did you switch to it in 2017, or stay with 8.2?

You can share your thoughts and opinions by clicking on the “post a comment or question” link below.

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

Upgrading Legacy Winder and Slitter Positioning Control Systems

Stock photo taken by morenosoppelsa

In today’s article, Jeff Turcotte of PLC Concepts discusses winder and slitter positioning control system upgrades, and how his company’s upgrades increase throughput and reduce downtime.

Written by Jeff Turcotte, PLC Concepts Inc:

Over the Holidays I had the pleasure of catching up with Shawn Tierney who I’ve known for many years prior to his launching of The Automation Blog and The Automation School.

Stock photo taken by morenosoppelsa

As we were talking, he suggested I share my story about how I built a successful business helping Paper Mills upgrade the automation systems on their legacy Winder and Slitter Positioning Systems, and that’s what I’ll share in today’s article.

First, let me share a little of my background with you.

I started in the paper industry back in 1986, working for Jagenberg, a company that made paper finishing machines.

After several years I decided to start my own company, PLC Concepts Inc, and the mainstay of my business has been performing upgrades on existing equipment in the paper industry.

Stock photo taken by Shawn Tierney

Along the way I’ve also branched into other areas, including acting as a service contractor for Rockwell, as well as designing control systems for baking equipment and biofuel conversions.

Most of the control systems I’ve used over the years have been centered on Rockwell products, from PLC-2s through ControlLogix and Studio 5000, as well as the various Rockwell HMI software packages.

That said, I’ve also had the opportunity to design and deploy control systems using Modicon, GE Series 6 and 90/70, Siemens S5 and S7, as well as Variable Frequency Drives from multiple vendors.

Upgrading Legacy Winder and Slitter Positioning Control Systems

The methods you choose to upgrade an existing control system on a Winder (or any piece of equipment) obviously depends on the installed control system, as well as the type of control used.

Many of my clients have control systems from Rockwell, and those with PLC-5 systems are typically very interested in reusing the installed I/O.

That may seem odd at first, until you realize many of these systems have up to a 1000 I/O points, and replacing and rewiring all that I/O would add substantial cost to any project. Though the bigger factor is the down time it would take to accomplish the task, with the potential for possible wiring errors

But regardless of the brand, upgrading existing equipment is a methodical task as you’re working with an existing program written many years before.

So prior to bidding any project, I make the following request of my customers to insure I’ve covered all the bases:

Stock photo taken by morenosoppelsa
  • Can I observe the machine running and speak with the operators?
  • Did the program run properly to begin with, and is all the original functionality still available or desired?
  • Are there any mechanical underlying issues or planned upgrades?
  • Are you looking to improve performance as the primary end goal, or is your goal more consistent uptime?
  • Does the machine interface with any auxiliary systems, and if so are they using legacy software/hardware?
  • How much downtime are you looking to allocate to do the project, and what is the production expectation after the initial work has been done? When do you expect to be back at 100% capacity?
  • Who is maintaining the system after the fact, and will any of these people be available to work with me during the conversion?

While the aforementioned questions might seem to be obvious, are they? Do we as controls integrators take things for granted when upgrading legacy systems?

Many would assume that the original program, which has been running for years, had to be solid. Otherwise, it would have been modified to correct any issues along the way, right?

Well, that’s not necessarily the case, as fact I was reminded of a few years ago when I broke my own protocol.

While I’ve found Jagenberg’s basic machine programs to be very robust over the years, I was once tasked with upgrading a system that was one of only a few machines built in that style.

And it turned out to have a very complex unloading sequence that was poorly written, something I didn’t realize that at the time.

After converting the equipment from Reliance Automax to ControlLogix, I began to run into a ton of issues.

Of course, now I owned the program so there was no going back.

After talking with several operators about what problems had always existed, I decided to rewrite that portion of the logic.

It was a costly reminder, which also added an extra week to the project.

Fortunately, the customer also saw the need to correct the original faulty code, and compensated me for the additional time onsite required to implement the changes.

I’ve also found over the years that, regardless of what industry a system comes from, higher end automation functionality was seldom put into the PLCs in the late 70’s and even into the early 90’s.

Third party HMI software was also non-existent during that time, so companies often made their own proprietary systems.

These proprietary systems acted as an interface and controller, and were often coupled with custom electronics that handled the actual machine functions and interface with the PLC’s.

That was the case at Jagenberg, where these types of systems handled Nip Pressure, Tension, Load Sharing, Diameter/Length Stops, and positioning of the Slitters/Stations corresponding to requested roll sizes.

Sometimes we only upgraded just the automation portion of the system, including retrofitting positioning portion. Regardless, to do away with these systems you had to engineer your own replacement solution from scratch.

And since the original programs were compiled, you couldn’t view the original code and therefore had no idea what was in the original logic.

As you may know, many companies run their systems until they just don’t work anymore. Or until it has an adverse effect on production.

So when I first began retrofitting positioning systems, I needed to analyze why and where they were failing.

In my first project there were several issues, including two mechanical points of failure, one maintenance related issue, and two evolving production related problems based on current customer demands:

  • The existing systems used encoders as feedback for the position of the slitters. The wiring was done through ribbon cables set up in a festoon. The cables were starting to break down and so was everything related to the encoders themselves causing potential errors in the system.
  • The mechanical portion of the slitter systems were also worn out causing excessive friction, skewing, and finally clamping issues. These issues were a root cause in preventing the system from finishing requested positioning sequences reliably. Truth is when you run machines 24/7, it’s hard to keep up with the recommended maintenance.
  • Since the systems were proprietary, they were almost impossible for the mills to maintain themselves (I also work with a consultant who use to troubleshoot and repair these systems.)
  • Standards for production were changing, and originally the customers who used the finished rolls always trimmed prior to processing the paper. This produced excessive waste and the tolerances the customer would accept became stricter. Back when I started in the industry roll sizes could be as much as .25 inches over and .125 inches under. Now you can be no more than a .03125 inches over and nothing under.
  • Finally, the way paper was made changed! Not necessarily the process itself, but the way orders were handled. Mills would make paper and store the rolls based on projected demand. So the machines might run specific roll sizes for days sometimes on a certain grade storing the finished product. This model shifted to manufacturing upon request, resulting in more size changes per shift. The result being the initial accuracy of the slitters and the time spent positioning now totally impact line performance.

That said, large scale mechanical rebuilds of slitter sections are typically not going to get funded.

They’re costly, and required more downtime than most mills want to give up.

The best you could hope for was to get them to repair the specific components in certain slitters, and possibly replace all of their bearings.

But given how sloppy the systems became through mechanical wear and tear, we had to find a way to get around these deficiencies.

Technically, you could reuse the Jagenberg encoders by wiring them into any 16 bit DC sourcing input like an Allen-Bradley 1756-IV16.

And in certain instances, we did this, especially related to the stations on a Single Drum Winder using Grey-Code to Binary conversion.

Reality is, this does nothing to eliminate the potential wiring issues related to the festoon.

In the pursuit of finding a solution to that issue, I was led back to a company I was exposed to at the end of my time with Jagenberg.

OLYMPUS DIGITAL CAMERA

The company is MTS Sensors, who I have been privileged enough to develop a long-term relationship with over the years.

MTS makes a myriad of products that use a time-based magnetostrictive position sensing principle based on the position of a magnet, or multiple magnets, relative to a wave guide.

This wave guide is inserted into a tube which is attached to a head that contains an on-board processor.

The processor then converts the signal into the specific communications protocol you want to use.

Using this device with a singular power/communications connection at each head eliminated the encoder and wiring issues.

NOTE: You can read the MTS case study on one of Jeff’s project here.

BENQ

Going forward we decided that upgrading positioning systems would revolve around this sensor, and looking back it was a good choice.

With an understanding of why the systems were failing, and through observation on my own time, I was able to understand the intent of the original design which then lead to the solution for mounting the new sensors and magnets on each element.

When I first started working on these systems, the PLC-5 was the most common controller, so I used a RS-422 signal with a start-stop style sensor that was wired directly to a 3rd party card in the HMI computer.

This data was then mapped into RSView32 through a Visual Basics program that polled the sensor.

Then the data was sent to the PLC to be used in the positioning sequence.

While this method did alleviate many of the initial wiring and mechanical issues, it didn’t improve the speed of the sequence, or the accuracy of the slitter elements in a pattern.

It wasn’t until about 15 years ago when MTS made a significant breakthrough with the material used to manufacture its waveguide.

This upgrade of the MTS product made a huge difference relative to the accuracy monitoring up to 15 magnets per sensor.

Coupled with that, they were able to extend the overall length of the sensor from 300 inches to 480 inches, along with a more flexible style that alleviated many of the installation and maintenance issues.

At the same time, they were also moving into Canbus/Profibus networks, which allowed the positioning data to go directly into the PLC via a 3rd party communications card.

This was a major hardware upgrade, which happened around the same time that ControlLogix was becoming the standard for many Paper Mills.

It was as that time that I also started using the SST Profibus card with these systems (SST is now owned by Molex.)

The current iteration of that card is the SST-PB3-CLX-RLL, and it is a 1756 rack based style.

Moving to the ControlLogix, the new MTS system, and the SST module changed everything, and enabled us to dramatically improve the original positioning sequence making it both faster and more accurate.

The HMI portion was also upgraded to FactoryTalkView, and allowed the operator to enter the roll sizes that our own algorithm would use to pick the appropriate slitters to use.

The last component to address for these upgrades is the motor itself, and how it was controlled.

They were originally standard European AC motors wired for 380, and capable of 220.

The initial Jagenberg systems used these motors to position the slitters via standard AC motor contactors.

The course movement was done by leaving the starter “on” based on a projected “millimeters per second” timed interval relative to the slitters last known position.

This was a limitation of the original system electronics because it could only look at one encoder at a time.

It is worth noting that Valmet/Metso and Beloit positioning systems have similar limitations, though for different reasons.

But now with the MTS sensor, we knew every position all the time. And since it had an update rate of 5 milliseconds, the PLC program had position feedback in real-time.

Once all of the slitters reached the course positioning target, the system would then switch over to a VFD acting as a variable step-down transformer for a certain group of motors.

Initially, all of these motors were of the pre-PWM era, so the drives either required filters/reactors, or had to be rewired to 220 to avoid issues.

Once this drive was in use, the fine positioning was done via a timed pulse, followed by a position verification wait time.

This cycle was repeated until the target position was reached without error.

Standard modules like the 1756-OW16I or OA16 have reasonable on/off cycle times, but the AC coils have inductance which needed to be considered in the timing.

If possible, you would want to update the contactors using DC coils, and add a 1756-OB16I or OB16D card to your PLC rack.

For optimal individual control, you can replace the contactors with PowerFlex 525 VFDs on Ethernet for a reasonable price comparatively.

Either of these options gives you the absolute best performance, keeping the positioning sequence at 30 seconds or less for almost any pattern.

This is a vast improvement over the 60 to 120 seconds it takes to position the slitters with the previous system when it’s running well.

And keep in mind that, at the end of their life cycle the original systems might have taken several attempts to reach their target settings.

Regardless of the design style of the original slitter system, the core of our new design is applicable, and extends the usefulness of the current mechanical components of any slitter beam.

And considering the alternative, which is total replacement, this upgrade option is a very acceptable solution.

It’s also worth mentioning that beyond slitter positioning, I’ve also used the MTS sensors for a multitude of positioning, size change, and general feedback applications, as the application demanded.

As I hope you can tell from this article, I feel strongly that mechanical aptitude is as big a component as electrical/programming abilities when it comes to upgrading Winder and Slitter systems, and insuring a positive outcome from your upgrade.

Thanks for reading, and remember: safety first!

Jeffrey C. Turcotte
Electrical Integrator And Programmer
PLC Concepts Inc
Website: PLCConcepts.com
Email: jturcotte@plcconcepts.com
Phone: (413) 650-0085
LinkedIn: Jeff Turcotte


Editors Footnote:

I want to thank Jeff for taking the time to write this article and share with us how he’s made a successful business upgrading Winder and Slitter Positioning control systems for Paper Mills.

Having worked with Jeff for many years outside of the Paper Industry, I have to say I really enjoyed learning about this side of his business.

If your plant has a Winder or Slitter Positioning system which needs upgrading, I would highly recommend reaching out to Jeff via his contact information above.

And if you’ll like to join the ranks of our guest bloggers, please let me know using the contact form here.

Sincerely, Shawn Tierney of The Automation Blog.

Migrate / Convert – MicroLogix 1000 Programs to Micro800 (M4E26)


In this episode I discuss how you go about converting MicroLogix 1000 programs to the Micro800 and CCW (Episode 26 of The Automation Minute Season 4:)




If you’ve found this video helpful, checkout my training courses here.

Check out our Video Collection #1 here, which includes the first five seasons of our shows for just $30!

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

Migrate / Convert – MicroLogix 1000 Programs to Micro800

In today’s article I’ll walk you through how to convert a MicroLogix 1000 program to a Micro800.

To accomplish this, we’ll use RSLogix 500 and the Connected Components Workbench “MicroLogix Library Converter” tool.

NOTE: If you don’t see the tool installed below, your can find it by following this article here.


Step 1) Start by opening CCW, and selecting the “MicroLogix Library Converter” under “Tools”:

Step 2) At the top of the tool we see instructions for exporting our MicroLogix program using RSLogix 500.

NOTE: Neither RSLogix Micro Starter or Lite will work because neither support saving Programs to Library files.

Note: Since the tool was released a few years back, it has always shown a picture of a MicroLogix 1200 (instead of a MicroLogix 1000,) however the tool clearly states it only works with MicroLogix 1000 files. That said, it’s fairly easy to change a project’s controller as shown in this article.

Update 05/03/18: With the release of CCW 11 the converter has been expanded to now work with all MicroLogix programs.

Step 3) Open RSLogix 500, and then open the MicroLogix program you’d like to convert and choose “Save As”:

Step 4) In the “Save As” dialog box, first choose a “save as type” of “Library Files (*.SLC)”

Step 5) Next, select the “Export Database” box, and insure the “Export file types” is set to “Logix”:

Step 6) Now choose a location to save the file to, and click on “Save”:

Step 7) When the “Export SLC Format” window pops up, insure that “Complete Program Save” is selected, along with all the “Export Options,” and then click on “OK.”

Step 8) After a few moments you should now see the “Export Results” window, at which point you can click on “OK”:

Step 9) Back in the MicroLogix Library Converter, select your source project as the .SLC file you just exported from RSLogix 500:

Step 10) Then select the Micro800 controller you’d like to import the project too:

Step 11) Finally, select the “OK” button to begin the import:

Step 12) Small projects can take a minute or two to import, while larger projects can take much longer:

Step 13) When done, you’ll see your new Micro800 project open in CCW. At this point you’ll need to review all the import errors, as well as fully test the program to insure everything imported correctly:

For more about converting MicroLogix projects to the Micro800 using CCW, check out our previous articles on the subject:


If you’d like to watch a video of the above, check out Episode 26 of The Automation Minute Season 4 below:




I hope the above article detailing how to import MicroLogix 1000 programs into Micro800s using the CCW conversion tool was helpful.

If you have any comments, questions, or suggestions, please feel free to leave them with us by clicking on the “post a comment or question” link below.

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

Migrate / Convert – SLC-500, MicroLogix, RSLogix 500 Programs to RSLogix/Studio 5000 and Logix Controllers (M4E25)


In this episode I discuss how you go about converting SLC-500 programs to ControlLogix and Studio 5000 (Episode 25 of The Automation Minute Season 4:)




If you’ve found this video helpful, checkout my training courses here.

Check out our Video Collection #1 here, which includes the first five seasons of our shows for just $30!

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

Migrate / Convert – SLC-500, MicroLogix, RSLogix 500 Programs to RSLogix/Studio 5000 and Logix Controllers

In this article we will convert SLC-500 programs to ControlLogix using the RSLogix Project Migrator version 3.0.

Note: To get RSLogix Project Migrator version 3.0, search the below website for “RSLogix Project Migrator (it also comes with RSLogix/Studio 5000 v19 and up)”

UPDATE – November 2021 by SMT: Rockwell no longer makers the Translation Tool or Project Migrator available as a download, so if you don’t have either in your RSLogix/Studio 5000 installation files or discs, you can try the “new” feature in RSLogix500 v12 and RSLogix5 v10 which allows you to save your program as a Logix file by using the “save as type” menu option, and choosing “Logix Designer Files (*.ACD)” For more information see the free tech note below:


Step 1) When you install Studio 5000 the RSLogix Project Migrator is also installed, and the first step it to launch it:

Step 2) Here we can select either a PLC-5 or SLC-500/MicroLogix project. In today’s example we’ll choose the SLC-500 option:

Step 3) According to the above instructions, we first need to open our SLC-500 program in RSLogix 500 and save it as an .SLC library file:

Step 4) After we select save, we can click on OK to select the default export mode:

Step 5) Back in the Project Migrator, we can see the next step is to export our comments and symbols:

Step 6) This is done in RSLogix 500 by selecting Tools, then Database, then ASCII Export:

Step 7) Then we select the CSV tab, and click on OK:

Step 8) To complete the process, we select where the export gets saved to:

Step 9) After the export is complete, we can click on OK to close the Export Results window:

Step 10) Back in the Project Migrator, we now need to select our exported .SLC file:

Step 11) Once done, we can click on Next:

Step 12) On this step I prefer to leave the checkbox checked to have Symbols imported as Alias tags:

Step 13) Once step three is done click on Next:

Step 14) Here on this step you select your Logix Controller, and Controller version:

NOTE: The new version of the utility that comes with Studio 5000 only supports versions 21 and up. To convert a SLC-500 program to RSLogix v20 or less, you can change the version on import as seen in Step 18, or use the older version of the utility which comes with RSLogix 5000 and can be seen in our blog article HERE.

Step 15) Here you can choose to either keep the existing I/O as a new remote rack, or replace the I/O with new local or remote I/O:

Step 16) When the migration is compete, click on launch Studio / RSLogix 5000:

Step 17) I also suggest clicking on “Help,” and reading the section about “Post Translation User Responsibilities”:

Step 18) Once Logix loads it will ask you where to save the imported file.

NOTE: It also allows you to change the version by using the drop down box at the bottom of the Save Dialog:

Step 18) Once Logix opens, and you select where to save your imported file, you’ll be able to view your newly imported code and make any corrections that are needed:



If you’d like to watch a video of the above, check out Episode 25 of The Automation Minute Season 4 below:



If you have a comment or question you’d like to post, just click on the “post a comment or question” link below.

And if you this article helpful and would like to support my work, you can pledge $1 a month at TheAutomationBlog.com/join and in return receive $3 in free downloads of my sample code, videos, and articles 😉

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

Migrate / Convert – SLC-500 Programs to MicroLogix (M4E24)


In this episode I discuss how you go about converting SLC-500 programs to MicroLogix, as well as how to deal with a couple of common errors (Episode 24 of The Automation Minute Season 4:)




If you’ve found this video helpful, checkout my training courses here.

Check out our Video Collection #1 here, which includes the first five seasons of our shows for just $30!

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

Migrate / Convert – SLC-500 Programs to MicroLogix


In this article we’ll look at converting SLC-500 programs to MicroLogix, including how to address two common errors.


Step 1) Start by opening RSLogix 500. In this example we open the SLC-500 sample program, IC500DMO.RSS:

NOTE: You can’t open and convert SLC-500 programs using RSLogix Micro

Step 2) Next, let’s take a look at the I/O Configuration of the sample program. It shows a 1746-IA4, IA8, and OA8:

Step 3) Before we make any changes, let’s save the existing SLC-500 program with a new name:

Step 4) Now we’ll open Controller Properties by double-clicking on it:

Step 5) In controller properties we’ll select a MicroLogix. In this case I choose a 1400:

Step 6) I’ll then click on OK on the confirmation screen:

Step 7) After the program is changed, you may see errors that need to be addressed. The two most common errors are “missing I/O” and “OSR” instructions:

Step 8) The reason for the missing I/O is that in the conversion all of the old SLC-500 I/O modules were removed:

Step 9) The easy way to resolve the missing I/O issue would be to add those I/O modules back in as we’ll do below. However, another solution would be to search and replace the old I/O addresses with the addresses of the embedded I/O:

Step 10) With the missing I/O replaced and the project verified again, we see all the the I/O error messages has been resolved. This leaves us with only “OSR” errors:

Step 11) The easiest way to resolve the OSR errors is to replace them with ONS instructions:

Step 12) To do so you can search and replace, or edit each line of code by double-clicking on the left side of the rung:

Step 13) Either way, the goal is to replace the OSR instructions with ONS instructions:

Step 14) Once done and re-verified, these errors will be eliminated from the error list:


If you’d like to watch a video of the above, check out Episode 24 of The Automation Minute Season 4 below:



If you have a comment or question you’d like to post, click on the “post a comment or question” link below.

And if you this article helpful and would like to support my work, you can pledge $1 a month at TheAutomationBlog.com/join and in return receive $3 in free downloads of my sample code, videos, and articles 😉

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

How to find, remove, and pause Windows updates impacting Rockwell Software

Yesterday we discussed how recent Microsoft Windows Updates were severely impacting some Rockwell Software customers.

Today we’ll look at how to work around these issues by finding our Windows 10 build number, list of installed patches, as well as how most users can delay and pause these updates from being automatically installed on their PCs.


How to find your Windows 10 Build version:

Unfortunately, with Windows 10 you won’t find the build number in the obvious locations, like under System, System Info, or using the “VER” command:

But the good news is you can find it using the following steps:

Step 1) In the search field (near the Start Menu) type in “settings” and then select it from the list:

Step 2) When it opens, select “System”:

Step 3) Then scroll to the bottom and select “About”:

Step 4) Then at the very bottom of the “About” page you’ll see your Windows 10 Build Version listed:


How to find which updates have been installed on Windows 10:

Step 1) In the search field (near the Start Menu) type in “windows update settings” and then select it from the list:

Step 2) Next select, “View installed update history”:

Step 3) Now that you have your Windows Updates list and Build Version, refer to the Rockwell Tech Note (here) we discussed yesterday to, (a) see if you have any of the identified updates installed, and (b) if there is a new update that resolves the issue:

Step 4) If there at no confirmed updates that resolved the documented issues, you’ll likely will want to uninstall the offending update. However, any update you uninstall will likely reinstall itself unless you follow the settings in the next section.


How to delay and pause Windows 10 Updates:

If you have Windows 10 Pro, Enterprise, or Education Build 1703 or later, these is an easy way to delay when updates are downloaded, as well as pause them for up to 35 days.

Step 1) In the search field near the Start Menu type in “windows update settings” and then select it from the list:

Step 2) Select “Advanced Options”:

Step 3) Here you will see options to pause feature updates up to 365 days, quality updates for up to 30 days, and pausing of all updates for up to 35 days:

NOTE: There was a time between Build 1703 and 1709 that the pause duration was lowered to 7 days. To increase it without installing another update, see this article over at Vishal Gupta’s excellent Windows blog.

NOTE: Unfortunately, if you are using Windows Home (not supported by all Rockwell Software) you will not see the above settings:


If you’d like to watch a video of the above, check out Episode 23 of The Automation Minute Season 4 below:



If you’ve run into any of these issues I’d love to hear from you – just click on the “post a comment or question” link below.

And if you this article helpful and would like to support my work, you can pledge $1 a month at TheAutomationBlog.com/join and in return receive free downloads of my sample code, videos, and articles 😉

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

Rockwell Software Stop Working? This may be why (and how to fix it) (M4E23)


In this episode I discuss how recent Windows Patches have caused Studio 5000, View Studio, And RSLinx to stop working. I also discuss how to fix the issues (Episode 23 of The Automation Minute Season 4:)




If you’ve found this video helpful, checkout my training courses here.

Check out our Video Collection #1 here, which includes the first five seasons of our shows for just $30!

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

Windows Meltdown and Spectre Patches Impact Rockwell Software Users

Earlier this week, Bob (a fellow automation instructor and a LinkedIn connection), sent me a message about a serious Windows update issue he encountered after returning from winter break.

Apparently, Microsoft released several security updates for Windows 7, 8.1, 10, Server 2012 and 2016 this month that have been discovered to cause multiple issues with popular Rockwell Software products.

Issues, that in some cases, stop products like Studio 5000 and FactoryTalk View Studio from working.

It appears Bob was on the leading edge of the discovery of these issues, as when he initially called Rockwell Tech Support no public Tech Note had yet been published.

But in the week’s since, Rockwell has now published a public Tech Note (ID 1071234) covering the many issues in quite some detail.

Note: You can view the above mentioned Tech Note here.

The issues reported so far include the following:

  • Inability to log into FactoryTalk Security
  • Inability to select a FactoryTalk Directory
  • Inability to run the FactoryTalk Directory Configuration Wizard
  • Nuisance errors when opening up Studio 5000 Logix Designer
  • Inability to down with Logix Designer because Who Active (RSLinx Classic) doesn’t work
  • RSLinx will not launch due to RSWho error
  • Rockwell Alarm Server service fails to start
  • FactoryTalk Directory fails to start with tray application showing errors
  • FactoryTalk Activation Manager Binding ID list shows as blank, no option to select
  • Installation of View SE generates error because it can’t locate FT Directory
  • RSLogix 5000 revision 20.04 won’t launch
  • Logix Compare Tool throws error message after selecting 2 projects
  • New install of FactoryTalk View Machine Edition generates Activation Failed error.

What exasperates this issue, is how Microsoft (and other vendors) are practically forcing users to install updates, and when those updates are not automatically and silently installed, users are berated with daily update reminders.

Now in my Windows 10 VM article posted last week, I mentioned how I typically set Windows 10 to update as infrequently as possible.

But even then, using Windows’ own built-in options, you can only postpone security updates for up to 30 days, which is not typically long enough for automation vendors to release fixes for issues.

The persistent nature of these updates lead Bob to have to implement a stop gap measure in his classroom.

At the beginning of each class he now has to have his students uninstall the above mentioned MS updates before starting the affected Rockwell Software products.

Hopefully the Rockwell MS Patch qualification team will be able to find workarounds for the affected products soon, so these MS patches will no longer prohibit some of Rockwell’s popular software packages from working.

That said, it’s no small task as currently there are a dozen MS Patches that have been observed to cause “anomalous behavior” with FactoryTalk based products:

  • KB4054517
  • KB4056888
  • KB4056890
  • KB4056891
  • KB4056892
  • KB4056895
  • KB4056896
  • KB4056898
  • KB4056899
  • KB4073291
  • KB4075199
  • KB4075200

If you’d like to watch a video discussion of the above, check out Episode 23 of The Automation Minute Season 4 below:



If you’ve run into any of these issues I’d love to hear from you – just click on the “post a comment or question” link below.

And if you enjoy reading articles like this and would like to support my work you can pledge $1 a month at TheAutomationBlog.com/join and in return receive free downloads of my sample code, videos, and articles 😉

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

How To Replace a PanelView 550 Lamp with an LED (M4E22)


In this episode I walk you through how to replace your PanelView 550 backlight with a new, cooler running LED Lamp (Episode 22 of The Automation Minute Season 4:)

NOTE: See the companion article here




If you’ve found this video helpful, checkout my training courses here.

Check out our Video Collection #1 here, which includes the first five seasons of our shows for just $30!

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney

PanelView 550 Lamp Replacement


So you have a PanelView 550 Series A with a “hard to find” backlight that’s failed and needs replacement?

Well, the good news is that there are several third parties that have come out with an LED version of the lamp that’s inexpensive, easy to install, and runs much cooler that the original.

If fact, I recently purchased one to install in a friend’s terminal, and in this article I’ll share some pictures of the replacement process.


Step 1) Disconnect power from your PanelView 550, then remove the back cover and failed lamp, if it’s still installed (below the cover and lamp have already been removed:)

Step 2) Unscrew the lamp and lens bracket and remove it.

Step 3) Remove the replacement LED lamp from the packaging (you can purchase it here).

Step 4) If you have concerns about the lamp becoming loose, install the anchors:

Step 5) Slide open end of the LED lamp as far in on the fiber bundle as you can:

Step 6) Secure lamp by tightening the set screen (be careful not to over-tighten).

Step 7) Slide the lamp into the metal lamp holder clip:

Step 8) If you installed the anchors in step 6, now go ahead and install the tie wraps (not shown).

Step 9) Plug the lamp connector into the PanelView 500 lamp socket.

NOTE: Since there are no polarity markings on the socket, you have a 50/50 chance of getting the polarity correct. With my PanelView 550, the correct polarity had the Red wire on top:)

Step 10) Replace the back cover and power on your PanelView 550. If the new lamp doesn’t light, power the PanelView 550 back off, and reverse the lamp connector.

Step 11) Once working, replace the PanelView 550’s back cover and you’re finished:


If you’d like to watch a video demonstration of the above, check out Episode 21 of The Automation Minute Season 4 below:



I hope you’ve found the above information above about replacing the lamp on a PanelView 550 helpful.

If you have any questions, or would like to comment on the above article, please feel free to click on the “post a comment or question” link below.

You can also become a Patron to support my work at TheAutomationBlog.com/join and in return receive free downloads of my sample, videos, and blog articles.

Until next time, Peace ✌️ 

If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.

Shawn M Tierney
Technology Enthusiast & Content Creator

Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.

Shawn Tierney