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

Handymanpa54

@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

@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

@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

@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

@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

@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

@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

@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

@phaedrux

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

Phaedrux

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

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

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

@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

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

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

Phaedrux

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

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

Mark

Phaedrux

@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.

Handymanpa54

@phaedrux
I did edit the home and config files that are located in the sys/folder of the sd card. When I open duet web control on the left I see * system and click on that brings up all the files config and homeg and others.
I flashed the firmware on paneldue to the latest, then flashed it again to the earlier version. Paneldue beeps at me showing the console and and a connector in the top right corner.
Mark

Phaedrux

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

What hardware version of PanelDue is it?
How do you have it wired up to the Duet? 4-wire or ribbon cable?

Do you have a case on the PanelDue that could be pressing against the screen?