Ncu Hmi SL 25 sp2 76

s SINUMERIK 840D sl 2009-10-13
NCU System Software 2.5 SP2

____________________________________________________________________________________
SINUMERIK 840D sl, NCU system software for 6 axes ) 6FC5850-1XG20-8YA0
with HMI sl, in 6 languages, on CF card; with license ) Export 6FC5850-1YG20-8YA0
SINUMERIK 840D sl, NCU system software for 31 axes ) 6FC5850-3XG20-8YA0

with HMI sl, in 6 languages, on CF card; with license ) Export 6FC5850-3YG20-8YA0
SINUMERIK 840D sl, NCU System Software for 6/31 axes ) 6FC5850-3XC20-8YA8
with HMI sl, in 6 languages, on DVD; without license ) Export 6FC5850-3YC20-8YA8
____________________________________________________________________________________
Information about installing and operating the software on SINUMERIK NCU 710.2, NCU 720.2, NCU 720.2
PN, NCU 730.2 and NCU 730.2 PN.
The NCU system software 2.5 SP2 consists of the following components:
o NCK software V72.07.01
o SNCK V02.01.00.00.005
o PLC-OpSys V20.70.40 (PLC 317)
o PLC-OpSys V26.90.13 (PLC 319)
o PLC-FB15 V01.05.08
o CP V01.32.09
o MCP Client V01.04.31
o SINAMICS Software V02.50.53.00
o HMI-sl V02.05.00.04.001
o LinuxBase V02.50.32.00
o SNC V01.01.00.00.010
o Technology Cycles V02.05.04
o Measuring Cycles V02.05.05
o Cycles ISO Compatibility V02.05.05
o MachineDataForCycles V02.05.04
o Adapting Cycles V07.01.09
1. Installation of the NCU software:

To install the NCU software, you need the NCU service system V02.50.21 or higher on a USB stick.
The new installation can only be carried out with the NCU service system and TCU with full keyboard resp.
WinSCP. Installations without keyboard or WinSCP can only be performed with an USB stick that has been
prepared for automatic upgrade (see 1.5).
The software may only be installed on a 1GB SanDisk CompactFlash 5000. MLFB / order no. for the empty card:
6FC5313-5AG00-0AA0.
1.1 Installation of the NCU service system on USB stick:

The NCU service system is stored as a USB stick image in directory emergency_bootsys_ncu on the supplied
DVD. The copy routine installdisk.exe is stored in the same location. Connect a USB stick 512MB or 1GB,
recommended type Siemens 6ES7648-0DCx0-0AA0, to your programming device or PC (with Windows XP) and
note down the letter of the drive to which the stick is connected. Run routine installdisk to copy the NCU service
system to the USB stick:
installdisk --verbose --blocksize 1m <Image file> <Drive letter:>
Example:
( -- means 2x minus sign)
installdisk --verbose --blocksize 1m D:\ emergency_bootsys_ncu\linuxbase-512M.img X:
The capacity of each USB stick is thus limited to 512MB.
Alternatively:
installdisk --verbose --blocksize 1m D:\ emergency_bootsys_ncu\linuxbase-resize.img X:
When using the resize.img, boot the NCU from this USB stick after the installation to unpack the image onto the
© Siemens AG, 2009 I DT MC R&D 51 Page 1 of 29
All rights reserved
SINUMERIK 840D sl 2009-10-13
NCU System Software with HMI sl 2.5 SP2
stick and generate the FAT partition. The USB stick can thus be fully utilized.
It is best to copy the image in a DOS shell.

For this, you require administrator rights on your PG / PC.
After completion of installdisk remove the USB stick from the PG / PC and insert it again. Under Windows you
can now see an empty USB stick. Now copy the desired NCU software (file with extension .tgz) from directory
ncu_sw on the delivered DVD to this USB stick.
The USB stick can be connected to one of the two USB connectors of the NCU 7x0. The NCU will boot from this
USB stick after power ON. The system operates either via a TCU that is connected to the NCU, or via PG / PC
through WinSCP under "Open Terminal".
Instructions on how to use the NCU service system can be found in documentation /IM7/ on the DVD supplied.
1.2 Upgrading NCU 7x0.2 with NCU-SW 2.4 SP1

Prerequisite: 1GB CF card ! Upgrading of SW 1.x is not permissible; here, a new installation is required! Where
relevant, Section 9.5, Upgrading the cycles must be observed.
The upgrade retains all user data on the CF card in the directories /user, /addon, /oem and the license key.
When upgrading systems with a number of NCUs / PCU 50s, please refer to section 7 Networking.
o Boot the NCU from the USB stick (see 1.1).
o Select the service shell by pressing F3.
o Log on as user "manufact". An external keyboard may be required for this, as user names must be
written in lowercase letters.
o Enter the following command after the operator prompt $ of the service shell:
sc restore -update /data/<ncu-sw>.tgz
The software update has finished when the prompt $ reappears.
o Remove the USB stick.
o Boot the NCU (Power OFF / ON).
o You can now start the PLC, drives and NC.
1.3 New installation

IMPORTANT: This procedure completely deletes anything existing on the CF card; this applies for an empty CF
card as well.
o Boot the NCU from the USB stick (see 1.1).
o Select the service shell by pressing F3.
o Log on as "manufact" user; if the CF card is empty use "admin", password "SUNRISE" instead. An
external keyboard may be required for this, as user names must be written in lowercase letters.
o Enter the following command after the operator prompt $ of the service shell:
sc restore -full /data/<ncu-sw>.tgz
Software installation will be completed when prompt $ is displayed again.
o Remove the USB stick.
o Boot the NCU (Power OFF / ON).
o When the system is started with TCU(s) for the first time, the TCU(s) must be logged on to the system.
Enter the TCU name (default TCUx) and the address of an assigned MCP.
o You can now start the PLC, drives and NC.
1.4 Systems without TCU

If no OP with TCU (for operating the NCU service system) is available for software installation according to 1.2
or 1.3, operation is also possible from PCU50 or PC/PG using WinSCP (Commands / Open Terminal) or VNC
Viewer.
It may not be possible to install the Card without NCU service-system on USB stick due to insufficient memory
capacity on the CF card.
1.5 Automatic upgrade using a bootable USB stick:

