Hi,
Unfortunately, this button does not currently exist.
But: You can write a macro that you save directly in the /macros folder, e.g. ATX toggle.
if state.status == "off"
; turn on power
M80
elif state.status != "processing"
; turn off power
M81
This will then be displayed on the Control tab of your PanelDue.
@droftarts I have found the issue, I suppose this is one for SuperSlicer...
The g-code exported from SuperSlicer 2.5.59 contains a M204 P0 T0. This was certainly not the case in the past.
I changed the following: Printer Settings > Machine limits > How to apply limits = "Disable"
Before this, it was set to "Use only as safeguards", but that and even "Use also for time estimate" gave an output of M204 P0 T0 ?!
I tested it with the change and can now print like normal (even on RC3). So case closed for you guys 
Since the pin logic of the ATX control pin can now be inverted (thanks for that, btw!) I started to implement M80/M81 to my tool changer setup with a MeanWell power supply. While this is working so far, I have a observation to share:
Every time M81 executes I get the following warning message in DWC and PanelDue:
Warning: 12V under-voltage event (9.4V)
IMO this should be suppressed because this is exactly what should happen in this case. Just a small detail but it could clarify some confusion if implemented. 
@brian said in Adding a Pause, continue prob:
{REPLACE "\n; layer 18, Z = " "\n; layer 18\nG1 X0 Y0\nM300\nM0 Click to continue\n; layer 18 "}
Where is this generated, what slicer are you using?
From what I can see the g-code produced from this containes a "M0" - that says: Stop or Unconditional stop (see docs here)
So the printer is actually doing what you told it to
if you want to pause the print at a specific height you should use "M226" in your g-code (see here)
Hi together,
I am in the process of refactoring all the macro files of my E3D ToolChanger - it got quite some conditional gcode happending.
As for tool changing, each tool has its own tpre#.g, tpost#.g and tfree#.g, despite having almost the same content. To eliminate this redundancy I created a 'global' tpre.g, tpost.g and tfree.g for all tools. Now I call each of those macros with a parameter (param.T).
With this change I can put together a common logic for all tools and call it in each specific file via 'M98 P"tpre.g" T#'.
Example of the 'global' tfree.g:
; tfree.g
; can be called with param.T: tool number to be freed
; abort if axes are not homed: 0:X 1:Y 2:Z 4:C
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed || !move.axes[4].homed
M291 T5 P"Please home axes before a toolchange" R"Cannot change tool"
abort
; create vars
var toolXpos = 0
var toolYpos = 0
; set tool dock position (and check for valid num)
if param.T == 0
set var.toolXpos = -157.7
set var.toolYpos = 115.5
elif param.T == 1
set var.toolXpos = -67.5
set var.toolYpos = 115.7
elif param.T == 2
set var.toolXpos = 61.3
set var.toolYpos = 115.3
elif param.T == 3
set var.toolXpos = 170.0
set var.toolYpos = 115.2
else
M291 "var.toolXpos or var.toolYpos was not set" R"error in tfree.g"
abort
; drop the bed
G91
G1 H4 Z5 F1200
G90
; move to location
G53 G1 X{var.toolXpos} Y55 F40000
; move in
G53 G1 Y110 F4000
; move slowly to final position
G53 G1 Y{var.toolYpos} F2500
; open coupler
M98 P"/macros/Coupler/unlock.g"
; move out
G53 G1 Y113 F2000
G53 G1 Y110 F4000
G53 G1 Y100 F6000
Example of tfree1.g:
; tfree1.g
; called when tool 1 is freed
M98 P"tfree.g" T1
This works well so far, but I would like to get rid of the individual toolchange files.
Therefore I would like to discuss the following ideas for calling tool change macros in RRF (changes are bold) :
If another tool is already selected, run macro tfree#.g where # is the number of that tool. If tfree#.g is not found, run tfree.g (with parameter T = #) instead.
If another tool is already selected, deselect it and set its heaters to their standby temperatures (as defined by the R parameter in the most recent G10/M568 command for that tool)
Run macro tpre#.g where # is the number of the new tool. If tpre#.g is not found run tpre.g (with parameter T = #) instead.
Set the new tool to its operating temperatures specified by the S parameter in the most recent G10/M568 command for that tool
Run macro tpost#.g where # is the number of the new tool. If tpost#.g is not found run tpost.g (with parameter T = #) instead.
Apply any X, Y, Z offset for the new tool specified by G10
Use the new tool.
What do you guys think? Is this a good idea or am I proposing a solution where no one has a problem?
@oliof I was about to, but someone was faster (issue was from 3 weeks ago). It even seems fixed for the next release:
https://github.com/supermerill/SuperSlicer/issues/4048
@chrishamm said in Plugin installation failed: package manager exited with code 67:
PS: That's a DCS log excerpt and nothing from the root DPS service.
Sorry, I copied the wrong output ... I have edited my post above
@Exerqtor have a look at this:
Added support for tool macro fallbacks (commit)
It is already included in the latest version (3.5.0-beta.4).
