Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.1k
    Topics
    86.5k
    Posts

    SonnyD1undefined

    @droftarts That is outstanding. I'm glad I could help. I'm the one that set this IDEX up in the beginning but I couldn't remember how. All it took was a clogged nozzle resulting in a nozzle change to throw all my work out of whack. I couldn't remember how I did it in the first place thus this post. As usual, you've managed to rescue me. I have a much better understanding of the offset and will hopefully retain it better. Thank you!

  • Using Duet Controllers

    811
    Topics
    7.3k
    Posts

    tristanryerparkeundefined

    Running 3.6 beta5+1 and the normal test_A_wrap_closed.g, test_A_nowrap_closed.g I got these results:
    36.png
    I'm now just trying to find a middle ground speed/acceleration combo where the missed steps do not occur, yet isn't prohibitively slow. @dc42 Any ideas on a semi-sealed, magnet-style closed loop motor? Maybe some existing product I could retrofit the duet3d encoder to?

    Best,
    T

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

    8.3k
    Topics
    75.1k
    Posts

    misterjtcundefined

    I am having an issue with my Duet 3 Mini 5+ and RaspberryPi (SBC).

    The issue: When the main board is powered off for some amount of time and then powered back on, the sbc (and duet web control) aren't able to remake the connection.

    To set up the Raspberry Pi, I followed the guide outlined here (it is not setup using the offical DuetPi image): https://docs.duet3d.com/User_manual/Machine_configuration/DSF_Other

    Steps to recreate the issue:

    Power off the Duet main board for X minutes, it appears to only lose the connection permenantly when its shut off for a while . Power on the Duet main board The Duet Web Control interface is unable to reconnect to the main board. This issue is present on both the SBC touch screen and the web interface on any computer.

    I am wondering if there is some timeout or specified number of reconnect attempts that needs to be adjusted?

    Like I mentioned, if the main board is powered down for only a few minutes, when the power is restored, the connection between the SBC and duet main board is automatically reestablished. It seems like the mainboard board needs to be powered down for an extended period of time for the issue to present itself.

    Any help is appreciated. Thanks in advance!

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

    538
    Topics
    4.8k
    Posts

    dc42undefined

    @oliof no you won't, because the only way to tell if a Modbus device is responding is to send a command to write or read a register and check whether the M260.1 or M261.1 command returns success - and you can do that yourself.

    When we start using Modbus to implement critical functions without using M260.1 or M261.1 such as changing spindle speed, then we may introduce events to handle failure of those operations.

  • Prototype hardware issues.

    16
    Topics
    645
    Posts

    zecretonundefined

    @dc42 do you think there is a person i could pay to come see it irl and fix the problem?

  • Discuss Duet on laser cutters and engravers.

    177
    Topics
    1.5k
    Posts

    dc42undefined

    @FHesse I think the simplest solution for now is to set up a macro that does this:

    use M451 to switch out of laser mode to free up the laser control pin use M950 to configure the laser pin as GpOut pin use M42 to set the desired PWM on that pin use M291 to prompt the user to press OK when focusing is complete use M42 to turn off the laser use M950 to deconfigure the GpOut port use M452 to reselect laser mode.

  • Ask questions about installing the firmwares here

    2.1k
    Topics
    23.1k
    Posts

    droftartsundefined

    @Alijambo73 Please post your homeall.g, homex.g, homey.g and homez.g as they currently stand. If you have any other homing macros, post them too.

    Ian

  • Speed, acceleration, microstepping etc - post your experiences of and questions about how to get the best out of the Duet WiFi here.

    5.2k
    Topics
    54.1k
    Posts

    Ralmsundefined

    Hi everyone,

    Raising the issue which I believe to be a bug here instead of GitHub, as requested by the instructions.

    In summary, I'm trying to use G30 S0 to home my Z axis and I'm running into inconsistent behavior.

    Calling Home Z on DWC (which calls G28 Z and consequently homez.g), results in:G28 Z Error: in file macro line 5: G1: insufficient axes homed However, calling the exact same Gcode, in the same conditions directly from Console, works and performs the homing of the Z axis.

    Here is my homez.g:

    var bedCenterX = (move.axes[0].max - move.axes[0].min)/2 var bedCenterY = (move.axes[1].max - move.axes[1].min)/2 M290 R0 S0 ; Reset baby stepping G1 X{var.bedCenterX} Y{var.bedCenterY} F5000 M400 ; added M400 as a troubleshooting step didn't make a difference G30 S0 X{var.bedCenterX} Y{var.bedCenterY} Z-9999 ; I've also tried doing just G30 S0, same result. M400 G1 Z20 F6000 ; Lift Z after homing. I've tested removing this, made no difference

    The steps to reproduce the issue are:

    Home X, called on DWC and wait it to finish Home Y, called on DWC and wait it to finish Home Z, called on DWC, fails with Insufficient axes homed error mentioned above. Go to the console and execute G30 S0, works and homes Z, however, it still shows an error in the console:G30 S0 Error: in file macro line 5: insufficient axes homed After this, all 3 axis are considered homed (and with correct coordinates).

    From the documentation, it says, that G30 without P, can be used to home the Z axis and the fact that it works outside of homez.g leaves me to believe to be a bug.

    Hardware:

    Duet 3 MB6HC running 3.5.2 Duet 3 Tool1LC running 3.5.2 DWC version 3.5.2

    Please let me know if I can raise the issue in GitHub or if I'm missing something.

    Also, if this is confirmed to be a bug, a workaround to unblock me would be appreciated, as I'm using the probe as a Z limit switch to home, no other option.
    Thank you.

  • Discuss using conditionals, loops and variables in gcode

    750
    Topics
    5.4k
    Posts

    dc42undefined

    @DonStauffer is this still an issue in RRF 3.5.3-rc.1 ?

  • Ask questions about the official web interface here

    1.5k
    Topics
    12.7k
    Posts

    chrishammundefined

    @andreasMch In standalone mode you must query rr_reply as well if you need the G-code response. To know when a new response is available, you should monitor seqs from rr_model as documented in the documentation article.

  • Feedback for docs.duet3d.com

    101
    Topics
    487
    Posts

    Maestroundefined

    @T3P3Tony I would suggest either removing or updating the 130mm dimension up the left side as well, as this dimension is in fact 129.5.

    Splitting the proverbial hair, I know!

  • 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
    786
    Topics
    9.5k
    Posts

    Dad003undefined

    i Went with the LDO , super power HT for my build , they have nice spec for a quick machine and 180C temp max and since they will sit outside the heated chamber we should have a good margin. pick up the 55mm shaft version as well so i could add an extra bearing to support the end .

    IMG_20240909_215057957.jpg IMG_20240909_224905446.jpg IMG_20240909_224944366.jpg

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

    111
    Topics
    770
    Posts

    Selmanundefined

    @droftarts Thanks a lot for the help ! Fore sure it was very helpful ! I was stuck in the situation where my PC (windows) could not detect the presence of the DUET, and so i used Type-C/Type-C cable, which turned out to be critically important. Many thanks once again !

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

    DueUI
    174
    Topics
    2.5k
    Posts

    Theboz1419undefined

    Thank you, this looks promising

  • Accessories and Add-ons

    65
    Topics
    592
    Posts

    Muhammedundefined

    @droftarts Thanks a lot, I had this in mind but wanted to see if there are other way to go around this. Using any output on the 50 pin expansion header would be fine, right?

  • Forum for discussing the Duet3d Filament Monitor

    392
    Topics
    3.9k
    Posts

    adambxundefined

    @Phaedrux will do 👍

  • Discuss the smart PCB effector for delta printers here.

    406
    Topics
    4.0k
    Posts

    dc42undefined

    @oarjjj the bug in 3.6 that I mentioned is now fixed. I expect to release 3.6.0-beta.1 this week.

  • No decsciption available

    231
    Topics
    1.9k
    Posts

    br7408undefined

    @dc42

    Excellent. I actually did more digging around last night and found one of your posts in another forum from many years ago recommending this. I will try it and report back. Your sensor is absolutely the best one out there in my opinion, so I will be happy to get it working on this machine.

    UPDATE: That did the trick David. It is now booting in digital mode. Thank you.

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

    672
    Topics
    5.3k
    Posts

    tecnoundefined

    @droftarts
    Thank you Ian

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

    200
    Topics
    2.2k
    Posts

    dc42undefined

    @KnyteTech looks good, but I suggest you use P1 instead of S1 in the M950 command.

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

    117
    Topics
    1.2k
    Posts

    cosmowaveundefined

    I think, thats one for @MintyTrebor
    I've designed a chart in Btn_Cmd which displays different values of my water cooling system.
    I found, that a scale setting of a value is not displayed correctly.

    The y-axle of my chart is set to show the water-temp in a range 0-50. All other parameters are scaled in the settings to suit in this range.
    One of the other parameters is the pump-PWM. To suit in the chart, it is multiplied by 10. But it isn't correctly displayed in the chart!

    On the first picture, you see the pump-PWM in decimals and in the chart:

    pump-PWM = 0.92 the grey graph in the chart should be at 9.2 (0.92 x 10) in the chart. But it is a bit higher than 5
    a3130cf9-4102-4124-b283-aa9c22ce06ca-Btn_Cmd1.png

    The second picture a bit later, same "problem"
    7d050ee8-ad3c-483e-bc77-638b0f809342-Btn_Cmd2.png

    All other graphs are scaled correctly. Perhaps there is something wrong with PWM values? Or the "restriction" in my config.g for that pump-PWM can also be the problem.
    For better control of the pump, i've limited the min and max speed with the L and X parameter of the M106 command:

    M106 P3 C"WaterPump" S0 L0.3 X0.6 B2 H-1 R1

    It could be, that the graph is showing the "real" PWM value. Not the "restricted" one?

  • RepRapFirmware on other controllers

    29
    Topics
    264
    Posts

    Inlinebrotherundefined

    Next update:

    By using the thread above now I see the bed temperature via a thermistor OK
    used first two cables out of 4 (white and green in my case)

    Config from this thread helped me to turn on thermocouples (though i had to downgrade them to thermocouple-max31855 from thermocouple-max31856) OK

    board fan working OK

    extruder heaters are working OK

    bed heater is not working, I'll check what's wrong next time TODO

    Also I need to close the printer TODO

    LEDs are not working and I don't think I am going to fix that in the nearest future NOT_HAPPENING
    I might replace the screen with the one from FYSETC TODO

    Fix config issues that i can come across TODO

    And finally print something TODO

  • STM based control boards

    41
    Topics
    326
    Posts

    gloomyandyundefined

    @wanwan These are my settings:

    ; Configuration file for Duet WiFi / Ethernet running RRF3 on E3D Tool Changer ; executed by the firmware on start-up ; modified by JSA 01-10-21 ; Gloomyandy version for RRF on Fly super8pro ; General preferences M111 S0 ; Debugging off G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ;M555 P2 ; Set firmware compatibility to look like Marlin M669 K1 ; Select CoreXY mode ; Network M550 P"ToolChanger" ; Set machine name M552 S1 ; Enable Networking M586 P0 S1 ; Enable HTTP M586 P1 S0 ; Disable FTP M586 P2 S0 ; Disable Telnet ; We need a delay for CAN boards to connect May as well do something usefull! ; pebble wiper m950 s1 C"pwm1" Q333 M280 P1 S140 G4 S1 M280 P1 S10 G4 S1 G4 S5 ; Neopixels M950 E0 C"20.rgbled" M150 R255 B255 U255 S3 M150 R0 B0 U0 S2 M150 R255 B165 U 0 S1 ; Neopixels M150 R255 B255 U255 S3 M150 R0 B0 U0 S2 M150 R255 B165 U 0 S1 ; Drive direction M569 P0 S0 ; Drive 0 B M569 P1 S0 ; Drive 1 A M569 P2 S1 ; Drive 2 Z M569 P3 S0 ; Drive 3 E0 ;M569 P4 S0 ; Drive 4 E1 M569 P124.0 S1 ; Toolboard ;M569 P5 S1 ; Drive 5 COUPLER M569 P20.0 S1 ; Drive 5 COUPLER M569 P22.0 S1 ; Toolboard M569 P23.0 S1 ; Toolboard M569 P6 S0 D3 V40 ; Drive 6 Pebble Wiper M569 P7 S0 ; Drive 7 UNUSED ;M584 X1 Y0 Z2 C5 A6 E3:4:22.0:23.0 ; Apply custom drive mapping M584 X1 Y0 Z2 C20.0 A6 E3:124.0:22.0:23.0 ; Apply custom drive mapping M98 P"SetSystemLimits.g" ;M208 X-35:328.5 Y-49:243 Z0:280 C-45:360 ; Set axis maxima & minima ;M208 X-35:314.9 Y-49:156 Z0:280 C0:500 ; Set axis maxima & minima M208 A0:71 M350 E16:16:16:16 I1 ; Configure microstepping with interpolation M350 A16 I1 ; Configure microstepping with interpolation M350 C16 I1 ; Configure microstepping with interpolation M350 X16 Y16 Z16 I1 ; Configure microstepping with interpolation M92 X100 Y100 Z800 C200 A360 E 397: 397: 397: 397 ; Set steps per mm assuming x16 microstepping ;M566 X800 Y800 Z50 C2 E800:800:800:800 ; Set maximum instantaneous speed changes (mm/min) ;M566 X750 Y750 Z50 C2 A360 E200:200:200:200 ; Set maximum instantaneous speed changes (mm/min) M566 X500 Y500 Z50 C2 A360 E500:500:500:500 ; Set maximum instantaneous speed changes (mm/min) M203 X35000 Y35000 Z1200 C5000 A2000 E5000:5000:5000:5000 ; Set maximum speeds (mm/min) ;M201 X6000 Y6000 Z400 C500 E2500:2500:2500:2500 ; Set accelerations (mm/s^2) ;M201 X2000 Y2000 Z400 C500 A500 E2500:2500:2500:2500 ; Set accelerations (mm/s^2) M201 X8000 Y8000 Z400 C500 A500 E2500:2500:2500:2500 ; Set accelerations (mm/s^2) M906 X1800 Y1800 Z1330 I25 ; Idle motion motors to 25% M906 E1000:1000:1000:1000 C500 I10 ; Idle extruder motors to 10% M906 A500 I30 ; Idle pebble wiper platform to 30% ; Endstops M574 X1 Y1 S3 ; Set X / Y endstop stall detection M574 C0 Z0 ; No C Z endstop M574 A2 S3 ; Tool detection switch M950 J0 C"^20.io2.in" ; Z probe M558 P8 C"^20.io1.in" H2 F500:100 I0 S0.005 A10 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 Y0:200 S20 ; Define mesh grid M308 A"SZP dummy" S13 Y"thermistor" P"20.temp1" M308 A"SZP coil" S12 Y"thermistor" P"20.temp0" ;Stall Detection M915 X Y S2 F0 H400 R0 ; X / Y Axes M915 A S-35 F0 H200 R0 ; Pebble Wiper ; Heaters M308 S0 P"adc0" Y"thermistor" A"Bed" T100000 B4138 C0 ; Set thermistor M950 H0 C"bedout" T0 Q10 ; Bed heater M143 H0 S225 ; Set temperature limit for heater 0 to 225C M140 H0 ; Bed heater is heater 0 ;M307 H0 B0 R1.276 C420.3 D5.16 S1.00 V24.2 M307 H0 R1.307 K0.285:0.000 D5.84 E1.35 S1.00 B0 M308 S1 P"adc1" Y"thermistor" A"T0" T100000 B4725 C7.06e-8 ; Set thermistor M950 H1 C"heat0" T1 ; Extruder 0 heater M143 H1 S305 ; Set temperature limit for heater 1 to 300C ;M307 H1 R1.843 K0.323:0.207 D5.86 E1.35 S1.00 B0 V24.2 M307 H1 R1.656 K0.313:0.214 D6.33 E1.35 S1.00 B0 V23.8 ;M308 S2 P"adc2" Y"thermistor" A"T1" T100000 B4725 C7.06e-8 ; Set thermistor ;M308 S2 P"124.temp0" Y"thermistor" A"T1" T100000 B4725 C7.06e-8 R1000 h-84 l100 ; calibrated with jumper set for 1K M308 S2 P"124.temp0" Y"thermistor" A"T1" T100000 B4725 C7.06e-8 ;M950 H2 C"heat1" T2 ; Extruder 0 heater M950 H2 C"124.out0" T2 ; Extruder 0 heater M143 H2 S305 ; Set temperature limit for heater 2 to 300C ;M307 H2 R1.742 K0.343:0.155 D7.12 E1.35 S1.00 B0 V24.2 ;M307 H2 R1.750 K0.322:0.203 D7.58 E1.35 S1.00 B0 V24.2 M307 H2 R3.254 K0.383:0.248 D2.13 E1.35 S1.00 B0 V23.3 ; Revo M308 S3 P"22.temp0" Y"thermistor" A"T2" T100000 B4725 C7.06e-8 ; Set thermistor M950 H3 C"22.out0" T3 ; Extruder 0 heater M143 H3 S305 ; Set temperature limit for heater 3 to 300C ;M307 H3 R1.904 K0.321:0.152 D4.78 E1.35 S1.00 B0 V23.8 M307 H3 R3.971 K0.441:0.227 D2.01 E1.35 S1.00 B0 V23.3 ; Revo M308 S4 P"23.temp0" Y"thermistor" A"T3" T100000 B4725 C7.06e-8 ; Set thermistor M950 H4 C"23.out0" T4 ; Extruder 0 heater M143 H4 S305 ; Set temperature limit for heater 4 to 300C M307 H4 R1.895 K0.311:0.113 D6.74 E1.35 S1.00 B0 V23.8 ; 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"fan0" M950 F2 C"fan1" ;M950 F3 C"fan2" M950 F3 C"124.out2" ;M950 F4 C"fan3" M950 F4 C"124.out1" M950 F5 C"22.out2" M950 F6 C"22.out1" M950 F7 C"23.out2" M950 F8 C"23.out1" 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 ; Electronics temperature and cooling M308 S10 P"D.0" Y"dht22" A"Electronics" M308 S11 P"S10.1" Y"dhthumidity" A"Elec Hum[%]" M950 F9 C"fan4" M106 P9 S255 H10 T40 M593 p"mzv" F33 S0.1 ; cancel ringing at 33Hz from I/S plugin M376 H10 ; bed compensation taper ;tool offsets G10 P0 X20.6 Y43.55 Z-5.51 ; T0 G10 P1 X20.52 Y43.74 Z-8.16 ; T1 Revo G10 P2 X19.63 Y43.39 Z-8.50 ; T2 Revo G10 P3 X20.47 Y43.68 Z-5.80 ; T3 M572 D0 S0.04 ; pressure advance T0 M572 D1 S0.04 ; pressure advance T1 M572 D2 S0.04 ; pressure advance T2 M572 D3 S0.04 ; pressure advance T3 M575 P1 S1 B57600 ; Enable LCD G29 S2 ; disable mesh T-1 ; deselect tools M280 P1 S140 M501 ; load config-override.g M150 R0 B255 U255 S1

    I don't see anything significantly different, though it is interesting that you have a different steps/mm than I do. I assume that was down to some change in e3d pully setup? My settings seem to match those from the e3d repo.

    As to noise levels. not sure if mine is much quieter than yours or not. The motors seem to make about the same amount of noise as my fans, but I am running 4020 blower fans on my tools which are no exactly silent.

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

    dc42undefined

    @MaxGyver is it repeatable? If so then please post your config.g file and the GCode file.

  • Discuss and contribute to the Duet Software Framework

    119
    Topics
    994
    Posts

    Arplyuundefined

    @chrishamm thanks! Now everything works fine!

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

    391
    Topics
    3.1k
    Posts

    dc42undefined

    @blair yes this new functionality applies to axes driven by expansion motors too in RRF 3.6.

  • Prototype hardware issues.

    46
    Topics
    659
    Posts

    Exerqtorundefined

    @dc42 Sounds promising! ☺️

    Well that plain sucks, esp. after putting in the legwork! Hope you find a good substitute sooner rather than later! PD is getting a little but long in the tooth at this point.

  • 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!)

    125
    Topics
    1.2k
    Posts

    0nn0undefined

    I'm still curious if there is any chance of this happening.

    If no official release from Duet is forthcoming, is there anyone in the community who can help me create this? I'm willing to do the design work, but I need guidance on how to proceed, as I have no experience with designing electronics.

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

    935
    Topics
    7.3k
    Posts

    DonStaufferundefined

    @dc42 The Adafruit documentation is ambiguous because it's internally contradictory by one byte. So I don't know.

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

    325
    Topics
    2.1k
    Posts

    droftartsundefined

    @NineMile I just tried this with DWC/RRF 3.5.2, toggled the 'Do not close error message automatically' to off, then provoked an error that displayed a red box. Like when a blue or green message box pops up, the red box had a white progress bar at the top of it, and disappeared once that completed. Also tried changing the notification period, and that worked too.

    I've noticed a couple of people have had problems with their DWC settings. Refreshing these seems to resolve some issues. Whether this is because the format of the dwc-settings.json has changed over time, or the file has become corrupt and not writeable, I'm not sure. Try renaming sys/dwc-settings.json to something different (eg .old on the end), and refresh the browser. Edit something, eg set 'Do not close error message automatically' to off, to create a new dwc-settings.json, and see if that resolves the problem.

    Ian

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

    345
    Topics
    3.8k
    Posts

    mikeabuilderundefined

    Great progress. You are nearly to the realm of fine tuning. I have a few specific suggestion, but they do not address all your questions. Specifically, I still have a similar blob on layer changes and I'll be watching fro someone to suggest something that helps me too.

    First Layer - In the initial photos, it looks pretty good. The top surface looks flat completely filled. The last photos of the more details part do look pretty bad. My first impression is that there may be a combination of too close to the bed (I know, your fixed that!), too much extrusion, and not sticking well to the glass plate. You may also have the hot end temperature too high. In my experience, I usually run the hot end just a few degrees above the low temperature rating of the filament.

    Second layer - In picture 5, the second layer looks like it has ridging between the lines. This means excess plastic is being pushed around by the nozzle. If the layers below don;t have excess plastic (and they look good in this picture), I would suspect your extrusion rate is too high. You can reduce it in the web interface while printing, change the extruder steps per mm in your config.g, or (probably) make a setting change in your slicer. If you consistently change it in the printer interface or in the slicer, and with different reels of filament, you should probably adjust the steps per mm in config.g. I think it's best to tweak the extrudion % while looking at the second or third layer and not the first layer because the first layer can be affected by the z-offset. Once the higher layers look great, use baby steps to adjust the offset so the first layer looks great too.

    Picture 6 - This looks to me like a classic example of a need for PA adjustment. PA (Pressure Advance) reduces the extrusion rate before the end of a line to compensate for oozing caused by pressure built up between the extruder motor and the hot end. You can adjust this live as your print builds up using M572 (see https://docs.duet3d.com/en/User_manual/Reference/Gcodes) . You can also probably do some clever stuff in the slicer to have it change the PA every 20 layers so you don't need to sit and watch it.

    Blobbies and observations on the last photo. - There is some darkened filament stuck to the side of the part. In my experience, this is plastic that's been clinging to the nozzle and burning, then finally getting pulled off. The causes is often stringing that gets picked up when the nozzle runs past it, or anything else sticking up - like those blobs at the layer change, or the ridges from too much extrusion. And one you get some plastic built up on the nozzle, it becomes a stick place to grab more. I also notice that the blue boot looks like it might be dragging on the plastic surface and this could be sweeping up more crud to melt on the nozzle. I'd get that boot pushed on better (you might need to make the hole around the nozzle bigger). And I'd also look at the nozzle after every print and clean off any excess plastic you see while it's still hot. And also take the boot off occasionally and clean off the bottom of the hot end. I like these brushes because they are cheap and there's a box full ( https://www.amazon.com/Pack-Brass-Brush-Tooth-Brushes/dp/B07FN6K9J9). I keep some long and trim the bristles on some shorter with scissors. I like brass better than stainless because it's less likely to mar the hot end or nozzle. And don't let plastic build up on the brush or you'll be brushing on as much as you're brushing off.

    Lastly - sorry this is so long. I like to use PrusaSlicer to get an idea for values of settings. I'll download the prusa config for a MK3.5 printer and see what it would use for all the settings. If mine are way off from that, I try to find a good reason, or test the Prusa value.

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

    100
    Topics
    921
    Posts

    dc42undefined

    @baird1fa for smoothly accelerating or decelerating motion the time t of the nth step pulse measured from the start of the move is given by this formula:

    t = t0 +/- sqrt(q + p * n)

    where p = 2/a, q = t0^2

    where t0 = -u/a, a is the acceleration and u is the initial speed.

  • 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

    159
    Topics
    944
    Posts

    Phaedruxundefined

    @chris-costa said in Duet 2 WiFi Warranty Claim:

    Was that a warranty replacement board?

    No

    Where and when was the replacement board purchased?

    Have you replaced the motor for the driver that has been giving the issue?

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