I could use some help
-
@fcwilt on to Y, X?
-
@fcwilt or should we test Z?
-
@mac said in I could use some help:
@fcwilt I just concerned that if I delete everything, then paste your code into that blank space, I'll loose the ; homez.g (header)?
It's not that I don't trust you, I've just never done any coding.
Just open the file, move down after the header lines, delete everything there to the end and paste what I posted into the blank space after the header.
Even if you did accidently delete the header lines you could simply type them in again.
; homeZ.g ; called to home the Z axis ;
Frederick
-
@fcwilt or are they related such that we have to do all 3 first, then test?
-
@fcwilt I see, but the header is in the list of files. it makes for a cleaner look, I think.
-
@mac said in I could use some help:
@fcwilt or are they related such that we have to do all 3 first, then test?
You can test homing Z and see if it works.
Then we will do X and Y.
Frederick
-
@mac said in I could use some help:
@fcwilt I see, but the header is in the list of files. it makes for a cleaner look, I think.
Absolutely - I include headers and footers.
; === homeZ.g BOF === ; the actual code would go here ; === homeZ.g EOF ===
Just FYI, BOF is for "beginning of file", EOF is for "end of file"
Frederick
-
@fcwilt so you write the code, but you don't put the line numbers in; that's what the program you write the code in does?
And the === before what you wrote, and the === after what you wrote create the idea of a "Header?"
-
@mac said in I could use some help:
@fcwilt so you write the code, but you don't put the line numbers in; that's what the program you write the code in does?
And the === before what you wrote, and the === after what you wrote create the idea of a "Header?"
The part at the top of the file is the "header"
The part at the bottom of the file is the "footer"
I actually put more than I posted into the header and footer - I was just posting a simple example.
Frederick
-
-
@fcwilt Z's going backwards. When I click on Z+0.5 it goes DOWN.
-
@mac @fcwilt you had the z probe working. Using an endstop on the low end is a retrograde step.
Ian
-
@droftarts hey, Ian, welcome to the show, what is a "retrograde step?"
-
@droftarts said in I could use some help:
@mac @fcwilt you had the z probe working. Using an endstop on the low end is a retrograde step.
Ian
In your opinion. I see it as a distinct improvement.
X and Y can be homed with no Z movement required.
And generally Z homing can be faster.
But that is just my opinion.
Frederick
-
@fcwilt @droftarts oh my god! what have I gotten myself between and betwixtd?
-
@mac said in I could use some help:
@fcwilt Z's going backwards. When I click on Z+0.5 it goes DOWN.
Then adjust the M569 for that Z drive and change it from normal to reverse or reverse to normal - the opposite of what it is now.
Re-boot and re-test.
Frederick
-
M569 P0.3 S1 ; physical drive 0.3 goes forwards
-
@fcwilt so I'm thinking I should change the S1 to S0? (I don't know that 0 means reverse, or the opposite of, I'm just surmising that's what I should do).
-
@mac said in I could use some help:
M569 P0.3 S1 ; physical drive 0.3 goes forwards
So you don't know what to change?
OK here you go:
The P specifies the driver number which you have as 0.3 which sounds fine.
The S specifies the direction with S1 being normal and S0 being reverse.
Don't get hung up on normal and reverse - there really is no standard for what rotation is considered normal and what is considered reverse.
So since you have S1 change it to S0, re-boot and re-test.
Frederick
-
@fcwilt nice to have that fan stop rattling away. I'm glad I figured that out, and thank you for the additional information. I was thinking of that song, One way, and another, when I read about there being no "normal and reverse."