[BUG] Mesh leveling Z-axis off (1.4.0-b3) #238

Closed
opened 2021-12-08 15:13:25 -06:00 by JanJastrow · 10 comments
JanJastrow commented 2021-12-08 15:13:25 -06:00 (Migrated from github.com)

Bug Description

Hi, I think there is a bug in the current 1.4.0-b3 releases.
I was unable to correctly set my mesh z coordinates with this version (especially in the bottom-right & top-right corners)

Steps to Reproduce

  • Flashed MEGA_S_TMC_v1.4.0-b3 onto my Mega S
  • Load FW defaults & save eeprom
  • Restart
  • Special Menu
  • Prehead bed
  • 4-point leveling
  • mesh leveling

Expected behavior: [What you expect to happen]

Beeing able to reach the bed while mesh leveling

Actual behavior: [What actually happens]

Hovering above the bed

Additional Information

I was on version 1.2.0 before and just today upgraded to 1.4.0.-b3 to test the fancy new features.

I was always leveling my printer the way I always do: first 4-point and afterwards mesh.
4-point seems to be working as always, but when switching to mesh, I immediately noticed that I had to set way higher numbers then before - 0.1mm instead of just 0.01 or 0.02.
Still, I was able to set the first 4 points with the menu, but with the 5th point I was unable to get the nozzle down to the bed.
I tried multiple times & resets, but never succeded.
I continued with the other "points", most of them were working okay (but still with way higher values then before), but was struggeling again with the last point (top-right).

I've downgraded to version 1.3.1 now and everything is working as before on 1.2.0.

### Bug Description Hi, I think there is a bug in the current 1.4.0-b3 releases. I was unable to correctly set my mesh z coordinates with this version (especially in the bottom-right & top-right corners) ### Steps to Reproduce - Flashed MEGA_S_TMC_v1.4.0-b3 onto my Mega S - Load FW defaults & save eeprom - Restart - Special Menu - Prehead bed - 4-point leveling - mesh leveling **Expected behavior:** [What you expect to happen] Beeing able to reach the bed while mesh leveling **Actual behavior:** [What actually happens] Hovering above the bed #### Additional Information I was on version 1.2.0 before and just today upgraded to 1.4.0.-b3 to test the fancy new features. I was always leveling my printer the way I always do: first 4-point and afterwards mesh. 4-point seems to be working as always, but when switching to mesh, I immediately noticed that I had to set way higher numbers then before - 0.1mm instead of just 0.01 or 0.02. Still, I was able to set the first 4 points with the menu, but with the 5th point I was unable to get the nozzle down to the bed. I tried multiple times & resets, but never succeded. I continued with the other "points", most of them were working okay (but still with way higher values then before), but was struggeling again with the last point (top-right). I've downgraded to version 1.3.1 now and everything is working as before on 1.2.0.
knutwurst commented 2022-01-24 01:37:02 -06:00 (Migrated from github.com)

I'm on it... the leveling works, but there is an offset, some other users reported. I just need to figure out why :D

I'm on it... the leveling works, but there is an offset, some other users reported. I just need to figure out why :D
esprudzs commented 2022-01-29 15:46:05 -06:00 (Migrated from github.com)

Just my 5 cents. My config is very different from stock, so I did suspect it was due to some of the settings I have changed in the beginning (which could still be the case).

My symptoms are, that whatever the values are for mesh towards the 0,0 corner, positive or negative, depending on how I set the end-stop screws, the printing only lowers to about the probe offset (1.34 for me) above bed, Interestingly, this is gradually corrected towards the middle of the bed and the remaining three quadrants get reasonably well leveled (I can see Z axis doing the work).

