Error: Attempting to extrude with no tool selected.
-
@phaedrux
T0 at the end is not the solution.
What do you mean with remember in dwc?Another option?
-
@index4d When exactly do you see the error? What is it you do just before the error appears? As @Phaedrux has alluded, you need to have a tool selected (i.e. active) before you can extrude with it - that's exactly what the message is telling you. So if you try to extrude with tool 0, you need to select tool 0 first. Likewise if you try to extrude with tool 1, you need to select tool 1 first.
-
Another option?
Yes: study your macros! The error message appears when the Duet wants to extrude (e.g. print) but misses a tool it can use for that.
So, follow the macros involved, look where a tool is selected (e.g.
T0
,T1
, …) or deselected (T-1
). You might want to look for invalid tool numbers, too, but that’s freestyle.It’s just a matter of T commands, and instead of having us to scan all your macros, you could do that as well.
One final note: initially, that is after executing the config.g, there is no tool selected at all. That’s why @Phaedrux advised you to add a
T0
- just to be sure. -
@infiniteloop
scam with all of my macros?
I tried to solve the problem months ago with no solution. At this thread somebody advised me to post my macros/t-files. I´m sorry
Where can I find a list for the actual rules for this forum? I don´t want to make anybody angry.I would have done it my myself like many other problems. Sorry for asking - after spending tousands of euros in duet boards.
-
the error appears directly after tpost has bin finished. But it´s no problem to extrude. I mean I can print just normally.
Problem is that the tool switch isn´t working with this IssueSorry for asking you. I just couldn´t find my mistake.
Thanks
R.G. -
@index4d said in Error: Attempting to extrude with no tool selected.:
I don´t want to make anybody angry.
You didn't
And there is no need to be sorry for asking. That's perfectly ok. The thing is: you posted two of your macros, and they do not tell the whole story. If the addition of a
T0
in config.g doesn't help either, we can only guess - that's why @deckingman asked for a hint where exactly you get the error.If I run into such a problem, I try to narrow down on it with two methods:
-
I scan the macros for occurrences of gCodes who can possibly lead to the error I get - in your case, that's just the
T…
commands. This gives me an idea of the control flow: where do I select a tool, where do I deselect all of them, or where do I switch to another one … -
I insert debug messages into the macros. This tells me which macros are called before the error occurs.
You can add simple debug messages with a line like this:
echo "this is my macro XY"
More elaborate messages are possible, but as I just read, your <real> problem is different: your tool switch doesn't work? Could you be a bit more specific on this? If extrusion works (as you just say), is it with the wrong tool? Please keep in mind that we are miles away from your printer, we can't imagine what really happens.
-
-
@infiniteloop
Ok, I´ll try to put in the echo etc. and write back asapI know sometimes it´s hard to solve Problems from another place.
I think I´ll install the tool switch by myself like loots of issues with the duet boards.
But pls make a suggestion if I should describe my plan for a tool switch.like that
Thanks
R.G. -
Edit
When I turn on the Printers, it says it´s changing tool. -
@index4d With multiple tools and tool change macros, you need to put T0 P0 in your config.g and not simply T0. The "P0" will suppress the tool change macros from running.
-
@index4d said in Error: Attempting to extrude with no tool selected.:
But pls make a suggestion if I should describe my plan for a tool switch.
… Which lets me ask whether your tool switching works, at least 'somehow'. I don't have the faintest idea what mechanism you use to alternate between T0 and T1. In my case, I use tfree to move a tool out of the way and tpost to activate it. You use tpre instead, but at least the
M116
gCodes should be in tpost. As far as I can see, you happily mixed up commands to release one tool with others to prepare the other one: it's better to keep them separate. Did you read and follow the - well written - guidelines?After you got your gCodes sorted into the proper macros, it's time to test them, one at a time. If you call such a macro from the command line with
M98 P"myFancyMacro.g"
, you receive messages on syntactical errors. In addition, you can focus on your coupling mechanism - I think you call this with
M98 P"/macros/Coupler - Lock"
Did you test this one?
BTW, there's yet another way to test a macro: comment-out all lines you don't need in the first place, e.g. some moves and all heater commands. By this, you can add functionality step by step, which makes it easy to spot problems.