I started to have really slow file transfers over the network with my P1P after the 01.05 update. Sometimes they would just fail to send. Then after a few days my prints would stop at random points, but the printer said the print was complete, no error. I looked for snags or clogs but found nothing. I changed filaments and the same failed prints with no error, all at different layers with different files.
Today I downgraded to 01.04.02 and my prints transfer faster and reliably and I have no more failed prints. So far this is just correlation but for me, it seems like the 01.05 firmware was causing issues.
Thanks for sharing that data. I can confirm the exact same experience. However, Bambuâs answer differs. Hereâs what they sent to me when I told them that the 1.04 and 1.05 firmware was unstable in Lan Only mode.
Unfortunately, it is currently only possible to roll back to the three versions of 01.04, and it is not possible to roll back to version 01.03.
Furthermore, according to the firmware release notes, the version update did not include any modifications to the LAN only mode functionality. So I would like to learn more details about the issue, such as specific error messages and any other relevant information in my previous email.
In my experience, a firmware upgrade should come with a factory reset (I guess this is not how it should be but thatâs life). I had exactly the same issue as you, but earlier last year on a different firmware.
Bold thing to say since they - Bambu - know what updates are made to the code. Also, support is still trying to help you so no need to publicly try to give them a bad rep.
This is not intended to publicly give them a bad rep my good sir. They are doing this quite well without my help. What I did not share was the number of exchanges before this one that I shared just to get them to respond.
And of course, they presupposed that A) Their tech supports are being told whatâs in the code by engineering, and B) that they are being open and honest. Then why the bug fixes in 1.05 where they stated that âIn rare casesâŚâ. Your statement demonstrates a lack of understanding on how software support actually functions. There is the issue of competence and the secondary issue of transparency of malfunctions. Bambu has demonstrated neither competence or transparency.
Unless you have a counter argument or evidence to the contrary, you are making a leap of faith to back up your statement of âBambu Knowsâ.
There are words, and then their is empirical evidence. What evidence do you have to the contrary? The evidence I have is gathered from a control group consisting of ongoing testing of one environment and then changing one variable in that environment, that variable being the version of the firmware.
So if I had a stable LAN-only connection in 1.04 and continually failed connections in 1.05 and rolling back to 1.04 made for more stable connectivity, what proof is there that this is NOT a faulty release? Oh wait a minute, I should just look at the logs they requested⌠oh but wait⌠I canât look at those either because they are encrypted on the device⌠hmmmm⌠what might they be hiding in those logs that they feel the user shouldnât be seeing? This speaks volumes to the lack of transparency and the implied untrustworthiness of the replies and avoidance.
Despite their offer of help, I believe it to be a wasted effort, as in my experience, past performance by Bambu has proven futile. This offer to examine my encrypted logs is merely an attempt to pander or placate, merely giving the appearance of âbeing helpful.â
Oh yes, I am making a leap of faith. Although technically âbambu knowsâ is true, I do get what youâre coming from though and I donât know everything about the issue youâre facing with Bambu. I was just triggered by the, in my opinion, blunt statement you made which made me reply.
That being said, I had issues with 1.05 myself and rolled back to 1.04. So, I agree that it seems like a faulty release. I didnât try to take a look at the logs so didnât know theyâre encrypted. Good to know.
most users dont have issues with the firmware releases. it is hard to pinpoint what exactly is the cause in a given case. Me personally never had a single issue on all the firmware updates on P1 series.
my issue is that I upgraded to the new 1.05.02.00 firmware, and now, when I send a print to the printer. the light comes on by its self. and when the print stops, the printer fan eventually shuts off, the printer eventually goes to sleep, but the light stays on.
I googled how to rollback the firmware because I couldnât find it searching the forum. iâm going to try to roll it back to the previous verison, and see if that fixes it.
I downgraded firmware also due to prints not sticking no matter the bed, temps ect. I found the part fan inop. unable to override it to get it to work. Reverted to 01.04.00.00 and part fan works correctly.
This behavior that you observed was part of my contention that 1.05 was unstable.
In case anyone else can report there experience, Iâll start a running list of what I observed in 1.05
Sending a print job often would result in a âprinter not foundâ forcing a manual reconnect. This connection failure was roughly about 30% of the time. While not scientific, I was marking on a sticky note the number of times I issued a print command and had to reissue it which is how I arrived at the 30% failure rate.
This failure mode made unattended print an impossibility.
Even though I lost connection in LAN-only mode, my FTP connection never faultered. I was also able to ping the IP address and my router reported the presence of the printer on my LAN.
This is proof that the problem is in the handshake between the Studio app and the printer.
As stated above, when a download was confirmed and the printer commenced homing, 30% of the time, it would just stop midway through and when I went to the P1P console, it would just say âready to printâ. In other words, the printer reset itself with no issuance of an error message.
As stated, rolling back to 1.04 helped the issue significantly but roughly 5% of the time, I would have to re-send a print to the printer. Note: This was often the case when I was printing something twice in a row where letâs say I was changing a single parameter such as layer height or temperature.
One way to disprove that this is a firmware issue would have been to allow me to roll back to the previous known stable condition. However, Bambu blocked such attempts and denied any problems.
SO, after some more time living in 1.4 I get the same failed prints with no error messages. The extruder just moves in the air and then Print Complete! But sending to the printer over network is better than in 1.5.
I looked into where filament could be snagged in the AMS, but it happens on the external spool too. I can even just restart a print right away and filament flows fine. I started to look at the tool head and the TH cable and saw it wasnât sitting in the cable molding and one of the wires was pinched and a little frayed, not enough to cause issues though, idk. This has been like this since day 1 from the factory and maybe just started to fail, Again, with no codes being thrown I have no idea what to do. Also, CS has no idea so Iâm not counting on them to help with this.
I replaced it with the upgraded Tool Head cable you use with the chain. I never installed so it was nice to have a backup, lol. It seems to be working fine again⌠for now.
FML, I just wish that I could get an error code from this printer so I can fix the problem that has been dragging on for months.
