Diagnose TAP File Editor failures when the file opens oddly, a nest/fix looks wrong, out-of-bounds selection mis-fires, Clip to Machine Limit surprises you, zoom/pan fights you, or the saved .tap misbehaves on the controller.
Not another CAM recompute lecture. Pair this with the TAP File Editor when the UI already “worked” and the result still fails. For the step-by-step workflow use How to Edit, Nest & Fix a TAP/G-code File. For which tool fits which job use G-code/TAP Viewers Compared. This page stays on diagnosis.
Quick Symptom → Fix Map
| Symptom | Likely cause | What to do |
|---|---|---|
| File won’t load / “No cut paths found” | Dialect or structure the parser doesn’t treat as cuts | Confirm G0 Z lift blocks + G0/G1/G2/G3 X/Y moves; re-post from CAM as plain .tap if needed |
| Nest/trim looks wrong after drag/rotate | Wrong cut selected; arcs display as chords; kerf width ignored while eyeballing | Re-select the gold/amber path; check bit diameter; undo (Ctrl+Z) and nudge with arrows |
| “Select Out-of-Bounds” picks too much / too little | Board size vs machine-limit mismatch, or limits off | Set board W/H and machine travel separately; turn machine limit on only when crash-checking |
| Clip to Machine Limit does nothing / clips wrong Y | Machine limit box off; wrong selection; clip is Y-top only | Enable machine limit; Select Out-of-Bounds first; read the clip-line alert before saving |
| Saved file won’t run / crashes / misses stock | Edits moved cuts past travel or off material; units mismatch | Re-check board + machine colors; verify inch/mm toggle matches the controller; dry-run on air |
| Can’t select / zoom / pan feels stuck | Empty selection; pan vs drag mode mix-up; scale extremes | Click empty canvas to clear; wheel zoom; right-drag (or empty left-drag) to pan; reload if needed |
1. File won’t load or parse correctly
The editor looks for cut blocks that start with a G0 Z… retract/lift, then consume following G0/G1/G2/G3 moves that carry X/Y. If it can’t find that pattern, you get “No cut paths found. Is this a valid .tap file?”
- Unsupported or exotic dialect. Post-processors that bury XY inside macros, use only incremental modes without clear Z lifts, or emit non-standard canned cycles may not split into selectable contours. Re-post from CAM as a simple absolute XY .tap when you can.
- Viewer/sim files ≠ edit-ready toolpaths. A file that “opens” in NCViewer or CutViewer can still fail here if it isn’t structured as discrete Z-lifted cuts.
- Wrong file type. Binary, compressed, or machine-proprietary formats aren’t plain G-code text. Save/export as .tap / .nc / plain G-code first.
- Partial programs. Header-only files, tool-change scripts with no XY cutting moves, or probing routines won’t produce selectable cuts — that’s expected, not a corrupted upload.
Nothing leaves your browser during parse. If the alert fires, the file never “half-loaded” onto a server — fix the source text or re-post, then try again.
2. Edited toolpath doesn’t match original intent after nest / trim
Per-toolpath move and rotate only change the contours you selected. Common ways the result diverges from what you meant:
- Wrong cut highlighted. Only the gold/amber selection moves. Overlapping paths look identical until you click — confirm the status bar selected count before dragging.
- Rotate pivots on the selection centroid. Alt+drag (or the rotate degrees control) spins around the selection’s center, not the machine origin. Multi-cut selections rotate as one group around the shared centroid.
- Arcs display as straight segments. G2/G3 are read by endpoints and drawn as chords for editing. Nesting by eye can look tighter/looser than the true arc will cut. After large rotates, spot-check critical clearances in a real simulator if the part depends on arc geometry.
- Kerf not in the mental model. Turn on bit diameter so the stroke width matches the real cut. Nesting “line-to-line” without kerf is how bridges disappear and tabs get skimmed.
- Delete is permanent until undo. Deleted cuts stay in history for Ctrl+Z, but a save after delete writes them out of the new file. Don’t Save as new .tap until the board view matches intent.
If a drag went sideways: Ctrl+Z, then use arrow keys (Shift for fine) instead of free drag for small nests.
3. “Select Out-of-Bounds” false positives / negatives
The button labeled Select Out-of-Bounds (overhang auto-select) marks every non-deleted cut that fails the current boundary checks — board-fit and/or machine-limit, depending on what you’ve enabled and configured.
- False positives (too many cuts selected). Board width/height don’t match the real sheet, or machine travel numbers are tighter than the controller actually allows. Purple “off board” and red “machine crash risk” are different systems — fix the wrong box first.
- False negatives (missed overhangs). Machine limit is off, so crash-zone geometry isn’t checked. Or board size was left at defaults that still contain the bad cut. Turn machine limit on when you care about travel; set board to the actual panel.
- Home zone tint. The unreachable home band is drawn for awareness; don’t confuse it with “selected.” Selection only happens via click or Select Out-of-Bounds.
- Zeroed differently than assumed. The editor assumes X=0, Y=0 at the bottom-left of the board (stock corner zero). If your job was posted with a different origin, board/machine overlays will disagree with floor reality even when G-code is “correct.”
4. Clip to Machine Limit produces unexpected results
Clip to Machine Limit is not a general trim-to-board tool. It requires the machine-limit box on, a non-empty selection, and it clips selected geometry against a Y clip line derived from the machine envelope (top travel), rewriting Y values in the underlying G-code lines.
- Alert: machine limit box is off. Enable it. Clip is intentionally refused against board size alone so you don’t “fix stock” when you meant “avoid a hard stop.”
- Alert: select cuts first. Use Select Out-of-Bounds to gather crash/off-board paths, then Clip — or select manually.
- Unexpected Y after clip. Read the success alert (it reports the clip Y). If that Y isn’t the edge you meant, adjust machine Y-top / home values, undo, and re-clip. Clip does not invent new lead-ins or re-pocket — it only clamps existing points/lines.
- Nothing clipped. Selection doesn’t actually cross the clip line. Re-check with machine-limit coloring before assuming the button failed.
Always Save as a new .tap after clip so you keep the original CAM post as fallback.
5. Exported file doesn’t run correctly on the machine
The editor never sends motion to the controller. Failures after Save as new .tap are almost always geometry, units, or workflow:
- Still off material or past travel. Purple/red warnings on screen become scrap or hard stops on the floor. Clear warnings before exporting.
- Inch vs mm mismatch. The units toggle changes how board/machine numbers and the view interpret coordinates. Your controller’s modal units must match the file’s posted units — flipping the UI toggle does not rewrite every G20/G21 in the program for you.
- Origin / work offset surprise. Moving cuts in the editor moves absolute XY in the file. If the machine still uses the old G54/fixture expectation, parts land in the wrong place even when the relative nest looks perfect on screen.
- Deleted ops still expected by the operator. Removing a bad cut from the file doesn’t update the traveler or setup sheet. Tell the floor which contours are gone.
- Dry-run first. Air-cut or single-block the edited region, especially after large rotates or clip operations.
6. Zoom, pan, and selection issues in the UI
- Select: click a cut (gold/amber). Click empty canvas to clear. Ctrl/Cmd+A selects all non-deleted cuts.
- Move: drag a selected cut. If the cut wasn’t selected first, left-drag pans instead of moving — select, then drag.
- Rotate: Alt+drag a selection, or use the degrees field + rotate buttons.
- Zoom: mouse wheel toward the cursor. If scale feels stuck at min/max, zoom the other direction or reload the page and re-open the file.
- Pan: right-drag, or left-drag on empty space / unselected area.
- Nudge: arrow keys; Shift for a finer step.
- Undo: Ctrl/Cmd+Z for delete, transform, and clip history entries.
If the canvas went blank after a bad zoom, reload, re-open the .tap, and use Fit-style zoom from a moderate wheel range before editing again.
When to stop editing and go back to CAM
Use the editor for reposition, rotate, delete, nest cleanup, and boundary clip of existing cuts. Go back to CAM when you need new geometry, different tools/feeds across ops, true arc-aware verification, multi-axis simulation, or a post dialect this parser won’t split. That’s the split covered in the viewer comparison.
Open the TAP File Editor → · Workflow guide → · Compare viewers →
Built for the Shop Floor