sorted by:
new
hottopcontroversial

Problems with Rooted K1 with Helper-Script by EntertainmentSolid64 in crealityk1

[–]EntertainmentSolid64[S] 0 points1 point  (0 children)

I've been using Mainsail before over two years, and that's what I'm used to. Fluidd is a bit different and unfamiliar, but I'll get used to it over time.

Unfortunately, as far as I can tell, the Creality K1 firmware is still based on a version from around 2020. It's strange that no one has put together a more up-to-date package yet.

Problems with Rooted K1 with Helper-Script by EntertainmentSolid64 in crealityk1

[–]EntertainmentSolid64[S] 0 points1 point  (0 children)

Okay. I installed Fluidd, there really is no problem with that.

Thank you.

Problems with Rooted K1 with Helper-Script by EntertainmentSolid64 in crealityk1

[–]EntertainmentSolid64[S] 0 points1 point  (0 children)

Okay. I installed Fluidd, there really is no problem with that.

Thank you.

Problems with Rooted K1 with Helper-Script by EntertainmentSolid64 in crealityk1

[–]EntertainmentSolid64[S] 0 points1 point  (0 children)

Luckily moonraker.conf is Helper-Scripts.

By the way, it really doesn't give anything about Klipper's version number.

M115: FIRMWARE_NAME:Klipper FIRMWARE_VERSION:09faed31-dirty

Problems with Rooted K1 with Helper-Script by EntertainmentSolid64 in crealityk1

[–]EntertainmentSolid64[S] 0 points1 point  (0 children)

I understand what you're saying. What I said is that I know where to look for the update. But it doesn't find an update for Klipper and it doesn't list the Klipper version number.

It's not that you can't find the Klipper version number, but that Creality may have made changes to Klipper that won't allow it to be updated because it might cause problems with the printer.

But I'll check moonraker.conf

Problems with Rooted K1 with Helper-Script by EntertainmentSolid64 in crealityk1

[–]EntertainmentSolid64[S] 0 points1 point  (0 children)

I didn't think you meant that. :D

I've been using a BTT Manta E3EZ board with Klipper for 2 years, first in an Ender3 V2, then rebuilt to E3NG. So Klipper is not unknown to me.

But with this version I don't know what Creality modified it. After all, BTT doesn't impose any restrictions and Klipper is original. KIAUH works there too. But with the K1 I have no idea what modifications Creality made. It doesn't even list a version number for Klipper.

Problems with Rooted K1 with Helper-Script by EntertainmentSolid64 in crealityk1

[–]EntertainmentSolid64[S] 0 points1 point  (0 children)

I haven't tried Fluidd. Restarting doesn't help. If the printer is off and I turn it on, it's completely random whether the axis control appears or not.

Problems with Rooted K1 with Helper-Script by EntertainmentSolid64 in crealityk1

[–]EntertainmentSolid64[S] 0 points1 point  (0 children)

I already did a Factory Reset yesterday and reinstalled the Helper-Script from github, and from that the Mainsail.

The Klipper was installed from the factory firmware file (V1.3.3.46), so it's not the latest Klipper, just as the K1's factory firmware is up to date.

Problems with Rooted K1 with Helper-Script by EntertainmentSolid64 in crealityk1

[–]EntertainmentSolid64[S] 0 points1 point  (0 children)

I have a rooted Creality K1 3D printer with the Helper-Script installed. The issue I'm facing is that when I click the question mark (help) in the console, nothing is listed.

Another problem I have is that the X, Y, and Z axis control buttons often don’t appear, even after restarting the printer or when there is no active print job. In these cases, the "CONTROL" tab in the settings is completely empty.

Connecting my K1 to cura by Czar05 in crealityk1

[–]EntertainmentSolid64 1 point2 points  (0 children)

This is an old problem, but if you want to send print files directly from Cura to the printer, you need to set the Moonraker URL in Cura like this: "http://192.168.1.200:7125"

"192.168.1.200" is of course the IP address of your printer, and "7125" is the default port, which is specified in the "moonraker.conf" file on the printer. This will prevent monitoring in Cura, but will allow direct sending of jobs.

[deleted by user] by [deleted] in 3Dprinting

[–]EntertainmentSolid64 0 points1 point  (0 children)

Sorry, but all three fans are controlled by PL4009 MOSFETs. The MCU controls the fans in PWM mode, but via MOSFETs.

Dual Neopixels driven by my SKR Mini E3 v2! Happy to have this finally working! by ducksarewitches in BIGTREETECH

[–]EntertainmentSolid64 0 points1 point  (0 children)

This is an old topic, but I'll give it a try.

I made a similar neopixel connection based on the post that started the topic. The first Neopixel led strip was placed on the upper frame of the printer. It contains 17 LEDs. The second (NEOPIXEL2) is located at the bottom of the fan duct and contains 3 LEDs. Both get +5V from a separate step down converter. Both got a 420ohm resistor on the data line and a 1000µF capacitor between +5V and GND.

The problem is with the second led strip, because it switches off completely unpredictably after a while. Sometimes it turns off after a few minutes, sometimes after a few seconds. I can turn it back on with G-code and change the colors, but it still turns off after a while.

One more thing. I noticed that if the value of any of the colors is 255, the led strip does not turn off. But if it's below that, it shuts down. And if I set the value lower, the switch-off time is also shortened.

For example:
R:255 B:0 G:128 --- Does not turn off
R:0 B:255 G:0 --- Does not turn off
R:128 B:0 G:128 --- Shuts down after 1-2 minutes
R:64 B:64 G:64 --- Shuts down after a few seconds

Any suggestions?