SINUMERIK 840D sl SW 4.8 SP2 Appendix Siemens Cycle Packages

Transcription

1 1. Reference documents List of reference documents and editions Documentation overview where cycle topics are described Compatibility Compatibility with cycle packages 840D sl / 828D as of SW 4.5 SP Compatibility with grinding programs with 802D sl SW Adapting machine manufacturer cycles Change status of CUST cycles between SW 4.5 SP3 and SW 4.8 SP The table provides an overview of the changes in the machine manufacturer cycles compared to software versions as of 4.5 SP3 (this also applies to the following SPx and HFx releases) Special notes on upgrade Changes with respect to the previous release Changes as of software version 4.8 SP Supplementary conditions Notes on the application of this cycle package Summarizing notes on the CUST_TECHCYC manufacturer cycle New functions Functional changes, expansions to existing markers Summarizing notes regarding the CUST_800 manufacturer cycle New functions Functional changes, expansions to existing markers Functional expansions for swiveling with OEM transformation Example of block formation in CUST cycles CUST_ Summarizing notes on the CUST_832 manufacturer cycle Summarizing notes on the CUST_MEAPROT manufacturer cycle Notes on software limit position consideration during workpiece measurement Notes on calibration on sphere in JOG CYCLE791 New cycle for commissioning nodding compensation Compensation of rotary axis orientation with VCS and CYCLE Creating a compensation file for VCS Verifying a compensation file for VCS Notes on the indirect programming of the name of the swivel data set Notes on increasing the number of calibration data sets Page 1 / 22 Unrestricted / Siemens AG 2017

2 1. Reference documents 1.1. List of reference documents and editions /1/ SINUMERIK 840D sl / 828D Measuring Cycles Programming Manual 05/2017 (SW 4.8 SP1) /2/ SINUMERIK 840D sl / SINUMERIK Operate (IM9) Commissioning Manual 05/2017 (SW 4.8 SP1) /3/ SINUMERIK 840D sl / 840D / 840Di Cycles Programming Manual 01/2008 (SW D sl or SW D) /4/ SINUMERIK 840D sl / 828D Milling Operating Manual 05/2017 (SW 4.8 SP1) /5/ SINUMERIK 840D sl / 828D Turning Operating Manual 05/2017 (SW 4.8 SP1) /6/ SINUMERIK 840D sl / 828D Production Planning Programming Manual 05/2017 (SW 4.8 SP1) /7/ SINUMERIK 840D sl / 828D Grinding Operating Manual 05/2017 (SW 4.8 SP1) /8/ SINUMERIK 840D sl / 828D Functional Manual Special Functions T4 05/2017 (SW 4.8 SP1) 1.2. Documentation overview where cycle topics are described Document SINUMERIK 840D sl/828d Milling Operating Manual SINUMERIK 840D sl/828d Turning Operating Manual SINUMERIK 840D sl/828d Measuring Cycles Programming Manual Contents In Setting up the machine chapter All functions for measuring in JOG workpiece and tools on milling machines Chapter Generating a G-code program Chapter Generating a ShopMill program Chapter Programming cycles (including all drilling, milling and turning cycles) In Setting up the machine chapter Measuring tools in JOG on lathes Chapter Generating a G-code program Chapter Generating a ShopTurn program Chapter Programming cycles (including all drilling, milling and turning cycles) Chapter Basics/measuring principle, etc. (as before) Chapter All measuring versions, workpiece and tool measuring, turning and milling SK oriented Chapter Overview parameter list of the measuring cycles (for external programming): contains the call interfaces for all measuring cycles in the G-code and detailed description of the Page 2 / 22 Unrestricted / Siemens AG 2017

3 transfer parameters Chapter Attachments, list for the changeover to SW from 2.7/4.4 SINUMERIK 840D sl/828d Programming Manual, Production Planning SINUMERIK 840D sl SINUMERIK Operate (IM9) Commissioning Manual SINUMERIK 840D sl/828d Grinding Operating Manual SINUMERIK 840D sl/828d Function Manual Special Functions Chapter Programming cycles externally: contains the call interfaces for all technological cycles in the G-code and detailed description of the transfer parameters Chapter Simulation and simultaneous recording Chapter Configuring cycles Contains a description of the machine and setting data for cycles, swiveling, JobShop, adapting manufacturer cycles (CUST_TECHCYC, CUST_MEACYC, etc.) Chapter Generating a G-code program Chapter Programming technological functions (including all grinding cycles) T4: Automatic reoptimization with AST (including all AST cycles) (only for 840D sl, description for machine manufacturers) Page 3 / 22 Unrestricted / Siemens AG 2017

