Channel Errors
Error(Hex) | Error(Dec) | Error type | Description |
---|---|---|---|
4101 | 16641 | Parameter | Group index not allowed The location within the channel specified for a group is not allowed. |
4102 | 16642 | Address | Null pointer The pointer to the group is invalid. This is usually a consequence of an error at system start-up. |
4103 | 16643 | Internal | Missing process image It is not possible to exchange data with the PLC. |
4104 | 16644 | Parameter | M-function index not allowed Unacceptable M-function (not 0...159) detected at the execution level. |
4105 | 16645 | Memory | No memory No more system memory is available. This is usually the result of another error. |
4106 | 16646 | Function | Not ready The function is not presently available, because a similar function is already being processed. Usually this is a result of access conflicts: more than one instance wants to issue commands to the channel. This can, for example, be the consequence of an incorrect PLC program. |
4107 | 16647 | Function | Function/command not supported A requested function or command is not supported by the channel. |
4108 | 16648 | Parameter | Invalid parameter while starting Parameters to start the channel (TwinCAT-Start) are invalid. Typically there is an invalid memory size or channel type requested. |
4109 | 16649 | Function | Channel function/command is not executable A channel function e.g. interpreter start is not executable because the channel is already busy, no program is loaded or in an error state. |
410A | 16650 | Function | ItpGoAhead not executable The requested ItpGoAhead command is not executable, because the interpreter is not executing a decoder stop. |
4110 | 16656 | Parameter | Error opening a file The specified file does not exist. Example: NC program unknown. |
4111 | 16657 | NC programming | Syntax error during loading The NC has found a syntax error when loading an NC program. |
4112 | 16658 | NC programming | Syntax error during interpretation The NC has found a syntax error when executing an NC program. |
4113 | 16659 | NC programming | Missing subroutine The NC has found a missing subroutine while loading. |
4114 | 16660 | Memory | Loading buffer of interpreter is too small The capacity of the interpreter loading buffer has been exceeded. |
4115 | 16661 | Internal | Symbolism Reserved, currently not used. |
4116 | 16662 | Internal | Symbolism Reserved, currently not used. |
4117 | 16663 | NC programming | Subroutine incomplete The header of the subroutine is missing. |
4118 | 16664 | NC programming | Error while loading the NC program The maximum number of loadable NC programs has been reached. |
4119 | 16665 | NC programming | Error while loading the NC program The program name is too long. |
4120 | 16672 | NC programming | Divide by Zero The NC encountered a computation error during execution: division by 0. |
4121 | 16673 | NC programming | Invalid circle parameterization The NC has detected a calculation error during processing: the specified circle is not calculable. |
4122 | 16674 | NC programming | Invalid FPU-Operation The NC encountered an invalid FPU-Operation during execution. This error occurs e.g. by calculating the square root of a negative number |
4130 | 16688 | NC programming | Stack overflow: Subroutines The NC has detected a stack overflow while processing: Too many subroutine levels. |
4131 | 16689 | NC programming | Stack underflow: Subroutines The NC has detected a stack underflow while processing: Too many subroutine return commands. |
4132 | 16690 | NC programming | Stack overflow: Arithmetic unit The NC has detected a stack overflow during processing: the calculation is too complex or is not written correctly. |
4133 | 16691 | NC programming | Stack underflow: Arithmetic unit The NC has detected a stack underflow during processing: The calculation is too complex or is not written correctly. |
4140 | 16704 | Parameter | Register index not allowed The NC has detected an invalid register index during processing: The program contains an invalid specification (not R0...R999) or a pointer register contains an invalid value. |
4141 | 16705 | NC programming | G-function index not allowed The NC has encountered an unacceptable G-function (not 0...159) during execution. |
4142 | 16706 | NC programming | M-function index not allowed The NC has encountered an unacceptable M-function (not 0...159) during execution. |
4143 | 16707 | NC programming | Extended address specification not allowed The NC has encountered an unacceptable extended address (not 1...9) during execution. |
4144 | 16708 | NC programming | Index to the internal H-function not allowed The NC has encountered an unacceptable internal H-function in the course of processing. This is usually a consequence of an error during loading. |
4145 | 16709 | Parameter | Machine data value not allowed While processing instructions the NC has detected an impermissible value for the machine data (MDB) (not 0…7). |
4150 | 16720 | Parameter | Tool compensation parameters cannot be changed here The NC has encountered an unacceptable change of parameters for the tool compensation during execution. This can be, for example, a changed tool radius while a circle was programmed. |
4151 | 16721 | Parameter | Cannot calculate tool compensation The NC has encountered an error by the calculation of the tool compensation. |
4152 | 16722 | NC programming | Tool compensation The plane for the tool compensation cannot be changed here. This error occurred for instance by changing the plane when the tool radius compensation is turned on or active. |
4153 | 16723 | NC programming | Tool compensation The D-Word is missing or invalid by turning on the tool compensation. |
4154 | 16724 | NC programming | Tool compensation The specified tool radius is invalid because the value is less or equal zero. |
4155 | 16725 | NC programming | Tool compensation The tool radius cannot be changed here |
4156 | 16726 | Internal | Tool compensation The Collision Detection Table is full. |
4157 | 16727 | Internal | Tool compensation An internal error has occurred when switching on the bottleneck detection |
4158 | 16728 | Internal | Tool compensation An internal error occurred in the bottleneck detection: Update Reversed Geo failed. |
4159 | 16729 | NC programming | Tool compensation An unexpected combination of geometry types with bottleneck detection turned on was detected. |
415A | 16730 | NC programming | Tool compensation The programmed inner circle is smaller than the cutter radius. |
415B | 16731 | NC programming | Tool compensation The bottleneck detection recognized a contour violation. |
415C | 16732 | Memory | No memory The table for corrected entries is full. |
415D | 16733 | Memory | No memory The input table for tangential following is full. |
415E | 16734 | Memory | No memory The executing table for tangential following is full. |
415F | 16735 | Internal | Geometry calculation The geometric entry for the tangential following cannot be calculated. |
4160 | 16736 | Internal | Reserved Reserved, currently not used. |
4161 | 16737 | Internal | Reserved Reserved, currently not used. |
4162 | 16738 | Parameter | Interpolation rules can not be determined The actual active interpolation rules (G-Code), zero offset shifts or rotation cannot be detected. |
4170 | 16752 | NC programming | Error loading: invalid parameter The NC has found an invalid parameter while loading an NC program. |
4171 | 16753 | Internal | Invalid contour start position The NC has detected a calculation error during processing: The specified contour cannot be calculated because the start position is not on the contour. |
4172 | 16754 | Internal | Reverse: invalid table index The NC encountered an invalid internal entry index during execution of the retrace function. |
4173 | 16755 | NC programming | Invalid G code Invalid default G code. Wrong expression/syntax in the default G code. |
4174 | 16756 | NC programming | Error opening the G code file Error opening the default G code file. |