G30 S-1 is giving me heart stitches [SOLVED]
-
Please share your full config file and your deploy/retract macros if you use them. DWC 3.2 supports RRFv2 so you may try that as well.
Do you run G30 S-1 or S-3 from the console or from a macro file?
-
@chrishamm
I use the console, but also tried to setup a probe grid and use the menu run mesh bed levelling
The funny thing is, beside doing these false horizontal moves, it probes the bed succesfully, but still the last move crashes into the leadscrew outside the printbed... -
@o_lampe said in G30 S-1 is giving me heart stitches:
M208 X280 Y170 Z250 ; set axis maxima (adjust to suit your machine)
this is incorrect . its missing the S parameter
the correct dwc version is part of the release
find it here
https://github.com/Duet3D/RepRapFirmware/releases/tag/2.05.1 -
@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
-
@Veti said in G30 S-1 is giving me heart stitches:
@o_lampe said in G30 S-1 is giving me heart stitches:
M208 X280 Y170 Z250 ; set axis maxima (adjust to suit your machine)
this is incorrect . its missing the S parameter
the correct dwc version is part of the release
find it here
https://github.com/Duet3D/RepRapFirmware/releases/tag/2.05.1Thanks!
I'll try S0 for maxima, but the examples in the gcode wiki only use S1 for minima ( S0 is default?)Regarding the firmware, I did a full update earlier, but the DWC version was still 2.04?!
-
did you download and install this?
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/DuetWebControl-SD-2.0.7.zip -
@o_lampe said in G30 S-1 is giving me heart stitches:
I'll try S0 for maxima, but the examples in the gcode wiki only use S1 for minima ( S0 is default?)
you really should be using the https://configtool.reprapfirmware.org/Start to generate your config
-
@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?
-
@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 M557i 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 -
OK, thanks to both of you @Veti and @chrishamm
for the qiuck responses.
I now have the confidence to solve it.
Will report later -
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?
-
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?
-
@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
-
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
-
@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 S1What 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. -
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=0that would also get rid of the Z=0 datum message.
-
@Veti
To be clear, it uses the Z-probe as endstop. -
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 -
@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?
-