All rights reserved
Automatic “update -restore“ or “update -full“ can be performed using an accordingly prepared USB stick >= 1GB.
For this, copy a script (autoexec.sh) and the NCU software onto the stick. The script name must not be changed.
The NCU software copied onto the stick must be renamed into update.tgz or full.tgz. Then, set the rotary switch
SIM/NCK on the NCU to position 7 and boot the NCU from the stick. The script can only be executed when the
switch is in position 7. Otherwise, the system is booted from the stick and branched into the service menu. On
the basis of the NCU software designation, the script decides whether to perform “restore -update“ or “restore -
full“. In addition, the script performs a data backup of the CF card before restoring. The progress of the individual
script steps can be monitored at the 7-segment display resp. the internal HMI. The exact meaning of the displays
and individual steps is described in a separate document. The script is stored on the delivery DVD.
2. New functions in NCK 72.00.00 (or later)
o In machine data $MN_ASUP_EDITABLE, the machine manufacturer can set whether the Siemens
system ASUP from _N_CST_DIR or a user ASUP from _N_CUS_DIR (_N_CMA_DIR) shall be executed
for RET or REPOS events.
o ET200S-F I/Os are supported for Safety Integrated.
o GETFREELOC can be called up several times during empty location search in the tool management.
o The machine data $MA_JOG_AND_POS_MAX_JERK[axis] is now active with NEWCONF.
o The couplings TRAIL, LEAD and ELG are implemented for (BCS) and (MCS).
o Fixed-point approach in JOG: Max. four fixed points can be defined via the machine data
$MA_FIX_POINT_POS[]. The number of valid fixed points is determined via the machine data 30610
$MA_NUM_FIX_POINT_POS.
Approach procedure:
- Select JOG mode
- Activate via PLC interface (see 4.3)
- Traverse axis using axis key (continuous resp. incremental) or handwheel until it stops automatically.
The axis stops at the defined fixed point without emitting an alarm message.
o The number of possible parameterizable transformations has been extended from 10 to 20.
o Generic transformation has been extended to include a 7th axis.
o The nesting depth of subprograms and control structures has been increased from 8 to 16.
o The current axial setpoint and actual braking path can be read using system variables.
Basic coordinate system:
$AA_DTBREB[AX] Total braking path
$AA_DTBREB_CMD[AX] Path – single interpolator
$AA_DTBREB_CORR[AX] Overlaid movements
$AA_DTBREB_DEP[AX] Coupled axis
Machine coordinate system:
$AA_DTBREM[AX]
$AA_DTBREM_CMD[AX]
$AA_DTBREM_CORR[AX]
$AA_DTBREM_DEP[AX]
o The number of safe cams (SN) has been increased to 30 with solution line.
o Empty location search within turret magazines can be performed using the same setting options as for
chain magazines.
o The program attribute ACTBLOCNO is used to output the block number from the current block
containing the alarm upon alarm output with active DISPLOF.
o Machine data $mc_ign_prog_state_asup defines whether the display of the ASUP name shall be
suppressed. The ASUP is performed “silently“.
o The function Any–Asup–Active sets the new channel-specific VDI signal “anyAsupActive“
in DB.[channel].DBX378.0.
The new channel-specific VDI signal “silentAsupActive“ is set in DB.[channel].DBX378 if an ASUP is
performed silently.
o Interruptability of ASUPs:
Certain Prog-Events shall not be prevented or stopped by VDI signal NC Stop DB[channel].DBX 7.3).
This ensures that the Prog-Event is executed completely independently of the VDI signal.
All rights reserved
The VDI signals NC Stop at the block end DB[channel].DBX 7.2, NC Stop “Axes plus spindle”
DB[channel].DBX 7.4 are discarded accordingly.
The function is activated by the bit-coded machine data $MC_PROG_EVENT_IGN_STOP for any
Prog-Events.
o The subprogram return RET(...) allows you to return to a block number or label of the calling program.
This function has been extended such that you can also specify any string as return target.
o Time monitoring on synchronous spindles:
When reaching setpoint-side synchronization, two time windows are initialized which are used to monitor
the time span until actual value-side coarse resp. fine synchronization is reached.
The size of the time windows is taken from MD 37240 $MA_COUP_SYNC_DELAY_TIME[0/1].
Index 0 for fine synchronization and Index 1 for coarse synchronization. The value of zero deactivates
the respective monitoring mode. If actual value-side coarse/fine synchronization is not reached before
the relevant time window has expired, Alarm 22018 is output.
3. General information:
o After new installation of NCU software 2.5 on CF card, a general reset of the NCU and PLC must be
performed: Change the SIM / NCK switch into position 1, the PLC switch into position 3 and perform a
power OFF/ON.
o NCU 710 / NCU 720: The PLC program must initiate an immediate (approx. 20 sec.) reaction to alarm
"2120 NCK fan alarm" by stopping the axes in a controlled manner.
o NCU 730: The PLC program must initiate an immediate (approx. 20 sec.) reaction to alarm "2120 NCK
fan alarm" by stopping the axes in a controlled manner, if NO double fan module is used.
o NCU 710 / NCU 720: The NCU will not power up if a fan module is not installed or if the fan is defective.
This applies for NCU 730 with double fan module only in the case of failure of both fans.
o Alarm 15122 "%1 data have been restored, of which %2 machine data, %3 error"
If %3 indicates that more than zero errors have occurred, it is not advisable to continue working with the
data. To avoid further problems, you should read in an up-to-date backup copy of the data.
o It is not always possible to port an NCK series startup file from 840D powerline without processing to
840D sl.
o Prior to overwriting a licensed CF card, a backup of the license key is absolutely necessary. The key is
available in file ‘keys.txt’ and is stored under the path card/keys/sinumerik
The backup of the key can be carried out, for example, with WinSCP, by the PG / PC.
o Each license is assigned to a specific CF card (card ID) and is valid only on the assigned card.
o Mini handheld unit
An additional hardware is now required to operate a mini handheld with handwheel. As previously the
inputs are connected directly to the PLC I/Os or can alternatively be integrated into the input image of
the MCP IE (X51…) using a relevant connection kit. For transmitting the handwheel signals a machine
control panel (Ethernet or PROFIBUS) or a handwheel connection module is now required.
o Data backups should be read in in the order NC, PLC, drive. It will therefore make sense to create the
archives NC, PLC and drive separately.
o Contour handwheel and speed override with handwheel has only been released with Profibus MCP.
o The reset button on the NCU enables the NCU module to be restarted. It is not certain that this will
restart the complete system in all configurations. This also applies for the PI service of PLC with FB4.
o The catalog /siemens/system/etc. contains a template for the current standard basesys.ini.
o By default, Port 102 on X130 is blocked. If you wish to access the controller via X130 using STEP 7 or
HMI, you have to activate Port 102.
This can be achieved using the following entry in the file /user/system/etc/basesys.ini:
[LinuxBase]
FirewallOpenPorts=TCP/102
If required, you can also activate the Port 5900 for the VNC Viewer.
o The Ethernet handwheel of the HT2 is jumpered on the fifth handwheel interface.
Example of three Ethernet handwheels. The third handwheel is in the HT2:
MD11350[0]=7 11351[0]=1 11352[0]=1
MD11350[1]=7 11351[1]=1 11352[1]=2
MD11350[2]=7 11351[2]=1 11352[2]=5
All rights reserved
HT2: The PLC application example for the HHU (=BHG) contained in the Powerline toolbox cannot be
transferred to the HT2 without modifications. The variable descriptions of the NCVAR have to be
adapted accordingly. A revised example is provided through e_Support or Toolbox
The FC13 supports the visualization of four lines. As a result, the meaning of the "ROW" parameter has
changed as follows:
0 = No display output
1 = 1st line
2 = 2nd line
3 = Line 1 and line 2 alternately
4 = 3rd line
5 = Line 1 and line 3 alternately
8 = 4th line
F = Automatic change of all lines
The display contents must be stored in the field “ChrArray“type string[64].

