You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to incorporate specifically the bed_mesh_fast macro into my config. I went through multiple errors trying to only include that cfg, and finally just subscribed to the full git and included all. Granted, I have my own print_start which conflicts with the subcribed start_end. Removing that from my include returned error:
!! Error evaluating 'gcode_macro _km_print_status:gcode': jinja2.exceptions.UndefinedError: 'extras.gcode_macro.GetStatusWrapper object' has no attribute 'gcode_macro print_start_set'
Simply trying to use the start_end cfg for my build resulted in CHAMBER errors. I have my chamber set to 0c in SS as while I do have an enclosure I do not use chamber monitoring.
If I must use the supplied start_end cfg then having the option to # out the chamber additions in the KM would be nice to make it work. Granted I can't seem to figure out the simplest way to incorporate simply the bed_mesh_fash cfg into my set up without having to include stuff I already have mapped out.
(My issue being I assume if I subscribe to the git that any edits to the underlying cfg files will be arguments, vs edits to the KM file)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I was trying to incorporate specifically the bed_mesh_fast macro into my config. I went through multiple errors trying to only include that cfg, and finally just subscribed to the full git and included all. Granted, I have my own print_start which conflicts with the subcribed start_end. Removing that from my include returned error:
!! Error evaluating 'gcode_macro _km_print_status:gcode': jinja2.exceptions.UndefinedError: 'extras.gcode_macro.GetStatusWrapper object' has no attribute 'gcode_macro print_start_set'
Simply trying to use the start_end cfg for my build resulted in CHAMBER errors. I have my chamber set to 0c in SS as while I do have an enclosure I do not use chamber monitoring.
If I must use the supplied start_end cfg then having the option to # out the chamber additions in the KM would be nice to make it work. Granted I can't seem to figure out the simplest way to incorporate simply the bed_mesh_fash cfg into my set up without having to include stuff I already have mapped out.
(My issue being I assume if I subscribe to the git that any edits to the underlying cfg files will be arguments, vs edits to the KM file)
Beta Was this translation helpful? Give feedback.
All reactions