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

G54-59 not working in start.g?

Scheduled Pinned Locked Moved
Duet Hardware and wiring
3
14
425
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.
  • undefined
    TC
    last edited by 25 Feb 2020, 13:52

    Hi all,

    is it possible the alternative coordinate systems are not working in start.g.
    The following code:

    G55
    G1 X0 Y0 F2000

    just executed in console moves the head to the origin of system 2. But executed in start.g or a from there called macro it moves to the origin of the absolute system...

    Thanks ahead

    1 Reply Last reply Reply Quote 0
    • undefined
      Danal
      last edited by 25 Feb 2020, 14:30

      For debugging, add G10 L2 with no other arguments. This will print offsets for the current work system on the console.

      This can also be the second command on a line, so this is a good way to do this for debugging:

      G55 G10 L2

      Delta / Kossel printer fanatic

      1 Reply Last reply Reply Quote 0
      • undefined
        TC
        last edited by 25 Feb 2020, 14:43

        @Danal said in G54-59 not working in start.g?:

        G55 G10 L2

        I tested it. It displays the correct offsets of system 2 even if it is executed from start.g. still the next G1 command goes to the wrong place...

        undefined 1 Reply Last reply 25 Feb 2020, 14:49 Reply Quote 0
        • undefined
          Danal @TC
          last edited by Danal 25 Feb 2020, 14:49

          @TC said in G54-59 not working in start.g?:

          @Danal said in G54-59 not working in start.g?:

          G55 G10 L2

          I tested it. It displays the correct offsets of system 2 even if it is executed from start.g. still the next G1 command goes to the wrong place...

          Wow, that's really not good.

          What releases are you running? Check the "machine specific" tab in the web interface, and copy the three lines that look like this (you may or may not have a DSF line):

          Board: Duet 3 MB6HC (MB6HC)
          DSF Version: 1.2.4.0
          Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.01-RC2 (2020-02-18b1)

          Delta / Kossel printer fanatic

          1 Reply Last reply Reply Quote 0
          • undefined
            TC
            last edited by 25 Feb 2020, 15:01

            Board: Duet WiFi 1.02 or later + DueX5
            Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.01-RC1 (2020-02-08b3)
            Duet WiFi Server Version: 1.23

            undefined 1 Reply Last reply 25 Feb 2020, 15:04 Reply Quote 0
            • undefined
              TC
              last edited by 25 Feb 2020, 15:02

              But the problem allready existed before the upgrade to RRF3

              undefined 1 Reply Last reply 25 Feb 2020, 15:05 Reply Quote 0
              • undefined
                Danal @TC
                last edited by 25 Feb 2020, 15:04

                @TC said in G54-59 not working in start.g?:

                Board: Duet WiFi 1.02 or later + DueX5
                Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.01-RC1 (2020-02-08b3)
                Duet WiFi Server Version: 1.23

                Hmmm... you could try RC2, just for completeness. It uploads just fine via web "system" tab.

                https://github.com/dc42/RepRapFirmware/releases/tag/3.01-RC2

                Delta / Kossel printer fanatic

                1 Reply Last reply Reply Quote 0
                • undefined
                  Danal @TC
                  last edited by 25 Feb 2020, 15:05

                  @TC said in G54-59 not working in start.g?:

                  But the problem allready existed before the upgrade to RRF3

                  Ahhh... interesting. I'm really stumped as to what would cause this, it would seem this is a function of a very basic parser that should work for you and me both.

                  Hmmm... @dc42 will probably need to look at this one.

                  Delta / Kossel printer fanatic

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    dc42 administrators
                    last edited by 25 Feb 2020, 15:21

                    Commands in macro files in the /sys folder always ignore workplace offsets. This is so that movement commands in homing files, pause.g and so on always go to the same places regardless of what coordinate system you are in.

                    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

                    undefined 1 Reply Last reply 25 Feb 2020, 18:06 Reply Quote 0
                    • undefined
                      TC
                      last edited by 25 Feb 2020, 15:39

                      Ah ok. In my case I set the origin and therefor the place to print before each print job. That is important because I need to print on prepared objects. Is it possible to add the function that if there is a G55 command directly in front of a G1 command it applies the offset?

                      1 Reply Last reply Reply Quote 0
                      • undefined
                        TC
                        last edited by 25 Feb 2020, 15:58

                        Or is it possible to get the offsets of the coordinate systems from the object model?

                        1 Reply Last reply Reply Quote 0
                        • undefined
                          TC
                          last edited by 25 Feb 2020, 16:04

                          Ah looks like I found it 🙂

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            TC
                            last edited by 25 Feb 2020, 16:20

                            Thanks to your awsome object model it was easy to solve!

                            1 Reply Last reply Reply Quote 0
                            • undefined
                              Danal @dc42
                              last edited by 25 Feb 2020, 18:06

                              @dc42 said in G54-59 not working in start.g?:

                              Commands in macro files in the /sys folder always ignore workplace offsets. This is so that movement commands in homing files, pause.g and so on always go to the same places regardless of what coordinate system you are in.

                              Very interesting and good to know. THANKS!

                              Delta / Kossel printer fanatic

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