G30 S-1 is giving me heart stitches [SOLVED]

o_lampe

@Veti said in G30 S-1 is giving me heart stitches:

also by any chance, do you have a G30.g in your sys folder?

:
That would explain a lot! But no...
Why there' a M486 in the override file, IDK. It' s the result of PID tuning the bed and M500 afterwards.
I can comment it out and see what happens.
Not much I guess, since I don't have a panelDue.

@Veti said in G30 S-1 is giving me heart stitches:

can you do a M92 P"config.g"

I know, you want to see a syntax check of config.g, but M92 is not the right command...couldn't find the right thing, so report later.

Veti

@o_lampe
M98 Sorry

Veti

M574 X1 S1 ; configure switch endstop for low end on X
M574 Y1 S1 ; configure switch endstop for low end on Y

that is not rrf3 syntax

o_lampe

@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

Veti

@o_lampe
thats why you lower the current only during homing

o_lampe

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

o_lampe

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.

o_lampe

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

Veti

can you post a picture of the back of your board?

Veti

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.

Veti

maybe. do you have a deployprobe.g?

o_lampe

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

Veti

@o_lampe

whats the content of deployprobe.g?

fcwilt

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

o_lampe

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.

o_lampe

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

Veti

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

fcwilt

@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

@Veti
Maybe they have changed that, but as I wrote earlier, I was glad to have found an old SD-card image for rrf2.0x

Anyway, A big thanks to @Phaedrux , @Veit and @fcwilt (in no particular order)
for their patience and time !

fcwilt

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

Anyway, 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