Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.4k
    Topics
    88.6k
    Posts

    undefined

    @DaveA said in With Shapeways gone - what now?:

    @fcwilt I don't know what the status of Shapeways is but I've been using https://www.jawstec.com/ for some SLA parts.

    Thanks - I will check them out.

    The current folks at Shapeways state they are trying to get up and running again but time will tell.

    Frederick

  • Using Duet Controllers

    829
    Topics
    7.5k
    Posts

    undefined

    @Esteban said in Information on the distribution of calculations on Duet cards:

    My first question arose from the fact that my machine, equipped with a single Duet 3 Mini 5+ card, shows artifacts when turning at “high speed”. I've carried out numerous speed and acceleration tests, and yet (without exceeding the mechanical limits of my printer) at high speed, it still lets gohsting appear in combined/complex movements such as bends, exceeding 120mm/s.

    Which firmware version are you using? 3.6 series firmware is much more effective at reducing ghosting on bends than 3.5 series is.

    @Esteban said in Information on the distribution of calculations on Duet cards:

    So I wanted to know if it's possible to saturate the Cortex M4? And if so, does it simplify calculations for the various movements?

    It's likely that you can saturate it by sending a lot of GCode commands in succession each of which commands a very small movement. If that happens then the print would slow down and perhaps get a little jerky. The only simplification that it performs is that if when the microstep rate gets very high, it calculates the interval between steps every 2, 4 or 8 steps instead of every step and then interpolates te timings of the other steps.

    @Esteban said in Information on the distribution of calculations on Duet cards:

    My second question is whether there's a way / a calculation to know if the calculations required of the processor by GCode are too complicated or not?

    You can get an idea of this by running the print in simulation mode. RRF will do most of the same calculations but it won't generate the steps.

    @Esteban said in Information on the distribution of calculations on Duet cards:

    In the case of expansion board connections, a 3HC, which board will perform PWM, motors and temperature monitoring calculations? In a certain logic, each board only performs the calculations for its own sub-components (except for the main board, which also reads the code and compiles the information received by the CAN to display it on the screen)?

    The main board does all the GCode processing and queues the commanded moves. For motors connected to expansion boards, the expansion board applies input shaping and generated the step pulses. On Duets, all PWM output is done by hardware. Management of heaters is done by the board that the heater is connected to.

    @Esteban said in Information on the distribution of calculations on Duet cards:

    SBC mode can help relieve the main board of certain calculations?

    In SBC mode the parsing of GCode files, the management of the filesystem and typically the user interface are tasks managed by the SBC. The Duet main board still calculates the moves.

    @Esteban said in Information on the distribution of calculations on Duet cards:

    My machine will soon have two servomotors in a loop connected to a 1XD daughter board, and I'm wondering if there might be a slight latency between the two 1XD boards (the X-axis and the Y-axis)? Especially in combined movements ...

    In a CAN-connected system, mves are sent to CAN-connected expansion boards a few tens of milliseconds in advance of when they are scheduled to start. A time sync protocol keeps the clocks of all the boards in sync with the main board. So using expansion boards doesn't introduce any differential latency. However, your servomotors may introduce latency.

    @Esteban said in Information on the distribution of calculations on Duet cards:

    Finally, I can't quite figure out who sends the correction command to the motor in the event of an error between the 1XD and the integrated box (for example, with a Cl-42-T box or much more powerful industrial boxes).

    Please explain what you mean by "correction command". It is the job of the servo motor to maintain the correct position. Servos typically have an error output that can be used to signal to the 1XD that they have been unable to maintain position. Such an error can be captured by an event handler in RRF. After fixing whatever caused the error, you would generally need to re-home the axis before continuing.

    BTW when using servos or other external motor controllers to drive the main axes of a machine, we recommend using the Duet 6XD main board instead of 1XD expansion boards because it achieves higher step rates. It also has a more powerful processor than the Duet 3 Mini.

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

    8.5k
    Topics
    76.7k
    Posts

    undefined

    @Triet Probably easiest just to connect a Klipper-ised RPi to the Duet 2 WiFi, via USB, and install Bossa on the Raspberry Pi. When you want to run Klipper, flash the MCU firmware. When you want to run RRF, flash the Duet 2 with RRF using Bossa and use it in standalone mode. You can probably leave the SD card in the Duet, as the Klipper doesn't use it.

    What limitations are you finding at the moment? The Duet 2 is getting a bit old now, and is limited by the size of the flash memory for all the current RRF features, but generally that's just extra kinematics.

    Ian

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

    581
    Topics
    5.0k
    Posts

    undefined

    @dhusolo can you provide a link to the manual for the VFD?

  • Prototype hardware issues.

    26
    Topics
    805
    Posts

    undefined

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

  • Discuss Duet on laser cutters and engravers.

    183
    Topics
    1.5k
    Posts

    undefined

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

  • Ask questions about installing the firmwares here

    2.1k
    Topics
    23.7k
    Posts

    undefined

    @kazolar for touch mode it's the same as for any other probe type, use the A parameter in the M558 command that configures the probe. There isn't a facility to do multiple scans in scanning mode.

  • 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

    @ash100 if it read zero, that suggests that the connection between the coil and the control board is broken.

  • Discuss using conditionals, loops and variables in gcode

    791
    Topics
    5.6k
    Posts

    undefined

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

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.0k
    Posts

    undefined

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

  • Feedback for docs.duet3d.com

    115
    Topics
    549
    Posts

  • We'd love to know what your Duet electronics is controlling! When you have your Duet up and running and controlling a 3D printer or other machine, please tell us about it here.

    Example setups and prints
    802
    Topics
    9.7k
    Posts

    undefined

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

    Thanks - looks interesting - especially the gearing you have added.

    These spur gears were printed with a resin printer using anycubic's tough resin. They don't last for ages, but I can print a whole bunch at once.
    There are a few user on this board using simpleFOC with it's GCode-compliant step/dir interface.
    It's a bit of a learning curve to get used to it's PID behaviour... Their development & documentation status isn't as professional as Duet3D's, yet.
    In the past, I've tagged some threads with sFOC or simpleFOC if you are interested.

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

    116
    Topics
    793
    Posts

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

    DueUI
    178
    Topics
    2.5k
    Posts

    undefined

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

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

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

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

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

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

  • Accessories and Add-ons

    66
    Topics
    599
    Posts

  • Forum for discussing the Duet3d Filament Monitor

    397
    Topics
    3.9k
    Posts

    T3P3Tonyundefined

    @adrien_tobeca more recent firmware reports the raw angle:

    M591 D0 Duet3D Roto magnetic filament monitor, enabled always, 25.20mm/rev, allow 10% to 190%, check printing moves every 2.0mm, agc 45, raw angle 354, no calibration data

    Also you can use the "S" parameter in M591 to monitor movement all the time if you prefer:

    Sn 0 = disable filament monitoring (default), 1 = enable filament monitoring when printing from SD card, 2 = enable filament monitoring all the time (S2 is supported RRF 3.5.0 and later ). Filament monitors accumulate calibration data (where applicable) even when filament monitoring is disabled

    https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m591-configure-filament-sensing

  • Discuss the smart PCB effector for delta printers here.

    411
    Topics
    4.1k
    Posts

    undefined

    @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

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

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

    Ian

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

    685
    Topics
    5.4k
    Posts

    undefined

    @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

    undefined

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

    Next step is to actually connect to a Duet3 🙂

    IMG_9231.jpg IMG_9232.jpg

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

    127
    Topics
    1.3k
    Posts

    T3P3Tonyundefined

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

  • RepRapFirmware on other controllers

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

    undefined

    @dc42 said in [3.6.0-rc.2] Code 3 move error:

    @MaxGyver said in [3.6.0-rc.2] Code 3 move error:

    Last software reset at 2025-04-01 13:22, reason: MemoryProtectionFault mmarValid daccViol, Platform spinning, available RAM 108732, slot 1

    I noticed the above in your M122 report. Do you know what provoked it?

    Unfortunately not. I had the same error again while printing the firts layer.

    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.01 (SBC mode) Board ID: 0JD2M-999AL-D25S4-7J1D2-3SJ6K-T51V3 Used output buffers: 1 of 40 (18 max) === RTOS === Static ram: 137420 Dynamic ram: 98656 of which 0 recycled Never used RAM 86548, free system stack 130 words Tasks: LASER(5,nWait 7,0.0%,167) SBC(2,nWait 7,0.9%,809) HEAT(3,nWait 6,0.0%,343) TMC(4,nWait 6,3.0%,375) CanReceiv(6,nWait 1,0.1%,770) CanSender(5,nWait 7,0.0%,327) CanClock(7,delaying,0.0%,348) MAIN(1,running,95.9%,500) IDLE(0,ready,0.1%,29) USBD(3,blocked,0.0%,149), total 100.0% Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:51:27 ago, cause: software Last software reset at 2025-04-01 13:56, reason: User, Platform spinning, available RAM 85548, slot 2 Software reset code 0x2000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 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 893, maxWait 1145489ms, bed comp in use: mesh, height map offset 0.000, hiccups added 0/0 (0.00/22.42ms), max steps late 0, ebfmin 0.00, ebfmax 0.00 Pos req/act/dcf: 98537.00/98253/0.34 62047.00/62132/-0.86 2388.00/2389/-0.87 Next step interrupt due in 142 ticks, disabled Driver 0: standstill, SG min n/a, mspos 8, reads 15179, writes 22 timeouts 1 Driver 1: standstill, SG min n/a, mspos 8, reads 15179, writes 22 timeouts 1 Driver 2: standstill, SG min n/a, mspos 8, reads 15179, writes 22 timeouts 1 Driver 3: standstill, SG min n/a, mspos 8, reads 15179, writes 22 timeouts 1 Driver 4: standstill, SG min n/a, mspos 8, reads 15179, writes 22 timeouts 1 Driver 5: standstill, SG min n/a, mspos 8, reads 15179, writes 22 timeouts 1 Phase step loop runtime (us): min=0, max=46, frequency (Hz): min=205, max=10000 === DDARing 0 === Scheduled moves 4906, completed 4846, LaErrors 0, Underruns [0, 0, 0] Segments left 10, axes/extruders owned 0x80000007, drives owned 0x80000007 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 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters 2 -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) 3 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 31: no filament === CAN === Messages queued 30786, received 201368, lost 0, ignored 0, errs 0, boc 0 Longest wait 2ms for reply type 6013, peak Tx sync delay 386, free buffers 50 (min 46), ts 14635/14634/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === Transfer state: 5, failed transfers: 0, checksum errors: 0 RX/TX seq numbers: 53220/53220 SPI underruns 0, overruns 0 State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x27a7c Buffer RX/TX: 864/2072-0, open files: 0 === Duet Control Server === Duet Control Server version 3.6.0-rc.2 (2025-03-31 10:50:27, 32-bit) HTTP+Executed: > Executing M122 File 0:/gcodes/LARGE SOFIA LAMPSHADE.gcode is selected, processing File: Buffered code: G3 X595.405 Y624.085 I-4.314 J1.866 E59.03433 Buffered code: G1 X595.555 Y625.451 E61.65082 Buffered code: G1 X595.363 Y626.871 E64.3791 Buffered code: G1 X595.253 Y627.261 E65.15063 Buffered code: G1 X594.762 Y628.389 E67.49298 Buffered code: G1 X594.557 Y628.731 E68.25217 Buffered code: G1 X593.692 Y629.799 E70.86893 Buffered code: G1 X530.615 Y691.023 E238.23745 Buffered code: G1 X529.101 Y692.304 E242.01349 Buffered code: G1 X527.47 Y693.353 E245.70575 Buffered code: G1 X525.685 Y694.194 E249.46271 Buffered code: G1 X523.985 Y694.745 E252.86527 Buffered code: G1 X522.022 Y695.116 E256.66898 Buffered code: G1 X520.059 Y695.221 E260.41187 Buffered code: G1 X518.125 Y695.07 E264.1054 Buffered code: G1 X516.185 Y694.66 E267.88074 Buffered code: G1 X444.689 Y674.356 E409.39167 Buffered code: G3 X442.260 Y671.078 I0.979 J-3.264 E417.70323 Buffered code: G1 F1290.186 Buffered code: G1 X442.218 Y670.833 E418.18384 Buffered code: G1 F1270.827 Buffered code: G1 X442.176 Y670.589 E418.66983 Buffered code: G1 F1252.039 Buffered code: G1 X442.134 Y670.344 E419.16508 Buffered code: G1 F1234.906 Buffered code: G1 X442.104 Y670.24 E419.38373 Buffered code: G1 F1218.236 Buffered codes: 1248 bytes total Code buffer space: 2024 Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0 Full transfers per second: 38.54, max time between full transfers: 362.2ms, max pin wait times: 73.7ms/16.9ms Codes per second: 1.65 Maximum length of RX/TX data transfers: 4604/1352

  • Discuss and contribute to the Duet Software Framework

    130
    Topics
    1.1k
    Posts

    undefined

    @chrishamm Thanks! That was it.

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

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

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

    404
    Topics
    3.2k
    Posts

    undefined

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

  • Prototype hardware issues.

    50
    Topics
    675
    Posts

    undefined

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

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

    130
    Topics
    1.3k
    Posts

    T3P3Tonyundefined

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

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

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

    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

    undefined

    @T3P3Tony

    If you go to the General section of the DWC there are a number of options/values that can be set/changed.

    So I was thinking that would be a place to have an "on/off" option that would change the behavior.

    As to M568 - I am using that.

    Here is a the relevant code from one of the filament config files:

    set global.print_beg_tool_temp_a [var.index] = 190 set global.print_beg_tool_temp_s [var.index] = 100 set global.print_beg_tool_ext_adj[var.index] = 100 set global.print_beg_tool_spd_adj[var.index] = 100 set global.print_beg_tool_bby_stp[var.index] = 0 set global.print_beg_tool_prime [var.index] = 10 set global.print_beg_tool_retract[var.index] = 0.5 set global.print_end_tool_retract[var.index] = 0.5 set global.print_beg_bed_temp_a [var.index] = 60 set global.print_beg_bed_temp_s [var.index] = 30

    Later on there is this code in another routine that applies these values:

    ; this part is just to make the use of these values down below a bit easier to read by using shorter names var bed_temp_a = global.print_beg_bed_temp_a [var.tool] var bed_temp_s = global.print_beg_bed_temp_s [var.tool] var tool_temp_a = global.print_beg_tool_temp_a [var.tool] var tool_temp_s = global.print_beg_tool_temp_s [var.tool] var ext_adj = global.print_beg_tool_ext_adj[var.tool] var spd_adj = global.print_beg_tool_spd_adj[var.tool] var bby_stp = global.print_beg_tool_bby_stp[var.tool] M568 P{var.tool} S{var.tool_temp_a} R{var.tool_temp_s} ; set extruder heater temps (active and standby) M221 D{var.tool} S{var.ext_adj} ; set extruder extrusion percentage adjust M140 S{var.bed_temp_a} R{var.bed_temp_s} ; set bed heater temps (active and standby) M220 S{var.spd_adj} ; set print speed adjust M290 R0 S{var.bby_stp} ; set initial baby steps

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

    349
    Topics
    3.8k
    Posts

    undefined

    @dc42 I dont know why i didn't think about backlash. commented out the extra z movments and perfect!
    Thank you.

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

    108
    Topics
    967
    Posts

    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