RSLogix 5000 Tag Structure - Creating Alias Tags for PLC Input Output Modules Point IO Studio 5000

RSLogix 5000 Tag Structure - Creating Alias Tags for PLC Input Output Modules Point IO Studio 5000
Visit SolisPLC.com for more Tutorials, Information & to connect with the Community
Tag aliasing is a concept which is particularly important in RSLogix 5000. The reason is that most RSLogix 5000 based Programmable Logic Controllers (PLCs) aren’t able to save tag descriptions within their memory. If the program is lost & needs to be uploaded from the controller, it will be restored without a single description. However, if you’re working with Studio 5000 v21 or above, your PLC will most likely have the capability to store the descriptions you add into your program.
In short, we’d recommend using tag descriptions in Studio 5000 and tag aliasing in RSLogix 5000. This ensures that you have a meaningful comment about the tag within your program and that whoever is going to work with it going forward is aware of what’s going on.
Tag aliasing isn’t a complicated concept, but it still surprises PLC programmers who are learning RSLogix 5000 for the first time or simply haven’t encountered this practice in other software packages such as RSLogix 500.
Default Tag Names for Input & Output Modules in RSLogix 5000
Input and Output modules are a critical component of every control system. No matter how small your system is, you’ll have at least a few local input or output cards which will receive feedback from field devices. Adding one of these modules is very simple in RSLogix and can be done by right-clicking the appropriate communications medium (EX: EtherNet, ControlNet, DeviceNet) and selecting “Add New Device…”. A prompt will be presented and allow the user to find the appropriate device from the Allen Bradley catalog. Once it’s selected, you will be prompted to enter the parameters of the module: give it a name, configure options, etc.
Full Tutorial: solisplc.com/rs...
Find us on social media:
Web: solisplc.com/
Forum: solisplc.com/f...
LinkedIn: / solisplc
Facebook: / solisplc
Instagram: / solisplc
Twitter: / solis_plc
Other Cool Content:
PLC Input Output Mapping / Buffering | IO Addressing Basics in RSLogix Studio 5000 Allen Bradley
• PLC Input Output Mappi...
PLC HMI Programming Project | Development Tutorial Beginners Ladder Logic Diagram RSLogix | Part 3
• PLC HMI Programming Pr...
RSLogix & Studio 5000 Produced and Consumed Tags | PLC Data Concentrator SCADA, Messaging, EtherNet
• RSLogix & Studio 5000 ...
HMI Development | FactoryTalk View Studio ME Rotation Animation Tutorial | Pump Fan Motor Program
• HMI Development | Fact...
PLC Vlog#1 - Which PLC Hardware to Buy, When to Invest & What You Should Know before Purchasing PLCs
• PLC Vlog#1 - Which PLC...
Relevant Search Terms
rslogix 5000 tag structure,rslogix tags,rslogix tag structure,rslogix alias,alias tags,rslogix 5000 alias tags,rslogix 5000 alias tags,rslogix 5000 alias tag,rslogix 5000 alias,rslogix 5000 alias,rslogix 5000 alias array,creating alias tags in rslogix 5000,studio 5000 alias,studio 5000 alais, studio 5000 alias tags,rslogix 5000 tag structure,rslogix 5000 udt alias

[@alancordeiro3491]

Thanks! I've always wanted to understand that, and you made it super clear

[@Enigma758]

I understand that aliases are one to many whereas you prefer comments because they are one to one. However, I believe there are other reasons to use aliases. For example, I would prefer to write code that resembles "XIC PackageReadyLimitSwitch" rather than "XIC Local:I:1:0". The former is in terms of my application, not the physical hardware layout. In fact, I may not even be able to provide the latter since I haven't even considered my I/O layout yet. Also, I think it is better to write code in application terms, and not physical I/O terms which are likely to be wrong, especially if I want to write reusable code fragments. True, multiple instances of the code fragment may require me to provide unique names for each instance such as "PackageReadyLimitSwitch1" and "PackageReadyLimitSwitch2, but at least I can achieve some semblance of modularity/reusability this way.

[@SolisPLC]

This is a huge debate in our industry and there's unfortunately no standard for this. I agree that there's a point where it's easier to create tags and to alias them to the right IO later. However, consider this - What I'd typically do is create all of the tags I need for programming regardless of the I/O that will be in the system - Ex: Control_INT[0], Control_INT[1], etc. I would then use those integers in my program without any consideration of IO. Once I'm done and the I/O is pecified, I can use a MOV or COP instruction to map all the I/O into those tags. If I want to be able to shift the addressing, I can do individual mov instructions. All without aliasing.

[@Enigma758]

@@SolisPLC Yes, I remember when working with the old PLC5, we would map the I/O that way using explicit copy instructions. But really, I always viewed aliasing as a better way to accomplish the same task and without actually paying the price to both write mapping code and having to waste cycles by physically moving the data. I believe that was the intent.

[@tradingsvivi1216]

Thanks again

[@almoqid]

Thank you for the video. It's useful for someone coming with Siemens background.
I have a quick question: why would a programmer create 2 different tags and allias them to the same I/O point?

[@SolisPLC]

Hi Abdel, that's a good question. There's really no point in doing so, but I've seen it done. Typically, this comes from either forgetting that the tag was already created or the person making new changes needed their own. For example, the system was built with a "Motor Start" output, 2 years later, a technician was asked to stop the motor based on a new switch and he creates a new tag instead of using the current one. Trust me, it was confusing to me to see that.

[@mab9316]

Thank you.

[@SolisPLC]

You're welcome!

[@mrtrader4628]

trying to toggle input on, but it will not turn on and the date table will not receive a 1.
This CLX 1756-l71 PLCv21 has in the rack with 1756 IB16, 1756 OB16, 1755 IB32, 1756 ENBT/A
2.
But there is also an PV 1000HMI also in these cabinet could this be use instead of real field device connected.
Trying to follow a class but not matching when I look at rack.
any help thanks.

[@tylerbaker555]

Do you have to be online/connected with a PLC processor in order to alias a tag or asign it to an input data bit? I have tried to do this practicing without a connection and no output or input data selections pop up?

[@benc8030]

Great Video. Vlad, can you post a video on ethernet losing comms on all devices connected thru ethernet

[@dperez-tv1lr]

ok what about configuring the actual physical inputs?
i liked rs link 500 much easier to understand

[@Iisidjenejiirjrkgawdcv9888yyyt]

Before you say, "Lets get into it...." do your sales pitch! Just saying.

[@mohammaddhimesh433]

unusful