synman
commented
8 months ago This is likely one of two things.
- I had a preprocessor bug related to "." characters in the filename not tied to the actual .gcode.3mf extension. This is fixed in an up and coming build I'll be releasing in a day or two.
- The .gcode.3mf file was not uploaded by BPM. In this scenario BPM does not have a "cached" copy of the 3mf and therefore can't find it. I haven't decided yet if I want to go through the trouble of syncing storage between the printer and container and suggest you always upload from BPM for now as this ensures both the printer and BPM get a copy of the archive.
Regarding the second point, you can also create a storage link between your host and the BPM container, linking to the container's /bambu-printer-app/api/uploads directory. You can then at least have access to what is in the BPM file "cache". Keep in mind, this does not upload the actual 3mf to the printer. It merely gives BPM access to it.
As I add additional features such as cancel objects and better AMS mapping support, solving this underlying issue will become more important.
I'm inclined to mark it as a bug for now.
I've deployed your container and all works very well but the "Get current 3mf png" (thumbnail of printing model).
If I'll open the missing image I receive of course the following message:
Link: /api/get_current_3mf_png
Is there something to fix on my site? I've defined the following environment variables for the container:
I'm using a Bambu P1S on latest firmware release 01.05.02.00.