D.Electron Z32 CNC-Alarme

D.Electron Z32 Numerical Controller Alarms Complete Listing for Z32 CNC Machinists Programers Setters.

Schwerwiegende Systemfehler

Sollte das Betriebssystem des Z32 eine Fehlfunktion feststellen, aktiviert es einen Systemfehlerzustand und stoppt die NC.
Diese Situation kann an der folgenden Anzeige auf der Befehlszeile erkannt werden:
** errorgen xxxxxxxx
wobei xxxxxxxx ein 8-stelliger Hexadezimalcode ist, der den Fehler beschreibt.
Alle Fehlermeldungen können von Softwarefehlern stammen (da ein Programmierfehler alles tun kann), aber auch auf spezifische Hardwarefehler oder Probleme mit der Anwendungssoftware hinweisen.
Sollte Sollte die Ursache des Fehlers unklar sein, sollte der Benutzer sie sorgfältig notieren (achten Sie auf die Zahl der Nullen, die die Bedeutung des Codes vollständig ändern kann) und D.Electron benachrichtigen sollte D.Electron benachrichtigt werden.
Im Falle eines schwerwiegenden Systemfehlers wird die Fähigkeit aller NCs deaktiviert; die Tastatur funktioniert nicht; und nur sichere Nullfolgen (Nullen) werden über den Link ausgegeben.

Fehler 00000100

Der PC konnte einige obligatorische Programme vor dem nächsten Maschinenzyklus nicht ausführen.
Dies kann bedeuten, dass der Prozessor des PCs zu langsam ist und nicht alle obligatorischen Funktionen ausführen kann.
Es kann auch bedeuten, dass ein schneller nicht programmierbarer Logikteil (MODUL 2, MODUL 4 oder MODUL 8) ist zu lang. Versuchen Sie in diesem Fall (sofern es sich nicht um einen Endlosschleifenfehler handelt) die Logik mit der Optimierungsoption -o neu zu kompilieren und einen schnelleren Prozessor zu installieren.

Fehler 00000110

Der Errorgen 00000110 für schnelle Interrupt-Zyklen ist ein Alarm, der entwickelt wurde, um anomale Situationen zu signalisieren, die derzeit experimentiert werden, und normalerweise erscheint er nie. Sollte diese Meldung erscheinen, benachrichtigen Sie bitte D.Electron.

Fehler 00000120

Der Fehler 00000120 erscheint, wenn Lese- oder Schreibvorgänge in den RAM des PCs übermäßig verzögert werden.

Fehler 00000800

Die vom Benutzer installierte programmierbare ML-Logik hat eine übermäßige durchschnittliche Dauer.
Reduzieren Sie die Logikgröße oder kompilieren Sie sie mit der Optimierungsoption -o oder installieren Sie einen schnelleren Prozessor.

Fehler 00001000

Die vom Benutzer installierte programmierbare ML-Logik dauert mehr als 24 ms. Zyklus.
Wenn keine Endlosschleifenfehler auftreten, reduzieren Sie die Logikgröße oder kompilieren Sie mit der Optimierungsoption -o oder installieren Sie einen schnelleren Prozessor.

Fehler 00001110

Ausschließlich für FlorenZ-Linux-Systeme, Interrupt-Überlappung von 2 ms.
Es wird von einem zu langsamen Prozessor oder (höchstwahrscheinlich) von einem unzureichenden Grafiktreiber verursacht.

Fehler 00001200

Dieser Alarm kann auftreten, wenn eine Simulation des Z32 unter Windows oder FlorenZ durchgeführt wird, wenn endlose Softwareschleifen ausgeführt werden, die den Computer blockieren könnten.
Zum Beispiel erzeugt ein SPS-Fehler, der eine endlose Softwareschleife erzeugt, einen Fehlercode 0000100 eine reale Maschine, kann aber den Computer während einer Simulation vollständig blockieren.
Diese Situationen werden erkannt und erzeugen den Fehler 00001200, sodass der Bediener seine Programme korrigieren kann.

Fehler 00004000

Allgemeiner nicht implementierter Befehlsfehler.
Er kann durch einen Hardwarefehler verursacht werden, der dazu führt, dass der PC den Speicher falsch liest und folglich versucht, fehlerhafte Befehle auszuführen.

Fehler 00004400

Nur in Windows- oder FlorenZ-Systemen möglich.
Der für die Z32-Echtzeitverarbeitung reservierte RAM-Speicher ist zu klein.
Bitte installieren Sie eine aktualisierte Version der „Z32-Treiber“-Software.
Achtung :Zusammen mit der „Z32-Treiber“-Software wird empfohlen, auch die „Z32 für Windows“-Software zu aktualisieren.

Fehler 00004F00

Prüfsummenfehler des Betriebssystems.
Dies weist darauf hin, dass der System-RAM beschädigt ist und daher aller Wahrscheinlichkeit nach ein Hardwarefehler vorliegt.
Es könnte auch bedeuten, dass es einem Programm irgendwie gelungen ist, die integrierten Sicherheitsvorkehrungen außer Kraft zu setzen und das Betriebssystem zu überschreiben reservierter Speicherbereich.

Fehler 00004FF0

Prüfsummenfehler des ML-Logikprogramms.
Es gilt die gleiche Diagnose wie bei errorgen 00004F00.

Fehler 00005000 – 00005FF0

Alarme, die von der SPS generiert werden, um spezielle verbotene Situationen zu verwalten. Weitere Informationen erhalten Sie beim Werkzeugmaschinenhersteller.

Fehler 00008000

Alarmmeldung durch illegale Softwareinstallation. Die installierte Master-Link-Karte wurde nicht aktiviert oder der Aktivierungscode ist falsch.

Fehler 00008001

Bei installiertem Z32 unter NT wird diese Alarmmeldung ausgelöst, wenn als Software-Umgebungseinstellung ein DES107-Master-Link-Board eingetragen wird. Dieses Board kann in einer NT-Umgebung nicht unterstützt werden. Der Alarm erscheint auf der Ereignisanzeige nach der Warnung wegen ungültiger Lizenznummer.

Fehler 0000C000

Es ist die Summe von zwei Alarmen:errorgen 00004000 (illegale Anweisung) plus errorgen 00008000 (illegale Installation).

Fehler 0000C400

Es ist die Summe zweier Alarme:errorgen 00004400 (RAM-Speicher zu klein) plus errorgen 00008000 (unzulässige Installation).

Fehler 00010000

Weist auf eine Softwarefehlfunktion hin, die D.Electron gemeldet werden sollte.

Fehler 00020000

Weist auf eine Softwarefehlfunktion hin, die D.Electron gemeldet werden sollte.

Fehler 00040000

Weist auf eine Softwarefehlfunktion hin, die D.Electron gemeldet werden sollte.

Fehler 00080000

Wird generiert, wenn eine Z32-Softwareversion mit seriellem Emulator installiert ist,
ohne den entsprechenden Schlüssel oder mit einem nicht aktivierten Schlüssel.

Fehler 03000000

Weist auf eine Softwarefehlfunktion hin, die D.Electron gemeldet werden sollte.

Fehler 05000000

Weist auf eine Softwarefehlfunktion hin, die D.Electron gemeldet werden sollte.

NUMERISCHE CONTROLLERALARME

Die Alarme von NC werden im dafür vorgesehenen Videobereich als Code angezeigt.
Der Alarmcode wird über 4 Hexadezimalziffern (0-1-…F) angezeigt.
Die letzten beiden Ziffern geben die allgemeinen Alarme an Kategorie, während die ersten beiden es im Detail spezifizieren.
Im Allgemeinen gilt, je niedriger die Kategorie, desto wichtiger der Alarm; Alarme der unteren Kategorien werden angezeigt, wenn mehr als ein Alarm gleichzeitig aktiv ist.

CN..02 – Initialisierungsalarme

Bei jedem Einschalten führt die Z32 eine Reihe von Prüfungen der internen PC-Schaltung sowie der DOS-Betriebssystemstruktur durch:Sollte eine Anomalie erkannt werden, wird der Alarm CN..02 angezeigt.
In einem solchen Fall In diesem Fall muss der Bediener den Alarmcode notieren und dem Kundendienst mitteilen.
Die folgenden Alarme wurden programmiert:

CN0102 – CMOS DEAKTIVIERT

Erscheint bei schwerwiegenden Systemfehlern errorgen.

CN0202

Fehlfunktion in der Routine zum Speichern der NC-Datenträgerdatei. Dies weist auf eine schwerwiegende Fehlfunktion der Hardware oder des DOS-Betriebssystems hin. Schalten Sie den Computer aus und wieder ein. Beim Neustart wird eine Meldung angezeigt, die besagt, dass die Dateien der numerischen Steuerung möglicherweise beschädigt sind und besondere Sorgfalt darauf verwendet werden sollte, ihre Integrität zu gewährleisten. Wenn die Datei 127 beim Neustart ein „x“ anstelle des „T“ für das Werkzeug auf der Spindel enthält, kann das „x“ einfach gelöscht werden, um die Arbeit wieder aufzunehmen. Es wird empfohlen, alle Werkzeuge in der Werkzeugtabelle zu überprüfen.

CN0302 – ANORMALE LINK-POSITIONSEINRICHTUNG

Zeigt an, dass die in TARAT definierten Achseneinstellungen in Bezug auf Detektor- oder Referenzpositionen in der Verbindung falsch sind. Ein Detektor oder Referenzkanal darf nicht mit mehr als einer Achse verbunden sein, auch nicht wenn er zu einem anderen Prozess gehört.

CN0402 – DREHACHSE INCH EINRICHTUNG FALSCH

Zeigt an, dass der Detektorschritt der Zoll-Rotationsachse über 0,005 Grad liegt. Dieser Alarm kann nur beim Einschalten generiert werden.

CN0502 – ANORMALE Z-LINK-DATENSTRUKTUR

Falsche Einrichtung in der Z-Link-Datenstruktur.

CN0602 – ANORMALE FILTEREINRICHTUNG

