G28 Z Error: Z probe already triggered at start of probing move

Phaedrux · 23 Jun 2021, 23:06

@handymanpa54 said in G28 Z Error: Z probe already triggered at start of probing move:

; Z-Probe
M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed
M557 X15:215 Y15:195 S20 ; define mesh grid

Since you don't have a Zprobe at all you can actually comment out these lines entirely by adding a; in front of the line. That way they will be ignored by the firmware.

Your homeall looks to be using the endstop rather than a probe, so I'm not sure where the error is coming from exactly.

 G1 H1 Z-405 F360        ; move Z down stopping at the endstop
G90                     ; absolute positioning
G92 Z0                  ; set Z position to axis minimum (you may want to adjust this)

Does your homez have the same lines?

Can you send M119 and check the status of your endstops? Send it once with the switch clicked, and again with it not clicked.

Also for good measure, please send M122 and M98 P"config.g" in the gcode console and post the responses here.

Handymanpa54 · 24 Jun 2021, 01:07

@phaedrux said in G28 Z Error: Z probe already triggered at start of probing move:

G1 H1 Z-405 F360 ; move Z down stopping at the endstop

6/23/2021, 9:03:23 PM M119
Endstops - X: not stopped, Y: not stopped, Z: at min stop, Z probe: at min stop
6/23/2021, 9:03:23 PM M119
Endstops - X: not stopped, Y: not stopped, Z: at min stop, Z probe: at min stop

