PandaPrint
This is a server that enables uploading from OrcaSlicer to Bambu Lab printers in LAN mode without the use of the Bambu Lab network plugin.
Users concerned about security or software freedom may be reluctant to use either the Bambu Lab cloud service or the proprietary Bambu Lab network plugin. PandaPrint does not replace all of the functionality in the network plugin, but it does allow sending a project to a printer directly from OrcaSlicer.
Configuration
Create a printers.yaml file like this example:
printers:
- name: bambu
host: bambu.lan
serial: 123456789012345
key: 12345678
The fields are as follows:
- name: A friendly name of your choosing. This will appear in the
url supplied to OrcaSlicer later. If you have more than one printer, ensure this is unique.
host: The hostname or IP address of the printer.
serial: The serial number of the printer.
- key: The access key for the printer. Get this from the LAN mode
screen.
Running
The easiest way to run this is from a container image.
Running the Container Image
A sample docker-compose file is included.
docker compose up -d
Running from Source
To run this directly from the source repo:
poetry install
poetry run pandaprint ./printers.yaml
Configuring OrcaSlicer
Edit the printer.
Enable the Advanced toggle.
Under Basic information, Advanced, check Use 3rd-party print host
Close the printer edit dialog.
Click the Connection button (wifi icon) next to the printer.
Under Print Host uplod set the following: Host Type: Octo/Klipper Hostname, IP or URL: http://localhost:8080/bambu (if you chose something other than bambu as the name in printers.yaml, use that here instead)
Press the Test button to ensure everything is working.
Press “OK”
At this point, you should be able to use the Print Plate button to send projects to the printer.
License
This software is licensed under the AGPLv3. See LICENSE.txt for details.
Contributing
Pull requests are welcome.
Running Tests
cd tools
./test-setup.sh
cd ..
poetry run stestr init
poetry run stestr run
Metadata
Release files for pandaprint 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pandaprint-1.0.0.tar.gz | 16.0 kB | Without provenance | Details for pandaprint-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pandaprint-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for pandaprint-1.0.0-py3-none-any.whl |
Total release size: 33.3 kB
Release files / pandaprint-1.0.0.tar.gz
| Download URL | pandaprint-1.0.0.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bfd9d8819b26fa0439ec7229c3e231f619b954025374e3974890599bf80a3654
|
|
BLAKE2b-256 checksum How to use checksums |
2ba43e3a35cad908159da836d56390d14e54fa703ad2494779e2febb5edc6d31
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.2 CPython/3.12.3 Linux/6.8.0-45-generic
|
Release files / pandaprint-1.0.0-py3-none-any.whl
| Download URL | pandaprint-1.0.0-py3-none-any.whl |
|---|---|
| Size | 17.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fda264f36850f4e7baa3953414879bd9f74f23d6471e31d27285eec42e0d3440
|
|
BLAKE2b-256 checksum How to use checksums |
565c08919b92bd98596677616a3b76599e29698224e6a2afe04d34642930be54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.2 CPython/3.12.3 Linux/6.8.0-45-generic
|
Security for pandaprint 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.