Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Question about G30 and firmware 3.2

    General Discussion
    2
    3
    56
    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.
    • fcwilt
      fcwilt last edited by fcwilt

      Hi,

      I've been testing my new Duet 3 Mini 5 board with firmware v3.2

      Working on Z probe testing - I have this in config.g:

      M558 P5 C"!^io0.in" H2 F120 T10000 R0.2 A1 S0.03
      G31 P500 X0 Y0 Z5

      When executing a G30 the Z stepper starts to move in the a correct direction and when I trigger the Z probe the stepper stops and the Z coordinate is set.

      The docs say this about G30:

      G30 ; Probe the bed at the current XY position. When the probe is triggered, set the Z coordinate to the probe trigger height.

      Now the "probe trigger height" mentioned is the value of the Z parameter in the G31 - correct?

      However the Z coordinate is actually being set to the sum of the Z probe trigger height from G31 and the Z probe dive height from M558.

      Is that a bug or just how G30 works.

      Thanks much.

      Frederick

      Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

      1 Reply Last reply Reply Quote 0
      • Veti
        Veti last edited by

        @fcwilt said in Question about G30 and firmware 3.2:

        Is that a bug or just a change in how G30 works.

        that is how it works.

        then the probe is trigged z is set to 5. then the probe moves out of the way as defined by H

        so you end up with z=7

        fcwilt 1 Reply Last reply Reply Quote 0
        • fcwilt
          fcwilt @Veti last edited by

          @Veti said in Question about G30 and firmware 3.2:

          @fcwilt said in Question about G30 and firmware 3.2:

          Is that a bug or just a change in how G30 works.

          that is how it works.

          then the probe is trigged z is set to 5. then the probe moves out of the way as defined by H

          so you end up with z=7

          Thanks.

          It seems that I just never noticed it before - when I looked at the locations on my printers gcode where G30 was used it was always followed by a Z move.

          Frederick

          Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

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