4 2. Compatibility 2.1. Compatibility with cycle packages 840D sl / 828D as of SW 4.5 SP3 In the following points, the behavior of the cycles has changed when compared to software releases as of SW 4.5 SP3: Technology cycles: - As of 4.5 SP6: Changes in the drilling cycles if no absolute drilling depth is programmed and the incremental drilling depth = 0 or is not programmed either: Alarm 61019, "Parameter DP, DPR defined incorrectly", is now output if DPR = 0 or is not programmed and DP is not programmed. Example cases: CYCLE81(7,5,2,,0) ; Alarm CYCLE81(7,5,2,, ) ; Alarm CYCLE81(7,5,2,0,0) ; absolute DP = 0 applies CYCLE81(7,5,2,0, ) ; absolute DP = 0 applies o As of SW 4.7: Changes in the thread cutting (CYCLE99, CYCLE97) and thread chain (CYCLE98) cycles The behavior for thread synchronization (operation via softkey in JOG) has been aligned to CYCLE 99 in CYCLE97 and CYCLE98. This means thread synchronization is only possible if no transformation, no TCARR and no rotations around X or Y are active. - As of SW 4.7 SP1: Changes to the High Speed Settings cycle (CYCLE832) concerning Top Surface: CTOL output in Top Surface as contour tolerance CTOL output in Advanced Surface as axis tolerance (*root(3)) (compatibility) - As of SW 4.7 SP2 HF1: Change in behavior in the swivel cycle (CYCLE800) or directly with the tool holder: The following machine data must be taken into account: MD $MC_TOCARR_ROTAX_MODE Bit 2 Bit 2 = 0... compatibility, recommended when upgrading software Bit 2 = 1... new function, recommended when commissioning for the first time The Bit 2 = 1 setting means that the control system only calculates a definitive solution when swiveling in the pole position (basic position). Existing NC programs with swivel function must subsequently be checked as the positioning behavior may have changed! - As of SW 4.8 SP1: Until now, the tool holder position was retained when retracting to the retraction position in Z and Z, XY. This sometimes resulted in the software limit position ($MA_POS_LIMIT_MINUS) being violated when a swiveled B axis was in the head, for example, when retracting to the retraction position. When retracting Z and Z, XY to the retraction position, the retraction position entered is now approached in the machine (MCS). This prevents violation of the software limit position. The new behavior has been implemented in CUST_800; the previous behavior can be restored by adjusting CUST_800. Measuring cycles: - As of 4.7 SP4: Functional improvement for workpiece measurement with automatic tool offset: The tool offset is precisely oriented to the tool management statuses Page 4 / 22 Unrestricted / Siemens AG 2017

5 "Tool is active" and "Tool has been in use" These statuses are evaluated even if no tool groups are provided (so-called "replacement tools"). Disabled tools are not offset. In this case, alarm 61404, "Tool offset could not be performed", is output. ShopTurn cycles: - As of 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, it is possible that, during an NC start, one of the alarms 61281, "Starting point of machining outside retraction planes", or 61282, "End point of machining outside retraction planes", is output. In this case, adapt the retraction planes in the program header Compatibility with grinding programs with 802D sl SW D sl grinding programs are not executable without making the relevant adjustments. This is due to the new tool concept (grinding wheels and dresser) Adapting machine manufacturer cycles Change status of CUST cycles between SW 4.5 SP3 and SW 4.8 SP1 The table provides an overview of the changes in the machine manufacturer cycles compared to software versions as of 4.5 SP3 (this also applies to the following SPx and HFx releases). Cycle Function, significance Adaptations after the upgrade CUST_TECHCYC Manufacture cycle to adapt the functions of the technological cycles Includes new functions when compared to SW 4.5 SP3 and 4.7 SP3 CUST_800 Manufacturer cycle for adaptation to the function swivel plane and swivel tool (CYCLE800) Includes new functions when compared to SW 4.5 SP3 and 4.7 SP3 CUST_832 Manufacturer cycle for adaptation of the High Speed settings function (CYCLE832) CUST_MEACYC Manufacturer cycle to adapt functions for measuring cycles CUST_T Cycle is used to track T-preparation after SERUPRO CUST_M6 Cycle is used to track tool change after SERUPRO CUST_MULTICHAN Manufacturer cycle for lathes with several channels CUST_CLAMP Manufacturer cycle for clamping elements CUST_MEAPROT Manufacturer cycle for logging during measuring cycles Includes new functions when compared to SW 4.7 SP2 No change since SW 4.5 SP3 No change since SW 4.5 SP3 No change since SW 4.5 SP3 No change with respect to all previous releases No change with respect to all previous releases No change with respect to SW 4.7 SP3 and higher Page 5 / 22 Unrestricted / Siemens AG 2017