The upper four keys are transferred to the PLC input image
(the LEDs under these keys cannot yet be addressed).
Sample parameter setting for the HT2 at FB1 (OB100):
BHG :=5
BHGIn :=DB100.BhgIn_170
BHGOut :=DB100.BhgOut_150
BHGStatSend :=DB100.DBD80
BHGStatRec :=DB100.DBD84
BHGInLen :=
BHGOutLen :=
BHGTimeout :=
BHGCycl :=
BHGRecGDNo :=2 // corresponds to the setting of the rotary switch * the connection box of the MPP.
BHGRecGBZNo :=2 // corresponds to the setting of the rotary switch * the connection box of the MPP.
BHGRecObjNo :=1
BHGSendGDNo :=2
BHGSendGBZNo :=1
BHGSendObjNo :=1
BHGMPI
BHGStop
BHGNotSend
* The rotary switches S1 and S2 determine the DIP number with which the station is logged onto the
system (here S1=0, S2=2). Address “0” is not permissible, as, with this setting, the DHCP Server cannot
assign any addresses.
o HT2: The update rate of the display and the transfer of the handwheel signals (this improves the velocity
control of the handwheel) can be improved as follows:
Copy the mcp_client file in the directory card\siemens\sinumerik\mcp_client\mcp_client.ini into the
card\users\sinumerik\mcp_client directory and in the HT2 section, change the entry cycleMCPSend =
50. The control must then be powered down/powered up.
o Alarm 46xx: The machine data for the Ethernet handwheel must be checked.
Example for the first handwheel: MD11350[0]=7, 11351[0]=1, 11352[0]=1
o Combinations of NCUs with SINAMICS Sxxx CUs have not been released. Exceptions are only
permissible after prior consultation.
o Spindle traversing with limited torque (Focon) or spindle traversing to fixed stop:
The performance display at the HMI is calculated as 100% of the limited torque and displayed.
o With NCK V67.05.03 or later and ADI4 board V01.04.04, the ADI4 board can be operated on 840D sl
with internal PLC 317.
o As before, Dbsi 1 is not released for SINUMERIK and integrated drive control.
o NCU Bios V1.4 (or later) is required to operate 1GB CompactFlash Cards in a NCU730.
All rights reserved
The system need only be upgraded infrequently so that the BIOS is only provided through e_support.
o Just as before, in conjunction with 840 D sl, the Starter is only enabled for diagnostic purposes.
4. Information about the NCK:

o If the number of part programs set via machine data nearly matches the currently available number, the
value must be increased in the machine data (due to additional cycles).
o Interpolatory movement of positioning axis is prevented with the alarm 8031 "...Axis has no IPO
functionality."
o SPI and PW have (always) been key words and cannot be used as axis identifiers.
o Function G643 (block-internal smoothing) has been released for applications in the tool change area
(e.g. optimizations for approaching the tool change position). The function has not been released for
applications in the machining process.
o Function G644 (smoothing at max. possible dynamics) has been released for applications in the tool
change area (e.g. optimizations for approaching the tool change position). The function has not been
released for applications in the machining process.
o Software variant 6 axes max.: The default setting for the number of axes is 3.
o The "Extended measurement" function with distributed measuring input on the SINAMICS modules is
not available (MEAC, MEASA, MEAWA).
o Gaps in the channel sequence are not permitted in systems with a maximum of two channels.
o Access to drive data via system variable $nn_nn is not enabled. The only available system variables are
those transferred in telegram 116.
o ESR is not enabled.
o ASUBs can now be started along the line of the 840Di functionality via the Profibus PLC I/Os. Machine
data settings must be selected by the same method used on the 840Di system. There are no high-speed
NCK I/Os mapped in DB10 of the PLC. However, the ASUB start options used in earlier versions (i.e.
from DB10 or FC9 via PLC program) are still available.
o High-speed ET200 Simatic modules can be used as a replacement for the DMP modules used on
Powerline. For this, you can operate one of the two Profibus lines in synchronism with the clock with
PLC317 in combination with NCK V 67.07.05 or later (more details are provided in a separate
description).
o With a 31-axis software on an NCU 710.1 you can use 6 out of 31 axes and 4 out of 10 channels.
o Machine data 10008 $MN_MAXNUM_PLC_CTRL_AXES is no longer included in the data record. It has
been replaced by MD19160.
o MD 10062 $mn_posctrl_cycle_delay must be zero. Check the available data backup.
o Machine data 32250 $ma_rated_outval[ ] must have value zero.
o IMD (integrated monitoring & diagnostics):
Feedback in GUD variable _PM_MISSING_TOOL_REFRESH after writing the variables to "1" is
updated only after image change.
o Safety: There is a new option handling referring to synchronized actions or synchronized action
elements. Up to version 1.3 (NCK 62) synchronized action level 2 was set automatically at the same
time with option SI. Thus, channel MD 28250, NUM_SYNC_ELEMENTS could be set to a value > 159.
This has been changed with NCK version 67. Synchronized action level 2 is no longer included in
Safety. Instead there is a new machine data, in which the synchronized action elements for SAFE.SPF
are defined, i.e. MD 28251, NUM_SAFE_SYNC_ELEMENTS.
This machine data can be written with a max. value of 500 for option SLP_I_O=1, and with a max. value
of 5000 for option SPL_I_O=2.
However, the number of synchronized action elements required should be determined in order to
prevent the performance from being loaded unnecessarily.
With system variable $AC_SAFE_SYNAC_MEM the relevant number of free SI synchronized action
elements can be read.
If this variable is called prior to starting and after running SAFE.SPF, the difference is the number of
elements occupied by SAFE.SPF. This difference adding a certain reserve should be entered in MD
28251. Index 1-5 must be indicated when writing MD 35300 via synchronized actions.
o Safety: Changed check sums of Safety integrated in the drive.

All rights reserved
The check sum for these functions must be confirmed again due to new drive-integrated safety
functions.
In order to do this enter “95” (safety start-up) in parameter p10.
Afterwards the parameters of the current check sum must be copied to the parameters of the planned
check sum.
p9798 to p9799
p9898 to p9899
Then reset p10 to zero. This will automatically save the values (p971=1 is set). Wait for the process of
saving to be completed.
The processes mentioned above can also be triggered in HMI Advanced under IBN/NC/Safety
Integrated using the softkeys "Activate start-up mode" and "Deactivate start-up mode".
o With Software Version 1.5 HF2 / 2.4 SP1 or later, the HT2 can be used as handheld unit.
o The auxiliary function M6 is no longer output as standard after block search.
Remedy:
Change the auxiliary function group in MD 22040 $mc_auxfu_predef_group[5] into an unassigned group.
o If the value of MD18210 deviates from the default, MD18210 must be increased by min. 21 MB DRAM to
upgrade the system from SW1.4 / 2.4 to SW1.5 / 2.5.
o SinuComNC is not released for 840D sl, Software Version 1.5 HF 4 and NCU sl 2.5 HF 1. This does no
longer apply for 1.5 HF5 resp. 2.5 HF2.
o From software release 1.5 HF5 / 2.4 SP1 and higher, the HT2 can be used as handheld operator unit.
Depending on the setting in basesys.ini, the HT2 is booted from the master (refer to the general
information and instructions for networked systems). The master can either be an NCU or a PCU 50.
o Tool Manager: There is a new handling option. If several real magazines are used, these must be
enabled using the option. One real magazine is included in the basic scope.
For compatibility reasons, the previous option bit $ON_TECHNO_FUNCTION_MASK Bit4=1 must still
remain set. This is, however, not included in the license handling.
o The function “parking axis“ with SMI encoder can only be used with voltage ON/OFF.
o The function “fixed point approach G75“ with active radius compensation G41 / G42 Is not permissible
(alarm 14091 index 9) .
o When performing fixed point approach with G75, the fixed point is now approached with non-linear
interpolation (RTLIOF). As a consequence of this, the axes are traversed with the jerk set for positioning
axes ($MA_JOG_AND_POS_MAX_JERK).
o The machine data 11295[0..9] is now memory configuring. Alarms are no longer output when making
changes. Values deviating from the standard have to be removed in the existing archives prior to the
upgrade.
o If you wish to use the service interface X127 with PG/PC on an NCU7x0.2 with SW 2.6, you have to
ensure that the PG/PC network interface is operated in the "DHCP Client" mode, that means
"Automatically obtain IP address".
After setting the PG/PC network interface to a fixed IP (192.168.215.xx), a ping is sent to X127, but you
cannot go online with Step7 or SINUMERIK Operate. The firewall is activated via default setting.
o The maximum drive system load of CU or NX may not exceed 80% (the load is displayed in parameter
9976[xx]).
o In the “Reset“ status, the NCU load applied by position controller and interpolator should not exceed
50%. The current load can be checked under Diagnosis / System resources.
o Functional Improvements and Further Developments:
AP00582494 AP00650310 AP00664996 AP00711788 AP00307709 AP00307996

