@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.
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?
@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.
There are no array variables yet, and no vector variables. Here are some ideas:
You could pack several integer variables into a single integer variable, but take care not to exceed 2^31-1.
You could create 9 axes in total, then use the offsets of each axis in one or more of the workplace coordinate systems as 9-element arrays
@SanderLPFRG Happy to help. Plus it looks like the probe is really nice and accurate.
Ive always been personally interested in loadcells as it looks like it fixes most of the issues I have with Piezo sensors. Any advice on where to get started?
