Recent content by shiftingtech

left out the final piece of that thought: if you wish to have additional *manually controlled* fans, you set them up as fan_generic, which can then be managed via the SET_FAN command

M106 should not have any impact on the heat break fan. since the config you posted looks reasonable, I have to assume that's a wiring situation of some sort. Also worth noting, the heatbreak fan shouldn't have speeds other than "on" and "off". In the config you posted, the answer to "how do...

What do you mean, "both fans respond equally"? which fans? Also, klipper doesn't use a "p" parameter for m106 or m107.

but seriously, "missed scheduling" can fall into some of the same troubleshooting paths as some other common canbus related errors. You should have a look at https://canbus.esoterical.online/troubleshooting/timer_too_close.html and *possibly* even...

Importing your V2.5 from the future is probably the issue. Should have stuck to printers that naturally exist in this place and time.

different (higher) microstepping and/or turning on interpolate might help tmc2240s are noticably quieter in other applications. haven't tried them in this one, but...maybe... I'm curious if you actually tested MOVING faster on Z. I mean, it's all well and good to talk about increasing the max...

Two problems stand out in your log. 1. usb-STMicroelectronics_STM32_Virtual_ComPort_3561384D3530-if00 does not sound like a board that's been successfully flashed with klipper firmware. 2. You need to use the full path. So, for example...

feels like you're WAY over thinking this: open your config file. look for LED related things. remove them. the end. It's also worth noting, I think that error is related to the ledeffects plugin, not stock klipper at all. So you may want to consider getting rid of the unnecessary plugin...

Should be fine. Also, the files must have dropped in the right place, because otherwise klipper would yell about THAT.

If that description is accurate, I'm almost sure you don't actually have the nitehawk file [include]ed

I'd be curious what you commented out that led to the mandatory message. If its a setting that has a dupe in the nitehawk file, and the nitehawk file is properly included, that really shouldn't happen

So, a couple of things. 1. Any setting can go in any file. What you don't want to do, is you don't want to set the same thing in multiple files. Because then one will Overwrite the other, and it will get confusing. So what you want, is to have the any given settings in the file *that makes...

well having the ENTIRE macro (and _FINE_QUAD_GANTRY_LEVEL) seems like it would probably work. But having half of it, and then the last 3 lines commented out, like you have? ya...that's no good.

Well but hold on. that macro you posted is the problem ! `{% if printer.quad_gantry_level.applied == False %}` So sure...that runs the first time, when qgl hasn't already been applied... but after that... 🤷‍♂️ applied==True. so...nothing happens!

What do you mean by that? What happens if you run the command again?