I could use some help

A Former User

@fcwilt So, I copy what's there from G91 to G30, delete that, then copy your code to that space to replace what was there, correct?

Doing that preserves the first 4 lines of code, and the last 6 lines as well.

fcwilt

@mac said in I could use some help:

@fcwilt So, I copy what's there from G91 to G30, delete that, then copy your code to that space to replace what was there, correct?

Doing that preserves the first 4 lines of code, and the last 6 lines as well.

Well if you wish to preserve those 2 or 3 first lines, that's fine.

But you don't need any code other than what I posted.

Frederick

A Former User

@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.

A Former User

@fcwilt okay, done

A Former User

@fcwilt on to Y, X?

A Former User

@fcwilt or should we test Z?

fcwilt

@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

A Former User

@fcwilt or are they related such that we have to do all 3 first, then test?

A Former User

@fcwilt I see, but the header is in the list of files. it makes for a cleaner look, I think.

fcwilt

@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

fcwilt

@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

A Former User

@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?"

fcwilt

@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

A Former User

@fcwilt link text

Here’s a link to the video of Z’s first attempt at homing.

A Former User

@fcwilt Z's going backwards. When I click on Z+0.5 it goes DOWN.

droftarts

@mac @fcwilt you had the z probe working. Using an endstop on the low end is a retrograde step.

Ian

A Former User

@droftarts hey, Ian, welcome to the show, what is a "retrograde step?"

fcwilt

@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

A Former User

@fcwilt @droftarts oh my god! what have I gotten myself between and betwixtd?

fcwilt

@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