Zeigt an, dass die in TARAT definierten Achseinstellungen für Referenzausgangsfilter falsch sind.
Dieser Alarm wird beim Start ausgelöst, wenn derselbe Filter zwei verschiedenen Achsen zugeordnet ist (auch in unterschiedlichen Prozessen) oder wenn Filter erforderlich sind mit einer Herkunftsnummer größer als 16.

CN0702 – MIT Z-LINK VERBUNDENE KNOTEN UNTER DEM SETUP

Im peripheren Glasfasersystem (Master-Link-Karten DE1065 und DE 1075) wird die Anzahl der angeschlossenen Knoten im Setup festgelegt. Wenn die Anzahl der physischen Knoten geringer als die Kalibrierung ist, wird ein CN0702-Alarm ausgelöst.

CN0902 – ANOMALE HILFSSPINDELEINRICHTUNG

Alarm verursacht durch einen Fehler in der Verwaltung von Doppelspindel und Tischspindeln unter G133KA0 – KA5. Das Setup der Hilfsspindel, definiert als Endlosachse mit der logischen Nummer 12, oder das Setup der Tischspindeln sollte spezifikationskonform eingegeben werden, sonst wird beim Start der Alarm CN0902 ausgelöst.

CN0A02 – ZYKLUS/REV FORCING FÜR Z-SER SPINDEL

Dieser Alarm tritt auf, wenn in den Maschineneinstellungen ein nicht mit Strom versorgter Spindeldetektor 2 definiert wurde und der Spindeldetektor über Z-ser.

CN0B02 – UNZUREICHENDER RAM-SPEICHER

Dieser Alarm wird bei der Installation von Z32 unter DOS ausgelöst, wenn der verfügbare RAM-Speicher nicht ausreicht, um die Z32-Programme zu unterstützen (weniger als 16 MB).

CN0C02 – Z-SER ODER Z-STAR:FALSCHER MASTER-LINK

Dieser Alarm erscheint, wenn Z-SER- oder Z-STAR-Einstellungen definiert sind, aber der Master-Link-Typ nicht richtig ist. Beispielsweise ist der Master-Link DE1075/1 definiert, der Z-SER-Abschnitt ist leer und Z-SER-Wandler (oder Referenzen) sind definiert.

CN0D02 – FALSCHE Z-STAR-EINSTELLUNGEN

Dieser Alarm erscheint, wenn die Einstellungen der Z-STAR-Laufwerke nicht konsistent sind.

CN0E02 – FALSCHE EINSTELLUNG:NULL-SUCHE TYP ENDAT FÜR NICHT-ENDAT-ACHSE

Dieser Alarm erscheint, wenn in den Einstellungen eine Endat-Nullsuche definiert ist, aber die relative Achsenplatine (kann nur eine Z-STAR-Achse sein) nicht Endat ist.

CN1002 – FALSCHE KONZENTRISCHE ACHSENEINSTELLUNGEN

Dieser Alarm bezieht sich auf die Funktionalität der konzentrischen Achsen. Dieser Alarm erscheint in der Startphase, wenn die Einstellungen der konzentrischen Achsen nicht den Spezifikationen entsprechen.

CN1102 – PRM[ ] INITIALISIERUNG FEHLGESCHLAGEN

Dieser Alarm bezieht sich auf die PRM[ ] (permanente Parameter) Funktionalität. Dieser Alarm erscheint in der Startphase aus folgenden Gründen:
– Aktivierung der PRM[ ]-Funktionalität mit Masterlink DES107 angefordert (der die PRM[ ]-Parameter nicht unterstützt)
– Dies ist nicht möglich um die CMOS-Datei zu erstellen, die zum Speichern der PRM[ ]-Parameter verwendet wird

CN1202 – FALSCHE EINSTELLUNGEN DER ZYLINDRISCHEN ACHSE

Dieser Alarm bezieht sich auf die Maschineneinstellungen, die die Funktionalität „Zylindrische Achse“ (G149) aktivieren. Dieser Alarm erscheint in der Startphase, wenn eine der Einstellungen bezüglich der Zylinderachse fehlt oder nicht den Spezifikationen entspricht.

CN1302 – ABSOLUTE ACHSE, ACHSENWEG ZU GROSS IN BEZUG AUF DEN ABSOLUTWEG

Dieser Alarm bezieht sich auf Absolutachsen mit Endlagen (linear oder rotatorisch). Er tritt in der Anlaufphase auf, wenn der Achsweg (bestehend aus positivem und negativem Endlagenbereich) gegenüber dem Absolutweg zu groß ist. Numerisch:Dieser Alarm tritt auf, wenn:(Achsenweg)> (0,8 x absoluter Weg).

CN1402 – ABSOLUTE ACHSE, FRAKTIONÄRE ÜBERSETZUNG, NICHT SPEZIELL AKTIVIERT

Dieser Alarm bezieht sich auf Absolutachsen, zyklisch, ohne Endlage. Er tritt in der Anlaufphase auf, wenn der absolute Weg des Wegaufnehmers eine gebrochene (nicht ganzzahlige) Anzahl von Achsumdrehungen enthält. Dieser Alarm kann durch eine zusätzliche Einstellung beseitigt werden.

CN1502 – ABSOLUTE ACHSE, FRAKTIONÄR, ABSOLUTE FAHRT ZU KURZ (<10 ACHSENUMDREHUNGEN)

Dieser Alarm bezieht sich auf zyklische Absolutachsen ohne Wegende, deren mechanisches Übersetzungsverhältnis so ist, dass in einem Absolutweg des Wegaufnehmers eine nicht ganzzahlige Anzahl von Achsumdrehungen enthalten ist. Er erscheint in der Startphase, wenn die in einem absoluten Weg des Gebers enthaltenen Achsumdrehungen kleiner als 10 sind. Der Grund für diesen Alarm liegt darin, dass unter diesen Bedingungen (Bruchverhältnis zwischen absolutem Weg und einer Achsumdrehung) der absolute Weg zurückbleibt muss viele Achsenumdrehungen (mindestens 10) enthalten, um ausreichende Sicherheitsspielräume und Sicherheitszonen zu ermöglichen, um sicherzustellen, dass die Achsenbewegungen nicht zu Positionen führen, an denen der Achsenwandler ein unsicheres Ausgangssignal liefert.

CN1602 – ABSOLUTE ACHSE, FRAKTIONÄRE, ZU KLEINE DISKRETISIERUNG

Dieser Alarm bezieht sich auf zyklische Absolutachsen ohne Wegende, deren mechanisches Übersetzungsverhältnis so ist, dass in einem Absolutweg des Wegaufnehmers eine nicht ganzzahlige Anzahl von Achsumdrehungen enthalten ist. Es erscheint in der Startphase, wenn die Anzahl der „Impulse“, die durch eine absolute Bewegung des Wandlers erzeugt werden, höher ist als das von den internen Formaten der CNC zugelassene Maximum. Beachten Sie, dass in einem absoluten Hub nicht mehr als 231 Impulse enthalten sein dürfen. Wenn dieser Alarm ertönt, überprüfen Sie bitte den Punkt „Impulse pro Umdrehung“ in den Z-Star-Einstellungen.

CN1702 – BESEITIGEN SIE DEN ALARM DES ANDEREN PROZESSES UND STARTEN SIE DANN NEU

Dieser Alarm kommt beim Start, wenn der Initialisierungsvorgang in einer kritischen Phase abgebrochen wird, weil ein Fehler CNxx14 in einem anderen Prozess erkannt wurde. In diesem Fall:
– auf dem ursprünglichen Prozess bleibt der ursprüngliche Alarm CNxx14 bestehen. Dieser Alarm bleibt auch bestehen, wenn der Fehler behoben wird, denn wenn der Initialisierungsvorgang in einer kritischen Phase abgebrochen wird, ist es nicht mehr möglich, den normalen Betrieb wiederherzustellen:Es ist notwendig, AUS und EIN zu schalten.
– bei jedem anderen Vorgang, der Alarm CN1702 kommt:„ELIMINATE THE ALARM OF THE OTHER PROCESS, THEN REBOOT“

CN1802 – FALSCHE EINSTELLUNGEN FÜR UNTERPROGRAMM-ACHSE

Es kommt beim Start, wenn Einstellungen einer oder mehrerer Unterprogramm-Achsen falsch sind.
Gute Einstellungen sollten sein:
– logische Zahl nicht> 12
– zugehöriges Unterprogramm im Bereich 1-98 oder 128-230
– Einstellungen:Rundachse, ohne Wegaufnehmer, ohne Referenzausgabe, ohne Nullpunkt, ohne Nachpositionieren

CN1902 – FALSCHE ERWEITERTE VERWALTUNG FÜR ABSOLUTE WANDLER

Es kommt beim Start, wenn die erweiterte Verwaltung für Absolutgeber für eine Achse angefordert wird, aber ihr Geber:
– kein absoluter Multiturn EDat oder Biss ist
– zyklisch ist und die Anzahl der übertragenen Impulse durch das ZStar-Laufwerk ist keine Zweierpotenz

CN1A02 – SYSTEMDATEI IM ARCHIVPROZESS NICHT VORHANDEN

Bezogen auf Mehrkopfmaschinen. Es kommt beim Start, wenn in einem oder mehreren Archivierungsvorgängen die Systemdateien fehlen (Ursprungstabelle, Werkzeugtabelle, Basisursprungstabelle).

CN1B02 – KEIN Z-LINK-PERIPHERIEGERÄT IN DEN GERÄTEEINSTELLUNGEN DEFINIERT

Es kommt nur in FlorenZ-Systemen vor, wenn kein peripherer Z-Link in den Maschineneinstellungen definiert wurde. Sie kann durch eine spezielle Einstellung in der Datei INI (Adresse 28A30B =1) beseitigt werden.

CNC002 – PROZESS 1 SOFTWAREOPTION

Alarm im Zusammenhang mit den Softwareoptionen. Es erscheint, wenn Prozess 1 aktiviert wird, ohne die richtige Lizenz installiert zu haben, die ihn aktiviert.

CNC102 – PROZESS 2 BIS 5 SOFTWAREOPTION

Alarm im Zusammenhang mit den Softwareoptionen. Es erscheint, wenn die Prozesse 2 bis 5 aktiviert werden, ohne die richtige Lizenz installiert zu haben, die sie aktiviert.

CNC202 – SOFTWAREOPTION FÜR PORTALACHSEN

Alarm im Zusammenhang mit den Softwareoptionen. Es erscheint, wenn die Gantry Axes-Funktion aktiviert wird, ohne die richtige Lizenz installiert zu haben, die sie aktiviert.

CNC302 – POLAR-/SCARA-ACHSEN-SOFTWAREOPTION

Alarm im Zusammenhang mit den Softwareoptionen. Es erscheint, wenn die Polar/Scara Axes-Funktionen aktiviert werden, ohne die richtige Lizenz installiert zu haben, die sie aktiviert.

CNC402 – TCP/IP-ETHERNET-SOFTWAREOPTION

Alarm im Zusammenhang mit den Softwareoptionen. Es erscheint, wenn eine TCP/IP-Ethernet-Verbindung aktiviert wird, ohne dass die richtige Lizenz installiert wurde, die sie aktiviert. Dieser Alarm wird nur ausgelöst, wenn eine TCP/IP-Ethernet-Verbindung mit einem nicht autorisierten Z32 hergestellt wird.
Dieser Alarm behindert jedoch nicht die Ethernet-Verbindung, damit das eingebettete System (das nur in einer vernetzten Umgebung arbeitet) um die Autorisierungsdatei zu erhalten und somit beim Neustart die autorisierte Ethernet-Verbindung aufzubauen.

CNC502 – ZU VIELE ACHSEN

Es tritt beim Start auf, wenn in den Maschineneinstellungen mehr durchgehende Achsen definiert sind, als von der CNC-Hardware unterstützt werden.

CNEC02

Ähnlich wie CN0202. Zeigt einen temporären Datenbereichsfehler des permanenten Speichers an, der beim Start erkannt wurde. Dies kann durch eine falsche Initialisierung des CNC-CMOS-Speichers oder durch ein schwerwiegendes Hardwareproblem verursacht werden.

CNFF02 – MASTER LINK VERALTET, NICHT MEHR UNTERSTÜTZT

Dieser Alarm kommt, wenn die Z32 mit einem veralteten Master-Link vom Typ ISA-Bus ausgestattet ist:DES107, DE1039, DE1065 ab dem Software-Release Z32 T112-1 werden diese Master-Link-Boards nicht mehr unterstützt.
Die letzte Software-Version, die diese Master-Link-Boards unterstützt, ist das T111-4 (jedoch nicht alle Features vorhanden; abhängig vom Prozessortyp).

CN..07 – FlorenZ-Systemalarme

Diese Art von Alarm gruppiert alle neuen Fehler im Zusammenhang mit dem FlorenZ-System, das unter Linux läuft. Diese Alarme kommen von Fehlern in der ETHERNET-, Z-LINK-, Z-STAR2-Kommunikation.

CN0007 – UNBEKANNTER INTERNER TREIBERFEHLER

Interner Alarm:darf nie kommen.
Falls vorhanden, wenden Sie sich bitte an D.Electron.

CN0107 – TREIBER INTERNER FEHLER 1

Interner Alarm:darf nie kommen.
Falls vorhanden, wenden Sie sich bitte an D.Electron.

CN0207 – TREIBER INTERNER FEHLER 2

Interner Alarm:darf nie kommen.
Falls vorhanden, wenden Sie sich bitte an D.Electron.

CN0307 – KOMMUNIKATION MIT MASTER-LINK DEFEKT (TREIBERFEHLER 3)

Zeigt an, dass die Ethernet-Verbindung zwischen der Master-Link-Karte und dem Linux-PC unterbrochen ist.
Die wahrscheinlichsten Gründe sind:
– Die Stromversorgung des Master-Link ist ausgeschaltet
– Die Das Ethernet-Kabel ist nicht angeschlossen oder defekt

CN0407 – TREIBER INTERNER FEHLER 4

Interner Alarm:darf nie kommen.
Falls vorhanden, wenden Sie sich bitte an D.Electron.

CN0507 – TREIBER INTERNER FEHLER 5

Interner Alarm:darf nie kommen.
Falls vorhanden, wenden Sie sich bitte an D.Electron.

CN0607 – TREIBER INTERNER FEHLER 6

Interner Alarm:darf nie kommen.
Falls vorhanden, wenden Sie sich bitte an D.Electron.

CN0707 – TREIBER INTERNER FEHLER 7

Interner Alarm:darf nie kommen.
Falls vorhanden, wenden Sie sich bitte an D.Electron.

CN1007 – 3 ZYKLEN BEI 2 MS VERLOREN

Zeigt an, dass es Kommunikationsfehler zwischen dem Linux-PC und der Master-Link-Karte gibt und dass es dreimal hintereinander nicht möglich war, mit den ZLink-Peripheriegeräten zu kommunizieren.
Dies kommt von schwerwiegenden Kommunikationsproblemen zwischen dem Linux-PC und dem Master -Link-Platine.
Die Ursache kann eine fehlerhafte Ethernet-Verbindung oder starkes elektrisches Rauschen oder ein langsamer Prozessor sein.
Zu beachten ist, dass die Fehler CN1007, CN1107, CN1207, CN1307, CN1407, CN1507, CN1607 , CN1707, CN1907, CN2007, CN2107 (je nach Kommunikationsschwierigkeit) sind einander sehr ähnlich:Sie können sich nach fast zufälligen Regeln austauschen.

CN1107 – ALLGEMEINES ÜBERTRAGUNGS-TIMEOUT

Zeigt eine generische übermäßige Verzögerung bei der Datenübertragung zwischen dem Linux-PC und der Master-Link-Karte an.
Dies kommt von schwerwiegenden Kommunikationsproblemen zwischen dem Linux-PC und der Master-Link-Karte.
Es kann verursacht werden durch eine fehlerhafte Ethernet-Verbindung oder durch starkes elektrisches Rauschen oder durch einen langsamen Prozessor.
Zu beachten ist, dass die Fehler CN1007, CN1107, CN1207, CN1307, CN1407, CN1507, CN1607, CN1707, CN1907, CN2007, CN2107, (alle abhängig von eine schwierige Kommunikation) sind einander sehr ähnlich:Sie können sich nach fast beiläufigen Regeln austauschen.

CN1207 – FEHLERHAFTE KOMMUNIKATION BEIM KOPIEREN DES CMOS-SPEICHERS

Zeigt Kommunikationsfehler während der CNC-Initialisierung an, wenn der CMOS-Speicher gelesen wird.
Es kommt von schwerwiegenden Kommunikationsproblemen zwischen dem Linux-PC und dem Master-Link-Board.
Es kann durch eine fehlerhafte Ethernet-Verbindung oder verursacht werden durch starkes elektrisches Rauschen oder durch langsamen Prozessor. Zu beachten ist, dass die Fehler CN1007, CN1107, CN1207, CN1307, CN1407, CN1507, CN1607, CN1707, CN1907, CN2007, CN2107, (alle abhängig von einer Kommunikationsschwierigkeit) sind sehr ähnlich:Sie können sich nach fast beiläufigen Regeln austauschen.

CN1307 – ÜBERTRAGUNGSZEITÜBERSCHREITUNG 0

Weist auf eine übermäßige Verzögerung im Datenübertragungskanal 0 zwischen dem Linux-PC und der Master-Link-Karte hin.
Dies kommt von schwerwiegenden Kommunikationsproblemen zwischen dem Linux-PC und der Master-Link-Karte.
Es kann ihren Ursprung haben durch eine fehlerhafte Ethernet-Verbindung oder durch starkes elektrisches Rauschen oder durch einen langsamen Prozessor.
Zu beachten ist, dass die Fehler CN1007, CN1107, CN1207, CN1307, CN1407, CN1507, CN1607, CN1707, CN1907, CN2007, CN2107, (alle abhängig bei einer schwierigen Kommunikation) sind einander sehr ähnlich:Sie können sich nach fast beiläufigen Regeln austauschen.

CN1407 – ÜBERTRAGUNGSZEITÜBERSCHREITUNG 1

Zeigt eine übermäßige Verzögerung im Datenübertragungskanal 1 zwischen dem Linux-PC und dem Master-Link-Board an.
Dies kommt von schwerwiegenden Kommunikationsproblemen zwischen dem Linux-PC und dem Master-Link-Board.
Es kann seinen Ursprung haben durch eine fehlerhafte Ethernet-Verbindung oder durch starkes elektrisches Rauschen oder durch einen langsamen Prozessor.
Zu beachten ist, dass die Fehler CN1007, CN1107, CN1207, CN1307, CN1407, CN1507, CN1607, CN1707, CN1907, CN2007, CN2107, (alle abhängig bei einer schwierigen Kommunikation) sind einander sehr ähnlich:Sie können sich nach fast beiläufigen Regeln austauschen.

CN1507 – ÜBERTRAGUNGSZEITÜBERSCHREITUNG 2

Zeigt eine übermäßige Verzögerung im Datenübertragungskanal 2 zwischen dem Linux-PC und dem Master-Link-Board an.
Dies kommt von schwerwiegenden Kommunikationsproblemen zwischen dem Linux-PC und dem Master-Link-Board.
Es kann seinen Ursprung haben durch eine fehlerhafte Ethernet-Verbindung oder durch starkes elektrisches Rauschen oder durch einen langsamen Prozessor.
Zu beachten ist, dass die Fehler CN1007, CN1107, CN1207, CN1307, CN1407, CN1507, CN1607, CN1707, CN1907, CN2007, CN2107, (alle abhängig bei einer schwierigen Kommunikation) sind einander sehr ähnlich:Sie können sich nach fast beiläufigen Regeln austauschen.

CN1607 – ÜBERTRAGUNGSZEITÜBERSCHREITUNG 3

Indicates an excessive delay in the data transmission channel 3 between the Linux PC and the Master-Link board.
It comes from severe communication problems between the Linux PC and the Master-link board.
It may be originated by a faulty Ethernet connection or by heavy electrical noise or by slow processor.
To be noted that the errors CN1007, CN1107, CN1207, CN1307, CN1407, CN1507, CN1607, CN1707, CN1907, CN2007, CN2107, (all depending on a difficulty communication) are very similar one to another:they may interchange following almost casual rules.

