Topics created by Timothee Leblond

@Timothee-Leblond

Now to risk really confusing you.

Here is my routine for setting the Z=0 datum - and as I warned you I make use of a lot of different routines that encapsulate commonly used chunks of code.

; ========================= ; === probe_set_z.g BOF === ; ========================= M98 P"check_homed.g" W"probe_set_z.g" X{null} Y{null} Z{null} M291 R"Setting Z=0 Datum" P"Please wait..." S0 M98 P"probe_config.g" ; insure probe is configured M98 P"cancel_mesh_bsteps.g" ; cancel any mesh compensation and zero the baby steps setting M98 P"move_to_z_home.g" ; position at Z home for probing M98 P"probe_to_center.g" ; move probe to bed center G30 ; do single probe - sets Z to probe trigger height M98 P"move_to_z_home.g" ; return to Z home M98 P"tool_to_center.g" ; move tool to back to bed center M291 R"Z=0 Datum has been set" P"OK" T3 ; ========================= ; === probe_set_z.g EOF === ; =========================

Don't worry if it makes little sense - if you wish I can explain it all in detail.

Just don't get over whelmed by my approach - I've been doing this work for several years.

Frederick

@Timothee-Leblond said in Z configuration for sensors:

@fcwilt

Hi Frederick,

I like your approach. Could you please show a test file?

Thank you,

TIM

Assume the X endstop is at max end and triggers exactly at X=90 and the axis range is -100 to 100.

G91 ; relative moves G1 H1 X210 F6000 ; fast move to endstop G1 X-20 ; backoff a bit G1 H1 X25 F300 ; slow move to endstop ; now at this point the logical position is X=100 even though the physical position is X=90 G1 X-90 ; move to physical X=0 G92 X0 ; sync logical and physical positions

@jay_s_uk

I kinda got what you meant. I tried using the following parameters and not It is not making noise anymore and works properly.

M915 X Y S5 R1 F1 H2 ; set sensorless homing

Do I need to put the same M915 at the end of my config.g after the endstop section? (instead of M915 X Y R0 F0)

Also, using a Biqu microprobe as Z sensor - Should I use the same parameters for Z axes such as D3 for stealthchop? Does my homez looks good:

; homez.g ; called to home the Z axis ; ; generated by RepRapFirmware Configuration Tool v3.5.8 on Tue Dec 10 2024 15:03:23 GMT-0500 (Eastern Standard Time) ; ################# Home Z Preparation ################ G91 ; Relative mode G1 H2 Z5 F5000 ; Lower the bed G90 var xCenter = move.compensation.probeGrid.mins[0] + (move.compensation.probeGrid.maxs[0] - move.compensation.probeGrid.mins[0]) / 2 - sensors.probes[0].offsets[0] var yCenter = move.compensation.probeGrid.mins[1] + (move.compensation.probeGrid.maxs[1] - move.compensation.probeGrid.mins[1]) / 2 - sensors.probes[0].offsets[1] G1 X{var.xCenter} Y{var.yCenter} F4000 ; go to bed centre ; Back to absolute positioning ; ################# Home Z Preparation ################ G30 ; Probe a single point

@droftarts Got it. Thank you so so much for your precious help.

................

@Timothee-Leblond There's no one quick way to set it, unfortunately, because it depends on the motors, current, speed and Duet board you're using, so you have to tune it. See this guide https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_stall_detection

Ian

I am not familiar with Klipper or which Duet boards it supports. If you ask around here, you'll likely be encouraged to just use RepRapFirmware, but what's easiest for you may be what you're already familiar with.