Just installed klipper using kiauh in Debian. When I try to access klipper I get the default Apache page.
…
How did you try that?
Seriously? This is all you’re giving us to help you?
Dude, when you posted this you were asked for information on your system and a klippy.log yet you just powered through and wrote two sentences without any information thinking that somehow magically people can help you.
Why don’t you start a new thread with something we can work with?
1 Like
I apologize for the lack of info. I was pressed for time and didn’t have access to the klipper log at the time. I am shamefully updating my information.
Ender 3 S1 PRO
Stock MCU
HP G3 with Debian OS
Over the weekend I switched from Ubuntu to Debian. I used KIAUH for the set up and everything went fine. I should mention that I am a teacher and this is set up I have at school (Middle School). When I took the computer to school and put in the IP address in the browser I am taken to the Debian Apache2 default page instead of klipper.
klippy.log (119.4 KB)
moonraker.log (34.5 KB)
I appreciate any help and I am ready to give more info if needed.
You’re not going to like this but it’s extremely difficult to get a laptop to work as a Klipper host reliably. It is possible, but you will have to go through some hoops and I think you have a problem related to using the laptop.
I’m not sure what IP address you’re talking about - normally that is of the host (in your case the laptop) and you’re accessing the Mainsail/Fluidd web page from another computer on the network.
Regardless, when I look at your klippy.log, I see that you’ve put in what looks like the correct information for the printer and connected and then ended up with a number of “Resetting prediction variance” errors that cause the printer connection to shut down.
My understanding of “Resetting prediction variance” is that the host (the HP G3 in this case) cannot and the main controller board (in the printer) cannot sync up. Timing between the host and the printer MCU is critical and if the host can’t get a good lock on the MCU then Klipper will shut down.
Going back to the start of this reply; it seems like using a laptop would be the ideal host for Klipper but it really isn’t. Typical user based Operating Systems have a lot of background tasks going on which makes it very difficult, if not impossible, for the laptop’s CPU to get a good, consistent read on the MCU’s.
Most people start with a very minimal OS (like Mint) and strip out everything that they can to minimize the chance that the CPU gets a process change while doing something critical with Klipper. It generally takes a lot of work, appears to the host hardware specific and there’s no simple solution.
My recommendation for you is to replace the HP G3 with a Raspberry Pi. The rPi 4B is generally recommended and won’t give you any issues. I’ve used the Raspberry Pi Zero 2W without any issues if you’re looking for a very low end device.
Thank you for the feedback. It seems that the problem was the apache server. Once I got rid of that I was finally able to klipper. Noe I am having a problem with printer connection. BTW I don’t know if it matter but this is not a laptop it is a small computer. Here are my new logs
klippy(1).log (701.0 KB)
moonraker(1).log (69.9 KB)
I’m glad you found the display problem.
Could you send me a reference to the “HP G3”? When I look for it, I find things like:
with no reference to anything other than a laptop.
Not that it makes any difference - trying to run a PC as a Klipper host can be problematic and difficult to get working reliably.
Now, when I look at your klippy.log, I see:
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-idusb-1a86_USB_Serial-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-idusb-1a86_USB_Serial-if00-port0'
Going back to your mcu statement, you have:
[mcu]
serial = /dev/serial/by-idusb-1a86_USB_Serial-if00-port0
restart_method = command
I think you overwrote a slash (“/”). Try:
[mcu]
serial = /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
restart_method = command
Finally, yYou have an amazing number of macros (other than the mainsail.cfg ones) - going by your klippy.log, they extend from line 17180 to 20101.
That’s almost 3,000 lines of macros. Do you understand exactly what they do and why they are there? How have you verified that they are critical to the operation of your printer?
If you can’t answer “yes” to all three questions and have a detailed answer for each of the three questions, I HIGHLY recommend that you get rid of them.
Macros are a great tool for enhancing a printer but they should be used sparingly with a clear understanding of what each of them do. A common newbie mistake is to see a package and add it to their printer.cfg without doing any kind of analysis (other than seeing somebody online saying “they’re great!”).
They can cause a lot of problems and are a bitch to debug unless you know EXACTLY each one does.
So, unless you understand what each line of the macros does and can recognize and debug any problems that arise from them, delete them for now and, if they are necessary once the printer is running, you can put them back up.
Here is a link to the computer I am using. https://support.hp.com/bg-en/product/product-specs/hp-prodesk-600-g3-desktop-mini-pc/15257642
The main reason I am using this computer is because they were free and I have over 50 of them. They were donated to my school.
As for the macros I believe I have a basic understanding of their purpose. I simply followed the direction from here. Klipper Macros - What They Are and How to Use Them | Obico Knowledge Base
I will be cautious in their use and work on getting rid of them. Thank you for your help and advice.
Did the change to the mcu UUID path get you connected?
You’re going to need much more than a “basic understanding” of the macros you use. As you go along and work with your system, anytime you ask for help, you’ll be asked what the macros are doing and how they affect the issue you’re asking about. If you can’t answer the questions precisely you’re going to be told to remove them before anybody will look at your issues - you may get told to remove them anyway to see if something unexpected is happening with them.
Trust me, it’s in your best interests to get rid of everything except for the basic macros that are brought in with mainsail.cfg.
I get why you’re using the HP Prodesk 600 G3 - Personally, I wish Klipper would work with Chromebooks as schools (here) have tons of them and they’re great little computers.
Again, it can be extremely difficult getting a PC based host working reliably due to the precise timing requirements of Klipper. I’m surprised that you can’t find a Raspberry Pi (4B ideally) somewhere in your school or board.
Anyway, good luck and keep us posted as to your progress!
Cool school project. What is your goal to achieve with the kids?
Regarding your ‘HP ProDesk 600 G3 Desktop Mini PC’. I would install ‘Ubuntu Server’ it’s without graphical interface. The look and feel is like a ‘Raspberry Pi OS lite’ Installing Klipper with KIAUH. I have to admit, I never used a real Debian installation. I would prefer Ubuntu, because I think there is a much better support from the community (also Go+g*_e and what you may get). I’m sure your ‘HP ProDesk 600 G3 Desktop Mini PC’ will work with Klipper and ‘klipper.discourse.group’ will probably help you to get the printer working.
Good luck, hcet14
1 Like
I did try ubuntu server, but it was too complicated with the network at my school. The IT people are not very helpful with projects like this.
Mmmh, I don’t get it.
My picture is:
Ender 3 S1 PRO
HP ProDesk 600 G3 Desktop Mini PC
…running Klipper and printing
Just use another ‘HP ProDesk 600 G3 Desktop Mini PC’ (you got 50?) as PC to connect to your ‘HP ProDesk 600 G3 Desktop Mini PC’ used as Klipper host.
That system is independent from
Do you need the network of your school for that school project?
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.