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

    1.17x & M665, M666

    Scheduled Pinned Locked Moved
    General Discussion
    3
    5
    920
    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.
    • LeonMFundefined
      LeonMF
      last edited by

      All, for all of the versions of 1.17 I've been noticing some weird behavior with the calibration system.

      Basically, when I start the machine up, it doesn't seem calibrated. I've even taken to just running a calibration on my mechanically stable delta every time I power up. I never had to do that with 1.15 or 1.16. I've been living with it but I noticed a weird behavior today that may have some relationship.

      After boot up, the first time I call M665 and M666 in a g-code console, it returns nothing. The second time it's fine.

      Maybe my problems are user error but I'm not sure why it would be different now!

      Current: Railcore II ZLT w/Duet 3 and Hemera hot end.
      Retired: Robo3D R1,BI V2.5 Delta updated to BerryBot magnets, bespoke carriages and Duet Ethernet, M3D Promega;

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

        I have known the gcode console in DWC become unresponsive occasionally. Refreshing DWC fixes it.

        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
        • T3P3Tonyundefined
          T3P3Tony administrators
          last edited by

          Lean regarding having to redo the calibration each time - do you have something in config-override.g that could be throwing the calibration out (e.g M666 with the wrong parameters?)

          www.duet3d.com

          1 Reply Last reply Reply Quote 0
          • LeonMFundefined
            LeonMF
            last edited by

            @dc42:

            I have known the gcode console in DWC become unresponsive occasionally. Refreshing DWC fixes it.

            I wasn't very clear in my text. The web console is fine. The first time I run either of those g codes the response is just the gcode. Meaning that if I type M665, I get a response of M665. The second time reports the parameters.

            Current: Railcore II ZLT w/Duet 3 and Hemera hot end.
            Retired: Robo3D R1,BI V2.5 Delta updated to BerryBot magnets, bespoke carriages and Duet Ethernet, M3D Promega;

            1 Reply Last reply Reply Quote 0
            • LeonMFundefined
              LeonMF
              last edited by

              @T3P3Tony:

              Lean regarding having to redo the calibration each time - do you have something in config-override.g that could be throwing the calibration out (e.g M666 with the wrong parameters?)

              I'll have to check but I'm 99% positive that I don't have a config-override. (Now that you mention it, I should go review the appropriate commands because that would be useful).

              The first time I type the command, it just returns the M code. M665 returns M665. The second time returns the values I have stored in config.g. This isn't a huge deal and it seems that I'm the only one suffering from whatever this is.

              Current: Railcore II ZLT w/Duet 3 and Hemera hot end.
              Retired: Robo3D R1,BI V2.5 Delta updated to BerryBot magnets, bespoke carriages and Duet Ethernet, M3D Promega;

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