Error: attempting to extrude with no tool selected

deckingman · 27 Sept 2020, 21:00

@theshabobo said in Error: attempting to extrude with no tool selected:

Hi all. I just did the Duet 2 Wifi Upgrade on my printer and I am getting this error when I print any file generated by Simplify3D.

Note: This issue only occurs with S3D, not any other Slicers.
History: The printer was not having this issue with S3D before the Duet 2 Wifi conversion.

This issue will happen at random points during any print. It starts the print fine, then at a random point it will throw this error. Even with the same file, it's random! I have had it happen halfway thru the 1st layer, or on the 10th layer, or the 50th while using the same .gcode file.

There is only 1 extruder, labeled as T0. In the S3D Profile. T1 is the heated bed.

So from the OP and stepping back from everything else that has been said in this thread, the issue is clearly to do with the gcode files that has been generated by S3D because of this statement (quote) "Note: This issue only occurs with S3D, not any other Slicers".

Or more specifically, those S3D gcode files have commands which are inconsistent with RRF firmware because of this statement (quote) "The printer was not having this issue with S3D before the Duet 2 Wifi conversion".

Therefore, the solution must lie in the gcode file so it might be an idea if the OP made that gcode file available, then we can see what commands are embedded which could be triggering the problem.

This comment could be a clue (quote) "There is only 1 extruder, labeled as T0. In the S3D Profile. T1 is the heated bed."

If S3D is putting T1 commands in the gcode file to control the heated bed, these commands will be interpreted by the duet firmware as being commands to select or control tool 1. But there is only a single tool defined in config.g so any "T1" commands will refer to a tool which does not exist. So switching to T1 is likely to trigger the error "attempting to extrude with no tool selected" because T1 does not exist.

So my best guess at a fix (without seeing the gcode file) would be to correct whatever setting in S3D is causing T1 commands to be inserted in the gcode file.

Edit - Or maybe the unsupported M40 and M429 commands the S3D is inserting in the gcode file are triggering the error. These need to be fixed in the slicer settings in any case.

theshabobo · 27 Sept 2020, 22:35

@deckingman this has all my config files and a copy of the G-code.
https://www.dropbox.com/sh/yvealx81yym4kqh/AACMONG_FHO9DB7TqGrw7dyia?dl=0

Also, Note. I tried using different slicers, and got the error in all of them.
Feel free to take a look and let me know if you can see what's happening.

deckingman · 28 Sept 2020, 06:22

@theshabobo Ahh so it's changed from being something specific the S3D as per your first post, to being slicer agnostic. I'll take a look at the files later is I get chance. Meanwhile are you setting the slicer output "flavour" to RepRap" ?

EDIT - I've had a quick gander at the gcode file and none of the bad commands that are being reported exist in the file itself. There is only one "T" command which is "T0" at the beginning of the file - exactly as it should be. So my take on that is that the file data is somehow being corrupted as it is being read from the card. I have no idea why that should be. So it's over to someone more knowledgable that I. You could try disconnecting the PanelDue - at least that would narrow it down a bit.

T3P3Tony · 28 Sept 2020, 12:31

If it is data corruption to/from the SD card, one way to check if the SD card has an issue is to download the gcode file from the SD card using DWC and compare it to the original file that was uploaded.

theshabobo · 28 Sept 2020, 13:05

@deckingman Yes, it is RepRap. I disconnected the Paneldue and was able to do a 2.5 hour print with no issues and no Bad commands appearing in the logs.

I will be changing the PanelDue cable to a shielded one later today (after work) and trying again.

@T3P3Tony I don't believe it is an SD card issue, or file corruption issue as I tried with a new card and new file. I also verified the files are proper when compared to eachother.

lifeform · 1 Nov 2020, 12:27

@theshabobo hello, sorry for asking directly
did you solved it? i also have this problem, i change to stp lan cable and this problem still happened.
any tips ?

lifeform · 2 Nov 2020, 02:55

@dc42 said in Error: attempting to extrude with no tool selected:

must be no more than 0.1 ohms per conductor

hello, sorry for asking. i am not electronic guy so i alittle bit blank with 0.1ohms per conductor. what this means

i check i use stp lan cable to do it and i check in the internet it is have resistence about 150ohms i cannot use this cable?

Phaedrux · 2 Nov 2020, 03:01

@lifeform That would be measured with a multimeter.

Surgikill · 13 Mar 2021, 19:59

@theshabobo @Phaedrux @deckingman I'm having the exact same issue as described here. Same garbage commands, and tool being de-selected.

Current firmware versions:
Board: Duet WiFi 1.02 or later + DueX5
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.2.2 (2021-02-11)
Duet WiFi Server Version: 1.23

Has there been any other instances of this? I am using prusaslic3r and was not having this issue before the upgrade to RRF V3, which I performed a few days ago.

I am using a 4 pin paneldue cable. There is only one small section where it is near a stepper motor (probably 5mm cross section) and the rest of the cable is in an aluminum extrusion, so it should be shielded.

There may be interference somewhere, but I think that would have shown up before the upgrade to RRF V3

Baud rate for PanelDue is 57600

Phaedrux · 13 Mar 2021, 21:35

@Surgikill said in Error: attempting to extrude with no tool selected:

There may be interference somewhere, but I think that would have shown up before the upgrade to RRF V3

V3 definitely seems more sensitive to interference. You can try lowering the baud rate to make it more tolerant.

What paneldue firmware version are you using?

@Surgikill said in Error: attempting to extrude with no tool selected:

Duet WiFi Server Version: 1.23

Unrelated, but the wifi version for 3.2.2 is 1.25.

Surgikill · 13 Mar 2021, 21:53

@Phaedrux Paneldue firmware is 3.2.11

I'll look into updating wifi server. I thought that all was updated with the combined firmware when I updated to 3.2.2.

Surgikill · 13 Mar 2021, 23:40

@Phaedrux Looks like the baud rate change might have fixed it. Any recommendations on wire? I want to re-wire some of my stepper motors with shielded wire to cut down on interference, can't seem to find any good wire.

Phaedrux · 13 Mar 2021, 23:46

Any decent gauge wire should do. I like to do a braid or twist which seems to help with crosstalk without shielding. I hear people mention silicone wire as nice to work with. I've only ever used some cheap spools of 22 gauge wire on amazon for low current DC applications. Nothing special. And for AC wiring some larger gauge stuff from the local auto parts store.

Surgikill · 14 Mar 2021, 00:22

@Phaedrux Well I lied, still getting communication issues. I replaced the SD card with a brand new one, and I moved the stepper motor wire that was near the paneldue wire so there is 4+ inches of separation. The only other wire near it is a mechanical endstop switch. Any other ideas? The paneldue does not have a SD card in it.

Phaedrux · 14 Mar 2021, 00:28

How long is the wire run?

Surgikill · 14 Mar 2021, 00:33

@Phaedrux The 4 pin wire is 1000mm long. I bought it from filastruder, who also offers a 3000mm cable, so I figured the 1000mm cable would be fine.

https://www.filastruder.com/products/paneldue-7i?_pos=1&_sid=6b2701afe&_ss=r&variant=2154915528719

Phaedrux · 14 Mar 2021, 00:34

@Surgikill Yeah that should be within spec.

I'll try and find out what was ever determined the last time this was reported. It's been found a few times but I don't think there was ever a definitive cause for why it becomes apparent in RRF3.

Can you measure the resistance of the wires in the cable?

Surgikill · 14 Mar 2021, 00:36

@Phaedrux Thanks. I'm still going to rewire this just to tidy it up. Maybe it will help.

Phaedrux · 14 Mar 2021, 00:43

@Surgikill "The length of the 4-way cable is not critical, however the resistance per conductor should not exceed 0.1 ohm. "

Surgikill · 14 Mar 2021, 00:53

@Phaedrux I can measure it and see. Definitely still having issues with my tool being de-selected.