6 Special notes on upgrade For functional entry points and changed functions regarding the individually changed CUST cycles, see the Notes on applying this cycle package section To use the new functions, the cycles must be copied and appropriately adapted by the machine manufacturer (OEM). Note: Generally, the machine manufacturer is advised to copy all CUST cycles with changed functionality with respect to the initial state before the upgrade and then readapt them. Page 6 / 22 Unrestricted / Siemens AG 2017

7 3. Changes with respect to the previous release 3.1. Changes as of software version 4.8 SP1 This section only describes the changes in relation to software release 4.7 SP4, i.e. the ZYKL_840DSL_ cycle packages. New functions, functional changes/expansions, measuring cycles: - Functional expansion, measuring in JOG Calibrate on sphere "Calibrate probe" in JOG has been expanded to include the function "Calibrate on sphere". See the "Notes on calibration on sphere in JOG" section - Functional expansion, CYCLE996 in conjunction with VCS Kinematics measuring cycle CYCLE996 now supports the compensation of rotary axis orientation via VCS. See the "Compensation of rotary axis orientation with VCS and CYCLE996" section Functional changes/expansions, configurable machine and setting data: - New machine and setting data For power display of the axes: MD $MAS_AXIS_MAX_POWER MD $MAS_AXIS_POWER_RANGE Maximum value of the axis power display Display range of the axis power display CYCLE791 New cycle for commissioning nodding compensation: - Functional expansion: The CYCLE791 cycle, which is required for commissioning nodding compensation, has now been integrated into the cycles.cfs cycle package. It is always available regardless of the technology. See section "CYCLE791 New cycle for commissioning nodding compensation" - Functional changes in CYCLE791: The following functional changes have been implemented: o Plunge distance and feedrate changed o Selection of just one track should not result in errors o The number of decimal places for the stiffness has been increased o G commands changed to accelerating distance (G645, etc.) o Depth determination in the cycle now via Z0, Z1, Z2 definitions o MD default values restored again after the end of the program New functions, functional changes/expansions, technology cycles: - Functional expansion, swivel cycle (CYCLE800) for indirectly programming the swivel data set The name of the swivel data set can now also be programmed indirectly via a GUD variable. See section "Notes on the indirect programming of the name of the swivel data set" New functions, functional changes/expansions, measuring cycles: - Functional expansion, measuring cycles Number of calibration data fields for workpiece probes has been increased 40 calibration data fields are now available for workpiece probes. See section "Notes on increasing the number of calibration data sets" New functions, functional changes/expansions, technology cycles: - Functional improvement, block formation in CUST cycles In the CUST_TECHCYC, CUST_800 and CUST_832 manufacturer cycles, the individual block markers have been grouped into blocks for better clarity. There are however no functional changes as a result! See section "Example of block formation in CUST cycles CUST_800" Page 7 / 22 Unrestricted / Siemens AG 2017

