Upgraded to the newest Firmware (01.07.00) and still have the bug / issue with Skipping Objects on my X1C Steps to recreate:
Add 2 models to Buildplate
Color them with two different filaments
Change the Print-order to “by object” so they print one after the other.
Start the Print
When first object is printing, hit “skip object” and skip the current printing object.
Issue
The Second object will be printed with the same color.
The Colorswitch From Filament A to Filament B is tied to the object being skipped - thus it completely destroys the ability to skip objects when Printing by Object instead of Layer.
Expected Behavior
When skipping an object while printing “per object” the printer should cancel the current print and still change filament according to the next object being printed.
Thanks. I’m not sure how I managed to miss what must clearly be several update notices. Maybe my habit of simply switching it on in the morning then immediately turning to my computer and squirting a sliced file at it without looking at the display. Updating now …
I think that was a concerning move in the wrong direction though. Obviously we have a target chamber temperature, heater or not. For PLA, it should be used for avoiding fan noise, ranging from no fan at all and all the way to 100% if/when needed. For things like ABS it could be used to wait until chamber is up to some fair temperature (just from the bed heater) before starting the print, avoiding warping.
That’s why I bought the Qidi XMAX3. Heat the chamber up to 65c, heat the bed up to 115c. I have printed a 300x300x15 plate. It did not warp. It took almost 2 hours to cool off before i removed the print. Its print speeds are about 90% of the BL printer.
I’m liking a lot. It’s got its little problems but they all do.
I create a new custom filament. When i trying to do either Flow Rate or Dynamic calibrations the spot the new filament is in comes up as incompatible. You have to use the drop down and pick the correct new filament then it will calibrate.
Had this issue with multi AMS units. It insisted that one was “A” unit the other “B” unit and this was not changeable. It decided and that was that, even when wires were switched. So I had to make sure I specified if I was directing Slot “A1” or “B1” or so on. When I did this, I did not have this problem anymore. This PARTICULAR problem that is! I have routinely strange random issues. That I think are being kicked out through the slicer and “Their” cloud slicer!!! I DO keep catching issues there with changes I did not make and am not being allowed to correct. They seem to be more interested in “Control” than fixing issues and keeping those fixes. I think this is “Big brother” over Bambu ■■■■. But who knows. At any rate it will lead to no good for Bambu if it continues. And that would be sad.
I upgraded firmware toay to 1.8.2.56 and all of a sudden, my prints are horrible. I made no changes other than the firmware. Can I go back to the previous firmware (for windows)?
Not sure what Bambu did with the software they just released, but it messed up every single print I tried. As soon s I reverted back to the previous version, everything is perfect once again!
I have a P1S and have noticed it has a tendency to crash the Z axis on the bottom of the machine. This can happen for numerous reasons. It happened when I first set the machine up out of the box (not sure what conditions caused this). The problem is that many actions make the bed move down when the machine does not know the current Z position. Even before a simple home action it moves the bed down which can crash.
One way to easily recreate this issue is to continuously start a print then cancel it. The bed will move lower and lower until finally when you start a print it will crash multiple times before homing. Another way is to print something very tall then on the next print, crash.
A workaround is before starting a print to manually move the bed up if it’s close to the bottom. Generally other machines have protections against this kind of stuff when Z position is unknown.
Received my A1 Combo today and run all setup and init sequences and checked for new FW - without success on the machine, whereby the WIKI is telling me there’s a new one available…
Okay, fixes the Problem: hat Connected the printer to my account and the update was successfully completed. BUT: THIS IS VERY BAD SYSTEM & SOFTWARE DESIGN!!! have my Prusa clone running for more than 1 year now, connected to a fake PrisaLink instance without any issue - so not all “new habits” are good - sometimes you should learn from the old guys…
Problem: Filament tangle detector is trigged by tighly wound fillament Firmware Version: 01.01.01.00 Printer: Bambu Lab A1 combo Steps to reproduce:
Turn on “Fillament tangle detector”
Loadfilament that is tighly wound to AMS lite
Trigger print job
Log file: I couldn’t figure out a way to obtain error logs from A1 printer.
Other information:
Once I disable the Fillament tangle detector, print continues and finishes without any issues. Multiple STL were tried with same results.
It would be great if there was option to set sensibility of the fillament tangle detector.