AP00511554 AP00554755 AP00570837 AP00573624 AP00582494 AP00588238
AP00603032 AP00623018 AP00629494 AP00632328 AP00646390 AP00649532
AP00650310 AP00650954 AP00664996 AP00666152 AP00679387 AP00683095
AP00686559 AP00691529 AP00692100 AP00696800 AP00700736 AP00701094
AP00711788
RQ id AP00307663 AP00307762 AP00307970 AP00307986

All rights reserved
AP00308014 AP00308044 AP00381742 AP00438261 AP00473047

AP00509447 AP00523979 AP00613449 AP00626178 AP00652655
AP00654074 AP00666267 AP00692100 AP00707258 AP00707457
AP00712550 AP00716107 AP00719121 AP00723124 AP00734128
AP00734454 AP00735285 AP00735963 AP00737273 AP00740569
AP00749131 AP00750610 AP00751483 AP00759049 AP00761660
AP00767248 AP00781549 AP00781774 AP00786858 AP00791396
AP00804262 AP00813437 AP00820426 AP00823202 AP00827957
AP00828475 AP00843898 AP00846197
5. Information about the PLC:
o Tool box V01.05.01 and STEP7 V5.4 SP2 are required.

o The retentive memory of PLC 319 is limited to 256kB.
o Deleting PLC 319:
After deleting the PLC using the operator sequence at the PLC rotary switch or from Step 7, the PLC
program is automatically reloaded.
If PLC initialization (booting) is initiated via an operator action by setting the PLC switch into position 3
followed by power off/on, the PLC program is not automatically loaded. This is then also no longer
realized with the above-mentioned operator sequence.
o The current cycle time is no longer available in DB5, but in DB8 instead. The cycle time can also be
called via the start information of OB1.
o The PLC module IM153-2 MLFB 6ES7 153-2AA02-0XB0 cannot be used.
Remedy: 6ES7 153-1AA03-0XB0
o The PLC series startup file must be generated when the PLC is stopped.
It cannot otherwise be guaranteed that the PLC will switch to cyclic operation when the data backup has
been loaded.
o Sinamics parameters are required for start / delta switchover with FC17.
Prerequisites:
The relevant DDS / MDS must be set up in the drive.
P827[0] Ù P827[1] Ù P827[n] must be set to different values.
The contactor is switched over by the application. => P833, Bit0=1
The pulses are disabled by the drive => P833, Bit1=0
Initial PLC position: Star mode, therefore set bit 21.5 in the axis DB to “1” during power-up.
o Use the NCU service interface X127 for commissioning and service only.
o The machine control panel (MCP) is operated on Profibus or Ethernet. No mixed operation!
o Profibus 1 must be configured so that the CU, supply and drive softkeys are displayed at the HMI.
o With PLC 319, Profibus diagnostics with FB125 is not possible.
o PLC 319, ProfiNet functionality: CBA PLC communication has been released.
o The FC1007 AG_LOCK, FC1008 AG_UNLOCK, FC1010 AG_CNTRL blocks have not been released.
o The PLC FORCEN [FORCING] in conjunction with 840D sl has only been released with some
restrictions. It is possible with the PLC317 from the PLC operating system >= V20.70.37 (2.4 SP1 HF11)
/ PLC319 and higher, PLC operating system >= V26.90.10 (2.4 SP1 HF11) and higher.
o With 840D sl, it is not permissible to connect the VDI interface signal DB10.DBX57.3.
6. Information about the SINAMICS drive:

o The Starter may not be used in combination with NCU software V1.5 / V2.5.
For this reason, the following remarks regarding the Starter are not relevant.
o The HMI-Avanced software / commissioning tool 7.5 HF1 (or later) is required for drive commissioning.
o No parallel use of measuring functions for i and n measurement via starter and HMI Advanced. Starter
measurements require a Power OFF => ON and immediate measurement with the starter. Starter
measurements must not be performed after HMI Advanced measurements.
o If a SINAMICS component is replaced and the software upgraded, the firmware release must be
checked and, where necessary, the original firmware release restored.
All rights reserved
(Key word: Macro 150399)

Firmware releases can be checked in the following parameters:
Control unit R18 Î Firmware release of CU
Infeed R128 Î Firmware release of infeed
Drive MD R128 Î Firmware release of power section
R148 Î Firmware release of sensor module
o For the time being, the starter is still required for determining the motor codes.
o Mains voltages: For smooth operation in the target country the following parameters must be set in the
specified order:
P010 = 1
P210 = mains rated voltage in the target country
P211 = mains rated frequency in the target country
P340 = 1
P3410 = 4
P3900 = 3
Save RAM to ROM
Power off the system; do not power it on again until it is connected to the mains of the target country.
With the next ON command on the ALM, a mains identification is run and the determined values are
saved powerfail-proof.
o The APC function increases the NCU load. Prior to using this function a performance estimate must be
carried out.
o p1240, p1244, p1248, p1250:
If Vdc control and DDS switchover have been activated in V2.4, check if correct values have been
entered in the contents of indexes >0 of p1240 after upgrading the system.
o DMC20/HUB has not been released.
o With 840D sl and SW 2.5 SP1, 62.5 µs drive cycles have been released. The following conditions apply
accordingly:
- with this setting, two axes can be operated on one CU or NX.
o - only the same clock cycles can be set on a double-axis module.
o Temperature prewarning messages ( DB[axis].DBX94.0, DBX94.1 ) sporadically occur.
Remedy: Only evaluate the PLC signal if this is pending for more than 1.5 s in the VDI interface.
o For SINUMERIK software releases 1.3 and 1.4/2.4, different firmware versions of the components (NCU,
NX, Motor Modules, DRIVE-CLiQ motors) involved in the safety functions can be combined (mixed)
without having to adapt the firmware versions.
The following applies from SINUMERIK software release 1.5/2.5 and higher:
The firmware versions of the Motor Modules, Sensor Modules and DRIVE-CLiQ motors (include
integrated Sensor Modules) involved in the safety functions must be adapted to the SINAMICS firmware
version of the NCU.
This occurs automatically when booting, if parameter p9826 (firmware, automatic) is set to 1 (standard
setting). When using Safety Integrated, parameter p9826 (firmware, automatic) must be set to 1 and
must not be re-parameterized. For the acceptance test of Safety Integrated, the safety firmware
versions of all of the Motor Modules, Sensor Modules and DRIVE-CLiQ motors - involved in the safety
functions - must be read-out, logged and checked against the following list:
http://support.automation.siemens.com/WW/view/de/28554461
Each line in the tables represents a possible combination of Safety firmware versions.
o When booting, chassis units must be operated in the open-loop control mode (refer to MD35020).
o When commissioning the drive, it may occur that parameter changes become active only after switching
off / on the system twice.
o Machine data change as a result of a changed Drive ES SlaveOM

The Drive ES SlaveOM is responsible for allocating addresses of drive units connected to Profibus of the
PLC. The addresses are allocated in the PLC HW Config. The addresses allocated here must be
entered into the NC machine data MD13050[nn] corresponding to the required axis configuration.

