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

    First cut success - with questions!

    Scheduled Pinned Locked Moved
    Duet Web Control
    8
    66
    3.5k
    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.
    • Nightowlundefined
      Nightowl @JoergS5
      last edited by Nightowl

      @joergs5 OK. Shall I load and run the file?

      Actually, what I did was upload the gcode file, then right-clicked it and simulated the project, with these results:

      21/05/2022, 19:54:21 File 0:/gcodes/102 Avalon Pocket_1-102 Avalon Pocket.gcode will print in 0h 14m plus heating time
      21/05/2022, 19:54:19 M37 P"0:/gcodes/102 Avalon Pocket_1-102 Avalon Pocket.gcode"
      Simulating print of file 0:/gcodes/102 Avalon Pocket_1-102 Avalon Pocket.gcode

      JoergS5undefined 1 Reply Last reply Reply Quote 0
      • JoergS5undefined
        JoergS5 @Nightowl
        last edited by

        @nightowl999 said in First cut success - with questions!:

        G53

        G53 is to clear coordinate changes and not using any machine coordinates, so I would not run it.
        https://duet3d.dozuki.com/Wiki/Gcode#Section_G53_Use_machine_coordinates

        There should be G54 to G59 somewhere else, probably in your Cut2D software.

        The problem now is that I don't know your software and which commands are run. I can only help to find out the reason why there is the G0/G1 error message.

        1 Reply Last reply Reply Quote 0
        • JoergS5undefined
          JoergS5 @Nightowl
          last edited by

          @nightowl999 said in First cut success - with questions!:

          and simulated the proj

          unfortunately it didn't find an error line, so it didn't help.
          The simulation mode may have some shortcuts, e.g. not checking limits....

          Nightowlundefined 2 Replies Last reply Reply Quote 0
          • Nightowlundefined
            Nightowl @JoergS5
            last edited by

            @joergs5

            Well, starting the file seemed to work, too.

            I'm not sure what's going on here, but I'm also getting random disconnects

            JoergS5undefined 1 Reply Last reply Reply Quote 0
            • JoergS5undefined
              JoergS5 @Nightowl
              last edited by

              @nightowl999 said in First cut success - with questions!:

              also getting random disconnects

              I am innocent 😉

              Nightowlundefined 1 Reply Last reply Reply Quote 1
              • Nightowlundefined
                Nightowl @JoergS5
                last edited by

                @joergs5

                What I'll do now I know this file runs is to let it finish, s
                hut everything down and use the same Work XYZ coordinates again tomorrow, but with the other file, and see how that goes.

                JoergS5undefined 1 Reply Last reply Reply Quote 0
                • Nightowlundefined
                  Nightowl @JoergS5
                  last edited by

                  @joergs5 said in First cut success - with questions!:

                  I am innocent

                  Every guilty person says that! 🙄 😀

                  1 Reply Last reply Reply Quote 0
                  • JoergS5undefined
                    JoergS5 @Nightowl
                    last edited by

                    @nightowl999 when you get a G0/G1 error, you know now how to analyze it. I expect a conflict between what the software wants to make and your M208 limits.

                    I checked Cut2D, there was one similar problem in
                    https://forum.vectric.com/viewtopic.php?t=32804
                    but I am not sure whether it can be the reason in your case.

                    Nightowlundefined 1 Reply Last reply Reply Quote 0
                    • Nightowlundefined
                      Nightowl @JoergS5
                      last edited by

                      Thank you, @joergs5

                      I'll check that forum out tomorrow, but that thread is exactly the issue here - if not the resolution!

                      Have a good evening and thank you for your help 👍

                      JoergS5undefined 1 Reply Last reply Reply Quote 0
                      • JoergS5undefined
                        JoergS5 @Nightowl
                        last edited by

                        @nightowl999 you're welcome, and I wish you success tomorrow!

                        1 Reply Last reply Reply Quote 1
                        • Nightowlundefined
                          Nightowl
                          last edited by

                          Maybe I've got to the bottom of this...

                          I've simulated several files from a specific Work XYZ, which is X27 Y198 and Z82. The maximum axis limits are X535 Y787 Z100.

                          I need to look at the Vectric software to see why, but I've compared a few gcode files produced by the Vectric software, and I've found this:

                          In both working and non-working files, there are four consistent lines of code at the start (excluding the headers) as follows:

                          G17 (Sets the XY plane for arc moves)
                          G21 (Sets the units to mm)
                          G90 (Sets to absolute positioning)

                          Then the files differ.

                          In the files that can be simulated, this is the next line:

                          G0Z6.350 (Which moves the Z axes to a safe height, I guess)

                          ...but in the files that can't be simulated, this is the next line:

                          G0Z20.320

                          I think this is the problem because if the Z Axis is already at 82mm when the Work XYZ is set, then trying to move the Z axis another 20.320mm will exceed the available Z axis movement of 100mm (82 + 20.32 = 102.32mm).

                          Does anyone agree, or am I talking out of my hat?

                          Thanks

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

                            @nightowl999 said in First cut success - with questions!:

                            I think this is the problem because if the Z Axis is already at 82mm when the Work XYZ is set, then trying to move the Z axis another 20.320mm will exceed the available Z axis movement of 100mm (82 + 20.32 = 102.32mm).
                            Does anyone agree, or am I talking out of my hat?

                            Yes, I think that is exactly what is happening.

                            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

                            Nightowlundefined 2 Replies Last reply Reply Quote 1
                            • Nightowlundefined
                              Nightowl @dc42
                              last edited by

                              Thank you, @dc42.

                              I was getting a bit tied up with this last night, but in the cold light of day - and after a good nights sleep! - a clear look at the problem certainly helps.

                              My thanks to @JoergS5 for pointing me towards the Z height, and everyone else who joined me on this journey.

                              Now all I have to do is find out why and prevent it from ruining my day again! 👏 👏

                              1 Reply Last reply Reply Quote 2
                              • Nightowlundefined
                                Nightowl @dc42
                                last edited by Nightowl

                                This post is deleted!
                                1 Reply Last reply Reply Quote 0
                                • Nightowlundefined
                                  Nightowl @Nightowl
                                  last edited by Nightowl

                                  This post is deleted!
                                  1 Reply Last reply Reply Quote 0
                                  • Nightowlundefined
                                    Nightowl
                                    last edited by

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