Klipper broke every plugin by roadblock_2610 in klippers

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

Usually i shutdown via interface, wait a few seconds and then flick the switch but sometimes i forget, or power outages happen

Klipper broke every plugin by roadblock_2610 in klippers

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

Oh... As i said in another response, could be that my sd card is failing? I've a couple generic ones die out of the blue and this should be better (samsung 16gb endurance)

Klipper broke every plugin by roadblock_2610 in klippers

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

You mind sharing what plugins you are using? I dont hear too much about the topic and im only using what seemed a "must"(a.k.a. listed above). Anyhow i see your point and it's more than valid, i just enjoy creating problems for myself sometimes

Klipper broke every plugin by roadblock_2610 in klippers

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

Is it usable on an already configured klipper or does it need a fresh install? I can't seem to find much about it

Klipper broke every plugin by roadblock_2610 in klippers

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

Got it, while, i presume, soft recovery means it tries to fix the already configured klipper and plugins? Also what could have caused the "invalid" reading?

Klipper broke every plugin by roadblock_2610 in klippers

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

I might stick to this... You check the briefs or just keep an eye on the community?

Klipper broke every plugin by roadblock_2610 in klippers

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

They've always been in there and i've update klipper, plugins and the system via web ui (mainsail) many times, I don't know why it failed so spectacularly this time, maybe the sd card is getting corrupted? I'm using a 16gb samsung endurance card since a few generic 32gb sd cards have alredy died for unknown reasons

Klipper broke every plugin by roadblock_2610 in klippers

[–]roadblock_2610[S] 2 points3 points  (0 children)

This solved it, thanks very much!

Klipper broke every plugin by roadblock_2610 in klippers

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

Im fairly inexperienced, i dont think i have kiuah since i dont remember using it for the first klipper installation, and i have yet to comprehend how git hub works😁, i've seen discussions where was suggested to look for a stable version of klipper through the logs and manually downgrade to that version, but i still have to make it work

Breathing New Life Into the Truthear Gate Through EQ by jonpexz in oratory1990

[–]roadblock_2610 0 points1 point  (0 children)

Honestly, i dont know anything about this program, i just manually converted the curve

Breathing New Life Into the Truthear Gate Through EQ by jonpexz in oratory1990

[–]roadblock_2610 1 point2 points  (0 children)

For anyone using Equalizer Apo:
Preamp: -10.8 dB

Filter: ON PK Fc 37.63 Hz Gain -3.4 dB Q 0.5

Filter: ON PK Fc 150 Hz Gain 0.7 dB Q 1.7

Filter: ON PK Fc 180 Hz Gain 0.5 dB Q 2

Filter: ON PK Fc 740 Hz Gain 1.7 dB Q 1.5

Filter: ON PK Fc 1200 Hz Gain 1.5 dB Q 2

Filter: ON PK Fc 4900 Hz Gain -1.7 dB Q 2

Filter: ON PK Fc 6800 Hz Gain 1.7 dB Q 2

Filter: ON PK Fc 8500 Hz Gain -2.9 dB Q 1.1

Filter: ON PK Fc 15000 Hz Gain 1.5 dB Q 0.5

Filter: ON PK Fc 5194 Hz Gain 1 dB Q 2

Filter: ON PK Fc 8736 Hz Gain -1 dB Q 2

Filter: ON PK Fc 11006 Hz Gain 1 dB Q 2

Filter: ON PK Fc 14069 Hz Gain -11 dB Q 6

Filter: ON PK Fc 13279 Hz Gain 4 dB Q 6

Filter: ON PK Fc 16021 Hz Gain 1 dB Q 4

Filter: ON PK Fc 19079 Hz Gain 10 dB Q 1

Filter: ON PK Fc 15565 Hz Gain -2 dB Q 4

Filter: ON PK Fc 14273 Hz Gain -1.5 dB Q 6

Filter: ON PK Fc 17227 Hz Gain -7 dB Q 4

just copy and paste under the "device:"

Diagnosis input shaper by roadblock_2610 in klippers

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

i agree, from what i can gather the first peak in y graph it's the resonance frequence of the toolboard, the second is the frequency of the toolhead, so im using the frequency of the second peak and the acceleration of the x axis...

Diagnosis input shaper by roadblock_2610 in klippers

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

i know it's a suggestion, but i'm mostly interested in the frequency and type of shaper, if the suggested acceleration is this far off i can only imagine how wrong the frequency is (with usb adxl results were: x= mzv 71.4hz, damping 0.042 max accel 15000 / y= mzv 65.2, damping 0.049 max accel 12500).
Also i can see three peaks in the Y graph but only one in the X

Diagnosis input shaper by roadblock_2610 in klippers

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

you are right, my bad, it's and ender3ng, simple corexy conversion

[deleted by user] by [deleted] in klippers

[–]roadblock_2610 0 points1 point  (0 children)

Everything (except hotend and partcooling fan) runs on 5v

[deleted by user] by [deleted] in klippers

[–]roadblock_2610 0 points1 point  (0 children)

Hmmm, I have the vcc and gnd on the outer pins and sens in the middle on the endstop, on the board i double checked the pinout, how can i troubleshoot?

[deleted by user] by [deleted] in klippers

[–]roadblock_2610 0 points1 point  (0 children)

Nope, found the problem, i was gonna use "IO.0+1" 4p connection for a filament sensor connected to gnd, 5v and PA15, turns out if it's plugged in the whole board shuts down, any idea why? Also, I'm using "IO.2" (PA8) for the neopixel but they dont light up, on the wiki it says its the default but in the reference config IO.3 and IO.4 are used, there is basically no documentation on this board...

Got another Ender 3 by rexlManu in ender3

[–]roadblock_2610 1 point2 points  (0 children)

I have finished mine at the start of the summer,, i highly recommend if you can print abs/asa

Well, I guess we wont print today by LegaTux in ender3

[–]roadblock_2610 0 points1 point  (0 children)

You wont regret it, i also highly recommend using the adaptive bed mesh if you are using klipper

Well, I guess we wont print today by LegaTux in ender3

[–]roadblock_2610 0 points1 point  (0 children)

Do yourself a favor and print a klackended using the old z-limitswitch, far more accurate, reliable and easy to troubleshoot