Universal Robots+

Controller shuts down while urcap development

I was testing two URCap in Polyscope 5.6 and 5.5 and I received a "No Controller " Error. I have attached the error its shows on the terminal. I am not sure if it is due to the XMLRPC issue discussed earlier. Is there anything I can do to avoid it?

Hi @tal,
This issue is not how xml-rpc fail affects controller. Looks like something else. I moved your post to new thread.
If this is reproducible, then please put steps to reproduce here. If you have no clue where to start from, then there should be flight record created at the time controller crashed. Upload controller log (or entire flight report) here on the forum.

I have been able to see this error only with a specific robot program I am sure that if it is used again it will give the same error. It also contains the usage of 3 different URcaps one from Robotiq and two other developed in house.

It will be lot easier to share the log files. Should I use ‘Support Log Reader or magic file’ to backup log ?

Ideally you should use “Save report as” feature from the log tab.
Navigate to log entry where controller disconnection is reported. Then there should be paperclip icon on the line. You will see a save button after you select log entry.
It’s important to download report exactly for controller disconnect log entry, as controller log files are not saved between reboots.

file from save repot as:

report_20200303_10_30_13.zip (2.2 MB)

log file from magic file (I was not able to upload the .zip file):