CN1707 – FAULTY COMMUNICATION WITH MASTER-LINK

Indicates that too frequently the master-link didn’t receive the answer back from the Linux PC via Ethernet connection.
It comes from severe communication problems between the Linux PC and the Master-link board.
It may be originated by a faulty Ethernet connection or by heavy electrical noise or by slow processor.
To be noted that the errors CN1007, CN1107, CN1207, CN1307, CN1407, CN1507, CN1607, CN1707, CN1907, CN2007, CN2107, (all depending on a difficulty communication) are very similar one to another:they may interchange following almost casual rules.

CN1807 – MASTER-LINK CMOS BATTERY LOW

Indicates that the lythium battery used on the master-link for the CMOS memory back-up is discharged or faulty and must be replaced.

CN1907 – WRONG ETHERNET DATA BLOCK

Indicates that too frequently the master-link received from the Linux PC corrupted Ethernet data blocks.
It comes from severe communication problems between the Linux PC and the Master-link board.
It may be originated by a faulty Ethernet connection or by heavy electrical noise or by slow processor.
To be noted that the errors CN1007, CN1107, CN1207, CN1307, CN1407, CN1507, CN1607, CN1707, CN1907, CN2007, CN2107, (all depending on a difficulty communication) are very similar one to another:they may interchange following almost casual rules.

CN2007 – WRONG TIMING FOR Z-STAR2

Indicates that too frequently the master-link received from the Linux PC Ethernet data blocks in a forbidden time instant (Time dedicated to the transmission Z-Star2) It comes from severe communication problems between the Linux PC and the Master-link board.
It may be originated by a faulty Ethernet connection or by heavy electrical noise or by slow processor.
To be noted that the errors CN1007, CN1107, CN1207, CN1307, CN1407, CN1507, CN1607, CN1707, CN1907, CN2007, CN2107, (all depending on a difficulty communication) are very similar one to another:they may interchange following almost casual rules.

CN2107 – WRONG TIMING FOR Z-LINK

Indicates that too frequently the master-link received from the Linux PC Ethernet data blocks in a forbidden time instant (Time dedicated to the transmission Z-Link) It comes from severe communication problems between the Linux PC and the Master-link board.
It may be originated by a faulty Ethernet connection or by heavy electrical noise or by slow processor.
To be noted that the errors CN1007, CN1107, CN1207, CN1307, CN1407, CN1507, CN1607, CN1707, CN1907, CN2007, CN2107, (all depending on a difficulty communication) are very similar one to another:they may interchange following almost casual rules.

CN2207 – WRONG CONNECTION WITH Z-STAR2 N. 1

Indicates an error in the connection between master-link and servodrives, channel Z-Star2 nr. 1.
This error is mainly originated by hardware problems:servodrive OFF, optical fibre not connected or faulty, heavy electrical noise, faulty servodrive.

CN2307 – WRONG CONNECTION WITH Z-STAR2 N. 2

Indicates an error in the connection between master-link and servodrives, channel Z-Star2 nr. 2.
This error is mainly originated by hardware problems:servodrive OFF, optical fibre not connected or faulty, heavy electrical noise, faulty servodrive.

CN2407 – WRONG CONNECTION WITH Z-STAR2 N. 3

Indicates an error in the connection between master-link and servodrives, channel Z-Star2 nr. 3.
This error is mainly originated by hardware problems:servodrive OFF, optical fibre not connected or faulty, heavy electrical noise, faulty servodrive.

CN2507 – WRONG CONNECTION WITH Z-STAR2 N. 4

Indicates an error in the connection between master-link and servodrives, channel Z-Star2 nr. 4.
This error is mainly originated by hardware problems:servodrive OFF, optical fibre not connected or faulty, heavy electrical noise, faulty servodrive.

CN2607 – FAULTY COMMUNICATION WITH Z-LINK

Indicates an error in the connection between master-link and Z-Link peripherals.
This error is mainly originated by hardware problems:Z-Link peripherals OFF, optical fibre not connected or faulty, heavy electrical noise, faulty Z-Link peripherals.

CN2707 – TIME RESERVED FOR Z-STAR2 TOO LOW

It is a configuration error that never must be present.
If it comes, notify to D.Electron.

CN2807 – TIME RESERVED FOR CMOS MEMORY ACCESS TOO LOW

It is a configuration error that never must be present.
If it comes, notify to D.Electron.

CN2907 – UPDATING OF THE DRIVE FIRMWARE IN PROGRESS…

DO NOT SHUT-OFF THE MACHINE, WAIT UNTIL THIS ALARM CHANGES IN CN2A07 OR WAIT AT LEAST FOR 2 MINUTES
This alarm comes when an updating of the firmware of the digital drives SP-Evo is in progress. It may come at the start-up phase after a replacement of a power drive module or after an updating of the Z32 CNC software, because at the CNC start-up the firmware of the drives is checked and, if necessary, updated automatically.
This alarm is replaced by the alarm CN2A07 when the updating is completed.
The time duration of the updating is normally terminated in less than 2 minutes. After this time, please restart and try again, and if this alarm doesn’t disappairs, call D.Electron

CN2A07 – UPDATING OF THE DRIVE FIRMWARE COMPLETED, PLEASE RESTART

This alarm comes when an updating of the firmware of the digital drives SP-Evo is correctly finished. It may come at the start-up phase after a replacement of a power drive module or after an updating of the Z32 CNC software, because at the CNC start-up the firmware of the drives is checked and, if necessary, updated automatically.
Please restart the system to activate the new firmware.

CN..08 – Z-Star Alarms

These alarms appear when errors are detected in the connection (optical-fibre link) between the master-link and the Z-Box.
The first two characters of the alarm code contain the map (8 bit map, where 8 is the maximum number of connectable Z-Box’s) of the Z-Box’s that are not communicating in the right way with the master-link.
For example, is there are two Z-Box’s, the following errors can appear:

CN0108 – ZSTAR:CONNECTION ERROR TO ZBOX NR. 1

This alarm appears when the first Z-Box is not communicating in the right way with the master-link.

CN0208 – ZSTAR:CONNECTION ERROR TO ZBOX NR. 2

This alarm appears when the second Z-Box is not communicating in the right way with the master-link.

CN0308 – ZSTAR:CONNECTION ERROR TO ZBOX NR. 1,2

This alarm appears when the first and the second Z-Box’s are not communicating in the right way with the master-link.

The connection error can be caused by hardware problems, like not connected or defective optical-fibre, failures in the peripheral boards contained in the Z-Box, etc.
Further details can be found in the PLC variable HHTIMES (see the Programmable logic manual).

An alarm not related to a Z-Box is also possible:

CN0008 – Z-STAR:SLOW RESPONSE TO REAL-TIME SYSTEM

This alarm appears when the real-time PC shows a slow response to the very stringent real-time requirements of the Z-Star system.
It may be due to PC mother-board, BIOS settings or software drivers not compatible with Z-Star.
To help to eliminate the error, please communicate to D.Electron the value of the PLC variable HHTIMES[8]. It contains some further detail useful to D.Electron.

CN..09 – Link alarms

The OS detected a problem in the peripheral connection link; this may be either hardware or software generated.

CN0009

Link closing with incorrect fiber optics. It is an unstable alarm condition associated to sporadic alarms. This message appears in the case a fiber optic link to peripherals has not been closed correctly, i.e. when the fiber optic end has not been cut perfectly on some node, or when there are strong optic losses, e.g. as a result of fiber crushing or too small bending radiuses.

CN0109

Indicates a malfunction in the peripheral connection link. It may be caused by electric interference or a hardware fault in the connections, the PC or some of the peripherals.
Resetting the PC this error should disappear. If it happens only very rarely, it could be tolerated (to give an idea, once a month should not be tolerated).

CN0209

Link starts with control register unwritten (slow processor).

CN0309

The same as CN0209.

CN0409

Parity error

CN0809

Frame error (bit longer than it should)

CN1009

Slow link (the ring is probably open)
The following codes may be compounded:CN0209 – CN0409 – CN0809 – CN1009:
CN0609 02 + 04
CN0A09 02 + 08
CN0C09 04 + 08
CN0E09 02 + 04 + 08
CN1409 04 + 10
CN1C09 04 + 08 + 10
etc.

CNFF09 – Z-STAR:WRONG Z-LINK BEHAVIOUR

Error in the DE1108 (Z-Star) board:the Z-Link in not working in the right way with loss of communication cycles.

CN..10 – CMOS alarms

The alarms type CNxx10 refer to the permanent CMOS memory errors.
They may be classified in two sub-types:
– Alarms type CN0x10 (the first character following “CN” is the number zero)
– Alarms type CNyx10 (the first character “y” following “CN” is different from zero)

Alarms type CN0x10
They are generated by four basic types of alarm:CN0110, CN0210, CN0410, CN0810 (see below).
Due to the fact that one or more of these basic alarms may be present at the same time, an error CN0x10 will result, where “x” is an hexadecimal number (0, 1, 2 ,…, 8, 9, A, B, C, D, E, F) generated by the sum of the four basic alarms 1, 2, 4, 8.
Examples:
CN0F10 is generated by the simultaneous presence of all the alarms,
CN0710 is generated by the alarms CN0110, CN0210 e CN0410…
Normally the simultaneous presence of more than 1 alarm of the type CN0x10 is originated by battery problems (the battery is used for the CMOS memory backup in the master.link board), or by a missed CMOS initialization.
As the alarms CN0x10 represent CMOS memory errors, they permanently last, even if the CNC is turned OFF and ON.
To eliminate these alarm, the most efficient mode is to reinitialize the CMOS memory.
But this operation will destroy all of the data memorized in the CMOS memory. If this is not wanted, the operator may correct manually the CMOS errors and subsequently eliminate the alarms CN0x10 with the following procedure:
– launch the internal CMOS files editor (activity 5)
– write the string “CNXX10 OFF”
– press Enter
– press RESET
Example:
5 NUMCAT:CNXX10 OFF
Warning:the string must be exactly as shown:
– one (and only one) blank to separate the fields
– no any additional blanks nor at the beginning, nor at the end

