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

    Disabling or changing the axis at which babystepping is applied

    Scheduled Pinned Locked Moved
    Duet Web Control wishlist
    2
    3
    123
    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.
    • ComedianTF2undefined
      ComedianTF2
      last edited by

      When using a belt printer, the slicer and thus the printer is setup using the Z axis as the belt axis, while the Y axis is the up/down movement.

      Now, it's possible to babystep using M290 Y<value>, and when sending these commands everything works all fine and dandy

      However the default paneldue (7i) or web interface babystepping buttons are set to always apply the babystepping to the Z (belt) axis.

      Is it possible to adjust the default babystepping axis? I was thinking of maybe using the daemon.g to translate the Z babystepping into Y babystepping, but I'm not really happy with that idea as there would be significant delay between the babystepping is applied and it getting applied on the correct axis.

      droftartsundefined ComedianTF2undefined 2 Replies Last reply Reply Quote 1
      • Phaedruxundefined Phaedrux moved this topic from General Discussion
      • droftartsundefined
        droftarts administrators @ComedianTF2
        last edited by

        @ComedianTF2 It's not currently possible to change the button on the PanelDue; it would need a firmware update to allow it to be configured, perhaps with the option in the Setup screen. Feel free to suggest a feature request on the Github repository here: https://github.com/Duet3D/PanelDueFirmware/issues

        As a workaround, you could create two macros, one to increase the Y babystepping a set amount, and the other to decrease it. Name the macros as suggested here https://docs.duet3d.com/User_manual/Tuning/Macros_tasks#naming-and-ordering-macros and you should be able to put them so they are easily accessible on the PanelDue.

        Ian

        Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

        1 Reply Last reply Reply Quote 1
        • ComedianTF2undefined
          ComedianTF2 @ComedianTF2
          last edited by

          Thanks, I've the macro workaround works for now, but a more integrated solution would be great. I've added a feature request on the github for the paneldue integration.

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