8 New functions, functional changes/expansions, JobShop cycles: - In JobShop, transformer data in the cycles is now also supported from description via kinematic chain for the following kinematic types: o Kinematic transformations TRANSMIT, TRACYL o Persistent kinematic transformer TRAANG o TRAORI and tool holder 3.2. Changes from SW 4.8 SP2 This chapter only describes the changes regarding SW release for 4.8 SP1, i.e. for the cycle packages ZYKL_840DSL_ Functional changes/expansions configurable machine and setting data: - New machine and setting data: For display resolution, scaling: MD $MNS_DISP_RES_SCALE Number of decimal places, scaling New functions, functional changes / expansions, technological cycles: - Function expansion, thread cutting cycle (CYCLE99), for improved dynamic performance (User Story ): From SW 4.8 SP2 with NCK H, dynamic performance has been improved when transitioning between thread blocks (G33, G34, G35, G335 and G336). The new blending behavior is now active in CYCLE99. This means that in thread blocks that serve as entry or exit - or as transition element of the thread, the dynamic adaptation has been improved, by using a higher percentage of the block length for the adaptation. After the upgrade, this response is automatically active, if SD $SC_THREAD_RAMP_DISP[2] = -1 (default value). Using SD $SCS_FUNCTION_MASK_TURN_SET bit 5 = 1, the previous response can be restored (compatibility) New functions, functional changes / expansions, technological cycles: - Function expansion, deep-hole drilling 2 (CYCLE830) to include new clearance distance parameter for pilot holes/bores (User Story ): When selecting "with pilot hole", now, using parameter ZPV, a clearance distance can be programmed for the pilot hole. Incrementally, this refers to the depth of the pilot hole, and feed motion starts there. New functions, functional changes / expansions, technological cycles: - Commissioning screens for tool carriers in the Start-up area: The swivel data sets are now displayed and entered under Startup / NC /Transformations. s. Chapter Fehler! Verweisquelle konnte nicht gefunden werden. New functions, functional changes / expansions, JobShop cycles: - Expanded functionality (User Story ): Now, a maximum of 99 TRACYL types are supported (previously only 2). New functions, functional changes / expansions, measuring cycles: - Function expansion, measuring cycles setpoint for calculating the WO can now be selected (User Story ): s. Chapter New measuring versions with setpoint input for workpiece measurement (CYCLE977, CYCLE979) - Function expansion, measuring cycles for measuring corner (CYCLE961): Page 8 / 22 Unrestricted / Siemens AG 2017

9 The confidence range TSA when measuring the corner now refers to the setpoint in the plane (reference point at the corner). Further, the angle reference (alpha) has been extended. s. Chapter Measure corner with angle reference in WCS (CYCLE961) 3.3. Supplementary conditions - The following supplementary conditions apply for the application of the new CYCLE9960: (1) The kinematic description of the machine must be stored in the controller via kinematic chains (including variable units). (2) A machine-specific release is required for the application of the CYCLE Note on measuring on the counterspindle (with CYCLE978): (1) It is assumed that, in order to perform work and measurements on the counterspindle, mirroring is active on the tool axis (Z). (2) It is also assumed that the tool is oriented with regard to the main spindle and counterspindle by rotating it around a B axis using an orientable tool holder. In order to suppress a position change of the tool spindle together with the probe included, set the channel-specific SD55740 $SCS_MEA_FUNCTION_MASK, Bit 1 = 0 when performing measurements on the counterspindle. This means that the function "Coupling of the tool spindle position with a coordinate rotation around the tool axis (Z)" is deactivated. The tool spindle remains at the position specified by the previous swivel cycle CYCLE800. (3) In order to perform measurements on the counterspindle, you must calibrate the main spindle with active G17. - Note on workpiece measurement with mixed technologies (both MD and > 0): A cutting position between 5 and 8 must be entered in the tool offset data of the probe. - Note on tool measurement, turning tools on lathes with Y axis (CYCLE982): To avoid traversing motion of a Y axis when measuring tools, a target position must be entered for the Y axis in the SD54629 $SNS_MEA_TP_TRIG_MINUS_DIR_AX3[n] and SD54630 $SNS_MEA_TP_TRIG_PLUS_DIR_AX3[n] setting data. - Note on "Align edge in the program" (with CYCLE998): "Align edge in the program" with CYCLE998 must always be programmed without specifying a protection zone. - Note on the application of measuring cycles or the MEAS command in test facilities with "all axes in simulation": In a special measuring application (which does not affect a real machine) in SW 4.8 SP1, there is a change in behavior caused by error correction. It only occurs when o all NC axes are simulated o AND the probe is simulated with the aid of MD13230>0 o AND the polarity of the probe in MD13200 = 1. The setting in MD13200 now also acts on simulated probes (MD13230 > 0). The level states of such simulated probes are displayed just as for real probes, now dependent on MD13200 in DB10.DBB107, and are checked before the measuring process begins. Depending on the outcome of the check, alarm may be triggered. To avoid the alarm being triggered, either the specification of the simulated level states in the part program must be aligned with the setting in MD13200, or MD13200 must be adjusted to the level states. - Note on workpiece measurement in the program with correction to the length of a turning tool for SD $SCS_TOOL_LENGTH_CONST <> -18 or 19: Page 9 / 22 Unrestricted / Siemens AG 2017

