grnick50
Lifetime Supporting Member
Can someone please explain to me what is the purpose of alias in the RSlogix5000 tags? How is this feature used?
Regards
Nik
Regards
Nik
Same as a "Symbol" used in the "Symbol Table" in step 7.Can someone please explain to me what is the purpose of alias in the RSlogix5000 tags? How is this feature used?
Regards
Nik
One drawback of using aliases is that it is not easy to change what the alias is referencing. Using the above example, maybe we want to make "EndOfStrokePX" aliased to "InputCard:1:I.4". Your options are to go offline and re-download (not always an option), or to get creative.
keshik said:...One drawback of using aliases is that it is not easy to change what the alias is referencing...
Paully's5.0 said:Yeah, I think part of this is that if this tag is 'on-scan' from an HMI/SCADA system it prevents you from modifiying it. If it isn't 'on-scan' I typically just rename 'EndOfStrokePX' to 'EndOfStrokePX_A' (this doesn't work if it is 'on-scan'). Then create a new tag of 'EndOfStrokePX'. Delete the old one once all the references have been removed. A hassle yes, but not too complicated if you are in a pinch.
Welcome to the forum! The answer may depend on the HMI in question. FT View has the ability to access the alias tag name, so this is not an issue.But if, as Daba said in his excellent description, the data is packed into arrays to send to the HMI, how is the data identified to the HMI builder? Is there any way the UDT packed array can transfer the aliasing or other description?
eg. Presumably the HMI builder receives only HMI_AxisData[37] so how do they identify that as Z_Axis_MaxTravel_SP?