@Gregory it's described at https://docs.duet3d.com/en/User_manual/Reference/Gcodes#g31-set-or-report-current-probe-status although the text isn't as clear as it could be.

Yes you can, just send an updated M671 before each attempt whether you want to adjust the Z axis or adjust the 4 bed points.

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_manual_levelling

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_auto_levelling

@tgarr said in MonoPrice Delta Pro - Height Map Interpretation?:

Does the rippling in the height map look like the result of a slightly wobbly rail? Or something else?

That pattern (ridges at one end of X turning into valleys at the other end) indicates that there is backlash in the mechanics. What's happening is that when the effector moves to a particular XY point other than the centre, the nozzle height depends on the direction from which the effector approached that point. G29 in RRF scans alternate lines in opposite directions, hence the alternate ridges and valleys.

To fix or at least mitigate this:

Check that the belts are sufficiently tight Check that the motor pulley grub screws are tight Lubricate the ball joints and the carriage rails or wheel bearings

@dc42 Thanks for letting me know!

@jay_s_uk

G91 ;realtive mode
G1 Z275 F1000 H1 ; move Z rapidly / 300mm up/ until Homing is triggered - the 275 is larger than the stroke.
G90 ;absolute mode
G1 Z256 F10 ; retract z 3mm slowly (Z 259 reaches the microswitch) so it backs off 3mm)
G91 ;realtive mode
G1 Z5 F0.1 H1 ; rehome at slow speed (then home very slowly)
G90 ; return to asoute mode
G1 Z261 ; back off (this goes down a bit away from the switch)

@bob0191 said in HELP with ender 3 duet2 wifi:

command M503 but this failed

Did you mean M303?

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Heaters_tuning

@moth4017
it is a BMG I installed on the LDO motor
they were not purchased as a unit

it is confirmed it is 0.9 degree stepper I get a full rotation when I request 7.7mm of filament which check out at 800 steps per mm with 16x micro stepping the machine seems to be doing whats asked of it

starting to wonder if something is off in super slicer

Good catch ... and yes, the linear rail is clearly wrong for that extrusion. Good job machining your own gantry !

@foesi said in BL-Touch M402 and M280 P0 S90 do not retract pin:

@Phaedrux I tried to position the screw in a position where the test at power on just gets the pin back up in retracted position.
I can´t get the screw in the position as mentioned in the antclabs documentation - because then the pin would not get back up.
And I also used magnets to get the pin magnetised.🤷

This makes it sound like there is something wrong with the BLtouch.

@dc42 Sure, I use your IR probe for that 😉

@Phaedrux, thank you!

The exact details on how to find your probe offset using G30 S-1 can be found here: https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing

Then you can use G30 to accurately home the Z axis to find the Z0 point using the probe.

G29 uses a series of G30 probes are various points to make the map.

If you're using an endstop at the high end of Z travel for homing, use that first for course homing, and then use a G30 at the center of the bed to establish the true Z0. If you use only the endstop at the high end you're likely to have an offset and inaccurate z position unless you measure the distance from the bed at z0 to the endstop at zmax very accurately.

@Phaedrux said in Time estimates from PrusaSlicer:

Can you send the speed, accel, jerk, etc commands while a print is in progress to see if the values are what you'd expect them to be?

Sorry for the slow reply, but covid paid a visit so i haven't had the energy to deal with this lol.

But i just managed to check the numbers during print, and apparently the printing accelerations are at 500 for some reason.

alt text

So i need to track down what the f**k sends that M204 P500.

EDIT:

I found the issue, when redoing print_level_bed.g i had forgot to turn up both speeds AND currents and the end.

Fixed print_level_bed.g:

