-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] UBL grid points visible in prints caused by LA pressure release #17050
Comments
Most likely you are not seeing the Artefakts at the mesh-points, but at the mesh-borders - the lines connecting the mesh-points. Where lithophanes could be the use-case the problem is best visible. Since lithophanes have a large contact area to the bed and therefor should stick well, i'd try to print them without or with linear BL. If that does not work - try a less bad bed. |
@AnHardt First thank you for the good explanation. I work with bed leveling because of observing babystep issues #16617, otherwise my bed is good enough to work without UBL. |
I can add some light to this discussion... When UBL was written, doing mesh based leveling added a lot of floating point math to every line segment printed. And the line segments needed to be cut off at each mesh cell boundary. UBL's Z-Height corrections fall on mesh cell boundaries. All of the different cases for crossing those boundaries are broken out in UBL's motion generation code and highly optimized to eleminate unneeded floating point operations. It may be time to jettison that code and just use the normal Planner:: code. I think what happened is the Linear Advance people hooked in to the Planner:: and Stepper:: code and never bothered to update the UBL code to be compatible with Linear Advance. |
Any idea why artifacts are still visible above fade hight? There is no Z move or direction change except layer change, or am i wrong? |
I don't think what you are seeing is a 'bed leveling' problem per se. The problem is all line segments are broken into more line segments at mesh cell boundaries. And if the nozzle is below the fade height, some amount of Z correction is added (or subtracted) at that point. The problem is Linear Advance is doing some thing extra at the mesh cell boundaries. It may think a sharp turn is being taken (when it is not) or something else. I don't know. But we have two options... We can hook UBL into the Stepper:: and Planner:: code and remove the optimized motion algorithms. Or we can figure out what the incompatibility is and add what is needed to the UBL motion code. And actually... There is a third option. We can move the optimized motion code for plotting paths across cell boundaries into the Planner:: and Stepper:: code. That way, all of the mesh based bed leveling schemes would have the more efficient code. But that still requires we figure out what is currently missing from it with respect to Linear Advance. |
In my case definitely emerging at the mesh vertices not like in this video: #10171 (comment) |
@rado79 still an issue? |
@boelle nice that you're back! Today i tested again with latest bugfix, UBL 10x10 and LA enabled. This issue seems to be gone. |
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. |
Bug Description
Printing with UBL and LA enabled shows visible artifacts on meshpoints. If nozzle travels over a meshpoint while priming, LA does a pressure-release-move on extruder. I noticed it a few weeks ago while doing some bed calibration prints with one layer. Yesterday i started to print some kind of curved lithophanes with translucent filament. They cover two or more of the meshpoints. I can see where the meshpoints are through the whole hight of the print.
If you put any object placed on a meshpoint with outer walls , you can see vertical artifact on skin.
My Configurations
Configuration.zip
Configuration_adv.zip
Steps to Reproduce
Expected behavior: print as expected
Actual behavior: artifacts on meshpoints
Additional Information
9x9 grid, meshinset 30.
I tried various slicers and changing the position of the object in x and y direction. Artifacts are always on same coordinates.
First time i noticed is about 5 weeks ago, i download new bugfix once a week.
#10171 (comment)
#16910 (comment)
The text was updated successfully, but these errors were encountered: