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

    Bug: gcode file not found in subdirectory

    Scheduled Pinned Locked Moved
    General Discussion
    2
    3
    508
    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.
    • garyd9undefined
      garyd9
      last edited by

      firmware 1.20 on a duet/ethernet:

      Steps:

      From the G-Code Files page, Make new Directory. Call the directory "PLA (L)" ("P", "L", "A", space, open paren, "L", close paren.)

      Upload a gcode file to the newly made directory.

      Try to print the gcode file just uploaded.

      Expected: The file prints. (Of course.)

      Actual result: Nothing prints, but an error appears: M32: GCode file "PLA /filename.gcode" not found

      Notice in the error message that the directory name is truncated before the open paren symbol.

      "I'm not saying that you are wrong - I'm just trying to fit it into my real world simulated experience."

      1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators
        last edited by

        This is because standard gcode uses parentheses to surround comments. The workaround in firmware v1.20 is to enclose filenames and other string parameters in double quotation marks within Gcode commands, but DWC doesn't do that yet. The v1.20 PanelDue firmware does.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        1 Reply Last reply Reply Quote 0
        • garyd9undefined
          garyd9
          last edited by

          It sounds like I might be bumping into minor "known" issues, but without knowing that they are known. Is there bug list available I can check before spamming the forum?

          Eventually, I'll just clone the code and fix things on my own (and send pull requests), but right now I'm extremely behind on my paying job, so don't have the time to do much more than document things.

          It's really very exciting to me to be using an excellent control board that's actually supported and being actively worked on, so I feel it's the least I can do to provide bug information to the best of my ability.

          "I'm not saying that you are wrong - I'm just trying to fit it into my real world simulated experience."

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