Hi All,
First, although I've been involved in the automation industry for a quite a while, it's been as a software developer and content developer for training programs, not as a PLC programmer. So I apologize in advance for any shortcomings in the following questions.
Platform: ControlLogix
Software: Studio 5000 or RSLogix 5000
No hardware so I can't go online
I'm trying to understand module-defined tags for an EN2T or ENBT Ethernet/IP module. The first thing I noticed was, when I added an EN2T to the I/O Configuration folder, no tags were added to the Controller Tags as they would be for an I/O module or another communications module such as a DeviceNet module. It was not until I added another EN2T module to the network of the first EN2T that Controller Tags had been added. In simple terms, why is that?
The tags created also seem to be just structures as opposed to being module-specific tags like those of an analog I/O module, for instance.
Can someone give me a real-world example of a binary value for the SlotStatusBits and any relationship of that value to the corresponding [module_name]:I.SlotStatusBits.0 - .31?
Also, I'd like an example of the [module_name]:I.Slot[0-31].Fault and [module_name]:I.Slot[0-31].Data.
Lastly, for [module_name]:O.Slot[0-31].Data elements, I'd like a real-world example of a binary value and/or explanation of how these tags are used in the system. Just a high level look.
Thank you in advance. I really appreciate your time.
Mark
First, although I've been involved in the automation industry for a quite a while, it's been as a software developer and content developer for training programs, not as a PLC programmer. So I apologize in advance for any shortcomings in the following questions.
Platform: ControlLogix
Software: Studio 5000 or RSLogix 5000
No hardware so I can't go online
I'm trying to understand module-defined tags for an EN2T or ENBT Ethernet/IP module. The first thing I noticed was, when I added an EN2T to the I/O Configuration folder, no tags were added to the Controller Tags as they would be for an I/O module or another communications module such as a DeviceNet module. It was not until I added another EN2T module to the network of the first EN2T that Controller Tags had been added. In simple terms, why is that?
The tags created also seem to be just structures as opposed to being module-specific tags like those of an analog I/O module, for instance.
Can someone give me a real-world example of a binary value for the SlotStatusBits and any relationship of that value to the corresponding [module_name]:I.SlotStatusBits.0 - .31?
Also, I'd like an example of the [module_name]:I.Slot[0-31].Fault and [module_name]:I.Slot[0-31].Data.
Lastly, for [module_name]:O.Slot[0-31].Data elements, I'd like a real-world example of a binary value and/or explanation of how these tags are used in the system. Just a high level look.
Thank you in advance. I really appreciate your time.
Mark