copying your code didn’t work for me (maybe can’t have the auto-level ticked with your code?. I commented out mech mode only copying yours and it worked, though I also unticked ABL
Awesome stuff, It would be great to get one for the End Gcode with one that doesn’t turn off the bed but instead lowers it to 45 (I print really regularly) and one that does turn it off.
But the main one is just that the printer retracts the bed before finishing,Like, Just let me get my god damn print while you do that stuff the in the background you dang A1 Mini!!!
Hello everyone.
I have an A1 machine, and I would like to use this G-code as well. But I guess it won’t work since the bed size is larger than that of the A1 Mini machine.
If anyone has a modified version for the A1, could you share it? Thanks!
I have changed the start g code myself to just skip vibration checking. Works fine for me. On A1 (not mini) v1.04 firmware. All other functions seem to be working fine like bed temperature, auto bed leveling.
Where in gcode did you modify to skip the vibration bit?
From here:
To here:
I didn’t delete anything, just use a semicolon to edit it out from running
This is orcaslicer, not sure if it appears the same way in bambu studio.
I think it’s not so much of expansion that is the issue, but more like the warping.
At least I have seen this with an other brand of 3D printer where I would level the bed at temperature instead of during and that helped. Warping was happening because the buildplate was under stress (like rails roads would ben in sunlight in the old times, hope I made myself clear…)
Now, it does ofcourse how the build plate is attached, if it’s correctly done, then it should not warp… again, for the Bambulabs I never cared to look at that.
I wish the repy to post worked better here, like it would show what you are replying to.
Instead of randomly scrolling to see what the person replied to.
Just click the name in the top right corner of the post and it will show the post that they are replying to.
Then if you click “Jump to post” it will take you to where in the thread the post is.
1 Like
Nice job, I will try this start G-code. How should I run the vibration test now?
I saved it for my A1 as a seperate printer profile, and run a print with the “normal” one every 50-100 hours.
2 Likes
sorry if i’m being ignorant, but is this still viable today, with the 2 release?
I want to try it to shave off some print start time, but I’m worried its going to cause some kind of issue.
Thanks!
I doubt the Bambu Studio v2 is going to have any really effect on this… this is machine start code after all. Compare the v1 stock code with the v2 stock code and see if there is any difference - if there is, you can work backwards from that.
1 Like
I realized that I entered the g-code into the filament startup g-code, and that there’s also a machine g-code area, so would Like to know which area to paste the gcode. When I entered the code into the filament startup g-code, the normal startup occurred, and then the modified start up occurred.
or you could just run the vibration calibration instead? maybe since I don’t print everyday that seems viable to me, but that is what I do.
1 Like
you have to paste the g-code into the machines startup profile, not the filament profile
Yeah, you want the machine start code since this is machine, not filament, specific 
I’m not sure it serves the same purpose here, as the reason to run it during print startup is primarily to check if the belts are loose, and throw a HMS prompt up if there is an issue. The startup check version is also a lot faster than the full vibration compensation run.