Steps to reproduce:
Expected Behavior:
Actual Behavior:
Workaround Suggestion:
Robot Serial Number:
Affected Version(s):
I’ve not personally had this problem, I’ve just seen it reported numerous times here on the forum with no response from UR. Please investigate this. @jbm
Hi,
I’m having a strange problem where every time my robot (ur10e) gets rebooted or is otherwise turned off and turned back on (not estop) I lose my palletizing node and get the following null pointer error:
[java.lang.NullPointerException]
The pallet and pattern were named unique names, but upon startup they have generic names. This happens even when no actions are put under “tool action”.
Any help with this would be greatly appreciated since simply keeping the robot powered on for its ent…
Hello everyone, I am currently facing a problem with subprogram.
When I click on ‘Keep Subprogram File Updated With this Program’ and then save and close the main program. And again when I open the main program. It shows yellow nodes with that subprogram. This error is ONLY happening with the subprograms which involve palletizing. And when I try to run the program it shows the error as shown in the image attached.
I have not been able to understand why is this happening. Please help me out. Th…
I’ve seen this a few other times by people reporting this, and it seems they are always using subprograms as well. It’s a bug on UR’s end, unfortunately, and there won’t be anything you can do to fix it beyond what you’ve done by reporting it. You could try workarounds like rebooting the robot or something.
Hello,
I had a program running for the last few days. Now I had some Problems with the Visor program (Send change job request failed).
I rebooted the UR10, but now the program that worked the last few days isn’t starting anymore. I now get a error message and can’t start the program…
Is there anything I can do?
This was the error why I restarted the UR
[IMG_4930]
This is the error message I get now
[IMG_4931]
[IMG_4932]
When using the palletizing function in a subroutine, everything works as expected until you close and reopen the program. This includes restarting the controller.
After reopening the file, variables relating to the palletizing template are automatically renamed. This causes NullPointerException errors and a total breakdown of the palletizing function, and I have not been able to recover by reassigning the original variables… the only way to fix is to delete the palletizing node and add/configur…
4 Likes
I use palletizing in sub programs. I have gotten that same error along with other issues doing so, but the workaround for me was to uncheck the “Save sub with this file” box in the sub prog, open sub, then open back up the main program. Hope this helps somebody out.
Hello, I had the same problem.
I solved it by creating installation variables in Installation → Variables.
By replacing these variables both in the main program and in the subprogram, the warning no longer appears.