M291c25en-Alarms z32

D.
ELECTRON
dal 1977 Al t a Tecnol ogi a
per l a Macchi na Ut ensi l e
CNC Z32
NUMERICAL CONTROLLER ALARMS
USER MANUAL
Document M291GB
C25 - 27.02.2015
This manual contains information destined exclusively to the users of D.Electron products for the correct usage of the equipment
supplied. It is forbidden to copy any part of this manual or pass it to thirds for other uses than the aforementioned one.
While all information herein has been accurately checked to be correct and reliable, D.Electron will take no responsibility for any
inaccuracy. D.Electron reserves the right to make any changes it will deem necessary to improve the performance or reliability of
its products.
D.Electron - Via R. Giuliani 140 - 50141 Florence ITALY Internet: www.delectron.it

Tel ++39 - 055 - 416927 Fax ++39 - 055 - 434220 email delectron@delectron.it
CNC Z32 Numerical Controller Alarms – M291GB
INDEX
1. DESCRIPTION..................................................................................................................... 1
2. SERIOUS SYSTEM ERRORS ............................................................................................. 1
3. NUMERICAL CONTROLLER ALARMS.............................................................................. 3

3.1 CN..02 - Initialization alarms............................................................................................................................. 3
3.2 CN..07 - FlorenZ system alarms....................................................................................................................... 7
3.3 CN..08 - Z-Star Alarms..................................................................................................................................... 10
3.4 CN..09 - Link alarms ........................................................................................................................................ 11
3.5 CN..10 - CMOS alarms..................................................................................................................................... 12
3.6 CN..12 - Axis detector alarms......................................................................................................................... 13
3.7 CN..13 - Axis movement alarms..................................................................................................................... 14
3.8 CN..14 - Machine programming and usage alarms...................................................................................... 20
i
1. DESCRIPTION
This manual describes all the Z32 alarms valid at the issue date of the manual.
WARNING
These information and data may change depending on the version of the Z32 software.
Therefore, they may be no longer effective in the case of successive software modifications.
Please check the software updates successive to the issue date of this manual.
2. SERIOUS SYSTEM ERRORS

Should the Z32's OS detect a malfunction, it will activate a system error condition and halt the
NC.
This situation may be recognized by the following being displayed on the command line:
** errorgen xxxxxxxx
where xxxxxxxx is an 8-digit hex code describing the error.
All errorgens may derive from software errors (since a programming bug may do anything) but
also indicate specific hardware faults or application software problems.
Should the errorgen's reasons be unclear, the user should carefully note it down (paying
attention to the zeroes' number, which may completely change the code's meaning) and notify
D.Electron.
Any errorgen's different from what reported below indicate malfunctions which should be notified
to D.Electron.
In case of serious system error, any NC's capability is disabled; the keyboard will not work; and
only safe null sequences (zeroes) are issued through the link.
errorgen 00000100
The PC could not run some mandatory program before the next machine cycle.
This may mean that the PC's processor is too slow and can not service all mandatory
functions.
It may also mean that a fast non–programmable logic section (MODULE 2, MODULE 4 or
MODULE 8) is too long. In this case (unless it is due to an endless loop error) try
recompiling the logic with -o optimization option, and install a faster processor.
errorgen 00000110
The errorgen 00000110 for fast interrupt cycles is an alarm designed to signal anomalous
situations that are currently being experimented, and normally it never appears. Should
this message appear, please notify D.Electron.
errorgen 00000120
The errorgen 00000120 appears when there is an excessive delay in reading or writing
operations to the RAM of the PC.
errorgen 00000800
The ML programmable logic installed by the user has an excessive average duration.
Reduce the logic size or compile using the -o optimization option, or install a faster
processor.
errorgen 00001000
The ML programmable logic installed by the user lasts more than a 24 ms. cycle.
If there are no endless loop errors, reduce the logic size or compile using the -o
optimization option, or install a faster processor.
1
errorgen 00001110
Exclusively for FlorenZ-Linux systems, 2 mS interrupt overlap.
It is originated by a too slow processor or (most likely) by an inadequate video driver.
errorgen 00001200
This alarm may come when a simulation of the Z32 is done under Windows or FlorenZ, if
endless software loops are executed, that might bloc the computer.
For example, a PLC error generating an endelss software loop originates an errorgen
0000100 on a real machine but might completely bloc the computer during a simulation.
These situations are detected and originate the errorgen 00001200, allowing the operator
to correct his programs.
errorgen 00004000
Generic unimplemented instruction error.
It may be caused by an hardware error, causing the PC to misread the memory and
consequently attempt to execute garbage instructions.
errorgen 00004400
Possible only in Windows or FlorenZ systems.
The RAM memory reserved for the Z32 real-time elaboration is too small.
Please, install an updated version of the "Z32 Driver" software.
Attention: together with the "Z32 driver" software it is recommended to update also the
"Z32 for Windows" software.
errorgen 00004F00
OS checksum error.
It indicates that the system RAM is corrupt, and therefore in all likelihood an hardware
fault.
It could also mean that somehow some program succeeded in overriding the built-in
safeguards and overwrote the OS reserved memory area.
errorgen 00004FF0
ML logic program checksum error.
The same diagnosis applies as to errorgen 00004F00.
errorgen 00005000 – 00005FF0
Alarms generated by the PLC, to manage special forbidden situations. For further
information, refer to the machine-tool manufacturer.
errorgen 00008000
Alarm message caused by illegal software installation. The master link board installed has
not been enabled or the enabling code is wrong.
errorgen 00008001
With Z32 installed under NT, this alarm message is triggered when a DES107 master link
board is entered as a software environment setting. This board cannot be supported in NT
environment. The alarm appears on the event display after the invalid license number
warning.
errorgen 0000C000
It is the sum of two alarms: errorgen 00004000 (illegal instruction) plus errorgen 00008000
(illegal installation).
errorgen 0000C400
It is the sum of two alarms: errorgen 00004400 (RAM memory too small) plus errorgen
00008000 (illegal installation).
errorgen 00010000
Indicates a software malfunction that should be notified to D.Electron.
errorgen 00020000
errorgen 00040000
2
errorgen 00080000
Generated when a Z32 software version with serial emulator is installed, without the
appropriate key or with a key not enabled.
errorgen 03000000
errorgen 05000000
3. NUMERICAL CONTROLLER ALARMS

NC's alarms are displayed in code in the display video area dedicated to that purpose.
The alarm code is displayed over 4 hexadecimal digits (0-1-…F).
The last two digits indicate the generic alarm's category, while the first two specify it in detail.
In general, the lower the category, the more important the alarm; lower categories' alarms are
those displayed should more than one alarm be active at the same time.
3.1 CN..02 - Initialization alarms

At every power up, the Z32 performs a series of checks on the internal PC's circuitry as well as
on the DOS operating system structure: should an anomaly be detected, the alarm CN..02 will be
displayed.
In such a case, the operator will have to note the alarm code and notify it to the support service.
The following alarms have been programmed:
CN0102 - CMOS DISABLED
Appears in the case of serious system error errorgen.
CN0202
Malfunction in the NC disk file save routine. This indicates a serious hardware or DOS
operating system malfunction. Turn the computer off and then on again. Upon restart, a
message will be displayed stating that numerical controller's files may be corrupt and
special care should be taken to ensure their integrity. If file 127, upon restart, contains an
"x" instead of the "T" for the tool on spindle, the "x" can be simply deleted in order to restart
the work. It is recommended to check all the tools in the tools' table.
CN0302 - ANOMALOUS LINK POSITION SETUP
Indicates that axes' setups defined in TARAT regarding detector or reference positions in
the link are incorrect. It is not allowed for a detector or reference channel to be connected
to more than one axis, not even if belonging to a different process.
CN0402 - ROTATIVE AXIS INCH SETUP INCORRECT
Indicates that the inch rotative axis detector step is above 0.005 degrees. This alarm may
be only generated upon power up.
CN0502 - ANOMALOUS Z-LINK DATA STRUCTURE
Incorrect setup in the Z-Link data structure.
CN0602 - ANOMALOUS FILTER SETUP
Indicates that the axis setup as defined in TARAT for reference output filters are incorrect.
This alarm is triggered on start-up if the same filter is associated to two different axes (also
in different processes), or if filters are required with an origin number exceeding 16.
3
CN0702 - NODES CONNECTED TO Z-LINK INFERIOR TO THE SETUP

