1. Home
  2. Categories

Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.2k
    Topics
    87.6k
    Posts

    T3P3Tonyundefined

    @wayneosdias yes a pocket on the back of the motor shaft is ideal.

  • Using Duet Controllers

    823
    Topics
    7.4k
    Posts

    infiniteloopundefined

    @axiom 1736183041163-flow.jpg

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

    8.4k
    Topics
    76.0k
    Posts

    mrehorstdmdundefined

    @Dizzwold I used a 7mm thick PVC foam board- I don't recall the product name. It isn't very rigid so I braced it with square aluminum tubing so it wouldn't sag too much.

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

    564
    Topics
    5.0k
    Posts

    droftartsundefined

    @kai25 Are you using a Duet board to control the closed loop motor drivers? If so, which one, and how is it wired? Was it working before with normal stepper motors and drivers? What firmware version are you running (send M122 and post the response) and please post your config.g.

    Most problems with external stepper motor drivers are usually due to enabling them, or setting them up to accept step/direction input.

    Ian

  • Prototype hardware issues.

    21
    Topics
    760
    Posts

    T3P3Tonyundefined

    @Mr-Crispin he has done the kinematics calculations in his gcode generation program. so in this case the Duet does not "know" its multi axis printing. @JoergS5 has done some work in implementing variations of robot kinematics that run on the Duet boards themselves.

  • Discuss Duet on laser cutters and engravers.

    182
    Topics
    1.5k
    Posts

    T3P3Tonyundefined

    @aytact when you say you have written script to handle the test fire, what so you mean, a gcode macro or something else?

    and by simulating the test fire, can you explain what the test fire actually is supposed to do?

  • Ask questions about installing the firmwares here

    2.1k
    Topics
    23.4k
    Posts

    thaug29undefined

    @jay_s_uk
    #############################################################
    ; AutoZ - Automatic probe offset adjustment
    ;
    ; to use autoz, please place the following near the end
    ; of your slicer start gcode
    ; M98 P"/macros/autoz/autoz.g" <<< Place in slicer
    ;##################################################################

    ;##################################################################
    ; prepare
    ;##################################################################

    M98 P"/macros/autoz/autoz_settings.g" ; Load your settings
    M98 P"/macros/autoz/scripts/autoz_globals.g" ; Load autoz framework
    G29 S2 ; Disable mesh
    M290 R0 S0 ; Reset baby stepping

    ;##################################################################
    ; Probe the nozzle on teh Z-pin
    ;##################################################################

    ;G1 E-5 F1000
    M98 P"/macros/autoz/scripts/autoz_move_up.g" ; large z hop incase the nozzle is low and you have a high pin
    M400
    M98 P"/macros/autoz/scripts/autoz_goto_zpin.g" ; go to the z pin
    M400
    M98 P"/macros/autoz/scripts/autoz_adjust_safe_zdrive.g" ; set z drive safe physics
    M400
    M98 P"/macros/autoz/scripts/autoz_probe.g" K1 H5 A4 S0.004
    M400

    if !exists(global.macrocallresult)
    echo "Call to macro failed. Aborting"
    abort
    ;end if

    var nozzleheight = {global.macrocallresult}
    echo "nozzleheight: ", {var.nozzleheight}

    M98 P"/macros/autoz/scripts/autoz_restore_zdrive.g" ; restore the z drive to the state before autoz
    M400
    M98 P"/macros/autoz/scripts/autoz_move_up_small.g" ; move up 2mm
    M400

    ;##################################################################
    ; Load the magprobe
    ;##################################################################

    M98 P"/macros/autoz/scripts/autoz_move_up.g"
    M400
    M98 P"/macros/magprobe_attach.g" ; pick up and verify clicky
    M400
    M98 P"/macros/autoz/scripts/autoz_goto_zpin_magprobe_offset.g" ; move the clicky probe switch body over the z pin
    M400
    M98 P"/macros/autoz/scripts/autoz_adjust_safe_zdrive.g" ; set z drive safe physics
    M400

    ;##################################################################
    ; Probe magprobe body on the Z-pin
    ;##################################################################

    M98 P"/macros/autoz/scripts/autoz_probe.g" K1 H5 A4 S0.004
    M400

    if !exists(global.macrocallresult)
    echo "Call to macro failed. Aborting"
    abort
    ;end if

    var magprobeheight = {global.macrocallresult}
    echo "magprobeheight: ", {var.magprobeheight}

    ;##################################################################
    ; Probe the bed
    ;##################################################################

    M98 P"/macros/autoz/scripts/autoz_move_up.g" ; hop to clear the switch
    M400
    M98 P"/macros/autoz/scripts/autoz_goto_bedcenter.g" ; go to the center of the bed
    M400

    M98 P"/macros/autoz/scripts/autoz_probe.g" K0 H5 A4 S0.004
    M400

    if !exists(global.macrocallresult)
    echo "Call to macro failed. Aborting"
    abort
    ;end if

    var bedheight = {global.macrocallresult}
    echo "bedheight: ", {var.bedheight}

    ;##################################################################
    ; Calculate probe offset
    ;##################################################################

    var nozzleswitchoffset = {var.magprobeheight - var.nozzleheight + global.switchoffset}
    echo "nozzleswitchoffset: ", {var.nozzleswitchoffset}

    var probeoffset = {var.bedheight - var.nozzleswitchoffset}
    echo "probeoffset: ", {var.probeoffset}

    ;##################################################################
    ; Set probe offset as baby step offset
    ;##################################################################

    M290 R0 S{var.probeoffset}
    M400

    ;##############################################
    ; Finish up
    ;##############################################

    M98 P"/macros/autoz/scripts/autoz_restore_zdrive.g" ; restore the z drive to the state before autoz
    M98 P"/macros/autoz/scripts/autoz_move_up.g" ; small z hop
    M400
    M98 P"/macros/magprobe_dock.g" ; unload the clicky probe
    M98 P"/macros/autoz/scripts/autoz_goto_bedcenter.g" ; go to the center of the bed

    ;##############################################
    ; Done
    ;##############################################

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

    5.2k
    Topics
    54.4k
    Posts

    bug2k22undefined

    Just a brief follow up to this, I never could get a good first layer with this setup. I tried with a bltouch, inductive and IR sensors all gave similar results, the first layer was very inconsistent.
    I have now installed a dyze designs horizon z probe which uses the nozzle for z probing, mesh bed compensation now works as expected and I get very good, consistent first layers.

  • Discuss using conditionals, loops and variables in gcode

    769
    Topics
    5.5k
    Posts

    dc42undefined

    @T3P3Tony that's expected. A driver ID is not a number because it holds both the CAN address and the driver number at that address. However, it should be allowed as the P operand in a M569 command.

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.0k
    Posts

    T3P3Tonyundefined

    @jocanetto an important consideration is you have this on a university LAN so you are exposing an insecure control board to a large network with a range of curious students on it. (I once was one of those students...... 😈 )

    I highly recommend not doing that. A direct ethernet cable or a Lab only LAN or similar is the way to go

  • Feedback for docs.duet3d.com

    105
    Topics
    506
    Posts

    dc42undefined

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

  • 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
    796
    Topics
    9.4k
    Posts

    dwukundefined

    @dwuk Designs for all parts on right hand side now completed - and printing underway. Left hand side fairly easy to derive as is mostly a mirror copy - with some height changes.

    Biggest issue is losing about 25mm build volume at front due to idler and about 15mm at the back. Will need to address these two issues at some point.

    Also had to remove the tensioner spring part to save a bit of space - so will need to so how well the tensioning works with just the side bolts.

    BCF2222A-8907-4D1B-B570-2CE56E070C7F.png 3A2031CF-734D-491E-A740-7C51432C062F.png

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

    113
    Topics
    780
    Posts

    chrishammundefined

    @magnets99 said in M308 error with the W value, doc has - config does not:

    Next issue is even though i have selected 4 as my number of wires, it is submitting the W argument as "K"

    Shouldn't it be W4?
    And i think K is an argument for the thermister type letter.

    Thanks for reporting this, it's now fixed.

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

    DueUI
    174
    Topics
    2.5k
    Posts

    Theboz1419undefined

    Thank you, this looks promising

  • Accessories and Add-ons

    65
    Topics
    596
    Posts

    AlexKidundefined

    @Inlinebrother
    I'm working on it with an Duet2 Ethernet and RRF.
    For startingpoint I used https://github.com/pfn/EnragedRabbitOnRRF.
    Assambly is already finished, loading and unloading is working.
    First testprint still waiting for time unfortunataly.

  • Forum for discussing the Duet3d Filament Monitor

    396
    Topics
    3.9k
    Posts

  • Discuss the smart PCB effector for delta printers here.

    407
    Topics
    4.0k
    Posts

    shaunpplundefined

    @oarjjj said in v2.0 consistently increasing probe heights:

    I am starting to think it may be an issue with the E3d Lite6, possibly its spring is compressing? I'm not sure.

    There should be no compression available on the E3D lite 6 with a Revo nozzle as the compression spring is there to hold the nozzle heat-break assembly tight against the thread of the body after hand tightening it, so when in constant use it does not come undone and also to allow the heater element a degree of heat expansion.
    The only case i have ever had with a loose nozzle was with a customer who had not tightened it it up fully and they kept getting a very inconsistent filament laydown and jagged edges as it would oscillate as it was moving. I am running 3 Delta printers all Anycubic Predators converted to linear rails and all using version 3.5 on Mini + 5 boards and all the motors directly from the motherboard with the Hemera sx extruders without any expansions as I have never needed them nor have i ever any issues to warrant using expansion board as I get extremely good prints.

  • No decsciption available

    232
    Topics
    1.9k
    Posts

    droftartsundefined

    @andy Sorry you have a broken IR probe. We are happy to replace the board under warranty, but also happy if it's just a soldering issue and you want to fix it yourself.

    If you would like to replace it under warranty, please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

    Ian

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

    681
    Topics
    5.3k
    Posts

    dc42undefined

    I've just released PanelDueFirmware 3.5.1 at https://github.com/Duet3D/PanelDueFirmware/releases/tag/3.5.1. The main purpose of this release is to play more nicely with DWC when both are completing for RRF output buffers, which could lead to DWC disconnecting.

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

    203
    Topics
    2.2k
    Posts

    taeggeundefined

    I'm a big fan of the Duet3 / SBC setup, but the physical interface to a raspberry pi has always bothered me (Different mount points, separate 5v power supply). I intend to develop a daughterboard(?) with the same footprint as the 6HC that will interface a Raspberry PI CM5, and include lots of raspberry pi IO, and some quality of life features for cleaner 6HC/SBC installs.

    Features:

    most of the same IO as the CM5 IO board (ethernet, USB A, USB C, HDMI, DSI/CSI, microSD, m.2, fan connector) footprint and mounting holes identical to 6HC 26pin IO connector is in-line with 6HC such that an enterprising person could make a direct board-to-board connection (or more likely just use a very short ribbon cable) 40mm cooling fan for CM5, also cooling back side of 6HC (standard 4 pin connector) Accept 12v - 48v Vin similar to 6HC Some extra fused distribution of Vin 5v @ 5A switching power supply for raspberry pi 24v @ TBD A switching power supply (possibly 12/24v selectable?) for powering 1LC toolboards on systems with greater than 24v
    *On the bubble: pcb or chip wifi antenna (I'll likely be sandwiching the CM5 between the two boards, considering adding a separate WIFI antenna for fun, but may just opt for an external antenna. )

    I have a preliminary schematic and board layout, but was curious if others had ideas to consider before I order a prototype PCB. If I'm successful I'll of course share the design with the community, but I don't have any plans to produce any significant quantities.

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

    120
    Topics
    1.2k
    Posts

    axiomundefined

    @Notepad Thank you very much, unfortunately I only have the option to install the plugin...perhaps the other options are no longer available in version 3.5.4?

  • RepRapFirmware on other controllers

    29
    Topics
    318
    Posts

    droftartsundefined

    @Inlinebrother said in Duet 3 mini 5+/FYSETC Big Dipper on FFCP/Flashforge Creator Pro:

    I installed the bltouch and it's working perfectly fine. Though I was concerned that it is glowing red and not violet

    My genuine BLTouch has a red LED on all the time. I think there's a blue one, but it is very dull. I think the red one goes off when the probe is triggered, so you see the blue one, but that happens very quickly, so hard to spot. So I think that's normal.

    Ian

  • STM based control boards

    46
    Topics
    348
    Posts

    RodrigoRMaraujoundefined

    @gloomyandy and @jay_s_uk
    First of all, thanks for answering.

    I don't have enough knowledge to start a challenge like this, I have no idea how it would be done lol.
    Using canbus would be ideal, because I'm currently converting a machine running klipper, which has an ebb42 board in the car.
    Because of the difficulty, I think I'll opt to run all the wiring for the car's accessories (without canbus).

    I'm leaving klipper and converting my printers back to RRF because of the complexity of klipper (for me). I want to go back to the simplicity of RRF and not depend on an SBC running linux.

    Sorry for the bad English, translated by google.

  • LPC based control boards

    17
    Topics
    156
    Posts

    Shadi_Polarundefined

    @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.1k
    Topics
    14.7k
    Posts

    T3P3Tonyundefined

    @Argo please could you test if this is resolved in 3.6beta3. test builds are available here:

    https://www.dropbox.com/scl/fo/22qkmz3oqxo2jb97l7716/AMVS8V_burccxcC5HWIfwEk?rlkey=v5vi2k9q1qjqviq97otkjqn1g&dl=0. Please try them on your machine(s) if you can.

    Release notes are at https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-Beta#reprapfirmware-360-beta3-in-preparation.

  • Discuss and contribute to the Duet Software Framework

    124
    Topics
    1.0k
    Posts

    NineMileundefined

    @chrishamm said in DSF Failed to serialize code:

    @NineMile I think the messages from M291 are too long, so DSF cannot send them to RRF. The maximum length of a G-code is 256 bytes, which is exceeded by your logic, and depending on the number of parameters it's a bit lower in SBC mode due to the way G-codes are transferred. If you reduce the message length, it should work again.

    I'm going to change the error message in v3.6 to be more specfic.

    Gotcha, thanks for the clarification. It has definitely been fun trying to fit the M291 dialog contents into 256 bytes so yes, some of these could be right up against the limit (I know I pushed some over by adding the J2 parameter on some dialogs while testing with v3.6.

    I'll take another look at dialog lengths and see where these need to be sorted out.

    Thanks again 👍

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

    397
    Topics
    3.1k
    Posts

  • Prototype hardware issues.

    49
    Topics
    669
    Posts

    jay_s_ukundefined

    @aOne email sales@duet3d.com and you can discuss prices etc with them

  • 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!)

    127
    Topics
    1.2k
    Posts

    jay_s_ukundefined

    @Polyneutron21 i'm not sure what board you are talking about.
    beacon and cartographer don't support RRF and neither does the eddy probe

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

    941
    Topics
    7.4k
    Posts

    T3P3Tonyundefined

    I have raised a feature request for the firmware part of this here:

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

    T3P3 created this issue in Duet3D/RepRapFirmware open Support BISS-C encoders #1068

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

    328
    Topics
    2.1k
    Posts

    Chrissundefined

    Hi * and happy x-mas,

    I can remember that we had the discussion about the colours in the DWC and the temp chart, I remember from the top of my head that this colours are not configurable, aren't they?

    I do not feel very satisfied with some colours here:
    da570c88-d8bb-4e1b-84f4-20d6f1619c96-image.png
    Brown seams a bit low in contrast, the difference between Tool1 and tool3 is hard to tell. And the black on that nice gray looks very ruff to me.

    It would be very, very nice if we could make that configurable or if some colours would not be used, specially in some combinations liek this red and orange.

    Cheers, Chriss

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

    346
    Topics
    3.8k
    Posts

    oliofundefined

    @Pyper yeah and you can see a pretty neon-ish/pink leaning light/muted color palette on the print sample (-:

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

    106
    Topics
    962
    Posts

    DocTruckerundefined

    @droftarts excellent, thanks. Missed that post in my abscence.

  • 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
    946
    Posts

    Phaedruxundefined

    Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

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