Notifications
Clear all

Some problem encountered, z leveling enforced  

  RSS
gnat
 gnat
(@gnat)
Noble Member
Some problem encountered, z leveling enforced

So what I've found searching seems to be about the issue happening in a consistent location and almost always due to something between the bed and plate or the PINDA is wonky. While the location has gotten more consistent it can still be random, I have wiped down between the bed and plate, and my PINDA appears to be working fine.

Currently it is most consistently failing in the 3rd location of the 7x7 test, but it also likes to fail on the last two rows as well (usually on either side of the middle). What else can I look to for causing this?

History:

  • Is 3.5 years old and started as a MK3.
  • Upgraded to a MK3S 3 years ago.
  • Installed Nyloc bed mod 3 years ago.
  • Upgraded to Bondtech extruder ~2 years ago.
  • Switched to a Revo hotend recently.
  • Updated to 3.10.1 when I installed the Revo.
  • Everything was working fine until the bed thermo started acting up (and trashed a 235 hour print at the 50% mark) and then the hotend thermo bit it as well.
    • Couldn't replicate or confirm the bed issues.
    • Hotend cable got rubbed through and the core was replaced by E3D.
  • Rebuilt it this weekend and did the following things:
    • Replaced the Revo core and also swapped nozzles as the one I was using was nasty with PETG.
    • Replaced the bed thermo
    • Replaced the bed u-bolts with the S+ mounts.
    • Replaced the Y bearings with Drylin bushings.
    • Replaced the Y rod mounts with the S+ mounts.
    • Changed to the Big Einsy+MMU case.

After rebuilding it went through the selftest, XYZ calibration, PID tuning, and temp calibration with no issues. I hooked up an Octopi to help me level the bed and this is where the issues started.

Sometimes it would fail with the error multiple times in a row and others I could get through a test or two before it would fail again. After running the XYZ calibration for the 4th time it seemed like the issue was solved as I ran about 10 more level tests without issue and was able to dial my bed in to a satisfactory level.

The next day I went to run a Live Z test (sliced 75x75mm square that I have used many times) and I got the error again. I've tried 10 times or so and they have all failed to make it all the way through the bed leveling and start the print. I've cleaned under the plate, I've re-run the XYZ calibration again, I've soft reset the printer, and I've power cycled it, but nothing appears to let me get through the leveling.

Anyone have any ideas what I might be missing here or additional things to check/try?

MMU tips and troubleshooting
Opublikowany : 10/05/2022 10:37 pm
Diem
 Diem
(@diem)
Illustrious Member

It's telling you there is too much difference between the measured bed mesh offset and the stored values from last time - if it repeatedly fails after fresh first layer Z calibrations then something is moving, something is loose...

Cheerio,

Opublikowany : 10/05/2022 11:50 pm
gnat
 gnat
(@gnat)
Noble Member
Topic starter answered:
RE: Some problem encountered, z leveling enforced
Posted by: @diem

if it repeatedly fails after fresh first layer Z calibrations then something is moving, something is loose...

I can't get it through a first layer calibration as it keeps failing on the bed leveling step.

Thanks for the tip about maybe something being loose, but I checked it this morning and nothing appears to be moving in a way that it shouldn't. I'll reconnect the Octopi later though and see if something shifted with the bed.

MMU tips and troubleshooting
Opublikowany : 11/05/2022 3:02 pm
gnat
 gnat
(@gnat)
Noble Member
Topic starter answered:
RE: Some problem encountered, z leveling enforced

So I finally appear to have it playing nice again. I ditched the OctoPi and went back to a program I wrote years ago. It's tests would either fail with the "z leveling enforced" loop or on the rare occasion it would finish, it would go through 2 iterations of unloading/loading filament when it never had filament to start with. The filament sensor hasn't been messed with and tested just fine via both the support menu and the LED I have attached to it (to make MMU life easier).

I turned off my filament sensor and did not get another "z leveling enforced" error through 10-15 g80/g81 cycles and a 75x75mm Live Z test. I enabled the sensor again and had no issues doing a XYZ cube. Besides turning the IR sensor off and back on, the only other change was bed adjustments to bring it from a 0.01mm variation (well within the auto leveling's abilities to compensate for) to 0.003mm.

All my sensors and movements appear to be working as expected and nothing is moving that shouldn't. I'm not clear what was causing filament runout to trip or why that might have anything to do with the leveling process.

MMU tips and troubleshooting
Opublikowany : 31/05/2022 3:16 pm
Andy0x1
(@andy0x1)
Active Member
RE:

Just re-run the Calibration Wiz.  It should take 15m or so.  I got this error a few prints after doing a firmware upgrade and got stuck in the calibration loop / failure until I did the full wiz re-cal.

This post was modified 2 years temu by Andy0x1
Opublikowany : 05/01/2023 6:03 am
ST
 ST
(@st)
Active Member
RE: Some problem encountered, z leveling enforced

Hello

Same problem encountered. I upgraded my MK3 to MK3S and upgraded the firmware to MK3S (it was Two years ago, everything  worked fine). Now I am back to my MK3,I upgraded the MK3S firmware and  cant succeed in Z bed leveling.  somewhere in the help/MK3 it recommends to use the good firmware to solve the problem. So I tried the MK3 firmware, unsuccessfully. Now I reinstalled MK3S but on the screen , it indicates "old settings founded" Is it the reason? I am still looking to anything I should have moved

regards

Opublikowany : 05/04/2024 7:56 am
ST
 ST
(@st)
Active Member
RE: Some problem encountered, z leveling enforced

Hello

I finally succeed after more than ten unsuccessfull wizard running( reading the post upthere) thank you

Opublikowany : 05/04/2024 9:09 am
Share: