Restrictions 1

SINUMERIK 840D sl

SINUMERIK Integrate
Run MyVNCK
Restrictions

Function Manual

Valid for

Control Version
SINUMERIK 840D sl 4.5 SP2

Software
SINUMERIK Integrate Run MyVNCK 4.5 SP1

05/2013
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.

DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.

WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.

CAUTION
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.

CAUTION
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.

NOTICE
indicates that an unintended result or situation can occur if the relevant information is not taken into account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.

Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.

Proper use of Siemens products

Note the following:

WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.

Trademarks
All names identified by are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.

Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.

Siemens AG Copyright Siemens AG 2004 - 2013

Industry Sector 05/2013 Technical data subject to change Technical data subject to change
Postfach 48 48
90026 NRNBERG
GERMANY
Contents

1 Restrictions .................................................................................................. 5

1.1 General restrictions.................................................................................... 5

1.2 System requirements................................................................................. 6

1.3 Installation Restrictions.............................................................................. 6

1.4 Deinstallation ............................................................................................. 7

1.5 Block and position display ......................................................................... 7

1.6 Restrictions due to missing drive functionality and sensor feedback

on the machine tool................................................................................... 8

1.7 Compile Cycles, NCU-Link and Safety ...................................................... 8

1.8 Restrictions concerning PLC ..................................................................... 8

1.9 Restrictions due to missing operator panel ............................................... 10

1.10 Restrictions due to missing machine control panel ................................. 10

1.11 Further restrictions in the NC language scope ........................................ 11

1.12 Restrictions concerning HMI-Advanced .................................................. 12

1.13 Restrictions concerning SINUMERIK Operate ........................................ 12

1.14 Preconditions and Known Issues............................................................. 14

1.15 Preconditions and Known Issues for Developers .................................... 16

Run MyVNCK Restrictions

Function Manual, 05/2013 3
Contents

4 Run MyVNCK Restrictions

Function Manual, 05/2013
1 Restrictions
1
1.1 General restrictions
The virtual NCU component of VNCK Version 4.5 SP1 was generated on the basis
of a SINUMERIK 840D sl software release Version 4.5 SP2.

Please check the software release of the CNC on the machine. Correct start-up
and simulation of the motion and timing response can only be ensured if the
machine data also match those of an NCK 4.5 SP2 on the CNC 840D sl.

VNCK has been designed to simulate an NC part program with a high level of
consistency with the machine.

NC part program testing can be facilitated by integrating the software into a

simulation system using material removal and collision calculation. This is,
however, not a replacement for the proper testing and execution of part program
commissioning on the machine tool itself. The simulated behavior may deviate from
the behavior of the real machine.

In particular, the creator does not guarantee the following when performing
simulations using control and position values generated by the VNCK:
1. The execution of the VNCK simulation in either case.
2. The proper material removal at the workpiece for any movement.
3. The detection of all collisions in the machine area between the machine room
components, the workpiece, the clamping devices and tools.
4. The evidence that any collision reported by the software is a real collision.
5. The evidence that the movement behavior of a simulated machine always
corresponds to the movement behavior of a real machine.

! Warning
VNCK must not be used to optimize or modify the CNC machine data. Never load
machine data or start-up archives that have been processed by VNCK into the
CNC on the machine tool.

Run MyVNCK Restrictions

Function Manual, 05/2013 5
1 Restrictions
1.2 System requirements

1.2 System requirements

VNCK requires a PC-based system with one of the following operating system
installed:
Windows XP Professional 32 bit SP3 or higher
Windows XP Professional 64 bit SP2 or higher
Windows 7 Professional 32 bit SP1 or higher
Windows 7 Professional 64 bit SP1 or higher

The minimum system requirements are:

Intel Pentium or compatible with 1 GHz clock rate
512 MB memory
network card
1 GByte hard disk
German or English operating system language
Admin privileges are required for installation

For known issues with 3rd party software please look at the chapter 1.14.

1.3 Installation Restrictions

The following restrictions apply for installation of VNCK:
VNCK installation setups do not work as update setups to existing
installations of the same major/minor version. Before installing a VNCK
version, existing versions of the same major/minor version must be
uninstalled including existing installations of SINUMERIK Operate.
Parallel installation of VNCK V4.4 (or lower) with VNCK V4.5:
VNCK versions older than V4.5 must be installed before VNCK V4.5 is
installed.
Parallel installation of VNCK V2.1 and VNCK V4.5 with HMI Base/HMI-
Advanced:
Before installing VNCK V2.1/VNCK V4.5 the HMI-Advanced version
matching to VNCK V4.5 needs to be installed (HMI-Advanced V7.6 SP2
HF3 or higher).
If VNCK is installed on Windows 7 operating systems via silent setup an
additional confirmation popup might appear before installation starts.
If VNCK is installed on 64bit operating systems, it must not be installed to
the Windows standard program folder. Some VNCK components are not
able to cope with braces in the program path (c:\program files (x86)\...).
If VNCK is installed with base services of HMI-Advanced and/or
SINUMERIK Operate the suggested standard paths for those two
components should not be changed. Both components must not be
installed to the Windows standard program folder.
During the VNCK installation process existing installations of HMI-
Advanced/ HMI Base and SINUMERIK Operate are detected. If the
existing installation is younger than the one to be installed, the existing
HMI installations are kept and not replaced by the versions included in the
VNCK setup.

Run MyVNCK Restrictions

6 Function Manual, 05/2013
 1 Restrictions
1.4 Deinstallation

1.4 Deinstallation
The following steps must be executed manually, when deinstalling VNCK software:
The path to the VNCK installation folder will remain in the Windows PATH
variable.
The environment variable HMI_INSTALL_DIR will not be deleted during
VNCK deinstallation.
If more than one VNCK version was installed to the computer and one or
more of them ran using HMI Base, the content and mmc.ini settings of the
user folders of HMI Base must be checked after deinstallation of VNCK for
consistency. Alternatively a re-installation of the remaining VNCK versions
is required.
After deinstallation of HMI Base/HMI-Advanced the installation folders of
this software components need to be deleted.
Additionally the registry entries
HKLM\SOFTWARE\Siemens\AUTSW\SIN_HMI-ADV
HKLM\SOFTWARE\Siemens\AUTSW\SIN_HMI-BAS
HKLM\SOFTWARE\Siemens\Shared Tools\HMI-Base
HKLM\SOFTWARE\Siemens\SINUMERIK\HMI-Advanced
need to be deleted.
After deinstallation of SINUMERIK Operate the installation folders of this
software component needs to be deleted.
Additionally the registry entries
HKLM\SOFTWARE\Siemens\AUTSW\SIN_HMISL
HKLM\SOFTWARE\Siemens\SINUMERIK\HMI sl
need to be deleted.
The environment variable HMI_INSTALL_DIR needs to be deleted.
When deinstalling one VNCK version HMI Base services are deinstalled as
well. The remaining VNCK version must be reinstalled with option HMI
Base.

1.5 Block and position display

Due to the asynchronous nature of the preparation and main run in the CNC and
the internal data preparation of the CNC, it may occur that
block displays in the main run do not contain individual blocks (e.g. when a
compressor is used)
time offsets are present between the displayed blocks of the preparation and
the positions in the machine or basic coordinate system as they are displayed in
the connected simulator

Run MyVNCK Restrictions

Function Manual, 05/2013 7
1 Restrictions
1.6 Restrictions due to missing drive functionality and sensor feedback on the machine tool

1.6 Restrictions due to missing drive functionality and sensor

feedback on the machine tool
The numerically controlled axes of the CNC are switched to a simulation mode for
VNCK, i.e. the position controller is approximated by a PT1 element. Speed, torque
or drive current information is not available in VNCK. This also means that drive
signals such as $AA_CUR, $AA_LOAD, $AA_POWER etc. cannot be used in NC
instructions unless they are simulated via the connected simulation system. The
following items are also not available:
master-slave axes, linked axes via position controller
drive speed feedback, such as it is e.g. required for thread-cutting with G33,
G34, G35, tapping with G331, G332, tapping with compensating chuck G63
drive-to-fixed-stop is not supported, when being programmed inside a
synchronous action

