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

    Connection lost by M203 setting .

    Scheduled Pinned Locked Moved
    General Discussion
    2
    5
    258
    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.
    • wydowawundefined
      wydowaw
      last edited by

      Connection lost by M203 setting ?

      Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
      Firmware Electronics: Duet Ethernet 1.02 or later
      Firmware Version: 2.04RC1 (2019-07-14b1)
      Web Interface Version: 1.22.6
      CoreXY, double Z steppers with high gear ratio (1:100)

      During my Z axis testing of the machine... I experienced my first "Connection lost" of the web interface.
      This one was not generated by switching of the board power, but by a "change" in the M203 Z-setting in the config.g

      Connection_lost_byM203 setting.jpg

      For my board and network setup, it's reproducable.

      Maybe there is a simple explanation for this.. or just a setting;

      1 Reply Last reply Reply Quote 0
      • T3P3Tonyundefined
        T3P3Tony administrators
        last edited by

        @wydowaw generally the Duet 3 maxes out at 130Ksteps/s/axis when multiple axis are being moved at once. For your Z axis that should be ~2900mm/min. Saying that, in this test maybe you were only moving the Z axis?

        Also intresting that You had connection lost at 1000mm/min on the second time but not on the first.

        www.duet3d.com

        1 Reply Last reply Reply Quote 0
        • wydowawundefined
          wydowaw
          last edited by

          Correct I am only moving the z-axis (Za,Zb)
          My M92 max value is 2640 , close to ~2900
          M92table.jpg

          But why is this reason to lose connection on the network card??

          Maybe my first test at 1000 was a short time span and it homed..., and I didn't spot the connection loss.
          first you lose the speed indication ...which is followed by the connection lose.

          130Ksteps/s/axis...that's intresting,
          just posted a problem how to do 20Ksteps/axis......so that should be possible! But How??

          T3P3Tonyundefined 1 Reply Last reply Reply Quote 0
          • T3P3Tonyundefined
            T3P3Tony administrators @wydowaw
            last edited by

            @wydowaw My understanding is when you get >130Ks/s the MCU does not have enough time to do lower priorty tasks like the web server.

            www.duet3d.com

            wydowawundefined 1 Reply Last reply Reply Quote 0
            • wydowawundefined
              wydowaw @T3P3Tony
              last edited by

              @T3P3Tony

              OK thanks ,
              Case Solved !!

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