G30 S-1 is giving me heart stitches [SOLVED]
-
This is the latest report:
I've updated to rrf3.2, changed a few minor settings from the config file I got from @Phaedrux (Z motor and probe needed to be inverted)
But still...
I also changed the z-probe port from zprobe.in to e1stop, but no change.
Anyone any idea? @fcwilt I'm now on rrf 3.2, you can chime in anytime
Is it possible I have my XY stepper config wrong? Their connectors would fit the Molex headers in both ways. They move the right way, but you never know...this is my last straw.
-
can you post your new config? and homing files?
-
@o_lampe said in G30 S-1 is giving me heart stitches:
Anyone any idea? @fcwilt I'm now on rrf 3.2, you can chime in anytime
All right - v3.2 - good job!
As mentioned post config and homing files.
Frederick
-
@fcwilt said in G30 S-1 is giving me heart stitches:
All right - v3.2 - good job!
I'm not so confident anymore, since I have to get used to the new gcodes and parameters. Will have to use the wiki quite often.
Printer is currently working, can't get the config or homing files.
BTW: I had to make a new PID tuning and write config-override, I'll post that too. Soon. -
@Veti said in G30 S-1 is giving me heart stitches:
can you post your new config? and homing files?
Here they come
homeall.g
config-override.g
config.gWhat you think?
-
whats the M486 S-1 doing in the config overwrite?
can you do a M92 P"config.g"
-
also by any chance, do you have a G30.g in your sys folder?
-
@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.
-
@o_lampe
M98 Sorry -
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?
