@dc42 I think so. I don't have the table here, but I'll probably be going to visit it later today. I'll check then. IRIC, the last time I updated firmware was about a year ago.

@Proschi78

I would like to know the same 🙂

could someone share what a daemon.g would look like for a heated chamber only to 80c tru a switching 3-32 vdc to SSR at mains VAC
i am getting way to many alarms in the 3.4 and wants to see 1.7C/sec without daemon.g and the chamber is expected to take about 10 min from cold chamber to set point and these types of alarms are no good for a chambers so i am here looking at daemon options to do so should someone have an example or kind of what it should look like?

@mikeabuilder
Great job! 👍 👍

@pcr
A single macro that could do all of that would be unwieldy and have probably too many parameters that needed to be passed to it to be user friendly.
You could easily modify these to cater for most of your examples, though input shaping type probably isn't practical until we have arrays.

@ww1g16
That's a good thing to have, but I thought, we'd have to home XY at once for a CoreXY?
Another thing is the 'backoff' move. Shouldn't you increase the motorcurrent first, to make sure this move doesn't cause an error?
Why do you abort the macro? Instead increase motorcurrent on every iteration, until it is high enough.

@spoonunit
Nice work. I'm looking forward to trying some of this out.

I run some fairly large production runs on my printers.

Thank you for sharing this.

@sacred-serpent
You would typically put it in the macros folder

@OwenD thanks a lot, I have asked @droftarts to look at how to incorporate this in the documentation.

There are no array variables yet, and no vector variables. Here are some ideas:

@fcwilt Thanks Frederick!

Is there a relatively easy way to edit these macros to work if one doesn't have a filament sensor?