I/O messaging is based on UDP/IP, and utilizes Multicast addressing when sending PLC input assemblies. It is the default
mode of operation for I/O messages in PLCs. Many PLCs also support Unicast (direct) addressing for PLC input
assemblies, but need to be specially configured.
Because I/O messaging uses UDP/IP and Multicast, it requires special, managed switches, and customized switch
configuration. Managed switches, when properly configured, prevent multicast devices from flooding the network with data.
Consult with your IT department to make sure that you have the correct switch type, and that these switches have Internet
Group Management Protocol (IGMP) snooping enabled to allow them to manage multicast groups.
Some switches with built-in firewalls block UDP traffic by default. If this is the case, and if the path between your devices
involves several switches or routers, it is possible that some of them might block the UDP traffic necessary for I/O
messages. Consult with your IT department to verify that your network is configured correctly.
Establishing CIP and EtherNet/IP I/O communications is a complicated process. There are several steps during which an
error can occur. Industrial Protocols log contains a detail description of the communications process, and should be
consulted if any errors are suspected.
Figure 184. Communication Log Detail Screen
A great level of detail is also provided in the log when the I/O connection is established.
Figure 185. Industrial Ethernet Screen
Figure 186. Communication Log Detail Screen
After the CIP and I/O connections are established, the Industrial Protocols Status screen shows the details of the
connection.
Figure 187. Industrial Ethernet Status Screen
Most of the errors in establishing the CIP and I/O connections have to do with specifying the proper Input and Output
Assembly Instance IDs and sizes. Refer to the appropriate sections of this manual for this information.
iVu Plus BCR Gen2 Series Sensor
172
www.bannerengineering.com - Tel: + 1 888 373 6767