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

o_lampe

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

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

I use the console, but also tried to setup a probe grid and use the menu run mesh bed levelling

i see no M557 definition in your config for the mesh bed leveling

Right,
It's defined through the autoleveling menu in DWC.
That's why I tried to update DWC to 2.07...

I can try to put it in the config.g and then simply send G29 from the console?

Veti

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

It's defined through the autoleveling menu in DWC.

again the configtool will generate a config for you that has all the relevant parameters set.
even M557

i suggest that you put your existing values in there.
this will also make the migration to version 3 a lot easier as you can just import he json

o_lampe

OK, thanks to both of you @Veti and @chrishamm
for the qiuck responses.
I now have the confidence to solve it.
Will report later

o_lampe

Ok, no changes in behaviour so far...
I changed the maxima setting to 208 ...S0
I added M557 X10:250 Y10:170 S40:40 to specify the mesh grid
I copied DWC 2.07 to the SD card. ( What a relieve)

But still it does these funny moves and crashes into the leadscrew.

Any other suggestions?

o_lampe

Oh, there's one thing I want to ask:
I have a negative number for Zmin in the M208 S1.
Now, when I home Z, the homed height is set to -2 or whatever I set in M208.
I haven't found the right way to compensate that other than overwriting it with G92 Z0.

Does it matter if my G31 Z-probe definition is before or after M208?

Veti

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

Now, when I home Z, the homed height is set to -2 or whatever I set in M208.

post you home script

fcwilt

M574 X Y S3 - where are the values for X and Y specify the location of the end stop?

You have specified the Z trigger height in G31 as 0. Usually a capacitive probe triggers a few mm off the surface.

Also capacitive probes can be slow to respond so you might need to change the F value in M558.

When you home any axis the position is set to the axis min/max based on the axis parameter in M574.

You have specified that the end stop of Z is at the low end so it gets set to Z min which you have as -2.

Why do you have Z min as -2?

Frederick

o_lampe

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

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

Now, when I home Z, the homed height is set to -2 or whatever I set in M208.

post you home script

G91
G29 S2
G1 S1 Z-300 F800
G1  Z5 F800
G1 S1 Z-10
;G92  Z0.0
G90
;G29 S1

What does it mean, when DWC is giving me a warning about Z=0 datum isn't set everytime i load the heightmap?
Is it trying to do that, when it crashes against the leadscrew?
I've made two short videos to show what happens, but I'm not sure when I find the nerve to upload them to u-tube.

Veti

that is not a home script. as it disregards any endstop

nevermind. it used the old S syntax.

that is the reason why its set to S-1
when the endstop is triggered the axis is set to the endstop position.
with a G30 this will not happen as this sets the current positon to z=0

that would also get rid of the Z=0 datum message.

o_lampe

@Veti
To be clear, it uses the Z-probe as endstop.

Veti

that is wrong.

try a default homez.

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.2.2 on Wed Jan 20 2021 13:31:39 GMT+0100 (Central European Standard Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X15 Y15 F6000 ; go to first probe point
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning

o_lampe

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

with a G30 this will not happen as this sets the current positon to z=0
that would also get rid of the Z=0 datum message.

So, I should use G30 instead of G1 S1?

Veti

@o_lampe

yes

you REALLY need to use a standard config that is generated by the config tool.

o_lampe

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

@o_lampe

yes

you REALLY need to use a standard config that is generated by the config tool.

I started filling out the config wizard, but then got stuck with the stepper settings. I would have to copy my existing config settings into the wizard, so what is it good for?
I'd just copy any possible mistake into the new file, if there's any...

Veti

@o_lampe
well it would have generated a correct homing script for once.
and as i said it will make the migration to version 3 easier

o_lampe

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

G1 X15 Y15 F6000 ; go to first probe point

The head moves to that first probe point and then throws an error insufficient axes homed
As always I homed X/Y before homeZ with G92 X0 Y0.

Do I really have to install endstops for X/Y axis?
I never needed them for my CNC. I just parked the toolhead at 0,0 before I switched off and went the G92 way to start...
I checked the homeX/Y files. They all look similar to the one I originally posted. (I had this SD-card backup from my CNC machine)

Veti

the G30 command give you insufficient axis homed?

fcwilt

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

As always I homed X/Y before homeZ with G92 X0 Y0.

The would work IF the actual positions of X and Y were zero. How do you know they are?

Do I really have to install endstops for X/Y axis?

No - you can use sensor-less homing.

I don't care for that myself. To me using physical end stop sensors for homing is like stopping your car using the brakes. Sensor-less homing seems like stopping your car by running into the car in front of you.

As to using G30: did you read the docs on what each variant of G30 does?

Frederick

o_lampe

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

the G30 command give you insufficient axis homed?

No, the macro doesn't run G30 because of the error message.

I used jumpers on X/Y endstops and defined them as active high
When I ask M119 it reports X/Y at min endstops. Now I should be able to use the homeall macro. But it stops after the same line as above mentioned.

Veti

post your homeall then