Since the new frimware update, this issue has started with the bed trying to go lower with no room left to do so. Prints themselves are fine but the buildplate bottoms out when starting the next print. Anyone else having this issue?
Same here. Even though nothing has changed in the end gcode.
I jumped a few times because of it. But it only happened to me when I had „tall“ prints, maybe after 13cm built height it starts.
Now thats interesting to see this. I didnt know what it was but at the start of a new print mine has just started to make a grinding noise so this sounds very likely it. I thought might have put the build place on wrong
This is not new behavior. It happens when the previous print leaves the bed very low - part of the print initialization process sends it even lower. I’ve seen this ever since I got my X1C in December.
It’s odd because the printer ought to know the Z level if it has not been shut off. But no harm seems to be done.
Thanks for confirming this isn’t a new issue. I guess I havent printed anything tall enough before the last firmware update. Maybe they’ll fix this in the next one…
Yeah good to know thats its not something new igm guess… i also have only just used if for a couple of tall prints so will see if its that next time cheers.
Hi, I had this issue too. Tried to change end gcode but it’s complicated. To quick resolve this ( if the bed is max down position) just lift up Z 3 times before start next print.
That’s what I do too. The printer will complain that you should Home first, but just dismiss it.
If it is any comfort. I’ve read that they’ve lowered the voltage when it does that move so it shouldn’t damage anything.
I still prevent it from happening though, I just can’t stand the sound
In my opinion, the software should check first with a laser if the bed is not too high and not lower it blindly. Maybe is in start gcode option to that.
I don’t think the lidar has the range to do that. (Also, not all models have the lidar.)
They could, I think, use current sensing the way that X/Y homing works. I’ve noticed the “grinding” in the Y direction if the head is over the poop chute when it starts up (there’s a reason it relocates to over the bed tab,)
Wouldn’t it be easier just to remember the Z position of the last printjob (when it didn’t turn off or got other commands after?)
That would certainly help.
I don’t think the lidar has the range to do that. Yes, but information You need is only that bed is in range! If not it’s okey You don’t have to lower bed.
I am having the same issue. I did suspect it was the bed and then the Y Axis. It almost sounds like a belt slipping or the stepper driver skipping. I do not recall this happening when I first received my printer near the end of February. Is it trying to do sensorless homing? It sounds bad to me. As long as it doesn’t hurt the machine I am ok. I would a firmware update will come out and resolve. I will raise the bed for now.
If the purpose of this movement is to avoid the nozzle, then it should move UP while watching the piezo sensors in the bed and then move slightly down.
It’s another example of the machine-specific g-code being a complete mess to be honest. It does so many unnecessary and useless steps it’s astonishing.
Still hoping someone is going to refactor/fix it (preferably BL).
Same problem still in October 23 with this issue which also affects P1 series printers. BUMP