I could use some help
-
@droftarts thank you so much, I'm going to try to learn how to do that.
-
@droftarts X-255? Y-255? my bed's 220 by 220! where is this coming from?
-
@droftarts not anything, my friend, but you can do amazing things, that's for sure.
I used to build houses. that was amazing until I had my accident.
-
@mac said in I could use some help:
X-255? Y-255? my bed's 220 by 220! where is this coming from?
It's -225 not -255
Your bed is 220, so you need to move slightly MORE then 220 to make sure you've hit the endstop in case it's way at the other end of the travel.
So your bed is 220, move -225 and you will always hit the home switch.
-
@mac Assuming you don't want to rewire the machine, or turn it around, the first thing you need to do is define the endstops as 'high end' or 'maximum' endstops. Change the following two M574 lines from X1 to X2 and Y1 to Y2:
; Endstops
M574 X1 S1 P"io5.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io5.in
M574 Y1 S1 P"io6.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io6.inNow when the nozzle homes against the endstops, it will set X and Y to the maximum value set by M208, rather than the minimum:
; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X220 Y220 Z240 S0 ; set axis maximaBut at the moment, your homing files will make the X and Y axis move towards the LOW end, rather than the HIGH end, so we need to flip these. In homex.g you currently have:
G1 H1 X-225 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F3600 ; go back a few mm
G1 H1 X-225 F360 ; move slowly to X axis endstop once more (second pass)These need to change to:
G1 H1 X225 F1800 ; move quickly to X axis endstop and stop there (first pass) G1 H2 X-5 F3600 ; go back a few mm G1 H1 X225 F360 ; move slowly to X axis endstop once more (second pass)
So that the X carriage goes to the maximum end of the axis, hits the X homing switch, backs off 5mm, then moves to touch it again.
You need to make the same changes to homey.g and homeall.g.
If you need to adjust where X0 Y0 is, you change the bed area in the M208 commands. Do the above first, and if you need more help with this part, let me know.
Ian
-
6/24/2022, 2:08:29 PM M208 X-8;200 Y0;202 ; set axis limits Error: M208: X axis maximum must be greater than minimum
-
@mac it should be a colon : between values, not a semicolon ;
Ian
-
@alankilian thanks, man, childhood dyslexia strikes again
-
@droftarts okay, so, now we're talking hard-core editing of the actual config files, correct? Versus using RRF to "edit" them, correct?
So I'm guessing I can just "look" at the files, and high light what I want to change, or delete, and hit ENTER, and that will make the change, then "SAVE" and that will save the whole file with the changes?
And the changed file will become the instructions used? (There's no reloading that needs to happen?)
A little confirmation (or correction), will go a long ways right about now.
Mark
-
@mac Yes, you can edit the files in DWC. Sorry, I should have made that clear. Make sure you make a backup, as any changes will only exist on the SD card.
Alternatively, now that you know you have maximum endstops on X and Y, you could go back to the Configuration tool and change it there.
Did you know you can load the config.json file from a previously created configuration back into the Configuration Tool, and all the settings you made previously will be applied? That can help if you have a lot of changes to do.
Ian
-
@alankilian nice clarification, Alan Killian
-
@droftarts I did not! but I think that's how i'll approach this humongous job-a-rooney.
Mark
-
@mac actually, that's what I've been doing all along (the line says / shows Square, config.json GRAPHIC with SQUARE with ARROW in it edit via config tool.
That's what I'm assuming your referring to.
Let's get started!
Mark
-
@droftarts so really, the only problem was the Endstop locations for x and y were low end when they should have been set to High end.
Once again, getting high wins the day!
Mark
-
@droftarts HERE'S AN UPDATE
X Y and Z performed MUCH BETTER. However, when I HOME ALL'd X hit the Endstop 3 or 4 times before stopping. Then the print head, accompanied by the BLTouch, qhich sensed the bed, and that was that.
So, should I post all of the config files again to see what's causing X to want to go further left than it should? What I'm seeing is the nozzle's pointed right at the very edge of the bed.
-
@drofarts Actually, I spoke too soon. I just tried to Home All again. The Print Head came to the X-endstop, and pounded on it until I turned the printer off.
Then, I turned the printer back on and Home All-d the printer to see what would happen. The Print Head came forwards, beyond the front edge of the bed, and then started to land in the empty space in front of the bed, where nothing would stop the BLTouch.
So, the Print Head is not honoring the X-endstop, and (it's possible) that the Y-axis is crushing the y-endstop at the rear of the machine.
(Actually, I have this extender on the Y-stop to move the bed FORWARDS. I think I'll remove that. It was put there to "correct" a problem with the original mystery firmware, which refused to take the bed all the way to the back."
Hmmmmm.
Mark
-
-
@droftarts I'm posting what's above this because the language says the end stops are "high end," but the code ends with S1, not S2?
-
@mac here’s a picture that I think is where the print head thinks Home is?
Mark
-
@mac said in I could use some help:
@droftarts I'm posting what's above this because the language says the end stops are "high end," but the code ends with S1, not S2?
Hey mac,
The number after the letter (X, Y or Z) specifies where the endstop is located - high end or low end of axis.
The S parameter specifies the type of endstop. From the docs for M574:
M574 Parameters
Xnnn Position of X endstop: 0 = none, 1 = low end, 2 = high end.
Ynnn Position of Y endstop: 0 = none, 1 = low end, 2 = high end.
Znnn Position of Z endstop: 0 = none, 1 = low end, 2 = high end.P"pin_name" Defines the pin name(s) that the endstop(s) for the specified axis are connected to, see Pin Names. Needed when S=1. May need ! before pin name to invert signal, or ^ to enable the pullup resistor, for example on the Duex expansion board.
Snnn 1 = switch-type, 2 = Z probe (when used to home an axis other than Z), 3 = single motor load detection, 4 = multiple motor load detection
This command must be later in config.g than the M584 command that creates additional axes, or axes that have multiple motors and endstops.
You may already know this but I will include just to be safe.
When you execute a G1 H1 command it stops when it activates an endstop sensor.
At that point the logical position of the axis is set to axis min or max (see M208) depending on the declared position of the endstop (high or low).
There is nothing that insures that physical position at that point matches the logical position.
If you have an endstop at the low end and the axis min is 0 but the endstop activates at 5 the logical position will be set to 0 but that physical position will be 5.
To keep the logical and physical positions in sync you can:
- insure the point at which the endstop activates matches the min/max for the axis (as appropriate)
- adjust the logical position using a combination of G1 moves and G92 set logical position commands.
Frederick