Core One back to head banging with firmware 6.4.0 - any tips?
Hi
My C1 is back to doing a lot of head banging when it's homing the head prior printing. It does 4 slower, then 10 rapid knocks. After an earlier firmware update it got down to just doing a few. The belts are in their happy range for tension and I'm not seeing any print defects or hearing any noises that otherwise have me concerned.
If anything though, 14 knocks is far more head banging than I remember previously.
Aside from the belt tension what other adjustments/settings might be making the homing sequence do this again?
Thanks
RE: Core One back to head banging with firmware 6.4.0 - any tips?
Before we start exploring other potential causes -- are the belt tension and gantry alignment actually ok? Using the new LED-based belt tuning wizard, are the two belt frequencies in the right range? And is the gantry squared at the same time?
When you pull the gantry forward against the end stops (motor power off), it must touch both stops. Try to gently push it against the stop on the left, then on the right, so see whether there is still wiggle room, i.e. a small gap between gantry and end stop. If you don't get "zero wiggle", you will have to straighten the gantry. On the new belt tuning instructions page, follow the Quick gantry alignment guide in the yellow box.
RE: Core One back to head banging with firmware 6.4.0 - any tips?
Before we start exploring other potential causes -- are the belt tension and gantry alignment actually ok? Using the new LED-based belt tuning wizard, are the two belt frequencies in the right range? And is the gantry squared at the same time?
Yes perfectly square, touches both sides with no play, and solidly in the frequency range. No adjustments are recommended by the tuner.
Belt tuning was my go-to but there's nothing to report there. Do we know of anything else causes longer homing?
RE: Core One back to head banging with firmware 6.4.0 - any tips?
For more info I ran the test just now and upper belt is 91.5 and lower is 92Hz
RE: Core One back to head banging with firmware 6.4.0 - any tips?
Ok, looks like the gantry and belts are in good shape!
You could try re-running the Homing Calibration (Control > Calibrations & Tests > 5 Homing Calibration). That one makes a real racket bumping into the stops, but I understand it determines how an end stop hit looks in the Stallguard readouts of the specific printer and stores those values. Maybe that helps to make the routine homing quicker again?
A couple of users have reported that the heater (bed and/or nozzle?) seems to interfere with the XY homing on their Core Ones. To my knowledge, it is not clear where that interference occurs -- maybe via the power supply? But the affected users report that homing with the heaters turned off works more reliably. Unfortunately firmware 6.4.0 no longer lets you do a precise homing without heaters from the menu -- the Control > Auto Homing will only do the quick, less accurate homing. Sending a G28 command while the heaters are off is probably the quickest test?
RE: Core One back to head banging with firmware 6.4.0 - any tips?
Thanks - I forgot there was a calibration for homing to try. It has printing to take care of for the next 6 hours so will jump on that tomorrow and see if it helps.
I also bought a lube kit for the linear rail in case there's a possibility that's adding drag that's upsetting it, but there's no noise and it doesn't feel tight (as much as you'd remember) when moving it with the motors off. Regardless will try that too. It's a shame there's no feedback from the machine as to why it needs to try more knocks when homing.
Truly appreciate your thoughts on this so far. It's always good to get a fresh perspective.
RE: Core One back to head banging with firmware 6.4.0 - any tips?
You could try re-running the Homing Calibration (Control > Calibrations & Tests > 5 Homing Calibration).
That has reduced it by around a half! Also I found in the settings menu something about calibration that was set to ASK that I've moved to AUTO. Haven't found any documentation on that yet, and you'd have thought it might have asked already if that was going to be helpful, but I've changed it anyway. I'm encouraged, but the quest continues...