Professional Documents
Culture Documents
KUKA OfficeLite 87 en
KUKA OfficeLite 87 en
KUKA.OfficeLite 8.7
For KUKA System Software 8.7
For VW System Software 8.7
Issued: 14.04.2022
KUKA.OfficeLite 8.7 V5
KUKA Deutschland GmbH
KUKA.OfficeLite 8.7
© Copyright 2022
KUKA Deutschland GmbH
Zugspitzstraße 140
D-86165 Augsburg
Germany
This documentation or excerpts therefrom may not be reproduced or disclosed to third parties
without the express permission of KUKA Deutschland GmbH.
Other functions not described in this documentation may be operable in the controller. The user
has no claims to these functions, however, in the case of a replacement or service work.
We have checked the content of this documentation for conformity with the hardware and soft-
ware described. Nevertheless, discrepancies cannot be precluded, for which reason we are not
able to guarantee total conformity. The information in this documentation is checked on a regu-
lar basis, however, and necessary corrections will be incorporated in the subsequent edition.
Subject to technical alterations without an effect on the function.
KIM-PS5-DOC
Translation of the original documentation
Contents
1 Introduction.............................................................................................. 5
1.1 Target group.......................................................................................................... 5
1.2 Industrial robot documentation.............................................................................. 5
1.3 Representation of warnings and notes................................................................. 5
1.4 Terms used............................................................................................................ 6
2 Product description................................................................................. 9
2.1 Product description................................................................................................ 9
2.2 Constraints............................................................................................................. 9
2.3 Performance.......................................................................................................... 10
2.4 Software components............................................................................................ 10
2.5 KUKA.Sim/KUKA.Sim Pro and KUKA.WorkVisual............................................... 11
2.6 Intended use and misuse...................................................................................... 11
4 Licensing................................................................................................... 29
4.1 License types......................................................................................................... 29
4.2 Creating a license request when starting KUKA.OfficeLite for the first time...... 29
4.3 Using KUKA.OfficeLite with a single PC license.................................................. 30
4.3.1 Requesting a single PC license............................................................................ 30
4.3.2 Activating KUKA.OfficeLite with a single PC license........................................... 30
4.4 Using KUKA.OfficeLite with a server license....................................................... 31
4.4.1 Requesting a server license................................................................................. 31
4.4.2 Starting up the license server for KUKA.OfficeLite.............................................. 31
4.4.3 Activating KUKA.OfficeLite with a server license................................................. 33
4.5 License management and use of server licenses............................................... 33
4.5.1 Borrowing licenses................................................................................................ 33
4.5.2 Returning borrowed licenses early....................................................................... 35
4.5.3 Transferring licenses............................................................................................. 36
5 Operation, KUKA.OfficeLite.................................................................... 37
5.1 Overview of the graphical user interface.............................................................. 37
5.2 Simulating inputs................................................................................................... 38
5.3 I/O simulation via VRC – Note............................................................................. 39
5.4 Testing I/Os with Y200 test client......................................................................... 39
7 Messages.................................................................................................. 43
7.1 Error messages during licensing.......................................................................... 43
8 KUKA Service........................................................................................... 45
8.1 Requesting support............................................................................................... 45
8.2 KUKA Customer Support...................................................................................... 45
Index 47
Introduction
1 Introduction
Safety
These warnings are provided for safety purposes and must be observed.
DANGER
These warnings mean that it is certain or highly probable that death or
severe injuries will occur, if no precautions are taken.
WARNING
These warnings mean that death or severe injuries may occur, if no
precautions are taken.
CAUTION
These warnings mean that minor injuries may occur, if no precautions
are taken.
NOTICE
These warnings mean that damage to property may occur, if no precau-
tions are taken.
Notices
Term Description
EMD Electronic Mastering Device
Hyper-V Hypervisor-based virtualization technology from Mi-
crosoft
Hyper-V is currently used as the virtual system for
OfficeLite.
KRL KUKA robot programming language (KUKA Robot
Language)
KLI The KLI is the Ethernet interface of the robot con-
troller for external communication. It is a physical
interface and can contain multiple virtual interfaces.
(KUKA Line Interface)
KPP KUKA Power Pack (drive power supply with drive
controller)
KSP KUKA Servo Pack (drive controller)
KUKA smartHMI User interface of the KUKA System Software
(KUKA smart Human-Machine Interface)
KUKA smartPAD Teach pendant for the industrial robot
NTFS File system for the Windows operating system
(New Technology File System)
VMware Software from VMware with which virtual machines
can be created and run
In the past, VMware was used as the virtual sys-
tem for OfficeLite.
VRC Interface for communication between the
simulation products KUKA.OfficeLite and
KUKA.Sim/Sim Pro
WinMOD Software from Mewes & Partner GmbH for process
simulation
Y200 Interface to WinMOD or SIMIT for virtual start-up
Introduction
Term Description
Y-NET Interface to WinMOD for virtual start-up
Product description
2 Product description
Description
Functions
2.2 Constraints
Functions
Technology packages
• KUKA.SafeOperation
• KUKA.SafeRangeMonitoring
• KUKA.RoboTeam
• KUKA.ServoGun FC
• KUKA.ServoGun TC
• KUKA.RobotSensorInterface
• KUKA.TouchSense
• KUKA.ConveyorTech
• KUKA.EqualizingTech
• KUKA.LoadDataDetermination
The list refers to the technology packages available at the time of docu-
mentation. Further technology packages may be added in the future
which may also be incompatible with installation on the system software
image. It is therefore advisable to install technology packages only after
consultation with KUKA Deutschland GmbH.
2.3 Performance
Scope of supply
Virtual system
Product description
2.5 KUKA.Sim/KUKA.Sim Pro and KUKA.WorkVisual
KUKA.Sim
KUKA.WorkVisual
Use
Misuse
Hardware
Host PC:
• Intel i5 (dual-core) or higher or comparable CPU
• 8 GB RAM or more
• 15 GB hard disk space or more
Recommendation
Power save mode may interfere with the correct running of KUKA.Office-
Lite. It is therefore advisable to deactivate the power save mode.
Automatic logon
When starting the virtual machine, the user is automatically logged in.
Manual login
3.3.1 Hyper-V
Preparation
• Save and close other open programs since the computer must be re-
started after activation.
Procedure
1. Right-click on the Windows icon in the taskbar, then select Apps and
Features.
2. Click on Programs and Features in the right-hand area.
3. Click on Turn Windows features on or off in the left-hand area.
4. Activate the check box for Hyper-V and confirm with OK.
Windows carries out the necessary changes. This may take several
minutes.
Windows displays a message indicating when the changes are com-
plete.
5. Reboot the computer.
Preparation
1. Copy the ZIP directory with the OfficeLite software to the following
path:
• C:\Users\Public\Documents\Hyper-V\Virtual hard disks
This is the default path. Another path can also be selected.
2. Unpack the ZIP directory.
Procedure
Description
Precondition
Procedure
Precondition
Procedure
6. A new window opens in which the size of the virtual desktop can still
be defined if required.
Click on Connect.
The user interface of the virtual machine is now displayed.
7. Only if the virtual machine is not yet licensed: The FLEXnet License
Finder is opened.
The license request can now be created via the FLEXnet License Finder.
(>>> 4.2 "Creating a license request when starting KUKA.OfficeLite for the
first time" Page 29)
Description
Procedure
1. Enter cmd in the Windows Start menu in the virtual machine and con-
firm with the Enter key.
2. Enter the command ping computer_name and confirm with the Enter
key.
3. If the pinged computer does not respond, contact the network adminis-
trator to check the network or domain settings.
Description
This procedure ensures that a USB device is available both there and on
the virtual machine after being plugged into the host computer.
The procedure must be carried out once per virtual machine. The settings
are then retained.
The procedure can be carried out as soon as the virtual machine is
started for the first time.
Precondition
Procedure
6. A new window opens in which the size of the virtual desktop can still
be defined if required.
If the window is not displayed, enhanced session mode is already
activated on the virtual machine.
Remedy: Deactivate enhanced session mode and restart the virtu-
al machine. See below for information about switching off.
2. Activate the check box next to Save my settings for future connec-
tions to this virtual machine.
The menu item and the entire menu bar are only visible if the win-
dow is NOT in fullscreen mode.
7. Log in:
• User name: KukaUser (Has administrator rights by default.)
• Password: 68kuka1secpw59
8. A USB device can now be plugged in.
The device is displayed on the virtual machine as drive “E on [host
name]”. The device is also displayed on the host computer.
9. Only if the virtual machine is not yet licensed: The FLEXnet License
Finder is opened.
The license request can now be created via the FLEXnet License Finder.
(>>> 4.2 "Creating a license request when starting KUKA.OfficeLite for the
first time" Page 29)
Description
Procedure
1. In the main menu, select Start-up > Additional software. All addition-
al programs installed are displayed.
2. Click on the New software button.
3. Select the entry VRC Interface or Y200 Interface and click on the In-
stall button. Reply to the request for confirmation with Yes. Installation
is prepared.
4. Confirm the reboot prompt with OK.
5. Restart Windows on the virtual machine. To do so, select Restart in
the Windows Start menu. Installation is resumed and completed.
6. For Y200Interface:
• Once Windows has booted, the smartHMI automatically restarts.
Precondition
Procedure
LOG file
Description
File storage
After the installation of Y200Interface, the associated files are located un-
der C:\KRC\Y200Interface.
Exception: The configuration file Y200Interface.config is located under
C:\KRC\User.
1 <?xml version="1.0"?>
2 <VrcY200Settings xmlns:xsi=
"http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
3 <Y200IpcName>Y200_VRC_R1</Y200IpcName>
4 <Y200ReadOffset>0</Y200ReadOffset>
5 <Y200WriteOffset>1024</Y200WriteOffset>
6 <UseWinModNetInterface>false</UseWinModNetInterface>
7 <WinModHostName>127.0.0.1</WinModHostName>
8 <WinModPort>40001</WinModPort>
9 <WinModTimeout>1000</WinModTimeout>
10 <WinModCycleRate>100</WinModCycleRate>
11 <WinModComElement>WinMOD_Project\active layer\KrcRobot
</WinModComElement>
12 <DebugMode>false</DebugMode>
13 </VrcY200Settings>
Precondition
• Y200Interface is installed.
Procedure
Parameter Description
Y200IpcName Name of controller. This is used by the simulation
system to address the OfficeLite instance.
Y200ReadOffset Start of the input data image on the Y200 shared
memory (in bytes)
Shared memory
Precondition
Procedure
Parameter Description
UseWinModNetInterface Set to TRUE: This activates the Y-NET interface.
WinModHostName Determine the local IP of the virtual machine and enter 1 as the
last number.
Example: The local IP is 192.168.91.130.
Then the following should be entered here: 192.168.91.1
WinModComElement The path is composed of: project name, object attributes of the
communication module, ident. of COM_01
The path is derived from these three names written in succes-
sion and separated by a backslash. Example:
WinMODSimulationVM86\active Layer\Rob1
If this parameter is not set correctly, no coupling between Win-
MOD and the WinMOD interface is possible.
DebugMode If no connection to WinMOD is established and it is suspected
that WinModComElement might be incorrect, then DebugMode
can be set to TRUE.
Then the system creates a LOG file under C:\KRC\Roboter\Log:
This usually contains the reason for the failure to establish com-
munication.
Icon Description
Icon with green dot: connection established to WinMOD.
Licensing
4 Licensing
The following license types are available for KUKA.OfficeLite and the VRC
interface:
• Single PC license
The license is valid for a specific PC. The license cannot be transfer-
red to a different PC.
This option is only supported in the case of PCs with a Windows op-
erating system.
• Server license
The license is accessed from a server with a certain number of (float-
ing) licenses. A corresponding license server must be available to
manage the licenses provided by the manufacturer.
A user can call licenses on any client PC that has access via the net-
work to the license server. It is also possible to borrow licenses for a
limited time, so that the software can be used without a connection to
the license server.
This option is only supported in the case of PCs with a Windows op-
erating system.
4.2 Creating a license request when starting KUKA.OfficeLite for the first
time
Description
Precondition
Procedure
1. When you start the virtual machine for the first time, the FLEXnet Li-
cense Finder opens.
Procedure
Precondition
Licensing
Procedure
Procedure
Precondition
Procedure
4. Under Service Name, enter the name of the new service, e.g. “OL
Service”.
5. Under Path to the lmgrd.exe file, enter the path to the lmgrd.exe file,
or use the Browse button to search for and load the file.
6. Under Path to the license file, enter the path to the license file *.lic
or use the Browse button to search for and load the file.
7. Under Path to the debug log file, enter the path to the license server
LOG file, or use the Browse button to search for and load the file.
8. Activate the Use Services check box (set the check mark).
9. If necessary, activate the Start Server at Power Up check box (set
the check mark).
The option Start Server at Power Up has the effect that the FLEXlm
license manager is automatically started when the computer is reboo-
ted.
10. Click on Save Service. “OL Service” is saved.
On the Start/Stop/Reread tab, “OL Service” can be started and stop-
ped, or the server license file can be reloaded.
Licensing
4.4.3 Activating KUKA.OfficeLite with a server license
Precondition
• Network connection to the license server on which the license file *.lic
is saved.
Procedure
Precondition
Procedure
1. Open the FLEXLM folder on the virtual machine via the shortcut on
the desktop and start the program lmtools.exe.
The LMTOOLS window is opened.
2. Make the following settings on the Utilities tab:
• Under Vendor Name, enter LM_LICENSE_FILE.
• Under Path, enter the path @Server name to the license server,
e.g. @Server01.
3. Click on Add Vendor Path to save the settings on the Utilities tab.
4. Make the following settings on the Borrowing tab:
• Enter KUKAROB under Vendor Name.
• Under Return Date, enter the date the license is required until,
e.g. 31-aug-2017 (31st August 2017; always enter the first 3
letters of the name of the month in English). The date must be
within the maximum borrowing period.
• Under Return Time, enter the time the license is required until,
e.g. 12:00.
Licensing
9. Click on List Currently Borrowed Features to check whether licens-
ing was successful.
The licensed applications are displayed:
Precondition
Procedure
1. Open the FLEXLM folder on the virtual machine via the shortcut on
the desktop and start the program lmtools.exe.
The LMTOOLS window is opened.
2. On the Borrowing tab under Feature Name, enter the name of the
application for which the license is to be returned to the license server
earlier than originally planned:
• KUKAROB_HMI_8 for KUKA.OfficeLite
• KUKAROB_VRC_2 for the VRC interface
Overview
Operation, KUKA.OfficeLite
5 Operation, KUKA.OfficeLite
Item Description
1 Button for the enabling switch
2 List box for selecting the operating mode
3 Buttons for manual motion (jog keys)
4 Button for setting the program override
5 Button for setting the jog override
6 This button is used to display the menu items on the user inter-
face (Main menu key).
7 Buttons for the status keys.
Status keys are used primarily for setting parameters in technol-
ogy packages. Their exact function depends on the technology
packages installed.
8 This button is used to start a program (Start key).
Item Description
9 This button is used to start a program backwards (Start back-
wards key).
10 This button is used to stop a program that is running (STOP
key).
11 Button for displaying the keyboard (Keyboard key)
It is generally not necessary to press this key to display the
keyboard, as the user interface detects when keyboard input is
required and displays the keyboard automatically.
Procedure
1. In the main menu, select Display > Inputs/outputs > Digital I/O.
2. Click on Go to and enter the number of the desired input via the key-
board. The display jumps to the input with this number.
3. Click on Sim on/off. Simulation is activated.
4. Click on Value. The input is set to TRUE and simulated.
Description
Item Description
1 Input number
2 Value of the input. The icon is green if an input is TRUE.
3 SIM entry: The input is simulated.
SYS entry: The value of the input is saved in a system variable.
This input is write-protected and cannot be simulated.
4 Name of the input
The following buttons are available:
Operation, KUKA.OfficeLite
Button Description
-100 Toggles back 100 inputs in the display.
+100 Toggles forward 100 inputs in the display.
Go to The number of the input being searched for can be
entered.
Value Toggles the selected input between TRUE and
FALSE.
This button is not available when simulation is switch-
ed off and in AUT and AUT EXT modes.
Name The name of the selected input can be modified.
Sim on/off Switches simulation on or off.
Description
Description
Inputs/outputs can be tested using the test client. The robot axes, the ex-
ternal axes, $ACT_POS, $TOOL and $BASE can also be viewed.
If, for example, an input is set in the test client, the corresponding status
is displayed on the smartHMI under Display > Inputs/outputs.
Precondition
Procedure
Description
Precondition
Procedure in KUKA.Sim
8. The target controller displays the request for confirmation Do you want
to activate the project […]?. In addition, a message is displayed as to
whether the activation would overwrite a project, and if so, which one.
If no relevant project will be overwritten: Answer the query with Yes.
9. The target controller displays an overview of the changes that are be-
ing made in comparison to the project that is still active. The check
box Details can be used to display details about the changes.
The overview displays the request for confirmation Do you want to
continue?. Confirm with Yes.
The project is activated on the target controller.
10. In KUKA.Sim: Close the Project deployment window by selecting
Finish.
Messages
7 Messages
The following FLEXlm error messages occur most frequently during licens-
ing:
No. Description / cause Remedy
-5 No such feature exists. Install the OfficeLite version for which
the license file is valid, or request a new
The license file does not match the in-
license file after a software update. For
stalled OfficeLite version.
this, send the old license file together
with the order number for the software
update to the following address: Simula-
tion.Robotics.De@kuka.com
-9 Invalid host. Request a new license file. To do so,
send the old license file together with
The current license file does not match
the following information to Simula-
the computer:
tion.Robotics.De@kuka.com:
• After exchanging the computer
• In the case of single PC license: fin-
• Or: The OfficeLite image has been gerprint file *.kfp
moved to a different folder.
• In the case of a server license: host
ID and host name of the license
server
Note: To reactivate OfficeLite, the old li-
cense file in the virtual machine or on
the license server must be deleted.
-10 Feature has expired. Request a new license file. For this,
send the old license file to the following
The license file has expired.
address: Simulation.Robot-
ics.De@kuka.com
-15 Cannot connect to license server sys- Contact the network administrator.
tem.
No connection can be established to the
license server:
Other error messages which may occur during licensing are described
in the chapter Error Codes in the License Administration Guide for
FLEXlm. This guide is included in the scope of supply for KUKA.Office-
Lite.
KUKA Service
8 KUKA Service
Introduction
Information
C L
Connection to the host computer, Hyper-V...15 License management..................................... 33
License request.............................................. 29
License server, start-up..................................31
D License types..................................................29
Diagnosis package......................................... 45 License, expired............................................. 36
Documentation, industrial robot....................... 5 Licenses, borrowing........................................33
Licenses, transferring..................................... 36
Licensing.........................................................29
E Login............................................................... 13
EMD.................................................................. 6
Enhanced session.......................................... 23
Error messages, licensing..............................43 M
Main menu key...............................................37
Messages........................................................43
F Misuse.............................................................11
Functions.......................................................... 9
Functions, constraints.......................................9
N
Network connection, checking....................... 20
G NTFS.......................................................... 6, 10
Graphical user interface, overview................ 37
O
H OfficeLite, activating.................................30, 33
Hard disk space............................................. 13 OfficeLite, operation....................................... 37
Hardware, system requirements.................... 13 Operation, OfficeLite.......................................37
Hyper-V.............................................................6 Outputs, simulating.........................................39
Hyper-V Manager, starting............................. 15 Overview, graphical user interface................ 37
I P
Inputs, simulating..................................... 38, 39 Password, changing....................................... 13
Intended use................................................... 11 Performance................................................... 10
Introduction....................................................... 5 Power save mode, deactivation.....................13
Product description...........................................9
J
Jog keys......................................................... 37 R
RAM................................................................ 13
K
Keyboard.........................................................38 S
Keyboard key..................................................38 Safety instructions............................................ 5
KLI................................................................ 6, 9 Server license.................................................29
Knowledge, required.........................................5 Server license, requesting..............................31
KPP...................................................................6 Server licenses, management........................33
KRL................................................................... 6 Simulation....................................................... 38
KSP...................................................................6 Single PC license........................................... 29
T
Target group..................................................... 5
Terms used....................................................... 6
Training............................................................. 5
U
User name...................................................... 13
V
VMware.............................................................6
VRC.................................................................. 6
W
Warnings........................................................... 5
WinMOD........................................................... 6
WorkVisual...................................................... 11
Y
Y-NET......................................................... 7, 26
Y-NET, configuring.......................................... 27
Y200........................................................... 6, 26
Y200, configuring............................................26
Y200Interface..................................................10
Y200Interface, installing................................. 24
Y200Interface, uninstalling............................. 25