In the peripheral fiber optic system (DE1065 and DE 1075 master-link boards) the number
of connected nodes is defined in the setup. If the number of physical nodes is inferior to
calibration, a CN0702 alarm will be triggered.
CN0902 - ANOMALOUS AUXILIARY SPINDLE SETUP
Alarm caused by an error in the management of double spindle and table spindles under
G133KA0 - KA5. The setup of the auxiliary spindle, defined as a continuous axis with
logical number 12, or the setup of the table spindles should be entered in compliance with
specifications, otherwise the CN0902 alarm is triggered on start-up.
CN0A02 - CYCLE/REV FORCING FOR Z-SER SPINDLE
This alarm appears when an unpowered spindle detector 2 has been defined in the
machine settings, and the spindle detector is via Z-ser.
CN0B02 - INSUFFICIENT RAM SPACE
This alarm is released on installing Z32 under DOS if the available RAM space is not
enough to support the Z32 programs (less than 16 MB).
CN0C02 - Z-SER OR Z-STAR: WRONG MASTER LINK
This alarm appears when Z-SER or Z-STAR settings are defined, but the master-link type
is not right. For example, the master-link DE1075/1 is defined, the Z-SER section is empty
and Z-SER transducers (or references) are defined.
CN0D02 - WRONG Z-STAR SETTINGS
This alarm appears when the Z-STAR drives settings are not consistent.
CN0E02 - WRONG SETTING: ZERO SEARCH TYPE ENDAT FOR NON ENDAT AXIS
This alarm appears when an Endat-type zero search is defined in the settings, but the
relative axis board (can be only a Z-STAR axis) is not Endat.
CN1002 - WRONG CONCENTRIC AXES SETTINGS
This alarm refers to the concentric axes functionality. This alarm appears in the start-up
phase when the concentric axes settings are not consistent with specifications.
CN1102 - PRM[ ] INITIALIZATION FAILED
This alarm refers to the PRM[ ] (permanent parameters) functionality. This alarm appears
in the start-up phase for the following reasons:
- Requested PRM[ ] functionality activation with master link DES107 (that doesn't support
the PRM[ ] parameters)
- It is not possible to create the CMOS file used for saving the PRM[ ] parameters
CN1202 - BAD SETTINGS OF CYLINDRICAL AXIS
This alarm refers to the machine settings activating the "cylindrical axis" functionality
(G149). This alarm appears in the start-up phase if any of the settings related to the
cylindrical axis is missing or not conform to the specifications.
CN1302 - ABSOLUTE AXIS, AXIS TRAVEL TOO BIG WITH RESPECT TO THE ABSOLUTE
TRAVEL
This alarm refers to absolute axes with end-of-travel (linear or rotary. It appears in the
start-up phase if the axis travel (comprised between the positive and negative end-of-
travel) is too big with respect to the absolute travel. Numerically: this alarm appears if:
(axis travel) > (0,8 x absolute travel).
CN1402 - ABSOLUTE AXIS, FRACTIONARY GEAR-RATIO, NOT SPECIALLY-ENABLED
This alarm refers to absolute axes, cyclic, without end-of-travel. It appears in the start-up
phase if the absolute travel of the transducer contains a fractionary (non integer) number
of axis turns. This alarm may be eliminated through a supplementary setting.
4
CN1502 - ABSOLUTE AXIS, FRACTIONARY, ABSOLUTE TRAVEL TOO SHORT (< 10 AXIS
TURNS)
This alarm refers to absolute axes, cyclic, without end-of-travel, having a mechanical gear-
ratio such that in an absolute travel of the transducer are contained a non-integer number
of axis turns. It appears in the start-up phase if the the axis turns contained in an absolute
travel of the transducer is less than 10. The reason of this alarm is that in these conditions
(fractionary ratio between absolute travel and an axis turn) the absolute travel must contain
many axis turns (at least 10) to allow sufficient safety margins and safety zones to be sure
that the axis movements may not lead to positions where the axis transducer gives an
uncertain output.
CN1602 - ABSOLUTE AXIS, FRACTIONARY, TOO SMALL DISCRETIZATION
This alarm refers to absolute axes, cyclic, without end-of-travel, having a mechanical gear-
ratio such that in an absolute travel of the transducer are contained a non-integer number
of axis turns. It appears in the start-up phase if the number of "pulses" generated by an
absolute travel of the transducer is higher than the maximum allowed by the internal
31
formats of the CNC. Remember that in one absolute travel no more than 2 pulses may
be contained. If this alarm comes, please check the "pulses per turn" item in the Z-Star
settings.
CN1702 - ELIMINATE THE ALARM OF THE OTHER PROCESS, THEN REBOOT
This alarm comes at the start-up, if the initializing procedure is aborted in a critical phase,
due to an arror CNxx14 detected in a different process. In this case:
- on the original process the original alarm CNxx14 remains. This alarm remains also if
the error is amended because if the initializing procedure is aborted in a critical phase
it is no more possible to restore the normal operation: it is necesssary to turn OFF and
ON.
- on any different process, the alarm CN1702 comes: "ELIMINATE THE ALARM OF
THE OTHER PROCESS, THEN REBOOT"
CN1802 - WRONG SETTINGS FOR SUBPROGRAM-AXIS
It comes at start-up if settings of one or more subprogram-axes are wrong.
Good settings should be:
- logical number not > 12
- associated subprogram in the range 1-98 or 128-230
- settings: rotary axis, without position transducer, without reference output, without
zero, without repositioning
CN1902 - WRONG ADVANCED MANAGEMENT FOR ABSOLUTE TRANSDUCERS
It comes at start-up if the advanced management for absolute transducer is requested for
an axis, but its transducer:
- is not an absolute multiturn EDat or Biss
- or is cyclic and the number of pulses transmitted by the ZStar drive is not power of two
- or is inaccessible (examples: connection broken, faulty transducer...)
CN1A02 - SYSTEM FILE NOT PRESENT IN ARCHIVE-PROCESS
Related to multiple-head machines. It comes at start-up if in one or more archive-process
the system files are missing (origins table, tool table, base origins table).
CN1B02 - NO Z-LINK PERIPHERAL DEFINED IN MACHINE SETTINGS
It comes, only in FlorenZ systems, if not any peripheral Z-Link has been defined in the
machine settings. It may be eliminated with a special setting in the file INI (address
28A30B = 1).
CNC002 - PROCESS 1 SOFTWARE OPTION
Alarm related to the software options. It appears when activating the Process 1 without
having installed the correct license that enables it.
5
CNC102 - PROCESS 2 TO 5 SOFTWARE OPTION

Alarm related to the software options. It appears when activating the Process 2 to 5
without having installed the correct license that enables them.
CNC202 - GANTRY AXES SOFTWARE OPTION
Alarm related to the software options. It appears when activating the Gantry Axes function
without having installed the correct license that enables them.
CNC302 - POLAR/SCARA AXES SOFTWARE OPTION
Alarm related to the software options. It appears when activating the Polar/Scara Axes
functions without having installed the correct license that enables them.
CNC402 - TCP/IP ETHERNET SOFTWARE OPTION
Alarm related to the software options. It appears when activating a TCP/IP ethernet
connection without having installed the correct license that enables it. This alarm is only
triggered when a TCP/IP ethernet connection is established with an unauthorised Z32.
However, this alarm does not impede the ethernet connection, so as to allow the
embedded system (which only operates in a networked environment) to receive the
authorisation file and therefore, to establish the authorised ethernet connection on
restarting.
CNC502 - TOO MANY AXES
It comes at start-up if in the machine settings more continuous axes are defined than
supproted by the CNC hardware.
CND002 - INTERNAL Z32 FILES ERROR
This alarm is obsolete. It may appear only in old versions of Z32.
Starting from the version T112-1 of 1.9.09 it has been changed to 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.
The same as CND002
The same as CND002
The same as CND002
The same as CND002
The same as CND002
6
CNEC02
Similar to CN0202. Indicates a permanent memory temporary data area fault detected at
startup. It may be caused from an incorrect CNC CMOS memory initialization, or from a
serious hardware problem.
CNFF02 - MASTER LINK OBSOLETE, NO MORE SUPPORTED
This alarm comes if the Z32 is equipped with an obsolete ISA-bus type master-link:
DES107, DE1039, DE1065.
Due to the fact that the processing power available for these types of master-link is too
low, starting from the software release Z32 T112-1 these master-link boards are no more
supported.
The last software version supporting these master-link boards is the T111-4 (but not all the
features will be present; depending on the processor type).
3.2 CN..07 - FlorenZ system alarms

This type of alarms groups all the new errors related to the FlorenZ system, operating under
Linux. These alarms come form errors in the ETHERNET, Z-LINK, Z-STAR2 communication.
CN0007 - UNKNOWN DRIVER INTERNAL ERROR
Internal alarm: it must never come.
If present, please contact D.Electron.
CN0107 - DRIVER INTERNAL ERROR 1
CN0307 - COMMUNICATION WITH MASTER-LINK BROKEN (DRIVER ERROR 3)
Indicates that the Ethernet connenction between the master-link board and the Linux PC is
broken.
The most probable reasons are:
- The power supply of the master-link is turnad OFF
- The Ethernet cable is disconnected or is faulty
Error originated by the driver software during the "receive" activity.
This error may come form hardware problems, as:
- faulty real time Ethernet board (RTE)
- faulty Ethernet cable
Error originated by the driver software during the "send" activity.
This error may come form hardware problems, as:
- faulty real time Ethernet board (RTE)
- faulty Ethernet cable
7

CN1007 - 3 CYCLES AT 2 MS LOST
Indicates that there are communication errors between the Linux PC and the master-link
board and that for three consecutive times it was not possible to communicate with the Z-
Link peripherals.
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, CN1707, CN1907, CN2007,
CN2107, (all depending on a difficulty communication) are very similar one to another: they
may interchange following almost casual rules.
CN1107 - GENERAL TRANSMISSION TIMEOUT
Indicates a generic excessive delay in the data transmission between the Linux PC and
the Master-Link board.
board.
processor.
CN1207 - FAULTY COMMUNICATION WHEN COPYING CMOS MEMORY
Indicates communication errors during the CNC initialization, when the CMOS memory Is
read.
board.
processor.
CN1307 - EXCESSIVE CMOS WRITING ZONE 0
Indicates an excessive number of simultaneous CMOS writings. It comes when a very
frequent writing in permanent variables is done by PLC in a 2 mS module and at the same
time there is a writing of CMOS file.
8
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.
board.
processor.
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.
board.
processor.
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).
board.
processor.
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)
board.
processor.
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.
nr. 2.
9
nr. 3.
nr. 4.
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.
3.3 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:
10
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.
3.4 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)
11
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.
3.5 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.
12
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 type 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 - INTERNAL Z32 FILES ERROR
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.
The same as CN1010
The same as CN1010
The same as CN1010
The same as CN1010
The same as CN1010
3.6 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 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 = abnormal input position from encoder
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:
13
- 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 transducer outputs a position with a value abnormally high. To eliminate
this alarm:
- extract the transducer and rotate it to a normal position
- if the transducer type is absolute multiturn, change the settings to activate the advanced
management of this transducer
3.7 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.
14
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.
15
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.
16
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
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
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
follows a master axis). This alarm appears when the master axis (or the slave axis) is in
17
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 Fieldbus management. It comes at turn-on if the Fieldbus interface
boards doesn't activate in 5 seconds. Probable causes: wiring error or board missing.
CN3113
Alarm related to the Fieldbus management. It comes at run-time if the Fieldbus INPUTS
are not refreshed for more than 48 mS. Probable causes: uncertain or interrupted
connection to the Fieldbus peripherals.
CN3213
Alarm related to the Fieldbus management. It comes at run-time if the Fieldbus OUTPUTS
are not refreshed for more than 48 mS. Probable causes: uncertain or interrupted
connection to the Fieldbus peripherals.
CN3313
Excessive following error for gantry system defined by machine settings (Note: the PLC-
defined 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.
18
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 head-
exchanging 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.
CN3613
This alarm is related to the TAO function (Tool Adaptive Override).
It can appear when adaptive override regulation is currently in process.
It is due to an overload condition: excessive spindle current absorption.
CN3713
Internal error.
CN3813
Internal error.
CN3913
Internal error.
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.
19
3.8 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
th
4 , 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.
20
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).
21
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 - <AC> 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 - <<FORMULA TOO LONG>>
A permanent formula has been programmed which requires an excessive execution time.
CN3914 - <<FORMULA + G53/54>>
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).
22
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.
23
CN5B14 - <<FORMULA G116/17/18/22 + G43/G44/G45>>

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 synchronised-
axes 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.
- 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.
- 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
- the master HX is different from the slave HX
- the slave and master HX is zero.
CN5E14 - G128-G129 INCONSISTENT MASTER/SLAVE STATUS
- the master is already in process lock status
- the slave is already in process lock status
- the master is already in process lock status.
CN5F14 - G128-G129 DIFFERENT MASTER/SLAVE LIVE AXES
- 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
- the slave axes have too different sensors (sensor pitch different by a factor >4).
24
CN6114 - G128 INCOMPATIBLE FUNCTION

