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

    Babystepping issue on 3.6.0 rc1

    Scheduled Pinned Locked Moved
    Beta Firmware
    2
    3
    77
    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.
    • ToWi1989undefined
      ToWi1989
      last edited by ToWi1989

      Changing babystepping while printing causes erratic stepper movement on 3.6.0 RC1 and fills log with repeating g0 g1 position outside machine limit errors. Can anyone else confirm/replicate?

      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @ToWi1989
        last edited by

        @ToWi1989 which way are you trying to baby step? Up or down? Also try RC2

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        ToWi1989undefined 1 Reply Last reply Reply Quote 0
        • ToWi1989undefined
          ToWi1989 @jay_s_uk
          last edited by ToWi1989

          @jay_s_uk it's when babystepping in -Z. I've updated to 3.6.0 rc2 and the issue persists. I believe it has something to do with the bed mesh compensation thinking the machine is going outside its limits. Also, when restarting a new print, the babystepping value has to be increased with the previous value to get to nozzle at the correct height, and the reported z axis position will start to drift every time this is repeated (I'd expect this to get reset).

          Anyhow, I've now run a first level calibration print and set the probe offset accordingly (g31 in the config) so I don't need to use babystepping for now. I'm also not entirely sure if this is an isolated 3.6.0 issue since I've only had to start messing with the babystepping after I've had a crash with disabled axis limits 😅

          1 Reply Last reply Reply Quote 0
          • Phaedruxundefined Phaedrux moved this topic from General Discussion
          • First post
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA