KUKA_OfficeLite_86_en

KUKA System Technology
KUKA.OfficeLite 8.6
For KUKA System Software 8.6
For VW System Software 8.6
Issued: 21.11.2023
KUKA.OfficeLite 8.6 V7
KUKA Deutschland GmbH
KUKA.OfficeLite 8.6
© Copyright 2023
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
Publication: Pub KUKA.OfficeLite 8.6 (PDF) en

PB12172
Book structure: KUKA.OfficeLite 8.6 V8.1

BS11232
Version: KUKA.OfficeLite 8.6 V7
2/48 | www.kuka.com KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023

KUKA.OfficeLite 8.6
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
3 Installation and configuration................................................................ 13

3.1 System requirements............................................................................................. 13
3.2 Logging into OfficeLite / changing the password................................................. 13
3.3 Virtual system........................................................................................................ 14
3.3.1 Hyper-V.................................................................................................................. 14
3.3.1.1 Activating Hyper-V................................................................................................. 14
3.3.1.2 Setting up virtual machine under Hyper-V........................................................... 15
3.3.1.3 Configuring the connection to the host computer................................................ 16
3.3.1.4 Starting virtual machine via Hyper-V manager.................................................... 19
3.3.2 Checking the network connection......................................................................... 20
3.3.3 Language settings for the virtual machine........................................................... 20
3.4 Using a USB device on the host computer and virtual machine........................ 21
3.5 Installing KUKA.VRC Interface or Y200Interface................................................. 24
3.6 Uninstalling KUKA.VRC Interface or Y200Interface............................................. 25
3.7 Y200 und Y-NET interfaces – Overview............................................................... 26
3.7.1 Configuring Y200 interface.................................................................................... 26
3.7.2 Activating and configuring Y-NET interface.......................................................... 27
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
KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023 www.kuka.com | 3/48

KUKA.OfficeLite 8.6
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
6 KUKA.Sim with KUKA.OfficeLite............................................................ 41

6.1 Deploying the project from KUKA.Sim/Sim Pro to KUKA.OfficeLite.................... 41
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

KUKA.OfficeLite 8.6
Introduction
1 Introduction
1.1 Target group
This documentation is aimed at users with the following knowledge and

skills:
• Basic knowledge of KRL programming

• Knowledge of the robot controller system
• Basic knowledge of the Windows operating system
For optimal use of KUKA products, we recommend the training courses

offered by KUKA College. Information about the training program can be
found at www.kuka.com or can be obtained directly from our subsidia-
ries.
1.2 Industrial robot documentation
The industrial robot documentation consists of the following parts:
• Documentation for the robot arm

• Documentation for the robot controller
• Documentation for the smartPAD-2 or smartPAD pro (if used)
• Documentation for the System Software
• Instructions for options and accessories
• Spare parts overview in KUKA Xpert
Each set of instructions is a separate document.
1.3 Representation of warnings and notes
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 pre-
cautions 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.

Introduction KUKA.OfficeLite 8.6
These warnings contain references to safety-relevant information or gen-

eral safety measures.
These warnings do not refer to individual hazards or individual precau-
tionary measures.
This warning draws attention to procedures which serve to prevent or rem-

edy emergencies or malfunctions:
SAFETY INSTRUCTION
The following procedure must be followed exactly!
Procedures marked with this warning must be followed exactly.
Notices
These notices serve to make your work easier or contain references to

further information.
Tip to make your work easier or reference to further information
1.4 Terms used
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

KUKA.OfficeLite 8.6
Introduction
Term Description
Y-NET Interface to WinMOD for virtual start-up

Introduction KUKA.OfficeLite 8.6

KUKA.OfficeLite 8.6
Product description
2 Product description
2.1 Product description
Description
KUKA.OfficeLite is a work environment which allows users to practice han-

dling the KUKA System Software on a PC. For this, an image of the Sys-
tem Software is run on a virtual machine.
KUKA.OfficeLite cannot be used to operate a robot.
Functions
The following functions of the System Software are supported:
• Creation and simulation of programs

• Copying of machine data with a plausibility check
• Simulation of physical inputs
• Installation of technology packages
• Updating the System Software
2.2 Constraints
Functions
KUKA.OfficeLite does not support the following functions of the System

Software:
• Diagnosis of the safety circuits

• Diagnosis of hardware modules, e.g. KPP, KSP, EMD on the Controller
Bus
• Safety controller
• Operation of field buses, e.g. DeviceNet, EtherNet/IP, Interbus, PROFI-
BUS, PROFINET
• Integration of a smartPAD
• Load data determination
• Torque mode and force control
• Brake test
• EMD mastering
• Fast measurement
• Network connection via the KLI
A network connection can be established by Windows via the virtual

network card.
Technology packages
Technology packages can only be installed on the System Software image

if these run completely within the virtual machine and do not require any
external communication.
The following technology packages cannot be used with OfficeLite:
• KUKA.SafeOperation
• KUKA.SafeRangeMonitoring
• KUKA.RoboTeam

Product description KUKA.OfficeLite 8.6
• 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
By default, KUKA.OfficeLite does not execute processes in real time, but

