SINUMERIK 840D SL / 828D Attached Siemens Cycle Packages For SW 4.7 SP6
SINUMERIK 840D SL / 828D Attached Siemens Cycle Packages For SW 4.7 SP6
2018
SINUMERIK 840D sl / 828D
Attached Siemens cycle packages for SW 4.7 SP6
1. Reference documents
Document Contents
SINUMERIK 840D sl/828D In Chapter Setting up the machine – all functions for measuring
Milling in JOG workpiece and tools on milling machines
Operating Manual Chapter – Generating a G-code program
Chapter – Generating a ShopMill program
Chapter – Programming technological functions (including all
drilling, milling and turning cycles)
SINUMERIK 840D sl/828D In Chapter Setting up the machine – measuring tools in JOG on
Turning lathes
Operating Manual Chapter – Generating a G-code program
Chapter – Generating a ShopTurn program
Chapter – Programming technological functions (including all
drilling, turning and milling cycles)
SINUMERIK 840D sl/828D Chapter – Externally programming cycles: contains the call
Programming Manual Job Planning interfaces for all technological cycles in the G-code and detailed
description of the transfer parameters
SINUMERIK 840D sl/828D T4: Automatic post optimization with AST (included, all AST
Function Manual Special Functions cycles)
(only for 840D sl, description for machine manufacturers)
2. Compatibility
2.1. Compatibility to cycle packages 840D sl / 828D from SW 4.5 SP3
In the following points, the behavior of the cycles has changed when compared to software releases from
SW 4.5 SP3 and higher:
Technology cycles:
- From 4.5 SP6: Change to the drilling cycles, if an absolute drilling depth is not programmed – and the
incremental drilling depth = 0 – or is also not programmed:
Alarm 61019 "Parameter DP, DPR incorrectly defined" is now output if DPR=0, DPR is not
programmed – and DP is not programmed.
Examples:
CYCLE81(7,5,2, ,0) ; alarm 61019
CYCLE81(7,5,2, , ) ; alarm 61019
CYCLE81(7,5,2,0,0) ;absolute, DP=0 applies
CYCLE81(7,5,2,0, ) ;absolute, DP=0 applies
- From SW 4.7: Changes in cycles for thread cutting (CYCLE99, CYCLE97) and threaded chain
(CYCLE98)
The behavior for thread synchronization (operation using softkey below JOG) has been aligned to
CYCLE 99 in CYCLE97 and CYCLE98. This means that: Thread synchronization is only possible, if no
transformation, no TCARR and no rotation around X or Z are active.
- From SW 4.7 SP1: Changes in the high-speed settings cycle (CYCLE832) in conjunction with Top
Surface:
Output CTOL for Top Surface as contour tolerance
Output CTOL for Advanced Surface as axis tolerance (*root (3)) (compatibility)
- From SW 4.7 SP2 HF1: Modified behavior for the swivel cycle (CYCLE800) – or direct with tool
carrier:
The following machine data must be observed:
MD 20196 $MC_TOCARR_ROTAX_MODE bit 2
Bit 2 = 0 … compatibility, is recommended in the case that the software is upgraded
Bit 2 = 1 … compatibility, is recommended when being commissioned for the first time
The setting, bit 2 = 1 means that the control, when swiveling in the pole position (initial position), only
calculates a unique solution.
Existing NC programs with swivel function must then be checked, as the positioning
behavior/response could have changed!
- From SW 4.7 SP5: Up until now, when retracting to the retraction position in Z and Z, XY, the position
of the tool adapter was kept. For example, for a swiveled B axis, when retracting to the retraction
position, the head could violate the software limit position ($MA_POS_LIMIT_MINUS).
When retracting Z and Z, XY to the retraction position, the entered retraction position is now
approached in the MCS. This avoids violating the software limit position.
The new behavior has been implemented in CUST_800; through adaptation, the old behavior can be
restored in CUST_800.
Measuring cycles:
- From 4.7 SP4: The function when measuring workpieces with automatic tool compensation has been
improved.
The tool compensation precisely aligns itself to the statuses in the tool manager.
"Tool is active" and "Tool was in use"
These statuses are also evaluated if there are no tool groups (known as "Replacement tools").
Locked tools are not corrected/compensated. Alarm 61404 "Tool correction not executed" is then
output.
ShopTurn cycles:
- From 4.5 SP5: Regarding the note "Starting point or end point of the machining outside the retraction
planes":
For programs with contour machining from earlier software releases, for an NC start, it is possible that
one of the alarms 61281 "Starting point of machining outside retraction planes" or
61282 "End point of the machining outside the retraction planes" is displayed.
In this case, adapt the retraction planes in the program header.
802Dsl grinding programs that have not been adapted cannot be executed. This is as a result of the new
tool concept (grinding disks and dressing tool).
The table provides an overview of the changes in the machine manufacturer cycles with respect to
software releases from 4.5 SP3 (this also applies to the following SPx and HFx releases).
To use the new functions, the cycles must be copied and appropriately adapted by the machine
manufacturer.
Note:
Generally, the machine manufacturer is recommended to copy all CUST cycles with changed functionality
with respect to the initial state before the upgrade and then readapt them.
This chapter only describes the changes regarding the released software version 4.7 SP4 – i.e. for cycle
packages ZYKL_840DSL_04.07.67.02.
This chapter only describes those changes related to the released software version for 4.7 SP5,
i.e. for the ZYKL_840DSL_04.07.70.03 cycle packages.
- The following general condition applies when using the HighSpeed Settings cycle (CYCLE832)
together with the TopSurface function:
If a CUST_832.SPF is already available in the manufacturer's cycle directory or user cycles, and the
new TopSurface function is to be used, then this CUST cycle must be upgraded to a version from 4.7
SP2 HF1 and higher.
- The following general conditions apply when using the new CYCLE9960:
(1) The kinematic description of the machine must be saved in the control using kinematic
chains (including variable aggregates).
(2) A release on a machine-for-machine basis is required when using the CYCLE9960.
- Notes regarding taking measurements at a counter spindle (with CYCLE978):
(1) It is assumed that to work and take measurements at the counter spindle, mirroring in the tool
axis (Z) is active.
(2) Further, that the alignment of the tool with respect to the main and counter spindle is realized
by rotating around a B axis using a tool carrier that can be orientated.
To suppress a position change of the tool spindle (with the associated probe), when taking
measurements at the counter spindle, the channel-specific
SD55740 $SCS_MEA_FUNCTION_MASK, bit1 should be set to = 0
This means that function "Coupling the tool spindle position with a coordinate rotation
around the tool axis (Z)" is deactivated. The tool spindle remains at the position that was
specified by the previous swivel cycle CYCLE800.
(3) When taking measurements at the counter spindle, calibration must be performed at the main
spindle with active G17.
- Note regarding workpiece measurement with mixed technologies (MD 52000 and 52001 both > 0):
A cutting-edge 5 … 8 must be entered in the tool compensation data of the probe.
- Notes regarding tool measurement, turning tools on lathes with Y axis (CYCLE982):
To avoid traversing motion of a Y axis when measuring tools, in the setting data
SD54629 $SNS_MEA_TP_TRIG_MINUS_DIR_AX3[n] and
SD54630 $SNS_MEA_TP_TRIG_PLUS_DIR_AX3[n]
a target position must be entered for the Y axis.
- Note regarding aligning edge in the program (CYCLE998):
Align edge in the program with CYCLE998 must always be programmed without specifying a
protection zone.
- Note regarding PROG_EVENT in conjunction with swiveling without CYCLE800 and block search:
If, in a part program where a tool carrier is selected and deselected without CYCLE800 call, a block
search between selection and deselection is performed, then for a channel reset, the number of the
last
selected tool carrier is in MD20126 TOOL_CARRIER_REST_VALUE. The precondition is that the
Progevent events are handled via system cycle PROG_EVENT.
In subcycle CYCPE_MA of the PROG_EVENT, for a channel reset event, MD20126 must be reset to
the required value.
- Position 4th axis after block search (e.g. linear axis of the counterspindle, tailstock, back rest)
Marker: _M30
- After end of tool change cycle (with tool change)
Marker: _M111
- Definition: Coupling, counterspindle / main spindle
Marker: _M120
- Definition: Coupling, main spindle / counterspindle
Marker: _M122
- Definition: CYCLE86 – Adapt spindle position to the tool orientation
Marker: _M300
_M440, _M450 … retraction in the tool direction zero (no distance traversed)
_M47 ... retract axis Z to fixed MCS position before tool alignment
_M48 ... retract axis Z and then the XY axes to fixed MCS position before tool alignment
_M75 ...align tool: Deselection
_M996 ... positioning rotary axes for kinematic measurement (called from CYLE9960)
The machine manufacturer (OEM) should check the markers listed above and adapt if required.
Manufacture cycle CUST_800 has been functionally expanded with respect to SW 4.7 SP3.
The following markers must be adapted depending on which modes are to be used:
_M20, _M21, _M22, _M30, _M57, _M58 und _M59.
In these markers, the 1st four-axis/five-axis transformation is activated with TRAORI(1) – and deactivated
with TRAFOOF. These two commands must be adapted to the corresponding kinematic situations.
This function is implemented in all measurement versions when measuring in JOG. This is also true for all
measurement versions in the automatic program, where measurements are made parallel to the axis.
4.6. Notes regarding the name of the swivel data set indirect programming
The GUD _TC_CHANGE defined in the channel is a string with a length of 32. Using this variable, before
the CYCLE800 call, it is possible to define which swivel data set is called in CYCLE800 – independent of
what is actually programmed in the call.
GUD variable _TC_CHANGE is reinitialized with each RESET. At the end of CYCLE800, the variable is
also deleted; this means that before each new CYCLE800 call, the variable must be written to again.
The swivel data set is changed in CYCLE800 after the CUST_800 jump out to marker _M40; this means
that the variable can also be written in CUST_800.
Programming example:
N10 _TC_CHANGE="HEAD_2"
N20 CYCLE800(0,"HEAD_1",100000,57,0,0,0,0,0,0,0,0,0,-1,100,1)
N30 M0 ;* HEAD_2 is active
N40 _TC_CHANGE="HEAD_3"
N50 CYCLE800(0,"HEAD_1",100000,57,0,0,0,0,0,0,0,0,0,-1,100,1)
N60 M0 ;* HEAD_3 is active
N70 CYCLE800(0,"HEAD_1",100000,57,0,0,0,0,0,0,0,0,0,-1,100,1)
N90 _TC_CHANGE="TABLE_2"
N100 CYCLE800(0,"TABLE_1",100000,57,0,0,0,0,0,0,0,0,0,-1,100,1)
N110 M0 ;* TABLE_2 is active
N120 M2
The swivel data set specified in_TC_CHANGE is checked for the following properties:
- The swivel data set to be activated must be enabled
- The following parameters must match the swivel data set selected in the screen form
o $TC_CARR23 (swivel data set type)
o $TC_CARR37 (swivel mode, ones position)
o $TC_CARR37 (select tracking, ten thousands position)
o The selected mode (bits 6,7) in the screen form (axis-by-axis, solid space, projection
angle/direct) to TC_CARR37
After reading in an NC archive, it must be ensured that this value can be overwritten.
1
Before each new CYCLE800 call, variable _TC_CHANGE must be written to again