@dellfer a possible way around this would be to define it as an extruder. with a very large number of steps/mm and then create a tool with both extruder drivers. That way when its extruding the stepper driven pump will turn as well. Some issues with this is the cooling will be related to the extrusion feed rate. and retractions will make it turn the opposite way!

I am moving this to the firmware wish list, but I don't think using steppers as fan motors will be a high priority to implement

@danzaywer I would rather have the slicer tell then firmware what sort of movements are coming up, e.g. outer perimeter, other perimeter, infill, bridging. Then the firmware could select the correct fan speeds, print speeds etc. ignoring the ones passed by the slicer. This would allow me to run exactly the same GCode on all my printers, as long as they all have the same nozzle size.

@pcr said in Brainstorming for mesh bed limits.:

@phaedrux that's what I want to say. I had this problem

Can you elborate?

@dc42
Ahh, that is great, thank you so much!

@dc42 said in Adding support for bus-based temperature sensors:

There are two bus-based protocols that have higher resistance to interference: CAN bus and Lin bus

Is RS485 signaling useful here?

Thanks @P3P3Tony. I see it in the meta commands page in the wiki. Should heave read more closely. Looks like I need to do a fw update.

this can be marked closed and resolved

@maxgyver hi Max, you can't override built in gcodes with macro files.

You can speed up the execution of the fan control in deamon.g by putting a while loop (with a wait of a second in it so it does not run continuously!).

@cncmodeller thanks, we are discussing how to work with filament width sensors sensibility.

@dc42 said in Multiple Z probes and multiple Z axis for IDEX:

We already support using axes other than X and U to define the grid, so using U and Y for one would not be a problem.

Is it possible to add one more axis to define grid such as V because the new machine I’m designing it should be coreXYUV with double gantry where it can print completely 2 different model at the same time

Just chiming in to say I am also interested in this feature and would greatly appreciate the flexibility.

@t3p3tony Ah OK, so could be around 6 months then, I'll go UCCNC in the meanwhile.

@t3p3tony Much appreciated. Thank you!

@merlin246 you could do that with daemon.g and querying the object model, no code change required.

@dc42 👍 👍

I was wondering, if a FW-solution for this problem would also help implementing infinite rotation for rotary axes?
Two flies with one clap

@bubblevisor said in Defining Bed mesh probe points to avoid neodymium magnets:

@fcwilt Thanks for the info. Could you explain how you would "edit out" specific problem probe points?

This is what I have in the config currently M557 X21:216 Y28:200 P4 . But I would like to adjust the position of a few of the points.

Hi,

Sorry I wasn't clear.

You could view the height map in the DWC and make note of any points they were clearly incorrect and likely the result of the probe reading being influenced by the magnets.

By noting the XY position of the point you could edit the height map .CSV file and assign a Z value to that point that made sense based on the Z values of the points around it.

Frederick

@adhanabal If you want to power your extruders off when not printing you could just use M18 E0 at the end of a print or possibly in one of the standard macro files (you could even put it in daemon.g along with a suitable test to see if you are not printing).