This procedure’s target is to learn how to backup and restore an UR robot. Each robot must have its own backup since they have unique calibration files given by UR.
Why?
• Prevent prolonged down time of corrupted robot software
• Prevent data loss such as URCaps, safety configuration and calibrations
• Implement preventive robot restoration at regular intervals (i.e. Weekly robot restore)
What is needed?
• Win32DiskImager software.
• Physical backup platform: 4Gb* SD card for e-Series robot or 2Gb USB key for CB-Series
• A Windows PC to perform the backup/restore
Note :
*The Memory size is the minimum requirement and can be more, but the rest of the memory will remain unusable.
Backup a robot
The first step is to save everything on the robot that needs to be kept and then shutting down the
entire robot.
The robot’s memory (SD card or USB key) must be pulled out of the robot and plugged into the
PC. The several error or message prompt can be ignored.
Then, opening WIN32DiskImager should show this window:
"Image File" is for deciding the destination and name of your robot Image file. The image file is
usually named after the robot serial number for better traceability (i.e. UR5_20185501097.img).
The file can be saved wherever it is desired on the PC.
Then, the right Device must be chosen. In the case of several partitions on a SD card, any related
to it can be chosen. Also, the Read Only Allocated Partitions must be checked.
Finally, the Read button will begin the backup process. The output will contain an exact clone of
the robot's memory unit.
Restore a robot
To restore a robot, a previous image of the same robot is needed. Once Win32DiskImager is
opened, grab the existing image file of the robot with the file icon button.
Then, the right device must be chosen. In the case of several partitions on a SD card, any related to it can be chosen.
The Write button will then be available and must be clicked on to begin to write on the chosen
device.
A prompt will warn that every data existing on the device prior to the restore will be erased, it can
be accepted to continue.
The output of the operation will be a perfect clone of the robot image on the memory unit and can
be used immediately.
Note :
The first reboot of a restored robot will prompt a warning of the current robot position that might not be the same as previously saved, which is normal. You can confirm the current positionof the robot and click Verified.Tip :
If you encounter issues when burning a new robot image, you can try using Rufus instead.