Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Error: attempting to extrude with no tool selected

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    11
    67
    9.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • theshaboboundefined
      theshabobo
      last edited by

      yes, let me try that.

      1 Reply Last reply Reply Quote 0
      • theshaboboundefined
        theshabobo
        last edited by

        I changed out the SD card with a new out of the box class 10 one. This was my output of the eventlog. The print did complete.

        2020-09-27 00:25:13 Event logging started
        2020-09-27 00:25:35 Error: Bad command: J184 M409 F"d99f"*71
        2020-09-27 00:26:15 Error: M409: control character in string
        2020-09-27 00:26:56 Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.
        2020-09-27 00:31:03 Error: M409: control character in string
        2020-09-27 00:36:36 Error: Bad command: s73 M409 F"d99f"
        2020-09-27 00:36:37 Error: Bad command: `M409 F"d99f"
        2020-09-27 00:36:38 Error: Bad command: >0M409 F"d99f"+72
        2020-09-27 00:36:56 Warning: M609: Command is not supported
        2020-09-27 00:37:00 Error: Bad command: M<09 F"d99f"
        2020-09-27 00:37:06 Error: Bad command: ^403 M409 F"d99f"*77
        2020-09-27 00:37:11 Error: M409: control character in string
        2020-09-27 00:37:55 Error: M409: expected string expression
        2020-09-27 00:38:19 Warning: M40: Command is not supported
        2020-09-27 00:38:26 Warning: M429: Command is not supported
        2020-09-27 00:41:23 Error: M409: control character in string
        2020-09-27 00:41:47 Error: M409: control character in string
        2020-09-27 00:41:55 Warning: M429: Command is not supported
        2020-09-27 00:45:03 Error: Bad command: $M409 F"d99f"
        2020-09-27 00:48:07 Error: Bad command: O409 F"d99f"
        2020-09-27 00:48:23 Error: Bad command: O628 M409 F"d99f"*70
        2020-09-27 00:49:36 Error: Bad command: `m409 F"d99f#*78
        2020-09-27 00:51:28 Error: Bad command: < M409 F"d99f"
        2020-09-27 00:53:12 Error: M409: control character in string
        2020-09-27 00:53:52 Warning: M40: Command is not supported
        2020-09-27 00:54:20 Error: Bad command: ?17 M409 F"d99f"
        2020-09-27 00:54:48 Error: M4: Command is not supported in machine mode FFF
        2020-09-27 00:55:40 Error: Bad command: `M409 F"d99f"
        2020-09-27 00:57:00 Error: Bad command: `M409 F"d99f"
        2020-09-27 00:58:32 Warning: M40: Command is not supported
        2020-09-27 01:00:28 Error: M4: Command is not supported in machine mode FFF
        2020-09-27 01:02:05 Error: M409: expected string expression
        2020-09-27 01:02:53 Warning: M40: Command is not supported
        2020-09-27 01:05:57 Error: Bad command: :91 M409 F"d99f"
        2020-09-27 01:11:05 Error: M409: expected string expression
        2020-09-27 01:12:05 Error: Bad command: 3 M409 K"job" F"v"
        2020-09-27 01:14:26 Error: Bad command: 018 M409 F"d99f"
        2020-09-27 01:15:22 Error: M409: expected string expression
        2020-09-27 01:15:34 Error: M409: expected string expression
        2020-09-27 01:17:58 Error: M4: Command is not supported in machine mode FFF
        2020-09-27 01:18:34 Error: Bad command: (M409 K"job" F"v"
        2020-09-27 01:20:38 Error: M409: expected string expression
        2020-09-27 01:24:42 Error: Bad command: J1172 M409 F"d99f"*127
        2020-09-27 01:26:48 Warning: M509: Command is not supported
        2020-09-27 01:28:26 Error: Bad command: y M409 F"d99f"
        2020-09-27 01:30:55 Error: M4: Command is not supported in machine mode FFF
        2020-09-27 01:31:11 Error: Bad command: :0 M409 K"job" F"v"
        2020-09-27 01:34:27 Warning: M40: Command is not supported
        2020-09-27 01:36:11 Error: Bad command: 55 M409 F"d99f"
        2020-09-27 01:37:53 Finished printing file 0:/gcodes/Printer Parts/Flying_Bondtech.gcode, print time was 1h 14m
        
        1 Reply Last reply Reply Quote 0
        • Phaedruxundefined
          Phaedrux Moderator
          last edited by

          Was this with a freshly uploaded gcode file or one that was copied over?

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • theshaboboundefined
            theshabobo
            last edited by theshabobo

            It was a fresh g-code. I also tried a different print and it ended up giving the same Attempting to extrude error.

            1 Reply Last reply Reply Quote 0
            • deckingmanundefined
              deckingman @theshabobo
              last edited by deckingman

              @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.

              Ian
              https://somei3deas.wordpress.com/
              https://www.youtube.com/@deckingman

              1 Reply Last reply Reply Quote 0
              • theshaboboundefined
                theshabobo
                last edited by

                @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.

                deckingmanundefined 1 Reply Last reply Reply Quote 0
                • deckingmanundefined
                  deckingman @theshabobo
                  last edited by deckingman

                  @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.

                  Ian
                  https://somei3deas.wordpress.com/
                  https://www.youtube.com/@deckingman

                  1 Reply Last reply Reply Quote 0
                  • T3P3Tonyundefined
                    T3P3Tony administrators
                    last edited by

                    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.

                    www.duet3d.com

                    1 Reply Last reply Reply Quote 0
                    • theshaboboundefined
                      theshabobo
                      last edited by

                      @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.

                      1 Reply Last reply Reply Quote 0
                      • lifeformundefined
                        lifeform
                        last edited by

                        @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 ?

                        1 Reply Last reply Reply Quote 0
                        • lifeformundefined
                          lifeform @dc42
                          last edited by

                          @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?

                          Phaedruxundefined 1 Reply Last reply Reply Quote 0
                          • Phaedruxundefined
                            Phaedrux Moderator @lifeform
                            last edited by

                            @lifeform That would be measured with a multimeter.

                            Z-Bot CoreXY Build | Thingiverse Profile

                            1 Reply Last reply Reply Quote 0
                            • Surgikillundefined
                              Surgikill
                              last edited by Surgikill

                              @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

                              Phaedruxundefined 2 Replies Last reply Reply Quote 0
                              • Phaedruxundefined
                                Phaedrux Moderator @Surgikill
                                last edited by

                                @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.

                                Z-Bot CoreXY Build | Thingiverse Profile

                                Surgikillundefined 2 Replies Last reply Reply Quote 0
                                • Surgikillundefined
                                  Surgikill @Phaedrux
                                  last edited by

                                  @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.

                                  1 Reply Last reply Reply Quote 0
                                  • Surgikillundefined
                                    Surgikill @Phaedrux
                                    last edited by

                                    @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.

                                    1 Reply Last reply Reply Quote 0
                                    • Phaedruxundefined
                                      Phaedrux Moderator
                                      last edited by

                                      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.

                                      Z-Bot CoreXY Build | Thingiverse Profile

                                      Surgikillundefined 1 Reply Last reply Reply Quote 0
                                      • Surgikillundefined
                                        Surgikill @Phaedrux
                                        last edited by

                                        @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.

                                        1 Reply Last reply Reply Quote 0
                                        • Phaedruxundefined
                                          Phaedrux Moderator
                                          last edited by

                                          How long is the wire run?

                                          Z-Bot CoreXY Build | Thingiverse Profile

                                          Surgikillundefined 1 Reply Last reply Reply Quote 0
                                          • Surgikillundefined
                                            Surgikill @Phaedrux
                                            last edited by

                                            @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

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA