RE: 6.5.3 Firmware for CORE One/+
Thats fine. It just doesnt have to bang every time.
It should be able to move a tad off of home if it knows it. Say 1/2 inch or so.
Oh, you mean it homes again, even when it already knows the head position from prior homing? I have not noticed that. Loading/unloading filament is typically my first step after I powered on the printer, in which case it needs to home to get its bearings. If the printer re-homes, e.g. when changing filament after a print, that is indeed redundant.
RE: 6.5.3 Firmware for CORE One/+
Thats fine. It just doesnt have to bang every time.
It should be able to move a tad off of home if it knows it. Say 1/2 inch or so.
Oh, you mean it homes again, even when it already knows the head position from prior homing? I have not noticed that. Loading/unloading filament is typically my first step after I powered on the printer, in which case it needs to home to get its bearings. If the printer re-homes, e.g. when changing filament after a print, that is indeed redundant.
I dont have enough time with 6.5.3 to say for sure. But old firmware had to home to do every trivial thing.
Bang. Bang bang. Bang bang bang bang bang
Just glad the print head didnt bash a hole in the side yet.
Vehemently against AI. I've seen that film. It ends badly.
RE: 6.5.3 Firmware for CORE One/+
The stepper motors are either grounded to the CoreXY frame via their mounting screws, or they are not. What other complex grounding scenario would you envision?
I'd say that main problem here is lack of contact bacauseframe is lacked. So when you put the screw in it doesn't make contatct on both party, in this case on frame and motor. That's why scraping paint off helps.
In fact, i did experience a few exactly same problems in my history: excessive paint preventing contact... the long term problem however can become rust at scraped parts if the frame is from common iron...
RE: 6.5.3 Firmware for CORE One/+
The stepper motors are either grounded to the CoreXY frame via their mounting screws, or they are not. What other complex grounding scenario would you envision?
I'd say that main problem here is lack of contact bacauseframe is lacked. So when you put the screw in it doesn't make contatct on both party, in this case on frame and motor. That's why scraping paint off helps.
In fact, i did experience a few exactly same problems in my history: excessive paint preventing contact... the long term problem however can become rust at scraped parts if the frame is from common iron...
Yes, we agree on that. Removing some paint below a screw head, and/or inserting a star washer, are the accepted fix to ensure that the motor mounting screws make electrical contact with the CoreXY frame.
My point was that a scenario where the motors are grounded "indirectly", via a long detour and a ground loop, seems implausible. If the motors are grounded at all, the only path I can see is the direct one, where the motors have direct electrical contact with the CoreXY frame.
So I am not quite sure what Page had measured originally, what he changed afterwards, and which action fixed his problem. Provided that it is indeed fixed and the printer did not just luckily make it through a few prints -- fingers crossed!
RE: 6.5.3 Firmware for CORE One/+
Well, I updated it today to 6.5.3 and so far so good.
That didn't last long. I have had nothing but issues with my printer I have never seen before until today.
I got a black screen of death. I had the rear Z axis all thread just stop, causing the entire bed level to be 30 degrees and error out. (I don't think adding grease to the thread would cause it to bind like this, it only seemed to happen one way and once I get it re-leveled it was fine)
Will probably downgrade back to maybe 6.4.0 just to keep the belt tension.
Vehemently against AI. I've seen that film. It ends badly.
RE: 6.5.3 Firmware for CORE One/+
The rear Z-Axis is connected with the two front Z-axis motors in parralel via a Y-splitter. The printer cannot individually adress each motor individually, only all three at once. This means a software update is very unlikely to cause this problem since this is not even a behaviour they could change at will.
I would say this problem specifically is just coincidence and has nothing to do with the update.
The only plausible explanation: They lowered the stepper current and now that one motor stalls first