Servo deployed probe on Duet Maestro

Blacksheep99

@Veti said in Servo deployed probe on Duet Maestro:

its pretty close to bltouch. just select P8 instead of p9.

same retract and deploy scripts (might have to adjust the angles slightly)
although you need to add a M401 if you want to deploy it before and M402 when you want to retract.

example homeall

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.0 on Fri Jan 01 2021 18:39:48 GMT+0100 (Central European Standard Time)
G91                     ; relative positioning
G1 H2 Z5 F6000          ; lift Z relative to current position
G1 H1 X-240 Y-240 F3000 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000       ; go back a few mm
G1 H1 X-240 Y-240 F240  ; move slowly to X and Y axis endstops once more (second pass)
G90                     ; absolute positioning
G1 X10 Y10 F6000        ; go to first bed probe point and home Z
M401
G30                     ; home Z by probing the bed
M402

; Uncomment the following lines to lift Z after probing
;G91                    ; relative positioning
;G1 Z5 F100             ; lift Z relative to current position
;G90                    ; absolute positioning

So taking your example I modified my home all to try this. I changed the X and X to my bed size. Sending just the M401 command deploys the probe fine, the M402 retracts it.

This is my config.g code.

M574 Z1 S1 ; Set endstops controlled by probe
M950 S0 C"^zprobe.mod" ; create servo pin 0 for BLTouch
M558 P8 C"^!zprobe.in" H2 F900 T6000 ; Set Z probe type to switch and the dive height + speeds
G31 P50 X50 Y-8 Z2.43 ; Set Z probe trigger value, offset and trigger height

When I home all the head moves out as expected, the bed starts to raise, probe deploys and the immediately retracts and the z stops.

My probe in the dashboard shows 0 when retracted and 1000 when deployed. Is the inverted pin causing an issue?

Blacksheep99

This is the bed and head setup. Excuse the chaos behind it!

Phaedrux

@Blacksheep99 said in Servo deployed probe on Duet Maestro:

Is the inverted pin causing an issue?

Could be. Your description makes it sound like it assumes that it's triggered as soon as it deploys? Correct?

dc42

@Blacksheep99 said in Servo deployed probe on Duet Maestro:

My probe in the dashboard shows 0 when retracted and 1000 when deployed. Is the inverted pin causing an issue?

What happens if you don't invert the pin? Does probing work then?

Veti

@Blacksheep99 said in Servo deployed probe on Duet Maestro:

My probe in the dashboard shows 0 when retracted and 1000 when deployed. Is the inverted pin causing an issue?

yes it needs to be inverted

change to C"^zprobe.in"

Blacksheep99

@Veti said in Servo deployed probe on Duet Maestro:

@Blacksheep99 said in Servo deployed probe on Duet Maestro:

My probe in the dashboard shows 0 when retracted and 1000 when deployed. Is the inverted pin causing an issue?

yes it needs to be inverted

change to C"^zprobe.in"

Ok, I've changed this. The probe itself is off the bed. Do I need to add a move command for X and Y to move the head over the bed?

I current have the mesh compensation commented out in the config.g not sure if that should be active?

Blacksheep99

Probe now shows 1000 when retracted.

To test the probe is working I moved X and Y over the bed and tried to run G30. It doesn't run as it says probe is already deployed.

Phaedrux

@Blacksheep99 said in Servo deployed probe on Duet Maestro:

Do I need to add a move command for X and Y to move the head over the bed?

yes.

@Blacksheep99 said in Servo deployed probe on Duet Maestro:

I current have the mesh compensation commented out in the config.g not sure if that should be active?

what exactly do you have commented out?

Phaedrux

@Blacksheep99 said in Servo deployed probe on Duet Maestro:

it says probe is already deployed.

In your homing files you may want to add a M401 at the start to ensure that the probe is retracted and so that the firmware is aware it's retracted.

Then try again.

Blacksheep99

@Phaedrux said in Servo deployed probe on Duet Maestro:

what exactly do you have commented out?

;M557 X15:265 Y15:135 S20                        ; define mesh grid

Phaedrux

Yes you should uncomment that line out. It tells the firmware where to probe when doing a G29.

Blacksheep99

@Phaedrux said in Servo deployed probe on Duet Maestro:

@Blacksheep99 said in Servo deployed probe on Duet Maestro:

it says probe is already deployed.

In your homing files you may want to add a M401 at the start to ensure that the probe is retracted and so that the firmware is aware it's retracted.

Then try again.

Do you mean M402?

Blacksheep99

@Phaedrux Thanks. Will do

Phaedrux

@Blacksheep99 said in Servo deployed probe on Duet Maestro:

Do you mean M402?

Yes, sorry. Retract the probe.

