I just updated our 10e to 5.22.xxxx and I can not run the robot. I’ve attached an image of the error message. Any idea what’s going on? Thanks!
Bruce
Are you using any sub programs in there? The palletizing node seems to struggle with subprograms or Installation variables. It’ll work until you save and try to re-open the program. I rarely use it, and opt to instead programmatically shift the Features around myself. (Palletizing in subprograms causes null pointers)
I’m not using any subprograms…just the palletizing feature in Polyscope. I’ve updated several times before and never had any issues. Could it be because I had a program open when I did the update? How can I fix it? Should I delete that open program and rebuild it?
You can probably just rebuild the pallet node. Insert a new one, configure it the same way as the old one, and cut and paste all your instructions into the new one. Then delete the old pallet node.
Thank you Eric, I’ll give it a try.
Eric, I discovered that all the Installation Variables were deleted when I did the software update! How could this happen! I’ve done updates before without this result. Is there any way to recover them? Over a dozen, and many years of work. No where did I see a procedure to back them up to restore them after an update!
When I attempted to recreate the depalletizing operation everything remains yellow for some reason, so it’s impossible to create new ones. When creating the second node it recognizes that previous variables have already been created and doesn’t allow me to name the variable the same as the old name. However when I go into the variables screen, it is completely blank. Really not sure what’s going on!
Yeah I’ve been screwed over by UR’s method for handling variables in the past as well. Exactly like you’re experiencing now. Well to a slightly lesser degree I guess since I never had mine get wiped.
The variables are stored in their own file on the controller called like “installation.variables.” Your best bet for seeing those is to save a backup to a flashdrive and put it in your computer. This is going to be blunt and probably not helpful at this moment in time, but if you’ve had the system for many years and never took a SINGLE backup of your programs/installation, then you’re probably out of luck, and this can be your hard lesson to form a habit of backing up your files at semi-regular intervals. If you have ANY backups, then you may be able to recover the variables from the file I mentioned.
Your last course of action is to contact UR’s help directly. This is just the forum for folks that have the robot. For true support from UR, you will need to create a case with them (https://myur.universal-robots.com/) and see if they can help. They are usually very responsive.
Best of luck!
For both of your information, the e-series controllers/operating system has always had a fault when removing the power from the controller without shutting it off properly first. For example with a blackout.
This can cause the installation variables to become corrupt. I have seen it happen many times by now and have had customers do it, too.
But I have never seen it happen during an update.
1 Like