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

Veti

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

o_lampe

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

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

Yes, and I also tried some other versions with various Px and Sx parameters.

o_lampe

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

post your homeall then

; homeall file for use with dc42 Duet firmware on CoreXY printers
; This file assumes the endstop switches are at the low end of each axis.
; Reverse the X and Y movement for high-end switches.
; Adjust the bed upper and lower limits in config.g (M208 commands) to get the correct homing positions

G91                       ; relative mode
G1 F2400 		   		; course home X or Y //S1 X-340 Y-240 
G1 S1 X-340               ; course home X
G1 S1 Y-240               ; course home Y
G1 X14 Y14 F600             ; move away from the endstops
G1 S1 X-20                ; fine home X
G1 S1 Y-20                ; fine home Y
G1 X20 Y20 F4000
G1 F600
G1 S1 Z-300 F600
G1 Z5 F200
G30

; If you are using a microswitch for Z homing, insert similar code for the Z axis here,
; but use lower feed rates suitable for your Z axis.

G90                       ; back to absolute mode

; If you homed the Z axis using an endstop switch, you can insert a G92 command here to correct the height.

Veti

what script wont work without endstops

o_lampe

with the homeall script the behaviour is a bit different: it runs to 20,20 then probes (G1 S1) and runs against the rear beam.

Whenever G30 is issued,the printer freaks out.

o_lampe

@Veti
that was just my interpretation why homeZ doesn't work even after I homed X/Y
Seems the fake endstops doesn't change anything

Veti

if you dont want to use endstops, you should just setup sensorless homing

https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing

fcwilt

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

with the homeall script the behaviour is a bit different: it runs to 20,20 then probes (G1 S1) and runs against the rear beam.

Whenever G30 is issued,the printer freaks out.

Do you understand what a G1 command with the S1 (now H1) parameter does?

If you have the X and Y end stops forced active your homeall.g script will not work.

If you wish to use the Z probe for homing you don't use any G1 S1 Znnn command - just G30 BUT you likely want to use a G1 Xnnn Ynnn command to move to the center of the bed first.

You also need to have M574 Z0 and a valid Z probe configuration - which you appear to have.

If you aren't going to have actual end stops and are not going to use sensor-less homing you can force any axis to be "homed" with G92 Xnnn (or Y) but naturally the value nnn should be where the axis is actually positioned at the time.

I suggest you just install actual end stop sensors.

Frederick

Phaedrux

Can you send M98 P"config.g" in the console to check for some syntax error messages that are normally lost in startup?

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

M584 X0 Y1 Z2 E3 ; drive mapping

The M584 should come earlier than any of the commands that reference the axis that it creates. I think the only reason it's worked so far is that you're using default mappings, but still weird things can happen.

Copying your values into the config generator won't duplicate any of the syntax errors that may be there. I really suggest you try generating a fresh set even just to see what it looks like to compare to yours. And yes it will make switching over to RRF3 much easier.

o_lampe

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

You also need to have M574 Z0 and a valid Z probe configuration

Thanks @fcwilt
I read that line last night and I couldn't find sleep, because it makes totally sense.
It's like re-purposing a fan connector for something else:

1. you have to undefine the fan
1. now you can define it as LED-light colour changer or whatever

@Phaedrux
I moved the drive mapping right behind the M667 CoreXY definition.

Now, downing the coffee and back to the printer

The new config.g. I've also changed the extruder settings, since the E3d Titan is the only new part of the printer. It's run by a 1.8° 1708 pancake stepper, an improvement against the 0.9° original motor i guess.
config.g

o_lampe

One problem less, two new problems?

I tested the new config and behaviour was unchanged. G30 refuses to run before Z axis is homed. When it runs, it goes all over the place instead of probing where it should.

G30 X20 Y20 S2 ; is a valid code,right?

Then I checked my M667 setting again. Here in RepRap-Wiki and then in the Duet dozuki pages and look, what it says:

This command is deprecated in RRF 2.03 and later. Use M669 instead.

So I used M669 K1 and started homeAll.

; homeall file for use with dc42 Duet firmware on CoreXY printers
; This file assumes the endstop switches are at the low end of each axis.
; Reverse the X and Y movement for high-end switches.
; Adjust the bed upper and lower limits in config.g (M208 commands) to get the correct homing positions

G91                       ; relative mode
G1 F2400 		   		; course home X or Y //S1 X-340 Y-240 
G1 S1 X-340               ; course home X
G1 S1 Y-240               ; course home Y
G1 X14 Y14 F600             ; move away from the endstops
G1 S1 X-20                ; fine home X
G1 S1 Y-20                ; fine home Y
G1 X20 Y20 F4000
G1 F600
G1 S1 Z-300 F600
G1 Z5 F200
G30 X20 Y20 S-2

; If you are using a microswitch for Z homing, insert similar code for the Z axis here,
; but use lower feed rates suitable for your Z axis.

G90                       ; back to absolute mode

The tool still dances around the bed, but luckily didn't crash anywhere. The endposition of it can be seen here:

WHY does it do that?
The good news is, when I move to X0 Y0 Z5, the position is almost correct.

Now I can spend my time with mesh bed leveling and see what happens next.

//edit Should I go to absolute positioning (G90) before G30 in homeAll? Hold your breath, BRB...

Veti

your homeall also uses old syntax.

the S1 is depricated.

also i dont understand why you are making your life so difficult, instead of using the correct generated homing files from the configurator.

Using S-2 here is incorrect

o_lampe

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

your homeall also uses old syntax.

the S1 is depricated.

No, it's not, the dozuki wiki says, they are the same.

G1 Xnnn Ynnn Znnn S0	Ignore endstops while moving.
G1 Xnnn Ynnn Znnn S1	Sense endstops while moving. On Delta (only), axis letters refer to individual towers.
G1 Xnnn Ynnn Znnn S2	Ignore endstops while moving. Also ignore if axis has not been homed. On Delta and CoreXY, axis letters refer to individual towers.
G1 Xnnn Ynnn Znnn S3	Sense endstops while measuring axis length, and set the appropriate M208 limit to the measured position at which the endstop switch triggers.

RRF_2.02 and later, BEFORE M452 Laser Mode.
S parameter behaves as shown above.