Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.4k
    Topics
    89.1k
    Posts

    undefined

    To anyone in the future that is creating files, like hand typed gcode in "text editor" on their Pi and can not figure out why DWC "upload and start" won't recognize the file its because the file name needs to end with .txt (or .gcode, etc). The Pi text editor doesn't have a file extension by default. A bit of a doh moment for me when it slapped me in the face

  • Using Duet Controllers

    833
    Topics
    7.5k
    Posts

    undefined

    @dc42 said in warning: received malformed responses:

    @R006 which version of PanelDueFirmware are you using? RRF 3.6 requires version 3.5.1. The "malformed responses" messages may occur because you are using an older version.

    Panel version is 3.4.1, but this warning appears after resume APF only, in normal printing this warning is not appears.

  • Ask questions about the hardware capabilities, compatibility, wiring etc. here.

    8.6k
    Topics
    77.0k
    Posts

  • Discuss Duet on CNC machines other than 3d printers and laser cutters

    587
    Topics
    5.1k
    Posts

    undefined

    @mrehorstdmd the MCU in Duet 2 doesn't have a true random number generator so it will use the system tick counter as the seed. The tick counter increments at 120MHz once the processor clock has been set up. So even a small change in the timing of e.g. reading config.g from the SD card or homing the axes would change the seed. Let me know if you don't find it to be random, in which case I could look at using the CPU temperature to contribute to the seed too.

  • Prototype hardware issues.

    29
    Topics
    830
    Posts

    undefined

    @tcpl this is an interesting design. I will develop the firmware to support it.

    The behaviour of the rotary axes depend on whether they are connected to the starting point (e.g. connected to the bed) or the endpoint (hot end or drill). Connected to one or the other changes the direction of the rotation. I will probably change the definitions and configuration to a general description. I will have to think about how to define it with the M669 parameters easiest.

  • Discuss Duet on laser cutters and engravers.

    184
    Topics
    1.5k
    Posts

    undefined

    @jimakron said in Trouble firing 45 watt TTL Laser on "output6_buff" PMW:

    Given the IN pin accepts 0-5 VDC or PWM I suspect that you need to connect a resistor (1K should be suitable) from the 5V_EXT pin to the out6_buff pin.

    Frederick

  • Ask questions about installing the firmwares here

    2.1k
    Topics
    23.7k
    Posts

    undefined

    Many of the past upgrades (3.6 series) on SBC failed to fully complete with the Mini 5+ firmware still on the previous version.

    This has been easily corrected by running sudo dpkg --configure -a

    Reporting this in case something needs to be addressed.

  • Speed, acceleration, microstepping etc - post your experiences of and questions about how to get the best out of the Duet WiFi here.

    5.3k
    Topics
    54.9k
    Posts

    undefined

    @sebastianwac

    Well one possible answer is that the X homing command simply isn't moving as far as you think it is going to move.

    We need to see the actual homing code for X.

    Also, have you verified that the X axis steps-per-mm setting is correct?

    Frederick

  • Discuss using conditionals, loops and variables in gcode

    799
    Topics
    5.7k
    Posts

    undefined

    @awitc

    echo >"/sys/coef.g" "set global.coef = {global.coef}"

    Extending on what @dc42 stated above, it’s fine to permanently store a variable like this, but it comes at a cost. You only need the file storage for some parameters to survive a reboot, reset or shutdown. During runtime, global variables do the job.

    Now, if you have two macros, one to store a set of globals, and one to restore these from disk (SD card), you just have to spot some events who potentially lead to a reset/shutdown, such as pause or end of print, and call the ”store” macro on these events.

    The ”restore” macro has to be called only once, either at the end of your config.g or when you start a print - whatever suits your needs.

    Essentially, you just have to write the ”store” macro, as it creates (by using ”echo”) an executable file which then IS the ”restore” macro. If you need some sample code on how to compose complex expressions, just drop a note.

    I completely missed having a G4 P1 executing at EVERY loop iteration.

    Well, that’s just a millisecond. However note the usage of G4 at this line in your daemon.g:

    G4 P{var.dt} ; loop delay, 500ms, P = [ms], S = [s]

    This one is essential for granting time to parallel processes. For details, look up the ”daemon” sections from the links in my previous post.

    If a macro has to wait for the completion of some code in the printing queue or from another macro, don’t use a delay, use M400 instead.

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.1k
    Posts

    undefined

    @airscapes it would be worth updating to firmware 3.5.4. If your system includes a PanelDue, please update that to the latest firmware (3.5.1) too.

  • Feedback for docs.duet3d.com

    117
    Topics
    561
    Posts

    undefined

    @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

  • We'd love to know what your Duet electronics is controlling! When you have your Duet up and running and controlling a 3D printer or other machine, please tell us about it here.

    Example setups and prints
    806
    Topics
    9.8k
    Posts

    dwuk3dundefined

    Having trouble getting the same Hanpose Nema11 x 28 lead screw motors for last extruder in a reasonable time.

    Considered ordering normal Nema11's, couplers and lead screws.

    But decided to go for these instead - will have to take them apart and cut down the lead screw - but delivery in a few days.
    I also get a free linear rail and carriage which might be useful -

    Also ordered a second ball probe for dimensional alignment

    Screenshot 2025-05-10 at 13.30.03.png

    Screenshot 2025-05-10 at 13.33.41.png

    Screenshot 2025-05-10 at 13.35.50.png

  • Report issues or feature request for the online RepRapFirmware config tool (https://configtool.reprapfirmware.org)

    117
    Topics
    795
    Posts

    jay_s_ukundefined

    @Akhteh no good asking here, no one uses marlin...

  • Discuss software & plugins that work with the Duet/RepRapFirmware ecosystem.

    DueUI
    180
    Topics
    2.5k
    Posts

    undefined

    @chrishamm
    Thanks. Confirmed working with first=0

  • Accessories and Add-ons

    67
    Topics
    603
    Posts

    undefined

    @AlexKid Hi, sorry I missed your messages
    Well, it's great that you are working at it.
    My plans changed, I got a bit tired of tinkering so I bought a p1s)

    But my duet printer is still here and when I finish input shaping setup and cooling duct I might think about ercf. But then I will have another problem that I would need to install a cutter somehow. Though for a dual extruder printer multicolor ability would be great)

  • Forum for discussing the Duet3d Filament Monitor

    397
    Topics
    3.9k
    Posts

    T3P3Tonyundefined

    @adrien_tobeca more recent firmware reports the raw angle:

    M591 D0 Duet3D Roto magnetic filament monitor, enabled always, 25.20mm/rev, allow 10% to 190%, check printing moves every 2.0mm, agc 45, raw angle 354, no calibration data

    Also you can use the "S" parameter in M591 to monitor movement all the time if you prefer:

    Sn 0 = disable filament monitoring (default), 1 = enable filament monitoring when printing from SD card, 2 = enable filament monitoring all the time (S2 is supported RRF 3.5.0 and later ). Filament monitors accumulate calibration data (where applicable) even when filament monitoring is disabled

    https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m591-configure-filament-sensing

  • Discuss the smart PCB effector for delta printers here.

    412
    Topics
    4.1k
    Posts

    droftartsundefined

    @mickeey

    the smart effector is original duet and the problem is there. the card was on another printer and never had problems

    I think the fan0 connector failed because you wired the fan backwards. If you want to fix it, try replacing the MOSFET. See https://docs.duet3d.com/en/User_manual/Troubleshooting/Parts#fan-mosfet

    I think you should also check the plug on the Smart Effector that connects to the Duet 2 board. These pins look like they are not fully inserted into the housing. There also looks like there might be some wires poking out, that may cause a short.

    9178fd43-e865-41a2-a068-e377984f2959-image.png

    you had region on fan 2 everything works. thanks for all the support

    Great, glad you got it working. Please check the above.

    Ian

  • No decsciption available

    233
    Topics
    1.9k
    Posts

    oliofundefined

    @o_lampe if you just want to know whether the filament is loaded, you can try using stall detection on the extruder for that.

  • Discuss PanelDue connection, operation, firmware, enclosures and usage here.

    686
    Topics
    5.4k
    Posts

    Phaedruxundefined

    Are they displaying correct on the web control?

    What exactly are you seeing on the PanelDue? Photo?

    Can you describe the heater layout for the printer?

  • Discuss how to use third-party Z probes, filament sensors, endstop switches and other hardware with Duet electronics here.

    208
    Topics
    2.2k
    Posts

    undefined

    @phoenix

    Hello, thank you for sharing this. I have a question — I own a ToolChanger controlled by a Duet 3 MB6HC board, and there are 4 tools installed. Tool “T4” is a Smart Orbiter V3.0, which is connected to a ToolBoard 1LC V1.3. I was wondering whether it is possible to use the functionalities of the Smart Orbiter V3.0 by connecting them directly to the ToolBoard 1LC V1.3. Thank you in advance for your reply, it would be a great help.

  • Third-party plugins for DuetWebControl and DuetSoftwareFramework (SBC) can be found in here

    129
    Topics
    1.3k
    Posts

    Sindariusundefined

    @oozeBot This is looking amazing! Great job!! Always room for more viewers 🙂

  • RepRapFirmware on other controllers

    30
    Topics
    364
    Posts

    CrazyCreatorundefined

    @CrazyCreator
    For anyone who has the same problem after me, here's how to connect or insert the ribbon cable.
    You have to flip the small black bracket upwards, then insert the cable, and then flip the bracket back down. This secures the cable.
    Of course, you should have known beforehand that there is a bracket on these mini jacks.

    IMG_0786.jpeg

  • STM based control boards

    48
    Topics
    384
    Posts

    undefined

    @dc42 @gloomyandy @achrn

    found the issue the 8 pin connector was the issue thanks to all of you

  • LPC based control boards

    17
    Topics
    156
    Posts

    undefined

    @gloomyandy said in RepRap Firmware Issue in behavior:

    M98 P"config.g"

    Hi @gloomyandy I appreciate your help on this below the outcome of M98P "Config.g", I agree with you some information might be strange in my Config.g file like the S because I added it without exact knowledge of the functionality so I thought that might Improve the result. but i do not know the actual value I should add :).

    Actually this is an old project i never finish as not dedicated to however since i am working on again i would like to know how should i move on below is a picture of the machine as i was not able to upload video due to the size

    I uploaded while the machine in action however if you notice that the circle is not exactly circle it looks like defected circle you can tell however in the square it is more clearer

    9/26/2022, 12:21:35 AM M98 P"config.g"
    HTTP is enabled on port 80
    FTP is enabled on port 21
    TELNET is disabled
    Error: bad grid definition: Too many grid points; suggest increase spacing to 58.4mm
    9/26/2022, 12:17:55 AM M122
    === Diagnostics ===
    RepRapFirmware for LPC176x based Boards (biquskr_1.4) version 3.2_4 running on LPC176x at 100Mhz
    Used output buffers: 1 of 16 (11 max)
    === RTOS ===
    Static ram: 4956
    Dynamic Memory (RTOS Heap 5): 7896 free, 7856 never used
    Allocations: 178 Frees: 21
    Never used RAM 256, free system stack 14 words
    Tasks: NETWORK(ready,187) HEAT(blocked,243) MAIN(running,354) IDLE(ready,21)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 00:01:25 ago, cause: [software]
    Last software reset at 2022-09-26 00:16, reason: User, GCodes spinning, available RAM 256, slot 0
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0042a000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
    Error status: 0x00
    Aux0 errors 0,0,0
    Supply voltage: under voltage events: 0
    Driver 0: position 0, standstill, SG min/max 0/10, error r/w 0/1, ifcnt 73, cnt r/w 7165/15, timeout 0, failedOp 0xff
    Driver 1: position 0, standstill, SG min/max 0/0, error r/w 0/1, ifcnt 68, cnt r/w 7168/12, timeout 0, failedOp 0xff
    Driver 2: position 0, standstill, SG min/max 0/18, error r/w 0/1, ifcnt 73, cnt r/w 7165/15, timeout 0, failedOp 0xff
    Driver 3: position 0, standstill, SG min/max 0/0, error r/w 0/1, ifcnt 63, cnt r/w 7169/11, timeout 0, failedOp 0xff
    Driver 4: position 0
    Driver 5: position 0
    Driver 6: position 0
    Date/time: 2022-09-26 00:17:51
    Slowest loop: 20.93ms; fastest: 0.13ms
    Step timer: target 34955404 count 84948299 delta -49992896 late 0
    USBSerial connected 0
    ADC not ready 2 ADC error threshold 10 ADC Init 1
    Ints: 51516; Calls 51516; fast: 3uS; slow 20uS adj 0 bad 0 big delta 0
    PWM Channels
    Delta -822796941 Start -1 End -1
    === Storage ===
    Free file entries: 6
    SD card 0 detected
    SD card longest read time 2.3ms, write time 0.0ms, max retries 0
    === Move ===
    DMs created 40, maxWait 20302ms, bed compensation in use: none, comp offset 0.000
    === DDARing ===
    Scheduled moves 7, completed moves 7, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === Heat ===
    Bed heaters = 0, chamberHeaters = -1
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP is idle in state(s) 0
    File is idle in state(s) 0
    USB is idle in state(s) 0
    Aux is idle in state(s) 0
    Trigger is idle in state(s) 0
    Queue is idle in state(s) 0
    Daemon is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 42.51ms; fastest: 0.00ms
    Responder states: HTTP(0) HTTP(0)
    HTTP sessions: 1 of 2

    WiFi -
    Network state is active
    WiFi module is connected to access point
    Failed messages: pending 0, notready 0, noresp 0
    WiFi firmware version 1.25-01LE-D
    WiFi MAC address c0:56:27:45:b2:f9
    WiFi Vcc 3.37, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 35944
    WiFi IP address 192.168.1.134
    WiFi signal strength -68dBm, mode 802.11n, reconnections 0, sleep mode modem
    Clock register 00181001
    Socket states: 0 0
    Untitled.jpg20220926_230657.mp4

  • Other control boards that are not specifically LPC or STM based

    42
    Topics
    602
    Posts

    T3P3Tonyundefined

    @Rat-Rig-CS thanks for your response and for how this had been handled.

    From our side part of the issue was between how warranty issues are handled when a product is supplied from a reseller, vs a board supplied with a complete product (be it a kit or an assembled machine):

    For a reseller supplied product, referral to the forum is the correct procedure. For a product incorporated in kit or complete machine we expect the manufacturer to handle the warranty process (and communicate with us directly, if there is a fault with the board).

    The basic idea being a machine sold as a complete product, which the manufacturer has control over would not be expected to have configuration or wiring issues that we want to debug here on the forum before confirming a hardware fault.

    We will update our T&Cs to make this clearer.

  • Future Direction

    14
    Topics
    196
    Posts
    No new posts.

  • Categories for specific issues with Beta and Release Candidate (RC) versions of RRF 2 and RRF 3

    1.2k
    Topics
    15.3k
    Posts

    undefined

    @dc42 said in [3.6.0-rc.3] sticky probe with 1HCL board:

    Don't enable the pullup in the M558 command. There is a permanent pullup resistor on that pin.

    AH, good to know.

    In the full run I see that hex digit swap between 1 and 3, but it's more often 3 than 1 (should alternate if it is working 100% of the time correctly).
    I'll drop the pullup and do some more tests.

  • Discuss and contribute to the Duet Software Framework

    132
    Topics
    1.1k
    Posts

    davidjryanundefined

    @chrishamm @T3P3Tony
    Looking at CodeLogger did help me figure a few things, thanks for that push.

    After some testing, the EXECUTED mode is what I need. I was only testing the PRE and POST interception modes previously.

    I am having issues with the sample program https://github.com/Duet3D/dsf-python/blob/v3.6-dev/examples/custom_m_codes.py

    My desire is to capture ALL error messages. Currently I am receiving just those that are generated by G/M/T codes.
    I want to do exactly what the first comment in the sample program is stating, capture the whole G-code stream (no filters).

    It crashes on the non-G/M/T codes being intercepted (the
    cde = intercept_connection.receive_code()
    call) and the reported exceptions are a bit Greek to me.

    If I change the interception mode from EXECUTED to POST, I get the non-G/M/T intercepts but lose the G/M/T intercepts completely, though the program does not crash. So I don't know if what I am facing is an issue the sample script or the binding call itself.

    Who might be the python guru for dealing with the dsf-python bindings? Is it @Falcounet ? I see AndyEveritt is pushing a lot of the contributions for dsf-python on git. Does he have a handle on here?

  • If you are adding features to the firmware yourself, discuss what you are doing here.

    406
    Topics
    3.2k
    Posts

    undefined

    @umutduman said in Duet 2 WiFi stuck in SAM-BA after SPI firmware update:

    @dc42 that is PsoC which is supplying by 3.3v

    I don't know what you mean by PsoC. However, when two microcontrollers communicate with each other and they are powered separately, it is important to ensure that when only one of them is powered, the outputs of that one cannot feed more current into the inputs of the second one than the maximum rated injection current of the second one. So my guess is that at some time, your other MCU was powered ands the Duet was not, causing the other MCU to feed injection current into the Duet input. In fact the SAM4E MCU on the Duet doesn't have an injection current rating, implying that injection current isn't allowed at all. Even if injection current doesn't burn out the input pin protection diode, it may trigger parasitic SCRs in some chips that then cause catastrophic damage.

    Our Duet 3 main boards use an SPI connection to the optional attached Raspberry Pi or similar SBC and we have to avoid damage when just one of the Duet and the Pi is powered. We connect the SPI signals via buffers that are designed to handle inputs that are referred to a different power rail from the outputs. You can find the schematic and the part numbers of those buffers in Github, for example at https://github.com/Duet3D/Duet3-Mainboard-6HC/tree/master/Duet3_Mainboard_6HC_v1.02.

  • Prototype hardware issues.

    50
    Topics
    675
    Posts

    undefined

    @ash100 what is your reason for wanting to reduce microstepping to x8?

  • Suggestions for additional hardware to interface with the DuetWifi. Also suggestions for Changes to the DuetWifi hardware (although the hardware design is pretty fixed now!)

    130
    Topics
    1.3k
    Posts

    T3P3Tonyundefined

    @Aurimas the 1HCLs allow you to use a range of stepper motor + encoders

    Yes you could use servos with integrated drivers and then use a 6XD to drive those 4 motors

  • How would you like us to improve the firmware, and which improvements should we make first? Tell us here.

    948
    Topics
    7.5k
    Posts

    Phaedruxundefined

    @wieman01 The post above yours describes a way to do it.

  • Do you have an idea for a cool new feature in Duet Web Control? Post it here!

    331
    Topics
    2.1k
    Posts

    undefined

    @T3P3Tony

    If you go to the General section of the DWC there are a number of options/values that can be set/changed.

    So I was thinking that would be a place to have an "on/off" option that would change the behavior.

    As to M568 - I am using that.

    Here is a the relevant code from one of the filament config files:

    set global.print_beg_tool_temp_a [var.index] = 190 set global.print_beg_tool_temp_s [var.index] = 100 set global.print_beg_tool_ext_adj[var.index] = 100 set global.print_beg_tool_spd_adj[var.index] = 100 set global.print_beg_tool_bby_stp[var.index] = 0 set global.print_beg_tool_prime [var.index] = 10 set global.print_beg_tool_retract[var.index] = 0.5 set global.print_end_tool_retract[var.index] = 0.5 set global.print_beg_bed_temp_a [var.index] = 60 set global.print_beg_bed_temp_s [var.index] = 30

    Later on there is this code in another routine that applies these values:

    ; this part is just to make the use of these values down below a bit easier to read by using shorter names var bed_temp_a = global.print_beg_bed_temp_a [var.tool] var bed_temp_s = global.print_beg_bed_temp_s [var.tool] var tool_temp_a = global.print_beg_tool_temp_a [var.tool] var tool_temp_s = global.print_beg_tool_temp_s [var.tool] var ext_adj = global.print_beg_tool_ext_adj[var.tool] var spd_adj = global.print_beg_tool_spd_adj[var.tool] var bby_stp = global.print_beg_tool_bby_stp[var.tool] M568 P{var.tool} S{var.tool_temp_a} R{var.tool_temp_s} ; set extruder heater temps (active and standby) M221 D{var.tool} S{var.ext_adj} ; set extruder extrusion percentage adjust M140 S{var.bed_temp_a} R{var.bed_temp_s} ; set bed heater temps (active and standby) M220 S{var.spd_adj} ; set print speed adjust M290 R0 S{var.bby_stp} ; set initial baby steps

  • General discussion about 3d printing related subjects that are not duet specific.

    349
    Topics
    3.8k
    Posts

    undefined

    @dc42 I dont know why i didn't think about backlash. commented out the extra z movments and perfect!
    Thank you.

  • Off topic technical discussion area. Keep it clean please! Not for Duet related discussion (use the appropriate Duet forum)

    109
    Topics
    968
    Posts

    undefined

    This is not an advertisment and I won't name any specific sellers on US ebay but if you search for tdk lambda and flex power PSU's there's some great deals. I have been using an $800 Flex for the last couple weeks that I bought for $25. Has 5v 10a, 12v 5a, 2x24v 5a and 48v 8.5a. Purchased a tdk lambda with similar specs also for $45. It's surplus from decomisioned equipment but is in great shape and the seller has dozens of them. Don't buy potentially dangerous junk for the same price when you can get these.

  • Purchasing

    21
    Topics
    140
    Posts

    Exerqtorundefined

    @T3P3Tony tried to send a chat message, but i don't know if it worked. Never done it on this forum platform before.

  • Help with ordering, announcements etc

    160
    Topics
    948
    Posts

    T3P3Tonyundefined

    @TNO_Marc please email sales@duet3d.com. The online shop accounts are currently for OEMs and Resellers purchasing in volume. We also may be able to assist with a reseller near you.

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