[Bug]: P1S re-print

[kampfklecks]

Bug Description

Hello,
I installed Bambuddy today.
everything I checked (printer sd card, webcam) works,
but I can not start a print. It says that the file transfer failed.
The file itself is in the root folder of the sd card. It somehow worked but the print not starting.

Expected Behavior

File should upload and start.

Steps to Reproduce

1. Connecting Printer
2. Upload GCode 3mf File to Archive
3. Send to Printer

Printer Model

P1S

Bambuddy Version

0.1.6b

Installation Method

Docker

Operating System

Linux (Ubuntu/Debian)

Relevant Logs

Screenshots

No response

Additional Context

No response

Checklist

• I have searched existing issues to ensure this bug hasn't already been reported
• I am using the latest version of Bambuddy

[maziggy]

Please provide logs and - if possible - the upladed 3mf file.

[kampfklecks]

2025-12-27 18:28:29,057 INFO [backend.app.services.bambu_ftp] FTP connecting to [PRINTERIP] for upload... 2025-12-27 18:28:29,874 INFO [backend.app.services.bambu_ftp] FTP connected to [PRINTERIP] 2025-12-27 18:28:29,874 INFO [backend.app.services.bambu_ftp] FTP uploading /app/archive/unassigned/20251227_181102_Bumper+Car+V1.05b_Body Design A.gcode/Bumper+Car+V1.05b_Body Design A.gcode.3mf (15181785 bytes) to /Bumper+Car+V1.05b_Body Design A.3mf 2025-12-27 18:30:08,138 ERROR [backend.app.services.bambu_ftp] FTP upload failed for /Bumper+Car+V1.05b_Body Design A.3mf: The read operation timed out INFO: [PCIP]:56159 - "POST /api/v1/archives/1/reprint?printer_id=1 HTTP/1.1" 500 Internal Server Error

It doesn't depend on the file size, I checked with a 30KB file and it gives me the same error.
I exported it with Bambu studio the same way I would send it directly to the printer.

[maziggy]

Since I don't have a P1S to test, some additional questions please:

• Can you connect with FileZilla (FTP over TLS, port 990) and upload a file?
• What firmware version is the P1S running?
• Is the P1S in LAN-only mode?

[kampfklecks]

I checked:

Uploading the same file with FileZilla worked (3seconds), as I mentioned before the file uploaded with Bambuddy is also completely transferred to the sd card of the printer

P1S FW is 01.09

I enabled LAN-only Mode.

[kampfklecks]

That may be interesting:

I checked also the printer screen shortly after I press print.
It gives me a HMS Error 0500-0500-0001-0007, enabling dev mode does not do anything

[maziggy]

First of all enabling dev mode is mandatory! Please enable it, restart the printer and check printer's display, if dev mode is enabled. After that please send the print job again and send me the related logs.

[kampfklecks]

Enabled Dev-Mode and restarted the printer.
I still can't start a print.

FTP Upload works fine, and I can start the file from the printers display. But Bambuddy doesn't start it for me.

The logs are the same

[maziggy]

OK, I've added a lot of debug logging to see, what exactly happens.

Please use branch issue-31-debug, use start_debug.sh or docker-compose.debug.yml to start and provide the debug logs.

[pinionless]

I have similar issue on A1
I can see that file gets uploaded successfully but the print does not start with an "upload failed" error.

[pinionless]