CN0110 – Service CMOS memory error

Indicates that upon power up, the service CMOS (which contains the ML logic’s permanent data, dynamic axes setups and other data) has become corrupted and therefore
unreliable.

CN0210 – Error:Sequence files Z32

Indicates concatenation errors in the Z32 files. As result of this error entire sections of one or more Z32 files can be lost.

CN0410 – Z32 file checksum error

Indicates that one or more Z32 files had a checksum error upon powering on. The area subjected to checksum error will be replaced by diesis marks ####…

CN0810 – Error:parameters PRM[ ]

It is shown in the start-up phase for indicating errors in the PRM[ ] parameters saved in the permanent memory.

Alarms tyep CNyx10 (where “y” is different from 0)
They are alarms showing errors in the CMOS memory management.
They may not be eliminated through the editor procedure “CNXX10 OFF”.

CN1010

Z32 files are corrupted; this indicates an inconsistency in the Z32 files memory.
To restart it is necessary to turn the NC off and on again. This may have to be done twice to get rid of the alarm.
Should this alarm be triggered, carefully check file integrity before restarting and always notify D.Electron.

CN1110

The same as CN1010

CN1210

The same as CN1010

CN1310

The same as CN1010

CN1410

The same as CN1010

CN1510

The same as CN1010

CN..12 – Axis detector alarms

The Z32’s transducer system is equipped with self-check circuits capable of detecting:
– power faults or detector output signal anomalies;
– step loss due to excessive speed.
– abnormal position coming from an absolute multi-turn rotary transducer
In these cases the processor is notified that the transducer’s data are no longer reliable and therefore does not allow axis movement. The Z32 subsequently triggers the CN..12 alarm.
The first alarm code’s character details the memorized anomaly type:
1 =overspeed
2 =power
3 =both power loss and overspeed
4 =absolute multiturn rotary encoder with abnormal input position
The second alarm code character (x) indicates the logical number of the axis for which the alarm has been generated.
To eliminate the alarms 1-3 the operator must execute the activity 7 (ZERO).
To eliminate the alarm 4 (normally coming only when installing the machine) the installer may:
– extract the encoder and rotate it to a normal position
– or, better, activate the advanced management of absolute multiturn transducer of this axis
Should more than one axis be in alarm mode, the code displayed is the one referring to the axis with lowest logical number, and switches to the next available code when activity 7 (zero restart) is executed.
Any CN..12 alarm is immediately displayed upon power on, even if the alarms are referred to axes either set up as “not live”, or indexed ones.
Examples:

CN1x12

Indicates an overspeed alarm (likely causes:electrical interference, false contacts or glitches, excessive vibration or speed).

CN2x12

Indicates a transducer alarm connected with its power source (likely causes:battery has gone flat, electrical interference, false contacts or glitches).

CN3x12

Indicates a transducer alarm for both power source and measured speed (likely causes:
very strong electrical interference, false contacts or glitches, battery gone flat or malfunctioning).

CN4x12

Indicates that the multiturn absolute transducer (EnDat or Biss) outputs an abnormal position. To eliminate it:
– extract the transducer and rotate it to a normal position
– or better, change the settings to activate the advanced management of this transducer

CN..13 – Axis movement alarms

They are alarms connected with the axis movements’ handling and other events detected in real-time, independently from the part–program flow. The Z32 continuously monitors the axis quotas, as specified by the machine setup, both with machine standing by and operating.
If the axes do not follow the desired quota closely enough (as defined in the system setup) the NC triggers alarm CN..13.
CN..13 is also triggered in conjunction with other axis movement – related alarms and other events.
In particular:

CN0013

Excessive error during a movement. This may be due to:
1) incorrect circular profile traits programming where a segment’s beginning does not coincide with the previous’ ending.
2) one or more machine axis did not follow NC’s commands with enough precision.
This may depend from a speed variator fault, or from mechanical hard points during the axis run, or from excessive work speeds. Verify the programming before everything else, and anyway, before contacting the technical support, display pursuit errors to know which axis caused the error (see chapter “Operating Modes”, paragraph “Special Displays:Axes and Axis errors”).
The trigger threshold for this error depends from the corresponding setup parameter (normally a few millimeters).
This error is forced by the NC’s OS in various occasions, e.g. during some external program’s execution:programmable logic installation forces a CN0013 error.

CN0113

Excessive error during positioning. This indicates an error which took place during the final positioning phase, or on an axis that should have been kept still. It appears normally if the machine axes are moved through manual keyboard controls without NC’s intervention. To locate which axis triggered the error, pursuit errors must be displayed (see chapter “Operating Modes”, paragraph “Special Displays:Axes and Axis errors”).

CN0313

The processor sent to the axis motion controller an incorrect command. This is an internal alarm which should NEVER trigger.

CN0413

During a blocking/unblocking procedure, the logic kept FEED HOLD longer than five seconds. Consult the machine tool’s manufacturer.

CN0513

Relative to a measure movement in G61. After making contact, the feeler retracted to movement beginning without contact interrupting, or, the contact was already established before the feeler started moving. It may depend from a programming error (a measure movement has been programmed without detaching the feeler) or from a hardware fault (the feeler always reports contact). See also the programming manual.

CN0613

Relative to a measuring movement en G61. It comes if, after the first touch and its release, during the second search the axis, instead of going forward toward the piece, goes back past the point where the movement begun. It is a very rare alarm, due to uncertain measuring probes with multiple commutating fronts. If it comes frequently, inform D.Electron.

CN0713

G63 overshoot. During G63 tapping or G33 threading, this alarm is triggered if the axis overshoots the endpoint of more than the set up quantity, because the chuck inversion is not fast enough or because the tapping movement is inverted due to an incorrect rotate direction recognition when the movement started.

CN0813

Copying buffer is full. While copying, the Z32 uses an accumulation buffer where data are stored before being transmitted to the PC; this alarm indicates that the buffer is full because the PC (external, connected through a serial port, or the Z32 itself) is not reading data fast enough or at all.

CN0913

Analog feeler deflection out of range. Indicates that the analog feeler’s deflection is excessive, beyond programmed emergency deflection if it happens during a G111S movement, or beyond setup emergency deflection in the other cases (manual feeler movement). This alarm appears also when height control is active (G146), if during a movement the sensor distance from the surface is smaller than the sensor negative tolerance.

CN0A13

Emergency quotas exceeded during copy (G111).
This alarm appears also when height control is active (G146), if the maximum deviation from the programmed surface (symmetrical in positive and negative way) is exceeded.

CN0B13

Feeler lost contact from model during copy (G111). This alarm appears also when height control is active (G146), if during a movement the sensor distance from the surface is greater than the sensor positive tolerance.

CN0C13

During a G111S copy init, the movement ended without model contact ever being made.

CN1013

“Live” axis anomaly in a SCARA manipulator:both axis couples, physical and linear virtual, are alive (e.g. if the couples VW and XY are both defined live, or both XY axes are not defined live).

CN1113

Negative W axis in a SCARA manipulator. A SCARA manipulator’s peripheral axis assumes a negative value during movement.

CN1213 and CN1313

Alarms relative to errors in DNC transmission from a host using codos type 16 commands (e.g. ZTERM).
The Z32’s OS monitors some pointers to the DOS files provided by the host, and triggers an alarm if these behave abnormally.
In particular:
– if the number of characters transmitted by the host (displayed in command Ris 6) does not equal the number of characters received by the Z32, a CN1213 alarm is triggered.
– if the host’s DOS file pointer (displayed in command Ris 5) is incremented by more than 1450 characters, an alarm CN1313 is generated.
Keep in mind that CN1313 alarm may be issued if the file to be transmitted contains a large number of empty lines. Reason:
– the maximum number of characters the host may send at the same time is 1024.
– for each row, a LF character is cancelled from the source file data (LF=0A hex; the “end of line” character is actually doubled under DOS, being made up of CR and LF characters, while the Z32 only receives the CR).
– Therefore each packet transmitted by the host may be at most 426 rows long.
The limit of 426 rows may be exceeded only if the source file contains many empty rows (even if all rows had only two characters plus CR it couldn’t be possible to exceed 426 rows).

CN1413

It is a protection in the handling of polar axes, to avoid possible operation anomalies too near to the spin center. If during the movement the distance from the center becomes less than 5 mm, an alarm CN1413 is triggered.

CN1513

The CN1513 alarm indicates an anomalous situation where machine axes are interpolated but not “alive”. This may happen when a movement is requested from a non-alive axis too near to the positioning threshold, thus making it move inside and outside the threshold (e.g. because of an axis quota oscillation). A typical example is that of an axis (rolling table) which, during blocking, has a slight movement that brings it near the allowed positioning error, or from which a movement is required which is slightly less than the positioning threshold.

CN1613

The CN1613 alarm signals that the ZSER ring is interrupted.

CN1713

Normally this alarm never appears. Should it appear, please notify D.Electron.

CN1813

The CN1813 alarm is triggered whenever, while sending $% type DNC part-programs (on a serial line), there is a data protocol transmission error, or a block error.

CN1A13

The CN1A13 error appears on machines with process lock under the following conditions:
if one of the related processes triggers an alarm during the lock cycle, the other processes that must interrupted immediately generate this alarm too.

CN1B13

The CN1B13 error appears on machines with process lock under the following conditions:
if one of the master/slave processes is triggered unexpectedly (e.g. when pressing the reset button) the other master/slave process generates this alarm too.

CN1C13

The CN1C13 alarm communicates that at least once, the AT data reading has been carried out with excessive delay (telegrams from the Z-SER linked drives to the Z32 CPU).
As a consequence, this may provoke faulty axis readings (e.g. repeated measures), and therefore faulty motions.

CN1D13

The CN1D13 alarm communicates that at least once, the MDT data writing has been carried out with excessive delay (telegrams from Z32 CPU to the Z-SER linked drives). As a consequence, faulty speed measures may be provided to the drives, therefore leading to faulty motions.