Just my 5 cents. My config is very different from stock, so I did suspect it was due to some of the settings I have changed in the beginning (which could still be the case). My symptoms are, that whatever the values are for mesh towards the 0,0 corner, positive or negative, depending on how I set the end-stop screws, the printing only lowers to about the probe offset (1.34 for me) above bed, Interestingly, this is gradually corrected towards the middle of the bed and the remaining three quadrants get reasonably well leveled (I can see Z axis doing the work).
knutwurst commented 2022-02-15 01:08:15 -06:00 (Migrated from github.com)

Should be fixed in >1.4.0

Should be fixed in >1.4.0
esprudzs commented 2022-02-17 16:50:44 -06:00 (Migrated from github.com)

Thanks for the fix, I'm much better off with leveling. However a new issue arises that is likely related. I'm using two extruders with a single hotend on modified mega S that worked like a charm before the update. After update to the latest version, there is some sort of negative Z offset after a toolchange (T1) and the thing is trying to print the layer at the same height or maybe even lower than there already is one, printed by T0. The screen is showing the expected (=correct) Z height and I have been and still am pulling my hair out :) analyzing my g-code, but I cannot see any problem/difference from previously flawlessly working configurations.

Thanks for the fix, I'm much better off with leveling. However a new issue arises that is likely related. I'm using two extruders with a single hotend on modified mega S that worked like a charm before the update. After update to the latest version, there is some sort of negative Z offset after a toolchange (T1) and the thing is trying to print the layer at the same height or maybe even lower than there already is one, printed by T0. The screen is showing the expected (=correct) Z height and I have been and still am pulling my hair out :) analyzing my g-code, but I cannot see any problem/difference from previously flawlessly working configurations.
esprudzs commented 2022-02-18 01:02:26 -06:00 (Migrated from github.com)

after a toolchange (T1) and the thing is trying to print the layer at the same height or maybe even lower than there already is one, printed by T0.

I ran a print overnight on T1 only and got the same problem of "insufficient Z height". The nozzle was at 2.40 according to the screen, but at about 1.80 in reality. I'm printing with 0.16 layer height, so this is many layerheights off. My fade height is 0.96, but as I have seen before, the problem starts no later than at Z=0.64. I don't see anything wrong with slicing, so I will swap some hardware to rule that out.
IMG_8606

> after a toolchange (T1) and the thing is trying to print the layer at the same height or maybe even lower than there already is one, printed by T0. I ran a print overnight on T1 only and got the same problem of "insufficient Z height". The nozzle was at 2.40 according to the screen, but at about 1.80 in reality. I'm printing with 0.16 layer height, so this is many layerheights off. My fade height is 0.96, but as I have seen before, the problem starts no later than at Z=0.64. I don't see anything wrong with slicing, so I will swap some hardware to rule that out. ![IMG_8606](https://user-images.githubusercontent.com/59663811/154633977-f4887d65-a083-4f10-b764-c8febf64cd15.jpg)
knutwurst commented 2022-02-24 01:16:13 -06:00 (Migrated from github.com)

Is the issue still there?

Is the issue still there?
github-actions[bot] commented 2022-03-26 20:56:41 -05:00 (Migrated from github.com)

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.
esprudzs commented 2022-03-29 05:44:11 -05:00 (Migrated from github.com)

You can close this down. I worked around this issue, which is not to say leveling works - I think it still does not. But I have figured out how to work around it and I need to print, not to tinker for some time now :D. I hope to be able to upgrade to the latest firmware within a few weeks and lets see where we stand then. Cheers!

You can close this down. I worked around this issue, which is not to say leveling works - I think it still does not. But I have figured out how to work around it and I need to print, not to tinker for some time now :D. I hope to be able to upgrade to the latest firmware within a few weeks and lets see where we stand then. Cheers!
github-actions[bot] commented 2022-04-28 21:04:13 -05:00 (Migrated from github.com)

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.

This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.
github-actions[bot] commented 2022-07-03 09:03:41 -05:00 (Migrated from github.com)

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wp/Marlin-2-0-x-Anycubic-i3-MEGA-S#238
No description provided.