ID-range 21250-21499
21250 | Active axis tracking on program end. | |||
| Description | At program end (M02, M30) the axis tracking selected by the command #CAXTRACK ON is still active. | ||
Reaction | Class | 1 | NC program processing is continued. | |
Solution | Class | 1 | Edit NC program. Enter #CAXTRACK OFF before program end. | |
Error type | 1, Error message from NC-program. | |||
|
21251 | Missing comma between axis name and log. axis number. | |||
| Description | Within the axis exchange command between the axis name and the logical axis number a comma has to be programmed. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modifiy the axis exchange command. | |
Error type | 1, Error message from NC-program. | |||
|
21252 | Missing comma between log. axis number and axis index. | |||
| Description | Within the axis exchange command between the logical axis number and the axis index a comma has to be programmed. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the axis exchange command. | |
Error type | 1, Error message from NC-program. | |||
|
21253 | Logical axis number exceeds range of data format. | ||||
| Description | Within the axis exchange command a logical axis number is programmed, which exceeds the permissible data range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the axis exchange command. | ||
Parameter | %1: | Incorrect value [-] | |||
Incorrect logical axis number of the axis in the axis exchange command. P-AXIS-00016, P-CHAN-00035 | |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21254 | Axis index exceeds range of data format. | ||||
| Description | Within the axis exchange command an axis index is programmed, which exceeds the permissible data range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the axis exchange command. | ||
Parameter | %1: | Incorrect value [-] | |||
Wrong index of the axis in the axis exchange command. [PROG], [CHAN - Chapter - Configuration of the path axes] | |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
Maximum permissible axis index in the NC channel. Version specific pre-setting [SYSP]. | |||||
%4: | Logical axis number [-] | ||||
Logical axis number of the axis with wrong index. P-AXIS-00016, P-CHAN-00035 | |||||
Error type | 1, Error message from NC-program. | ||||
|
21255 | Missing comma between axis index and offset mode. | |||
| Description | Within the axis exchange command behind the axis index a comma has to be programmed, if an offset mode follows. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the axis exchange command. | |
Error type | 1, Error message from NC-program. | |||
|
21256 | Multiple use of the same axis name. | |||
| Description | Within the axis exchange command it is tried to exchange different axes with the same name into the channel. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the axis exchange command. Assign to the meant axes different names. | |
Error type | 1, Error message from NC-program. | |||
|
21257 | Multiple use of the same axis index. | ||||
| Description | Within the axis exchange command it is tried to set different axes on the same index (place) in the channel. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the axis exchange command. Assign to the meant axes different free indizes (places) of the channel. | ||
Parameter | %1: | Incorrect value [-] | |||
Index of the axes in the axis exchange command. [PROG], [CHAN - Chapter -Configuration of the path axes] | |||||
Error type | 1, Error message from NC-program. | ||||
|
21258 | Multiple use of the same log. axis number. | ||||
| Description | Within the axis exchange command it is tried to exchange the same axis (clearly identified by the logical axis number) several times into the NC channel. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the axis exchange command. The axis with the meant logical axis number may be programmed only once within the axis exchange command. | ||
Parameter | %1: | Logical axis number [-] | |||
Logical axis number of the axis, which is used several times withinthe axis exchange command. P-AXIS-00016, P-CHAN-00035 | |||||
Error type | 1, Error message from NC-program. | ||||
|
21259 | Too many axes requested. | ||||
| Description | For the channel more axes are requested, than in the channel are permissible at all. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the axis exchange command. Request less axes and/or redesign program concept. There is no way to exchanged more axes into a NC channel, than the system limits allow. | ||
Parameter | %1: | Incorrect value [-] | |||
Current number of requested axes. | |||||
%2: | Upper limit value [-] | ||||
Maximum number of permissible axes in the NC channel. Version specific pre-setting [SYSP]. | |||||
Error type | 1, Error message from NC-program. | ||||
|
21260 | Axis index is already used in channel. | ||||
| Description | The index (place) of a requested new axis is already occupied by an existing channel axis. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the axis exchange command. Assign to the affected axis an index (place), which is not used yet in channel. | ||
Parameter | %1: | Incorrect value [-] | |||
Index of the axis in the axis exchange command. [PROG], [CHAN - Chapter - Configuration of the path axes] | |||||
Error type | 1, Error message from NC-program. | ||||
|
21261 | Axis name is already used in channel. | |||
| Description | The name of a requested new axis is the same like the name of an already existing channel axis. P-CHAN-00006 | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the axis exchange command. Request affected axis with a name, which is not already used in channel. | |
Error type | 1, Error message from NC-program. | |||
|
21262 | Channel parameters: Default feedrate factor negative or 0. | ||||
| Description | The default feed rate factor P-CHAN-00108 defined in the channel parameters has a negative value or is zero. | |||
Reaction | Class | 1 | Start-up of the control is continued. | ||
Solution | Class | 1 | Check and modify the default feed rate factor P-CHAN-00108 before next start-up in the channel parameters. During start-up in case of conflict the default feed rate factor P-CHAN-00108 is set to 1 (not defined) and the start-up is continued. | ||
Parameter | %1: | Incorrect value [-] | |||
Invalid feed rate factor | |||||
%2: | Corrected value [-] | ||||
Corrected default value | |||||
Error type | 2, Error message by data transfer from parameter list into control device. | ||||
|
21263 - 21268 |
| |||
| Description | This error message informs about internal states, error solutions and the place of error in the source.Please give the complete error message data to the CNC manufacturer. | ||
Reaction | Class | 2 |
| |
Solution | Class | 8 | Restart of NC-control necessary. |
21269 | Unknown string parameter. | |||
| Description | In the #MSG command for a format element of the type %s the corresponding parameter is no syntax conform string parameter. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the #MSG command: Permissible string parameters are: - External variables V.E.xx of the type string - String variables of the type V.STR.xx - "Macro names" - "Strings" Hint:"Macro names" and "Strings" must be included in quotation marks. At first it is checked, if the string within the quotation marks is a known macro name. - If yes, the macro is evaluated. - If no, the string is used "as it is" | |
Error type | 1, Error message from NC-program. | |||
|
21270 - 21272 |
| |||
| Description | This error message informs about internal states, error solutions and the place of error in the source.Please give the complete error message data to the CNC manufacturer. | ||
Reaction | Class | 2 |
| |
Solution | Class | 8 | Restart of NC-control necessary. |
21273 | Double programming in #SAVE/LOAD-command. | |||
| Description | Within the commands #SAVE CONFIG or #LOAD CONFIG keywords are programmed several times or in wrong combinations. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the commands #SAVE CONFIG or #LOAD CONFIG in the NC program. | |
Error type | 1, Error message from NC-program. | |||
|
21274 | No recoverable axes configuration found. | ||||
| Description | The command #LOAD CONFIG can not be executed, because no recoverable axes configuration is stored. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Before the first use of #LOAD CONFIG[AX] in the NC program an axes configuration must be stored with #SAVE CONFIG[AX]. | ||
Parameter | %1: | State [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21275 | No recoverable axes couplings found. | ||||
| Description | The command #LOAD CONFIG can not be executed, because no recoverable axes couplings (synchronous operation) were stored. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Before the first use of #LOAD CONFIG[AXLINK] in the NC program the active axes couplings must be stored with #SAVE CONFIG[AXLINK]. | ||
Parameter | %1: | State [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21276 | Axis names have to be separated by commas or terminated by ']'. | |||
| Description | Within the commands #PUT AX or #AX RELEASE the separating comma ',' is missing between the axes names or behind the last axis name the closing square bracket ']' is missing | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the commands #PUT AX or #AX RELEASE in the NC program. | |
Error type | 1, Error message from NC-program. | |||
|
21277 | #LOAD CONFIG not allowed while active synchronous operation. | |||
| Description | While active synchronous operation (#ENABLE AX LINK or #AX ILNK ON) the command #LOAD CONFIG is programmed. This is not permitted. Example: Wrong: N10 G00 X0 Y0 Z0 N30 #SET AX LINK[1, B=X] N40 #ENABLE AX LINK[1] : N100 #LOAD CONFIG [AX] : N1000 M30 Correct: N10 G00 X0 Y0 Z0 N30 #SET AX LINK[1, B=X] N40 #ENABLE AX LINK[1] : N90 #DISABLE AX LINK[1] N100 #LOAD CONFIG [AX] : N1000 M30 | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. Deselect the activesynchronous operation with #DISABLE AX LINK or #AX LINK OFF (ALL)before the use of the command #LOAD CONFIG. | |
Error type | 1, Error message from NC-program. | |||
|
21278 |
| |||
| Description | This error message informs about internal states, error solutions and the place of error in the source.Please give the complete error message data to the CNC manufacturer. | ||
Reaction | Class | 2 |
| |
Solution | Class | 8 | Restart of NC-control necessary. |
21279 | Maximum number of oscillation axes exceeds limit. | ||||
| Description | Within the NC block too many oscillation axes (<axis name>[OSC ON...]) are programmed. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify NC program. Reduce the number of programmed oscillation axes in the invalid NC block on the maximum permissible number. | ||
Parameter | %1: | Limit value [-] | |||
Maximum permissible number of oscillation axes | |||||
Error type | 1, Error message from NC-program. | ||||
|
21280 | At #SAVE CONFIG too many coupling pairs shall be saved. | ||||
| Description | With the use of the command #SAVE CONFIG[AXLINK] the total number of axes coupling pairs of all active axes coupling groups, which should be saved, is too large. The total number of coupling pairs to be saved is limited, because the restoring with #LOAD CONFIG[AXLINK] implicitly generates a new coupling group 1, which itself also only offers a limited number of coupling pairs. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. If possible, reduce the number of active axes coupling groups with#DISABLE AX LINK or #AX LINK OFF before the use of #SAVE CONFIG. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21281 | Maximum number of coupling pairs exceeds limit. | ||||
| Description | Within the commands #SET AX LINK or #AX LINK the maximum permissible number of coupling pairs is exceeded. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Reduce thenumber of coupling pairs on maximum permissible number. Divide if possible the coupling pairs on several coupling groups. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21282 | The slave axis to be blocked, is unknown. | ||||
| Description | With the selection of a coupling group it is detected, that one of the slave axis is not included into the NC channel or that the axis name is unknown. Especially this error can occur during the so called implicit axes exchange of gantry axes, if the gantry coupling shall be restored in the new channel. | |||
Reaction | Class | 3 | Abort of the NC program processing. | ||
Solution | Class | 3 | Deselect the gantry couplings before axes exchange. Then exchange explicitly with #PUT AX/ #AX RELEASE and #CALL AX/ #AX REQUEST the involved axes between the channels. | ||
Parameter | %1: | Logical axis number [-] | |||
| |||||
%2: | Actual value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21283 | A slave axis is already programmed in an active coupling group as slave axis. | ||||
| Description | With the selection of a coupling group it is detected, that a slave axis is already programmed as slave axis in another active coupling group. This inter coupling group relation is not permissible, because a slave axis may only be assigned to one master axis. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Deselect the already active coupling group (#DISABLE AX LINK / #AX LINK OFF) with the slave axis, which causes the conflict. | ||
Parameter | %1: | Logical axis number [-] | |||
Logical number of the invalid coupling axis | |||||
%2: | Actual value [-] | ||||
Number of the already active coupling group | |||||
Error type | 1, Error message from NC-program. | ||||
|
21284 | A slave axis is already programmed in an active coupling group as master axis. | ||||
| Description | With the selection of a coupling group it is detected, that a slave axis is already programmed as master axis in another active coupling group. This inter coupling group relation is not permissible, because a slave axis may not be master axis at the same time. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Deselect the already active coupling group (#DISABLE AX LINK / #AX LINK OFF) with the master axis, which causes the conflict. | ||
Parameter | %1: | Logical axis number [-] | |||
Logical number of the invalid coupling axis | |||||
%2: | Actual value [-] | ||||
Number of the already active coupling group | |||||
Error type | 1, Error message from NC-program. | ||||
|
21285 | A master axis is already programmed in an active coupling group as slave axis. | ||||
| Description | With the selection of a coupling group it is detected, that a master axis is already programmed as slave axis in another active coupling group. This inter coupling group relation is not permissible, because a master axis may not be slave axis at the same time. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Deselect the already active coupling group (#DISABLE AX LINK / #AX LINK OFF) with the slave axis, which causes the conflict. | ||
Parameter | %1: | Logical axis number [-] | |||
Logical number of the invalid coupling axis | |||||
%2: | Actual value [-] | ||||
Number of the already active coupling group | |||||
Error type | 1, Error message from NC-program. | ||||
|
21286 | Control-Area-ID exceeds range of data format. | ||||
| Description | Using the command #CONTROL AREA START[ ] the area number ID exceeds the permissible data range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Use a permissible area number. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21287 | Definition of a previous control area has not been finished. | |||
| Description | It is detected, that the definition of a new control area with #CONTROL AREA START[ ] is programmed within the NC program sequence of the previous control area definition. But the nested definition of control areas is not allowed. Syntax example: : N10 #CONTROL AREA START... N20 G01 X10 Y10 N30 G01 X20 Y20 N40 #CONTROL AREA START... -> ERROR : Nxx #CONTROL AREA END : | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. The definition of a new control area only is permissible, if the definition of a previous control area is finished with #CONTROL AREA END. Syntax example: : N10 #CONTROL AREA START... N20 G01 X10 Y10 N30 G01 X20 Y20 : Nxx #CONTROL AREA END Nxx #CONTROL AREA START... | |
Error type | 1, Error message from NC-program. | |||
|
21288 | No related definition of a control area. Command has no effect. | |||
| Description | For the command #CONTROL AREA END the corresponding start of the definition of the control area with #CONTROL AREA START[...] is missing. So #CONTROL AREA END is ignored. Syntax example: WRONG: N20 G01 X10 Y10 N30 G01 X20 Y20 : Nxx #CONTROL AREA END -> ERROR : CORRECT: N10 #CONTROL AREA START... N20 G01 X10 Y10 N30 G01 X20 Y20 : Nxx #CONTROL AREA END : | ||
Reaction | Class | 1 | Continue NC program processing. | |
Solution | Class | 1 | Check and modify the NC program. The definition of a control area always must start with #CONTROL AREA START[...] and must be finished with #CONTROL AREA END. | |
Error type | 1, Error message from NC-program. | |||
|
21289 | Missing programming of control area mode. | |||
| Description | In the command #CONTROL AREA START[...] the programming of the keyword WORK or PROT is missing. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. Complete the definition of the control area with WORK or PROT. | |
Error type | 1, Error message from NC-program. | |||
|
21290 | Missing programming of control area type. | |||
| Description | In the command #CONTROL AREA START[...] the programming of the keyword POLY or CIRC is missing. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. Complete the definition of the control area with POLY or CIRC. | |
Error type | 1, Error message from NC-program. | |||
|
21291 | Control area has no excursion in the third dimension. | ||||
| Description | In the command #CONTROL AREA START[...] neither a minimum excursion MIN_EXCUR nor a maximum excursion MAX_EXCUR is programmed. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Complete the definition of the control area with the definition of a minimum and/or maximum excursion (MIN_EXCUR / MAX_EXCUR). | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Incorrect value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21292 | Invalid Control-Area-ID programmed. | ||||
| Description | In the command #CONTROL AREA START[...] the programmed area number ID has the value zero. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Use a permissible area number. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21293 | Missing programming of Control-Area-ID. | |||
| Description | In the command #CONTROL AREA START[...] the programming of the keyword ID with an area number is missing. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. Complete the definition of the control area with an area number ID. | |
Error type | 1, Error message from NC-program. | |||
|
21294 | Double programming in #CONTROL AREA-command. | |||
| Description | In the command #CONTROL AREA START[...] excluding keywords or redundant keywords are programmed. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. In thecommands #CONTROL AREA START[...] remove redundant or excluding keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21295 | Definition of a control area during active thread cutting or tapping is not allowed. | ||||
| Description | The definition of a control area with #CONTROL AREA START[...] is programmed during active thread cutting (G33) or tapping (G63). | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Before the definition of a control area deselect thread cutting (G33) or tapping (G63) with a motion block (G00, G01, G02, G03). | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21296 | Keyword value exceeds range of data format. | ||||
| Description | Within the command #DB INFO[...] a value of a programmed keyword exceeds the permissible data range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Program in the command #DB INFO [...] for the invalid keyword a permissible value within the data range. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21297 | Requested data of a data base group are invalid. | ||||
| Description | The received data of a data group, requested by the command #DB INFO[...]from the PLC have an invalidacknowledgement. The check for the validity of the received data and the output of an error message is only executed, if the command #DB INFO[...] is programmed with the logical flag CHV. If the logical flag is not programmed, no check is active. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 6 | Check the reason for the invalid acknowledgement inside the PLC and ensure the validity of the data group. | ||
Parameter | %1: | Incorrect value [-] | |||
Identification string of the invalid data base group | |||||
Error type | 1, Error message from NC-program. | ||||
|
21298 | Number of received data exceeds number of data requested by #DB INFO-command. | |||
| Description | The data base manager in PLC has send more data groups than requested by the command #DB INFO[ ]. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 6 | Check the data base manager in PLC. | |
Error type | 1, Error message from NC-program. | |||
|
21299 | Double programming in #DB INFO-command. | |||
| Description | In the command #DB INFO[...] redundant keywords are programmed several times. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. In thecommand #DB INFO[...] remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21300 | Axis is not homed! Programmed movement is not allowed. | ||||
| Description | Although P-AXIS-00277 is set to 1, an unreferenced axis shall be moved. The check is done during automatic mode for the interpolation types G00/G01/G02/G03 for programmed moves (Path axes, independent axes, oscillating axes). Spindles and single axes (SAI, PLC-Open) are not checked. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Homing of the axis before moving. | ||
Parameter | %1: | Logical axis number [-] | |||
Logical axis number of the unreferenced axis. P-AXIS-00016, P-CHAN-00035 | |||||
Error type | 1, Error message from NC-program. | ||||
|
21301 | Starting keyword invalid. | |||
| Description | Within the axis specific programming X[...] after 'opening square bracket' an invalid keyword is programmed. At the first position the programming of the function specific keyword (identification) is necessary. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. Ensure that the following identifications are the first in the command sequence ofaxis specific programming: Independent axis: - INDP_SYNor INDP_ASYN -> e.g. X[INDP_SYN...] Oscillating axis: - OSC-> e.g. X[OSC...] Sampled spindles: - DIST_CTRL-> z.B. X[DIST_CTRL...] Spindle feed link: - FEED_LINK-> e.g. S[FEED_LINK ] Techno informations: - Mor H -> e.g. X[M10 ] | |
Error type | 1, Error message from NC-program. | |||
|
21302 | Maximum number of distance controlled axes exceeded. | ||||
| Description | In the NC block too many so called "Touching spindles" (Distance controlled axes: X[DIST_CTRL...] ) are programmed. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Ensure, that in NC-block only the maximum permissible number of distance controlled axes are programmed. | ||
Parameter | %1: | Incorrect value [-] | |||
Invalid number of programmed distance controlled axes in NC block | |||||
%2: | Limit value [-] | ||||
Permissible number of programmed distance controlled axes in NC block | |||||
Error type | 1, Error message from NC-program. | ||||
|
21303 | Automatic determination of feed coupling factor without selection not allowed. | |||
| Description | During the programming of spindle feed link the keyword AUTO is programmed without ON or OFF. Example: Wrong: N10 G00 X0 Y0 Z0 N20 S[FEED_LINK AUTO] : N1000 M30 | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. The keyword AUTO only may be programmed in combination with ON or OFF. Example: Correct: N10 G00 X0 Y0 Z0 N20 S[FEED_LINK ONAUTO] : N1000 M30 | |
Error type | 1, Error message from NC-program. | |||
|
21304 | Channel parameters: SLOPE parameter exceeds range of permissible values. | ||||
| Description | One of the default slope parameters (P-CHAN-00071, P-CHAN-00073, P-CHAN-00001) defined in the channel parameters exceeds the permissible data range. | |||
Reaction | Class | 1 | Start-up of the control is continued. | ||
Solution | Class | 1 | Check and modify the corresponding slope parameter before next start-up in the channel parameters. During start-up in case of conflict the invalid default slope parameter is set to zero and the start-up is continued. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
%4: | Corrected value [-] | ||||
| |||||
Error type | 2, Error message by data transfer from parameter list into control device. | ||||
|
21305 | Channel parameters: Default feed rate 'F' is negative. | ||||
| Description | The default feed rate P-CHAN-00099 defined in the channel parameters has a negative value. | |||
Reaction | Class | 1 | Start-up of the control is continued. | ||
Solution | Class | 1 | Check and modify the default feed rate P-CHAN-00099 before next start-up in the channel parameters. During start-up in case of conflict the default feed rate P-CHAN-00099 is set to zero and the start-up is continued. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Corrected value [-] | ||||
| |||||
Error type | 2, Error message by data transfer from parameter list into control device. | ||||
|
21306 | Invalid log. axes number of the main spindle. | ||||
| Description | A spindle axis with the logical axis number of the main spindle is not available in the NC channel. The error message can appear in an active NC program on use of the command #MAIN SPINDLE. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check the command #MAIN SPINDLE and program the number of a spindle, which is configured in the channel. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21307 | Axis tracking must be deactivated before enable/disable of this function. | |||
| Description | Tangential axis tracking is still active during evaluation of one of the following functions - #TRAFO OFF - #CS OFF - #MCS ON Further information to the functions listed above see [PROG]. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Deactivation of axis tracking (#CAXTRACK OFF) before use of the commands listed above. | |
Error type | 1, Error message from NC-program. | |||
|
21308 | Double-programmed precontrol adaptation. | ||||
| Description | In the same NC block, more than one G-function from the group of adaptive precontrol (G335/G337) was programmed. Example: Wrong: N10 G00 X0 Y0 Z0 N20 G135 X100 G137 : N1000 M30 | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify NC program. Remove the inadmissible G function. | ||
Parameter | %1: | Incorrect value [-] | |||
Number of the inadmissible programmed G function | |||||
Error type | 1, Error message from NC-program. | ||||
|
21309 | Syntax check in channel must always be instructed with MACHINE_LOCK. | |||
| Description | With the instruction of a NC program start in syntax check machining mode it is detected, that the bit MACHINE_LOCK is not set. | ||
Reaction | Class | 1 | NC program processing is continued. | |
Solution | Class | 1 | The missing bit MACHINE_LOCK is set implicitly and NC program start is continued. With the generation of a NC-program instruction in MMI or PLC in syntax check machining mode both, the bit for syntax check and the bit MACHINE_LOCK has to be set. | |
Error type | 1, Error message from NC-program. | |||
|
21310 | Maximum number of non acknowledged SIGNAL/WAIT exceeded. SIGNAL could not be saved anymore. | ||||
| Description | In the event manager the internal system resource for the processing and storing of SIGNAL/WAIT is used up. The latest SIGNAL cannot be processed no more. | |||
Reaction | Class | 3 | Abort of the NC program processing. | ||
Solution | Class | 3 | Optimize the program sequences and reduce the number of SIGNAL/ WAIT synchronizations in the NC programmes of the channels. | ||
Parameter | %1: | Actual value [-] | |||
| |||||
%2: | Limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21311 | Maximum number of non acknowledged SIGNAL/WAIT exceeded. WAIT could not be saved anymore. | ||||
| Description | In the event manager the internal system resource for the processing and storing of SIGNAL/WAIT is used up. The latest WAIT cannot be processed no more. | |||
Reaction | Class | 3 | Abort of the NC program processing. | ||
Solution | Class | 3 | Optimize the program sequences and reduce the number of SIGNAL/ WAIT synchronizations in the NC programmes of the channels. | ||
Parameter | %1: | Actual value [-] | |||
| |||||
%2: | Limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21312 | Axis involved in synchronous operation may not be rearranged. | ||||
| Description | An axis, which at the moment is active as master or slave axis in synchronous operation, may not be rearranged with SET AX... or #AX DEF... . Example: Wrong: N10 G00 X0 Y0 Z0 N30 #SET AX LINK[1, C=Y] N40 #ENABLE AX LINK[1] N50 #SET AX [X,1,0] [Y,2,1] [Z,3,2] [C,4,6] : N1000 M30 Correct: N10 G00 X0 Y0 Z0 N30 #SET AX LINK[1, C=Y] N40 #ENABLE AX LINK[1] : N500 #DISABLE AX LINK[1] N510 #SET AX [X,1,0] [Y,2,1] [Z,3,2] [C,4,6] : N1000 M30 | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify NC-program sequence. Before #SET AX... or #AX DEF... deselect the active coupling groups, were the axes to be rearranged are used. | ||
Parameter | %1: | Logical axis number [-] | |||
Number of the involved axis | |||||
%2: | Actual value [-] | ||||
Number of the coupling group | |||||
%3: | Actual value [-] | ||||
Number of the coupling pair within the coupling group | |||||
Error type | 1, Error message from NC-program. | ||||
|
21313 | Percent sign not allowed within global subroutine part. | |||
| Description | Within a global subroutine (GUP) a percent character (%) is programmed, although the global subroutine is already in execution. The execution of a global subroutine is started, if either a %-character followed by a program name (without "L"!) is found in file, or if in the file outside the comments, a character is noticed as the first character that is neither a space character nor a "%". In this case this character is evaluated as the first character of an unnamed program. This also means that in front of the first "%", no block numbers, variable declarations etc. may be programmed. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify global NC subroutine. Ensure that no NC block numbers,variable declarations etc.were programmed before the first %-character (e.g. remove block numbers at the beginning of comment lines!). Nxx (Comment) (GUP-Start here) : %L UP1 (<- Error 21313 here!) Nxx : %GUP Nxx : or Nxx (Comment) (GUP-Start here) : %GUP (<-Error 21313 here!) : or (Comment) : %L UP1 Nxx : %GUP (GUP-Start here) Nxx : %STRING (<-Error 21313 here!) : or Nxx (GUP-Start here) : %STRING (<-Error 21313 here!) : | |
Error type | 1, Error message from NC-program. | |||
|
21314 | Singular position in kinematic transformation, no valid result. | |||
| Description | The kinematic backward transformation #WCS TO MCS can not be calculated, because the values defined via the axis specific variables V.A.WCS... describe a singular (ambiguous) position. This delivers for the machine coordinate system no clear result. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | The kinematic backward transformation must be executed for another position to produce a useful position in the machine coordinate system. | |
Error type | 1, Error message from NC-program. | |||
|
21315 | Removing of signals failed. | ||||
| Description | In the event manager the deleting of open signals programmed with the NC command #SIGNAL REMOVE[ ] could not be completely executed. | |||
Reaction | Class | 3 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check the NC command #SIGNAL REMOVE[...]. Remove or modify possibly programmed unknown signal IDs, signal areas or channel numbers. | ||
Parameter | %1: | Actual value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21316 | Tangential selection or deselection during active inner corner selection not allowed. | ||||
| Description | During active inner corner selection of tool radius compensation (TRC) the tangential selection or deselection with G05 is not permitted. The used command G05 is ignored. Example: Wrong: N10 G238 : N100 G41 G05 N110 G01 X100 F1000 : N1000 M30 Correct: N10 G238 : N100 G41 N110 G01 X100 F1000 : N1000 M30 | |||
Reaction | Class | 1 | NC program processing is continued. | ||
Solution | Class | 1 | Check and modify the NC program. Remove G05. | ||
Parameter | %1: | Actual value [-] | |||
Used G function | |||||
Error type | - | ||||
|
21317 | Inner corner selection during active TRC not allowed. | ||||
| Description | During active tool radius compensation (TRC) the changing to inner corner selection with G238 is not permitted. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Programming of inner corner selection (G238) before TRC selection (G41/G42). | ||
Parameter | %1: | Incorrect value [-] | |||
Invalid G command | |||||
Error type | 1, Error message from NC-program. | ||||
|
21318 | Changing selection mode during active TRC not allowed. | ||||
| Description | During active inner corner selection of tool radius compensation (TRC) the changing of the selection mode with G138, G139 or G237 is not permitted. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Remove the invalid G function. | ||
Parameter | %1: | Incorrect value [-] | |||
Invalid G command | |||||
Error type | 1, Error message from NC-program. | ||||
|
21319 | Full circle with radius greater than 214 m not allowed. | |||
| Description | In NC-program a full circle with a radius more than 214 m is programmed. Because of that the maximum permissible moving range of the axes is exceeded. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. Approximate and reproduce the circle contour by linear blocks. Arcs of a circle with a radius greater than 214 m can only be programmed, if their starting points and end points are located inside thepermissible moving range of the axes. | |
Error type | 1, Error message from NC-program. | |||
|
21320 | Six axes are necessary for complete cartesian transformation. | |||
| Description | While the complete cartesian transformation it is detected, that at least one axis of the first six axes is missing (P-CHAN-00006, P-CHAN-00035, P-CHAN-00003). | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the channel configuration or NC program. For the complete cartesian transformation at least six axes must exist without a gap in the channel. During the active coordinate system #CS, it is not allowed to change the axes configuration of these six axes. | |
Error type | 1, Error message from NC-program. | |||
|
21321 | For effector coordinate system an active kinematic transformation is required. | |||
| Description | With activation of effector coordinate system (#ECS ON) with non cartesian machine kinematic e.g. Hexapod kinematic it is detected, that the kinematic transformation is not active. Example: Wrong: N10 #KIN ID[26] N20 #TRAFO ON N30 G01 G90 X10 Y10 Z100 A15 B15 C0 F5000 N40 G01 G90 X-10 Y-10 Z100 A15 B15 C0 N50 #TRAFO OFF N60 #ECS ON N70 G01 G90 X25 Y25 Z0 A-15 B-15 C0 : N1000 M30 Correct: N10 #KIN ID[26] N20 #TRAFO ON N30 G01 G90 X10 Y10 Z100 A15 B15 C0 F5000 N40 G01 G90 X-10 Y-10 Z100 A15 B15 C0 N50 #ECS ON N70 G01 G90 X25 Y25 Z0 A-15 B-15 C0 N80 #TRAFO OFF : N1000 M30 | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Before activation of effector coordinate system with non cartesian machine kinematic (#ECS ON) the kinematic transformation must be active (#TRAFO ON). If orientation can be programmed with 3 rotation angles for this type of kinematic structures there is no influence of channel parameters P-CHAN-00031, P-CHAN-00050 on #ECS function. | |
Error type | 1, Error message from NC-program. | |||
|
21322 | Implicit compensation of tool offsets with that block mode not allowed. | |||
| Description | In the same NC block the D word is programmed together with a G function, which changes the block mode and also the meaning of the programmed axes positions (e.g. G04, G63, G74, G92, G98, G99, G100...). This causes a conflict, if the implicit compensation of tool offsets is configured (P-CHAN-00100). Example: Wrong: N10 G00 X0 Y0 Z0 N20 G92 X10 Y20 Z10 D1 : N1000 M30 Correct: N10 G00 X0 Y0 Z0 N20 G92 X10 Y20 Z10 N30 D1 : N1000 M30 | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify NC program. Program the D word in a separate NC block. | |
Error type | 1, Error message from NC-program. | |||
|
21323 | For #TOOL ORI CS function active kinematic transformation is required. | |||
| Description | With activation of automatic orientation function m (#TOOL ORI CS) with non cartesian machine kinematic e.g. Hexapod kinematic it is detected, that the kinematic transformation is not active. Example: Wrong: N10 #KIN ID[26] N20 #TRAFO ON N30 G01 G90 X10 Y10 Z100 A15 B15 C0 F5000 N40 G01 G90 X-10 Y-10 Z100 A15 B15 C0 N50 #TRAFO OFF N60 #TOOL ORI CS N70 G01 G90 X25 Y25 Z0 A-15 B-15 C0 : N1000 M30 Correct: N10 #KIN ID[26] N20 #TRAFO ON N30 G01 G90 X10 Y10 Z100 A15 B15 C0 F5000 N40 G01 G90 X-10 Y-10 Z100 A15 B15 C0 N50 #TOOL ORI CS N70 G01 G90 X25 Y25 Z0 A-15 B-15 C0 N80 #TRAFO OFF : N1000 M30 | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Before activation of automatic orientation function the kinematic transformation must be active (#TRAFO ON). | |
Error type | 1, Error message from NC-program. | |||
|
21326 | TRANS_ID exceeds range of data format. | ||||
| Description | Using the command #COLL DEF[ ] the translatory identification number TRANS_ ID exceeds the permissible data range. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. Use a permissibletranslatory identification number. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21327 | Programmed TRANS_ID not allowed. | ||||
| Description | In the command #COLL DEF[...] the programmed translatory identification number TRANS_ID has an invalid value. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. Use atranslatory identification number, which is within the range of permissible values. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21328 | ROT_ID exceeds range of data format. | ||||
| Description | Using the command #COLL DEF[ ] the identification number for the rotatory orientation ROT_ID exceeds the permissible data range. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. Use a permissibleidentification number for the rotatory orientation. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21329 | Programmed ROT_ID not allowed. | ||||
| Description | In the command #COLL DEF[...] the programmed identification number for the rotatory orientation ROT_ID has an invalid value. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. Use anidentification number for the rotatory orientation, which is within the range of permissible values. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21330 | Programmed rotation coefficient not allowed. | ||||
| Description | In the command #COLL DEF[...] or #COLL POS[...] one of the programmed rotation coefficients (XX - ZZ) has an invalid value. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. Userotation coefficients, which are within the range of permissible values. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21332 | Invalid programming of translatory shifts. | |||
| Description | Using the command #COLL DEF [TRANS_ID.. ...] one ore more of the translatory shifts (X.. Y.. Z..) are missing. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program.Using the command #COLL DEF [TRANS_ID.. ...] all translatory shifts (X.. Y.. Z..) must be programmed. | |
Error type | 1, Error message from NC-program. | |||
|
21333 | Invalid programming of rotatory orientation. | |||
| Description | Using the command #COLL DEF [ROT_ID.. ...] one ore more of the the programmed rotation coefficients (XX - ZZ) are missing. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program.Using the command #COLL DEF [ROT_ID.. ...] all rotation coefficients (XX - ZZ) must be programmed. | |
Error type | 1, Error message from NC-program. | |||
|
21335 | Radius too small, circle is skipped . | ||||
| Description | A circular NC block was programmed with a too small radius. So no useful calculation of a center point is possible. | |||
Reaction | Class | 1 | Continue NC program processing. | ||
Solution | Class | 1 | The circular block is skipped and transformed to a linear block with moving distance 0. | ||
Parameter | %1: | Incorrect value [0.1 µm or 0,0001°] | |||
Circle radius in µm | |||||
%2: | Lower limit value [Increment] | ||||
Smallest permissible circle radius | |||||
Error type | 1, Error message from NC-program. | ||||
|
21336 | Invalid programming of positioning of an element. | |||
| Description | In the command #COLL POS [...] the position respectively the orientation of an element is not correctly programmed. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. The position has to be programmed either by translatory shifts (X.. Y.. Z..) or by a predefined translatory ID (TRANS_ID). The orientation has to be programmed by the complete definition of the rotatorycoefficients (XX - ZZ)or by a predefined rotatory ID (ROT_ID). If no orientation is programmed, the default values are valid (XX=1, YY=1, ZZ=1, all othercoefficients= 0). | |
Error type | 1, Error message from NC-program. | |||
|
21337 | No group name or pair name programmed. | |||
| Description | Using the command #COLL ON / OFF / CLEAR [...] no group name GROUP or element name ELEM is programmed. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. Completethe command#COLL ON / OFF / CLEAR [...]with apermissiblegroup name GROUP or element name ELEM. | |
Error type | 1, Error message from NC-program. | |||
|
21338 | Double programming in #COLL-command. | |||
| Description | In the command #COLL ... [...] redundant keywords are programmed several times. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. In thecommand #COLL ... [...] remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21339 | Invalid programming of #COLL DEF-command. | |||
| Description | Using the command #COLL DEF[ ] neither a identification for translation TRANS_ID nor for a rotatory orientation ROT_ID is programmed. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. Completethe command with the missing identification TRANS_ID or ROT_ID. | |
Error type | 1, Error message from NC-program. | |||
|
21340 | Double programming in #TRC-command. | |||
| Description | Within the command #TRC keywords are programmed several times or in wrong combinations. Example with error: #TRC | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Modification of #TRC command in the NC program [PROG]. | |
Error type | 1, Error message from NC-program. | |||
|
21341 | Cancellation of request without axis registration. | ||||
| Description | This case is not relevant in normal operation mode. The message is only useful for diagnosis of resulting operation states. | |||
Reaction | Class | 1 | Continue NC program processing. | ||
Solution | Class | 1 | Message is used for diagnosis of axis exchange problems. | ||
Parameter | %1: | Logical axis number [-] | |||
| |||||
Error type | - | ||||
|
21342 | Memory for external variables is not configured. | |||
| Description | CNC got an order from PLC or another process (i.e. Object Browser) to display the memory layout of the external variables. During that procedure CNC detects that there is no memory allocated for using external variables. | ||
Reaction | Class | 2 | Memory layout of the external variables isnt displayed. | |
Solution | Class | 7 | You have to assign parameter P-STUP-00037 a value > 0. | |
Error type | - | |||
|
21343 | Memory to store external variables is too small. Could not display layout of external variables. | ||||
| Description | CNC got an order from PLC or another process (i.e. Object Browser) to display the memory layout of the external variables. | |||
Reaction | Class | 3 | Memory layout of the external variables isnt displayed. | ||
Solution | Class | 7 | You have to assign parameter P-STUP-00037 a value that is greater than the actual value. | ||
Parameter | %1: | Actual value [-] | |||
Index of declaration of an external variable (i.e.: var[0]....) in list that contains the external variables declarations. | |||||
%2: | Actual value [-] | ||||
The name of that external variables from which the information about the layout of the memory used by external variables couldnt be displayed, because the existing memory is to small. | |||||
Error type | - | ||||
|
21344 | Synchronous WAIT with parameters not allowed. | |||
| Description | Signal parameters can only be evaluated on decoding level, a synchronized waiting with evaluation of parameters #WAIT SYN[... P[0] = ... ] is not allowed. See also in [PROG - Chapter Channel synchronization Waiting for signals] | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Modification of #WAIT command in the NC program. Change the sequence of the NC program in that way, that waiting is possible without synchronization#WAIT[...P[0] = ... ]. | |
Error type | 1, Error message from NC-program. | |||
|
21345 | No licence available for spline interpolation. | |||
| Description | Spline interpolation is not possible with the installed licence key of the CNC software package. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | For the use of the spline interpolation the suitable licence key has to be installed. Please contact the control manufacturer. | |
Error type | 1, Error message from NC-program. | |||
|
21346 | No licence available for transformation. | |||
| Description | Cartesian or kinematic transformation is not possible with the installed licence key of the CNC software package. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | For the use of transformations the suitable licence key has to be installed. Please contact the control manufacturer. | |
Error type | 1, Error message from NC-program. | |||
|
21347 | Slave axis is not allowed to be a main spindle. | ||||
| Description |
| |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify NC program. | ||
Parameter | %1: | Logical axis number [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21348 | Helical interpolation with pitch but without 3. dimension not allowed. | ||||
| Description | The helical interpolation is a superimposition of a circular interpolation (plane of the 1. and 2. main axes) and a linear movement in the 3. main axis. The message is created, if for the programmed helix a movement in the 3. main axis(Z axis) is missing. Example: Wrong: N10 G17 G90 X-10 Y0 Z0 F500 N20 G03 I0 J0 K10 : N1000 M30 Correct: N10 G17 G90 X-10 Y0 Z0 F500 N20 G03 I0 J0 Z50 K10 (Helix with 5 : N1000 M30 | |||
Reaction | Class | 1 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify NC program. Add for the programmed helix a movement in the 3. main axis(Z axis). | ||
Parameter | %1: | Start value [0.1 µm or 0,0001°] | |||
Start position of the 3. main axis | |||||
%2: | End value [0.1 µm or 0,0001°] | ||||
Target position of the 3. main axis | |||||
Error type | 1, Error message from NC-program. | ||||
|
21349 | Double programming in #TGC-command. | ||||
| Description | Within the command #TGC keywords are programmed several times or in wrong combinations. | |||
Reaction | Class | 2 | Abort of the NC program processing | ||
Solution | Class | 3 | Modification of the #TGC command in the NC program. | ||
Parameter | %1: | State [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21350 | Programmed minimum path transition velocity is negative. | ||||
| Description | The minimum block transition velocity on the path programmed with #TRANSVEL MINON is negativ. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the command. Programmedminimum block transition velocitymust have a value larger or equal to zero. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21351 | Relative programmed moving distance not allowed with that variable. | ||||
| Description | The use of the variable V.A.ACT_POS.** (current actual position, [PROG]) for the programming of a relative linear movement of the same axis is not allowed. This behaviour is version specific. Example: Wrong: N10 G90 X10 Y20 Z30 F500 N20 G91 : N1000 M30 | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the command. Change relative programming (G91) into absolute programming (G90). | ||
Parameter | %1: | Logical axis number [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21352 | Invalid programming of #SCENE-command. | |||
| Description | Using the command #SCENE ... [...] either an incorrect index value for the keywords KEY oder VALUE is programmed or necessary keywords are missing and the command is incomplete. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. Correct the faulty value or complete the missing keywords according to [PROG] in NC command. | |
Error type | 1, Error message from NC-program. | |||
|
21353 | Double programming in #SCENE_command. | |||
| Description | In the command #SCENE ... [...] keywords are programmed several times or in wrong combinations. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. In thecommand #SCENE ... [...] remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21354 | Too many link points programmed. | ||||
| Description | In the command #SCENE DELETE [ LINKPOINT<name> ...] too many linkpoints are programmed. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. Reduce the maximum number of linkpoints in the command on the permissible limit. If necessary, use step-by-step additional #SCENE DELETE [...] for deleting of further linkpoints. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21355 | Too many grafic objects programmed. | ||||
| Description | In the command #COLL DEF [...], #SCENE DELETE [...] or #GROUP ADD/ DELETE[...] too many graphical objects are programmed. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. Reduce the maximum number of graphical objects in the command on the permissible limit. If necessary, use step-by-step additional commands for handling of further graphical objects. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21356 | Too many groups programmed. | ||||
| Description | In the command #COLL DEF [...] or #SCENE DELETE [...] too many groups are programmed. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. Reduce the maximum number of groups in the command on the permissible limit. If necessary, use step-by-step additional commands for handling of further groups. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21357 | Invalid programming of #GROUP-command. | |||
| Description | Using the command #GROUP... [...] necessary keywords are missing and the command is incomplete. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. Complete the missing keywords according to [PROG] in NC command. | |
Error type | 1, Error message from NC-program. | |||
|
21358 | Double programming in #GROUP-command. | |||
| Description | In the command #GROUP ... [...] keywords are programmed several times or in wrong combinations. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. In thecommand #GROUP ... [...] remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21359 | Value of the parameter set exceeds range of data format. | ||||
| Description | The parameter set number(PARAM_SET) programmed in the NC command #DRIVE exceeds the permissible data range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Use a permissible parameter set number. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21360 | Motor number exceeds range of data format. | ||||
| Description | The motor number(MOTOR) programmed in the NC command #DRIVE exceeds the permissible data range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Use a permissible motor number. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21361 | Value of the telegram element exceeds range of data format. | ||||
| Description | The telegram element number(ID) programmed in the NC command #DRIVE exceeds the permissible data range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Use a permissible telegram element number. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21362 | Double programming in #DRIVE-command. | |||
| Description | Within the command #DRIVE keywords are programmed several times or in wrong combinations. Example with error: #DRIVE WR | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. In thecommand #DRIVE remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21363 | Axis is not allowed for the definition of a control area. | ||||
| Description | Only the first 2 main axes, which determine the working plane (G17, G18, G19) may be programmed for the definition of the contour of a control area. The third main axis and all other coupled axes may not be programmed during the definition of a control area contour. Example: Wrong: N10 #CONTROL AREA START [ID1 N20 G01 F1000 G90 X-150 Y75 N30 X-50 Y150 : N130 X-150 Y75 N140 #CONTROL AREA : N1000 M30 Correct: N10 #CONTROL AREA START [ID1 N20 G01 F1000 G90 X-150 Y75 N30 X-50 Y150 : N130 X-150 Y75 N140 #CONTROL AREA : N1000 M30 | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Ensure, that only thefirst 2 main axes are used for the definition of the contour of a control area. See also [PROG - Chapter - Definition of a control area] | ||
Parameter | %1: | Logical axis number [-] | |||
Logical axis number of the illegal programmed axis | |||||
Error type | 1, Error message from NC-program. | ||||
|
21364 |
| |||
| Description | This error message informs about internal states, error solutions and the place of error in the source.Please give the complete error message data to the CNC manufacturer. | ||
Reaction | Class | 3 |
| |
Solution | Class | 8 | Restart of NC-control necessary. |
21365 | Negative distance not allowed. | ||||
| Description | The values of the monitoring distances programmed with the keywords ERROR or WARNING of the command #COLL DEF [...] are negative. | |||
Reaction | Class | 1 | Continue NC program processing. | ||
Solution | Class | 1 | The invalid negative value is multiplied by 1 and the NC program is continued. Check and modify NC command #COLL DEF [...] before next program start. The programmedmonitoring distances must have values > 0. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Corrected value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21366 - 21368 |
| |||
| Description | This error message informs about internal states, error solutions and the place of error in the source.Please give the complete error message data to the CNC manufacturer. | ||
Reaction | Class | 3 |
| |
Solution | Class | 8 | Restart of NC-control necessary. |
21369 | PDU received from tool management contains illegal parameter index. | ||||
| Description | During transparent read access on some specific tool object data of an external tool database via V.G.WZ[j].GOBJECT[i].* the NC channel receives an object data record with an invalid index. With maximally 5 permissible object data records per tool the highest index may have the value 4. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 6 | Check the internal sequence in the external tool management (e.g. PLC) during transparent read access. The maximum index in the object data record which can be made available must be in the range 0 - 4. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21370 |
| |||
| Description | This error message informs about internal states, error solutions and the place of error in the source.Please give the complete error message data to the CNC manufacturer. | ||
Reaction | Class | 2 |
| |
Solution | Class | 8 | Restart of NC-control necessary. |
21371 | NC command requires SYN. | |||
| Description | The command #DRIVE may be programmed only with synchronisation (SYN). Example: #DRIVE WR | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. In thecommand #DRIVE add the missing keyword SYN. | |
Error type | 1, Error message from NC-program. | |||
|
21372 | Unknown or invalid logical axis number programmed. | ||||
| Description | The logical axis number programmed in a NC command (e.g. #IDENT , #DRIVE, S[MC_GearIn...], #SCENE, axis exchange commands) could not be assigned to a configurated channel axis or an other available axis of the system. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Only available and known axes of the system may be programmed via their logical axis numbers. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21373 | Double programming in SAI command sequence. | |||
| Description | In a SAI specific command sequence ( e.g. S[MC_GearIn...] ) keywords are programmed several times or in wrong combinations. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. In theSAI specific command sequence remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21374 | Programmed SAI value exceeds range of data format. | ||||
| Description | The value of a keyword programmed in a SAI specific command sequence ( e.g. S[MC_GearIn...] ) exceeds the permissible data range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Check the values of the keywords for plausibility and adjust them if necessary. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21375 | Invalid SAI value programmed. | ||||
| Description | The value of a keyword programmed in a SAI specific command sequence ( e.g. S[MC_GearIn...] ) is not allowed. Example: S[MC_GearIn Master=1 | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Check the values of the keywords for plausibility and adjust them if necessary. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21376 | No master axis programmed. | |||
| Description | In the SAI specific command sequence for gearing of axes S[MC_GearIn...] the definition of a master axis (MASTER) is missing. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. Complete the missing definition of the master axis (MASTER=<expr>) in command sequence. | |
Error type | 1, Error message from NC-program. | |||
|
21377 | Invalid programming of #COLL PRINT command. | |||
| Description | In the command #COLL PRINT the keywords REL or LOG may only be used in combination with the definition of a record file FILE. Examples: Nxx #COLL PRINT [REL] -> Fehler Nxx #COLL PRINT [LOG] -> Fehler Nxx #COLL PRINT [FILE=prot1.txt REL] -> OK Nxx #COLL PRINT [FILE=prot1.txt LOG] -> OK | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. If the command #COLL PRINT is programmed without the definition of a record file FILE, either also remove the keywords REL or LOG or complete the command sequence by the definition of a record file FILE. | |
Error type | 1, Error message from NC-program. | |||
|
21379 | Double programming in CYCLE call. | |||
| Description | In a cylce specific command sequence (L CYCLE[NAME=...] ) keywords are programmed several times or in wrong combinations. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. In the cyclespecific command sequence remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21380 | Cycle call during active thread cutting or tapping is not allowed. | ||||
| Description | A cycle call L CYCLE[NAME=...] during active thread cutting or tapping (G33/G63) is not permitted. Example: Wrong: N05 X0 Y0 Z0 N10 G91 N20 M03 S100 X100 M19 N30 G63 Z-100 N40 Z100 N45 L CYCLE N50 G01 X200 N60 G63 Z-70 F300 N70 Z70 N80 M05 G01 X300 N90 M30 Correct: N05 X0 Y0 Z0 N10 G91 N20 M03 S100 X100 M19 N30 G63 Z-100 N40 Z100 N50 G01 X200 N55 L CYCLE N60 G63 Z-70 F300 N70 Z70 N80 M05 G01 X300 N90 M30 | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Before the cycle callthread cutting or tapping has to be deselected by programming another modal block mode (e.g. G01). | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21381 | Cycle call during active modal cycle not allowed. | |||
| Description | Although a modal cycle is still active (L CYCLE [NAME=... MODAL ..]), a second cycle is called. Example: Wrong: N05 X0 Y0 Z0 N10 L CYCLE N20 G01 X200 N30 G01 X300 N40 L CYCLE N50 G01 Y300 N60 G01 Z300 N90 M30 Correct: N05 X0 Y0 Z0 N10 L CYCLE N20 G01 X200 N30 G01 X300 N35 #DISABLE MODAL N40 L CYCLE N50 G01 Y300 N60 G01 Z300 N90 M30 | ||
Reaction | Class | 1 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. Before a new cycle call, first the modal cycle has to be deselected(#DISABLE MODAL CYCLE). | |
Error type | 1, Error message from NC-program. | |||
|
21382 | Invalid read/write access on cycle parameter. | ||||
| Description | This error output is caused by a write/read access on a cycle parameter within a main program or by a direct call of a cycle as a stand-alone program. A write/read access on cycle parameters (@Pxx=..) is only allowed in a cycle program itself (e.g. @P1=@P5+@P6) or inside a cycle call L CYCLE [NAME=... @Pxx=..]. Example: Wrong: %main N05 X0 Y0 Z0 N20 G01 X200 N25 N40 L CYCLE N50 G01 Y300 N60 G01 Z300 N90 M30 Correct: %main N05 X0 Y0 Z0 N20 G01 X200 N25 N40 L CYCLE N50 G01 Y300 N60 G01 Z300 N90 M30 | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Deletewrite/read access from main or standard sub program respectively move it into the cycle. Start cycle only by a global sub program call within the main program (L CYCLE [...]). | ||
Parameter | %1: | Actual value [-] | |||
| |||||
%2: | Incorrect value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21383 | Invalid use of a cycle axis name. | ||||
| Description | This error output is caused by using acycle axis name (@X..)within a main program or by a direct call of a cycle as a stand-alone program. A cycle axis name only may be used in a cycle program itself (e.g. @X= @P5/2) Invalid example: N05 X0 Y0 Z0 N20 G01 X200 N25 N40 L CYCLE N50 G01 Y300 N60 G01 Z300 N90 M30 | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Usecycle axis names only in cycle.Start cycle only by a global sub program call within the main program (L CYCLE [...]). | ||
Parameter | %1: | Actual value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21384 | Invalid use of a cycle center point coordinate. | ||||
| Description | This error output is caused by using acycle center point coordinate (@I..)within a main program or by a direct call of a cycle as a stand-alone program. A cycle center point coordinate only may be used in a cycle program itself (e.g. @I= @P6) Invalid example: N05 X0 Y0 Z0 N20 G01 @I=100 N40 L CYCLE N50 G01 Y300 N60 G01 Z300 N90 M30 | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Usecycle center point coordinates only in cycle.Start cycle only by a global sub program call within the main program (L CYCLE [...]). | ||
Parameter | %1: | Actual value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21385 | Invalid use of a cycle spindle name. | ||||
| Description | This error output is caused by using acycle spindle name (@S..)within a main program or by a direct call of a cycle as a stand-alone program. A cycle spindle name only may be used in a cycle program itself (e.g. @S=1000) Invalid example: N05 X0 Y0 Z0 N20 G01 X200 N25 @S=1000 N40 L CYCLE N50 G01 Y300 N60 G01 Z300 N90 M30 | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Usecycle spindle names only in cycle.Start cycle only by a global sub program call within the main program (L CYCLE [...]). | ||
Parameter | %1: | Actual value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21386 | Wrong sequence of channel specific signal-/wait requests. | ||||
| Description | In NC channel the ID of a programmed #WAIT does not match to the pending signal ID. | |||
Reaction | Class | 3 | Abort of the NC program processing. | ||
Solution | Class | 3 | Normal channel specific signals (no broadcast) have to be confirmed by #WAIT in the same order like they have been created by #SIGNAL. This means in the NC channels the ID's of the #SIGNAL/#WAIT have to be processed in the correct order. | ||
Parameter | %1: | Actual value [-] | |||
Value of the unexpected Wait-ID | |||||
Error type | 1, Error message from NC-program. | ||||
|
21387 | Conditional interpretation: #IF without corresponding #ENDIF programmed. | |||
| Description | Aconditional instruction was programmed in incomplete syntax. A #IF can only be programmed in combination with a closing #ENDIF. Example: Wrong: N01 P1=0 #IF P1==1 N10 G00 X0 Y0 Z0 : N25 G01 X100 Y0 Z0 F1000 : N1000 M30 Correct: N01 P1=0 #IF P1==1 N10 G00 X0 Y0 Z0 : N25 G01 X100 Y0 Z0 F1000 #ENDIF : N1000 M30 | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program sequence. Complete the #IF/ #ENDIF construct or remove the #IF command. | |
Error type | 1, Error message from NC-program. | |||
|
21388 | Double programming in #OTC-command. | |||
| Description | In the command #OTC ... [...] keywords are programmed several times or in wrong combinations. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. In thecommand #OTC ... [...] remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21389 | Parameter setting during active OTC not allowed. | |||
| Description | The parameterisation of the OTC function (Online Tool Compensation) only is allowed before or during the selection with#OTC ON [...]. If the OTC already is active, the predefined parameters may not be changed again. Example: Wrong: N05 G01 X100 N10 #OTC ON N15 #OTC [LENGTH CONT WEAR_CONST_TOOL] or N10 #OTC ON [LENGTH CONT WEAR_CONST_TOOL] N15 #OTC [LENGTH AUTO WEAR_CONST_TOOL] N20 G01 X200 : N900 #OTC OFF N1000 M30 Correct: N05 G01 X100 : N10 #OTC [LENGTH CONT WEAR_CONST_TOOL] N15 #OTC ON or N10 #OTC ON [LENGTH CONT WEAR_CONST_TOOL] : N20 G01 X200 : N900 #OTC OFF N1000 M30 | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. Adapt the sequence ofparameterisation and selection of OTC. | |
Error type | 1, Error message from NC-program. | |||
|
21390 | OTC is already active. Renewed call not allowed. | |||
| Description | During already active OTC function(Online Tool Compensation) theOTC shall be selected again. Example: Wrong: N05 G01 X100 N10 #OTC ON [LENGTH CONT WEAR_CONST_TOOL] N20 G01 X200 : Nxx #OTC ON : N900 #OTC OFF N1000 M30 Correct: N05 G01 X100 N10 #OTC ON [LENGTH CONT WEAR_CONST_TOOL] N20 G01 X200 : N900 #OTC OFF N1000 M30 | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. Remove the redundant selection of OTC. | |
Error type | 1, Error message from NC-program. | |||
|
21391 | Invalid tool type for OTC operation. | ||||
| Description | At selection of OTC function (Online Tool Compensation) it has to be ensured, that the used tool is a grinding tool. That's why the tool type, entered in the tool data is checked. An error message is output, if the current tool is no grinding tool, this means the corresponding parameter setting of P-TOOL-00001 in the tool data is not correct. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Enter tool type 2 for grinding tools (P-TOOL-00001) in the related tool data. Update the tool list and restart the NC program. | ||
Parameter | %1: | Incorrect value [-] | |||
Current entered tool type | |||||
%2: | Expected value [-] | ||||
Tool type for grinding tools | |||||
Error type | 1, Error message from NC-program. | ||||
|
21392 | OTC not active. Deselection not allowed. | |||
| Description | The programming of #OTC OFF is only useful, ifOTC function(Online Tool Compensation) was activated before. Example: Wrong: N05 G01 X100 N20 G01 X200 : N900 #OTC OFF N1000 M30 Correct: N05 G01 X100 N10 #OTC ON [LENGTH CONT WEAR_CONST_TOOL] N20 G01 X200 : N900 #OTC OFF N1000 M30 | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. Remove the unnecessary deselection of OTC (#OTC OFF) or select OTC before. | |
Error type | 1, Error message from NC-program. | |||
|
21393 |
| |||
| Description | This error message informs about internal states, error solutions and the place of error in the source.Please give the complete error message data to the CNC manufacturer. | ||
Reaction | Class | 3 |
| |
Solution | Class | 8 | Restart of NC-control necessary. |
21394 | Active OTC on program end. | |||
| Description | At program end (M02, M30) the online tool compensation selected by the command #OTC ON [ ] is still active. | ||
Reaction | Class | 1 | NC program processing is continued. | |
Solution | Class | 1 | Edit NC program. Enter #OTC OFF before program end. | |
Error type | 1, Error message from NC-program. | |||
|
21395 | Plane selection during active OTC not allowed. | ||||
| Description | As long as theOTC function (Online Tool Compensation)is active, it is not allowed to programme a plane selection by G17, G18 or G19. Example: Wrong: N10 G00 X0 Y0 Z0 N20 #OTC ON [LENGTH CONT WEAR_CONST_TOOL] N100 G19 : N1000 M30 Correct: N10 G00 X0 Y0 Z0 N20 #OTC ON [LENGTH CONT WEAR_CONST_TOOL] : N90 #OTC OFF N100 G19 : N1000 M30 | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify NC program sequence. Deselect the OTC function with #OTC OFF before programming of plane selection. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21396 | Changing kinematic transformation (RTCP) during active OTC not allowed. | |||
| Description | Selection or changing the kinematic transformation is not possible whileOTC function (Online Tool Compensation)is active. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the sequence of the NC program. Deselection ofOTC function(#OTC OFF)before changing or selection of kinematic transformation. | |
Error type | 1, Error message from NC-program. | |||
|
21397 | Coordinate system transition during active OTC not allowed. | |||
| Description | During the transition of coordinate systems with the commands #CS, #ACS and/or #MCS theOTC function (Online Tool Compensation)may not be active. This restriction applies both with the selection and with the deselection of respective functionality. Example: Wrong: N10 G00 X0 Y0 Z0 N20 #OTC ON [LENGTH CONT WEAR_CONST_TOOL] N30 #CS ON [10,20,30,0,0,45] : N900 #OTC OFF N1000 M30 Correct: N10 G00 X0 Y0 Z0 N20 #CS ON [10,20,30,0,0,45] N30 #OTC ON [LENGTH CONT WEAR_CONST_TOOL] : N900 #OTC OFF N1000 M30 | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the sequence of the NC program. Select OTC function (#OTC ON [...]) after the transition of coordinate system. | |
Error type | 1, Error message from NC-program. | |||
|
21398 | Tool change during active OTC not allowed. | |||
| Description | It is not possible to activate a different set of parameters for the tool geometry correction with the D word or #TOOL DATA[ ] while theOTC function (Online Tool Compensation)is active. Example: Wrong: N10 G00 X0 Y0 Z0 N20 #OTC ON [LENGTH CONT WEAR_CONST_TOOL] : N90 D2 N100 #OTC OFF : N1000 M30 Correct: N10 G00 X0 Y0 Z0 N20 #OTC ON [LENGTH CONT WEAR_CONST_TOOL] : N90 #OTC OFF N100 D2 : N1000 M30 | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify NC program sequence. DeselectOTC function with#OTC OFF before programming of the D word or #TOOL DATA[ ]. | |
Error type | 1, Error message from NC-program. | |||
|
21399 | Start position of block search is inside a locked program area. | |||
| Description | The block search shall be continued at a start position in the NC program. But this position is located inside a forbidden area for the block search, defined by the command #BLOCKSEARCH LOCKED/ RELEASED (see also [PROG]). | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Select a start position, which is outside the locked area for block search or redefine the forbidden areas in NC program. | |
Error type | 1, Error message from NC-program. | |||
|
21400 | Global feed weighting is programmed negative. | ||||
| Description | The global feed weighting value programmed with G129 for rapid velocity is negative. Example: Wrong: N10 G00 X0 Y0 Z0 N20 G129 = -60 : N1000 M30 Correct: N10 G00 X0 Y0 Z0 N20 G129 = 60 : N1000 M30 | |||
Reaction | Class | 1 | NC program processing is continued. | ||
Solution | Class | 1 | In case of conflict the feedweighting automatically is set on 100% andNC program processing is continued. Before the next program starta useful value greater than zeroshould be programmed. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Corrected value [-] | ||||
Automatic corrected value of feed weighting | |||||
Error type | 1, Error message from NC-program. | ||||
|
21401 | Programmed PATH_DEV not allowed. | ||||
| Description | If during the extended HSC programming (#HSC ON/OFF [BSPLINE...]) the keyword MERGE is set on 1 (TRUE), also the deviation from path contour PATH_DEV has to be programmed with a value unequal to zero. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Programming of the deviation from path contour PATH_DEV with a value unequal to zero or complete removing from the command (in this case the related default value is valid, see[PROG]). | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21402 |
| |||
| Description | This error message informs about internal states, error solutions and the place of error in the source.Please give the complete error message data to the CNC manufacturer. | ||
Reaction | Class | 3 |
| |
Solution | Class | 8 | Restart of NC-control necessary. |
21403 | The compensation settings of an axis involved in synchronous operation may not be modified. | ||||
| Description | With the command <axis>[COMP ...]the compensation setting of an axis shall be changed, which at the moment is included as a master or slave axis in the active synchronous operation. Example: Wrong: N10 G00 X0 Y0 Z0 N30 #SET AX LINK[1, B=X] N40 #ENABLE AX LINK[1] : N100 X[COMP ON CROSS] : N1000 M30 Correct: N10 G00 X0 Y0 Z0 N30 #SET AX LINK[1, B=X] N40 #ENABLE AX LINK[1] : N90 #DISABLE AX LINK[1] N100 X[COMP ON CROSS] : N1000 M30 | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program.Deselect the activesynchronous operation with #DISABLE AX LINK or #AX LINK OFF (ALL)before the use of the command<axis>[COMP ...]. | ||
Parameter | %1: | Logical axis number [-] | |||
Number of the axis, which causes the conflict with an active master or slave axis. | |||||
%2: | Actual value [-] | ||||
Number of the active coupling group | |||||
%3: | Actual value [-] | ||||
Number of the axes coupling pair | |||||
Error type | 1, Error message from NC-program. | ||||
|
21404 | Channel parameters: Multiple axes programming without active "multi_dimension_in_block" is not useful. | ||||||
| Description | During start-up the check of the channel parameters detects, that the setting of P-CHAN-00148 on 1 is only useful, if P-CHAN-00116 is also set on 1. | |||||
Reaction | Class | 1 | Start-up of the control is continued. | ||||
Solution | Class | 1 | During start-up in case of conflict the multiple axes programming is set to 0 (FALSE) and the start-up is continued. Before nextstart-up correct setting of the channel parameters P-CHAN-00116 and P-CHAN-00148: | ||||
P-CHAN-00116 | P-CHAN-00148 | Check result | |||||
0 | 0 | OK | |||||
1 | 0 | OK | |||||
1 | 1 | OK | |||||
Parameter | %1: | Incorrect value [-] | |||||
Incorrect channel parameter P-CHAN-00148 | |||||||
%2: | Corrected value [-] | ||||||
| |||||||
Error type | 2, Error message by data transfer from parameter list into control device. | ||||||
|
21405 | Double programming in #FGROUP-command. | |||
| Description | In the command #FGROUP ... [...] keywords are programmed several times or in wrong combinations. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. In thecommand #FGROUP ... [...] remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21406 | No license available for extended HSC programming. | |||
| Description | Extended HSC programming is not possible with the installed licence key of the CNC software package. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | For the use of the extended HSC programming the suitable licence key has to be installed. Please contact the control manufacturer. | |
Error type | 1, Error message from NC-program. | |||
|
21407 | WCS target value is out of permissible range. | ||||
| Description | Based on the command #GET WCS POSLIMIT during the calculation of the motion limits in the WCS system the resulting target position of one of the main axes exceeds the permissible data format. The value of the multiple ID shows the corresponding axis, in which the invalid position has been calculated: Multiple ID 1à1. Main axis Multiple ID 2à2. Main axis Multiple ID 3à3. Main axis | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | This error only occurs, if the setting of the kinematic or cartesian transfomation is wrong. Check and correct the settings if necessary. | ||
Parameter | %1: | Incorrect value [-] | |||
Calculated distance to the motion limit | |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21408 | #GET WCS POSLIMIT not allowed while active synchronous operation. | |||
| Description | While active synchronous operation (#ENABLE AX LINK or #AX ILNK ON) the command #GET WCS POSLIMIT is programmed. This is not permitted. Example: Wrong: N10 G00 X0 Y0 Z0 N30 #SET AX LINK[1, B=X] N40 #ENABLE AX LINK[1] : N100 #GET WCS POSLIMIT [VC1=1 VC2=0 VC3=0] : N1000 M30 Correct: N10 G00 X0 Y0 Z0 N30 #SET AX LINK[1, B=X] N40 #ENABLE AX LINK[1] : N90 #DISABLE AX LINK[1] N100 #GET WCS POSLIMIT [VC1=1 VC2=0 VC3=0] : N1000 M30 | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program. Deselect the activesynchronous operation with #DISABLE AX LINK or #AX LINK OFF (ALL)before the use of the command#GET WCS POSLIMIT. | |
Error type | 1, Error message from NC-program. | |||
|
21409 | Current MCS position outside soft limits. | ||||
| Description | Based on the command #GET WCS POSLIMIT during the calculation of the motion limits in the WCS system it is detected that at least one of the main axes start positions exceeds the corresponding software limits. In this case with the programmed direction vector no motion limit can be determined. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Before the selection of #GET WCS POSLIMIT it must be ensured, that all axes involved in transformation are positioned inside the motion area, defined by the sofware limit switches. | ||
Parameter | %1: | Logical axis number [-] | |||
Axis, which exceeds the software limits | |||||
%2: | Actual value [0.1 µm or 0,0001°] | ||||
MCS axis position | |||||
%3: | Upper limit value [0.1 µm or 0,0001°] | ||||
Positive software limit | |||||
%4: | Lower limit value [0.1 µm or 0,0001°] | ||||
Negative software limit | |||||
Error type | 1, Error message from NC-program. | ||||
|
21410 | Movement direction vector is 0. | ||||
| Description | The direction vector, programmed in the command #GET WCS POSLIMIT [...] is zero or too short. The calculation of a motion limit is not possible. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. The components of the direction vector must be programmed with a useful value. | ||
Parameter | %1: | Actual value [-] | |||
First component of the direction vector (VC1) | |||||
%2: | Actual value [-] | ||||
Second component of the direction vector (VC2) | |||||
%3: | Actual value [-] | ||||
Third component of the direction vector (VC3) | |||||
Error type | 1, Error message from NC-program. | ||||
|
21411 | Double programming in #FILTER command. | |||
| Description | In the command #FILTER ... [...] keywords are programmed several times or in wrong combinations. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. In thecommand #FILTER ... [...] remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21412 | Second main axis not allowed. | |||
| Description | In connection with the command #ROTATION and the function "rotation of several axes" the additional axes may only be linked to the second main axis (master axis) of the current plane. In case of error an inadmissible master axis is programmed as second main axis in the definition of the axes pairs. Example: Wrong: G00 X0 X1=0 X2=0 X3=0 Y0 Z0 G01 F1000 X1=0 X2=260 X3=520 X4=780 Y=-10 #ROTATION ON[ANGLE=1 G91 Y1=-1200 G91 Y1=1200 : N1000 M30 Correct: G00 X0 X1=0 X2=0 X3=0 Y0 Z0 G01 F1000 X1=0 X2=260 X3=520 X4=780 Y=-10 #ROTATION ON[ANGLE=1 G91 Y1=-1200 G91 Y1=1200 : N1000 M30 | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. Correct the definition of the axes pairs in the command #ROTATION | |
Error type | 1, Error message from NC-program. | |||
|
21413 | WAIT without SYN is not allowed. | |||
| Description | In the command #MACHINE DATA the keyword WAIT may only be used, if a synchronized setting (SYN) of an axis parameter is instructed. Example: Setting of a software limit switch with waiting in channel: Wrong: G00 X0 Y0 Z0 : #MACHINE DATA [AX=X : N1000 M30 Correct: G00 X0 Y0 Z0 : #MACHINE DATA SYN : N1000 M30 | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. Either complete the command #MACHINE DATA by the keyword SYN or remove WAIT. For more information see [PROG - Chapter Writing of machine data] | |
Error type | 1, Error message from NC-program. | |||
|
21414 | Spindle axis is not allowed. | |||
| Description | In combination with the keyword AX or AXNR in the command #FILTER [..] a spindle axis is programmed. But the programming only is allowed for path axes available in the NC channel. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. The command #FILTER [ ] is only useful for path axes in the NC channel. | |
Error type | 1, Error message from NC-program. | |||
|
21415 | Axis not referenced! Automatic trafo selection not possible. | ||||
| Description | A kinematic transformation may only be selected, if all axes, involved in transformation, are referenced. If the automatic trafo selection is activated by the channel parameter P-CHAN-00151 (auto_enable_kin_trafo), at manual mode selection (G200, G201) or at the first motion block in NC program it is checked, weather all trafo axes are referenced. If this is not the case, this error message is generated. | |||
Reaction | Class | 1 | Continue NC program processing. | ||
Solution | Class | 1 | Check and modify the NC program. For active channel parameter P-CHAN-00151 (auto_enable_kin_trafo) before the first motion all transformation axes must be referenced (G74). | ||
Parameter | %1: | Logical axis number [-] | |||
Number of the unreferenced axis | |||||
Error type | 1, Error message from NC-program. | ||||
|
21416 | New operation mode is not permitted if 3D tool geometry compensation is active. | ||||
| Description | While active 3D tool geometry compensation (TGC) in NC program a new operation mode (OPMODE) is programmed. This is not allowed. Example: Wrong: N10 #TGC ON [OPMODE=2] : N.. #TGC [OPMODE=1] : N.. #TGC OFF : N1000 M30 Correct: N10 #TGC ON [OPMODE=2] : N.. #TGC OFF N.. #TGC ON [OPMODE=1] ... or N.. #TGC [OPMODE=1] N.. #TGC ON : N1000 M30 | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. The setting of a new operation mode(OPMODE) is only allowed either in combination with a repeated selection of 3D-TGC or during inactive 3D-TGC. | ||
Parameter | %1: | Actual value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21417 | Invalid TGC-mode. | ||||
| Description | In the #TGC [ ] command the keyword OPMODE has an invalid value. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. Set the operation mode in the #TGC command on a permissible value[PROG]. | ||
Parameter | %1: | Actual value [-] | |||
Keyword | |||||
%2: | Incorrect value [-] | ||||
Invalid TGC-mode | |||||
Error type | 1, Error message from NC-program. | ||||
|
21418 | Double programming in #MEAS command. | |||
| Description | In the command #MEAS [...] keywords are programmed several times or in wrong combinations. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. In thecommand #MEAS [...] remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21419 | Override factor exceeds range of permissible value. | ||||
| Description | A programmed path or axis specific override factor (e.g. FEED_FACT ) exceeds the permissible value range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Programming of a permissible override factor (valid values:0.1% ... 200%,, see also [PROG - Description of the command #OVERRIDE or axis specific override programming] ). | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21420 | Double programming in #OVERRIDE command. | |||
| Description | In the command #OVERRIDE [...] keywords are programmed several times or in wrong combinations. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. In thecommand #OVERRIDE [...] remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21422 | Double programming in OVERRIDE command sequence. | |||
| Description | In the spindle specific override command S[OVERRIDE...] keywords are programmed several times or in wrong combinations. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. In thecommand sequence S[OVERRIDE...] remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21423 | Helpchannel without license, move only with link axis(see. P-AXIS-00101). | ||||
| Description | For the programmed NC function this channel requires a licence. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 6 | Please contact your distribution partner for a channel licence oder just use link axes. | ||
Parameter | %1: | Logical axis number [-] | |||
Number of the unlinked axis | |||||
Error type | 1, Error message from NC-program. | ||||
|
21424 | Invalid parameter setting of edge banding. | |||||||
| Description | During start-up the check of the edge banding parameters detects, that the setting of P-CHAN-00029 on 1 is only useful, if P-CHAN-00149 and P-CHAN-00153 are set on 0. | ||||||
Reaction | Class | 1 | Start-up of the control is continued. | |||||
Solution | Class | 1 | During start-up in case of conflict the block global edge banding P-CHAN-00029 is set to 0 (FALSE) and the start-up is continued. Before nextstart-up correct setting of the channel parameters P-CHAN-00029, P-CHAN-00149 and P-CHAN-00153: | |||||
P-CHAN-00029 | P-CHAN-00149 | P-CHAN-00153 | Check result | |||||
0 | 1 | 0 | OK | |||||
0 | 0 | 1 | OK | |||||
0 | 1 | 1 | OK | |||||
1 | 0 | 0 | OK | |||||
1 | 1 | 0 | NOT OK | |||||
1 | 0 | 1 | NOT OK | |||||
1 | 1 | 1 | NOT OK | |||||
Parameter | %1: | Incorrect value [-] | ||||||
Incorrect channel parameter P-CHAN-00029 | ||||||||
%2: | Corrected value [-] | |||||||
| ||||||||
Error type | 2, Error message by data transfer from parameter list into control device. | |||||||
|
21425 | Axis not referenced! Automatic trafo selection not possible. | ||||
| Description | A kinematic transformation may only be selected, if all axes, involved in transformation, are referenced. If the automatic trafo selection is activated by the channel parameter P-CHAN-00151 (auto_enable_kin_trafo), at manual mode selection (G200, G201) or at the first motion block in NC program it is checked, weather all trafo axes are referenced. If this is not the case, this error message is generated. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. For active channel parameter P-CHAN-00151 (auto_enable_kin_trafo) before the first motion all transformation axes must be referenced (G74). | ||
Parameter | %1: | Logical axis number [-] | |||
Number of the unreferenced axis | |||||
Error type | 1, Error message from NC-program. | ||||
|
21426 | Tool length is smaller than minimum limit value. | ||||
| Description | During taking over tool data it is detected, that the tool length is smaller than the permissible minimum length, defined by the channel parameter P-CHAN-00156. | |||
Reaction | Class | 3 | Abort of the running NC-program. | ||
Solution | Class | 6 | Check, if an alternative tool with a sufficient length is available. Then execute NC program with that tool. Alternative: Setting P-CHAN-00156 to 0 the check for minimum length is deselected. Restart NC control. | ||
Parameter | %1: | Incorrect value [-] | |||
Length of the requested tool. | |||||
%2: | Lower limit value [-] | ||||
Configurated minimum tool length | |||||
Error type | 3, Error message from communication. | ||||
|
21427 | Tool radius is smaller than minimum limit value. | ||||
| Description | During taking over tool data it is detected, that the tool radius is smaller than the permissible minimum radius, defined by the channel parameter P-CHAN-00157. | |||
Reaction | Class | 3 | Abort of the running NC-program. | ||
Solution | Class | 6 | Check, if an alternative tool with a sufficient radius is available. Then execute NC program with that tool. Alternative: Setting P-CHAN-00157 to 0 the check for minimum radius is deselected. Restart NC control. | ||
Parameter | %1: | Incorrect value [-] | |||
Radius of the requested tool. | |||||
%2: | Lower limit value [-] | ||||
Configurated minimum tool radius | |||||
Error type | 3, Error message from communication. | ||||
|
21429 | Name of external variable structure too long. | ||||
| Description | For the external variables it is possible to specify user-defined variable types e.g. for variable structures (s. [EXTV]). However, the given name for the variable type (type[i].name) is too long. | |||
Reaction | Class | 2 | Name of the variable structure is shortend. | ||
Solution | Class | 3 | Correct the name of the variable structure. | ||
Parameter | %1: | Actual value [-] | |||
Incorrect name | |||||
%2: | Actual value [-] | ||||
Index i of the variable type definition | |||||
%3: | Incorrect value [-] | ||||
Length of given name | |||||
%4: | Limit value [-] | ||||
Maximum permissible length of name | |||||
%5: | Corrected value [-] | ||||
Correct name for variable type | |||||
Error type | - | ||||
|
21430 | Invalid character in the name of the external variable structure. | ||||
| Description | For the external variables it is possible to specify user-defined variable types e.g. for variable structures (s. [EXTV]). However, the given name for the variable type (type[i].name) contains at least one invalid character. Permitted characters are letters, the numbers 0-9 and an underline. | |||
Reaction | Class | 2 | The variable type is deleted. | ||
Solution | Class | 3 | Correct name of the variable type. | ||
Parameter | %1: | Incorrect value [-] | |||
Incorrect name | |||||
%2: | Actual value [-] | ||||
Index i of the variable type definition | |||||
%3: | Actual value [-] | ||||
Position of the invalid character in the name | |||||
Error type | - | ||||
|
21431 | Name of external variable structure corresponds elementary data type. | ||||
| Description | For the external variables it is possible to specify user-defined variable types e.g. for variable structures (s. [EXTV]). However, the given name for the variable type (type[i].name) is equivalent to an elementary variable type of the numerical control. Default variable types of the numerical control are: - BOOLEAN - SGN08, SGN16, SGN32 - UNS08, UNS16, UNS32 - REAL64 - STRING | |||
Reaction | Class | 2 | The variable type is deleted. | ||
Solution | Class | 3 | Change name of the variable type. | ||
Parameter | %1: | Incorrect value [-] | |||
Incorrect name | |||||
%2: | Actual value [-] | ||||
Index i of the variable type defintion. | |||||
Error type | - | ||||
|
21432 | Name of the structure element too long. | ||||
| Description | For the external variables it is possible to specify user-defined variable types e.g. for variable structures (s. [EXTV]). However, the given name for the structure element (type[i].element[j].name) is too long. | |||
Reaction | Class | 2 | Name of the structure element is shortend. | ||
Solution | Class | 3 | Correct the name of the structure element. | ||
Parameter | %1: | Actual value [-] | |||
Name of the affected variable type | |||||
%2: | Actual value [-] | ||||
Incorrect element name | |||||
%3: | Incorrect value [-] | ||||
Length of given name | |||||
%4: | Limit value [-] | ||||
Maximum permissible length of name | |||||
%5: | Actual value [-] | ||||
Corrected name for the structure element | |||||
Error type | - | ||||
|
21433 | Invalid character in the name of the structure element. | ||||
| Description | For the external variables it is possible to specify user-defined variable types e.g. for variable structures (s. [EXTV]). However, the given name for the structure element (type[i].element[j].name) contains at least one invalid character. Permitted characters are letters, the numbers 0-9 and an underline. | |||
Reaction | Class | 2 | The structure element is deleted. | ||
Solution | Class | 3 | Correct the name of the structure element. | ||
Parameter | %1: | Actual value [-] | |||
Incorrect name | |||||
%2: | Actual value [-] | ||||
Index i of the variable type definition | |||||
%3: | Actual value [-] | ||||
Index j of the structure element | |||||
%4: | Incorrect value [-] | ||||
Incorrect name | |||||
%5: | Actual value [-] | ||||
Position of the invalid character in the name | |||||
Error type | - | ||||
|
21434 | Variable type identifier of structure element too long. | ||||
| Description | For the external variables it is possible to specify user-defined variable types e.g. for variable structures (s. [EXTV]). However, the given variable type of the structure element (type[i].element[j].type) is too long. | |||
Reaction | Class | 2 | Variable type is shortened. | ||
Solution | Class | 3 | Correct the variable type of the structure element. | ||
Parameter | %1: | Actual value [-] | |||
Name of affected variable type definition | |||||
%2: | Actual value [-] | ||||
Name of affected structure element | |||||
%3: | Actual value [-] | ||||
Given variable type | |||||
%4: | Incorrect value [-] | ||||
Length of given variable type | |||||
%5: | Limit value [-] | ||||
Maximum permissible length | |||||
Error type | - | ||||
|
21435 | Invalid character in the variable type of the structure element. | ||||
| Description | For the external variables it is possible to specify user-defined variable types e.g. for variable structures (s. [EXTV]). However, the given name for the variable type (type[i].element[j].name) contains at least one invalid character. Permitted characters are letters, the numbers 0-9 and an underline. | |||
Reaction | Class | 2 | The variable structure is deleted. | ||
Solution | Class | 3 | Correct the variable type of the structure element. | ||
Parameter | %1: | Actual value [-] | |||
Name of affected variable structure | |||||
%2: | Actual value [-] | ||||
Index j of affected structure element | |||||
%3: | Actual value [-] | ||||
Name of affected structure elment | |||||
%4: | Incorrect value [-] | ||||
Incorrect variable type name | |||||
%5: | Actual value [-] | ||||
Position of incorrect character | |||||
Error type | - | ||||
|
21436 | No elements in external variable structure. | ||||
| Description | For the external variables it is possible to specify user-defined variable types e.g. for variable structures (s. [EXTV]). The given variable type however has no elements (type[i].element[j]). | |||
Reaction | Class | 2 | The variable structure is deleted. | ||
Solution | Class | 3 | Define elements for the variable structure. | ||
Parameter | %1: | Actual value [-] | |||
Name of affected variable structure | |||||
%2: | Actual value [-] | ||||
Index i of affected variable structure | |||||
Error type | - | ||||
|
21437 | Variable type of external variable too long. | ||||
| Description | The identifier for the variable type of the external variable is too long (s. [EXTV]). | |||
Reaction | Class | 2 | Variable type is shortened. | ||
Solution | Class | 3 | Correct the variable type of the external variable. | ||
Parameter | %1: | Actual value [-] | |||
Name of the effected variable | |||||
%2: | Actual value [-] | ||||
Given variable type | |||||
%3: | Incorrect value [-] | ||||
Length of given variable type | |||||
%4: | Limit value [-] | ||||
Maximum permissible length | |||||
Error type | - | ||||
|
21438 | Invalid character in the variable type of the external variable. | ||||
| Description | The variable type identifier of the external variable contains at least one invalid character (s. [EXTV]). Permitted characters are letters, the numbers 0-9 and an underline. | |||
Reaction | Class | 2 | External variable is deleted | ||
Solution | Class | 3 | Correct the variable type identifier | ||
Parameter | %1: | Actual value [-] | |||
Name of the affected external variable | |||||
%2: | Actual value [-] | ||||
Index of the affected external variable | |||||
%3: | Incorrect value [-] | ||||
Incorrect variable type | |||||
%4: | Actual value [-] | ||||
Position of the invalid character | |||||
Error type | - | ||||
|
21439 | Memory index of the external variable exceeds valid range. | ||||
| Description | The external variables are stored in 24-byte blocks in the memory (s. [EXTV]). The memory block of an external variable is addressed with the memory index var[i].index. The given value for the memory index however exceeds valid range. | |||
Reaction | Class | 2 | The external variable is deleted. | ||
Solution | Class | 3 | Correct the memory index of the variable. | ||
Parameter | %1: | Actual value [-] | |||
Name of the affected external variable | |||||
%2: | Actual value [-] | ||||
Index i of the affected external variable | |||||
%3: | Incorrect value [-] | ||||
Incorrect value for memory index | |||||
%4: | Upper limit value [-] | ||||
Maximum permissible value for memory index | |||||
Error type | - | ||||
|
21440 | Maximum nesting depth in externel variable structure exceeded. | ||||
| Description | For the external variables it is possible to specify user-defined variable types e.g. for variable structures (s. [EXTV]). The elements of a variable type definition (type[I].element[j]) could also be a variable structure. However, the possible nesting depth is limited. | |||
Reaction | Class | 2 | The external variable is deleted. | ||
Solution | Class | 3 | Reduce the nesting depth of the structure definitions. | ||
Parameter | %1: | Actual value [-] | |||
Name of affected external variable | |||||
%2: | Actual value [-] | ||||
Index of the affected variable | |||||
%3: | Actual value [-] | ||||
Actual nesting depth | |||||
%4: | Upper limit value [-] | ||||
Maximum permissible nesting depth | |||||
Error type | - | ||||
|
21441 | Variable type in external variable structure unknown. | ||||
| Description | For the external variables it is possible to specify user-defined variable types e.g. for variable structures (s. [EXTV]). However, the variable type of a structure element (type[I].element[j].type) is unknown. It must be a user-defined type or a default variable type of the CNC. | |||
Reaction | Class | 2 | The external variable is deleted. | ||
Solution | Class | 3 | Correct the variable type of the structure element. | ||
Parameter | %1: | Incorrect value [-] | |||
Incorrect variable type | |||||
%2: | Actual value [-] | ||||
Name of the affected external variable | |||||
%3: | Actual value [-] | ||||
Index of the affected variable | |||||
%4: | Actual value [-] | ||||
Name of the variable structure | |||||
%5: | Actual value [-] | ||||
Name of the affected structure element | |||||
Error type | - | ||||
|
21442 | No variable type for structure element specified. | ||||
| Description | For the external variables it is possible to specify user-defined variable types e.g. for variable structures (s. [EXTV]). The variable type (type[i].element[j].type) for an element of the variable structure was not specified. | |||
Reaction | Class | 2 | Variable structure definition is deleted. | ||
Solution | Class | 3 | Specify a variable type for the structure element. | ||
Parameter | %1: | Actual value [-] | |||
Name of affected variable strucutre | |||||
%2: | Actual value [-] | ||||
Name of affected structure element | |||||
%3: | Incorrect value [-] | ||||
Incorrect variable type | |||||
Error type | - | ||||
|
21443 | Incompatible variable types. Assignment operation not possible. | |||
| Description | The assignment could not be executed due to incompatible variable types on the left and right side (s. [EXTV]) e.g. a SGN32 variable is assigned to an external variable structure: var[1].name var_1 var[1].type STRUCT_1 var[2].name var_2 var[2].type SGN32 Incorrect assignment in the NC-program: V.E.var_1 = V.E.var_2 | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Correct the nc program. | |
Error type | 1, Error message from NC-program. | |||
|
21444 | Structure copy only possible with equal structure types. | ||||
| Description | Copying of whole variable structures (structure copy) in the NC program requires variables with identical variable type (var[i].type, s. [EXTV]). Example: var[1].name var_1 var[1].type STRUCT_1 var[2].name var_2 var[2].type STRUCT_2 var[3].name var_3 var[3].type STRUCT_2 NC-program: Error: V.E.var_1 = V.E.var_2 Correct: V.E.var_2 = V.E.var_3 | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the nc program or change the variable type. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Incorrect value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21445 | Different size of variable structures. Structure copy not possible. | ||||
| Description | Copying of whole variable structures (structure copy) in the NC program requires variables with identical variable type var[i].type and identical variable size var[i].size (s. [EXTV]). | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the NC program. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Incorrect value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21446 | Assignement operation not permitted for variable structures. | |||
| Description | The assignment operator = (structure copy) is the only allowed operator for external variables, which are a variable structure (s. [EXTV]). The assignment operators +=, -=, += and /= could not be used. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Correct the NC program. | |
Error type | 1, Error message from NC-program. | |||
|
21447 | Structure copy only possible with two external variables. | |||
| Description | Copying of a whole variable structure (structure copy) is only possible between external variables (s. [EXTV]). The variable type of the two variables must be identical. Example: var[1].name var1 var[1].type STRUCT_1 var[2].name var2 var[2].type STRUCT_1 Assignment in the NC-program: Error: V.E.var1 = 123 Correct: V.E.var1 = V.E.VAR2 | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Correct the NC program. | |
Error type | 1, Error message from NC-program. | |||
|
21448 - 21450 |
| |||
| Description | This error message informs about internal states, error solutions and the place of error in the source.Please give the complete error message data to the CNC manufacturer. | ||
Reaction | Class | 2 |
| |
Solution | Class | 8 | Restart of NC-control necessary. |
21451 | Maximum number of tools per unit exceeds limit. | ||||
| Description | For the definition of a tool unit (UNIT) in NC command #TOOL DEF [...] too much tools T= are summarized. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify NC program. In #TOOL DEF [...] do not exceed the maximum permissible number of tools per unit. | ||
Parameter | %1: | Incorrect value [-] | |||
Decoded number of tools up to now | |||||
%2: | Limit value [-] | ||||
Maximum number of tools per unit | |||||
Error type | 1, Error message from NC-program. | ||||
|
21452 | Illegal UNIT value programmed. | ||||
| Description | The programmed tool unit (UNIT), defined by the NC command #TOOL DEF [...] can not be stored in the internal working data. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify NC program. Reduce number of unit definitions or if possible replace redundant definitions by new unit definitions. | ||
Parameter | %1: | Incorrect value [-] | |||
ID number of the programmed UNIT | |||||
%2: | Lower limit value [-] | ||||
Maximum number of permissible UNIT definitions | |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21453 | Double programming in #TOOL DEF command. | |||
| Description | In the command #TOOL DEF [...] keywords are programmed several times or in wrong combinations. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. In thecommand #TOOL DEF [...] remove the redundant keywords. | |
Error type | 1, Error message from NC-program. | |||
|
21454 | For the T function in NC channel still no complete tool data set is available. | ||||
| Description | There are no data available for the tools, which are grouped in the programmed tool unit. These data are necessary especially for the consideration of the tool offsets. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 1 | Case 1: Set channel parameter P-CHAN-00014 on 1 (TRUE). Thus during T word programming implicitly the tool data are completed. Case 2: Check and modify the NC program. Before the T word programming of the related D word. Thus the corresponding tool data are completed and available at the following T word. | ||
Parameter | %1: | Actual value [-] | |||
Programmed T number (UNIT) | |||||
Error type | 1, Error message from NC-program. | ||||
|
21455 | Combined string exceeds maximum permissible string length. | ||||
| Description | Two strings are combined with the + operator. The resulting string however is too long. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the NC program. | ||
Parameter | %1: | Incorrect value [-] | |||
Length of the compbined string | |||||
%2: | Upper limit value [-] | ||||
Maximum permissible string length | |||||
Error type | 1, Error message from NC-program. | ||||
|
21456 | Assignment operation not permitted for string variables. | |||
| Description | The assignment operators = and += could be used with string variables. The other operators -=, *= and /= are not allowed. Example with external variable (s. [EXTV]): var[1].name str1 var[1].type STRING Error: V.E.str1 *= Hello world! Correct: V.E.str1 = Hello V.E.str1 += world! | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Correct the NC program. | |
Error type | 1, Error message from NC-program. | |||
|
21457 | Incompatible data types in mathematical calculation or string operation. | ||||
| Description | The given expression contains mathematical terms and string expressions. It cannot be evaluated. Example: Error: V.E.string = Peter + 23 Correct: V.E.string = Peter + 23 V.E.string = Peter + INT_TO_STR[23] | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the NC program. Use converting functions. | ||
Parameter | %1: | Actual value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21458 | Operator not permitted for string expressions. | ||||
| Description | The + operator to combine two strings or the comparison operators == and != can be used with string expression. All other operators like -" or * are not permitted. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the NC program. | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21459 | Invalid argument type for function call. | ||||
| Description | The type of the argument for the function is invalid e.g. a mathematical function has received a string expression. Example: Error: SIN[Peter] STR_TO_INT[123] Correct: SIN[1.23] STR_TO_INT[123] | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the NC program. | ||
Parameter | %1: | Actual value [-] | |||
| |||||
%2: | Actual value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21460 | String expression expected. | |||
| Description | The result of the given expression is expected to be a string e.g. since it is assigned to a string variable. Example: Error: V.E.string = 100 + 10 Correct: V.E.string = 1 + 10 V.E.string = INT_TO_STR[100 + 10] | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Correct the NC program. Use conversion functions. | |
Error type | 1, Error message from NC-program. | |||
|
21461 | Mathematical term expected. | |||
| Description | The result of the given expression is expected to be a numerical value e.g. since it is assigned to an integer or REAL64 variable. Example: Error: V.E.sgn32 = 1" + 10 Correct: V.E.sgn32 = 100 + 10 V.E.sgn32 = STR_TO_INT[1 + 10] | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Correct the NC program. Use conversion functions. | |
Error type | 1, Error message from NC-program. | |||
|
21462 | String for variable too long. | ||||
| Description | A string is assigned to a variable of type string, but the string is too long for the variable. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the NC program. | ||
Parameter | %1: | Incorrect value [-] | |||
Length of string | |||||
%2: | Upper limit value [-] | ||||
Maximum string length of variable | |||||
Error type | 1, Error message from NC-program. | ||||
|
21463 | Argument of integer string conversion exceeds valid range. | ||||
| Description | The function INT_TO_STR converts an integer number to a string. However, the given number exceeds valid range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the NC program. | ||
Parameter | %1: | Incorrect value [-] | |||
Given value for conversion | |||||
%2: | Lower limit value [-] | ||||
Minimum permissible value | |||||
%3: | Upper limit value [-] | ||||
Maximum permissible value | |||||
Error type | 1, Error message from NC-program. | ||||
|
21464 | Numeric character for string to number conversion expected. | |||
| Description | The function STR_TO_INT and STR_TO_REAL convert a string to an integer or to a floating-point value. For the conversion the string is expected to contain the numeric characters 0 .. 9. | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Correct the NC program. | |
Error type | 1, Error message from NC-program. | |||
|
21465 | String too long for string to number conversion. | ||||
| Description | The function STR_TO_INT and STR_TO_REAL convert a string to an integer or to a floating-point value. The string however contains too many numeric characters. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the NC program. | ||
Parameter | %1: | Upper limit value [-] | |||
Maximum permissible length | |||||
Error type | 1, Error message from NC-program. | ||||
|
21466 | Result of string to number conversion exceeds valid range. | ||||
| Description | The function STR_TO_INT converts a string to an integer value. The calculated value however exceeds valid range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the NC program. | ||
Parameter | %1: | Incorrect value [-] | |||
Converted value | |||||
%2: | Lower limit value [-] | ||||
Minimum permissible value | |||||
%3: | Upper limit value [-] | ||||
Maximum permissible value | |||||
Error type | 1, Error message from NC-program. | ||||
|
21467 | Exponent of string to floating point number conversion exceeds valid range. | ||||
| Description | The function STR_TO_REAL converts a string to a floating-point number. The calculated exponent however exceeds valid range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the NC program. | ||
Parameter | %1: | Upper limit value [-] | |||
Maximum permissible exponent | |||||
Error type | 1, Error message from NC-program. | ||||
|
21468 | 'REPEAT' must be programmed exclusively in NC-block. | |||
| Description | In the same NC block a control block command was programmed together with other NC commands. After a $REPEAT no further NC commands may be programmed. Example: Wrong: N10 G00 X0 Y0 Z0 P1=0N20 $REPEAT P1=P1+1:N50 $UNTIL P1>2:N1000 M30 Correct: N10 G00 X0 Y0 Z0 P1=0N20 $REPEAT N30 P1 =P1+1 :N50 $UNTIL P1>2:N1000 M30 | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify NC program. Move the not permissible NC commands after $REPEAT to other NC blocks or delete them. | |
Error type | 1, Error message from NC-program. | |||
|
21469 | Unexpected 'UNTIL'; it does not match the actual control block. | |||
| Description | A control block statement was programmed in incomplete syntax. A $UNTIL can only be programmed in combination with a previous $REPEAT. Example: Wrong: N10 G00 X0 Y0 Z0 P1=1N20 $UNTIL P1>2 : N1000 M30 Correct: N10 G00 X0 Y0 Z0 P1=1N15 $REPEAT:N20 $UNTIL P1>2:N1000 M30 | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify the NC program sequence. Insert a $REPEAT command or remove the $UNTIL command. | |
Error type | 1, Error message from NC-program. | |||
|
21470 | After 'UNTIL' only the condition is permissible. | |||
| Description | In the same NC block a control block command was programmed together with other NC commands. After a $UNTIL command only the necessary condition may be programmed. Example: Wrong: N10 G00 X0 Y0 Z0 N20 P2=10 N30 $REPEAT : N40 $UNTIL P2 > 20G01 X100 F1000 : N1000 M30 Correct: N10 G00 X0 Y0 Z0 N20 P2=10 N30 $REPEAT : N40 $UNTIL P2 > 20 N45 G01 X100 : N1000 M30 | ||
Reaction | Class | 2 | Abort of the NC program processing. | |
Solution | Class | 3 | Check and modify NC program. Move the not permissible NC commands to other NC blocks or delete them. | |
Error type | 1, Error message from NC-program. | |||
|
21471 | Not enough parameter for function call. | ||||
| Description | Too less parameter was passed to the programmed function.
Correct: N10 V.E.string = LEFT[Hello world!, 5] | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the NC program. | ||
Parameter | %1: | Actual value [-] | |||
| |||||
%2: | Actual value [-] | ||||
Name of programmed function | |||||
%3: | Incorrect value [-] | ||||
Number of given parameters | |||||
%4: | Expected value [-] | ||||
Expected number of parameters | |||||
Error type | 1, Error message from NC-program. | ||||
|
21472 | Parameter value for number of characters in string operation invalid. | ||||
| Description | For the string operation the desired number of characters must be specified. The value of the parameters is however smaller or greater than permissible. Example: N10 V.E.string = LEFT[Hello world!, 100000] Correct: N10 V.E.string = LEFT[Hello world!, 5] | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the NC program. | ||
Parameter | %1: | Actual value [-] | |||
Name of programmed function | |||||
%2: | Actual value [-] | ||||
Number of incorrect parameter | |||||
%3: | Incorrect value [-] | ||||
Incorrect value | |||||
%4: | Lower limit value [-] | ||||
Mimimum permissable value | |||||
%5: | Upper limit value [-] | ||||
Maximum permissible value | |||||
Error type | 1, Error message from NC-program. | ||||
|
21473 |
| |||
| Description | This error message informs about internal states, error solutions and the place of error in the source.Please give the complete error message data to the CNC manufacturer. | ||
Reaction | Class | 2 |
| |
Solution | Class | 8 | Restart of NC-control necessary. |
21474 | Too many parameters for function call. | ||||
| Description | Too many parameters were passed to the programmed function.
Correct: N10 V.E.string = LEFT[Hello world!, 5] | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Correct the NC program. | ||
Parameter | %1: | Actual value [-] | |||
| |||||
%2: | Actual value [-] | ||||
Name of programmed function | |||||
%3: | Upper limit value [-] | ||||
Number of given parameters | |||||
Error type | 1, Error message from NC-program. | ||||
|
21475 |
| |||
| Description | This error message informs about internal states, error solutions and the place of error in the source.Please give the complete error message data to the CNC manufacturer. | ||
Reaction | Class | 2 |
| |
Solution | Class | 8 | Restart of NC-control necessary. |
21476 | Streaming data has no correct end-of-line mark. | |||
| Description | The data block reading via the streaming interface exceeds the permissible internal cache length. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check, if there is a too long block in NC program. If possible, segmentize this block in several shorter blocks. Ensure, that in NC program the correct Windows conform end of line marks are used (carriage return + line feed). | |
Error type | - | |||
|
21477 | Backward jump during streaming not allowed. | |||
| Description | During streaming in NC program a backward jump with $GOTO shall be executed. This is not allowed. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. Linearize or redesign the program sequence in a way, that backward jumps will not be necessary any longer. Hint: Foreward jumps with$GOTOduring streaming are allowed! | |
Error type | 1, Error message from NC-program. | |||
|
21478 | Loop during streaming not allowed. | |||
| Description | During streaming in NC program a loop ($FOR, $WHILE, $DO, $REPEAT ) shall be executed. This is not allowed. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. Linearize or redesign the program sequence in a way, that loops will not be necessary any longer. | |
Error type | 1, Error message from NC-program. | |||
|
21479 | Call of local sub program during streaming not allowed. | |||
| Description | During streaming in NC program a local sub program (LL ) shall be executed. This is not allowed. | ||
Reaction | Class | 2 | Abort of the running NC-program. | |
Solution | Class | 3 | Check and modify the NC program. Linearize or redesign the program sequence in a way, that local sub programs will not be necessary any longer. If possible replacing of local sub programs by global sub programs(L...). | |
Error type | 1, Error message from NC-program. | |||
|
21480 | Jump inside a loop is not allowed. | ||||
| Description | Within a loop ($FOR, $WHILE, $DO, $REPEAT ) a jump via $GOTO shall be executed. This is not allowed. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. Linearize or redesign the program sequence within the loop in a way, that jumps will not be necessary any longer. Hint: A loop always can be left completely. | ||
Parameter | %1: | Incorrect value [-] | |||
Name of the loop with the programmed jump | |||||
Error type | 1, Error message from NC-program. | ||||
|
21481 | Active synchronous axes are not permitted to move independent. | ||||
| Description | While active synchronous operation ( #SET AX LINK[...]) for aselected master axis an independent axis movement is programmed. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Modify the sequence of NC program, for example deselect the synchronous operation before programming the "master" axis as independent axis. | ||
Parameter | %1: | Logical axis number [-] | |||
Number of the axis, which is already moved as master axis | |||||
%2: | Actual value [-] | ||||
Number of the selected coupling group | |||||
Error type | 1, Error message from NC-program. | ||||
|
21482 | Invalid parameter setting of synchronization tolerance. | ||||
| Description |
| |||
Reaction | Class | 1 |
| ||
Solution | Class | 1 |
| ||
Parameter | %1: | Incorrect value [0.1 µm or 0,0001°] | |||
| |||||
%2: | Corrected value [0.1 µm or 0,0001°] | ||||
| |||||
Error type | 2, Error message by data transfer from parameter list into control device. | ||||
|
21483 | Invalid parameter setting for velocity factor on hold limits. | ||||
| Description |
| |||
Reaction | Class | 1 |
| ||
Solution | Class | 1 |
| ||
Parameter | %1: | Incorrect value [0.1 µm or 0,0001°] | |||
| |||||
%2: | Corrected value [0.1 µm or 0,0001°] | ||||
| |||||
Error type | 2, Error message by data transfer from parameter list into control device. | ||||
|
21484 | Invalid parameter setting of hold limit tolerance. | ||||
| Description |
| |||
Reaction | Class | 1 |
| ||
Solution | Class | 1 |
| ||
Parameter | %1: | Incorrect value [0.1 µm or 0,0001°] | |||
| |||||
%2: | Corrected value [0.1 µm or 0,0001°] | ||||
| |||||
Error type | 2, Error message by data transfer from parameter list into control device. | ||||
|
21485 | Name of the external variable is defined twice. | ||||
| Description | While the initialization of the external variables it is detected, that a variable name is already used in another definition. An access to the incorrect variable is not possible in the NC program. The name of the variable is set on /0. | |||
Reaction | Class | 2 | NC start-up is continued. | ||
Solution | Class | 3 | Check and modify the name of the external variable before next start-up in the list of the external variables. To avoid the error message set a unique name in the list [EXTV]. | ||
Parameter | %1: | Actual value [-] | |||
Name of the multiple defined variable names | |||||
%2: | Actual value [-] | ||||
List index of the first variable of the same name | |||||
%3: | Incorrect value [-] | ||||
List index of the second variable of the same name | |||||
Error type | - | ||||
|
21486 | Double programming in #MIRROR-command. | ||||
| Description | In the command #MIRROR [...] keywords are programmed several times or in wrong combinations. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. In thecommand #MIRROR [...] remove the redundant keywords. | ||
Parameter | %1: | State [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21487 | Linkage of (A)CS during active #MIRROR not allowed. | ||||
| Description | Further coordinate systems should be activated after selection of#MIRROR [...]. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. The linkage of the coordinate system must be programmed before theselection of#MIRROR [...]. | ||
Parameter | %1: | Actual value [-] | |||
Type of the error causing coordinate system. | |||||
Error type | 1, Error message from NC-program. | ||||
|
21488 | Value for the maximum radius difference exceeds limit. | ||||
| Description | During the start-up check of the channel parameters is was detected that the absolute radius difference P-CHAN-00171 excceds the maximum limit of 100mm. | |||
Reaction | Class | 3 | NC start-up is continued. | ||
Solution | Class | 6 | During start-up in case of conflict the absolute radius difference P-CHAN-00171 is set to 1000000 [0.1μm] and the start-up is continued. | ||
Parameter | %1: | Incorrect value [0.1 µm or 0,0001°] | |||
| |||||
%2: | Corrected value [0.1 µm or 0,0001°] | ||||
| |||||
Error type | 2, Error message by data transfer from parameter list into control device. | ||||
|
21489 | Double programming in #ORI MODE-command. | ||||
| Description | In the command #ORI MODE [...] keywords are programmed several times or in wrong combinations. | |||
Reaction | Class | 2 | Abort of the running NC-program. | ||
Solution | Class | 3 | Check and modify the NC program. In thecommand #ORI MODE [...] remove the redundant keywords. | ||
Parameter | %1: | State [-] | |||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21490 | Invalid number of transformation axes at ORI MODE selection. | ||||
| Description | The #ORI MODE[] command was programmed without correct active complete kinematic transformation with orientation axes. For more detailed information see [PROG], [KITRA], [CHAN]. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and correct the nc program. | ||
Parameter | %1: | Actual value [-] | |||
Kinematic ID | |||||
%2: | Incorrect value [-] | ||||
Number of transformation axes of active kinematic transformation. | |||||
%3: | Lower limit value [-] | ||||
Minimum number of necessary transformation axes. | |||||
Error type | 1, Error message from NC-program. | ||||
|
21491 | Invalid kinematic type for ORI MODE selection. | ||||
| Description | The #ORI MODE[] command was programmed without correct active complete kinematic transformation with orientation. The kinematic ID can be defined in tool or channel parameters or can be selected in NC programm via #KIN ID[] command. For more detailed information see [PROG], [KITRA], [CHAN]. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and correct nc program and if necessary tool parameter or channel parameters. | ||
Parameter | %1: | Actual value [-] | |||
Active kinematic ID. | |||||
Error type | 1, Error message from NC-program. | ||||
|
21492 | Error in calculation angle from vector components. | ||||
| Description | The #ORI MODE[] function is active. If the last rotation in sequence is around the tool axis there is no change in orientation of tool. There is a change in tool coordinate system orientation. The tool coordinate system is defined with kinematic parameters which are presetted in channel or tool parameters. For more detailed information see [PROG], [KITRA], [CHAN]. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and correct parameters. | ||
Parameter | %1: | Actual value [-] | |||
| |||||
%2: | Actual value [-] | ||||
| |||||
%3: | Actual value [-] | ||||
| |||||
%4: | Actual value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21493 | Value for the maximum relative radius difference excceds limit. | ||||
| Description | During the start-up check of the channel parameters is was detected that the relative radius difference P-CHAN-00172 excceds the maximum limit of 500 [0.1%]. | |||
Reaction | Class | 3 | NC start-up is continued. | ||
Solution | Class | 6 | During start-up in case of conflict the relative radius difference P-CHAN-00172 is set to 500 [0.1%] and the start-up is continued. | ||
Parameter | %1: | Incorrect value [0.1 µm or 0,0001°] | |||
| |||||
%2: | Corrected value [0.1 µm or 0,0001°] | ||||
| |||||
Error type | 2, Error message by data transfer from parameter list into control device. | ||||
|
21494 | Additive M value exceeds range of data format. | ||||
| Description | The additional value programmed with the M word (M<expr>=<additive_expr>) exceeds the permissible data range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Use a permissible additional M value (negative oder positive integer). | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21495 | Additive H value exceeds range of data format. | ||||
| Description | The additional value programmed with the H word (H<expr>=<additive_expr>) exceeds the permissible data range. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program. Use a permissible additional H value (negative oder positive integer). | ||
Parameter | %1: | Incorrect value [-] | |||
| |||||
%2: | Lower limit value [-] | ||||
| |||||
%3: | Upper limit value [-] | ||||
| |||||
Error type | 1, Error message from NC-program. | ||||
|
21496 | Coupling group is already active. Selection is ignored. | ||||
| Description | The selection of a coupling group with #ENABLE AX LINK [...] or #AX LINK ON [...] is not executed because this coupling group is already active. | |||
Reaction | Class | 1 | NC program processing is continued. Re-selection is ignored. | ||
Solution | Class | 1 | Check and modify the NC program. Remove redundant selection of coupling group. | ||
Parameter | %1: | Actual value [-] | |||
ID-number of the already active coupling group. | |||||
Error type | 1, Error message from NC-program. | ||||
|
21497 | Number of axes of a channel exceeds range of permissible values of the CNC export version. | ||||
| Description | The CNC export version only allows a limited number of path axes per NC channel.During start-up the check of the channel parameters detects, that in the axes group the real number of configurated path axes P-CHAN-00007exceeds the permissible limit value. | |||
Reaction | Class | 3 | NC start-up is aborted. | ||
Solution | Class | 7 | Consider the permissible number of path axes during configuration. | ||
Parameter | %1: | Incorrect value [-] | |||
Configurated number of path axes | |||||
%2: | Limit value [-] | ||||
Permissible number of path axes | |||||
Error type | 2, Error message by data transfer from parameter list into control device. | ||||
|
21498 | Contouring mode 6 in combination with a lead axis is not allowed. | ||||
| Description | The parametrization with #CONTOUR MODE [DIST_SOFT...] can not be executed, because at least one of the channel axes is configurated as lead axis. | |||
Reaction | Class | 2 | Abort of the NC program processing. | ||
Solution | Class | 3 | Check and modify the NC program or configuration. Either selection of another contouring mode or configuration of all channel axes with a permissible axis mode according to P-AXIS-00015. | ||
Parameter | %1: | Actual value [-] | |||
Identifier of the programmed contouring mode | |||||
%2: | Logical axis number [-] | ||||
Number of the axis, which is defined as lead axis | |||||
Error type | 1, Error message from NC-program. | ||||
|
21499 | Default axes configuration after reset with active "reset_no_axis_to_axv" not allowed. | ||||
| Description | During start-up the check of the channel parameters detects, that the setting of P-CHAN-00179 on 1 is only useful, if P-CHAN-00075 is set on 0. | |||
Reaction | Class | 1 | Start-up of the control is continued. | ||
Solution | Class | 1 | During start-up in case of conflict P-CHAN-00075 is set to 0 (FALSE) and the start-up is continued. Before nextstart-up correct setting of the channel parameters P-CHAN-00179 and P-CHAN-00075. | ||
Parameter | %1: | Incorrect value [-] | |||
Incorrect channel parameter P-CHAN-00075 | |||||
%2: | Corrected value [-] | ||||
| |||||
Error type | 2, Error message by data transfer from parameter list into control device. | ||||
|