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

o_lampe

Hi Guys,
at first I apologize in advance for ranting about RRF2.05.1 and for the lenghty read.
I should bite the lemon and migrate to rrf3.x, but I can't let go...

here's the story:
My CoreXY with Duet2 WiFi works well, so I'm confident, my config.g is OK.

For a while now I want to use G29 for mesh bed levelling,
but the printer goes nuts when I send a simple G30 S-1 at the center of the bed.

What I did so far:
Set the probe offset with G31 in config.g
Home the printer with G92 XYZ
Move the head to the center of the bed
Send G30 S-1 or G30 S-3 as I've done so many times

But the printer moves the head to Z35 and into the negative X-area. ( It's defined as CoreXY not Delta)
It does a slow probing move there, moves back to the center, then goes again even further into the neg. X-area and crashes viciously against the leadscrew.
The steppers scream, I scream and gone is the homed position and my good mood.

That happens for a week now. Today I saw that I'm using DWC2.04 instead of 2.07 or 1.22.6 as mentioned in the github repository.
So I searched for 2.07, but couldn't find it. Went for 1.22.6 instead ( which I regret because of the different setup)
That didn't change the behaviour anyway.

It seems, I'm the only one with these false horizontal moves at least, I couldn't find other forum threads.

What could be wrong with my setup?

THX for reading
o_lampe

//edit
for those who read that thread later, make sure you don't have deploy-probe.g and/or retract-probe.g in your sys folder.

Veti

post your config

o_lampe

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

post your config

Just thought the same...
config.g

; Configuration file for Duet Ethernet and Wifi

; Communication and general
M111 S0                            		; Debug off
M550 PDuetCNC					; Machine name and Netbios name (can be anything you like)
M551 Preprap                   			; Machine password (used for FTP)
;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED		; MAC Address

;*** Networking - Enable for both WiFi and Ethernet boards.
M552 S1						; Turn network on

M555 P2			; Set output to look like Marlin
G21				; Work in millimetres
G90				; Send absolute coordinates...
M83				; ...but relative extruder moves

M667 S1						; set CoreXY mode
M92 X200 Y200 Z2500			; Set axis steps/mm
M92 E400					; Set extruder steps per mm for Titan 1.8degree

M201 X1000 Y1000 Z100 E1000      	; Accelerations (mm/s^2)
M203 X15000 Y15000 Z1200 E3600  	; Maximum speeds (mm/min)
M566 X600 Y600 Z30 E20          	; Maximum jerk speeds mm/minute
M208 X280 Y170 Z250					; set axis maxima (adjust to suit your machine)
M208 X0 Y0 Z-2 S1					; set axis minima (adjust to make X=0 and Y=0 the edges of the bed)
M906 X1500 Y1500 Z1200 E800 I40		; Set motor currents (mA) and increase idle current to 40

; Axis and motor configuration
M569 P0 S1					; Drive 0 goes forwards
M569 P1 S0					; Drive 1 goes backwards
M569 P2 S1					; Drive 2 goes forwards
M569 P3 S0					; Drive 3 goes forwards
M569 P4 S1					; Drive 4 goes forwards
M574 X Y S3					; set endstop config (x y sensorless homing)
M574 Z1 S2					; z endstop is on zprobe
M584 X0 Y1 Z2 E3			; drive mapping
M350 X16 Y16 Z16 E16 I1		; Set 16x microstepping with interpolation

; Thermistors
M305 P0 T100000 B3950 R4700 H30 L0		; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 T100000 B3974 R4700 H30 L0		; Put your own H and/or L values here to set first nozzle thermistor ADC correction

M570 S180					; Hot end may be a little slow to heat up so allow it 180 seconds

; Adjustments for J-heads used as dummy heaters on test rig
M307 H0 A145 C904 D2.5 B1
M307 H1 A250 C140 D5.5 B0

; Fans
M106 P1 S-1					; disable thermostatic mode for fan 1

; Tool definitions
M563 P0 D0 H1					; Define tool 0
G10 P0 S0 R0					; Set tool 0 operating and standby temperatures

; Z probe and compensation definition
;*** If you have a switch instead of an IR probe, change P1 to P4 in the following M558 command
M558 P5 I1 F500 T5000 A3 H5			; Z probe is an capacitive NPN sensor
G31 X55 Y10 Z0 P500					; Set the zprobe height and threshold (put your own values here)

T0						; select first hot end

chrishamm

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?

o_lampe

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

Veti

@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

Veti

@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

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:

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

Thanks!
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?!

Veti

did you download and install this?
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/DuetWebControl-SD-2.0.7.zip

Veti

@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

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.