1. learn about your system before making changes
2. make sure to create backup before making changes
3. follow WorkVisual process flow
the flow was described several times on this forum and includes something like this:
1. install correct version of WorkVisual (WoV)
2. integrate KOPs from controller into WoV
3. integrate any DTMs into WoV DTM catalog
4. get working project from controller and save it
5. create copy of that project with different name and make your changes here
6. compile project and make sure there are no build errors
7. deploy and activate project
8. if changes include hardware changes, fieldbus configuration change, safety configuration etc. activate new safety configuration
about step 4, you really really need to get working project from the controller until you really really know the system.
Panic has the right of it here.
Any time a change is made to the robot safety configuration, the change must be confirmed in the Safety Configuration menu, on the teach pendant, by an operator who has access to the Safety Maintenance user group, and logged in as such. This is because the safety controller is, in effect, a separate control system sharing the teach pendant with the robot. And any changes to the safety configuation must be approved on the pendant, as the final authority.
so unlink (comment out) not found dependencies
btw submit interpreter has nothing to do with enabling drives and jogging robot. you can deselect submit and should still be able to jog in T1
