search

MarlinFirmware / Marlin

Marlin is an optimized firmware for RepRap 3D printers based on the Arduino platform. Many commercial 3D printers come with Marlin installed. Check with your vendor if you need source code for your specific machine.
https://marlinfw.org
GNU General Public License v3.0
16.22k stars 19.22k forks source link

[BUG] Bilinear_Subdivision cause problems with overcompensating ABL values #15818

Closed opiswahn closed 4 years ago

opiswahn commented 4 years ago

Description

EDIT I'm fairly certain the cause here is Bilinear_Subdivision. With it enabled, the ABL probing is way off, producing an extremly offset mesh, that seems also to be overcompensated while printing, causing the nozzle to drop into the print cause the printer thinks the bed is off by more than 3mills there... With Bilinear_Subdivision disabled, the ABL probing is very flat(as expected) and it prints very nicely.

I'm on a Ender-2 with a SKR E3 Mini v1.2 board. With the current Marlin version and ABL, I get some strange behavior while printing. On start, homing, ABL (with a 3dTouch) does it's thing, and it begins to print. The first 1 or 2 layers look very good, but then is suddenly drops the nozzle while printing for a short period and backs up again. Looks some kind of an inverted Z-Hop, the palces where this happens are pretty consistent through the print and through different print attempts. I can only print 4 layers or so as the nozzle seems to drop lower every time and gets burried within the print at some point where I have to abort.

Does this sound familiar to anyone?

Configuration.zip

boelle commented 4 years ago

maybe ask here

RepRap.org Marlin Forum Tom's 3D Forums Facebook Group "Marlin Firmware" Facebook Group "Marlin Firmware for 3D Printers" Marlin Configuration on YouTube Marlin Discord server. Join link: https://discord.gg/n5NJ59y

also

Configurations, please Please ZIP up your Configuration.h and Configuration_adv.h files (as requested in the Issue template) and drop them into your next reply. We'll check them over and see if anything is amiss.

opiswahn commented 4 years ago

@boelle uploaded the config files

opiswahn commented 4 years ago

I'm pretty sure it has to do something with ABL... this is the current mesh it produces: image

With Marlin 1.1.9 some days ago it was nearly complete flat (sadly i have no visualization of that anymore), with the same sensor and same other hardware besides the board.

The movement it makes during the print match the topology, but the correction movements are rather harsh...

opiswahn commented 4 years ago

so... anything?

boelle commented 4 years ago

nope i dont have the issue myself and i just updated 3 days ago

opiswahn commented 4 years ago

It has definitly something to do with Bilinear_Subdivision... as soon as i disable it everything is ok. Activated with no matter what setting, the mesh is way off and extremly overcorrected in printing...

shitcreek commented 4 years ago

I think @akaJes is responsible for Bilinear_Subdivision, maybe he/she could chime in.

boelle commented 4 years ago

@akaJes ??

tpruvot commented 4 years ago

overcompensating ? i see the opposite here... its like if the mesh levels were 10x more flat than before... the xyze struct change, made in the end of september. to be more clear... the Z is compensating less than it should... i believe

opiswahn commented 4 years ago

Well, maybe it's manifesting differently on different setups... mine is definitly overcompensating, or better the mesh is overexaggerated...

boelle commented 4 years ago

is the issue still the same with all the updates in the last 33 days?

boelle commented 4 years ago

btw, who can confirm there is an issue? use the same configs as OP and the same hardware if possible

opiswahn commented 4 years ago

I'm still having the problems... nothing has changed here sadly

boelle commented 4 years ago

@opiswahn still no good news with the latest bugfix 2.0.x?

boelle commented 4 years ago

Lack of Activity This issue is being closed due to lack of activity. If you have solved the issue, please let us know how you solved it. If you haven't, please tell us what else you've tried in the meantime, and possibly this issue will be reopened.

github-actions[bot] commented 4 years ago

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.