I could use some help

A Former User

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

A Former User

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

A Former User

@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

A Former User

@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

A Former User

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

A Former User

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

A Former User

@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

A Former User

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

A Former User

@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

A Former User

@fcwilt

M569 P0.1 S0                                       ; physical drive 0.1 goes backwards

This is what's in the config.g. This makes the jog buttons work correctly.

fcwilt

@mac said in I could use some help:

@fcwilt
M569 P0.1 S0                                       ; physical drive 0.1 goes backwards
This is what's in the config.g. This makes the jog buttons work correctly.

So a minus Y jog move makes the bed move backwards. Correct?

Frederick

A Former User

@fcwilt yes, clicking on the jog buttons make them do what they're supposed to do. When you click on < Y-10 the bed goes towards the rear of the printer. When you click on Y+10> the bed goes towards the front of the printer.

However, when the bed gets to what it thinks is 220, it stops.

Shite! I was clicking on the jog buttons. I looked at the Status Display. I was expecting to see Y at almost 220.

Right now the bed is 5/8th of an inch closer to the front of the printer than the back of the printer. And Y in the DWC Status Display reports 0.0.

I moved the bed forwards 3 more times. The display is reporting Y at 80. now

Okay, I told the bed to go back to the rear -50, then -50 again. The bed stopped when Y in the display reached 0.0. So it didn't go the full 50mm the second time, because it can't go into negative territory.

So this tells me why the bed pounded on the front adjustment. It's trying to get to 220, which is about ten inches forwards of the front of the printer.

Where is this coming from? What codes are providing this information to the printer?????

fcwilt

@mac said in I could use some help:

@fcwilt yes, clicking on the jog buttons make them do what they're supposed to do. When you click on < Y-10 the bed goes towards the rear of the printer. When you click on Y+10> the bed goes towards the front of the printer.

However, when the bed gets to what it thinks is 220, it stops.

Shite! I was clicking on the jog buttons. I looked at the Status Display. I was expecting to see Y at almost 220.

Right now the bed is 5/8th of an inch closer to the front of the printer than the back of the printer. And Y in the DWC Status Display reports 0.0.

I moved the bed forwards 3 more times. The display is reporting Y at 80. now

Okay, I told the bed to go back to the rear -50, then -50 again. The bed stopped when Y in the display reached 0.0. So it didn't go the full 50mm the second time, because it can't go into negative territory.

So this tells me why the bed pounded on the front adjustment. It's trying to get to 220, which is about ten inches forwards of the front of the printer.

Where is this coming from? What codes are providing this information to the printer?????

It is the homing code that syncs up the physical position of the bed with the logical position.

At the start of the homing code let's assume the firmware has no idea where the bed is.

So the homing code should start moving the bed backwards until it triggers the endstop.

Since the firmware (in theory) knows where the endstop is it now knows where the bed is.

Jogging, even when homing has failed, is going to limit moves, as displayed in the DWC, to the range of 0 to 220, regardless of where the bed actually is.

So the question is, since the jog buttons are working, why isn't the homing work.

Let's try clicking the Home Y button again, please.

It should:

move back at a medium speed until it triggers the endstop and stop briefly
move away from the endstop by 15mm
move back at a slow speed until it triggers the endstop and stop briefly
move away from the endstop until the bed is more or less in the middle of it's travel and stop
the DWC should be displaying 110

Thanks.

Frederick