Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.3k
    Topics
    88.4k
    Posts

    undefined

    @jay_s_uk You are correct, I re-connected all of it correctly and nothing changed. First time for everything. I have tried two different pi 5's and two different 26 pin to 40 pin GPIO and this was a new Pi 4B 8GB.
    20250312_171520[1].jpg

  • Using Duet Controllers

    828
    Topics
    7.5k
    Posts

    undefined

    @dc42
    Thank you for your response.

    If I want to change the pin number to light up LEDs, where should I modify the firmware code?

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

    8.5k
    Topics
    76.6k
    Posts

    undefined

    @adhanabal your very welcome hope you got what you needed to do done 🙂

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

    576
    Topics
    5.0k
    Posts

    undefined

    @ojje I think I have figured it out. 🙂

    b54da31a-9362-466b-afaf-2d5cc72239dd-image.png

  • Prototype hardware issues.

    26
    Topics
    805
    Posts

    undefined

    @dwuk3d Yeahh we use a geared linear actuator. For Z hopping I can see why they might be slow, but we only use them for aligning the IDEX tools, and in the future we indeed want to use them for mesh compensation as well. Both of them don't require high accelerations.

  • Discuss Duet on laser cutters and engravers.

    183
    Topics
    1.5k
    Posts

    undefined

    @Macwolf ok then. so you just need to connect the "L" connection to the duet. You will need to connect a ground connection, like on PSU type 2, to your power supply powering your duet

  • Ask questions about installing the firmwares here

    2.1k
    Topics
    23.6k
    Posts

  • 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.7k
    Posts

    undefined

    My diy printer is 600x600 build plate. I have 4 independent z ball screws. G32 is configured to loop until it gets to 0.0075 precision. That runs fine. When I run a mesh afterwards it shows the bed is high in the max y area, when I do the mesh 8x8 the variance is about .3 as if the bed is tilted in the end y travel. I switched to a 4x4 mesh, and the deviation is less than .1. Also the 8x8 bed mesh is wrong, 4x4 mesh looks accurate. I'm using a bl touch, could this be some bounce issue in bl touch, the more points I use the more wrong the mesh is.

  • Discuss using conditionals, loops and variables in gcode

    788
    Topics
    5.6k
    Posts

    undefined

    @SanderLPFRG

    Hi,

    Well I've done some preliminary testing.

    I created, by hand, a heightmap (X range from -90 to +90, Y range from -90 to +90) that had extreme Z offsets,

    Z offset by X range

    X=-90 to -54 : Z offset 0 X=-18 to +18 : Z offset 5 X=+54 to +90 : Z offset 0

    I then created some macros.

    Two to turn mesh compensation on and off
    Two to set the tool X offset to either +90 or 0
    Three to do G53 moves to -90, 0, +90

    My testing revealed what I thought to be true.

    Mesh compensation takes tool offsets into account.

    If the tool is outside the height map nothing seems to be done.

    Frederick

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.0k
    Posts

  • Feedback for docs.duet3d.com

    113
    Topics
    537
    Posts

  • 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
    799
    Topics
    9.6k
    Posts

    undefined

    @droftarts Looks good. The only comment I have is that in my current test configuration I have the M606 near the end of the Start Gcode in Orca Slicer, not at the start of the print file - just before it starts actual printing - as I didn't need homing etc. to be parallel processed.

    I wouldn't personally expect to put it in the start.g - as I wouldn't want every print to be forked, also I guess the Macro issue mentioned in this post might start occurring.

    https://forum.duet3d.com/topic/35023/mutiple-motion-systems-macro-conflicts-in-3-5/20?_=1741787414435

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

    116
    Topics
    793
    Posts

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

    DueUI
    178
    Topics
    2.5k
    Posts

    undefined

    @guywinslow
    Ok - that's good news but a mystery as to why it did not work the first time, as I assume you, effectively, just reinstalled from github.

    If you had used the version I posted yesterday - there would have been a duetBackup ONLY log created (along with additional debug information) that you could access directly using the DWC UI.

    The version that I sent to you yesterday will be the version posted in github soon. I do not use github for "in progress" builds - just for version bumps, once they are tested.

    While I have tested on my 3.6 beta build - It would be very helpful if you could validate it against your 3.5 build.

    Can you do that for me? I.e. Try the version I posted yesterday.

    P.S. The permissions dsf:dsf from the ls -l look correct - so there may have been some other issue.

  • Accessories and Add-ons

    65
    Topics
    597
    Posts

    undefined

    @Inlinebrother printing and filament change is working. Struggling with the servo, sometimes it will not engage completely. Will try to provide 6V instead of 5V power this should result in ~500g more force. If you are still interested in this topic you can contact me.

  • Forum for discussing the Duet3d Filament Monitor

    397
    Topics
    3.9k
    Posts

    undefined

    @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.

    409
    Topics
    4.0k
    Posts

    undefined

    Thanks for the follow-up. The one picture was taken before and one after but I just held the wire on there with my finger and did not solder it on. Thank you, I will send the email a little later. I do appreciate all the help from everyone!

  • 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.

    684
    Topics
    5.3k
    Posts

    undefined

    I found the reason for the problem. Perhaps you explain its nature. The steps motors of the axes A and B had 6 wires 4 of which were sweaty to the controller. After replacing the engines with 4 wired problems did not appear.

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

    206
    Topics
    2.2k
    Posts

    undefined

    My vision is almost fully realized! I must have jinxed myself in my last post. No show stoppers, but have hit a couple issues:
    1- you might notice the ethernet jack isn't soldered. It's just dry-fit for show right now. I removed it after realizing that my part didn't match the footprint i used. It was a physical fit, but pins were wrong. I could only find the matching part overseas, so still waiting. I intend to update the schematic/layout to use a more common magjack. In the meantime wireless is working great.
    2- the 12v/24v regulator isn't behaving all the way up to 5A. It's fine up to 3A, but starts cutting out above 4A. I forgot to upgrade the inductor and diode when I moved my target from 3A to 5A. That's probably part of it. I need to take another look at the layout too. Thankfully 5v appears reliable all the way up to 5A. The printer i'm going to test this out on doesn't need the aux supply, so no biggie for now.
    3 - when I added the Molex KK PC style fan header, I mistakenly assumed the Pi5's 4 pin connector followed the same standard. Nope. Easy fix. Happy accident to get to trim the wires down and solder in the correct places. (I guess I could have rearranged the connectors too, but ick)

    Next step is to actually connect to a Duet3 🙂

    IMG_9231.jpg IMG_9232.jpg

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

    126
    Topics
    1.3k
    Posts

    undefined

    @chrishamm

    I understand the refresh - that was a secondary thing. I'm not too fussed, now that I know its not a bug / issue.
    Cosmetically - I think it would benefit from consistent language.

  • RepRapFirmware on other controllers

    30
    Topics
    321
    Posts

    undefined

    @dc42 said in Set Z height Max For clay Delta printer:

    @JetClay one option may be to use G30 S-1 to do manual probing without setting the Z height to zero. Then run this:

    G10 L2 Z{sensors.probes[0].lastStopHeight}

    This will set the Z offset of the workplace to that height. Or you could use:

    G10 L2 Z{move.axes[2].userPosition}

    since the current Z position will be the same. Or even:

    G10 L20 Z0

    You can include

    G10 L2 Z0

    in your homedelta.g file to reset the offset to zero when you home the printer again.

    Thank you very much for your response we finally made it work! we used this code

    ; SetZHeight.g - Manual Z height calibration & M665 H update
    M291 P"Ensure the nozzle is clean. Press OK to continue." R"Z-Height Calibration" S3

    G28 ; Home all axes completely before probing
    M665 ; Print current M665 values for reference

    ; Ensure previous height offsets are cleared
    G10 L2 Z0

    M291 P"Move the nozzle down until it just touches the bed. Press OK when done." R"Manual Adjustment" S3 S2

    G30 S-1 ; Perform manual probing without setting Z=0

    M291 P"Extracting new height offset..." R"Processing" S1

    ; Ensure latest calibration data is loaded before changing M665 H
    M501 ; Load saved config-override.g (M665 H value)

    ; Capture the last probe height and set Z offset
    G10 L2 Z{sensors.probes[0].lastStopHeight}

    ; Update M665 H dynamically based on last saved value
    M665 H{move.kinematics.homedHeight - sensors.probes[0].lastStopHeight}

    ; Save new M665 H for persistence
    M500 ; Save parameters to config-override.g

    M291 P"Calibration complete! The new Z height and M665 H value have been saved." R"Success" S1
    M501 ; override config file
    G28 ; Home axes

    Hope it works for maore people!

  • 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

    undefined

    @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.0k
    Posts

    undefined

    It seems that replacing the CAN cable solved the problem. It's strange but after about 30 hours of printing the problem did not appear. So please close this topic. Thanks for your help.

  • Discuss and contribute to the Duet Software Framework

    129
    Topics
    1.1k
    Posts

    undefined

    @LindsayC

    And finally if you run this code where you just pass a string to the P parameter.

    var ind = 0 var driverAddress = "51.0" M569.1 P{var.driverAddress} T2 C1000 S200 R150 I50 D0.1 V500 A1 E4.0:2.0 D1;

    You get this error message:
    Error: in file macro line 3 column 27: M569: expected driver ID

    Which is different to the error message you get if the variable is obtained from the object model.

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

    403
    Topics
    3.2k
    Posts

    undefined

    @Triet I guess if one is using the feedforward in the way intended, the temperature shown is the target temperature. I have been playing with the parameters, trying to understand how they work. I am trying out a 0.25mm nozzle, which has an extrusion rate of about 8.8cumm/sec with 0.125mm layers at 140mm/sec, which is think corresponds to about 3.6mm/sec for 1.75 filament. A T parameter of 12 seems to give the expected increase of just greater than 40deg over the base temperature. I think there is a bit of under extrusion at this speed with the 0.25 nozzle, but checking that out. For my standard 0.4 cht nozzle, 0.2 layers give about 22cumm/sec at 140 mm/sec, that is about 9mm/sec filament. Using T5, this gives the expected increase of about 45deg above base temperature. I dont think the cht nozzle is underextruding under these conditions. I have just started using an S parameter of 1.0, and this seems to work fine with the 0.25 nozzle - not tried with the 0.4 nozzle yet. Tried increasing the A parameter to 50, and the feed forward stops working.
    I have been using M570 H1 P15 T45, and not been getting heater faults. The revo nozzle setup I am using has a low thermal mass, and seems to be controlled very well by the duet.

  • Prototype hardware issues.

    50
    Topics
    675
    Posts

    dc42undefined

    @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

    undefined

    @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.

    944
    Topics
    7.4k
    Posts

    undefined

    @droftarts Thank you I will look into this GitHub link. Hopefully the feature is implemented soon. In the meantime, I will try to add the functionality so I can learn more about RepRap firmware.

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

    329
    Topics
    2.1k
    Posts

    chrishammundefined

    @pixelpieper I'm going to adjust the minimum of the temperature chart dynamically in the next build. It will be the lowest value of the configured temperature presets or heaters[].min.

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

    348
    Topics
    3.8k
    Posts

    droftartsundefined

    @fcwilt send an email to the email address @elmoret gave you, with the details he asked for, and he’ll send you a pre-paid shipping label.

    Ian

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

    108
    Topics
    967
    Posts

    undefined

    Maybe some more details about the project.

  • 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

    undefined

    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