Hello everyone, I am currently working with a 1756-L73S Controller and a Fanuc Robot that is configured as follows: The Fanuc Robot is mapped in Slot 2 of the 1756-EN2TR module as an Ethernet-Module R01_R1 with the IP address 192.168.1.16, and in Slot 3 as an Ethernet-SafetyModule R01_R1Saf with the same IP address. Both modules are connected to different ethernet switches: Slot 2 and the Fanuc controller are connected to ethernet switch 1, which is then linked to ethernet switch 2 where Slot 3 is connected. I attempted to put both R01_R1 and R01_R1Saf in the same slot, but encountered an error due to the duplicate IP addresses. Can anyone provide guidance on resolving this issue?
The Rockwell Ethernet safety module offers both standard and safety tags. Rockwell PLCs feature generic Ethernet module options in the IO tree configuration. The standard generic Ethernet module allows users to define any user-configurable device without requiring an EDS file or additional software, as Rockwell generates the "devicename:C" tag. However, multiple connections from the same controller to the same device through different slots could lead to complications. Learn more about Ethernet safety modules on www.plctalk.net.
Thank you so much, I will investigate further and keep you updated on my findings.
It seems that there may have been a misunderstanding in the problem description. According to you, there are two separate EtherNet/IP communication boards linked to the same network using identical IP addresses. EtherNet/IP has a feature known as "address conflict detection," which, although not mandatory, is widely supported by modern devices. If the Fanuc device has this feature and what you have mentioned is accurate, one of the devices should be experiencing an IP address conflict, as indicated on the teach pendant. If this feature is not supported, the system will not function properly because the EtherNet/IP scanner will not permit the configuration of two devices with the same IP address. I hope this information is of assistance.
Back in the day, I have experience working with a Fanuc robot where the Logix firmware did not initially support both "non-safe and safe" connections over the same generic device. I recall reading in the FANUC manual about a clever workaround involving running a DNS server on the Fanuc robot. By assigning the Generic Safety as the IP address x.x.x.x and the Generic Non-Safety as the hostname "robot" on the same EN2T, we were able to resolve the hostname to the same IP address. This allowed Logix to accept the setup, even though non-safe and safe connections are technically separate entities that can function on the same IP address. Unfortunately, Logix Studio did not facilitate this configuration, although it was perfectly feasible. The key was to set the Fanuc IP address as the DNS server for the EN2T and configure the DNS server on the Fanuc robot accordingly. It took some time to piece it all together, but the solution ultimately proved effective.
To effectively transmit both safe and non-safe data to your Fanuc Robot, be sure to utilize the AOP tool available for download on the RA website. It is crucial for the PLC to set the SNN for Fanuc operations, and the AOP simplifies this process for seamless communication. Failure to do so can result in a frustrating experience.
One possible solution could be to assign unique IP addresses to each module to avoid overlap. It's generally not best practice to have two devices sharing an IP within the same network. Having unique IPs would enable the controller to differentiate and communicate with both modules. Another approach could be subnetting, which allows multiple devices on the same network to share a single IP, but this might require more knowledge and effort to set up. Do keep in mind as you're troubleshooting that each switch and every piece of interconnectivity should also be reviewed for errors or potential misconfigurations.
It sounds like your setup is having an IP conflict when you try to put both modules in the same slot. A common practice to deal with duplicate IP issues is to give each device its own unique IP. However, you could also consider configuring VLANs on your ethernet switches. This will allow you to segment your network and isolate the traffic for each module, even if they're on the same IP. This should work effectively if your Ethernet switches support VLAN tagging. Always remember to test and verify connectivity after making these changes!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - The duplicate IP addresses error occurs because both modules (Ethernet-Module R01_R1 and Ethernet-SafetyModule R01_R1Saf) are configured with the same IP address (192.168.1.16), causing a conflict in the network.
Answer: - To resolve the duplicate IP addresses issue, you need to assign unique IP addresses to each module. Modify the IP address of either the Ethernet-Module R01_R1 or the Ethernet-SafetyModule R01_R1Saf to ensure they are different within the network configuration.
Answer: - Having duplicate IP addresses in the mapping of Fanuc Robot controller modules can lead to network communication issues, conflicts, and disruptions in the operation of the system. It is essential to avoid duplicate IP addresses to maintain a stable and efficient network environment.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.