All rights reserved
When a Starter V4.1.n (or later) is installed (later, including the installation of toolbox V2.6), the “new“
Drive ES SlaveOM is linked in. Contrary to the previous situation, an address space for six axes is now
reserved for each CU or NX. This is realized when creating a PLC hardware configuration for the first
time. As a result, addresses may be shifted or gaps occur.
This modified address allocation must then be communicated to the NC in machine data 13050[nn], as
otherwise the allocations will no longer be correct.
This is especially true if existing NC data back-ups (archives) are being used as otherwise these will no
longer match the PLC hardware configuration.
Further, in HW Config, the address of telegram 390 (PZD-2/2) of the first NX changes from 6516 to
6530. When using additional NX modules, the address is incremented with an offset of 10. Machine data
MD13120[1+n] must be correspondingly adapted.
If existing PLC projects are imported into an S7 environment with “new” Drive ES SlaveOM, then the old
(previous) address configurations are kept. However, the drive objects that have been newly inserted
into this project receive the “new” address allocation.
A “Standard” (new) address allocation is achieved using “Reorganize addresses”. If, for NX objects, the
“Standard telegram 1 (PZD-2/2)” is entered from an existing configuration, then this must be replaced by
telegram 390 in order to achieve a standard, new address allocation.
Example:
One NCU with a Sinamics Integrated and two NX10 each with 3 axes are configured.
Address allocation with the Drive ES SlaveOM version “old”:

On NX10_1, the 3rd axis has the address 4420
On NX10_2, the 1st axis has the address 4460
Address allocation with the Drive ES SlaveOM “new”

On NX10_1, the 3rd axis has the address 4420
On NX10_2, the 1st axis has the address 4580

All rights reserved
Version of Drive ES
SlaveOM“old”

All rights reserved
PLC HW
configuration

All rights reserved
NX10_1

All rights reserved
NX10_2

All rights reserved
Version of Drive ES SlaveOM “new”

All rights reserved
NX10_1

All rights reserved
NX10_2

All rights reserved
Machine
data13050[nn]

All rights reserved
Re-organizing
addresses
7. HMI sl
7. 1 Functional improvements in the HMI sl compared to SW 2.5 SP1:

o For an NCK and drive reset, a cold drive start is now initiated with p972=3.
o Machine area, large actual value display: The decimal places in the inch dimension system are
sporadically incorrect
o Machine area, tool measuring: Incorrect values if X0 and Y0 are empty
o Machine area, block search: Search target in EXTCALL program is not found
o Machine area, set WO: WO for incorrect axis with suppressed (hidden) axes
o Machine area, suppress (hide) axis independent of the operating modes.
o Machine area, setting-up feed for G95 is written into the incorrect setting data
o Machine area, large actual value display: For a command axis, the spindle override is displayed
o Parameter area: GUD9 is not listed under GUD selection
o Parameter area: Tool list, tool additional data, problems with the cursor
o Diagnostics area: Axis diagnostics display for master-slave drive
o Commissioning (start-up) area: PC keyboard, numerical block, the enter key is ineffective
o Commissioning area, logical drives: Several network drives to a PC do not function
o Text length has been adapted for the English language.
o HT8: Under certain circumstances, traversing keys act on the input fields of the HMI sl
o AP00729615 Commissioning, system data: NC OEM folder no longer displayed
o AP00714272 Program can no longer be copied from USB stick to MDA
All rights reserved
o AP00818991 Tool offset entry gets lost when changing the edge in the NC
o AP00825779 Incorrect SI diagnostic screen due to channel gap
o AP00826636 Incorrect checksums in the SI diagnostic screen due to axis gaps
o AP00832030 HT8, CPF menu: Inteface signal gets stuck with pressed softkey and hidden CPF menu
7. 2 Remarks regarding HMI sl:

o The HMI sl software V2.5 is an integral component of the NCU software 2.5 and started automatically
when the NCU7x0 runs up. The HMI sl is also designated as “internal HMI“.
o HMI sl can only be operated via an operator panel equipped with TCU which is connected to the X120 of
the NCU7x0 via Ethernet. For service purposes, it can also be operated via a PC/PG using VNC Viewer.
For this, the entry "ExternalViewerSecurityPolicy=2" must be set in the tcu.ini.
o Configuring data such as PLC message and alarm texts must be stored on the NCU CF Card in the
corresponding directories under /card/user/sinumerik/hmi/... or /card/oem/sinumerik/hmi/... (see HMI sl
Intallation and Startup Guide). The file system on the CF Card can only be accessed “online“, that
means on the running NCU. Data are transferred either via USB stick or the network connection of the
HMI operator interface (Commissioning / System data area) or via the WinSCP network connection.
IMPORTANT: In general, data names of configuring files must be written in lower case letters.
o When upgrading NCU-SW 2.4 SP1, display MD values (from the file hmi_md.ini) may have to be
manually converted into the relevant new NC-MDs. The conversion table is included in the HMI sl
Intallation and Startup Guide, Chap. 9.1.
o The option “Additional 256MB HMI user memory on CF Card“ is required to store part programs and
archives on the CF Card (“local drive“). Notice: General NCK reset also deletes this option. As a result,
the “local drive“ is not available until the option is reset. All existing data are retained.
o When operating an NCU without TCU (i.e. only with HMI-Advanced on PCU 50), the HMI sl must be
deactivated using the service command “sc disable hmi“.
o Tool management - "Reactivate" softkey:
The actual values of all monitoring types set in the NC for the selected tool are reset upon reactivation
with the following setting in the file sltmlistconfig.xml (milling) resp. sltmturninglistconfig.xml (turning).
<SETTINGS>
<ReactivateAllMonitorModes value="true" type="bool" />
</SETTINGS>
ReactivateAllMonitorM Refers to the "Reactivate" function
odes true – Resets the actual values of all monitoring types set in the
NC
false – Resets the actual value of the monitoring type active on
the tool
o HT8 – User-specific key labeling in the CPF menu:
The user can label the texts of the CPF menu (CPF: Control Panel Function) and the traversing keys on
HT8 entering individual texts in his own language.
For this, we have prepared a template for language-independent U key labeling, "oem_slck_deu.ts" in
the directory "siemens/sinumerik/hmi/lng".
Create for each language used a copy of this original file in one of the two directories
oem/sinumerik/hmi/lng or user/sinumerik/hmi/lng and designate these copies as follows:
German slck_deu.ts
English slck_eng.ts
French slck_fra.ts
Spanish slck_esp.ts
Italian slck_ita.ts
Chinese slck_chs.ts
Open the relevant language file and modify the text between the two tags
“<translation>U1</translation>“ as desired. Enter %n wherever you want to force a line break.
Example: <translation>Ex%ample</translation>
Max.10 characters can be entered in 2 lines. When you have adapted all text files, reboot the NCU.
Remark: You can also create / edit "*.ts" files externally on PC. Please note that the files are stored with

All rights reserved
UTF8 code.
o How to process special characters within the editor:
Use the HMI sl editor to edit text files which use the character LF (0aH) or the string CRLF (0d0aH) as
end-of-line / end-of-phrase ID. Binary files cannot be opened with the editor. Neither can you open files
with one of the following extension: .EXE, .LIB, .ELF, .ARC, .TS, .ZIP, .SO, .PNG, .BMP, .ICO, .CFS,
.BIN, .QM, .HMI, .CFG, .ACX, .EMF, .ALM, .ARD, .TGZ, .PTE, .CYC.
Files which are newly created with the HMI sl editor are coded in UTF8 and have the LF character as
end of block ID. Special characters included in UTF8-coded files are displayed correctly. When opening
files, the HMI sl editor assumes that the files are UT8-coded. When opening files using other codes such
as Windows code page coding, special characters may not be displayed correctly. This refers, for
example, to files that have been created using the HMI-Advanced editor. The coding of such files is not
changed when being opened with the HMI sl editor. They are not automatically converted into UTF8
code.
If files are created / edited using an external editor (e.g. Notepad under Windows) instead of the HMI sl
editor, please ensure that the file is stored with UTF8 code. For this, enter "UTF-8" as encoding when
storing the file in the "Save As" dialog with Notepad. If no special characters are used, you can also
enter "ANSI" as encoding.
7. 3 Limitations in HMI sl:

