I am currently a student studying robotics. For my final project I have been trying to get and lrmate 200 ic to communicate with an Allen Bradley plc. I have installed the Ethernet ip adapter and configured my setting on the teach pendant as the ethernet ip manual has stated. Same for using the generic Ethernet module in rslogix 5000. My issue arises when I try to ping from the robot to my pc or the plc. It says the ping times out, but when I use command prompt on my pc for a ping to the robot it finds it no problem. I also find the correct info when I type in the robot ip address on a web browser. Any ideas? what my problem is thought maybe it's a system variable setting possibly? but would like some more opinions.
Ethernet ip adapter installed but having issues ponging from the robot
-
Tigblake -
February 15, 2018 at 12:02 AM -
Thread is marked as Resolved.
-
-
Is your robot and plc communicating? In setting up many robot to plc connections I have never had a need to ping from the robot.
-
No it is not. I tried using Fanuc robotics add on module no luck so I reverted to the generic Ethernet module and set the setting from the Fanuc manual and matched them with the mapping of my I/O on the tp. When it said it wasn't connecting I figured trying the ping was a good place to start but it failed when doing it from the robot. So I tried on the pc and it came back good. Agree with you though when I did it at my internship with an integrator never had to ping or encountered a problem like this.
-
A few more notes. In setting up the generic Ethernet module I set it to data integer, input assembly instance to 101 with 4 words as size, output to 151 and 4 words, and configuration to 100 and 0 words, it also matches the Ethernet ip configuration on the tp. Just thought I'd clarify since I've seen that on earlier threads.
-
Do you have the robot set as an adapter or a scanner?
You shouldn't have to set up the assembly instances on the robot, only the plc. The robot should be set as an adapter.
-
Robot is set as an adapter. And I now thinking about realize I was not able to put the I/O assembly instances on the robot as you stated. Sorry for the confusion I'm fairly new at this. Thanks for the feedback. Is it possible I goofed in my system config settings?
-
Please provide more information.
Do you have the IP addresses set correctly in both the plc and robot.
Is the connection enabled in the robot. What is the status?
Any error messages?
What controller model?
What is your io config for UOP and DI/O?
-
R30ia mate controller, ip's are both set correctly, i have prio 230 and 231 error, ethernet ip menu on the pendant says online but i know it supposed to say running. UO 1-8 are rack 89 slot 1 start 21, UI 1-16 are rack 89 slot 1 start 23, DI121-184 rack 89 slot 1 start 1, DO 121-184 rack 89 slot 1 start 1. I believe I enabled the connection but could be wrong what menu would that of been in?
Thanks again for helping
-
If by enabled you are referring to the Ethernet ip menu under type in IO then yes it's set to true.
-
I just read in the internet options setup and operations manual about a system variable $SFAC_ENABLE. I assume since it's for ftp it's not an issue but honestly haven't checked if it's enabled. Thought maybe could be a problem?
-
Yes, the eip set to true is what I meant so you are good there.
So you can get to the robots webpage and get online with the plc via Ethernet?
Nothing else on the network already using those ip addresses? Check by pinging when device is off.
Robot and plc are on the same subnet?
What is the rest of the error message with prio-230?
PLC module settings does not use multicast and what is the rpi set to?
Also another person had the following issue in an older post:
"Gentlemen,I got it to work - turns out the development PLC i was using had some sort of ethernet port restriction or configuration issue.
Thank you for all your help and verification that everything was set up correctly, and that there was another issue!
Andy"
-
Plc and robot are on the same subnet, the error code is stating that the adapter is idle which just means connection isn't there. Plc module is set to unicast and 32 rpi. What would I do or how would I check if the plc Ethernet port has the restrictions you mentioned? And how could I change those restrictions if that is the issue?
-
I don't know, I'm not sure what he meant by "development" plc, it was just something that was posted before that may help.
One idea, do you have any other EIP adapter devices that the PLC can control, such as a VFD? If you can prove that it works with other devices it will help isolate the problem.
-
Try to ping from the robot the robot IP address, if unsuccessful, something is wrong in the robot port setup.
Ensure there is no IP conflict on the network.
If the controller has 2 Ethernet ports, they cannot be on the same subnet.
In the EIP adapter setup, change the alarm severity from the default STOP to WARN. -
It is set up to warn and ping to robot ip is successful.
-
Post here the screenshots of the PLC module setup (all tabs).
-
I know this seems to simple but.... when i am setting my Robot IP address or trying to Ping the PLC IP address, once entered i have to cycle power on the robot. Otherwise it gives me the same Ping Timeout message.
-
Anytime you change the TCP/IP settings you need to cycle power.
-
I know this seems to simple but.... when i am setting my Robot IP address or trying to Ping the PLC IP address, once entered i have to cycle power on the robot. Otherwise it gives me the same Ping Timeout message.
Anytime you change the TCP/IP settings you need to cycle power.If you don't want to reboot, you can hit next on the TCP/IP, then hit F3 for INIT. It re-initializes the comms without a reboot.
-
I changed the assembly instances applies them then downloaded. Then went offline and changed them back to the right ones now I'm online. I don't understand how this worked but it did...
Thanks to everyone for helping me through the process!