slightly more slowly than a real robot controller. The process time depends
on the host system on which OfficeLite is installed and the utilization of
the host system.
The cycle time analysis is not affected by this. For example, a robot pro-
gram simulated with OfficeLite runs more slowly than on a robot controller.
The program run time measured with $TIMER is identical to the program
run time on a robot controller, however.
Example: The simulation of a robot program in OfficeLite takes 3.5 mi-
nutes and a duration of 3 minutes is displayed in OfficeLite. On a robot
controller, the execution of the program would take 3 minutes.
The individual IT environment on site can impact the operation of
KUKA.OfficeLite. An operable system can therefore only be assured
through prior tests.
2.4 Software components
Scope of supply
KUKA.OfficeLite is supplied as a ZIP directory and contains a virtual ma-

chine and other components.
The following components are included in the scope of supply:
• KSS 8.6 or VSS 8.6
• Operating system Windows 10 IoT on NTFS
• KUKA.VRC Interface software
• Y200Interface software
Virtual system
The virtual system is Hyper-V (KUKA.OfficeLite 8.6 Build 09 or higher).

Hyper-V is not included in the scope of supply of KUKA.OfficeLite. Win-
dows 10 Pro and Windows 10 Enterprise contain Hyper-V as a service
that can be activated.
Older builds of KUKA.OfficeLite do not use Hyper-V as the virtual sys-
tem, but VMware. Information about this can be found in the documen-
tation supplied with the respective build.

KUKA.OfficeLite 8.6
Product description
2.5 KUKA.Sim/KUKA.Sim Pro and KUKA.WorkVisual
KUKA.Sim/KUKA.Sim Pro
KUKA.OfficeLite 8.6 can be used in combination with KUKA.Sim Pro 3.x

or KUKA.Sim 4.0 as a virtual robot controller, e.g. for carrying out robot
simulations and cycle time measurements.
For the connection to KUKA.Sim/Sim Pro, the VRC interface must be in-
stalled on the virtual image.
KUKA.Sim/Sim Pro can be installed on the same host computer as
KUKA.OfficeLite but not on the same virtual system as KUKA.OfficeLite.
The connection is always established from KUKA.Sim/Sim Pro.
KUKA.WorkVisual
Projects created with KUKA.WorkVisual 6.x can be transferred to the Sys-

tem Software image, e.g. in order to simulate programs created in Work-
Visual or configure the desired robot type.
WorkVisual can be installed on the same host computer as KUKA.Office-
Lite but not on the same virtual image as KUKA.OfficeLite.
Information about transferring and activating WorkVisual projects can be
found in the WorkVisual documentation.
2.6 Intended use and misuse
Use
KUKA.OfficeLite is exclusively intended for executing an image of the

KUKA System Software on a virtual system.
KUKA.OfficeLite may only be installed on a PC that meets the specified
system requirements. This PC must not be a real robot controller.
Misuse
Any use or application deviating from the intended use is deemed to be

misuse and is not allowed. KUKA Deutschland GmbH accepts no liability
for damage or injury caused thereby. The risk lies entirely with the user.
Misuse includes, for example, the installation of the software on a real ro-
bot controller.

Product description KUKA.OfficeLite 8.6

KUKA.OfficeLite 8.6
Installation and configuration

3 Installation and configuration
3.1 System requirements
The individual IT environment on site can impact the operation of

KUKA.OfficeLite. An operable system can therefore only be assured
through prior tests.
Hardware
Host PC:
• Intel Core i5 or higher or comparable CPU
• CPU benchmark: at least 12 000, recommended 16 000
• 16 GB RAM or more
• 15 GB hard disk space or more
Software (from KUKA.OfficeLite 8.6 Build 09 onwards)
• Windows 10 Pro or Windows 10 Enterprise

• The Windows service Hyper-V is active.
(>>> 3.3.1.1 "Activating Hyper-V" Page 14)
Older builds of KUKA.OfficeLite do not use Hyper-V as the virtual sys-

tem, but VMware. Information about this can be found in the documen-
tation supplied with the respective build.
Recommendation
Power save mode may interfere with the correct running of KUKA.Office-
Lite. It is therefore advisable to deactivate the power save mode.
3.2 Logging into OfficeLite / changing the password
Automatic logon
When starting the virtual machine, the user is automatically logged in.
Manual login
It may sometimes be necessary to log in manually, for example if the vir-

tual machine has not been used for a while or if enhanced session
mode is activated on the virtual machine.
The login credentials are the same as the default login credentials in the
KUKA System Software or VW System Software:
• User name: KukaUser (Has administrator rights by default.)
• Password: 68kuka1secpw59
The password 68kuka1secpw59 can be changed. Information about

changing the password can be found in the Operating and Programming
Instructions for System Integrators for the System Software (KSS or
VSS).

Installation and configuration KUKA.OfficeLite 8.6
3.3 Virtual system
3.3.1 Hyper-V
3.3.1.1 Activating Hyper-V
Hyper-V can be activated in other ways besides the procedure descri-

bed here – i.e. via PowerShell. Information can be found on the Internet
on Microsoft webpages.
If the Windows service Hyper-V is active and the VMware software is

