Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. ELAD
    3. Topics
    • Profile
    • Following 0
    • Followers 0
    • Topics 10
    • Posts 21
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by ELAD

    • ELADundefined

      Upgrading from 3.5.2 to 3.5.4 - Help request

      Firmware installation
      • • • ELAD
      3
      0
      Votes
      3
      Posts
      133
      Views

      ELADundefined

      @droftarts
      Ian thank you very much!
      Problem solved
      šŸ¤—

    • ELADundefined

      ODrive S1 + Duet3 XD

      Third-party add-ons
      • • • ELAD
      5
      0
      Votes
      5
      Posts
      392
      Views

      flopesundefined

      @ELAD . Is it working properly? I am designing a laser cutter with the ODRIVEs. Please let me know

    • ELADundefined

      SZP + two mainboards

      Duet Hardware and wiring
      • • • ELAD
      5
      0
      Votes
      5
      Posts
      279
      Views

      dc42undefined

      @ELAD to remove the CAN1 termination, break both the CAN1 termination connections indicated on the back of the 6HC. We've included small holes where the traces need to be cut so that you can do this easily using a twist drill bit. See https://www.youtube.com/watch?v=BFHzTmaF1CU.

      6HC_CAN_termination.jpg

    • ELADundefined

      Solved BL-Touch doesn't work via Tool Board V1.0

      General Discussion
      • • • ELAD
      6
      0
      Votes
      6
      Posts
      228
      Views

      jay_s_ukundefined

      @ELAD don't worry, we all get cable blindness sometimes!

    • ELADundefined

      Two MB6HC 1.02 boards connected

      Duet Hardware and wiring
      • • • ELAD
      2
      0
      Votes
      2
      Posts
      108
      Views

      jay_s_ukundefined

      @ELAD yes

    • ELADundefined

      Modix3d 120X - Two gantries

      My Duet controlled machine
      • • • ELAD
      5
      0
      Votes
      5
      Posts
      290
      Views

      jay_s_ukundefined

      @T3P3Tony i thought it might be on the cards considering the 3HC already does

    • ELADundefined

      Solved Motors unresponsive via 3HC

      Duet Hardware and wiring
      • • • ELAD
      8
      0
      Votes
      8
      Posts
      301
      Views

      ELADundefined

      @dc42 Thank you very much ! It fixed it ! šŸ™

    • ELADundefined

      distinguishing between two kinds of pause

      Filament Monitor
      • • • ELAD
      2
      0
      Votes
      2
      Posts
      120
      Views

      dc42undefined

      I have it on the work list to add a new macro file for a pause caused by a filament problem.

    • ELADundefined

      Assistance with editing PAUSE.G and other files

      Tuning and tweaking
      • • • ELAD
      5
      0
      Votes
      5
      Posts
      396
      Views

      dc42undefined

      @ELAD said in Assistance with editing PAUSE.G and other files:

      If during a pause there is a power cut the X and Y coordinates are saved but the Z coordinate gets an extra 5mm, therefore when the sending M916 the print continues well, except it pours filament 5mm too high over the model.

      That might be caused by the G1 Z5 move in your resurrect-prologue.g file, along with the fact that you are not homing Z. Try reversing that movement at the end of the file.

      If the print pauses due to a signal received from the filament runout sensor (Trianglelab), it doesn't invoke filament-change.g but it invokes pause.g.

      That is intentional. File filament-change.g is only invoked in response to M600, which is for use within a Gcode file where a manual change of filament colour is wanted. We are considering defining a separate macro file to be invoked when a filament sensor indicates a filament problem.

      In addition, if an M291 is contained inside the pause.g the message of "Extruder # reports no filament" is not being shown.

      Is this on PanelDue, or in DWC? PanelDue can only track and display a single popup message at a time.

      Furthermore, if an M291 with S2or3 is used, then the print resumes automatically when that message pops to the display. (without pressing on the resume)

      That sounds odd. I will see if I can reproduce it in firmware 3.1.1.

      I would appreciate it if someone knowledgeable than me could advise how to edit the pause.g and resume.g thus it will cool down the hotend but remembers the standby and active temps and works well for dual colour prints with two tools.

      I don't think there's a way to do that yet, although you can get close to it using conditional GCode in RRF3. The mechanism would be to command a reduction in temperature by a fixed amount (e.g. 200C) using conditional GCode. Then increase it again by the same amount in resume.g. When we introduce variables into RRF3 conditional GCode, it will be more straightforward.

      Meanwhile, in RRF2 you can set the active tool to standby using T-1 so that at least the temperature of the active tool drops to the standby temperature. Then use command T R1 in resume.g to active it again.

      Perhaps a G60 would be useful?

      In what way? G60 saves the current position, but not the temperatures.

      HTH David

    • ELADundefined

      Actions when heater fault detection occurs

      Duet Hardware and wiring
      • • • ELAD
      1
      0
      Votes
      1
      Posts
      135
      Views

      No one has replied