P1P Unreliable Since Latest Firmware Update

Bambu Lab P1 Series
1

I don’t know if anyone else is having these issues, but since this latest firmware update the P1P has changeable qualities at best.

We run a print to order operation in the UK and have 8 P1Ps and 2 CX1s. Since the update we’re lucky if we can send a job to the P1Ps through the cloud, and when we do we have dragged layers and spaghetti on 50% of them. We’ve changed nothing to trigger this, but to try and fix it we’ve checked the nozzles and carried out cold pulls to see if that’s the issue and no change, we’ve also had to try a re calibration. The biggest PITA is that the next time we send a print if we’ve changed nothing at all, all is well.

Frustrating, we’ve fired up the Prusas to take the strain from the wasted prints.

If anyone from Bambu is looking at this. Please stress and beta test your firmware updates properly before releasing them. Some of us run these things 24/7 as a tool and not a hobby.

5 Likes
2

I have noticed something similar.
0.6mm nozzle

Can you still calibrate the K factor?
I can no longer get any line on the bed.

The strange thing is that old print jobs that I still had in the history can be printed perfectly.

I always get a 3mm seam.
very ingenious.

@ Bambu?
how do you do a FW downgrade?

1 Like
3

Do you mean a layer shift? I do have the 1st layer as expected but the rest is shifted around 5mm to right and front area of the bed.

In BambuStudio 1.4 and 1.5(beta) as well :face_with_monocle:
May need to give it a try via microSD :laughing: Could be a cloud issue right now… or firmware related when unzipping the 3mf file.

Looks like here for me:

IMG_2104
IMG_21041920×3413 932 KB

1 Like
4

I have the similar issue with the recent P1P upgrade. It is NO good for me. I can hardly get any print through the cloud services. I have rebooted my router, P1P several times and still same issue with timeouts etc. How do I roll back to the previous version?

5

Hello, same problem with the latest firmware update (P1P 01.02.01.00) 90% of the time the printer is not able to download the file to start printing.
At first I thought it was a problem in the Bambulab cloud, or in my internet connection, now it’s clear to me that the problem is in the WI-FI communication.
This latest update leaves the WI-FI unusable, I have the printer 2 meters from the router, my laptop is also 2 meters from the router, I ping the printer’s IP and the latency and losses are insane, in this state it doesn’t make sense manage anything by the bambulab cloud or by FTP, since Filezilla connects and disconnects to the printer intermittently.

If any Bambu engineer wants to connect via ssh to my printer or needs me to provide remote access, contact me, something leaves the printer with the CPU at full throttle or causes instability in the OS, or the drivers of the wifi module, some error in security implementation, etc.

In summary, put your printer and laptop 2 meters from the router, ping it and if you lose packets and have high latency, cross your fingers so that they release a new firmware and while using the SD to print, since WI-FI is not possible to communicate decently with the printer.

I did a factory reset to the printer, more calibration, more restart of my router, after this no ping is lost and the latency is 1-2 ms, sustained and completely stable, a couple of reboots later the problem returned.
I have several WI-FI devices at home and they all respond to ping with 1-2 ms and 0 packet loss except the printer, it is clear that the WI-FI of this printer does not work well with the latest firmware.
I read that logging out from the printer and logging back in can solve the problem, I’ll try it and comment later.

Another thing that I noticed is that my router detects the MAC of the printer and it does not correspond 100% with the MAC that the printer shows on its screen.

MAC of the printer that my router sees: F4:12:FA:D2:EA:00
MAC of the printer displayed on its LCD screen 00:12:FA:D2:EA:00

Tiempo de espera agotado para esta solicitud.
Tiempo de espera agotado para esta solicitud.
Tiempo de espera agotado para esta solicitud.
Respuesta desde 192.168.0.24: bytes=32 tiempo=559ms TTL=254
Tiempo de espera agotado para esta solicitud.
Tiempo de espera agotado para esta solicitud.

