Avisos
Vaciar todo

Y axis length failure  

  RSS
Grandpa-G
(@grandpa-g)
Active Member
Y axis length failure

I know this has been talked about ad naseum, but I have done everything possible and have contacted support. I may have to send the unit back but I want to try to avoid doing that.

I just reload the firmware and then also looked at the output of the Arduino that runs the printer. I wondered if there is any clue in the output that might help me fix the unit rather than sending it back. Here is the output. Can anyone help?

echo: 3.11.0-4955
echo: Last Updated: Apr  7 2022 11:09:51 | Author: (none, default config)
Compiled: Apr  7 2022
echo: Free Memory: 2066  PlannerBufferBytes: 1760
echo:Hardcoded Default Settings Loaded
adc_init
Extruder fan type: NOCTUA
CrashDetect ENABLED!
08:01:50.446 -> FSensor ENABLED (sensor board revision: 0.4 or newer)
08:01:50.923 -> Sending 0xFF
08:01:51.025 -> echo:SD card ok
08:01:52.895 -> LCD status changed
08:02:11.626 -> tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x00
08:02:11.626 -> tmc2130_home_enter(axes_mask=0x04)
08:02:12.068 -> tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x04
08:02:12.102 -> tmc2130_home_enter(axes_mask=0x01)
08:02:17.958 -> X AXIS SG1=252
08:02:17.958 -> MMU not responding - DISABLED
08:02:17.992 -> echo:busy: processing
08:02:19.961 -> echo:busy: processing
08:02:21.964 -> echo:busy: processing
08:02:23.596 -> tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x01
08:02:23.698 -> Measured axis length:251.090
08:02:23.698 -> Measured axis length:251.730
08:02:23.698 -> Axis length difference:0.640
08:02:23.970 -> tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x00
08:02:23.970 -> tmc2130_home_enter(axes_mask=0x02)
08:02:24.038 -> echo:busy: processing
08:02:28.759 -> Y AXIS SG1=273
08:02:28.759 -> echo:busy: processing
08:02:30.763 -> echo:busy: processing
08:02:32.769 -> echo:busy: processing
08:02:33.381 -> tmc2130_home_exit tmc2130_sg_homing_axes_mask=0x02
08:02:33.483 -> Measured axis length:206.930
08:02:34.775 -> echo:busy: processing
08:02:36.813 -> echo:busy: processing

Best Answer by Diem:

That just tells you that the Y axis is shorter than expected..

Check the cable bundle is not hitting a wall at the rear.

Check the Y belt is free to move (with power off move it by hand, is it smooth? Does it reach both limits?)

Clean and lubricate the smooth rods.

Check the belt tension, check the Y idler is free to move and not clogged with filament debris.

Let us know how you get on.

Cheerio,

Respondido : 03/12/2022 3:11 pm
Diem
 Diem
(@diem)
Illustrious Member

That just tells you that the Y axis is shorter than expected..

Check the cable bundle is not hitting a wall at the rear.

Check the Y belt is free to move (with power off move it by hand, is it smooth? Does it reach both limits?)

Clean and lubricate the smooth rods.

Check the belt tension, check the Y idler is free to move and not clogged with filament debris.

Let us know how you get on.

Cheerio,

Respondido : 03/12/2022 3:34 pm
Grandpa-G
(@grandpa-g)
Active Member
Topic starter answered:
RE: Y axis length failure

What number should it be and what are the units, mm?

Respondido : 03/12/2022 3:40 pm
Grandpa-G
(@grandpa-g)
Active Member
Topic starter answered:
RE: Y axis length failure

I think your answer was the clue.

I make a camera mount that connects at the side of the y axis frame. Apparently it had moved or changed its position over time and was interfering with the stop limit of the Y bed movement to the front. I took it off and it passed belt test. Self test is no passing all the X Y Z position tests.

I can't thank you enough for the clue.

Respondido : 03/12/2022 3:47 pm
Compartir: