Well, I think I've got it, but there may be a tweak I could use to improve it, but as I've only got one spindle/tool this will probably do. This pause.g file works and saves the spindle speed to the defined variable:

set global.savedSpindleSpeed = spindles[0].active echo "Spindle speed saved at " ^ {global.savedSpindleSpeed} ^ "RPM" G1 Z{max(move.axes[2].userPosition+5,move.axes[2].max-5)} F2400 ; move the Z axis to a safe height G0 X273.5 Y560 ; move XY to a safe place M5 ; turn the spindle off

...and the resume.g file turns the spindle back on, although I think there are a few spurious lines in it now. I'll deal with that in the morning!

Thanks @OwenD and @dc42 for your help with this 👍 👍

@nightowl999
See the other thread.
I suspect you have no tool defined when the resume starts.

@oliof - I'll do that and share with this forum in a new post when I get it in place. I'm a little scared of the kibbitzing part because I'm a poor github repo manager. My usual response to github requests for changes is to stop sharing things on github. Also, a lot of the macros I write are to get me over a specific small issue and then I don't use them much after that and my interest in spiffing them up kind of dies away. But I do try to put in a lot of comments to explain what I'm trying to do so they might be useful inspiration for other people to grab and run with.

You can use M119 to test the state of the endstops.

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_endstops

@hlwerschner
Not much I'm afraid. I wanted to engrave some acrylic strips and animate them with NeoPixels. But i got so distracted by commissioning and upgrading the new Co2 laser, that I almost forgot, why I bought it 😉
In the meantime, I stumbled across a four color LED strip, which looks quite nice, too.
Now I'm trying to figure out, if designing a 4-fold NeoPixel LED strip would be possible. So I'm looking into the smallest possible footprint of programable LEDs.
4-colorAcryl.jpg

I should mention, that this isn't my work. I found it on a discord channel about the K40-laser from the member @raineroe

@owend That G4 should do it! Everything else remains idle. Thank you!

@infiniteloop Sorry, I missed your earlier answer. Your solution works. Thanks a lot for your help.

@Arnold_R_Clark No.

@mikeabuilder BtnCmd is a DWC plugin - it runs in the browser. Everything I showed above was generated by the plugin and runs in the browser (with the exception of the Global Variables). When the user selects an option, the value of the option is assign to the global variable by executing the standard command:

set global.varname = ####

The Global variables can be used in Macros and other gcode.
BtnCmd does not work on Panel Due.
There is a wiki if you want to see the full range of features it offers.

If you want to learn about how to write DWC or DSF plugins here is a good place to start.

@taylo708
I was assuming you were not getting the humidity readings from the sensor.
If you have the sensor set up to display the humidity then you can use daemon.g to control the heater.
I'd imaging you'd need to set up several global variables in config.g including one to ensure you can turn the heater on/off

global ChamberHeaterOn = false global lowHumidity = 25 global midHumidity = 50 global highHumidity = 75

Then in daemon.g use something like this (change the sensor value)

if global.ChamberHeaterOn = false M140 S-273.1 ; switch off heater elif sensors.analog[2].lastReading <= global lowHumidity M140 S40 elif sensors.analog[2].lastReading <= global midHumidity M140 S60 elif sensors.analog[2].lastReading <= global highHumidity M140 S80 else ; whatever you want to do if over the high value

And set up a couple of buttons to set the global to true or false to offer manual control when needed

@deckingman Thanks a ton, sir

@owend said in Input debounce setting:

G4 P10 ; delay 10ms to debounce if sensors.filamentMonitors[0].status="ok" echo "switch bounce detected - error cancelled" M99 ; break out of macro if sensor value is zero again (bouncing)

This seems to have worked. I haven't fully tested it yet, also I needed add a filament-error.g where I put this code (incase someone comes across this post in the future) I was just using the pause.g for the filament runout.

@bludin
About the only way I can think to do it in software is a bit convoluted.
EDIT: on second thought no need for half these steps
1: Use M571 to control an output pin . There doesn't need to be anything connected to it. relay or mosfet module
2: Connect to output of the relay to a GPIO pin
3: Create a trigger.g file for both rising & falling trigger events to update a couple of global variables with the led state required and current time.
4: Monitor the output pin in daemon.g to turn the led on and off when the sate is off and the current time > set time plus delay

Monitor the output in daemon.g.
Turn on the led if it's high and also set the stop time to "now + 5 seconds"
If it's low and current time is > stop time, turn off LED

You'd need to do the whole lot in a while loop if you need timing less than 10 seconds as that's the default cycle time for daemon.g

@aronmeszaros thanks for pointing that out. I've corrected it.

@oliof said in DUEX 0.11 FAN 5:

@paolozampini1973 after you update to 3.4, you can try heater feedforward https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m309-set-or-report-heater-feedforward which raises the heater power for higher speed prints.
Alternately you can adjust the heater fault detection using M570 https://docs.duet3d.com/User_manual/Reference/Gcodes#m570-configure-heater-fault-detection but since this is a critical safety feature I would only use this as a last resort. It does allow you to adjust the excursion limit as you requested.

Thanks for the very kind reply

Also take a look here: https://forum.duet3d.com/topic/22729/automating-sequenced-prints-and-repetitions

Update:

My script works with a few little tweaks and the thought that you safe the z offset for your main tool modules in your config an if you change your tool through a script it performs the z probe of the tool and saves it internally. If i use a tool more frequently like Tool4 i can safe it in the override with M500. After a restart the main tool should be taken from the config and other tools must be changed trhough the script.

The working script looks like so:

T-1 ;deselect any tool G28 ;home all M400 ;wait for current movement to finish G1 Z65 F800 ;move bed to a save height (65 as high as the filament storage) where no tool can interfere T4 P0 ;select tool 4 without running macros (P0) G1 X295 Y72.9 F4000 ;move TCP over the probe M400 G30 K2 H-0.8 S-2 ;Probe the tool Z offset at the current XY position and change it so Z is 0 M500 T-1 P0 ;deselect tool G28 U V Z ;home U and V

The endstop switches where set as new z probes:

; Tool Probes M558 K1 P8 C"duex.e5stop" H80 F200 ; Set left z probe with an expected 80mm probing height a probing speed of 200 mm/min M558 K2 P8 C"duex.e6stop" H80 F200 ; Set right z probe with an expected 80mm probing height a probing speed of 200 mm/min

I might put an output of the probed offset in the console so people can copy it from there