Endstops Stop working

dank0

@t3p3tony 3.4.0beta4, ok so i think found the issue - when the homing goes direction Z it disable all endstops. Did you guys see this issue before?

T3P3Tony

@dank0 i have not seen that, whats in your homez.g? Also could you try downgrading to 3.4b4 temporarily to see if the problem goes away?

dank0

@t3p3tony so i tried to downgrade, it was still with the same issue. I also have one SD card with configured klipper, so i tried to flash klipper and klipper works fine. But i want to use reprap fw.

; homez.g
; called to home the Z axis

G90 					; absolute mode
G1 H2 Z40 F3000   		; lift Z relative to current position
G1 X310 Y345 F7000		; go to enprobe point
G1 H1 Z-340 F1000  		; move Z down stopping at the endstop
G1 H2 Z5 F1000 			; move Z back 5mm
G1 H1 Z-10 F1000 		; move Z slowly towards the switch until it triggers
G1 H2 Z50 F3000			; move Z up 50mm
G1 X175 Y175 F7000		; go to the center of bed
G90 					; back to absolute mode

dank0

I have another question maybe that is the issue -

from top view my origin 0.0 position is in rear, right corner. In klipper i have same origin. In klipper my movement to left are positive so for example if i go from 0 to 200, it is + direction. Here is the minus direction so it will be -200. is that correct or i have switched motor directions?

|-----------| 0.0
|.............|
|.............|
|.............|
|________|

When i was installing Klipper i have to switch Z motors position so they are like this

Z3 |-----------| Z
      |.............|
      |.............|
      |.............|
Z2 |________| Z1

In the REPRAP the motors are defined with M584

M584 X0 Y1 Z2:5:6:4 E3

does the Z order matters?

T3P3Tony

@dank0 RepRap firmware assumes a right handed co-ordinate system

So for CoreXY XY motors:
https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCoreXYPrinter#Section_Testing_motor_movement

For a CoreXY or H-Bot machine, RepRapFirmware assumes that the motor connected to the X motor output moves the head in the +X and +Y directions when it runs forwards, and that the Y motor moves the head in +X and -Y directions when it runs forwards.
Important: make sure that you have chosen a right-hand axis system. That is, looking down on the printer the +Y direction should be 90 degrees anticlockwise from the +X direction. If instead it is 90 degrees clockwise, you have a left-hand axis system, which will give you mirror-image prints.

For the independent Z motors:
https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors

You must use the M671 command to define the X and Y coordinates of the leadscrews. The M671 command must come after the M584 command and must specify the same number of X and Y coordinates as the number of motors assigned to the Z axis in the M584 command; and these coordinates must be in the same order as the driver numbers of the associated motors in the M584 command. The M671 command must also come after any M667 or M669 command.

So I think you have everything backwards, however I am not convinced this is the cause of the Z homing issue.

fcwilt

@dank0

In your homeZ.g file you have an initial G90 - it should be a G91.

Frederick

dank0

Thanks @T3P3Tony and @fcwilt
i switched all those motors correctly by it really didn't help me with ENDSTOPs
. So i went back to Klipper and they all work fine, weird. I cannot firuge out RR.

T3P3Tony

@dank0 how did they not work with the endstops? you can set where the endstops are on the axis with the M574 commands, so they can be configured as either at the min or the max of the axis.

Or do you mean the issue where homing Z stops the endstops working?

dank0

@t3p3tony no, the endstops become not activated. they work after reboot but when the motors make motion they become not active, i don't know why. but Klipper have no issue - in klipper i have to just add pin numbers and works but RR doesnt react properly on xstop, ystop etc. also i tried to change to other sockets without luck.

fcwilt

@dank0

Did you verify that when triggering the endstop sensors by hand that the correct state appeared in the the Object Model as displayed in the DWC?

Did you correct your homing code where you had the G90 that should have been a G91?

Frederick

dc42

@dank0 did you correct that G90 to G91 as @fcwilt pointed out?

Please post your homex.g, homey.g and homeall.g files too.

BTW your Z homing script is incorrect - although I don't think that is the cause of your issue with re-homing X and Y. When using a Z probe for homing, you should home Z using a G30 command, not a G1 H1 command, and you do not need to define a Z endstop using M574. See https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_Z_using_a_Z_probe.