DECODING
GILDEMEISTER
ERROR MESSAGES

1. Write it down in full.

Note the error code and the plain text shown on the display — including the axis or module designation, if given. A photo of the screen is the quickest option. Almost every diagnosis starts with knowing the complete wording.

2. Find the first fault, not the last.

A hardware defect often triggers several follow-up faults at once. Scroll back through the alarm log until you see the first entry that occurred — that is usually the actual cause.

3. Reproducible or random?

Note whether the fault always occurs during the same operation (e.g. during a tool change at position 7), only under load, only with a warm machine — or completely sporadically. This information halves the diagnosis time.

4. Back again after a restart?

If the fault returns immediately after a full reset (main switch off, wait 30 seconds, switch back on), it is rarely a software hang-up. Trial and error is not worth it then — calling us straight away is cheaper.

5. Identify the source of the message.

Pay attention to the module prefix of the message. Controls report faults from different subsystems (drive, axis, hydraulics, tool magazine) and the prefix tells you where to look — the exact code logic is documented in the manual for your control version.