Bought a Fabtotum on Kickstarter, received it in 2015, and got my 3D Printing training with it. Good training, since it learned me by practice all the mistakes to avoid as a user, but also all those to avoid as a designer.
For instance, it stopped using it after the ribbon broke due to trailing on the bed and colliding with printing part. Collecting dust since 2 years since.

I decided recently to give it a rebirth by changing almost everything except COREXY mechanic, the most valuable thing in FT in my view.

Removed all guts, including the RPI and heads, printed parts for X end stop, new bowden E3D V6 / TITAN based with most advanced parts, and it worked almost at the 1st run.
I will now use this as a test platform for new heads, water cooled, TITAN direct drive and more.

@fcwilt Yes, I print tiny parts ( custom gears and connectors), and I need minimal entry points on my objects to allow best external mechanical interface possible.

Therefore I need to purge my nozzle between each part to ensure identical start conditions.

And since I need many parts, I stuff my printing bed with as much as possible parts.

@dc42 Many thanks for advice, will keep u posted when done.

@Phaedrux I am thinking about current, both peak and hold, since it's a CNC, not a 3D printer.

I want to rebuild a ROLAND CAMM3 machine, which seems to have 3xNEMA17 X Y Z.

Do I need a DUET3 6HC, eventually associate 2 drivers for one stepper or a DUET 6XD and some external stepper drivers like DM542T?

Many thanks for advice

@dc42 So I solved the problem by putting a simple macro that shows up on Panel Due main page.
This toggles the variable that control the cooling. Then I can modify it while a macro is running in a loop.

Regarding daemon.g, I think user should have control on the 10 sec delay. I understand the reason why this is done that way, but this greatly limit the usability of this interesing functionality.

Many thanks again for help

@dc42 Yes, but it will fire only at 10 sec interval, plus the G4 parameter, plus more, which is far too long.
I understand the reason why you stretched this delay, but in my case, I just scan the print area with the fan running at100%, nothing to do with print quality. BTW it cools the part, dual extruders and bed 40% quicker on my bigbox.

For instance, a G4 S4 will end up with 4 +10 minimal delay. Since I cannot change the 10 sec delay, it is useless. Would need as low as 100 ms to be workable for my use case.

BUT it works when I use the DWC console (set global.cool_part=false) while printing through Octoprint on a RPI 4. There is hope there, except I have to switch from Octoprint to DWC, what I try to avoid.
I don't dislike DWC, but I use mainly the PanelDue rather than the web interface once launched the print through OCTOAPP on mobile, and setting up a global variable through the panel is not very easy and I don't see how I can do it through octoapp.

Maybe I miss something on panel due ( custom button with a meta command on main page possible? )

Many thanks

@cosmowave Thanks for the tip, but I cannot wait 10 Sec between action not put a loop inside the daemon.g code, since my code is scanning a a certain rate to cool down, and I need also to deactivate the daemon.g from the outside => more global variables..... Since this 10 sec is hard coded, I'm stuck....

I wrote a macro to cool down parts after print, using the fan and the XY part trace to scan the entire printed area of the bed until head temperature reach an acceptable value. The idea is to accelerate part cool down, thus reducing wait time.

However, this process should be interrupted manually if the cooled part is easily removed from bed without damaging it.

I run a macro to do this, however I would like to interrupt the macro by setting a flag from command line, something like set global.part_cool = false. Macro does something like
"while (global.part_cool and temperature> something)
scan_the_bed
"

Using G4 P100 in the loop doesn't solve the problem, since G4 does wait, but don't allow me to send command to set a global variable until macro end, which is precisely what I want to avoid.

Using daemon.g won't solve the problem, since it will execute a set of commands the same way, only at regular intervals.

Question: Is there a command/trick that would allow this, other than wiring a hardware button somewhere and using it as a trigger?

Many thanks for help

+state.time converts the present time to an absolute 1970 value.
as the documentation says:

• int->int, float->float Unary +
• DateTime->int Converts a date & time value to a number of seconds since the datum. Available in RRF 3.4 and later.

It is either an unary operator or a function.

When I use it in expression if(+state.time - global.last_time) I get an error

"Error: in file macro line 14 column 17: meta command: expected numeric or enumeration value after '+' " which means the it doesn't recognize the + operator function in this context.

Solution is to declare a var then use it at the same place.

Is it a desired behavior or did I miss something?

Many thanks

@phaedrux

Hi

This is a copy of the screen

The green one is the faulty guy

@phaedrux I did not record the graph on DWC since I mainly use Octoprint as a GUI.
I don't think it's an artefact from octoprint but I'll check next time it happens and let you know.
let's see