6/23/2021, 9:05:37 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6M2-NW4SS-6JKD2-3SD6M-9VZ7L
Used output buffers: 3 of 24 (13 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73168 of which 76 recycled
Never used RAM 15376, free system stack 121 words
Tasks: NETWORK(ready,164) HEAT(blocked,308) MAIN(running,453) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:17:39 ago, cause: power up
Last software reset at 2021-06-23 17:14, reason: User, GCodes spinning, available RAM 15412, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 16.5, current 27.5, max 28.3
Supply voltage: min 23.8, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 1200, standstill, SG min/max 107/300
Driver 1: position 1200, standstill, SG min/max 104/310
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-06-23 21:05:36
Cache data hit count 1298563318
Slowest loop: 10.66ms; fastest: 0.21ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.9ms, write time 2.1ms, max retries 0
=== Move ===
DMs created 83, maxWait 557224ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 17, completed moves 17, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 21.15ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8

WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.25
WiFi MAC address f4:cf:a2:e2:10:76
WiFi Vcc 3.37, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25360
WiFi IP address 192.168.0.11
WiFi signal strength -75dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

6/23/2021, 9:06:40 PM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

; homez.g
; called to home the Z axis
;
G1 H1 Z-405 F360 ; move Z down stopping at the endstop
G90 ; absolute positioning
G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

Handymanpa54 · 24 Jun 2021, 01:12

@phaedrux
Hi,
My homez.g had other text so I copy and pasted in what you showed. Still the same results.
Then I toggled the x axis with my finger and saw the lite go on and off.I tried the same on the Z axis, but the lite goes dim but not all the way off!!!
Mark

Handymanpa54 · 24 Jun 2021, 01:34

@Phaedrux edrux

I noticed in the dashboard window Status shows Z_probe with red and 988? I don't know if that is normal?

Handymanpa54 · 24 Jun 2021, 01:36

@phaedrux

I got z to show homed, so I was able to use machine movement to give +5 but it moves down towards the bed and -5 makes it move away from the bed.

Phaedrux · 24 Jun 2021, 03:21

@handymanpa54 said in G28 Z Error: Z probe already triggered at start of probing move:

+5 but it moves down towards the bed and -5 makes it move away from the bed.

Then you'll need to change the direction of rotation for the Z axis.

M569 P2 S0 ; physical drive 2 goes backwards

Change S0 to S1 in config.g

@handymanpa54 said in G28 Z Error: Z probe already triggered at start of probing move:

6/23/2021, 9:03:23 PM M119
Endstops - X: not stopped, Y: not stopped, Z: at min stop, Z probe: at min stop
6/23/2021, 9:03:23 PM M119
Endstops - X: not stopped, Y: not stopped, Z: at min stop, Z probe: at min stop

And this is with the endstops both clicked and unclicked? Or just Z?

@handymanpa54 said in G28 Z Error: Z probe already triggered at start of probing move:

Then I toggled the x axis with my finger and saw the lite go on and off.I tried the same on the Z axis, but the lite goes dim but not all the way off!!!

Sounds like a wiring issue. Bad crimp maybe? Bad switch?

@handymanpa54 said in G28 Z Error: Z probe already triggered at start of probing move:

I noticed in the dashboard window Status shows Z_probe with red and 988? I don't know if that is normal?

If you commented out those probe lines I'm not sure what it would show there or why, but it's not really relevant at all when using an endstop instead of a probe.

@handymanpa54 said in G28 Z Error: Z probe already triggered at start of probing move:

RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2

While we're at it might as well update the firmware.

Download this zip file and upload it to the System tab in DWC.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip

Handymanpa54 · 24 Jun 2021, 03:39

@phaedrux
hi, the Z axis travels in the proper direction now. I changed from S1 to S0. I still had the problem with the limit switch. That turned out to be 10k resistor on the limit switch board. I get it to stop on home now. I just need some code so that it will do a double kiss of the z limit switch and the second one should be slower so it can be more exact.
I'm actually making progress.
Thanks for your help!

Phaedrux · 24 Jun 2021, 03:43

@handymanpa54 said in G28 Z Error: Z probe already triggered at start of probing move:

I just need some code so that it will do a double kiss of the z limit switch and the second one should be slower so it can be more exact.

You can see an example of that in the other homing files.

Sounds like you're making some progress now.

Handymanpa54 · 24 Jun 2021, 19:17

@phaedrux I'm trying to get paneldue working and proper code for z home.

6/24/2021, 3:09:26 PM 	Download of PanelDueFirmware-3.3.0-rc1-5.0i-7.0i.bin successful after 1s
6/24/2021, 3:08:34 PM 	Error: M997: File 0:/firmware/PanelDueFirmware.bin not found
6/24/2021, 3:08:34 PM 	M997 S4
6/24/2021, 3:07:07 PM 	Error: Probe already triggered at start of probing move
6/24/2021, 3:06:55 PM 	G28
Error: Probe already triggered at start of probing move
6/24/2021, 3:04:29 PM 	Error: M997: File 0:/firmware/PanelDueFirmware.bin not found
6/24/2021, 3:04:28 PM 	M997 S4
undefined

Handymanpa54 · 24 Jun 2021, 19:18

@phaedrux

; called to home the Z axis
;
G1 H1 Z-405 F1200        ; move Z down stopping at the endstop
G90                     ; absolute positioning
G92 Z0                  ; set Z position to axis minimum (you may want to adjust this)

G91                    ; relative positioning
G1 Z5 F100             ; lift Z relative to current position
G90                    ; absolute positioning

G1 H1 Z-405 F260        ; move Z down stopping at the endstop
G90                     ; absolute positioning
G92 Z0                  ; set Z position to axis minimum (you may want to adjust this)


G91                    ; relative positioning
G1 Z5 F100             ; lift Z relative to current position
G90                    ; absolute positioning
undefined

Handymanpa54 · 24 Jun 2021, 19:20

@phaedrux

Paneldue display is live but touch keys don't work.

Phaedrux · 24 Jun 2021, 19:46

What hardware version of PanelDue is it?
How do you have it wired up to the Duet?
You may need to connect the PanelDue to your PC via USB and flash that way once we identify which PanelDue you have and which firmware is appropriate for it. The automatic flashing via the Duet will only work with recent PanelDue hardware

Phaedrux · 24 Jun 2021, 19:49

I've cleaned up your homing file. You were using absolute positioning a few too many times.

 ; called to home the Z axis
;
G91 ; relative positioning
G1 H1 Z-405 F1200        ; move Z down stopping at the endstop
G1 Z5 F600             ; lift Z relative to current position
G1 H1 Z-405 F120        ; move Z down stopping at the endstop
G1 Z5 F600             ; lift Z relative to current position
G92 Z0    ; Define the actual gap between nozzle and bed here
G90                    ; absolute positioning

Phaedrux · 24 Jun 2021, 19:51

I'm still not sure why it's complaining about the probe.

Can you confirm that you are editing the config.g and homing files that are located in the /sys/ folder of the SD card, or the System tab in DWC?

Handymanpa54 · 25 Jun 2021, 13:08

@phaedrux
I flashed the panel due using Bossa with PanelDueFirmware-3.3.0-rc2-5.0i-7.0i. It works. Now I think the problem is with duetwifi config.g or something with duet wifi.
The touch screen works but it always jumps back to Console screen. Someplace I have something not right!

Help

Phaedrux · 25 Jun 2021, 15:31

You may want to stick with PanelDue firmware 3.2.11 for now while the bugs get worked out. Trying to use beta versions while getting setup can compound problems.

Can you confirm that you are editing the config.g and homing files that are located in the /sys/ folder of the SD card, or the System tab in DWC? And not the macros folder or elsewhere?

Handymanpa54 · 25 Jun 2021, 15:54

@phaedrux What do I need to edit in config.g???

Phaedrux · 25 Jun 2021, 16:51

In the Duet web control interface you go to the system tab and then click on the config.g to open the editor.

Or you pull the SD card and open the file in a text editor on your PC.

https://duet3d.dozuki.com/Wiki/Duet_Web_Control_v2_and_v3_(DWC)_Manual#Section_System

Handymanpa54 · 25 Jun 2021, 19:03

@phaedrux Hi,
What should I edit in config.g and anywhere in the config.g?

Mark

Phaedrux · 25 Jun 2021, 19:06

@phaedrux said in G28 Z Error: Z probe already triggered at start of probing move:

You may want to stick with PanelDue firmware 3.2.11 for now while the bugs get worked out.

Did you go back a version for PanelDue firmware?

@phaedrux said in G28 Z Error: Z probe already triggered at start of probing move:

Can you confirm that you are editing the config.g and homing files that are located in the /sys/ folder of the SD card, or the System tab in DWC? And not the macros folder or elsewhere?

Is this the case?

You're not really answering my questions, so I'm not really sure what's going on.

	G1 H1 Z-405 F360 ; move Z down stopping at the endstop
	G90 ; absolute positioning
	G92 Z0 ; set Z position to axis minimum (you may want to adjust this)

	; called to home the Z axis
	;
	G91 ; relative positioning
	G1 H1 Z-405 F1200 ; move Z down stopping at the endstop
	G1 Z5 F600 ; lift Z relative to current position
	G1 H1 Z-405 F120 ; move Z down stopping at the endstop
	G1 Z5 F600 ; lift Z relative to current position
	G92 Z0 ; Define the actual gap between nozzle and bed here
	G90 ; absolute positioning