If your robot will not boot at all you will have to create a new robot image, without a backup I suspect you are likely not able to restore the robot in its current state. If you tried to go from 3.10 straight to 3.15 there is a very good chance you have corrupted your robot and a new image will be the only solution. For a CB3 robot you must update polyscope 1 major version at a time, i.e. 3.10 → 3.11 → 3.12 etc. You can find instructions on flashing a new robot image here (you may be able to rescue your program files etc, instructions for this can also be found in the link)
@sam.verity-hilton Hi,Sam, you are right, my robot was crashed when I try to update it from 3.10 to 3.11. I have 2 questions for you:
should I downloard the 3.15 image directly or make it back to 3.10 and update aftwards?
I don’t have the original calibration file backups, I watched some github issues, which said if I make the new image, I will get an un-calibrated robot… and that guy said on the web that we may get the original calibration files from UR by sending my robot ser. No., is that true?
Old thread but I am also having same issue. The my-UR is giving me issues to access ticket. I wrote to tech support to solve that. My UR crashed. I got the new image but need calibration files for my unit. Can you help? Please
You did have issues with your UR Robot, re-flashed the SD-Card and now miss the Calibration files? In addition myUR is making troubles for you to access the ticket?
This would be a case for our local Support colleagues, but let me see if I can ping them as well.
What SW Version did you use, have now updated to and what S/N does your robot have?
You can also share the ticket number you did get with me.
/Stefan
PS - What would we need to do change the robot in your profile picture ?
Yes, that’s essentially the situation. The original internal USB flash drive completely failed. It is no longer detected by the robot controller BIOS or by a Windows PC/Disk Management, and unfortunately I don’t have a backup of the original drive.
The robot details are:
Model: UR5 CB3.1 S/N: 2019350080 Manufactured: January 2019
I downloaded the official CB3.1 PolyScope 3.15.8 full robot image from the Universal Robots website and flashed it onto a new USB drive. I have not installed/booted the new USB in the controller yet, so I haven’t changed or updated the robot software itself. I plan to test the new USB today.
Since the original USB is completely unreadable, I am missing the robot-specific factory calibration/configuration files for S/N 2019350080.
I wasn’t able to successfully create/access a myUR support ticket, so unfortunately I don’t have a ticket number to provide.
I really appreciate you pinging the local support team for me.
And regarding the profile picture… I think getting this UR5 running again would be a pretty good start toward convincing me to change it.
Thank you very much for sending the files and for all your help.
@sko Everything worked successfully, and I was able to complete the process without any issues. I really appreciate your guidance and support throughout this.
Thank you again! Everything is working great now. The robot is fully operational, all six joints are moving smoothly, and the original calibration data was successfully restored.
And yes… I had to keep my end of the deal! The FANUC finally gave up its spot in the profile picture.
Really appreciate your help getting this UR5 back to life!