1.7 Compile Cycles, NCU-Link and Safety

Before using OEM specific compile cycles with VNCK it must be ensured that the
OA interface version against which the compile cycles are created is compatible
with the VNCK version. If in doubt please contact the OEM and/or the compile
cycle vendor.

VNCK has been designed to simulate either a single NCU or a NCU link system
with up to three NCUs.

VNCK does not support Safety Integrated.

1.8 Restrictions concerning PLC

Generally VNCK does not include a PLC. However, the PLC logic and PLC-
controlled motions can be simulated by the simulation system of which VNCK
forms an integral part. This results in restrictions in the use of
synchronous actions if the events relate to the PLC,
PLC-controlled axes,
multiple feed rates within a single block (FMA),
H functions (PLC function must be simulated by simulation system),
external work offset (PLC).

Nevertheless there is the possibility to run a VPLC unit to simulate a complete

virtual machine:

When running VNCK with VPLC the following restrictions apply:

SIMATIC STEP7:
Running SIMATIC STEP7 on the same PC as VPLC has not been tested. Although
the configuration may succeed sometimes, Siemens will take no responsibility for a
correct behaviour of this system. Please use a separate PC with STEP7 to connect
to VPLC using a standard Ethernet connection. VPLC inherits the IP-Address from
the Host-PC it is executed on.

Run MyVNCK Restrictions

8 Function Manual, 05/2013
 1 Restrictions
1.8 Restrictions concerning PLC

A compatible version of the PLC Toolbox 840D sl required for SIMATIC STEP7 to
work with VPLC. The PLC application has to include a matching version of the
basic program (Grundprogramm). Please check VNCK_server_versions.txt for
the enclosed version of the NCK system software.

VPLC:
The integrated PLC version is based on PLC firmware version 20.70.45 of PLC
317-2DP (released with SINUMERIK V2.7 SP1). It does not support firmware
version 32.71.07 of PLC 317-3DP/PN (released with SINUMERIK V4.5 SP1) or
higher.
In version VNCK4.5 SP1 however the VPLC was extended to be compatible with
Profibus-based hardware configurations.
Profinet-based hardware configurations are not supported.
The real PLC controller 317-3DP/PN comes with some additional PLC functions,
which are not supported by VPLC. The following PLC functions are not supported
by VPLC:

OB 61 Synchronous cycle interrupt

OB 83 Insert/remove module interrupt
OB 87 Communication error

SFB 73 Receive a process data Record

SFB 74 Provide a process data record
SFB 81 Reading predefined parameters asynchronous
SFB 104 Set IP configuration data

SFC 70 Determine logical address

SFC 71 Determine geographical address
SFC 82 Create a data block in load memory
SFC 83 Read data block out of load memory
SFC 84 Write data block in load memory
SFC 99 Process web request
SFC 102 Reading predefined parameters asynchronous
SFC 103 Determination of DP bus technology
SFC 105 Reading dynamically assigned system instances
SFC 106 Deleting dynamically assigned system instances
SFC 107 Creating acknowledgeable block-related message
SFC 108 Creating acknowledged block-related message
SFC 109 Protect CPU access
SFC 112 Update the inputs of the PROFINET component user program interface
SFC 113 Update the outputs of the PROFINET component interface
SFC 114 Update the DP interconnections
SFC 126 Synchronous updating of a process-image partition of the inputs
SFC 127 Synchronous updating of a process-image partition of the outputs

Safety:
A SINUMERIK Safety Integrated configuration is not supported by VNCK with
VPLC. However, it is possible to download a SINUMERIK Safety Integrated
configuration to VNCK with VPLC, as the system will adjust the settings in the
archives accordingly to run with VNCK and VPLC.

Run MyVNCK Restrictions