Blacksheep99

@Phaedrux said in Servo deployed probe on Duet Maestro:

@Blacksheep99 said in Servo deployed probe on Duet Maestro:

Do you mean M402?

Yes, sorry. Retract the probe.

Thanks, shows I'm paying attention if just a bit! ha

Blacksheep99

So I've got the probe showing '0' when retracted. I position the probe over the bed and run G30. The probe immediately deploys and the bed starts moving towards the print heads.

Following this guide: https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

I press the Z probe up expecting the bed to stop but it continues leaving me to use emergency stop to kill things. What have I got wrong?

Phaedrux

please share your current probe config and refresh me on your wiring.

Blacksheep99

@Phaedrux full config.g

The probe is wired as per this.
https://www.thingiverse.com/thing:3303618

So 5v to servo and sensor, shared ground, zprobe mod to the servo, probe.in to the sensor

; Configuration file for Duet Maestro (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Sat Jan 09 2021 18:02:08 GMT+0000 (Greenwich Mean Time)

; General preferences
G90                                             ; send absolute coordinates...
M83                                             ; ...but relative extruder moves
M550 P"ST3Di280 Duet"                           ; set printer name

; Network
M552 P0.0.0.0 S1                                ; enable network and acquire dynamic address via DHCP
M586 P0 S1                                      ; enable HTTP
M586 P1 S0                                      ; disable FTP
M586 P2 S0                                      ; disable Telnet

; Drives
M569 P0 S1                                      ; physical drive 0 goes forwards
M569 P1 S0                                      ; physical drive 1 goes backwards
M569 P2 S0                                      ; physical drive 2 goes backwards
M569 P3 S0                                      ; physical drive 3 goes backwards
M569 P4 S1                                      ; physical drive 4 goes forwards
M584 X0 Y1 Z2 E3:4                              ; set drive mapping
M350 X16 Y16 Z16 E16:16 I1                      ; configure microstepping with interpolation
M92 X91.13 Y106.84 Z1235.52  E420.00:420.00       	; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00:120.00      ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00:250.00      ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800:800 I30                ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                         ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                                ; set axis minima
M208 X280 Y150 Z150 S0                          ; set axis maxima

; Endstops
M574 X1 S1 P"xstop"                             ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop"                             ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S1 P"zstop"                             ; configure active-high endstop for low end on Z via pin zstop

; Z-Probe
M574 Z1 S1 										; Set endstops controlled by probe
M950 S0 C"^zprobe.mod" 							; create servo pin 0 for BLTouch
M558 P8 C"^!zprobe.in" H150 F900 T6000 			; Set Z probe type to switch and the dive height + speeds
G31 P50 X-50 Y-8 Z1.5 							;Set Z probe trigger value, offset and trigger height
M557 X15:265 Y15:135 S20                        ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950  ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                           ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B0 S1.00                                ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                         ; map heated bed to heater 0
M143 H0 S120                                    ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B3950   ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                            ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                                ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                    ; set temperature limit for heater 1 to 280C
M308 S2 P"e1temp" Y"thermistor" T100000 B3950   ; configure sensor 2 as thermistor on pin e1temp
M950 H2 C"e1heat" T2                            ; create nozzle heater output on e1heat and map it to sensor 2
M307 H2 B0 S1.00                                ; disable bang-bang mode for heater  and set PWM limit
M143 H2 S280                                    ; set temperature limit for heater 2 to 280C

; Fans
M950 F0 C"fan0" Q500                            ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1                                  ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                            ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1:2 T45                             ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 S"Right" D0 H1 F0                       ; define tool 0
G10 P0 X0 Y0 Z0                                 ; set tool 0 axis offsets
G10 P0 R0 S0                                    ; set initial tool 0 active and standby temperatures to 0C
M563 P1 S"Left" D1 H2 F0                        ; define tool 1
G10 P1 X0 Y0 Z0                                 ; set tool 1 axis offsets
G10 P1 R0 S0                                    ; set initial tool 1 active and standby temperatures to 0C

; Custom settings are not defined
M501
M911 S21 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

Phaedrux

@Veti said in Servo deployed probe on Duet Maestro:

change to C"^zprobe.in"

Veti suggested that, but you still have

@Blacksheep99 said in Servo deployed probe on Duet Maestro:

C"^!zprobe.in"

Blacksheep99

@Phaedrux said in Servo deployed probe on Duet Maestro:

@Veti said in Servo deployed probe on Duet Maestro:

change to C"^zprobe.in"

Veti suggested that, but you still have

@Blacksheep99 said in Servo deployed probe on Duet Maestro:

C"^!zprobe.in"

I tried it but when i then test G30 it fails immediately and tells me the probe is already triggered. Is this in relation to the G31 P500?