I just saw on Reddit some complains about the now missing ability to downgrade the firmware and that there have been some related issues.
Can anyone tell me what happened?
Funny enough, after upgrading my P1S 2 days ago, I yesterday made a print and had my first ever failure. I printed 10 Keytags on the original BBL gold textured PEI plate with my PETG and one of the Tags started warping - something that had not yet happened since I received the printer in November.
I do think that this was / is just a coincident, but bags the question, what issue have you guys encountered due to updates?
My PIP turned into a BRICK because the filament sensor doesn’t work. I had been printing a lot with the sensor bad. I just had to press resume when the "filament out’ message came up.
Since the last two upgrades I can’t print anything. NOT ANYTHING.
How do I downgrade back to what worked in December?
The filament sensors won’t be available until January 29.
Having major issues ever since the update with my P1S. Mainly print quality after first motor noice calibration. It’s overall more silent but I get strange noises while printing (rasping / rattling sound) and in the front+right of the build-plate things look NOT GOOD.
First layer is a catastrophe now, looks like a resonance or faulty compensation to me. You can even see the head moving irregular, not in a constant pace even though it’s printing a perfectly straight line…
Wow!! That’s actually something to be concerned of. Maybe something similar happened to mine and therefore the print warped. The other seemed to have printed fine though.
There is a new update since yesterday. Have you already tried that?
Yeah I think I am already on the latest (01.05.01.00). It’s printing right now, after it get’s through the first layer it seems somewhat OK. Seems worst on first layer when moving slow and close to the bed.
I’ll check again if there’s a new version after the print finished. Already did a reset this morning and full self check + calibration.
Some of the bad looks on the second image is probably due to poor flow calibration, never did it for that filament. But the white one in the first image is terrible and with a properly calibrated filament.
If this problem persists I’ll raise another ticket for the support. Had already quite some fun with my AMS unit and the infamous “slot 3 filament is stuck” issue…
For a 1000 EUR+ device I must say it has not entirely been the experience I hoped for.
Same thing here, since 01.05.00, the printer is no longer making any good part.
Update to 01.05.01 shows available, but the updating failed, several times.
This is severely crashing the unbelievable good expierience from last 10 days i have this machine in use.
Is there a known solution for getting the update running?
As mentioned, 01.05.01 did nothing for me, same issue and bad prints, warping, and overall problems with what seems resonances coming from the “motor noise compensation”.
Still says 01.05.01 is latest, joined the Beta program but nothing. Downgrading to 01.04.02 now. Hopefully able to print (a bit louder) but more successful again.
To answer your question. Many people have been experiencing networking issues since the update to 1.04 for the P1 series.
Funny thing though, or not so funny. Bambu revoked the ability to restore back prior to 1.04 which was the last LAN-Only stable build. I am furious right now because to me that smells like we are being herded back to online cloud use. More specifically, it seems odd that all these issues popped up when they launched Makerworld and issued the new firmware. Now you can’t go back and you’re stuck with bad connections.
Here is what my findings are with 1.04 and 1.05.
1.05 was the most unstable connectivity for LAN-only mode. Rolling back to 1.04 helped.
FTP using FileZilla was never affected so that tells me it’s solely a firmware issue. When the printer would lose connection, FileZilla and the camera as well as the temp sensors worked fine, only execution of the actual print was affected. Noteworthy is that in 1.05, you weren’t even notified, the job would just quit and the printer would go idle. At least with 1.04, I get an error message. Again this tells me that someone is either not testing their code or is deliberately obfuscating errors to force people off LAN-only mode and back to the cloud where they can dictate control of the end-user’s experience.
Using Send rather than Print and then manually printing it from the folder at the LCD panel also worked. Again, thus proving that they sabotaged the existing protocol because the file was successfully transmitted the printer simply wouldn’t execute the job.
My first layers look the same on my P1S with 01.05.01.00.
I upgraded to 01.05.00.00 via the beta-channel first, had the same problems, did a downgrade to 01.04.02.00 and then the upgrade to 01.05.01.00 which was officially released by then.
Is there a difference between calibrating from App / Bambulab Studio and via the LCD on the printer?
Calibration from bambulab studio after updating to 01.05.01 didn’t do anything for me and I still had crappy prints.
I did the same thing you’re doing. It wasn’t successful in Studio but once I calibrated from the printer itself, everything worked. Hope it works for you too.
When you say “it wasn’t successful” you mean you experienced similar issues as I did and after calibration started from the device itself it went away?
I’ll give it a try then, I’ll report back in a few hours when it’s done and I had the time to test it sufficiently.
@eike there should be no difference weather you perform the calibration from the App or Printer itself as both are downloaded from the same server.
I just recalled during writing that the last calibration I made must have been with Version 01.04.02… As since I was running the earliest 01.05.00 the printer kept on doing the same noise as previous, but started to have problems.
Therefore I upgraded to the latest 01.05.01, performed the calibration, restarted and ran the typically test of a round 0.2 circle.
Though, before calling this the printers fault I rubbed down the plate with 96% alcohol and ran the same print with a different filament to make sure its actually the printer… and not something else…
So for everyone involved, clean the plates you’re using, perform the calibration without touching the printer in any moment, restart and test.
In my case it seems so have been a chain of weird coincidences - nothing to blame Bambu for. Cheers!
PD: Kudos to Bambu for implementing the noise-cancelling (What a difference!!)
PPD: BUT there is one thing I might have to open a ticket for, and that is the lack of BambuStudio to detect that the print is colliding with the purge-line.
It’s just a test, so I don’t care, but would this be a serious print it would quite bother me to have that purge sticking onto my print.