2026-01-04 11:42:04,116 INFO [backend.app.api.routes.archives] [REPRINT-DEBUG] === REPRINT STARTED: archive_id=1, printer_id=1 ===
2026-01-04 11:42:04,118 INFO [backend.app.api.routes.archives] [REPRINT-DEBUG] File size: 2524061 bytes
2026-01-04 11:42:04,118 INFO [backend.app.api.routes.archives] [REPRINT-DEBUG] Remote filename: cap.3mf
2026-01-04 11:42:04,118 INFO [backend.app.api.routes.archives] [REPRINT-DEBUG] Remote path: /cap.3mf
INFO:     172.100.40.109:52612 - "GET /api/v1/pending-uploads/ HTTP/1.1" 200 OK
*get* '220 BBL-P003 FTP Server\n'
*resp* '220 BBL-P003 FTP Server'
*cmd* 'USER bblp'
*put* 'USER bblp\r\n'
*get* '331 \n'
*resp* '331 '
*cmd* 'PASS ********'
*put* 'PASS ********\r\n'
*get* '230 \n'
*resp* '230 '
*cmd* 'PBSZ 0'
*put* 'PBSZ 0\r\n'
*get* '200 \n'
*resp* '200 '
*cmd* 'PROT P'
*put* 'PROT P\r\n'
*get* '200 \n'
*resp* '200 '
*cmd* 'DELE /cap.3mf'
*put* 'DELE /cap.3mf\r\n'
*get* '250 \n'
*resp* '250 '
*cmd* 'QUIT'
*put* 'QUIT\r\n'
*get* '221 \n'
*resp* '221 '
2026-01-04 11:42:04,979 INFO [backend.app.api.routes.archives] [REPRINT-DEBUG] Starting FTP upload to 192.168.1.40...
2026-01-04 11:42:04,979 INFO [backend.app.services.bambu_ftp] FTP connecting to 192.168.1.40 for upload...
*get* '220 BBL-P003 FTP Server\n'
*resp* '220 BBL-P003 FTP Server'
*cmd* 'USER bblp'
*put* 'USER bblp\r\n'
*get* '331 \n'
*resp* '331 '
*cmd* 'PASS ********'
*put* 'PASS ********\r\n'
*get* '230 \n'
*resp* '230 '
*cmd* 'PBSZ 0'
*put* 'PBSZ 0\r\n'
*get* '200 \n'
*resp* '200 '
*cmd* 'PROT P'
*put* 'PROT P\r\n'
*get* '200 \n'
*resp* '200 '
2026-01-04 11:42:05,735 INFO [backend.app.services.bambu_ftp] FTP connected to 192.168.1.40
2026-01-04 11:42:05,735 INFO [backend.app.services.bambu_ftp] FTP uploading /app/archive/unassigned/20260104_114152_cap.gcode/cap.gcode.3mf (2524061 bytes) to /cap.3mf
*cmd* 'TYPE I'
*put* 'TYPE I\r\n'
*get* '200 \n'
*resp* '200 '
*cmd* 'PASV'
*put* 'PASV\r\n'
*get* '227 (192,168,1,40,7,232)\n'
*resp* '227 (192,168,1,40,7,232)'
*cmd* 'STOR /cap.3mf'
*put* 'STOR /cap.3mf\r\n'
*get* '150 \n'
*resp* '150 '
INFO:     127.0.0.1:33458 - "GET /health HTTP/1.1" 200 OK
2026-01-04 11:42:29,299 ERROR [backend.app.services.bambu_ftp] FTP upload failed for /cap.3mf: The read operation timed out (after 23.6s)
*cmd* 'QUIT'
*put* 'QUIT\r\n'
*get* '226 \n'
*resp* '226 '
2026-01-04 11:42:29,311 INFO [backend.app.api.routes.archives] [REPRINT-DEBUG] FTP upload result: False (took 24.33s)
2026-01-04 11:42:29,311 ERROR [backend.app.api.routes.archives] [REPRINT-DEBUG] FTP upload FAILED after 24.33s

In File Manager I can see that the file cap.3mf was uploaded

[maziggy]

Please try latest 0.1.6b6 release. There are some FTP related improvements. Maybe that helps....

[pinionless]

ERROR [backend.app.services.bambu_ftp] FTP upload failed for ... The read operation timed out

[kampfklecks]

I am definitely too slow :D

Checked it too.
Still not working.

FTP Upload works fine but ends with a timeout. Its needs to be something with the print start MQTT or the waiting time. Maybe there is no response from the printer that the upload succeeded.