o The HMI-Advanced software / commissioning tool 7.5 HF1 (or later) is required for drive commissioning.
o After reading in a drive archive with HMI sl, you have to power OFF / ON the controller in order to
activate the drive data.
o Loadable compile cycles are not stored using the NC series startup archive because they are stored on
the NCU CF Card and are retained beyond general NC reset. They can be processed analogously to
HMI configuring data.
o In general, only 1 HMI may be active on each NCU, either the internal HMI sl or 1 external HMI-
Advanced. Exceptions: Commissioning / Service; HMI-Advanced for the master operator panel with
permanently assigned MCP and 1 tool loading station with HMI sl without MCP.
Remark: In this configuration, PLC alarm 410906 "M:N: HMI sign of-life missing" is output after NCK
reset resp. restart of the HMI sl.
o The tool management only supports 1 TO area in the NC.
o Only NC channel 1 can be simulated. No alarm help is available during simulation.
o External part programs exceeding the available unassigned NC part program memory cannot be
simulated.
o The data required for simulation may have to be adjusted after modifying the NC configuration resp.
reading in an NC series startup archive. The adjustment is initiated in the Commissioning / HMI area via
the softkey "Simulation Power On" on the 2nd vertical softkey bar.
o Simultaneous recording option: The program runtime display can be activated via MD 27860
$MC_PROCESSTIMER_MODE.
o The contour editor generates G codes using the Geo axis names of NC channel 1.
o The editor cannot display codepage-coded language-specific special characters.
o Upper and lower cases with path names used in joblist SELECT instructions that refert to part programs
stored on CF Card or USB data carrier are relevant.
8. Information on the NCU Base software:

o The Linux operating system of the NCU7x0 is also referred to as the NCU Base software, similar to the
PCU Base software for the PCU 50. You will find the relevant documentation in IM7 on the supplied
DVD. The NCU base software ensures, among other things, the start of the NC, PLC, and HMI software
during power-up as well as the booting of the TCU (if present). The NCU Base software is user-oriented,
i.e. you must log in and enter a password in order to obtain specific access authorization. This current
login and password protection is relevant only for accessing a Linux service shell or the CF card using
WinSCP. For startup and servicing activities, the login ID is "manufact" and the password "SUNRISE"
(case-sensitive!). To open the Linux service shell on the TCU, press keys "Area switchover" and "Recall"
(F10 and F9) simultaneously, then "Scan for Servers", "2" or boot from the USB stick.
All rights reserved
o For access via the network using WinSCP, enter the above mentioned login and password on the
"Session" screen. This login procedure also applies after the NCU7x0 has booted from a USB stick with
the NCU service system provided that executable NCU software is installed on the CompactFlash Card.
If this is not the case (e.g. if the CF card is empty), enter the login ID "admin" and password "SUNRISE".
o You can display a list of the syntax of all available service commands in the service shell by running
command "sc help".
8. 1 Networking:
o Please observe the current documentation "Operator Components and Networking (IM5) Version
04/2008" !
o Important system and network settings for the NCU base software have been preset in the file
basesys.ini in the directory /card/user/system/etc and may be modified there. The original basesys.ini is
located at /card/siemens/system/etc, it is entitled "template-basesys.ini".
o Each NCU within the plant / system network should be assigned a unique ("talking") computer name,
together with the entry "Host name=..." in basesys.ini. Permissible characters are uppercases /
lowercases, numbers and minus signs.
o The NCU DHCP server should always be switched on.
o When modifying NCU / PCU IP addresses, perform the service command “clear dhcp" to activate the
change.
8.1.1 Configuring 1 NCU with TCUs and MCPs

In this configuration, no special settings must be made in the basesys.ini.
The DHCP server and internal HMI-Embedded remain activated.
8.1.2 Configuring 1 NCU with 1 PCU 50, MCPs and TCUs, if required
Configuring 1 NCU with 1 PCU 50, MCPs and TCUs, if required
In this configuration, make the following settings in the basesys.ini of the NCU:
Host name = ....
SyncModeDHCPD_SysNet = ON_MASTER
In general, the internal HMI-Embedded must be deactivated because two HMIs (HMI-Advanced and HMI-
Embedded/JobShop) may only be operated on one NCU in particular cases.
On PCU 50, we recommend that you use PCU base software V8.2 (or later).
In the System Network Center, tab TCU Support, select the default configuration "No boot support".
If the system is equipped with a TCU (HT8) that shall be switched to PCU 50 by default, the following entries
must be made in the file /card/user/common/tcu/<TCU Name>/common/tcu/config.ini on the NCU
MaxHostIndex = 1
[host_1]
Address = <IP address of the PCU>.
8.1.3 Configuring several NCUs and, if necessary, 1 or several PCUs, TCUs, MCPs
In this configuration, make the following settings in the basesys.ini of the NCU:
Unique host name = .... for each NCU
Unique InternalIP= ....
Unique InternalNetMask= ....
Exactly one NCU with SyncModeDHCPD_SysNet = ON_MASTER
When booting for the first time after establishing the network, initially, the DHCP master should be
booted and then the other stations.
On PCU 50, you have to use PCU base software V8.1 SP3 or later.
In the System Network Center, tab TCU Support, leave the default configuration "Complete TCUsupport"
unchanged. Under the tab DHCP Settings, we recommend that you set "Sync mode low priority".
All operator stations within the plant / system network (TCUs, HT8, PCU 50) are managed on the NCU
with "ON_MASTER", that means the config.ini files as well as the .leases file comprising all IP
addresses assigned within the system which are relevant during the runtime are stored there.
All rights reserved
The config.ini files are distributed to all other NCUs / PCUs by the master NCU using the service
command "sc distribute tcudata".
Via the Service command "sc clear dhcp" and subsequent power ON / OFF of the complete system, the
NCUs / PCUs are assigned preset IP addresses. New addresses are assigned to TCUs and MCPs and
the .leases file is then distributed to all other NCUs / PCUs.
Important: The System Network Center, tab OPs allows to directly edit on each PCU 50 the config.ini
files of all operator stations on the master NCU. The data are automatically distributed to all NCUs /
PCUs each time they are changed.
9. Cycle packages:
NCU SW 2.5 comprises the following cycle packages which can be installed:
Technological cycles (standard cycles)
Measuring cycles
ISO cycles
With HMI sl, these packages are found in the Commissioning area under System Data / HMI data /
cycles archive.
Upgrading from NCU-SW 1.4 or 1.5, refer to Section 9.5
Important remarks:
The HMI sl cycle support is based on the above-mentioned cycle packages V2.5. Cycle calls within part
programs regarding these cycles cannot be recompiled nor processed using the HMI-Advanced 7.x
cycle support. If you wish to use the HMI-Advanced 7.x cycle support, you have to load the cycle
packages 7.x included in HMI-Advanced on the NC.
These cycle calls cannot be recompiled nor processed with HMI sl.
With HMI sl, cycle packages 2.5 are stored in the Commissioning area, system data under HMI data /
Cycle archive / System. The relevant subdirectories comprise archives including cycles and the
corresponding GUDs which must be activated after being read in under NC data / Definitions.
The following settings must be made in the NC-MD to commission the cycles:
MD 11270=1
MD 18170=150
MD 18180=1500
MD 18280=150
9.1 Techological Cycles – Functional Scope

Drilling
Cycle Function and entry softkeys
CYCLE801 Drilling / positions / grid or frame

