Siemense CNC 48SP2
Siemense CNC 48SP2
SINUMERIK 840D sl
CNC Software 4.8 SP2
3 PREREQUISITES ...................................................................................................................................................................... 6
4 INSTALLATION ....................................................................................................................................................................... 7
5.5 Notes regarding the use of the Starter with SINUMERIK ......................................................................................... 16
This document serves as a guide for the software update to SINUMERIK 840D sl CNC Software 4.8 SP2.
We kindly request you to carefully read through this document, as it comprises essential information for the installation and
use of the software.
The following binding notes supersede the statements made in other documents. Additional information is provided in the
following documents:
Cycles siemensd/e_appendix_cycles.pdf
1 SOFTWARE COMPONENTS
The CNC software 4.8 SP2 (internal version 04.08.02.00.035) comprises the following components:
Component Version
SNCK V04.08.00.00.001
SINAMICS V05.10.23.00
FB15(sl) V04.08.03
PLC_F_COPY 01.05.00
CP V02.42.01
MCP_CLIENT V01.06.10
LinuxBase V04.71.29.00
Profinet FW 14.01.06.04
Cycles V04.08.02.00.986
HMIARC-Tool 04.07.02.03.001
SinIntClient 03.00.11.00.024
2 NEW FUNCTIONS
o Collision Avoidance ECO (6FC5800-0AS03-0YB0), collision monitoring with models based on primitive basic solids
o Positioning behavior at the end of the SINAMICS brake test can be set in MD36968 SAFE_BRAKETEST_CONTROL
o When using multitouch operation with SINUMERIK Operate, option SINUMERIK extended touch (6FC5800-0AP80-
0YB0) for Operate running on PCU/PC is no longer required. In conjunction with Operate running on NCU, for non-
SINUMERIK panels, option SINUMERIK Operate /universal client (6FC5800-0AS87-0YB0) is required:
The new option S87 replaces P87+P80 in applications with S00 without P88
The number of available input/output variables is now defined via the NUM_SPL_IO option data as follows:
Available on NCU710.3 X X -
Available on NCU720.3/730.3 X X X
ALL system variables are available to the SPL programmer regardless of the option settings (example: Programming of the
$A_INSE system variables is no longer limited to the 1-64 range when using the COMFORT option).
The limitation of system variables as a function of the option settings is checked using the parameterized PROFIsafe and
FSEND/FRECV connections, and triggers alarm 8049, "Option 'SPL input/output' has not been adequately set", when exceeded.
o Collision Avoidance Advanced (6FC5800-0AS04-0YB0) - the COLA compile cycle has been included in the system
o Expansion of "Calculator"
o New "Save diag. data" softkey in the area of Diagnostics, alarm list screen:
This function collects all of the log files available in the HMI, and saves them to directory /card/user/sinumerik/didac
as .7z file out_<date-time>.zip.
When HMI problems and issues occur, this zip file should be sent to the SINUMERIK hotline to simplify analysis of the
problem.
The softkey text is the same in all languages.
o A VNC viewer can be integrated as operating area in SINUMERIK Operate to access a remote PC.
3 PREREQUISITES
3.1 Software
When using SINUMERIK Operate on PCU 50 / IPC / PC, version V4.8 SP1 must be used.
3.2 Hardware
The CNC SW 4.8 SP2 may only be operated on SINUMERIK NCUs 710.3 PN / 710.3B PN, 720.3 PN / 720.3B PN and
730.3 PN / 730.3B PN.
NCU 7x0.3 modules with boot code of PLC Version V2.5 (see also Chap. “Boot code ...“)
3.4 Tools
Toolbox STEP7 classic V04.08.07.00, under Windows 10 with STEP7 Version from V5.6
For the internal use of SINUMERIK Operate on NCU, you require the option S00 SINUMERIK Operate on NCU in
combination with real drives
For the external use of SINUMERIK Operate on PCU or PC, you require the option P87/P88 SINUMERIK Operate on
PCU / PC in combination with real drives
4 INSTALLATION
The NCU Service System >= V04.70.47 on USB stick is required to install the CNC software. New installations can be performed
via the NCU service system and TCU or with WinSCP / AMM /P2P from V4.6 SP1 HFx.
An upgrade or new installation can also be carried out using the tools of the Create MyConfig Version from V4.7 SP2. To do
this, a CMC package must be generated that is stored and booted either on a PG, PC, a PCU or a USB stick at the NCU or PCU.
The relevant instructions are included in the Create MyConfig manual.
The Software Version 4.7 only starts with PLC boot code V2.5 (or later) internally coded on the NCU hardware. If this PLC boot
code has not yet been installed, the control will not start (in this case, the 7-segment display shows “PLC“ and SF and DP LED
flash red).
In this state, the boot code upgrade can be initiated by actuating the PLC rotary switch. The boot code is flashed by turning the
PLC rotary switch into position 5. This can be identified by the fact that a rotating wheel is displayed in the 7-segment display.
This takes approx. 15 s. With this procedure, under no circumstances is it permissible that the NCU is witched off! The
7-segment display goes dark after the boot code upgrade has been completed. The PLC rotary switch can now be turned back
to position 3 (general reset) and the system continues to boot.
It is best if the command specified above is executed in a DOS shell. For this, you require administrator rights on your PG/PC.
Sequence of screens for the NCU service system – Generate a separate file “Emergency Boot System.pdf”
Alternatively, the image can also be installed using the tool AccessMyMaschine /P2P as of V4.6 SP1 HFx via the menu item
"Write file system image".
Installation on the NCU:
Upon completion of installdisk, remove the USB stick from the PG / PC, boot once an NCU 7x0 from this stick (this boot process
takes a little bit longer; a "P" in the 7-segment display of the NCU indicates that the FAT partition of the USB stick is
partitioned) and reinsert the stick in the PG / PC. Under Windows, you can now see an empty USB stick. Now copy the
requested CNC software (file with extension .tgz) from the directory ncu_sw on the DVD supplied. The USB stick can be
connected to one of the two USB connectors of the NCU 7x0.3. The NCU will boot from this USB stick after power ON. The
system is operated either via a TCU that is connected to the NCU, or via PG / PC using WinSCP under "Open Terminal".
Instructions on how to use the NCU service system can be found in the documentation /IM7/ on the DVD supplied. We
recommend that you use the USB stick "SIMATIC IPC USB Flashdrive, 6ES7648-0DC60-0AA0".
The HMI-Pro sl software as of V8.0 HF1 can be used in combination with the CNC SW 4.8 SP2.
The additional languages V4.7.3 can be used. New texts from SW 4.8 SP2 may be displayed in English.
The additional language of Vietnamese for 4.7 SP3 can only be used if the new skin is NOT active.
The CBA function may only be used together with a declaration regarding machine-specific release
Collision Avoidance Advanced option 6FC5800-0AS04-0YB0 has not been generally released
As of SW 4.7 SP3 HF1, the option S17 Top Surface is generally available; the following notes must be taken into
account:
• Operation only alternatively to Advanced Surface with moldmaking applications (moldmaking involves short
blocks from CAD/CAM systems only a few millimeters long).
•
• The setting instructions for Advanced Surface and Top Surface must be complied with – see
https://support.industry.siemens.com/cs/ww/de/view/109738423
The current secondary conditions for Advanced Surface and Top Surface must be observed.
• Operation only with NCU 7x0.3B hardware, the NCU 710.3B hardware is only conditionally suited for Top Surface.
• In terms of resources, 5(6)-axis simultaneous machining should only be implemented with 720/730.3B hardware.
• Top Surface may only be configured in the first and another channel and only active in a single channel.
• Collision Avoidance (ECO) or Collision Avoidance (Advanced) can be used (active) in the AUTOMATIC mode, but
not the Collision Avoidance (Standard)
• NCU utilization: IPO/position controller and possibly PLC approx. 3 0% (visible under system utilization
diagnostics)
• Operation only with 3D-TRC differential tools other than CUT3DFD or CUT3DCD
With Top Surface, the tolerance value from CYCLE832 is used for the contour – in contrast to Advanced Surface,
where the tolerance value is used for the axis tolerance. When comparing Advanced Surface with Top Surface, this
yields a difference of SQRT(3) between the active contour tolerance and possibly surface and speed respectively
machining time differences.
With Top Surface, an enhanced jerk consideration is performed, compared to Advanced Surface.
If the data throughput of data-intensive part programs leads to a reduction of the IPO buffer filling level, the FIFOCTRL
function reduces the path velocity in order to prevent stopping of the system.
o The Collision Avoidance ECO function is generally available, taking into account the following information:
- Operation for 840D sl only with NCU720.3B or 730.3B hardware
- Collision Avoidance ECO may only be used in single-channel systems
- Machine modeling is only permitted using primitive basic solids (cubes, cylinders, spheres)
- A maximum of 34 primitives, 17 protection zones and 10 collision pairs is permitted
The recommended settings can be downloaded from Siemens Industry Online Support (SIOS).
o The function "Configuring static and dynamic transformations via kinematic chains" was completed with CNC SW 4.8
SP2.
The launch should first be accompanied by the Siemens Technology and Application Center (TAC) (Mr. Claudio Jans,
claudio. jans@siemens.com).
o When upgrading the system from V4.5 SPx and having licensed all options, the options P87 and P88 (Operate on PC
respectively PCU 50) may have to be licensed subsequently following the upgrade.
o If an upgrade is made from SW 4.7 within an active test license period (trial license), then the actual remaining time is
shortened to 1/10. The next period then has the normal length.
DDS0, and not the DDS currently selected via PLC/NC, is always pre-selected under "Active filter optimization". The
DDS must be explicitly selected via "Filter group".
AST filter settings: Changes are discarded when switching to another axis, for example. This also applies to filter
groups and DDS settings.
Commissioning wizard: Drive wizard does not function for axes on CU320-PN with plugged TB30 modules.
o SinuComARC
Series commissioning archives can no longer be edited with SinuComArc.
Alternatively, you can use Create MyConfig (for example, also CMC Diff) respectively AMM /P2P as of V4.7 SP2; does
not claim to be a successful competitor.
If a USB stick on a TCU is accessed by several HMIs / NCUs in parallel, the components are not coordinated. This
entails the danger that a program being processed is modified / destroyed by another component.
[FetchWrite]
# Selection of the S5 fetch/write implementation
# Version = 1 : the previous behavior
# Version = 2 : the new as far as possible CP 343 compatible behavior
Version = 1
The problem solution becomes active when recopying this file (possible as manufact) into the directory
/user/sinumerik/cp and modifying the entry "Version = 1" in "Version = 2".
o Safety: When traversing at low speeds, alarm 27011 is triggered during traversing movements in the negative
direction.
The following supplementary conditions must be considered a remedy for the described behavior:
The minimum possible resolution (quantization) of the monitoring functions for Safety Integrated is one increment
per monitoring cycle [incr/mcc].
Two increments per monitoring cycle are necessary, so that no speed violation alarm is triggered when the axis is
stationary.
The minimum speed limit value that can be set for the machine data $MA_SAFE_VELO_LIMIT can be determined as
follows:
For a rotary axis:
$MA_SAFE_VELO_LIMIT[rpm] = 2[incr/mcc] * 60[s/min] / 360[deg/rev] / 1000[incr/deg] / MCC[s/mcc]
o Adjustment of the default machine data in the area "Saving of persistent data".
With the values set, the number of write processes onto the CF card has been reduced.
a) Change of the memory default values for saving persistent data on the system CF card
Old New
N17610 $MN_DEPTH_OF_LOGFILE_OPT_PF[0]= 10 100
N17610 $MN_DEPTH_OF_LOGFILE_OPT_PF[1]= 0 10
N17610 $MN_DEPTH_OF_LOGFILE_OPT_PF[2]= 0 30
b) In order to keep the preprocess running during the Flush process, the system has been set to asynchronous flush
by default.
N18234 $MN_MM_MEMORY_CONFIG_MASK= 1
Note:
After loading the archive, the new default values remain only topical if the “old“ default values are not changed and
an archive has been created with
MD11210=FF
MD11212=1.
o When activating TRAILON using a synchronized action with active transformation (TRAORI), an incorrect coupling may
occur if a RESET is triggered with active coupling. In case of a RESET, the transformation is deactivated for an IPO
cycle. As a result, a setpoint is specified in the MCS instead of BCS. Thus, the coupling is made for the machine axis
instead of the geometry axis, which leads to a position jump. TRAILON interpolates this jump and generates a
movement to an incorrect coupling position (MCS), which leads to large and quick axis movements.
Solution:
The user must ensure that the transformation is active with activated TRAILON and the triggering / setting of RESET is
suppressed in the PLC.
o The function G643 (block-internal approximate positioning) has been released for tool change applications (e.g.
optimizations when approaching the tool change position). It has not been released for machining applications.
o The function G644 (approximate positioning with maximally possible dynamics) has been released for tool change
applications (e.g. optimizations when approaching the tool change position). It has not been released for machining
applications.
o If different arithmetic resolutions have been set for rotary and linear axes using $MN_INT_INCR_PER_MM and
$MN_INT_INCR_PER_DEG, this must also be taken into account in the new machine data 31092
$MA_JOG_INCR_WEIGHT_TRAFO. This applies if the machine axes assigned to the geometry axes are rotary axes.
Alternatively, you can make a manual entry in the file /user/system/etc/basesys.ini (such as the ports 102 and 5900
are activated).
o The MD13200 MEAS_PROBE_LOW_ACTIVE now also works for simulated probes that are configured via MD13230
MEAS_PROBE_SOURCE > 0. The level states of such simulated probes are displayed just like they are for real probes as
a function of MD13200 in DB10.DBB107, and are therefore checked with regard to the permissible deflection state
before the measuring process begins. Depending on the deflection state, alarm 21700 may be triggered during this
check. To avoid alarm 21700 being triggered, either the setting in MD13200 must be taken into account when
specifying the simulated level states via digital outputs or the MD13200 must be adjusted to the required level states.
o Now, the passwords for NCK and the corresponding Linux accounts of the NCU basis system are changed using the
Operate dialog "Change password".
o Tool manager
- "Monifact" function:
Monifact has been taken out of the TOA context, and can be completely handled on a channel-for-channel basis.
The active Monifact value can be read in the channel-specific status data (block C/S) "aMonifact".
Now, the tool lifetimes are not converted at the OPI (block T/TS).
This means, that in Operate the tool lifetimes are no longer evaluated with MONIFACT – i.e. they are shown in
realtime.
If the real remaining lifetime of a tool is to be specified, taking into account $A_MONIFACT, then the application
must link the remaining lifetime ($TC_MOP2) with $A_MONIFACT
The tool lifetime monitoring is evaluated, unchanged using the Monifact value (i.e. part programs are or remain
fully compatible).
Supported functions:
Creating a hardware configuration
Support of software versions 4.5, 4.7, 4.8
Basic PLC program libraries for software versions 4.5, 4.7, 4.8
Configuring the drive telegrams (telegram configuration)
Migrating STEP7 Classic projects from STEP7 5.4 SP5
Support of ‘SINUMERIK Safety Integrated (SPL)’ and ‘SINUMERIK Safety Integrated plus ‘
Exporting PLC symbols for SINUMERIK Operate
Generating SINUMERIK PLC archives
Note:
It is not permissible that projects, which were created for SW 4.7 and for which "SINUMERIK Safety Integrated plus" is
activated, are loaded to an NCU 7x0.3. These projects must first be upgraded to SW 4.8 using the "Replace device" function.
In conjunction with toolbox V04.08.07, with Windows 7 , we recommend the use of STEP7 from V5.5 SP4 HF7
. Under Windows 10, STEP7 from V5.6 should be used.
If no new functions from Software 4.8 SP2 are used, you need not upgrade the PLC user program to the basic program
version 4.8. PLC basic user programs Version 4.5 (or later) are functional. PLC user programs with basic PLC program
from Version 4.5 can function.
When configuring HLA hardware, you may only change the telegrams as of slot (object) 1 from 136 to 166.
With an isochronous alarm of the NCU, select the setting for the Ti/To mode as “fixed“ rather than “in IO device“.
Upgrading the system software version 4.8 SP2 using the existing PLC user program causes a problem to arise with the
Toolbox >= V04.07.21 at the call interface of the FB1 in the OB100.
Inserting the new parameter “MCP_IF_TCS“ results in a change to the call interface of the FB1. This causes the user to
receive an error message from STEP 7 after inserting the blocks from the Toolbox >= V04.07.21.
This error message only occurs if the OB100 is opened.
The block call FB1 “RUN_UP“ has to be updated once and then the call parameters are displayed without any time
stamp conflict.
Mark block,
Menu Edit > Call > Update
Starter version V4.5 SP1 HF5 must be used with SSP SINUMERIK (int. Vers. 05.10.10.00 / Release V05.10.18.00_02.50.09.00).
Note: Standard drive commissioning and also the commissioning of SINUMERIK Safety Integrated plus must be performed via
SINUMERIK Operate or SINUMERIK Commissioning, and are not supported by Starter.
Offline commissioning using Starter is likewise not supported.
• Access using the VNC Viewer for Operate or Linux via the company network X130 is password-protected from SW 4.8
SP2.
A password with max. 8 characters can be set using service commands at the Linux level:
sc vncpwd set companynetwork <my_pass>
sc vncpwd reset companynetwork
Password protection can also be disabled in file user\system\etc\sinumerikvnc.ini using entry
VNC operation in the plant/system network X120 can also be protected with a password that deviates from the
"password" standard value. However, this is only possible with panels with TCU30.3; however, not for mixed
operation with TCU20.2 or HT8. The password can be entered at the TCU30.3 using the TCU menu, and is saved on the
TCU. The old password must be entered in order to be able to change the password. This is important if the TCU30.3
is to be used in a different plant/system with different password.
At the present time it is not possible to reset the password. You must return the TCU if you have forgotten the
password.
Interface X127 responds just like the X120 interface, and in the basic setting, does not request that a password is
entered.
When using SIMATIC ITC panels, no touch softkey is available for the help function.
The mold and die view cannot be used with POLY and G91 blocks.
The mold and die view cannot be used with BSPLINE blocks.
Only the elements 0 to max. 65534 can be displayed respectively changed in GUD arrays, even if the array is greater in
the NC.
When executing part programs from network drives or editing files on network drives, the user must provide for a
stable, interference-free network connection to the network drives.
OPC-UA:
There are two possibilities to set up a connection:
• Connection without security
• Connection with the security policy "Basic128Rsa15" respectively “Basic256“ and the security mode
"SignAndEncrypt"
Siemens recommends that you always establish a connection with security, as only in this way the confidentiality of
the data transferred can be ensured.
Archiving/series commissioning:
Whether files with logon data should be backed up in an archive can be set via the new display machine data 9115
$MM_SAVE_CREDENTIALS.
$MM_SAVE_CREDENTIALS
0 = Dialog is displayed (default)
1 = No dialog, logon data is not backed up
2 = No dialog, logon data is always backed up
From SW 4.8 SP2, a VNC Viewer can be integrated as operating area in SINUMERIK Operate for access to a remote PC.
The VNC Area configuration dialog can be found under
Startup area / HMI /Operating area menu (VSK 5)
You can move through all of the operating area softkey bars using softkey "Level>>". In every displayed bar, the first
available operating area softkey is automatically selected.
Using the "Change" softkey, you can change the parameter of an empty or a VNC operating area softkey. The
following parameters can be configured:
VNC connection
- Type: Only "VNC" (or <leer> for delete) possible.
- Computer name: IP address or DNS name of the host, on which the associated server runs.
- Port: TCP port that the server uses.
- Password (optional): Password for the appropriately protected access to the VNC server.
- Operate Header: Defines whether the Operate header should be visible while the VNC area is selected and is in
the foreground.
- Position of the status display: Position of the display of the connection status of the VNC area.
Note: As standard, function keys F1 to F12 are not transferred to the remote PC.
CNC SW 4.8 SP2 contains the following cycle packages on the CF card:
Measuring cycles
ISO cycles
ShopMill cycles
ShopTurn cycles
Grinding cycles
AST cycles
Adapting Cycles
All these Siemens cycles are automatically loaded into the NC during the run-up of the NCU. The corresponding variables are
stored in the definition file PGUD.
Note:
The “programGUIDE“ in SINUMERIK Operate is based on the cycle packages of CNC SW 4.8 SP1.
Cycle calls in part programs for these cycles cannot be recompiled or processed with the cycle support in HMI-Advanced 7.x.