installed at the same time on one and the same host computer, this can
lead to performance problems.
Recommendation: Only use one type of virtual system on a host com-
puter.
The virtual machine must be imported onto the host computer via the
Hyper-V manager. (>>> 3.3.1.2 "Setting up virtual machine under Hyper-
V" Page 15)
It is not possible to leave the associated files on a network drive or
USB stick and to operate the virtual machine from there. In this case,
the virtual machine does not achieve the required performance and can-
not be started.
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.

KUKA.OfficeLite 8.6

Fig. 3-1: Activating Hyper-V
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.
3.3.1.2 Setting up virtual machine under Hyper-V
Precondition
• The Windows service “Hyper-V” is active.
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
1. Start Hyper-V Manager, for example, as follows:

a. Click on the magnifying glass icon in the Windows taskbar and en-
ter “Hyper-V” as the search term.
b. Click on “Hyper-V Manager App” in the search results.
Hyper-V Manager opens.
2. In the right-hand area under the host computer, click on Import Virtu-
al Machine….
The Import Virtual Machine window is opened.
3. Make the following settings on the relevant pages and confirm each
page with Next:
a. On the Before You Begin page: straight to Next

b. Browse for Folder page:

• Navigate to the directory that has been unzipped from the Offi-
ceLite zip file.
• Select the directory and click on Select Folder. The path is
now displayed on the Browse for Folder page.
c. Select Virtual Machine page:
Select the virtual machine in the list. (Generally already marked.)
d. Choose Import Type page:
Select Copy the virtual machine (create a new unique ID).
e. Choose Destination page:
• Activate the check box next to Store the virtual machine in a
different location.
• In all three boxes, enter the same path as on the Browse for
Folder page (step 3 b).
f. Choose Storage Folders page:
Enter the same path here as on the Browse for Folder page
(step 3 b).
g. On the Summary page: Finish
Hyper-V Manager then displays the new virtual machine.
3.3.1.3 Configuring the connection to the host computer
Description
This configuration must be carried out in the following cases:

• If a server license is to be used.
Configuration is not necessary for a single PC license!
• If a connection to KUKA.Sim or KUKA.Sim Pro is required.
Precondition
• The virtual machine is set up under Hyper-V.

• There is no network activity or only network activity where an interrup-
tion will not cause problems.
In the following procedure, the network connection of the host comput-
er may be briefly interrupted – after a security query – when the
switch is created.
Procedure
A: Creating a virtual network switch

If several virtual machines are to run simultaneously, one switch must
be created for each machine.
1. Start Hyper-V Manager.

2. On the left-hand side under Hyper-V Manager, right-click on the host
computer, then select: Virtual Switch Manager....
The Virtual Switch Manager for […] window opens.
3. Select New virtual network switch on the left-hand side.
4. Select the Internal switch type and click on Create virtual switch.

KUKA.OfficeLite 8.6

Fig. 3-2: Creating a virtual switch
5. The properties display for the new switch opens.

As the name of the switch, enter: Connection to host computer.
If multiple switches are being created, include a consecutive number
in the name.
6. Select Internal network as the network.
Fig. 3-3: Properties of the switch
7. Confirm with OK.

8. It may be necessary to briefly interrupt the network connection of the
host computer. If this is the case, a request for confirmation is dis-
played.
• In order for the switch to be created, the request must be an-
swered with Yes.
In this case, the network connection is interrupted and then auto-
matically restored.

KUKA.OfficeLite 8.6
B: Assigning the virtual switch to the network card

1. In Hyper-V Manager, right-click on the virtual machine, then select:

Settings….
The Settings for […] window opens.
2. On the left, under Hardware, select the entry Network Card.
3. On the right, under Virtual Switch, select the entry Connection to
host computer.
Fig. 3-4: Assigning the switch to the network card
4. Confirm with OK.

C: Sharing the virtual switch in the company network
1. Navigate here on the host computer:
Control Panel > “Network and Internet” > “Network Connections” (or
“Change adapter options”)
2. Right-click on the Ethernet switch of the company network (!) and se-
lect Properties.
This does NOT refer to the new switch “Connection to host comput-
er” or the “Hyper-V Virtual Ethernet Adapter”.
The properties display is opened.

3. Select the Sharing tab.
• Activate both check boxes.
• Under Home networking connection, select: … (Connection to
host computer).
• OK

KUKA.OfficeLite 8.6

Fig. 3-5: Sharing the switch
The virtual machine can now be started.

(>>> 3.3.1.4 "Starting virtual machine via Hyper-V manager" Page 19)
3.3.1.4 Starting virtual machine via Hyper-V manager
Precondition
• The virtual machine is set up and configured under Hyper-V.
Procedure

2. Select the current computer on the left-hand side under Hyper-V Man-
ager.
3. Select the virtual machine in the central area under Virtual Machines.
4. Click on Start under the new virtual machine on the right-hand side.
(The Start button is now hidden. New buttons, e.g. Pause, appear.)
5. Click on Connect..., which is also on the right-hand side.
Fig. 3-6: Connecting started virtual machine
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)
3.3.2 Checking the network connection
Description
If it is not possible to access an external system, e.g. the license server,

from the virtual machine, it is recommended to check whether the corre-
sponding computer can be pinged.
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.
Fig. 3-7: Send ping
3. If the pinged computer does not respond, contact the network adminis-
trator to check the network or domain settings.
3.3.3 Language settings for the virtual machine
• The Windows language of the virtual machine is English by default.

• The keyboard assignment is German by default.
The language settings can be changed on the virtual machine in the same
manner as for a real computer.
NOTICE
Information about changing the language settings can be found on the
Internet on Microsoft webpages.

KUKA.OfficeLite 8.6

3.4 Using a USB device on the host computer and virtual machine
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
• The virtual machine is set up and configured under Hyper-V.
Procedure
A: Start the virtual machine

2. Select the current computer on the left-hand side under Hyper-V Man-
ager.
3. Select the virtual machine in the central area under Virtual Machines.
4. Click on Start under the new virtual machine on the right-hand side.
(The Start button is now hidden. New buttons, e.g. Pause, appear.)
5. Click on Connect..., which is also on the right-hand side.
Fig. 3-8: Connecting started virtual machine
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.
B: Settings for USB usage

1. Click on Show options in the new window.

Fig. 3-9: Click on “Show options”
2. Activate the check box next to Save my settings for future connec-
tions to this virtual machine.
Fig. 3-10: Selecting “Save my settings […]”
3. Select the Local Resources tab.

Click on More… .

KUKA.OfficeLite 8.6

Fig. 3-11: Click on “More...”
4. Select the drives and devices.
Fig. 3-12: Selecting drives and devices
Confirm with OK.

5. The window from step B1 is now shown again.
Click on Connect.
The user interface of the virtual machine is now displayed.
6. Click on the menu item View and check:
• Enhanced session is already activated? -> Continue directly to
next step.
• Enhanced session is not yet activated? -> Click on the entry to
activate the check box.
The menu item and the entire menu bar are only visible if the win-
dow is NOT in fullscreen mode.

Fig. 3-13: “Enhanced session” activated
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.
Fig. 3-14: USB device is displayed on the virtual machine
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)
3.5 Installing KUKA.VRC Interface or Y200Interface
Description
For connection to KUKA.Sim/Sim Pro, the KUKA.VRC Interface software

must be installed on the virtual image on which KUKA.OfficeLite is instal-
led. KUKA.VRC Interface is only licensed in conjunction with KUKA.Sim or
KUKA.Sim Pro.
For connection to another simulation program, e.g. WinMOD, the Y200In-
terface software must be installed on the virtual image. Y200Interface
does not have to be licensed.
KUKA.VRC Interface and Y200Interface cannot be installed together on
the virtual image.

KUKA.OfficeLite 8.6

Precondition
• Only for Y200Interface: The simulation program used supports Y200In-

terface.
• KUKA.OfficeLite is started.
• For KSS: User rights: Function group General configuration
• For VSS: User group “User”
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.
• The following icon is now displayed in the task bar:

The following applies for KUKA.VRC Interface:
• Once Windows has booted, the smartHMI is no longer (!) automat-
ically started.
• To start smartHMI, select All Programs > KUKA > StartKRC in
the Windows Start menu of the virtual machine.
3.6 Uninstalling KUKA.VRC Interface or Y200Interface
Precondition
• For KSS: User rights: Function group General configuration

• For VSS: User group “User”
Procedure
1. In the main menu, select Start-up > Additional software.

2. Activate the check box next to the entry VRC Interface or Y200 Inter-
face and press Uninstall.
3. Answer the request for confirmation with Yes.
4. Answer the request for confirmation Do you want to activate the
project […]? with Yes.
5. An overview with the changes and a request for confirmation are dis-
played. Answer this with Yes. The interface is uninstalled and the ro-
bot controller carries out a reboot.
LOG file
A LOG file is created under C:\KRC\ROBOTER\LOG.

3.7 Y200 und Y-NET interfaces – Overview
Description
The Y200Interface software comprises the following interfaces:

• Y200
• Y-NET (from Y200Interface V2.1 onwards)
The interfaces can be used to read and write $IN[1] to $IN[8192] and
$OUT[1] to $OUT[8192]. $BASE, $TOOL, $POS_ACT and $AXIS_ACT as
well as safety inputs/outputs can likewise be read or written.
Only one of the two interfaces can be used: Activating Y-NET automati-
cally sets Y200 inactive.
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.
Y200Interface.config with default settings
The Y-NET interface (lines 6 to 12) is included from Y200Interface V2.1

onwards.
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>
3.7.1 Configuring Y200 interface
Precondition
• Y200Interface is installed.
Procedure
• Edit the following parameters in the file C:\KRC\User\Y200Inter-

face.config:
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)

KUKA.OfficeLite 8.6

Y200WriteOffset Start of the output data image on the Y200 shared
memory (in bytes)
UseWinModNetIn- Must be FALSE.
terface
Shared memory
The following data are stored on the shared memory:

Byte offset Length (byte) Data
0 1024 Inputs $IN[]
1024 1024 Outputs $OUT[]
2048 48 Axis-specific position $AXIS_ACT
2096 24 Cartesian position $POS_ACT
2120 24 Current base $BASE
2144 24 Current tool $TOOL
3.7.2 Activating and configuring Y-NET interface
Precondition
• Y200Interface ≥ V2.1 is installed.
Procedure
• Edit the following parameters in the file C:\KRC\User\Y200Inter-

face.config:
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.

Icons in the task bar
Icon Description
Icon with green dot: connection established to WinMOD.
Icon with red dot: no connection to WinMOD.

KUKA.OfficeLite 8.6
Licensing
4 Licensing
4.1 License types
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
A license key is required for licensing KUKA.OfficeLite and VRC.
Precondition
• The virtual machine has been started.
Procedure
1. When you start the virtual machine for the first time, the FLEXnet Li-
cense Finder opens.
Fig. 4-1: FLEXnet License Finder
• If a server license is to be used and a license server already ex-

ists:

KUKA.OfficeLite 8.6
Select Specify the License Server System.

Licensing
Continue with Next> and enter the server name. Continue with
Next> and confirm with Finish.
If there is a server license available, it is possible to start using Of-
ficeLite directly.
• If a single PC license is to be used, but none is yet available, or if
there is not yet a license server available:
Click on Cancel to close the activation wizard and acknowledge
the error message with OK.
• If a single PC license is already available: It is possible to select
Specify the License File and navigate to the license.
2. Do not exit the virtual machine yet. The subsequent procedure for li-
censing OfficeLite depends on whether a single PC license or server
license is to be used.
(>>> 4.3 "Using KUKA.OfficeLite with a single PC license" Page 30)
(>>> 4.4 "Using KUKA.OfficeLite with a server license" Page 31)
The following shortcuts can now be found on the desktop:
• To the FLEXLM folder
• To FingerprintCreator.exe
4.3 Using KUKA.OfficeLite with a single PC license
4.3.1 Requesting a single PC license
Procedure
1. Start the FingerprintCreator via the desktop shortcut. KUKA Finger-

print Creator opens.
2. Enter the path for saving the fingerprint in the Select Output File box,
or use the ... button to select the file location.
If the data are being saved to a USB stick, the virtual machine must
be active when the stick is connected. If no USB drive is displayed
in the virtual machine, it must be connected manually to the virtual
machine.
3. Click on the Create button. The KUKA Fingerprint *.kfp is created in

the specified location.
4. Send the fingerprint file *.kfp with the following information by e-mail to
Simulation.Robotics.De@kuka.com:
• KUKA reference number for the purchased software (found under
Supplier Ref. No. on the Order Confirmation from KUKA)
The license key is requested. The license file *.lic will be sent to you by
KUKA Roboter.
4.3.2 Activating KUKA.OfficeLite with a single PC license
Precondition
• The license file *.lic is present.

• The virtual network cards are activated.

KUKA.OfficeLite 8.6
Licensing
Procedure
1. Start the virtual machine.

KUKA.OfficeLite is started and the activation wizard FLEXnet License
Finder is opened.
2. Save the license file *.lic on the virtual machine.
3. Select the license type Specify the License File. Click Next> to pro-
ceed.
4. Enter the location and name of the license file *.lic or use Browse to
search for the license file *.lic and load it. Click Next> to proceed.
5. Confirm the licensing with Finish.
KUKA.OfficeLite is now licensed and activated.
The smartHMI is closed in the event of a licensing error, e.g. if an incor-

rect license file has been used.
To repeat the licensing, execute the program C:\KRC\SmartHMI\SmartH-
MI.exe on the virtual machine. The activation wizard FLEXnet License
Finder is opened again.
4.4 Using KUKA.OfficeLite with a server license
4.4.1 Requesting a server license
Procedure
1. In the virtual machine, copy the folder FLEXLM in the directory

C:\KRC\UTIL.
2. Save the folder FLEXLM on the license server. The virtual system can
now be terminated.
3. Start the lmtools.exe program in the FLEXLM folder on the license
server. The LMTOOLS window is opened.
4. On the System Settings tab, click on the button Save HOSTID Info
to a File.
5. Select the file location and enter a name for the license request file.
Click on Save. The license request file is created.
6. Send the license request file with the following information by e-mail to
Simulation.Robotics.De@kuka.com:
• KUKA reference number for the purchased software (found under
Supplier Ref. No. on the Order Confirmation from KUKA)
The license key is requested. The license file *.lic will be sent to you by
KUKA Roboter.
4.4.2 Starting up the license server for KUKA.OfficeLite
Precondition
• The license file *.lic is present.
Procedure
1. Save the license file *.lic on the license server.

2. Start the lmtools.exe program in the FLEXLM folder on the license
server. The LMTOOLS window is opened.
3. Select the Config Services tab.

Licensing KUKA.OfficeLite 8.6
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.
Fig. 4-2: LMTOOLS – Config Services
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.
Fig. 4-3: LMTOOLS – Start/Stop/Reread

KUKA.OfficeLite 8.6
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
1. Start the virtual machine.

KUKA.OfficeLite is started and the activation wizard FLEXnet License
Finder is opened.
2. Select the license type Specify the License Server System. Click
Next> to proceed.
3. Enter the name of the license server. Click Next> to proceed. The li-
cense server automatically assigns a license from its license pool.
4. Confirm the licensing with Finish.
KUKA.OfficeLite is now licensed and activated.
The smartHMI is closed in the event of a licensing error, e.g. if an incor-