CYCLE802 Drilling / positions / arbitrary positions
CYCLE81 Drilling / centering
CYCLE82 Drilling / boring reaming / boring
CYCLE83 Drilling / deep-hole drilling
CYCLE85 Drilling / boring reaming / reaming
CYCLE86 Drilling / boring
HOLES1 Drilling / positions / hole series
HOLES2 Drilling / positions / hole circuit
CYCLE840 Thread / tapping with compensating chuck
CYCLE84 Thread / rigid tapping
All rights reserved
Turning
CYCLE92 Turning / cutoff

CYCLE930 Turning / groove
CYCLE940 Turning / undercut
- Form E, form F, undercut thread DIN, undercut thread
CYCLE951 Turning / cutting
CYCLE98 Turning / thread / thread chain
CYCLE99 Turning / thread
- longitudinal, taper, face
CYCLE95 Contour turning / cutting
CYCLE62 Contour turning / contour
Milling
CYCLE61 Milling / face milling

CYCLE70 Milling / thread milling
CYCLE76 Milling / spigot / rectangular spigot
CYCLE77 Milling / spigot / circular spigot
CYCLE79 Milling / spigot / polygon
LONGHOLE Milling / groove / elongated hole
POCKET3 Milling / pocket / rectangular pocket
POCKET4 Milling / pocket / circular pocket
SLOT1 Milling / groove / longitudinal groove
SLOT2 Milling / groove / circular groove
CYCLE72 Contour milling / path
CYCLE62 Contour milling / contour
Compatibility cycles for 802Dsl:

• These cycles can be recompiled and modified via screenforms
Cycle Function
CYCLE87 Compatibility 802Dsl – boring 3

CYCLE88 Compatibility 802Dsl – drilling with stop
CYCLE89 Compatibility 802Dsl – boring 5
• Programs (from SINUMERIK 802Dsl) comprising the following cycles to be called can still be executed. These cycles
can, however, not be recompiled nor modified via screenforms.
Cycle Function
CYCLE71 Compatibility 802Dsl – face milling

CYCLE90 Compatibility 802Dsl – thread milling
CYCLE93 Compatibility 802Dsl – groove
CYCLE94 Compatibility 802Dsl – undercut form E and F
CYCLE96 Compatibility 802Dsl – thread undercut form A, B, C, D
CYCLE97 Compatibility 802Dsl – thread cutting

All rights reserved
Other cycles – internal:
Cycle Function
CYCLE861 Reverse countersinking, for ISO compatibility only, no input screen

CYCLE203 Auxiliary cycle for chamfer
CYCLE204 Auxiliary cycle, calculate pitch for metric thread
CYCLE206 Auxiliary cycle, tool change within JOG
PROG_EVENT ASUP for supporting special operating modes
Important new functions as compared to 840Dsl cycles SW 7.3
General information
• Cycle functions resp. input screenforms for cycles are configured in the configurable machine and setting data. Part
programs using the old GUD setting data (field _ZSD[x]) can still be executed.
Drilling
• Drilling cycles support the selection of depth with regard to shaft / pivot
• New frame drilling pattern
Turning
• Contour transfer via CYCLE62 during cutting

• New cutoff cycle
• Extended groove functionality
• Extended undercut functionality
• Extended thread cutting functionality
Milling
• Contour transfer via CYCLE62 with path milling

• Extended functionality face milling (margin stop)
• Extended functionality thread milling
• New polygon cycle
• Milling cycles can be executed for individual positions and position patterns
• Milling cycles comprise the new chamfer function
Difference list for cycles / cycle functions for 840Dsl SW 7.5:

This cycle package does not comprise the following cycles / cycle functions:
CYCLE60 Engraving cycle

CYCLE800 Swivel cycle
CYCLE832 High Speed Settings
CYCLE899 Advanced Milling
POCKET1 Rectangular pocket / circular pocket 1
POCKET2
1
The POCKET1/POCKET2 function is covered by the state-of-the-art pocket milling cycles POCKET3/POCKET4
All rights reserved
Special remarks:
• To activate the cycle support function, set the following MDs
o MD 52200 MCS_TECHNOLOGY > 0 (1 or 2)
o MD 52201 MCS_TECHNOLOGY_EXTENSION > 0
9.2 Measuring cycles – Functional Scope

The measuring cycles support the following setup functions in JOG (SK “Workpiece zero“):
• Probe adjustment (radius, length)
• Edge setting
• Edge alignment
• Corner measurement messen (3 points)
• Corner measurement (4 points)
• Hole measurement
• Spigot measurement
This package also comprises measuring cycles for the following functions:
• Tool probe adjustment
• Tool measuring, length
• Tool measuring, radius
Prerequisites for application
• A switching probe is required for measuring cycles.

• According to the machine data setting for measuring cycles, you have to connect the workpiece probe to the first
controller measuring input, the tool probe to the second measuring input (MD 52600
MCS_MEA_INPUT_PIECE_PROBE, and MD 52601 MCS_MEA_INPUT_TOOL_PROBE)
Important new functions as compared to 840Dsl measuring cycles SW 7.3
General information
• All measuring cycle data which are important for machine manufacturers and users are provided in the configurable
machine and setting data (e.g. data fields for calibration values). The GUD blocks GUD5, GUD6 and GUD7_MC are
no longer required.
Difference list for measuring cycles / cycle functions for 840Dsl SW 7.5:
This cycle package does not comprise the following cycles / cycle functions:
• Measuring within the automatic program – Measuring result screen display – Recording
• Measuring cycle support by the editor
• Plane adjustment in JOG
• Kinematic measurement (CYCLE996)
Special remarks:
• Please note the following two setting data to achieve the full range of measuring functions:

All rights reserved
o SD 54798 SCS_J_MEA_FUNCTION_MASK_PIECE
o SD 54799 SCS_J_MEA_FUNCTION_MASK_TOOL
• The call-up of measuring cycles within the part program is not included in this Software Version. The relevant program
call-ups yield an NC alarm.
9.3 Cycles ISO compatibility – Functional Scope

The functional scope of the cycles for ISO compatibility corresponds to Software Version 6.5 for SINUMERIK 840D. The
two ISO dialects are still supported.
The cycle setting data for ISO compatibility have not been converted to configurable machine or setting data.
The data fields for GUD setting are no longer relevant.
9.4 Configurable machine and setting data – Functional Scope

New configurable machine and setting data have been introduced in SW 2.5 (or later).
• These data replace the GUD variables of the cycle packages and the HMI display MDs.
• Like all other machine and setting data, they are displayed in the “Commissioning“ area (according to the protection
level) and lie within the number range starting from 50000.
51xxx General MD
52xxx Channel MD
53xxx Axis MD
54xxx General SD
55xxx Channel SD
56xxx Axis SD
• The data names indicate the MD meaning and use, abbreviations are stated directly after the prefix – e.g. DISP for
display, ISO for ISO cycles, MEA for measuring cycles, TURN for turning technology, etc.
List of G codes together with the corresponding shell cycles and technology cycles:
Milling:
G Code Shell Cycle Siemens Technology Cycles
G05 CYCLE305
G08 CYCLE308
G10.6 CYCLE3106
G22 CYCLE322
G23 CYCLE323
G27 CYCLE328
G28 CYCLE328
G30 CYCLE330
CYCLE396
G71.1 / 72.2 CYCLE3721
G81 CYCLE381M CYCLE82

All rights reserved

