I have extensively researched the process of connecting an Automation Direct C-More EA9 series HMI to a FANUC robot, but so far, I have not been successful. Some sources suggest that it can be done, while others believe it is impossible. The FANUC robot has the R-553 HMI option, which emulates a GE 90/30 PLC. I have confirmed that the robot controller option is working properly and that the robot registers are correctly mapped using Kepware on my computer. The HMI is set up to utilize the GE 90/30 SRTP Ethernet driver, which FANUC claims to be compatible with. However, I am encountering a PLC-001 PLC Communication Timeout on the HMI. Can anyone provide guidance on establishing communication between these two devices? I have encountered enough clues to suggest that they are attempting to communicate, but I may be overlooking something or they may truly be incompatible. Your insights are appreciated.
Are you required to configure the robot's HMI option? The C-More SRTP driver requires %I addresses for inputs, %Q addresses for outputs, %M addresses for internal discretes, and %R addresses for 16-bit data registers. Since these addresses are not native to the robot, it is likely that the HMI option maps robot addresses to SRTP addresses.
I successfully completed memory mapping on the robot and confirmed my ability to access different I/O types and registers using Kepware server software on my computer.
It may be time to contact AD tech support for assistance. My experience with C-More and a GE driver is limited to using an EA-7 with serial communications (SNPX protocol). The ethernet driver (SRTP protocol) for GE was introduced with the EA-9 series. I do not have practical experience with it. Could the issue be related to a port number? The robot typically defaults to using port 18245 according to this document. What port is the C-More attempting to use? Check out this link for more information on General Electric's SRTP protocol: https://doc.ipesoft.com/display/D2D...RTP+protocol#GeneralElectricSRTPprotocol-R30i.
While both FANUC and AD tech support have been cooperative, neither have been able to offer a solution, often deflecting blame onto one another. Despite confirming the correct port settings, this troubleshooting process has spanned several weeks. Recently, I achieved a breakthrough by establishing communication between the HMI and a modbus driver. The memory mapping for the robot with Modbus seems disorganized, but it appears to function adequately for my current requirements, though it falls short of being ideal.
Robot_Guy expressed frustration with the lack of solutions provided by FANUC and AD tech support, as they have been pointing fingers at each other. Despite this, progress has been made in establishing communication between the HMI and robot using a modbus driver. Although memory mapping with Modbus for the robot is not ideal, it seems to be sufficient for the tasks at hand. The goal is to display pendant information, including alarms, on the HMI screen. The setup involves an R-30iB Mini Plus (CRX-10iA) robot connected to an A.B. CompactLogix PLC via ethernet. The HMI panel is configured to communicate with the PLC using the "GE Ethernet SRTP (90/30 Rx3i)" protocol and with the robot using standard SNPX. Despite SNPX typically being used for direct connections with robots via RS-232/485, the setup is being tested. The IP address of the robot is entered in the Panel Manager of the HMI, and ASCII strings are used in registers for communication. The robot can successfully ping the HMI panel, but further testing is needed to determine the optimal IP port settings for communication. The focus is on establishing a reliable connection to display pendant information on the HMI screen.
From your description, it seems like you've done a thorough job setting up and troubleshooting this issue. I also have some experience connecting HMIs to FANUC robots and had a similar issue. The problem might not be with the compatibility, but in the communication settings. Have you checked both your HMI and robot controller for matching communication parameters like baud rate, parity, stop bits, etc? If there's a mismatch somewhere, it could cause a communication timeout. Also, try reaching out to Automation Direct's tech support - they were quite responsive and helpful in my experience.
I recall encountering a similar issue in the past when connecting an HMI to a FANUC Robot. A communication timeout typically indicates some sort of mismatch or miscommunication in the settings. Specifically, you might want to double-check your Ethernet settings on both the Robot and the HMI, particularly the IP address, Subnet, and Gateway. Also, ensure that the R-553 HMI option you mentioned is correctly configured and mapped to use the Ethernet port. Lastly, check whether the SRTP Ethernet driver you're using on the HMI side is updated to the latest version. Bear in mind that while establishing such connection can be tricky, it is certainly not impossible. FANUC wouldn't claim compatibility if it didn't exist. So, keep looking, and don't be discouraged!
I walked through a similar situation once and what I found was that the timeout issue might be due to improper setting of the communication rate between the devices - it's crucial to ensure that they're both operating at a compatible pace for efficient data exchange. You might want to check and possibly adjust the configurable settings on your HMI device. Additionally, ensure that your HMI and FANUC robot are in the same subnet - that's another common tripping point. If both these aspects are looking good, another troubleshooting step is updating your device drivers. The problem might be that your current drivers aren't supporting this specific communication. If none of this works, it could indeed be a compatibility issue, despite the purported claims.
✅ 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: Answer: To connect a C-More EA9 HMI to a FANUC robot with the R-553 HMI option, ensure that the HMI is set up to utilize the GE 90/30 SRTP Ethernet driver, which FANUC claims to be compatible with. Verify that the robot registers are correctly mapped using Kepware on your computer.
Answer: Answer: The PLC-001 PLC Communication Timeout on the HMI could be due to incorrect settings, incompatible communication protocols, or misconfigured parameters. Double-check the settings and ensure that the communication parameters match between the HMI and the FANUC robot.
Answer: Answer: When troubleshooting communication issues between the C-More EA9 HMI and FANUC robot, check the network settings, communication protocols, cable connections, and ensure that both devices are configured correctly. Verify the compatibility of the communication drivers being used.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.