I could use some help
-
@fcwilt I have to run an errand. I'll be back in an hour.
-
@mac said in I could use some help:
@fcwilt hmmmm, the bed's being weird. I'm sending G1 H1 Y-92 , but the bed is inching towards the end stop instead of going straight for it.
And Y is now 0.0 again, whereas it was -30.
The change to Y=0 should be because the endstop was triggered.
The post move behavior of a G1 H1 move is to set the axis position to the min or max value specified in the M208 for that axis.
Since the endstop for this axis is specified to be at the low end, the min value is used, and that is just what you are seeing.
Was the move, while slow, smooth and even?
It could because you did not specify an F parameter for the move. In that case it uses the speed set by the last F parameter that was executed.
You could try it all again but this time include, say, F3600 in the G1 H1 moves.
Frederick
-
@mac said in I could use some help:
@fcwilt I have to run an errand. I'll be back in an hour.
Sounds good. I have a chore to do as well.
Be safe.
Frederick
-
@fcwilt
I've got to hand it to you, Frederick. You have tha patience of Job. -
@nightowl said in I could use some help:
@fcwilt
I've got to hand it to you, Frederick. You have tha patience of Job.Uh... I like a challenge?
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
-
@mac
Hey mac,
What am I seeing?
Did something work as expected for once?
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
-
@mac said in I could use some help:
Hey mac,
Nice but G1 H2 is not the same as G1 H1.
To make use of the endstop for homing, you have to use G1 H1.
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
@fcwilt yep one down, two to go.
-
@fcwilt of course there has to be something weird going on.
I changed the H2 to H1. When I hit SEND, the board went back a bit, then stopped. So I sent the instructions 3 more times to get the bed all the way back to the end stop.
So H2 makes the bed home as is expected. And H1 does something unexpected.
-
@fcwilt the printer's back to its old tricks. It's pounding on the front of the bed when I tell it to home. I'm just trying to get it to do what it did, and it's telling me something I won't write. I'm thinking the same thing towards it.
-
@fcwilt I'm having a hard time believing this, but it's true.
I sent G91
Then I wrote G1 H2 Y-220 F2600 (not 3600) (that was just a typo, but I'm not going to change it).
Now the jog menu to the right of Home Y is available. Before, it wasn't. (Like I had to Home Y to get the jog menu to function).
Now, when I use the jog menu to send the bed forwards 50mm, it goes all the way to the front of the printer.
Then, when I send the code again (G1 H2 Y-220 F2600) it goes all the way back to the end stop.
And I see that in the Status box, Y is showing as -220.0It seems to me that DWC is making shite up, Frederick. What say you?
-
@fcwilt I understood what you said, but when I used that code it did not work. Instead, the bed moved towards the end stop, stopped, and I had to push the button again and again to make it get there. But it never did because the firmware said you’re at 0 where you are, and that’s that.
-
@fcwilt I’m done for today. Did something to my ear that’s killing me.
-
@mac said in I could use some help:
@fcwilt I understood what you said, but when I used that code it did not work. Instead, the bed moved towards the end stop, stopped, and I had to push the button again and again to make it get there. But it never did because the firmware said you’re at 0 where you are, and that’s that.
I don't know what to say.
You did a series of short G1 H1 moves and they behaved as they should.
But a long G1 H1 move did not.
That suggests a stepper configuration issue.
Frederick
-
@mac
Here is the meaning of the various H parameter options for a G1 move:
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)
Notice that H1, H3 and H4 do respond to the triggering of the endstop switch but H2 does not.
H1 is used for homing.
H2 is often used to move an un-homed axis in the homing code of another axis.
I've never had an occasion to use H3 or H4.
Frederick
-
@fcwilt I’ve been looking at the M208 lines in my config.g.
M208 X0 Y0 Z0 S1 M208 X220 Y220 Z240 S0S1 means Forwards? S0 means backwards.
Why do those M208 lines end with S commands?
-
@mac said in I could use some help:
@fcwilt I’ve been looking at the M208 lines in my config.g
M208 X0 Y0 Z0 S1
M208 X220 Y220 Z240 S0I know S1 is different than S0. I’ll have to review above before I can finish this post.
Are you feeling better?
And if you recall I mentioned my preferred short form:
M208 Xmin:max Ymin:max Zmin:max
where there is no S0/S1 to remember - which I never could.
But for the old, two line way, S1 is min, S0 is max.
So your two lines are setting X, Y and Z min as 0, X and Y max as 220 and Z max as 240.
Frederick
Fredric
-
@fcwilt not really I kind of punctured my ear. A bit wobbly.
I read your bit about the H commands. I wish H1 would do what it’s supposed to on my machine.
I’ve been looking at the gcode info on the duet site.
Maybe the H-command issues are related to the X or the Z somehow. Maybe working on X will provide some insight. Do you have any Job left in you to put up with my stupidity?
Mac
