WorkVisual assigns the robot controller to the robot controller of the actual application-EEWORLD

Collect

This procedure allows you to assign each element in the project to a real robot controller. The project can then be transferred from WorkVisual to the real robot controller.

Prerequisites

A robot controller has been added to WorkVisual.

Connection to real-world robot control systems

The robot controller and KUKA smartHMI for practical use have been started up.

If you subsequently want to transfer and also activate the project:

In the case of practical robot control systems, the expert and higher user groups have been selected.

Restriction: If activation results in changes within the range of safety-related communication parameters, you must select the user group Safety Maintenance Personnel or higher.

If the AUT operating mode is selected in the actual robot controller or

AUT EXT: The project only contains settings that affect the KRL program. If the project contains settings that would cause other changes, these cannot be activated.

Procedure

1. In the menu bar, click the Install... button. The WorkVisual Project Transfer window opens automatically.

The virtual robot controllers in the project are displayed on the left.

The target controller is displayed on the right.

If a control has not yet been selected, the control is grayed out.

Assigning the robot controller to the unit

2. Activate the virtual unit using the check box on the left. Now a real robot controller must be assigned to the unit.

3. Click the ... button. A window opens automatically. The filter is automatically set so that only controllers of the same type and version as the virtual control are displayed. This setting can be changed.

Assigning the real robot controller to the virtual system

4. Select the desired real robot controller and click Ok.

The real robot controller is assigned to the virtual robot controller.

After the assignment, the real robot controller is displayed in color and displays the name and IP address.

5. If the project has several robot controllers, repeat steps 3 and 4 for the other robot controllers.

6. Click Continue. The assignment is checked for conflicts. If there are conflicts, a message is displayed. Conflicts must be resolved, otherwise the project cannot be transferred. If there are no conflicts, the code is automatically generated.

7. The project can now be transferred to the robot controller.

The project can also be transferred at a later time. To do this, click Exit: The assignment is saved and the WorkVisual Project Transfer window closes automatically.

Transferring a project to the robot controller In this way, a project is transferred from WorkVisual to the actual robot controller.

If there is a project on the actual robot controller that was transferred at a previous time but never activated, this will be overwritten when another project is transferred.

By transferring and activating a project, a project with the same name on the actual robot controller is overwritten (after a safety query). Prerequisites

The project has been assigned to a robot control system for practical application.

Conflicts during allocation are resolved.

Network connection to actual robot control systems

The robot controller and KUKA smartHMI for practical use have been started up.

If you want to activate the project as well:

In the case of practical robot control systems, the expert and higher user groups have been selected.

Restriction: If activation results in changes within the range of safety-related communication parameters, you must select the user group Safety Maintenance Personnel or higher.

If the AUT or AUT EXT operating mode is selected in the actual robot controller: The project only contains settings that affect the KRL program. If the project contains settings that would cause other changes, these cannot be activated.

If you want to transfer a project that contains an option package that has been added to the project, but the window listing the changes is not displayed, you must follow the following procedure:

1. Transfer the project to the robot controller, but do not activate it!

2. Install the option package on the robot controller. Install it as usual. For information, refer to the documentation for the option package.

3. Transfer the activated project from the robot controller to WorkVisual and configure the user configuration.

4. Transfer the project to the robot controller again.

5. Activate the project in the robot controller.

Procedure

1. Click the Install... button in the menu bar. The WorkVisual Project Transfer window opens automatically.

2. Click Next. The program generation starts.

3. Click Next. The project is transferred. If you have transferred a project that contains an option package that has been added to the project, but the window listing the changes is not displayed: Do not activate this project, i.e. do not proceed to the next step! Please note the information about projects with option packages at the beginning of this section!

4. Click Next. In the AUT and AUT EXT operating modes, projects that only involve program changes can be activated without a safety query.

5. Only in operating modes T1 and T2: The KUKA smartHMI displays the safety query "Do you want to activate the project [...]?". It also displays whether a project is to be overwritten by the activation and, if so, which one. If there is no relevant project to be overwritten: Confirm this query with "Yes" within 30 minutes.

6. An overview of the changes made compared to the project still active in the robot controller is displayed. The Details check box can be used to display the details of the relevant changes. If the heading "Change" is marked under "Safety-related communication parameters" in the overview, the emergency stop behavior and "operator protection device" of the previous project can be changed.

Therefore, after activating the project, you must check whether the emergency stop and "operator protection device" signals are functionally reliable. If the project is activated on multiple robot controllers, this check must be carried out on each robot controller. Failure to do so could result in death, bodily injury or property damage

. 7. The overview displays the safety query "Do you want to continue?". Answer with "Yes". The project is now activated in the robot controller. A confirmation message is displayed in WorkVisual to this effect.

If an option package was installed by activating the project, the project must then be loaded from the robot controller. Otherwise, further work on the project may result in inconsistent files and the project cannot be transferred again.

8. Click the Finish button to close the WorkVisual Project Transfer window.

9. If you do not respond to the robot controller's query within 30 minutes, the project is still transferred but not activated in the robot controller. The project can be activated individually.