Function Manual, 05/2013 9
1 Restrictions
1.9 Restrictions due to missing operator panel

1.9 Restrictions due to missing operator panel

VNCK does not contain any software to emulate the operator panel. For this
reason, the simulation of the operator panel requires extensions in the connected
simulation system. Otherwise, the entire operator panel functionality will not be
available, including for example adjustable work offset, skipping of blocks, setting
of tool/compensation data via operator panel etc. (see also SINUMERIK 840D sl
user manual). These restrictions also apply to user software that is installed on the
operator panel, e.g. tool management packages.

1.10 Restrictions due to missing machine control panel

When running without a VPLC the following functionality is only available to a
limited degree, if simulated by the simulation system, or is not available at all:
hand wheel offset
feed with hand wheel override FD, FDA
reference point approach via MCP

When a VPLC unit is running simulation has to provide a virtual machine control
panel vMCP using the delivered API.

1.11 Further restrictions in the NC language scope

The following NC language elements cannot be used or can only be used with
restrictions or with special extensions of the simulation system:

DRFOF DRF OFF

FFWOF Feed forward OFF
FFWON Feed forward ON
FD Feed DRF
FDA Feed DRF axial
FOCON Activate drive with torque limitation
FOCOF Deactivate drive with torque limitation
G74 Reference point approach
MEAC Continuous measure without deleting distance to go
MEASA Measure with deleting distance to go
MEAWA Measure without deleting distance to go
MMC HMI Command
OS Oscillating ON/OFF
OSC Constant smoothing tool orientation
OSCILL Axis assignment for oscillation enable oscillation
OSCTRL Oscillating control options
OSE Oscillating: final position
OSNSC Oscillating: number spark out cycles
OSOF Smoothing tool orientation OFF
OSP1 Oscillating: Position 1
OSP2 Oscillating: Position 2
OSS Smoothing tool orientation at end of block
OSSE Smoothing tool orientation at start and end of block

Run MyVNCK Restrictions

10 Function Manual, 05/2013
 1 Restrictions
1.12 Restrictions concerning HMI-Advanced

OST1 Oscillating: Stop in position 1

OST2 Oscillating: Stop in position 2
PDELAY-OF Punch with delay OFF
PDELAY-ON Punch with delay ON
PON Punch ON
PONS Punch ON slow
REPOSA Repositioning linear all axes
REPOSH Repositioning semi circle
REPOSHA Repositioning semi circle all axes
REPOSL Repositioning linear
REPOSQ Repositioning quarter circle
REPOSQA Repositioning quarter circle all axes
RMB Repositioning mode start of block
RME Repositioning mode end of block
RMI Repositioning mode interrupt
RMN Repositioning mode of nearest orbital block
SON Stroke ON
SONS Stroke ON slow
SPIF1 Stroke/punch interface 1
SPIF2 Stroke/punch interface 2
SPOF Stroke/punch OFF
SPN Stroke/punch number
SPP Stroke/punch path
SR Sparking out retract path
SRA Sparking out retract external
ST Sparking out time
STA Sparking out time axial
WAITS Wait for spindle position

1.12 Restrictions concerning HMI-Advanced

VNCK does not contain any graphical user interface to interactively operate the
software. This has to be provided by the connected simulator.

The software HMI-Advanced for PC can only be used with restrictions (e.g. missing
VPLC or drives) or with special extensions in connection with VNCK. The
connection between HMI-Advanced for PC and VNCK was tested exclusive.

Note
HMI-Advanced full version must not be installed to the standard program folder
(e.g. c:\program files\...). Instead c:\HMIAdv is suggested.

To use HMI-Advanced with standard user rights in Windows 7, HMI-Advanced

must be started once explicitly requesting administrative rights.
VNCK together with HMI Base services must not be used explicitly requesting
administrative rights.

Run MyVNCK Restrictions

Function Manual, 05/2013 11
1 Restrictions
1.13 Restrictions concerning SINUMERIK Operate

1.13 Restrictions concerning SINUMERIK Operate

