Having ordered my first 3D printer, I am giddy and preparing various things.
I have installed Octoprint on my home server as a Docker container, but when running it, it seems that it wants to have a serial connection to a printer. Octoprint expects to be running on a Raspberry that is connected via its serial interface.
What am I missing?
The printer I ordered (Prusa Mini) comes with a wifi dongle, so I guess there will be a way to reach it over the network. But that does not automagically mean Octoprint can work with it.
I used to use Octoprint to connect to an Ender 3, which didn’t come with an internet connection. Now that I have an Ankermake M5, I don’t use it anymore.
You could connect your desktop to the 3D printer, I don’t think a Raspberry is required.
Luckily the S in USB stands for serial, so I have 3 printers connected to my server via USB and each one has its own octoprint docker container
I thought Octoprint can have more than 1 printer? Why do you have 3 separate containers?
Also, let’s say I connect my printer to my server with USB, how do I route that USB connection from the server into the container? How did you map that?
Octoprint can only connect to 1 printer at a time, so if you want to use 2 printers at the same time you need 2 separate instances of octoprint. I use portainer so passing through a device is just a matter of finding the device path on the host machine and plugging its path into the portainer config under the runtime & resources tab. In a docker compose you’d use the devices key, for example
devices:
- /dev/ttyUSB1:/dev/ttyUSB1
You will likely need to create a separate alias for the host USB path though because devices can be found in a different order every reboot so the path will change. The USB device alias will be based on the device vendor and product id so it will be persistent. https://michaelgreenhill.net/persistent-addressing-for-usb-devices-in-linux/ is one site that explains the issue and how to deal with it
I’m getting mixed signals, (home server/seems like basics question). You just need to establish a TTY serial connection between the host and board. Linux is Linux regardless of the physical hardware.
Octoprint requires connecting printer to the computer running octoprint via a USB cable. It can be a raspberry pi but it doesn’t have to be.
The wifi dongle works with PrusaLink software which appears to be an alternative to Octoprint. So you’d use one or the other, not both together.
As you’ve already noticed, the default way to get Octoprint running is by running it on an RPi with OctoPi as its operating system and connecting that to your printer using a serial connection, which basically means connecting a USB cable in your case.
The docker container gets interesting if your home server is physically close enough to your printer that you can connect the printer directly. Then you can just mount the serial connection into the container and run Octoprint there, cutting out the need for a RPi.
As others already said, the Prusa Mini also has PrusaLink integrated into its , which is an alternative to Octoprint and only needs the printer connected to your network via Ethernet or Wi-Fi with the Wi-Fi upgrade.
