zellneralex / klipper_config Goto Github PK

Hi, your repo with your config is very useful and I used something here and there, but there is a feature, among the many, which I think it could be useful to separate as a fully contained package (a .conf file with all it's needed): the filament management.

As of now it relies on some parts of the main macros run at startup, and it's not that obvious which ones to extract and so on.

Maybe you could split the main macros in blocks, with comments like "following block related to filament management" or similar, so that it's easier to get what I need to put in my macros/config to get your very interesting filament management.
If you are reasonably happy with the current management system, splitting it as a separate repo only with that one is an option too.

Of course I know that this is your configuration, provided as courtesy to us, so I don't really expect you to do it (I'm sure you are time constrained, just like I am or I would do it, even if it would take me way more time that it would to you), but at least you are aware of this feedback.
If you do it, I'll be thankful. If not, well, maybe I'll find the time one day... so far, I'm writing a macro per material, I just need to click on the one for the spool I use before starting a print. It's polluting the macro config file, but it works too.

Hi i follow your files to add cancel object pre process in moonraker file but I get unknown command when I print a file

04:08:27
Unknown command:"END_CURRENT_OBJECT"
04:07:14
Unknown command:"START_CURRENT_OBJECT"
04:07:14
Unknown command:"END_CURRENT_OBJECT"
04:06:01
Unknown command:"START_CURRENT_OBJECT"

cant find where you define that macros

Thanks for all the info

Noticed a typo in your printer.cfg in section [gcode_macro _EXECUTE_AT_INIT].

{% if user.hw.relay,ena %} _HEATER_ON {% endif %}

This causes the if to always be true. Modifying your configs for my voron 2.4 kept giving message about _HEATER_ON macro being non existent.

After an update, the neopixel control no longer works on the display

Error evaluating 'gcode_macro _LCD_KNOB:gcode': TypeError: coercing to Unicode: need string or buffer, Undefined found

Is there any chance you could do a mapping guide for other boards like Octopus?

When running the belt test I am getting this:
Traceback (most recent call last):
// File "/home/pi/klipper/scripts/graph_accelerometer.py", line 259, in
// main()
// File "/home/pi/klipper/scripts/graph_accelerometer.py", line 218, in main
// datas = [parse_log(fn, opts) for fn in args]
// File "/home/pi/klipper/scripts/graph_accelerometer.py", line 218, in
// datas = [parse_log(fn, opts) for fn in args]
// File "/home/pi/klipper/scripts/graph_accelerometer.py", line 22, in parse_log
// if not header.startswith('freq,psd_x,psd_y,psd_z,psd_xyz'):
// UnboundLocalError: local variable 'header' referenced before assignment
19:19:23 // Command {plot_graph} finished

The 2 files are being generated in home/pi/klipper_config/input_shaper
raw_data_belt_a_20220315_191922.csv
raw_data_belt_b_20220315_191922.csv

Klipper version: v0.10.0-312-g81283423

Tried your filament sensor code and klipper chokes on:

{% set _dummy = filament_sensor.update({params.SENSOR|string: params.ENABLE|int}) %}

stating that there is no .update in jinja. Any thoughts on that one?

Even with the latest commit, a failed QGL (e.g. due to a not probably docked probe) would still run into a issue during prime line and before print.

Since the CHECK_QGL will be executed after the prime line!

Result: MAG Probe (e.g. Klicky) can smash into the bed.

Hello
can you please "document" which hardware you use?
Like which Stepper Motors?
Heater? may be LED etc...

Thanks

During printing, lines are constantly popping up by type
// Invalid M204 command "M204 P2000"

Not really an issue but more a question: You defined the Z_ADJUST as parameter for PRINT_START in your script. If I want to handover this in the Super Slicer through the "Filament Settings" and not "Printer Settings", how can I do that?

It works if I add it as parameter to PRINT_START in the "Printer Settings" but don't know how to handover the variable out of "Filament Settings". Or is there a other way to do this?

Hi, thanks for your config files.

I don't understand the point in having _CG28 which homes only if needed, if homing_override already does that, on an axis by axis basis.

Is it a leftover from the past? If I remember correctly, few months I ago I didn't see the homing_override.

I have been compiling a my own Klipper configuration and have taken a few bits and pieces from this repository. Thank you for publishing your code. I want to upload my Klipper config to Github as well, unfortunately, as long as it includes pieces from your repository, I can't do this since your code doesn't include a license, which means it's "all rights reserved". I'd like to ask if you could consider choosing an open source license so that I'm allowed to publish my config with some of your code.

I recommend the GPLv3 license popular with many projects in the 3D printing space, but of course this decision is up to you. https://choosealicense.com/ gives you a good overview of open source licenses. Best practice is to include a copy of the license in a file called LICENSE in the repository.

In your README.md you have the following;

Your README

Error loading template 'gcode_macro PRINT_START:gcode': UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 2539: ordinal not in range(128)
Traceback (most recent call last): File "/home/pi/klipper/klippy/extras/gcode_macro.py", line 51, in __init__

If you use Python2 or Python3 you can still use one uniform method to translate special characters. JINJA2 template engine is meant to render HTML pages. HTML has special codes for special symbols.

So In your PRINT_START routine, you have the following:

    _PRINT_AR T="{"Bed temp: act %3.1f°C min %3.1f°C (target(%3.1f°C) - delta(%2.1f°C)) %s" % 
                    (actBed,targetBed,var.temp.bed,var.delta.bed,text)}"

which causes errors for python2 users. But instead of using the unicode character you could do this instead:

    _PRINT_AR T="{"Bed temp: act %3.1fºC min %3.1fºC (target(%3.1fºC) - delta(%2.1fºC)) %s" % 
                    (actBed,targetBed,var.temp.bed,var.delta.bed,text)}"

the º is the special coding for HTML page for ° or the symbol called masculine ordinal indicator

You can find all special characters representation for HTML at https://www.html.am/reference/html-special-characters.cfm

Here is another example, you have this in your CANCEL_PRINT:

      {action_respond_info("Extruder Temp to low heat to %3.1f°C" % printer.configfile.settings.extruder.min_extrude_temp)}

But it can be written as follows and will work no matter if you are using python2:

      {action_respond_info("Extruder Temp to low heat to %3.1f&ordmC" % printer.configfile.settings.extruder.min_extrude_temp)}

Here is the HTML code for the degree symbol

° = &ordm

Below is my output to the UI console:

Here is the code I used:

M118 Chamber Temp set to {S}ºC

I hope this helps other.

Why change motor current during homing/QGL moves? Does this help improve accuracy or is it to protect against toolhead crashes from causing damage?

This should be
SET_GCODE_VARIABLE MACRO=BED_MESH_STORE VARIABLE=save_at_end VALUE='"true"'
to work properly

Hi Alex,

sorry for another question/issue. I really like your config and it is running now really well. Only one thing is left and you can give me maybe an advise:

My printer is not going into sleep after a print, which means my controller fan stays permanently on until I manually shutdown my printer.

Do you have an idea where I should have a look at?

This is actually the opposite of an issue.
I just wanted to thank you for making all of this public.
These macros are insane!!!!
😃

Hi

if printer.quad_gantry_level.leveled|lower == 'false'

does not work for me.
What is different on yours?
leveled seems not be an attribute of printer.quad_gantry_level

Hallo ich bekomme leider diesen fehler in der Console.
Was habe ich in _USER_VARIABLE nicht definiert ?
Error evaluating 'gcode_macro _USER_VARIABLE:gcode': TypeError: unsupported operand type(s) for -: 'tuple' and 'float'