Open amv101 opened 2 years ago
Are you using the pause and resume macros specifically for ERCF?
It's probably related to being in relative vs absolute positioning somewhere in your macros
There is definitely something up with that setting. From some searching, it has something to do with the probe offsets and the mesh possibly. My Delta has a print radius of 150mm and a print height about 340mm. I run the delta calibration and mesh at 130mm.
When I use this setting, the issue goes away…
[gcode_macro PAUSE]
rename_existing: BASE_PAUSE
gcode:
{% set x_park = printer.toolhead.axis_minimum.x|float + 55.0 %}
{% set y_park = printer.toolhead.axis_maximum.y|float - 55.0 %}
Now it will park at -95.00 95.00 without any issues.
Maybe I should run the delta calibrate and bed mesh with the same radius as the print radius?
Are you using the pause and resume macros specifically for ERCF?
Yes... I run the "pause" command from the Octoprint terminal.
Are you using the pause and resume macros specifically for ERCF?
Yes... I run the "pause" command from the Octoprint terminal.
That’s not what I asked. Did you replace the klipper pause ad resume macros with the ones from the ERCF GitHub?
Are you using the pause and resume macros specifically for ERCF?
Yes... I run the "pause" command from the Octoprint terminal.
That’s not what I asked. Did you replace the klipper pause ad resume macros with the ones from the ERCF GitHub?
I assume so, but I am pretty new to Klipper. I never added any pause macros to my printer.cfg file, except for the ercf macros. I added the ercf macros and then type "pause" into the terminal via Octoprint.
My cfg file is posted above with the macros I have. Would there be another place to check for conflicting klipper pause macros?
The "ercf compatible" pause and resume macros are in the "client_macros.cfg" file on the ercf repo (klipper file folder).
Those are the one you need to use with the ercf (or adapt the ones you have to contain the ercf stuff).
The "ercf compatible" pause and resume macros are in the "client_macros.cfg" file on the ercf repo (klipper file folder).
Those are the one you need to use with the ercf (or adapt the ones you have to contain the ercf stuff).
Thanks for the help. I posted my cfg above. Did you see an issue with how I added the ercf macros? Not sure why I am getting the error on my delta. Does it have something to do with my bed mesh radius, delta calib radius, and delta print radius being different?
The "ercf compatible" pause and resume macros are in the "client_macros.cfg" file on the ercf repo (klipper file folder). Those are the one you need to use with the ercf (or adapt the ones you have to contain the ercf stuff).
Thanks for the help. I posted my cfg above. Did you see an issue with how I added the ercf macros? Not sure why I am getting the error on my delta. Does it have something to do with my bed mesh radius, delta calib radius, and delta print radius being different?
First, you should really split your printer.cfg into dedicated files (like "steppers.cfg", "bed.cfg" etc.). This will give you a much better clarity on your printer config, and less prone to errors.
Concerning your issue, I never own a delta, so I don't really know their specificities. If you think it's related, just change the pause park position (i.e. " {% set x_park = printer.toolhead.axis_minimum.x|float + 5.0 %} {% set y_park = printer.toolhead.axis_maximum.y|float - 5.0 %}" to something else that will suit your printer.
Also, how are you g-files? are the moves in those in absolute or relative positioning? because you want to match the positioning mode of your gcode files of course. In principle it's in absolute, hence the G90 at the end of the RESUME, but if you're in relative mode...
That being said, I'll play with the pause and resume macros to snapshot the positioning mode before used during the print, so it should avoid any future problem like that. Hopefully pushed by tomorrow
I believe this to be correct: If you have definitions for PAUSE and RESUME in printer.cfg and you import client_macros.cfg prior to the definitions the macros in client_macros.cfg will be overridden. Also in general if two definitions for the same item occur in a ".cfg" the first one will be overridden and ignored.
I am running ercf on a custom Delta printer. When a clog is detected, or there is no filament in the cart, I will get a "Move out of range" error when the printer goes into the pause state. I have tried reducing my delta radius by half, to see if there was an issue with the probe offset, but I still get the same error.
Any ideas what the issue might be?
Error from the Octoprint terminal when sending "pause" right after homing / moving down
printer.cfg