G28 Z Error: Probe already triggered at start of probing move???

Pickett · 18 Jul 2021, 05:41

I do not know what is going on here it was working then it wasnt working it still detracts and retracts when the board is powered on but I get this"

G28 Z
Error: Probe already triggered at start of probing move ?????

However when I run an M558 I get this:

M558
Z Probe 0: type 9, input pin io3.in, output pin nil, dive height 5.0mm, probe speeds 120,120mm/min, travel speed 6000mm/min, recovery time 0.00 sec, heaters normal, max taps 1, max diff 0.03

And here is my config.g:

; Configuration file for Duet 3 Mini 5+ (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Jul 17 2021 23:11:52 GMT-0500 (Central Daylight Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"DarkHorsev2" ; set printer name
M918 P1 E4 F2000000 ; configure direct-connect display

; Drives
M569 P0.0 S0 ; physical drive 0.0 goes backwards
M569 P0.1 S0 ; physical drive 0.1 goes backwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S0 ; physical drive 0.3 goes backwards
M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z600.00 E3600.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z200.00 E2500.00 ; set accelerations (mm/s^2)
M906 X1050 Y1150 Z1250 E900 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 X400 Y400 Z450 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"io5.in" ; configure active-high endstop for low end on X via pin io5.in
M574 Y1 S1 P"io6.in" ; configure active-high endstop for low end on Y via pin io6.in
M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"io3.out" ; create servo pin 0 for BLTouch
M558 P9 C"^io3.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X19 Y15 Z2 ; set Z probe trigger value, offset and trigger height
M557 X15:385 Y15:385 S20 ; define mesh grid

; Heaters
M308 S0 P"temp1" Y"thermistor" T98801 B4185 ; configure sensor 0 as thermistor on pin temp1
M950 H0 C"out1" T0 ; create bed heater output on out1 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"temp2" Y"thermistor" T98801 B4185 ; configure sensor 1 as thermistor on pin temp2
M950 H1 C"out2" T1 ; create nozzle heater output on out2 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S320 ; set temperature limit for heater 1 to 320C

; Fans
M950 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency
M106 P0 C"Part Cooler" S0 H-1 ; set fan 0 name and value. Thermostatic control is turned off
M950 F1 C"out4" Q500 ; create fan 1 on pin out4 and set its frequency
M106 P1 C"Hotend" S1 H1:0 T45 ; set fan 1 name and value. Thermostatic control is turned on
M950 F2 C"out5" Q500 ; create fan 2 on pin out5 and set its frequency
M106 P2 C"Case/PWR Strip" S1 H1:0 T45 ; set fan 2 name and value. Thermostatic control is turned on
M950 F3 C"out6" Q500 ; create fan 3 on pin out6 and set its frequency
M106 P3 C"LED's" S1 H-1 ; set fan 3 name and value. Thermostatic control is turned off

; Tools
M563 P0 S"V6 TI Hotend" 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

; Custom settings are not defined

; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue
M501 ; load saved parameters from non-volatile memory
M911 S22 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first tool

Any help would be much appreciated thanks in advance let me know what I else I neeed to tackle this problemo thanks!!!!!!

fcwilt · 18 Jul 2021, 08:02

@pickett

As a first step you can execute M98 P"config.g" from the DWC console and check for any errors reported.

Frederick

jay_s_uk · 18 Jul 2021, 08:17

@pickett do you have deploy and retract files in your sys folder? Do M401 and M402 deploy and retract the probe?

Pickett · 18 Jul 2021, 15:25

@fcwilt I have tried the M98 P"config.g" and it returns no errors, none reported it just replies with the same command all highlighted in green?

@jay_s_uk No I tried this already and it doesnt seem to retract or deploy said Z Probe? Is it unusual that it says Output Pin Nil?

as seen above:

Z Probe 0: type 9, input pin io3.in, output pin nil<<<-----?????

DIY-O-Sphere · 18 Jul 2021, 15:38

@pickett said in G28 Z Error: Probe already triggered at start of probing move???:

M501 ; load saved parameters from non-volatile memory

Please provide content of config-override.g

jay_s_uk · 18 Jul 2021, 16:06

@pickett don't worry about the output pin. It doesn't use one. It uses a servo pin which is set through M950

Pickett · 18 Jul 2021, 20:44

@jay_s_uk and yes FTM yes there are two separate files one for deployprobe and the other for retractprobe.g

Pickett · 18 Jul 2021, 21:08

@diy-o-sphere ; config-override.g file generated in response to M500 at 2021-07-11 08:59

; Heater model parameters
M307 H0 R0.274 C461.300:461.300 D2.10 S1.00 V24.2 B0
M307 H1 R2.429 C140.000:140.000 D5.50 S1.00 V0.0 B0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00

jay_s_uk · 19 Jul 2021, 05:37

@pickett where are the deploy and retract files and what's in them?
And the ^ isn't needed on io3.in
Can you also post a photo of the wiring at the duet end?

dc42 · 19 Jul 2021, 06:59

@pickett try adding parameter R0.2 to your M558 command. This is to give the probe time to deploy before you read it. Also remove the ^ as @jay_s_uk suggests.

Pickett · 21 Jul 2021, 03:43

@jay_s_uk retractprobe.g is located in system directory....

                       @pickett where are the deploy and retract files and what's in them?

; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Jul 20 2021 14:02:58 GMT-0500 (Central Daylight Time)
M280 P0 S90 ; retract BLTouch; deployprobe.g

; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Jul 20 2021 14:02:58 GMT-0500 (Central Daylight Time)
M280 P0 S10 ; deploy BLTouch

                                       Can you also post a photo of the wiring at the duet end?

YOU KNOW WHAT FOR SOME ODD EFFIN REASON I HAD PLACED IT IN io4 I feel so freaking dumb wow guys I do apologize I sincerely thank you for your time and efforts in helping me getting this resolved. WHen I had referenced the pic from the tutorial I had been using I realized I simply plugged it all back in to io4 and not io3.in/out wow I feel so silly thanks guys ok that does it until next time............... Quick question if any of you can..... can I use a mechanical endstop as in an endstop that simply completes a circuit in a mechanical fashion and use that for an endstop? Isnt this what endstops technically do anyways is to complete a circuit for a brief moment to trigger the END in a STOP?

I have this lovely looking endstop that is brass internals inside of a clear acrylic case and it looks freaking awesome and was wondering if I could use that as endstops. It even has this nice satisfying click when it is depressed? Here is a pic:

jay_s_uk · 21 Jul 2021, 04:59

@pickett glad you got it sorted.
And yes you can