10 In this special case, the measuring cycle must be called up with the measurement variant "Measure only" and the correction to the length of the tool must be performed by the users themselves. - Note on kinematic measurement (with CYCLE996) when the program is called up by "local. drive" or "USB": No report is generated; the results are only available in the _OVR[n] result parameters of the measuring cycle and can be viewed in the Parameter operating area. (For a description of the relevant values, see Measuring Cycles manual). - Note regarding CUST_800 for specific versions: The following change must be made if a CUST_800 is being used as of SW 4.7 SP4 HF1 or HF2 or 4.8 SP1: Second ENDIF at marker _M47: delete Page 10 / 22 Unrestricted / Siemens AG 2017

11 4. Notes on the application of this cycle package 4.1. Summarizing notes on the CUST_TECHCYC manufacturer cycle New functions Compared to SW 4.5 SP3, the following new functions have been added to the CUST_TECHCYC manufacturer cycle: _M115 After tool preselection (ShopTurn) _M116 At tool change point (ShopTurn) _M117 Before tool change T command (ShopMill, ShopTurn, CYCLE206) _M118 Output of M and H functions after tool change (ShopMill, ShopTurn) _M Start of program (ShopMill program) _M End of program header (ShopMill program) _M End of program loop (ShopMill program) _M End of program (ShopMill program) Functional changes, expansions to existing markers Compared to SW 4.5 SP3, the CUST_TECHCYC manufacturer cycle has been functionally expanded for the following applications: - Position 4th axis after block search (e.g. linear axis of counterspindle, tailstock, back rest) Marker: _M30 - After end of tool change cycle (with tool change) Marker: _M111 - Definition: Coupling of counterspindle/main spindle Marker: _M120 - Definition: Coupling of main spindle/counterspindle Marker: _M Summarizing notes regarding the CUST_800 manufacturer cycle New functions Compared to SW 4.5 SP3, the following new functions have been added to the CUST_800 manufacturer cycle: _M440, _M450 Zero retraction in tool direction (no distance) _M47... Retract axis Z to MCS fixed position before tool alignment _M48... Retract axis Z and then the XY axes to MCS fixed position before tool alignment _M75... Align tool: Deselection _M Positioning of rotary axes for kinematic measurement (call from CYCLE9960) Functional changes, expansions to existing markers Compared to SW 4.7 SP3, the CUST_800 manufacturer cycle functions have been expanded for the following applications: - Automatically remove old and load new swivel head (ShopMill) Markers: _M6 and _M7 Page 11 / 22 Unrestricted / Siemens AG 2017

12 The rotary axes are no longer automatically moved to 0 when the tool holder is deselected in JOG. The behavior of SW 4.5 is thus restored. - Retraction to retraction positions (in Z or Z, XY) Markers: _M41 and _M42 The new behavior in CUST_800 has been implemented at the markers. When retracting Z and Z, XY to the retraction position, the retraction position entered is now approached in the machine (MCS). By making the following adjustment where the deselection of the tool holder is commented out at the following position, the previous behavior (approach position in WCS) can be restored in CUST_800: IF (_MODE==41)OR(_MODE==42) ; TCARR=0 _ALARM=GETTCOR(_LEN,"-T:M"). - Retraction in tool direction when turning on milling machines Markers: _M44 and _M45 and _M47 and _M48 The machine manufacturer must check the specified markers and make any necessary adjustments Functional expansions for swiveling with OEM transformation Depending on the modes to be used, the following markers must be adjusted: _M20, _M21, _M22, _M30, _M57, _M58 and _M59. In these markers, the first 4-axis/5-axis transformation is activated with TRAORI(1) and deactivated with TRAFOOF. These two commands must be adjusted to the corresponding kinematic conditions Example of block formation in CUST cycles CUST_800 Each functional marker has been grouped into a block. Page 12 / 22 Unrestricted / Siemens AG 2017

