I could use some help

fcwilt

@fcwilt @droftarts FREAKIN' SUCCESS!

With all of the endstops up, all of them are off, with Y endstop depressed, it is at min stop. with Z depressed, it is at min stop, and with X depressed, it is at MIN STOP!

Congrats.

Now that you know the endstops are working you can proceed to fine tune your homing code.

Because you have a Z endstop you can start with that.

One Z is homed then homing X and Y is a piece of cake.

How about doing one at a time.

Please post your Z homing code which should be in homeZ.g

Frederick

A Former User

@fcwilt

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Jun 27 2022 06:45:01 GMT-0700 (Pacific Daylight Time)
G91                      ; relative positioning
G1 H2 Z5 F3600           ; lift Z relative to current position
G90                      ; absolute positioning
G1 X-10.875 Y4.375 F3600 ; go to first probe point
G30                      ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91                     ; relative positioning
;G1 Z5 F60               ; lift Z relative to current position
;G90                     ; absolute positioning

fcwilt

@mac

OK that is code for homing with a Z probe.

Now that you have a working Z endstop you can use simpler code.

Something like:

G91               ; relative movements
G1 H1 Z-250 F3600 ; fast move toward Z endstop
G1 Z10            ; backup off a bit
G1 H1 Z-15 F360   ; slow move toward Z endstop

G90               ; absolute movements
G1 Z10 F3600      ; move to 10mm off the bed to allow X and Y movements

Frederick

A Former User

@fcwilt so you're saying I can copy and paste your suggestion into the homez.g, correct?

fcwilt

@mac said in I could use some help:

@fcwilt so you're saying I can copy and paste your suggestion into the homez.g, correct?

As long as you make sure none of the existing code is there.

Or you can rename the existing file if you want to save it.

And then create a new homeZ.g file and paste what I posted into it.

Frederick

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.