Mesh bed leveling not working
-
I tested a few capacitive sensors and found that their response time was quite slow compared to inductive sensors.
Have you tried lower the probing speed from 300 to, say, 100?
You may also want to probe each point multiple times. To do that add A10 to your M558 command. With the default value of S=0.03 it will probe up to 10 times trying to get 2 consecutive readings within 0.03 as specified by S.
You can also force averaging of a number of readings. For example if you include A3 and S-1 it will probe each point 3 times and average them.
Frederick
-
@fcwilt it was at 150 until earlier this morning when I mirrored the settings on my ender.
I'll give those a shot, thanks
-
-
80 points is not a very dense grid.
I probe the max which is around 400 or so.
Frederick
-
it prints about 2mm in the air on one side and scrapes the bed on the other, don't think probe density is the issue
-
@pats-prints said in Mesh bed leveling not working:
it prints about 2mm in the air on one side and scrapes the bed on the other, don't think probe density is the issue
2mm? That is a lot.
Still if mesh compensation is working it should be able to cope unless there is a Z speed issue - I think I remember reading something about that.
I see you are using G32 to auto-level the bed.
Is that working? If auto-level is not setup correctly each pass makes things worse.
You should complete the auto-level procedure by setting the Z=0 datum with a G30 positioning the probe at the center of the bed.
You also follow auto-level with G29.
Do you have a file mesh.g?
Frederick
-
@pats-prints said in Mesh bed leveling not working:
@fcwilt
M558 P5 C"!^zprobe.in" H3 F80 T5000 A10
tested slower probing, same issue. The lead screws turn while its running so I know mesh is at least working. I had the same issue when I had a bl touch on the printer.
Those ridges look like backlash causing your print head to tilt back and forth causing the probe to move up and down depending on the direction.
Do you have a lot of play if you grab the print head and try and move it by hand? Are your belts tight?
-
I've tried with the same results running both g29 and g32, neither of my printers save a mesh.g file, not sure why
There is a fair bit of play in the gantry, belts are tight
-
@pats-prints said in Mesh bed leveling not working:
neither of my printers save a mesh.g file, not sure why
Because it's a file you create akin to bed.g.
G32 calls bed.g
G29 would call mesh.g if it existed.@pats-prints said in Mesh bed leveling not working:
There is a fair bit of play in the gantry, belts are tight
If you move the X axis back and forth can you visually tell that it's tilting the probe/nozzle back and forth as well?
-
@phaedrux no, moved it back and forth rapidly no issues, hotend doesn't seem to move at all.
My last ditch effort I just tried was moving my ender's pei sheet and calibrating on that. Same problem.
A thought just crossed my mind that on the cheapo anet they used two different lead screws? Causing this issue no matter what I do to fix it
-
Well the image of your heightmap is tell tale backlash. It's higher in one direction and lower in the other. Until you identify and eliminate that backlash, it will persist.
-
@phaedrux I'll see if the prusa X helps, otherwise this printer is going in the trash
-
What's a prusa X?
-
I see your probe‘s offset is 15mm on Y.
If your axis is slightly tilted it’s more pronounced for the probe and the mesh is not usable. -
@phaedrux meant the prusa bear x upgrade
-
@argo the probe is offset x 0 y -50, it has happened across multiple sensors and bed types the nozzle slopes to be in the air on the low end of the x and scrapes the bed on the higher end of the x
I guess I should also mention I started with 2.0 firmware and recently switched to 3.3 to see if it would help
-
The bear parts didn't fit but I tried 2 LMU88 bearings on each side for the x carriage and had horrible binding. Went back to the stock long bearing- and still the exact same issue. the bed looks fine on the height map viewer.
I think I'm just going to buy some corexy machine and throw the anet in the trash
thanks for your input
-
Sometimes that is the best thing to do.
I had three deltas and decided I didn't like them - gave two away, trashed the third.
Frederick