rect license file has been used.
To repeat the licensing, execute the program C:\KRC\SmartHMI\SmartH-
MI.exe on the virtual machine. The activation wizard FLEXnet License
Finder is opened again.
4.5 License management and use of server licenses
Detailed information about license management can be found in the Li-

cense Administration Guide for FLEXlm. This guide is included in the
scope of supply for KUKA.OfficeLite.
4.5.1 Borrowing licenses
Precondition
• KUKA.OfficeLite is not running.

• KUKA VRC Manager is not running.
• Network connection to the license server
• The maximum borrow time for licenses is known. (Can be requested
from the server administrator.)
The borrow time for licenses is limited as standard to 30 days by

KUKA. If there is only a limited number of licenses available on the li-
cense server, it is possible that the server administrator may further re-
duce the maximum borrow time.
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.

Fig. 4-4: LMTOOLS – Utilities
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.
Fig. 4-5: LMTOOLS – Borrowing
5. Click on Set Borrow Expiration to save the settings on the Borrow-

ing tab.
6. Start KUKA.OfficeLite.
7. Start KUKA VRC Manager if required for connecting to KUKA.SimPro.
8. The PC can be disconnected from the license server: remove the net-
work cable.

KUKA.OfficeLite 8.6
Licensing
9. Click on List Currently Borrowed Features to check whether licens-
ing was successful.
The licensed applications are displayed:
• KUKAROB_HMI_8 for KUKA.OfficeLite

• KUKAROB_VRC_2 for the VRC interface
4.5.2 Returning borrowed licenses early
Precondition
• KUKA.OfficeLite is not running.

• KUKA VRC Manager is not running.
• Network connection to the license server
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
Fig. 4-6: LMTOOLS – Borrowing (returning licenses)
3. Click on Return Borrowed Licenses Early to return the license for

the application specified unter Feature Name.
4. Start the application (KUKA.OfficeLite or KUKA VRC Manager). The li-
cense is returned to the license server only after the application has
been started.
5. Click on List Currently Borrowed Features to check that the bor-
rowed license has been successfully returned. The application is no
longer shown in the list of licensed applications.

4.5.3 Transferring licenses
Overview
A new license must be requested in the following cases:

Case License transfer
After the host computer has been exchanged, Send the old license file together with the fol-
the old license is no longer valid on the new lowing information to Simulation.Robot-
computer. ics.De@kuka.com:
If the current license no longer matches the • In the case of a single PC license: finger-
computer, this is indicated by FLEXlm (Error print file *.kfp
Code -9: Invalid host).
• In the case of a server license: host ID
If the OfficeLite image is moved to a different and host name of the license server
folder, the old license is no longer valid.
Note: To reactivate OfficeLite, the old license
FLEXlm issues an error message (Error Code file in the virtual machine or on the license
-9: Invalid host). server must be deleted.
Licenses are valid for 12 months. If a license Send the old license file to the following ad-
has expired, it can be renewed. dress: Simulation.Robotics.De@kuka.com
If a license has expired, this is indicated by
FLEXlm (Error Code -10: Feature has ex-
pired).
After a software update, i.e. if a new build of Send the old license file together with the or-
KUKA.OfficeLite is installed, the host ID is der number for the software update or soft-
changed. The old license is no longer valid. ware maintenance agreement to the following
address: Simulation.Robotics.De@kuka.com
Modification of the number of server licenses Send the old server license file together with
on the license server the desired number of server licenses to the
following address: Simulation.Robot-
ics.De@kuka.com
Modification of the maximum possible borrow Send the old server license file together with
time of server licenses on the license server the desired number of hours to the following
address: Simulation.Robotics.De@kuka.com
As standard, server licenses can be borrowed
for a maximum of 30 days (= 720 hours).

KUKA.OfficeLite 8.6
Operation, KUKA.OfficeLite
5 Operation, KUKA.OfficeLite
5.1 Overview of the graphical user interface
The KUKA.OfficeLite user interface is largely identical to the KUKA

smartHMI. The operator control elements of the KUKA smartPAD that are
required for programming are made available as additional buttons.
The user interface is displayed in the language that was selected during
installation of the software. If desired, a different language can be set
again from the main menu.
Further information about the KUKA smartHMI is contained in the oper-
ating and programming instructions for the System Software.
Fig. 5-1: Overview of the graphical user interface
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).

Operation, KUKA.OfficeLite KUKA.OfficeLite 8.6
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.
5.2 Simulating inputs
KUKA.OfficeLite can be used to simulate physical inputs. Some inputs are

write-protected and cannot be simulated.
Procedure
Setting a simulated input:
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
Fig. 5-2: Digital inputs
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:

KUKA.OfficeLite 8.6
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.
5.3 I/O simulation via VRC – Note
Description
KUKA.OfficeLite can be used together with KUKA.Sim / Pro in order to

simulate, for example, the signal exchange between a sensor and a robot.
A signal is only transmitted when an edge change is detected.
To ensure that an edge change occurs from FALSE to TRUE when an
output is set, the I/Os used must be set to FALSE at the beginning of the
program.
5.4 Testing I/Os with Y200 test client
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
• Y200 interface is configured.

