alias and base tags; difference?

I agree, ugly all the way through. Multiple aliases for the same memory location is the modern equivalent of the double-coil syndrome. Who thought that it could ever be an advantage?

Rockwell needs to add a new Option where you choose how many levels of Aliases you want to allow for the same tag. I would set mine to "1".

Agreed, although you need 2 levels for Rack Optimisation.

The system automatically creates I/O alias tags in the standard "location:slot:type" format (e.g. Remote:3:I), which is an alias for the rack-optimised tag Remote:I[3].

When you create your alias...

e.g.
Start_Button - alias for Remote:3:I.Data.5 - then the base tag will be Remote:I[3].Data.5

That is why the database view shows both "Alias For", and "Base Tag" columns.

Admittedly, you can create your Start_Button alias directly to the base tag, but you now have 2 different-looking tag formats for I/O points. I prefer, and recommend when teaching, to stick with the "location:slot:type" format throughout.
 

Similar Topics

Hi all. From looking at the controller tags list in Logix5000, how do I look at a local I/O base tag and see what alias tags are using it...
Replies
9
Views
4,600
Hey fellas, My question is about best practice for COP ladder instruction in RSL5k when aliases are involved. I'm dealing with some...
Replies
4
Views
3,835
A program I am working with has all its tags in the controller scope. The tags that needed meaningful names for SCADA consumption were aliased...
Replies
2
Views
3,084
This would likely pertain to any scenario but in case it matters, here's mine: I have an array of Dints representing alarm bits, (i.e...
Replies
8
Views
6,009
Hi. I'm using a Modbus ProSoft where I basically map data to a big INT array. Example, where GX_I_63HPU is a REAL, MNETC.DATA.WriteData[200] an...
Replies
21
Views
437
Back
Top Bottom