No connection to UR10e after polyscope update

Technical Questions
1

Situation:
We tried to set up the Schunk EGU/EGK URCap with our UR10e robot. The URCap required an update of the UR10e Polyscope software from version 5.9 to a version >= 5.14. We opted to update to the latest version, which is 5.16.1. Following the guidelines outlined in section 5.2.1 of the e-Series Service Manual (available here), we followed steps 1 through 12.

Problem:
After starting the software update we are now unable to connect to the UR10e. The LED on the control box shows that the robot is on and we are able to ping the robot. However, we are not able to connect via VNC Viewer. We tried to connect a screen, but we dont get a signal from the PC and thus the screen stays black. Right now the robot is on and the usb stick is still connected. We did not turn off the power of the robot since starting the update.

Question:
How can we resolve this?
Is it safe to try and restart the UR10e? Is it safe to turn off the power, remove the USB and start the UR10e again?

Thank you very much for your support!

2 Likes
2

Did you found a solution?
We are experiencing a similar issue, after updating to Polyscope version 5.16.1, we are unable to connect via VNC viewer.

3

If you’re using the magic file that has been floating around for installing the VNC server on the robot, you’ll need to reinstall it after every update as it’s not an official solution.

My personal method to get this to work is:

  1. Have the magic file on the root of a USB.
  2. Insert the USB into the the Teachpendant/controller.
  3. Wait for the green-colored message to pop up saying the VNC has been installed.
  4. With the USB still inserted, restart the robot.

You’ll see the message about installing the VNC server pop up again while Polyscope is booting, but that’s not a problem. When Polyscope fully starts up (you’ll be on the Run screen), you should be good to connect to the robot. You can at this point remove the USB.

Make sure you’re on the same network as the robot.

4

That’s our procedure also, though I don’t think that we’ve needed to leave the USB stick in during the reboot.

5

Leaving the USB in is (most likely) complete superstition as the first time I ever installed the server I had connection issues and then when I tried again leaving it in it worked :sweat_smile:

6

No solution yet. We will now try to go back to the original version using a back up that we created before the update.

7

Thank you!

However, the problem is not only the VNC server. We also tried to connect a screen via the mini-DisplayPort to the control box. We also do not get any image there and the screen stays black.

So we are still looking for a solution to our problem.

8

Two things on the Displayport which may be affecting you:

  1. The Displayport requires an active Mini Display to DVI or HDMI converter to connect monitors with DVI/HDMI interfaces. Passive converters do not work with the DVI/HDMI ports.
  2. The cable must be plugged in before the controller boots up. It won’t auto-find the display like you would get with a typical PC.