I could use some help

@mac well, I guess that's the end of that.

droftarts

; Endstops
M574 X2 S1 P"!^io5.in"                             ; configure switch-type (e.g. microswitch) endstop for high end on X via pin !^io5.in
M574 Y2 S1 P"!^io6.in"							   ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin !^io6.in
M574 Z2 S1 P"!^io2.in"							   ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin !^io2.in

Change to X1, Y1 and Z1. How did these get changed back? These were right yesterday!

Ian

@droftarts

; Endstops
M574 X1 S1 P"!^io5.in"                             ; configure switch-type (e.g. microswitch) endstop for high end on X via pin !^io5.in
M574 Y1 S1 P"!^io6.in"							   ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin !^io6.in
M574 Z1 S1 P"!^io2.in"							   ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin !^io2.in

@droftarts I guess I could scroll backwards through this thread to find out, but I don't want to blame anyone. I changed them, for whatever reason, so I'm the one at fault.

And now I've changed them again.

@droftarts

Here's the M119 report:

6/28/2022, 10:58:25 AM	M119
Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped

@droftarts what did that change accomplish? Is there something I’m supposed to do now? Would you like me to home the Y-axis to see if it stops at the endstop, then backs off?

@droftarts my apologies to Frederick for pissing him off. He didn’t say anything to me; he just disappeared.

droftarts

@mac said in I could use some help:

@droftarts what did that change accomplish? Is there something I’m supposed to do now? Would you like me to home the Y-axis to see if it stops at the endstop, then backs off?

When you press them and send M119, they will say ‘at min stop’ now, assuming you restarted. Try homing.

I’m sure Frederick has just been distracted, not annoyed. I’m putting kids to bed, so away for a while.

Ian

@droftarts

The y-axis was set as M574 Y1 S1 P"!^i06.in". So it went towards the front of the printer, and when it got there it pounded on the front of the bed until I turned the printer off.

The end-stop for Y is at the rear of the machine, so, I changed the code to: M574 Y1 S0 P"!^io6.in" to send the bed backwards instead of forwards.

Now I'm going to give it a try, but first, I'm going to M119 the end-stops.

Interesting, Y: no endstop. At the bottom of the Console screen I'm seeing G28 Y Error: Failed to enable endstops.

Why would changing the direction of the bed from moving forwards to an endstop that isn't there to moving backwards to an endstop that is there cause the endstop to disappear?

I'll come back to his later.

fcwilt

@mac said in I could use some help:

@droftarts my apologies to Frederick for pissing him off. He didn’t say anything to me; he just disappeared.

Mac, you did not upset me in the slightest. My wife and I had made plans to go to lunch and the time to leave snuck up on me.

Lunch was grand.

Perhaps that will bring us luck.

Frederick

droftarts

@mac M574 S0 means no endstop. You change axis direction with M569. Again, this was fixed last night, so either you didn’t save it, or you’re using the wrong config.g.

Ian

fcwilt

@mac said in I could use some help:

@droftarts

The y-axis was set as M574 Y1 S1 P"!^i06.in". So it went towards the front of the printer, and when it got there it pounded on the front of the bed until I turned the printer off.

The end-stop for Y is at the rear of the machine, so, I changed the code to: M574 Y1 S0 P"!^io6.in" to send the bed backwards instead of forwards.

Now I'm going to give it a try, but first, I'm going to M119 the end-stops.

Interesting, Y: no endstop. At the bottom of the Console screen I'm seeing G28 Y Error: Failed to enable endstops.

Why would changing the direction of the bed from moving forwards to an endstop that isn't there to moving backwards to an endstop that is there cause the endstop to disappear?

I'll come back to his later.

Mac,

The M574 settings have no effect on the direction of travel. The merely specify the type of endstop (the S parameter ) and the location (the X, Y or Z parameter).

When you changed S1 to S0 you were specifying that there was no endstop on that axis.

S1 specifies a simple switch type endstop - which is what you have.

