- Joined
- Feb 19, 2024
- Messages
- 32
- Reaction score
- 0
| Code | Description | Why this error occurs | Solution |
| 100 | Copying Gcode file from USB to local; Copying error, printing not started | / | / |
| 101 | AI detection prompt Key:101, A print quality problem has been detected and printing has been paused AI detected an issue during printing, printing paused | 1.False trigger due to using colored consumables 2.Triggered by printing failure | 1. If it is a false trigger or human judgment can continue printing, you can click continue printing on the machine screen/slicing software/creative cloud at any end 2. If printing fails, you need to clean the machine and re-initiate printing 3. The function can be turned off in System Settings - Camera - AI function |
| 102 | / | Current gcode file name is too long | / |
| 103 | AI detection prompt Key:103, A print quality problem has been detected and printing has been paused | First layer detection result abnormal, printing paused | 1. If false trigger or user decides it's safe to continue, click to resume print on machine screen, slicing software or Creativity Cloud 2. If print failure, clean machine and restart printing 3. To disable feature, go to System Settings - Camera - AI Function |
| 104 | Error Key:104, Foreign object detected on the printing platform, printing paused | Heat bed foreign object detection abnormal, printing paused Possible reasons: 1. Special patterns on the printing platform surface triggered falsely 2. White residue on the printing platform surface triggered falsely 3. Placement of other items on the printing platform triggered | / |
| 108 | / | Laser radar offset correction failure | / |
| 109 | Error Key:109, Fan feedback exception | Heat break fan abnormal, printing paused | / |
| 110 | / | Main MCU hardware connection abnormal | / |
| 111 | / | Nozzle MCU hardware connection abnormal | / |
| 112 | / | Heat bed MCU hardware connection abnormal | / |
| 500 | AI detection prompt Key:500, Printing quality problems detected by AI | AI detected an issue during printing, only a prompt is given | / |
| 501 | Error Key:501, Heat break fan exception | 1. Loose terminal connector 2. Fan stuck by screw during installation 3. Fan damaged | 1. Remove the nozzle cover and small board, check whether the heat sink fixing screws have fallen into the heat break fan, tighten the screws fixing the heat sink fan 2. Replug the heat break fan terminal 3. Replace the heat break fan [501 error code handling process] |
| 502 | Error Key:502, Mainboard fan exception | Mainboard fan abnormal Possible reasons: 1. Loose terminal connector 2. Fan stuck by screw during installation 3. Fan damaged | / |
| 503 | / | First layer detection abnormal, only a prompt is given | / |
| 504 | AI detection prompt Key:504, Current file does not support flow detection | Flow detection abnormal, only a prompt is given | / |
| 505 | AI detection prompt Key:505, AI LiDAR anomaly | Laser radar does not exist, only a prompt is given | 1. Check laser radar wiring 2. Replace laser radar |
| 506 | AI detection prompt Key:506, AI LiDAR calibration failure | Laser radar calibration failure, only a prompt is given | / |
| 507 | Laser radar calibration failed, only a prompt | Laser radar calibration failure, only a prompt is given | / |
| 508 | Error Key:508, Current storage space usage has reached %s, please clean up in time | / | / |
| 2000 | Error Key:2000, Unknown exception | Cannot update MCU configuration because MCU is turned off | Restart first; check the connection line |
| 2001 | Error Key:2001, Unknown exception | 1. Unable to read the register status of the E-axis drive IC, a timeout occurred 2. Poor contact or interference with the communication line between the mainboard and the nozzle leads to a timeout of the nozzle MCU communication | 1. Resend the nozzle board 2. Resend the nozzle cable |
| 2002 | / | Host cannot connect | / |
| 2014 | Slicing distance is negative or greater than entire movement length | 1. Problem with the printing file, not using the official slicing, or selecting the wrong model 2. System error | 1. Check whether the official slicing is used, whether the third-party slicing configuration is provided by the official, and whether the official slicing model is selected correctly 2. Restart and re-initiate printing after |
| 2016 | / | Printing not paused, recovery aborted | / |
| 2019 | / | Target temperature {0} exceeds the set range ({1}:{2}) | / |
| 2020 | / | Homing error: {0} | / |
| 2021 | / | {0} homing timeout error | / |
| 2056 | / | No data measured by the {0} axis accelerometer | / |
| 2057 | / | Unknown exception | / |
| 2060 | / | / | 1. Unplug the nozzle terminal 2. Replace the nozzle connection line 3. Restart |
| 2065 | / | Unable to set ADXL345 register [0x%x] to 0x%x: got 0x%x. This usually means connection problems (like wiring faults) or ADXL345 chip failure. | Replace the nozzle small board |
| 2069 | / | There is a "M107 P3" code in the slicing file | Confirm whether the slicing software is the latest version, then re-slice |
| 2090 | / | Timer off, this usually means that the host is overloaded. | / |
| 2091 | / | Missed the next schedule, this usually means intermittent communication failure between the microcontroller and the host. | / |
| 2092 | / | ADC out of range, this usually happens when the heater temperature exceeds its configured minimum or maximum temperature. | / |
| 2093 | / | Reschedule timer in the past, step too far in the past, when the microcontroller requests to step at a rate higher than its capability. | / |
| 2095 | / | Must return to the origin first | / |
| 2111 | Error Key: 2111, Unknown exception | The extrusion temperature is below the minimum temperature set by the machine configuration, and the minimum limit for CrealityOS is 170 degrees | 1. Slicing problem, please use the official slicing or contact the official to use the third-party slicing configuration file provided by the official 2. Problem caused by key2507, stop printing, heat the nozzle, if error ket2507 is reported, please refer to the error handling scheme of 2507 |
| 2112 | / | Movement exceeds maximum stretch ({0}mm^2 vs {1}mm^2) <br /> For detailed information, please refer to the "Maximum Extrusion Cross Section" configuration option | / |
| 2113 | / | The extruder is not configured | / |
| 2114 | / | Extrusion when there is no extruder | / |
| 2115 | / | Unknown value {0} in enumeration type {1} | / |
| 2116 | / | Invalid output format {0} | / |
| 2117 | / | Extra data at the end of the message | / |
| 2118 | / | Cannot query adxl345 fifo | / |
| 2119 | / | Invalid adxl345 id (got {0} vs {1}). This usually indicates a connection problem (e.g., wiring failure) or adxl345 chip failure | / |
| 2210 | / | Unable to automatically load filament, the extruder is below the minimum temperature | / |
| 2211 | / | Printing has been paused | / |
| 2242 | / | First zero: {0} {1} {2} [{3}] | / |
| 2243 | / | Out of range: {0} {1} {2} [{3}] | / |
| 2252 | / | The minimum value of parameter {0} must be {1} | / |
| 2253 | / | The maximum value of parameter {0} must be {1} | / |
| 2283 | / | Printer not ready | / |
| 2295 | / | Failed to restart MCU{0} | / |
| 2298 | / | Unable to update MCU{0} configuration because it's turned off | / |
| 2299 | / | Unable to configure MCU {0} | / |
| 2300 | / | Error occurred during MCU{0} configuration: {1} | / |
| 2308 | / | No data measured from {0}-axis accelerometer | / |
| 2313 | / | Internal error occurred while processing accelerometer data{0} | / |
| 2340 | / | The temperature required by heater%s (%.1f) is out of range (%.1f:%.1f) | / |
| 2343 | / | Main mcu connection timeout | / |
| 2344 | / | Nozzle mcu connection timeout | / |
| 2345 | / | Heat bed mcu connection timeout | / |
| 2503 | Error Key:2503, Unknown exception | Unable to read Z-axis stress film data | / |
| 2504 | Error Key:2504, Unknown exception | Z zeroing exception | / |
| 2505 | Error Key:2505, Unknown exception | Motor driver chip TMC exception Possible causes: Overheating: main board fan anomaly, low voltage: printing speed is too fast | / |
| 2506 | Error Key:2506, Unknown exception | Communication exception Possible causes: Common problem: 1, nozzle wiring problem | / |
| 2509 | Error Key:2509, Unknown exception | Nozzle sensor temperature anomaly | / |
| 2510 | Error Key:2510, Unknown exception | Heat bed sensor temperature anomaly | / |
| 2511 | Error Key:2511, Unknown exception | Cavity temperature anomaly | / |
| 2512 | / | Main MCU chip temperature anomaly | / |
| 2513 | / | Command format is incorrect | / |
| 2514 | / | Command parameter format is incorrect | / |
| 3002 | / | When not printing, nozzle communication exception, main board side nozzle wire is not inserted in place Possible causes: Check the terminal contact problem on the main board side | / |
| 2520 | Reading pressure sensor timeout, i.e. this read HX711 needs 11ms, but actual HX711 still not ready after 25ms | Replace leveling board | If occurs frequently, replace machine |
| 2521 | Error Key:2521, Leveling Sensor Chip Anomaly or Sensor Damage | The pressure data read is a constant value, such as always being -1 Possible causes: Z-axis sensor chip anomaly or sensor damage | / |
| 2522 | Error Key:2522, Level Sensor Data Transmission Anomaly | The pressure sensor cannot detect pressure, i.e., before and after placing heavy objects on the hot bed, the pressure data collected does not change Possible causes: Z-axis sensor chip anomaly or sensor damage | / |
| 2523 | Error Key:2523, Level Sensor Data Transmission Anomaly | During measurement, serial port packet loss, or Z-axis stuck timeout did not trigger, thus losing pressure data. Possible causes: Z-axis sensor data transmission anomaly | / |
| 2524 | Error Key:2524, Leveling sensor chip abnormality, sensor damage or environmental impact. | The pressure data noise collected when the machine is stationary is too large Possible causes: Z-axis sensor chip anomaly, sensor damage or environmental impact | / |
| 2526 | Error Key:2526, Z-axis movement not smooth or lead screw rotation not smooth | Z-axis motor, during leveling process, loses steps, and still loses steps after deceleration retesting Possible causes: Z-axis movement not smooth, or lead screw rotation not smooth | / |
| 2527 | Error Key:2527, Level Sensor Data Transmission Anomaly | During measurement, after triggering, serial port packet loss results in incomplete motor step data received Possible causes: Z-axis sensor data transmission anomaly | / |
| 2529 | Error Key:2529, Leveling sensor chip abnormality, sensor damage or environmental impact. | When G28 Z-axis zeroing, the number of measurements exceeds the limit (maximum 20 times) Possible causes: Z-axis sensor chip anomaly, sensor damage or environmental impact | / |
| 2532 | Error Key:2532, Abnormal wiring connection or poor contact | The synchronization wire between the two MCUs is not working properly (disconnected) Possible causes: Abnormal wiring connection or poor contact | / |
| 2533 | Error Key:2533, Parameter anomaly, please re-level | In the case of CHECK_BED_MESH AUTO_G29=0, i.e., leveling is not allowed, but the hot bed does not match the leveling data Possible causes: Parameter anomaly | / |
| 2560 | / | Communication with main MCU is abnormal Possible causes: Communication with the lower machine is lost, and the upper machine has not received data for more than 5 seconds | Check the wiring, restart. |
| 2561 | / | Communication with nozzle MCU is abnormal | Check the wiring, restart. |
| 2562 | / | Communication with heat bed MCU is abnormal | Check the wiring, restart. |
| 2563 | / | Communication with rpi MCU is abnormal | Check the wiring, restart. |
| 2564 | Error Key:2564, The nozzle is not heating as expected | The nozzle is not heating as expected Possible causes: The nozzle heating is turned on, but the temperature is not rising | Check the ceramic heating block and heating wiring, reinsert the terminal, check whether the ceramic heating ring is broken or damaged, check whether the terminal is loose, whether the thermistor base and heating rod base are loose; if damaged, please contact cs heat bed is not heating as expected |
| 2565 | Hotbed not heating as expected | The heat bed heating is turned on, but the temperature is not rising | Please reinsert the hotbed wiring and check if the soldering point of the heated bed power supply is desoldered. If so, please contact [email protected] |
