G1 move option removed?

gnydick

There used to be an option to move until the end stop is hit without doing anything. Or didn't set anything, was just a noop to let you get to the switch quickly before an actually slow homing move. Where did that option go?

alankilian

@gnydick

GCODE directory says:

G0/G1 H and S parameter

The meaning of the H parameter is as follows:

    H0 no special action (default)
    H1 terminate the move when the endstop switch is triggered and set the axis position to the axis limit defined by M208. On delta printers, H1 also selects individual motor mode as for H2. Normally used with relative motor coordinates (see G91).
    H2 Individual motor mode. X refers to the X motor, Y refers to the Y motor, and so on. Normally used with relative motor coordinates (see G91).
    H3 terminate the move when the endstop switch is triggered and set the axis limit to the current position, overriding the value that was set by M208.
    H4 terminate the move when the endstop switch is triggered and update the current position (supported in RRF 3.2-b4 or newer)

Is there some reason that a G1 "move-until endstop is hit and do nothing" is somehow required and none of the other options will work for you?

gnydick

@alankilian, oh geez...

I have "vertical dyslexia". I don't know what it's actually called, but I can't read text very easily unless there's a lot of vertical spacing.

Thank you for pointing that out. I've been reading the gcode G1 section over and over and over and just never saw H0.

dc42

@gnydick I think H4 is what you are looking for. The phrase "update the current position" is not very clear; what it actually means is update the user position according to how much movement was actually done.

gnydick

@dc42 I just wanted to fast move Z before it does the slow z probe. With 600mm in Z it can take a long time to home.

BTW, I'm having a hard time finding how to be able to have both a probe and endstop configured for the same input.

I tried the fast z to endstop before homing and it just crashed hard, triggering the probe did nothing.

Phaedrux

@gnydick Why not just alter the probe speed for the first pass?

M558 F600
G30
M558 F60
G30

gnydick

@phaedrux yeah, I've done that in the past, I don't like changing what should be a global, reliable, dependable setting, that I don't have to keep track of throughout macros and configs.

jay_s_uk

@gnydick you can't have 2 things configured on the same pin at the same time. You'd have to configure it as an endstop, use it and then configure it as a probe

dc42

@gnydick said in G1 move option removed?:

@phaedrux yeah, I've done that in the past, I don't like changing what should be a global, reliable, dependable setting, that I don't have to keep track of throughout macros and configs.

Set it to your usual probing speed in config.g. Then in your Z homing file, save the existing value in a local variable before changing to the fast speed, so that you can restore it afterwards.

droftarts

@gnydick If you're using RRF 3.3 or later, M558 F parameter can take two values:

Fnnn or Fnnn:nnn Feed rate (i.e. probing speed, mm/min). Initial fast probe followed by probing at second speed supported in RRF 3.3 and later.

See https://docs.duet3d.com/en/User_manual/Reference/Gcodes/M558

Ian

A Former User

This post is deleted!

gnydick

@herve_smith I think that's a great idea. I'll try and build on that.

They could crowd source the documentation. Open it up using a wiki model that has moderation.

Phaedrux

@gnydick said in G1 move option removed?:

Open it up using a wiki model that has moderation.

That's exactly what dozuki was. It did get some community updates, but not many.

I think the plan is to open up the new documentation site as well.

gnydick

@phaedrux I had no idea that dozuki did that. And Duet's isn't the only group I use that uses it.