I am a new user on this forum (but fairly experienced in RSlogix navigation and editing) and have tried to search this topic so if it is here please direct me and I'll stop wasting everyones time, heh heh.
My question: I have noticed different structures of base tags in rslogix5000 controller/program tag database for allen bradley flex I/O modules. Can anyone please explain why some naming conventions differ? I can't figure out especially on the digital modules why some use "location:type.data[slot].bit" and others use "location:type:slot.data.bit" in their tag structure. I have some examples posted below with Program tags that Alias Controller Base tags. I notice this when looking in the program tag database window with the "Edit Tags" active (not "Monitor Tags")........
Ex 1. 1794-IE8/B Analog Input module: UF0085 channel 6 (UF0080 is an ACNR, module is in slot 5, channel 6 connected to a 4-20mA pressure transmitter)
Base Tag is UF0080:5:I.ch6Data with Program tag name PDT6050 (aliasing the base tag on the left)
I understand that ch6Data means its analog data and is using all of the binary bits ch6Data.1 & ch6Data.2 etc......so this isn't a problem for me
Ex 2. 1974-OB16P/A Digital Output module: UF0092 channel 3 (channel 3 connected to a binary run command for a motor)
Base Tag is UF0090:O.Data[2].3 with Program tag name M6041 (Alias For the base tag on the left)
I don't know the rules to why this structure is the way it is.
Ex 3. 1794-OB8EP/A Digital Output module: UF0080 channel 4 (channel 4 connected to a binary motor pump command)
Base Tag is UF0080:0:O.Data.4 with Program tag name M6020 (Alias For the base tag on the left
I see this structure in Rockwell's literature pdf: 1756-pm004 Logix5000 Controllers I/O and Tag Data
My question: I have noticed different structures of base tags in rslogix5000 controller/program tag database for allen bradley flex I/O modules. Can anyone please explain why some naming conventions differ? I can't figure out especially on the digital modules why some use "location:type.data[slot].bit" and others use "location:type:slot.data.bit" in their tag structure. I have some examples posted below with Program tags that Alias Controller Base tags. I notice this when looking in the program tag database window with the "Edit Tags" active (not "Monitor Tags")........
Ex 1. 1794-IE8/B Analog Input module: UF0085 channel 6 (UF0080 is an ACNR, module is in slot 5, channel 6 connected to a 4-20mA pressure transmitter)
Base Tag is UF0080:5:I.ch6Data with Program tag name PDT6050 (aliasing the base tag on the left)
I understand that ch6Data means its analog data and is using all of the binary bits ch6Data.1 & ch6Data.2 etc......so this isn't a problem for me
Ex 2. 1974-OB16P/A Digital Output module: UF0092 channel 3 (channel 3 connected to a binary run command for a motor)
Base Tag is UF0090:O.Data[2].3 with Program tag name M6041 (Alias For the base tag on the left)
I don't know the rules to why this structure is the way it is.
Ex 3. 1794-OB8EP/A Digital Output module: UF0080 channel 4 (channel 4 connected to a binary motor pump command)
Base Tag is UF0080:0:O.Data.4 with Program tag name M6020 (Alias For the base tag on the left
I see this structure in Rockwell's literature pdf: 1756-pm004 Logix5000 Controllers I/O and Tag Data
Last edited: