@dc42 is it implemented or in the roadmap?

@DavidG_68kg_PLA said in Marlin M86 counterpart: reduced idle temp:

while the Machine is in sequential pause midprint

What you you mean by "in a sequential pause"?

Pausing in RRF executes the pause.g macro (or for some types of pause an alternative macro if present, such as filament-change.g). It's common to set the hot end heater to standby in pause.g and then to set it back to active in resume.g.

@curieos said in Save/Recall Heater State:

I'm not sure, I had some concern about changing values that aren't necessary to be changed. It feels like bad practice, but I can't think of a real problem it would cause.

It will not cause any problems if my experience, using firmware 3.4.6, is any indication and I use variables extensively, both local and global. Currently on my 4 tool printer I have 70 some global variables and many things get updated in a group regardless of how many values within that group may actually have changed. No problems to date.

Frederick

I have a new application for tapering extrusions that might make this feature request more popular. Moves that taper z height with fixed extrusion width will facilitate the production of invisible seams.

I have proposed a new feature for PrusaSlicer whereby it would make seams that I call scarf seams where the seam is spread out over complementary tapers. The feature request is here.
The scarf seam could be made entirely b y the slicer, but it is my opinion that the firmware should be responsible for the tapers. That would allow me (and others, presumably) to easily use tapered extrusions for other purposes.

My proposal is for an extra parameter in moves to allow the extrusion to start at one value and end at another.

@oliof said in "Safe" Z Probe:

@fcwilt if you set the Z axis values to 0:25 rather than 175:200, does the behavior improve? if yes, maybe there is an issue in how rrf determines the maximum length moved before aborting the homing move.

I will perform that test after diner and post back here.

Frederick

That would be great. There is so much to calibrate with different materials etc.. So having something to support it would be great!

@daninet filament sensor and other errors already raise error events, see https://docs.duet3d.com/en/User_manual/RepRapFirmware/Events -- these can be handled in their own macros.

@dc42 Okay, thanks for the insight, I'll look forward to that lower current model!

@dc42 I tested Secondary Dive Height as well and it's wonderful, but it disables Secondary Dive Speed.

@MaxGyver i use 2 kinds of probes on my CNC- an aligator clip to connect to the tool/touch-off plate for Z and a baby reinshaw type probe for X-Y.

the touch off plate will probe twice for setting Z.

the X-Y probe i think will only touch once.

I am not currently near that machine but will be over the weekend. i will try to make some experiments and report back.

sinneD

@deckingman been a long time, hope you are doing well. Watched a lot of your more recent videos last week to get caught up on "fun crazy machines".

Thanks for that link. My search didn't find it, likely because they didn't say "binary" in the title.

@chrishamm

Hmm.

It is working now.

All is good.

Thanks.

Frederick

@jay_s_uk said in A couple of idea regard endstops:

@fcwilt use g92 to set a position other than the min/max axis limit

I can do that sometimes. But when the endstop is past the min/max limit that causes its own issues.

Thanks.

Frederick

@dc42 great, I was searching for "slot" and "position". Even better!

@fcwilt originally i was going to put an address on each tool head so that the printer would auto configure , but i didnt have enough inputs free on my control board , so ended up doing the macro route , its still something im going to look at using an analogue input 0v=tool 1, 1v = tool 2 etc this way i only use 1 input .
then you could did the setup via global variable's or macros , i like the macro route as all the settings for the too head are in one place .

@droftarts said in M140 question:

Probably worth checking it's not impacting memory too much! Check available memory with M122.

At what point should I worry?

My Duet 2 machines report "never used" as 6K , the Duet 3 machines report 22K to 90K.

Thanks for mentioning it.

Frederick

@dc42 I tried that but M400 introduces a weird stutter:
PXL_20231019_120452795.jpg

Same gcode, left one uses G4 before M569.4, right one uses M400