Hello everyone, it's been a while since my last post. Three months ago, I began a new role as a corporate automation engineer. Since then, I have had many opportunities to troubleshoot a lot of code, especially in Rockwell Studio 5000. Some plants standardized on Wonderware 2011 a while back. Now, let's dive into the topic at hand. These plants using Wonderware and programmed via Rockwell Studio 5000 are heavily relying on aliasing. When I first started delving into the world of Allen Bradley (AB), I found aliasing to be useful, but soon discovered some drawbacks and eventually stopped using it as it was deemed "bad". Can anyone provide insights on the advantages and disadvantages of aliasing and shed some light on why integrators chose to use this method? Thank you all.Chris
The excessive use of aliases can lead to major maintenance issues, which is why I tend to avoid them. One drawback is that aliases cannot be edited online. In order to avoid this, I typically create a routine that links tags to other tags when necessary. This process involves assigning actual hardware inputs or outputs to a specific tag that corresponds to the device as labeled on the electrical schematics. For instance:
One of the best aspects of using Aliases is the ease of working with legacy programs for critical equipment. These Aliased tags remain unchanged during online edits, making it convenient for making updates without affecting production. In addition to Aliased tags, you may come across directly referenced IO tags within a continuous task instead of a periodic one, as well as IO tags buffered in a routine. This mix of referencing styles can be found in the code for Palletizing and Conveyor lines, showcasing a variety of methods used to interact with IO in an inconsistent manner.
I typically set up an array of DINTs named BITS to manage various bits required for one-shots, holding coils, and more. To do this, I assign a tag to a specific bit within the DINT array as needed.
In the world of industrial automation, excessive use of aliases can lead to major maintenance issues. That's why I tend to avoid them, as they cannot be easily modified online. Instead, I rely on a routine that links tags to other tags when necessary. This is how I connect actual hardware inputs or outputs to a tag named after the specific device indicated on electrical schematics. For example, see attachment 71444 for a visual representation. This method has become my go-to approach, as I moved away from using Aliases due to their troublesome nature.
Ken Moore explained his strategy of creating arrays of DINTs, such as BITS for one shots and holding coils. By aliasing tags to specific bits within the DINT array, he avoids unnecessary tag creation. Instead, he utilizes unique tag descriptions to directly access the required bits. This approach helps prevent controller tag overload and streamlines communication efficiency, especially when dealing with a mix of Oneshots and HMI status bits. Avoiding unnecessary tag aliasing can optimize data transfer and prevent inefficiencies in reading 32-bit DINTs for specific status bits among unrelated data.
Hi Chris, congratulations on the new role! In my experience, aliasing in Allen Bradley PLCs can be a double-edged sword. Aliasing can indeed be beneficial when you are reconfiguring hardware or shifting inputs/outputs without rewriting the program. It creates an additional layer of abstraction, which can make systems more understandable by allowing naming of inputs/outputs relevant to their purpose. However, the downside of aliasing, as you noticed, is it can make troubleshooting difficult--especially when an alias points to an alias or when you're working with someone else's code. Debugging can become frustrating trying to trace back to the original tag. As for why certain integrators choose this method, it might be related to personal style, client's demand for flexible code, or simply what they find more efficient.
Hey Chris, welcome back to the forum! I've faced a similar scenario in my work with AB, although I still use aliasing somewhat frequently. One of the main advantages is that aliasing can make your code simpler and easier to read, especially if you've got a complex system that deals with many devices. However, the drawbacks can certainly outweigh the benefits in certain scenarios. For instance, troubleshooting can be a real pain as it becomes difficult to trace the root cause of a malfunction. Additionally, managing aliases can become cumbersome in large applications and can cause confusion if not documented properly. In my guess, your integrators probably prioritized initial readability and simplicity over potential troubleshooting efforts later down the line, which is indeed a common trade-off in our field.
Hi Chris! Welcome to the world of corporate automation—it can be quite the journey! I definitely see the appeal of aliasing; it streamlines reference points for tags and can simplify code management, especially in larger systems. However, as you noticed, it can lead to confusion during troubleshooting since you’re essentially adding another layer to the actual data. Some integrators swear by it for its efficiency in reducing repetitive typing and making overall code cleaner, but flexibility can come at the cost of increased complexity. It’s all about finding the right balance for your specific projects, so play around with it and see what works best in your environment!
Hey Chris! Great to see you jumping into corporate automation; it can be quite the journey! Aliasing in Rockwell Studio 5000 definitely has its pros and cons. On the plus side, it simplifies code management and makes it easier to handle changes across multiple instances, which is super helpful in larger systems. However, the drawbacks can really trip you up—like when it leads to confusion over variable references or makes troubleshooting a bit more challenging if you’re not careful. Integrators often opt for aliasing to reduce redundancy and streamline updates, but it’s essential to weigh that against the potential for added complexity down the line. Have you found a strategy that balances these aspects in your work?
Hey Chris! Welcome back to the forum and congrats on your new role! I totally understand your concerns about aliasing in Rockwell Studio 5000. While aliasing can simplify your code and make it more readable by using meaningful names instead of raw addresses, it can sometimes lead to confusion, especially if not properly documented or if the references change. One advantage is that it allows for easier updates; you can change the underlying address without having to rewrite your entire program. On the downside, if you're troubleshooting or working with multiple integrators who may not be as familiar with the aliasing setup, it can create a bit of a learning curve. It might be worth considering a balanced approach—using aliases where clarity is essential, but keeping the raw addresses handy for those complex troubleshooting sessions. What do you think?
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - Aliasing can simplify the programming process by providing a way to reference tags using user-defined names, making it easier to understand and maintain the code. - It can help in integrating systems from different platforms, such as Rockwell Studio 5000 and Wonderware, by creating a common interface for communication.
Answer: - Aliasing can lead to confusion and errors if not managed properly, especially when dealing with complex systems and multiple integrators working on the project. - It may introduce delays in troubleshooting and debugging, as the true source of an issue might not be immediately apparent due to the abstraction introduced by aliasing.
Answer: - Integrators often use aliasing for its convenience in mapping and referencing tags between different systems, which can speed up development and deployment processes. - The use of aliasing may have been initially adopted for historical reasons or to align with existing standards within the organization, even if it comes with certain challenges.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.