Turning:
G Code A/B/C Shell Cycle Siemens Technology Cycles
G05 CYCLE305
G10.6 CYCLE3106
G22 CYCLE322
G23 CYCLE323
G27 CYCLE328
G28 CYCLE328
G30 CYCLE330
CYCLE396
G50.2 / 51.2 CYCLE3512
G70 / 70 / 72 CYCLE370T
G71 / 71 / 73 CYCLE371T CYCLE395
G90 / 77 / 20 CYCLE371T
G72 / 72 / 74 CYCLE372T CYCLE395
G94 / 79 / 24 CYCLE372T
G73 / 73 / 75 CYCLE373T
G74 / 74 / 76 CYCLE374T CYCLE375T
G75 / 75 / 77 CYCLE374T CYCLE375T
G76 / 76 / 78 CYCLE376T CYCLE398
G92 / 78 / 21 CYCLE376T CYCLE398
G83 CYCLE383T CYCLE375T
G84 CYCLE384T CYCLE84
G88 CYCLE384T CYCLE84
9.5 Upgrading cycles from NCU-SW 1.4 / 1.5
Initial situation:
840D sl with SW V1.4 or V1.5.
These releases include technological cycles V7.3 or V7.5 and measuring cycles V7.3 or V7.5.
Objective of the upgrade:

840D sl with SW V2.5.
This release includes technological cycles V2.5 and measuring cycles V2.5 for measuring in JOG. These cycles
are not identical with the cycles from V7.3 or V7.5 – but they are compatible from a functional perspective. The
cycles are always upwards compatible, but not downwards compatible. The difference is in the cycle support
and the configuration of cycle functions - or the input screen forms are made in the configurable machine and
setting data. Part programs that use the old settings in the GUD parameters can still be run.
Upgrade procedure:
1. Back up data by reading out the series commissioning archive for the NC, PLC and drive.

All rights reserved
2. Install the NCU-SW V2.5 on the CF card (sc restore -full ...).
It is then necessary to initiate a general reset for the NCU and PLC: Set the SIM/NCK switch into position 1,
the PLC switch into position 3 and power down/power.up.
3. Read in the saved series commissioning archive for NC, PLC and drive.
4. Using the upcycdat.mpf program, write the GUD values to the cycles machine and setting data. The program
can be downloaded from eSupport. The path is as follows:
-> Automation systems Engineering, Service tools
-> NC engineering tools
-> Cycle tools
“Upgrade, cycle data for 840D sl”
The archive file should be read into the NC, whereby the upcycdat.mpf is saved in the “TEMP” workpiece.
When using cycles in several channels, the program should be started in each of these channels. The
upcycdat.mpf program should then be deleted on the NC.
5. Delete the NC data/definitions GUD7_SC, GUD7_MC, GUD7, GUD5, GUD6, SMAC_SC, SMAC. The files
can be found under Start-up/System data.
6. Copy the CUST_TECHCYC.SPF cycles – which also have to be adapted by the machinery construction
OEM - and CUST_MEACYC.SPF from the CF card/Siemens/ Sinumerik/Cycles/sc/prog or CF card/Siemens/
Sinumerik/cycles/mc/prog to NC data/Cycles/Manufacturer cycles (or -/User cycles). This is accessed via
Start-up/System data.
7. The CUST_MEACYC.SPF cycle replaces the CYCLE198 and CYCLE199 from cycle status V07.xx.xx. If
changes were made to these cycles (i.e. they have been adapted), then these should be transferred into the
cycle CUST_MEACYC.SPF. The cycles CYCLE198.SPF and CYCLE199.SPF can then be subsequently
deleted.
8. Delete the technological and measuring cycles in the NC data/Cycles/Standard cycles path. These files can
also be found under Start-up/System data.
9. Power down/power up the control.
10. Download the cycles and definition files from the CF card into the NC. This is again realized under Start-
up/System data and read in the archive cycles.arc and defines.arc under the CF card/Siemens/
Sinumerik/cycles/sc/prog path and the archiv mcycles.arc under the CF card/
Siemens/Sinumerik/cycles/mc/prog path
11. To activate the cycle support the machine data
• MD 52200 MCS_TECHNOLOGY
• MD 52201 MCS_TECHNOLOGY_EXTENSION
must be set. A value of “1” stands for turning and value of “2” for milling.
12. Power down/power up the control.

All rights reserved

Ncu Hmi SL 25 sp2 76

Uploaded by

Document Information

Original Title

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

Ncu Hmi SL 25 sp2 76

Uploaded by

Copyright:

Available Formats

s SINUMERIK 840D sl 2009-10-13

NCU System Software 2.5 SP2

SINUMERIK 840D sl, NCU system software for 31 axes ) 6FC5850-3XG20-8YA0

1. Installation of the NCU software:

1.1 Installation of the NCU service system on USB stick:

It is best to copy the image in a DOS shell.

1.2 Upgrading NCU 7x0.2 with NCU-SW 2.4 SP1

1.3 New installation

1.4 Systems without TCU

1.5 Automatic upgrade using a bootable USB stick:

2. New functions in NCK 72.00.00 (or later)

The display contents must be stored in the field “ChrArray“type string[64].

Sample parameter setting for the HT2 at FB1 (OB100):

4. Information about the NCK:

© Siemens AG, 2009 I DT MC R&D 51 Page 6 of 29

o Functional Improvements and Further Developments:

AP00582494 AP00650310 AP00664996 AP00711788 AP00307709 AP00307996

RQ id AP00307663 AP00307762 AP00307970 AP00307986

AP00308014 AP00308044 AP00381742 AP00438261 AP00473047

5. Information about the PLC:

o Tool box V01.05.01 and STEP7 V5.4 SP2 are required.

6. Information about the SINAMICS drive:

(Key word: Macro 150399)

o Machine data change as a result of a changed Drive ES SlaveOM

© Siemens AG, 2009 I DT MC R&D 51 Page 9 of 29

Address allocation with the Drive ES SlaveOM version “old”:

Address allocation with the Drive ES SlaveOM “new”

© Siemens AG, 2009 I DT MC R&D 51 Page 10 of 29

© Siemens AG, 2009 I DT MC R&D 51 Page 11 of 29

© Siemens AG, 2009 I DT MC R&D 51 Page 12 of 29

© Siemens AG, 2009 I DT MC R&D 51 Page 13 of 29

© Siemens AG, 2009 I DT MC R&D 51 Page 14 of 29

Version of Drive ES SlaveOM “new”

© Siemens AG, 2009 I DT MC R&D 51 Page 15 of 29

© Siemens AG, 2009 I DT MC R&D 51 Page 16 of 29

© Siemens AG, 2009 I DT MC R&D 51 Page 17 of 29

© Siemens AG, 2009 I DT MC R&D 51 Page 18 of 29

7. 1 Functional improvements in the HMI sl compared to SW 2.5 SP1:

7. 2 Remarks regarding HMI sl:

© Siemens AG, 2009 I DT MC R&D 51 Page 20 of 29

7. 3 Limitations in HMI sl:

8. Information on the NCU Base software:

8.1.1 Configuring 1 NCU with TCUs and MCPs

Upgrading from NCU-SW 1.4 or 1.5, refer to Section 9.5

9.1 Techological Cycles – Functional Scope

Cycle Function and entry softkeys

CYCLE801 Drilling / positions / grid or frame

Cycle Function and entry softkeys

CYCLE92 Turning / cutoff

Cycle Function and entry softkeys

CYCLE61 Milling / face milling

Compatibility cycles for 802Dsl:

CYCLE87 Compatibility 802Dsl – boring 3

CYCLE71 Compatibility 802Dsl – face milling

© Siemens AG, 2009 I DT MC R&D 51 Page 24 of 29

Other cycles – internal:

CYCLE861 Reverse countersinking, for ISO compatibility only, no input screen

Important new functions as compared to 840Dsl cycles SW 7.3

• Contour transfer via CYCLE62 during cutting

• Contour transfer via CYCLE62 with path milling

Difference list for cycles / cycle functions for 840Dsl SW 7.5:

Cycle Function and entry softkeys

CYCLE60 Engraving cycle