CN1E13

MU type memory alarm. The CN1E13 alarm is triggered whenever a sporadic MU alarm occurs that has not been stored by the PLC:this alarm appears – even for a very short time (a logic cycle) – and then disappears.

CN1F13

This alarm is released when – in the variable pitch threading function (G34/G35) – a pitch lower that or equal to zero is obtained as a consequence of a K decrease (thread pitch).

CN2013

This alarm is released when the NOT live axes to be monitored are outside their position beyond the admissible tolerance limit.

CN2113

PC HARDWARE TOO SLOW.
This alarm appears when the hardware of the PC where Z32 is running is not sufficiently fast for Z32 and some Z32 functionalities can be compromised.

CN2313

This alarm refers to the PCL function FFCOUPLE, used for coupling axes (a slave axis follows a master axis). This alarm appears when requesting a coupling procedure when the slave axis is alive. If the slave axis is alive, the coupling doesn’t takes place and a CN2313 alarm appears both on the master axis process and on the slave alive axis process.

CN2413

This alarm refers to the PCL function FFCOUPLE, used for coupling axes (a slave axis follows a master axis). This alarm appears when the following error of the slave axis is greater than the maximum following error set in the axis settings. In this case, the movement stops and a CN2313 alarm appears both on the master axis process and on the slave alive axis process. For more information, read the specific machine documentation.

CN2513

This alarm refers to the PCL function FFCOUPLE, used for coupling axes (a slave axis follows a master axis).This alarm appears when there is a position transducer error on the master (or the slave) axis and the master (or the slave) axis is defined with zero setting in the settings. In this case a CN2513 alarm appears both on the master axis process and on the slave alive axis process.

CN2613

This alarm refers to the PCL function FFCOUPLE, used for coupling axes (a slave axis follows a master axis). This alarm appears when the master axis (or the slave axis) is in the “zero setting” procedure. The alarm appears both on the master axis process and on the slave alive axis process.

CN2713

The CN2713 alarm appears when the writing procedure of a PRM[ ] parameter inside the CMOS memory was not successful.

CN2813

This alarm appears when programming a movement involving more that 5 interpolating axes while it is active a function not compatible with movements involving more that 5 interpolating axes.

CN2A13

This alarm appears (on all the active processes):
– in the case Z-Star, if one or more peripheral boards (ENC, PWM) have faulty communication with the CNC
– in the case Z-Star2:if one or more servodrives have faulty communication with the CNC
To know the faulty unit:
– in the case Z-Star, read the PLC variable HHBOARDALARM[0] (bit map of the faulty boards installed in the Z-Box 0 to 3) and the variable HHBOARDALARM[1] (bit map of the faulty boards installed in the Z-Box 4 to 7)
– in the case Z-Star2, read the PLC variable HHBOARDALARM[0] (bit map of the faulty servodrives 0 to 32).
The alarm CN2A13 is eliminated by a simple CN RESET if the board error has been removed.

CN2B13

This alarm refers to the G155 (raster-type laser printing). It comes when the mass-memory access (hard-disk) is too slow (printing data not available)

CN2D13

This alarm refers to the G155 (raster-type laser printing). It comes when it is programmed a parameter #P lss than zero when the printing mode is mono-directional.

CN2E13

This alarm may come when in the machine there is an absolute axis, without end-of travel (cyclic axis) and the absolute travel of the motor generates a non-integer number of axis turns. This is a “critical” axis, were the available number of turns in the same direction is limited. This alarm comes if this number is surpassed (in other words, the absolute axis is over ½ of its travel). Please move back manually the axis, so to conduct it in a safe zone.

CN3013

Alarm related to the Profibus management. It comes at turn-on if the Profibus interface boards doesn’t activate in 5 seconds. Probable causes:wiring error or board missing.

CN3113

Alarm related to the Profibus management. It comes at run-time if the Profibus INPUTS are not refreshed for more than 48 mS. Probable causes:uncertain or interrupted connection to the Profibus peripherals.

CN3213

Alarm related to the Profibus management. It comes at run-time if the Profibus OUTPUTS are not refreshed for more than 48 mS. Probable causes:uncertain or interrupted connection to the Profibus peripherals.

CN3313

Excessive following error for gantry system defined by machine settings (Note:the PLCdefined gantry system has a different alarm code). It comes if the following error of the gantry slave axis becomes higher than the “Tolerance when moving” defined for the slave axis in the machine settings.

CN3413

Excessive following error for gantry system PLC-defined (Note:gantry system define by machine settings has a different alarm code). It comes if the following error of the gantry slave axis becomes higher than the “Tolerance when moving” defined for the slave axis in the machine settings.

CN3513

Spindle head has undefined state. This alarm comes in machines equipped with headexchanging system if a CN activity is requested (Automatic, MDI, JOG) before the PLC has defined what head is installed.
Probable cause:the head exchanging system is not well defined or corrupted.

CNCx13

A CNCx13 alarm (x =logical number of alarmed axis) is triggered when permanent formulas are active and an axis exceeds 8.000.000 detector steps relative to the current origin. To give an idea, this corresponds to about 4 meters (12 feet) with the most discretized (i.e. sensitive) detectors the Z32 can handle. The alarm is also released in the case that one of the linear axes XYZ exceeds the limit of 134,217,728 detector steps (referred to the current origin) with G118NHR1 active:with the most sensitive detectors that can be controlled with the Z32, this measure corresponds to about 72 metres.

CNDx13

A CNDx13 alarm (x =logical number of alarmed axis) is triggered when a machine axis is moving with a different speed than what was required by the NC. The NC integrates the speed imposed to the axis and determines the space this must cover, comparing it with the detector’s report; if they are not equal, the NC triggers a CNDx13 alarm. The alarm is active on both continuous and indexed axes.

CNEx13

Where x is the logical number of the continuous axis which triggered the alarm. During the execution of a movement with RTCP, «…» permanent formulae, or tracing, the axis motion controller detected that the axis got dangerously near the end of run. For example, CNE013 indicates end of run error on the axis with logical number 0 (normally the X axis)..

CNFx13

Where x is the logical number of the continuous axis which triggered the alarm. During the execution of a movement with RTCP, «…» permanent formulae, or tracing, the axis motion controller detected an excessive speed on the axis. For example, CNF113 indicates overspeed alarm on the axis with logical number 1 (normally the Y axis).

CNFF13

Error forced after execution of activity 8, speed controlled axis motion. The alarm is automatically cleared upon activity exit.

CN..14 – Machine programming and usage alarms

These alarms indicate a programming error, a program permanent memory storage fault, or an incorrect usage of some activities.
They are usually accompanied by a plaintext explanation on the command line.
The first part of the row where the error was detected precedes the explanation on the command line.
All allowed error messages are listed below.

CN0214 – OUT OF MEMORY

Available program memory has no room available for the requested write operation(s). It is necessary to erase some programs, archiving them on floppy, to make room.

CN0914 – CMOS ERROR …..

Indicates that an error occurred in numerical controller file manipulation. The CMOS error code has the following meanings:
1 too many files open, or file already open;
2 file is not open;
3 pointer beyond end of file;
4 memory full;
5 reading beyond end of file;
6 file not found;
7 file already exists;
13 internal formal error;
14 attempt to read and write on the same file;
20 internal file concatenation error;
21 CMOS variation memory full;
22 physical write into CMOS memory did not terminate successfully.

CN1914 – RESTORE TOOL

A block search has been done and the tool in the chuck is different from the one that should be there at that point of the program.
It is necessary to switch to semiauto mode, change the tool and repeat program choice and block search.

CN1A14 – AXIS MOVEMENT ATTEMPT DURING ZERO SETTING

An attempt has been made to launch the jog mode, or an automatic program or a semiautomatic movement, during axis zero setting.

CN1C14 – MISSING %

An attempt has been made to run a main program or a subprogram (or fixed cycle or special M) which has no leading percent sign. With software versions dated after October 4th, 1993 the “%” symbol is no longer mandatory at the beginning of a part program.

CN1D14 – PROGRAM ERROR

The program row being analyzed (showed on the command line before the error message) contains an error:
– undefined G
– excessive M
– incorrect parameter name
– incorrect arithmetical expression
– some other syntax error
The character after the one which triggered the error, if it is inside the displayed part of the row, is shown in inverse video to help locating the error.
If no shown character is displayed in inverse video, this means that the row is too long and the error is contained in the row section that does not fit on the display.

CN2414 – RETURN ERROR

It is an error message related to a return from a series of rows, which should never happen. If it does, notify D.Electron.

CN2514 – BASE ORIGINS ERROR

Base origins are not correct; the file containing the current process’ base origins is missing, or is in memory error, or does not contain the base origins of all of the machine axes.

CN2614 – ADDITIONAL ORIGINS ERROR

Additional origins are not correct; the file where such origins are defined is missing or is in memory error, or the program recalled an additional origin which was not defined in the process origins’ table nor in any local section.

CN2714 – SETUP IMPOSSIBLE

A G111T (copy mode analog feeler setup) has been programmed and the values returned are not correct. This alarm can also appear during the automatic axis setup (activity 11) when detected values are out of tolerance limits. This alarm can also appear during the G125 (axes setup for high speed) if exceptional movement conditions leads to impossible axis setup.

CN2B14 – INCOMPATIBLE PROFILE

During a radius correction outlining the NC has found a profile which can not be executed.
For more details check the programming manual.

CN2C14 – INCOMPATIBLE PARAMETERS

A profile block has been programmed with a wrong parameters combination (typically geometrical ones – quotas, center, radius…). Refer to the programming manual.

CN2D14 – TOO MANY SUSPENDS

The transient memory available to the Z32 has been filled. This should never happen; notify D.Electron, if possible including the listing of the part-program which causes the error.

CN2E14 – TOO MANY SUBROUTINES

A subroutine call (GON..-N.., GOP.., special Ms, fixed cycles, permanent subprograms, G110, DO cycle) has been made which exceeds the maximum allowed subroutine nesting level.
Since the allowed limit is more than enough for normal uses, this error may indicate that a programming error resulted in a “branch loop” where a subroutine calls itself without returning, thus performing branch on branch until the allotted stack slots are exhausted.

