Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.4k
    Topics
    88.8k
    Posts

    undefined

    I'm currently modifying a printer that has belts on all axis , to have additional micro Z adjustment using small lead screw motors on each print head - which on reading your thread makes me think I might be introducing some backlash problems too.

    Due to multiple print heads not being supported by firmware mesh levelling - I was planning when I get to the stage of refining print quality to address micro Z mesh adjustments using a GCODE post processor.

    I was thinking the post processor could reads in the bed mesh file and then make any necessary tiny adjustments to the Z coordinates of the layers within the mesh compensation scope . If necessary splitting up any long moves that span irregular areas of the bed into smaller chunks that can have the appropriate MicroZ compensation applied.

    Thinking about mesh compensation I think a post processor should take backlash in to account too - I guess it might not be that hard to allow for the fact that moves in a certain direction might need a tiny little bit of extra or less Z adjustment made to them to take in to account the backlash.

    My Bed is fixed - so I don't think I will be affected by backlash amounts changing depending on the weight of print on the bed - but I guess that could also be included too in a post processor - although I am guessing that printed object weight would only start to become significant when you are well above the normal bed mesh compensation layers.

  • Using Duet Controllers

    830
    Topics
    7.5k
    Posts

    undefined

    I think you're on the right track with the G60 command. You don't provide any details of the trigger macros, so the rest of this post is just guessing on my part...

    I assume you've read this page on setting up triggers: https://docs.duet3d.com/en/User_manual/Tuning/Triggers, and that you've set up the inputs for the two buttons using M950, and also defined triggers numbered 10 and 11 using M581. Also, you've got these commands in your config.g file so they'll be executed every time you start the machine.

    The trigger10.g macro should need only one command.

    ;trigger10.g G60 S3

    When this macro runs it will save the current machine location into slot #3.

    The trigger11.g macro should looks something like this:

    ;trigger11.g G0 R3 X0 Y0 Z0

    This commands a fast move to the stored S3 location without any offset in the X,Y,or Z positions stored in S3. If you don't have the X0 Y0 Z0 in your command, those axes won't be moved (it will look like nothing has happened when you push the second button).

    An additional thing to consider in your trigger 11.g macro. If your "move to" button is pressed before the "save position" button, the default coordinates stored in slot S3 are 0,0,0 so you'll drive a move you might not want. If you are unlikely to ever save 0,0,0 with your "save location" button, you could write an IF statement into your trigger11.g macro to look at the current values saved in this slot and if they are all 0, you could do something like post a message and not make the move.

    To test your trigger10.g macro without the buttons, you can send M98 P"trigger10.g" in the Web control window, then send echo state.restorePoints[3].coords to see the saved coordinates. You can also look at the object model plugin to see if the location has been stored. It will be in state > restorePoints >3

    You can similarly test trigger11.g. After running trigger10, move the machine using the Web control then send M98 P"trigger11.g" in the Web control window. Your machine should move back to the stored position.

    You can also test the inputs by looking at the inputs section of the object model while you press the buttons.

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

    8.5k
    Topics
    76.8k
    Posts

    undefined

    @vaike_peeter I would not expect re-initialising the probe to cause the board to reset, but it looks like there was a "HardFault" reset in your M122 output. One for @dc42 to comment on I think.

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

    582
    Topics
    5.1k
    Posts

    undefined

    @Tool88 said in Duet 3 6hc canned cycle:

    Also is reprap capable of i-0. J-0. Commands

    I see the administrator responded
    But I don't see a way to respond to thank you
    A i-0.0 and j-.0
    Would look something like
    G03 x location i-0.234 j-0.0038
    It's just a way to cut circle without having to do every arc move as a single step

    Yes, RRF supports G2 and G3 using I and J parameters, see https://docs.duet3d.com/User_manual/Reference/Gcodes#g3-controlled-arc-move

    Ian

  • Prototype hardware issues.

    27
    Topics
    808
    Posts

    undefined

    @dc42 Sounds great thanks.

    I don't think the number of overridden GCODEs is likely ever to be a very long list - so maybe a lookup list could work too - perhaps with some sort of extra M command in the config.g or start gcode in the slicer to register the overrides.

    In the meantime I think I will alter my post processor to be more generic and do more or less the same thing.
    i.e. Look for some sort of override registration M command (M802 for example) in the gcode stream, and then use that info to then override any relevant G/M/T commands later in the stream into .x equivalents.

  • 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

    @rodneysramosj Is the X endstop a max endstop or min endstop? Currently your G1 H1 X... homing moves are positive, so should be moving to the right, towards a max endstop. If this is wrong, you probably need to check the direction the motors are moving is correct, see https://docs.duet3d.com/en/How_to_guides/Commissioning#h-10-check-stepper-motors

    Your printer origin X0 Y0 Z0 should be in the front left corner. Positive X moves should move the nozzle to the right, positive Y moves should move the nozzle towards the back.

    Ian

  • 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

    @dc42, it is working now. Thank you for the quick update.

    I guess it could be a bad connection.But why does it happens at random points on the buildplate. And why can't I reproduce the issue on RRF 3.6.0-RC.1 or before. Could it be an issue with the debouncer ?

    I switched to a NO sensor and the issue is now flipped the error is now "Error: G29: Probe already triggered before probing move started". and the Z-probe status is stuck in the triggered state until I trigger/un trigger it manually.

  • Discuss using conditionals, loops and variables in gcode

    793
    Topics
    5.6k
    Posts

    undefined

    @mikeabuilder bouncing is not normally a problem with PanelDue so perhaps something is wrong with the touch membrane. Maybe your enclosure is pressing against it enough to increase its sensitivity but it enough to cause a permanent trigger.

    BTW the most precise way to touch the PanelDue buttons is to use the.tip of your fingernail, not the pad of your finger.

    The buttons auto-repeat if you maintain the pressure.

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.1k
    Posts

    undefined

    I see you already have a thread started here. Please keep it limited to one thread per issue.

    https://forum.duet3d.com/topic/37842/printer-not-hitting-any-of-the-endstops

  • Feedback for docs.duet3d.com

    116
    Topics
    558
    Posts

    undefined

    @oliof @gloomyandy After discussing this with @dc42, I think I've misunderstood how extruder acceleration is limited under PA. The jerk / PA limit on acceleration is applied automatically by RRF, so the user doesn't need to set jerk or acceleration manually to take account of PA. The user sets extruder speed, jerk and acceleration at whatever the extruder can achieve in extruder-only moves (like retraction). The user only needs to know that acceleration is limited when PA is applied, to jerk / PA, so may have consequences such as slowing down or stuttering during printing moves, or skipping steps. This, at least, makes the documentation simpler! Which I'll now update, again...

    Ian

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

    undefined

    @dwuk3d said in Sovol SV08 Multiple Motion System Upgrade.:

    Z0, X1,Z1,Y,X2,Z2, U1,Z3,V,U2,Z4, Y2

, Which in RRF will be XYZUVABCDEFG

    Just call it Alphabet kinematics , because there aren't many unused letters left 😉

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

    undefined

    @dwuk3d yes, it'll work with that

  • 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

    @patterson6 They're in stock, I think for a couple days stock ran out, but nearly immediately restocked. Could have signed up for restock emails?

    Most, nearly all Volcano nozzles are in stock. Which materials/sizes are you wanting?

  • No decsciption available

    232
    Topics
    1.9k
    Posts

    undefined

    I tested and had no consistent results with a structured PEI coated steel sheet. Moving the head just 1or 2mm sideways produced deviations of up to 0.2mm in either direction. I am back to BL-Touch with more consistent overall results whereas the IR-probe was more consistent on the same spot.

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

    686
    Topics
    5.4k
    Posts

    undefined

    Are they displaying correct on the web control?

    What exactly are you seeing on the PanelDue? Photo?

    Can you describe the heater layout for the printer?

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

    208
    Topics
    2.2k
    Posts

    undefined

    Encouraged by the post by @cdoe on setting up the Orbiter 2 filament sensor, I gave it a hard try to set up the Smart Orbiter 3. All features are working and I come amazed at the power of RRF 🙂

    The Smart Orbiter 3 has 8 connections at the base, containing a RGB Matrix LED connection, a simple hotend LED and 2 outputs (FS for sensing if filament is present) and FTU (outputs if filament is tangled or filament unload button is pressed). (check the website https://www.orbiterprojects.com/so3/ in section 3.3 Integrated Smart Features for polarity: I spent a day trying to figure out why nothing was working only to discover that blue and red wires are NOT GND and 3V 🙂 )

    Similar to the Orbiter 2 Sensor, the set up is slightly more elaborate than just a sensor since both outputs have 2 functions and logic is not straightforward as well. FS output works as expected as in changing state when filament is present or runs out, FTU output only changes state if filament is already present.

    I am running a e3d toolchanger with Duet 2 Wifi and DueX5. I connected the cables to the pins 1 -6 of the LCD connector. (all works just fine on 3.3V) and reused triggers developed by @cdoe for things to work.

    This is a section in config.g

    ; Filament Sensor & Smart H2 M950 J3 C"^connlcd.enca" ; define logical input for filament auto load M581 P3 T5 S1 R0 ; define trigger for filament auto load triggers trigger5.g M581 P3 T2 S0 R0 ; define trigger for filament sensing triggers trigger2.g M950 J4 C"^connlcd.encb" ; define logical input for filament unload M581 P4 T6 S1 R0 ; define trigger for filament auto unload triggers trigger6.g M950 P5 C"connlcd.rs" ; define logical output for hotend LED M950 E0 C"connlcd.5" T1 U1 ; create a RGB Neopixel LED strip on the LCD Connector 5 port (RRF 3.5 and later) M98 P"0:/macros/h2led" ; Set LED Colour according to state of H2 M42 P5 S0 ; Turn Hotend LED off

    Obviously the most important part is getting the matrix LED to work 😁 with a macro I called h2led.g

    ; Sets MatrixLED according to filament Sensor status if sensors.gpIn[3].value = 1 M150 E0 R000 U255 B000 P255 ; set LEDs to green, full brightness else M150 E0 R255 U000 B000 P128 ; set LEDs to red, half brightness

    Triggers 2, 5 & 6 reuse the macros developed for the smart orbiter

    ; trigger2.g if state.status == "processing" M300 S2000 P100 ; play beep sound M291 P"Ran out of filament while printing" S0 T3 ; display message M25 elif state.status == "pausing" || state.status == "paused" M291 P"Retriggered filament sensor during pause" ; display message else M300 S2000 P100 ; play beep sound M291 P"Ran out of filament" S0 T3 ; display message

    For the load and unload triggers, I am using a single printer macro for all toolheads for loading and unloading. As such, I pass on a parameters representing the toolhead to the macro for addressing the right toolhead. And then obviously triggering the color LED macro at the end of it to adjust LED according to status.

    ; trigger5.g M150 E0 R000 U000 B255 P128 ; set LEDs to blue, half brightness M98 P"0:/macros/filament-load" X2 ; Load Filament for T2 M98 P"0:/macros/h2led" ; Set LED Colour according to state of H2 T-1 ; Park tool ; trigger6.g if state.status = "processing" M300 S2000 P100 ; play beep sound M291 P"Filament is stuck or filament unload button pressed" S0 T3 ; display message M150 E0 R000 U000 B255 P128 ; set LEDs to blue, half brightness M25 else M150 E0 R000 U000 B255 P128 ; set LEDs to blue, half brightness M98 P"0:/macros/filament-unload" X2 ; Call Unload Macro and pass Tool number using X parameter M98 P"0:/macros/h2led" ; Set LED Colour according to state of H2 T-1

    Hope this helps somebody else - it's a nifty little extruder and I'm stoked the electronics are now fully integrated!

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

    127
    Topics
    1.3k
    Posts

    undefined

    @jonsteinmetz

    Also does this return any results?

    sudo find / -name cv2

  • RepRapFirmware on other controllers

    30
    Topics
    352
    Posts

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

    marvineerundefined

    @dc42 Hi! I have increased the motor current to 40 percent during homing -> still the same
    I have reduced the speed even further but still the same.
    I do not notice the clicking sound of skipped steps either, so I still think there are no steps being sent to the right motor (looking from the front)

    I am out of ideas, but maybe you have something to try for me?

    This is the response of M122:

    === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.6.0-rc.2 (2025-03-31 12:17:13) running on Duet 3 MB6HC v1.0 or earlier (SBC mode) Board ID: 08DJM-956L2-G43S4-6JTD4-3SS6J-TA7GH Used output buffers: 1 of 40 (36 max) === RTOS === Static ram: 137420 Dynamic ram: 101532 of which 356 recycled Never used RAM 104604, free system stack 142 words Tasks: SBC(2,nWait 7,1.9%,793) HEAT(3,nWait 6,0.0%,325) Move(4,nWait 6,0.0%,242) TMC(4,nWait 6,3.0%,343) CanReceiv(6,nWait 1,0.1%,796) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,350) MAIN(1,running,94.6%,101) IDLE(0,ready,0.4%,29) USBD(3,blocked,0.0%,149), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:04:31 ago, cause: power up Last software reset at 2025-04-06 15:09, reason: User, Platform spinning, available RAM 104084, slot 2 Software reset code 0x2000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043c000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a === Storage === Free file entries: 20 SD card 0 not detected, interface speed: 37.5MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === Segments created 6, maxWait 126600ms, bed comp in use: none, height map offset 0.000, hiccups added 0/0 (0.00/0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00 Pos req/act/dcf: -31536.00/-31536/0.00 -2000.00/-2000/0.00 16000.00/16000/0.00 0.00/0/0.00 0.00/0/0.00 Next step interrupt due in 9 ticks, disabled Driver 0: standstill, SG min 14, mspos 8, reads 18409, writes 26 timeouts 0 Driver 1: standstill, SG min 40, mspos 776, reads 18403, writes 32 timeouts 0 Driver 2: standstill, SG min 26, mspos 696, reads 18403, writes 32 timeouts 0 Driver 3: standstill, SG min n/a, mspos 8, reads 18417, writes 18 timeouts 0 Driver 4: standstill, SG min n/a, mspos 8, reads 18417, writes 18 timeouts 0 Driver 5: standstill, SG min n/a, mspos 8, reads 18417, writes 18 timeouts 0 Phase step loop runtime (us): min=0, max=38, frequency (Hz): min=1865, max=2148 === DDARing 0 === Scheduled moves 12, completed 12, LaErrors 0, Underruns [0, 0, 0] Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000 Code queue is empty === DDARing 1 === Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0] Segments left 0, axes/extruders owned 0x00000000, drives owned 0x00000000 Code queue is empty === Heat === Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1 -1 -1 -1 -1, ordering errs 0 === GCodes === Movement locks held by null, null HTTP* is doing "M122" in state(s) 0 Telnet 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 LCD is idle in state(s) 0 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 File2 is idle in state(s) 0 Queue2 is idle in state(s) 0 === Filament sensors === Driver 29: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === CAN === Messages queued 2321, received 8507, lost 0, ignored 0, errs 0, boc 0 Longest wait 1ms for reply type 6028, peak Tx sync delay 329, free buffers 50 (min 49), ts 1287/1286/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 41930/41930 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x27a7c Buffer RX/TX: 0/0-0, open files: 0 === Duet Control Server === Duet Control Server version 3.6.0-rc.2 (2025-03-31 10:53:52, 64-bit) HTTP+Executed: > Executing M122 Code buffer space: 4096 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 0.31, max time between full transfers: 141.5ms, max pin wait times: 27.1ms/15.0ms Codes per second: 0.00 Maximum length of RX/TX data transfers: 5013/796

    And this is my config.g:

    ; here we define everything connected to the main board ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"MultiPrint" ; set printer name M669 K1 ; select CoreXY mode M80 C"!pson" ; invert the PS_ON output for Meanwell power supply ; Network ;M552 P0.0.0.0 S1 ; enable network and set IP address ;M553 P255.255.255.0 ; set netmask ;M554 P192.168.1.254 ; set gateway ;M586 P0 S1 ; enable HTTP ;M586 P1 S0 ; disable FTP ;M586 P2 S0 ; disable Telnet ; PanelDue 5.0i with custom logo M575 P1 S1 B115200 ; wait for expansion boards to start G4 S1 ; lower SPI transfer max wait Time for quicker system respone (default 25 ms and 5ms if file open) ; ignore this if 3 or more events are in queue M576 S6 F3 P3 ; Define inputs and their trigger if necessary M950 J5 C"^io5.in" ; input 5 - ActiveToolDetect (Tool Detect Switch) M950 J6 C"^io7.in" ; input 6 - OpenDoorDetect M581 P6 T2 S1 R0 ; define rising edge trigger --> door opened (trigger2.g) M581 P6 T3 S0 R0 ; define falling edge trigger --> door closed (trigger3.g) M582 T2 ; check for trigger (necessary, we might start with door open) M950 J7 C"^io8.in" ; input 7 - E-Stop (trigger 0) M581 P7 T0 S1 R0 ; define rising edge trigger --> emergency stop (M112) (NOT-HALT) ; check if e-stop is triggerd at startup if sensors.gpIn[7].value == 1 M291 T0 P"pull e-stop and reset machine to continue" R"e-stop is active" M300 M582 T0 abort "e-stop is active - pull e-stop and reset machine to continue" ; Lights M950 P0 C"1.out1" Q500 ; main M950 P1 C"1.out0" Q500 ; head if sensors.gpIn[6].value == 1 ; door is closed M98 P"/macros/Lights/set.g" D"main" B0.75 ; turn on main light else M98 P"/macros/Lights/set.g" D"main" B0.05 ; LED Strip M950 E0 U18 T1 C"0.led" ; Drives D3: stealthChop2 V4000: switch from stealthChop to to spreadCycle mode at 0.1 mm/sec speed (quiet at standstill) M569 P0.2 S0 ; physical drive 0.2 goes backwards (X - Axis) M569 P0.1 S0 ; physical drive 0.1 goes backwards (Y - Axis) M569 P0.0 S1 ; physical drive 0.0 goes forwards (Z - Axis) M569 P0.3 S0 ; physical drive 0.3 goes backwards (C - COUPLER) M569 P1.0 S1 ; physical drive 1.0 goes forwards (B - BRUSH) M569 P0.4 S1 ; physical drive 0.4 goes forwards (E0 - V6) M569 P0.5 S1 ; physical drive 0.5 goes forwards (E1 - Volcano) M569 P121.0 S0 ; physical drive 121.0 goes forwards (E2 - HighTemp Direct) M584 X0.2 Y0.1 Z0.0 C0.3 B1.0 E0.4:0.5:121.0 ; set drive mapping M350 X16 Y16 Z16 B16 E16:16:16 I1 ; configure microstepping with interpolation M350 C16 I0 ; configure microstepping without interpolation M92 X100 Y100 Z1600 C91.022 B128 E400:400:400 ; set steps per mm M98 P"/macros/Speeds/set_speed.g" S"startup" ; set speeds, jerk and accel. for the beginning M566 Z20 C2 B8 E450:900:450 ; set maximum instantaneous speed changes (mm/min) M203 Z800 C8000 B1000 E4500:5500:4500 ; set maximum speeds (mm/min) M201 Z400 C500 B500 E10000:23000:6000 ; set accelerations (mm/s^2) M906 X1800 Y1800 Z1130 B500 I20 ; set motor currents (mA) and motor idle factor in per cent (X Y Z B) M906 C500 E1000:1000:1000 I10 ; set motor currents (mA) and motor idle extruder motors to 10% M84 S15 ; Set idle timeout ;spindle M950 R0 C"^vfd" Q900 L10000 ; Spindle 0 uses out9/vfd as RPM pin with 200 Hz PWM freq and has a max RPM of 10000 ; limits M98 P"/macros/Boundaries/ToolHead.g" ; set dynamic axis Limits M208 Z0:264.6 C-45:360 B0:23 ; set static axis limits (min:max) ; Endstops M574 X1 S1 P"^io3.in" ; configure active-high endstop for low end on X via pin ^io1.in M574 Y1 S1 P"^io4.in" ; configure active-high endstop for low end on Y via pin ^io2.in M574 Z2 S1 P"^io2.in" ; configure active-high endstop for high end on Z via pin ^io7.in M574 C0 ; No C endstop M574 B1 S1 P"^1.io3.in" ; configure active-high endstop for low end on B via pin ^io5.in ; Z-Probe M558 P8 C"io1.in" H2.5:0.7 F600:300 I0 A8 S0.003 T20000 ; set Z probe type to switch and the dive height + speeds G31 P200 X0 Y0 Z0 ; set Z probe trigger value, offset and trigger height M557 X-140:140 Y-90:90 S20:30 ; Define mesh grid ;Stall Detection M915 X Y S5 F1 R1 ; X and Y Axes ; Heaters M308 S0 P"temp0" Y"thermistor" A"Bed" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0 ; BED ; correction val for port "temp0": H=-19; L=0 M950 H0 C"out0" T0 Q5 ; create bed heater output on out0 and map it to sensor 0 with a PWM freq of 5 Hz M307 H0 B0 R1.240 C413.8 D3.17 S1 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S200 ; set temperature limit for bed heater 0 to 200C M308 S1 P"temp1" Y"thermistor" A"T0" T100000 B4138 ; configure sensor 1 as thermistor on pin temp3 ; TOOL 0 ; correction val for port "temp3": H=-7; L=13 M950 H1 C"out1" T1 ; create nozzle heater output on out3 and map it to sensor 1 M307 H1 R2.320 K0.406:0.085 D5.66 E1.35 S1.00 B0 V24.0 ; disable bang-bang mode for heater and set PWM limit M143 H1 S285 ; set temperature limit for heater 1 to 285C M308 S2 P"temp2" Y"thermistor" A"T1" T100000 B4138 ; configure sensor 2 as thermistor on pin temp3 ; TOOL 1 ; correction val for port "1.temp0": H=-6; L=3 M950 H2 C"out2" T2 ; create nozzle heater output on 1.out1 and map it to sensor 2 M307 H2 R2.016 K0.366:0.030 D5.70 E1.35 S1.00 B0 V24.5 ; disable bang-bang mode for heater and set PWM limit M143 H2 S285 ; set temperature limit for heater 2 to 285C M308 S3 P"121.temp0" Y"thermistor" A"T2" T100000 B4138 ;configure sensor 3 as thermistor on pin 121.temp0 ; TOOL 2 ; correction val for port "121.temp0": H=-13; L=0 M950 H3 C"121.out0" T3 ; create nozzle heater output on 121.out0 and map it to sensor 3 M307 H3 R2.409 K0.350:0.180 D5.36 E1.35 S1.00 B0 V23.9 ; disable bang-bang mode for heater and set PWM limit M143 H3 S250 ; set temperature limit for heater 3 to 250C ; Fans M950 F0 C"out4" Q500 ; create fan 0 on pin out9 and set its frequency M106 P0 S0 H-1 L0.2 C"T0" ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out7" Q500 ; create fan 1 on pin out8 and set its frequency M106 P1 S1 H1 T60 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"out5" Q500 ; create fan 2 on pin 1.out6 and set its frequency M106 P2 S0 H-1 L0.2 C"T1" ; set fan 2 value. Thermostatic control is turned off M950 F3 C"out8" Q500 ; create fan 3 on pin 1.out7 and set its frequency M106 P3 S1 H2 T60 ; set fan 3 value. Thermostatic control is turned on M950 F4 C"121.out1" Q500 ; create fan 4 on pin 121.out1 and set its frequency M106 P4 S0 H-1 L0.4 C"T2" ; set fan 4 value. Thermostatic control is turned off M950 F5 C"121.out2" Q500 ; create fan 5 on pin 121.out2 and set its frequency M106 P5 S1 H3 T60 ; set fan 5 value. Thermostatic control is turned on M950 F6 C"!out6+out6.tach" Q500 ; create fan 6 on pin out4, this is a PWM fan so the output needs to be inverted, and using out4.tach as a tacho input M106 P6 S0 H-1 C"Filterbox" ; set fan 6 value. Thermostatic control is turned off M106 P6 S0 ; Input Shaping ;M593 P"zvdd" F42.2 ; cancel ringing at 42.2Hz ;(https://forum.e3d-online.com/threads/accelerometer-and-resonance-measurements-of-the-motion-system.3445/) ; Tools M563 P0 S"V6 Bowden" D0 H1 F0 ; define tool 0 G10 P0 X-8.02 Y38.97 Z-4.68 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M572 D0 S0.2 ; pressure advance T0 M308 S8 Y"linear-analog" P"1.io0.in" A"T0FilamentScale" B-65 C3240 ; Filament Weight Scale for tool 0 M563 P1 S"Volcano Bowden" D1 H2 F2 ; define tool 1 G10 P1 X-7.92 Y38.96 Z-13.2 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C M572 D1 S0.3 ; pressure advance T1 M308 S9 Y"linear-analog" P"1.io1.in" A"T1FilamentScale" B45 C4100 ; Filament Weight Scale for tool 1 M563 P2 S"Hemera Direct" D2 H3 F4 ; define tool 2 G10 P2 X21.05 Y43.75 Z-5.7 ; set tool 2 axis offsets G10 P2 R0 S0 ; set initial tool 2 active and standby temperatures to 0C M591 D2 P3 C"121.io1.in" ; Configure filament sensing for tool 2 M572 D2 S0.05 ; pressure advance T2 M308 S10 Y"linear-analog" P"1.io2.in" A"T2FilamentScale" B-233 C8500 ; Filament Weight Scale for tool 2 M563 P3 S"Spindle" R0 ; define tool 3 G10 P3 X0 Y52.50 Z-78.7 ; set tool 3 axis offsets M563 P4 S"Pen" ; define tool 4 G10 P4 X0 Y50.0 Z-21.0 ; set tool 4 axis offsets ; PowerFail Script (use M916 to resume the print from where it stopped) M911 S23.6 R23.8 P"M913 X0 Y0" ; set voltage thresholds and actions to run on power loss ;MCU Temp Calibration M912 P0 S8 ;room temp: 20°C (reportet MCU temp right after startup: 12°C) M308 S5 Y"mcu-temp" A"6HC MCU" ;show MCU-temp of Mainboard (MB6HC) in DWC (Tools -> Extra) Graph M308 S6 Y"mcu-temp" P"1.dummy" A"3HC MCU" ;show MCU-temp of CAN expansion board 1 (3HC) in DWC (Tools -> Extra) Graph M308 S7 Y"mcu-temp" P"121.dummy" A"1LC MCU" ;show MCU-temp of CAN expansion board 121 (1LC) in DWC (Tools -> Extra) Graph ;DHT Sensor (temp and humidity) M308 S11 P"io6.out" Y"dht22" A"Chamber" ; define DHT22 temperature sensor M308 S12 P"S11.1" Y"dhthumidity" A"Rel. Humidity[%]" ; attach DHT22 humidity sensor to secondary output of temperature sensor

    If you or anyone suspect something inside a called macro, you can have a look at my public repo:
    https://github.com/marvineer98/MultiPrint_RRF_config/tree/backup

  • Discuss and contribute to the Duet Software Framework

    131
    Topics
    1.1k
    Posts

    undefined

    @Gamefanatic3D thanks, I have corrected the persistentGlobal.g example.

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

    405
    Topics
    3.2k
    Posts

    undefined

    @Triet we do process a lot of segments together, however we need to retain low latency for starting movement and for pausing. If you want to advance feedforward by 6 seconds then that means we would have to delay starting moton for 6 seconds from when you send the first motion command; otherwise how can we apply the correct feedforward to that first move? Similarly we would have to delay responding to a pause command for 6 seconds so that we don't apply incorrect feedforward to moves that have already been queued.

    The compromise we have chosen is to use 50ms latency. So moves already in the queue can be amended up to about 50ms before they are due to start. We could maybe increase it to 100ms without users complaining too much, but certainly not to 6 seconds.

  • Prototype hardware issues.

    50
    Topics
    675
    Posts

    undefined

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

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

    130
    Topics
    1.3k
    Posts

    T3P3Tonyundefined

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

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

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

    948
    Topics
    7.5k
    Posts

    undefined

    Good evening,

    Would it be possible to operate an extruder in closed loop mode?

    For instance with:

    Duet3D magnetic encoder on the extruder's stepper (commutation) Duet3D magnetic filament monitor near the hotend (close the loop) Duet3D 1HCL

    If this would be possible, it could improve:

    Estep calibration, material independent Retraction Backlash in the bowden tube VFA due to excentric hobs VFA due to speed variations caused by poorly meshed (dual) extruder gears Possibly pressure advance Non linear extrusion Extruder feed forward

    Thanks in advance!

  • 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

    Oben221undefined

    @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

    Phaedruxundefined

    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