I could use some help
-
@mac said in I could use some help:
6/27/2022, 9:17:19 AM M574 Endstop configuration: X: low end switch connected to pin !io5.in Y: low end switch connected to pin !io6.in Z: low end switch connected to pin io2.inGreat. You getting the hang of this, aren't you!
So it says the Z endstop is configured on the low end, is connected to io2.in and does not have the ! character because the white wire is connected to the NO connection on the switch.
But it seems that pressing or not pressing the Z endstop switch doesn't change what M119 reports.
Did you verify that the Z endstop switch is still plugged onto the IO2 connector?
Frederick
-
@mac are you sure z endstop is connected to io2? Check with wiring diagram. https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Mini_5+_Hardware_Overview#wiring-diagram
Ian
-
@droftarts hey's baaaaaaaaaccccccccckkkkkkk
I just moved the white wire on the 5 pin io2 connector from io2_out to io2_in, The green wire is still in the center of the connector / connected to GND.
-
@mac said in I could use some help:
@droftarts hey's baaaaaaaaaccccccccckkkkkkk
I just moved the white wire on the 5 pin io2 connector from io2_out to io2_in, The green wire is still in the center of the connector / connected to GND.
Well that certainly should make a difference.
Please run the M119 tests with the Z endstop switch pressed and not pressed.
Frederick
-
@droftarts @fcwilt M119 reported all of the axis are NOT STOPPED, WAIT A MINUTE!!!!!
6/27/2022, 9:28:48 AM M119 Endstops - X: not stopped, Y: not stopped, Z: at min stop, Z probe: not stopped 6/27/2022, 9:28:11 AM M119 Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stoppedLook at the timecode, between :11 and :48 Z changed!
-
@droftarts @fcwilt I knew there was a reason I named this machine Frankenstein's Cinderella.
-
@mac said in I could use some help:
@droftarts @fcwilt M119 reported all of the axis are NOT STOPPED, WAIT A MINUTE!!!!!
6/27/2022, 9:28:48 AM M119 Endstops - X: not stopped, Y: not stopped, Z: at min stop, Z probe: not stopped 6/27/2022, 9:28:11 AM M119 Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stoppedLook at the timecode, between :11 and :48 Z changed!
So it seems like the Z endstop switch is now working?
Frederick
-
@droftarts @fcwilt I turned off the machine, then turned it back on. M119 reports that Z is at min stop.
My finger isn't anywhere near it.
But, when I depress Z, and send M119, it says Z NOT STOPPED.
-
@droftarts @fcwilt Z needs to be reversed, doesn't it.
-
@mac said in I could use some help:
@droftarts @fcwilt Z needs to be reversed, doesn't it.
Just edit the M574 line for the Z endstop and add the ! character, save, re-boot and re-test with M119.
You see what X and Y endstops do.
You need to get Z doing the same.
Frederick
-
@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!
-
@droftarts @fcwilt I wonder where that puts us?
-
@mac said in I could use some help:
@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
-
; 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 -
@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 movementsFrederick
-
@fcwilt so you're saying I can copy and paste your suggestion into the homez.g, correct?
-
@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
-
@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.
-
@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
-
@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.
