Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. Documentation
    Log in to post
    Load new posts
    • Recently Replied
    • Recently Created
    • Most Posts
    • Most Votes
    • Most Views
    • droftartsundefined

      Request for machine config, macro, and meta Gcode example links

      • • droftarts
      1
      1
      Votes
      1
      Posts
      190
      Views

      No one has replied

    • NEW Duet3D documentation site - now official!

      • • droftarts
      21
      19
      Votes
      21
      Posts
      2.3k
      Views

      T3P3Tonyundefined

      @gallaghersart ahh good idea with the meta tags on each of the old HTML pages - will look into that.

      Wiki.js has a setting to apply meta robots index and follow to the site - which it is set to do.

      Unfortunately we have no access on the old site to things like ftp or the htaccess or equivalent.

      thanks for the help!

    • T3P3Tonyundefined

      Keep this category for docs.duet3d.com issues

      • • T3P3Tony
      1
      0
      Votes
      1
      Posts
      233
      Views

      No one has replied

    • Macgyverundefined

      Detailed ref on X/Y offsets BLtouch and IDEX tool head

      • • Macgyver
      2
      0
      Votes
      2
      Posts
      134
      Views

      crpalmerundefined

      @Macgyver, I also have a hard time keeping the offset meanings (both probes and tools) correct in my brain. As such, I'm not willing to try to turn the contents of my brain into sentences at the risk of getting it backwards and making it harder for you! That said, I have a macro that probes a fixed point with each of my 2 idex nozzles and updates the tool offset based on the results of probing. Here is the macro on the off chance that it helps you visualize the offsets:

      if ! exists(tools[1]) abort "idex-calibration failed, no second tool" if global.probe_block_middle == null || global.probe_block_diameter == null abort "idex-calibration failed, no probe block defined" T0 M98 P"/sys/wipe-for-probing.g" M98 P"/sys/probe-block.g" var p0 = global.last_probe_result var needs_calibration = true while var.needs_calibration && iterations < 3 T1 M98 P"/sys/wipe-for-probing.g" M98 P"/sys/probe-block.g" var p1 = global.last_probe_result var d_u = var.p0[0] - var.p1[0] var d_y = var.p0[1] - var.p1[1] var d_z = var.p0[2] - var.p1[2] if abs(var.d_u) < 0.1 && abs(var.d_y) < 0.1 set var.needs_calibration = false echo "Current offets:", tools[1].offsets[3], ",", tools[1].offsets[1], ",", tools[1].offsets[2] echo "Correction:", var.d_u, ",", var.d_y, ",", var.d_z G10 P1 U{tools[1].offsets[3] + var.d_u} Y{tools[1].offsets[1] + var.d_y} Z{tools[1].offsets[2] + var.d_z} echo "New offets:", tools[1].offsets[3], ",", tools[1].offsets[1], ",", tools[1].offsets[2]

      FYI, var.p0 is the (x,y,z) position of the fixed point as probed by T0 and var.p1 is the (x,y,z) position of the same fixed point as probed by T1 and it computes the delta between the two points as p0 - p1 and then sets the tool offsets as old_offset + delta

    • oliofundefined

      Unsolved E acceleration has to be limited to to E jerk/PA

      • • oliof
      15
      5
      Votes
      15
      Posts
      966
      Views

      droftartsundefined

      @oliof @gloomyandy After discussing this with @dc42, I think I've misunderstood how extruder acceleration is limited under PA. The jerk / PA limit on acceleration is applied automatically by RRF, so the user doesn't need to set jerk or acceleration manually to take account of PA. The user sets extruder speed, jerk and acceleration at whatever the extruder can achieve in extruder-only moves (like retraction). The user only needs to know that acceleration is limited when PA is applied, to jerk / PA, so may have consequences such as slowing down or stuttering during printing moves, or skipping steps. This, at least, makes the documentation simpler! Which I'll now update, again...

      Ian

    • davidjryanundefined

      Solved SD Card Structure Question and Typos

      • • davidjryan
      4
      0
      Votes
      4
      Posts
      83
      Views

      davidjryanundefined

      When we started this project 2 years ago, we put everything into the /sys folder because of the M98 info. I just wanted to make sure we weren't missing out on any fun by not having them in the /macros folder. We do not need them to show up in the DWC so I'll leave my files where they are.

      Thanks, gents!

    • ComedianTF2undefined

      M140 parameter for heating up multiple bed heaters

      • • ComedianTF2
      7
      0
      Votes
      7
      Posts
      213
      Views

      ComedianTF2undefined

      @droftarts thanks, have added a feature request:

      https://github.com/Duet3D/RepRapFirmware/issues/1103

      ComedianTF2 created this issue in Duet3D/RepRapFirmware open [FeatureRequest]: Assigning multiple heaters heaters for a single bed using M140 P0 H0:1 #1103
    • gratgrat27undefined

      Get the bit index of a line in a gcode file

      • • gratgrat27
      6
      0
      Votes
      6
      Posts
      152
      Views

      gratgrat27undefined

      Ok perfect I could restart from the desired index thank you two.

      There are many things I don't get on M24 though, It is using the resurect file, but modifying the M26 line of the resurect file does not modify the resume index. I guess there are hidden actions at a deeper level!
      Is there any documentation I can read to understand it better?

      Alex

    • konvalmundefined

      Declaration of conformity for Duet 3 Expansion 3HC

      • • konvalm
      2
      0
      Votes
      2
      Posts
      58
      Views

      T3P3Tonyundefined

      @konvalm please email sales@duet3d.com

    • Tech_Sam03undefined

      Solved Input shaping on Expansion Board

      • • Tech_Sam03
      5
      0
      Votes
      5
      Posts
      157
      Views

      dc42undefined

      @Tech_Sam03 thanks for pointing this out. I have corrected the text.

    • jltxundefined

      custom mcode documentation

      • • jltx
      6
      0
      Votes
      6
      Posts
      165
      Views

      chrishammundefined

      @jltx DSF is written in C#, so the official API bindings are provided as .NET (NuGet) packages. As a good start for custom codes using a C# application I'd recommend the DuetPiManagementPlugin source code. If you prefer Python, check out the links @droftarts shared.

    • MaxGyverundefined

      Solved Broken documentantion links for Bookworm DuetPi 64-bit images

      • • MaxGyver
      6
      0
      Votes
      6
      Posts
      107
      Views

      chrishammundefined

      @MaxGyver @droftarts Looks like Chromium-based browsers don't like plain http links, I replaced them again with https and that appears to fix it.

    • jltxundefined

      Solved 31 Temp compensation

      • • jltx
      2
      0
      Votes
      2
      Posts
      70
      Views

      droftartsundefined

      @jltx Thanks, fixed!

      For example, G31 Z1.2 T0.02 S20 H2 when sensor 2 measures 26C would calculate trigger height as 1.2 + 0.02x6 = 1.32mm

      Ian

    • Exerqtorundefined

      Solved Dead picture link in the docs.

      • • Exerqtor
      3
      1
      Votes
      3
      Posts
      139
      Views

      droftartsundefined

      @Exerqtor Thanks, fixed! Just a missing forward slash in the image link.

      Ian

    • Shokiundefined

      Duet3D Offline Documentation

      • • Shoki
      2
      0
      Votes
      2
      Posts
      126
      Views

      droftartsundefined

      @Shoki As far as I'm aware there's no way to download the whole wiki. You can save individual pages as pdfs (they come out okay for me, though the tabbed content doesn't work) or html web pages (in Firefox I chose "Save webpage as..." > "HTML, complete", though again tabbed content doesn't work). Why do you need clickable links if you're not going to be connected to the internet?!

      The pages are formatted in markdown, so I can supply you with a text file of the page, and you could view it in an offline markdown viewer. Note that pages, and particularly the Gcode dictionary page, are frequently updated.

      Ian

    • print_everythingundefined

      Unsolved Documentation Location for 6XD Rev1.02

      • • print_everything
      5
      2
      Votes
      5
      Posts
      126
      Views

      print_everythingundefined

      @T3P3Tony
      Thanks I appreciate it.

      Are there updated Kicad and step files somewhere?

    • achrnundefined

      Roto toolboard spec error?

      • • achrn
      2
      2
      Votes
      2
      Posts
      99
      Views

      dc42undefined

      @achrn thanks for pointing this out. I have corrected it.

    • NineMileundefined

      Meta gcode result variable inconsistent with docs

      • • NineMile
      11
      1
      Votes
      11
      Posts
      797
      Views

      T3P3Tonyundefined

      @NineMile thanks!

    • davidjryanundefined

      Switch to unstable packages commands

      • • davidjryan
      4
      0
      Votes
      4
      Posts
      148
      Views

      droftartsundefined

      @davidjryan There are also the instructions here: https://github.com/Duet3D/DuetSoftwareFramework/wiki/SBC-Setup-Guide#unstable-package-feed
      Though I think they are the same is in the wiki.

      Are you on Debian Buster? You should be on Bookworm to run 3.5 or newer. We recommend starting with a new DuetPi image, as trying to upgrade from Buster to Bookworm breaks too much. See https://docs.duet3d.com/en/How_to_guides/SBC_Buster_to_Bookworm

      If you're still having problems, and reverting to an older version, you probably need to run the 'Downgrade packages' instructions: https://docs.duet3d.com/en/User_manual/Machine_configuration/DSF_RPi#downgrade-packages or https://github.com/Duet3D/DuetSoftwareFramework/wiki/SBC-Setup-Guide#downgrading-to-stable-packages

      Ian

    • Chrissundefined

      M308 max senseors not correct?

      • • Chriss
      6
      0
      Votes
      6
      Posts
      221
      Views

      dc42undefined

      @Chriss you are right, the M308 documentation was misleading. I have removed the reference to the maximum number of sensors being 32. Thank you for pointing this out.

    Unless otherwise noted, all forum content is licensed under CC-BY-SA