VNCK does not contain any graphical user interface to interactively operate the
software. This has to be provided by the connected simulator.

The software SINUMERIK Operate for PC can only be used with restrictions (e.g.
missing VPLC or drives) or with special extensions in connection with VNCK. The
connection between SINUMERIK Operate for PC and VNCK was tested exclusive.

During VNCK installation an existing installation of SINUMERIK Operate for PC will

be detected. VNCK will only install required ini file settings to the existing Operate
installation. If SINUMERIK Operate is not installed, VNCK will install Operate base
services to the PC. During this installation also a shortcut for starting
SINUMERIK Operate will be created. Double-clicking this shortcut will open only an
empty Operate Windows frame, since the full GUI version was not installed.

Parallel installation of different versions of SINUMERIK Operate will overwrite the

link to the Operate executable file in Start Programs
SINUMERIK Operate does not install a version specific link.

Note
SINUMERIK Operate full version must not be installed to the standard program
folder (e.g. c:\program files\...). Instead c:\Siemens\SINUMERIK\HMIsl\... is
suggested.

If more than one version of SINUMERIK Operate shall be used with VNCK, it is
necessary to install SINUMERIK Operate to version specific folders. The default
installation path does not contain a version specific part, thus would overwrite
existing versions.
Additionally the environment variable HMI_INSTALL_DIR must point to the
SINUMERIK Operate installation to be used with VNCK before VNCK is started.

Usage of VNCK And Operate GUI:

The usage of the GUI version of SINUMERIK Operate is restricted to the following
workflow:
Instantiate VNCK COM interface (will start SINUMERIK Operate
services)
Boot your machine
Start SINUMERIK Operate GUI version (will start SINUMERIK Operate
GUI)
Shutdown and restart your machine (optional)
Shutdown your machine
Uninstantiate VNCK COM interface (shutdown of SINUMERIK Operate
services and Operate GUI)
Any other workflow will end up in a software crash of SINUMERIK Operate.

Restrictions with Windows computer names:

In Windows 7 it is possible to give computer names containing special characters
like , , . SINUMERIK Operate or its base services wont work on computers
like that. The computer must be renamed accordingly.

Run MyVNCK Restrictions

12 Function Manual, 05/2013
 1 Restrictions
1.14 Preconditions and Known Issues

Restrictions with Operate trace options:

When having activated the Operate trace option switch off timeouts VNCK will not
boot correctly.

Restrictions concerning alarm messages:

When working with SINUMERIK Operate, alarm messages are sent to VNCK in
English independent from the language setting in the Operate GUI.

Restrictions concerning JobShop programs:

If a JobShop program is opened in HMI Operate for editing, was edited and is now
executed via VNCStart function, HMI Operate will first of all initiate a test run of the
JobShop program and request for a second NCStart event. This is displayed in the
HMI GUI as popup window. VNCK however will receive an error code
PROGRAM_START_FAILED.

Restrictions concerning length of INI filenames:

SINUMERIK Operate can only handle INI filenames with maximum 25 signs
(excluding the .INI extension).

1.14 Preconditions and Known Issues

The power scheme on laptops should be set Desktop. Otherwise the
modulation of the CPU frequency might lead to a software crash of the
NCK software.
When working with the SOPHOS product suite the Web Protection feature
must be turned off.
The Microsoft software VSCommands (part of Microsoft VisualStudio
2010) blocks HMI-Advanced services during start-up. This software must
be uninstalled to be able to work with HMI-Advanced.
When working with VPLC the error message Alarm 2001 PLC has not
start up might appear although VPLC is running. The problem can be
solved by modifying the value of ltc_sleeptime in theVNC.ini to values
bigger than 0.
A boot process might get stuck between VNCBoot and SIMBootResponse
if the BTSS connection between HMI service and NCK is lost. This
behaviour can be improved by activating the following setting in VNC.ini
[GLOBAL]
btss_ignore_state=1
The HMI Base/HMI-Advanced software component
SOPC_MachineSwitch.exe might remain as process although the VNCK
shutdown was finished. This behaviour will not block new VNCK sessions.

