Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.3k
    Topics
    88.4k
    Posts

    undefined

    @troydeming

    Just to be sure we are all on the same page, what is the issue you are having with homing?

    Frederick

  • Using Duet Controllers

    828
    Topics
    7.5k
    Posts

    droftartsundefined

    @gsch1803 are you setting a static IP address with M552? Have you tried a different Ethernet cable to the Duet, or checked the one you’re using with another device?

    Ian

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

    8.5k
    Topics
    76.6k
    Posts

    undefined

    Hi All,

    Last year I received an E3D toolchanger from a friend. Recently I've been having an issue where the current tool heater setpoint will be set to 0 after a little under 4hrs of printing. The printer will continue trying to print but extrusion will stop once the hotend temp reaches below extrusion minimum temp.

    Its not a timeout. The heater setpoint itself is being set to 0. Like the actual temperature target. It is not a heater error, there are no errors in the logs, the heater is still shown as 'active' in the web control UI, and it continues to print. I have PID tuned the heater multiple times, no change I have power cycled the printer before printing, no change (still is set to 0 after ~4hrs of printing)

    This is the Gcode file I was printing. I use OrcaSlicer. Please note I had the feedrate machine side set to 90%, so it took longer than the estimate.

    It set the heater to 0 about 3hrs/53min into the print, between layer 312 and 315.

    obj_1_rotator cube 3.STL_CookieCAD_PLA_3h35m.gcode

    Troubleshooting goals:

    upload a photo of the temperature graph showing setpoint and temp drop test another slicer to see if issue is replicated

    Thank you.

    Config:

    ; Configuration file for Duet WiFi / Ethernet running RRF3 on E3D Tool Changer ; executed by the firmware on start-up ; General preferences M111 S0 ; Debugging off G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves M667 S1 ; Select CoreXY mode ; Network M550 P"ToolChanger" ; Set machine name M587 S"****" P"****" ; WiFi Settings M552 S1 P"****" ; Enable WiFi Networking M552 S1 ; Enable Networking M586 P0 S1 ; Enable HTTP M586 P1 S1 ; Enable FTP M586 P2 S0 ; Disable Telnet ; Drive direction M569 P0 S0 ; Drive 0 X M569 P1 S0 ; Drive 1 Y M569 P2 S1 ; Drive 2 Z M569 P3 S0 ; Drive 3 E0 M569 P4 S1 ; Drive 4 E1 M569 P5 S1 ; Drive 5 E2 M569 P6 S1 ; Drive 6 E3 M569 P7 S0 ; Drive 7 COUPLER M569 P8 S0 ; Drive 8 Pebble Wiper M569 P9 S0 ; Drive 9 UNUSED M584 X0 Y1 Z2 C7 E3:4:6:5 A8 ; Apply custom drive mapping M208 X-35:328.5 Y-49:243 Z0:300 C-45:360 A0:55 ; Set axis maxima & minima M92 X100 Y100 Z800 C91.022 E409:409:409:409 A360 ; Set steps per mm assuming x16 microstepping M350 E16:16:16:16 A16 I1 ; Configure microstepping with interpolation M350 C16 I0 ; Configure microstepping without interpolation M350 X16 Y16 Z16 I1 ; Configure microstepping with interpolation M566 X300 Y300 Z100 C2 E300:300:300:300 ; Set maximum instantaneous speed changes (mm/min) M203 X30000 Y30000 Z2000 C5000 E5000:5000:5000:5000 ; Set maximum speeds (mm/min) M201 X3000 Y3000 Z1000 C500 E5000:5000:5000:5000 ; Set accelerations (mm/s^2) M906 X2000 Y2000 Z1330 I30 ; Idle motion motors to 30% M906 E1200:1200:1200:1200 C500 I10 ; Idle extruder motors to 10% ; Pebble Wiper M566 A360 ; Set maximum instantaneous speed changes (mm/min) M201 A1200 ; Set accelerations (mm/s^2) M203 A6000 ; Set maximum speeds (mm/min) M906 A1000 I20 ; Set motor currents (mA) and idle percent M574 A1 S2 ; Set A endstop stall detection (using Z probe) M950 S1 C"duex.pwm4" Q333 ; Servo hooked up to PWM 4 header ; Endstops M574 X1 Y1 S3 ; Set X / Y endstop stall detection M574 C0 Z0 ; No C Z endstop ; Z probe M558 P8 C"zstop" H3 F360 I0 T20000 ; Set Z probe type to switch, the axes for which it is used and the dive height + speeds G31 P200 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height M557 X10:290 Y20:180 S40 ; Define mesh grid ;Stall Detection M915 X Y S1 F0 H400 R2 ; X / Y Axes ; Heaters M308 S0 P"e1temp" Y"thermistor" A"Bed" T100000 B4138 C0 ; Set thermistor M950 H0 C"bedheat" T0 ; Bed heater M307 H0 B0 M143 H0 S225 ; Set temperature limit for heater 0 to 225C M140 H0 ; Bed heater is heater 0 M308 S1 P"e2temp" Y"thermistor" A"T0" T100000 B4658 C6.5338987554e-08 ; Set thermistor M950 H1 C"e0heat" T1 ; Extruder 0 heater M143 H1 S305 ; Set temperature limit for heater 1 to 300C M307 H1 S0.8 M308 S2 P"e3temp" Y"thermistor" A"T1" T100000 B4658 C6.5338987554e-08 ; Set thermistor M950 H2 C"e1heat" T2 ; Extruder 0 heater M143 H2 S305 ; Set temperature limit for heater 2 to 300C M308 S3 P"e4temp" Y"thermistor" A"T2" T100000 B4725 C7.060000e-8 ; Set thermistor M950 H3 C"duex.e4heat" T3 ; Extruder 0 heater M143 H3 S305 ; Set temperature limit for heater 3 to 300C M308 S4 P"e6temp" Y"thermistor" A"T3" T100000 B4725 C7.060000e-8 ; Set thermistor M950 H4 C"duex.e3heat" T4 ; Extruder 0 heater M143 H4 S305 ; Set temperature limit for heater 4 to 300C ; Tools M563 P0 S"T0" D0 H1 F2 ; Define tool 0 G10 P0 X0 Y0 Z0 ; Reset tool 0 axis offsets G10 P0 R0 S0 ; Reset initial tool 0 active and standby temperatures to 0C M563 P1 S"T1" D1 H2 F4 ; Define tool 1 G10 P1 X0 Y0 Z0 ; Reset tool 1 axis offsets G10 P1 R0 S0 ; Reset initial tool 1 active and standby temperatures to 0C M563 P2 S"T2" D2 H3 F6 ; Define tool 2 G10 P2 X0 Y0 Z0 ; Reset tool 2 axis offsets G10 P2 R0 S0 ; Reset initial tool 2 active and standby temperatures to 0C M563 P3 S"T3" D3 H4 F8 ; Define tool 3 G10 P3 X0 Y0 Z0 ; Reset tool 3 axis offsets G10 P3 R0 S0 ; Reset initial tool 3 active and standby temperatures to 0C ; Fans M950 F1 C"fan1" M950 F2 C"fan2" M950 F3 C"duex.fan3" M950 F4 C"duex.fan4" M950 F5 C"duex.fan5" M950 F6 C"duex.fan6" M950 F7 C"duex.fan7" M950 F8 C"duex.fan8" M106 P1 S255 H1 T70 ; T0 HE M106 P2 S0 ; T0 PCF M106 P3 S255 H2 T70 ; T1 HE M106 P4 S0 ; T1 PCF M106 P5 S255 H3 T70 ; T2 HE M106 P6 S0 ; T2 PCF M106 P7 S255 H4 T70 ; T3 HE M106 P8 S0 ; T3 PCF M376 H25 ; bed compensation taper height ; Tool offsets ; Z is negative because the nozzle is "Lower" than the Z axis switch ; If we want to move the nozzle closer to the bed, move Z toward zero ; If we want to move the nozzle away from the bed, move Z away from zero G10 P0 X20.000 Y43.500 Z-8.45 ; T0 G10 P1 X20.430 Y43.190 Z-7.60 ; T1 G10 P2 X20.970 Y43.410 Z-7.9 ; T2 G10 P3 X20.070 Y43.530 Z-8.1 ; T3 ; Pebble Wiper Offsets G10 P0 A{tools[0].offsets[2]} G10 P1 A{tools[1].offsets[2]} G10 P2 A{tools[2].offsets[2]} G10 P3 A{tools[3].offsets[2]} M572 D0 S0.00 ; pressure advance T0 M572 D1 S0.00 ; pressure advance T1 M572 D2 S0.00 ; pressure advance T2 M572 D3 S0.00 ; pressure advance T3 G29 S2 ; disable mesh T-1 ; deselect tools ;M955 P0 C"spi.cs4+spi.cs3" I42 ;configure accelorometer M593 P"zvdd" F41 ; configure input shaper ; Global Variables - Needed for on the fly tool position adjustment global T0_Pickup_X = -12.690 global T0_Pickup_Y = 227.600 global T1_Pickup_X = 77.210 global T1_Pickup_Y = 227.200 global T2_Pickup_X = 212.370 global T2_Pickup_Y = 226.550 global T3_Pickup_X = 301.590 global T3_Pickup_Y = 226.900 global primeAmount = 2.0 global tuneTools = false M501 ; Load them overrides

    M122:

    === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later + DueX5 Board ID: 0JD0M-9X6JA-JUNSW-6JKD4-3SJ6N-9VJRT Used output buffers: 1 of 26 (20 max) === RTOS === Static ram: 23836 Dynamic ram: 79032 of which 12 recycled Never used RAM 5264, free system stack 88 words Tasks: NETWORK(notifyWait,2263.6%,211) HEAT(notifyWait,44.6%,308) Move(notifyWait,478.2%,282) DUEX(notifyWait,0.0%,24) MAIN(running,861.0%,408) IDLE(ready,6.8%,30), total 3654.3% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 26:45:36 ago, cause: software Last software reset at 2025-03-14 13:52, reason: User, GCodes spinning, available RAM 4600, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 0 MCU temperature: min 31.3, current 33.6, max 42.8 Supply voltage: min 25.8, current 26.5, max 27.3, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/10, heap memory allocated/used/recyclable 2048/436/298, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min 0 Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: standstill, SG min 0 Driver 6: standstill, SG min n/a Driver 7: standstill, SG min 0 Driver 8: standstill, SG min 0 Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2025-03-15 17:41:16 Cache data hit count 4294967295 Slowest loop: 195.17ms; fastest: 0.09ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 23.1ms, write time 63.8ms, max retries 0 === Move === DMs created 83, segments created 45, maxWait 503821ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 937457, completed 937457, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by 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 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 Daemon is doing "G4 S10 " in state(s) 0 0, running macro Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 1, 0.00 reads/min === Network === Slowest loop: 179.06ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.27 WiFi MAC address 48:3f:da:a6:e2:b2 WiFi Vcc 3.38, reset reason Power up WiFi flash size 2097152, free heap 21304 WiFi IP address 192.168.7.98 WiFi signal strength -45dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0

    M98 P"config.g"

    M98P"config.g" HTTP is enabled on port 80 FTP is enabled on port 21 TELNET is disabled Error: in file macro line 156 column 21: meta command: variable 'T0_Pickup_X' already exists

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

    577
    Topics
    5.0k
    Posts

    undefined

    Im trying to connect a vfd to out 9 using this pwm converter https://www.amazon.com/dp/B091B6LGXB?ref=ppx_yo2ov_dt_b_fed_asin_title

    When i measure the pwm signal it is only putting out 3.8 volts when i turn the spindle on at the max rpm of 24,000. The voltage out is only getting to 9V.

    ; Configuration file for RepRapFirmware on Duet 3 Main Board 6HC ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.5.4 on Mon Sep 09 2024 22:47:07 GMT-0600 (Mountain Daylight Time) ; General G90 ; absolute coordinates M83 ; relative extruder moves M550 P"Duet3CNC" ; set hostname M453 ; select CNC mode ; Accessories M575 P1 S0 B57600 ; configure PanelDue support ; Smart Drivers M569 P0.0 S1 D2 ; driver 0.0 goes backwards (X axis) M569 P0.1 S0 D2 ; driver 0.1 goes backwards (Y axis) M569 P0.2 S1 D2 ; driver 0.2 goes forwards (Z axis) M569 P0.3 S1 D2 ; driver 0.3 goes forwards (U or Y2 axis) M569 P0.4 S1 D2 ; driver 0.4 goes forwards (V or Z2 axis) ; Motor Idle Current Reduction M906 I30 ; set motor current idle factor M84 S1000 ; set motor current idle timeout ; Axis M669 K0 ; set Cartesian kinematics M584 X0.0 Y0.1:0.3 Z0.2:0.4 U0.3 V0.4 P3 ; U=Y2 V=Z2 set axis mapping M350 X16 Y16 Z16 U16 V16 I1 ; configure microstepping with interpolation M906 X1205.2 Y1100.4 Z1100.4 U1100.4 V1100.4 ; set axis driver currents M92 X100.067 Y100.067 Z400 U100.067 V400 ; configure steps per mm M566 X60 Y60 Z60 U60 V60 ; set maximum instantaneous speed changes (mm/min) M203 X12000 Y12000 Z3000 U12000 V3000 ; set maximum speeds (mm/min) M201 X600 Y600 Z60 U600 V60 ; set accelerations (mm/s^2) ; Axis Limits M208 X0 Y0 Z-100 U0 V-100 S1 ; set axis minimum M208 X1252 Y2467.8 Z140 U2467.8 V140 S0 ; set axis maximum ; Endstops M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io2.in M574 Y1 S1 P"io2.in+io3.in" ; configure active-high endstop for low end on Y via pin io2.in M574 Z2 S1 P"io4.in+io5.in" ; configure active-high endstop for high end on Z via pin io4.in ;M574 U1 S1 P"io3.in" ; configure active-high endstop for low end on U (Y2) via pin io3.in ;M574 V2 S1 P"io5.in" ; configure active-high endstop for high end on V (Z2) via pin io5.in ; Probes M558 P5 C"!io6.in" H5 F120 T6000 ; configure analog probe via slot #0 G31 P850 X-10 Y-10 Z5.89 ; set Z probe trigger value, offset and trigger height ;M574 V2 S1 P"io5.in" ;M666 Y+2 ; move Y1 motor -1.5 from block to adjust for square ; Heaters M140 H-1 ; disable heated bed (overrides default heater mapping) M141 H-1 ; Tools M453 ; Set to CNC mode M950 R0 C"out9" Q1000 L0:24000 K1 ; configure spindle #0 M563 P1 S"Makita R0701C" R0 F0 ; create tool #0 ; Lasers M950 P2 C"out4" ; air Assist solenoid ; Laser offset from spindle is X - 57.5 Y - -49.10 M452 C"io7.out" R255 F500 S1 ; configure Laser port ;M563 P2 S"Laser" ;M452 ; LED Lighting ;M950 P3 c"out1" Q500 M950 F0 c"out1" Q500 ;M42 P3 S1 M106 P0 S0 H-1 C"LEDs" ;M563 P0 D-0 R0 ; tool 0 uses extruder 0, heater 1 and fan 0 ; Emergency Stop M950 J1 C"io8.in" M581 T1 P0:1 S1 R0 ;M582 T1 ;M42 P2 S1 ; Tools M563 P2 S"Laser" F0 ;M568 P0 F0 ; set initial tool #0 active and standby temperatures to 0C ; Miscellaneous ;M452 ; select Laser mode T0 ; select first tool M308 S10 Y"mcu-temp" A"MCU" M308 S11 P"DRIVER_0" Y"drivers" A"X Driver" M308 S12 P"DRIVER_1" Y"drivers" A"Y Driver" M308 S13 P"DRIVER_3" Y"drivers" A"Y1 Driver" M308 S14 P"DRIVER_2" Y"drivers" A"Z Driver" M308 S15 P"DRIVER_4" Y"drivers" A"Z1 Driver"

    What am i missing?

    Thanks

  • 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

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

    Auréundefined

    @Phaedrux Ok! Thank you very much! That's work fine now. 👍

    I had a problem with my tablet but I found the solution on this post.
    I also had an error report with my ZPROBE line in my config.g but after a complete reboot of the printer I no longer had an error.

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

    undefined

    After extensive testing, I concluded that something was distorting my sensor reading. Since I had two SameSky CUI AMT10E3 capacitive encoders.
    WhatsApp Image 2025-03-14 at 20.22.22.jpeg

    I set them to 2500PPR and mounted them. Now closed loop runs whisper quiet. Here are two examples:

    stealthchop.mp4
    closed loop.mp4

  • Discuss using conditionals, loops and variables in gcode

    790
    Topics
    5.6k
    Posts

    undefined

    I recently went through this exact thing with my multi-tool printer. I discovered that with Prusa Slicer and multiple tools, if you use only tool 1 (tool number in slicer number = RRF tool0), Prusa slicer does not include a T0 in it's output. But if you use any other tool as the only tool, or if you use multiple tools, then T0 is included in the gcode. I added the following to my printer's custom gcode:

    ; set the tool if only the first extruder is used {if is_extruder_used[0] and not is_extruder_used[1] and not is_extruder_used[2]}T0{endif}

    And while I'm sharing, I also include the following to set tool active and standby temperatures only when the tools are used:

    ;Set standby temperatures for extruders that are used in this print {if is_extruder_used[0]} M568 A1 P0 R{temperature[0] -5}{endif} {if is_extruder_used[1]} M568 A1 P1 R{temperature[1] -5}{endif} {if is_extruder_used[2]} M568 A1 P2 R{temperature[2] -5}{endif}

    Note that in the user interface Prusa refers to extruders starting with #1, but in their gcode output, they start numbering at 0.

  • Ask questions about the official web interface here

    1.6k
    Topics
    13.0k
    Posts

    undefined

    @dc42 Thanks. Here is my .pcap file. Wireshark reveals just how much back and forth takes place between my laptop browser and the Duet. I tried to limit the packets capture to just the act of uploading but that was hard. I believe the upload is initiated at the TimeStamp: 738 21.597390

    UploadFail.pcapng

  • Feedback for docs.duet3d.com

    114
    Topics
    542
    Posts

    undefined

    Ok perfect I could restart from the desired index thank you two.

    There are many things I don't get on M24 though, It is using the resurect file, but modifying the M26 line of the resurect file does not modify the resume index. I guess there are hidden actions at a deeper level!
    Is there any documentation I can read to understand it better?

    Alex

  • 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
    800
    Topics
    9.6k
    Posts

    dwuk3dundefined

    Auto alignment with ball probe complete.

    Original plan was to use the electro magnet on the bed - but it is quite weak - despite specs being near to the permanent magnet that works very well.

    So switched to having the magnet off the bed grabbing a big circular plate.

    Not sure how much it is really needed.

    Also ordered a bigger magnet - but not sure if I will need to use it.

    Demo video of homing, levelling, deployment of probe and alignment attached.

    6C958E75-0CB9-49CB-97B0-2673E6C0A2D6_1_201_a.jpeg

    https://youtu.be/kpVAuKwoTiQ

  • 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

    65
    Topics
    597
    Posts

    undefined

    @Inlinebrother printing and filament change is working. Struggling with the servo, sometimes it will not engage completely. Will try to provide 6V instead of 5V power this should result in ~500g more force. If you are still interested in this topic you can contact me.

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

    409
    Topics
    4.0k
    Posts

    Phaedruxundefined

    @apak said in Smart effector not remembering sensitivity:

    I just got a old smarteffector that seems to have this very same problem.

    No sensitivity store, and need to program it every power cicle.

    Is it there any instruction on how to flash fw to smarteffector? It´s a V2. So don´t know the best or latest fw to install

    Everything to know about the smart effector can be found here: https://docs.duet3d.com/en/Duet3D_hardware/Accessories/Smart_Effector

    If you're still stuck, please create a new thread with all the details.

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

    684
    Topics
    5.3k
    Posts

    undefined

    I found the reason for the problem. Perhaps you explain its nature. The steps motors of the axes A and B had 6 wires 4 of which were sweaty to the controller. After replacing the engines with 4 wired problems did not appear.

  • 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

    126
    Topics
    1.3k
    Posts

    undefined

    @chrishamm

    I understand the refresh - that was a secondary thing. I'm not too fussed, now that I know its not a bug / issue.
    Cosmetically - I think it would benefit from consistent language.

  • RepRapFirmware on other controllers

    30
    Topics
    321
    Posts

    undefined

    @dc42 said in Set Z height Max For clay Delta printer:

    @JetClay one option may be to use G30 S-1 to do manual probing without setting the Z height to zero. Then run this:

    G10 L2 Z{sensors.probes[0].lastStopHeight}

    This will set the Z offset of the workplace to that height. Or you could use:

    G10 L2 Z{move.axes[2].userPosition}

    since the current Z position will be the same. Or even:

    G10 L20 Z0

    You can include

    G10 L2 Z0

    in your homedelta.g file to reset the offset to zero when you home the printer again.

    Thank you very much for your response we finally made it work! we used this code

    ; SetZHeight.g - Manual Z height calibration & M665 H update
    M291 P"Ensure the nozzle is clean. Press OK to continue." R"Z-Height Calibration" S3

    G28 ; Home all axes completely before probing
    M665 ; Print current M665 values for reference

    ; Ensure previous height offsets are cleared
    G10 L2 Z0

    M291 P"Move the nozzle down until it just touches the bed. Press OK when done." R"Manual Adjustment" S3 S2

    G30 S-1 ; Perform manual probing without setting Z=0

    M291 P"Extracting new height offset..." R"Processing" S1

    ; Ensure latest calibration data is loaded before changing M665 H
    M501 ; Load saved config-override.g (M665 H value)

    ; Capture the last probe height and set Z offset
    G10 L2 Z{sensors.probes[0].lastStopHeight}

    ; Update M665 H dynamically based on last saved value
    M665 H{move.kinematics.homedHeight - sensors.probes[0].lastStopHeight}

    ; Save new M665 H for persistence
    M500 ; Save parameters to config-override.g

    M291 P"Calibration complete! The new Z height and M665 H value have been saved." R"Success" S1
    M501 ; override config file
    G28 ; Home axes

    Hope it works for maore people!

  • STM based control boards

    48
    Topics
    384
    Posts

    undefined

    @dc42 @gloomyandy @achrn

    found the issue the 8 pin connector was the issue thanks to all of you

  • LPC based control boards

    17
    Topics
    156
    Posts

    undefined

    @gloomyandy said in RepRap Firmware Issue in behavior:

    M98 P"config.g"

    Hi @gloomyandy I appreciate your help on this below the outcome of M98P "Config.g", I agree with you some information might be strange in my Config.g file like the S because I added it without exact knowledge of the functionality so I thought that might Improve the result. but i do not know the actual value I should add :).

    Actually this is an old project i never finish as not dedicated to however since i am working on again i would like to know how should i move on below is a picture of the machine as i was not able to upload video due to the size

    I uploaded while the machine in action however if you notice that the circle is not exactly circle it looks like defected circle you can tell however in the square it is more clearer

    9/26/2022, 12:21:35 AM M98 P"config.g"
    HTTP is enabled on port 80
    FTP is enabled on port 21
    TELNET is disabled
    Error: bad grid definition: Too many grid points; suggest increase spacing to 58.4mm
    9/26/2022, 12:17:55 AM M122
    === Diagnostics ===
    RepRapFirmware for LPC176x based Boards (biquskr_1.4) version 3.2_4 running on LPC176x at 100Mhz
    Used output buffers: 1 of 16 (11 max)
    === RTOS ===
    Static ram: 4956
    Dynamic Memory (RTOS Heap 5): 7896 free, 7856 never used
    Allocations: 178 Frees: 21
    Never used RAM 256, free system stack 14 words
    Tasks: NETWORK(ready,187) HEAT(blocked,243) MAIN(running,354) IDLE(ready,21)
    Owned mutexes: WiFi(NETWORK)
    === Platform ===
    Last reset 00:01:25 ago, cause: [software]
    Last software reset at 2022-09-26 00:16, reason: User, GCodes spinning, available RAM 256, slot 0
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0042a000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
    Error status: 0x00
    Aux0 errors 0,0,0
    Supply voltage: under voltage events: 0
    Driver 0: position 0, standstill, SG min/max 0/10, error r/w 0/1, ifcnt 73, cnt r/w 7165/15, timeout 0, failedOp 0xff
    Driver 1: position 0, standstill, SG min/max 0/0, error r/w 0/1, ifcnt 68, cnt r/w 7168/12, timeout 0, failedOp 0xff
    Driver 2: position 0, standstill, SG min/max 0/18, error r/w 0/1, ifcnt 73, cnt r/w 7165/15, timeout 0, failedOp 0xff
    Driver 3: position 0, standstill, SG min/max 0/0, error r/w 0/1, ifcnt 63, cnt r/w 7169/11, timeout 0, failedOp 0xff
    Driver 4: position 0
    Driver 5: position 0
    Driver 6: position 0
    Date/time: 2022-09-26 00:17:51
    Slowest loop: 20.93ms; fastest: 0.13ms
    Step timer: target 34955404 count 84948299 delta -49992896 late 0
    USBSerial connected 0
    ADC not ready 2 ADC error threshold 10 ADC Init 1
    Ints: 51516; Calls 51516; fast: 3uS; slow 20uS adj 0 bad 0 big delta 0
    PWM Channels
    Delta -822796941 Start -1 End -1
    === Storage ===
    Free file entries: 6
    SD card 0 detected
    SD card longest read time 2.3ms, write time 0.0ms, max retries 0
    === Move ===
    DMs created 40, maxWait 20302ms, bed compensation in use: none, comp offset 0.000
    === DDARing ===
    Scheduled moves 7, completed moves 7, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
    === Heat ===
    Bed heaters = 0, chamberHeaters = -1
    Heater 1 is on, I-accum = 0.0
    === GCodes ===
    Segments left: 0
    Movement lock held by null
    HTTP is idle in state(s) 0
    File is idle in state(s) 0
    USB is idle in state(s) 0
    Aux is idle in state(s) 0
    Trigger is idle in state(s) 0
    Queue is idle in state(s) 0
    Daemon is idle in state(s) 0
    Autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 42.51ms; fastest: 0.00ms
    Responder states: HTTP(0) HTTP(0)
    HTTP sessions: 1 of 2

    WiFi -
    Network state is active
    WiFi module is connected to access point
    Failed messages: pending 0, notready 0, noresp 0
    WiFi firmware version 1.25-01LE-D
    WiFi MAC address c0:56:27:45:b2:f9
    WiFi Vcc 3.37, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 35944
    WiFi IP address 192.168.1.134
    WiFi signal strength -68dBm, mode 802.11n, reconnections 0, sleep mode modem
    Clock register 00181001
    Socket states: 0 0
    Untitled.jpg20220926_230657.mp4

  • Other control boards that are not specifically LPC or STM based

    42
    Topics
    602
    Posts

    T3P3Tonyundefined

    @Rat-Rig-CS thanks for your response and for how this had been handled.

    From our side part of the issue was between how warranty issues are handled when a product is supplied from a reseller, vs a board supplied with a complete product (be it a kit or an assembled machine):

    For a reseller supplied product, referral to the forum is the correct procedure. For a product incorporated in kit or complete machine we expect the manufacturer to handle the warranty process (and communicate with us directly, if there is a fault with the board).

    The basic idea being a machine sold as a complete product, which the manufacturer has control over would not be expected to have configuration or wiring issues that we want to debug here on the forum before confirming a hardware fault.

    We will update our T&Cs to make this clearer.

  • Future Direction

    14
    Topics
    196
    Posts
    No new posts.

  • Categories for specific issues with Beta and Release Candidate (RC) versions of RRF 2 and RRF 3

    1.2k
    Topics
    15.1k
    Posts

    undefined

    Guys.. found the macro that cause the disconnects..
    Has nothing to do with the tool change macros, but with the mesh leveling macro.

    Found the problem, but I don't understand what is wrong with it. bed.g and mesh.g are unchanged for a while and they worked very well..

    This is bed.g and this complete without problems

    ; bed.g ; called to perform automatic bed calibration via G32 M106 S0 if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed G28 G30 P0 X5 Y6 Z-99999 G30 P1 X287 Y6 Z-99999 G30 P2 X287 Y278 Z-99999 G30 P3 X5 Y278 Z-99999 S2 G1 X{(310/2)-sensors.probes[0].offsets[0]} Y{(310/2)-sensors.probes[0].offsets[1]} F6000 G30

    And this is mesh.g that causes DWC to start looping:

    ; mesh.g ; called to perform automatic bed compensation via G29 var rmsMin = -0.08 var rmsMax = 0.08 var meanMin = -0.08 var meanMax = 0.08 var isOK = true M116 H0 S0.2 ; wait for bed temperature with a tolerance of 0.2 degC M106 P0 S0 ; turn fans off if active M80 ; override ATX thermostatic shutdown M561 ; clear any bed transform M290 S0 R0 ; reset babystepping G32 G29 S0 ; Probe the bed if move.compensation.meshDeviation.mean > var.meanMax && move.compensation.meshDeviation.deviation > var.rmsMax set var.isOK = false M291 P"Mean & RMS deviations too high" R"Mesh warning!" S1 T0 elif move.compensation.meshDeviation.mean < var.meanMin && move.compensation.meshDeviation.deviation < var.rmsMin set var.isOK = false M291 P"Mean & RMS deviations too low" R"Mesh warning" S1 T0 elif move.compensation.meshDeviation.mean > var.meanMax && move.compensation.meshDeviation.deviation < var.rmsMin set var.isOK = false M291 P"Mean deviation too high & RMS deviation too low" R"Mesh warning" S1 T0 elif move.compensation.meshDeviation.mean < var.meanMin && move.compensation.meshDeviation.deviation > var.rmsMax set var.isOK = false M291 P"Mean deviation too low & RMS deviation too high" R"Mesh warning" S1 T0 elif move.compensation.meshDeviation.deviation > var.rmsMax set var.isOK = false M291 P"RMS deviation too high" R"Mesh warning" S1 T0 elif move.compensation.meshDeviation.deviation < var.rmsMin set var.isOK = false M291 P"RMS deviation too low" R"Mesh warning" S1 T0 elif move.compensation.meshDeviation.mean > var.meanMax set var.isOK = false M291 P"Mean deviation too high" R"Mesh warning" S1 T0 elif move.compensation.meshDeviation.mean < var.meanMin set var.isOK = false M291 P"Mean deviation too low" R"Mesh warning" S1 T0 else set var.isOK = true M291 P"Auto calibration successful!" R"Mesh complete" S0 T4 G0 X0 Y0 F4800 if var.isOK = true M300 S2000 P500 G4 P500 M300 S1700 P500 else M300 S300 P1000

    G29 S0 works ok
    What's wrong with the mesh macro? I'm lost 🤤

  • Discuss and contribute to the Duet Software Framework

    129
    Topics
    1.1k
    Posts

    undefined

    @LindsayC

    And finally if you run this code where you just pass a string to the P parameter.

    var ind = 0 var driverAddress = "51.0" M569.1 P{var.driverAddress} T2 C1000 S200 R150 I50 D0.1 V500 A1 E4.0:2.0 D1;

    You get this error message:
    Error: in file macro line 3 column 27: M569: expected driver ID

    Which is different to the error message you get if the variable is obtained from the object model.

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

    403
    Topics
    3.2k
    Posts

    undefined

    @Triet I guess if one is using the feedforward in the way intended, the temperature shown is the target temperature. I have been playing with the parameters, trying to understand how they work. I am trying out a 0.25mm nozzle, which has an extrusion rate of about 8.8cumm/sec with 0.125mm layers at 140mm/sec, which is think corresponds to about 3.6mm/sec for 1.75 filament. A T parameter of 12 seems to give the expected increase of just greater than 40deg over the base temperature. I think there is a bit of under extrusion at this speed with the 0.25 nozzle, but checking that out. For my standard 0.4 cht nozzle, 0.2 layers give about 22cumm/sec at 140 mm/sec, that is about 9mm/sec filament. Using T5, this gives the expected increase of about 45deg above base temperature. I dont think the cht nozzle is underextruding under these conditions. I have just started using an S parameter of 1.0, and this seems to work fine with the 0.25 nozzle - not tried with the 0.4 nozzle yet. Tried increasing the A parameter to 50, and the feed forward stops working.
    I have been using M570 H1 P15 T45, and not been getting heater faults. The revo nozzle setup I am using has a low thermal mass, and seems to be controlled very well by the duet.

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

    944
    Topics
    7.4k
    Posts

    undefined

    @droftarts Thank you I will look into this GitHub link. Hopefully the feature is implemented soon. In the meantime, I will try to add the functionality so I can learn more about RepRap firmware.

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

    329
    Topics
    2.1k
    Posts

    chrishammundefined

    @pixelpieper I'm going to adjust the minimum of the temperature chart dynamically in the next build. It will be the lowest value of the configured temperature presets or heaters[].min.

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

    348
    Topics
    3.8k
    Posts

    droftartsundefined

    @fcwilt send an email to the email address @elmoret gave you, with the details he asked for, and he’ll send you a pre-paid shipping label.

    Ian

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

    Phaedruxundefined

    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.

Unless otherwise noted, all forum content is licensed under CC-BY-SA