Change them all to S1.

The direction of travel is controlled, in part, by the settings in M569. Do you change those again. We had them correct, at least for Y.

The direction of homing is controlled by the G1 moves in the homing files.

For the Y axis a negative amount should move the bed backwards.

Example: G91 followed by G1 H1 Y-360

For the Y axis a positive amount should move the bed forwards.

Example: G91 followed by G1 Y+10

Frederick

fcwilt

@mac said in I could use some help:

@fcwilt how do we tell the firmware that 104mm is 0mm / home?

We don't need to worry about that now.

We have more fundamental problems with basic axis behavior.

Frederick

@droftarts @fcwilt

; Endstops
M574 X1 S1 P"!^io5.in"               ; configure switch-type (e.g. microswitch) endstop for high end on X via pin !^io5.in
M574 Y1 S1 P"!^io6.in"		      ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin !^io6.in
M574 Z1 S1 P"!^io2.in"		      ; configure switch-type (e.g. microswitch) endstop for high end on Z via pin !^io2.in
``
Okay, that's fixed?

@fcwilt

; Drives
M569 P0.0 S1                                       ; physical drive 0.0 goes forwards
M569 P0.1 S0                                       ; physical drive 0.1 goes backwards
M569 P0.2 S1                                       ; physical drive 0.2 goes forwards
M569 P0.3 S1                                       ; physical drive 0.3 goes forwards

That is what they are currently. Y is supposed to be going backwards. Does that reverse the jog buttons in DWC?

@fcwilt

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Jun 27 2022 12:50:38 GMT-0700 (Pacific Daylight Time)
G91
G1 H1 Y-360 F3600
G1 Y15
G1 H1 Y-10 F360
 
G90
G1 Y110 F3600 ; this just moves Y to the centerline of the bed - doesn't matter where - it can be any place at all that suits you.

That's what they are currently.

fcwilt

@mac said in I could use some help:

@fcwilt

; Drives
M569 P0.0 S1                                       ; physical drive 0.0 goes forwards
M569 P0.1 S0                                       ; physical drive 0.1 goes backwards
M569 P0.2 S1                                       ; physical drive 0.2 goes forwards
M569 P0.3 S1                                       ; physical drive 0.3 goes forwards

That is what they are currently. Y is supposed to be going backwards. Does that reverse the jog buttons in DWC?

The setting in M569 affects everything that tries to use the stepper.

If the jog buttons move the axis in the right directions than everything else that tries to move the axis will move the axis in the right directions.

You had the Y jog buttons working yesterday but you also had the endstops working yesterday.

As I understand somehow the settings for the endstops got changed.

Perhaps the setting for M569 for the Y axis got changed?

In any case, just use the jog buttons to move Y. If it moves in the wrong directions just change the S parameter in the M596 for Y, save, re-boot and re-test.

Frederick

@fcwilt just so you know, I just tried to HOME Y. The bed went to the FRONT of the printer, and pounded on it.

G91
G1 H1 Y-360 F3600
G1 Y15
G1 H1 Y-10 F360
 
G90
G1 Y110 F3600 ; this just moves Y to the centerline of the bed - doesn't matter where - it can be any place at all that suits you.

This is the code that told Y what to do.

@mac Y is showing it's position as 110.0 It is smashed against the tensioning cap.

fcwilt

@mac said in I could use some help:

@fcwilt just so you know, I just tried to HOME Y. The bed went to the FRONT of the printer, and pounded on it.
G91
G1 H1 Y-360 F3600
G1 Y15
G1 H1 Y-10 F360
 
G90
G1 Y110 F3600 ; this just moves Y to the centerline of the bed - doesn't matter where - it can be any place at all that suits you.
This is the code that told Y what to do.

Well it sounds like the S setting in the M569 for the Y axis has gotten changed to the wrong value again.

Test with jogging and change the S setting as needed so jogging works.

Then try homing Y again.

Frederick