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

    Sensorless Homing Error: Operation failed

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    2
    4
    205
    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.
    • oliofundefined
      oliof
      last edited by

      Hi,
      on my Duet 3 0.6 board with RRF 3.01-beta3, I am currently trying to get sensorless homing set up for X and Y so I can use the printer while trying to come up with a mount for normal endstop. My suspicions about sensorless homing don't seem unfounded because at times while the motor stalls, I get

      G28 Y Error: Operation failed (Reason: Transport endpoint is not connected)

      At this point, any attempts to send commands to the board are stuck (i.e. the spinner on the send button in the dashboard keeps spinning). Files and status from the printer still update in DWC

      and after that, no more connectivity between the duet3 board and the raspberry pi until I reboot the pi. I had to completely power down the boards (connected via ribbon cable, Pi gets power from the duet3 board) to get the system up again.

      The issue seems to be that if you don't cause a stall event within the home*.g quickly enough, the communications between the board and the SBC fail. As I am cleaning up my scripts and make sure the endstop positions are right and the travel moves are far enough, the error starts ceasing.

      Is there a way to recover from the Transport endpoint is not connected error without a full power cycle?

      <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

      1 Reply Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators
        last edited by

        Please upgrade RRF to 3.01-RC1 and DSF to 1.2.4.0 and try again.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        1 Reply Last reply Reply Quote 0
        • oliofundefined
          oliof
          last edited by

          Same issue with 3.01-RC1 -- system already was on DSF 1.2.4

          M122-RC1.txt

          PS I figured out by now that systemctl restart duetcontrolserver.service is enough to make the system respond to commands issued via DWC again. duetcontrolserver's logs don't seem to log anything specific:
          duetcontrolserverlogs.txt

          <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

          1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators
            last edited by

            One for @chrishamm I think.

            Duet WiFi hardware designer and firmware engineer
            Please do not ask me for Duet support via PM or email, use the forum
            http://www.escher3d.com, https://miscsolutions.wordpress.com

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