Hello guys, I would like your help confirming the 1761 NETENI function.
As in the AB manual 1761 UM006E says:
Peer-to-Peer Messaging
This chapter describes messaging between the ENI/ENIW and DF1
devices. The following topics are covered:
• Messaging Between the ENI/ENIW and DF1 Devices
• Message to Configuration Nodes (Nodes 100 to 149) and
Sending a Message to a Destination Controller (Nodes 0 to 49)
Messaging Between the
ENI/ENIW and DF1 Devices
The ENI/ENIW can route a DF1 message received from the attached
controller to a compatible destination TCP/IP device, using DF1 node
addresses 0 through 49. ENI/ENIW Node addresses 100 through 149
store TCP/IP destination addresses. When the ENI/ENIW receives a
write message to nodes 100 to 149, it stores the TCP/IP destination
address in the corresponding map register.
To configure the destination TCP/IP addresses, you can use either the
ENI/ENIW Configuration Utility, or you can send a 485CIF/PLC2
message to each node as described in this section.
EtherNet/IP Connectivity The 1761-NET-ENI and 1761-NET-ENIW provide EtherNet/IP
connectivity for all MicroLogix controllers, CompactLogix controllers,
and other DF1 full-duplex devices. The Ethernet Network Interface,
ENI or ENIW, allows you to easily connect non-Ethernet controllers
onto new or existing Ethernet networks and upload/download
programs, communicate between controllers, and generate email
messages via SMTP (simple mail transport protocol).
EtherNet/IP is an industry standard open protocol which provides
inter-device compatibility. You can exchange information with other
Allen-Bradley Ethernet controllers (SLC, PLC, and ControlLogix) in a
peer-to-peer relationship, so you do not need any master-type device.
The ENI and ENIW also support an SMTP mail service that allows an
existing controller to send email messages to any destination
connected to the network. The email can be used to initiate the
transmission of data or status information.
Is it possible to send a TCP message to an TCP/IP device which is not an SLC?
In this specific case I have a 2D reader QXHAWK which has TCP/IP communication capability and it can be commanded remotely by using a special command language. The thing is, as long as there are no register to access in this reader as in the SLC controllers when using the MSG instruction to write or read, what should I use as the DATA TABLE ADDRESS in the TARGET DEVICE segment of the message setup?
Or does it the NETENI is only focused to messaging between SLC, Micrologix and other AB devices only?
I'll appreciate any comments.
Regards,
IA
As in the AB manual 1761 UM006E says:
Peer-to-Peer Messaging
This chapter describes messaging between the ENI/ENIW and DF1
devices. The following topics are covered:
• Messaging Between the ENI/ENIW and DF1 Devices
• Message to Configuration Nodes (Nodes 100 to 149) and
Sending a Message to a Destination Controller (Nodes 0 to 49)
Messaging Between the
ENI/ENIW and DF1 Devices
The ENI/ENIW can route a DF1 message received from the attached
controller to a compatible destination TCP/IP device, using DF1 node
addresses 0 through 49. ENI/ENIW Node addresses 100 through 149
store TCP/IP destination addresses. When the ENI/ENIW receives a
write message to nodes 100 to 149, it stores the TCP/IP destination
address in the corresponding map register.
To configure the destination TCP/IP addresses, you can use either the
ENI/ENIW Configuration Utility, or you can send a 485CIF/PLC2
message to each node as described in this section.
EtherNet/IP Connectivity The 1761-NET-ENI and 1761-NET-ENIW provide EtherNet/IP
connectivity for all MicroLogix controllers, CompactLogix controllers,
and other DF1 full-duplex devices. The Ethernet Network Interface,
ENI or ENIW, allows you to easily connect non-Ethernet controllers
onto new or existing Ethernet networks and upload/download
programs, communicate between controllers, and generate email
messages via SMTP (simple mail transport protocol).
EtherNet/IP is an industry standard open protocol which provides
inter-device compatibility. You can exchange information with other
Allen-Bradley Ethernet controllers (SLC, PLC, and ControlLogix) in a
peer-to-peer relationship, so you do not need any master-type device.
The ENI and ENIW also support an SMTP mail service that allows an
existing controller to send email messages to any destination
connected to the network. The email can be used to initiate the
transmission of data or status information.
Is it possible to send a TCP message to an TCP/IP device which is not an SLC?
In this specific case I have a 2D reader QXHAWK which has TCP/IP communication capability and it can be commanded remotely by using a special command language. The thing is, as long as there are no register to access in this reader as in the SLC controllers when using the MSG instruction to write or read, what should I use as the DATA TABLE ADDRESS in the TARGET DEVICE segment of the message setup?
Or does it the NETENI is only focused to messaging between SLC, Micrologix and other AB devices only?
I'll appreciate any comments.
Regards,
IA