CN2F14 – TOOL

Either the programmed tool or the one on the chuck are not defined in the active tool section, or the related tool section is missing, or the wrong tool is on the chuck.

CN3114 – BEYOND F.C. (Fine Corsa =End Run)

During a program execution, between the block shown as ‘executing’ and the one shown on the command line, a movement has been programmed which is beyond the end run as defined in the machine setup.

CN3214 – PREVIOUS WRONG

In the profile programming the segment preceding the one shown on the command line is of the wrong type (see also the geometry section in the programming manual).

CN3314 – INSIDE CIRCLE

In the profile programming, the segment shown on the command line requires a circle/line tangent which can not be found, since the line starting point is inside the circle, or because the two circles to be joined are either internal or intersecting (see also the geometry section in the programming manual).

CN3414 – PREVIOUS OPEN

In the profile programming the segment preceding the one shown on the command line is open (see also the geometry section in the programming manual).

CN3514 – ROW TOO LONG

The row displayed on the command line (alone or concatenated using the dollar sign) is too long.

CN3714 – MOVEMENT NOT ALLOWED

A motion has been programmed on the third axis, with G12 active, on a segment or arc of circle that has been shortened or eliminated by the radius correction.

CN3814 – <>

A permanent formula has been programmed which requires an excessive execution time.

CN3914 – <>

Either G53 or G54 have been programmed while permanent formulas are active.

CN3A14 – AXIS NOT ALIVE

A movement has been requested from a G29-disabled axis or from an axis defined as “not alive” upon reset without previously activating it with G28.

CN3B14 – SUBROUTINE WAS MODIFIED

During the automatic execution a subprogram was called that had been modified either through the editor or through external communication.

CN3C14 – G33, G34, G35 or G63 ACTIVE

With G33 (threading), G34/G35 (variable pitch threading) or G63 (rigid tapping) active, an incompatible function has been also programmed (see Programming Manual for further details).
The program has to be modified.

CN4014 – G110 ROW NUMBER NOT FOUND

One of the row numbers (beginning or end) programmed in G110 does not exist in the specified program or subprogram.

CN4114 – G110 SUBROUTINE NOT FOUND

A call to a nonexistent subroutine level has been programmed in G110.

CN4214 – RB AT CIRCLE BEGINNING

A RB (rounding) has been programmed at the beginning of this trait, which is an arc of circle.

CN4314 – RB AT CIRCLE END

A RB (rounding) has been programmed at the end of this trait, which is an arc of circle.

CN4414 – MISSING INTERSECTION

The programmed trait requires a geometrical intersection which was not found.

CN4514 – RB/RR OVER CONTINUOUS ENTRY

A RB (rounding) or a RR (joint radius) has been programmed at the beginning of this trait, which needed a continuous entry.

CN4614 – PREVIOUS POINT NOT ON CIRCLE

A circle with center and endpoint was programmed, but the previous endpoint is outside the circle by more than about 0.0625 mm.

CN4714 – FEELER DISCONNECTED

A G111 has been programmed, but the analog copy feeler was not installed (the logic bit is not 1).

CN4B14 – TOO MANY PARAMETERS

Too many two-character user parameters have been put in a part-program (e.g. HA, HB, HC, … up to a maximum of sixty).

CN4C14 – ANSWER ERROR

CN4D14 – SUSPENDED BLOCKS INTERNAL ERROR

CN4E14 – :L DISK FILE ERROR

Related to the :L feature to load/download a disk file on part-program’s command. This means that the DOS program got a read error accessing the selected file. The exact cause of the error is not available, and the error may be due to various causes:file or path not found, disk not ready, disk access error… it is up to the operator to remove the error.

CN4F14 – :L Z32 FILE ERROR

Related to the :L feature to load/download a disk file on part-program’s command. This means that the Z32 got a write error writing to the file. As for CN4E14, there is no additional information; the error may be caused by the memory being full, the file being locked by the Z32, or a write data error. Here too it is up to the operator to remove the error.

CN5014 – UNKNOWN :L ERROR

Related to the :L feature to load/download a disk file on part-program’s command, it indicates a malfunction in the exchange between the Z32 and the support program.
If the DOS program (TERMS in this case) is correct, this type of error should never happen.

CN5114 – AXIS MOTION WITH INCOMPLETE G121 INITIALIZATION

The part-program commanded an axis movement while the G121 initialization had not been completed yet.

CN5214 – G121 LIMITS NOT IN SEQUENCE

The G121 limits defined in the part-program are not in the correct sequence.

CN5314 – INSUFFICIENT PROCESSING POWER

Indicates that the PC processor is not powerful enough to handle the “advanced speed” (G113V).

CN5414 – INCONSISTENT MACHINE SETUP

This alarm is triggered whenever, during a G117, G118, G122, G141, G142 programming, the related axes’ setups are incorrect or do not comply with the required specifications.
This alarm message also appears whenever a G120 is programmed and the use of this function has been inhibited in the PLC.

CN5514 – G123 LIMITS NOT VALID

This alarm is triggered in G123 when a positive limit is programmed which is less than the negative limit.

CN5614 – G123 QUOTA EXCEEDS LIMITS

This alarm is triggered in G123 if the programmed quotas are outside limit quotas.

CN5714 – G123 CIRCLE+G123

This alarm is triggered in G123 if a circle is programmed (G2 or G3).

CN5814 – G124+ G117 ROTATIVE AXIS

This alarm is triggered if one of the G117 related rotative axes is programmed into G124.

CN5914 – G123+ G105

G105 has been programmed while G123 is active.

CN5A14 – G123+G53

One of G53 or G123 has been programmer while the other is active.

CN5B14 – <>

One of G43, G44 and G45 has been programmed while one of G116, G117, G118 or G122 is active. This situation triggers an alarm as it could lead to wrong measure calculations in relation to the logical axes 0, 1, 2 (as a general rule, X, Y and Z).

CN5C14 – G128+G130 WRONG DATA

Error related to the “process lock”, the specific running of multi-process or synchronisedaxes machines. This error is displayed under various conditions:
In the line where G128 has been programmed, if:
– it is not a master
– no slave or less than 5 slave processes have been defined
– the slave process is lower than the master
– the slave process does not exist
– the slave process has not been defined as slave
– the slave process has been attached to another process.
In the line where G129 has been programmed, if:
– it is not a slave process
– the slave process is lower than the master
– the master process does not exist
– the master process has not been defined as master
– the master does not control this slave.
In the line where G130 has been programmed, if:
– it is not a master
– a lock process is not running (G128 or the previous function is missing).

CN5D14 – G128-G129 DIFFERENT OR ZERO MASTER/SLAVE HX

Error related to the “process lock”, the specific running of multi-process or synchronisedaxes machines. This error is displayed under various conditions:
In the line where G128 has been programmed, if:
– the master HX is different from the slave HX
– the slave and master HX is zero.

CN5E14 – G128-G129 INCONSISTENT MASTER/SLAVE STATUS

Error related to the “process lock”, the specific running of multi-process or synchronisedaxes machines. This error is displayed under various conditions:
In the line where G128 has been programmed, if:
– the master is already in process lock status
– the slave is already in process lock status
In the line where G129 has been programmed, if:
– the master is already in process lock status.

CN5F14 – G128-G129 DIFFERENT MASTER/SLAVE LIVE AXES

Error related to the “process lock”, the specific running of multi-process or synchronisedaxes machines. This error is displayed under various conditions:
In the line where G128 has been programmed, if:
– the slave has live axes that are not so on the master
During the lock process (i.e. after G128 and before G130), if:
– the master is enabling or disabling axes during the lock process.

CN6014 – G128-G129 DIFFERENT MASTER/SLAVE SENSORS

Error related to the “process lock”, the specific running of multi-process or synchronisedaxes machines. This error is displayed under various conditions:
In the line where G128 has been programmed, if:
– the slave axes have too different sensors (sensor pitch different by a factor>4).

CN6114 – G128 INCOMPATIBLE FUNCTION

Error related to the “process lock”, the specific running of multi-process or synchronisedaxes machines. During the lock process, the part-program on correlated movements and activities. The following functions are therefore forbidden and trigger this alarm:
M0 M1 M2 M3 M4 M5 M6 M7 M8 M9 M19 special M MA MB MC T G115 G114 G61 G98 G111 G127 G126 G125 G113X G62 G124 G123 G121 G54 G53
This alarm is also displayed when an attempt is made to launch the JOG mode during the lock process, or to program G128 or G129 in semi-automatic mode.

CN6214 – LIVE AXES CHANGE + G33/G34/G35/G63

This alarm appears up when an axis state change (live/idle) is requested with active G33, G34, G35 or G63. This alarm is triggered not only when programming G28 or G29, but also if a movement is programmed for an idle axis, which therefore should be first enabled and then disabled.

CN6314 – INVALID STRING

The CN6314 alarm is related to the INPUT instruction (parameter and part-program entering through the keyboard). The alarm is only triggered when the comment (string) displayed to the operator as an explanation of parameter function is not correct.

CN6414 – G110 WRONG PAR [ ] NUMBERS

This alarm indicates that AP and KA values exceeding the set limits have been programmed in the G110T6 macrofunction (analysis with multiple intersections).

CN6514 – :L WITH [ ]:SYNTAX ERROR

Performance error of the structured DNC related to the !:L254 instruction, whose syntax includes the start and end pointers for the file portion to be sent in DNC mode. This error appears when the syntax of the structured DNC activation line is wrong.

CN6614 – :L WITH [ ]:POINTERS NOT IN LINE HEAD POSITION

Performance error of the structured DNC related to the !:L254 instruction, whose syntax includes the start and end pointers for the file portion to be sent in DNC mode. This error appears when the pointers of the structured DNC activation line are not in line head position.

CN6714 – :L WITH [ ]:POINTERS BEYOND END OF FILE

Performance error of the structured DNC related to the !:L254 instruction, whose syntax includes the start and end pointers for the file portion to be sent in DNC mode. This error appears when the pointers of the structured DNC activation line are beyond the end of file.

