Синтаксическая ошибка при самоблокировке сименс

Содержание

1. Что означает ошибка при синтаксическом анализе пакета и ее причины
2. Причины синтаксической ошибки в Android:
3. Дополнительные причины ошибки синтаксического анализа пакета
4. Почему вы должны быть осторожны с синтаксической ошибкой?
5. Чем синтаксическая ошибка отличается от других ошибок кодирования?
6. Можно ли исправить ошибки синтаксиса?
7. Устранение неполадки
8. Проверить манифест-файл
9. Позволить установить приложение из незнакомых веб-ресурсов
10. Проверка совместимости приложения и версии Android
11. Включение отладки по USB
12. Проблемы с установочным файлом
13. Перемещение инсталлятора на внутреннюю память
14. Проверка версии приложения
15. Установка разрешения скачивать файлы из посторонних источников
16. Возникновение ошибки из-за вирусов
17. Перезагрузика приложения и использование другого загрузчика или браузера
18. Проверить название APK-файла приложения
19. Несовместимое приложение
20. Дополнительные способы решения проблемы
21. То, о чем молчат другие источники
22. Если ошибка синтаксического анализа на всех приложениях
23. Если ничего не помогло
24. Заключение

Чаще всего ошибка появляется на старых версиях Андроид

Содержание

• 1 Что такое синтаксический анализ пакета
• 2 Как исправить синтаксический анализ пакета
  • 2.1 Как переименовать файл
  • 2.2 Файл поврежден
  • 2.3 Старая версия Андроид
  • 2.4 Как переместить файл
• 3 Где скачать APK

Попробуйте установить приложение через Google Play

Присвойте файлу имя попроще

Возможно, стоит задумать об обновлении ОС или покупке нового смартфона

Устанавливайте приложения через APK, которые хранятся во внутренней памяти

Нужна консультация?

Задавайте свои вопросы и получите ответ бесплатно!

Отзывы о пройденном обучении

1. Manuals
2. Brands
3. Siemens Manuals
4. Security System
5. SINAMICS S120
6. Diagnostic manual

Quick Links

SINUMERIK

SINUMERIK 828D,

SINAMICS S120

Alarms

Diagnostics Manual

Valid for: CNC system software

Version 4.3 SINAMICS S120 Booksize / Combi

Version 4.3 SP2

07/2010

6FC5398-8BP40-0BA0

System reactions

1 

2 

3 

4 

5 

6 

7 

8 

A 

• Page 1
  Preface 1    Introduction 2  NCK alarms SINUMERIK 3  HMI alarms SINUMERIK 828D, 4  SINAMICS alarms SINAMICS S120 Alarms 5  611D drive alarms 6  Diagnostics Manual PLC alarms 7  List of actions 8  System reactions A  Appendix Valid for: CNC system software Version 4.3 SINAMICS S120 Booksize / Combi Version 4.3 SP2…
• Page 2
  Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems.
• Page 3
  Information on DOConCD and direct access to the publications in DOConWEB. • Compiling individual documentation on the basis of Siemens contents with the My Documentation Manager (DM), refer to http://www.siemens.com/mdm. My Documentation Manager provides you with a range of features for generating your own machine documentation.
• Page 4
  Technical Support If you have any technical questions, please contact our hotline: Europe / Africa Phone +49 (0) 911 895 7222 +49 (0) 911 895 7223 Internet http://www.siemens.com/automation/support-request Americas Phone +1 423 262 2522 +1 423 262 2200 E-mail mailto:techsupport.sea@siemens.com…

• Page 5: Preface

  If you have any queries (suggestions, corrections) in relation to this documentation, please send a fax or e-mail to the following address: Fax: +49 9131 98 2176 A fax form is available at the end of this document. mailto:docu.motioncontrol@siemens.com SINUMERIK Internet address http://www.siemens.com/sinumerik Alarms…

• Page 6
  Preface Alarms Diagnostics Manual, 07/2010, 6FC5398-8BP40-0BA0…

• Page 7: Table Of Contents

  Table of contents Preface……………………………3 Introduction …………………………9 Using the Diagnostics Manual ………………… 9 Structure of the diagnostics manual ………………10 Alarm number ranges …………………… 13 System error alarms ……………………16 NCK alarms ………………………….17 HMI alarms …………………………501 SINAMICS alarms ………………………507 611D drive alarms ………………………891 PLC alarms ………………………..903 List of actions ……………………….909 System reactions ……………………….931…

• Page 8
  Table of contents Alarms Diagnostics Manual, 07/2010, 6FC5398-8BP40-0BA0…

• Page 9: Introduction

  Introduction Using the Diagnostics Manual The Diagnostic Manual specifies the alarms/messages from the NCK area. It should be used as a reference manual and allows operators at the machine tool: • To correctly assess special situations when operating the machine. •…

• Page 10: Nck Alarms

  Introduction 1.2 Structure of the diagnostics manual Structure of the diagnostics manual NCK / HMI / 611D drive / PLC alarms The descriptions of the NCK/HMI/611D drive/PLC alarms are provided in the chapters: • NCK alarms [Page 17] • HMI alarms [Page 501] •…

• Page 11
  Introduction 1.2 Structure of the diagnostics manual SINAMICS alarms The faults and states detected by the individual components of the drive system are indicated by alarms. These SINAMICS alarms are categorized into faults and alarms. The differences between faults and alarms are as follows: Fault •…

• Page 12: Structure Of The Diagnostics Manual

  Introduction 1.2 Structure of the diagnostics manual • Message value The information provided under the message value tells you about the composition of the fault/alarm value. Example: Message value: Component number: %1, cause: %2 This fault value or alarm value contains information about the component number and cause.

• Page 13: Hmi Alarms

  027 000 — 027 999 Alarms for Safety Integrated 030 000 — 099 999 Functional alarms 060 000 — 064 999 Cycle alarms SIEMENS 065 000 — 069 999 Cycle alarms user 070 000 — 079 999 Compile cycles, manufacturer and OEM…

• Page 14: Sinamics Alarms

  Reserved 249 000 — 249 999 SINAMICS GM/SM/GL 250 000 — 250 499 Communication Board (COMM BOARD) 250 500 — 259 999 OEM Siemens 260 000 — 265 535 SINAMICS DC MASTER (DC closed-loop control) Alarms Diagnostics Manual, 07/2010, 6FC5398-8BP40-0BA0…

• Page 15: Alarm Number Ranges

  Introduction 1.3 Alarm number ranges Table 1-4 611D drive alarms 300 000 — 399 999 General drive alarms Table 1-5 PLC alarms/messages 400 000 — 499 999 General PLC alarms 500 000 — 599 999 Channel alarms 600 000 — 699 999 Axis/spindle alarms 700 000 — 799 999 User area…

• Page 16: System Error Alarms

  Introduction 1.4 System error alarms System error alarms The following alarms are system errors: 1000 1005 1013 1017 1001 1010 1014 1018 1002 1011 1015 1019 1003 1012 1016 1160 These system error alarms are not described in detail. If such a system error occurs, please contact the hotline and indicate the following details: •…

• Page 17
  NCK alarms Product: Solutionline_828, Version: V12.0, Language: eng, Objects: 2000 PLC sign-of-life monitoring Definitions: The PLC must give a sign of life within a defined period of time (MD10100 $MN_PLC_CYCLIC_TIMEOUT). If this does not occur, the alarm is triggered. The sign of life is a counter reading on the internal NC/PLC interface which the PLC causes to count up with the 10 ms time alarm.
• Page 18
  NCK alarms 2130 5V/24V encoder or 15V D/A converter undervoltage Definitions: A failure has occurred in the power supply to the encoder (5V/24V) or D/A converter (+/-15V). Reaction: NC not ready. The NC switches to follow-up mode. Mode group not ready, also effective for single axes. NC Start disable in this channel.
• Page 19
  NCK alarms 4000 [Channel %1: ] Machine data %2[%3] has gap in axis assignment Parameters: %1 = Channel number %2 = String: MD identifier Definitions: The assignment of a machine axis to a channel by the MD20070 $MC_AXCONF_MACHAX_USED must be contigu- ous.
• Page 20
  NCK alarms 4004 [Channel %1: ] Machine data %2 axis %3 defined repeatedly as geometry axis Parameters: %1 = Channel number %2 = String: MD identifier %3 = Axis index Definitions: An axis may only be defined once as a geometry axis. Reaction: Mode group not ready.
• Page 21
  NCK alarms Remedy: Please inform the authorized personel/service department. The sum of the two option data $ON_NUM_AXES_IN_SYSTEM and $ON_NUM_ADD_AXES_IN_SYSTEM must not exceed the maximum number of axes (dependent on configuration). Program Switch control OFF — ON. Continuation: 4009 Machine data %1 contains an illegal value. Parameters: %1 = String: MD identifier Definitions:…
• Page 22
  NCK alarms 4011 [Channel %1: ] Invalid identifier used in machine data %2[%3] Parameters: %1 = Channel number %2 = String: MD identifier %3 = Index: MD array index Definitions: When defining names in the channel-specific tables for geometry axes and channel axes, one of the following syntax rules for the identifier to be entered has been violated: — The identifier must be an NC address letter (A, B, C, I, J, K, U, V, W, X, Y, Z), possibly with a numerical extension.
• Page 23
  NCK alarms Remedy: Please inform the authorized personnel/service department. Select for the identifier to be entered a character string that is not yet used in the system (max. 32 characters). Program Teileprogramm neu starten.Clear alarm with the RESET key in all channels of this mode group. Restart part program. Continuation: 4021 [Channel %1: ] Identifier %2 used several times in machine data %3…
• Page 24
  NCK alarms Reaction: Mode group not ready. Channel not ready. NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm. Remedy: Please inform the authorized personnel/service department. Add the correct identifier. Program Switch control OFF — ON. Continuation: 4040 [Channel %1: ] Axis identifier %2 not consistent with machine data %3…
• Page 25
  NCK alarms 4050 NC code identifier %1 cannot be reconfigured to %2 Parameters: %1 = String: Old identifier %2 = String: New identifier Definitions: Renaming of an NC code was not possible for one of the following reasons: — The old identifier does not exist — The new identifier lies in another type range.
• Page 26
  NCK alarms 4065 Buffered memory was restored from backup medium (potential loss of data!) Definitions: Only occurs with SINUMERIK 840D / 840Di sl / 802D. !! 840Di sl only The user data of the NC and the remanent data of the PLC are stored in the static memory area (SRAM) of the MCI board.
• Page 27
  NCK alarms 4071 Check the position of the encoder Definitions: A machine data has been changed that affects the value of an absolute encoder position. Please check the postion values. For absolute encoders: Encoder adjustment has been changed, the machine reference of the axis position may have changed, check the encoder adjustment.
• Page 28
  NCK alarms 4077 New value %1 of MD %2 not set. Requested %3 bytes too much %4 memory. Parameters: %1 = New value of machine data %2 = Machine data number %3 = Number of bytes requested that exceeded availability %4 = Type of memory Definitions: An attempt was made to enter a new value in the specified memory configuration machine data.
• Page 29
  NCK alarms 4090 Too many errors during power-up Definitions: More than <n> errors occurred during control power-up. Reaction: NC Start disable in this channel. Alarm display. Remedy: Set the machine data correctly. Program Switch control OFF — ON. Continuation: 4100 System cycle time/scan time divider corrected for digital drive Definitions: MD10050 $MN_SYSCLOCK_CYCLE_TIME (system clock cycle) and/or MD10080…
• Page 30
  NCK alarms 4112 Servo cycle changed to %1 ms Parameters: %1 = String (new servo cycle time) Definitions: For PROFIBUS/PROFINET only: MD10060 $POSCTRL_SYSCLOCK_TIME_RATIO has been modified because of the modified DP cycle in the SDB (MD10050 $SYSCLOCK_CYCLE_TIME). Reaction: Alarm display. Remedy: MD10060 $MN_POSCTRL_SYSCLOCK_TIME_RATIO RATIO has been modified.
• Page 31
  NCK alarms 4150 [Channel %1: ] Invalid M function subprogram call configured Parameters: %1 = Channel number Definitions: MD10715 $MN_M_NO_FCT_CYCLE[n] or MD10718 $MN_M_NO_FCT_CYCLE_PAR contains invalid configuration data: An M function, which is occupied by the system and cannot be replaced by a subprogram call has been specified in MD10715 $MN_M_NO_FCT_CYCLE[n] for the configuration of the subprogram call via M function: — M0 to M5, — M17, M30,…
• Page 32
  NCK alarms 4160 [Channel %1: ] Invalid M function number configured for spindle switchover Parameters: %1 = Channel number Definitions: An M function was specified in MD20094 $MC_SPIND_RIGID_TAPPING_M_NR in order to configure the M function number for spindle switchover. The M function number is assigned by the system and cannot be used for the switcho- ver (M1 to M5, M17, M30, M40 to M45).
• Page 33
  NCK alarms 4182 [Channel %1: ] Invalid M auxiliary function number in %2%3, MD reset Parameters: %1 = Channel number %2 = MD identifier %3 = If required, MD index Definitions: In the specified machine data, a number has been specified for the configuration of an M function which is occupied by the system, and cannot be used for an assignment.
• Page 34
  NCK alarms 4185 [Channel %1: ] Illegal auxiliary function configured %2 %3 %4 Parameters: %1 = Channel number %2 = Type of auxiliary function %3 = Extension %4 = Auxiliary function value Definitions: An auxiliary function has been illegally configured. Predefined auxiliary functions cannot be reconfigured by user-defined auxiliary functions.
• Page 35
  NCK alarms Remedy: Please inform the authorized personnel/service department. Set rotary axis declaration for this machine axis in the axis-specific MD30300 $MA_IS_ROT_AX. Program Switch control OFF — ON. Continuation: 4215 [Channel %1: ] Spindle %2 declaration as modulo axis missing Parameters: %1 = Channel number %2 = Axis name, spindle number…
• Page 36
  NCK alarms 4230 [Channel %1: ] Data alteration from external not possible in current channel state Parameters: %1 = Channel number Definitions: It is not allowed to enter this data while the part program is being executed (e.g. setting data for working area limitation or for dry run feedrate).
• Page 37
  NCK alarms Remedy: Please inform the authorized personnel/service department. Correct machine data. Activate required inputs/outputs via MDs: MD10350 $MN_FASTIO_DIG_NUM_INPUTS MD10360 $MN_FASTIO_DIG_NUM_OUTPUTS MD10300 $MN_FASTIO_ANA_NUM_INPUTS MD10310 $MN_FASTIO_ANA_NUM_OUTPUTS Activation of fast inputs/outputs does not require the corresponding hardware configuration to be available at the con- trol.
• Page 38
  NCK alarms Reaction: NC not ready. Channel not ready. NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm. Remedy: Please inform the authorized personnel/service department. Alter MD10368 $MN_HW_ASSIGN_DIG_FASTOUT or MD10364 $MN_HW_ASSIGN_ANA_FASTOUT. Program Switch control OFF — ON. Continuation: 4300 Declaration in MD %1 is not allowed for axis %2.
• Page 39
  NCK alarms Program Switch control OFF — ON. Continuation: 4334 [Channel %1: ] The amount of fine correction in parameter %2 of the orientable toolholder %3 is too large Parameters: %1 = Channel number %2 = Invalid parameter of the orientable toolholder %3 = Number of the orientable toolholder Definitions: The maximum permissible value of the fine correction in an orientable toolholder is limited by the MD20188…
• Page 40
  NCK alarms 4340 [Channel %1: ] Block %2 invalid transformation type in transformation no. %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Transformation number Definitions: An invalid, i.e. undefined, number was entered in one of the machine data TRAFO_TYPE_1 … TRAFO_TYPE_8. This alarm also occurs if a certain type of transformation is only impossible on the type of control used (e.g.
• Page 41
  NCK alarms 4342 [Channel %1: ] Invalid machine data for general 5-axis transformation error no. %2 Parameters: %1 = Channel number %2 = Error type Definitions: The machine data which describe the axis directions and the basic orientation and the input axes for the general 5- axis transformation are invalid.
• Page 42
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. NC Stop on alarm at block end. Remedy: Specify the axis available in the channel. Program Clear alarm with the RESET key. Restart part program Continuation: 4345 [Channel %1: ] Invalid configuration in chained transformation no.
• Page 43
  NCK alarms 4347 [Channel %1: ] Invalid channel axis assignment in machine data %2[%3] Parameters: %1 = Channel number %2 = Name of machine data %3 = Transformation number Definitions: MD2..$MC_TRAFO_AXIS_IN_… contains an invalid entry. The following causes for the error are possible: — The entry refers to a channel axis which does not exist.
• Page 44
  NCK alarms 60. Geometry axes 1 and 2 are parallel. 61. Geometry axes 1 and 3 are parallel. 62. Geometry axes 2 and 3 are parallel. 65. The 3 geometry axes are on one plane. — 100. The maximum number of kinematic elements (total of linear axes, rotary axes, and constant elements) has been exceeded.
• Page 45
  NCK alarms Remedy: Please inform the authorized personnel/service department. Resetting of MD32420 $MA_JOG_AND_POS_JERK_ENABLE or MD35240 $MA_ACCEL_TYPE_DRIVE. Program Switch control OFF — ON. Continuation: 4400 MD alteration will cause reorganization of buffered memory (Art %1), (loss of data!) — Parameters: %1 = Memory type %2 = MD identifier, if required Definitions: A machine data has been altered that configures the buffered memory.
• Page 46
  NCK alarms 4503 [TO unit %1: ] H number %2 assigned more than once. Machine data is not set. Parameters: %1 = TO unit %2 = H number Definitions: This error can only occur if MD10880 $MN_MM_EXTERN_CNC_SYSTEM= 1 or 2. MD10890, $MN_EXTERN_TOOLPROG_MODE bit 3 is reset (this MD becomes effective at power-on).
• Page 47
  NCK alarms 4632 Logical PROFIBUS handwheel slot base address for handwheel %1 not found Parameters: %1 = Handwheel number Definitions: For PROFIBUS/PROFINET only: The logical basic address of the PROFIBUS handwheel slot in machine data array $MN_HANDWHEEL_LOGIC_ADDRESS[] indexed in machine data $MN_HANDWHEEL_MODULE was not found in the current STEP 7 hardware configuration.
• Page 48
  NCK alarms 6010 [Channel %1: ] Data block %2 not or not completely created, error code %3 Parameters: %1 = Channel number %2 = String (block name) %3 = Internal error code Definitions: Data management has detected an error during ramp-up. The specified data block may not have been created. The error number specifies the type of error.
• Page 49
  NCK alarms — _N_NC_TRA — System internal: transformation data sets, NCK-specific — _N_NC_WAL — System internal: data to describe coordinate-specific working area limitation — _N_COMPLETE_CYD — System internal: cycle and display machine data, NCK-, channel-, axis-specific c = Channel number a = Machine axis number t = TOA unit number There are also other internal system data blocks with identifiers.
• Page 50
  There is no interference with any NCK functions. It shows that the NCK has less free user memory available than spec- ified by Siemens for this control variant. The value of the actually available free user memory can also be taken from the MD18050 $MN_INFO_FREE_MEM_DYNAMIC, MD18060 $MN_INFO_FREE_MEMS_STATIC.
• Page 51
  NCK alarms 6402 [Channel %1: ] Tool change not possible. Magazine no. %2 not available Parameters: %1 = Channel ID %2 = Magazine number Definitions: The desired tool change is not possible. The magazine with the specified number is not available. Reaction: NC Start disable in this channel.
• Page 52
  NCK alarms 6405 [Channel %1: ] Command %2 has invalid PLC acknowledge parameter %3 — identifier Parameters: %1 = Channel ID %2 = Command no. %3 = PLC acknowledge parameter %4 = Error code Definitions: The specified command has been answered by the PLC with an invalid acknowledgement in the current context. The following assignments are defined for «command no.»: 1 Move tool, load or unload magazine 2 Prepare tool change…
• Page 53
  NCK alarms Remedy: Please inform the authorized personnel/service department. — Erroneous PLC communication: Correct the PLC program. — It is possible to release NCK with the PLC command 7 from the wait condition. This aborts the waiting command. Program Clear alarm with the RESET key. Restart part program Continuation: 6407 [Channel %1: ] Tool %2 cannot be placed in magazine %3 on location %4.
• Page 54
  NCK alarms 6411 [Channel %1: ] Tool %2 has reached its prewarning limit with D = %4 Parameters: %1 = Channel number %2 = Tool identifier (name) %3 = -Not used- %4 = D number Definitions: Tool monitoring: This message informs that the specified D offset has reached its prewarning limit for a time-, quantity- or wear-monitored tool.
• Page 55
  NCK alarms 6421 [Channel %1: ] Tool move not possible. Empty location for tool %2 on magazine %4 not available. Parameters: %1 = Channel ID %2 = String (identifier) %3 = -Not used- %4 = Magazine number Definitions: The desired tool motion command — triggered from the MMC or PLC — is not possible. The tool cannot be moved into the specified tool magazine.
• Page 56
  NCK alarms 6424 [Channel %1: ] Tool move not possible. Tool %2 not available/not usable. Parameters: %1 = Channel ID %2 = String (identifier) Definitions: The desired tool motion command — triggered from the HMI or PLC — is not possible. The status of the specified tool does not allow movement of the tool.
• Page 57
  NCK alarms 6430 Workpiece counter: overflow in table of monitored cutting edges. Definitions: No more cutting edges can be entered in the piece counter table. As many cutting edges can be noted for the workpiece counter as are possible in total in the NCK. This means that if for each tool each cutting edge in each TO unit is used precisely once for a workpiece then the limit is reached.
• Page 58
  NCK alarms 6433 [Channel %1: ] Block %2 %3 not available with tool management Parameters: %1 = Channel number %2 = Block number, label %3 = Source symbol Definitions: The symbol variable specified in %3 is not available with active tool management. The function GELSELT should be used with $P_TOOLP.
• Page 59
  NCK alarms 6438 [Channel %1: ] Block %2 inconsistent data modification is not permitted. Parameters: %1 = Channel number %2 = Block number, label Definitions: In a defined multitool, for example, the distance coding $TC_MTP_KD cannot be changed once the multitool location has been generated.
• Page 60
  NCK alarms 6450 [Channel %1: ] Block %2 tool change not possible. Invalid magazine location no. %3 in buffer magazine Parameters: %1 = Channel ID %2 = Block number, label %3 = Magazine location number Definitions: The desired tool change is not possible. The specified magazine location is either toolholder/spindle or empty. Only the numbers of the buffer that are not toolholder/spindle may be programmed with the NC command TCI, i.e.
• Page 61
  NCK alarms 6453 [Channel %1: ] Block %2 tool change not possible. No assignment between toolholder/ spindle no. = %3 and buffer magazine location %4 Parameters: %1 = Channel ID %2 = Block number, label %3 = Spindle no. %4 = Location no. Definitions: The desired tool change is not possible.
• Page 62
  NCK alarms 6460 [Channel %1: ] Block %2 Command ‘%3’ can only be programmed for tools. ‘%4’ does not designate a tool. Parameters: %1 = Channel number %2 = Block number, label %3 = Programmed command %4 = Programmed parameter Definitions: The specified command can only be programmed for tools.
• Page 63
  NCK alarms 6500 NC memory full Definitions: The NCK file system is full. The available buffered memory does not suffice. Note: At first commissioning, files of the NC file system may be affected such as drive data, MMC files, FIFO files, NC programs… Reaction: Alarm display.
• Page 64
  NCK alarms 6540 Too many directories in the NC memory Definitions: The number of directories in the NC file system (part of the NC memory) has reached the maximum limit. Reaction: Alarm display. Remedy: — Delete or unload directory (e.g. workpiece), or — Increase MD18310 $MN_MM_NUM_DIR_IN_FILESYSTEM.
• Page 65
  Clear alarm with the Delete key or NC START. Continuation: 6583 NC system memory full Definitions: The DRAM file system of the system area (Siemens) is full. The order cannot be executed. Reaction: Alarm display. Remedy: Delete or unload files (e.g. parts programs) Program Clear alarm with the Delete key or NC START.
• Page 66
  Alarm display. Remedy: Modify definition files /_N_DEF_DIR/_N_MACCESS_DEF or /_N_DEF_DIR/_N_UACCESS_DEF-CESS_ DEF. Please see the Siemens Programming Guide or the OEM documentation for the language commands permissible for the relevant system configurations. Program Clear alarm with the RESET key. Restart part program…
• Page 67
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Please inform the authorized personnel/service department. Do not use rapid interrupt inputs or contact the machine manufacturer with a view to retrofitting this option! Program Clear alarm with the RESET key.
• Page 68
  NCK alarms 8030 [Channel %1: ] Block %2 option ‘interpolation of more than %3 axes’ not set Parameters: %1 = Channel number %2 = Block number, label %3 = Number of permissible axes Definitions: The option for the number of interpolating axes does not correspond to the number of axes programmed in the inter- polation group.
• Page 69
  NCK alarms Remedy: Please inform the authorized personnel/service department. For retrofitting the option, please refer to your machine manufacturer or to a sales representative of SIEMENS AG, A&D MC. Program Clear alarm with the Delete key or NC START. Continuation:…
• Page 70
  One ore more options were activated, that are not licensed by the license key entered. Reaction: Alarm display. Remedy: Generate a new license key on the internet at http://www.siemens.com/automation/licence and enter it in the operating area «Setup», function (HSK) «Licenses».. Program Clear alarm with the Delete key or NC START.
• Page 71
  NCK alarms 8120 [Channel %1: ] Block %2 following axis/spindle %3 generic coupling %4 required Parameters: %1 = Channel number %2 = Block number %3 = Slave axis %4 = String Definitions: The option stage is inadequate for the desired function. Possible reasons: More couplings have been created than are permitted.
• Page 72
  NCK alarms 10208 [Channel %1: ] Continue program with NC start Parameters: %1 = Channel number Definitions: After block search with calculation, the control is in the desired state. The program can now be started with NC Start or the state can be changed for the time being with overstore/jog. Reaction: Interpreter stop Alarm display.
• Page 73
  NCK alarms 10600 [Channel %1: ] Block %2 auxiliary function during thread cutting active Parameters: %1 = Channel number %2 = Block number, label Definitions: An auxiliary function output is programmed in a thread cutting block. Reaction: Alarm display. Remedy: Consequential errors can occur if the machining path of the thread block is too short and further blocks (thread blocks) follow in which no machining stop may occur.
• Page 74
  NCK alarms 10605 [Channel %1: ] Block %2 thread pitch decrease too high Parameters: %1 = Channel number %2 = Block number, label Definitions: The thread pitch decrease is causing an axis standstill in the thread block. Reaction: Correction block is reorganized. Local alarm reaction.
• Page 75
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 10620 [Channel %1: ] Block %3 axis %2 at software limit switch %4 Parameters: %1 = Channel number %2 = Axis name, spindle number %3 = Block number, label %4 = String Definitions: During the traversing motion, the system detected that the software limit switch would be traversed in the direction…
• Page 76
  NCK alarms Reaction: Local alarm reaction. NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm at block end. Remedy: Program other motion or do not perform overlaid motion. Program Clear alarm with the RESET key. Restart part program Continuation: 10631 [Channel %1: ] Axis %2 rests at working area limit %3%4…
• Page 77
  NCK alarms 10634 [Channel %1: ] Axis %2, tool radius compensation is inactive for type %3 working area limitation, reason: The tool is not oriented parallel to the axis. Parameters: %1 = Channel number %2 = Axis, spindle %3 = 0: BCS, 1: WCS / SZS Definitions: The tool radius compensation of the working area limitation of the stated axis is not taken into account.
• Page 78
  NCK alarms Definitions: The tool radius compensation of the working area limitation of the stated axis is not taken into account. Reason: No tool is active. The alarm is reported in JOG mode. Reaction: Alarm display. Remedy: The tool radius compensation for working area limitations in JOG mode cannot be taken into account wihout an active tool.
• Page 79
  NCK alarms Remedy: Please inform the authorized personnel/service department. Correct the machine data: MD37100 $MA_GANTRY_AXIS_TYPE 0: No gantry axis 1: Master axis grouping 1 11: Slave axis grouping 1 2: Master axis grouping 2 12: Slave axis grouping 2 3: Master axis grouping 3 13: Slave axis grouping 3 Program Switch control OFF — ON.
• Page 80
  NCK alarms Remedy: Please inform the authorized personnel/service department. See Function Manual, Special Functions, Gantry Axes (G1) Program Alarm display showing cause of alarm disappears. No further operator action necessary. Continuation: 10655 [Channel %1: ] Synchronization of gantry group %2 in progress Parameters: %1 = Channel number %2 = Gantry unit…
• Page 81
  NCK alarms 10658 [Channel %1: ] Axis %2 impermissible axis status %3. Parameters: %1 = Channel number %2 = Axis number %3 = Error ID and gantry unit. Definitions: Error ID and gantry unit — 30XX => Gantry group cannot be closed, as not all gantry axes are in one channel. — 40XX =>…
• Page 82
  NCK alarms Reaction: Local alarm reaction. Interface signals are set. Alarm display. NC Stop on alarm. Remedy: Protection zone can be traversed after a new NC Start. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 10702 [Channel %1: ] NCK protection zone %2 violated during manual mode…

• Page 83: Manual Mode

  NCK alarms 10706 [Channel %1: ] NCK protection zone %2 reached with axis %3 during manual mode Parameters: %1 = Channel number %2 = Protection zone number %3 = Axis name Definitions: The workpiece-related NCK protection zone has been reached with the specified axis. Note that another tool-related protection zone is still active.

• Page 84
  NCK alarms Remedy: Check and correct positions in the NC program. Please inform the authorized personnel/service department. Check machine data: MD36100 $MA_POS_LIMIT_MINUS / MD36120 $MA_POS_LIMIT_MINUS2 and MD36110 $MA_POS_LIMIT_PLUS / MD36130 $MA_POS_LIMIT_PLUS2 for the software limit switches. Check the axis-specific interface signals: DB380x DBX1000.3 / .2 (2nd software limit switch plus/minus) to see whether the 2nd software limit switch is selected.
• Page 85
  NCK alarms Remedy: Check and correct positions in the NC program. Please inform the authorized personnel/service department. Machine data: MD36100 $MA_POS_LIMIT_MINUS/MD36120 $MA_POS_LIMIT_MINUS2 and MD36110 $MA_POS_LIMIT_PLUS/MD36130 $MA_POS_LIMIT_PLUS2 must be checked for the software limit switches. Check the axis-specific interface signals: DB380x DBX1000.3 / .2 (2nd software limit switch plus/minus) to see whether the 2nd software limit switch is selected.
• Page 86
  NCK alarms Remedy: a) Check NC program for correct positional data and, if necessary, make corrections. b) Check zero offsets (current frame) c) Correct working area limitation via G25/G26, or d) Correct working area limitation via setting data, or e) Deactivate working area limitation via setting data 43410 WORKAREA_MINUS_ENABLE=FALSE Program Clear alarm with NC START or RESET key and continue the program.
• Page 87
  NCK alarms 10733 [Channel %1: ] Block %5 axis %2 working area limitation violated, residual distance: %6 %3<ALUN> Parameters: %1 = Channel number %2 = Axis name, spindle number %3 = Unit of distance %4 = Block number, label|residual distance Definitions: The motion planned for the axis violates the currently active working area limitation.
• Page 88
  NCK alarms 10736 [Channel %1: ] Block %5 axis %2 coordinate system-specific working area limitation violated, residual distance: %6 %3<ALUN> Parameters: %1 = Channel number %2 = Axis name, spindle number %3 = Unit of distance %4 = Block number, label|residual distance Definitions: This alarm is generated if it is determined during block preparation that the programmed path of the stated axis violates the coordinate system-specific working area limitation.
• Page 89
  NCK alarms 10742 [Channel %1: ] Block %2 WAB distance invalid or not programmed Parameters: %1 = Channel number %2 = Block number, label Definitions: Possible causes: In a WAB block, the parameter DISR has not been specified or its value is less than or equal to 0. During approach or retraction with circle and active tool radius, the radius of the internally generated — WAB contour is negative.
• Page 90
  NCK alarms 10745 [Channel %1: ] Block %2 WAB end position not clear Parameters: %1 = Channel number %2 = Block number, label Definitions: In the WAB block and in the following block, the position has been programmed perpendicular to the machining direc- tion.
• Page 91
  NCK alarms 10748 [Channel %1: ] Block %2 illegal retract plane with WAB Parameters: %1 = Channel number %2 = Block number, label Definitions: By means of DISRP a position of the retraction plane has been programmed which is not situated between the safety distance (DISCL) and the starting point (during approach) and/or end point (during retraction) of the WAB movement.
• Page 92
  NCK alarms Reaction: Correction block is reorganized. Local alarm reaction. Interface signals are set. Alarm display. NC Stop on alarm at block end. Remedy: Modify part program. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 10792 [Channel %1: ] Block %2 illegal interpolation type during linear programming with…
• Page 93
  NCK alarms Reaction: Correction block is reorganized. Local alarm reaction. Interface signals are set. Alarm display. NC Stop on alarm at block end. Remedy: Modify part program. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 10795 [Channel %1: ] Block %2 end point specification during angle programming…
• Page 94
  NCK alarms 10805 [Channel %1: ] Block %2 repositioning after switch of geometry axes or transformation Parameters: %1 = Channel number %2 = Block number, label Definitions: In the asynchronous subroutine the assignment of geometry axes to channel axes was changed or the active trans- formation modified.
• Page 95
  NCK alarms 10860 [Channel %1: ] Block %2 feedrate not programmed Parameters: %1 = Channel number %2 = Block number, label Definitions: Cause: A traversing velocity has not been programmed for the displayed traversing block. Feed F or FZ: With the traversing velocity defined by feed F or FZ, F or FZ was not reprogrammed after the feed type changed, for example linear feed G94 after revolutional feedrate G95 F or G95 FZ.
• Page 96
  NCK alarms Remedy: Modify the program so that no reference is possible to the program itself. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 10865 [Channel %1: ] Block %2 FZ active, but no tool offset, tool %3 Parameters: %1 = Channel number %2 = Axis name, spindle number…
• Page 97
  NCK alarms 10870 [Channel %1: ] Block %2 facing axis for constant velocity not defined Parameters: %1 = Channel number %2 = Block number, label Definitions: Constant cutting speed was selected although no transverse axis was applied as reference axis for constant cutting speed or assigned through SCC[AX].
• Page 98
  NCK alarms 10882 [Channel %1: ] Block %2 activation of chamfers or radii (non-modal) without traversing movement in the block Parameters: %1 = Channel number %2 = Block number, label Definitions: No chamfer or radius has been inserted between 2 linear or circle contours (edge breaking) because: There is no straight line or circle contour in the plane There is a movement outside the plane A plane change has taken place…
• Page 99
  NCK alarms 10891 [Channel %1: ] Block %2 multiplicity of node is greater than its order Parameters: %1 = Channel number %2 = Block number, label Definitions: In the B spline the distance between nodes PL (node = point on spline at which 2 polynomials meet) has been pro- grammed with zero too often in succession (i.e.
• Page 100
  NCK alarms 10911 [Channel %1: ] Block %2 transformation prohibits to traverse the pole Parameters: %1 = Channel number %2 = Block number, label Definitions: The given curve passes through the pole of the transformation. Reaction: Interpreter stop Local alarm reaction. NC Start disable in this channel.
• Page 101
  Interface signals are set. Alarm display. NC Stop on alarm. Remedy: Change parameterization. Increase work memory. Use standard Look Ahead. Contact Siemens if necessary. Program Clear alarm with the RESET key. Restart part program Continuation: 10916 [Channel %1: ] Block %2 preparation problem in Look Ahead (module %3, identifier…
• Page 102
  NCK alarms 10930 [Channel %1: ] Block %2 interpolation type not allowed in stock removal contour Parameters: %1 = Channel number %2 = Block number, label Definitions: The following types of interpolation are allowed in the contour program for stock removal: G00, G01, G02, G03, CIP, Reaction: Local alarm reaction.
• Page 103
  NCK alarms Reaction: Local alarm reaction. NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Increase the size of the program with the stock removal contour to include at least 3 NC blocks with movements in both axes of the current machining plane.
• Page 104
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 10961 [Channel %1: ] Block %2 maximum cubic polynomials are allowed on active radius compensation. Parameters: %1 = Channel number %2 = Block number, label Definitions: With active radius compensation, only up to cubic polynomials are permissible for the geometry axes.
• Page 105
  NCK alarms 12000 [Channel %1: ] Block %2 address %3 programmed repeatedly Parameters: %1 = Channel number %2 = Block number, label %3 = Source string of the address Definitions: Most addresses (address types) may only be programmed once in an NC block, so that the block information remains unambiguous (e.g.
• Page 106
  NCK alarms 12040 [Channel %1: ] Block %2 expression %3 is not of data type ‘AXIS’ Parameters: %1 = Channel number %2 = Block number, label %3 = Source string in the block Definitions: Some keywords require that the data in their parameters be written in variables of the type «AXIS». For example, in the keyword PO the axis identifier must be specified in the parenthesized expression, and it must be defined as a variable of the AXIS type.
• Page 107
  NCK alarms Remedy: Press the NC Stop key and select the function «Correction block» with the softkey PROGRAM CORRECT. The cor- rection pointer positions on the incorrect block. No remedy is required. You should, however, check whether the G function last programmed really is the one required. Program Clear alarm with NC START or RESET key and continue the program.
• Page 108
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Press the NC Stop key and select the function «Correction block» with the softkey PROGRAM CORRECT. The cor- rection pointer positions on the incorrect block. Program function without parameter transfer. Program Clear alarm with NC START or RESET key and continue the program.
• Page 109
  NCK alarms 12120 [Channel %1: ] Block %2 G function not separately programmed Parameters: %1 = Channel number %2 = Block number, label Definitions: The G function programmed in this block must be alone in the block. No general addresses or synchronous actions may occur in the same block.
• Page 110
  NCK alarms 12150 [Channel %1: ] Block %2 operation %3 not compatible with data type Parameters: %1 = Channel number %2 = Block number, label %3 = String (violating operator) Definitions: The data types are not compatible with the required operation (within an arithmetic expression or in a value assign- ment).
• Page 111
  NCK alarms 12161 [Channel %1: ] Block %2 Error on defining the limit %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Impermissible limit value Definitions: The alarm may have the following causes. — During definition (DEF) or redefinition (REDEF) of a variable’s limits, a value was entered for the upper limit that is smaller than that for the lower limit.
• Page 112
  NCK alarms 33 Torque [Nm] 34 Torque constant [Nm/A] 35 Current controller gain [V/A] 36 Speed controller gain [Nm/rad s 1] 37 Speed [rev/min] 42 Power [kW] 43 Low power [µA] 46 Low torque [µNm] 48 Per mill HZ_PER_SEC = 49, [Hz/s] 65 Flow [l/min] 66 Pressure [bar] 67 Volume [cm³]…
• Page 113
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 12170 [Channel %1: ] Block %2 name %3 defined several times Parameters: %1 = Channel number %2 = Block number, label %3 = Symbol in block Definitions: The symbol shown in the error message has already been defined in the active part program.
• Page 114
  NCK alarms 12190 [Channel %1: ] Block %2 variable of type ARRAY has too many dimensions Parameters: %1 = Channel number %2 = Block number, label Definitions: Array with variables of type STRING may be no more than 1-dimensional, and with all other variables no more than 2-dimensional.
• Page 115
  NCK alarms 12210 [Channel %1: ] Block %2 string %3 too long Parameters: %1 = Channel number %2 = Block number, label %3 = String in the source block Definitions: — In the definition of a STRING type variable, an attempt has been made to initialize more than 200 characters. — In an allocation, it has been found that the string does not fit the given variable.
• Page 116
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 12260 [Channel %1: ] Block %2 too many initialization values specified %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Source string Definitions: In the initialization of an array (array definition and value assignments to individual array elements) there are more initialization values than array elements.
• Page 117
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Press the NC Stop key and select the function «Correction block» with the softkey PROGRAM CORRECT. The cor- rection pointer positions on the incorrect block. Select DEFINE instruction with another macro name. Program Clear alarm with NC START or RESET key and continue the program.
• Page 118
  NCK alarms 12300 [Channel %1: ] Block %2 call-by-reference parameter missing on subroutine call %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Source string Definitions: In the subroutine definition, a formal REF parameter (call-by-reference parameter) has been specified with no actual parameter assigned to it.
• Page 119
  NCK alarms Remedy: Press the NC Stop key and select the function «Correction block» with the softkey PROGRAM CORRECT. The cor- rection pointer positions on the incorrect block. Program the missing AXIS parameter in the call. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 12320 [Channel %1: ] Block %2 parameter %3 is no variable…
• Page 120
  NCK alarms 12340 [Channel %1: ] Block %2 number of parameters too high %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Source string Definitions: When calling a function or a procedure (predefined or user-defined) more parameters were transferred than defined. Predefined functions and procedures: The number of parameters has been set permanently in the NCK.
• Page 121
  NCK alarms 12370 [Channel %1: ] Block %2 range of values %3 not permissible Parameters: %1 = Channel number %2 = Block number, label %3 = Source string Definitions: A variable has been initialized with a value range outside an initialization block. The definition of program-global vari- ables is allowed only in special initialization blocks.
• Page 122
  NCK alarms 12390 [Channel %1: ] Block %2 initialization value %3 cannot be converted Parameters: %1 = Channel number %2 = Block number, label %3 = Source string Definitions: During initialization, a value has been assigned to a variable that does not correspond to the type of the variable, nor can it be converted to the data type of the variable.
• Page 123
  NCK alarms 12410 [Channel %1: ] Block %2 incorrect index type for %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Source string Definitions: In assigning a value to an element of an array variable, the array index was specified in a way that is not allowed. Only the following are allowed as array index (in square brackets): — Axis identifier, provided the array variable was defined as data type FRAME.
• Page 124
  NCK alarms 12440 [Channel %1: ] Block %2 maximum number of formal arguments exceeded Parameters: %1 = Channel number %2 = Block number, label Definitions: In the definition of a procedure (a subroutine) or in an EXTERN instruction, more than 127 formal parameters have been specified.
• Page 125
  NCK alarms Remedy: Generally reduce the number of symbols in the affected block (possibly by using the array technique or by using R parameters), or adapt the corresponding machine data (see below). MD28020 $MC_MM_NUM_LUD_NAMES_TOTAL with error in LUD blocks (i.e. if more variable definitions were made in the active part program than allowed by the MD).
• Page 126
  NCK alarms 12480 [Channel %1: ] Block %2 subroutine %3 already defined Parameters: %1 = Channel number %2 = Block number, label %3 = Source string Definitions: The name used in the PROC or EXTERN instruction has already been defined in another call description (e.g. for cycles).
• Page 127
  NCK alarms Remedy: Press the NC Stop key and select the function «Correction block» with the softkey PROGRAM CORRECT. The cor- rection pointer positions on the incorrect block. — Use the REDEF instruction only in the INITIAL_INI block — Using the operator panel, set the current protection level to at least the same level as that of the variable with the highest level — Program protection level within the permissible value range — Only program new protection levels that are lower than the old values…
• Page 128
  NCK alarms 12510 [Channel %1: ] Block %2 too many machine data %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Source symbol Definitions: In the part program, in the machine data file (…_TEA) and in the initialization file (…_INI), no more than 5 machine data may be used per block.
• Page 129
  NCK alarms 12530 [Channel %1: ] Block %2 invalid index for %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Source string Definitions: In macro definitions, an attempt was made to define a G function with more than 3 decades or an M function with more than 2 decades as identifier of the macro.
• Page 130
  NCK alarms Remedy: Press the NC Stop key and select the function «Compensation block» with the softkey PROGRAM CORRECT. The cursor positions itself on the incorrect block. — Correct the name used (writing error) — Check definitions of variables, subroutines and macros — Declare subroutine with EXTERN, load subroutine to SPF-Dir — Check interface definition of subroutine — Check options.
• Page 131
  NCK alarms 12554 [Channel %1: ] Block %2 replacement cycle %3 for the predefined procedure is missing. Parameters: %1 = Channel number %2 = Block number, label %3 = Cycle name Definitions: The replacement cycle that is to be called instead of the predefined procedure is not present / unknown in the control.
• Page 132
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 12560 [Channel %1: ] Block %2 programmed value %3 exceeds allowed limits Parameters: %1 = Channel number %2 = Block number, label %3 = Source string Definitions: In a value assignment, the permissible value range of the data type has been exceeded.
• Page 133
  NCK alarms 12586 [Channel %1: ] Block %2 motion synchronous action: type conflict in variable %3 Parameters: %1 = Channel number %2 = Block number %3 = Source symbol Definitions: Type conversion is not possible for online variables $A.. or $V.., which are evaluated or written in the interpolation cycle.
• Page 134
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 12589 [Channel %1: ] Block %2 motion synchronous action: variable %3 not allowed with modal ID Parameters: %1 = Channel number %2 = Block number %3 = Variable name Definitions: The modal ID in motion synchronous action must not be formed by means of an on-line variable.
• Page 135
  NCK alarms Remedy: Correct INI file or correct MD and create new INI file (via «upload»). Program Switch control OFF — ON. Continuation: 12610 [Channel %1: ] Block %2 accessing single character with call-by-reference parameter not possible %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Source string Definitions:…
• Page 136
  NCK alarms 12640 [Channel %1: ] Block %2 invalid nesting of control structures Parameters: %1 = Channel number %2 = Block number Definitions: Error in program run: Opened control structures (IF-ELSE-ENDIF, LOOP-ENDLOOP etc.) are not terminated or there is no beginning of loop for the programmed end of loop. Example: LOOP ENDIF ENDLOOP Reaction:…
• Page 137
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 12660 [Channel %1: ] Block %2 motion synchronous action: variable %3 reserved formotion synchronous actions and technology cycles Parameters: %1 = Channel number %2 = Block number %3 = Variable name Definitions: The displayed variable may only be used in motion synchronous actions or in technology cycles.
• Page 138
  The programmed language element is not allowed or unknown in external language mode. Only the language ele- ments from Siemens mode which are used for subprogram calls (except for Lxx) and the language constructs for pro- gram repetition with REPEAT (UNTIL) are allowed.
• Page 139
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Deactivate modal cycles or modal macro calls if one of the above mentioned G functions has been programmed. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 12724 [Channel %1: ] Block %2 no radius programmed for cylinder interpolation activation/…
• Page 140
  NCK alarms 12730 [Channel %1: ] Block %2 no valid transformation machine data parameterized Parameters: %1 = Channel number %2 = Block number, label Definitions: The machine data MD24100 $MC_TRAFO_TYPE_1, MD24110 $MC_TRAFO_AXES_IN_1[1], MD24210 $MC_TRAFO_AXES_IN_2[1] are incorrectly set for G07.1, G12.1. Reaction: Correction block is reorganized.
• Page 141
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Read out the part program, modify it with a text editor (e.g., insert blanks or comments before the displayed block), so that after reading it in again the part program has a different structure in the memory. Program Clear alarm with the RESET key.
• Page 142
  NCK alarms 14009 [Channel %1: ] Block %2 illegal program path %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Program path Definitions: The part program command CALLPATH was called with a parameter (program path) referring to a directory which does not exist in the file system of the NCK.
• Page 143
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Ensure that the subroutine (alarm parameter %3) — is available in the parts program memory — has been released and is not being edited — is available in the search path if not being called via an absolute path name. Program Clear alarm with NC START or RESET key and continue the program.
• Page 144
  NCK alarms Program Clear alarm with the Delete key or NC START. Continuation: 14015 [Channel %1: ] Block %2 program %3 is not enabled Parameters: %1 = Channel number %2 = Block number, label %3 = Program name Definitions: The execution right currently set in the control (e.g. key switch position 0) is inadequate to execute part program %3. Reaction: Correction block is reorganized.
• Page 145
  Interface signals are set. Alarm display. Remedy: Modify parts program. Please see the Siemens Progamming Guide or OEM documentation for the language com- mands permissible for the relevant system configuration. Program Clear alarm with NC START or RESET key and continue the program.
• Page 146
  NCK alarms 14022 [Channel %1: ] Block %2 error on function or procedure call, error code %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Error code Definitions: An error occurred during a function or procedure call. The cause of the error is indicated more closely by an error code.
• Page 147
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Modify part program. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 14028 [Channel %1: ] Block %2 motion-synchronous action: Technology cycle programmed with too many parameters Parameters: %1 = Channel number…
• Page 148
  NCK alarms 3. Center points: A new circle center is calculated using the circle radius at the starting position. It lies on the mid- perpendicular positioned on the connecting straight line from the starting point to the end point of the circle. The angle in the radian measure between both straight lines from the starting point to the center calculated/programmed as such must be lower than the root of 0.001 (corresponding to approx.
• Page 149
  NCK alarms 14050 [Channel %1: ] Block %2 nesting depth for arithmetic operations exceeded Parameters: %1 = Channel number %2 = Block number, label Definitions: For calculating arithmetic expressions in NC blocks, an operand stack with a fixed set size is used. With very complex expressions, this stack can overflow.
• Page 150
  NCK alarms 14060 [Channel %1: ] Block %2 invalid skip level with differential block skip Parameters: %1 = Channel number %2 = Block number, label Definitions: With «Differential block skip», a skip level greater than 7 has been specified. (In packet 1 specification of a value for the skip level is rejected by the converter as a syntax error, i.e.
• Page 151
  NCK alarms 14082 [Channel %1: ] Block %2 label %3 program section not found Parameters: %1 = Channel number %2 = Block number, label %3 = Start or end label Definitions: The start point for repetition of the program part with CALL <program name> BLOCK <start label> TO <end label> has not been found or the same program part repetition has been called recursively.
• Page 152
  NCK alarms 14091 [Channel %1: ] Block %2 illegal function, index %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Index Definitions: A function has been programmed or triggered which is not permitted in the current program context. The function in question is encoded in the «index»…
• Page 153
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: — Correct the part program according to which of the above errors is involved. — Program SPOS. — Set the correct master spindle with SETMS. Program Clear alarm with NC START or RESET key and continue the program.
• Page 154
  NCK alarms 14095 [Channel %1: ] Block %2 radius for circle programming too small Parameters: %1 = Channel number %2 = Block number, label Definitions: The radius entered for radius programming is too small, i.e. the programmed radius is smaller than half of the distance between start and end point.
• Page 155
  NCK alarms Remedy: Please inform the authorized personnel/service department. Check the transferred parameter (axis name) of the func- tion AXNAME to determine whether a geometry, channel or machine axis of this name has been configured by means of the machine data: MD10000 $MN_AXCONF_MACHAX_NAME_TAB MD20060 $MC_AXCONF_GEOAX_NAME_TAB MD20080 $MC_AXCONF_CHANAX_NAME_TAB…
• Page 156
  NCK alarms Remedy: Press the NC Stop key and select the function «Correction block» with the softkey PROGRAM CORRECT. The cor- rection pointer positions on the incorrect block. — Check the number of the transformation grouping when calling the part program with the keyword TRAORI(n) (n … number of the transformation grouping).
• Page 157
  NCK alarms Remedy: Change the NC program and/or the settings of the machine data Program Clear alarm with NC START or RESET key and continue the program. Continuation: 14106 [Channel %1: ] Block %2 orientation calculation not possible with ORISOL. Parameters: %1 = Channel number %2 = Block number, label…
• Page 158
  NCK alarms 14109 [Channel %1: ] Block %2 simultaneous linear and rotary axis movement with static orientation transformation. Parameters: %1 = Channel number %2 = Block number, label Definitions: The interpolation type CP (C group code 49) is not permitted with an active static orientation transformation if linear and rotary axes have to interpolate simultaneously.
• Page 159
  NCK alarms 14112 [Channel %1: ] Block %2 programmed orientation path not possible Parameters: %1 = Channel number %2 = Block number, label Definitions: In 5-axis transformation, the two orientation axes place a coordinate system comprising lengths and circles of latitude on a spherical surface.
• Page 160
  NCK alarms 14117 [Channel %1: ] Block %2 no angle or direction of the cone programmmed Parameters: %1 = Channel number %2 = Block number, label Definitions: With taper circumference interpolation of orientation (ORICONCW and ORICONCC), either the opening angle or the direction vector of the taper must be programmed.
• Page 161
  NCK alarms Remedy: Modify the part program so that the orientation vectors of a block are not directly opposed to each other, for instance by dividing the block up into 2 subblocks. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 14121 [Channel %1: ] Block %2 no orientation defined (distance equals zero).
• Page 162
  NCK alarms 14124 [Channel %1: ] Block %2 start tangent for orientation is zero Parameters: %1 = Channel number %2 = Block number, label Definitions: With taper circumference interpolation with tangential continuation (ORICONTO), the start tangent of orientation must not be zero. Reaction: Correction block is reorganized.
• Page 163
  NCK alarms Reaction: Correction block is reorganized. Interpreter stop Interface signals are set. Alarm display. Remedy: Modify part program. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 14128 [Channel %1: ] Block %2 absolute programming of the orienting rotation with active ORIROTC.
• Page 164
  NCK alarms 14131 [Channel %1: ] Block %2 orientation axes and lead/tilt angles programmed Parameters: %1 = Channel number %2 = Block number, label Definitions: An orientation angle and a leading or sideways angle were programmed at the same time. Reaction: Correction block is reorganized.
• Page 165
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Adapt machine data. Program Clear alarm with the RESET key. Restart part program Continuation: 14136 [Channel %1: ] Block %2 Orientation polynomial is not permitted Parameters: %1 = Channel number %2 = Block number, label…
• Page 166
  NCK alarms 14139 [Channel %1: ] Block %2 Polynomial for angle of rotation PO[THT] is not permitted Parameters: %1 = Channel number %2 = Block number, label Definitions: A polynomial for the angle of rotation of orientation (PO[THT]) can only be programmed, if the active transformation supports it.
• Page 167
  NCK alarms 14147 [Channel %1: ] Block %2 spline for orientation not possible. Parameters: %1 = Channel number %2 = Block number, label Definitions: If an orientation has been programmed while BSPLINE is active, the interpolation of tool orientation must be interpolated via a 2nd space curve. This means that G code ORICURVE must be active for the interpolation of the orientation.
• Page 168
  NCK alarms 14152 [Channel %1: ] Block %2 tool carrier: invalid orientation. Error code: %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Error code Definitions: An attempt was made to define a tool orientation by means of the active frame which cannot be reached with the cur- rent toolholder kinematics.
• Page 169
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. NC Stop on alarm at block end. Remedy: Enter a valid fine correction value. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 14155 [Channel %1: ] Block %2 invalid base frame definition for tool carrier offset…
• Page 170
  NCK alarms 14159 [Channel %1: ] Block %2 more than two angles programmed with ROTS or AROTS Parameters: %1 = Channel number %2 = Block number, label Definitions: Frame rotations are described using space angles with the language commands ROTS or AROTS. A maximum of two angles can be programmed.
• Page 171
  NCK alarms Remedy: Correct the tool data of the active tool, or modify the part program in the case of error 7. Alternatively, suppress all error alarms with the aid of MD20125 $MC_CUTMOD_ERR. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 14165 [Channel %1: ] Block %2 selected ISO H/D number %3 does not match tool %4…
• Page 172
  ISO3 mode. When writing the tool offset with G10: Only tool offsets 1 — 98 are permissible in ISO2 and ISO3 modes. Tool offset H99 can only be written in Siemens programming mode (G290) with $TC_DPx[y,z]=. Reaction: Correction block is reorganized.
• Page 173
  The alarm is also output, if MD10890 $MN_EXTERN_TOOLPROG_MODE, bit6=1: If the Siemens offset memory with H99 or a cutting edge has been selected in Siemens mode, both the tool length and tool radius offsets will have to be reselected the next time the ISO offset memory is selected.
• Page 174
  Identifier 2: A toolcarrier has been activated in Siemens mode, and a tool offset is now activated in ISO2 mode. Identifier 3: A tool is active in the adapter in Siemens mode, and a tool offset is now activated in ISO2 mode.
• Page 175
  NCK alarms Remedy: Enter valid string in SD42984 $SC_CUTDIRMOD. Program Clear alarm with the RESET key. Restart part program Continuation: 14197 [Channel %1: ] Block %2 D number and H number programmed simultaneously Parameters: %1 = Channel number %2 = Block number, label Definitions: A D word and H word have been programmed simultaneously.
• Page 176
  NCK alarms 14200 [Channel %1: ] Block %2 negative polar radius Parameters: %1 = Channel number %2 = Block number, label Definitions: In the endpoint specification of a traversing block with G00, G01, G02 or G03 in polar coordinates, the polar radius entered for the keyword RP=…
• Page 177
  NCK alarms Remedy: Correct the NC part program. Permissible inputs for the pole radius are only positive, absolute values that specify the distance between the reference point and the new pole. (The direction is defined with the pole angle AP=…). Program Clear alarm with NC START or RESET key and continue the program.
• Page 178
  NCK alarms 14290 [Channel %1: ] Block %2 polynominal degree greater than 5 programmed for polynominal interpolation Parameters: %1 = Channel number %2 = Block number, label Definitions: A polynominal degree greater than five was programmed for the polynominal interpolation. You can only program poly- nomials up to the 5th degree.
• Page 179
  NCK alarms 7: The DRF movement for this axis cannot be executed as a velocity override of the path with the handwheel is active and the axis belongs to the path 8: The DRF movement for this axis cannot be executed as the contour handwheel is active with this handwheel and the axis belongs to the path 9: The DRF movement for this axis cannot be executed as the axis is a PLC axis with handwheel override that is active with this handwheel…
• Page 180
  NCK alarms 14404 [Channel %1: ] Block %2 illegal parameterization of transformation Parameters: %1 = Channel number %2 = Block number, label Definitions: Error has occurred when selecting transformation. Possible causes of error: — An axis traversed by the transformation has not been enabled: — is being used by another channel (->…
• Page 181
  NCK alarms 14412 [Channel %1: ] Block %2 transformation active at geometry axis changeover Parameters: %1 = Channel number %2 = Block number, label Definitions: It is not permissible to change the assignment of geometry axes to channel axes when transformation is active. Reaction: Correction block is reorganized.
• Page 182
  NCK alarms 14420 [Channel %1: ] Block %2 index axis %3 frame not allowed Parameters: %1 = Channel number %2 = Block number, label %3 = Axis Definitions: The axis is to be traversed as an indexing axis, but a frame is active. This is not allowed by MD32074 $MA_FRAME_OR_CORRPOS_NOTALLOWED.
• Page 183
  NCK alarms 4. Subroutine structure with keyword and subroutine name (with parameter transfer «call-by-reference»): PROC UPNAME (Typ1 VARNAME1, Typ2 VARNAME2, …) ENDPROC Program Clear alarm with NC START or RESET key and continue the program. Continuation: 14520 [Channel %1: ] Block %2 illegal PROC instruction in data definition section Parameters: %1 = Channel number %2 = Block number, label…
• Page 184
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 14541 [Channel %1: ] Block %2 contour tool: the max. limit angle has been programmed more than once (edge D%3) Parameters: %1 = Channel number %2 = Block number, label %3 = Edge number, label Definitions:…
• Page 185
  NCK alarms 14544 [Channel %1: ] Block %2 contour tool: edge D%3 is not positioned between the two border edges Parameters: %1 = Channel number %2 = Block number, label %3 = Edge number, label Definitions: On defining a form tool with limit, all edges must be positioned between the edge with the minimum limit angle and the edge with the maximum limit angle when rotating counter-clockwise.
• Page 186
  NCK alarms 14547 [Channel %1: ] Block %2 contour tool: checksum erroneous or not available Parameters: %1 = Channel number %2 = Block number, label Definitions: When MD20372 $MC_SHAPED_TOOL_CHECKSUM was set, no edge was found for which the tool length compo- nents and the tool radius equal the negative sum of the previous edges.
• Page 187
  NCK alarms Remedy: Change the NC program. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 14550 [Channel %1: ] Block %2 contour tool: impermissible tool contour change. Code no. Parameters: %1 = Channel number %2 = Block number, label %3 = Error code Definitions:…
• Page 188
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: — Release memory, e.g. by deleting part programs — Modify MD18360 $MN_MM_EXT_PROG_BUFFER_SIZE and/or MD18362 $MN_MM_EXT_PROG_NUM. Program Clear alarm with the RESET key. Restart part program Continuation: 14601 [Channel %1: ] Block %2 reload buffer could not be deleted…
• Page 189
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: — Acknowledge the alarm by pressing the RESET key — Repeat program selection — Start the part program 14610 [Channel %1: ] Block %2 compensation block not possible Parameters: %1 = Channel number %2 = Block number, label…
• Page 190
  Otherwise, the A&D MC system support should be contacted with a precise description of the error situation: (contact SIEMENS AG, System Support for A&D MC products, Hotline (Tel.:see alarm 1000) Program Switch control OFF — ON.
• Page 191
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Proceed as in the case of a system error. Program Clear alarm with the RESET key. Restart part program Continuation: 14710 [Channel %1: ] Block %2 error in initialization sequence in function %3 Parameters: %1 = Channel number %2 = Block number, label…
• Page 192
  NCK alarms Remedy: Please inform the authorized personnel/service department. If parameter %3= 0 -3: If the alarm or alarms occur on RESET: Check the settings of machine data MD20110 $MC_RESET_MODE_MASK, MD20120 $MC_TOOL_RESET_VALUE, MD20121 $MC_TOOL_PRESEL_RESET_VALUE, MD20122 $MC_TOOL_RESET_NAME (only if tool management is active), MD20130 $MC_CUTTING_EDGE_RESET_VALUE, MD20132 $MC_SUMCORR_RESET_VALUE, MD20126 $MC_TOOL_CARRIER_RESET_VALUE, MD20150 $MC_GCODE_RESET_VALUES, MD20154 $MC_EXTERN_GCODE_RESET_VALUES,…
• Page 193
  NCK alarms 14751 [Channel %1: ] Block %2 resources for motion synchronous actions not sufficient (code: %3) Parameters: %1 = Channel number %2 = Block number, label %3 = Identifier Definitions: Processing of motion-synchronous actions requires resources that are configured using MD28060 $MC_MM_IPO_BUFFER_SIZE, MD28070 $MC_MM_NUM_BLOCKS_IN_PREP, MD28251 $MC_MM_NUM_SAFE_SYNC_ELEMENTS, MD28250 $MC_MM_NUM_SYNC_ELEMENTS, and MD28253 $MC_MM_NUM_SYNC_STRINGS.
• Page 194
  NCK alarms 14754 [Channel %1: ] Block %2 motion synchronous actions and wrong feed type Parameters: %1 = Channel number %2 = Block number, label Definitions: The active feed type is not allowed for the motion synchronous action or for the function «Several feeds». Reaction: Correction block is reorganized.
• Page 195
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 14758 [Channel %1: ] Block %2 programmed value not available Parameters: %1 = Channel number %2 = Block number, label Definitions: The synchronous variables $AA_LOAD, $AA_TORQUE, $AA_POWER and $AA_CURR are available only for the SIMODRIVE611D drive.
• Page 196
  NCK alarms 14761 [Channel %1: ] Block %2 motion synchronous action: DELDTG function not allowed with active tool radius compensation Parameters: %1 = Channel number %2 = Block number, label Definitions: Rapid delete distance-to-go for synchronous actions is not allowed with DELDTG when tool radius compensation is active.
• Page 197
  NCK alarms 14770 [Channel %1: ] Block %2 auxiliary function programmed incorrectly Parameters: %1 = Channel number %2 = Block number, label Definitions: The permissible number of programmed auxiliary functions per NC block has been exceeded or more than one aux- iliary function of the same auxiliary function group has been programmed (M and S function).
• Page 198
  NCK alarms TechCycle option Liftfast option ProgAccel option AllAsupSynact option CmdAxSpind option Mea2 option ProgAnaOut option OptAaTOff option MachineMaintenance option PathFeedSAInput option ElecTransfer option Cut3D option CDA option Reserved: generic coupling option Measuring cycles option ForceControl option Reaction: Correction block is reorganized. Interface signals are set.
• Page 199
  NCK alarms 14790 [Channel %1: ] Block %2 axis %3 programmed by PLC Parameters: %1 = Channel number %2 = Block number, label %3 = Axis Definitions: In the NC block, an axis has been programmed that is already being traversed by the PLC. Reaction: Correction block is reorganized.
• Page 200
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Adjust the value range in accordance with the Programming Guide. Values of 1 … 200% are allowed. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 14812 [Channel %1: ] Block %2 SOFTA not available for axis %3…
• Page 201
  NCK alarms 14824 [Channel %1: ] Block %2 conflict with GWPS Parameters: %1 = Channel number %2 = Block number, label Definitions: The functions of constant grinding wheel surface speed GWPS and constant cutting speed G96 S… have been acti- vated at the same time for a spindle.
• Page 202
  NCK alarms 14860 [Channel %1: ] Block %2 Selection of the tool cutting rate not allowed. Cause %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Cause of the error Definitions: Selection of the cutting rate SVC is not permissible in the current state Causes of the problem: the following function is active.
• Page 203
  NCK alarms 14863 [Channel %1 ] Block %2 The programmed SVC value is zero or negative Parameters: %1 = Channel number %2 = Block number, label Definitions: The programmed value for the cutting velocity SVC is zero or negative. Reaction: Correction block is reorganized.
• Page 204
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Locate the position of the intermediate point with the parameters I, J and K in such a way that it actually is located between the initial and end points of the circle or do not make use of this type of circle programming and instead pro- gram the circle with radius or opening angle or center point parameters.
• Page 205
  Further machining with the data is not recommended. Please load a suitable archive file before continuing machining to avoid subsequent problems. Please inform the authorized personnel/service department. File /_N_MPF_DIR/_N_SIEMDIAGMEMPF_MPF contains information that may help Siemens for error diagnosis. Alarms Diagnostics Manual, 07/2010, 6FC5398-8BP40-0BA0…
• Page 206
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 15150 [Channel %1: ] Block %2 reload from external aborted Parameters: %1 = Channel number %2 = Block number, label Definitions: Execution from external was aborted because the reload buffer does not have enough machine function blocks (tra- versing blocks, auxiliary function, dwell time etc.).
• Page 207
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Modify part program. Program Clear alarm with the RESET key. Restart part program Continuation: 15166 [Channel %1: ] User system asup _N_ASUP_SPF not available Parameters: %1 = Channel number Definitions:…
• Page 208
  NCK alarms 15172 [Channel %1: ] Block %2 subroutine %3. No interface available at time of preprocessing. Parameters: %1 = Channel number %2 = Block number, label %3 = Subroutine name Definitions: In compilation mode no program interface of the subroutine to be called was available at the time of pre-compilation. Reaction: Interpreter stop Interface signals are set.
• Page 209
  NCK alarms 15176 [Channel %1: ] Block %2 Program%3 may only be executed after Power ON Parameters: %1 = Channel number %2 = Block number, label %3 = File name Definitions: If an encrypted program is loaded to the NCK, an NCK reset (restart) must be performed afterwards, because internal data for efficient processing of the encrypted program are preprocessed during NCK power-up.
• Page 210
  NCK alarms 15185 [Channel %1: ] %2 errors in INI file Parameters: %1 = Channel number %2 = Number of detected errors Definitions: Errors were found when processing initialization program _N_INITIAL_INI. This alarm will also be output, if errors are found during editing of _N_INITIAL_INI in the GUD definition files or if errors are found on ramp-up in the macro definition files.
• Page 211
  NCK alarms 15188 [Channel %1: ] Error during execution of ASUB file %3. Parameters: %1 = Channel number %2 = Is not used %3 = ASUB file name Definitions: An error has occurred on executing an ASUB. Alarm 15188 displays the name of the program that was started as ASUB.
• Page 212
  NCK alarms Reaction: Alarm display. Remedy: Enter only positive number of passes within the range of values. Program Clear alarm with the Delete key or NC START. Continuation: 15310 [Channel %1: ] Block %2 file requested during block search is not available Parameters: %1 = Channel number %2 = Block number, label…
• Page 213
  NCK alarms Remedy: Repeat the input with corrected label. Program Clear alarm with the Delete key or NC START. Continuation: 15350 [Channel %1: ] Block %2 search target not found Parameters: %1 = Channel number %2 = Block number, label Definitions: The specified program has been searched to the end of the program without the selected search target having been found.
• Page 214
  NCK alarms Remedy: Find search destination in which the axes are programmed using an absolute reference. Deactivate adding of the accumulated search position with SD42444 $SC_TARGET_BLOCK_INCR_PROG = FALSE. Use search run with calculation «at contour». Program Clear alarm with the RESET key. Restart part program Continuation: 15395 [Channel %1: ] Master-slave not executable during block search…
• Page 215
  NCK alarms 15420 [Channel %1: ] Block %2 instruction in current mode not allowed Parameters: %1 = Channel number %2 = Block number, label Definitions: The alarm is output in the following situations: — The interpreter has detected an illegal instruction (e.g. a motion command) while processing an INI file or a definition file (macro or GUD).
• Page 216
  Definitions: A SETAL command has been programmed with a cycle alarm number smaller than 60 000 or greater than 67 999. Alarm reaction of Siemens standard cycles: Nos. 61 000 -61 999: Interpreter stop; delete with Reset Nos. 62 000 — 62 999: Compensation block; delete with NC Start…
• Page 217
  NCK alarms Remedy: Modify part program. Program Clear alarm with the RESET key. Restart part program Continuation: 15900 [Channel %1: ] Block %2 touch probe not allowed Parameters: %1 = Channel number %2 = Block number, label Definitions: Measure with deletion of distance-to-go In the part program, an illegal probe has been programmed with the command MEAS (measure with deletion of dis- tance-to-go).
• Page 218
  NCK alarms 15950 [Channel %1: ] Block %2 no traverse motion programmed Parameters: %1 = Channel number %2 = Block number, label Definitions: Measure with deletion of distance-to-go In the part program, no axis or a traversing path of zero has been programmed with the command MEAS (measure with deletion of distance-to-go).
• Page 219
  NCK alarms Remedy: Modify part program. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 16010 [Channel %1: ] Block %2 machining stop after lift fast Parameters: %1 = Channel number %2 = Block number, label Definitions: LIFTFAST without interrupt routine (Asup) has been programmed.
• Page 220
  NCK alarms 16017 [Channel %1: ] Axis %2 Identifier %3, LIFTFAST ignores this axis, current axis not capable of retraction Parameters: %1 = Channel %2 = Axis, spindle %3 = Identifier Definitions: LIFTFAST cannot be applied to the axis. Alarm can be suppressed via MD11415 $MN_SUPPRESS_ALARM_MASK_2 bit 11. Identifiier (parameter 3) is bit-coded and displays some possible causes for the alarm: 0x01Axis is in another channel 0x02Axis is in spindle mode (e.g.
• Page 221
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Modify the part program if necessary. Program Clear alarm with the RESET key. Restart part program Continuation: 16025 [Channel %1: ] Block %2 impermissible axis exchange in REPOS command by axis %3. Parameters: %1 = Channel number %2 = Block number, label…
• Page 222
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Correct setting data or modify part program. Program Clear alarm with the RESET key. Restart part program Continuation: 16111 [Channel %1: ] Block %2 spindle %3 No speed programmed Parameters: %1 = Channel number %2 = Block number, label…
• Page 223
  NCK alarms 16130 [Channel %1: ] Block %2 command not allowed with FTOCON Parameters: %1 = Channel number %2 = Block number, label Definitions: — Case 1: A plane change is not allowed if the modal G function FTOCON: «fine tool compensation» is active. — Case 2: Transformation selection is allowed only for zero transformation or transformation inclined axis, Transmit or Tracyl if FTOCON is active.
• Page 224
  NCK alarms 16300 [Channel %1: ] Block %2 denominator polynominal with zero places within parameter range not allowed Parameters: %1 = Channel number %2 = Block number, label Definitions: The programmed denominator polynomial (with PL [ ] = … , i.e. without specification of geometry axis) has a zero place within the defined parameter range (PL = …).
• Page 225
  NCK alarms 16420 [Channel %1: ] Block %2 axis %3 programmed repeatedly Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name, spindle number Definitions: It is not allowed to program an axis more than once. Reaction: Correction block is reorganized.
• Page 226
  NCK alarms 16424 [Channel %1: ] Block %2 coordinate %3 programmed repeatedly in the block Parameters: %1 = Channel number %2 = Block number, label %3 = Coordinate Definitions: It is not allowed to program a coordinate of the 2nd contact point of the tool for description of the tool orientation several times in one block.
• Page 227
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Values for chamfers, roundings and modal roundings must be programmed with positive values only. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 16510 [Channel %1: ] Block %2 no facing axis for diameter programming available…
• Page 228
  NCK alarms Definitions: A gear stage change for the spindle will not be possible, if: — thread cutting (G33, G34, G35) is active — the spindle is active as master or slave spindle in a coupling — the spindle is being positioned Reaction: Correction block is reorganized.
• Page 229
  NCK alarms 16672 [Channel %1: ] Block %2 leading axis/spindle %3 maximum number of CP master values (%4) exceeded Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name, spindle number %4 = Max. number of CP master values Definitions: An attempt was made to activate more master values of generic couplings than are configured in MD18452 $MN_MM_NUM_CP_MODUL_LEAD.
• Page 230
  NCK alarms 16678 [Channel %1: ] Block %2 following axis/spindle %3 status %4 impermissible traversing instruction Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name, spindle number %4 = Status Definitions: An addtional traversing in the following axis/spindle is not permitted in the current status of the generic coupling.
• Page 231
  NCK alarms 16682 [Channel %1: ] Block %2 following axis/spindle %3 instructions %4 are not possible. Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name, spindle number %4 = CP instruction Definitions: The stated instructions are not permitted together in one block for a following axis/spindle of a generic coupling. Reaction: Correction block is reorganized.
• Page 232
  NCK alarms Definitions: The stated instruction is not permitted for the stated type of generic coupling. Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Modify part program. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 16687 [Channel %1: ] Block %2 following axis/spindle %3 type of coupling/instruction %4 is…
• Page 233
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 16690 [Channel %1: ] Block %2 following axis/spindle %3 changing the reference system %4 is not possible. Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name, spindle number %4 = Reference system Definitions:…
• Page 234
  NCK alarms 16694 [Channel %1: ] Block %2 following axis/spindle %3 status/instruction %4 is not possible. Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name, spindle number %4 = Status, instruction Definitions: The stated instruction is not permitted for the current status of the generic coupling. Reaction: Correction block is reorganized.
• Page 235
  NCK alarms Reaction: NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm. Remedy: Modify part programm. Define the coupling and activate, if necessary, before the instruction. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 16698 [Channel %1: ] Block %2 following axis/spindle %3 leading axis/spindle %4 has not…
• Page 236
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Use only the feed type G94 or G95 in the thread cutting functions. After G33 and before G63, deselect the thread cutting function with G01. Program Clear alarm with NC START or RESET key and continue the program.
• Page 237
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 16740 [Channel %1: ] Block %2 no geometry axis programmed Parameters: %1 = Channel number %2 = Block number, label Definitions: No geometry axis was programmed for tapping (G33) or for rigid tapping (G331, G332). The geometry axis is, how- ever, essential if an interpolation parameter has been specified.
• Page 238
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Procedure for automatically engaging the suitable gear stage prior to thread cutting: * Program the spindle speed (S) in a G331 block without axis motions and prior to thread cutting, e.g. G331 S1000. * Activate M40 for the spindle.
• Page 239
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 16755 [Channel %1: ] Block %2 no stop required Parameters: %1 = Channel number %2 = Block number, label Definitions: No Stop is needed for the programmed function. A Stop is necessary after SPOSA or after M5 if the next block is to be loaded only after a spindle stop.
• Page 240
  NCK alarms 16760 [Channel %1: ] Block %2 axis %3 S value missing Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name, spindle number Definitions: No spindle speed has been given for rigid tapping (G331 or G332). Reaction: Correction block is reorganized.
• Page 241
  NCK alarms 16770 [Channel %1: ] Block %2 axis %3 no measuring system available Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name, spindle number Definitions: One of the following spindle functions has been programmed, the position control requires: SPCON, SPOS, SPOSA, COUPON,…
• Page 242
  NCK alarms 16773 [Channel %1: ] Axis %2 is the following axis. The axis/spindle disables of leading axes %3 and %4 differ from one another. Parameters: %1 = Channel number %2 = Axis, spindle %3 = Axis, spindle %4 = Axis, spindle Definitions: The axis is active in a coupling as a following axis.
• Page 243
  NCK alarms 16778 [Channel %1: ] Block %2 coupling: Ring coupling at following axis %3 and leading axis %4 impermissible Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name, spindle number %4 = Axis name, spindle number Definitions: A coupling has been switched on which results in a cyclic coupling, allowance being made for further couplings.
• Page 244
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Modify part program. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 16782 [Channel %1: ] Block %2 following spindle/axis %3 not available Parameters: %1 = Channel number %2 = Block number, label…
• Page 245
  NCK alarms 16786 [Channel %1: ] Block %2 coupling to master spindle %3 already exists Parameters: %1 = Channel number %2 = Block number, label %3 = Leading spindle number Definitions: A coupling is to be switched on, in which the slave axis is already actively coupled with the other master axis. Only one master spindle is allowed for the synchronous spindle function.
• Page 246
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Check in the part program whether another link already exists for the axes. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 16790 [Channel %1: ] Block %2 Parameter is zero or missing…
• Page 247
  NCK alarms 16793 [Channel %1: ] Block %2 coupling of axis %3 prohibits transformation change Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name, spindle number Definitions: The specified axis is a slave axis in a transformation grouping. When the coupling is switched on, the transformation cannot be changed to another one.
• Page 248
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 16797 [Channel %1: ] Block %2 coupling is active Parameters: %1 = Channel number %2 = Block number, label Definitions: An operation is to be performed in which no coupling may be active, e.g. COUPDEL or TANGDEL must not be used on active couplings.
• Page 249
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 16820 [Channel %1: ] Block %2 traverse instruction ACN for axis %3 not allowed Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name, spindle number Definitions: The keyword ACN (Absolute Coordinate Negative) is only allowed for «modulo axes».
• Page 250
  NCK alarms Reaction: Alarm display. Remedy: Check the program status and channel status. Program Clear alarm with the Delete key or NC START. Continuation: 16905 [Channel %1: ] Program control: action %2<ALNX> not allowed Parameters: %1 = Channel number %2 = Action number/action name Definitions: Operation cannot be started or continued.
• Page 251
  NCK alarms 16909 [Channel %1: ] Action %2<ALNX> not allowed in current mode Parameters: %1 = Channel number %2 = Action number/action name Definitions: A different operating mode must be activated for the activated function. Reaction: Alarm display. Remedy: Check operation and operating state. Program Clear alarm with the Delete key or NC START.
• Page 252
  NCK alarms Definitions: Incorrect mode change, e.g.: Auto -> MDIREF. Reaction: Alarm display. Remedy: Check operation or selected mode. Program Clear alarm with the Delete key or NC START. Continuation: 16915 [Channel %1: ] Action %2<ALNX> not allowed in the current block Parameters: %1 = Channel number %2 = Action number/action name…
• Page 253
  NCK alarms 16922 [Channel %1: ] Subprograms: action %2<ALNX> maximum nesting depth exceeded Parameters: %1 = Channel number %2 = Action number/action name Definitions: Various actions can cause the current procedure to be interrupted. Depending on the action, asynchronous subrou- tines are activated.
• Page 254
  NCK alarms 16925 [Channel %1: ] Program control: action %2<ALNX> not allowed in the current state, action %3<ALNX> active Parameters: %1 = Channel number %2 = Action number/action name %3 = Action number/action name Definitions: The action has been refused since a mode or sub-mode change (change to automatic mode, MDI, JOG, overstoring, digitizing, etc.) is taking place.
• Page 255
  NCK alarms 16930 [Channel %1: ] Preceding block and current block %2 must be separated through an executable block Parameters: %1 = Channel number %2 = Block number Definitions: The language functions WAITMC, SETM, CLEARM and MSG must be packed in separate NC blocks due to the lan- guage definition.
• Page 256
  NCK alarms 16933 [Channel %1: ] Interrupt treatment: action %2<ALNX> not allowed in the current state Parameters: %1 = Channel number %2 = Action number/action name Definitions: If a temporary standstill has occurred because of a Reorg event across block boundaries, it is possible that a block without Reorg capability has been loaded.
• Page 257
  NCK alarms Reaction: Alarm display. Remedy: Abort program with the RESET key. Program Clear alarm with the Delete key or NC START. Continuation: 16937 [Channel %1: ] Action %2<ALNX> not possible due to program test Parameters: %1 = Channel number %2 = Action number/action name Definitions: This action is not allowed as program test is currently active.
• Page 258
  NCK alarms Reaction: Alarm display. Warning display. Remedy: Alarm is suppressed by means of MD11411 $MN_ENABLE_ALARM_MASK bit 1 = 0. Program Alarm display showing cause of alarm disappears. No further operator action necessary. Continuation: 16941 [Channel %1: ] Action %2<ALNX> rejected because no program event has been executed yet Parameters: %1 = Channel number…
• Page 259
  NCK alarms 16943 [Channel %1: ] Action %2<ALNX> not possible due to ASUP Parameters: %1 = Channel number %2 = Action number/action name Definitions: The action in the 2nd parameter was rejected, since an asynchronous subprogram is currently active. Currently, only the integrated search run is rejected with this alarm. The integrated search run is activated, if search run is triggered in the Stop program state.
• Page 260
  NCK alarms 16945 [Channel %1: ] Action %2<ALNX> delayed up to the block end Parameters: %1 = Channel number %2 = Action number/action name Definitions: The currently executing action (e.g. dry run on/off, change skip levels, etc.) should be active immediately, but it can become active not earlier than at the end of the block, since a thread is currently being machined.
• Page 261
  NCK alarms Reaction: Alarm display. Remedy: MD11410 $MN_SUPPRESS_ALARM_MASK, MD22680 $MC_AUTO_IPTR_LOCK and language command IPTRLOCK Program Clear alarm with the Delete key or NC START. Continuation: 16951 [Channel %1: ] Search run in a protected program section. Parameters: %1 = Channel number Definitions: A part programmer can define protected part program sections with the language commands IPTRLOCK and IPTRUNLOCK.
• Page 262
  NCK alarms Remedy: Set axis/spindle disable of the master axis Program Clear alarm with the RESET key. Restart part program Continuation: 16954 [Channel %1: ] Block %2 programmed stop prohibited in stop delay area Parameters: %1 = Channel ID %2 = Block number, label Definitions: In a program area (stop delay area) that is bracketed with DELAYFSTON and DELAYFSTOF, a program command was used that causes a stop.
• Page 263
  NCK alarms 16957 [Channel %1: ] Stop-Delay area is suppressed Parameters: %1 = Channel ID Definitions: The program area (Stop-Delay area), which is bracketed by DELAYFSTON and DELAYFSTOF, could not be acti- vated. Every stop therefore becomes effective immediately and is not delayed! This occurs every time, when braking into a stop Stop-Delay area, i.e.
• Page 264
  NCK alarms 16962 [Channel %1: ] NCK computing time reduced, start is not allowed. Parameters: %1 = Channel number Definitions: The computing time available to the NCK has been reduced, starts have therefore been locked. The computer perfor- mance is inadequate for smooth program execution. The computing time of the NCK may have been reduced by the HMI because of an HMI part program simulation.
• Page 265
  NCK alarms 17001 [Channel %1: ] Block %2 no memory left for tool/magazine data Parameters: %1 = Channel number %2 = Block number, label Definitions: The number of the following tool/magazine data variables in the NC is specified using machine data: — Number of tools + number of grinding data blocks: MD18082 $MN_MM_NUM_TOOL — Number of cutting edges: MD18100 $MN_MM_NUM_CUTTING_EDGES_IN_TOA Tools, grinding data blocks, cutting edges can be used independently of the tool management.
• Page 266
  NCK alarms 17018 [Channel %1: ] Block %2 incorrect value for parameter %3 Parameters: %1 = Channel number %2 = Block number, label %3 = Parameter name Definitions: An incorrect value has been assigned to the stated parameter. Only the following values are permissible for the parameter $P_WORKAREA_CS_COORD_SYSTEM =1 for workpiece coordinate system =3 for settable zero system.
• Page 267
  NCK alarms 17030 [Channel %1: ] Block %2 illegal array index 2 Parameters: %1 = Channel number %2 = Block number, label Definitions: General: A read or write access has been programmed to an array variable with an invalid 2nd array index. The valid array indi- ces must lie within the defined array size and the absolute limits (0 — 32,766).
• Page 268
  NCK alarms 17050 [Channel %1: ] Block %2 illegal value Parameters: %1 = Channel number %2 = Block number, label Definitions: A value has been programmed that exceeds the value range or the limit value of a variable or a machine data item. Example: In a string variable (e.g.
• Page 269
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 17070 [Channel %1: ] Block %2 data is write-protected Parameters: %1 = Channel number %2 = Block number, label Definitions: An attempt was made to write into a write-protected variable (e.g. a system variable). Safety Integrated: Safety system variables can only be written into via the safety SPL program.
• Page 270
  NCK alarms Remedy: Please inform the authorized personnel/service department. Determine the input limits of the machine data and assign a value within these limits. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 17095 [Channel %1: ] Block %2 invalid value Parameters: %1 = Channel number %2 = Block number, label…
• Page 271
  NCK alarms 17120 [Channel %1: ] Block %2 analog input no. %3 not activated Parameters: %1 = Channel number %2 = Block number, label %3 = Input number Definitions: An attempt has been made by means of the system variable $A_INA[n] to read an analog input n that has not been activated by the MD10300 $MN_FASTIO_ANA_NUM_INPUTS.
• Page 272
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Program fewer digital/analog outputs in a block. The specified maximum number applies in each case separately for analog or digital outputs. If necessary, program two NC blocks. Program Clear alarm with NC START or RESET key and continue the program.
• Page 273
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Check tool call in the NC parts program: — Correct tool correction number D programmed? If no D number is specified with the tool change command, then the D number set by MD20270 $MC_CUTTING_EDGE_DEFAULT will be active automatically.
• Page 274
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: — Change program: — Select different H number Program Clear alarm with NC START or RESET key and continue the program. Continuation: 17188 [Channel %1: ] D number %2 defined in tool T no. %3 and %4 Parameters: %1 = Channel number %2 = Offset number D…
• Page 275
  NCK alarms Remedy: Check tool call in the NC part program: — Correct tool number T.. programmed? — Tool parameters P1 — P25 defined? The dimensions of the tool edge must have been entered previously either through the operator panel or through the V.24 interface. Description of the system variables $P_DP x [n, m] n …
• Page 276
  NCK alarms 17193 [Channel %1: ] Block %2 the active tool is no longer on toolholder no./spindle no. %3, program %4 Parameters: %1 = Channel number %2 = Block number, label %3 = Toolholder no., spindle no. %4 = Program name Definitions: The tool at the specified toolholder/spindle at which the last tool change was carried out as master toolholder or master spindle, has been replaced.
• Page 277
  NCK alarms 17200 [Channel %1: ] Block %2: Data of tool %3 cannot be deleted. Parameters: %1 = Channel number %2 = Block number, label %3 = T number Definitions: An attempt has been made to delete from the part program the tool data for a tool currently being processed. Tool data for tools involved in the current machining operation may not be deleted.
• Page 278
  NCK alarms 17212 [Channel %1: ] Tool management: Load manual tool %3, duplo no. %2 onto spindle/ toolholder %4 Parameters: %1 = Channel number %2 = Duplo no. %3 = Tool identifier %4 = Toolholder number (spindle number) Definitions: Indicates that the specified manual tool must be loaded in the specified toolholder or spindle before the program con- tinues.
• Page 279
  NCK alarms 17216 [Channel %1: ] Remove manual tool from toolholder %4 and load manual tool %3 %2 Parameters: %1 = Channel number %2 = Duplo no. %3 = Tool identifier %4 = Toolholder number (spindle number) Definitions: Indicates that the specified manual tool must be loaded in the specified toolholder or spindle before the program is continued and that the manual tool located there must be removed.
• Page 280
  NCK alarms 17224 [Channel %1: ] Block %2 tool T/D= %3 — tool type %4 is not permitted Parameters: %1 = Channel number %2 = Block number, label %3 = Incorrect T no. / D no. %4 = Incorrect tool type Definitions: On this system, it is not possible to select tool offsets of the indicated tool types.
• Page 281
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Correct the NC program. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 17260 [Channel %1: ] Block %2 illegal magazine location definition Parameters: %1 = Channel number %2 = Block number, label…
• Page 282
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Modify NC program: Assign the value of the machine data or of the system variable to a program-local variable and transfer this as parameter. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 17500 [Channel %1: ] Block %2 axis %3 is not an indexing axis…
• Page 283
  NCK alarms 17502 [Channel %1: ] Block %2 indexing axis %3 with Hirth tooth system stop is delayed Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name Definitions: For the indexing axis, the ‘Hirth tooth system’ function is activated and the override has been set to 0 or another stop condition (e.g.
• Page 284
  NCK alarms 17600 [Channel %1: ] Block %2 preset on transformed axis %3 not possible Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name, spindle number Definitions: The programmed PRESET axis is involved in the current transformation. This means that setting the actual value memory (PRESET) is not possible for this axis.
• Page 285
  NCK alarms 17630 [Channel %1: ] Block %2 referencing for transformed axis %3 not possible Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name, spindle number Definitions: In the displayed block, an axis is programmed for reference point approach (G74) that is involved in the active trans- formation.
• Page 286
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Program keyword FP with machine fixed points 1 or 2. Example: Approach fixed point 2 with machine axes X1 and Z2. N100 G75 FP=2 X1=0 Z2=0 Or modify MD30610 $MA_NUM_FIX_POINT_POS and, if necessary, MD30600 $MA_FIX_POINT_POS[].
• Page 287
  NCK alarms 17813 [Channel %1: ] Axis %2 fixed-point approach in JOG and override motion active Parameters: %1 = Channel number %2 = Axis name, spindle number Definitions: ‘Fixed-point approach in JOG’ is active for the axis, but another offset motion — for example a synchronization offset $AA_OFF — has been interpolated simultaneously.
• Page 288
  NCK alarms 17820 [Channel %1: ] JOG to position not possible for axis %2, reason %3 Parameters: %1 = Channel number %2 = Axis name, spindle number %3 = Cause Definitions: A ‘JOG to position’ has been requested for an axis. This is not possible because: Reason 1: The axis is involved in the active transformation.
• Page 289
  NCK alarms Reaction: Interface signals are set. Alarm display. Remedy: Trigger JOG motion again. Program Clear alarm with the Delete key or NC START. Continuation: 17825 Indexing axis %1 $SA_JOG_POSITION unequal indexing position Parameters: %1 = Axis number Definitions: The axis is a referenced indexing axis and ‘JOG to position’ is activated in JOG mode, but SD43320 $SA_JOG_POSITION does not coincide with an indexing position.
• Page 290
  NCK alarms Program Clear alarm with the Delete key or NC START. Continuation: 17833 [Channel %1: ] JOG a circle is active and JOG circles deactivated Parameters: %1 = Channel number %2 = Axis name, spindle number Definitions: A circular motion is active but ‘JOG in circles’ has been deactivated. The circular motion is canceled. Reaction: Interface signals are set.
• Page 291
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. Remedy: Please inform the authorized personnel/service department. Modify definition of the protection zone and check MD. Program Clear alarm with NC START or RESET key and continue the program. Continuation: 18001 [Channel %1: ] Block %2 channel-specific protection zone %3 incorrect.
• Page 292
  NCK alarms 10: Error in internal structure of the protection zones. 11: Other, not further specified errors. 12: The number of protection zones simultaneously active exceeds the maximum number (channel-specific machine data). 13,14: Contour element for protection zones cannot be created. 15,16: No more memory space for the protection zones.
• Page 293
  NCK alarms Reaction: Correction block is reorganized. Interface signals are set. Alarm display. If the alarm is output on ramp-up (2nd parameter: «INIT» instead of block number), «Channel not ready to operate» will be set. Remedy: Please inform authorized personnel / the service department. 1.
• Page 294
  NCK alarms 18006 [Channel %1: ] Block %2 serious error in definition of channel-specific protection zone Parameters: %1 = Channel number %2 = Block number, label %3 = Protection zone number Definitions: The protection zone definition must be terminated with EXECUTE before a preprocessing stop is performed. This also applies to any that are initiated implicitly such as with G74, M30, M17.
• Page 295
  NCK alarms Program Clear alarm with NC START or RESET key and continue the program. Continuation: 18300 [Channel %1: ] Block %2 frame: fine shift not possible Parameters: %1 = Channel number %2 = Block number, label Definitions: Allocation of a fine shift to settable frames or the basic frame is not possible since MD18600 $MN_MM_FRAME_FINE_TRANS is not equal to 1.
• Page 296
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm. Remedy: Modify machine data. Program Clear alarm with the RESET key. Restart part program Continuation: 18313 [Channel %1: ] Block %2 frame: illegal switchover of geometry axes Parameters: %1 = Channel number %2 = Block number, label…
• Page 297
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 20000 [Channel %1: ] Axis %2 reference cam not reached Parameters: %1 = Channel number %2 = Axis name, spindle number Definitions: After starting the reference point approach, the rising edge of the reduction cam must be reached within the section defined in the MD34030 $MA_REFP_MAX_CAM_DIST (phase 1 of referencing).
• Page 298
  NCK alarms 20002 [Channel %1: ] Axis %2 zero mark not found Parameters: %1 = Channel number %2 = Axis name, spindle number Definitions: The hardware zero mark of the incremental position encoder or the substitute zero mark of the absolute position encoder is not within a defined section.
• Page 299
  NCK alarms Remedy: Please inform the authorized personnel/service department. Determine the distance between 2 odd reference point markers (reference point marker interval). This value (which is 20.00 mm on Heidenhain scales) must be entered in the MD34060 $MA_REFP_MAX_MARKER_DIST. Check the reference point track of the scale including the electronics for the evaluation. Program Clear alarm with the RESET key.
• Page 300
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 20007 [Channel %1: ] Axis %2 reference point approach requires 2 measuring systems Parameters: %1 = Channel number %2 = Axis name, spindle number Definitions: 2 encoders are needed for setting MD34200 $MA_ENC_REFP_MODE = 6! Reaction: NC Start disable in this channel.
• Page 301
  NCK alarms Program Alarm display showing cause of alarm disappears. No further operator action necessary. Continuation: 20052 [Channel %1: ] Axis %2 already active Parameters: %1 = Channel number %2 = Axis name, spindle number Definitions: The axis is to traverse as a machine axis in JOG mode using the direction keys on the machine control panel. However, this is not possible because: 1.
• Page 302
  NCK alarms 20055 [Channel %1: ] Master spindle not present in JOG mode Parameters: %1 = Channel number Definitions: The displayed axis is to be traversed as machine axis in JOG mode with revolutional feed, but no master spindle has been defined from which the actual speed could have been derived.
• Page 303
  NCK alarms 20058 [Channel %1: ] Axis %2 revolutional feedrate: illegal feed source Parameters: %1 = Channel number %2 = Axis name, spindle number Definitions: An axis/spindle is to be traversed at revolutional feedrate. The reference axis/spindle defined in SD 43300 $SA_ASSIGN_FEED_PER_REV_SOURCE refers to itself.
• Page 304
  NCK alarms Reaction: Alarm display. Remedy: Register the axis as an orientation axis. Program Clear alarm with the Delete key or NC START. Continuation: 20062 [Channel %1: ] Axis %2 already active Parameters: %1 = Channel number %2 = Axis name, spindle number Definitions: The displayed axis is already traversing as a machine axis.
• Page 305
  NCK alarms Reaction: Local alarm reaction. Interface signals are set. Alarm display. Remedy: If the revolutional feedrate is to be active in JOG mode too, then a master spindle must be declared in the channel- specific machine data MD20090 $MC_SPIND_DEF_MASTER_SPIND. In this case, you have to open a screen in the PARAMETER operating area with the softkeys «SETTINGDATA»…
• Page 306
  NCK alarms Remedy: Please inform the authorized personnel/service department. The FC POS-AXIS for linear and rotary axes should be used or the axis should be declared as an indexing axis. Corresponding machine data for indexing axis declaration: Modify MD30500 $MA_INDEX_AX_ASSIGN_POS_TAB Modify MD10900 $MN_INDEX_AX_LENGTH_POS_TAB_1 Modify MD10910 $MN_INDEX_AX_POS_TAB_1 Modify MD10920 $MN_INDEX_AX_LENGTH_POS_TAB_2…
• Page 307
  NCK alarms 20082 [Channel %1: ] Axis %2 coordinate system-specific working area limit %3 end position Parameters: %1 = Channel number %2 = Axis number %3 = «+» or «-» %4 = End position Definitions: The displayed axis is operated as a «concurrent positioning axis», and the corresponding active coordinate system- specific working area limitation for the axis is violated.
• Page 308
  NCK alarms 20091 Axis %1 has not reached fixed stop Parameters: %1 = Axis name, spindle number Definitions: On attempting to traverse against a fixed stop, the programmed end position has been reached or the traversing move- ment has been aborted. The alarm can be concealed by means of the MD37050 $MA_FIXED_STOP_ALARM_MASK. The alarm can be reprogrammed in the MD11412 $MN_ALARM_REACTION_CHAN_NOREADY (channel not ready).
• Page 309
  NCK alarms Remedy: Please inform the authorized personnel/service department. — Check the mechanical components, e.g. has the stop broken away? Has the part to be clamped given way? — Position window for zero speed control too small (MD37020 $MA_FIXED_STOP_WINDOW_DEF) (SD43520 $SA_FIXED_STOP_WINDOW).
• Page 310
  NCK alarms Reaction: Interface signals are set. Alarm display. Remedy: Note the supplementary conditions of the brake test, see additional info. Program Clear alarm with the Delete key or NC START. Continuation: 20097 Axis %1 incorrect travel direction brake test Parameters: %1 = Axis name, spindle number Definitions:…
• Page 311
  NCK alarms Reaction: Interface signals are set. Alarm display. Remedy: Please inform the authorized personnel/service department. Check and correct the axis assignment in the compensa- tion table. If the error cannot be found, the alarm can be suppressed by switching off the table ($SN_CEC_TABLE_ENABLE) or switching off compensation in the axis ($MA_CEC_ENABLE).
• Page 312
  NCK alarms 20130 [Channel %1: ] Contour tunnel monitoring Parameters: %1 = Channel number Definitions: The tool tip has exited the tunnel placed around the desired contour, i.e. the distance between tool tip and desired contour was greater than specified in the MD21050 $MC_CONTOUR_TUNNEL_TOL. The alarm can be reprogrammed in the MD11412 $MN_ALARM_REACTION_CHAN_NOREADY (channel not ready).
• Page 313
  NCK alarms 20141 [Channel %1: ] Motion synchronous action: illegal axis type Parameters: %1 = Channel number Definitions: The requested command is not permissible in the current axis status for the command axis or spindle. This alarm occurs with command axes (POS, MOV), spindle commands from motion synchronous actions (M3/M4/M5, SPOS), coupled motion (TRAILON, TRAILOF) and lead value coupling (LEADON, LEADOF).
• Page 314
  NCK alarms Reaction: NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm. Remedy: Correct error in expression. Program Clear alarm with the RESET key. Restart part program Continuation: 20146 [Channel %1: ] Block %2 motion synchronous action: nesting depth exceeded Parameters: %1 = Channel number %2 = Block number…
• Page 315
  NCK alarms Reaction: NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm. Remedy: Change synchronous action. Program Clear alarm with the RESET key. Restart part program Continuation: 20149 [Channel %1: ] Block %2 motion-synchronous action: Index %3 is illegal Parameters: %1 = Channel number %2 = Block number…
• Page 316
  NCK alarms 20170 [Channel %1: ] Machine data $AC_FIFO invalid Parameters: %1 = Channel number Definitions: the structure of the FIFO variable $AC_FIFO1 — $AC_FIFO10 determined by machine data MD28260 $MC_NUM_AC_FIFO, MD28262 $MC_START_AC_FIFO, MD28264 $MC_LEN_AC_FIFO, MD28266 $MC_MODE_AC_FIFO cannot be stored in the R parameter field defined in MD28050 $MC_MM_NUM_R_PARAM. Reaction: NC Start disable in this channel.
• Page 317
  NCK alarms 20203 [Channel %1: ] No active tool Parameters: %1 = Channel number Definitions: A tool fine compensation has been written for the active tool of channel %1 with PUTFTOC. No tool is active in this channel. Therefore, the compensation cannot be assigned. Reaction: Interpreter stop NC Start disable in this channel.
• Page 318
  NCK alarms Reaction: NC Start disable in this channel. Alarm display. Remedy: Remedy for error cause: 1 Define another travel direction 2 Deactivate the coupling and travel the axis/axes separately 3 Deactivate the coupling and travel the axis/axes separately 4 Reserved 5 Deactivate the transformation and travel the axis/axes separately Program Clear alarm with the RESET key.
• Page 319
  NCK alarms Remedy: Please inform the authorized personnel/service department. Check the interface signals DB380x DBX0002.1 (Servo enable), DB380x DBX4001.7 (Pulse enable), check the drive signals DB390x DBX4001.7 (Pulses enabled), DB390x DBX4001.5 (Drive ready) for example with the PLC status dis- play in the DIAGNOSTICS operating area.
• Page 320
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 21616 [Channel %1: ] Block %2 overlaid motion active at transformation switchover Parameters: %1 = Channel number %2 = Block number, label Definitions: The overlaid motion in the BCS changes its significance because of the transformation change and can therefore lead to undesired axis movements.
• Page 321
  NCK alarms 21619 [Channel %1: ] Block %2 transformation active: motion not possible Parameters: %1 = Channel number %2 = Block number, label Definitions: The machine kinematics does not allow the specified motion. Transformation-dependent error causes can be in: TRANSMIT: A (circular) area exists around the pole, where positioning is not possible. The area is caused by the fact that the tool reference point cannot be traversed as far as into the pole.
• Page 322
  NCK alarms 21660 [Channel %1: ] Block %2 axis %3 conflict between SYNACT: $AA_OFF and CORROF Parameters: %1 = Channel number %2 = Block number, label %3 = Axis name Definitions: When deselecting the position offset ($AA_OFF) via the part program command CORROF (<axis>, «AA_OFF») an active synchronized action is detected that immediately sets $AA_OFF for the axis (DO_$AA_OFF [<axis>] =<value>).
• Page 323
  NCK alarms 21700 [Channel %1: ] Block %3 axis %2 touch probe already deflected, edge polarity not possible Parameters: %1 = Channel number %2 = Axis name, spindle number %3 = Block number Definitions: The probe programmed under the keyword MEAS or MEAW is already deflected and has switched. For a further mea- suring operation, the probe signal must first be canceled (quiescent state of the probe).
• Page 324
  NCK alarms 21702 [Channel %1: ] Block %3 axis %2 measurement aborted Parameters: %1 = Channel number %2 = Axis name, spindle number %3 = Block number Definitions: The measurement block has ended (the programmed end position of the axis has been reached) but the activated touch probe has not yet responded.
• Page 325
  NCK alarms 21760 [Channel %1: ] Block %2 too many auxiliary functions programmed Parameters: %1 = Channel number %2 = Block number, label Definitions: The number of programmed auxiliary functions has exceeded the maximum permissible amount. This alarm can occur in conjunction with motion synchronous actions: The maximum number of auxiliary functions must not be exceeded in motion block and motion synchronous actions.
• Page 326
  NCK alarms Remedy: The gear stage is to be set prior to the corresponding machining step. If it is necessary, however, to change the gear stage within one of the above mentioned functions, this function must be switched off for the time of the gear stage change. Thread cutting is deselected with G1; synchronous spindle cou- pling is switched off with COUPOF;…
• Page 327
  NCK alarms Program Clear alarm with the Delete key or NC START. Continuation: 22012 [Channel %1: ] Block %2 leading spindle %3 is in simulation. Parameters: %1 = Channel number %2 = Block number, label %3 = Leading spindle number Definitions: When coupling, no synchronism can be achieved if the lead spindle/axis is in simulation mode and the following spin- dle/axis is not.
• Page 328
  NCK alarms 22015 [Channel %1: ] Block %2 following spindle %3 No dynamic response for supplementary motion Parameters: %1 = Channel number %2 = Block number, label %3 = Number of following spindle Definitions: The differential motion of the following spindle cannot be executed due to a lack of available velocity. The coupling consumes the entire available dynamic response.
• Page 329
  NCK alarms 22019 [Channel %1: ] Block %2 following axis/spindle %3 time monitoring: ‘Synchronism coarse’ not reached Parameters: %1 = Channel number %2 = Block number, label %3 = Following axis/spindle number Definitions: After reaching the setpoint-side synchronism, the time until reaching the actual value-side synchronism is coarsely monitored.
• Page 330
  NCK alarms Program Clear alarm with the Delete key or NC START. Continuation: 22024 [Channel %1: ] Block %2 Spindle %3 tapping: PLC signal ‘invert M3/M4’ changed after Parameters: %1 = Channel number %2 = Block number, label %3 = Spindle %4 = Value Definitions: When loading a G331 block it was detected that the NC/PLC interface signal <M3M4_invertieren/>…
• Page 331
  NCK alarms Remedy: Please inform the authorized personnel/service department. The following axis/spindle was not able to follow the leading axis(axes)/spindle(s). Program Clear alarm with the Delete key or NC START. Continuation: 22030 [Channel %1: ] Block %2 following spindle %3 Impermissible programming Parameters: %1 = Channel number %2 = Block number, label…
• Page 332
  NCK alarms Definitions: The determination of the offset value ($AA_COUP_CORR[Sn]) intended by the NC/PLC signal <Synchronlauf_nachfuehren/> (correct synchronism) cannot be executed. The offset value cannot be calculated prop- erly. The reasons for this may be: — Reason 1: The following axis is not configured as a spindle. — Reason 2: The coupling has more than one active leading axis.
• Page 333
  NCK alarms 22038 [Channel %1: ] Block %2 Axis/Spindle %3 ‘Delete synchronism override’ is being ignored Parameters: %1 = Channel number %2 = Block number, label %3 = Axis/spindle number Definitions: VDI interface signal DB31..,DBX31.7 ‘Correct synchronism’ is being ignored, because VDI interface signal DB31..,DBX31.6 ‘Delete synchronism override’ has been set.
• Page 334
  NCK alarms 22051 [Channel %1: ] Block %3 spindle %2 reference mark not found Parameters: %1 = Channel number %2 = Axis name, spindle number %3 = Block number, label Definitions: When referencing, the spindle turned through a greater distance than given in the axis-specific MD34060 $MA_REFP_MAX_MARKER_DIST, without receiving a reference mark signal.
• Page 335
  NCK alarms Remedy: Modify setting of MD34200 $MA_ENC_REFP_MODE or change to JOG+REF and then reference. Program Clear alarm with the RESET key. Restart part program Continuation: 22055 [Channel %1: ] Block %3 spindle %2 configured positioning speed is too high Parameters: %1 = Channel number %2 = Axis name, spindle number…
• Page 336
  NCK alarms 22060 [Channel %1: ] Position control expected for axis/spindle %2 Parameters: %1 = Channel number %2 = Axis name, spindle number Definitions: The programmed coupling type (DV, AV) or the programmed function requires position control. Reaction: Alarm display. Remedy: Activate position control, e.g.
• Page 337
  NCK alarms Definitions: The desired tool motion command — triggered from the MMC or PLC — is not possible. The specified tool is not contained in the specified magazine. (NCK cannot contain tools that are not assigned to a magazine. With this kind of tool, no operations (motion, change) can be performed.) Reaction: NC Start disable in this channel.
• Page 338
  NCK alarms 22068 [Channel %1: ] Block %2 tool management: no tool available in tool group %3 Parameters: %1 = Channel number %2 = Block number, label %3 = String (identifier) Definitions: The specified tool group does not contain a tool which is ready for use and could be used for tool change. It is possible that all of the tools in question have been set to the ‘Disabled’ state by the tool monitoring function.
• Page 339
  Typical reasons of display are present, if the operator works with the function ‘definite D numbers’, which can be dis- played on Siemens MMC in a definite form only, if exactly one tool from a tool group has the status ‘active’.
• Page 340
  NCK alarms 22100 [Channel %1: ] Block %3 spindle %2 chuck speed exceeded Parameters: %1 = Channel number %2 = Axis name, spindle number %3 = Block number, label Definitions: The actual spindle speed is higher than the maximum speed configured in MD35100 $MA_SPIND_VELO_LIMIT plus a tolerance of 10 percent (fixed setting).
• Page 341
  NCK alarms 22260 [Channel %1: ] Spindle %2 thread might be damaged Parameters: %1 = Channel number %2 = Axis name %3 = Block number Definitions: When DECODING SINGLE BLOCK has been selected and there is a chain of thread blocks, then machining pauses occur at the block limits until the next block is executed with the new NC Start.
• Page 342
  NCK alarms 22280 [Channel %1: ] In block %2: Prog. acceleration path too short %3, %4 required Parameters: %1 = Channel number %2 = Block number, label %3 = Prog. acceleration path %4 = Required acceleration path Definitions: In order to stay within the programmed acceleration path, the acceleration caused an overload on the thread axis. In order to accelerate the axis with the programmed dynamic response, the length of the acceleration path must be at least as large as the value in parameter %4.
• Page 343
  NCK alarms 22295 [Channel %1: ] Spindle %2 DBB30 function not possible (cause: error code %3) Parameters: %1 = Channel number %2 = Axis name, spindle number %3 = Error code Definitions: The function request by PLC via DBB30 interface could not be executed. The cause is specified by the error code. Error codes: — Error code 1 : internal use — Error code 2 : internal use…
• Page 344
  NCK alarms 22297 [Channel %1: ] Spindle %2 FC18 function not possible (cause: error code %3) Parameters: %1 = Channel number %2 = Axis name, spindle number %3 = Error code Definitions: The function request by PLC via FC18 interface could not be executed. The cause is specified by the error code. Error codes: — Error code 1 : internal use — Error code 2 : internal use…
• Page 345
  NCK alarms 22322 [Channel %1: ] Axis %2 PRESET: illegal value Parameters: %1 = Channel number %2 = Axis name, spindle number Definitions: The entered Preset value is too large (number format overflow). Reaction: NC Start disable in this channel. Interface signals are set.
• Page 346
  NCK alarms 25001 Axis %1 hardware fault of passive encoder Parameters: %1 = Axis name, spindle number Definitions: The signals from the currently inactive position actual value encoder are missing, or they are not of the same phase, or they exhibit grounding/short-circuit. For PROFIdrive only: MD36310 $MA_ENC_ZERO_MONITORING >100 replaces the existing PowerOn alarm by the Reset alarm 25011.
• Page 347
  NCK alarms Remedy: Please inform the authorized personnel/service department. Check the measuring system in accordance with the instructions given by the measuring device manufacturer. Monitoring can be switched off by setting MD36310 $MA_ENC_ZERO_MONITORING[n] to 100 (n = encoder number: 1,2). Program Clear alarm with the Delete key or NC START.
• Page 348
  NCK alarms 25022 Axis %1 encoder %2 warning %3 Parameters: %1 = Axis name, spindle number %2 = Encoder number %3 = Error fine coding Definitions: This alarm only occurs with absolute encoders: a. Warning notice of missing absolute encoder adjustment (on the SIMODRIVE 611D or with PROFIdrive drives), that is if MD34210 $MA_ENC_REFP_STATE equals 0.
• Page 349
  NCK alarms 25040 Axis %1 standstill monitoring Parameters: %1 = Axis name, spindle number Definitions: The NC monitors to ensure that the position is held at zero speed. Monitoring is started after a time that can be set for a specific axis in the MD36040 $MA_STANDSTILL_DELAY_TIME after interpolation has ended. A constant check is made to determine whether the axis remains within the tolerance range given in MD36030 $MA_STANDSTILL_POS_TOL.
• Page 350
  NCK alarms 25050 Axis %1 contour monitoring Parameters: %1 = Axis name, spindle number Definitions: The NCK calculates for each interpolation point (setpoint) of an axis the actual value that should result based on an internal model. If this calculated actual value and the true machine actual value differ by a larger amount than given in the MD36400 $MA_CONTOUR_TOL, then the program is aborted and the alarm message is issued.
• Page 351
  NCK alarms 25070 Axis %1 drift value too large Parameters: %1 = Axis name, spindle number Definitions: Only with analog drives! The permissible maximum value of drift (internal, integrated drift value of automatic drift compensation) was exceeded during the last compensation operation. The permissible maximum value is defined in the axis-specific MD36710 $MA_DRIFT_LIMIT.
• Page 352
  NCK alarms 25100 Axis %1 measuring system switchover not possible Parameters: %1 = Axis name, spindle number Definitions: The prerequisites are not satisfied for the required encoder switchover: 1. The newly selected encoder must be in the active state: (DB380x DBX0001.5 / 1.6 = 1 (Position measuring system 1/2).
• Page 353
  NCK alarms Reaction: Alarm display. Remedy: Please inform the authorized personnel/service department. Enter the number of actual value encoders used for this axis in the MD30200 $MA_NUM_ENCS («Number of encoders»). Input value 0: Axis without encoder -> e.g. spindle Input value 1: Axis with encoder -> default setting Input value 2: Axis with 2 encoders ->…
• Page 354
  NCK alarms 25202 Axis %1 waiting for drive Parameters: %1 = Axis name, spindle number Definitions: Drive group error (self-clearing). Reaction: Interface signals are set. Alarm display. Remedy: For PROFIdrive only: Wait for the drive. This alarm reveals similar problems to alarm 25201 (see that alarm). It is continuously active during power-up if the drive does not communicate (e.g.
• Page 355
  NCK alarms 26002 Axis %1 encoder %2 parameterization error: number of encoder marks Parameters: %1 = Axis name, spindle number %2 = Encoder number Definitions: 1. Rotary measuring system (MD31000 $MA_ENC_IS_LINEAR[]==FALSE) The number of encoder marks set in MD31020 $MA_ENC_RESOL[] does not correspond to the value in the drive machine data (SIMODRIVE 611D: MD1005 $MD_ENC_RESOL_MOTOR;…
• Page 356
  NCK alarms Reaction: Mode group not ready. The NC switches to follow-up mode. Channel not ready. NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm. Channel not ready. Remedy: Please inform the authorized personnel/service department. Enter the encoder grid point distance according to the data given by the machine (or measuring device) manufacturer in the MD31010 $MA_ENC_GRID_POINT_DIST.
• Page 357
  NCK alarms Reaction: Mode group not ready. The NC switches to follow-up mode. Channel not ready. NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm. Channel not ready. Remedy: Please inform the authorized personnel/service department. Check machine data MD30240 $MA_ENC_TYPE and/or MD30130 $MA_CTRLOUT_TYPE and make the necessary corrections.
• Page 358
  NCK alarms 26010 Axis %1 QEC: invalid acceleration characteristic Parameters: %1 = Axis name, spindle number Definitions: $AA_QEC_ACCEL_1/2/3: The acceleration characteristic is divided into three areas. In each area there is a different quantization of the acceleration steps. The defaults should be changed only if compensation is inadequate in these acceleration areas.
• Page 359
  NCK alarms 26014 Axis %1 machine data %2 invalid value Parameters: %1 = Axis name, spindle number %2 = String: MD identifier Definitions: Machine data includes a value that is not valid. Reaction: NC not ready. The NC switches to follow-up mode. Mode group not ready, also effective for single axes.
• Page 360
  NCK alarms 26017 Axis %1 machine data %2[%3] invalid value Parameters: %1 = Axis name, spindle number %2 = String: MD identifier %3 = Index: MD array Definitions: Machine data includes a value that is not valid. Reaction: NC not ready. The NC switches to follow-up mode.
• Page 361
  NCK alarms 26022 Axis %1 encoder %2 measurement with simulated encoder not possible Parameters: %1 = NC axis number %2 = Encoder number Definitions: Alarm occurs on the control when a measurement was made without the encoder hardware (simulated encoder). Reaction: Local alarm reaction.
• Page 362
  NCK alarms Reaction: NC not ready. The NC switches to follow-up mode. 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: — Set P2038 = 1 or — Set P0922 = 100…199 or — Set bit 15 of MD13070 $MN_DRIVE_FUNCTION_MASK (note the boundary conditions, see above) and execute a Power ON in each case.
• Page 363
  Another possible cause is that a synchronized action needs to be finished before the path interpolation continues. The alarm is only output if MD11400 $MN_TRACE_SELECT = ‘H400’. The alarm output is normally sup- pressed. — MD11400 $MN_TRACE_SELECT has SIEMENS password protection. Reaction: Alarm display.
• Page 364
  NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm. Remedy: Please contact Siemens. Program Clear alarm with the RESET key. Restart part program Continuation: 26054 [Channel %1: ] Block %2 interpolation warning in Look Ahead (module %3, problem…
• Page 365
  NCK alarms 26070 [Channel %1: ] Axis %2 cannot be controlled by the PLC, max. number exceeded Parameters: %1 = Channel number %2 = Axis name, spindle number Definitions: An attempt was made to define more axes than allowed as PLC-controlled axes. Reaction: Interface signals are set.
• Page 366
  NCK alarms 26076 [Channel %1: ] Axis %2 not available for NC program, firmly assigned PLC axis Parameters: %1 = Channel %2 = Axis, spindle Definitions: The axis is a firmly assigned PLC axis. The axis is therefore not available for the NC program. Reaction: Interpreter stop NC Start disable in this channel.
• Page 367
  NCK alarms 26102 Axis %1 drive %2 sign of life missing Parameters: %1 = Axis name, spindle number %2 = Drive number Definitions: For PROFIdrive only: The sign-of-life cell is no longer being updated by the drive. Reaction: Mode group not ready. The NC switches to follow-up mode.
• Page 368
  NCK alarms Reaction: Mode group not ready. The NC switches to follow-up mode. Channel not ready. NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm. Remedy: Possible causes: — MD 30240 $MA_ENC_TYPE not equal to 0 as a result of an oversight; the encoder should actually be simulated (= 0). — MD 30220 $MA_ENC_MODULE_NR entered incorrectly, i.e.
• Page 369
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. NC Stop on alarm. Remedy: Set $AA_ESR_ENABLE[axis] = 0 before axis exchange. Program Clear alarm with the RESET key. Restart part program Continuation: Set $AA_ESR_ENABLE[axis] = 0 26124 [Channel %1: ] Axis %2, $AC_ESR_TRIGGER triggered but axis is NEUTRAL and…
• Page 370
  NCK alarms 61001 [Channel %1: ] Block %2: Thread pitch incorrectly defined Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycles: CYCLE84, CYCLE840, CYCLE96, CYCLE97. Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 371
  NCK alarms 61005 [Channel %1: ] Block %2: 3rd geometry axis not available Parameters: %1 = Channel number %2 = Block number, label Definitions: With an application on the lathe with no Y-axis in the G18 plane. Alarm triggered by following cycle: CYCLE86. Remedy: Check parameter on cycle call.
• Page 372
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Program tool (T). Program Clear alarm with the RESET key. Restart part program Continuation: 61010 [Channel %1: ] Block %2: Finishing allowance too large Parameters: %1 = Channel number %2 = Block number, label…
• Page 373
  NCK alarms 61013 [Channel %1: ] Block %2: Basic settings were changed, program cannot be executed Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The basic settings are not compatible with the generated program. Alarm triggered by following cycles: E_CP_CE, E_CP_CO, E_CP_DR, F_CP_CE, F_CP_CO, F_CP_DR.
• Page 374
  NCK alarms Remedy: Program Clear alarm with the RESET key. Restart part program Continuation: 61018 [Channel %1: ] Block %2: function %4 not executable with NCK Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: Alarm triggered by following cycles: . Reaction: Interpreter stop NC Start disable in this channel.
• Page 375
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Program Clear alarm with the RESET key. Restart part program Continuation: 61022 [Channel %1: ] Block %2: Parameter %4 value too low Parameters: %1 = Channel number %2 = Block number, label channel number…
• Page 376
  NCK alarms 61025 [Channel %1: ] Block %2: Check tool carrier position Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: Alarm triggered by following cycles: . Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 377
  NCK alarms 61029 %[[Channel %1: ] Block %2: %]Program name %4 too long Parameters: %1 = Channel number %2 = Block number, label Definitions: The alarm is triggered by the following cycles: CYCLE62, CYCLE63, CYCLE64, CYCLE952 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 378
  NCK alarms 61033 [Channel %1: ] Block %2: Incorrect file type: %4 Parameters: %1 = Channel number %2 = Block number, label Definitions: The alarm is triggered by the following cycles: Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 379
  NCK alarms 61037 [Channel %1: ] Block %2: No access rights to file: %4 Parameters: %1 = Channel number %2 = Block number, label Definitions: The alarm is triggered by the following cycles: Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 380
  NCK alarms 61041 [Channel %1: ] Block %2: Line range too large: %4 Parameters: %1 = Channel number %2 = Block number, label Definitions: The alarm is triggered by the following cycles: Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 381
  NCK alarms 61044 %[[Channel %1: ] Block %2: %]Illegal character(s) in file name: %4 Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycles: CYCLE952, CYCLE63, CYCLE64 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 382
  NCK alarms Remedy: — select shorter label name Program Clear alarm with the RESET key. Restart part program Continuation: 61048 [Channel %1: ] Block %2: Multi-channel data not found in job list: %4 Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycle: CYCLE208 Reaction:…
• Page 383
  NCK alarms 61051 %[[Channel %1: ] Block %2: %]Program name assigned twice Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm was triggered by the following cycles: CYCLE63, CYCLE64, CYCLE952 The same program name was assigned twice. Reaction: Interpreter stop NC Start disable in this channel.
• Page 384
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Select desired job list again, and start programs afresh. Program Clear alarm with the RESET key. Restart part program Continuation: 61099 [Channel %1: ] Block %2: Internal cycle error (%4) Parameters: %1 = Channel number %2 = Block number, label channel number…
• Page 385
  NCK alarms 61103 [Channel %1: ] Block %2: Number of holes is zero Parameters: %1 = Channel number %2 = Block number, label Definitions: No value for the number of holes has been programmed. Alarm triggered by following cycles: HOLES1, HOLES2. Remedy: Check parameter NUM.
• Page 386
  NCK alarms 61107 [Channel %1: ] Block %2: First drilling depth incorrectly defined Parameters: %1 = Channel number %2 = Block number, label Definitions: First drilling depth is in the opposite direction to the total drilling depth. Alarm triggered by following cycle: CYCLE83. Reaction: Interpreter stop NC Start disable in this channel.
• Page 387
  NCK alarms 61111 [Channel %1: ] Block %2: Infeed width > Tool diameter Parameters: %1 = Channel number %2 = Block number, label Definitions: The programmed infeed width is greater than the diameter of the active tool. Alarm triggered by following cycles: CYCLE71, POCKET3, POCKET4.
• Page 388
  NCK alarms 61115 [Channel %1: ] Block %2: Approach or retract mode(straight / circle / plane / space) incorrectly defined Parameters: %1 = Channel number %2 = Block number, label Definitions: The approach or retract mode to/from the contour has been incorrectly defined. Alarm triggered by following cycle: CYCLE72.
• Page 389
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 61119 [Channel %1: ] Block %2: Nominal or core diameter programmed incorrectly Parameters: %1 = Channel number %2 = Block number, label Definitions: The nominal or core diameter was incorrectly programmed. Alarm triggered by following cycles: CYCLE70, E_MI_TR, F_MI_TR.
• Page 390
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Define the safety clearance. Program Clear alarm with the RESET key. Restart part program Continuation: 61123 [Channel %1: ] Block %2: CYCLE72 cannot be simulated Parameters: %1 = Channel number %2 = Block number, label…
• Page 391
  NCK alarms 61126 [Channel %1: ] Block %2: Thread length too short Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycle: CYCLE840. Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display.
• Page 392
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 61130 [Channel %1: ] Block %2: positions of parallel axes cannot be compensated. No workpiece reference agreed. Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycle: CYCLE69.
• Page 393
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Program Clear alarm with the RESET key. Restart part program Continuation: 61134 [Channel %1: ] Block %2: Rotary axis parameters incorrect, check values for rotary axis parameters ABS/INK Parameters: %1 = Channel number…
• Page 394
  NCK alarms 61137 [Channel %1: ] Block %2: swiveling and parallel axes cycle are mutually exclusive because of workpiece reference $P_WPFRAME Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycle: CYCLE69. Reaction: Interpreter stop NC Start disable in this channel.
• Page 395
  NCK alarms 61151 [Channel %1: ] Block %2: Orientation of tool not possible —> error code: %4 Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycle: CYCLE800. Remedy: Causes of error: 1st error code = A -> only additive swivel plane permitted, see parameter _ST 61152 [Channel %1: ] Block %2: B axis kinematics (turning technology) either not or incorrectly set up in Start-up of swivel cycle —>…
• Page 396
  NCK alarms 61157 %[[Channel %1: ] Block %2: %]Reference point wrongly programmed Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm is triggered by the following cycle: CYCLE63, CYCLE64, CYCLE899 Remedy: Check reference point in screen form, input only -X, centred or +X 61158 %[[Channel %1: ] Block %2: %]Machining plane wrongly programmed Parameters:…
• Page 397
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 61163 [Channel %1: ] Block %2: Infeed width in the plane too large Parameters: %1 = Channel number %2 = Block number, label Definitions: The alarm is triggered by the following cycles: CYCLE899 Remedy: 61175 [Channel %1: ] Block %2: angle of aperture programmed too small…
• Page 398
  NCK alarms 61178 [Channel %1: ] Block %2: code page not present Parameters: %1 = Channel number %2 = Block number, label Definitions: The specified code page is not supported by the cycle. Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 399
  NCK alarms 61183 [Channel %1: ] Block %2: Swivel CYCLE800: Retraction mode parameter lies outside value range: %4 Parameters: %1 = Channel number %2 = Block number, label Definitions: The value of the retraction mode parameter (_FR) lies outside the valid range. Alarm triggered by following cycles: CYCLE800.
• Page 400
  NCK alarms 61187 [Channel %1: ] Block %2: Check setup of the swivel cycle CYCLE800. —> Error code: Parameters: %1 = Channel number %2 = Block number, label Definitions: The alarm is triggerd by the following cycles: CYCLE800. Reaction: Interpreter stop NC Start disable in this channel.
• Page 401
  NCK alarms 61191 [Channel %1: ] Block %2: Multi-axis transformation not set up. Error code: %4 Parameters: %1 = Channel number %2 = Block number, label Definitions: See error code for error cause. The alarm is triggerd by the following cycles: CYCLE800, 832. Reaction: Interpreter stop NC Start disable in this channel.
• Page 402
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 61196 [Channel %1: ] Block %2: No swiveling in JOG —> Multi-axis transformations and TCARR activated at the same time Parameters: %1 = Channel number %2 = Block number, label Definitions: Multi-axis transformations (TRAORI) and Toolcarrier (TCARR) activated at the same time.
• Page 403
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 61200 [Channel %1: ] Block %2: Too many elements in machining block Parameters: %1 = Channel number %2 = Block number, label Definitions: The machining block contains too many elements. Alarm triggered by following cycles: CYCLE76, CYCLE77, E_CALL, E_DR, E_DR_BGF, E_DR_BOR, E_DR_O1, E_DR_PEC, E_DR_REA, E_DR_SIN, E_DR_TAP, E_MI_TR, E_PI_CIR, E_PI_REC, E_PO_CIR, E_PO_REC, E_PS_CIR, E_PS_FRA, E_PS_HIN, E_PS_MRX, E_PS_POL, E_PS_ROW, E_PS_SEQ, E_PS_XYA, E_SL_LON,…
• Page 404
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Program positioning block. Program Clear alarm with the RESET key. Restart part program Continuation: 61204 [Channel %1: ] Block %2: Technology cycle unknown Parameters: %1 = Channel number %2 = Block number, label…
• Page 405
  NCK alarms 61207 [Channel %1: ] Block %2: No counterspindle step found for synchronizing Parameters: %1 = Channel number %2 = Block number, label Definitions: No counterspindle step was found in any channel with which this channel could synchronize. Alarm is triggered by the following cycles: F_SUB_SP. Reaction: Interpreter stop NC Start disable in this channel.
• Page 406
  NCK alarms 61211 [Channel %1: ] Block %2: Absolute reference missing Parameters: %1 = Channel number %2 = Block number, label Definitions: An incremental indication was made, but the absolute reference is unknown. Alarm triggered by following cycles: E_MI_CON, E_MI_PL, E_PI_CIR, E_PI_REC, E_PO_CIR, E_PO_REC, E_PS_CIR, E_PS_HIN, E_PS_MRX, E_PS_POL, E_PS_SEQ, E_PS_XYA, E_SL_CIR, E_SL_LON, F_PS_CIR, F_PS_MRX, F_PS_SEQ Reaction:…
• Page 407
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 61215 [Channel %1: ] Block %2: Unfinished dimension incorrectly programmed Parameters: %1 = Channel number %2 = Block number, label Definitions: Check the blank spigot dimensions. The blank spigot must be larger than the production part spigot. Alarm triggered by following cycles: CYCLE76, CYCLE77, E_PI_CIR, E_PI_REC, E_PO_CIR, E_PO_REC, F_PI_CIR, F_PI_REC, F_PO_CIR, F_PO_REC Remedy:…
• Page 408
  NCK alarms Remedy: Enter the number of teeth on the milling tool in the «Tool list» menu. Program Clear alarm with the RESET key. Restart part program Continuation: 61219 [Channel %1: ] Block %2: Tool radius too large Parameters: %1 = Channel number %2 = Block number, label Definitions: The tool radius is too large for machining.
• Page 409
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Reduce plane infeed. Program Clear alarm with the RESET key. Restart part program Continuation: 61223 [Channel %1: ] Block %2: Approach path too small Parameters: %1 = Channel number %2 = Block number, label…
• Page 410
  NCK alarms 61226 [Channel %1: ] Block %2: Inclinable head cannot be exchanged Parameters: %1 = Channel number %2 = Block number, label Definitions: The parameter «Swivel data block» is set to «No». In spite of this, an attempt has been made to change the swivel head. Alarm triggered by following functions: E_TCARR, F_TCARR.
• Page 411
  NCK alarms Remedy: 840D: Check the following variables in data block E_MESS_MT_DR[n] or E_MESS_MT_DL[n] for probe n+1 840D sl: Check the following machine data: 51778 $MNS_J_MEA_T_PROBE_DIAM_LENGTH[n] or 51780 $MNS_J_MEA_T_PROBE_DIAM_RAD[n] for probe n+1 61231 [Channel %1: ] Block %2: ShopMill program %4 not executable, as not tested by ShopMill Parameters: %1 = Channel number…
• Page 412
  NCK alarms 61234 [Channel %1: ] Block %2: ShopMill subroutine %4 cannot be executed, as not tested by ShopMill Parameters: %1 = Channel number %2 = Block number, label %4 = Subroutine name Definitions: Before a ShopMill subroutine can be used, it has to be tested by ShopMill. Alarm triggered by following cycle: E_HEAD.
• Page 413
  Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Please contact the responsible Siemens regional office. Program Clear alarm with the RESET key. Restart part program Continuation: 61239 [Channel %1: ] Block %2: Tool change point lies within retraction area!
• Page 414
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Check feed type Program Clear alarm with the RESET key. Restart part program Continuation: 61241 [Channel %1: ] Block %2: Retraction plane not defined for this machining direction Parameters: %1 = Channel number %2 = Block number, label…
• Page 415
  NCK alarms 61244 [Channel %1: ] Block %2: Pitch change causing Parameters: %1 = Channel number %2 = Block number, label Definitions: The specified pitch change causes a reversal of the thread direction. Alarm triggered by following cycle: CYCLE99 Reaction: Interpreter stop NC Start disable in this channel.
• Page 416
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 61248 [Channel %1: ] Block %2: Infeed too small Parameters: %1 = Channel number %2 = Block number, label Definitions: The infeed is too small for machining. Alarm triggered by following cycle: CYCLE79.
• Page 417
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Decrease key width/edge length. Program Clear alarm with the RESET key. Restart part program Continuation: 61252 [Channel %1: ] Block %2: Chamfer/radius too large Parameters: %1 = Channel number %2 = Block number, label…
• Page 418
  NCK alarms 61255 [Channel %1: ] Block %2: Error during cut-off: Tool broken? Parameters: %1 = Channel number %2 = Block number, label Definitions: Cut-off could not be completed. A tool breakage might have occurred. Alarm triggered by following cycles: F_PARTOF, F_SUB_SP. Reaction: Interpreter stop NC Start disable in this channel.
• Page 419
  NCK alarms 61258 [Channel %1: ] Block %2: Assign parameters for counterspindle chuck in the spindle chuck data Parameters: %1 = Channel number %2 = Block number, label Definitions: The parameters for the counterspindle chuck in the spindle chuck data have not been assigned. The alarm is triggered by the following cycles: F_SUB_SP.
• Page 420
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Enter smaller center offset (see display machine data 9862). Program Clear alarm with the RESET key. Restart part program Continuation: 61262 [Channel %1: ] Block %2: pitch not possible with selected tool Parameters: %1 = Channel number %2 = Block number, label…
• Page 421
  NCK alarms 61265 [Channel %1: ] Block %2: Too many restrictions, use rectangular pocket Parameters: %1 = Channel number %2 = Block number, label Definitions: In face milling a maximum of only 3 sides can be delimited. Alarm triggered by following cycle: CYCLE61 Reaction: Interpreter stop NC Start disable in this channel.
• Page 422
  NCK alarms Remedy: The machining direction must be selected to match the delimitations. Program Clear alarm with the RESET key. Restart part program Continuation: 61269 [Channel %1: ] Block %2: External tool diameter too small Parameters: %1 = Channel number %2 = Block number, label Definitions: Incorrect tool definition.
• Page 423
  NCK alarms 61272 %[[Channel %1: ] Block %2: %]Insertion depth too small Parameters: %1 = Channel number %2 = Block number, label Definitions: Insertion depth on chamfering too small. Alarm triggered by following cycles: E_SP_CHA, F_SP_CHA. Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 424
  NCK alarms Remedy: Select another retraction plane or approach a suitable interpolation point. Program Clear alarm with the RESET key. Restart part program Continuation: 61276 [Channel %1: ] Block %2: External tool diameter required for restrictions Parameters: %1 = Channel number %2 = Block number, label Definitions: Outer tool diameter required in case of delimitations.
• Page 425
  NCK alarms 61279 [Channel %1: ] Block %2: If tool angle equals 90°, both tool diameters must be equal Parameters: %1 = Channel number %2 = Block number, label Definitions: For tool angles equal to 90°, the two tool diameters must be identical. Alarm triggered by following cycle: CYCLE61.
• Page 426
  NCK alarms Remedy: Adjust the retraction planes. Program Clear alarm with the RESET key. Restart part program Continuation: 61283 [Channel %1: ] Block %2: direct approach not possible, as tool change required Parameters: %1 = Channel number %2 = Block number, label Definitions: After block search a position is to be reached by direct approach, but a tool change is required before.
• Page 427
  NCK alarms 61286 [Channel %1: ] Block %2: machining not possible, check tool angle. Parameters: %1 = Channel number %2 = Block number, label Definitions: Machining not possible with the specified tool. Alarm triggered by following cycles: F_UCUT_T. Reaction: Interpreter stop NC Start disable in this channel.
• Page 428
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 61290 [Channel %1: ] Block %2:Tool spindle not set up Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycle: CYCLE210 Reaction: Interpreter stop NC Start disable in this channel.
• Page 429
  NCK alarms Remedy: Select spindle rotation direction in tool list. Program Clear alarm with the RESET key. Restart part program Continuation: 61294 [Channel %1: ] Block %2: Active radius/diameter setting does not match reset setting Parameters: %1 = Channel number %2 = Block number, label Definitions: The alarm is triggered by the following cycles: E_HEAD, F_HEAD…
• Page 430
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Program the retraction plane in absolute terms. Program Clear alarm with the RESET key. Restart part program Continuation: 61298 [Channel %1: ] Block %2: No work offset entered for main spindle Parameters: %1 = Channel number %2 = Block number, label…
• Page 431
  NCK alarms 61301 [Channel %1: ] Block %2: Probe not switching Parameters: %1 = Channel number %2 = Block number, label Definitions: The measuring distance was completely traversed, but no switching signal was generated at the measuring input. Alarm can be triggered by following measuring cycles: all measuring cycles. Remedy: -Check measuring input.
• Page 432
  NCK alarms Program Clear alarm with the RESET key. Restart part program Continuation: 61306 [Channel %1: ] Block %2: Permissible measuring difference exceeded Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: Alarm triggered by following cycles: CYCLE971, CYCLE972, CYCLE974, CYCLE977, CYCLE978, CYCLE979, CYCLE982, CYCLE994.
• Page 433
  NCK alarms 61311 [Channel %1: ] Block %2: No D number active Parameters: %1 = Channel number %2 = Block number, label Definitions: No tool offset for the measuring probe (for workpiece measurement) or no tool offset for the active tool (for tool mea- surement) is selected.
• Page 434
  NCK alarms 61316 [Channel %1: ] Block %2: Center and radius cannot be determined Parameters: %1 = Channel number %2 = Block number, label Definitions: No circle can be calculated from the measured points, as all measured points lie on a straight line. The alarm is triggered by: CYCLE979 Remedy: Program change…
• Page 435
  NCK alarms 61321 [Channel %1: ] Block %2: Check WO memory number Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm is triggered: CYCLE974, CYCLE977, CYCLE978, CYCLE979, CYCLE994, CYCLE998. Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 436
  NCK alarms 61326 [Channel %1: ] Block %2: Check measuring direction Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered: CYCLE973, CYCLE976. Remedy: Parameter for measuring direction _MD has an incorrect value. 61327 [Channel %1: ] Block %2: Program reset required Parameters: %1 = Channel number %2 = Block number, label…
• Page 437
  NCK alarms 61332 [Channel %1: ] Block %2: Modify tool tip position Parameters: %1 = Channel number %2 = Block number, label Definitions: The tool tip is below the measuring probe surface (e.g. for a ring gauge or cube). Alarm is triggered: CYCLE971, CYLCE972, CYCLE982, E_MT_CAL, E_MT_LEN, E_MT_RAD.
• Page 438
  NCK alarms 61337 [Channel %1: ] Block %2: Check measuring input Parameters: %1 = Channel number %2 = Block number, label Definitions: Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Program Clear alarm with the RESET key. Restart part program Continuation: 61338 [Channel %1: ] Block %2: Positioning speed equal to zero…
• Page 439
  NCK alarms 61342 [Channel %1: ] Block %2: Upgrade NCK software version Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: Alarm can be triggered by following measuring cycles: all measuring cycles. Remedy: Up to measuring cycle software 6.2: _SI[1] in GUD6 has no value or a value < 3 As from measuring cycle software 6.3: Upgrade NCK software version.
• Page 440
  NCK alarms 61347 [Channel %1: ] Block %2: Angle 1st edge — 2nd edge equals 0 Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm is triggerd by the following cycles: CYCLE961. Remedy: Parameter following angle (_INCA) equals 0. 61348 [Channel %1: ] Block %2: Angle rel.
• Page 441
  NCK alarms 61352 [Channel %1: ] Block %2: Path for logfile not permitted Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm is triggerd by the following cycles: CYCLE106. The specified path for the log file is incorrect. Remedy: Check parameter _PROTNAME[1] 61353…
• Page 442
  NCK alarms Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Delete or unload files MD18270: $MN_MM_NUM_SUBDIR_PER_DIR, MD18280: $MN_MM_NUM_FILES_PER_DIR or MD18320: Check $MN_MM_NUM_FILES_IN_FILESYSTEM and increase if necessary. Program Clear alarm with the RESET key. Restart part program Continuation: 61358 [Channel %1: ] Block %2: Error during recording…
• Page 443
  NCK alarms 61363 [Channel %1: ] Block %2: Max. no. of value lines for recording exceeded Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: Maximum number of value lines exceeded. Alarm triggerd by following cycle: CYCLE105. Remedy: Reduce the number of value lines.
• Page 444
  NCK alarms 61368 [Channel %1: ] Block %2: Straights through parameter _SETV[0…3] or _SETV[4…7]do not intersect Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm is triggerd by the following cycles: CYCLE961. Remedy: Specify different positions for the relevant points of _SETV[0…7] . 61369 [Channel %1: ] Block %2: Position of corner not clearly definable, check parameter _SETV[0…7]…
• Page 445
  NCK alarms 61373 [Channel %1: ] Block %2: Mono-directional probe requires SPOS-capable spindle Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: Alarm can be triggered by following measuring cycles: all measuring cycles. Remedy: Check machine equipment. 61374 [Channel %1: ] Block %2: Probe not calibrated in axis direction %4 Parameters:…
• Page 446
  %1 = Channel number %2 = Block number, label channel number Definitions: Alarm can be triggered by following measuring cycles: all measuring cycles. Remedy: Call the SIEMENS hotline 61404 [Channel %1: ] Block %2: Tool correction not executed Parameters: %1 = Channel number…
• Page 447
  NCK alarms 61409 [Channel %1: ] Block %2: set up offsets not present Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: Alarm can be triggered by following measuring cycles: all measuring cycles. Remedy: Set MD 18112, Bit 4=1 61410 [Channel %1: ] Block %2 access to nonexistent tool element or property Parameters:…
• Page 448
  NCK alarms 61415 [Channel %1: ] Block %2: Check probe / machining plane Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm is triggerd by the following cycles: CYCLE971 Remedy: Enter permissible probe for machining plane: — For 840D: Check the variables _TP[x,8] and _TPW[x,8] in GUD6 — For 840D sl: Check the setting data 54633 $SNS_MEA_TP_TYPE and 54648 $SNS_MEA_TPW_TYPE or change the machining plane.
• Page 449
  NCK alarms 61420 [Channel %1: ] Block %2: Check calibration of multi/mono probes. Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following measuring cycles: CYCLE974, CYCLE994, CYCLE977, CYCLE978, CYCLE979, CYCLE997, CYCLE998 Remedy: The workpiece probe must be calibrated according to its type and use.
• Page 450
  NCK alarms 61425 [Channel %1: ] Block %2: Parameter for measuring axis rotary axis 1 or 2 incorrect -> Error code: %4 Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following measuring cycles: CYCLE996 Remedy: Causes of error: 1.
• Page 451
  NCK alarms 61429 [Channel %1: ] Block %2: Measuring axis (rotary axis 1 or 2) not in basic or intended position -> Error code: %4 Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following measuring cycles: CYCLE996 Remedy: Causes of error: 1.
• Page 452
  NCK alarms 61442 [Channel %1: ] Block %2: Tool carrier not parallel to the geometry axes Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following measuring cycle: CYCLE982 Remedy: As a result of incorrect positioning of the orientable tool carrier, tool lengths L1,2,3 are not parallel to the geometry axes.
• Page 453
  NCK alarms 61501 [Channel %1: ] Block %2: Simulation is active Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following grinding cycles: all grinding cycles Remedy: Reset simulation Program Clear alarm with the RESET key.
• Page 454
  NCK alarms 61506 [Channel %1: ] Block %2: infeed path < 1mm Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following grinding cycle: CYCLE420 Remedy: Increase infeed path Program Clear alarm with the RESET key.
• Page 455
  NCK alarms 61511 [Channel %1: ] Block %2: Incorrect shoulder position or tool edge D1/D2 Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following grinding cycle: setup function Remedy: Program Clear alarm with the RESET key.
• Page 456
  NCK alarms 61517 [Channel %1: ] Block %2: Angle of inclined grinding wheel missing Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following grinding cycle: CYCLE416 Remedy: Enter angle under $TC_TPG8 Program Clear alarm with the RESET key.
• Page 457
  NCK alarms 61522 [Channel %1: ] Block %2: Overlap >= current grinding wheel width Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following grinding cycle: CYCLE411 Remedy: Reduce overlap Program Clear alarm with the RESET key.
• Page 458
  NCK alarms 61527 [Channel %1: ] Block %2: Grinding wheel radius >= workpiece radius Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following grinding cycle: CYCLE414 Remedy: Change grinding wheel radius or workpiece radius Program Clear alarm with the RESET key.
• Page 459
  NCK alarms 61533 [Channel %1: ] Block %2: No length L1 entered under D… Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following grinding cycles: CYCLE416, CYCLE420 Remedy: Enter length L1 in the tool offset D of the grinding wheel Program Clear alarm with the RESET key.
• Page 460
  NCK alarms 61544 [Channel %1: ] Block %2: Grinding wheel diameter worn down Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following grinding cycle: CYCLE438 Remedy: New grinding wheel required, or check limit values in the grinding wheel data Program Clear alarm with the RESET key.
• Page 461
  NCK alarms 61549 [Channel %1: ] Block %2: Incorrect dresser type selected Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following grinding cycles: CYCLE402, CYCLE421, CYCLE422, CYCLE423, CYCLE424 Remedy: Check dresser type on input Program…
• Page 462
  NCK alarms 61559 [Channel %1: ] Block %2: Chamfer / radius + shoulder height are less than the retraction height of the right edge of the grinding wheel Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following grinding cycle: CYCLE432 Remedy:…
• Page 463
  NCK alarms 61564 %[[Channel %1: ] Block %2: %]Feed insertion <=0 Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following grinding cycles: CYCLE434, CYCLE444 Remedy: Check values in grinding wheel data Program Clear alarm with the RESET key.
• Page 464
  NCK alarms 61604 [Channel %1: ] Block %2: Active tool violates programmed contour Parameters: %1 = Channel number %2 = Block number, label Definitions: Contour violation in the relief cut elements due to the tool clearance angle of the tool used. Alarm triggered by following cycle: CYCLE95.
• Page 465
  NCK alarms 61608 [Channel %1: ] Block %2: Incorrect tool point direction programmed Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycles: CYCLE94, CYCLE96. Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 466
  NCK alarms 61613 [Channel %1: ] Block %2: Undercut position incorrectly defined Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycles: CYCLE94, CYCLE96. Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display.
• Page 467
  NCK alarms Remedy: — Check parameter CON — Check contour call — Check whether the contours exist in the program storage (workpieces, subroutines or part programs) Program Clear alarm with the RESET key. Restart part program Continuation: 61702 %[[Channel %1: ] Block %2: %]Label %4 not existing in machined part contour Parameters: %1 = Channel number %2 = Block number, label…
• Page 468
  NCK alarms 61705 %[[Channel %1: ] Block %2: %]Blank contour missing Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycle: CYCLE952 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display.
• Page 469
  NCK alarms Remedy: — Check number of contours — Max. two contours (machined part and blank contours) — Min. one contour (machined part contour) Program Clear alarm with the RESET key. Restart part program Continuation: 61709 %[[Channel %1: ] Block %2: %]Cutting edge radius too small Parameters: %1 = Channel number %2 = Block number, label…
• Page 470
  Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Call the SIEMENS hotline Program Clear alarm with the RESET key. Restart part program Continuation: 61730 %[[Channel %1: ] Block %2: %]Machining range outside delimitation…
• Page 471
  NCK alarms 61731 %[[Channel %1: ] Block %2: %]Unable to determine contour direction Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycle: CYCLE952 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display.
• Page 472
  NCK alarms 61735 %[[Channel %1: ] Block %2: %]Infeed D larger than the tip length of the tool Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycle: CYCLE952 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 473
  NCK alarms Remedy: — Check cutting edge position in tool management Program Clear alarm with the RESET key. Restart part program Continuation: 61739 %[[Channel %1: ] Block %2: %]Blank must be closed contour Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycle: CYCLE952 Reaction:…
• Page 474
  NCK alarms 61742 %[[Channel %1: ] Block %2: %]Retraction plane %4 is within the machining range Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycle: CYCLE952 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 475
  NCK alarms Remedy: Program Clear alarm with the RESET key. Restart part program Continuation: 61803 [Channel %1: ] Block %2: Programmed axis not available Parameters: %1 = Channel number %2 = Block number, label Definitions: The programmed axis is not in the system. Alarm triggered by following cycles: CYCLE83, CYCLE84, CYCLE840.
• Page 476
  NCK alarms 61806 [Channel %1: ] Block %2: Wrong axis assignment Parameters: %1 = Channel number %2 = Block number, label Definitions: The axis-assignment sequence is wrong. Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display.
• Page 477
  NCK alarms 61810 [Channel %1: ] Block %2: ISO G code not possible Parameters: %1 = Channel number %2 = Block number, label Definitions: In the call block an impermissible ISO axis name was programmed. Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 478
  NCK alarms 61814 [Channel %1: ] Block %2: Polar coordinates not possible with cycle Parameters: %1 = Channel number %2 = Block number, label Definitions: Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Program Clear alarm with the RESET key.
• Page 479
  NCK alarms 61818 [Channel %1: ] Block %2: Axis range limits are equal Parameters: %1 = Channel number %2 = Block number, label Definitions: Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Program Clear alarm with the RESET key.
• Page 480
  NCK alarms 61903 %[[Channel %1: ] Block %2: %]Label %4 not existing in the blank contour Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycles: CYCLE63 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 481
  NCK alarms 61907 %[[Channel %1: ] Block %2: %]Pocket contour missing Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycles: CYCLE63, CYCLE64 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display.
• Page 482
  NCK alarms 61911 %[[Channel %1: ] Block %2: %]Error in island contour %4 Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycles: CYCLE63 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display.
• Page 483
  NCK alarms 61915 %[[Channel %1: ] Block %2: %]Cutter radius too small Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycles: CYCLE63, CYCLE64 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display.
• Page 484
  Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display. Remedy: Call the SIEMENS hotline Program Clear alarm with the RESET key. Restart part program Continuation: 61930 %[[Channel %1: ] Block %2: %]No contour available…
• Page 485
  NCK alarms 61931 %[[Channel %1: ] Block %2: %]Contour not closed Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycles: CYCLE63, CYCLE64 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display.
• Page 486
  NCK alarms 61935 %[[Channel %1: ] Block %2: %]Programming of inch/metric measuring system not allowed here Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycles: CYCLE63, CYCLE64 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 487
  NCK alarms Remedy: — Check parameter for specified starting point, — for G17: XS, YS — for G18: ZS, XS — for G19: YS, ZS Program Clear alarm with the RESET key. Restart part program Continuation: 61939 %[[Channel %1: ] Block %2: %]No center point specified for circle Parameters: %1 = Channel number %2 = Block number, label…
• Page 488
  NCK alarms 61942 %[[Channel %1: ] Block %2: %]Helix violates contour Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycles: CYCLE63 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set. Alarm display.
• Page 489
  NCK alarms Remedy: — Check parameter for plane infeed — for G17: DXY — for G18: DZX — for G19: DYZ Program Clear alarm with the RESET key. Restart part program Continuation: 61946 %[[Channel %1: ] Block %2: %]Island contour existing twice Parameters: %1 = Channel number %2 = Block number, label…
• Page 490
  NCK alarms 61949 %[[Channel %1: ] Block %2: %]Island is outside the pocket Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycles: CYCLE63, CYCLE64 Reaction: Interpreter stop NC Start disable in this channel. Interface signals are set.
• Page 491
  NCK alarms 62000 [Channel %1: ] Block %2: Insert new tool Parameters: %1 = Channel number %2 = Block number, label Definitions: Please load new tool. Remedy: Program Clear alarm with the Delete key or NC START. Continuation: 62100 [Channel %1: ] Block %2: No drilling cycle active Parameters: %1 = Channel number %2 = Block number, label…
• Page 492
  NCK alarms 62104 [Channel %1: ] Block %2: Drilling cycle incorrectly defined Parameters: %1 = Channel number %2 = Block number, label Definitions: Reaction: Alarm display. Remedy: Program Clear alarm with the Delete key or NC START. Continuation: 62105 [Channel %1: ] Block %2: Number of columns or lines equals zero Parameters: %1 = Channel number %2 = Block number, label…
• Page 493
  NCK alarms 62180 [Channel %1: ] Block %2: Set rotary axes %4 [deg] Parameters: %1 = Channel number %2 = Block number, label Definitions: Alarm triggered by following cycle: CYCLE800. Note on 62180 and 62181: Sample display of the swivel angle to be set for a manual rotary axis in CYCLE800: 62181 «Set rotary axis B: 32.5 [grd]»…
• Page 494
  NCK alarms 62185 [Channel %1: ] Block %2 : angle adapted to angle grid: %4 Parameters: %1 = Channel number %2 = Block number, label Definitions: %4 difference angle with Hirth tooth system Alarm triggered by following cycle: CYCLE800. Remedy: Check setup of swivel CYCLE800.
• Page 495
  NCK alarms 62202 [Channel %1: ] Block %2: NOTICE: tool travels directly to machining! Parameters: %1 = Channel number %2 = Block number, label Definitions: After block search a position is to be reached by direct approach. Alarm triggered by following cycle: F_TFS. Remedy: Check whether the desired position can be reached without collision.
• Page 496
  NCK alarms 62305 [Channel %1: ] Block %2: Dimension too small Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm is triggerd by the following cycles: CYCLE974, CYCLE977, CYCLE978, CYCLE979, CYCLE994 Remedy: The difference between actual and setpoint value is smaller than lower tolerance limit (parameter _TLL). 62306 [Channel %1: ] Block %2: Permissible measuring difference exceeded Parameters:…
• Page 497
  NCK alarms 62310 [Channel %1: ] Block %2: The max. number of characters per line is limited to 200 characters per line Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: Alarm triggered by following cycles: CYCLE105. The maximum number of characters per line has been limited to 200 characters per line.
• Page 498
  NCK alarms 62315 [Channel %1: ] Block %2: Overwrite swivel data record TCARR = %4, yes -> NC start, no -> reset Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm is triggered by the following cycle: CYCLE996 Remedy: 62316 [Channel %1: ] Block %2: Overwrite TRAORIdata, yes ->…
• Page 499
  NCK alarms 62500 [Channel %1: ] Block %2: GWPS has been limited Parameters: %1 = Channel number %2 = Block number, label channel number Definitions: The alarm can be triggered by the following grinding cycle: CYCLE446 Remedy: Check limit value for GWPS and program a lower value in the NC program if necessary Program Clear alarm with the Delete key or NC START.
• Page 500
  NCK alarms Alarms Diagnostics Manual, 07/2010, 6FC5398-8BP40-0BA0…
• Page 501
  HMI alarms 120006 The channel switchover is currently disabled by area %1. Parameters: %1 = Operating area name Definitions: The area %1 has disabled the channel switchover at the moment, as it is performing a critical operation (e.g. execution from external sources, etc.), during which no channel switchover may occur. Reaction: Alarm display.
• Page 502
  HMI alarms 120400 The settings for the acyclic links with the drive units are not yet effective.%nSwitch off/ on HMI ! Definitions: A file transfer from/to a drive unit has failed as the settings for acyclic links with the drive units become effective only after an HMI reboot.
• Page 503
  3. Return to factory settings of the affected drive unit, switch off/on control, drives and HMI, and then repeat the pro- cess leading to the alarm. 4. Contact Siemens AG, Industry Sector, I DT MC, Hotline (Phone/Fax: see Alarm 1000) regarding the error text. Program…
• Page 504
  2. Check drive load: The CPU time load values in parameter r9976 for the corresponding Control Unit should be less than 80%. 3. Make a note of the error text and contact Siemens AG, Industry Sector, I DT MC, hotline (phone/fax: see alarm 1000).
• Page 505
  HMI alarms 150202 Waiting for a connection to %1 Parameters: %1 = Source URL of the component involved Definitions: The operator panel is connected to the NC and PLC by a communications bus. This alarm occurs if the MMC is started for the first time and the NC/PLC ramp-up has not yet finished or the commu- nication to these components is faulty.
• Page 506
  HMI alarms Alarms Diagnostics Manual, 07/2010, 6FC5398-8BP40-0BA0…
• Page 507
  POWER ON Cause: An internal software error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — evaluate fault buffer (r0945). — carry out a POWER ON (power off/on) for all components. — upgrade firmware to later version.
• Page 508
  IMMEDIATELY Cause: An internal software error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — carry out a POWER ON (power off/on) for all components. — upgrade firmware to later version. — contact the Hotline.
• Page 509
  — check the selected component number (p7828). — check the DRIVE-CLiQ connection. — save suitable firmware file for download in the directory «/siemens/sinamics/code/sac/». — use a component with a suitable hardware version — after POWER ON has been carried out again for the DRIVE-CLiQ component, download the firmware again. Depend- ing on p7826, the firmware will be automatically downloaded.
• Page 510
  SINAMICS alarms 201006 <location>Firmware update for DRIVE-CLiQ component required Message value: Component number: %1 Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The firmware of a DRIVE-CLiQ component must be updated as there is no suitable firmware or firmware version in the component for operation with the Control Unit.
• Page 511
  SINAMICS alarms 201010 <location>Drive type unknown Message value: Drive object: All objects Reaction: NONE Acknowledge: IMMEDIATELY Cause: An unknown drive type was found. Fault value (r0949, interpret decimal): Drive object number (refer to p0101, p0107). Remedy: — Replace Power Module. — carry out a POWER ON (power off/on) for all components.
• Page 512
  Acknowledge: NONE Cause: At least one firmware file in the directory /SIEMENS/SINAMICS/ has been changed without authorization with respect to the version shipped from the factory. No changes are permitted in this directory. Alarm value (r2124, interpret decimal): 0: Checksum of one file is incorrect.
• Page 513
  Acknowledge: NONE Cause: On the memory card, one file in the directory /SIEMENS/SINAMICS/DATA or /ADDON/SINAMICS/DATA has been illegally changed with respect to that supplied from the factory. No changes are permitted in this directory. Alarm value (r2124, interpret decimal): The problem is indicated in the first digit of the alarm value: 1.
• Page 514
  SINAMICS alarms Remedy: Set the monitoring time higher at the PC or, if required, completely disable the monitoring function. For the commissioning software, the monitoring time is set as follows: <Drive> -> Commissioning -> Control panel -> Button «Fetch master control» -> A window is displayed to set the mon- itoring time in milliseconds.
• Page 515
  Instead, a back-up data set or a back-up parameter back-up file is downloaded. Alarm value (r2124, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: If you have saved the project using the commissioning software, carry out a new download for your project. Save using the function «Copy RAM to ROM»…
• Page 516
  = 012 —> data save started with p0977 = 12 Byte 4, 3: Only for internal Siemens troubleshooting. Remedy: — check whether one of the files to be overwritten has the attribute «read only» and change this file attribute to «writable».
• Page 517
  = 011 —> data save started with p0977 = 11 b = 012 —> data save started with p0977 = 12 d, c: Only for internal Siemens troubleshooting. Remedy: — check the file attribute of the files (PSxxxyyy.***, CAxxxyyy.***, CCxxxyyy.***) and, if required, change from «read only»…
• Page 518
  3: Target directory cannot be set up. 4. Target file cannot be set up/opened. 5. Target file cannot be written to. Additional values: Only for internal Siemens troubleshooting. Remedy: — save the parameters. — download the project again to the drive unit.
• Page 519
  SINAMICS alarms 108: Unit unknown. 109: Write access only in the commissioning state, encoder (p0010 = 4). 110: Write access only in the commissioning state, motor (p0010 = 3). 111: Write access only in the commissioning state, power unit (p0010 = 2). 112: Write access only in the quick commissioning mode (p0010 = 1).
• Page 520
  An error was detected when evaluating the parameter files PSxxxyyy.ACX, PTxxxyyy.ACX, CAxxxyyy.ACX, or CCxxxyyy.ACX saved in the non-volatile memory. Alarm value (r2124, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: Restore the factory setting using (p0976 = 1) and re-load the project to the drive unit. Operation without any restrictions is then possible.
• Page 521
  SINAMICS alarms 201050 <location>Memory card and device incompatible Message value: Drive object: All objects Reaction: Servo: OFF2 (NONE, OFF1, OFF3) Infeed: OFF2 (NONE, OFF1) Acknowledge: IMMEDIATELY Cause: The memory card and the device type do not match (e.g. a memory card for SINAMICS S is inserted in SINAMICS G). Remedy: — insert the matching memory card.
• Page 522
  SINAMICS alarms 201065 <location>Drive: Fault on non-active encoder Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: One or several non-active encoders indicate an error. Remedy: Remove the error for the non-active encoder. 201068 <location>CU: Data memory, memory overflow Message value: Drive object: All objects…
• Page 523
  Too many functions have been configured on this Control Unit (e.g. too many drives, function modules, data sets, OA applications, blocks, etc). Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: — change the configuration on this Control Unit (e.g. fewer drives, function modules, data sets, OA applications, blocks, etc).
• Page 524
  Cause: An internal software error occurred while the terminal functions were being initialized. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — carry out a POWER ON (power off/on) for all components. — upgrade firmware to later version.
• Page 525
  998: Too many time slices occupied by OA (e.g. DCC) 999: Too many time slices occupied by the basic system Too many different sampling times may have been set. Further values for internal Siemens troubleshooting. Remedy: — check the sampling time setting (p0112, p0115, p4099).
• Page 526
  Acknowledge: POWER ON Cause: Insufficient processing time is available for the existing topology. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — reduce the number of drives. — increase the sampling times. 201221 <location>CU: Bas clk cyc too low…
• Page 527
  SINAMICS alarms 21: Value can be a multiple of the current controller sampling time of a servo or vector drive in the system (e.g. for TB30, the values of all of the indices should be taken into account). 30: Value less than 31.25 µs. 31: Value less than 62.5 µs.
• Page 528
  Acknowledge: POWER ON Cause: Error when reading the read-only data of the EEPROM in the Control Unit. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: — carry out a POWER ON. — replace the Control Unit. 201251 <location>CU: CU-EEPROM incorrect read-write data…
• Page 529
  Acknowledge: NONE Cause: Error when reading the read-write data of the EEPROM in the Option Board. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: — carry out a POWER ON. — replace the Control Unit. 201303 <location>DRIVE-CLiQ component does not support the required function…
• Page 530
  SINAMICS alarms 201305 <location>Topology: Component number missing Message value: Drive object: All objects Reaction: NONE Acknowledge: IMMEDIATELY Cause: The component number from the topology was not parameterized (p0121 (for power unit, refer to p0107), p0131 (for servo/vector drives, refer to p0107), p0141, p0151, p0161). Fault value (r0949, interpret decimal): The fault value includes the particular data set number.
• Page 531
  SINAMICS alarms 201315 <location>Drive object not ready for operation Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: For the active drive object involved, at least one activated component is missing. Note: All other active and operational drive objects can be in the «RUN» state. Remedy: The alarm automatically disappears again with the following actions: — de-activate the drive object involved (p0105 = 0).
• Page 532
  SINAMICS alarms 201318 <location>BICO: De-activated interconnections present Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: This alarm is used in the following cases: — If an inactive/non-operational drive object is active again/ready for operation — If there are items in the list of BI/CI parameters (r9498[0…29], r9499[0…29]) — If the BICO interconnections saved in the list of BI/CI parameters (r9498[0…29], r9499[0…29]) have actually been changed Remedy:…
• Page 533
  SINAMICS alarms 201321 <location>Topology: Drive object number does not exist in configuration Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: p0978 contains a drive object number that does not exist. Alarm value (r2124, interpret decimal): Index of p0978 under which the drive object number can be determined. Remedy: Set p0009 to 1 and change p0978: Rules:…
• Page 534
  SINAMICS alarms 201324 <location>Topology: Dummy drive object number incorrectly created Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: In p0978, dummy drive object numbers (255) are only permitted in the first partial list. Alarm value (r2124, interpret decimal): Index of p0978 under which the illegal value is located.
• Page 535
  SINAMICS alarms aa = 03 hex = 3 dec: More than 16 components are connected at a DRIVE-CLiQ socket of the Control Unit. — bb = 0, 1, 2, 3 means e.g. detected at the DRIVE-CLiQ socket X100, X101, X102, X103. — cccc: Not used.
• Page 536
  SINAMICS alarms 201340 <location>Topology: Too many components on one line Message value: Component number or connection number: %1, fault cause: %2 Drive object: All objects Reaction: NONE Acknowledge: IMMEDIATELY Cause: For the selected communications clock cycle, too many DRIVE-CLiQ components are connected to one line of the Control Unit.
• Page 537
  The fault only occurs if the topology was commissioned using the automatic internal device mechanism and not using the commissioning software. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. See also: r0098 (Actual device topology), p0099 (Device target topology) Remedy:…
• Page 538
  SINAMICS alarms 201360 <location>Topology: Actual topology not permissible Message value: Fault cause: %1, preliminary component number: %2 Drive object: All objects Reaction: NONE Acknowledge: IMMEDIATELY Cause: The detected actual topology is not permissible. Fault value (r0949, interpret hexadecimal): ccccbbaa hex: cccc = preliminary component number, aa = fault cause aa = 01 hex = 1 dec: Too many components were detected at the Control Unit.
• Page 539
  NONE Cause: At least one topology rule for the SINAMICS S120 Combi has been broken. In the event of a fault, the ramping up of the drive system is aborted and closed-loop drive control is not enabled. Fault value (r0949, interpret decimal): The fault value indicates which rule has been broken.
• Page 540
  SINAMICS alarms 201375 <location>Topology: Actual topology, duplicate connection between two components Message value: Preliminary component number: %1, component class: %2, connection number: %3 Drive object: All objects Reaction: NONE Acknowledge: IMMEDIATELY Cause: When detecting the actual topology, a ring-type connection was detected. Fault value (r0949, interpret hexadecimal): ccbbaaaa hex: cc = connection number…
• Page 541
  SINAMICS alarms 201381 <location>Topology: Comparison power unit shifted Message value: Component number: %1, Component class: %2, Component (target): %3, Connection number: %4 Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The topology comparison has detected a power unit in the actual topology that has been shifted with respect to the target topology.
• Page 542
  SINAMICS alarms 201383 <location>Topology: Comparison Terminal Module shifted Message value: Component number: %1, Component class: %2, Component (target): %3, Connection number: %4 Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The topology comparison has detected a Terminal Module in the actual topology that has been shifted with respect to the target topology.
• Page 543
  SINAMICS alarms 201385 <location>Topology: Comparison CX32 shifted Message value: Component number: %1, Component class: %2, Component (target): %3, Connection number: %4 Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The topology comparison has detected a controller extension 32 (CX32) in the actual topology that has been shifted with respect to the target topology.
• Page 544
  SINAMICS alarms 201387 <location>Topology: Comparison option slot component shifted Message value: Component number: %1, Component class: %2, Component (target): %3, Connection number: %4 Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The topology comparison has detected a option slot component in the actual topology that has been shifted with respect to the target topology.
• Page 545
  SINAMICS alarms 201389 <location>Topology: Comparison motor with DRIVE-CLiQ shifted Message value: Component number: %1, Component class: %2, Component (target): %3, Connection number: %4 Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The topology comparison has detected a motor with DRIVE-CLiQ in the actual topology that has been shifted with respect to the target topology.
• Page 546
  SINAMICS alarms 201420 <location>Topology: Comparison a component is different Message value: Component number: %1, component class target: %2, component class actual: %3, fault cause: %4 Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The topology comparison has detected differences in the actual and target topologies in relation to one component. There are differences in the electronic rating plate.
• Page 547
  SINAMICS alarms Remedy: Check the component soft-wired connections against the hardware configuration of the drive unit in the commissioning software and correct differences. Note: Under «Topology —> Topology view» the commissioning software offers improved diagnostics capability (e.g. setpoint/ actual value comparison). 201425 <location>Topology: Comparison serial number of a component is different Message value:…
• Page 548
  SINAMICS alarms Remedy: Adapting the topologies: — change over the actual topology to match the target topology. — download the target topology that matches the actual topology (commissioning software). — automatically remove the topology error (p9904). Note: Under «Topology —> Topology view» the commissioning software offers improved diagnostics capability (e.g. setpoint/ actual value comparison).
• Page 549
  SINAMICS alarms 201470 <location>Topology:Target topology ring-type connection detected Message value: Component number: %1, Component class: %2, Connection number: %3 Drive object: All objects Reaction: NONE Acknowledge: IMMEDIATELY Cause: A ring-type connection was detected when writing to the target topology. Fault value (r0949, interpret hexadecimal): ddccbbaa hex: cc = connection number bb = component class…
• Page 550
  SINAMICS alarms 201481 <location>Topology: Comparison power unit missing in the actual topology Message value: Component number: %1 Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The topology comparison has detected a power unit in the target topology that is not available in the actual topology. Alarm value (r2124, interpret decimal): Component number of the additional target components.
• Page 551
  SINAMICS alarms 201483 <location>Topology: Comparison Terminal Module missing in the actual topology Message value: Component number: %1 Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The topology comparison has detected a Terminal Module in the target topology that is not available in the actual topol- ogy.
• Page 552
  SINAMICS alarms 201485 <location>Topology: Comparison CX32 missing in the actual topology Message value: Component number: %1 Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The topology comparison has detected a controller extension 32 (CX32) in the target topology that is not available in the actual topology.
• Page 553
  SINAMICS alarms Remedy: — delete the option board in the commissioning software project and download the new configuration to the drive unit. — re-configure the drive unit in the commissioning software project and download the new configuration to the drive unit. — check that the actual topology matches the target topology and if required, change over.
• Page 554
  SINAMICS alarms 201505 <location>BICO: Interconnection cannot be established Message value: Parameter: %1 Drive object: All objects Reaction: NONE Acknowledge: IMMEDIATELY Cause: A PROFIdrive telegram has been set (p0922). An interconnection contained in the telegram was not able to be established. Fault value (r0949, interpret decimal): Parameter receiver that should be changed.
• Page 555
  SINAMICS alarms 201508 <location>BICO: Interconnections to inactive objects exceeded Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The maximum number of BICO interconnections (signal sinks) when de-activating a drive object was exceeded. When de-activating a drive object, all BICO interconnections (signal sinks) are listed in the following parameters: — r9498[0…29]: List of the BI/CI parameters involved.
• Page 556
  SINAMICS alarms 201512 <location>BICO: No scaling available Message value: Drive object: All objects Reaction: Servo: OFF2 Infeed: OFF2 (OFF1) Acknowledge: POWER ON Cause: An attempt was made to determine a conversion factor for a scaling that does not exist. Fault value (r0949, interpret decimal): Unit (e.g.
• Page 557
  SINAMICS alarms 201515 <location>BICO: Writing to parameter not permitted as the master control is active Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: IMMEDIATELY Cause: While changing the number of CDS or when copying from CDS, the master control was active. Remedy: None necessary.
• Page 558
  SINAMICS alarms 201611 <location>SI CU: Defect in a monitoring channel Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE (OFF1, OFF2, OFF3) Acknowledge: IMMEDIATELY (POWER ON) Cause: The drive-based «Safety Integrated» function in the Control Unit (CU) has detected a fault in the data cross-check between the CU and Motor Module (MM) and initiated a STOP F.
• Page 559
  SINAMICS alarms Re fault value = 2000, 2001, 2002, 2004, 2005: — check the tolerance time SGE changeover and if required, increase the value (p9650/p9850, p9652/p9852). — check the wiring of the safety-relevant inputs (SGE) (contact problems). — check the causes of the STO selection in r9772. When the SMM functions are active (p9501 = 1), STO can also be selected using these functions.
• Page 560
  — there is either a DRIVE-CLiQ communication error or communication has failed. — a time slice overflow of the safety software has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: — select Safe Torque Off and de-select again.
• Page 561
  SINAMICS alarms 201630 <location>SI CU: Brake control error Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 Acknowledge: IMMEDIATELY (POWER ON) Cause: The drive-based «Safety Integrated» function in the Control Unit (CU) has detected a brake control error and initiated a STOP A. Fault value (r0949, interpret decimal): 10, 11: Fault in «open holding brake»…
• Page 562
  Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — carry out a POWER ON (power off/on) for all components. — re-commission the «Safety Integrated» function and carry out a POWER ON.
• Page 563
  This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal): 150: Fault in the synchronization to the PROFIBUS master. All other values: Only for internal Siemens troubleshooting. See also: p9510 (SI Motion clock-cycle synchronous PROFIBUS master) Alarms…
• Page 564
  SINAMICS alarms Remedy: Re fault value = 150: — check the setting of p9510 (SI Motion clock-cycle synchronous PROFIBUS master) and if required, correct. General: — carry out a POWER ON (power off/on) for all components. — upgrade the Motor Module software. — upgrade the Control Unit software.
• Page 565
  SINAMICS alarms Remedy: For enabled drive-based SI monitoring (p9601/p9801 > 0): — upgrade the Control Unit software. For enabled motion monitoring function (p9501 > 0): — correct the monitoring clock cycle (p9500) and carry out POWER ON. Re fault value = 101: — actual value sensing clock cycle corresponds to position control clock cycle/DP clock cycle (factory setting).
• Page 566
  Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — carry out a POWER ON (power off/on) for all components. — upgrade the Motor Module software.
• Page 567
  SINAMICS alarms Remedy: — re-commission the safety functions. — upgrade the Control Unit software. — upgrade the Motor Module software. — replace the memory card or Control Unit. Re fault value = 132: — check the electrical cabinet design and cable routing for EMC compliance Note: CU: Control Unit MM: Motor Module…
• Page 568
  SINAMICS alarms Re fault value = 16: — inhibit the internal voltage protection (p1231). Note: CU: Control Unit MM: Motor Module SBC: Safe Brake Control SI: Safety Integrated SS1: Safe Stop 1 (corresponds to Stop Category 1 acc. to EN60204) STO: Safe Torque Off / SH: Safe standstill SBA: Safe Brake Adapter See also: p9501 (SI Motion enable safety functions (Control Unit)), p9601 (SI enable, functions integrated in the drive…
• Page 569
  Cause: Before the drive booted the last time, it detected a defect in the system and carried out an emergency stop. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — carry out a POWER ON (power off/on).
• Page 570
  SINAMICS alarms 201670 <location>SI Motion: Invalid parameterization Sensor Module Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 Acknowledge: IMMEDIATELY (POWER ON) Cause: The parameterization of a Sensor Module used for Safety Integrated is not permissible. Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret decimal): 1: No encoder was parameterized for Safety Integrated.
• Page 571
  Note: This fault does not result in a safety stop response. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: — upgrade the Sensor Module software. — use a Sensor Module that supports the safe motion monitoring function.
• Page 572
  SINAMICS alarms 201680 <location>SI Motion CU: Checksum error safety monitoring functions Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 Acknowledge: IMMEDIATELY (POWER ON) Cause: The actual checksum calculated by the drive and entered in r9728 via the safety-relevant parameters does not match the reference checksum saved in p9729 at the last machine acceptance.
• Page 573
  SINAMICS alarms 201682 <location>SI Motion CU: Monitoring function not supported Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 Acknowledge: IMMEDIATELY (POWER ON) Cause: The monitoring function enabled in p9501, p9601 or p9801 is not supported in this firmware version. Note: This fault results in a STOP A that cannot be acknowledged.
• Page 574
  SINAMICS alarms 201684 <location>SI Motion: Safely limited position limit values interchanged Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 Acknowledge: IMMEDIATELY (POWER ON) Cause: For the function «Safely-Limited Position» (SE), a lower value is in p9534 than in p9535. Note: This fault does not result in a safety stop response.
• Page 575
  SINAMICS alarms Remedy: Correct the cam position and carry out a POWER ON. Note: SCA: Safe Cam / SN: Safe software cam SI: Safety Integrated See also: p9536 (SI Motion SCA (SN) plus cam position (Control Unit)), p9537 (SI Motion SCA (SN) plus cam position (Control Unit)) 201687 <location>SI Motion: Illegal parameterization modulo value SCA (SN)
• Page 576
  SINAMICS alarms 201689 <location>SI Motion: Axis re-configured Message value: Parameter: %1 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 Acknowledge: POWER ON Cause: The axis configuration was changed (e.g. changeover between linear axis and rotary axis). Parameter p0108.13 is internally set to the correct value. Note: This fault does not result in a safety stop response.
• Page 577
  SINAMICS alarms 201691 <location>SI Motion: Ti and To unsuitable for DP cycle Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The configured times for PROFIBUS communication are not permitted and the DP cycle is used as the actual value acquisition cycle for the safe movement monitoring functions: Isochronous PROFIBUS: the total of Ti and To is too high for the set DP cycle.
• Page 578
  SINAMICS alarms 201696 <location>SI Motion: Testing of the motion monitoring functions selected when booting Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The test of the motion monitoring functions was already illegally active when booting. This is the reason that the test is only carried out again after selecting the forced checking procedure parameterized in p9705.
• Page 579
  SINAMICS alarms 201698 <location>SI CU: Commissioning mode active Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM54F_MA Reaction: NONE Acknowledge: NONE Cause: The commissioning of the «Safety Integrated» function is selected. This message is withdrawn after the safety functions have been commissioned. Note: This message does not result in a safety stop response.
• Page 580
  SINAMICS alarms Remedy: — remove the cause of the fault on the second monitoring channel — carry out a diagnostics routine for message C01706. — carry out a diagnostics routine for message C01714. — carry out a diagnostics routine for message C01701. — check the value in p9557 (where available), increase the value if necessary, and carry out a POWER ON — check the shutdown path of the Control Unit (check DRIVE-CLiQ communication if it has been implemented) — replace the Motor Module/Power Module…
• Page 581
  SINAMICS alarms 201707 <location>SI Motion CU: Tolerance for safe operating stop exceeded Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: IMMEDIATELY (POWER ON) Cause: The actual position has distanced itself further from the target position than the standstill tolerance. The drive is shut down by the message C01701 «SI Motion: STOP B initiated».
• Page 582
  SINAMICS alarms 201709 <location>SI Motion CU: STOP D initiated Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: IMMEDIATELY (POWER ON) Cause: The drive is stopped via a STOP D (braking along the path). «Safe Operating Stop» (SOS) is activated after the parameterized timer has expired. Possible causes: — stop request from the higher-level control.
• Page 583
  Message value (r9749, interpret decimal): 0 to 999: Number of the cross-checked data that resulted in this fault. Message values that are not subsequently listed are only for internal Siemens troubleshooting. 0: Stop request from the other monitoring channel. 1: Status image of monitoring functions SOS, SLS or SLP (result list 1) (r9710[0], r9710[1]).
• Page 584
  SINAMICS alarms 44: Position actual value (r9713) + limit value for SLS1 (p9531[0]/p9331[0]) 45: Position actual value (r9713) — limit value for SLS1 (p9531[0]/p9331[0]) 46: Position actual value (r9713) + limit value for SLS2 (p9531[1]/p9331[1]) 47: Position actual value (r9713) — limit value for SLS2 (p9531[1]/p9331[1]) 48: Position actual value (r9713) + limit value for SLS3 (p9531[2]/p9331[2]) 49: Position actual value (r9713) — limit value for SLS3 (p9531[2]/p9331[2]) 50: Position actual value (r9713) + limit value for SLS4 (p9531[3]/p9331[3])
• Page 585
  5000, 5014, 5023, 5024, 5030 … 5032, 5042, 5043, 5052, 5053, 5068, 5072, 5073, 5082 … 5087, 5090, 5091, 5122 … 5125, 5132 … 5135, 5140: An internal software error has occurred (only for internal Siemens troubleshooting). 5012: Error when initializing the PROFIsafe driver.
• Page 586
  SINAMICS alarms Re message value = 1001: — carry out a POWER ON (power off/on) for all components. — upgrade the Motor Module software. — upgrade the Control Unit software. Re message value = 1005: — check the conditions for pulse enable. Re message value = 1011: — for diagnostics, refer to parameter (r9571).
• Page 587
  SINAMICS alarms Re message value = 6000: — carry out a POWER ON (power off/on) for all components. — check whether there is a DRIVE-CLiQ communication error between the Control Unit and the Motor Module involved and, if required, carry out a diagnostics routine for the faults identified. — increase the monitoring cycle clock settings (p9500, p9511).
• Page 588
  SINAMICS alarms 201712 <location>SI Motion CU: Defect in F-IO processing Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: IMMEDIATELY (POWER ON) Cause: When cross checking and comparing the two monitoring channels, the drive detected a difference between parame- ters or results of the F-IO processing and initiated a STOP F. One of the monitoring functions no longer reliably func- tions — i.e.
• Page 589
  SINAMICS alarms 201714 <location>SI Motion CU: Safely-Limited Speed exceeded Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: IMMEDIATELY (POWER ON) Cause: The drive has moved faster than that specified by the velocity limit value (p9531). The drive is stopped as a result of the configured stop response (p9563).
• Page 590
  IMMEDIATELY (POWER ON) Cause: The DRIVE-CLiQ encoder for safe motion monitoring signals an error for the effectivity tests. Message value (r9749, interpret decimal): Only for internal Siemens troubleshooting. Remedy: — check the encoder connection. — replace the encoder. This message can be acknowledged as follows:…
• Page 591
  SINAMICS alarms 201799 <location>SI Motion CU: Acceptance test mode active Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: IMMEDIATELY (POWER ON) Cause: The acceptance test mode is active. The POWER ON signals of the safety-relevant motion monitoring functions can be acknowledged during the acceptance test using the RESET button of the higher-level control.
• Page 592
  SINAMICS alarms 201840 <location>SMI: Component found without motor data Message value: Component number: %1 Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: An SMI/DQI without motor data has been found (e.g. SMI installed as replacement part). Alarm value (r2124, interpret decimal): Component number from target topology.
• Page 593
  SINAMICS alarms 201901 <location>PROFIBUS: Parameterizing telegram error Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: A PROFIBUS master attempts to establish a connection using an incorrect parameterizing telegram. Alarm value (r2124, interpret decimal): 1: Incorrect parameterizing bits. 10: Illegal length of an optional parameterizing block.
• Page 594
  SINAMICS alarms 201903 <location>COMM INT: Receive configuration data invalid Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The drive unit did not accept the receive configuration data. Alarm value (r2124, interpret decimal): Return value of the receive configuration data check. 0: Configuration accepted.
• Page 595
  SINAMICS alarms 201911 <location>IF1: PB/PN clock cycle synchronous operation clock cycle failure Message value: Drive object: All objects Reaction: Servo: OFF1 (OFF3) Infeed: OFF1 Acknowledge: IMMEDIATELY Cause: The global control telegram to synchronize the clock cycles has failed — in cyclic operation — for several DP clock cycles or has violated the time grid specified in the parameterizing telegram over several consecutive DP clock cycles (refer to the bus cycle time, Tdp and Tpllw).
• Page 596
  SINAMICS alarms 201914 <location>COMM INT: Monitoring time configuration expired Message value: Drive object: All objects Reaction: Servo: OFF1 (NONE, OFF2, OFF3) Infeed: OFF1 (NONE, OFF2) Acknowledge: IMMEDIATELY Cause: The monitoring time for the configuration has expired. Fault value (r0949, interpret decimal): 0: The transfer time of the send configuration data has been exceeded.
• Page 597
  SINAMICS alarms 201921 <location>PROFIBUS: Receive setpoints after To Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: Output data of PROFIBUS master (setpoints) received at the incorrect instant in time within the PROFIBUS clock cycle. Remedy: — check bus configuration. — check parameters for clock cycle synchronization (ensure To >…
• Page 598
  SINAMICS alarms 201932 <location>IF1: PB/PN clock cycle synchronization missing for DSC Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: There is no clock cycle synchronization and DSC is selected. Note: DSC: Dynamic Servo Control Remedy: Set the clock cycle synchronization when configuring the bus.
• Page 599
  IMMEDIATELY (POWER ON) Cause: Synchronization of the internal clock cycle to the global control telegram has failed. The internal clock cycle exhibits an unexpected shift. Remedy: Only for internal Siemens troubleshooting. Note: IF1: Interface 1 PB: PROFIBUS PN: PROFINET Alarms…
• Page 600
  Control Unit. This synchronization routine was unsuccessful. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: — carry out a POWER ON (power off/on) for all components. — upgrade the software of the DRIVE-CLiQ components.
• Page 601
  After the drive system is powered up, the synchronization between the basic clock cycle, DRIVE-CLiQ clock cycle and application clock cycle was started and was not able to be successfully completed. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: 1. Ensure perfect functioning of the DRIVE-CLiQ.
• Page 602
  SINAMICS alarms 202005 <location>Function generator: Drive does not exist Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The drive object specified for connection does not exist. See also: p4815 (Function generator drive number) Remedy: Use the existing drive object with the corresponding number. Note: The alarm is reset as follows: — remove the cause of this alarm.
• Page 603
  SINAMICS alarms 202008 <location>Function generator: Drive specified a multiple number of times Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The drive object specified for connection is already specified. Alarm value (r2124, interpret decimal): Drive object number of the drive object that is specified a multiple number of times. Remedy: Specify a different drive object.
• Page 604
  SINAMICS alarms 202011 <location>Function generator: The actual drive speed is not zero Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The speed actual value of a drive selected for connection is greater than the value for the standstill detection set using p1226.
• Page 605
  SINAMICS alarms 202020 <location>Function generator: Parameter cannot be changed Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: This parameter setting cannot be changed when the function generator is active (p4800 = 1). See also: p4810, p4812, p4813, p4815, p4820, p4821, p4822, p4823, p4824, p4825, p4826, p4827, p4828, p4829 Remedy: — stop the function generator before parameterizing (p4800 = 0).
• Page 606
  SINAMICS alarms 202030 <location>Function generator: Physical address equals zero Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The specified physical address is zero. See also: p4812 (Function generator physical address) Remedy: Set a physical address with a value other than zero. Note: The alarm is reset as follows: — remove the cause of this alarm.
• Page 607
  SINAMICS alarms 202047 <location>Function generator: Time slice clock cycle invalid Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The time slice clock cycle selected does not match any of the existing time slices. See also: p4830 (Function generator time slice cycle) Remedy: Enter an existing time slice clock cycle.
• Page 608
  SINAMICS alarms 202057 <location>Trace: Time slice clock cycle invalid Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The time slice clock cycle selected does not match any of the existing time slices. See also: p4723 (Time slice cycle for trace) Remedy: Enter an existing time slice clock cycle.
• Page 609
  SINAMICS alarms 202061 <location>Trace: Invalid signal Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: — the specified signal does not exist. — the specified signal can no longer be traced (recorded). See also: p4730 (Trace record signal 0), p4731 (Trace record signal 1), p4732 (Trace record signal 2), p4733 (Trace record signal 3) Remedy: — specify the signal to be traced.
• Page 610
  SINAMICS alarms 202075 <location>Trace: Pretrigger time too long Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The selected pretrigger time must be shorter than the trace time. See also: p4721 (Trace recording time), p4722 (Trace trigger delay) Remedy: Check the pretrigger time setting and change if necessary.
• Page 611
  NONE Cause: The system was not able to load an OA application. Alarm value (r2124, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — carry out a POWER ON (power off/on) for all components. — upgrade firmware to later version.
• Page 612
  SINAMICS alarms 203000 <location>NVRAM fault on action Message value: Drive object: All objects Reaction: NONE Acknowledge: IMMEDIATELY Cause: A fault occurred during execution of action p7770 = 1, 2 for the NVRAM data. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = fault cause, xx = application ID yy = 1: The action p7770 = 1 is not supported by this version if Drive Control Chart (DCC) is activated for the drive object concerned.
• Page 613
  SINAMICS alarms 203501 <location>TM: Sampling time change Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The sampling times of the inputs/outputs were changed. This change only becomes valid after the next boot. Remedy: Carry out a POWER ON. 203505 <location>TM: Analog input wire breakage Message value:…
• Page 614
  SINAMICS alarms 203590 <location>TM: Module not ready Message value: Drive object: All objects Reaction: Servo: NONE (ENCODER, IASC/DCBRAKE, OFF1, OFF2, OFF3, STOP1, STOP2) Infeed: OFF2 (NONE) Acknowledge: IMMEDIATELY (POWER ON) Cause: The Terminal Module involved does not send a ready signal and no valid cyclic data. Fault value (r0949, interpret decimal): Drive object number of the Terminal Module involved.
• Page 615
  SINAMICS alarms 205002 <location>Power unit: Air intake overtemperature Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The alarm threshold for the air intake overtemperature has been reached. For air-cooled power units, the threshold is 42 °C (hysteresis 2 K).
• Page 616
  SINAMICS alarms 205005 <location>Cooling system: Cooling medium flow rate too low Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: Cooling system: Alarm — flow rate has fallen below the alarm value Remedy: 205006 <location>Power unit: Overtemperature thermal model Message value: Drive object:…
• Page 617
  SINAMICS alarms 205051 <location>Parallel circuit: Power unit pulse enable missing Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_SINUMERIK_828 Reaction: OFF2 (NONE, OFF1) Acknowledge: IMMEDIATELY Cause: For one or several power units, the pulses were not able to be enabled. Fault value (r0949, interpret decimal): Number of the power unit involved.
• Page 618
  SINAMICS alarms 205055 <location>Power circuit: Power units with different code numbers Message value: Parameter: %1 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 (NONE) Acknowledge: IMMEDIATELY Cause: The code numbers of the power units do not match. Fault value (r0949, interpret decimal): Parameter in which the first different power unit code number was detected.
• Page 619
  SINAMICS alarms 205059 <location>Parallel circuit: VSM firmware versions differ Message value: Parameter: %1 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: IMMEDIATELY Cause: The firmware versions of the Voltage Sensing Module (VSM) do not match. Fault value (r0949, interpret decimal): Parameter in which the first different version number was detected.
• Page 620
  SINAMICS alarms 206000 <location>Infeed: Precharging monitoring time expired Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 (OFF1) Acknowledge: IMMEDIATELY Cause: After the line contactor closes the power unit does not signal the READY state within the monitoring time (p0857). The end of the DC link pre-charging was not able to be completed for one of the following reasons: 1) There is no line supply voltage connected.
• Page 621
  SINAMICS alarms 206050 <location>Infeed: Smart Mode not supported Message value: Drive object: AFE_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 Acknowledge: IMMEDIATELY (POWER ON) Cause: The power unit does not support the Smart Mode. Remedy: — set the suitable sampling time 250 µs <= p0115[0] <= 400 µs (e.g. by setting p0112 and p0115 to the factory setting). — upgrade the power unit software and/or hardware for the Smart Mode.
• Page 622
  SINAMICS alarms 206105 <location>Infeed: Line supply undervoltage Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The filtered (steady-state) value of line supply voltage is lower than the alarm threshold (p0282). Alarm condition: Vrms < p0282 * p0210 Alarm value (r2124, floating point): Actual steady-state line supply voltage.
• Page 623
  SINAMICS alarms 206205 <location>Infeed: Voltage dip in at least one line supply phase Message value: Drive object: AFE_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: Voltage dip or overvoltage in one or several line supply phases has been detected in operation. The pulses are then inhibited for a time of at least 8 ms.
• Page 624
  SINAMICS alarms 206210 <location>Infeed: Summation current too high Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 (OFF1) Acknowledge: IMMEDIATELY (POWER ON) Cause: The smoothed total of the phase currents (i1 + i2 + i3) is greater than 4 % of the maximum power unit current (r0209). Possible causes: — the DC link has a ground fault that results in a high summation current (r0069.6).
• Page 625
  SINAMICS alarms 206250 <location>Infeed: Defective capacitor(s) in at least one phase of line filter Message value: Drive object: AFE_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: A change in the line filter capacitance was detected in at least one line phase. The voltages and phase currents of the line filter, measured using a Voltage Sensing Module (VSM), indicate a devi- ation of the filter capacitances from the value parameterized in p0221.
• Page 626
  SINAMICS alarms 206261 <location>Infeed: Temperature in the line filter permanently too high Message value: Drive object: AFE_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 (OFF1) Acknowledge: IMMEDIATELY Cause: After the temperature monitoring responded, the temperature in the line filter was permanently exceeded. Note: The temperature monitoring is only available for an Active Interface Module.
• Page 627
  SINAMICS alarms 206301 <location>Infeed: Line supply overvoltage Message value: Line supply voltage: %1 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The filtered (steady-state) value of the rms line supply voltage Vrms is higher than the alarm threshold (p0281). Alarm condition: Vrms >…
• Page 628
  SINAMICS alarms 206311 <location>Infeed: Supply voltage (p0210) incorrect Message value: Line supply voltage: %1 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 (OFF1) Acknowledge: IMMEDIATELY (POWER ON) Cause: The line voltage nominal value indicated in p0210 is outside the nominal voltage range of the power unit. After pre-charging was completed, the current line supply voltage Vrms was calculated using the measured DC link voltage.
• Page 629
  SINAMICS alarms 206350 <location>Infeed: Measured line frequency too high Message value: Line frequency: %1 Drive object: AFE_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The actual line frequency f_line is higher than the parameterized alarm threshold (f_line > p0211 * p0284). The alarm can be output in two operating states: 1.
• Page 630
  SINAMICS alarms 206400 <location>Infeed: Line supply data identification selected/active Message value: Drive object: AFE_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The line supply data identification is selected and active. The line inductance and the DC link capacitance are measured at the next pulse enable. See also: p3410 (Infeed identification method) Remedy: No remedial action required.
• Page 631
  SINAMICS alarms 206502 <location>Infeed: Unable to achieve line synchronization in transformer magnetization Message value: Drive object: AFE_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: Line synchronization is not possible within the monitoring time (p5481[2]). Remedy: — check the setting of the threshold value (p5485) — check the setting of the maximum time (p5481[2]) — check the line supply quality.
• Page 632
  SINAMICS alarms 206700 <location>Infeed: Switch line contactor for load condition Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE (OFF2) Acknowledge: IMMEDIATELY Cause: For an ON command, the infeed line contactor should be switched under load. Remedy: — do not load the DC link if the infeed has not issued an operating signal (r0863.0 = 1). — after the infeed has been powered down, all power units connected to the DC link should be powered down.
• Page 633
  SINAMICS alarms 206849 <location>Infeed: Short-circuit operation active Message value: Drive object: AFE_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The current hysteresis controller sequence control has detected a short circuit (r5452, r5522). The absolute line supply voltage (r5444[0], r5512[0]) is below the short-circuit voltage limit (p5459[2], p5529[2]), and the current limitation is active (r5402.3=1, r5502.3=1).
• Page 634
  SINAMICS alarms 206860 <location>Infeed: Function module activation not possible Message value: Drive object: AFE_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: Function module activation is not possible. The power unit used does not have a «gating unit with current limitation control» (p0192.19). The affected function module is identified in fault code r0949 (the value of r0949 corresponds to the bit of parameter p0108).
• Page 635
  SINAMICS alarms 206904 <location>Braking Module internal is inhibited Message value: Drive object: BIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The internal Braking Module was inhibited via the binector input BI: p3680 = 1 signal. In the inhibited state, energy cannot be dissipated using the braking resistor. See also: p3680 (Braking Module internal inhibit) Remedy: Release the internal Braking Module (BI: p3680 = 0 signal).
• Page 636
  SINAMICS alarms 206907 <location>Braking Module internal overtemperature Message value: Drive object: BIC_SINUMERIK_828 Reaction: OFF2 (NONE, OFF1) Acknowledge: IMMEDIATELY Cause: The temperature sensor connected to the braking resistor signals an overtemperature. The Braking Module is still active. If the overtemperature persists for more than 60 s, fault F06908 is output, and the braking module is switched off.
• Page 637
  SINAMICS alarms 207011 <location>Drive: Motor overtemperature Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 (NONE, OFF1, OFF3, STOP1, STOP2) Acknowledge: IMMEDIATELY Cause: KTY: The motor temperature has exceeded the fault threshold (p0605) or the timer (p0606) after the alarm threshold was exceeded (p0604) has expired.
• Page 638
  SINAMICS alarms 207015 <location>Drive: Motor temperature sensor alarm Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: An error was detected when evaluating the temperature sensor set in p0600 and p0601. With the fault, the time in p0607 is started. If the fault is still present after this time has expired, then fault F07016 is output;…
• Page 639
  SINAMICS alarms 207080 <location>Drive: Incorrect control parameter Message value: Parameter: %1 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: IMMEDIATELY (POWER ON) Cause: The closed-loop control parameters have been parameterized incorrectly (e.g. p0356 = L_spread = 0). Fault value (r0949, interpret decimal): The fault value includes the parameter number involved.
• Page 640
  SINAMICS alarms 207083 <location>Macro: ACX file not found Message value: Parameter: %1 Drive object: All objects Reaction: NONE Acknowledge: IMMEDIATELY Cause: The ACX file (macro) to be executed was not able to be found in the appropriate directory. Fault value (r0949, interpret decimal): Parameter number with which the execution was started.
• Page 641
  SINAMICS alarms 207086 <location>Units changeover: Parameter limit violation due to reference value change Message value: Parameter: %1 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: IMMEDIATELY Cause: A reference parameter was changed in the system. This resulted in the fact that for the parameters involved, the selected value was not able to be written in the per unit representation (cause: e.g.
• Page 642
  SINAMICS alarms 207089 <location>Changing over units: Function module activation is blocked because the units have been changed over Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: An attempt was made to activate a function module. This is not permissible if the units have already been changed over.
• Page 643
  SINAMICS alarms 207200 <location>Drive: Master control ON/OFF1 command present Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The ON/OFF1 command is not 0, either via binector input p0840 (current CDS) or in control word bit 0 via the master control.
• Page 644
  — when exiting commissioning or at the end of the motor identification routine or the speed controller optimization, the drive unit is not automatically powered up again. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — increase the number of restart attempts (p1211). The actual number of starting attempts is displayed in r1214.
• Page 645
  SINAMICS alarms Remedy: Re fault value = 1, 2: — carry out an identification of the voltage emulation error in the drive converter (p1909.14 = 1, p1910 = 1). — set the parameter to compensate the voltage emulation error in the drive converter (p1952, p1953). Re fault value = 3: — enable the compensation of the voltage emulation error in the drive converter (p1780.8 = 1).
• Page 646
  SINAMICS alarms 207402 <location>Drive: DC link voltage minimum controller active Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The DC link voltage controller has been activated due to the lower switch-in threshold (r1248). A system deviation can occur between the setpoint and actual speed. A possible cause can be e.g.
• Page 647
  SINAMICS alarms 207410 <location>Drive: Current controller output limited Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 (NONE, OFF1) Acknowledge: IMMEDIATELY Cause: The condition «I_act = 0 and Uq_set_1 longer than 16 ms at its limit» is present and can be caused by the following: — motor not connected or motor contactor open.
• Page 648
  SINAMICS alarms 207412 <location>Drive: Commutation angle incorrect (motor model) Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (NONE, OFF2) Acknowledge: IMMEDIATELY Cause: An incorrect commutation angle was detected that can result in a positive coupling in the speed controller. Possible causes: — the motor encoder is incorrectly adjusted with respect to the magnet position.
• Page 649
  SINAMICS alarms 207414 <location>Drive: Encoder serial number changed Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (NONE, OFF2) Acknowledge: IMMEDIATELY Cause: The serial number of the motor encoder of a synchronous motor has changed. The change was only checked for encoders with serial number (e.g.
• Page 650
  SINAMICS alarms 207420 <location>Drive: Current setpoint filter natural frequency > Shannon frequency Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE (OFF1, OFF2, OFF3) Acknowledge: IMMEDIATELY (POWER ON) Cause: One of the filter natural frequencies is greater than the Shannon frequency. The Shannon frequency is calculated according to the following formula: 0.5 / p0115[0] Fault value (r0949, interpret hexadecimal): Bit 0: Filter 1 (p1658, p1660)
• Page 651
  SINAMICS alarms 207429 <location>Drive: DSC without encoder not possible Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 Acknowledge: IMMEDIATELY (POWER ON) Cause: The function DSC (Dynamic Servo Control) was activated although there is no encoder. See also: p1191 (DSC position controller gain KPC) Remedy: If there is no encoder and connector input p1191 (DSC position controller gain) is interconnected, then connector input p1191 must have a 0 signal.
• Page 652
  SINAMICS alarms 207433 <location>Drive: Closed-loop control with encoder is not possible as the encoder has not been unparked Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE (OFF1, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: The changeover to closed-loop control with encoder is not possible as the encoder has not been unparked. Remedy: — check whether the encoder firmware supports the «parking»…
• Page 653
  SINAMICS alarms 207501 <location>Drive: Motor Data Set MDS not configured Message value: Drive data set: %1 Drive object: All objects Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: Only for power units: The motor data set was not configured — this means that a data set number was not entered into the associated drive data set.
• Page 654
  SINAMICS alarms 207509 <location>Drive: Component number missing Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: A Drive Data Set (DDS) is assigned to a Motor Data Set (MDS) or Encoder Data Set (EDS) that does not have a com- ponent number.
• Page 655
  SINAMICS alarms First parameter: Index: First and second decimal place (99 for EDS, not assigned DDS) Parameter number: Third decimal place (1 for p0187, 2 for p0188, 3 for p0189, 4 for EDS not assigned DDS) Drive number: Fourth and fifth decimal place Second parameter: Index: Sixth and seventh decimal place (99 for EDS, not assigned DDS) Parameter number: Eighth decimal place (1 for p0187, 2 for p0188, 3 for p0189, 4 for EDS, not assigned DDS)
• Page 656
  SINAMICS alarms 207515 <location>Drive: Power unit and motor incorrectly connected Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: A power unit (via PDS) was assigned to a motor (via MDS) in a drive data set that is not connected in the target topol- ogy.
• Page 657
  SINAMICS alarms 207518 <location>Drive: Motor data set changeover incorrectly parameterized Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: IMMEDIATELY Cause: The system has identified that two motor data sets were incorrectly parameterized. Parameter r0313 (calculated from p0314, p0310, p0311), r0315 and p1982 may only have different values if the motor data sets are assigned different motors.
• Page 658
  SINAMICS alarms 207530 <location>Drive: Drive Data Set DDS not present Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The selected drive data set is not available (p0837 > p0180). The drive data set was not changed over. See also: p0180, p0820, p0821, p0822, p0823, p0824, r0837 Remedy: — select the existing drive data set.
• Page 659
  SINAMICS alarms 207551 <location>Drive encoder: No commutation angle information Message value: Fault cause: %1, drive data set: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 (IASC/DCBRAKE) Acknowledge: IMMEDIATELY (POWER ON) Cause: The commutation angle information is missing. This means that synchronous motors cannot be controlled (closed-loop control) Fault value (r0949, interpret decimal): yyyyxxxx dec: yyyy = fault cause, xxxx = drive data set…
• Page 660
  SINAMICS alarms 207553 <location>Drive encoder: Sensor Module configuration not supported Message value: Encoder data set: %1, first incorrect bit: %2, incorrect parameter: %3 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 (IASC/DCBRAKE, NONE, OFF1, OFF3, STOP1, STOP2) Acknowledge: IMMEDIATELY (POWER ON) Cause: The Sensor Module does not support the requested configuration.
• Page 661
  SINAMICS alarms Remedy: — use an absolute encoder. — if necessary, de-select the position tracking (p0411 for the measuring gear, p2720 for the load gear). — use a Control Unit with sufficient NVRAM. — Only activate position tracking of the load gear in the same encoder data set if the gear ratio (p2504, p2505), axis type (p2720.1) and tolerance window (p2722) are also the same.
• Page 662
  SINAMICS alarms 207562 <location>Drive, encoder: Position tracking, incremental encoder not possible Message value: Fault cause: %1, component number: %2, encoder data set: %3 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 (IASC/DCBRAKE, NONE, OFF1, OFF3, STOP1, STOP2) Acknowledge: IMMEDIATELY (POWER ON) Cause: The requested position tracking for incremental encoders is not supported.
• Page 663
  SINAMICS alarms 207567 <location>Drive: Encoder error in PROFIdrive encoder interface 3 Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: An encoder error was signaled for encoder 3 via the PROFIdrive encoder interface (G3_ZSW.15). Alarm value (r2124, interpret decimal): Error code from G3_XIST2, refer to the description regarding r0483.
• Page 664
  SINAMICS alarms 207576 <location>Drive: Encoderless operation due to a fault active Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: Encoderless operation is active due to a fault (r1407.13). The required response when an encoder fault occurs is parameterized in p0491. See also: p0491 (Motor encoder fault response ENCODER) Remedy: 207580…
• Page 665
  SINAMICS alarms 207801 <location>Drive: Motor overcurrent Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 (NONE, OFF1, OFF3) Acknowledge: IMMEDIATELY Cause: The permissible motor limit current was exceeded. — effective current limit set too low. — current controller not correctly set. — motor was braked with an excessively high stall torque correction factor.
• Page 666
  See also: r0206 (Rated power unit power), r0207 (Rated power unit current), r0208 (Rated power unit line supply volt- age), r0209 (Power unit, maximum current) Remedy: Replace the power unit or inform Siemens Customer Service. 207815 <location>Drive: Power unit has been changed…
• Page 667
  SINAMICS alarms 207815 <location>Drive: Power unit has been changed Message value: Parameter: %1 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: IMMEDIATELY Cause: The code number of the actual power unit does not match the saved number. The fault only occurs if the comparator in p9906 or p9908 is not at 2 (low) or 3 (minimum).
• Page 668
  SINAMICS alarms Remedy: — bring the infeed into an operational state. — check the interconnection of the binector input for the signal «infeed operation» (p0864). — increase the monitoring time (p0857). — wait until the infeed has completed the line supply identification routine. See also: p0857 (Power unit monitoring time), p0864 (Infeed operation) 207841 <location>Drive: Infeed operation withdrawn…
• Page 669
  SINAMICS alarms 207852 <location>External alarm 3 Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: The BICO signal for «external alarm 3» was triggered. The condition for this external alarm is fulfilled. See also: p2117 (External alarm 3) Remedy: Eliminate the causes of this alarm.
• Page 670
  SINAMICS alarms 207890 <location>Internal voltage protection / internal armature short-circuit with STO active Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: The internal armature short-circuit (p1231 = 4) is not possible as Safe Torque Off (STO) is enabled. The pulses cannot be enabled.
• Page 671
  SINAMICS alarms 207902 <location>Drive: Motor stalled Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 (IASC/DCBRAKE, NONE, OFF1, OFF3, STOP1, STOP2) Acknowledge: IMMEDIATELY Cause: For a vector drive the system has identified that the motor has stall for a time longer than is set in p2178. Fault value (r0949, interpret decimal): 1: Stall detection using r1408.11 (p1744 or p0492).
• Page 672
  SINAMICS alarms 207904 <location>External armature short-circuit: Contactor feedback signal «Closed» missing Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: When closing, the contactor feedback signal (p1235) did not issue the signal «Closed» (r1239.1 = 1) within the moni- toring time (p1236).
• Page 673
  SINAMICS alarms Remedy: Re cause 1: — an armature short-circuit / voltage protection is only permissible for permanent-magnetic synchronous motors. The highest position of the motor type in p0300 must either be 2 or 4. Re cause 101: — the contactor for the external armature short-circuit configuration should be controlled using output signal r1239.0. The signal can, e.g.
• Page 674
  SINAMICS alarms 207908 <location>Internal armature short-circuit active Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The Motor Module signals that the motor is short-circuited through the power semiconductors (r1239.5 = 1). The pulses cannot be enabled. The internal armature short-circuit is selected (p1231 = 4): Remedy: For synchronous motors, the armature short-circuit braking is activated if a 1 signal is present via binector input p1230.
• Page 675
  SINAMICS alarms 207913 <location>Excitation current outside the tolerance range Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: The difference between the excitation current actual value and setpoint has exceeded the tolerance: abs(r1641 — r1626) > p3201 + p3202 The cause of this fault is again reset for abs(r1641 — r1626) <…
• Page 676
  SINAMICS alarms 207927 <location>DC brake active Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The motor is braked with a DC current, the DC current brake is active. An alarm with response DCBRAKE is active. The motor is braked with the braking current set in p1232 for the duration set in in p1233.
• Page 677
  SINAMICS alarms 40: Fault in «brake closed» state. 50: Fault in the brake control circuit of the Control Unit or communication fault between Control Unit and Motor Module (brake control diagnostics). Note: The following causes may apply to fault values: — motor cable is not shielded correctly.
• Page 678
  SINAMICS alarms 207950 <location>Drive: Incorrect motor parameter Message value: Parameter: %1 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: IMMEDIATELY Cause: — the motor parameters were incorrectly entered while commissioning (e.g. p0300 = 0, no motor) — The braking resistor (p6811) has still not been parameterized — commissioning cannot be completed. Fault value (r0949, interpret decimal): The parameter number involved.
• Page 679
  SINAMICS alarms 207960 <location>Drive: Incorrect friction characteristic Message value: Parameter: %1 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The friction characteristic is incorrect. Alarm value (r2124, interpret decimal): 1538: The friction torque is greater than the maximum from the upper effective torque limit (p1538) and zero. This is the rea- son that the output of the friction characteristic (r3841) is limited to this value.
• Page 680
  SINAMICS alarms 207963 <location>Drive: Friction characteristic record interrupted Message value: Parameter: %1 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 Acknowledge: IMMEDIATELY Cause: The conditions to record the friction characteristic are not fulfilled. Fault value (r0949, interpret decimal): 0046: Missing enable signals (r0046). 1082: The highest speed value to be approached (p3829) is greater than the maximum speed (p1082).
• Page 681
  SINAMICS alarms 207965 <location>Drive: Save required Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The angular commutation offset (p0431) was re-defined and has still not been saved. In order to permanently accept the new value, it must be saved in a non-volatile fashion (p0971, p0977). See also: p0431 (Angular commutation offset), p1990 (Encoder adjustment, determine angular commutation offset) Remedy: None necessary.
• Page 682
  SINAMICS alarms Remedy: None necessary. The alarm automatically disappears after the rotating measurement has been successfully completed or for the setting p1960 = 0. If a POWER ON or a warm restart is performed with motor data identification selected, the motor data identification request will be lost.
• Page 683
  SINAMICS alarms Remedy: Re fault value = 0: — check whether the motor is correctly connected. Observe configuration (star-delta). Re fault value = 1 … 40: — check whether motor data have been correctly entered in p0300, p0304 … p0311. — is there an appropriate relationship between the motor power rating and that of the Motor Module? The ratio of the Motor Module to the rated motor current should not be less than 0.5 and not be greater than 4.
• Page 684
  SINAMICS alarms Re fault value = 173: Re fault value = 180: — increase max. speed (p1082). — reduce p1755. — suppress meas. (p1909, p1959). Re fault value = 190: — set speed setpoint to zero. Re fault value = 191: — do not start motor data ident.
• Page 685
  SINAMICS alarms 207993 <location>Drive: Incorrect direction of rotation of the field or encoder actual value inversion Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 (NONE) Acknowledge: IMMEDIATELY Cause: Either the direction of the rotating field or the encoder actual value has an incorrect sign. The motor data identification automatically changed the actual value inversion (p0410) in order to correct the control sense.
• Page 686
  SINAMICS alarms Remedy: Re fault value = 1: — check the motor connection and DC link voltage. — for the following parameters, set practical values that are not zero (p0325, p0329). Re fault value = 1, 2: — in the case of a large computing time load (e.g., 6 drives with Safety Integrated), set the computing dead time of the current controller to late transfers (p0117 = 3).
• Page 687
  SINAMICS alarms 207996 <location>Drive: Pole position identification routine not carried out Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (OFF2) Acknowledge: IMMEDIATELY Cause: In operation, the operating mode that requires a pole position identification was changed over, which is not possible in this state: — the drive was changed over, flying, from encoderless operation to operation with encoder without having previously carried out a pole position identification for the encoder.
• Page 688
  SINAMICS alarms 208000 <location>TB: +/-15 V power supply faulted Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, CU_I_COMBI, CU_I_SINUMERIK_828, CU_LINK, CU_NX_828, HUB, SIC_COMBI, SIC_SINUMERIK_828, TM120, TM54F_MA, TM54F_SL Reaction: NONE (OFF1, OFF2) Acknowledge: IMMEDIATELY (POWER ON) Cause: Terminal Board 30 detects an incorrect internal power supply voltage. Fault value (r0949, interpret decimal): 0: Error when testing the monitoring circuit.
• Page 689
  SINAMICS alarms Cause: The power unit has detected an overcurrent condition. — closed-loop control is incorrectly parameterized. — motor has a short-circuit or fault to ground (frame). — V/f operation: Up ramp set too low. — V/f operation: Rated motor current is significantly greater than that of the Motor Module. — infeed: High discharge and post-charging currents for voltage dip.
• Page 690
  SINAMICS alarms Remedy: — increase the ramp-down time — activate the DC link voltage controller — use a brake resistor or Active Line Module — increase the current limit of the infeed or use a larger module (for the Active Line Module) — check the device supply voltage — check and correct the phase assignment at the VSM and at the power unit — check the line supply phases.
• Page 691
  SINAMICS alarms 230005 <location>Power unit: Overload I2t Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: The power unit was overloaded (r0036 = 100 %). — the permissible rated power unit current was exceeded for an inadmissibly long time. — the permissible load duty cycle was not maintained.
• Page 692
  SINAMICS alarms Remedy: — check the electrical cabinet design and cable routing for EMC compliance — for projects with the VECTOR drive object, check whether p0117 = 6 has been set on the Control Unit. — increase the fault threshold (p7789). See also: p0117 (Current controller computing dead time mode) 230010 <location>Power unit: Sign-of-life error cyclic data…
• Page 693
  SINAMICS alarms 230013 <location>Power unit: Temperature sensor heat sink short-circuit Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF1 (OFF2) Acknowledge: IMMEDIATELY Cause: The heat sink temperature sensor in the power unit is short-circuited. Fault value (r0949, interpret hexadecimal): Bit 0: Module slot (electronics slot) Bit 1: Air intake Bit 2: Inverter 1…
• Page 694
  SINAMICS alarms Cause: The hardware current limitation in the relevant phase (see A30031, A30032, A30033) has responded too often. The number of times the limit has been exceeded depends on the design and type of power unit. For infeed units, the following applies: — closed-loop control is incorrectly parameterized.
• Page 695
  SINAMICS alarms 230021 <location>Power unit: Ground fault Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: Power unit has detected a ground fault. — ground fault in the power cables. — winding fault or ground fault at the motor. — CT defective.
• Page 696
  SINAMICS alarms 230023 <location>Power unit: Overtemperature thermal model alarm Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The temperature difference between the heat sink and chip has exceeded the permissible limit value. — the permissible load duty cycle was not maintained. — insufficient cooling, fan failure.
• Page 697
  SINAMICS alarms Cause: Chip temperature of the semiconductor has exceeded the permissible limit value. — the permissible load duty cycle was not maintained. — insufficient cooling, fan failure. — overload. — ambient temperature too high. — pulse frequency too high. Fault value (r0949): Temperature difference between the heat sink and chip [1 Bit = 0.01 °C].
• Page 698
  SINAMICS alarms Status, power unit (upper 16 bit, hexadecimal number): 0: Fault status (wait for OFF and fault acknowledgement) 1: Restart inhibit (wait for OFF) 2: Overvoltage condition detected -> change into the fault state 3: Undervoltage condition detected -> change into the fault state 4: Wait for bypass contactor to open ->…
• Page 699
  SINAMICS alarms 230032 <location>Power unit: Hardware current limiting, phase V Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: Hardware current limit for phase V responded. The pulsing in this phase is inhibited for one pulse period. — closed-loop control is incorrectly parameterized.
• Page 700
  SINAMICS alarms Cause: The alarm threshold for internal overtemperature has been reached. If the temperature inside the unit continues to increase, fault F30036 may be triggered. — ambient temperature might be too high. — insufficient cooling, fan failure. Fault value (r0949, interpret binary): Bit 0 = 1: Control electronics range.
• Page 701
  SINAMICS alarms 230037 <location>Power unit: Rectifier overtemperature Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: The temperature in the rectifier of the power unit has exceeded the permissible temperature limit. — insufficient cooling, fan failure. — overload.
• Page 702
  SINAMICS alarms Cause: Failure of the 24 V power supply for the power unit. — The undervoltage threshold was undershot for longer than 3 ms. Fault value (r0949, interpret decimal): 24 V voltage [1 bit = 0.1 V]. Remedy: — check the 24 V DC voltage supply to power unit. — carry out a POWER ON (power off/on) for the component.
• Page 703
  SINAMICS alarms 230044 <location>Power unit: Overvoltage 24 V alarm Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The following applies for CU31x: 24 V power supply fault for the power unit. — the 32.0 V threshold was exceeded. Fault value (r0949): 24 V voltage [1 bit = 0.1 V].
• Page 704
  SINAMICS alarms Remedy: 230048 <location>Power unit: External fan faulty Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The feedback signal from the external fan indicates a fault. — fan faulty, blocked. — feedback signal inaccurate. Remedy: — check the external fan and replace if necessary.
• Page 705
  0: The EEPROM data read in from the power unit module is inconsistent. 1: EEPROM data is not compatible to the firmware of the power unit application. Additional values: Only for internal Siemens troubleshooting. Remedy: Re fault value = 0: Replace the power unit module or update the EEPROM data.
• Page 706
  SINAMICS alarms 230061 <location>Bypass contactor monitoring Message value: Fault cause: %1 bin Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 (NONE, OFF1) Acknowledge: IMMEDIATELY (POWER ON) Cause: At the end of the monitoring time (p0255[1]), the actual state of the bypass contactor does not match the desired state. Fault value (r0949, interpret bitwise binary): Bit 0: Monitoring time exceeded.
• Page 707
  SINAMICS alarms 230071 <location>No new actual values received from the power unit module Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: The number of actual value telegrams from the power unit module that have failed has exceeded the permissible num- ber.
• Page 708
  SINAMICS alarms 230080 <location>Power unit: Current increasing too quickly Message value: Fault cause: %1 bin Drive object: All objects Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: The power unit has detected an excessive rate of rise in the overvoltage range. — closed-loop control is incorrectly parameterized. — motor has a short-circuit or fault to ground (frame).
• Page 709
  SINAMICS alarms 230081 <location>Power unit: Switching operations too frequent Message value: Fault cause: %1 bin Drive object: All objects Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: The power unit has executed too many switching operations for current limitation. — closed-loop control is incorrectly parameterized. — motor has a short-circuit or fault to ground (frame).
• Page 710
  SINAMICS alarms 230502 <location>Power unit: DC link voltage, overvoltage Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The power unit has detected overvoltage in the DC link on a pulse inhibit. — device connection voltage too high. — line reactor incorrectly dimensioned.
• Page 711
  SINAMICS alarms 230611 <location>SI MM: Defect in a monitoring channel Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: Servo: NONE (OFF1, OFF2, OFF3) Infeed: NONE (OFF1, OFF2) Acknowledge: IMMEDIATELY (POWER ON) Cause: The drive-based «Safety Integrated» function in the Motor Module (MM) has detected a fault in the data cross-check between the Control Unit (CU) and MM and initiated a STOP F.
• Page 712
  SINAMICS alarms Re fault value = 2000, 2001, 2002: — check the tolerance time SGE changeover and if required, increase the value (p9650/p9850, p9652/p9852). — check the wiring of the safety-relevant inputs (SGE) (contact problems). — check the cause of the STO selection in r9772. When the SMM functions are active (p9501 = 1), STO can also be selected using these functions.
• Page 713
  — there is either a DRIVE-CLiQ communication error or communication has failed. — a time slice overflow of the safety software has occurred. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: — select Safe Torque Off and de-select again.
• Page 714
  Note: This fault results in a STOP A that can be acknowledged. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: For the higher-level control, the following applies: — check the PROFIsafe address in the higher-level control and Motor Modules and if required, align.
• Page 715
  — Carry out an acceptance test and generate an acceptance report. The procedure when carrying out an acceptance test as well as an example of the acceptance report are provided in the following literature: SINAMICS S120 Function Manual Safety Integrated Alarms Diagnostics Manual, 07/2010, 6FC5398-8BP40-0BA0…
• Page 716
  The procedure when carrying out an acceptance test as well as an example of the acceptance report are provided in the following literature: SINAMICS S120 Function Manual Safety Integrated Re fault value = 9999: — carry out diagnostics for the other safety-related fault that is present.
• Page 717
  Note: This fault results in a STOP A that cannot be acknowledged. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — carry out a POWER ON (power off/on) for all components. — upgrade the Motor Module software.
• Page 718
  Acknowledge: POWER ON Cause: A module-internal communication error has occurred. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — carry out a POWER ON (power off/on). — upgrade firmware to later version. — contact the Hotline. Alarms…
• Page 719
  Acknowledge: POWER ON Cause: An error has occurred during booting. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — carry out a POWER ON (power off/on). — upgrade firmware to later version. — contact the Hotline. 230665 <location>SI MM: System is defective…
• Page 720
  SINAMICS alarms 230680 <location>SI Motion MM: Checksum error safety monitoring functions Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF2 Acknowledge: IMMEDIATELY (POWER ON) Cause: The actual checksum calculated by the Motor Module and entered in r9398 over the safety-relevant parameters does not match the reference checksum saved in p9399 at the last machine acceptance.
• Page 721
  SINAMICS alarms Remedy: — de-select the monitoring function involved (p9301, p9301, p9303, p9601, p9801). — Upgrade the Motor Module firmware. See also: p9301 (SI Motion enable safety functions (Motor Module)), p9501 (SI Motion enable safety functions (Control Unit)), p9503 (SI Motion SCA (SN) enable (Control Unit)), p9601 (SI enable, functions integrated in the drive (Control Unit)), p9801 (SI enable, functions integrated in the drive (Motor Module)) 230683 <location>SI Motion MM: SOS/SLS enable missing…
• Page 722
  SINAMICS alarms Remedy: — Either select the «actual value synchronization» function or parameterize a 2-encoder system. — Either de-select the function «actual value synchronization» or the monitoring functions with absolute reference (SCA/ SLP) and carry out a POWER ON. Note: SCA: Safe Cam / SN: Safe software cam SI: Safety Integrated SLP: Safely-Limited Position / SE: Safe software limit switches…
• Page 723
  SINAMICS alarms Remedy: — remove the cause to the fault on the Control Unit. — check the value in p9357, if required, increase the value. — check the shutdown path of the Control Unit (check DRIVE-CLiQ communication). — carry out a diagnostics routine for message C30706. — carry out a diagnostics routine for message C30714.
• Page 724
  SINAMICS alarms 230707 <location>SI Motion MM: Tolerance for safe operating stop exceeded Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: IMMEDIATELY (POWER ON) Cause: The actual position has distanced itself further from the target position than the standstill tolerance. The drive is shut down by the message C30701 «SI Motion MM: STOP B initiated».
• Page 725
  SINAMICS alarms 230711 <location>SI MM MM: Defect in a monitoring channel Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: IMMEDIATELY (POWER ON) Cause: When cross-checking and comparing the two monitoring channels, the drive detected a difference between the input data or results of the monitoring functions and initiated a STOP F.
• Page 726
  SINAMICS alarms Re message value = 1040: — de-select encoderless monitoring functions, select and de-select STO. — if monitoring function is active, issue SLS pulse enable within 5 s of de-selecting STO. Re other message values: — The significance of the individual message values is described in safety message C01711 of the Control Unit. Note: This message can only be acknowledged via the Terminal Module 54F (TM54F) or PROFIsafe.
• Page 727
  SINAMICS alarms 230798 <location>SI Motion MM: Test stop running Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: IMMEDIATELY (POWER ON) Cause: The test stop is active. Remedy: None necessary. The message is withdrawn when the test stop is finished. Note: SI: Safety Integrated 230799…
• Page 728
  SINAMICS alarms Remedy: — check the electrical cabinet design and cable routing for EMC compliance — remove DRIVE-CLiQ components that are not required. — de-select functions that are not required. — if required, increase the sampling times (p0112, p0115). — replace the component involved. 230802 <location>Power unit: Time slice overflow Message value:…
• Page 729
  SINAMICS alarms Cause: For 3P gating unit: The last switching status word in the setpoint telegram is identified by the end ID. Such an end ID was not found. Remedy: — carry out a POWER ON (power off/on) for all components. — upgrade firmware to later version.
• Page 730
  SINAMICS alarms 230835 <location>Power unit DRIVE-CLiQ: Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. The nodes do not send and receive in synchronism.
• Page 731
  POWER ON Cause: An internal software error has occurred in the power unit. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: — replace power unit. — if required, upgrade the firmware in the power unit. — contact the Hotline.
• Page 732
  SINAMICS alarms 230853 <location>Power unit: Sign-of-life error cyclic data Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The power unit has detected that the cyclic setpoint telegrams of the Control Unit have not been updated on time. At least two sign-of-life errors have occurred within the window set in p7788.
• Page 733
  SINAMICS alarms 230885 <location>CU DRIVE-CLiQ (CU): Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, CU_LINK, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM120 Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the power unit to the Control Unit involved. The nodes do not send and receive in synchronism.
• Page 734
  SINAMICS alarms Cause: Fault detected on the DRIVE-CLiQ component (power unit) involved. Faulty hardware cannot be excluded. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 20 hex: Error in the telegram header. xx = 23 hex: Receive error: The telegram buffer memory contains an error.
• Page 735
  SINAMICS alarms 230899 <location>Power unit: Unknown fault Message value: New message: %1 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: Servo: NONE (IASC/DCBRAKE, OFF1, OFF2, OFF3, STOP1, STOP2) Infeed: NONE (OFF1, OFF2) Acknowledge: IMMEDIATELY (POWER ON) Cause: A fault occurred on the power unit that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit.
• Page 736
  SINAMICS alarms 230920 <location>Power unit: Temperature sensor fault Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm, PT100: R > 375 Ohm). 2: Measured resistance too low (PTC: R <…
• Page 737
  SINAMICS alarms 231101 <location>Encoder 1: Zero marked failed Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE, OFF1, OFF2, OFF3, STOP1, STOP2) Acknowledge: PULSE INHIBIT Cause: The 1.5 x parameterized zero mark distance was exceeded. The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder). Fault value (r0949, interpret decimal): Number of increments after POWER ON or since the last zero mark that was detected (4 increments = 1 encoder pulse).
• Page 738
  SINAMICS alarms 231110 <location>Encoder 1: Serial communications error Message value: Fault cause: %1 bin Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: PULSE INHIBIT Cause: Serial communication protocol transfer error between the encoder and evaluation module. Fault value (r0949, interpret binary): Bit 0: Alarm bit in the position protocol.
• Page 739
  SINAMICS alarms 231111 <location>Encoder 1: Absolute encoder EnDat, internal fault/error Message value: Fault cause: %1 bin Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: PULSE INHIBIT Cause: The EnDat encoder fault word supplies fault bits that have been set. Fault value (r0949, interpret binary): Bit 0: Lighting system failed.
• Page 740
  SINAMICS alarms 231115 <location>Encoder 1: Amplitude error track A or B (A^2 + B^2) Message value: A track: %1, B-track: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: PULSE INHIBIT Cause: The amplitude (root of A^2 + B^2) for encoder 1 exceeds the permissible tolerance. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex: yyyy = Signal level, track B (16 bits with sign).
• Page 741
  For a square-wave encoder (bipolar, double ended) the A* and B* and R* signals are not inverted with respect to sig- nals A and B and R. Fault value (r0949, interpret binary): Bits 0-15: Only for internal Siemens troubleshooting. Bit 16: Error track A. Bit 17: Error track B.
• Page 742
  SINAMICS alarms 231120 <location>Encoder 1: Power supply voltage fault Message value: Fault cause: %1 bin Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: PULSE INHIBIT Cause: Encoder 1 power supply voltage fault. Fault value (r0949, interpret binary): Bit 0: Undervoltage condition on the sense line. Bit 1: Overcurrent condition for the encoder power supply.
• Page 743
  SINAMICS alarms 231123 <location>Encoder 1: Signal level A/B unipolar outside tolerance Message value: Fault cause: %1 bin Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: PULSE INHIBIT Cause: The unipolar level (AP/AN or BP/BN) for encoder 1 is outside the permissible tolerance. Fault value (r0949, interpret binary): Bit 0 = 1: Either AP or AN outside the tolerance.
• Page 744
  SINAMICS alarms 231126 <location>Encoder 1: Amplitude AB too high Message value: Amplitude: %1, Angle: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: PULSE INHIBIT Cause: The amplitude (root of A^2 + B^2 or |A| + |B|) for encoder 1 exceeds the permissible tolerance. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex: yyyy = Angle…
• Page 745
  SINAMICS alarms 231130 <location>Encoder 1: Zero mark and position error from the coarse synchronization Message value: Angular deviation, electrical: %1, angle, mechanical: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE, OFF1, OFF2, OFF3, STOP1, STOP2) Acknowledge: PULSE INHIBIT Cause: After initializing the pole position using track C/D, Hall signals or pole position identification routine, the zero mark was detected outside the permissible range.
• Page 746
  SINAMICS alarms 231135 <location>Encoder 1: Fault when determining the position Message value: Fault cause: %1 bin Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: PULSE INHIBIT Cause: The DRIVE-CLiQ encoder supplies status information via bits in an internal status/fault word. Some of these bits cause this fault to be triggered.
• Page 747
  Acknowledge: PULSE INHIBIT Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Fault value (r0949, interpret binary): Only for internal SIEMENS use. Remedy: Replace encoder 231138 <location>Encoder 1: Internal error when determining multiturn information Message value:…
• Page 748
  SINAMICS alarms 231151 <location>Encoder 1: Encoder speed for initialization AB too high Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE, OFF1, OFF2, OFF3, STOP1, STOP2) Acknowledge: PULSE INHIBIT Cause: The encoder speed is too high during while initializing the sensor. Remedy: Reduce the speed of the encoder accordingly during initialization.
• Page 749
  SINAMICS alarms 231400 <location>Encoder 1: Alarm threshold zero mark distance error Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs. This means that if a zero mark is missing, depending on the pair generation, this cannot result in a fault and also has no effect in the system.
• Page 750
  SINAMICS alarms 231407 <location>Encoder 1: Function limit reached Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The encoder has reached one of its function limits. A service is recommended. Alarm value (r2124, interpret decimal): 1 : Incremental signals 3 : Absolute track 4 : Code connection Remedy:…
• Page 751
  SINAMICS alarms 231412 <location>Encoder 1: Error bit set in the serial protocol Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The encoder sends a set error bit via the serial protocol. Alarm value (r2124, interpret binary): Bit 0: Fault bit in the position protocol. Bit 1: Alarm bit in the position protocol.
• Page 752
  The change to the averaged speed actual value — if applicable — is monitored in the current controller sampling time. Alarm value (r2124, interpret decimal): Only for internal Siemens troubleshooting. See also: p0492 (Square-wave encoder, maximum speed difference per sampling cycle) Remedy: — check the tachometer feeder cable for interruptions.
• Page 753
  SINAMICS alarms 231419 <location>Encoder 1: Track A or B outside the tolerance range Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The amplitude, phase or offset correction for track A or B is at the limit. Amplitude error correction: Amplitude B / Amplitude A = 0.78 … 1.27 Phase: <84 degrees or >96 degrees SMC20: Offset correction: +/-140 mV SMC10: Offset correction: +/-650 mV…
• Page 754
  SINAMICS alarms Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. This alarm is triggered with active square-wave encoder PPR correction and re-parameterized fault 31131 if the accu- mulator contains larger values than p4683 or p4684. The zero mark distance for zero mark monitoring is set in p0425 (rotary encoder).
• Page 755
  SINAMICS alarms 231432 <location>Encoder 1: Rotor position adaptation corrects deviation Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: For track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected. Alarm value (r2124, interpret decimal): Last measured deviation of zero mark in increments (4 increments = 1 encoder pulse).
• Page 756
  SINAMICS alarms 231460 <location>Encoder 1: Analog sensor channel A failed Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The input voltage of the analog sensor is outside the permissible limits. Alarm value (r2124, interpret decimal): 1: Input voltage outside detectable measuring range. 2: Input voltage outside measuring range set in p4673.
• Page 757
  SINAMICS alarms 231470 <location>Encoder 1: Soiling detected Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: In the case of the alternative encoder system interface on the Sensor Module Cabinet 30 (SMC30), encoder soiling is signaled via a 0 signal at terminal X521.7. Remedy: — check the plug connections — replace the encoder or encoder cable…
• Page 758
  SINAMICS alarms 231502 <location>Encoder 1: Encoder with measuring gear, without valid signals Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: The encoder with measuring gear no longer provides any valid signals. Remedy: It must be ensured that all of the encoders, with mounted measuring gear, provide valid actual values in operation. 231503 <location>Encoder 1: Position tracking cannot be reset Message value:…
• Page 759
  SINAMICS alarms 231801 <location>Encoder 1 DRIVE-CLiQ: Sign-of-life missing Message value: Component number: %1, fault cause: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 0A hex:…
• Page 760
  SINAMICS alarms 231805 <location>Encoder 1: EPROM checksum error Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: IMMEDIATELY Cause: Internal parameter data is corrupted. Fault value (r0949, interpret hexadecimal): 01: EEPROM access error. 02: Too many blocks in the EEPROM. See also: p0491 (Motor encoder fault response ENCODER) Remedy: Replace the module.
• Page 761
  SINAMICS alarms 231811 <location>Encoder 1: Encoder serial number changed Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The serial number of the motor encoder of a synchronous motor has changed. The change was only checked for encoders with serial number (e.g. EnDat encoders) and build-in motors (e.g. p0300 = 401) or third-party motors (p0300 = 2).
• Page 762
  SINAMICS alarms 231813 <location>Encoder 1: Hardware logic unit failed Message value: Fault cause: %1 bin Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: PULSE INHIBIT Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Fault value (r0949, interpret binary): Bit 0: ALU watchdog has responded.
• Page 763
  SINAMICS alarms 231835 <location>Encoder 1 DRIVE-CLiQ: Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. The nodes do not send and receive in synchronism.
• Page 764
  SINAMICS alarms Remedy: — check the DRIVE-CLiQ wiring (interrupted cable, contacts, …). — check the electrical cabinet design and cable routing for EMC compliance — if required, use another DRIVE-CLiQ socket (p9904). — replace the component involved. 231845 <location>Encoder 1 DRIVE-CLiQ: Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object:…
• Page 765
  SINAMICS alarms 231851 <location>Encoder 1 DRIVE-CLiQ (CU): Sign-of-life missing Message value: Component number: %1, fault cause: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit.
• Page 766
  SINAMICS alarms 231885 <location>Encoder 1 DRIVE-CLiQ (CU): Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit. The nodes do not send and receive in synchronism.
• Page 767
  SINAMICS alarms xx = 42 hex: Send error: The telegram buffer memory contains an error. xx = 43 hex: Send error: The telegram buffer memory contains an error. xx = 60 hex: Response received too late during runtime measurement. xx = 61 hex: Time taken to exchange characteristic data too long.
• Page 768
  Acknowledge: NONE Cause: Error when operating the internal SPI bus. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — replace the Sensor Module. — if required, upgrade the firmware in the Sensor Module. — contact the Hotline.
• Page 769
  SINAMICS alarms 231905 <location>Encoder 1: Parameterization error Message value: Parameter: %1, supplementary information: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE, OFF1, OFF2, OFF3, STOP1, STOP2) Acknowledge: IMMEDIATELY Cause: A parameter of encoder 1 was detected as being incorrect. It is possible that the parameterized encoder type does not match the connected encoder.
• Page 770
  1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm). 2: Measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm). Additional values: Only for internal Siemens troubleshooting. Low word high byte: Channel number. See also: p0491 (Motor encoder fault response ENCODER) Remedy: — check that the encoder cable is the correct type and is correctly connected.
• Page 771
  SINAMICS alarms 232100 <location>Encoder 2: Zero mark distance error Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3, STOP1, STOP2) Acknowledge: PULSE INHIBIT Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs.
• Page 772
  SINAMICS alarms Cause: The amplitude of the reference track signal (track R) does not lie within the tolerance bandwidth for encoder 2. The fault can be initiated when the unipolar voltage level is exceeded (RP/RN) or if the differential amplitude is under- shot.
• Page 773
  SINAMICS alarms Re fault value, bit 6 = 1: — Update Sensor Module firmware. Re fault value, bit 8 = 1: — Check parameterization (p0429.2). Re fault value, bit 9 = 1: — EMC / connect the cable shield, replace the encoder or encoder cable, replace the Sensor Module. Re fault value, bit 10 = 1: — Check parameterization (p0429.2, p0449).
• Page 774
  SINAMICS alarms 232112 <location>Encoder 2: Error bit set in the serial protocol Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: PULSE INHIBIT Cause: The encoder sends a set error bit via the serial protocol. Fault value (r0949, interpret binary): Bit 0: Fault bit in the position protocol.
• Page 775
  For a square-wave encoder (bipolar, double ended) the A* and B* and R* signals are not inverted with respect to sig- nals A and B and R. Fault value (r0949, interpret binary): Bits 0-15: Only for internal Siemens troubleshooting. Bit 16: Error track A. Bit 17: Error track B.
• Page 776
  The change to the averaged speed actual value — if applicable — is monitored in the current controller sampling time. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. See also: p0492 (Square-wave encoder, maximum speed difference per sampling cycle) Remedy: — check the tachometer feeder cable for interruptions.
• Page 777
  SINAMICS alarms 232122 <location>Encoder 2: Internal power supply voltage faulty Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER Acknowledge: IMMEDIATELY Cause: Fault in internal reference voltage of ASICs for encoder 2. Fault value (r0949, interpret decimal): 1: Reference voltage error. 2: Internal undervoltage.
• Page 778
  SINAMICS alarms Remedy: — check that the encoder cables and shielding are routed in compliance with EMC. — replace the encoder or encoder cable 232126 <location>Encoder 2: Amplitude AB too high Message value: Amplitude: %1, Angle: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3, STOP1, STOP2) Acknowledge:…
• Page 779
  SINAMICS alarms 232130 <location>Encoder 2: Zero mark and position error from the coarse synchronization Message value: Angular deviation, electrical: %1, angle, mechanical: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3, STOP1, STOP2) Acknowledge: PULSE INHIBIT Cause: After initializing the pole position using track C/D, Hall signals or pole position identification routine, the zero mark was detected outside the permissible range.
• Page 780
  SINAMICS alarms 232135 <location>Encoder 2: Fault when determining the position Message value: Fault cause: %1 bin Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: PULSE INHIBIT Cause: The DRIVE-CLiQ encoder supplies status information via bits in an internal status/fault word. Some of these bits cause this fault to be triggered.
• Page 781
  Acknowledge: PULSE INHIBIT Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Fault value (r0949, interpret binary): Only for internal SIEMENS use. Remedy: Replace encoder 232138 <location>Encoder 2: Internal error when determining multiturn information Message value:…
• Page 782
  SINAMICS alarms 232151 <location>Encoder 2: Encoder speed for initialization AB too high Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE, OFF1, OFF2, OFF3, STOP1, STOP2) Acknowledge: PULSE INHIBIT Cause: The encoder speed is too high during while initializing the sensor. Remedy: Reduce the speed of the encoder accordingly during initialization.
• Page 783
  SINAMICS alarms 232400 <location>Encoder 2: Alarm threshold zero mark distance error Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs. This means that if a zero mark is missing, depending on the pair generation, this cannot result in a fault and also has no effect in the system.
• Page 784
  SINAMICS alarms 232407 <location>Encoder 2: Function limit reached Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The encoder has reached one of its function limits. A service is recommended. Alarm value (r2124, interpret decimal): 1 : Incremental signals 3 : Absolute track 4 : Code connection Remedy:…
• Page 785
  SINAMICS alarms 232412 <location>Encoder 2: Error bit set in the serial protocol Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The encoder sends a set error bit via the serial protocol. Alarm value (r2124, interpret binary): Bit 0: Fault bit in the position protocol. Bit 1: Alarm bit in the position protocol.
• Page 786
  The change to the averaged speed actual value — if applicable — is monitored in the current controller sampling time. Alarm value (r2124, interpret decimal): Only for internal Siemens troubleshooting. See also: p0492 (Square-wave encoder, maximum speed difference per sampling cycle) Remedy: — check the tachometer feeder cable for interruptions.
• Page 787
  SINAMICS alarms 232419 <location>Encoder 2: Track A or B outside the tolerance range Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The amplitude, phase or offset correction for track A or B is at the limit. Amplitude error correction: Amplitude B / Amplitude A = 0.78 … 1.27 Phase: <84 degrees or >96 degrees SMC20: Offset correction: +/-140 mV SMC10: Offset correction: +/-650 mV…
• Page 788
  SINAMICS alarms 232422 <location>Encoder 2: Pulses per revolution square-wave encoder outside tolerance bandwidth Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. This alarm is triggered with active square-wave encoder PPR correction and re-parameterized fault 31131 if the accu- mulator contains larger values than p4683 or p4684.
• Page 789
  SINAMICS alarms 232431 <location>Encoder 2: Deviation, position incremental/absolute too large Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: When the zero pulse is passed, a deviation in the incremental position was detected. For equidistant zero marks, the following applies: — The first zero mark passed supplies the reference point for all subsequent checks.
• Page 790
  SINAMICS alarms 232443 <location>Encoder 2: Unipolar CD signal level outside specification Message value: Fault cause: %1 bin Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The unipolar level (CP/CN or DP/DN) for encoder 2 is outside the permissible tolerance. Alarm value (r2124, interpret binary): Bit 0 = 1: Either CP or CN outside the tolerance.
• Page 791
  SINAMICS alarms Remedy: Re alarm value = 1: — check the output voltage of the analog sensor. Re alarm value = 2: — check the voltage setting for each encoder period (p4675). Re alarm value = 3: — check the range limit setting and increase it if necessary (p4676). 232462 <location>Encoder 2: Analog sensor, no channel active Message value:…
• Page 792
  SINAMICS alarms 232501 <location>Encoder 2: Position tracking encoder position outside tolerance window Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (NONE, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: When powered down, the drive/encoder was moved through a distance greater than was parameterized in the toler- ance window.
• Page 793
  SINAMICS alarms 232700 <location>Encoder 2: Effectivity test does not supply the expected value Message value: Fault cause: %1 bin Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Fault value (r0949, interpret binary): Bit x = 1: Effectivity test x unsuccessful.
• Page 794
  SINAMICS alarms 232804 <location>Encoder 2: Checksum error Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: A checksum error has occurred when reading-out the program memory on the Sensor Module. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex yyyy: Memory area involved.
• Page 795
  SINAMICS alarms Bit 15: The standard deviation of the calculated mid-voltages is too great (> 0.3 V) Bit 16: Internal fault — fault reading a register (CAFE) Bit 17: Internal fault — fault writing a register (CAFE) Bit 18: Internal fault: No mid-voltage matching available Bit 19: Internal error — ADC access error.
• Page 796
  SINAMICS alarms 232813 <location>Encoder 2: Hardware logic unit failed Message value: Fault cause: %1 bin Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: PULSE INHIBIT Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Fault value (r0949, interpret binary): Bit 0: ALU watchdog has responded.
• Page 797
  SINAMICS alarms 232835 <location>Encoder 2 DRIVE-CLiQ: Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. The nodes do not send and receive in synchronism.
• Page 798
  SINAMICS alarms 232845 <location>Encoder 2 DRIVE-CLiQ: Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 0B hex:…
• Page 799
  SINAMICS alarms 232860 <location>Encoder 2 DRIVE-CLiQ (CU): Telegram error Message value: Component number: %1, fault cause: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 11 hex = 17 dec:…
• Page 800
  SINAMICS alarms 232885 <location>Encoder 2 DRIVE-CLiQ (CU): Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit. The nodes do not send and receive in synchronism.
• Page 801
  SINAMICS alarms 232887 <location>Encoder 2 DRIVE-CLiQ (CU): Component fault Message value: Component number: %1, fault cause: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: Fault detected on the DRIVE-CLiQ component involved (Sensor Module for encoder 2). Faulty hardware cannot be excluded.
• Page 802
  Acknowledge: NONE Cause: Error when operating the internal SPI bus. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — replace the Sensor Module. — if required, upgrade the firmware in the Sensor Module. — contact the Hotline.
• Page 803
  SINAMICS alarms 232905 <location>Encoder 2: Parameterization error Message value: Parameter: %1, supplementary information: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3, STOP1, STOP2) Acknowledge: IMMEDIATELY Cause: A parameter of encoder 2 was detected as being incorrect. It is possible that the parameterized encoder type does not match the connected encoder. The parameter involved can be determined as follows: — determine the parameter number using the fault value (r0949).
• Page 804
  1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm). 2: Measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm). Additional values: Only for internal Siemens troubleshooting. Low word high byte: Channel number. Remedy: — check that the encoder cable is the correct type and is correctly connected.
• Page 805
  SINAMICS alarms 233100 <location>Encoder 3: Zero mark distance error Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3, STOP1, STOP2) Acknowledge: PULSE INHIBIT Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance. For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs.
• Page 806
  SINAMICS alarms Note: The analog value of the amplitude error is not measured at the same time with the hardware fault output by the Sensor Module. The fault value can only be represented between -32767dec and 32767dec (-770 mV … 770 mV). The signal level is not evaluated unless the following conditions are satisfied: — Sensor Module properties available (r0459.31 = 1).
• Page 807
  SINAMICS alarms Re fault value, bit 11 = 1: — Check parameterization (p0436). Re fault value, bit 12 = 1: — Check parameterization (p0429.6). Re fault value, bit 13 = 1: — Check data line. 233111 <location>Encoder 3: Absolute encoder EnDat, internal fault/error Message value: Fault cause: %1 bin Drive object:…
• Page 808
  SINAMICS alarms 233115 <location>Encoder 3: Amplitude error track A or B (A^2 + B^2) Message value: A track: %1, B-track: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: PULSE INHIBIT Cause: The amplitude (root of A^2 + B^2) for encoder 3 exceeds the permissible tolerance. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex: yyyy = Signal level, track B (16 bits with sign).
• Page 809
  For a square-wave encoder (bipolar, double ended) the A* and B* and R* signals are not inverted with respect to sig- nals A and B and R. Fault value (r0949, interpret binary): Bits 0-15: Only for internal Siemens troubleshooting. Bit 16: Error track A. Bit 17: Error track B.
• Page 810
  SINAMICS alarms Note: If the encoder cables 6FX2002-2EQ00-..and 6FX2002-2CH00-..are interchanged, this can result in the encoder being destroyed because the pins of the operating voltage are reversed. Remedy: Re fault value, bit 0 = 1: — correct encoder cable connected? — check the plug connections of the encoder cable.
• Page 811
  SINAMICS alarms Note: The signal level is not evaluated unless the following conditions are satisfied: — Sensor Module properties available (r0459.31 = 1). — Monitoring active (p0437.31 = 1). Remedy: — make sure that the encoder cables and shielding are installed in an EMC-compliant manner. — check the plug connections and contacts of the encoder cable.
• Page 812
  SINAMICS alarms 233129 <location>Encoder 3: Position difference, hall sensor/track C/D and A/B too large Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: PULSE INHIBIT Cause: The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° electrical or the error for the Hall signals is greater than +/-60 °…
• Page 813
  SINAMICS alarms Cause: Absolute encoder: When cyclically reading the absolute position, an excessively high difference to the incremental position was detected. The absolute position that was read is rejected. Limit value for the deviation: — EnDat encoder: Is supplied from the encoder and is a minimum of 2 quadrants (e.g. EQI 1325 > 2 quadrants, EQN 1325 >…
• Page 814
  Acknowledge: PULSE INHIBIT Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Fault value (r0949, interpret binary): Only for internal SIEMENS use. Remedy: Replace encoder 233138 <location>Encoder 3: Internal error when determining multiturn information Message value:…
• Page 815
  SINAMICS alarms Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set. Fault value (r0949, interpret binary): Only for internal SIEMENS use. Remedy: Replace encoder 233150 <location>Encoder 3: Initialization error Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction:…
• Page 816
  SINAMICS alarms 233161 <location>Encoder 3: Analog sensor channel B failed Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE) Acknowledge: PULSE INHIBIT Cause: The input voltage of the analog sensor is outside the permissible limits. Fault value (r0949, interpret decimal): 1: Input voltage outside detectable measuring range.
• Page 817
  SINAMICS alarms 233405 <location>Encoder 3: Temperature in the encoder evaluation inadmissible Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: ENCODER (IASC/DCBRAKE, NONE, OFF1, OFF2, OFF3, STOP1, STOP2) Acknowledge: IMMEDIATELY (POWER ON) Cause: The encoder evaluation for a motor with DRIVE-CLiQ has detected an inadmissible temperature. The fault threshold is 125 °…
• Page 818
  SINAMICS alarms 233411 <location>Encoder 3: EnDat encoder signals alarms Message value: Fault cause: %1 bin Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: NONE Acknowledge: NONE Cause: The error word of the EnDat encoder has alarm bits that have been set. Alarm value (r2124, interpret binary): Bit 0: Frequency exceeded (speed too high).
• Page 819
  The change to the averaged speed actual value — if applicable — is monitored in the current controller sampling time. Alarm value (r2124, interpret decimal): Only for internal Siemens troubleshooting. See also: p0492 (Square-wave encoder, maximum speed difference per sampling cycle) Remedy: — check the tachometer feeder cable for interruptions.
• Page 820
  SINAMICS alarms Cause: The amplitude, phase or offset correction for track A or B is at the limit. Amplitude error correction: Amplitude B / Amplitude A = 0.78 … 1.27 Phase: <84 degrees or >96 degrees SMC20: Offset correction: +/-140 mV SMC10: Offset correction: +/-650 mV Alarm value (r2124, interpret hexadecimal): xxxx1: Minimum of the offset correction, track B…
• Page 821
  SINAMICS alarms Remedy: — check that the encoder cables are routed in compliance with EMC. — check the plug connections . check the encoder type (encoder with equidistant zero marks). — adapt the parameter for the distance between zero marks (p0424, p0425). — replace the encoder or encoder cable 233429 <location>Encoder 3: Position difference, hall sensor/track C/D and A/B too large…
• Page 822
  SINAMICS alarms Cause: For track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected. Alarm value (r2124, interpret decimal): Last measured deviation of zero mark in increments (4 increments = 1 encoder pulse). The sign designates the direc- tion of motion when detecting the zero mark distance.
• Page 823
  SINAMICS alarms Remedy: Re alarm value = 1: — check the output voltage of the analog sensor. Re alarm value = 2: — check the voltage setting for each encoder period (p4673). Re alarm value = 3: — check the range limit setting and increase it if necessary (p4676). 233461 <location>Encoder 3: Analog sensor channel B failed Message value:…
• Page 824
  SINAMICS alarms 233500 <location>Encoder 3: Position tracking traversing range exceeded Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (NONE, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: For a configured linear axis without modulo correction, the drive/encoder has exceeded the maximum possible tra- versing range.
• Page 825
  SINAMICS alarms 233503 <location>Encoder 3: Position tracking cannot be reset Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (NONE, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: The position tracking for the measuring gear cannot be reset. Remedy: The fault should be resolved as follows: — select encoder commissioning (p0010 = 4).
• Page 826
  SINAMICS alarms 233802 <location>Encoder 3: Time slice overflow Message value: Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: A time slice overflow has occurred in encoder 3. Fault value (r0949, interpret decimal): 9: Time slice overflow of the fast (current controller clock cycle) time slice. 10: Time slice overflow of the average time slice.
• Page 827
  SINAMICS alarms Bit 2: Mid-voltage matching for track A unsuccessful. Bit 3: Mid-voltage matching for track B unsuccessful. Bit 4: Mid-voltage matching for acceleration input unsuccessful. Bit 5: Mid-voltage matching for track safety A unsuccessful. Bit 6: Mid-voltage matching for track safety B unsuccessful. Bit 7: Mid-voltage matching for track C unsuccessful.
• Page 828
  SINAMICS alarms Cause: A cycle requested from the Control Unit or RX/TX timing is not supported. Alarm value (r2124, interpret decimal): 0: Application cycle is not supported. 1: DQ cycle is not supported. 2: Distance between RX and TX instants in time too low. 3: TX instant in time too early.
• Page 829
  SINAMICS alarms 233835 <location>Encoder 3 DRIVE-CLiQ: Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. The nodes do not send and receive in synchronism.
• Page 830
  SINAMICS alarms 233845 <location>Encoder 3 DRIVE-CLiQ: Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 0B hex:…
• Page 831
  SINAMICS alarms 233860 <location>Encoder 3 DRIVE-CLiQ (CU): Telegram error Message value: Component number: %1, fault cause: %2 Drive object: SERVO_COMBI, SERVO_SINUMERIK828 Reaction: OFF1 (IASC/DCBRAKE, NONE, OFF2, OFF3) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 11 hex = 17 dec:…
• Page 832
  SINAMICS alarms Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit. The nodes do not send and receive in synchronism. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 1A hex = 26 dec: Sign-of-life bit in the receive telegram not set and the receive telegram is too early.
• Page 833
  SINAMICS alarms Remedy: — check the DRIVE-CLiQ wiring (interrupted cable, contacts, …). — check the electrical cabinet design and cable routing for EMC compliance — if required, use another DRIVE-CLiQ socket (p9904). — replace the component involved. 233895 <location>Encoder 3 DRIVE-CLiQ (CU): Alternating cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object:…
• Page 834
  Acknowledge: NONE Cause: Error when operating the internal SPI bus. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: — replace the Sensor Module. — if required, upgrade the firmware in the Sensor Module. — contact the Hotline.
• Page 835
  SINAMICS alarms yyyy = 5: For SQW encoder, value in p4686 greater than in p0425. yyyy = 6: DRIVE-CLiQ encoder cannot be used with this firmware version. yyyy = 7: For the SQW encoder, the Xact1 correction (p0437.2) is only permitted with equidistant zero marks. Remedy: — check whether the connected encoder type matches the encoder that has been parameterized.
• Page 836
  1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm). 2: Measured resistance too low (PTC: R < 20 Ohm, KTY: R < 50 Ohm). Additional values: Only for internal Siemens troubleshooting. Low word high byte: Channel number. Remedy: — check that the encoder cable is the correct type and is correctly connected.
• Page 837
  SINAMICS alarms 234211 <location>VSM: Temperature alarm threshold exceeded Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: The temperature (r3666) measured using the Voltage Sensing Module (VSM) has exceeded the threshold value (p3667). Alarm value (r2124, interpret decimal): The hundred-thousands and ten-thousands position specifies the component number of the VSM which detected the fault.
• Page 838
  SINAMICS alarms 234803 <location>VSM: Memory test Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 (NONE, OFF1) Acknowledge: IMMEDIATELY Cause: An error has occurred during the memory test on the Voltage Sensing Module. Remedy: — check whether the permissible ambient temperature for the Voltage Sensing Module is being maintained. — replace the Voltage Sensing Module.
• Page 839
  SINAMICS alarms 234807 <location>VSM: Sequence control time monitoring Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: Error, timeout in the sequence control on the Voltage Sensing Module (VSM). Remedy: Replace the Voltage Sensing Module. 234820 <location>VSM DRIVE-CLiQ: Telegram error Message value: Component number: %1, fault cause: %2…
• Page 840
  SINAMICS alarms Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module. The nodes do not send and receive in synchronism. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 21 hex: The cyclic telegram has not been received.
• Page 841
  SINAMICS alarms 234845 <location>VSM DRIVE-CLiQ: Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: OFF2 (NONE, OFF1) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module (VSM). Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 0B hex:…
• Page 842
  SINAMICS alarms Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module (VSM) to the Control Unit. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 11 hex = 17 dec: CRC error and the receive telegram is too early.
• Page 843
  SINAMICS alarms xx = 22 hex = 34 dec: Timeout in the telegram receive list. xx = 40 hex = 64 dec: Timeout in the telegram send list. xx = 62 hex = 98 dec: Error at the transition to cyclic operation. Remedy: — check the power supply voltage of the component involved.
• Page 844
  SINAMICS alarms 234895 <location>VSM DRIVE-CLiQ (CU): Alternating cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, CU_LINK, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM120 Reaction: Servo: NONE (OFF1, OFF2) Infeed: OFF2 (NONE, OFF1) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module (VSM) to the Control Unit.
• Page 845
  SINAMICS alarms 234903 <location>VSM: I2C bus error occurred Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: An error has occurred when accessing the module-internal I2C bus. Remedy: Replace Voltage Sensing Module (VSM). 234904 <location>VSM: EEPROM Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828…
• Page 846
  SINAMICS alarms 234999 <location>VSM: Unknown alarm Message value: New message: %1 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: A fault occurred on the Voltage Sensing Module (VSM) an alarm has occurred that cannot be interpreted by the Control Unit firmware.
• Page 847
  SINAMICS alarms Cause: The commissioning mode setting was rejected because for at least one drive belonging to the TM54F, the pulses had not been suppressed. Fault value (r0949, interpret decimal): Drive object number of the first drive found without pulse suppression. Remedy: Cancel the pulses for the drive specified in the fault value.
• Page 848
  SINAMICS alarms Cause: An error was detected when carrying out the test stop on the TM54F. As fault response fail-safe input terminal signals are transferred to the motion monitoring functions. Fault value 0xaaaabbcc hex (r0949, interpret hexadecimal): aaaa: Specifies the DOs or F-DIs (dependent on test step cc) for which the expected state was not assumed. The number is bit-coded (bit 0 = F-DI 0 or F-DO 0;…
• Page 849
  SINAMICS alarms 235014 <location>TM54F: Test stop required Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM54F_MA, TM54F_SL Reaction: NONE Acknowledge: NONE Cause: — after powering up the drive, a test stop has still not been carried out. — a new test stop is required after commissioning. — the time to carry out the forced checking procedure (test stop) has expired (p10003).
• Page 850
  SINAMICS alarms 235040 <location>TM54F: 24 V undervoltage Message value: Fault cause: %1 bin Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM54F_MA, TM54F_SL Reaction: NONE Acknowledge: IMMEDIATELY Cause: For the 24 V power supply for the Terminal Module 54F (TM54F) an undervoltage condition was detected. As fault response fail-safe input terminal signals are transferred to the motion monitoring functions.
• Page 851
  Cause: An internal software/hardware error has been detected on the Terminal Module 54F (TM54F). Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: — check the electrical cabinet design and cable routing for EMC compliance — upgrade TM54F firmware to more recent version.
• Page 852
  As fault response fail-safe input terminal signals are transferred to the motion monitoring functions. Fault value (r0949, interpret decimal): Only for internal Siemens troubleshooting. Remedy: — allow the TM54F to cool down. — carry out safe acknowledgement (p10006).
• Page 853
  A communication error between the TM54F master and Control Unit or between the TM54F slave and the Motor Mod- ule was detected. Fault value (r0949, interpret hexadecimal): Only for internal Siemens troubleshooting. Remedy: When replacing a Motor Module, carry out the following steps: — start the copy function for the node identifier on the TM54F (p9700 = 1D hex).
• Page 854
  SINAMICS alarms 235151 <location>TM54F: Discrepancy error Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM54F_MA, TM54F_SL Reaction: NONE Acknowledge: IMMEDIATELY Cause: The safety input terminals or output terminals show a different state longer than that parameterized in p10002. Fault value (r0949, interpret hexadecimal): yyyyxxxx hex xxxx:…
• Page 855
  SINAMICS alarms 235152 <location>TM54F: Internal software error Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM54F_MA, TM54F_SL Reaction: NONE Acknowledge: IMMEDIATELY Cause: An internal software error has occurred in the Terminal Module 54F (TM54F). The fail-safe digital inputs and digital outputs (F-DI, F-DO) on the TM54F have been set to the safe state. Note: F-DI: Failsafe Digital Input F-DO: Failsafe Digital Output…
• Page 856
  SINAMICS alarms Note: For PTC, the following applies: — if r4101[0] > 1650 ohms, the temperature r4105[0] = 250 °C — if r4101[0] <= 1650 ohms, the temperature r4105[0] = -50°C The measured temperature is displayed in r4105[0]. This fault can only be initiated if temperature evaluation was activated (p4100[0] = 2 for KTY84 sensor, p4100[0] = 1 for PTC thermistor or p4100[0] = 4 for bimetallic NC contact).
• Page 857
  SINAMICS alarms 235209 <location>TM: Temperature fault/alarm threshold channel 3 exceeded Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM120 Reaction: Servo: OFF2 (NONE, OFF1, OFF3) Infeed: OFF2 (NONE, OFF1) Acknowledge: IMMEDIATELY (POWER ON) Cause: For the temperature evaluation via the Terminal Module 120 (TM120), at least one of the following conditions to initiate this fault is fulfilled: — alarm threshold has been exceeded longer than that set in the timer stage (p4102[4], p4103[2]).
• Page 858
  SINAMICS alarms 235211 <location>TM: Temperature alarm threshold channel 1 exceeded Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM120 Reaction: NONE Acknowledge: NONE Cause: The temperature measured using the temperature sensing of the Terminal Module (TM) (r4105[0]) has exceeded the threshold value to initiate this alarm (p4102[0]).
• Page 859
  SINAMICS alarms 235214 <location>TM: Temperature alarm threshold channel 4 exceeded Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM120 Reaction: NONE Acknowledge: NONE Cause: The temperature measured using the temperature sensing of the Terminal Module 120 (TM120) (r4105[3]) has exceeded the threshold value to initiate this alarm (p4102[6]).
• Page 860
  SINAMICS alarms 235800 <location>TM: Group signal Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM120, TM54F_MA, TM54F_SL Reaction: Servo: OFF2 (IASC/DCBRAKE, NONE, OFF1, OFF3, STOP1, STOP2) Infeed: OFF2 (NONE, OFF1) Acknowledge: NONE Cause: The Terminal Module has detected at least one fault. Remedy: Evaluates other actual messages.
• Page 861
  SINAMICS alarms 235804 <location>TM: CRC Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM120, TM54F_MA, TM54F_SL Reaction: NONE Acknowledge: NONE Cause: A checksum error has occurred when reading-out the program memory on the Terminal Module. Fault value (r0949, interpret hexadecimal): Difference between the checksum at POWER ON and the actual checksum.
• Page 862
  SINAMICS alarms Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module to the encoder involved. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 01 hex: CRC error. xx = 02 hex: Telegram is shorter than specified in the length byte or in the receive list.
• Page 863
  SINAMICS alarms Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module to the encoder involved. Data were not able to be sent. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 41 hex: Telegram type does not match send list.
• Page 864
  SINAMICS alarms 235850 <location>TM: Internal software error Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM120, TM54F_MA, TM54F_SL Reaction: Servo: OFF1 (NONE, OFF2, OFF3) Infeed: OFF1 (NONE, OFF2) Acknowledge: POWER ON Cause: An internal software error in the Terminal Module (TM) has occurred. Fault value (r0949, interpret decimal): 1: Background time slice is blocked.
• Page 865
  SINAMICS alarms xx = 04 hex = 04 dec: The length of the receive telegram does not match the receive list. xx = 15 hex = 21 dec: The type of the receive telegram does not match the receive list and the receive telegram is too early. xx = 05 hex = 05 dec: The type of the receive telegram does not match the receive list.
• Page 866
  SINAMICS alarms 235886 <location>TM DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data Message value: Component number: %1, fault cause: %2 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, CU_LINK, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM120, TM54F_MA, TM54F_SL Reaction: OFF1 (OFF2) Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module (TM) to the Control Unit involved. Data were not able to be sent.
• Page 867
  SINAMICS alarms Remedy: Carry out a POWER ON. See also: p9915 (DRIVE-CLiQ data transfer error shutdown threshold master) 235896 <location>TM DRIVE-CLiQ (CU): Inconsistent component properties Message value: Component number: %1 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, CU_LINK, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM120, TM54F_MA, TM54F_SL Reaction: Servo: OFF2 (IASC/DCBRAKE, NONE, OFF1, OFF3, STOP1, STOP2) Infeed: OFF2 (NONE, OFF1)
• Page 868
  SINAMICS alarms 235904 <location>TM: EEPROM Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM120 Reaction: NONE Acknowledge: NONE Cause: An error has occurred accessing the non-volatile memory on the Terminal Module. Remedy: Replace the Terminal Module. 235905 <location>TM: Parameter access Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI,…
• Page 869
  SINAMICS alarms Cause: The Terminal Module was not successfully initialized. Alarm value (r2124, interpret hexadecimal): 01: TM17 or TM41 — incorrect configuration request. 02: TM17 or TM41 — programming not successful. 04: TM17 or TM41 — invalid time stamp Remedy: Carry out a POWER ON.
• Page 870
  SINAMICS alarms 235921 <location>TM: Error temperature sensor channel 2 Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM120 Reaction: NONE Acknowledge: NONE Cause: When evaluating the temperature sensor, an error occurred. Alarm value (r2124, interpret decimal): 1: Wire breakage or sensor not connected (KTY: R > 1630 Ohm). 2: Measured resistance too low (PTC: R <…
• Page 871
  SINAMICS alarms Cause: An alarm has occurred on the Terminal Module that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit. Alarm value (r2124, interpret decimal): Alarm number.
• Page 872
  SINAMICS alarms 236216 <location>Hub: undervoltage fault 24 V supply Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, HUB, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE (OFF1, OFF2) Acknowledge: IMMEDIATELY (POWER ON) Cause: The 24 V power supply on the DRIVE-CLiQ Hub Module has undershot the fault threshold. Fault value (r0949, interpret decimal): Actual operating voltage in 0.1 °C resolution Remedy:…
• Page 873
  SINAMICS alarms 236802 <location>Hub: Time slice overflow Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, HUB, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: Servo: NONE Infeed: OFF2 (NONE) Acknowledge: IMMEDIATELY (POWER ON) Cause: A time slice overflow has occurred on the DRIVE-CLiQ Hub Module. Fault value (r0949, interpret decimal): xx: Time slice number xx Remedy:…
• Page 874
  SINAMICS alarms 236820 <location>Hub DRIVE-CLiQ: Telegram error Message value: Component number: %1, fault cause: %2 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, HUB, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the DRIVE-CLiQ Hub Module involved. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 01 hex = 1 dec:…
• Page 875
  SINAMICS alarms 236836 <location>Hub DRIVE-CLiQ: Send error for DRIVE-CLiQ data Message value: Component number: %1, fault cause: %2 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, HUB, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the DRIVE-CLiQ Hub Module involved. Data were not able to be sent.
• Page 876
  SINAMICS alarms 236851 <location>Hub DRIVE-CLiQ (CU): Sign-of-life missing Message value: Component number: %1, fault cause: %2 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, CU_LINK, HUB, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828, TM120 Reaction: NONE Acknowledge: IMMEDIATELY Cause: DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question to Control Unit. The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit.
• Page 877
  SINAMICS alarms Remedy: — carry out a POWER ON. — check the electrical cabinet design and cable routing for EMC compliance — check the DRIVE-CLiQ wiring (interrupted cable, contacts, …). 236885 <location>Hub DRIVE-CLiQ (CU): Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, CU_LINK, HUB, SERVO_COMBI, SERVO_SINUMERIK828,…
• Page 878
  SINAMICS alarms Cause: Fault detected on the DRIVE-CLiQ component (DRIVE-CLiQ Hub Module) involved. Faulty hardware cannot be excluded. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 20 hex = 32 dec: Error in the telegram header.
• Page 879
  SINAMICS alarms 236899 <location>Hub: Unknown fault Message value: New message: %1 Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, HUB, SERVO_COMBI, SERVO_SINUMERIK828, SIC_COMBI, SIC_SINUMERIK_828 Reaction: Servo: NONE (IASC/DCBRAKE, OFF1, OFF2, OFF3, STOP1, STOP2) Infeed: NONE (OFF1, OFF2) Acknowledge: IMMEDIATELY (POWER ON) Cause: A fault occurred on the DRIVE-CLiQ Hub Module that cannot be interpreted by the Control Unit firmware. This can occur if the firmware on this component is more recent than the firmware on the Control Unit.
• Page 880
  SINAMICS alarms 240001 <location>Fault at DRIVE-CLiQ socket X101 Message value: Drive object: All objects Reaction: NONE Acknowledge: IMMEDIATELY Cause: A fault has occurred at the drive object at the DRIVE-CLiQ socket X101. Fault value (r0949, interpret decimal): First fault that has occurred for this drive object. Remedy: Evaluate the fault buffer of the specified object.
• Page 881
  SINAMICS alarms 240005 <location>Fault at DRIVE-CLiQ socket X105 Message value: Drive object: All objects Reaction: NONE Acknowledge: IMMEDIATELY Cause: A fault has occurred at the drive object at the DRIVE-CLiQ socket X105. Fault value (r0949, interpret decimal): First fault that has occurred for this drive object. Remedy: Evaluate the fault buffer of the specified object.
• Page 882
  SINAMICS alarms 240103 <location>Alarm at DRIVE-CLiQ socket X103 Message value: Drive object: All objects Reaction: NONE Acknowledge: NONE Cause: An alarm has occurred at the drive object at the DRIVE-CLiQ socket X103. Alarm value (r2124, interpret decimal): First alarm that has occurred for this drive object. Remedy: Evaluate the alarm buffer of the specified object.
• Page 883
  SINAMICS alarms 240801 <location>CX32 DRIVE-CLiQ: Sign-of-life missing Message value: Component number: %1, fault cause: %2 Drive object: All objects Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the controller extension involved. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 0A hex: The sign-of-life bit in the receive telegram is not set.
• Page 884
  SINAMICS alarms 240835 <location>CX32 DRIVE-CLiQ: Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: All objects Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the controller extension involved. The nodes do not send and receive in synchronism.
• Page 885
  SINAMICS alarms 240845 <location>CX32 DRIVE-CLiQ: Cyclic data transfer error Message value: Component number: %1, fault cause: %2 Drive object: All objects Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the controller extension involved. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 0B hex:…
• Page 886
  SINAMICS alarms xx = 05 hex: The type of the receive telegram does not match the receive list. xx = 16 hex: The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early.
• Page 887
  SINAMICS alarms 240887 <location>CX32 DRIVE-CLiQ (CU): Component fault Message value: Component number: %1, fault cause: %2 Drive object: All objects Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded. Fault value (r0949, interpret hexadecimal): yyxx hex: yy = component number, xx = fault cause xx = 20 hex: Error in the telegram header.
• Page 888
  SINAMICS alarms 249151 <location>Cooling system: Conductivity has exceeded the fault threshold Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_SINUMERIK_828 Reaction: OFF2 Acknowledge: IMMEDIATELY Cause: The conductivity of the cooling liquid has exceeded the selected fault threshold (p0269[2]). See also: p0261 (Cooling system, starting time 2), p0262 (Cooling system, fault conductivity delay time), p0266 (Cool- ing system, feedback signals, signal source) Remedy: Check the device to de-ionize the cooling liquid.
• Page 889
  SINAMICS alarms 249155 <location>Cooling system: Power Stack Adapter, firmware version too old Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_SINUMERIK_828 Reaction: OFF2 Acknowledge: POWER ON Cause: The firmware version in the Power Stack Adapter (PSA) is too old and does not support the liquid cooling. Remedy: Upgrade the firmware.
• Page 890
  SINAMICS alarms 249172 <location>Cooling system: Conductivity actual value is not valid Message value: Drive object: AFE_SINUMERIK_828, BIC_SINUMERIK_828, SIC_SINUMERIK_828 Reaction: NONE Acknowledge: NONE Cause: When monitoring the conductivity of the cooling liquid, there is a fault in the wiring or in the sensor. Remedy: — check the wiring between the cooling system and the Power Stack Adapter (PSA).
• Page 891
  Please inform the authorized personnel/service department. The alarm can be suppressed with MD11411 $MN_ENABLE_ALARM_MASK bit 1 == 0 SIEMENS AG, System Support for A&D MC products, Hotline (Phone: see alarm 1000) Program Clear alarm with the Delete key or NC START.
• Page 892
  611D drive alarms 300411 Axis %1 drive %2 error when reading a file (%3, %4) Parameters: %1 = NC axis number %2 = Drive number %3 = Error code 1 %4 = Error code 2 Definitions: An attempt to read a data block, e.g. a drive boot file, from the file system has failed. The data block or the file system is damaged.

• Page 893: D Drive Alarms

  611D drive alarms 300423 Measuring result could not be read (%1) Parameters: %1 = Error code Definitions: An attempt to read a measurement result has failed: — Error code = 4: Not enough space for test result — Error code = 16: Measurement not yet finished Reaction: Interface signals are set.

• Page 894
  611D drive alarms Remedy: Remedy for 1-11 1. Check the control project, check MD11240 $MN_PROFIBUS_SDB_NUMBER, and reload it when using a user-spe- cific SDB. 2. If the error still occurs, back up data, and restart the control with the standard values as per the as-delivered condi- tion.
• Page 895
  611D drive alarms Remedy: — For error cause 01: — Check the electrical and fault-related specifications for PROFIBUS/PROFINET, assess the cable installation — Check the terminating resistors of the PROFIBUS connectors (ON setting at ends of cables, otherwise OFF setting required) — Check slave/device — For error causes 02, 03, 04:…
• Page 896
  611D drive alarms SDB source: — 99 = Passive file system: _N_SDB_DIR — 100 = CF card: /siemens/sinumerik/sdb/… — 101 = CF card: /addon/sinumerik/sdb/… — 102 = CF card: /oem/sinumerik/sdb/… — 103 = CF card: /user/sinumerik/sdb/… Reaction: PROFIBUS/PROFINET is inactive or working with the default SDB.
• Page 897
  611D drive alarms — 11 = The telegram configured in the SDB is too short for the selected telegram acc. to $MN_DRIVE_TELEGRAM_TYPE. — 20 = SDB contains too many slaves/devices, quantity — 21 = SDB missing or contains invalid data, error code — 22 = SDB configuration data incorrect, slave/device address, error code — 23 = Reserved — 24 = Reserved…
• Page 898
  611D drive alarms 380051 PROFIBUS/PROFINET: Multiple assignment of outputs on address %1 Parameters: %1 = Logical address Definitions: Multiple assignments of input data have been detected in the logical address space. Logical address: Base address of the address area defined several times Reaction: Channel not ready.
• Page 899
  611D drive alarms Remedy: Enter correct base addresses in the machine data: — For length=1: Correct machine data MN_HW_ASSIGN_DIG_FASTIN. — For length=2: Correct machine data MN_HW_ASSIGN_ANA_FASTIN. — NCK restart If the error cannot be eliminated by this procedure, please make a note of the error text and contact the control system manufacturer.
• Page 900
  611D drive alarms 380075 PROFIBUS/PROFINET: DP I/O failure bus %2 slave/device %1 Parameters: %1 = Slave/device address %2 = Number of the affected bus Definitions: Failure of a PROFIBUS/PROFINET slot used by the NCK for digital or analog I/Os. Reaction: Alarm display.
• Page 901
  611D drive alarms 380500 PROFIBUS/PROFINET: Fault on drive %1, code %2, value %3, time %4 Parameters: %1 = Axis %2 = Fault code of drive (P947(/945)/P824) %3 = Fault value of drive ((P949/P826) %4 = Fault time of drive (P948/P825) Definitions: Contents of fault memory of assigned drive.
• Page 902
  611D drive alarms Alarms Diagnostics Manual, 07/2010, 6FC5398-8BP40-0BA0…
• Page 903
  With this alarm, internal alarm states are displayed that, in conjunction with the transferred error number, provide infor- mation on the cause and location of the error. Reaction: PLC Stop Remedy: Notify Siemens of this error together with the error message. Program Switch control OFF — ON. Continuation: 400002…
• Page 904
  PLC alarms 400005 PLC stop specified from start-up menu Definitions: User program is not being processed Reaction: Alarm display. Remedy: Switch controller off/on Program Switch control OFF — ON. Continuation: 400006 Loss of remanent PLC data Definitions: The following causes are possible: Control handling (e.g.

• Page 905: Plc Alarms

  3Number of slots per function exceeded 4Profinet I/O server not ready Reaction: PLC Stop Remedy: Types 1 to 3:Report error to Siemens Type 4:828D – Check and/or replace PCU hardware and/or check MD 11240 Program Switch control OFF — ON. Continuation:…

• Page 906
  PLC alarms 400015 Profinet — IO I/O fault: log. addr. %1 bus/station: %2 Definitions: The PLC-AWP is using I/O addresses which are not available. %1Logical I/O address %2Bus number/station number Causes of error: Bus peripheral has no voltage Bus address set incorrectly Bus connection faulty Active MD 11240 (SDB configuration) is set incorrectly Reaction:…
• Page 907
  PLC alarms 400021 Wait until I/O access is possible Definitions: I/O access is not possible at the current time. Reaction: Alarm display. Remedy: Program Clear alarm with the Delete key or NC START. Continuation: 400022 The PLC functionality: %2 is not permitted. Definitions: PLC functionality: %2 The specified PLC functionality is not supported.
• Page 908
  PLC alarms Alarms Diagnostics Manual, 07/2010, 6FC5398-8BP40-0BA0…
• Page 909
  List of actions Product: Handbuch_Sinumerik, Version: V12.0, Language: eng, Objects: /NON/ No. 0 /SYSTEM_SHUTDOWN/ No. 96 Definitions: Switch off system (VDI signal) Should not occur in any alarm /SERUPRO_ON/ No. 97 Definitions: Connect block search PI in mode 5. Block search is simulated in this mode by executing the program under «program test mode»…
• Page 910
  List of actions /EXT_ZERO_POINT/ No. 101 Definitions: External work offset is activated via PLC. To do this the path is stopped, REORG executed, the interpreter changed over, and then selected and continued automatically with REPOS. Not permitted if: 1. The channel is not in AUTO or MDA. 2.

• Page 911: List Of Actions

  List of actions /SINGLEAX_RESET_MASTER/ No. 106 Definitions: Canceling a single axis motion (VDI signal) Not permitted if: The axis is not controlled by the PLC Initially, not for all types of axis /SINGLEAX_DELDIS_MASTER/ No. 107 Definitions: Delete distance-to-go of a single axis motion (VDI signal) Not permitted if: The axis is not controlled by the PLC…

• Page 912
  List of actions /SINGLEAX_JOG_PLUS_INC_MASTER/ No. 113 Definitions: Available soon /SINGLEAX_JOG_MINUS_INC_MASTER/ No. 114 Definitions: Available soon /REPOSMODECHANGE/ No. 115 Definitions: The event is triggered by the positive PLC edge of the signal «Repos mode edge». Not permitted if: 1. The channel is active (program running, block search, loading machine data) Possible actions: 1.
• Page 913
  List of actions /STOPRUN/ No. 119 Definitions: Stop run, that is the NCK stops automatically at a block defined by the OPI. Not permitted if 1. Control is not in Automatic. /SINGLEAX_LIFTFASTOFF_MASTER/ No. 120 Definitions: Fast retraction with a single axis Not permitted if: The axis is not controlled by the PLC /SINGLEAX_STOPLIFTOFF_MASTER/ No.
• Page 914
  List of actions /FASTMODESWITCHTOAPROGMODE/ No. 126 Definitions: Implicit mode change back at the end of a «JOG motion» started in automatic mode. See also $MN_JOG_MODE_MASK Not permitted if: 1. A channel has left the mode group on account of an interrupt. 2.
• Page 915
  List of actions /REDUCE_CALC_TIME/ No. 132 Definitions: PI service _N_NCKMOD (BIT-1) has been rejected. Not permitted if: Should not occur. /SIMULATION_ON_OFF/ No. 133 Definitions: PI service _N_NCKMOD (BIT-1) has been rejected. Not permitted if: Should not occur. Abort subroutine execution /PROGCANCELSUB/ No. 17 Definitions: Cancel the subprogram execution.
• Page 916
  List of actions Activate decoding single block /SINGLEBLOCK_DECODIER/ No. 21 Definitions: Activate decoding single block. (OPI variable and VDI signal: activate single block) Not permitted if: 1. The nesting depth is too great 2. If there is a reorganize brake error Possible actions: 1.
• Page 917
  List of actions Activate single block /SINGLEBLOCKSTOP/ No. 18 Definitions: Activate single block. (VDI signal: activate single block) Should not occur in any alarm Activate test run /PROGMODEDRYRUNON/ No. 63 Definitions: Activate test run. (VDI signal: rapid traverse override) Not permitted if: 1.
• Page 918
  List of actions Automatic mode change /MODESWITCHTOSAVEDMODE/ No. 6 Definitions: Automatic change from an internal mode into the externally set mode. E.g: With teach-in: Internal mode = automatic or MDA Should not occur in any alarm Change measuring system /CONVERT_SCALING_SYSTEM/ No. 95 Definitions: Change over PI service measuring system Should not occur in any alarm as, if necessary, the PI service is acknowledged negatively…
• Page 919
  List of actions Conditional stop at end of block /CONDITIONAL_STOPATEND/ No. 73 Definitions: Conditional stop at the block boundary. There is another stop if there is still a stop reason «Stop at end of block» after continuation by an NC start. Should not occur in any alarm Conditional stop at end of block (SBL2) /CONDITIONAL_SBL_DEC_STOPATEND/ No.
• Page 920
  List of actions Continue selected processing /RESUMEJOGREFDIGIT/ No. 27 Definitions: Start continue the selected processing, (VDI signal, NC start) (JOG or reference point) Not permitted if: 1. JOG motion is active, 2. An alarm response is pending: which prevents a start, or compels braking.
• Page 921
  List of actions Deactivate test run /PROGMODEDRYRUNOFF/ No. 64 Definitions: Deactivate test run. (VDI signal: rapid traverse override) Not permitted if: 1. The nesting depth is too great 2. If there is a reorganize brake error Possible actions: 1. Wait until previous ASUB has finished or cancel program 2.
• Page 922
  List of actions Digitizing inactive /DIGITIZEOFF/ No. 54 Definitions: ! Digitize function removed ! Deactivate digitization (PI command) Should not occur in any alarm Digitizing processing /STARTDIGITIZE/ No. 28 Definitions: ! Digitize function removed ! Start processing in digitize submode (VDI signal, NC start) Not permitted if: 1.
• Page 923
  List of actions Locking save data /SAVEDATA/ No. 92 Definitions: Interlock for data recovery Is not permitted if: The NCK channel status is not Stopped Machine data execution (external) /INITIALINIEXTSTART/ No. 36 Definitions: Start machine data processing (PI command) (INI file is located externally (e.g.) on MMC) Should not occur in any alarm Machine data processing /INITIALINISTART/ No.
• Page 924
  List of actions Program stop /STOPPROG/ No. 30 Definitions: Execute a program stop (NC block M0) Should not occur in any alarm Rapid retract /FASTLIFTOFF/ No. 13 Definitions: Execute a fast retraction Should not occur in any alarm Reorganize after block preparation /STOPATIPOBUF_EMPTY_ALARM_REORG/ No. 72 Definitions: Stop at end of block preparation (alarm) followed by reorganization of the block preparation.
• Page 925
  List of actions Save asynchon. subroutine /ASUPDEFINITION/ No. 47 Definitions: Save definition of an activatable ASUB (PI command) Should not occur in any alarm Select external program /PROGSELECTEXT/ No. 45 Definitions: Select program that is still located internally (PI command) Should not occur in any alarm Select NC block /BLOCK_SELECT/ No.
• Page 926
  List of actions Start program execution (program) /STARTPROG/ No. 24 Definitions: Start program execution, (VDI signal, NC start) Not permitted if: 1. Program status is active, 2. An alarm response is pending: which prevents a start, or compels braking. 3. Reference point approach not yet executed Possible actions: 1.
• Page 927
  List of actions Stop active processing /STOPSIG/ No. 34 Definitions: Stop the active processing. (VDI signal, NC stop) Should not occur in any alarm Stop after block preparation /STOPATIPOBUFFER_ISEMPTY_ALARM/ No. 71 Definitions: Stop at the end of block preparation (alarm) Should not occur in any alarm Stop all axes /STOPALL/ No.
• Page 928
  List of actions Stop processing at block limit (program) /PROG_STOP/ No. 41 Definitions: Stop the processing at the block boundary. (NC block, M00/M01) Should not occur in any alarm Stop processing at block limit (VDI) /STOPPROGATBLOCKEND/ No. 42 Definitions: Stop the processing at the block boundary. (Alarm, VDI signal: NC stop at the block boundary) Should not occur in any alarm Stop single block because of mode group (type A) /BAGSTOP_SLBTYPA/ No.
• Page 929
  List of actions User interrupt ASUP /INTERRUPT/ No. 10 Definitions: Execute an «ASUB» user interrupt. (VDI signal, ASUB interface, digital-analog interface) Alarms can be switched on by machine data «HW_DEBUG_MASK» (for test purposes only). Not permitted if: 1. The channel is active on account of block search or loading machine data 2.
• Page 930
  List of actions Waiting for end of program /WAITE/ No. 58 Definitions: Wait for a program end (channel communication, NC block, WAITE) Should not occur in any alarm Waiting for program marker /WAITM/ No. 57 Definitions: Wait for a program marker (channel communication, NC block, WAITM) Should not occur in any alarm Waiting for program marker /WAITMC/ No.
• Page 931
  System reactions System reactions to SINUMERIK alarms Identifier COMPBLOCKWITHREORG Effects Block preparation has detected an error, which can be rectified by modifying the program. Reorganization is performed after a program modification. • Correction block with reorganization. Identifier COMPENSATIONBLOCK Effects Block preparation has detected an error, which can be rectified by modifying the program. •…
• Page 932
  System reactions 8.1 System reactions to SINUMERIK alarms Identifier NOREADY | BAGREACTIONVIEW Effects Mode group ready off: Active fast braking (i.e. with maximum braking current) of the drives in this mode group, the controller enable of the NC axes involved is deleted. •…

• Page 933: System Reactions

  System reactions 8.1 System reactions to SINUMERIK alarms Identifier SHOWALARMAUTO Effects The alarm is displayed whenever bit 0 of machine data ENABLE_ALARM_MASK is set. The reaction should be set whenever an alarm should only occur during automatic mode without manual operation by the user.

• Page 934: Cancel Criteria For Alarms

  System reactions 8.2 Cancel criteria for alarms Cancel criteria for alarms Identifier CANCELCLEAR Effects The alarm is cleared in any channel when the Cancel key is pressed. It is also cleared by the Start part program key. • Clear the alarm with the Clear key or with NC-START. Identifier CLEARHIMSELF Effects…

• Page 935
  System reactions 8.2 Cancel criteria for alarms Identifier NOCLEAR Effects The clear information is only required for the internal pseudo alarm number EXBSAL_NOMOREALARMS. Alarms Diagnostics Manual, 07/2010, 6FC5398-8BP40-0BA0…
• Page 936
  System reactions 8.3 System reactions for SINAMICS alarms System reactions for SINAMICS alarms Designation NONE Reaction None Description No reaction when a fault occurs Designation OFF1 Reaction Brake along the ramp-function generator down ramp followed by pulse disable Description Closed loop speed control (p1300 = 20, 21) •…
• Page 937
  System reactions 8.3 System reactions for SINAMICS alarms Designation OFF3 Reaction Brake along the OFF3 down ramp followed by pulse disable Description Closed loop speed control (p1300 = 20, 21) • n_set=0 is input immediately to brake the drive along the OFF3 down ramp (p1135). •…

• Page 938: System Reactions For Sinamics Alarms

  The parameter number consists of a «p» or «r» as prefix, followed by a 4-digit number(xxxx) and optionally an index, e.g. p0918[0…3]. References A detailed description of the SINAMICS parameters is provided in the: SINAMICS S120/S150 List Manual Alarms Diagnostics Manual, 07/2010, 6FC5398-8BP40-0BA0…

• Page 939
  Appendix List of abbreviations Output Automation system ASCII American Standard Code for Information Interchange ASIC Application Specific Integrated Circuit: User switching circuit ASUB Asynchronous subprogram AuxF Auxiliary function Job planning Operating mode Ready to run Binary Coded Decimals: Decimal numbers encoded In binary code Basic Coordinate System Binary files (Binary Files) BIOS…
• Page 940
  Appendix A.1 List of abbreviations Data Carrier Detect Dynamic Data Exchange Deutsche Industrie Norm (German Industry Standard) Data Input/Output: Data transfer display Directory: Directory Dynamic Link Library Data transmission equipment Disk Operating System Dual-Port Memory Dual-Port RAM DRAM Dynamic Random Access Memory Differential Resolver Function: Differential resolver function (DRF) Dry Run: Dry run feedrate Decoding Single Block: Decoding single block…

• Page 941: A.1 List Of Abbreviations

  Appendix A.1 List of abbreviations Human Machine Interface: Operator functionality of SINUMERIK for operation, programming and simulation. High-resolution Measuring System Hardware Input/Output Infeed/regenerative-feedback unit (power supply) of the SIMODRIVE 611digital Startup Drive module pulse enable IK (GD) Implicit communication (global data) Interpolative Compensation: Interpolatory compensation Interface Module Interconnection module Interface Module Receive: Interconnection module for receiving data…

• Page 942
  Appendix A.1 List of abbreviations Microsoft (software manufacturer) Main Spindle Drive Numerical Control: Numerical Control Numerical Control Kernel: NC kernel with block preparation, traversing range, etc. Numerical Control Unit: Hardware unit of the NCK Name for the operating system of the NCK NURBS Non-Uniform Rational B-Spline Organization block in the PLC…
• Page 943
  Appendix A.1 List of abbreviations SKiP: Skip block Stepper Motor Sub Routine File: Subprogram Subprogram SRAM Static RAM (non-volatile) Serial Synchronous Interface: Synchronous serial interface Statement list Software System Files System files Tool Tool change Testing Data Active: Identifier for machine data Tool length compensation TNRC Tool Nose Radius Compensation…

• Page 944: A.2 Feedback On The Documentation

  This document will be continuously improved with regard to its quality and ease of use. Please help us with this task by sending your comments and suggestions for improvement via e-mail or fax to: E-mail: mailto:docu.motioncontrol@siemens.com Fax: +49 9131 — 98 2176 Please use the fax form on the back of this page.

• Page 945
  Appendix A.2 Feedback on the documentation Alarms Diagnostics Manual, 07/2010, 6FC5398-8BP40-0BA0…

• Page 946: A.3 Documentation Overview

  Appendix A.3 Documentation overview Documentation overview Alarms Diagnostics Manual, 07/2010, 6FC5398-8BP40-0BA0…

Что означает ошибка при синтаксическом анализе пакета и ее причины

Появление синтаксической ошибки при установке apk, сообщает о проблемах чтения и распаковки файла. К возможным причинам относится:

• версия Android или характеристики смартфона не соответствуют минимальным требованиям приложения;
• на девайсе запрещено устанавливать софт с неизвестного источника;
• скачанный apk не загрузился до конца, был поврежден перед “заливкой” на сайт или не работал изначально;
• процесс распаковки блокирует антивирус;
• manifest файл программы был изменен;
• установочный документ был переименован.

Прежде чем приступить к исправлению ошибки, давайте посмотрим, что может послужить причиной ее возникновения. На сегодняшний день известны несколько таких причин:

1. Внесение изменений в manifest-файл приложения (например, изменение требований к версии ОС Android).
2. Повреждение или неполная закачка .apk файла.
3. Загрузка и установка сторонних приложений из неизвестных источников при отсутствии разрешения на подобные действия в настройках смартфона.
4. Несовместимость версии ОС Android или аппаратного обеспечения смартфона с требованиями устанавливаемого приложения.
5. Блокировка установки любых сторонних приложений настройками безопасности.

Дополнительные причины ошибки синтаксического анализа пакета

Если дело не в версии или синтаксическая ошибка возникает при попытке установки приложения из Play Маркет, возможны следующие варианты причины и способов исправить ситуацию:

• Во всех случаях, когда речь идет о приложении не из Play Маркет, а из стороннего файла .apk, убедитесь, что в Настройки — Безопасность на вашем устройстве включен пункт «Неизвестные источники. Разрешить установку приложений из неизвестных источников». 
• Антивирус или другое защитное ПО на вашем устройстве могут мешать установке приложений, попробуйте временно отключить или удалить его (при условии, что уверены в безопасности приложения).
• Если вы загружаете приложение со стороннего источника и сохраняете на карту памяти, попробуйте использовать файловый менеджер, перенести файл apk во внутреннюю память и запустить оттуда с помощью этого же файлового менеджера (см. Лучшие файловые менеджеры для Android). Если вы и без того открываете apk через сторонний файловый менеджер, попробуйте очистить кэш и данные этого файлового менеджера и повторить процедуру.
• Если файл .apk находится в виде вложения в письме электронной почты, то предварительно сохраните его во внутреннюю память телефона или планшета.
• Попробуйте загрузить файл приложения из другого источника: возможен вариант, когда в хранилище на каком-то сайте файл поврежден, т.е. нарушена его целостность.

Ну и в завершение еще три, варианта: иногда проблему удается решить, включив отладку по USB (хотя мне и непонятна логика), сделать это можно в меню разработчика (см. Как включить режим разработчика на Android).

Также, в том, что касается пункта про антивирусы и защитное ПО, возможны случаи, когда установке мешает и какое-то иное, «обычное», приложение. Чтобы исключить этот вариант, попробуйте установить приложение, вызывающее ошибку, в безопасном режиме (см. Безопасный режим на Android).

И последнее, может пригодиться начинающему разработчику: в некоторых случаях, если переименовать файл .apk подписанного приложения, при установке он начинает сообщать о том, что произошла ошибка при синтаксическом анализе пакета (или there was an error parsing the package в эмуляторе/устройстве на английском языке).

Почему вы должны быть осторожны с синтаксической ошибкой?

Компьютерный язык очень отличается от других форм языка. Вся программа основана на этом языке. Например, если вам нужно создать веб-страницу, и если вы упустили важные орфографические и пунктуационные знаки в программировании, вы не сможете заставить веб-страницу работать на другом конце. Чтобы избежать таких обстоятельств, вам нужно избегать ошибок в командах. Чтобы программа работала или программа работала правильно, вам нужно избегать синтаксических ошибок.

Чем синтаксическая ошибка отличается от других ошибок кодирования?

Обычно есть только две ошибки, которые могут повлиять на выполнение программы. Одним из них является синтаксическая ошибка, а другим — логическая ошибка. В то время как синтаксическая ошибка, как упоминалось ранее, является ошибкой, которую вы можете выяснить или определить, когда появляется синтаксическая ошибка. Однако логическую ошибку не так легко обнаружить. И это главное различие в синтаксической ошибке и других ошибках кодирования.

Логические ошибки не выделяются компилятором, потому что они, в действительности, соответствуют синтаксису вычислительного языка. И именно поэтому компилятору очень трудно обнаружить логическую ошибку в своей программе.

Тот факт, что компилятор не может распознать логическую ошибку, которая соответствует синтаксису языка вычислений, не означает, что программа будет работать без сбоев. Будут ошибки, и это логические ошибки, которые трудно выделить компилятору.

Можно ли исправить ошибки синтаксиса?

Конечно, они могут быть исправлены. Вам просто нужно снова получить доступ к вашей программе и перепроверить всю программу на наличие знаков препинания или орфографических ошибок. Это звучит слишком много работы, но программирование не легкая работа. Если вы хотите, чтобы ваша программа была идеальной и чтобы она работала без сбоев, вы должны следить за такими ошибками и в первую очередь избегать их.

Устранение неполадки

Убрать ошибку при синтаксическом анализе пакета можно несколькими способами.

Проверить манифест-файл

Такой способ решить проблему подходит лишь для тех, кто использует программы, позволяющие вносить изменения в манифест-файлы. Если пользователь изменил указанный файл, то понадобится его восстановление «по умолчанию». Перед тем, как что-то делать, следует удостовериться в том, что наименование .apk было подвергнуть изменению. Так, если изначальный .apk был переименован в original.apk, и пользователь назвал его original11.apk. В этом случае потребуется назвать его как прежде, то есть «Original.apk». После этого потребуется снова выполнить установку на смартфон и взглянуть, исчезла ли возникшая проблема.
В этом случае также могли появиться сложности с кодом. Установить определенную причину непросто, и универсальных способов решить ее нет. Тут или нужно разбираться длительное время и всерьез, или выбрать более простой альтернативный метод — установить приложение (в частности, с иного смартфона).

Позволить установить приложение из незнакомых веб-ресурсов

Согласно требованиям системной защиты телефон с ОС Андроид способен осуществлять запрет на установку постороннего софта с незнакомых веб-ресурсов, дозволяя делать это лишь из Гугл Плэй Маркет. Это объясняется тем, что скаченный из незнакомых источников способен нанести вред смартфону.
Поэтому когда пользователь выполняет установку файла под названием .apk, то это способно вызвать проблемный вопрос. Для исправления положения следует позволить скачивание с незнакомых сайтов. Такое положение есть в настройках, отвисающих за защиту смартфона. Для этого необходимо:

1. выполнить переход в «Настройки
   
2. затем выбрать «Безопасность
   
3. в разделе «Неизвестные источники» и выделить разблокировку скачивания — если телефон запросит подтверждение, то следует согласиться и нажать на «OK».
   После этого следует возвратиться в папку, где располагается указанный файл, нажав на него и выполнив установку.

Открытость операционной системы Android позволяет устанавливать приложения разными способами. Это можно делать как через специализированные приложения вроде Google Play, так и через APK-файлы, то есть вручную. И в тот момент, когда пользователь выбирает второй вариант установки, при попытке открыть APK на экране появляется ошибка при синтаксическом анализе пакета. Проблема является довольно частой, но, к счастью, поддается решению. Давайте посмотрим, что мы можем сделать при возникновении синтаксической ошибки.

Что такое синтаксический анализ пакета

Сначала разберемся, с чем мы имеем дело, и какое отношение к Android имеет синтаксис, знакомый нам по школьному курсу русского языка. В лингвистике синтаксической ошибкой называют нарушение связи слов в предложении. В программировании это понятие имеет схожее значение и, если не углубляться в подробности, ошибка синтаксического анализа на Андроид — проблема, вызванная отсутствием совместимости между действующей конфигурацией операционной системы и APK (пакетом).

⚡ Подпишись на Androidinsider в Дзене, где мы публикуем эксклюзивные материалы

Подобного рода неполадки чаще всего дают о себе знать на устройствах со старой версией Android. Но это не значит, что исправить ошибку синтаксического анализа пакета можно только обновлением Андроид. Просто старые версии операционной системы имеют ряд особенностей, которые не позволяют установить каждый APK, несмотря на заявленную совместимость.

Как исправить синтаксический анализ пакета

Поскольку ошибка при синтаксическом анализе пакета Андроид возникает в процессе ручной установки APK, в первую очередь рекомендую инсталлировать приложение через магазин Google Play. Там все файлы проверяются на вирусы, а несовместимый софт даже не отображается в списке. Если ваше приложение отсутствует в магазине, попробуйте установить APK в соответствии с рекомендациями, изложенными здесь. Если и это не поможет — действуйте по нашей инструкции, и решение точно найдется.

❗ Поделись своим мнением или задай вопрос в нашем телеграм-чате

Как переименовать файл

Как я уже сказал, ошибка при синтаксическом анализе обычно возникает на смартфонах со старым Android. Особенностью устройств на ранних версиях операционной системы является то, что они не могут прочитать содержимое APK-файла с большим количеством символов. Тот же Android 7 вводят в ступор лишние точки в названии. Следовательно, для решения проблемы нужно переименовать файл:

1. Найдите проблемный APK.
2. Выделите файл.
3. Нажмите кнопку «Еще».
4. Выберите опцию «Переименовать».
5. Присвойте файлу короткое имя, состоящее из латинских символов.

С высокой долей вероятности после внесения изменений в название файла ошибка синтаксического анализа пакета при установке исчезнет. Если нет — воспользуйтесь следующим вариантом решения проблемы.

Файл поврежден

Также неполадки при синтаксическом анализе пакета бывают вызваны повреждением APK. Что я имею в виду? Во-первых, файл мог загрузиться не до конца. Естественно, в таком случае установочный пакет будет не полным, и смартфон не сможет прочитать его содержимое. Почему это произошло — другой вопрос. Либо в процессе загрузки прервалось интернет-соединение, либо на смартфоне закончилась память. Что делать в таком случае — читайте тут.

🔥 Загляни в телеграм-канал Сундук Али-Бабы, где мы собрали лучшие товары с АлиЭкспресс

Еще не стоит исключать вероятность изначального повреждения файла. То есть APK мог быть залит на сайт, откуда вы его скачивали, в неисправном виде. Единственная рекомендация в такой ситуации — скачать APK-файл через другой источник. В конце я приведу несколько примеров, откуда загрузить APK бесплатно и безопасно.

Старая версия Андроид

Конечно, проблема могла возникнуть и по причине устаревшей версии Android. Да, подавляющее большинство приложений работает и на Android 7, но с каждым обновлением системные требования становятся более жесткими. Поэтому настоятельно рекомендую проверить версию Андроид на телефоне, в чем вам поможет отдельный материал. Затем сопоставьте ее с требованиями, указанными на странице приложения.

Отмечу также, что многие люди жалуются на ошибку при синтаксическом анализе пакета на телевизоре. Если на вашем ТВ-приемнике установлена операционная система Android TV, то при установке APK обязательно проверяйте совместимость. Приложение изначально должно быть предназначено для телевизионного Андроид.

Как переместить файл

Если при синтаксическом анализе пакета возникла неполадка, убедитесь, что сам APK-файл находится во внутренней памяти телефона. Конечно, приложения можно устанавливать и с карты памяти. Однако, если вы покупали дешевую MicroSD-карту, такая возможность будет заблокирована из-за низкой скорости записи или повреждения файловой системы. Для решения проблемы нужно просто переместить файл во внутреннюю память:

1. Выделите APK-файл.
2. Нажмите кнопку «Переместить».
3. Укажите любую папку на внутреннем накопителе и подтвердите перемещение.

Наконец, выделю еще несколько факторов, которые теоретически могли стать причиной появления ошибки при синтаксическом анализе пакета Android. Это конфликт с одним из установленных на телефоне приложений и блокировка неизвестных APK антивирусом. Обязательно учитывайте данные факторы.

⚡ Подпишись на Androidinsider в Пульс Mail.ru, чтобы получать новости из мира Андроид первым

Где скачать APK

Итак, у APK ошибка при синтаксическом анализе пакета очень часто возникает по причине неисправного или поврежденного файла. Минимизировать риски помогают специальные веб-магазины, откуда можно бесплатно скачать APK:

• APKMirror;
• APKPure;
• APK Store.

Подробнее о каждом из этих магазинов мы рассказывали здесь, так что не забывайте читать и другие материалы на нашем сайте, которые помогут вам оставаться в курсе новостей, а также решить распространенные проблемы.

Оглавление:

• Коды ошибок частотника Siemens G120
• Типы сообщений
• Индикация
• Коды отказов частотника
• F01000 – аппаратная/программная ошибка
• F01001 – ошибка FloatingPoint
• F01002 – аппаратная/программная ошибка
• F01003 – Задержка квитирования при обращении к памяти
• F01010 – Неизвестный тип привода
• F01018 – Запуск прерван многократно
• F01023 – тайм-аут ПО внутренний
• F01054 – высокая вычислительная нагрузка
• F01068 – высокая загруженность памяти
• F01250 – ошибка данных CU-EEPROM Read-Only
• F06922 – выпадение фазы тормозного резистора
• F07011 – перегрев двигателя
• F07220 – нет управления через PLC
• F07300 – отсутствует подключение сетевого контактора
• F07801 – перегрузка двигателя по току
• F07807 – обнаружено коротко замыкание / замыкание на землю
• F07900 (N, A) — Привод: двигатель заблокирован
• F07902 (N, A) — Привод: двигатель опрокинут
• A07910 (N) — Привод: перегрев двигателя
• F30002 Силовая часть: напряжение промежуточного контура перенапряжение
• F30003 Силовая часть: пониженное напряжение промежуточного контура
• F30004 Силовая часть: перегрев радиатора инвертора
• F30005 Силовая часть: перегрузка I2t
• F30011 Силовая часть: выпадение фазы сети в силовой цепи
• F30012 Силовая часть: датчик температуры радиатор обрыв кабеля
• F30013 Силовая часть: датчик температуры радиатор короткое замыкание
• F30017 Силовая часть: слишком частое срабатывание ограничения тока аппаратного обеспечения
• F30021 Силовая часть: замыкание на землю
• F30024 Силовая часть: перегрев, температурная модель
• F30025 Силовая часть: перегрев чипа

Преобразователь частоты (ПЧ) – сложное устройства управления электрическим двигателем. В случае нештатных и аварийных ситуаций ПЧ выдает сообщения об аварии или предупреждении на панель частотника или по линии связи в контроллер, так же может остановить двигатель во избежание поломок оборудования. На панели частотника выдается код ошибки. В данной статье приведены коды ошибок, их детальное описание и возможные причины появления.

Типы сообщений

Существует несколько типов сообщений:

• A – предупреждение, выводится в случае появления неаварийных ситуаций, на которые необходимо обратить внимание. Сброс при исчезновении причины предупреждения
• F – ошибка, выводится в случае появления аварийных ситуаций. Сброс при исчезновении причины отказа и подтверждения данного отказа.
• N – сообщение отсутствует или «внутреннее сообщение».
• C – сообщение безопасности.

Предупреждение. Код сопровождается буквой A. Выводятся в случае появления неаварийных ситуаций, на которые стоит обратить внимание. Сбрасываются при исчезновении причины предупреждения.

Отказ. Код сопровождается буквой F. Выводятся в случае появления аварийных ситуаций. Сбрасываются при исчезновении причины отказа и подтверждения данного отказа.

Индикация

На частотнике присутствует индикатор с обозначением RDY с помощью которого можно определить наличие отказов.

Мигающий красный индикатор один раз в пол секунды – обозначает отказ.

Коды отказов частотника:

Это – лишь часть списка кодов ошибок, которые описаны в руководстве. Если требуемый код ошибки не был описан в статье – необходимо воспользоваться официальным руководством пользователя.

F01000 – аппаратная/программная ошибка

Возможные причины:

• Возникла ошибка программного обеспечения или внутренняя программная ошибка.

Возможные решения:

• Обработать буфер ошибок (r0945).
• Выполнить POWER ON для всех компонентов (выключить/включить).
• При необходимости проверить данные в энергонезависимой памяти (к примеру, на карте памяти).
• Обновить микропрограммное обеспечение до новой версии.
• Связаться с «горячей линией».
• Заменить управляющий модуль.

F01001 – ошибка FloatingPoint

Возможные причины:

• При работе с типом данных FloatingPoint произошла ошибка.

Возможные решения:

• Выполнить POWER ON для всех компонентов (выключить/включить).
• Проверить конфигурацию сигналов блоков для FBLOCKS.
• Проверить конфигурацию и сигналы схем для DCC.
• Обновить микропрограммное обеспечение до новой версии.
• Связаться с «горячей линией»

F01002 – аппаратная/программная ошибка

Возможные причины:

• Возникла ошибка программного обеспечения или внутренняя программная ошибка.

Возможные решения:

• Выполнить POWER ON для всех компонентов (выключить/включить).
• Обновить микропрограммное обеспечение до новой версии.
• Связаться с «горячей линией».

F01003 – Задержка квитирования при обращении к памяти

Возможные причины:

• При обращении к ячейке памяти возникал ошибка.

Возможные решения:

• выполнить POWER ON для всех компонентов (выключить/включить).
• связаться с «горячей линией».

F01010 – Неизвестный тип привода

Возможные причины:

• Был найден неизвестный тип привода.

Возможные решения:

• Заменить блок питания.
• Выполнить POWER ON (выключить/включить).
• Обновить микропрограммное обеспечение.
• Связаться с «горячей линией»

F01018 – Запуск прерван многократно

Возможные причины:

• Загрузка модуля была отменен многократно. Поэтому выполняется загрузка модуля с заводскими установками.
• Возможные причины отмены загрузки:
  • Прерывание подачи питания.
  • Сбой CPU.
  • Недействительное параметрирование.

Возможные решения:

• Выполнить POWER ON (выключить/включить). После включения модуль снова загружается с правильными параметрами (при наличии таковых).
• Восстановить правильное параметрирование. Примеры:
  • Выполнить первый ввод в эксплуатацию, сохранить параметры, выполнить POWER ON (выключить/включить).
  • Загрузить другую правильную резервную копию параметров (к примеру, с карты памяти), сохранить параметры, выполнить POWER ON (выключить/включить).

Указание: При повторном сборе эта ошибка снова появляется после нескольких отмененных загрузок.

F01023 – тайм-аут ПО внутренний

Возможные причины:

• Возник внутренний программный тайм-аут.

Возможные решения:

• Выполнить POWER ON для всех компонентов (выключить/включить).
• обновить микропрограммное обеспечение до новой версии.
• связаться с «горячей линией».

F01054 – высокая вычислительная нагрузка:

При наличии этой ошибки сохранение параметров невозможно

возможные причины:

• Слишком высокая вычислительная нагрузка;
• Слишком высокая пиковая нагрузка.

Возможные решения:

• Снизить нагрузку на процессор приводного устройства до уровня ниже 100 %.
• Проверить и при необходимости настроить время выборки.
• Деактивировать функциональные модули.
• Деактивировать приводные объекты.
• Удалить приводные объекты из заданной топологии.
• Соблюдать правила топологии DRIVE-CLiQ и при необходимости изменить топологию DRIVE-CLiQ. При использовании Drive Control Chart (DCC) или свободных функциональных блоков (FBLOCKS) действует:
  • Нагрузка на процессор отдельных динамических групп на приводном объекте может быть считана в r21005 (DCC) и r20005 (FBLOCKS).
  • При необходимости изменить согласование динамической группы таким образом, чтобы время выборки увеличилось.
  • При необходимости сократить число циклически вычисляемых блоков (DCC) или функциональных блоков (FBLOCKS).

F01068 – высокая загруженность памяти.

Возможные причины:

• Слишком высокая загруженность области памяти данных

Возможные решения:

• Деактивировать функциональный модуль.
• Деактивировать приводной объект.
• Удалить приводной объект из заданной топологии.

F01250 – ошибка данных CU-EEPROM Read-Only

Возможные причины:

• Ошибка при чтении данных Read-Only EEPROM на устройстве управления.

Возможные решения:

• выполнить POWER ON.
• заменить устройство управления

F06922 – выпадение фазы тормозного резистора;

Возможные причины:

• Обнаружено выпадение фазы для тормозного резистора.

Возможные решения:

• Проверить подводку тормозных резисторов.

F07011 – перегрев двигателя;

Возможные причины:

• двигатель перегружен.
• слишком высокая окружающая температура двигателя.
• обрыв провода датчика или отсутствие подключения.

Возможные решения:

• Снизить нагрузку двигателя.
• Проверить внешнюю температуру и вентиляцию двигателя.
• Проверить проводку и соединение PTC или биметаллического NC.

F07220 – нет управления через PLC

Возможные причины:

• Сигнал «Управление через PLC» отсутствует при работе. –
• неправильное подключение бинекторного входа для «Управление через PLC» (p0854).
• СЧПУ верхнего уровня отменила сигнал «Управление через PLC».
• передача данных через полевую шину (Master/привод) была прервана

Возможные решения:

• Проверить подключение бинекторного входа для «Управления через PLC».
• проверить и при необходимости включить сигнал «Управление через PLC».
• проверить передачу данных через полевую шину (Master/привод).

F07300 – отсутствует подключение сетевого контактора;

Возможные причины:

• Сетевой контактор не включен в течении времени в p0861;
• Сетевой контактор не выключен в течении времени в p0861;
• Сетевой контактор отключился при работе;
• Сетевой контактор включен, хотя преобразователь отключен.

Возможные решения:

• Проверить установку p0860.
• Проверить цикл подтверждения сетевого контактора.
• Увеличить время контроля в p0861.

F07800 – отсутствует силовая часть

Возможные причины:

• Чтение параметров силовой части невозможно или в силовой части нет сохраненных параметров
• выбрана неправильная топология при вводе в эксплуатацию.

Возможные решения:

• Выполнить ПОДАЧУ ПИТАНИЯ для всех компонентов (выключить/включить).
• Проверить и при необходимости заменить силовую часть.
• Проверить и при необходимости заменить управляющий модуль.
• После исправления топологии снова выполнить загрузку параметров с помощью ПО для ввода в эксплуатацию.

F07801 – перегрузка двигателя по току

Возможные причины:

• Эффективная граница тока установлена слишком низкой;
• Регулятор тока настроен неправильно;
• Режим U/f: время разгона установлено слишком маленьким или слишком высокая нагрузка;
• Режим U/f: короткое замыкание в кабеле двигателя или замыкание на землю;
• Режим U/f: ток двигателя не подходит к току силовой части;
• Включение на вращающийся двигатель без функции «рестарт на лету» (p1200).

Возможные решения:

• Проверить границы тока.
• Векторное управление: проверить регулятор тока.
• Управление U/f: проверить ограничительный регулятор тока.
• Увеличить рампу разгона или уменьшить нагрузку.
• Проверить двигатель и кабели двигателя на предмет короткого замыкания и замыкания на землю.
• Проверить двигатель на предмет соединения звезда/треугольник и параметрирования шильдика.
• Проверить комбинацию силовой части и двигателя.
• Выбрать функцию рестарта на лету, если происходит включение на вращающийся двигатель

F07807 – обнаружено коротко замыкание / замыкание на землю.

Возможные причины:

• На выходных клеммах преобразователя со стороны двигателя было обнаружено межфазное короткое замыкание или замыкание на землю.

Указание: Перепутывание кабелей питания и двигателя также определяется как короткое замыкание со стороны двигателя. Проверка на предмет замыкания на землю функционирует только в состоянии покоя двигателя. Включение на не размагниченный или только частично размагниченный двигатель может определяться как замыкание на землю.

Возможные решения:

• Проверить соединение преобразователя со стороны двигателя на предмет наличия межфазного короткого замыкания.
• Исключить перепутывание кабеля питания и двигателя.
• Проверить на предмет замыкания на землю.
• Не включать разрешение импульсов на вращающийся двигатель без активированной функции «Рестарт на лету».
• Увеличить продолжительность размагничивания.
• Для обеспечения состояния покоя увеличить время задержки гашения импульсов.
• При необходимости деактивировать контроль.

F07900 (N, A) — Привод: двигатель заблокирован

Возможные причины:

• Двигатель работает дольше, чем время в p2177, на границе момента вращения и ниже установленного порога числа оборотов в p2175. Это сообщение может появиться, если число оборотов колеблется, и выход регулятора числа оборотов постоянно кратковременно доходит до ограничения. Возможно и то, что тепловой контроль силовой части уменьшает границу тока (см. p0290) и из-за этого происходит торможение двигателя.

Возможные решения:

• Проверить двигатель на предмет свободного движения.
• Проверить эффективную границу момента вращения.
• Проверить и при необходимости исправить параметры сообщения «Двигатель заблокирован».
• Проверить разрешения направления вращения при рестарте двигателя на лету.
• Для управления U/f: проверить границы тока и время разгона.

F07902 (N, A) — Привод: двигатель опрокинут

Возможные причины:

• Было обнаружено, что двигатель опрокинут дольше, чем установлено в p2178.

Возможные решения:

• Следует убедиться, что как идентификация параметров двигателя, так и измерение при вращении, были выполнены.
• Проверить, не опрокидывается ли привод в управляемом режиме или когда заданное значение скорости еще ноль, только нагрузкой. Если да, то увеличить заданное значение тока через p1610.
• Если время возбуждения двигателя (p0346) было сильно уменьшено и привод опрокидывается при включении и немедленном начале движения, то снова увеличить p0346.
• Проверить, не имеет ли место выпадение фазы сети у силовых частей PM230, PM250, PM260.
• Проверить, не отсоединена ли электропроводка к двигателю (см. A07929).
• Если ошибки отсутствуют, то можно увеличить отказоустойчивость (p1745) или время задержки (p2178).
• Проверить предельный ток. При слишком низких предельных токах намагничивание привода невозможно.
• Если возникает ошибка со значением 2 при очень быстром разгоне двигателя в области ослабления поля, то путем уменьшения p1596 или p1553 можно сократить отклонение между заданным и фактическим значением потока и тем самым сообщение не будет появляться.

A07910 (N) — Привод: перегрев двигателя

Возможные причины:

• Измеренная температура двигателя или температура тепловой модели двигателя превысила порог предупреждения (p0604).

Возможные решения:

• Проверить нагрузку двигателя.
• Проверить температуру окружающей среды двигателя.
• Проверить KTY84.
• Проверить перегревы тепловой модели двигателя.

F30002 Силовая часть: напряжение промежуточного контура перенапряжение

Возможные причины:

• Силовая часть обнаружила перенапряжение в промежуточном контуре.
• Двигатель рекуперирует слишком много энергии.
• Слишком высокое напряжение питающей сети.
• Фаза сети прервана.
• Регулирование напряжения промежуточного контура отключено.
• Слишком высокая или низкая динамика регулятора напряжения промежуточного контура.

Возможные решения:

• Увеличить время торможения.
• Установить время сглаживания. Это рекомендуется прежде всего в режиме U/f, чтобы разгрузить регулятор напряжения промежуточного контура при коротком времени торможения задатчика интенсивности.
• Активировать регулятор напряжения промежуточного контура.
• Согласовать динамику регулятора напряжения промежуточного контура.
• Проверить напряжение питающей сети и установку в p0210.
• Проверить и исправить назначение фаз на силовой части.
• Проверить фазы сети.

F30003 Силовая часть: пониженное напряжение промежуточного контура

Возможные причины:

• Силовая часть определила пониженное напряжение в промежуточном контуре.
• Отказ питания.
• Напряжение сети ниже допустимого значения.
• Прерывание фазы сети.

Возможные решения:

• Проверить напряжение сети.
• Проверить фазы сети.

F30004 Силовая часть: перегрев радиатора инвертора

Возможные причины:

• Температура радиатора силовой части превысила допустимое предельное значение.
• Недостаточная вентиляция, отказ вентилятора.
• Перегрузка. — слишком высокая внешняя температура.
• Слишком высокая частота импульсов.

Возможные решения:

• Проверить, работает ли вентилятор.
• Проверить компоненты вентилятора.
• Проверить, находится ли внешняя температура в допустимом диапазоне.
• Проверить нагрузку двигателя.
• Уменьшить частоту импульсов, если она выше номинальной частоты импульсов.

Внимание: Эта ошибка может быть квитирована только после выхода за нижнюю границу порога предупреждения для A05000.

F30005 Силовая часть: перегрузка I2t

Возможные причины:

• Перегрузка силовой части (r0036 = 100 %).
• Допустимый ном. ток силовой части был превышен недопустимо долго.
• Допустимый нагрузочный цикл не был соблюден.

Возможные решения:

• Снизить длительную нагрузку.
• Согласовать нагрузочный цикл.
• Проверить ном. токи двигателя и силовой части.
• Уменьшить границу тока (p0640).
• При работе с характеристикой U/f: уменьшить постоянную времени интегрирования токоограничительного регулятора (p1341).

F30011 Силовая часть: выпадение фазы сети в силовой цепи

Возможные причины:

• Выпадение фазы сети.
• Недопустимая асимметрия 3 фаз сети.
• Емкость конденсатора промежуточного контура создает резонансную частоту с индуктивностью сети и возможно с интегрированным в силовую часть дросселем.
• Срабатывание предохранителя фазы силовой цепи.
• Выпадение фазы двигателя.

Возможные решения:

• Проверить предохранители силовой цепи.
• Проверить, не искажает ли однофазный потребитель напряжения сети.
• Рассогласовать резонансную частоту с индуктивностью сети путем подключения сетевого дросселя.
• Погасить резонансную частоту с индуктивностью сети путем программного переключения на компенсацию напряжения промежуточного контура или усиления сглаживания. Но это может ухудшить пульсацию момента на двигателе.
• Проверить электропроводку к двигателю.

F30012 Силовая часть: датчик температуры радиатор обрыв кабеля

Причина:

• Соединение с датчиком температуры радиаторов в силовой части прервано.

Решение:

• Связаться с изготовителем.

F30013 Силовая часть: датчик температуры радиатор короткое замыкание

Причина:

• Датчик температуры радиатора в силовой части замкнут накоротко.

Решение:

• Связаться с изготовителем.

F30017 Силовая часть: слишком частое срабатывание ограничения тока аппаратного обеспечения

Возможные причины:

• Слишком частое срабатывание ограничения тока аппаратного обеспечения в соответствующей фазе. Число допустимых превышений зависит от вида и типа силовой части.
• Регулирование спараметрировано неправильно.
• Ошибка в двигателе или в силовых кабелях.
• Превышена макс. допустимая длина силовых кабелей.
• Слишком высокая нагрузка двигателя.
• Неисправность силовой части.

Возможные решения:

• Проверить параметры двигателя.
• Проверить тип соединения двигателя (звезда/треугольник).
• Проверить нагрузку двигателя.
• Проверить соединения силовых кабелей.
• Проверить силовые кабели на предмет короткого замыкания или замыкания на землю.
• Проверить длину силовых кабелей.
• Заменить силовую часть.

F30021 Силовая часть: замыкание на землю

Возможные причины:

• Замыкание на землю в силовых кабелях. –
• Замыкание на землю на двигателе. –
• Трансформатор неисправен. –
• Зажимающие тормоз является причиной срабатывания аппаратного контроля постоянного тока. –
• Короткое замыкание на тормозном резисторе. Значение ошибки (r0949, дес. интерпретация): 0: —
• Сработал аппаратный контроль постоянного тока. –
• Короткое замыкание на тормозном резисторе. > 0:
• Величина суммарного тока [32767 = 271 % ном. Тока

Возможные решения:

• Проверить соединение силовых кабелей. –
• Проверить двигатель. –
• Проверить преобразователь тока. –
• Проверить кабели и контакты соединения тормоза (возможен обрыв кабеля). –
• Проверить тормозной резистор. Смотри также: p0287

F30024 Силовая часть: перегрев, температурная модель

Возможные причины:

• Разность температур между радиатором и чипом превысила допустимое предельное значение.
• Допустимый нагрузочный цикл не соблюден.
• Недостаточное вентилирование, выход из строя вентилятора.
• Перегрузка.
• Внешняя температура слишком высока.
• Частота импульсов слишком высока.

Возможные решения:

• Согласовать нагрузочный цикл.
• Проверить, работает ли вентилятор.
• Проверить фильтрующие элементы.
• Проверить, в допустимом ли диапазоне находится температура окружающей среды.
• Проверить нагрузку двигателя.
• Уменьшить частоту модуляции, если она выше номинальной.
• Если активно торможение на постоянном токе: уменьшить тормозной ток (p1232).

F30025 Силовая часть: перегрев чипа

Возможные причины:

• Температура чипа полупроводников превысила допустимое предельное значение.
• Допустимый нагрузочный цикл не был выдержан.
• Недостаточная вентиляция, отказ вентилятора.
• Перегрузка.
• Слишком высокая внешняя температура.
• Слишком высокая частота импульсов.

Возможные решения:

• согласовать нагрузочный цикл.
• проверить, работает ли вентилятор.
• проверить элементы вентилятора.
• проверить, находится ли внешняя температура в допустимом диапазоне.
• проверить нагрузку двигателя.
• уменьшить частоту импульсов, если она выше ном. частоты импульсов.

Внимание: эта ошибка может быть квитирована только после выхода за нижнюю границу порога предупреждения для предупреждения A05001.

Отзывы о пройденном обучении

Синтаксическая ошибка сообщения об ошибке рядом с неожиданным токеном `(‘ возникает в среде типа Unix, Cygwin и в интерфейсе командной строки в Windows. Эта ошибка, скорее всего, будет вызвана при попытке запустить сценарий оболочки, который был отредактирован или созданный в старых системах DOS / Windows или Mac.

Это сообщение об ошибке также появляется, когда вы вводите команды в командной строке Linux для повседневных задач, таких как копирование файлов вручную и т. Д. Основные причины появления этого сообщения об ошибке либо из-за неправильного синтаксиса, либо из-за проблемы ОС при интерпретации команд другой системы / оболочка.

Что вызывает синтаксическую ошибку рядом с неожиданным токеном `(‘?

Причины этого сообщения об ошибке очень разнообразны и не могут быть перечислены в одной статье, так как существуют тысячи возможных ошибок синтаксиса при выполнении команд. Основные причины этой ошибки:

• Неверный синтаксис при выполнении любой команды на любой платформе. Либо вы неправильно используете команду, либо ввели неправильный синтаксис.
• Оболочка несовместима между системами Unix / DOS.
• Возникли проблемы с запуском сценария оболочки bash из другого источника .

В этой статье мы предполагаем, что вы знаете основы программирования и имеете представление о том, что делаете. Если вы новичок, лучше всего следовать подробным инструкциям по языку / команде, которую вы пытаетесь выполнить. Вероятно, вы ошиблись в синтаксисе.

Решение 1. Проверка синтаксиса и формата команд

Первая и основная причина, по которой вы можете получить это сообщение об ошибке, — это неправильный синтаксис в вашем коде или несоблюдение точного формата команд. Каждая команда имеет предопределенный формат, который вы можете увидеть в ее документации. Некоторые параметры являются необязательными, другие — обязательными.

Кроме того, следует уделять особое внимание дополнительному пространству , использованию двойных кавычек и обязательным параметрам. Если какие-либо из них отсутствуют или были объявлены неправильно, вы не сможете выполнить свой код.

Например, вместо следующего кода

[mycom7] # ./ctopo.sh um_test1 [(1,2), (2,1)]

Вам нужно выполнить его как

[mycom7] # ./ctopo.sh um_test1 "[(1,2), (2,1)]"

Также убедитесь, что вы правильно выполняете свои команды / сценарий оболочки, если он занимает несколько строк.

Из-за типа параметра необходимы двойные кавычки. Дополнительное пространство также может испортить ваш код и вызвать сообщение об ошибке. Убедитесь, что вы проверили официальную документацию команды, которую вы выполняете, и посмотрите, есть ли там проблема.

Решение 2. Устранение неполадок сценария оболочки

Если вы используете сценарий оболочки, который работает в исходной системе, но возвращает ошибку в целевой системе, вы можете устранить неполадки сценария, проверив переменные, которые хранятся во время выполнения, а затем посмотреть, что вызывает проблему. Это очень частая причина, поскольку в некоторых случаях оболочка пытается интерпретировать непечатаемый символ.

Попробуйте запустить оболочку с параметром vx. Это покажет нам, какие команды выполняются и какие значения хранятся в скрипте. Здесь вы можете устранять неполадки и диагностировать, что не так.

Например, выполните скрипт в терминале после включения vx как:

# sh -vx ./test_script5.sh

Вы можете проверить содержимое скрипта, используя команду cat как:

# cat test_script5.sh

Решение 3. Использование команды dos2unix.exe

В текстовых файлах Windows / DOS новая строка представляет собой комбинацию символа возврата каретки ( r), за которым следует перевод строки ( n). В Mac (до Mac OS X) для переноса строки использовался простой возврат каретки ( r). Unix / Linux и Mac OS X используют перевод строки ( n). Если вы используете Cygwin, он не сможет обработать сценарии, созданные DOS / Windows и более ранними версиями Mac из-за дополнительного символа возврата каретки ( r).

Здесь вы можете создать команду ‘dos2unix.exe’, которая преобразует скрипт в правильный формат, а затем вы можете выполнить его без каких-либо проблем.

В заключение вам необходимо изучить свои команды и тип используемой платформы и убедиться, что нет никаких расхождений. Поскольку мы не можем охватить все возможные варианты, у вас будет представление о том, какие ошибки могут возникнуть и как их исправить.

Чаще всего ошибка появляется на старых версиях Андроид

Содержание

• 1 Что такое синтаксический анализ пакета
• 2 Как исправить синтаксический анализ пакета
  • 2.1 Как переименовать файл
  • 2.2 Файл поврежден
  • 2.3 Старая версия Андроид
  • 2.4 Как переместить файл
• 3 Где скачать APK

Попробуйте установить приложение через Google Play

Присвойте файлу имя попроще

Возможно, стоит задумать об обновлении ОС или покупке нового смартфона

Устанавливайте приложения через APK, которые хранятся во внутренней памяти