axes 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 - <IN: …> 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
appears when the pointers of the structured DNC activation line are not in line head
position.
CN6714 - :L WITH [ ]: POINTERS BEYOND END OF FILE
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
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).
25
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
26
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
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.
27
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 part-
program, 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 block-
search) 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.
CN8D14 - INTERNAL SOFTWARE ERROR
This is an internal error that should never happen. If it does, notify D.Electron.
28
CN8E14 - TAO ERROR, VISUALIZE ZZTAOERR USING MLDEB

It comes when there is an error related to TAO function (Tool Adaptive Override).
When the alarm CN8E14 is present, more details about the error are available through the
PLC variable ZZTAOERR:
ZZTAOERR=1: file not found. It means wrong/incomplete TAO software installation or
hard-disk files corruption.
ZZTAOERR=2: phase parameter error. It means wrong/incomplete TAO software
installation or hard-disk files corruption.
ZZTAOERR=3: strategy table missing. Refer to the TAO function user manual for further
information about creating TAO strategy table.
ZZTAOERR=4: strategy not found. The strategy number corresponding to the TAO
parameter in the tool table is nod defined in the strategy table.
ZZTAOERR=5: wrong strategy parameter. It means wrong/incomplete TAO software
installation or hard-disk files corruption.
ZZTAOERR=6: timeout. It means wrong/incomplete TAO software installation or hard-disk
files corruption.
ZZTAOERR=7: tool error. The tool currently in the spindle is different from the expected
tool.
CN8F14 - G118N + G113XKA2 WRONG PROGRAMMED AXES
This alarm comes when G118N (not HR1) and G113XKA2 are simultaneously in progress
and in the some part-program line both rotary axes related to the G118 and linear axes are
present.
Solution is to program rotary axes and linear axes in different lines.
CN9014 - G142 NOT DONE
workpiece.
This alarm can come if, when the retract movement is finished, the real movement length
is less than the value contained in the PLC variable ZZG142MINMOV.
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.
29

