Sinumerik 850T: Troubleshooting SPF83 and Turret Sync

The available program identifies %SPF83 on a Voest WNC 500 S with a Sinumerik 850T. Its arithmetic, repeated drilling moves, dwell commands, and retracts support treating it as a drilling-cycle candidate. The stronger claim that it exactly duplicates standard G83 behavior remains unverified. Two-turret coordination is a separate issue and requires machine-specific channel and M-function assignments.

Separate Confirmed Code from Working Hypotheses

Decode the SPF83 Register Operations

The symbolic comments provide abbreviated register labels, but the full meanings are not documented in the evidence. Use the expressions below to trace actual behavior without assigning unsupported names.

The multiplication by R51 means that changing this register changes three working values together. Do not assume that R51 equals one or represents a particular unit; confirm its calling convention in the machine documentation or existing proven programs.

Trace the Drilling Motion Path

The main drilling path selects G00 G60 G90, positions using R11 and R57, feeds with G01 toward R53, retracts toward R08, and executes G04 F=R00. Another path feeds to R03, executes G04 F=R04, returns to R02, then moves to R08. These operations support a peck or deep-hole drilling interpretation, but the evidence does not define command 440, the coordinate units, or the meanings of the two dwell registers.

R52 = R02 - R03
R57 = R02
R53 = R02 - R01
...
G00 G60 G90 440 R11 R57
G01 440 R11 R53
G00 440 R11 R08
G04 F=R00
...

The subprogram has multiple conditional branches using K destinations and @ commands. Preserve those branches during testing; extracting only the visible G-code moves would remove the step-size, remainder, and loop decisions.

Validate SPF83 Without Assuming G83 Equivalence

1. Record the current machine program, the complete %SPF83 listing, its caller, and the values supplied to R00, R01, R02, R03, R04, R05, R08, R11, R50, R51, and R60.
2. Confirm the coordinate relationship among R02, R03, and R08. The listing calculates travel from R02 - R03 and commands motion to all three coordinates.
3. Calculate the scaled values produced by R51 before motion: R01 × R51, R05 × R51, and R50 × R51. Verify that their signs and magnitudes produce clearance from the fixture and workpiece.
4. Run the cycle with a safety clearance and observe each rapid, feed, dwell, and retract. Confirm that R53 advances toward R03, that retract motion goes to the intended coordinate, and that the loop terminates.
5. Only after the observed path matches the calculated path should the cycle be tested in the hole. Do not populate its registers merely by copying a G83 parameter list unless the machine documentation confirms that interface.

Evaluate Two-Turret Synchronization Separately

An example associated with a Siemens 880TT used N13 [WAIT M, R49, 1, 2] after assigning an M command to the leading axis. The account states that the relevant program-coordination extension must be enabled and that M commands are freely selectable, making the actual assignment machine-specific. This is useful as a configuration lead, not as confirmed Sinumerik 850T syntax.

A different WNC 700 S installation used M2=81 H99=1 as a wait mark for the second turret and M4=81 H99=1 for the first, with successive H99 values such as H99=2. Because this evidence concerns another machine family, do not copy those assignments into the WNC 500 S. First verify the installed coordination option, the channel mapping, the configured leading-axis M command, and the wait-mark implementation. Then test synchronization with both turrets clear of the work envelope and confirm that neither channel passes a wait point before its partner arrives.

FAQ