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

    Heater timeout

    Scheduled Pinned Locked Moved
    Firmware wishlist
    12
    24
    3.0k
    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.
    • gregsaunundefined
      gregsaun @OwenD
      last edited by

      @owend thanks for your help. Any reason why you want to get the current instead of machine position like with move.axes[].machinePosition ?

      github.com/gregsaun - Papa Bear

      OwenDundefined 1 Reply Last reply Reply Quote 0
      • OwenDundefined
        OwenD @gregsaun
        last edited by

        @gregsaun
        I wasn't actually looking at the position, but at the current that the motor is set at.
        However it may actually be that you would look at move.axes[0].percentCurrent
        After the timeout set in M84, your motor(s) will be set to a lower current.
        I just tried to check on this, but the object model doesn't change for either move.axes[0].percentCurrent or move.axes[0].current after M84 is issued despite the axis being marked as unhomed.
        Perhaps @dc42 can comment.

        gregsaunundefined 1 Reply Last reply Reply Quote 0
        • gregsaunundefined
          gregsaun @OwenD
          last edited by

          @owend Sorry for my late answer, thanks I better understand now 🙂

          github.com/gregsaun - Papa Bear

          1 Reply Last reply Reply Quote 0
          • petriheinoundefined
            petriheino
            last edited by

            Hi, did anybody actually get this working with daemon.g or other means?

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