HAAS® Alarm 316 — PROBE STYLUS BROKEN
Part of: our HAAS® alarm reference · covering 60 of the most common alarms.
What it means
A probing cycle started but the probe didn't trigger when expected, or started already triggered. The control thinks the probe stylus has been damaged.
Common causes
- Stylus actually broken or bent (most common — check it!)
- Probe battery dead (on wireless probes)
- Probe receiver or transmitter problem
- Probe was moved into something at rapid feed
- Probe activation M-code missing from the program
What to check first
- Inspect the stylus — bent or broken stylus is by far the most likely cause
- Check the probe battery indicator
- Confirm the probe receiver is powered and aligned
Prevention
Programming alarms are best prevented at the post-processor and verification stages. Always verify a new program in single-block mode with rapid override at 5–10% before committing to a full run. Keep a small library of tested macros rather than rewriting logic each job — and comment your variables clearly so the next person (or future-you) can read them.
If you’re still stuck
If you’ve worked through the checks above and the alarm hasn’t cleared — or if it cleared and came back — that’s the point to call. Persistent alarms after a reset usually mean a real component fault, and pushing through them risks turning a simple repair into a bigger one. Keith covers HAAS® breakdowns across the UK with same-day phone diagnosis.
A note on this guide. Alarm wording and numbering can vary by HAAS® machine model and software revision. The descriptions here are written in plain English to help you understand what the machine is reporting and what to check first — they’re not a substitute for the official HAAS® operator manual or for a qualified service engineer’s diagnosis. Always confirm the exact alarm message on your screen and consult your machine’s documentation before attempting any repair.