Well, I just encountered yet another little "treat" that WorkVisual has in store for us. I had a KRC4 drop dead today, to the point that I had to rebuild it from scratch using the USB Recovery drive. And I had to restore to factory first, b/c while I had recent Archives, I did NOT have a full Clone Image.
Things actually went quite well at first -- the restore-to-factory process apparently saves and restores the robot's IP address and network setup, which is handy. The issues came when I had to dig up an old WorkVisual project file in order to restore all of the I/O configurations.
First issue: Unless you have WorkVisual save the project to the robot, not just Deploy, there will not be a copy of the WV project stored in the robot's Archives. Important note for future.
Addendum: Hm. I may have spoken too soon on this one. There doesn't seem to be any option for "save to robot" in WV. But now, when I have the robot perform an Archive All, the WV project now shows up in the Archive file. Strange.
Second issue: Some of the files in the robot's /R1/PROGRAMS directory had been moved about into different sub-folders since the WorkVisual project was made. This meant that, when I tried to Deploy the project, certain modules were duplicated in different sub-folders of /R1/PROGRAMS. This gave me an error message in WV. But the real bad part was that this error prevented the safety config from being deployed. I spent rather some time chasing that around, not realizing that the two issues were related. Once I deleted the duplicate modules and re-deployed the WV project, my safety configuration (Profisafe) and bus config (Profinet) were restored. Which is what I wanted most from the WV project, b/c mapping 512 bytes of Profinet in WV is a PAIN.
So, a word of warning for anyone who needs to do this in the future: errors in one part of a WorkVisual project can prevent other, totally unrelated parts, from deploying properly. And you will not get a good error message warning you of this.