M291c25en-Alarms z32

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

M291c25en-Alarms z32

Uploaded by

Copyright:

Available Formats

D.

NUMERICAL CONTROLLER ALARMS

D.Electron - Via R. Giuliani 140 - 50141 Florence ITALY Internet: www.delectron.it

2. SERIOUS SYSTEM ERRORS ............................................................................................. 1

3. NUMERICAL CONTROLLER ALARMS.............................................................................. 3

2. SERIOUS SYSTEM ERRORS

3. NUMERICAL CONTROLLER ALARMS

3.1 CN..02 - Initialization alarms

CN0702 - NODES CONNECTED TO Z-LINK INFERIOR TO THE SETUP

CNC102 - PROCESS 2 TO 5 SOFTWARE OPTION

3.2 CN..07 - FlorenZ system alarms

CN0707 - DRIVER INTERNAL ERROR 7

CN1707 - FAULTY COMMUNICATION WITH MASTER-LINK

3.3 CN..08 - Z-Star Alarms

CN0108 - ZSTAR: CONNECTION ERROR TO ZBOX NR. 1

3.4 CN..09 - Link alarms

The following codes may be compounded: CN0209 - CN0409 - CN0809 - CN1009:

CNFF09 - Z-STAR: WRONG Z-LINK BEHAVIOUR

3.5 CN..10 - CMOS alarms

Alarms type CN0x10

CN0210 - Error: Sequence files Z32

Alarms type CNyx10 (where "y" is different from 0)

3.6 CN..12 - Axis detector alarms

- extract the encoder and rotate it to a normal position

3.7 CN..13 - Axis movement alarms

3.8 CN..14 - Machine programming and usage alarms

CN2414 - RETURN ERROR

CN3414 - PREVIOUS OPEN

CN4B14 - TOO MANY PARAMETERS

CN5B14 - <<FORMULA G116/17/18/22 + G43/G44/G45>>

CN6114 - G128 INCOMPATIBLE FUNCTION

CN6E14 - LOOP WITHOUT DO

Internal errors (should never happen):

CN8214 - G800/1/2 PC FILE ERROR

CN8E14 - TAO ERROR, VISUALIZE ZZTAOERR USING MLDEB

You might also like