Reoccurring “No controller” errors

Technical Questions Report a Bug
1

Software version : 5.10.0
Robot generation : E-Series (UR10e)

Steps to reproduce : We can’t reproduce it 100% of the time but the error seems to happen when you’re holding the button to move the robot to the program starting position on the tablet whilst simultaneously holding the 3PE button.

Expected behavior : The robot stops when you let go of the 3PE while moving.

Actual behavior : The robot produces the “No controller” error if you let go of the 3PE “at the right moment”.

2

Hi @domi.nik,

Thank you for the feedback. If you see any pattern in when “the right moment” occurs please let us know!

Ebbe

3

I observed same error, but in different scenario here. Updated from 5.9.x to 5.10.1 last week and observered several “No Controller” issue since then.

Software version: 5.10.1
Robot generation: E-series (UR10e)

Steps to reproduce: Not 100 % reproducible, but it seems to happen after a pausing a program in my case. One scenario, in which the error occurs quite often is: Pause a program for about 5 min and stop the program. Go to Move Tab and turn the base or shoulder with the controls, haven’t tried to reproduce using the other joints

Expected behavior: Moving arm resp. continue program.

Actual behavior: The robot stops and shows “No Controller” (german: “Kein Controller”) in the bottom left of the screen . I have seen no error messages in the log, except “Polyscope controller disconnected” (german: Polyscope Vom Controller getrennt")

Sven

4

Try upgrading the Software version to 5.11.8
there seems to have been a lot of bug fixes regarding No Controller issues
see release notes Release Notes 5.11

Not saying it will fix it but its worth a go!

1 Like
5

That was the solution. The latest version back end didn’t fix the issue. But since we have upgraded to 5.11.8 we haven’t encountered the problem again.

1 Like
6

I also had this problem 5.9 (with pausing by a light curtain), after upgrading to 5.13 has it disappeared.

7

I just had this issue with polyscope 5.14.5.
For additional context I am running a set of custom functions to exchange data over sockets with node red.
Weird thing is that it was working last week, but still seems like it must be something to do with my socket communication functions.
What is the standard way of monitoring and maintaining a socket connection in URscript?
this is what I’m doing now:

‘’’
def CtrlX_data_exchange(freq = 0.3):
#limit cycles of the communication loop
sleep(freq)

#Check socket connection:
CtrlX_socket = check_socket_connection("CtrlX")

#if no connection, establish it
while (CtrlX_socket == False):
    socket_close("CtrlX")
    CtrlX_socket = socket_open(CtrlX_IP, 1800, "CtrlX")
end

# ---------- Send data to PLC ----------
CtrlX_set_var("bool8","m1/robot_ready", M1_robot_ready)

#  ---------- Get PLC Data ----------
M1_ready = CtrlX_get_bool("m1/machine_access_allowed")

end
#--------------------------------------------------------------------------------------
‘’’

8

An update on this:
I haven’t been able to pinpoint why, but this program instantly bricks my UR20 (5.14.5)
broken.zip (15.9 KB)

When it says “no controller” i can’t even click on the power button and restart. I have to pull the power cable to be able to reboot it.

I’ll try to figure out why this is happening, but any help would be appreciated.
Thanks!