ER22 - Active leveling correction failed

During the active leveling process, the printer will move the bed up to the nozzle to detect the height of each print core and any possible variations in the build plate. During printing, the firmware will then correct for these offsets during printing.

When something goes wrong during the active leveling process, this error might appear. There can be several reasons for this. This page contains some quick tips to improve active leveling reliability. For more in-depth advice on troubleshooting active leveling problems, please check this page:

Active leveling errors


In case of an ER22, the error often appears because the detected values are too far out of range for reliable compensation. This can be due to material left on the nozzle, or a skewed build plate.

Clean the printer Before you retry the active leveling, ensure that the tips of the print cores and the build plate are clean. Any material stuck to these components can cause inaccurate readings during the leveling process.
Don't touch the printer While the Ultimaker 3 is going through the active leveling process, do not touch the printer or the print head. This can interrupt the process and corrupt the measurements. Also, ensure that no other machinery nearby could be causing interference.
Stable surface Ensure that the printer is placed on a flat, stable, and level surface. This is important during printing to ensure optimal print quality and also during the leveling process as vibrations can interfere with the measurements.
Manual leveling If the build plate is too skewed or raised too far, the firmware cannot use the active leveling measurements to compensate for this during printing. Relevel the build plate using the calibration card. Ensure the build plate is not too high; reset the position to 14 mm as described here.

If you require further support, please contact us by submitting a ticket.

Please ensure to include the error number (ERXX) and your printer's log files.


Was this article helpful?
1 out of 9 found this helpful



Article is closed for comments.