KST PLC ProConOS 40 en
KST PLC ProConOS 40 en
Issued: 07.07.2011
© Copyright 2011
KUKA Roboter 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 Roboter 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 software
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 regular basis, how-
ever, and necessary corrections will be incorporated in the subsequent edition.
Subject to technical alterations without an effect on the function.
Translation of the original documentation
KIM-PS5-DOC
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 Trademarks ................................................................................................................ 6
1.5 Terms used ................................................................................................................ 6
3 Safety ............................................................................................................ 9
3.1 Safety measures for “single point of control” ............................................................. 9
4 Installation ................................................................................................... 11
4.1 System requirements ................................................................................................. 11
4.2 Installing or updating KUKA.PLC ProConOS 4-1 ...................................................... 11
4.3 Uninstalling KUKA.PLC ProConOS 4-1 ..................................................................... 11
5 Operation ...................................................................................................... 13
5.1 Controlling ProConOS by means of KRL ................................................................... 13
5.1.1 Calling up the status of ProConOS ....................................................................... 13
5.1.2 Powerfail status .................................................................................................... 13
5.1.3 Starting ProConOS ............................................................................................... 14
5.1.4 Stopping ProConOS ............................................................................................. 14
6 Configuration ............................................................................................... 15
6.1 Configuring a task priority .......................................................................................... 15
6.2 Configuring the ProConOS/Multiprog interface .......................................................... 16
6.3 Configurable ProConOS parameters ......................................................................... 16
6.3.1 PrioSvisor parameter ............................................................................................ 16
6.3.2 PRIOUSER parameter .......................................................................................... 17
6.3.3 PRIOSYSTEM parameter ..................................................................................... 17
6.3.4 PrioIdle parameter ................................................................................................ 18
6.3.5 KukaScheduling parameter .................................................................................. 18
6.3.6 KukaSettings/NrkTick parameter .......................................................................... 18
6.3.7 KukaSettings/ExempTask parameter ................................................................... 19
6.3.8 FileAccess_RootPath parameter .......................................................................... 19
6.3.9 WriteTsmOnStop parameter ................................................................................. 19
6.3.10 ProgramSize parameter ........................................................................................ 19
6.3.11 ReloadBootFileAtReconfig parameter .................................................................. 19
6.3.12 IgnoreDeinstalledIoDrv parameter ........................................................................ 19
6.3.13 WarmStartCheck parameter ................................................................................. 20
6.3.14 DELRETAIN parameter ........................................................................................ 20
6.3.15 AUTOARCHIVERETAIN parameter ..................................................................... 20
6.3.16 RETAINSIZE parameter ....................................................................................... 20
6.3.17 ProConOS_ROOTPATH parameter ..................................................................... 21
6.3.18 SIGNALFILES parameter ..................................................................................... 21
6.3.19 SIGNALFILEREAD parameter .............................................................................. 21
7 Diagnosis ...................................................................................................... 23
7.1 Displaying diagnostic data ......................................................................................... 23
Index ............................................................................................................. 33
1 Introduction
This documentation is aimed at users with the following knowledge and skills:
Advanced KRL programming skills
Advanced PLC programming skills
Advanced knowledge of the robot controller system
Hints These hints serve to make your work easier or contain references to further
information.
1.4 Trademarks
Term Description
KLI KUKA Line Interface. Connection to higher-level control
infrastructure (PLC, archiving)
Exception Exceptional treatment for a specific event.
KUKA.PLC Soft PLC for use in the robot controller.
Multiprog 5-35
WorkVisual Software that serves as an offline engineering system
for the software of KR C4-controlled robot systems.
SPOC Single Point of Control
Retentive data Data that are retained even when the PLC is reset.
Time slice Allocated time slot in which an application takes over the
CPU processing time.
Watchdog Function that monitors the max. allocated processing/
response time.
2 Product description
Description KUKA.PLC ProConOS 4-1 is a runtime system that is used by the technology
package KUKA.PLC Multiprog 5-35 to execute PLC applications on the robot
controller. ProConOS is compatible with the IEC standard 61131-3, and thus
employs standardized syntax and semantics. ProConOS can be configured by
means of an initialization file, and can be adapted flexibly to the requirements
of the robot system.
Item Description
1 KR C4:
Windows operating system
VxWorks real-time operating system
ProConOS runtime system
2 Connection: KLI
3 External PC/laptop:
Windows operating system
MULTIPROG PLC development environment
WorkVisual offline engineering system
3 Safety
This documentation contains safety instructions which refer specifically to the
software described here.
The fundamental safety information for the industrial robot can be found in the
“Safety” chapter of the Operating and Programming Instructions for System In-
tegrators or the Operating and Programming Instructions for End Users.
Overview If certain components in the industrial robot are operated, safety measures
must be taken to ensure complete implementation of the principle of “single
point of control” (SPOC).
Components:
Submit interpreter
PLC
OPC Server
Remote control tools
Tools for configuration of bus systems with online functionality
KUKA.RobotSensorInterface
External keyboard/mouse
Since only the system integrator knows the safe states of actuators in the pe-
riphery of the robot controller, it is his task to set these actuators to a safe
state, e.g. in the event of an EMERGENCY STOP.
T1, T2 In the test modes, the components referred to above (with the exception of the
external keyboard/mouse) may only access the industrial robot if the following
signals have the following states:
Submit inter- If motions, (e.g. drives or grippers) are controlled with the Submit interpreter
preter, PLC or the PLC via the I/O system, and if they are not safeguarded by other means,
then this control will take effect even in T1 and T2 modes or while an EMER-
GENCY STOP is active.
If variables that affect the robot motion (e.g. override) are modified with the
Submit interpreter or the PLC, this takes effect even in T1 and T2 modes or
while an EMERGENCY STOP is active.
Safety measures:
In the test modes, the system variable $OV_PRO must not be written to
by the Submit interpreter or the PLC.
Do not modify safety-relevant signals and variables (e.g. operating mode,
EMERGENCY STOP, safety gate contact) via the Submit interpreter or
PLC.
If modifications are nonetheless required, all safety-relevant signals and
variables must be linked in such a way that they cannot be set to a dan-
gerous state by the Submit interpreter or PLC.
OPC server, These components can be used with write access to modify programs, outputs
remote control or other parameters of the robot controller, without this being noticed by any
tools persons located inside the system.
Safety measures:
KUKA stipulates that these components are to be used exclusively for di-
agnosis and visualization.
Programs, outputs or other parameters of the robot controller must not be
modified using these components.
If these components are used, outputs that could cause a hazard must be
determined in a risk assessment. These outputs must be designed in such
a way that they cannot be set without being enabled. This can be done us-
ing an external enabling device, for example.
Tools for configu- If these components have an online functionality, they can be used with write
ration of bus access to modify programs, outputs or other parameters of the robot control-
systems ler, without this being noticed by any persons located inside the system.
WorkVisual from KUKA
Tools from other manufacturers
Safety measures:
In the test modes, programs, outputs or other parameters of the robot con-
troller must not be modified using these components.
External These components can be used to modify programs, outputs or other param-
keyboard/mouse eters of the robot controller, without this being noticed by any persons located
inside the system.
Safety measures:
Only use one operator console at each robot controller.
If the KCP is being used for work inside the system, remove any keyboard
and mouse from the robot controller beforehand.
4 Installation
Overview KR C4
PROFINET, PROFIBUS or Interbus
Network connections (network switch, network cable, 100 Mbit network
card)
Procedure 1. Select Start-up > Install additional software in the main menu. All addi-
tional programs installed are displayed.
2. Mark the entry ProConOS 4-1 and press Uninstall. Reply to the request
for confirmation with Yes. Uninstallation is prepared.
3. Reboot the robot controller. Uninstallation is resumed and completed.
5 Operation
Description ProConOS can be controlled by means of KRL applications using the function
cIoCtl. The following functions can be executed:
Start ProConOS
Stop ProConOS
Call up status of ProConOS
The function call returns a value of data type INT.
Parameter Description
Function Function number
Parameter Function parameter (data type INT)
StrParameter Additional string parameter
pRet Return status (data type INT)
The value returned by the function is binary coded. However, at no time will
more than one bit be set.
Return values:
Return values:
Value Description
1 Powerfail status is not active.
2 Powerfail status is active.
Return value:
Value Description
0 ProConOS has been started.
Return value:
Value Description
0 ProConOS has been stopped.
6 Configuration
Description The ProConOS priority model describes the fundamental relationships be-
tween the priorities and the various ProConOS tasks. The priority indicates a
precedence in the allocation of CPU computing time and the use of system re-
sources. The priority of tasks is defined in the initialization file ...Config\Us-
er\Common\ProConOS.xml.
Each task is assigned to a task range. The assignment is preset and cannot
be changed. Each task range is assigned a priority. The defined priority is as-
signed to the allocated task in this range. Each task range is represented by a
parameter in the initialization file. The value of the parameter defines the pri-
ority of the tasks located in this range.
The following task ranges are available:
ProConOS Supervisor tasks (high-level tasks): This task range con-
tains all tasks which have a higher priority than the highest-priority user
task, for example robot tasks.
Default value of Supervisor tasks: 141
(>>> 6.3.1 "PrioSvisor parameter" Page 16)
ProConOS User tasks and ProConOS Default task (ProConOS-level
tasks): This task range contains the PLC tasks and the Default task.
Default value of User tasks: 142 to 149
(>>> 6.3.2 "PRIOUSER parameter" Page 17)
ProConOS Internal tasks:
Default value of Internal tasks: 200
(>>> 6.3.4 "PrioIdle parameter" Page 18)
ProConOS System tasks (low-level tasks): Low Level tasks have a low-
er priority than the Default task.
Default value of System tasks: 218 to 223
(>>> 6.3.3 "PRIOSYSTEM parameter" Page 17)
Fig. 6-1
Description A connection to ProConOS can be made via a network card in the robot con-
troller and an external Windows network. This connection can be established
using KLI: KLI can route any TCP/IP ports for the KR C, for VxWorks and for
external PCs. It is thus possible to access ProConOS from an external PC.
Item Description
1 KR C4:
Windows operating system
VxWorks real-time operating system
ProConOS runtime system
2 Connection: KLI
3 External PC/laptop:
Windows operating system
MULTIPROG PLC development environment
WorkVisual offline engineering system
Description The value of this parameter specifies the priority of the ProConOS Supervisor
task. The ProConOS Supervisor task must have the highest priority of all Pro-
ConOS tasks. An example of a Supervisor task is exception handling. The ro-
bot controller must be restarted after the value of this parameter is changed.
Description The value of this parameter specifies the priority of the ProConOS User tasks.
MULTIPROG allows the assignment of 15 priority levels, which can be
mapped on ProConOS by means of PRIOUSER. The priority defined via this
parameter corresponds to priority 1 in MULTIPROG. The default task has the
lowest priority level of the user tasks. The priority of the default task cannot be
defined, since it is calculated by ProConOS from the value of the PRIOUSER
parameter (DEFAULT TASK = PRIOUSER + 15). The default task receives
computing time if no other ProConOS task requires computing time.
The value of the PRIOUSER parameter must be greater than the val-
ue of the PrioSvisor parameter plus 1 (PRIOUSER ≥ PrioSvisor + 1).
Description The value of this parameter specifies the priority of the ProConOS System
tasks. The functions of the ProConOS System tasks are communication with
MULTIPROG, debugging and memory management. System tasks receive
the lowest priority level. The robot controller must be restarted after the value
of this parameter is changed.
Description The value of this parameter defines the priority of two tasks which are used for
internal management purposes:
one task that initializes and starts the ProConOS runtime system
another task that saves the retentive data to the hard drive in the event of
a power failure (Powerfail)
The robot controller must be restarted after the value of this parameter is
changed.
Description The value of this parameter defines which scheduling method is used.
Description The value of this parameter defines the number of ticks within an interpolation
cycle (12 ms) if ProConOS tasks are active.
Description The name of the task that must not be adversely affected by the scheduling
(= continuous cycle access) is entered in this parameter.
Description The value of the parameter defines whether the TSMLog file is saved if the
PLC enters the Stop state.
Description The value of the parameter defines the size (in bytes) of the application pro-
gram.
Description The value of the parameter defines whether the boot file is reloaded after a re-
configuration.
Description The value of the parameter defines whether an error is signaled if the I/O driver
has been uninstalled, but is still active in the ProConOS configuration.
Description The value of the parameter defines whether the retentive data are checked for
CRC equality in the case of a HOT start.
Description The value of this parameter defines whether the retentive data are deleted or
retained.
The robot controller must be restarted after the value of this parameter is
changed.
If retentive variables are inserted in the variable list, all of the subse-
quent variables are shifted. Thus with DELRETAIN = 1, the consis-
tency of the subsequent retentive variables cannot be ensured. New
variables should be inserted only at the end of the variable list.
Description The value of this parameter defines whether the retentive data are saved in
the file when the robot controller is shut down.
Description The value of this parameter defines the size of the area for the retentive data
in bytes. This size can be defined if necessary.
Value Description
4096 Default size 4096 bytes
Description The path specified in this parameter defines the directory in which the ProCo-
nOS files are located. The directory must be read- and write-enabled.
The robot controller must be restarted after the path specification is changed.
Syntax Description
ProConOS_ROOTPATH = ProConOS Path relative to
C:\KRC\ROBOTER
Description The SIGNALFILES parameter is used to signal *.dat files to the ProConOS
system. These files are used to access I/O data symbolically. The parameter
is preset during setup with the following files:
KRC\R1\System\$CONFIG.DAT
KRC\STEU\MADA\$MACHINE.DAT
These files can be expanded.
The function is used by the following libraries:
AutoExLib
ExtensionLib
Description The signal files in the parameter SIGNALFILES are read in accordance with
the entry SIGNALFILEREAD.
Syntax Description
SIGNAL- The signal files are read once by ProConOS on
FILEREAD = START booting.
If the area after “=” is left blank or the parameter
is deleted, the signal files are read every time the
ProConOS program execution is started.
7 Diagnosis
Name Description
Run status ProConOS status:
SPS_ON: ProConOS is started and no
PLC program is loaded.
SPS_RUN: The PLC program is started.
SPS_STOP: The PLC program is loaded
and not started.
SPS_DEBUGGED: The PLC program is
stopped.
SPS_LOADING: The PLC program is
being loaded.
Ticks per second Ticks triggered per second by the PLC
ProConOS system tick Status of the ProConOS system ticks:
status
1: OK
0: Error
ProConOS system tick Consecutive counter of the ProConOS sys-
tem ticks
ProConOS RT tick ProConOS system ticks in seconds
Project status Internal status of the project
Default task cycle time Cycle time of the ProConOS default task (in
ms)
ProConOS project source Exist: ProConOS project exists as a ZIP
code: ZIP name file on the target controller.
None: ProConOS project does not exist
on the target controller.
Name of the boot project Name of the boot project
Project name Name of the ProConOS project
Project configuration Hardware configuration in the project
Resource name Name of the hardware resource
Number of errors Number of errors in the ProConOS error
memory
Pcos_Error(x) Error in the ProConOS memory. The first 10
errors are displayed with error code.
Number of user tasks Number of tasks defined by the user in the
ProConOS project
User_Task_Info(x) Information about a user task:
Name
Watchdog
Type of task: event, cyclical, default
A maximum of 16 user tasks can be config-
ured.
Name Description
User_Task_Statistics(x) Statistics about a user task:
Name
Cycle time
Delay
Number of system tasks Number of system tasks (max. 12)
Sys_Task_Info(x) Information about a system task:
Name
Priority
Mode
Current status
Kernel version Version of the ProConOS kernel
Firmware version KUKA firmware version of ProConOS
ProConOS root dir Directory entered in the
ProConOS_ROOTPATH parameter.
ProConOS file access dir Directory entered in the
FileAccess_RootPath parameter.
Configured program size Value entered in the ProgramSize parameter
Configured retain size Value entered in the RETAINSIZE parameter
Max. available memory Maximum contiguous block of memory avail-
block able in the system (in bytes)
Program memory Program memory available for ProConOS (in
bytes)
System data memory Memory available for system data (in bytes)
SPOC: UserSaveActive Status of the variable
bSPOC_UserSafetyActive:
1: Not safe
0: Safe
SPOC: MotionEnabled Status of the variable
bSPOC_MotionEnabled:
1: Motion is enabled.
0: Motion is not enabled.
Retain data valid 1: ProConOS data that were saved when
the system was shut down are valid.
0: ProConOS data that were saved when
the system was shut down are not valid.
Exemp task Name of the task entered in the KukaSet-
tings/ExempTask parameter
Scheduling ticks Value entered in the KukaSettings/NrkTick
parameter
KRC signal read mode each START: The signal files entered in
the SIGNALFILES parameter are read
every time ProConOS is started.
each BOOT: The signal files entered in
the SIGNALFILES parameter are read
every time the controller is booted.
8 KUKA Service
Introduction The KUKA Roboter GmbH documentation offers information on operation and
provides assistance with troubleshooting. For further assistance, please con-
tact your local KUKA subsidiary.
Availability KUKA Customer Support is available in many countries. Please do not hesi-
tate to contact us if you have any questions.
Index
A PRIOUSER 17
AUTOARCHIVERETAIN 20 PRIOUSER parameter 17
AUTOARCHIVERETAIN parameter 20 ProConOS_ROOTPATH 21
ProConOS_ROOTPATH parameter 21
C ProConOS/Multiprog interface, configuration 16
Configurable ProConOS parameters 16 Product description 7
Configuration 15 PROFIBUS 11
Configuring a task priority 15 PROFINET 11
Configuring the ProConOS/Multiprog interface ProgramSize 19
16 ProgramSize para 19
Controlling ProConOS by means of KRL 13
R
D ReloadBootFileAtReconfig 19
DELRETAIN 20 ReloadBootFileAtReconfig parameter 19
DELRETAIN parameter 20 RETAINSIZE 20
Diagnosis 23 RETAINSIZE parameter 20
Diagnostic data, displaying 23 Retentive data 6
Diagnostic monitor (menu item) 23
Documentation, industrial robot 5 S
Safety 9
E Safety instructions 5
Exception 6 Service, KUKA Roboter 25
SIGNALFILEREAD 21
F SIGNALFILEREAD parameter 21
FileAccess_RootPath 19 SIGNALFILES 21
FileAccess_RootPath parameter 19 SIGNALFILES parameter 21
Single point of control 9
I SPOC 6, 9
IgnoreDeinstalledIoDrv 19 Support request 25
IgnoreDeinstalledIoDrv parameter 19 System requirements 11
Installation 11
Interbus 11 T
Introduction 5 Target group 5
Terms used 6
K Time slice 6
KLI 6 Trademarks 6
KUKA Customer Support 25 Training 5
KUKA.PLC Multiprog 5-35 6
KUKA.PLC ProConOS 4-1, installing 11 W
KUKA.PLC ProConOS 4-1, uninstalling 11 WarmStartCheck 20
KukaScheduling 18 WarmStartCheck parameter 20
KukaScheduling parameter 18 Warnings 5
KukaSettings/ExempTask 19 Watchdog 6
KukaSettings/ExempTask parameter 19 WorkVisual 6
KukaSettings/NrkTick 18 WriteTsmOnStop 19
KukaSettings/NrkTick parameter 18 WriteTsmOnStop parameter 19
O
Operation 13
Overview, KUKA.PLC ProConOS 4-1 7
P
PrioIdle 18
PrioIdle parameter 18
PriosSvisor 16
PrioSvisor parameter 16
PRIOSYSTEM 17
PRIOSYSTEM parameter 17