The operator sees a spot drill miss its expected surface after an apparently normal probing cycle. On the PFH_4800, the X- and Z-axis workpiece coordinates were wrong by nearly the 0.4 in. distance between the probe start point and the expected contact point. The control appeared to store the starting coordinates rather than the coordinates at physical contact. Treat that pattern as a failed measurement chain, not as a normal part-location variation.
What is the screen telling you?
Start with the displayed workpiece coordinate, or WPC, before inspecting hardware. Record the X and Z values before probing, the expected values, and the values written after the cycle. A start-point value written into both axes separates a probe-state or sequence problem from ordinary fixture variation.
| Observed symptom | Likely cause class | Deciding check |
|---|---|---|
| X and Z equal or nearly equal their probing start positions | The cycle saw a trigger before normal travel, captured an invalid state, or did not execute the intended search | Compare the stored WPC with the commanded start coordinates and watch the probe input transition |
| Only Z is wrong and the probe behaves intermittently | Probe holder seating, loose pull stud, spindle-taper contamination, or incorrect running length | Remove and inspect the probe assembly, then verify repeatable seating |
| Several axes shift after a tool change | The tool was clamped before it was fully seated | Observe the tool-change motion and inspect the pull-stud engagement |
| Probe values are correct, but the final WPC is old or unexpected | The probe update was skipped, overwritten, or negated during a restart | Trace the program sequence from measurement through the final offset write |
| Low-signal alarms or intermittent operation occur with contamination | Chips are blocking or weakening the optical path | Clean the optical pickup and verify stable state changes through repeated triggers |
Fixture variation does not explain an error that closely matches the full approach clearance. The 0.4 in. start distance protects the probe during approach, but it also defines the possible error if the start position is accepted as the result.
Check before continuing: Confirm whether the bad WPC matches the probe start point, the previous offset, or a mechanically shifted position. Each pattern sends the diagnosis down a different path.
Does the optical signal change cleanly?
The measurement chain runs from stylus contact through the probe transmitter, optical pickup, interface input, probing routine, and WPC write. Contamination at the pickup can interrupt that chain. Chips were present on the optical pickup when the failure occurred, and the same installation had previously produced low-signal alarms when chips reduced the optical signal.
- Stop the automatic cycle and record the current X and Z WPC values.
- Clean chips from the optical pickup and the probe transmission path without moving the receiver alignment.
- Place the machine in a controlled diagnostic or manual state where the probe input can be observed.
- Confirm the resting state with the stylus untouched.
- Deflect the stylus gently and confirm one clean transition to the triggered state.
- Release the stylus and confirm an immediate return to the resting state.
- Repeat the test from the orientations used during X- and Z-face probing.
A permanently active input can make a probing routine treat the cycle as already triggered, while a missing transition can produce an alarm or continued motion. The exact response depends on the active probing routine and its interface logic. The decisive observation is the control input state at rest, at stylus contact, and after release.
A new battery removes one common source of intermittent transmission, but it does not validate the optical path, receiver input, or interface wiring. If state changes remain unstable after cleaning, inspect the probe indication, receiver indication, interface input, and controller indication in that order.
Check before continuing: The displayed probe state must remain inactive at rest and change once, cleanly and repeatably, when the stylus is deflected.
Is the probe seated at the expected length and position?
A valid electrical trigger can still produce a bad measurement when the probe assembly is not mechanically seated. Inspect the probe holder with the same discipline used for a cutting tool that suddenly changes length.
| Item | Inspection location | Effect on probing |
|---|---|---|
| Chips or damage | Spindle taper and tool taper | Changes the probe axis or running position; contamination commonly produces a smaller, closer error |
| Loose pull stud | Probe holder | Changes running length relative to the stored tool data and can fail intermittently |
| Incomplete clamping | Automatic tool-change sequence and drawbar engagement | Can displace X, Y, or Z substantially if the holder is clamped before full seating |
| Repeatability after exchanges | Probe loaded, unloaded, and loaded again | Reveals an intermittent seating or tool-change timing problem |
Look for witness marks, trapped chips, an unsecured pull stud, and abnormal clamping sound or motion. Observe the automatic tool-change sequence rather than judging it only from the final tool-in-spindle indication. If the drawbar grips the wrong portion of the pull stud, the control can still report a completed tool change while the probe sits far from its calibrated position.
Check before continuing: Reload the probe several times and confirm that its indicated position and measurement result repeat after every exchange.
Did the program execute the intended probe and WPC update?
The tag can be right while the binding is wrong: a correct measured position is useless if the program writes another WPC, skips the write, or later restores an older offset. Mazatrol probing was being used inside programs to adjust WPCs associated with G offsets, so the complete sequence must be traced through both the probing unit and any surrounding EIA logic.
- Identify the Mazatrol probing unit that performs the X-face and Z-face searches.
- Record the target WPC or G offset before the probing unit runs.
- Confirm that the program enters the probing unit during the actual automatic sequence.
- Observe the measured X and Z results before the WPC update.
- Confirm that the intended WPC changes immediately after the update.
- Search the remaining sequence for another offset write, including any
G10lines, that can replace the measured values. - Repeat the trace from every restart point used by the operator.
A restart can skip the probe, repeat an initialization block, or reread an offset assignment. Those paths can negate a valid probing update without generating a probe alarm. Compare the normal-start path with the recovery path after a stop or machine restart.
Check before continuing: Prove that one probe result reaches one intended WPC and remains unchanged until the cutting operation uses it.
Which probing configuration gives the required control?
Both Mazatrol probing and EIA-based probing can update work coordinates. Mazatrol is the direct choice for simple in-program WPC updates because it is quick to configure and fits the existing programming workflow. An EIA probing implementation, including Renishaw Inspection Plus macros, provides a better location for custom acceptance logic when the built-in Mazatrol face routine does not expose the needed tolerance setting.
| Configuration | Best use | Control limitation or advantage |
|---|---|---|
| Mazatrol probing | Simple X- and Z-face measurements followed by WPC updates | Direct workflow, but no identified built-in tolerance parameter for the face routines in question |
| Mazatrol plus comparison macro | Keep the existing probing workflow while rejecting implausible offsets | Adds a programmable comparison and macro alarm around the measured update |
| EIA probing with Inspection Plus | Applications needing more explicit control over results and program decisions | Requires an EIA implementation and validation of the selected macro interface |
For this setup, retaining Mazatrol and adding a comparison macro is the smallest functional change. Moving the entire probing sequence to EIA is appropriate when multiple measured features, richer result handling, or more explicit acceptance decisions justify the programming change.
Check before continuing: Select the configuration that exposes a usable measured result before the WPC becomes available to cutting.
How should the position tolerance stop a bad update?
The parameter book showed tolerance settings for manual measurement and skew, but no identified tolerance parameter for X-face or Z-face probing. A macro comparison can provide the missing guard. Compare each measured offset with a known reference and raise a macro alarm when the deviation exceeds the allowed loading and fixture variation.
Apply the decision independently to each probed axis:
if |measured X - expected X| > allowed X deviation, raise alarm
if |measured Z - expected Z| > allowed Z deviation, raise alarm
only update or release the WPC when both comparisons pass
Place the comparison before any cutting motion that relies on the new WPC. If the control architecture writes the measured WPC before the comparison, preserve the prior value or block cycle continuation when the comparison fails. The operator must see a fault that requires investigation, not a silent continuation with a rejected coordinate.
Set the threshold from measured fixture repeatability plus the legitimate loading allowance. One cited example uses a fixture that repeats within 0.005 in. and sets the limit to 0.006 in.. That is an example, not a universal probe tolerance. Establish separate X and Z limits if the fixture or loading process repeats differently by axis.
A limit small enough to reject a 0.4 in. start-point capture would have stopped the reported failure before the spot-drill operation. Keep the limit wide enough for valid process variation but far below a displacement that can damage the part, tool, fixture, or machine.
Check before continuing: Deliberately present a measured value just beyond the configured limit and confirm that the macro alarm blocks the cutting sequence and prevents acceptance of the bad WPC.
How do you verify the complete repair?
Verify the signal, mechanics, program path, and rejection logic as one commissioning sequence. A few successful cycles after cleaning show recovery, but repeated end-to-end tests reveal intermittent tool seating, optical interruption, and restart-path errors.
- Record the expected X and Z location from a known correctly loaded part or reference.
- Clean the optical pickup and verify the probe state at rest and when triggered.
- Load the probe through the normal automatic tool-change sequence.
- Run the X- and Z-face probing operations while observing the measured results and WPC changes.
- Confirm that the measured positions fall inside the approved axis limits.
- Verify that the cutting program reads the same WPC that the probing cycle updated.
- Run several complete cycles and confirm a fresh, plausible WPC update on every cycle.
- Test the restart path and confirm that it neither skips probing nor overwrites the accepted WPC.
- Force an out-of-tolerance test condition and confirm that the alarm stops the sequence before the spot drill or another cutting tool approaches the part.
Check before continuing: Release production only after normal cycles repeat and every deliberately invalid result is rejected before cutting.
FAQ
Why does a Renishaw probe store the start position?
The control may see the probe as triggered before normal search travel, or the program may skip the search and write an unintended value. Compare the stored WPC with the commanded start coordinates and watch the probe input from rest through stylus contact.
Why does cleaning the optical pickup appear to fix the probe?
Chips can weaken or interrupt the optical signal between the probe and receiver. Cleaning is proven only when the controller then shows stable inactive, triggered, and released states across repeated X- and Z-direction tests.
Why does the WPC change again after a successful probe cycle?
A restart path, skipped probing unit, initialization block, or later G10 offset write can replace the measured value. Trace every offset write from the probing result to the first cutting motion.
How do I prove the probing fault cannot reach the cutting cycle?
Run repeated normal cycles, verify each X and Z WPC update, test every restart path, and inject an out-of-tolerance result. The final verification is an alarm that blocks the spot drill before any rejected coordinate can control cutting motion.