Have attempted multiple times to go through the calibration steps
Printer is a modified ender 3 pro
Mini E3 V2
Go through the probe calibrations and it still prints at the same height it always has
Same with my roation_distance when attempting to calibrate extruder
Below is my klippy.log including cfg
#New settings not being applied
keen gust
ocean barn
Don't do just a log rollover and send that log, if you got problems with saving or similar. That log now only contains information about your config
So make a roll over and then execute the calibration and save it. Then home or make a bed once
keen gust
Apologies messed it up when attempting to reduce the unnecessary log data
was trying to do that actually, doing it agian now
keen gust
sorry again, uploaded with a fresh calibration ran, and an attempted print
and here it unzipped
ocean barn
WTF is that?
[gcode_macro CANCEL_PRINT]
description = Cancel the actual running print
rename_existing = BED_MESH_CALIBRATE_BASE
....
Why is your CANCEL_PRINT your bed meshing?
keen gust
this was only added this morning
was https://gist.github.com/ChipCE/95fdbd3c2f3a064397f9610f915f7d02 recommended after I get this issue resolved
no issue deleting all that right now though
i cleared all my macros last night and still encounter the issue
ocean barn
It shouldn't create problems, but it's just wrong. And you didn't even read the top of the page correctly. You don't need that macro anymore for adaptive
Overall the change lands in the config and seems to take effect
keen gust
was deleted, was more of just something to look into after this
ocean barn
So you tested it and you are sure the offset doesn't work?
Easiest would be to just do some careful testing of adjusting the value. So if you run SET_GCODE_OFFSET Z_ADJUST=+10, then save your config and home again
But be very careful, I'm not sure if it's + or - and it might end up crashing your nozzle into the bed
keen gust
so what I just did was delete all that other crap
removed any non-stock start code in cura
implemented the bed_mesh_calibrate setting (correctly....hopefully)
and going through it again
ocean barn
implemented the bed_mesh_calibrate setting (correctly....hopefully)
Tell me how and I can tell you if it was correct ^^
keen gust
was going to show a video of my issue but rushing i uploaded it upside down
but if you look at the end you will see there is always this gap
ocean barn
That's currently without adaptive meshing. This would pass on the parameters and then you could create an adaptive mesh with BED_MESH_CALIBRATE ADAPTIVE=1
[gcode_macro BED_MESH_CALIBRATE]
rename_existing: BASE_BED_MESH_CALIBRATE
gcode:
BED_MESH_CLEAR
QUAD_GANTRY_LEVEL
G1 X125 Y125 Z5 F6000
BASE_BED_MESH_CALIBRATE {rawparams}```Send the sliced gcode
ocean barn
Then my first recommendation is to not use Cura ^^
keen gust
What is the new preferred? Orca? Sorry I am playing catch-up to all this. Been training Ukranians past 2 years. My duets were the hotness at that time. Simplify3d seemed pointless to upgrade to 5
ocean barn
Orca is the one with the most and fastest updates. Prusa is a bit more stable and the UI is a bit better imo
But I currently use Orca
I really cannot find any problems in the configuration or similar
I just realised, you got QUAD_GANTRY_LEVEL but no quad gantry....
But that shouldn't create problems ig
keen gust
Yeah I need to do a better job organizing this. I have seven fdm and 2 resin Jupiter's. Three are quad
Was a sloppy copy and psste
The same thing when I calculated the extrusion the new numbers made no change
ocean barn
I asked someone else for a second opinion, but currently I cannot spot any configuration mistakes.
ocean barn
The same thing when I calculated the extrusion the new numbers made no change
That also makes not much sense
keen gust
I do 120mm take the remaining amount multiply than divide that's not changed or any? Went from like 9 to 7.6 but same extrusion
ocean barn
Let's see, maybe I'm just missing the obv and some new pair of eyes can see it
keen gust
I am really really bad about making the simplest dumbest mistakes
ocean barn
Upload your printer.cfg file and the included files (except mainsail.cfg)
keen gust
Rgr
naive cargo
was https://gist.github.com/ChipCE/95fdbd3c2f3a064397f9610f915f7d02 recommended ...
this is complete outdated... i would use the official adaptive mesh, like the first headline and paragraph also told you...
ocean barn
this is complete outdated... i would use the official adaptive mesh, like the fi...
I already told him that ^^
keen gust
I am adding that per his instructions
naive cargo
pls upload all your config files. i think you mixed up some configurations and this will create these issues. i would need your config files to see "override settings"
naive cargo
why do you have pause, resume, CANCEL_PRINT, _TOOLHEAD_PARK_PAUSE_CANCEL macros in your printer.cfg?
i cleaned up your config and deleted all very wrong parts:
why do you have no x,y offset in your bltouch config section?
keen gust
I did at some point
yea even my safe home was different
[safe_z_home]
home_xy_position: 163, 129 # base 120x120, plus x and y offsets for bltouch to sit in the center
speed: 50
z_hop: 20
z_hop_speed: 5
#[safe_z_home]
#home_xy_position: 117.5,117.5 # Change coordinates to the center of your print bed
#z_hop: 10 # Move up 10mm z_hop_speed: 5
keen gust
i cleaned up your config and deleted all very wrong parts:
I really do appreciate your assistance, I know I am making this harder than necessary. tends to be a problem of mine
naive cargo
120x120 is the center of your bed?
keen gust
no was the template I was starting with, but i never got past resolving the gap issue regardless of my calibrations
naive cargo
is your bltouch 43mm left from your nozzle and 9mm in front of your nozzle?
keen gust
its the typical setup directly at its side
i can measure to be exact i do have calipers
That seems correct
naive cargo
addressing the No trigger on probe after full movement
what did you executed?
naive cargo
That seems correct
you have to add:
x_offset: -43
y_offset: -9
to your b-touch section. but then your bed_mesh will not work anymore, because it uses a offset. let me calculate your bed_mesh
keen gust
i was just sorting that out
now have a better understanding of this min,max and adjusting my two steppers as well
naive cargo
should i double-check your new printer.cfg?
keen gust
i can in just a moment, moving the toolhead to correctly do my min/max
keen gust
so I am really close i think to having all this. I finally got my head around the concept of doing the calculations correctly as well. Not sure why that took me so long to grasp.
during bed_mesh_calibrate it will sometimes fail to deploy on the last row. Is Z_Hop the correct setting to fix this?
naive cargo
depends on the error... pls upload a klippy.log from a failed bed mesh
keen gust
if i apply the smallest of pressure to the back left it goes all the way though
there seems to be an almost 1mm difference from back left and front left
naive cargo
Stepper stepper_z phase change (was 30 now 38)
BLTouch failed to deploy
Stats 24392.3: gcodein=0 mcu: mcu_awake=0.011 mcu_task_avg=0.000017 mcu_task_stddev=0.000016 bytes_write=99186 bytes_read=1185317 bytes_retransmit=9 bytes_invalid=0 send_seq=12440 receive_seq=12440 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=71997663 heater_bed: target=70 temp=34.5 pwm=1.000 sysload=0.01 cputime=385.717 memavail=3495572 print_time=9544.514 buffer_time=0.000 print_stall=0 extruder: target=254 temp=62.9 pwm=1.000
Failed to verify BLTouch probe is raised; retrying.
Stats 24393.3: gcodein=0 mcu: mcu_awake=0.011 mcu_task_avg=0.000017 mcu_task_stddev=0.000016 bytes_write=99429 bytes_read=1185695 bytes_retransmit=9 bytes_invalid=0 send_seq=12456 receive_seq=12456 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=18 freq=71997663 heater_bed: target=70 temp=34.8 pwm=1.000 sysload=0.01 cputime=385.755 memavail=3495572 print_time=9544.514 buffer_time=0.000 print_stall=0 extruder: target=254 temp=65.0 pwm=1.000
Stats 24394.3: gcodein=0 mcu: mcu_awake=0.009 mcu_task_avg=0.000016 mcu_task_stddev=0.000015 bytes_write=99542 bytes_read=1185966 bytes_retransmit=9 bytes_invalid=0 send_seq=12464 receive_seq=12464 retransmit_seq=2 srtt=0.000 rttvar=0.000 rto=0.025 ready_bytes=0 upcoming_bytes=0 freq=71997667 heater_bed: target=70 temp=35.4 pwm=1.000 sysload=0.01 cputime=385.782 memavail=3495572 print_time=9544.514 buffer_time=0.000 print_stall=0 extruder: target=254 temp=66.9 pwm=1.000
BLTouch failed to deploy
this error means, that the bl touch cannot make the pin ready for a probe:
BLTouch failed to deploy
[bed_mesh default]
version = 1
points =
0.265000, -0.085000, -0.360000, -0.815000
0.137500, 0.115000, -0.042500, -0.437500
0.105000, 0.090000, 0.050000, -0.277500
-0.135000, -0.155000, -0.212500, -0.120000
x_count = 4
y_count = 4
mesh_x_pps = 2
mesh_y_pps = 2
algo = lagrange
tension = 0.2
min_x = 15.0
max_x = 186.0
min_y = 25.0
max_y = 224.98
it looks like your bed is at the right/back side up. pls try to level the bed first with the bed screws close the the same level. bed mesh should only fix minimal issuees from your bed. if you print with a bed like this + bed_mesh, your printed part will also have this wrong level on the bottom side.
this is a nice function from klipper to level the bed-screws with help of your probe: https://www.klipper3d.org/Config_Reference.html#screws_tilt_adjust
keen gust
If I am now initializing KAMP, is this still worth doing as well?
ocean barn
Like we multiple times wrote, don't add the adaptive bed meshing of KAMP
Just add ADAPTIVE=1 to your BED_MESH_CALIBRATE call
keen gust
? I understand all that. I just liked some of the options in kamp and figured if i was tackling all this.
naive cargo
All options from the adaptive mesh are also in Klipper. It was Made by the same people
ocean barn
? I understand all that. I just liked some of the options in kamp and figured i...
Do you mean adaptive purge? I specifically wrote adaptive meshing, as the adaptive purge, is not integrated in Klipper. So just don't add the adaptive meshing, but the rest is fine
keen gust
smart park, purge yessir
naive cargo
@keen gust when all questions are answered, pls close this post
keen gust
I may have one last one today trying to get some time to get back at it thank you for everything
keen gust
I might of figured out one of my major headaches. One of my printers I'm testing the new Eddy sensor. Is it safe to assume variables.cfg print_start macro is over writing my printer.cfg macro? That would greatly explain my recent backwards progress