The required postprocessor is a narrow data-mapping task: insert each hole's X position, Y position, and final depth into a fixed, machine-approved block sequence. Keep cycle identifiers and all other parameters configurable until the recalled sequence has been checked against the machine documentation and a proven NC program.
Define the postprocessor scope
The application covers vacuum holes without cross holes. It does not require cross-hole recognition, oil-pressure control, drilling-unit pressure control, superimposed Z/W-axis calculations, five-axis transformations, guide-bushing compensation, or steady-rest control.
This scope matters because cross-hole recognition is a separate problem. The evidence identifies TDRILL and an additional postprocessor for that function, while standard Tebis does not know which holes have already been drilled. Do not represent cross-hole feed handling as supported by this simplified postprocessor.
Establish the NC data contract
| Input | Required use | Status |
|---|---|---|
| X hole position | X word in positioning blocks and V90 in the cycle call | Variable per hole |
| Y hole position | Y word in positioning blocks and V91 in the cycle call | Variable per hole |
| Final drilling depth | V91 in the G808 block shown in the recalled sequence | Variable per hole |
| Spot-drilling cycle parameters | V90, V91, and any remaining cycle fields | Unspecified; retain as validated constants or configured inputs |
| Remaining G808 parameters | V90, V92, and V93 | Unspecified; do not guess values |
V91 has different roles in the recalled blocks: it carries final depth in G808 and the Y position in G809. Map values by block context rather than treating each V-variable as one global semantic field.
Generate the fixed block sequence
The proposed sequence was recalled from memory, so treat it as a structural template rather than a controller-ready program:
Gxx is explicitly unresolved. Confirm the actual spot-drilling cycle identifier before output generation. Likewise, confirm whether the controller expects signed final depth, because the recalled example used V91=-987.65 but does not establish a universal sign convention.
Implement the workflow without a 2.5D module
- Obtain X, Y, and final-depth data from the CAM operation or another export that is available without the 2.5D module.
- Bind those three fields to the context-specific placeholders in the approved template.
- Repeat the same X and Y values in both G00 positioning blocks and in the G809 call.
- Keep the spot-drilling fields and the unspecified G808 fields fixed only after they have been copied from a proven machine program.
- Reject postprocessor output when X, Y, final depth, or any required validated constant is missing; do not substitute guessed values.
The NCEditor was suggested as a possible way to break paths and cycles into steps, but the evidence does not establish that workflow as complete. It would still require a postprocessor and does not remove the missing 2.5D capability.
Verify the generated program
- Compare the emitted sequence block-for-block with a controller-approved program for the same machine.
- Confirm that both G00 blocks use identical X and Y values and that G809 receives those values as V90 and V91.
- Confirm that G808 receives the intended final depth in its V91 field, including the required sign.
- Verify the real replacement for Gxx and every constant V-parameter against machine documentation or a proven program.
- Validate the meanings and safe behavior of
G01 E0,G80 M5,G808,G809, andG01 E5 Z5on the target control before production release.
FAQ
Which values must the Tebis deep-hole drilling postprocessor generate?
For the stated scope, generate the hole's X position, Y position, and final depth. Insert X and Y in both G00 blocks and again as V90 and V91 in G809; insert final depth as V91 in the recalled G808 block.
Can Tebis handle this deep-hole cycle without the 2.5D module?
The evidence does not confirm a complete CAM workflow without 2.5D. NCEditor was suggested as a possible path-editing approach, but a postprocessor is still required.
Does this postprocessor support cross-hole recognition?
No. The requested scope excludes cross holes; the evidence identifies TDRILL plus an additional postprocessor for cross-hole recognition because standard Tebis does not track which holes have already been drilled.