13 4.3. Summarizing notes on the CUST_832 manufacturer cycle Compared to SW 4.7 SP2, the following new functions (for Top Surface) have been added to the CUST_832 manufacturer cycle: _M_INIT Init CYCLE832 _M_TOP_SURFACE_FINISH Finishing with COMPSURF _M_TOP_SURFACE_SEMIFINISH Semi-finishing with COMPSURF _M_TOP_SURFACE_ROUGH Roughing with COMPSURF 4.4. Summarizing notes on the CUST_MEAPROT manufacturer cycle Compared to SW 4.7 SP3, the CUST_MEAPROT manufacturer cycle functions have been expanded for the following applications: - Changes at the marker _LAB5 MD and are now also taken into account in the measurement report. (MD $MNS_DISP_RES_ROT_WO Display resolution, rotation in NPV and MD $MNS_DISP_RES_ANG Display resolution, brackets) 4.5. Notes on software limit position consideration during workpiece measurement All paraxial measurement functions are now continuously referenced to the axis-specific software limit position in the machine coordinate system. This means if a software limit position is located closely behind a setpoint to be measured, the traversing path for pre-positioning is reduced accordingly. The setpoint can thus still be measured without the traversing path extending beyond the software limit position and the corresponding NCK alarm being triggered. The NC functions "TRAORI" and "Swiveling" may be active. Page 13 / 22 Unrestricted / Siemens AG 2017

14 When measuring in JOG, this function is implemented in all measuring variants. The same applies to all measuring variants in the automatic program which are measured paraxially. This leads to the following error situations: - It may occur that, on account of the path reduction caused by the software limit positions, the measuring range no longer extends up to the measurement object. After several unsuccessful probing attempts, alarm 61401, "Probe does not switch, traversing path limitation through software limit position", is output. - If, on account of the reduction of the measuring range, the probe collides on the infeed axis, alarm 61402, "Probe collision, traversing path limitation through software limit position", is output. - If the traversing path has been limited, an acknowledgeable alarm is displayed prior to lowering on the infeed axis: 62314, "Traversing path limitation through software limit position, collision monitoring has been activated, continue with NC START / abort with RESET" 4.6. Notes on calibration on sphere in JOG The functions are selected via softkey in the machine/jog: "Calibrate probe"/"calibrate on sphere" The following function definitions apply for calibration on sphere in JOG: - The measuring variant requires an SPOS-capable spindle. - The probe types 3D probe (type 710) and mono probe (type 712) can be calibrated. - Collision monitoring is always active. - Calibration is always carried out with calculation of the position deviation. - Positioning is always carried out with "circling around the ball". - A contact angle (starting angle) is always computed. Page 14 / 22 Unrestricted / Siemens AG 2017

15 SINUMERIK 840D sl SW 4.8 SP CYCLE791 New cycle for commissioning nodding compensation CYCLE791 is generated exclusively by the HMI interface in the Commissioning area for the commissioning of nodding compensation. The basic function of the cycle is that paths with varying compensation values for nodding compensation are milled on a rectangular workpiece that can initially be face milled if necessary (selection mode). The acceleration and compensation axes are specified for this purpose, as is the min-max range for the compensation values. Requirements: - Channel is in the RESET state and milling tool must be loaded Basic functionality: - The cycle generates adjacent milling paths on a surface (in a similar manner to face milling), according to its parameterization. - The compensation values are changed for each path After the milling procedure has ended, the user has a number of options which can be selected via the operator screen: o The best milling path is selected HMI transfers its compensation data from the file that has been logged and sets it; o If the milling pattern is still not satisfactory, the surface first has to be "cleanly milled" again (by selecting "face mill cycle" in the cycle) before the procedure for milling the individual paths can be repeated; it is possible to refine the compensation change from one path to the next; Page 15 / 22 Unrestricted / Siemens AG 2017

16 4.8. Compensation of rotary axis orientation with VCS and CYCLE Creating a compensation file for VCS VCSROTVEC_VERIFICATION=0 (standard) The existing /_N_CMA_DIR/_N_VCSROTVEC_SPF file is deleted for the first measuring point and rewritten with the ideal vectors from the tool holder. The VCS file is reactivated. After the measurements, the orientation vectors are calculated and the /_N_CMA_DIR/_N_VCSROTVEC_SPF file is rewritten. The VCS file is reactivated. Example /_N_CMA_DIR/_N_VCSROTVEC_SPF: [ROTV1] [ROTV2] Verifying a compensation file for VCS VCSROTVEC_VERIFICATION=1 The existing /_N_CMA_DIR/_N_VCSROTVEC_SPF file is retained during measuring. After measurement, a new /_N_CMA_DIR/_N_VCSROTVEC_VERIFI_SPF file is created. The file contains the orientation vectors for compensation and the calculated orientation vectors with active compensation. Example /_N_CMA_DIR/_N_VCSROTVEC_VERIFI_SPF: //active compensation for rotary axis orientation [ROTV1] [ROTV2] //measured rotary axis orientation with active compensation [ROTV1] [ROTV2] Page 16 / 22 Unrestricted / Siemens AG 2017

