G30 S-1 is giving me heart stitches [SOLVED]
-
M574 X1 S1 ; configure switch endstop for low end on X
M574 Y1 S1 ; configure switch endstop for low end on Ythat is not rrf3 syntax
-
@Veti
two errors
I didn't like the stall detection feature on a coreXY. It either * rips my gt2 belts apart* or with current too low, one motor eventually skips steps.
Will add pin numbers and test again -
@o_lampe
thats why you lower the current only during homing -
the new endstop config
; Endstops M574 X1 S1 P"!xstop" ; configure switch endstop for low end on X M574 Y1 S1 P"!ystop" ; configure switch endstop for low end on Y M574 Z1 S2 ; configure Z-probe endstop for low end on Z
-
The endstop config doesn't make any difference.
I tried G92 x0 y0 homing and the g1 h1 homing, both ways home the axis, but G30 still refuses to work, unless I also home Z. And it still does the mambo all over the bed. -
Is there a chance, I got an counterfeit Duet board?
I remember, there were fysetec Duet Wifi 1.02 clones around, when I was busy building new printers. Maybe I've bought one of those, I don't remember....? -
can you post a picture of the back of your board?
-
there is something really wrong.
i cant see a reason why G30 would cause a G0 or G1 to be executed.
if the axis are not homed i get this error.
-
maybe. do you have a deployprobe.g?
-
@Veti said in G30 S-1 is giving me heart stitches:
maybe. do you have a deployprobe.g?
Yes they are there (deploy and retract )
I never thought, they'd be executed without setting it up?
It would be a great relief, if it was that simple.
But still, after all the reading of everything related to mesh bed leveling, there was NO hint of deploy/retract....
I can test it right now, the next print is done... -
whats the content of deployprobe.g?
-
Hi,
A couple of questions.
-
What sort of Z probe do you have? How does it work? How is it mounted?
-
Why is the Z axis min set to -2?
Thanks.
Frederick
-
-
OK, I think we can call it SOLVED
To my defense:
The standard SD-card images contain a lot of unused macros or sys-files.
How do I know, I have to remove some of them to make G30 work.
Which it does now, that I renamed them dont-deploy-probe and dont-retract-probe
Those names should be standard on all SD-card images.
And only those who have to deploy a probe, they will check the wiki and it should mention to rename them to deploy-probe etc...BTW: how can I call this thread solved?
I've already seen unsolved, but don't know, how that's done either. -
@fcwilt said in G30 S-1 is giving me heart stitches:
What sort of Z probe do you have? How does it work? How is it mounted?
Why is the Z axis min set to -2?
It's a conductive probe with NPN output. It's mounted to the extruder assembly.
The Z-axis is -2 because it allowed me to adjust Z height easier. -
@o_lampe said in G30 S-1 is giving me heart stitches:
The standard SD-card images contain a lot of unused macros of sys-files.
here is the standard content of the sd card
https://github.com/Duet3D/Duet-2-Hardware/tree/master/Duet2/SD Card Contents
it does not contain a retract and deploy script.
-
@o_lampe said in G30 S-1 is giving me heart stitches:
Which it does now, that I renamed them dont-deploy-probe and dont-retract-probe
Hi,
What was in deployprobe.g?
I added that file (just a M117 message) to my test setup and while it DID execute it didn't prevent G30 from working.
So I'm thinking it was the content of your delployprobe.g that was causing the problem.
Thanks.
Frederick
-
-
@o_lampe said in G30 S-1 is giving me heart stitches:
@Veti
Maybe they have changed, that, but as I wrote earlier, I was glad to have found an old SD-card image for rrf2.0xAnyway, A big thanks to @Phaedrux ,@Veit and @fcwilt (in no particular order)
for their patience and time !We are always glad to try to help and are even gladder (is that a word) when we actually do help.
Frederick
-
So did you check the contents of your delployprobe.g file?
Thanks.
Frederick
-
@fcwilt said in G30 S-1 is giving me heart stitches [SOLVED]:
even gladder (is that a word)
No Silly, the right term is more gladderer
@fcwilt said in G30 S-1 is giving me heart stitches [SOLVED]:
So did you check the contents of your delployprobe.g file?
; Probe deployment routine M564 S0 ; don't apply limits G1 X25 Y93 Z40 F10000 ; put probe arm next to belt G1 X-5 F500 ; move probe arm across belt G1 X12 F1000 ; move probe back G1 X0 Y0 F10000 ; move to somewhere sensible M564 S1 ; apply limits again
I don't remember ever using that, although I had an Allen key Z-probe on my very first Delta.
I always deployed and retracted it by hand.