Duet3D Logo

    Duet3D

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

    Found why G30 under beta9 was not doing what I expected

    Firmware installation
    1
    1
    326
    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

      Hi,

      I don't know if this would be consider a "bug" or not but the behavior of commands like G30 P0 X0 Y0 Z-99999 H0 were not doing what I expected.

      It turns out the when doing a simple G30 S-1 the movement starts out very slow and the Z-probe is monitored.

      However it appears that when doing a command like G30 P0 X0 Y0 Z-99999 H0 the movement starts out fast and the Z-probe is NOT monitored.

      Then when nearing the bed the movement slows to the same rate as exhibited by a G30 S-1 command and the Z-probe is now monitored.

      In my case, due to a config file typo, the "near the bed" position was unreachable, the movement never slowed, the Z-probe was never monitored and, naturally, the bed was impacted.

      I'm thinking that perhaps the Z-probe should be monitored during all phases of G30 movement so this type of problem does not occur.

      Perhaps if the Z-probe is activated during the "fast movement" phase the process could be aborted and an appropriate error message displayed informing the user of the issue.

      On the other hand I could be completely wrong about what I think is happening.

      Thanks.

      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