Error solving manual.
CNC 8060
CNC 8065
·6·
(REF: 1709)
0008 'The key has been rejected.
DETECTION On CNC startup or during execution.
CAUSE The CNC has detected that two incompatible keys have been pressed at the same
time. The [START ] key, the spindle start keys and the key for spindle orientation must
always be pressed alone; if they are pressed at the same time, they are both canceled.
SOLUTION If it has been by mistake, ignore the error. If the error persist s or it comes up dur ing
start-up, verify that no keys are pressed (stuck) on the keyboard. If the error persists
after powering the CNC up several times, contact your supplier.
0010 'Error when testing the RAM with battery'
DETECTION During CNC startup.
CAUSE The start-up test has detected a checksum error in the data of the NVRAM and,
therefore, a failure in it.
CONSEQUENCE The saved data may not be correct (related to coordinates, zero offsets, parts counter,
kinematics, etc.).
SOLUTION If the error persists after powering the CNC up several times, contact your supplier.
0011 'Checksum error in block search data'
DETECTION During CNC startup.
CAUSE Checksum error in the data required to execute an automatic block search.
CONSEQUENCE An automatic block search cannot be executed.
SOLUTION If the error persists after powering the CNC up several times, contact your supplier.
0020 'Wrong access to a variable'
DETECTION On CNC startup or when changing pages.
CAUSE The CNC is accessing an interface variable that does not exist.
SOLUTION Contact the machine manufacturer or the person who designed the interface screens
to remove or correct the access to the variable.
0022 'Variable that may be modified during setup'
DETECTION When defining variables during setup.
CAUSE A variable has been defined in the setup environment that is not admitted.
SOLUTION Refer to the operating manual for the list of variables that are admitted.
0023 'The program must be stopped before initiating the trace for the first time.
DETECTION When starting a trace at the oscilloscope.
CAUSE It is the first time that the oscilloscope starts a trace and there is a program in
execution. The trace uses drive variables that either are not in the machine
parameters table or are in that table but are asynchronous.
SOLUTION Stop the program in execution.
0024 'Error when initiating the trace'
DETECTION When starting a trace at the oscilloscope.
CAUSE There are no variables defined in the channels of the oscilloscope, there are more
than two Sercos variables of the same drive or the syntax of one of the variables is
wrong.
SOLUTION Check the variables defined in the channels of the oscilloscope. The oscilloscope can
only access two Sercos variables of each drive.
0025 'Error when registering PLC defines'
DETECTION When registering the variables associated with the external PDEF symbols defined
in the PLC program.
CAUSE The plc_prg.sym that contains the necessary information to create the variables
associated with the external PDEF symbols is corrupt.
SOLUTION Delete the plc_prg.sym file and compile the PLC program to create this file again. If
the error persists, contact your supplier.
0026 'Variable not allowed in the oscilloscope environment'
DETECTION When defining variables defined in a channel of the oscilloscope.
CAUSE The variable assigned to the channel of the oscilloscope is a simulation,
asynchronous variable or is a string.
SOLUTION Refer to the operating manual for the list of variables that are admitted.