Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.1k
    Topics
    86.3k
    Posts

    yoshimitsuspeedundefined

    @droftarts

    Haha I made the suggestion ages ago to adjust heat based on volumetric flow rate here and in Prusa Slicer forums and more people than not basically told me I was being stupid lol. I will check it out as that would be huge especially with filaments like TPU which I print with a lot.
    I think nonlinear extrusion is still valuable especially with TPU.
    I am currently running 3.5 RC2 but I have had frustrations with nonlinear extrusion for ages and several different versions.

  • Using Duet Controllers

    811
    Topics
    7.3k
    Posts

    tristanryerparkeundefined

    Hi All,
    I'm running a PNP-style machine with MB6HC(SBC Pi5), 5x 1HCL. During continuous operation I noticed some drift in the A-axis. The drift was large enough that when commanding the (rotational) A axis to a 0 position (which looks square to the gantry after a homing cycle), it looks visibly off by about 10 or 15 degrees.

    I was running some g-code which "unwraps" the A axis by calculating % 360 of the last position (I generate my code with python) and running a G92 A{remainder} to avoid a lengthy travel back to the normal range. I thought this might be causing the cumulative positional drift, and disabled it which seemed to fix the issue. But I was frustrated that what seemed like an obvious solution to the lengthy unwind wasn't working, so I ran some tests.

    How I'm testing for deviation:

    G91 G53 G1 H4 A-360 F3000 G53 G1 A2 G53 G1 H4 A-4 F100 G90 G4 S0.5 ; wait for motion to complete and allow OM to settle (nessecary? or maybe the issue?) echo {"deviation from home position: "^move.axes[3].machinePosition + 142.5} ; 142.5 is the offset I specify in homea.g

    The deviation tests involve running a homing-style motion but not setting any position, and then observing how far the current position is from the supposed home position by polling the OM. To me this seemed a viable method of recording the deviation, and I hope it does to everyone else as well. I've used similar tests in the past to verify the position of open loop systems during operation.

    The two test files which simulate an identical set of motions that my machine currently makes during normal operation, one with the G92 unwrap and the other without:

    with_python_mod.g with_no_wrap.g

    My testing script:

    echo "homing the A axis to reset" G28 A echo "initial tolerance score" M98 P"/macros/test_a_issues/print_deviation.g" ;default M203 A25000 M201 A2000 ;slow 1 ;M203 A10000 M201 A500 while iterations < 20 echo "iteration ", iterations + 1 ;M98 P"/macros/test_a_issues/with_python_mod.g" M98 P"/macros/test_a_issues/with_no_wrap.g" M98 P"/macros/test_a_issues/print_deviation.g"

    This allowed me to observe the deviation over time as the problematic macro(s) were repeatedly run, and the results were quite worrisome. Graphing my console output csv from multiple runs produced this:
    newplot.png
    I tried the same motion macros with several different configurations, open loop mode, closed loop mode, assisted, slow accel and feedrate etc. Uncommented lines in my testing script and homing files should show how I produced the varying tests, and attached are my testing_x.g and print_deviation_x.g files that I used as a "control".

    A axis runs the following hardware:

    1HCL configured as shown in config.g and homea.g This Closed Loop Stepper This geared stage 1:10 ratio PM-R45 NPN Optical endstop on the output face of the stage

    X axis uses a 1HCL, Nema23 motor and a 40T GT2 Pulley with 9mm Gates belt on a high quality linear rail.

    The accumulation I observed with the G92 wrapping was apparent, but shockingly, its omission showed a serious drift moving in the opposite direction. This led me to think that this was a hardware issue, so I added tests with my simple belt driven (direct drive) X axis as a control. This showed a continual deviation increase of 0.5-1mm across the standard 20 iterations with the same file, despite the mode of operation.

    So I have the following set of questions to ask on the forum:

    Is this a viable way to determine the deviation, and if not why? Do I need to give the object model more time to sync up before I make the comparison? If that is the case why are upward/downward trends visible? Is the issue related to the high speed at which I am running the A axis motor shaft, and why did a reduction of speed and acceleration not solve the cumulative error issue? Due to the 10x gear reduction of my A axis, could I be running into floating point errors for the shaft position/micro-step calculation? Maybe some tests with low micro stepping could answer this. On the X axis control, what other than a slipping belt pulley could cause the visible increase in X error.

    Attached is my m122.txt M122 report after a single run of the with_python_mod.g macro. No blazing issues stand out to me from the report.

    I'm happy to run additional tests and provide more information to diagnose the issue.

    Cheers and hoping to figure this out,
    T

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

    8.3k
    Topics
    74.9k
    Posts

    mike_bundefined

    @dc42 thank you so much for all your debugging suggestions. Every time I run the following command:

    M569.7 P40.0 C"40.out6"

    I'm presented with this error:

    9/7/2024, 3:37:01 PM M569.7 P40.0 C"40.out6" Error: M569.7:

    I do not get this error message when running the equivalent command on the main board. Because of this, I just assumed the brake wasn't functioning on the expansion board. For context, I’m using two Mini5+ boards - the first as the main board and the second as the expansion board with a CAN address of 40.

    However, the good news is that, despite the error showing up every time, the brake actually works! I tested it using a multimeter on 40.out6, and running M17 disengages the brake (i.e., the voltage across 40.out6 reads ~24V with current ~0.2A), and while running M18 engages the brake (voltage across 40.out6 drops to ~0V).

    In conclusion, seems like the only bug here is the error message appearing when running the command.

    Now that the brake is working, the erroneous error message isn’t much of a concern for me. However, please let me know if there’s anything you’d like me to test - I'd be more than happy to assist in any way I can. For example, if you think it’s helpful, I could try installing 3.6.0-alpha.5 and see how it performs.

    EDIT: apologies, forgot to answer one of your questions: the response I get after sending M569.7 P40.0 after sending he original command is as follows:

    9/7/2024, 3:57:07 PM M569.7 P40.0 Driver 40.0 uses brake port 40.(out6,laser,vfd)

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

    536
    Topics
    4.8k
    Posts

    timschneiderundefined

    @Kittifix you are maybe able to use it, but RRF is able to create a spindle with an PWM output for the speed control.

    https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m950-create-heater-fan-spindle-led-strip-or-gpioservo-pin

    If you use a PWM to Freqency Converter PCB you will maybe able to use the pulse input.

  • Prototype hardware issues.

    16
    Topics
    642
    Posts

    zecretonundefined

    @dc42 M17 and M18 don't change anything, the rotor stays locked even with the ena disconnected

  • Discuss Duet on laser cutters and engravers.

    177
    Topics
    1.5k
    Posts

    FHesseundefined

    @dc42 Is there already a solution to the problem?

  • Ask questions about installing the firmwares here

    2.1k
    Topics
    23.1k
    Posts

    Phaedruxundefined

    Perhaps @chrishamm can confirm if the pi imager user setup should be working?

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

    droftartsundefined

    @SanderLPFRG what firmware version are you running? Please send M122 and post the results. Also post your config.g, and the response to M669.

    Ian

  • Discuss using conditionals, loops and variables in gcode

    748
    Topics
    5.3k
    Posts

    crpalmerundefined

    @dc42 sbc for both machines.

  • Ask questions about the official web interface here

    1.5k
    Topics
    12.7k
    Posts

    Sindariusundefined

    @zBeeble Hello, I have a fix that I need to get put into place in DWC that will address this issue.

  • 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

    oliofundefined

    @dwak you may still want to peruse the documentation on metacommands so you get an idea how to enable your own codes with parameters

    https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands

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

    405
    Topics
    4.0k
    Posts

    Crosswireundefined

    @Phaedrux
    The documentation of the Smart Effector says:
    The version 2 and later Smart Effectors perform an additional self-test at power up to check that the strain gauge output is within the expected range. This test may fail during the first few seconds after power up as the voltages settle, so it is repeated until it passes. Therefore, if your sensor flashes 6 or 7 times once or twice before it flashes twice, this is normal. However, if it continues to flash 6 or more times, the sensor is faulty:

    7 flashes - strain gauge output out of tolerance (too high)

    It is an old sensor, I bought it with a second hand non working delta printer. Don't know its life history or age.

    I measured the voltage drop across each resistor and found one that had much more across it than all the others. When I tried to redo the solder joints the resistor split in two parts. Replaced with a new smaller (1206) 100 Ohm resistor. This will not be strain sensitive. Replacing another resistor in the same way.

    The sensor works now, probably with reduced sensitivity, Flashes twice at startup.

    I have no photos since I didn't know about the crack until I resoldered the resistor.
    The crack was not visible under amagnifying glass.

    If it happens again I think I will try to glue six real strain sensors to the board as a better fix.

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

    199
    Topics
    2.1k
    Posts

    Jman3undefined

    Sorry for the late update I ran into some other issues I needed to take care of.

    So it looks like I got this working after I fixed a few issues. I managed to print a temp tower without issue, maybe I'll have problems in the future with other prints.

    Installed a mount close by the extruder (around 1" of distance between the sprite pro extruder Removed my filament-error.g (it was trying to pause then run filament-error.g) Used the BTT recomended g-code but adjusted E value to 22 Changed my retraction speed to 60mm/s

    Here is the g-code I'm using

    ; Filament Monitor (Filament Runout Sensor, Big Tree Tech - Smart Filament Sensor V2) M591 D0 P7 C"io0.in" L2.88 R75:125 S2 E22

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

    116
    Topics
    1.2k
    Posts

    stuartofmtundefined

    @chrishamm

    I took the liberty of adding some additional checks / logging to build-plugin.js. Warns if the plugin src/index.js file is missing. Hopefully helpful:

    build-plugin.js

  • RepRapFirmware on other controllers

    29
    Topics
    261
    Posts

  • 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

    edspedundefined

    Will try the M400 commands and if they don't help, I'll disable IS at start of tool change and re-enable it after tool is picked up.

    Thanks for the assistance

  • Discuss and contribute to the Duet Software Framework

    118
    Topics
    978
    Posts

    curieosundefined

    I updated the packages via apt this morning on a machine in SBC mode, and after restarting the Pi I'm getting this error:
    IMG_20240906_093931.jpg
    The setup is two 6XDs and two 1LCs. The Pi is a Pi 5 running the bookworm image from April 19th. Fully rebooting the machine (cutting power) does not work.

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

    391
    Topics
    3.1k
    Posts

    dc42undefined

    @NineMile please create a feature request for this on the Github Issues page of the RepRapFirmware project.

  • 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

    moth4017undefined

    @gloomyandy i did look , great 🙂

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

    344
    Topics
    3.8k
    Posts

    infiniteloopundefined

    @vbtalent2 The gaps between adjacent seams look frightening. Maybe you can get rid of them following @mikeabuilder’s advice - but I’m puzzled by the fact that these gaps just begin to appear after about 10 perfectly looking rounds. From your videos, I get no clue: the nozzle deposits the first layer pretty well.

    I can imagine two possible suspects:

    Mechanical issues. I've seen inappropriately adjusted V rollers to generate these gaps. However, as the first few rounds look perfect, probability of this to be the cause is low.

    Under extrusion due to some clogging which develops over time. It is often caused by heat creep, i.e. the temperature of the heater block gradually overcomes the heatbreak up into the cold end (of your hotend). In most cases, this indicates insufficient cooling by the tool fan or a blocked air flow. Can you provide an image of your print head?

    The blobs should be a minor problem - they didn’t appear with the gray filament you used before, so I think you you just have to fine-tune nozzle temperature and maybe pressure advance for the black filament (to begin with, I would not enable PA at this stage).

    As a final note, I'd like to add that you got to manage adjustment of the nozzle height very well. It's a long time since I saw such a perfect first layer seam as demonstrated in your videos. On glass, this is a rare event. Congratulations.

  • 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