17 4.9. Notes on the indirect programming of the name of the swivel data set The _TC_CHANGE GUD defined in the channel is a string of length 32. This variable can be used to define which swivel data set is called up in CYCLE800 before the CYCLE800 call, regardless of what is programmed in the call-up itself. The _TC_CHANGE GUD variable is reinitialized after each RESET. At the end of CYCLE800, the variable is likewise deleted, which means the _TC_CHANGE variable must be rewritten before each new CYCLE800 call. The change of swivel data set takes place in CYCLE800 after the CUST_800 exit in marker _M40 so that the variable can also be rewritten 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) N80 M0 ;* HEAD_1 is active 1 1 Before each new CYCLE800 call, the _TC_CHANGE variable must be rewritten Page 17 / 22 Unrestricted / Siemens AG 2017

18 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 Programmed supplementary conditions in CYCLE800: The swivel data set specified in _TC_CHANGE is checked for the following characteristics: - The swivel data set to be activated must be enabled - The following parameters must match the swivel data set selected in the mask o $TC_CARR23 (swivel data set type) o $TC_CARR37 (swivel mode, ones digit) o $TC_CARR37 (track selection, ten thousands digit) o The mode set (BIT 6,7) in the mask (axis by axis/solid angle/projection angle/direct) for TC_CARR Notes on increasing the number of calibration data sets The number of calibration data fields used (up to a maximum of 40) must be set in the MD $MNS_MEA_CAL_WP_NUM machine data. NB: Make sure this value can be overwritten again by the importing of an NC archive Notes for measuring kinematics CYCLE996 When normalizing/scaling the 2nd rotary axis of a table kinematic, the corresponding value of vector I3 is set (vector from the axis of rotation of the 1st. rotary axis to the axis of rotation of the 2nd rotary axis or to the reference point of the tool adapter). Before SW4.7 SP4, the "closing" vector I4 was normalized - and this was incorrect. Calling CYCLE996 to calculate the table kinematics must be checked. If necessary, the normalization value of the 2nd rotary axis must be adapted. Page 18 / 22 Unrestricted / Siemens AG 2017

19 4.12. New commissioning screens for transformations and tool carrier The swivel data sets are now displayed and entered using the new commissioning/startup screen forms under softkey "Startup" / "NC" /"Transformations". As a consequence, the "Swivel data" softkey in commissioning/startup now has no function. An overview screen shows all of the available transformations with associated name and type. Data, which were previously displayed in the "Swivel data" screen, now have the TOOL_CARRIER_CLASSIC type. Page 19 / 22 Unrestricted / Siemens AG 2017

20 The swivel data have been combined in a screen, and it is now no longer necessary to toggle between "Kinematics" and "Rotary axis". Page 20 / 22 Unrestricted / Siemens AG 2017

21 4.13. New measuring versions with setpoint input for workpiece measurement (CYCLE977, CYCLE979) New measuring versions CYCLE977 Now, when measuring holes/bores, rectangular pockets, circular and square spigots - as well as grooves and ribs - a setpoint can now be entered for the center point of the object being measured. Just the same as measuring in jog, the correction of a work offset is then calculated and made, referred to this setpoint. When selecting setpoint "no", the measuring cycle responds just the same as before. The correction is calculated referred to the start position in the plane before calling the measuring cycle New measuring versions CYCLE979 When measuring circle segments, a setpoint can also be entered, which is then used as reference when calculating the work offset. Page 21 / 22 Unrestricted / Siemens AG 2017

22 When selecting setpoint "no", the measuring cycle responds just the same as before. The correction is calculated, referred to the programmed center point in the plane Measure corner with angle reference in WCS (CYCLE961) When measuring a corner with CYCLE61, for newly programmed cycle calls from 4.8 SP2, then angle alph0 always acts on the WCS. The response/behavior of existing programs does not change! If CYCLE961 calls from existing programs are recompiled, then for the parameter angle, a selection field "MCS"/"WCS" is also displayed. This is preassigned MCS, which corresponds to the previous response for measure corner. Page 22 / 22 Unrestricted / Siemens AG 2017