Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    DWC comm error

    Firmware developers
    2
    5
    706
    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.
    • denke
      denke last edited by

      Dear DC,

      I dunnot know if you are still interested in 1.21 bugs or not, if you arn't please ignore!

      After an unsuccessful delta homing (I set the stepper currents too low causing missed steps on the motion steppers) DWC got disconnected from the duet wifi board, and it could not be reconnected until a Duet board reset. All three versions are 1.21. console.log messages are as follows:

      dwc.js:416:4 13:59:08.004 Error! The following JSON response could not be parsed: dwc.js:416:4
      dwc.js:417:4 13:59:08.004 {"status":"I","coords":{"axesHomed":[0,1,1],"xyz":[9999.900,9999.900,9999.900],"machine":[nan,nan,nan],"extr":[0.0]},"currentTool":0,"params":{"atxPower":0,"fanPercent":[0.00,100.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00],"speedFactor":100.00,"extrFactors":[100.00],"babystep":0.000},"seq":3,"sensors":{"probeValue":1000,"fanRPM":0},"temps":{"bed":{"current":25.6,"active":0.0,"state":0,"heater":0},"current":[25.6,219.9,2000.0,2000.0,2000.0,2000.0,2000.0,2000.0],"state":[0,2,0,0,0,0,0,0],"heads":{"current":[219.9],"active":[220.0],"standby":[0.0],"state":[2]},"tools":{"active":[[220.0]],"standby":[[0.0]]},"extra":[{"name":"MCU","temp":39.4}]},"time":349.0,"spindle":{"current":0,"active":0},"coldExtrudeTemp":160,"coldRetractTemp":90,"tempLimit":320,"endstops":4094,"firmwareName":"RepRapFirmware for Duet 2 WiFi/Ethernet","geometry":"delta","axes":3,"axisNames":"XYZ","volumes":2,"mountedVolumes":1,"name":"Kokuc Printer","probe":{"threshold":100,"height":-0.05,"type":5},"tools":[{"number":0,"name":"","heaters":[1],"drives":[0],"axisMap":[[0],[1]],"fans":1,"filament":"","offsets":[0.00,0.00,0.00]}],"mcutemp":{"min":38.9,"cur":39.4,"max":39.6},"vin":{"min":24.3,"cur":24.4,"max":24.6}} dwc.js:417:4

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

        Did you configure high microstepping in the M350 command? It's a known issue that if you use a combination of high microstepping and high speeds when homing, the MaxReps figure (as reported by M122) goes very high unless you use a slow homing speed, resulting in a disconnection. This is because of the additional overhead of checking endstop switches on each step during a homing move.

        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
        • denke
          denke last edited by

          Microstepping settings:
          M350 X16 Y16 Z16 E16 I1

          Homing speed is 125mm/s.

          I could not reconnect even minutes after the homing has failed, and all movement has stopped

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

            I just spotted the 3 nan values in the machine coordinates. I will fix this in the 1.21.1 maintenance release as well as in 2.0. Thanks for your report.

            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
            • denke
              denke last edited by

              You are welcome!

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