The P1S moves to the front left corner of the plate, the gray 2x3 square area in bambu studio, but with PETG this is not helpful and can end up rarely dropping the purge onto the plate (when it gets to the purge area and purges, effectively purging onto the plate) because of the rigid nature of the ooze that can occur here.
It also results in additional travel which with oozy PETG at 250 can easily result in marking or blobs.
It would be much better if it skipped this and went directly to the purge slot.
It may not be a feature to disable this, but the cutter isn’t there, it is in the head, there’s no reason it can’t cut it over the purge gutter is there?
Is it possibly because it wants the bowden at max extension at that moment?
*Oh I guess it is there. I didn’t see it before. Oh well.
LOL The answer my friend is in the wind…
Nice song and it nicely reflects on how Bambu works.
The P1 series does a lot of things that make no sense, not just these corner moves.
By the way: those are for checking what build build plate is installed.
Some other things that just keep happening for no reason at all things related to the Lidar sensor…
In short:
Bambu uses the same firmware on our P1 series that is used on the X1.
But rather than properly cleaning it out they just disabled the firmware response.
Meaning all the things the X1 does by default our P1’s do as well, but they won’t produce an error or correction factor.
All big manufacturers do this when they use one mainboard across multiple devices with different hard- or software features.
Problem is that none of those devices, like phones, laptops, TV’s or such come with MOVING parts or mechanical gadgets.
If you check the G-code for a P1, P1S and X1 for the same model, sliced with the same default settings you will find a tons of code that ONLY really works on the X1 while it is junk that wastes time on the other printers.
The P series and X series use entirely different chipsets which require different code base. So no, it’s not the same firmware.
The gcode generated by Bambu Studio for the P series does have some unneeded carry over code from the X series. You can remove it by editing the start/end gcode added by Bambu Studio.
I installed the latest updates and it seems many of these unwanted moves and additions are finally gone.
Have not checked in all detail but things go now in a more logical way.
Maybe I was not THAT correct to blame the firmware - I used the term as it seemed the easiest for everyone to relate to.
What I meant was the machine specific implementation through Bambu studio, based on their defaults.
As most of it relates to non existing hardware it is a matter of firmware consideration in the software but not the firmware itself.