I could use some help

A Former User

@fcwilt I'm going to make the change, etc., and will let you know as quickly as I can.

fcwilt

@droftarts thanks for asking, Ian. I'm going to focus all of my attention of meeting Frederick's needs today, as he's hell-bent to get my printer working properly. I feel like I need to support his efforts as best I can.

At some point, I'll make a video about all of this, and put what I've learned about the technology and the coding and the great customer support I've received. Hopefully, I'll be able to use moving pictures to make the points that need to be made.

Mac

I assume you want to get it working as well?

If that is not the case then let me know and we can explore any aspect of your printer you like.

Frederick

droftarts

@mac once the axes are moving correctly, it may help you to draw a picture of the bed. Measure the size of the bed. Move the nozzle to the home X and Y position, touching the endstops. Is the nozzle over the bed, on the edge of the bed, or not over the bed? Measure the offsets. Do the same with the nozzle at the maximum position, measuring the offsets from the bed. You will need these numbers for the M208 commands, to get the printer to know where the printable are of the bed is.

Ian

A Former User

@fcwilt REPORT: the bed started towards the rear of the printer slowly, then moved faster, until it came to where it thought it should stop, and did so.

UPDATE: I decided to move the bed forwards as far as it would go. DWC is telling me that the bed will go to 220mm. According to my metal measuring stick, 220mm is 327mm in the real world.

UPDATE: I thought I was seeing weird behavior. So I moved the bed forwards and backwards to the limits imposed on it by the firmware. A couple of times I hit the endstop and then kept going to pound on the motor a bit. None of this bothers me. I have a box of endstops and a box of motors I can use to repair whatever damage these efforts produce.

The firmware is limiting how far the bed can go forwards to where it thinks 220mm is. It's 220mm is 327mm in the real world.

It's not lightly touching the end-stop, then backing up (forwards) / away from it.

M119 reports that Y is at Max Endstop.

A Former User

@fcwilt "properly" means exactly that.

I'll put it another way: I want this $160+ dollar board to outperform the mystery board in my Xvico. I think my efforts, and everyone's help require that to put the world right again.

Mac

A Former User

@droftarts I understand. And I'm working on developing that image.

A Former User

@fcwilt I just ran M119 for all 3 endstops. When depressed, all of them are reporting that they are at Max Endstop.

fcwilt

@mac said in I could use some help:

@fcwilt REPORT: the bed started towards the rear of the printer slowly, then moved faster, until it came to where it thought it should stop, and did so.

UPDATE: I decided to move the bed forwards as far as it would go. DWC is telling me that the bed will go to 220mm. According to my metal measuring stick, 220mm is 327mm in the real world.

UPDATE: I thought I was seeing weird behavior. So I moved the bed forwards and backwards to the limits imposed on it by the firmware. A couple of times I hit the endstop and then kept going to pound on the motor a bit. None of this bothers me. I have a box of endstops and a box of motors I can use to repair whatever damage these efforts produce.

The firmware is limiting how far the bed can go forwards to where it thinks 220mm is. It's 220mm is 327mm in the real world.

It's not lightly touching the end-stop, then backing up (forwards) / away from it.

M119 reports that Y is at Max Endstop.

I have no idea what is going wrong.

Your testing confirmed the Y jogged in the correct directions.

You testing confirmed that all of the endstops were working.

The Y homing code is very simple.

How about this:

move the bed to roughly the center of it's possible travel
verify the Y endstop is working using M119
if all is good execute G91 then G1 H1 Y-360 F3600

It should move to the endstop and halt. The DWC display should read Y = 0.

Frederick

fcwilt

@mac said in I could use some help:

@fcwilt I just ran M119 for all 3 endstops. When depressed, all of them are reporting that they are at Max Endstop.

Max Endstop?

That's wrong.

What do the current M574 commands look like.

Thanks.

Frederick

A Former User

@fcwilt I put a + on the center of the bed. I also put a l on the left side of the bed. I lined those marks up with 9 inches, which is half of the 18 inches the bed can travel.

I sent the codes.

The bed moved may-be a millimeter to the rear.

A Former User

@fcwilt

; 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

A Former User

@fcwilt M119 is reporting Y not stopped. The bed is forwards of it 60mm.

A Former User

@fcwilt DWC is reporting that when the bed is at the center of it's actual real-world run (228.6mm), it's at 220mm, which is the end of it's run.

A Former User

@fcwilt when I run the bed back to the y-endstop, DWC says the bed is at 104mm.

A Former User

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

A Former User

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

droftarts

@mac said in I could use some help:

@fcwilt

; 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

A Former User

@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

A Former User

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

A Former User

@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