As the videos and articles are coming out more, as deliveries are finally made, I have come to the conclusion that the #Prusa XL is an early access printer.
It is literally like buying early access games. "Here is a game at full price. The functionality is limited, and we promise we will release this in the future, but there are many bugs."
Prusa literally finalized the design, did some internal testing, and said to themselves, "Yeah. This is fine. Send it to manufacturing."
What I do like about the XL is that they actually use Gcode. For example the #Qidi and #Creality printers have these built in Gcodes. So even with a vanilla #Klipper install, part of the starting Gcode is hidden begind these macros, unless you completely re-write them.
The XL actually uses the slicer Gcode for stuff like toolchangea. So you are able to change and tweak a lot.
Both #nozzle (#extruder)) #heater and #hotbed one do not warm up. Beyond all doubt (using external power sources and hairdryer) I confirmed that both thermistors, heaters and wiring are ok.
Under warranty, RatRig sent me replacement board, which I configured, flashed with updated firmware and got the same error.
I also tried to redirect the nozzle heater power to another pin (see in the config file at lib.tepewu.pl/f/8f1d29fe05d44c…) where I hooked up the multimeter. Nothing happened, when I set up nozzle temp to 50*C - after timeout I had the same error "extruder is not heating fast enough", thus klipper shutdown.
I cannot believe to have such a bad luck to got two boards with the same hardware fault (especially that steppers and hotbed probe work perfectly), so it is something I do not know - and I run out of ideas.
Der neue Hotendlüfter (5015) ist angebaut. Die Probe-Touchsonde hat damit auch ihre Position verändert, was einiges an Umkonfiguration in #Klipper erforderte. Zudem den Hotend Lüfter auf 60% gestellt.
Dann alles neu kalibriert, inkl. PID Kalibrierung der Hotend-Temperatur.
Nun einen Durchschnittspegel von 34 dB (31-37). Was ggü. dem Original Lüfter eine Verringerung von 9 dB bedeutet. Also wieder Halbierung der Lautstärke.
Months ago, I saw youtubers insisting that Creality was going to start honoring open source license terms soon after actually shipping the K1 and K1 Max products to the general market. Did that ever actually happen? #3DPrinting#openSource
That's the problem. The #Creality#K1 stock doesn't run #Klipper as we all know and love it. They run #CrealityOS. So naturally, it has no documentation, and you have no Idee what macros exist or what you can do with #Gcode.
Wirh the rooted verion, you can use #Mainsail and #Fluids, but naturally, the updates are broken, and you are dependent on Creality. But at least I have access to Klipper Macros and can also make my own. I can also correct the mistakes they made with the config.
@koz has the Qidi, and did have a better experience than me initially, but did have to change more in the Klipper config.
I just don't understand. Just give me pure #Klipper! Stop thinking you can make it better, you can't! Just give me vanilla Klipper. I buy your printer because I don't have the time or money to build a #Voron. So just give me a blank slate machine with pure Klipper and leave me alone!!!
3D printing random things to use up the last of a spool of filament and make sure settings are ok since I switched from SuperSlicer to PrusaSlicer today.
Eyeball diff of settings because the configs are too different due to extra settings in SuperSlicer and my Prusa settings were a version or two old.
The other day I upgraded the OctoPi install and also Klipper but that didn't change the printing any.
The fact that you paid for your 3D printer doesn't mean that any of that money reached the developers giving their time to create and maintain the software it runs.
The rule of thumb is that if you use free open-source software, please consider sponsoring the developers and maintainers of said software.
Oh, an ugly bug with #OrcaSclicer, and adaptive slicing, and tree support. With adaptive slicing, the tree structure is too small.
Without adaptive slicing, the tree support reaches the painted area.
Btw., also #Klipper runs in calculation issues (the max layer amount and current layer is not in sync with variable layer size), but this tree error in Orca is a more certain bug.
Ich habe einen Gehäusebausatz gekauft (aus Frankreich) und möchte die Gehäusetemperatur / Luftfeuchtigkeit darin messen und habe dafür ZigBee Sensoren gekauft (da ich ohnehin noch für andere Ecken welche brauchte).
#HomeAssistant wird die Sensoren ohnehin angedockt bekommen. Also liegen die Daten per MQTT vor.
#Klipper kann i. d. R. nur direct attached Sensoren (an Pins) auslesen, aber auch (für Host-Temperatur) aus dem Temperature System File lesen.
Also spricht doch nichts dagegen, dass ich mit einem Script mich als Listener an ein MQTT-Topic hänge und die Daten in ein eigenes File schreibe und das Klipper als Host-Temperatur unterschiebe (natürlich mit einem sprechenden Namen).
Man kann ja beliebige Temp-Sensoren konfigurieren und auch die Config für die Host-Temp erlaubt einen Pfad zu der Datei.
Der Inhalt des ARM System Temperature File ist einfach auszulesen:
$ cat /sys/class/thermal/thermal_zone0/temp
Wenn ich eine eigene Datei anlege, in dem ich Celsius * 1000 reinschreibe, sollte das für #Klipper reichen.
Man könnte das einfach testen. Eine statische Datei anlegen, mit einer Zahl und Klipper darauf konfigurieren. Wenn das geht, ist der Rest der Lösung klar.
Also, part of #Klipper is being configurable. If they use #KlipperScreen, then I can customise it, change the theme, add other features, measurements, and buttons, and customise it to my liking. If they use their own UI, the source code is normally not used, and you can extend it.
I made a quick dashboard in #HomeAssistant for my #3DPrinting activities. Right now it just has a couple graphs and buttons from #OctoPrint and a button to turn on and off my filament dryer with a timer.
Has anyone else done similar? Any good ideas out there I should incorporate?
@amd
I have #HomeAssistant, ConBee II, #Klipper, a WiFi Outlet and an Ikea Shortcut Button via #Zigbee. All together can shutdown the printer and cut off the power for the Raspi and the printer.
If the print is finished, I call a macro to shutdown the Pi. On shutdown I send a #MQTT Message to HA. HA waits for 20s and switch the power off.
In Klipper (Web/Screen) you can signal at any time to shutdown or not at the end of a print (managed by two additional macros).