Estadísticas de ping para 192.168.0.24:
Paquetes: enviados = 1958, recibidos = 1599, perdidos = 359
(18% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 1ms, Máximo = 3424ms, Media = 329ms
Control-C
^C
C:\Users\conta>

2 Likes
6

I know i’m not being helpfull here, but i thank everything alive at this moment in time that i did not upgrade the firmware on my printer, even though the new features are on my wishlist.
So, for now all I can confirm is: My printer does not experience any of these issues listed above on a lower firmware version.

And as a late hint for @Badger_3D perhaps next time update 1 or 2 printers in a production envoirement and test the before updating all.

7

I had the same issue with the cloud and sending the programm to the printer.
I have read that these problems had occured as well in the past after firmware updates.
The soloution, in some cases, was to reconnect the printer with the Bambulab Account. After this my 3 printer works with the cloud again.

But after the firmware update to P1P 01.02.01.00 i have extreme problems with ghostings in my surfaces. Don’t know where it come from. Still trying to find a soloution here…

1 Like
8

Yup, we wouldn’t normally. Just a moment of weakness at 2:00am and fed up of having to remove the reminder from the screens. It shall not be happening again.

1 Like
9

We can still calibrate, but it makes little difference. I’m 99% sure it’s the printer applying a different z offset. We get better prints off stored gcodes, but nowhere near as good as they were.

1 Like
10

Not sure if this is fine. I would redirect to this thread as well: layer-shift-after-first-layer-with-pics

My upper noted “layer shift” / Z-axis shift is isolated to a P1P problem with PTFE tube and toolhead cable! It blocked the movement at rear right corner. Maybe a possible solution for you guys? In my case it seems to be not a cloud / firmware issue.

1 Like
11

Hello, I can confirm that:
Closing session from the printer and logging in again, it solves the WI-FI communication problems and therefore all my problems to download the gcode from the bambulab cloud, hopefully they will release a firmware version soon that will solve this bug and be more proactive when communicating or offering WA (workaround).
Regarding the print quality with the new firmware, I have to carry out more tests, I notice a slight decrease in quality, but everything is very subjective, I touch too many parameters in bamboo studio and different filaments, I will comment in a few days if I notice something else concrete.

Respuesta desde 192.168.0.24: bytes=32 tiempo=3ms TTL=254
Respuesta desde 192.168.0.24: bytes=32 tiempo=2ms TTL=254
Respuesta desde 192.168.0.24: bytes=32 tiempo=2ms TTL=254
Respuesta desde 192.168.0.24: bytes=32 tiempo=2ms TTL=254
Respuesta desde 192.168.0.24: bytes=32 tiempo=1ms TTL=254
Respuesta desde 192.168.0.24: bytes=32 tiempo=5ms TTL=254
Respuesta desde 192.168.0.24: bytes=32 tiempo=2ms TTL=254
Respuesta desde 192.168.0.24: bytes=32 tiempo=1ms TTL=254
Respuesta desde 192.168.0.24: bytes=32 tiempo=2ms TTL=254

Estadísticas de ping para 192.168.0.24:
Paquetes: enviados = 752, recibidos = 752, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 1ms, Máximo = 134ms, Media = 2ms
Control-C
^C
C:\Users\conta>

1 Like
12

I can confirm that cloud is very slow sending files and many times do not work at all.

1 Like
15

Hello, yesterday I did some extra tests and I saw the following:
Sending files to the printer directly via FTP once again leaves WI-FI communications with the printer unusable, leaving it with extreme degradation.
Also this occurred while printing and the printer crashed and I lost the print.
I rebooted and the communication problem continued (it is clearly seen with ping) I logged off from the printer and logged on again and everything working perfectly, I rebooted and once again extreme degradation in communications returned.
For the moment everything works ok as long as you log out and log in again and don’t restart the printer or use the FTP function.

1 Like
16

I also noticed something weird on my P1P.

Some strange layer shift that wasnt there prior. Exact same gcode from cloud or SD card. Nothings changed. Literally overnight this started happening… hmmmm?

1 Like
17

tempted to confirm. Several flat objects printed with same filament smoothly. After update: one line too high and crippled the print surface.

1 Like