• Y-NET interface is not active.
Procedure
1. Right-click on the Y200 icon in the task bar:

2. Select Visu in the context menu.
The test client opens.
3. For testing purposes, set inputs, for example.

Operation, KUKA.OfficeLite KUKA.OfficeLite 8.6
Fig. 5-3: Y200 test client

KUKA.OfficeLite 8.6
KUKA.Sim with KUKA.OfficeLite

6 KUKA.Sim with KUKA.OfficeLite
6.1 Deploying the project from KUKA.Sim/Sim Pro to KUKA.OfficeLite
Description
KUKA.Sim automatically creates a WorkVisual project in the background

for each Sim project. This can be transferred directly from KUKA.Sim to
KUKA.OfficeLite (or to another target controller).
Detailed information about the following steps, e.g. loading a robot into
the 3D scene, can be found in the help of KUKA.Sim.
Precondition
• Network connection to the target controller
Procedure in KUKA.Sim
A: Important settings when creating the project in KUKA.Sim

1. FILE area > Options > General > Machine data service
• Supply voltage: Select the required voltage.
• Controller version: Select the required controller version.
2. Confirm with OK.
The controller version must be set before a robot is loaded into the
3D scene.
The controller version must correspond to that of the target control-

ler. In KUKA.OfficeLite (or on another target controller), the controller
version can be viewed here: Main menu Help > Info > Info
3. Load the robot into the 3D scene.

B: Configure the cell as required in KUKA.Sim.
C: Deploying a project from KUKA.Sim to the controller
1. Save the Sim layout in KUKA.Sim.
2. Press Play in the 3D scene to generate the project.
3. In the START area, click on Transfer configuration onto controller

on the ribbon.
The Project deployment window opens.

• The controller from the Sim project is displayed on the left-hand
side.
• The target controller is displayed on the right-hand side. It is
grayed out when no specific controller has yet been selected.
4. To select the target controller:
a. Click on the ... button (3 dots). A window opens.

KUKA.OfficeLite 8.6
The filter is automatically set to only display controllers of the

KUKA.Sim with KUKA.OfficeLite
same type and version as the project controller.

b. Select the target controller and click on OK.
5. Now set the following on the target controller (!):
• Administrator user group
• T1 mode
6. Click on Finish in the Project deployment window in KUKA.Sim (!).
KUKA.Sim checks the controllers for conflicts.
7. Only if conflicts exist:
The Resolve conflicts view is displayed. Conflicts must be resolved;
otherwise, the project cannot be transferred.
a. Click on the desired solution for each conflict. The selected solu-
tion is now highlighted in blue.
b. Click on Finish.
Common conflicts are, for example, Name conflict for the cell or
Name conflict for the controller '{0}': In these cases, always rename
the local controller!
Fig. 6-1: Example view “Resolve conflicts”
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.

KUKA.OfficeLite 8.6
Messages
7 Messages
7.1 Error messages during licensing
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:
• The license server is not running.

• Or: The wrong license file is being
used.
• Or: The host ID or host name has
been changed.
-88 System clock has been set back Adapt the Windows system time and
time zone in the virtual machine to the
The Windows system time in the virtual
current actual world time (UTC).
machine differs too greatly from the cur-
rent actual world time (UTC).
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.

Messages KUKA.OfficeLite 8.6

KUKA.OfficeLite 8.6
KUKA Service
8 KUKA Service
8.1 Requesting support
Introduction
This documentation provides information on operation and operator con-

trol, and provides assistance with troubleshooting. For further support,
please contact your local subsidiary.
Information
The following information is required for processing a support re-

quest:
• Description of the problem, including information about the duration
and frequency of the fault
• The greatest possible amount of information about the hardware and
software components of the overall system
The following list gives an indication of the information which is rele-
vant in many cases:
‒ Model and serial number of the kinematic system, e.g. the manip-
ulator
‒ Model and serial number of the controller
‒ Model and serial number of the energy supply system
‒ Designation and version of the system software
‒ Designations and versions of other software components or modifi-
cations
‒ System software diagnosis package
Additionally for KUKA Sunrise: Existing projects including applica-
tions
For versions of KUKA System Software older than V8: Archive of
the software (Diagnosis package is not yet available here.)
‒ Application used
‒ External axes used
8.2 KUKA Customer Support
The contact details of the local subsidiaries can be found at:

www.kuka.com/customer-service-contacts

KUKA Service KUKA.OfficeLite 8.6

KUKA.OfficeLite 8.6
Index KUKA Customer Support............................... 45

