This information on pre installed Klipper on 3D-Printers
To access Klipper from OctoPrint, Klipper has to provide the /tmp/printer virttual USB port. The port name can be different. For this, OctoPrint must have access to this port. For this is a virtual and no physical USB port, OctoPrint must run on the same system as the Klipper installation. (Like classical OctoKlipper). The physical USB port of the printer is used by Klipper to communicate.
Over at the Klipper forum we made the experience that pre installed Klipper differ slightly up to massive from genuine Klipper (see Sonic Pad).
Due to special hardware, it is also difficult to install genuine Klipper on those systems.
@linuxpaul
The point is, as the title describes, that users, who have a printer with pre installed Klipper, want to connect them to OctoPrint.
This does not work out of the box - if even possible at all.
The point is that when using Octoprint and Klipper, you should always familiarise yourself with the Klipper documentation; /tmp/printer is the least of it. If you install octoklipper straight away, you won't come across this issue at all.
At best, I would add a reference to the original documentation.
But that seems to be the biggest challenge to deal with original docs. It's exactly the same with octoprint. A lot of outdated instructions from the net are ploughed through and nothing works and nobody looks at the docs here in the group.
No offence, everyone may has their own opinions.
I run my self a OctoKlipper installation and made the printer.cfg all on myself. So I know what I am talking about.
Again, what I am takling about is not new installations, its about People who get themself a printer with Klipper already installed it. And then they try to connect it to OctoPrint.
I am one of those users who has a klipper printer and want to use octopi to connect and manage the print jobs. My whole ecosystem runs octopi with my other printers that are running Marlin.
So if I am understanding this correctly, I cannot connect octopi to a printer that has klipper already running on it unless I install octopi in the actual printer or install a vanilla klipper and go through all the setup process to get the printer running with this opensource klipper. Is that correct? If that is the case my best option is then to use fluidd that is already running in my printer to manage print jobs remotely.
Thank you, I have been messing with my octopi for the past two weeks trying to make it work and I was not understanding it until today when I reinstalled everything again and could not connect to the printer. I then installed klipper in octopi and it magically connected even with the USB cable disconnected. That is when it dawn on me, this thing is connecting to the klipper server running on the raspberry PI and not the printer.
I appreciate the help.
This will possibly be available with version 1.12.0 of OctoPrint. Foosel is working on a communication layer change that will allow OctoPrint to communicate over the network to klipper directly as a plugin example. I think she was missing OctoPrint working with the klipper embedded printer she ended up getting.