; /sys/lib/print/print_level_bed.g v2.1 ; Called as part of print_start.g ; Used to make sure the bed is leveled ; ====================--------------------------------------------------------- ; Homing check ; ==================== ; Lower currents, speed & accel M98 P"/sys/lib/current/xy_current_low.g" ; Set low XY currents M98 P"/sys/lib/current/z_current_low.g" ; Set low Z currents M98 P"/sys/lib/speed/speed_probing.g" ; Set low speed & accel ; LED status set global.sb_leds = "homing" ; Make sure all axes are Homed if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed ; If axes aren't homed ; Home all axis G91 ; Relative positioning ; Lower Z relative to current position if needed if !move.axes[2].homed ; If Z ain't homed G1 Z20 F9000 H1 ; Lower Z(bed) relative to current position elif move.axes[2].userPosition < 10 ; If Z is homed and less than 10 G1 Z20 F9000 ; Move to Z 10 ; Coarse home X or Y G1 X600 Y600 F2400 H1 ; Move quickly to X or Y endstop(first pass) ; Coarse home X G1 X600 H1 ; Move quickly to X endstop(first pass) ; Coarse home Y G1 Y600 H1 ; Move quickly to Y endstop(first pass) ; Move away from the endstops G1 X-5 Y-5 F9000 ; Go back a few mm ; Fine home X G1 X600 F360 H1 ; Move slowly to X axis endstop(second pass) ; Fine home Y G1 Y600 H1 ; move slowly to Y axis endstop(second pass) ; Absolute positioning G90 ; Absolute positioning ; Home Z ; Load the probe M401 P0 ; Load the klicky probe M400 ; Wait for moves to finish M98 P"/sys/lib/klicky/klicky_status.g" ; Refresh klicky status ; Last check to ensure klicky is attached if global.klicky_status = "Attached" echo "Probe ATTACHED" else echo "Error probe not attached - aborting" M291 T5 R"Z Homing Aborted!" P"Z haven't been homed - check probe" abort ; Move to bed center and home Z M98 P"/sys/lib/goto/bed_center.g" ; Move to bed center M98 P"/sys/lib/speed/speed_probing.g" ; Set low speed & accel G30 K0 Z-99999 ; Probe the center of the bed ; ====================--------------------------------------------------------- ; Check if bed is leveled ; ==================== ; If the bed isn't leveled if global.bed_leveled = false ; LED status set global.sb_leds = "leveling" ; ====================--------------------------------------------------------- ; Prepare to probe ; ==================== ; Report whats going on M291 R"Bed leveling" P"Please wait..." T0 ; Leveling bed message M561 ; Clear any bed transform M290 R0 S0 ; Reset baby stepping M84 E0 ; Disable extruder stepper ; ====================--------------------------------------------------------- ; Probing code ; ==================== ; Coarse leveling pass M558 K0 H15 F600 A1 ; Increase the depth range, gets the bed mostly level immediately M98 P"/sys/bed_probe_points.g" ; Probe the bed ; Probe the bed while true ; Probe near lead screws M558 K0 H3 F240:120 A30 ; Reduce depth range, probe slower for better repeatability M98 P"/sys/bed_probe_points.g" ; Probe the bed ; Check results - exit loop if results are good if move.calibration.initial.deviation < 0.02 ; If probing result is less than 0.02mm break ; Stop probing ; Check pass limit - abort if pass limit reached if iterations = 5 ; If probed more than 5 times M291 P"Bed Leveling Aborted" R"Pass Limit Reached" ; Abort probing, something wrong set global.bed_leveled = false ; Set global state abort "Bed Leveling Aborted - Pass Limit Reached" ; Abort probing, something wrong ; ====================--------------------------------------------------------- ; Finish up ; ==================== ; Home Z ; Move to bed center and home Z M98 P"/sys/lib/goto/bed_center.g" ; Move to bed center M98 P"/sys/lib/speed/speed_probing.g" ; Set low speed & accel G30 K0 Z-99999 ; Probe the center of the bed ; Dock the probe M402 P0 ; Dock the klicky probe M400 ; Wait for moves to finish set global.bed_leveled = true ; set global state ;echo "global.bed_leveled. Value : " , global.bed_leveled M291 R"Bed leveling" P"Done" T5 ; bed leveling done message else ; ====================--------------------------------------------------------- ; Response if leveled ; ==================== ; Dock the probe M402 P0 ; Dock the klicky probe M400 ; Wait for moves to finish M98 P"/sys/lib/klicky/klicky_status.g" ; Refresh klicky status ; Full currents, speed & accel M98 P"/sys/lib/current/z_current_high.g" ; Restore normal Z currents M98 P"/sys/lib/current/xy_current_high.g" ; Set high XY currents M98 P"/sys/lib/speed/speed_printing.g" ; Restore normal speed & accels ; Bed already leveled, no need to probe M291 S1 R"Bed leveling" P"Bed allready leveled" T1 M561 ; Clear any bed transform M290 R0 S0 ; Reset baby stepping ; LED status set global.sb_leds = "ready"

@jay_s_uk, thanks, I misread the RRF 3.5 as RRF 3.4.5 and thought I had the option of using the feature. I will be patient until 3.5!

@mendelevium said in precisionpiezo adaptaion:

M558 P1 I0 C"zprobe.in" H5 R0.2 F1000 X0 Y0 Z100 ; piezo

I0 is not used in RRF3. If you need to invert the probe signal, use a ! before the pin name, like this `C"!zprobe.in"

That may be the source of your probe already triggered message.

I don't understand what you're trying to do with the Z probe zeroing macro. With the steps you're using the G30 S-1 will give you the height you started it from, which is probably why you have a G31 Z of 12mm, which is obviously wrong.
I think you should follow these steps instead.
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing#calibrate-the-z-probe-trigger-height

@jdzender said in PID Tuning Part Fan Not Turning On:

M303 H1 S230

To get the fan to be part of the tuning process you must tune it as a tool using M303 T0 S230 instead.

i had similar bed issues. very likely, your physical wiring or tubing connected to the print head bumps up against the corner wall or frame of your printer in this corner, and it slightly pushes the probe and print head downward, appearing like the bed is raised. Since it only happens in that corner, very extreme, it very likely is physical force on your toolhead.

@T3P3Tony, thanks! ..... funny enough, it hadn't occurred to me that I could manually set the temperatures before the print (yes, seriously). I need to investigate this option some more because my one fully self designed two colour print had the 'sitting over the build plate and drooling' issue for every tool change. It is possible that I am missing a strategic M116 someplace. It is of course also possible that this trick doesn't work unless the standby temperature is the same as the active temperature (which I also hadn't considered and a 10 degree differential between the two might not actually make any difference).
I am curious how many people just use one temperature and enjoy the lack of drooling over the build plate and the substantial speed improvements this would bring.

@simobone19 it will probably use the max speed in config, so you could reduce that. or, use G1 R2 Z0 Fxxx in your toolchange file and obviously set the appropriate speed.
See here for more info