CN6814 – :L WITH [ ]:START POINTER HIGHER THAN END POINTER

Performance error of the structured DNC related to the !:L254 instruction, whose syntax includes the start and end pointers for the file portion to be sent in DNC mode. This error appears when the start pointer of the structured DNC activation line is higher than the end pointer.

CN6914 – G116 + G118HR1

This alarm appears when G118HR1 is active and a G116 is programmed, or vice-versa, when a G116 is active and a G118HR1 is programmed.

CN6A14 – DEFINE END WITHOUT DEFINE

An END DEFINE has been programmed with DEFINE not open.

CN6B14 – END IF WITHOUT IF

An END IF has been programmed without an open IF.

CN6C14 – DEFINE INSIDE DEFINE

A DEFINE has been programmed inside another DEFINE.

CN6D14 – EXCESSIVE IF (>31)

This alarm indicates that an IF has been programmed inside another IF beyond the maximum admissible level (31 nesting levels).

CN6E14 – LOOP WITHOUT DO

A LOOP has been programmed without an open DO.

CN6F14 – FPU INTERNAL ERROR

This is an internal error that should never happen. If it does, notify D.Electron.

CN7014 – G126/G127 WRONG DATA

This alarm is related to the G126/G127 functions for the machining of moving pieces. This error appears in the G126 programming line when the plant settings, as defined through the PLC functions, are inconsistent, or when the slave process has not been set at 2 ms.

CN7114 – IF/DO AND !GON..! IN THE SAME FILE

The structured instructions IF and/or DO and the !GON… instructions have been programmed inside the same program or sub-program. These instruction cannot exist together in the same file.

CN7214 – EXIT WITHOUT DO

An EXIT DO has been programmed without an open DO.

CN7314 – ELSE OR ELSEIF WITHOUT IF

An ELSE or ELSEIF has been programmed without an open IF.

CN7414 – LOOP DURING OPEN IF

The LOOP instruction must be at the same level as the IF of the relative DO, otherwise this alarm is triggered. More simply the IFs opened inside the DO LOOP body must be all closed before the LOOP instruction.

CN7514 – INTERNAL ERROR ON STRUCTURED INSTRUCTIONS

This is an internal error related to structured instructions that should never happen. If it does, notify D.Electron.

CN7614 – DO – LOOP CYCLE TOO LARGE IN DNC

In a program executed in DNC mode, the DO body size (i.e. the instructions between DO and LOOP) cannot exceed 44K, otherwise this alarm is triggered.

CN7714 – NON-EDITABLE FILE ERROR

This alarm is related to the DEFINE structured instruction, and is triggered whenever defining (creating):a subprogram whose number is higher than 119; a program or subprogram that is currently executed; one of the programs to which the cycle must return.
More simply, it is not possible to overwrite the program or subprogram currently executed, nor the programs to which the cycle must return.

CN7814 – SOFTWARE OPTION NOT ENABLED

This alarm is related to the software options system and is released whenever using the software options without having installed the license that enables them.

CN7914 – SUBTEMP ERROR

This error is related to temporary subroutines (subtemp). Inside a subtemp, it is not possible to enable local sections regarding tools, origins, parameters (G37TL, G37OL, G37PL). The use of this functions will trigger this alarm. The CN7914 alarm will be also triggered if the G110 (emptying macro) is programmed inside a subtemp, or if the G110 caller is a subtemp.
In the event of a subtemp error such as the CN7914, the command line (displayed under TERMS) contains a final number indicating the error type. The cause of this error may be:
User errors:
1 attempt to open a new file with 128 files already open
2 write memory full
3 reading of an inexistent file
4 reading of a too long line
5 reading beyond end of file
Internal errors (should never happen):
101 too many files to be opened
102 no file to be opened
103 not defined
104 global to local file assignment is inconsistent
105 write calling with file not opened for the calling in process
106 too long write string (>255 characters)
107 string research in an inexistent file
108 in the reading stage, unprintable characters not allowed
109 string search with string length =0

CN7A14 – … G125 KA1 REQUIRED

This alarm is released on activating the G113X KA1 if any of the axes has not been calibrated with G125 KA1. Before activating G113X KA1 it is necessary that all the axes involved in the motion (i.e. all live axes) be calibrated using the G125 KA1 function; in the case that, on activating the G113X KA1, some live axes have never been calibrated, the CN7A14 … G125 KA1 REQUIRED will be released, where the names of the non-calibrated axes are displayed instead of the dots.

CN7B14 – G141 + G43,G44,G41,G42,G2,G3

This alarm is related to the G141 function “Three-dimensional correction of tool radius”, and appears:
– a G2/G3/G41/G42/G43/G44 function has been programmed while G141 is active.
– G141 is programmed while it is already active.
– G141 is programmed while G2/G3/G41/G42 are active

CN7C14 – G141:TOOL AXIS NOT VALID

This alarm is related to the G141 function “Three-dimensional correction of tool radius”, and appears when on activating G141, the third axis of the chosen triad does not correspond to the axis along which the tool length is compensated (G43/G44).

CN7D14 – RTCP + AXIS NOT LIVE

This alarm is triggered when a RTCP function is activated (G116, G117, G118, G122) and one or more of the main machine axes (X,Y,Z) are not live; or when one or more RTCP functions are active (G116, G117, G118, G122) and one of the main machine axes (X,Y,Z) is switched to the not live status.

CN7E14 – G142 EXECUTED

This alarm is related to the G142 function (Retract) for retracting the tool from the workpiece. Once the motion programmed in G142 has been executed, the NC releases the CN7E14 alarm (G142 EXECUTED) which can be only cancelled by resetting or switching off the machine.

CN7F14 – G142:TOOL AXIS NOT VALID

This alarm is related to the G142 function (Retract) for retracting the tool from the workpiece. The alarm appears when on activating G142, the tool length compensation (G43) is associated with an axis other than X,Y,Z; or the tool length compensation is associated with an axis other than X,Y,Z (through G43) while G142 is active.

CN8014 – EXCESSIVE LENGTH

This alarm is released whenever the total length of the motion (linear or circular) exceeds 1,000,000 mm, i.e. 1 km.

CN8114 – G125 KA1:EXCESSIVE TIME LENGTH

This alarm is related to G125 KA1, which carries out a “vectorial” calibration of the machine’s dynamic responses. As for the G125 KA1 there is a test time limit:a forward/backward motion cannot last longer than about 8 sec, otherwise the calibration may result inaccurate. Therefore, if the motion time exceeds 8 sec, the alarm CN8114 – G125KA1:EXCESSIVE TIME LENGTH will be released.

CN8214 – G800/1/2 PC FILE ERROR

This alarm refers to G800, G801 and G802 functions for managing “canned cycle”, “positioning macros” and “machining macros” saved on hard-disk. This alarm appears when a cycle or a macro is called, but the correspondent file is not found on the hard-disk.

CN8314 – G800/1/2 MEMORY FULL

This alarm refers to G800, G801 and G802 functions for managing “canned cycle”, “positioning macros” and “machining macros” saved on hard-disk. This alarm appears when a cycle or a macro is called, but the correspondent file dimension exceed the maximum loadable in memory.

CN8414 – TOO MANY AXES

This alarm indicates that a movement involving more that 5 axes has been programmed and that one or more of the following G-functions are active:G61, G63, G110, G132. All these functions are not compatible with movement involving more than 5 axes.

CN8514 – G131+G148

This alarm indicates that a G131 function has been programmed while a G148 is active, or vice-versa that a G148 function has been programmed while a G131 is active

CN8614 – JUMP OR RETURN ERROR IN DNC

This alarm refers to GON and GON-N programming inside a program executed via DNC.
Inside a DNC execution, the searching of jump destination and return points is devolved to the Windnc program (the DNC manager in Windows operative systems). When the searching ends with no found occurrences, the CN8614 alarm appears.

CN8714 – TARAT TO BE RUN:WRONG CONTINUOUS AXES COMPENSATION

Installation alarm. It informs that the length compensations for the continuous axes are not regular. To eliminate this alarm, the program “TARAT” (Machine settings) has to be executed.

CN8814 – Z32DG NOT INSTALLED

Installation alarm. It informs that a software program (Z32DG.exe) is not running. If this software is not running, the CNC may not receive information referring to the macine installation memorized on disk:a restore of this software is necessary.

CN8914 – G70/G71 + SYSTEM CANNED CYCLE OR G800/G900

The alarm is shown in two cases:
– A system canned cycled (from G27C1 to G27C30) or a G800/G900 macro has been programmed while the machine was in forced condition (millimetres machine forced in inches with G70, or inches machine forced in millimetres with G71)
– A G70 or a G71 has been programmed inside a system canned cycle (from G27C1 to G27C30) or a G800/G900 macro.

CN8A14 – G155 + BLOCK SEARCH

This alarm refers to the G155 (raster-type laser printing). This function is not compatible with the block-search. This alarm comes if a G155 is found during a block-search.

CN8B14 – 5 AXES NOT ENABLED

This alarm indicates that 5 or more axes have been programmed on the same line of partprogram, but the installation of the Z32 supports a maximum of 4 simultaneous axes. For further information, please refer to the machine-tool manufacturer.

CN8C14 – … AXIS NOT IN POSITION

This alarm indicates that at the beginning of an automatic execution (typically after a blocksearch) a special subprogram-axis is not in the programmed position. The command line shows both the present position and the programmed position. Move the axis in the programmed position and repeat.

CNEx14 – POSITIVE SOFTWARE END OF TRAVEL

This alarm indicates that a movement has been programmed which would exceed the positive x axis end run, where x is the axis’ logical number. This alarm supersedes the generic CN3114 END OF TRAVEL.

CNFx14 – NEGATIVE SOFTWARE END OF TRAVEL

This alarm indicates that a movement has been programmed which would exceed the negative x axis end run, where x is the axis’ logical number. This alarm supersedes the generic CN3114 END OF TRAVEL.

References

1. M291C21GB – Z32 Alarms pdf by D.ELECTRON