Ender 3 Pro BL Touch Trigger Height
-
@DIY-O-Sphere said in Ender 3 Pro BL Touch Trigger Height:
@jcv1977
The main problem is that the guide uses a file named config.g.overwright but it has to be "called" by the config.g
So you have to add a M501 at the end of the config.g
https://duet3d.dozuki.com/Wiki/Gcode#Section_M501_Read_stored_parametersOr edit the z value of G31 directly in the config.g
There is no use of M500 to save a measured G31 Z trigger height in the guide he linked. Though it is a viable option, but it's not described there.
-
@Phaedrux
Sorry . Only read "Open config-override.g and check...."
Getting to late here.... -
@Phaedrux Thanks Guys for the reply! I got it like that, apparently 8mm (i don't have my caliper with me, but it's close. I would swear that it is some parameter issue but i i am not that gcode savy myself. I am probing at the center with printing temperature. Every time i tried to get one this is what it says:
G29 Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh. 88 points probed, min error 0.240, max error 1.130, mean 0.766, deviation 0.229 Height map saved to file 0:/sys/heightmap.csvand this is the results dumped on height map.csv:
RepRapFirmware height map file v2 generated at 2021-01-19 17:27, min error 0.240, max error 1.130, mean 0.766, deviation 0.229 xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum 47.00,205.00,20.00,230.00,-1.00,20.00,20.00,8,11 0.240, 0.303, 0.428, 0.543, 0.683, 0.800, 0.885, 0.960 0.275, 0.352, 0.460, 0.590, 0.692, 0.793, 0.900, 0.945 0.300, 0.380, 0.502, 0.618, 0.717, 0.832, 0.915, 0.975 0.365, 0.440, 0.562, 0.675, 0.780, 0.908, 0.977, 1.038 0.415, 0.517, 0.615, 0.717, 0.808, 0.915, 1.008, 1.055 0.488, 0.570, 0.655, 0.733, 0.855, 0.952, 1.062, 1.087 0.500, 0.582, 0.685, 0.772, 0.827, 0.940, 1.020, 1.087 0.545, 0.605, 0.697, 0.827, 0.873, 0.955, 1.050, 1.105 0.600, 0.660, 0.728, 0.825, 0.875, 0.960, 1.043, 1.090 0.610, 0.695, 0.788, 0.858, 0.918, 0.977, 1.065, 1.092 0.673, 0.750, 0.798, 0.900, 0.945, 1.013, 1.082, 1.130 -
I just tried a print test but i have to cancel it because the nozzle is still scratching the bed. Also i 've got a doubt ( one more lol) should i pre level the bed manually before even do the auto level? Does it helps?
-
post a picture of the heigh map.
its hard to see it in numbers.
but yes, you should level the bed as best as you can.
-
@Veti I am using Reprap 3 and i don’t see any function to show a geaphic of the heightmap do you know where it is?
-
general->plugins->height map
-
Hmmm i think i am going to rely it but this is what i got
image url) -
Maybe take a look here. Get the bed as level as possible first. Then run the mesh.
Also, redo your Z probe trigger height measurement. If the probe body is 8mm above the nozzle the trigger height should be around 2mm, not around 0mm.
-
@Phaedrux Seems ok but i don't think its 8mm between the bltouch/nozzle and the bed.
-
After the bed is leveled well, follow these steps.
-
@Phaedrux said in Ender 3 Pro BL Touch Trigger Height:
I've already done it but then when i home z it is way upper than the picture. The best way to describe it it would be imagine the same picture but with the bltouch deployed so the nozzle would be even far from the bed.
-
@jcv1977 said in Ender 3 Pro BL Touch Trigger Height:
G1 X50 Y20 F6000 ; go to first probe point G30 ; home Z by probing the bed
In your homez and homeall you're using the corner of the bed to probe. Change that to place the probe at the center of the bed.
Also use that position to measure your trigger height.
If there is tilt in the bed when you do this the the trigger height won't be right either, so make sure the bed is leveled. The guide linked shows it being done with both the hotend and bed at temp to allow for thermal changes. Also make sure that the mesh isn't loaded when doing the leveling.
-
I 've had it with this, it keeps happening the same all over again. I guess there is something wrong with the bltouch. I have done a manual level of the freaking bed that i thing it would be perfect. Then i follow the guide again and the result is that the homing of the z axis is in the middle of the bed but the damn nozzle is really way too up to even try an auto level .
-
Are we sure your z axis steps per mm is correct? Does moving 10mm in Z actually move 10mm?
Video of the process so we can maybe see something we're missing? Sometimes it's the little things that get overlooked, or a misunderstanding that becomes easy to clear up when we can see what's happening.
-
@Phaedrux I 've been asking the same question for a couple of days now, today i will get a caliper and i will be able to measure it correctly.
Sometimes it's the little things that get overlookedAmen to that!!!!
I'll make a video of it.
-
Well trying again to set the bltouch right. I did some modification to the bed, i 've replaced the springs for m3 spacers so the bed is really steady also there where a severe difference between the spacers been used in the bed gantry i don't know how did that machine pass the "quality test" but now the bed has little margin of error
BUT yep there is always that frightening word, the freaking compensation is not working when i run the bed compensation i get this on some mesh parts:
1/31/2021, 10:11:05 AM Warning: Skipping grid point (47.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (67.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (87.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (107.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (127.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (147.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (167.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (187.0, 220.0) because Z probe cannot reach it 70 points probed, min error -0.034, max error 0.477, mean 0.251, deviation 0.152 Height map saved to file 0:/sys/heightmap.csv 1/31/2021, 10:11:04 AM Warning: Skipping grid point (47.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (67.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (87.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (107.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (127.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (147.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (167.0, 220.0) because Z probe cannot reach it Warning: Skipping grid point (187.0, 220.0) because Z probe cannot reach it 70 points probed, min error -0.034, max error 0.477, mean 0.251, deviation 0.152 Height map saved to file 0:/sys/heightmap.csv 1/31/2021, 10:10:45 AM Warning: Skipping grid point (187.0, 180.0) because Z probe cannot reach it Warning: Skipping grid point (187.0, 200.0) because Z probe cannot reach it 1/31/2021, 10:10:05 AM Warning: Skipping grid point (187.0, 140.0) because Z probe cannot reach it Warning: Skipping grid point (187.0, 160.0) because Z probe cannot reach it 1/31/2021, 10:09:26 AM Warning: Skipping grid point (187.0, 100.0) because Z probe cannot reach it Warning: Skipping grid point (187.0, 120.0) because Z probe cannot reach itThe thing is that all of that coordinates can indeed be reached by the prove i've seen all the measurement itself and i can tell you that non of that coordinates are unreachable. So there might be something else wrong.
this is my actual G31 part:
G31 P500 X-46 Y6 Z3.34 ; set Z probe trigger value, offset and trigger heightIf a run a test print the print is ok but i don't want to try a really big print if i am not sure that the bltouch is working the way it should.
Any ideas?
-
when defining the grid you have to take the offset of the probe into consideration.
-
@Veti But when i defined the grid i used the probe as point of reference thats why in reality all that coordinates are indeed reachable.
-
post the output of
M208
and
G31
