Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.4k
    Topics
    89.3k
    Posts

    Nano.01505undefined

    Hi,

    Before ill start Questioning, ill have to explain the past of this printer.

    i bought a Guider 2S in 2019 with the intent to just print stuff. I didnt wanted to "nerd-down" this printer - just use it....
    2 Burned Mainboards, and some heating issues later i decided to throw the Flashforge electronics away, and rebuild it with Duet.

    Bought and successfully installed an MB6HC.
    After about a year of working just fine, the Flashforge OEM toolboard burned.
    Bought a Duet toolboard, installed it, wired it.

    7.6.2025, 12:32:39 M122 b121 Diagnostics for board 121: Duet TOOL1LC rev 1.1 or later firmware version 3.4.6 (2023-07-21 14:17:33) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) All averaging filters OK Never used RAM 2596, free system stack 88 words Tasks: Move(notifyWait,0.0%,155) HEAT(notifyWait,0.4%,111) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,3.0%,57) MAIN(running,91.7%,343) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0% Last reset 00:02:23 ago, cause: software Last software reset data not available Driver 0: pos 0, 1553.5 steps/mm,standstill, SG min 0, read errors 0, write errors 1, ifcnt 162, reads 6218, writes 14, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter 0/4, peak Rx sync delay 207, resyncs 0/0, no step interrupt scheduled VIN voltage: min 25.2, current 25.2, max 25.2 MCU temperature: min 31.8C, current 32.0C, max 32.2C Last sensors broadcast 0x00000002 found 1 76 ticks ago, 0 ordering errs, loop time 1 CAN messages queued 2897, send timeouts 0, received 1331, lost 0, free buffers 37, min 37, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 Accelerometer: LIS3DH, status: 00 I2C bus errors 0, naks 3, other errors 0

    sooo,
    Communication is working.
    ive done the rest of rewireing.
    Heater + FAN - works!
    CoolingFan - works!

    Servo for Leveling - well here is the first Problem:

    ; Z-Probe M558 P8 C"121.io0.in" H3 F100 T8000 ; set Z probe type to switch and the dive height + speeds G31 P200 X0 Y0 Z2.5,;Z1.3 ;X-10 Y-25 Z2.5 M557 X0:280 Y0:210 S20:30 ; define mesh grid M376 H8 M950 S8 C"121.io0.out"

    Thats my current config after 4h troubleshooting.
    But i can not move the servo with M401 / M402.

    So if i am right, M401 / 402 just calling retract.g / deploy.g in the /sys/ folder.

    so i took the comand in that file and tested it direct:

    M280 P8 S20

    And the Servo Moves...
    So it seems, that my config is correct, but M401/402 is pointing to an other file?
    Ive even tryed to rename deploy.g and retract.g as described in the Documentation, to deploy8.g and retract8.g
    Didnt work...

    I do not understand why just changing the adress is making that problem. Surly just a small failure of my own, but i dont see it...

    The second Problem is,
    that the ExtruderMotor is not working.

    ; Drives M569 P0.0 S1 ; physical drive x 0.0 goes forwards M569 P0.1 S1 ; physical drive y 0.1 goes forwards M569 P0.2 S0 ; physical drive z 0.2 goes forwards M569 P121.0 S1 ; physical drive extruder 0.3 goes forwards M584 X0.0 Y0.1 Z0.2 E121.0 ; set drive mapping

    Config looks like this.
    After heating up, i placed a piece of filament in it, i wanted to test the extrudtion via the DWC.

    no movement - not even noise...

    Duet Web Control 3.4.6
    Duet 3 MB6 HC
    Toolboard V1.1

    pls somebody help me
    it can only be a small dumb failure of my own... but i dont see it...

  • Using Duet Controllers

    836
    Topics
    7.5k
    Posts

    R006undefined

    @dc42

    Thank you.

    Could you please provide example files for both driver-warning.g and driver-stall.g, if available?

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

    8.6k
    Topics
    77.1k
    Posts

    callum1243undefined

    Hi All,

    As the title suggests I'm having an issue setting up a second 6HC as an expansion board. My current configuration is the following:

    (Board 1) Duet 6HC Mainboard v1.02 running firmware 3.60 (Board 2) Duet 1HCL Expansion Board v2.0 running firmware 3.60 [CAN address 123] (Board 3) Duet 1HCL Expansion Board v2.0 running firmware 3.60 [CAN address 124] (Board 4) Duet 1HCL Expansion Board v2.0 running firmware 3.60 [CAN address 125] (Board 5) Duet 6HC Mainboard as expansion board v1.02 running firmware 3.60 [CAN address 2]

    Screenshot 2025-06-07 at 10.16.41 pm.png

    All boards are supplied with 48V power and I have verified the CAN cables between each of them. All of expansion boards (excluding the last 6HC) as functioning as expected. However, I can't seem to establish a connection with the final 6HC, this has been checked both via the CAN plugin in duet web control and by sending M122 B2.

    On the final 6HC I have removed all files on the boards SD card except for the firmware directory and the sys directory. Within each directory I have the following:

    \firmware directory
    Duet3_CANiap32_MB6HC.bin
    Duet3Firmware_MB6HC.bin \sys directory
    config.g (with the single line M954 A2 to configure the 6HC as an expansion board on CAN 2)

    On the first 6HC main board, I have also included G4 command in the config file to wait for all CAN boards to connect prior to assigning motors / pins etc.. I've also tried removing the 3 x 1HCL boards and just connecting straight from the first 6HC to the second 6HC, still with no luck.

    Does anyone have any advice on how to troubleshoot this? The documentation for what explicitly needs to be included on the duet 6HC as an expansion board is not entirely clear, so it could be an issue with the firmware configuration that I have included in the \firmware directory. Note I've also verified that this board does in fact work, as I was using it by itself for another project.

    Any help would be greatly appreciated!

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

    591
    Topics
    5.2k
    Posts

    Alijambo73undefined

    @Alijambo73 it seems it had something to do with the z offset getting saved in config-override.g. this seems to be working well```
    code_text

    G28 G1 X58 Y100 F3000 ; === Run Z probing macro === G91 ; relative M291 P"Connect probe and jog tip over Z touchplate. Press OK to continue." R"Z Probe" S3 G38.2 Z-100 F75 G1 Z2 F300 G38.2 Z-100 F45 G4 P0.1 G92 Z5.89 G1 Z5 F300 G90 ; absolute ; === Proceed with squaring === M558 P5 C"!io6.in" H5 F120 T6000 M584 Z0.2:0.4 P3 M671 X58:1183 Y100:100 S15 G10 L2 P1 Z0 var iterations = 0 while true G1 X58 Y100 F3000 G30 P0 Z-99999 G1 X1183 Y100 F3000 G30 P1 Z-99999 S2 set var.iterations = var.iterations + 1 if abs(move.calibration.initial.deviation) < 0.01 || var.iterations >= 2 break M584 X0.0 Y0.1:0.3 Z0.2:0.4 U0.3 V0.4 P3 M671 X58:1183 Y100:100 S5 M118 P0 S"Z gantry squaring complete."

  • Prototype hardware issues.

    30
    Topics
    836
    Posts

    JoergS5undefined

    @droftarts thank you Ian for the link. This approach is through Jacobian calculations. I started with this approach, but it takes too long time to calculate in Duet, because it needs iterations. Iterations are really bad for the resticted calculation resources of Duet and the approach described has a serious limitation of multiple singularity situations. Worse, sometimes I had no solution for the iterations. I changed to direct mathematical calculations instead and found screw theory and geometric algebra better suited.

    As you told, the article is of course very good, e. g. to motivate starting oneself with robotics.

  • Discuss Duet on laser cutters and engravers.

    184
    Topics
    1.5k
    Posts

    droftartsundefined

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

    We are NOT ABLE to fire the laser using the 'output6.buff" pin on the Duet 3 mini 5+when we wire to the IN pin on the MYJG5W.
    The ... 'IN' pin is a analog 0-5vdc analog PMW signal.

    M452 C"!out6" R255 S0 F3000 ; enable Laser mode, on out6 (F3000)

    Have you got a link to the manual for the Cloudray MYJG50W PSU? The product page is quite vague, https://www.cloudraylaser.com/products/cloudray-50w-co2-myjg-series-power-supply-black-shell-myjg-50w

    As far as I can tell 'H' and 'L' are on/off (L being H inverted) inputs. The 'IN' pin is said to support "input 0V to 5V analog signal, can also input PWM signal" (there's no such thing as an "analog PWM" signal). By 'analog signal', it means a signal of 0 to 5V, usually controlled by a potentiometer. The Mini 5+ output6.buff doesn't supply an analogue signal, only a 5V PWM signal.

    I can't find any information on the PWM frequency that the Cloudray MYJG50W accepts, but it's possible that F3000 in the M452 command is too high. The firmware default is 500Hz (F500), have you tied that?

    Ian

  • Ask questions about installing the firmwares here

    2.2k
    Topics
    23.7k
    Posts

    dwuk3dundefined

    @dwuk3d Further update

    Have tried various combinations of inserts of G1 H2's into print to try and kick motors back into action.

    Adding this to the start of the extruding section seems to kick U & V back into action.
    But they drop out again after priming.

    ;M98 P"0:/macros/changeFilament.g" A previous_extruder B new_filament_temp L layer_num N next_extruder F first_layer_temperature1 M98 P"0:/macros/changeFilament.g" A0 B220 L0 N1 F220 M203 M201 M106 S0 ; Filament gcode G10 S220 P1 ; set nozzle temperature ;prev preheat:0:T1:**NO PREHEAT** M116.1 ; wait for temperature to be reached ; printing object Cube id:0 copy 0 ; stop printing object Cube id:0 copy 0 ; printing object Cube id:2 copy 0 ; stop printing object Cube id:2 copy 0 ; printing object Cube id:1 copy 0 G1 F450.0 E-.8 M486 S-1 M486 S1 G1 D{global.dOffset+0.4} F15000.0 M802 L416; G1 F15000.0 U142.213 V205.264 G1 F15000.0 D{global.dOffset+0.4} M802 L419; G1 F15000.0 D{global.dOffset} M802 L421; G1 E.8 F450.0 ;TYPE:Inner wall ;WIDTH:0.499999 G1 F1500.0 G1 F750.0 U123.627 V205.264 E.69225 G91 G1 H2 U0.1 V0.1 ; Added to see if it makes a difference G1 H2 U-0.1 V-0.1 ; Added to see if it makes a difference G90 M73 P10 R3 G1 F750.0 U123.627 V186.678 E.69225 G1 F750.0 U142.213 V186.678 E.69225 G1 F750.0 U142.213 V205.224 E.69076

    Priming within changefilament works ok

    if global.primeLayer[param.N] < param.L M98.1 A"clean T1" T1 while iterations < var.primeLoops M203 U{global.xyMaxFeed} V{global.xyMaxFeed} G1 F12000 G1 U48 V295 F12000 M801 U{50+0.4*(4-iterations)} V{295+0.4*(4-iterations)} T1 S{10+0.8*(iterations-4)} A{20+0.8*(iterations-4)} ; Prime set global.primeLayer[param.N] = param.L if exists(param.L) && param.L > 0 && global.primeLayer[param.N] < param.L T1 M203 U{global.xyMaxFeed} V{global.xyMaxFeed} G1 F12000 G1 U48 V295 F12000 M801 U50 V295 T1 S10 ; Prime set global.primeLayer[param.N] = param.L G1 D{global.dOffset} F500 set global.T1Clean = false var timeC = state.upTime+state.msUpTime/1000 ;echo {state.thisInput},"M598 started" ;M598 ;M400 ;echo {state.thisInput},"M598 waited for ",{state.upTime+state.msUpTime/1000-var.timeC},"secs" if param.A != 0 echo {state.thisInput},"No need to wait for Y Axis, Move W Over" G1 W300 F10000 else set var.timeC = state.upTime+state.msUpTime/1000 while global.startParkXY == -1 ; move.axes[1].machinePosition > 25 G4 P59 M400 echo {state.thisInput},"waited for xy to start Parking ",{state.upTime+state.msUpTime/1000-var.timeC},"secs" if global.startParkXY < var.timeC echo {state.thisInput},"too late by ",{state.upTime+state.msUpTime/1000-global.startParkXY},"secs" echo >>>"delays.g" ",",var.startHeat-var.startWait,",-",{state.upTime+state.msUpTime/1000-global.startParkXY} set global.delayAdjust = state.upTime+state.msUpTime/1000-global.startParkXY else echo >>>"delays.g" ",",var.startHeat-var.startWait,",",{state.upTime+state.msUpTime/1000-var.timeC} set global.delayAdjust = 0 set var.timeC = state.upTime+state.msUpTime/1000 if global.startParkXY+0.1 > var.timeC G4 P{floor((global.startParkXY+0.1 - var.timeC)*1000)} echo "waited further",floor((global.startParkXY+0.1 - var.timeC)*1000),"ms" set global.uvParked = false set global.startParkUV = -1 M800 T2 H1 M203 W{global.xyMaxFeed} V{global.xyMaxFeed} G1 F12000 G1 W310 F20000 M203 M201 echo {state.thisInput},"finished changeFilament"

    With the M801 having the following Gcodes for the priming - which always seem to work

    var speed = 1500 G1 D{global.dPrimeOffset} F300 G1 F{var.speed} G1 U{param.U} V{param.V} F{var.speed} ;M800 T{param.T} H0 ; ZHop down G1 U{param.U} V{param.V+param.S} E{var.E} F{var.speed} G1 U{param.U+var.S2} V{param.V+param.S} E{var.E*2} F{var.speed} G1 U{param.U+var.S2} V{param.V} E{var.E*2} F{var.speed} G1 U{param.U} V{param.V} E{var.E} F{var.speed} G1 U{param.U-2} V{param.V+param.S/2} F{var.speed} G1 U48 V295 F2000 G1 D{global.dOffset} F300 M400 echo {state.thisInput},"prime time T1",{state.upTime+state.msUpTime/1000 - var.primeT},"s"

    I added in the M203's due to the speed issue - will try removing them to see if that makes a difference.
    Update - it's not the M203s or M201s - removed them all and still get the same issue.

    Also just went back to 3.5.4 - it didn't brick this time, and have run the exact same config and print and it is again as expected working fine on 3.5.4 (not withstanding the speed issue).

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

    SamKudarauskasundefined

    I've done some testing with different ideas, how do I make it wait untill filament is detected/ removed in the middle of the load/ unload macro?

    Right now I have each filament heat up to the correct temp then call this macro

    if move.axes[2].machinePosition < 20 M564 H0 ; allow movement of unhomed axies G91 ; relative movement G1 Z10 ; lift z 10mm G90 ; absolute movement M400 ; wait for current moves to finish M564 H0 ; forbid movement of unhomed axies var count = 0 while true if sensors.gpIn[2].value = 1 M292 P0 ; hide the message break else M291 P"Push filament through filament sensor to nozzle" S3 set var.count = var.count + 1 if var.count > 60 ; Timeout after ~60 seconds ;abort "Timeout: No filament detected!" M292 P1 ; Abort Loading G4 S1 M291 P"Load filament?" S3 M291 P"Loading" T15 S0 ; Display new message M83 ; Extruder to relative mode ; Load filament G1 E15 F300 ; Feed 15mm of filament at 300mm/min M400 ; wait for current moves to finish M291 P"Loading to melt zone" T10 S0 ; Display new message G1 E25 F600 ; Feed 25mm of filament at 600mm/min M400 ; wait for current moves to finish M291 P"Priming filament" T15 S0 ; Display new message G1 E45 F300 ; Feed 45mm of filament at 300mm/min M400 ; wait for current moves to finish ; Retract filament G4 P1000 ; Wait one second G1 E-5 F1800 ; Retract 5mm of filament at 1800mm/min M400 ; Wait for moves to complete M292 ; Hide the message

    In my config.g I have a filament pressence sensor set up as a trigger

    ; Filment Autoloading Trigger M950 J2 C"io5.in" ; Input 2 uses io2.out pin M581 P2 S1 T2 R0 ; trigger2.g

    And in trigger2.g

    M292 ; send continue

    Right now it does wait until filament presence is detected and then it proceeds but I get the warning:

    M701 S"PLA" M703
    Warning: M703: Awaiting input, command ignored

    Why is this and how can I address it or implement this functionality another way?

    Sam

  • Discuss using conditionals, loops and variables in gcode

    802
    Topics
    5.7k
    Posts

    dc42undefined

    @mikeabuilder thanks for confirming.

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.1k
    Posts

    MaxGyverundefined

    Today I re-flashed the SD-card and updated to 3.6.0 stable via M997 S2 without any issues. This time all boards+ DSF and DWC were successfully updated right away and DWC is working as expected across multiple web browsers. I don't know what might have gone wrong the first two times.

    I will set up some more printers next week, but for now I would consider this issue solved.

    Thank you all for your input and support!

  • Feedback for docs.duet3d.com

    118
    Topics
    562
    Posts

    jbjhjmundefined

    Hey everyone, I've just finished setting up SZP nozzle probing on my printer.
    Had to figure out some things which were difficult to understand in docs, so I thought I'd write down a full example to help others.
    Don't know if it's the appropriate forum. Feel free to move it somewhere else and/or add the example to documentation.
    (Search terms: beacon contact probe)

    Note that at the time of setting this up, the printhead had TWO probes mounted, so within the code you'll see "K1" everywhere to refer to the SZP instead of the default probe (K0).

    config.g

    sets basic config only. Most configuration is handled dynamically within homing / bed mesh scripts.

    ; Define SZP Scanning Probe ===================================================================== M558 K1 P11 C"120.i2c.ldc1612" F36000 T36000 ; K0 = primary probe, K1 = secondary probe M308 A"SZP coil" S10 Y"thermistor" P"120.temp0" ; configurate coil thermistor G31 K1 X0 Y24 Z2 ; set default XYZ offsets, other params will be set on demand by macros M98 P"szp_mode_normal.g" ; this is optional, just here to calm you down when opening DWC, which would show probe 999999 values otherwise. ...

    nozzle probing and "default" mid-air probing requires different calibrations.
    For that reason, my solution relies on two custom macro files to set up any of the two when needed.

    szp_mode_normal.g M558.3 K1 S0 ; S0 -> enter normal probing mode ; get the S and R values by calling M558.2 K1 S-1 in a good Z distance. 5-10mm from bed worked fine for me. ; manually move Z axis and ensure no 99999 values are being reported ; (when coming super close to bed it may happen, but should be fine as it is not used to probe in super-close distance.) M558.2 K1 S16 R132663 szp_mode_touch.g ; get the S and R values by calling M558.2 K1 S-1 in small Z distance. 2-5mm from bed worked fine for me. M558.2 K1 S16 R133019 ; V=Threshold. Start with V0.1 and increase until it works reliably without misdetections. M558.3 K1 S1 V0.3 homez.g

    a bit more complicated as it needs to handle every situation on the fly.
    As recommended in docs, we first to a mid-air measurement which aims to get the nozzle/probe "kinda close" to the bed.
    Then, a second probing is executed.

    This is not a copy-and-paste script, you'll need to run multiple calibrations to figure out the right values for your printer.
    I recommend to comment out the Step 1/2 seconds and re-add and test them step by step to ensure low risk of damaging your printer due to misconfiguration.
    See the inline comments for explanation as well as instructions on how to calibrate

    ; Step 0: move to a safe probing position M564 H0 ; unlock movement G91 ; relative positioning G1 H0 Z30 F6000 ; lift Z a bit to ensure we arent too close to the bed -- H2 is outdated and not used anymore. H1 respects endstops, H0 ignores them. G90 ; absolute positioning G1 H0 X150 Y140 F10000 ; move probe to bed center M913 Z55 ; 50% Z motor current to reduce damage/intensity of impact ; Step 1: do a rough contact-free measurement to get *kinda close* to bed M98 P"szp_mode_normal.g" ; set a safe Z trigger height to trigger when the bed is coming close but safely not touching. omit XY, these were defined in config.g! ; Z and P values are important here: These relate "Probe value [P] of 8850 relates to [Z] offset of 6mm". ; Get your probe's P value by moving to Z=6 manually after calibrating as described in szp_mode_normal.g, and read the value reported in DWC then. ; if szp_mode_normal.g is modified, these values must be updated too! G31 K1 Z6 P8850 G30 K1 S1 ; execute Z homing to ensure printhead is close to bed ; Step 2: we should now be ~6mm above the bed. TIme to do the fine tuning! M98 P"szp_mode_touch.g" G30 K1 S1 ; execute contact probing and set Z G91 ; relative positioning G1 Z3 ; move up a bit G90 ; absolute positioning ; FInalization M564 H1 ; re-lock movement M913 Z100 ; reset Z motor current to 100%

    You should now be able to successfully home all axes using nozzle touch probing for Z.

    bed.g

    not much special things in here. Call the szp_mode_normal to ensure SZP is using correct configuration.

    M561 ; clear any bed transform M98 P"szp_mode_normal.g" G30 K1 P0 X10 Y25 Z-99999 ; probe near a leadscrew G30 K1 P1 X150 Y280 Z-99999 ; probe near a leadscrew G30 K1 P2 X280 Y25 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors mesh.g

    pretty much the example found in documentation.
    Only change was I'm calling the homez.g macro.
    Not sure if it makes any difference.

    M557 X10:290 Y25:275 P28:25 ; Define grid for mesh bed compensation, origin in bed centre P=Number of points per axis G29 S2 ; Disable mesh bed compensation M98 P"homez.g" ; Home Z G1 Z6 ; To avoid backlash move to point higher than start of calibration M558.1 K1 S1.7 ; Calibrate probe G1 Z6 ; Move up at end of calibration G29 S0 K1 ; Scan the bed and create mesh

    I think that's it! Took a while but totally worth it. Don't give up if you can't make it work immediately.
    Have fun and good luck!

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

    dwuk3dundefined

    @dc42 i didn'r think it was worth raising issues until I went to 3.6.0.

    I tried 3.6.0 yesterday and today and have got a more fundamental issue with 3.6.0 which I have raised as a separate thread.
    Once I have resolved that (or found a workaround) I will retest other issues and if they still existing raise them as 3.6.0 threads.

  • 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

    stuartofmtundefined

    @chrishamm
    Thanks. Confirmed working with first=0

  • Accessories and Add-ons

    67
    Topics
    603
    Posts

    Inlinebrotherundefined

    @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

    398
    Topics
    3.9k
    Posts

    bastundefined

    I just received my LLL PLUS Buffer from Mellow 3D.
    I'd like to connect it to my Duet to retrieve buffer information. The Duet also has information about filament progress and breakage.
    Here's the device's date sheet:
    https://mellow.klipper.cn/en/docs/ProductDoc/ExtensionBoard/fly-buffer-plus/?persistLocale=true
    It must be connected to 12/24V and has a switch pin and a motion pin.

    Thank you.

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

    687
    Topics
    5.4k
    Posts

    dc42undefined

    @wschadow is that really a bug? If it really is that low then previously I think it would have been shown as 0.001mm. if it has been even lower (e.g. 4e-4mm) then it would have been shown as 0.000 which I don't think is helpful.

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

    209
    Topics
    2.2k
    Posts

    Adrian52undefined

    @DocTrucker I approached this problem by clipping a spare thermistor to the cold end, and monitoring it via daemon.g. Might add a belt to your tacho braces.

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

    130
    Topics
    1.3k
    Posts

    MintyTreborundefined

    Updated to V1.3.5 for DWC 3.6

  • RepRapFirmware on other controllers

    30
    Topics
    368
    Posts

    madeinta1wanundefined

    @jay_s_uk ---

    Thanks, after thinking about what you said I tried swapping my H and L in the CAN connections and I've got one of three tool boards running now.

    🙏

    Nate

  • STM based control boards

    48
    Topics
    384
    Posts

    sankafolaundefined

    @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

    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.2k
    Topics
    15.3k
    Posts

    MaxGyverundefined

    Like mentioned in my previous thread the Y-Axis EXP1XD board is disconnecting when printing a succession of short segments (text) if the input shaping frequency is below 12Hz. This is still the case with RRF 3.6.0. When the board is disconnected I have to power cycle the printer to get it back online.
    I have also noticed, that after a disconnect, the green ACT led is blinking rapidly while the STATUS led is blinking in sync with the other boards.

    So far I have tried the following frequencies with RRF 3.6.0:

    M593 P"EI3" S0.05 F8.7 -> disconnect
    M593 P"EI3" S0.05 F10 -> disconnect
    M593 P"EI3" S0.05 F12 -> works
    M593 P"EI3" S0.05 F13 -> works
    M593 P"EI3" S0.05 F15 -> works

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

    408
    Topics
    3.2k
    Posts

    sebkritikelundefined

    @dc42 David, sincerest thanks for the comments!

    I've received the crystals, as well as the Atmel-ICE, and can verify that I can use the Atmel-ICE over SWD to erase and program the board.

    With some work, I'm able to debug in Eclipse with OpenOCD. After seeing some initial crashes/exceptions (out of memory, hard faults, etc), I've gotten to the point where the board continues to "run" (as far as the thread running Eclipse), though no blinking LED, nor any can activity (as far as RRF can tell). When pausing, the indicated line I pause at has been line 209 in CanId.H:

    uint8_t Src() const noexcept { return (all >> SrcAddressShift) & BoardAddressMask; }

    Debugger console:

    IsNonZero (f=0) at C:\Users\Jared\Documents\GitHub\RRFBuild\CANlib\src/CanId.h:209 209 uint8_t Src() const noexcept { return (all >> SrcAddressShift) & BoardAddressMask; }

    More noodling to be done, but I'll be away from this project for a bit. If you have any general debugging tips, I'm all ears! Thanks!

  • 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

    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

    dc42undefined

    @GeneRisi feel free to create a feature request at https://github.com/Duet3D/RepRapFirmware/issues with a link to this thread in it.

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

    354
    Topics
    3.9k
    Posts

    kcressundefined

    @droftarts Ian, Thanks for the link. I've implemented automatic tramming into bed.g

    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

    3DPMicroundefined

    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