Example - Siemens SINUMERIK 840D sl Function Manual

● MD24720 $MC_TRAANG_PARALLEL_VELO_RES_1 and
MD24770 $MC_TRAANG_PARALLEL_VELO_RES_2
● MD24721 $MC_TRAANG_PARALLEL_ACCEL_RES_1 and
MD24771 $MC_TRAANG_PARALLEL_ACCEL_RES_2
Chained transformations
Machine data which are relevant for chained transformations:
● MD24995 $MC_TRACON_CHAIN_1 and
MD24996 $MC_TRACON_CHAIN_2
● MD24997 $MC_TRACON_CHAIN_3 and
MD24998 $MC_TRACON_CHAIN_4
Persistent transformation
Machine data which are relevant for persistent transformations:
● MD20144 $MC_TRAFO_MODE_MASK
● MD20140 $MC_TRAFO_RESET_VALUE
● MD20110 $MC_RESET_MODE_MASK and
MD20112 $MC_START_MODE_MASK
Not transformation-specific
Machine data that are not transformation-specific. they are not uniquely assigned to a particular
transformation data set or they are relevant even when a transformation is not active:
● MD21110 $MC_X_AXIS_IN_OLD_X_Z_PLANE
● MD21090 $MC_ MAX_LEAD_ANGLE
● MD21092 $MC_ MAX_TILT_ANGLE
● MD21100 $MC_ORIENTATION_IS_EULER
7.8.5

Example

It would be permissible in the following example to reconfigure (write) a machine data affecting
the second transformation (e.g. MD24650 $MC_TRAFO5_BASE_TOOL_2[2]) in block N90,
since writing a machine data alone does not activate it. However, if the program remained
otherwise unchanged, an alarm would occur in block N130, because an attempt would then
be made to modify an active transformation.
Example program:
Program code
N40 TRAORI(2)
N50 X0 Y0 Z0 F20000 T1 T1
N60 A50 B50
Extended Functions
Function Manual, 10/2015, 6FC5397-1BP40-5BA3
7.8 Activating transformation machine data via part program/softkey
M1: Kinematic transformation
Comment
; Select 2nd orientation transformation
489