Run MyVNCK Restrictions

Function Manual, 05/2013 13
1 Restrictions
1.14 Preconditions and Known Issues

The JobShop feature in SINUMERIK Operate handles zero offsets as

follows. If a NC program is modified or executed in context of the real NC
machine, offset values are read from and written to the original G500ff
registers. If JobShop simulation is active those registers are ignored and
standard values are used. The JobShop cycles identify real and simulated
machine by value of $P_SIM.
For VNCK based solutions however $P_SIM is set to value 1. This
JobShop cycles are not able to differentiate between integrated simulation
and VNCK based simulation. A solution is planned for future SINUMERIK
releases.
When working with Operate GUI it is possible to manually modify NC
programs within the Operate window. If a JobShop program is modified
this way and the program execution is started via VNCStart a popup will
appear telling Program test completed. Press CYCLE START again. The
event SIMStartResponse delivers VRV_PROGRAM_START_FAILED. In
that case the popup in Operate needs to be confirmed via Softkey OK. The
VNCStart command needs to be resent.
When booting an SRAM, which contains compile cycles, with the CC
option in order to load other compile cycles from cc.dir to the SRAM, this
will fail without an according error. The compile cycles in the cc.dir folder
will be ignored.
The Logitech browser plugin Flow Scroll impacts the installation procedure
of HMIAdvanced. A error message During installation of Service Pack for
HMI-Base/Advanced error -1 occured might occur. It is recommended to
uninstall the Logitech browser plugin before installation of the VNCK
software.
The VNCBoot function will send its response as soon as the underlying
NCK system is booted. The function does not check, whether ASUP
programs or ProgEvents were executed successfully. The following picture
shows how the end of ASUP/ProgEvent activities can be determined.

Run MyVNCK Restrictions

14 Function Manual, 05/2013
 1 Restrictions
1.14 Preconditions and Known Issues

Run MyVNCK Restrictions

Function Manual, 05/2013 15
1 Restrictions
1.15 Preconditions and Known Issues for Developers

1.15 Preconditions and Known Issues for Developers

Blocked applications due to DDE communication
The Windows operating system assumes that windows are able to process
messages at any given time. For this reason, the thread to which a window belongs
must not be allowed to continuously block the Windows messaging system. This
applies in particular to top-level windows, because there are numerous situations
where messages are sent to all top-level windows currently existing in the system.
If a thread of one of these top-level windows blocks messages, then the application
triggering the messages will also be blocked. This is typically indicated when the
HMI applications no longer appear to be responding to operator actions or when
the system takes a long time to react to the activation of softkeys.

The most frequent causes of blocking windows include the following:

Blocking system calls (e.g. WaitForMultipleObjects, select, WaitForSingleObject,

SignalObjectAndWait) are used in a COM single-threaded apartment (STA).
STAs always have a window!

A call into a single-threaded apartment, which uses DDE communication, is

initiated from a COM multit-hreaded apartment.

An API function is called in a worker thread or in a thread contained in a COM

Multit-hreaded apartment. The API function creates a window - typically without
the users knowledge - and the relevant thread subsequently executes blocking
system calls (e g. WaitForMultipleObjects, WaitForSingleObject).

Since Windows messages are usually sent to all top-level windows in the system,
When a DDE connection is opened, only the DCTL control should be used to
access process variables. The DCTL control reduces the number of cases where
messages are sent to existing top-level windows upon opening a DDE connection,
and uses timeouts to prevent the continuous blocking of an application.
In order to minimize the risk of blocking an HMI application, it is recommended to
set up a hotlink to a process variable via a DCTL control when launching the
application, and to keep the hotlink as long as the application is running.

Slice settings in Link interface

Modifying slice and freeze settings for NCUs will influence the settings set for the
Link environment. E.g. activating BLOCK_CHANGED for an NCU will modify the
time slice set via Link interface, thus the Link settings should be activated after the
NCU settings.

Run MyVNCK Restrictions

16 Function Manual, 05/2013