I could use some help
-
@fcwilt they appear to be consistent.
-
@fcwilt okay, I did a test. I clicked on Y-50 twice. That took the rear of the bed to the endstop (it hit it, versus touching it and backing away).
-
@mac said in I could use some help:
@fcwilt I have an American tape measure going from the front of the printer to the back rail, where it's hooked on to the back rail. What I'm doing is bringing the adjustment wheel for the left corner of the bed to 10 inches. I just watched the bed move from 10 inches to 12 inches twice. So the bed travelled back and forth 51mm twice.
I don't care about homing Y right now because we know it is not working.
I need to be sure that Y movements done via jogging are now moving the correct distances.
Once that is assured the next step will be to determine if the current min/max limits for the Y axis are correct.
Why? Because I based my Y homing code on them. If they are wrong the homing code is wrong and will not work.
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
@mac said in I could use some help:
@fcwilt they appear to be consistent.
What appear to be consistent?
-
@fcwilt I'm looking at the Status window? Y is currently at 34.5.
-
@fcwilt I just moved the bed FORWARDS. Y is now at 124.5.
-
@mac said in I could use some help:
@fcwilt okay, I did a test. I clicked on Y-50 twice. That took the rear of the bed to the endstop (it hit it, versus touching it and backing away).
Where did the test start from? The fact that -100 took the rear of the bed to the endstop tells us nothing without knowing where the bed started from.
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
@mac said in I could use some help:
@fcwilt I'm looking at the Status window? Y is currently at 34.5.
You cannot trust those numbers until you are absolutely sure the 100 is the correct value for Y in M92.
If M92 values are off everything the printer "says" and does will be off.
Frederick
-
@fcwilt okay, here's something, I moved the Y-axis as far forwards as it would go. Status is saying I'm at 220.00.
The nozzle is 59 mm in front of the rear of the bed. So, for the nozzle to be at the back of the bed, the front of the bed has to go another 59mm. At which point Status should say Y is at 279.0.
-
@fcwilt I understand what you're saying about how the numbers have to be exact. Being close would be a good beginning to that journey, I think.
-
@fcwilt I just moved the nozzle to where I'd like the front of the bed to be. Status is reporting 62.0. I moved the bed as far forwards as it would go. I'm at 220.0 according to status, but I have another 59mm to go.
-
@fcwilt im sorry this is so frustrating. For me as well. But based on what we’ve learned, I’m starting to see the problem spatially. So that’s helpful, to me, at least.
-
@mac said in I could use some help:
@fcwilt okay, here's something, I moved the Y-axis as far forwards as it would go. Status is saying I'm at 220.00.
The nozzle is 59 mm in front of the rear of the bed. So, for the nozzle to be at the back of the bed, the front of the bed has to go another 59mm. At which point Status should say Y is at 279.0.
Yes, one of the things I am trying to determine is if the M208 values you are using are correct.
As I mentioned if they are off then my homing code is off and will not work.
Here is what needs to be done.
- double or triple check that jogging Y by a specified distance moves that distance when measured with a ruler. You cannot use the readout from the DWC.
- once you are absolutely sure you can use the Y jog buttons to move known amounts we can then determine the max travel on the Y axis.
- once we know that we can determine if the M208 values for the Y axis are correct.
To use jogging of Y to measure the max travel of Y is simple:
- execute M564 H0 S0 (from the DWC console is fine) so you can jog the entire axis without being limited by the current M208 limits
- jog the bed as far back as possible
- execute G92 Y0
- jog the bed as far forward as possible
- read the current Y position as displayed by the DWC
Report the results. Fingers crossed again.
Frederick
-
@mac said in I could use some help:
@fcwilt im sorry this is so frustrating. For me as well. But based on what we’ve learned, I’m starting to see the problem spatially. So that’s helpful, to me, at least.
It can be tricky and sometimes it is hard to wrap your head around all the interacting bits.
IF I was sitting with you at the computer this whole thing would have been finished in about an hour. But having to communicate back and forth slows things down.
But we are getting closer.
Frederick
-
@fcwilt yes, I agree, we are. I’ll use a metal ruler I have. It hasn’t changed in 70 years.
-
@mac said in I could use some help:
@fcwilt yes, I agree, we are. I’ll use a metal ruler I have. It hasn’t changed in 70 years.
DRAT and DOUBLE DRAT.
I posted M92 when it should have been G92.
DO NOT ENTER M92 Y0.
IF you do just re-boot the machine and be sure and use G92 and the specified point in the process.
Frederick
-
@fcwilt sorry? are you saying that the changes I made to Y were supposed to be in another line?
-
@fcwilt where's this G92?
-
@mac said in I could use some help:
@fcwilt sorry? are you saying that the changes I made to Y were supposed to be in another line?
This part here:
To use jogging of Y to measure the max travel of Y is simple:
- execute M564 H0 S0 (from the DWC console is fine) so you can jog the entire axis without being limited by the current M208 limits
- jog the bed as far back as possible
- execute G92 Y0
- jog the bed as far forward as possible
- read the current Y position as displayed by the DWCThe G92 above was original posted as M92 which was wrong, wrong, wrong and would have messed up the entire process.
I have corrected the original post and re-posted it here.
As long as you have not started this process listed above all is good.
Frederick
-
@fcwilt I haven't even started measuring again. I did turn the printer off so I could move the bed back to the end-stop. I'd like to use that 0-point to measure from. But getting to it is brutal!
