Thank you for all this information, I have gone to our cooperate IT with the things you have helped me find to see if this is a simple problem to go about fixing. Ill post updates in case it helps out anybody in the future.
Posts by Hooks85
-
-
I also forgot to add that theses robots have been running for years, nothing was changed intentionally recently.
-
-
1. Six of our robots are hooked up to the network, four using Modbus and of those four this error has happened on only three. We have about 25 Keyence vision cameras also on our network as our other machines that as far as I know are not being affected by this issue.
2. Slave is Wago 750-352 on all four robots.
3/4 This is the reason I'm having a lot of trouble, I have very limited experience with networking, as far as I can tell from the documentation the It guy and the former robot guy left there are no conflicting IPs, but who knows if its right and I'm not sure an easy way to check this. We have almost 200 devices total on this network.
What do you mean by communication architecture and r/w frequency? How would I be able to see this stuff?
6. I am able to ping each device.
Each of these robots are in a different system, but they will all get this error simultaneously. Its very intermittent, happened around 10 am yesterday and haven't seen it since. Once the robot displays this error the operator can come over and hit ok and resume the program again.
We had a problem with our sprinkler system a couple weeks ago and the server room was effected, I have noticed since then this has been happening more frequently.
Here are some screenshots of the error
-
Hello everybody, long story short, I am at a company where the only person with any knowledge about automation quit 2 weeks into training me, and this is my first job out of collage so I have very limited experience with automation. Apparently this problem has been happening for a long time
I am having a serious problem where simultaneously, all of my UR robots on different systems will get the error Modbus signal is not connected to slave. Sometimes this will cause the UR robots to hold and send a fault signal to the rest of the system like it should, but in this scenario the UR robots stopped while the rest of the system kept running which damaged the machine because these UR robots are spraying lube. I need to try and fix this error to see if this is the reason the machines keep running after they should be faulted because the UR robots are not spraying lube. These systems are all hooked up to one network which I also have no experience with and our IT guy quit last week. I am going to be putting in a "heartbeat" to make it so if the machine does not see and output from the robot for a certain about on time, it will fault out and an operator has to come and clear the fault before it makes another shot, but this is not a permanent solution. I know I haven't provided many details about models of things and software versions, nothing is documented here and all of the hardware is in a place i cant get to when the machines are running. I will answers questions as soon as I can.