
NCK alarms/ISO alarms
06/2007 Overview of alarms
2-39
" Siemens AG 2007 All Rights Reserved
SINUMERIK 802D sl, Diagnostics Manual, 06/2007Edition
6000 Memory reorganized using standard machine data
Definitions: The memory management was not able to allocate the NC user memory with the values in the
machine data. Because the total memory is available as dynamic or static memory for the NC user
(e.g. for: the number of tool offsets, the number of directories and files, etc.) and is therefore not suf-
ficient.
Reaction: NC not ready.
Mode group not ready, also effective for single axes
NC Start disable in this channel.
Interface signals are set.
Alarm display.
NC Stop on alarm.
Remedy: Redefine the NC memory structure!
A specific MD for NC user memory allocation cannot be given as the cause of the alarm. Therefore,
the MD initiating the alarm must be determined on the basis of the default values in the machine data
by changing the user-specific memory structure step by step.
Usually, not just one MD has been chosen too large and therefore it is advisable to reduce the memory
area by a certain proportion in several MDs.
Program Con-
tinuation:
Teileprogramm neu starten.Clear alarm with the RESET key in all channels of this mode group.
Restart part program.
6010 Channel %1 data block %2 not or not completely created, error code %3
Parameters: %1 = channel number
%2 = string (module name)
%3 = internal error ID
Definitions: Data management has detected an error in power-up. The specified data block may not have been
created. The error number specifies the type of error. If the error number >100000, then there is a fatal
system error. Otherwise, the user memory area was made too small. In this case the (user) error
codes have the following meaning:
Error numberExplanation
1No memory space available
2Maximum number of possible symbols exceeded
3Index 1 lies outside valid range of values
4Name in channel already exists
5Name in NC already exists
If the alarm occurs after cycle programs, macro definitions or definitions for global user data (GUD)
have been introduced, the machine data for the NC user memory configuration have been incorrectly
configured. In all other cases, modifications to machine data that are already correct produce errors
in the user memory configuration.
The following block names (2nd parameter) are known in the NC (all system and user data blocks; in
general, only problems in the user data blocks can be remedied by user intervention)
_N_NC_OPT- System-internal: Option data, NC global
_N_NC_SEA- System-internal: Setting data, NC global
_N_NC_TEA- System-internal: Machine data, NC global
_N_NC_CEA- System-internal: 'cross error compensation'
_N_NC_PRO- System-internal: Protection zones, NC global
_N_NC_GD1- User: 1st GUD block defined by
_SGUD_DEF, NC global
_N_NC_GD2- User: 2nd GUD block defined by
_N_MGUD_DEF, NC global
_N_NC_GD3- User: 3rd GUD block defined by
_N_UGUD_DEF, NC global
_N_NC_GD4- User: 4th GUD block defined by
_N_GUD4_DEF, NC global
_N_NC_GD5- User: 5th GUD block defined by
_N_GUD5_DEF, NC global
_N_NC_GD6- User: 6th GUD block defined by
Komentarze do niniejszej Instrukcji