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

    3.5.0-beta.3

    Scheduled Pinned Locked Moved Solved
    Beta Firmware
    4
    8
    460
    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.
    • Proschi3Dundefined
      Proschi3D
      last edited by

      I switched to the latest beta firmware.
      Since then, this message has appeared before every print start

      Error: in file macro: G1: G1/G2/G3: intermediate position outside machine limits

      Love my Duet 3 Mini.
      https://www.instagram.com/proschi3d
      https://youtube.com/@proschi3d
      https://www.proschi3d.de

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

        Any idea where that error line would be?

        Z-Bot CoreXY Build | Thingiverse Profile

        Proschi3Dundefined 1 Reply Last reply Reply Quote 0
        • Proschi3Dundefined
          Proschi3D @Phaedrux
          last edited by

          @Phaedrux No, unfortunately not. When I go back to the beta 2+ the error doesn't come up

          Love my Duet 3 Mini.
          https://www.instagram.com/proschi3d
          https://youtube.com/@proschi3d
          https://www.proschi3d.de

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

            If it's when you start a print there must be a G1 command somewhere. You could tag them with M117 message commands and see which one is causing the error.

            Also I'm not familiar with your printer or setup, so you could share your files and some details.

            Z-Bot CoreXY Build | Thingiverse Profile

            Proschi3Dundefined 1 Reply Last reply Reply Quote 1
            • Proschi3Dundefined
              Proschi3D @Phaedrux
              last edited by

              @Phaedrux I found the G1 command, the error is now gone. The strange thing, however, is that the error did not occur on the beta 2+.
              Thanks

              Love my Duet 3 Mini.
              https://www.instagram.com/proschi3d
              https://youtube.com/@proschi3d
              https://www.proschi3d.de

              Exerqtorundefined 1 Reply Last reply Reply Quote 0
              • Exerqtorundefined
                Exerqtor @Proschi3D
                last edited by Exerqtor

                @Proschi78
                I've had similar things happen too, where a piece of bad code (I've myself put in there because I'm a dumbass) suddenly starts throwing errors in a new RRF build and i can't for the life of me remember where on earth it might even be.

                So i end up throwing echo's i at the start of each macro trying to find out where the fudge it's located. And when i finally find it. it's totally logical that it's throwing faults, and it probably should have earlier too lol.

                This time, when I went from b2 too b3 i suddenly started getting a error from my Toggle Chamber Lighting macro, because i was using else wrong (again because I'm CLEARLY a dumbass).
                What it was:

                ;Check if the LEDs are on or off, and act accordingly
                if state.gpOut[0].pwm = 0
                  M42 P0 S1                                                                    ; Swith GPIO port 0 on
                else state.gpOut[0].pwm = 1
                  M42 P0 S0                                                                    ; Swith GPIO port 0 off
                

                How it should have been all the time:

                ;Check if the LEDs are on or off, and act accordingly
                if state.gpOut[0].pwm = 0
                  M42 P0 S1                                                                    ; Swith GPIO port 0 on
                elif state.gpOut[0].pwm = 1
                  M42 P0 S0                                                                    ; Swith GPIO port 0 off
                

                But all RRF 3 version up until now have been fine with it and ignored it, I'm glad it finally made me aware of the problem though 🤣

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

                  @Proschi78 said in 3.5.0-beta.3:

                  Error: in file macro: G1: G1/G2/G3: intermediate position outside machine limits

                  The error usually occurs when segmentation is enabled (either because the kinematics uses segmentation or because you have explicitly enabled segmentation using M669) and the print head is in a location outside the printable area defined by M208 after taking account of tool offsets. For the print head to be outside the printable area, one of the following has usually happened:

                  • You have executed G1 H1 or G1 H2 moves (these moves ignore the axis limits)
                  • You have use G92 to specify the position of the print head
                  • You have executed a M208 command so that a position that was previously allowed is no longer allowed
                  • You have changed the tool offset using G10

                  However, it may be that there is a new bug in 3.5beta3. In order to track this down, we would need your config.g file and the sequence of commands that causes 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

                  Proschi3Dundefined 1 Reply Last reply Reply Quote 0
                  • Proschi3Dundefined
                    Proschi3D @dc42
                    last edited by

                    @dc42 It was a G1 command in the intro line. The right extruder came too close to the left one. I shortened the movement by 5mm and the message disappeared. Thank you for your explanation

                    Love my Duet 3 Mini.
                    https://www.instagram.com/proschi3d
                    https://youtube.com/@proschi3d
                    https://www.proschi3d.de

                    1 Reply Last reply Reply Quote 1
                    • dc42undefined dc42 marked this topic as a question
                    • dc42undefined dc42 has marked this topic as solved
                    • First post
                      Last post
                    Unless otherwise noted, all forum content is licensed under CC-BY-SA