Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.3k
    Topics
    88.6k
    Posts

    undefined

    @btmclain we've seen this once before. The cause was identified as high backlash in the drive chain between the motor and the axis. In the version 3.6.0-rc.1+3 binaries at https://www.dropbox.com/scl/fo/geqmn8gbn97n6b587mkbk/AJ2hBIqO-L57_QpR_uqHJ9c?rlkey=fw37wycbp2gil8rvxhe7aopy7&dl=0 I've increased the amount of backlash allowed when using a linear composite encoder, so that version might work for you. To use it you will need to update your whole system to firmware 3.6. If you are running in SBC mode then update to 3.6.0-rc.1 first, then you can install the 3.6.0-rc.1+3 binary on the 1HCL.

  • Using Duet Controllers

    828
    Topics
    7.5k
    Posts

    undefined

    @gsch1803 said in Unresponsive duet 3 6HC board:

    @Phaedrux I believe it was purchased from Amazon in October

    Who is the amazon seller?

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

    8.5k
    Topics
    76.7k
    Posts

    undefined

    @U-Friedrich said in Control of SG90 hobby servos - which mainboard:

    Have I understood this correctly?

    Yes; although if you are looking to reduce cost then if you wish you could drive the first two hot ends/extruders/servos directly from the Duet 3 Mini. This would leave you with 3 drivers to control the axis motors, or 5 with the optional 2-driver daughter board.

    @U-Friedrich said in Control of SG90 hobby servos - which mainboard:

    Another question in advance: if you control the servo via the G-code commands M280, can I influence the speed at which the servo moves to the end position?

    Analog hobby servos don't provide that degree of control. You might be able to achieve lower speeds by using M280 in a loop that gradually changes the commanded position between the initial and final required positions. You can also reduce the speed of a hobby servo by reducing the supply voltage, For example, if using a 5V supply then you could put 1 or 2 silicon diodes in series with the 5V wire to the servo. If you reduce the voltage too much then the servo will stop working, or may work but not provide as much force as you need.

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

    579
    Topics
    5.0k
    Posts

    undefined

    @meki05 if you don't want to read those sensors independently then you could connect both in parallel to a single temperature sensor input, and set the R parameter in the M308 command to double the standard value to compensate for that. The standard value is 2200 on Duet 3 boards.

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

    undefined

    @jltx said in SZP for bed level in 3.6-RC1:

    @Phaedrux said in SZP for bed level in 3.6-RC1:

    https://docs.duet3d.com/User_manual/Machine_configuration/SBC_setup#update-firmware

    I know how to do that when the firmware is via a depot but this is from a dropbox so I assume there is a manual procedure. Do I need to sftp them over?

    Are you already on the unstable branch? If so, you should be able to upload the bin file and send M997 to flash to it. See here for parameter details for M997 in SBC mode.

    https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m997-perform-in-application-firmware-update

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

    undefined

    @ianborg From the heater curve on the graph you posted, it does look like the heater is getting close to the maximum heat it can achieve. Controlling it at this point does get a bit squirrelly, because the heating rate isn't what is expected. Not much you can do about that, apart from what you've already done, unfortunately. Did you tune it at 90C with M303, or lower?

    Ian

  • Discuss using conditionals, loops and variables in gcode

    791
    Topics
    5.6k
    Posts

    undefined

    @Mike-1
    Oh no, it crashed my z-offsets. But why? I implemented it it in the start gcode

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.0k
    Posts

    undefined

    @Piet please post a photo showing how you have connected that cable to the Duet.

  • Feedback for docs.duet3d.com

    115
    Topics
    547
    Posts

    undefined

    Tested it out using both 3.5.4 and 3.6.0 RC1

  • 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
    801
    Topics
    9.7k
    Posts

    dwuk3dundefined

    Nema8 update - spent quite a lot of time yesterday (in between looking at Bambulab H2D videos) trying to get my improved Nema8 design to work.

    Either the motors are getting weaker or my design has introduced more resistance - as the motors no longer seem to be able to lift the extruders despite a few changes to the 3d printed components and oiling up the linear rail.

    Also managed to mess up firmware on Mini5+ and 6HC board again as I thought 3.6.0 Rc1+3 might be having some impact on Nema8 motor power -

    Accidentally downgraded to 3.4.0 instead of 3.5.4 - which the Mini5 board doesn't like moving up from.

    Had to manually update the Mini5+ again via SD card, and erase a reflash the firmware on the 6HC board too. Luckily I followed my own instructions on how to overcome the Mini5+ 3.4.0 upgrade issue earlier in this thread.

    Same Nema8 lifting power issue with 3.5.4 though - so will move back to 3.6.0rc1+3.

    I think I am probably wasting too much time on Z hoppers trying to keep the extruders as light as possible - will drop the Nema8's for now and try to over-engineer instead by trying some of the heavier more powerful motors and thicker support structures next.

    Probably best to get everything working functionally and with good print quality up to at least the double IDEX phase - then worry about optimising weight as part of later speed tuning phase.

  • 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

    66
    Topics
    599
    Posts

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

    411
    Topics
    4.1k
    Posts

    undefined

    can change it to SOLVE

  • No decsciption available

    232
    Topics
    1.9k
    Posts

    undefined

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

    685
    Topics
    5.4k
    Posts

    undefined

    @Candy yes you could display simple text or images by editing the main() function in PanelDueFirmware.cpp and directly calling functions in the LCD module in the hardware folder.

  • 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

    127
    Topics
    1.3k
    Posts

    T3P3Tonyundefined

    @achrn have you considered releasing this as a plugin via plugins.duet3d.com

  • 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

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

    undefined

    @cichaczech please can you run levelling with 3.6.0-rc.1 again and this time observe the leadscrews to check whether they actually move when they are supposed to make the corrections. Also please try firmware 3.6.0-rc.1+3 available at https://www.dropbox.com/scl/fo/geqmn8gbn97n6b587mkbk/AJ2hBIqO-L57_QpR_uqHJ9c?rlkey=fw37wycbp2gil8rvxhe7aopy7&dl=0.

  • Discuss and contribute to the Duet Software Framework

    130
    Topics
    1.1k
    Posts

    undefined

    @chrishamm Thanks! That was it.

    Changed the imports and the send.response() and now it works.

    With hindsight I then find this change (and some others) had been made at https://github.com/Duet3D/dsf-python/blob/v3.6-dev/examples/custom_http_endpoint.py in early December last year, but I had missed that.

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

    404
    Topics
    3.2k
    Posts

    undefined

    @dc42 The thoroughgoing extrapolation of this idea would be an
    INo Trident

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

    947
    Topics
    7.5k
    Posts

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

    331
    Topics
    2.1k
    Posts

    fcwiltundefined

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

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