mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-05-09 08:25:54 +02:00
[GH-ISSUE #632] [Bug]: Printing stopped because the printer was unable to parse the file. Please resend your print job. #409
Labels
No labels
A1
automated
automated
bug
bug
Closed due to inactivity
contrib
dependencies
dependencies
duplicate
enhancement
feedback
hold
invalid
Notes
P1S
pull-request
security
ThumbsUp
user-report
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/bambuddy-maziggy-1#409
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dfjaapie on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/632
Originally assigned to: @maziggy on GitHub.
Bug Description
When a print is started from the file manager, the following error message appears.
"Printing stopped because the printer was unable to parse the file. Please resend your print job."
This happens after the file has been uploaded successfully.
I am experiencing this issue on six P1S printers.
The printers have a static IP address and developer mode enabled. However, the support-info.json file shows: "developer_mode": null.
Expected Behavior
After starting a print, the printer should begin printing without showing an error.
Steps to Reproduce
BambuBuddy v0.2.2b2 running inside a Docker container.
Steps to reproduce:
Start a print from the file manager on a P1S printer.
Wait until the file has been successfully uploaded.
The printer then shows the following error:
"Printing stopped because the printer was unable to parse the file. Please resend your print job."
Printer Model
P1S
Bambuddy Version
v0.2.2b2
Printer Firmware Version
01.09.01.00
Installation Method
Docker
Operating System
Docker
Relevant Logs / Support Package
Screenshots
No response
Additional Context
bambuddy-support-20260306-143751.zip
Checklist
@maziggy commented on GitHub (Mar 6, 2026):
Show me one of the files you tried to print please.
@dfjaapie commented on GitHub (Mar 6, 2026):
No problem, hereby attached.
testprint.gcode.zip
@maziggy commented on GitHub (Mar 6, 2026):
No, this is not a file that I see in logs.
@maziggy commented on GitHub (Mar 6, 2026):
2026-03-06 12:23:26,286 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/c25559f998ff4c4fa0fb712a27d096d8.3mf (8240927 bytes) to /test.3mf
2026-03-06 12:23:26,353 INFO [backend.app.services.bambu_ftp] FTP upload complete: /test.3mf (8240927 bytes in 0.1s, 120121 KB/s)
2026-03-06 12:25:45,600 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/c25559f998ff4c4fa0fb712a27d096d8.3mf (8240927 bytes) to /test.3mf
2026-03-06 12:25:45,686 INFO [backend.app.services.bambu_ftp] FTP upload complete: /test.3mf (8240927 bytes in 0.1s, 93200 KB/s)
2026-03-06 14:14:59,662 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/c25559f998ff4c4fa0fb712a27d096d8.3mf (8240927 bytes) to /test.3mf
2026-03-06 14:14:59,720 INFO [backend.app.services.bambu_ftp] FTP upload complete: /test.3mf (8240927 bytes in 0.1s, 139094 KB/s)
2026-03-06 14:16:31,078 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/c25559f998ff4c4fa0fb712a27d096d8.3mf (8240927 bytes) to /test.3mf
2026-03-06 14:16:31,154 INFO [backend.app.services.bambu_ftp] FTP upload complete: /test.3mf (8240927 bytes in 0.1s, 106847 KB/s)
2026-03-06 14:18:30,967 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/c25559f998ff4c4fa0fb712a27d096d8.3mf (8240927 bytes) to /test.3mf
2026-03-06 14:18:31,025 INFO [backend.app.services.bambu_ftp] FTP upload complete: /test.3mf (8240927 bytes in 0.1s, 139129 KB/s)
2026-03-06 14:19:53,941 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/c25559f998ff4c4fa0fb712a27d096d8.3mf (8240927 bytes) to /test.3mf
2026-03-06 14:19:54,136 INFO [backend.app.services.bambu_ftp] FTP upload complete: /test.3mf (8240927 bytes in 0.2s, 41476 KB/s)
2026-03-06 14:22:58,481 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/a37c16fe1e14418daf4091143706e370.3mf (1077924 bytes) to /test 2.3mf
2026-03-06 14:22:58,583 INFO [backend.app.services.bambu_ftp] FTP upload complete: /test 2.3mf (1077924 bytes in 0.1s, 10360 KB/s)
2026-03-06 14:24:30,906 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/50c3398c68774ed8ab973ab555f0d2fd.3mf (8240927 bytes) to /Unifi USW Flex Mini 2.5G wallmount.3mf
2026-03-06 14:24:30,969 INFO [backend.app.services.bambu_ftp] FTP upload complete: /Unifi USW Flex Mini 2.5G wallmount.3mf (8240927 bytes in 0.1s, 129149 KB/s)
2026-03-06 14:25:49,026 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/50c3398c68774ed8ab973ab555f0d2fd.3mf (8240927 bytes) to /Unifi USW Flex Mini 2.5G wallmount.3mf
2026-03-06 14:25:49,223 INFO [backend.app.services.bambu_ftp] FTP upload complete: /Unifi USW Flex Mini 2.5G wallmount.3mf (8240927 bytes in 0.2s, 40943 KB/s)
2026-03-06 14:26:51,072 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/c25559f998ff4c4fa0fb712a27d096d8.3mf (8240927 bytes) to /test.3mf
2026-03-06 14:26:51,267 INFO [backend.app.services.bambu_ftp] FTP upload complete: /test.3mf (8240927 bytes in 0.2s, 41521 KB/s)
2026-03-06 14:29:18,574 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/c25559f998ff4c4fa0fb712a27d096d8.3mf (8240927 bytes) to /test.3mf
2026-03-06 14:29:18,634 INFO [backend.app.services.bambu_ftp] FTP upload complete: /test.3mf (8240927 bytes in 0.1s, 133733 KB/s)
2026-03-06 14:34:17,072 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/994caafb292a4ab6b058fa3591e256e3.3mf (8339486 bytes) to /Unifi USW Flex Mini 2.5G wallmount v2.3mf
2026-03-06 14:34:17,149 INFO [backend.app.services.bambu_ftp] FTP upload complete: /Unifi USW Flex Mini 2.5G wallmount v2.3mf (8339486 bytes in 0.1s, 105965 KB/s)
2026-03-06 14:36:26,530 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/b59b97c2a5f947f7bd70d800f914d273.3mf (8339486 bytes) to /test.3mf
2026-03-06 14:36:26,633 INFO [backend.app.services.bambu_ftp] FTP upload complete: /test.3mf (8339486 bytes in 0.1s, 79452 KB/s)
@dfjaapie commented on GitHub (Mar 6, 2026):
It doesn’t matter which file I use, the issue occurs with every file. The previous file was just a test file.
I have attached a new debug log along with the file that was used. I can see the file in the printer’s file manager.
When I download this file and open it in the slicer, the file appears to be OK.
bambuddy-support-20260306-151628.zip
@maziggy commented on GitHub (Mar 6, 2026):
No, I want to see one of these files please.
I'm 99% sure, that you are sending non Gcode files (e.g. source files saved from slicer) to your printer.
@dfjaapie commented on GitHub (Mar 6, 2026):
This is the file, i just made it with bambustudio 2.5.0.66 sliced it uploaded it and started a print of it that failed. the name of the file is testprint.gcode.3mf the complete proces should be in the bambuddy-support-20260306-151628.zip i've uploaded above.
@dfjaapie commented on GitHub (Mar 6, 2026):
@maziggy commented on GitHub (Mar 6, 2026):
No no.....that's not correct. You are trying to send 3mf files. Sliced files have the format gcode.3mf. So you saved or exported the file from BambuStudio and this is no sliced file.
For example: 2026-03-06 15:14:36,887 INFO [backend.app.services.bambu_ftp] FTP upload complete: /testprint.3mf (12621579 bytes in 27.1s, 455 KB/s)
and I'm 99% sure, that if you open this 3mf file, it is NOT a Gcode file.
@dfjaapie commented on GitHub (Mar 6, 2026):
This is the proces I'm using:
With small files it seems to be working but with larger files there's something strange happening see the attached screenshots
I'm really uploading a sliced gcode file but after uploading it changes it's name.
@maziggy commented on GitHub (Mar 6, 2026):
This is a known error which is already fixed. You need to pull branch 0.2.2b2 and rebuild the Docker image locally.
@dfjaapie commented on GitHub (Mar 6, 2026):
I have created a fresh docker container with branch 0.2.2b2 but the issue remains.
bambuddy-support-20260306-162158.zip
testprint_large.gcode.zip
@maziggy commented on GitHub (Mar 6, 2026):
With Docker image 0.2.2b2, or with branch 0.2.2b2? Huge difference.
@dfjaapie commented on GitHub (Mar 6, 2026):
Sorry, I was referring to the Docker image. I’m not yet familiar with how branches work. I have found the branch and I’m trying to clone it and build it in Docker.
@maziggy commented on GitHub (Mar 6, 2026):
I think there's no need to debug any loger.
You send me this file testprint_large.gcode.3mf. This file was never printed aaccording to yout logs. So I can't use if for debugging.
When looking at your logs:
2026-03-06 16:17:31,732 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/cf47b5abc3cc4f2cb948134084a03648.3mf (30295519 bytes) to /testprint_large.3mf
2026-03-06 16:17:31,732 DEBUG [backend.app.services.bambu_ftp] FTP STOR command starting for /testprint_large.3mf
2026-03-06 16:21:12,331 INFO [backend.app.services.printer_manager] PRINT COMMAND: printer=1, file=testprint_large.3mf
This looks like the 3mf you sent to the printer is not a sliced file ready for printing.
Proove: when sending a gcode file ready for printing you see something like
2026-03-06 16:55:33,052 DEBUG [backend.app.services.bambu_mqtt] [xxxxxx] Received gcode_state: RUNNING, gcode_file: /data/Metadata/plate_1.gcode, subtask_name: C
If you provide me this file
2026-03-06 16:17:31,732 INFO [backend.app.services.bambu_ftp] FTP uploading /app/data/archive/library/files/cf47b5abc3cc4f2cb948134084a03648.3mf (30295519 bytes) to /testprint_large.3mf
i could double check, but without there's no more I can do. I'm sorry.
@dfjaapie commented on GitHub (Mar 7, 2026):
I’m 100% sure that I’m using a sliced G-code file. The file is included in the post so you can verify it. In the upload logs, the .gcode extension is always removed. This happens regardless of which file I upload and start. Also, when you upload a file that has not been sliced, you cannot start a print because that option is not available.
I have narrowed the problem down to the Docker installation I’m using. I’m running it on a QNAP. When I install Bambuddy in a Docker instance on a Raspberry Pi, it works correctly, but I can’t figure out why it doesn’t work on the QNAP.
On both instances, the .gcode file is uploaded as a .3mf file in the root directory. However, on the Raspberry Pi instance, after the upload it moves to the cache folder as .gcode and .bbl. On the QNAP instance it stays in the root directory and the process stops there. I have verified the file in the root directory on both systems and it is exactly the same.
Do you have any idea which process runs after the upload so I can try to determine why that step does not work on the QNAP Docker instance?
@maziggy commented on GitHub (Mar 7, 2026):
Since I don't know the QNAP system, I don't have any idea. Firewall?