KUKA Service.................................................45
KUKA.Sim....................................................... 11
KUKA.Sim Pro................................................ 11
B KUKA.Sim with KUKA.OfficeLite....................41
Borrowed licenses, returning..........................35 KUKA.VRC Interface...................................... 10
Borrowing................................................. 29, 33 KUKA.VRC Interface, installing......................24
KUKA.VRC Interface, uninstalling..................25
C
Connection to the host computer, Hyper-V...16 L
License management..................................... 33
License request.............................................. 29
D License server, start-up..................................31
Diagnosis package......................................... 45 License types..................................................29
Documentation, industrial robot....................... 5 License, expired............................................. 36
Licenses, borrowing........................................33
Licenses, transferring..................................... 36
E Licensing.........................................................29
EMD.................................................................. 6 Login............................................................... 13
Enhanced session.......................................... 23
Error messages, licensing..............................43
M
Main menu key...............................................37
F Messages........................................................43
Functions.......................................................... 9 Misuse.............................................................11
Functions, constraints.......................................9
N
G Network connection, checking....................... 20
Graphical user interface, overview................ 37 NTFS.......................................................... 6, 10
H O
Hard disk space............................................. 13 OfficeLite, activating.................................30, 33
Hardware, system requirements.................... 13 OfficeLite, operation....................................... 37
Hyper-V.............................................................6 Operation, OfficeLite.......................................37
Hyper-V Manager, starting............................. 15 Outputs, simulating.........................................39
Overview, graphical user interface................ 37
I
Inputs, simulating..................................... 38, 39 P
Intended use................................................... 11 Password, changing....................................... 13
Introduction....................................................... 5 Performance................................................... 10
Power save mode, deactivation.....................13
Product description...........................................9
J
Jog keys......................................................... 37
R
RAM................................................................ 13
K
Keyboard.........................................................38
Keyboard key..................................................38 S
KLI................................................................ 6, 9 Safety instructions............................................ 5
Knowledge, required.........................................5 Server license.................................................29
KPP...................................................................6 Server license, requesting..............................31
KRL................................................................... 6 Server licenses, management........................33
KSP...................................................................6 Simulation....................................................... 38

KUKA.OfficeLite 8.6
Single PC license........................................... 29
Single PC license, requesting........................30
smartHMI.......................................................... 6
smartPAD..........................................................6
Software, components....................................10
Software, system requirements......................13
Start backwards key.......................................38
Start key......................................................... 37
STOP key....................................................... 38
Support request.............................................. 45
System requirements......................................13
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
Z
ZIP............................................................ 10, 15

KUKA_OfficeLite_86_en

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

KUKA_OfficeLite_86_en

Uploaded by

Copyright:

Available Formats

KUKA System Technology

Publication: Pub KUKA.OfficeLite 8.6 (PDF) en

Book structure: KUKA.OfficeLite 8.6 V8.1

Version: KUKA.OfficeLite 8.6 V7

2/48 | www.kuka.com KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023

3 Installation and configuration................................................................ 13

KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023 www.kuka.com | 3/48

6 KUKA.Sim with KUKA.OfficeLite............................................................ 41

4/48 | www.kuka.com KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023

1.1 Target group

This documentation is aimed at users with the following knowledge and

• Basic knowledge of KRL programming

For optimal use of KUKA products, we recommend the training courses

1.2 Industrial robot documentation

The industrial robot documentation consists of the following parts:

• Documentation for the robot arm

1.3 Representation of warnings and notes

KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023 www.kuka.com | 5/48

These warnings contain references to safety-relevant information or gen-

This warning draws attention to procedures which serve to prevent or rem-

Procedures marked with this warning must be followed exactly.

These notices serve to make your work easier or contain references to

1.4 Terms used

6/48 | www.kuka.com KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023

KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023 www.kuka.com | 7/48

8/48 | www.kuka.com KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023

2.1 Product description

KUKA.OfficeLite is a work environment which allows users to practice han-

The following functions of the System Software are supported:

• Creation and simulation of programs

KUKA.OfficeLite does not support the following functions of the System

• Diagnosis of the safety circuits

A network connection can be established by Windows via the virtual

Technology packages can only be installed on the System Software image

KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023 www.kuka.com | 9/48

By default, KUKA.OfficeLite does not execute processes in real time, but

2.4 Software components

KUKA.OfficeLite is supplied as a ZIP directory and contains a virtual ma-

The virtual system is Hyper-V (KUKA.OfficeLite 8.6 Build 09 or higher).

10/48 | www.kuka.com KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023

KUKA.OfficeLite 8.6 can be used in combination with KUKA.Sim Pro 3.x

Projects created with KUKA.WorkVisual 6.x can be transferred to the Sys-

2.6 Intended use and misuse

KUKA.OfficeLite is exclusively intended for executing an image of the

Any use or application deviating from the intended use is deemed to be

KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023 www.kuka.com | 11/48

12/48 | www.kuka.com KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023

Installation and configuration

3.1 System requirements

The individual IT environment on site can impact the operation of

Software (from KUKA.OfficeLite 8.6 Build 09 onwards)

• Windows 10 Pro or Windows 10 Enterprise

Older builds of KUKA.OfficeLite do not use Hyper-V as the virtual sys-

3.2 Logging into OfficeLite / changing the password

It may sometimes be necessary to log in manually, for example if the vir-

The password 68kuka1secpw59 can be changed. Information about

KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023 www.kuka.com | 13/48

3.3 Virtual system

3.3.1.1 Activating Hyper-V

Hyper-V can be activated in other ways besides the procedure descri-

If the Windows service Hyper-V is active and the VMware software is

14/48 | www.kuka.com KUKA.OfficeLite 8.6 V7 | Issued: 21.11.2023

Installation and configuration

3.3.1.2 Setting up virtual machine under Hyper-V