Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.3k
    Topics
    88.6k
    Posts

    stuartofmtundefined

    I'm trying to get telnet to work as part of an experiment I'm doing but having no luck.

    I've looked at this post:
    https://forum.duet3d.com/topic/27396/basic-telnet-connection-help?_=1743333389705

    I cannot get the python code to reflect the messages in M118.

    I'm using SBC Bookworm with 3.6.0-rc.1

    Here are some questions:

    ON SBC: Does Duet Firmware implement its own telnet server or does it rely on the OS (telnetd)?

    If telnetd is not running - I get a connection refused message. If telnetd is running connection succeeds but I do not see the output from M118 P4 S"Message"

    Depending on the answer above - what does M586 P2 S1 actually do? Does it start a duet firmware telnet server? Does it enable / block M586 P2

    I've seen a suggestion of using Putty to confirm telnet messages are being sent. Connection to the SBC using telnet on Putty does not show the M118 messages either.

  • Using Duet Controllers

    828
    Topics
    7.5k
    Posts

    Phaedruxundefined

    @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

    Trietundefined

    @stuartofmt I slowly tend to that Shelly thing as it looks like a manageable and straightforward solution, until I am forced to do something more fancy. Thanks.

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

    580
    Topics
    5.0k
    Posts

    Jon vdkundefined

    An update:

    I have modified the RepRap fusion 360 post processor to allow for my 4th axis with two options to handle 3 + 1 machining. This enables the configuration of my machine to simply think the A axis is a 4th prismatic axis with no rotational kinematics to consider.

    The first option rotates the orientation from the angled tool orientation back to the wcs. This was done so that an easy kinematic configuration on the duet which would just translate the tool according to the given A angle so that the the tip remains in the desired location. The machines kinematics would look like the one described in my above post.

    The second option in the post processor is to both rotate and translate the tool orientation back to the wcs. This uses the selected tools length or an optional input length to calculate the translation required. With this option no transformation or kinematics are needed on the machine. As long as an accurate length from the centre of rotation to the tool tip is known, this should work fine.
    I will post the post processor once I know it works once I complete the build.

    While this option should be able to work currently, it is not optimal. Optimally the machine touches off the tool to determine its z offset which will translate to the length from centre of rotation to the tool tip. With that offset length the duet can handle the kinematics.

    My question to @JoergS5 and @dc42 is how should I approach this? would this be relatively simple to implement if I was to add/modify a src/Movement/Kinematics file? In reality it is a CNC5AC with no C.

    Thank you for your time.

  • Prototype hardware issues.

    26
    Topics
    805
    Posts

    SanderLPFRGundefined

    @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

    jay_s_ukundefined

    @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

    gloomyandyundefined

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

    G31 K1 X0 Y36 Z3 ; define probe 1 offsets and trigger height
    M558.2 K1 S16 R120000 ; set drive current and reading offset

    You are not setting the probe threshold/trigger value in config.g (the P parameter to G31), so it will be using whatever the default is (which is almost certainly not correct) until you have performed a M558.1.

    As to the mesh not reading zero at the centre of the bed. I would expect the scan to return 0 for wherever you have homed/set Z=0, ideally you will be homing and calibrating the probe at the same location, which again is ideally probably in the centre of the bed. I don't think you have posted your homez.g file so I'm not sure what you are doing to set z=0. Depending upon how you are setting Z=0 you may need to adjust the position of the nozzle to place your szp coil over the same location used to set z=0 before carrying out the calibration of the szp.

  • 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

    Dutchprintingundefined

    @droftarts Hi ian, thank you for your swift response. Here is the m122

    Duet 6ch mainboard
    4x duet 1xd for the bridge/gantry
    1x 1XD for X-axis
    1x 1XD for extruder
    1x 1HCL for Y-motor (other one on mainboard for now)
    firmware: 3.5b4

    i am actually printing at the moment and shot the next video for reference, i will make another one when it has a longer perimiter. (dont mind the wobbly hot air tubes)
    https://www.dropbox.com/scl/fi/ipg2zb2h06mb7aswqh766/Video-30-03-2025-14-35-05.mov?rlkey=4mfreacwh6p62th9tp045yr8e&st=y9515bpx&dl=0

    m122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.5.0-beta.4 (2023-06-08 23:41:30) running on Duet 3 MB6HC v1.02 or later (standalone mode) Board ID: 08DJM-956BA-NA3TN-6J9D0-3SD6Q-1BB2T Used output buffers: 3 of 40 (36 max) === RTOS === Static ram: 155012 Dynamic ram: 120548 of which 204 recycled Never used RAM 67228, free system stack 136 words Tasks: NETWORK(1,ready,39.6%,169) ETHERNET(5,nWait,0.2%,314) HEAT(3,nWait,0.0%,353) Move(4,nWait,0.0%,243) CanReceiv(6,nWait,0.1%,771) CanSender(5,nWait,0.0%,330) CanClock(7,delaying,0.0%,349) TMC(4,nWait,8.2%,59) MAIN(1,running,51.8%,444) IDLE(0,ready,0.0%,30), total 100.0% Owned mutexes: === Platform === Last reset 01:05:48 ago, cause: software Last software reset at 2025-03-30 12:28, reason: User, Gcodes spinning, available RAM 68104, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,1 MCU temperature: min 25.0, current 35.1, max 35.6 Supply voltage: min 47.6, current 47.8, max 48.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.0, current 12.2, max 12.5, under voltage events: 0 Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/1936/1936, gc cycles 10 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, mspos 368, reads 9781, writes 21 timeouts 0 Driver 1: standstill, SG min n/a, mspos 8, reads 9791, writes 11 timeouts 0 Driver 2: standstill, SG min n/a, mspos 8, reads 9791, writes 11 timeouts 0 Driver 3: standstill, SG min n/a, mspos 8, reads 9792, writes 11 timeouts 0 Driver 4: standstill, SG min n/a, mspos 8, reads 9792, writes 11 timeouts 0 Driver 5: standstill, SG min n/a, mspos 8, reads 9792, writes 11 timeouts 0 Date/time: 2025-03-30 13:34:04 Slowest loop: 130.70ms; fastest: 0.05ms === Storage === Free file entries: 19 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 7.2ms, write time 67.0ms, max retries 0 === Move === DMs created 125, segments created 6, maxWait 3426434ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00 next step interrupt due in 30425683 ticks, disabled === DDARing 0 === Scheduled moves 50, completed 47, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 17], CDDA state 3 === DDARing 1 === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Movement locks held by null, null HTTP is idle 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 assembling a command 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 doing "M42 P6 S0" in state(s) 0 0, running macro 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 Q0 segments left 0, axes/extruders owned 0x80000003 Queue 0 has 'M42 P4 S0' for move 49 Queue 0 has 'M42 P6 S0' for move 50 Queue 0 has 'M42 P5 S0' for move 50 Queue 0 has 'M42 P4 S0' for move 50 Queue 0 has 'M42 P6 S0' for move 50 Queue 0 has 'M42 P5 S0' for move 50 Queue 0 has 'M42 P4 S0' for move 50 Queue 0 has 'M42 P6 S0' for move 50 Queue 0 has 'M42 P5 S0' for move 50 Queue 0 has 'M42 P4 S0' for move 50 Queue 0 has 'M42 P6 S0' for move 50 Queue 0 has 'M42 P5 S0' for move 50 Queue 0 has 'M42 P4 S0' for move 50 Queue 0 has 'M42 P6 S0' for move 50 Queue 0 has 'M42 P5 S0' for move 50 Queue 0 has 'M42 P4 S0' for move 50 Q1 segments left 0, axes/extruders owned 0x0000000 Code queue 1 is empty === CAN === Messages queued 20007, received 300264, lost 0, boc 0 Longest wait 1ms for reply type 6041, peak Tx sync delay 281, free buffers 50 (min 46), ts 19744/19743/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 1158.85ms; fastest: 0.03ms Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 2 of 8 = Ethernet = Interface state: active Error counts: 0 0 0 1 0 0 Socket states: 5 2 2 2 2 0 0 0 = WiFi = Interface state: disabled Module is disabled Failed messages: pending 0, notready 0, noresp 0 Socket states: 0 0 0 0 0 0 0 0 === Multicast handler === Responder is inactive, messages received 0, responses 0

  • Discuss using conditionals, loops and variables in gcode

    791
    Topics
    5.6k
    Posts

    Mike 1undefined

    @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

    dc42undefined

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

  • Feedback for docs.duet3d.com

    115
    Topics
    548
    Posts

    droftartsundefined

    @ComedianTF2
    @dc42 replied:

    looking at the code, M140 and M141 (they use the same code) support only one P, one H, one S and one R parameter.
    I've been aware for several years that the support for multiple bed heaters may need to be changed because slicers assume a single bed heater.

    So I was wrong, sorry! You'll have to set them individually for now. I don't see any feature requests for this functionality, so maybe you could create one? https://github.com/Duet3D/RepRapFirmware/issues and click 'New issue', select 'Feature request'.

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

    DIY-O-Sphereundefined

    @fcwilt
    That is a good option. I hope you both have a great time with them.

  • 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

    stuartofmtundefined

    @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

    droftartsundefined

    @jay_s_uk Awesome work!

    Ian

  • 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

    elmoretundefined

    @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

    droftartsundefined

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

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

    Ian

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

    685
    Topics
    5.4k
    Posts

    Candyundefined

    @dc42 Nice. Thanks for the help. This means a lot

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

    206
    Topics
    2.2k
    Posts

    taeggeundefined

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

    CrazyCreatorundefined

    @jay_s_uk
    Oh dear... How could I have forgotten that? I put the MOSFET in a small bowl so I wouldn't forget it!!!

    Now the fan works too 🙂

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

    Argoundefined

    Hi,

    last print failed / stopped.
    It seems communication with Duet tool board was lost?
    The print continued and I found the extruder in it's final parking position.
    After disconnecting power for a moment, everything worked again.
    Both the board and tool board (1LC) run the firmware from the 3.6.0 RC1 bundle.

    Error message:

    IMG_0470.jpeg

    Config:

    ;; Helpful Toolboards commands ;M115 B121 ; Show board 121 ;M997 B121 ; Update tool 121 ;M122 B121 ; Detailed status of toolboard G4 S1 ; wait 1s for expansion boards to start ; General preferences G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ; Network M550 P"Walross" ; Set machine name M552 S1 ; Enable network ;*** Access point is configured manually via M587 M586 P0 S1 ; Enable HTTP M586 P1 S1 ; Disable FTP M586 P2 S1 ; Disable Telnet M575 P1 S1 B57600 ; Panel Due ; Printer geometry M669 K1 ; Select CoreXY mode M208 X0:290 Y-3:300 Z-0.2:270 ; Axis Limits M564 H0 ; allow unhomed movement ;------- drives from top--------------------------------------------------- ; B -------+------ A ; | P.02 | P.03 | ; -------+------- Z-Drives ; | P0.1 | P0.4 | ; -------+------- ; Front ; Drive Mappings M569 P121.0 S0 D2 ; Drive 0: E Axis M569 P0.1 S1 D2 ; Drive 1: Z-LeftFront Axis M569 P0.2 S0 D2 ; Drive 2: Z-LeftRear Axis M569 P0.3 S1 D2 ; Drive 3: Z-RightRear Axis M569 P0.4 S0 D2 ; Drive 4: Z-RightFront Axis M569 P0.5 S1 D2 ; Drive 5: Expansion: B motor (X-axis) M569 P0.6 S0 D2 ; Drive 6: Expansion: A motor (Y-axis) ; Motor remapping for dual Z and axis Limits M584 X5 Y6 Z1:2:3:4 E121.0 ; Motor mapping M671 X-60:-60:360:360 Y-10:370:370:-10 S20 ; Z leadscrews positions Left Front - Let Rear - Right Rear - Right Front ; Microstepping and Speed M350 X32 Y32 E16 Z32 I1 ; Configure microstepping with interpolation M92 X160.00 Y160.00 Z800.00 E682.00 ; Set steps per mm 1.8 motors ; Speeds, Acceleration and Jerk M566 X300.00 Y300.00 Z25.00 E600.00 P1 ; Set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z900.00 E7200.00 ; Set maximum speeds (mm/min) ; SpreadCycle M201 X5000.00 Y5000.00 Z1000.00 E3000.00 ; Set accelerations (mm/s^2) ; SpreadCycle ; Motor currents M906 X1250.00 Y1250.00 Z1100.00 E1200.00 I50 ; Set motor currents (mA) and motor idle factor in percent M84 S30 ; Set idle timeout ; Endstops for each Axis M574 X2 S1 P"io1.in" ; Set X endstop controlled by switch M574 Y2 S1 P"io2.in" ; Set Y endstop controlled by switch M574 Z1 S2 ; Set endstops controlled by probe "OLD" VINDA ;M574 Z1 S1 P"io6.in" ; Z endstop switch ; Stallgaurd Sensitivy (maybe use to pause print after crash) M915 X S2 F0 H200 R0 ; Set X axis Sensitivity 1.8 motors M915 Y S2 F0 H200 R0 ; Set y axis Sensitivity 1.8 motors ; Input Shaper and Accelerometer M955 P121.0 I05 ;Accelerometer M593 P"zvdd" F50.7 S0.12 ; Z-Probe M558 P8 C"121.io2.in" I1 H1.5 F350:300 T12000 A15 S0.001 ; VINDA ; Mesh Grid M557 X5:260 Y30:250 P7 ; ; Z Probe Offset (Probe behind Afterburner) G31 P1000 X0 Y25 Z0.700 ; VINDA - 3DSWay Textured 0.4 nozzle ;G31 P1000 X0 Y25 Z0.580 ; VINDA - 3DSWay Textured 0.4 nozzle ; Filament Runout sensor ;M591 D0 P3 L25.95 E3 R1:900 C"121.io1.in" S1 ; Filament Sensor ; Heatbed Heaters and Thermistor Bed M308 S0 P"temp0" Y"thermistor" T100000 B4725 C7.060000e-8 ; Heatbed Thermistor M950 H0 C"out0" T0 Q10 ; Creates Bed Heater (SSR) M307 H0 R0.889 K0.762:0.000 D3.02 E1.35 S0.7 B0 M140 H0 ; Bed uses Heater 0 M143 H0 S116 ; Set temperature limit for heater 0 to 115C Bed ; HotEnd Heaters and Thermistor HotEnd M308 S1 P"121.temp0" Y"thermistor" T100000 B4725 C7.06e-8 ; define E0 temperature sensor M950 H1 C"121.out0" T1 Q100 ; Create HotEnd Heater M307 H1 R4.568 K0.683:0.000 D4.04 E1.35 S1.00 B0 V24.4 ; PID as heater M143 H1 S295 ; Set temperature limit for heater 1 to 285C HotEnd M302 S15 R15 ; min extrusion (cold extrusion) temp ; Fans Hotend + Part M950 F3 C"121.out1" Q100 ; Creates HOTEND Fan M106 P3 T65 L1.0 X1.0 H1 ; HOTEND Fan Settings M950 F0 C"121.out2" Q100 ; Creates PARTS COOLING FAN M106 P0 H-1 ; Parts Cooling Fan ; Fans Electronic compartment & Exhaust M950 F1 C"out3" Q100 ; Creates Case Fan 1 M106 P1 T40 S170 L170 X170 H0 ; Case Fan 1 Settings M950 F2 C"out4" Q100 ; Creates Case Fan 2 M106 P2 T40 S170 L170 X170 H0 ; Case Fan 2 Settings M950 F5 C"out5" Q100 ; Creates Exhaust Fan M106 P5 T82 S150 L150 X150 H0 ; Exhaust fan ; Chamber Thermistor M308 S3 P"temp1" A"Chamber" Y"thermistor" T100000 B4725 C7.060000e-8 ; define chamber sensor ; Tools M563 P0 D0 H1 F0 ; Define tool 0 G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

    M122 B121 after reset:

    M122 B121 Diagnostics for board 121: Duet TOOL1LC rev 1.1 or later firmware version 3.6.0-rc.1 (2025-02-28 15:03:36) Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1) All averaging filters OK Never used RAM 7480, free system stack 140 words Tasks: Move(3,nWait 7,0.0%,140) TMC(2,nWait 6,3.6%,52) HEAT(2,nWait 6,0.2%,110) CanAsync(5,nWait 4,0.0%,58) CanRecv(3,nWait 1,0.0%,70) CanClock(5,nWait 1,0.0%,58) ACCEL(3,nWait 6,0.0%,72) MAIN(1,running,91.4%,318) IDLE(0,ready,0.0%,26) AIN(2,delaying,4.8%,112), total 100.0% Owned mutexes: Last reset 01:45:08 ago, cause: power up Last software reset time unknown, reason: AssertionFailed, available RAM 3392, slot 0 Software reset code 0x0120 ICSR 0x00000000 SP 0x2000415c Task Freestk 129 bad marker Stack: 00000544 00022ffc 00019b65 20003134 00016cff 20003134 000163d1 20000ed0 00000000 00000001 00008275 200071c8 200071c8 200071e0 00000000 20000f50 00011647 000223b8 00022474 00021ac8 00019b05 200071c8 200071c8 20000f50 000083ed 200071d8 000009c7 Moves scheduled 0, hiccups 0 (0.00/0.00ms), segs 0, step errors 0 (types 0x0), maxLate 0 maxPrep 0, ebfmin 0.00 max 0.00 Peak sync jitter -5/11, peak Rx sync delay 207, resyncs 0/0, no timer interrupt scheduled, next step interrupt due in 3858308480 ticks, disabled VIN voltage: min 24.2, current 24.2, max 24.3 MCU temperature: min 36.0C, current 36.3C, max 44.9C Driver 0: pos 0, 682.0 steps/mm, standstill, SG min 0, read errors 0, write errors 0, ifcnt 13, reads 8669, writes 13, timeouts 0, DMA errors 0, CC errors 0 Last sensors broadcast 0x00000002 found 1 91 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 126204, send timeouts 0, received 55152, lost 0, ignored 0, errs 0, boc 0, free buffers 18, min 18, error reg 0 dup 0, oos 0/0/0/0, rxMotionDelay 0 Accelerometer: LIS3DH, status: 00 I2C bus errors 0, naks 3, contentions 0, other errors 0

  • Discuss and contribute to the Duet Software Framework

    130
    Topics
    1.1k
    Posts

    achrnundefined

    @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

    Trietundefined

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

  • 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

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