Hopefully this isn't a repeat issue. I did a search in robot forum and didn't find anything.
We've got a large installation of 180+ Fanuc robots. Key Points:
- Less than 20 have this problem.
- Of those, 90% are MIG welders. (Possibly Coincidence)
- Of key note is that with the MIG robots any MIG that controls an Aux axis doesn't have this problem. (Possibly Coincidence)
- Backups are on Port 3. This was a Fanuc change per this customers request.
- Ring Network (shouldn't matter)
- The port 3 works with web server using internet browser. Just not back ups on these 20 robots.
- All robots running v8.30
- Regular USB backups work fine.
The problem is that doing a back up Using Eric's Robot Backer Upper (I'm sure a few of you have used this), it doesn't back up the robot. With the old version of his backup program it just looked like it completed without downloading everything. The new version has an error message. Failed to connect to remote server.
This is the first time I have ever encountered this so I am fairly sure it's a set-up issue either by us / the integrator, or Fanuc when they did their general set-up for the customer (free issued robots with pre loaded options / packages).
Things I have done so far:
- Validate TCP and Subnet mask settings. As an FYI this is done as a simultaneous backup for 12 robots (zone) at a time and only certain robots failed to download so I don't see it as an issue on my PC's end as it backs up the robot right beside it no problem. And other projects have never caused problems either
- Checked to make sure cabling is correct. I'm fairly certain it is because I can see the robots on the network. Also Eric's back up program will grab the MAC id. So there is communication occurring.
- Checked the few ENET variables I could find and the working and non working robots have the same settings, $EIP_CFG, $ENETMODE Maybe there are more variables I could check. I am still looking.
- Tried direct to port 3 without network. Still doesn't work.
I'd be happy for any other ideas of what might be different between robots that might be causing this issue.