Heidenhain Faulty range data alarm: Incorrect probing range data

The TNC detects an invalid or out-of-limits MIN/MAX range in probing/digitizing cycles. It is an alarm from the Program area, and in the catalog it is listed as “Incorrect probing range data”. On the machine you notice it like this: The digitising cycle does not start, FAULTY RANGE DATA message, Coordenadas MIN/MAX incoherentes.

On the shop floor it almost always comes from one of these causes: MIN greater than or equal to MAX, Range outside software limits, RANGE was not defined before MEANDER/CONTOUR. Rule out the most likely one on your machine first, before touching parameters or swapping anything.

Reset tras corregir datos de rango. Resetting without fixing the cause first only hides the problem: Heidenhain Faulty range data trips again and, in the meantime, you keep working with the machine in bad shape.

With the machine stopped and in a safe state, start with these checks: Revisar coordenadas MIN/MAX, Confirm software limits, Define RANGE before the cycle. That alone will tell you whether it is the program or whether you need to raise a maintenance job.

With Heidenhain Faulty range data active, avoid this: Do not widen the range without checking the travel, Do not run it if it could hit the stops. Skipping any of these points is what turns a minor stop into an expensive breakdown.

Normally requires no maintenance. If you are not sure how far it goes, stop the machine and report it: a repeat alarm always works out cheaper than a crash.

It is a stop alarm: the cycle will not continue until you fix the cause. It does not always mean serious damage, but it leaves the machine where it is and you have to check it before running again. Guidance reference. Always confirm the full text in the exact machine/control manual.