So I did this with the a1 mini, I edited the machine G code start to not do the vibration compensation. I want to do the same with my new p2s, but I wanted to ask if i’m editing the correct parameters.
I will admit on the p2s the quick test is a lot faster and less noisy than the A1 ( I live on the top floor of an apartment, dont’ like loose screws and waking my neighbors)
I must admit, i’ve only ever owned one other core xy machine, and it was much slower than this (qidi x plus original) but this p2s is freaking loud man. At least double the noise of the a1. Not only the vibrations but just the motor noises and the pre print proceedure mashing over that filament cutter bar is loud.
Shoot… I was hoping one of you guys would chime in! Thats alright, i’ll contact bambu I guess.
Haven’t been 3d printing long enough to feel comfortable editing G code and knowing if its going to cause a catastrophic problem or not… had my taste of that already accidently loading a file manually from a machine with a different bed size… wasn’t great.
Personally, I do not mind the noise or the time it takes for the machine to calibrate itself before it starts printing.
I do not think the P2S is that loud (except when it is homing the toolhead and triggers the filament cutter 100 times) when compared to other printers like the Core One.
I’m going to link you into this thread. I have 0 GCode experience, but I think there may be useful info in here for you to look at. The vibration comp code is called out in a section. How one would use it is up to you to figure out. P2S starts after 1.5 minutes POST 22
