Which tool is enabled after startup?

taconite

@dc42 any idea of the behavior?

dc42

A macro containing just a T0 or T1 command works for me. Tested on two machines.

taconite

@dc42 okay this is super strange
have you had a look at the video?
I will try it again but just have no idea why that is

taconite

holy moly! I finally made it work. Thank you for all your support. In my tpreX.g macros I had an abort command which aborted the tool change when there was still a tool in the effector. I removed it and now it is working.

The strange thing is that it was working when manually selecting a tool on PanelDue or on the DWC and I have no idea what kept it from working when running a macro with Tn

T3P3Tony

@taconite what was the abort command?

taconite

I use the abort command (https://duet3d.dozuki.com/Wiki/GCode_Meta_Commands) to abort things that should not occur (e.g. tool still there after parking) - maybe there is a better way to do that

EDIT: @T3P3Tony

T3P3Tony

@taconite so you had some "if <expression> ... abort" logic to check for certain conditions and then abort if they were true or false? Maybe the issue was the expression was evaluating to true (or false) when it should not have been.

taconite

I had it this way (tpre.g)

if no tool in effector
      pick tool
	
else {}
	display message "Sill tool in effector"
	abort

I removed the abort. Everything was correct but the execution of a macro with a Tpren.g just did not work with the abort

jay_s_uk

@taconite try it with break rather than abort

K01571N3N

Hi, this is what i have been thinking and i need this for my toolchanger.
Duet 3 6HC, 3HC and Raspberry pi.

If i write to console

M560 P"0:/sys/test"

or run macro like that

M560 P"/sys/test"
<!-- **EoF** -->

or whatever else, "Error: M560: Can't open file test for writing" appears...

If i write

M98 P"0:/sys/test

it will run that macro.

Is Raspberry pi somehow causing the trouble here or what?

K01571N3N

@dc42 @T3P3Tony Do you have any idea for my problem?

Phaedrux

@K01571N3N Might be better idea to start a new thread with exactly what you're trying to do. Include firmware version details etc.