Categories

  • Discuss setting up and using the DuetWifi and compatible hardware

    9.0k
    Topics
    86.0k
    Posts

    westechundefined

    @MJLew Thanks, I remember this being solved a long time ago. Your suggestion is familiar. I just thought I might look at old non retracting gcode I've printed.

  • Using Duet Controllers

    806
    Topics
    7.3k
    Posts

    Kiwi 0undefined

    @droftarts
    Thanks for the hint with the H3
    It was in the toolchange macro and probably a heatertuning with a M500 at the end brought it do the override...

    Thanks a lot!

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

    8.3k
    Topics
    74.6k
    Posts

    Strider007undefined

    I have an Ultimaker clone, with a used Duet 2 WIFI. The heater appears rock solid viewing DWC until it switches to standby. I see the temp drop on DWC or if looking at the PanelDue, the normally red indicator turns yellow. I get no heater fault, or message. If I use either the PanelDue or the DWC I can easily reset the bed temp back to active. I've been saving my prints by setting my bed standby temp to 93C (2 degrees below my desired active temp). So far it has not slipped past the standby temp but what is going on.

    Note, the motherboard was purchase used from Europe and shipped over.It is a clone, and driver 0 was blown. Since I only need 4 drivers I just programmed around that issue.

    The system runs on a 12v supply but the bed heater is powered by mains with a SSR-25 controlling it so I don't believe it to be momentary PS sag. Possibly a memory issue? Running RRF3.5.1. Here is my config for this system.

    ; Configuration file for Duet WiFi (firmware version 3.5.1) ; executed by the firmware on start-up ; ; General preferences M575 P1 S1 B57600 ; enable support for PanelDue G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"U-2" ; set printer name ; Network ; WIFI on for home network M552 S1 ; enable network M586 P0 S1 ; enable HTTP ; No WIFI for stand alone, network off ; M552 S0 ; disable network ; M586 P0 S0 ; disable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives ; Driver P0 is not functional M569 P1 S0 ; physical drive 1 goes backwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M569 P4 S0 ; physical drive 4 goes backwards M584 X1 Y3 Z2 E4 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z1600.00 E400.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X900 Y900 Z900 E490 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S90 ; Set idle timeout ; Axis Limits M208 X-98 Y-120 Z0 S1 ; set axis minima M208 X112 Y90 Z300 S0 ; set axis maxima ; Endstops M574 X1 S1 P"!xstop" ; configure switch-type (microswitch) endstop for low end on X via pin xstop, active low M574 Y2 S1 P"!ystop" ; configure switch-type (microswitch) endstop for high end on Y via pin ystop, active low M574 Z1 S1 P"zstop" ; configure switch-type (Optical) endstop for low end on Z via pin zstop, active high ; Z-Probe M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X-90:90 Y-90:90 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 R0.766 K0.379:0.000 D2.01 E1.35 S1.00 B0 ; Auto tune provided values for PID mode 11-2022 M140 H0 ; map heated bed to heater 0 M143 H0 S100 A2 ; shut heater off temporarily if tripped M143 H0 S110 A0 ; set temperature limit for heater 0 to 110C, set fault if tripped M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 R2.371 K0.338:0.000 D10.03 E1.35 S1.00 B0 V11.8 ; parameters derived from Autotune on 11-2022 PID mode. M143 H1 s250 A2 ; shut heater off temporarily if tripped M143 H1 S260 ; set temperature limit for heater 1 to 250C ; Fans M950 F0 C"fan0" ; create fan 0 on pin fan0 and set its frequency M106 P0 S0.0 H1 T45 ; set heatsink fan 0 value. Thermostatic control is turned on at 45C M950 F1 C"fan1" ; create fan 1 on pin fan1 and set its frequency M106 P1 S0.0 ; set part cooling fan 1 value. Thermostatic control is turned off ; Tools M563 P0 D0 H1 F1 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined M501 ; Use settings in override file that were dervived from Auto tuning system

    Any insight would be appreciated.

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

    530
    Topics
    4.7k
    Posts

    dc42undefined

    @ziggymanpopo it looks as though you may be the first!

  • Prototype hardware issues.

    14
    Topics
    581
    Posts

    oliofundefined

    @Coutered we'd need to get way more info about your targeted machine, or the answer may as well be about Jason Statham vs Ansel Elgort ...

  • Discuss Duet on laser cutters and engravers.

    173
    Topics
    1.4k
    Posts

    titusouundefined

    @infiniteloop I got it works as you described. Thank you!!!

    Some detail for future reference.

    Duet [PANEL DUE 5V_EXT] ==(orange)== Relay [JD-VCC]
    Duet [PANEL DUE 3.3V_EXT] ==(green)== Relay [VCC]
    Duet [PANEL DUE GND] ==(black)== Relay [GND]
    Duet [out3-] ==(yellow)== Relay [IN1]
    Duet [out4-] ==(blue)== Relay [IN2]
    Duet [out5-] ==(brown)== Relay [IN3]

    6673708b-eca8-40a8-8cd6-cf670a5a3606-image.png

    83db91cc-387c-4398-8765-8e66b75b386f-image.png

    config.g

    ; Laser mode M452 C"out6" R255 F200 ; Enable Laser mode, on out6, with max intensity being 255, and a PWM frequency of 200 ; FAN-as-IO setup M950 P0 C"out3" ; Red Laser M950 P1 C"out4" ; Laser Enable M950 P2 C"out5" ; placeholder

    No strange behavior during power on nor power lost. Everything looks good.

    Note: the board next to relay is isolated PWN to 0-10V converter, in case someone wondering.

  • Ask questions about installing the firmwares here

    2.1k
    Topics
    22.9k
    Posts

    Chrashemundefined

    @droftarts
    Hi Ian,
    thank you for your answer. I’m sorry for my late reply, but I was three days on vacation. A bit below you’ll find my homeall.g .
    I assume that the homeall is fine because the homeing itself worked and the crash happened during the "true bed levelling", but maybe I'm wrong. To be honest it happened very quickly.
    I just have one Tool and I didn’t use a toolchange.
    So I don’t think that this is the root of evil.
    I think there is no other way than try it again. Is there a special development or kind of logging mode which I can activate? That we gain more information about what’s going on?
    Otherwise i be afraid, that I will crash my machine again and we still have no clue about why it happens.

    What do you think? Should I limit the maximum speeds and accelerations for the test? Maybe than the printer is doing slow movements and I will gain some time to react if something is going wrong.

    homeall.g:

    ; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v3.3.15 on Sat Feb 25 2023 23:42:30 GMT+0100 (CET) G91 ; relative positioning G1 H2 Z5 F10000 ; lift Z relative to current position G1 H1 X-625 F4000 ; move quickly to X Endstop G1 X3 F600 ; go back a few mm G1 H1 X-625 F360 ; Move slowly to X endstops once more (second pass) G1 H1 Y625 F4000 ; Move quickly to Y Endstop G1 Y-3 F600 ; Go back a few mm G1 H1 Y625 F360 ; Move slowly to y endstop once more (second pass) M201 X10000 Y10000 ; Return to full acceleration G90 ; Absolute positioning G1 X150 Y150 F8000 ; Go to the center of the bed (300x300) G30 ; Home Z by probing the bed G91 ; Relative positioning ;G1 Z5 F100 ; Lift Z relative to current position G90 ; Absolute positioning ;G1 H1 X305 ; home X axis ;G1 H1 Y305 ; home Y axis ;G1 X-5 Y-5 F6000 ; go back a few mm ;G1 H1 X305 F360 ; move slowly to X axis endstop once more (second pass) ;G1 H1 Y305 ; then move slowly to Y axis endstop ;G1 H1 Z-305 F360 ; move Z down stopping at the endstop ;G90 ; absolute positioning ;G92 Z0 ; set Z position to axis minimum (you may want to adjust this) ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F100 ; lift Z relative to current position ;G90 ; absolute positioning

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

    5.1k
    Topics
    53.8k
    Posts

    cosmowaveundefined

    @LuniLAB Can it be that your feedrates are a bit high?
    Is it a delta? According to the square bed, i think not...
    Can your printer reach this fast z-movement?

  • Discuss using conditionals, loops and variables in gcode

    738
    Topics
    5.2k
    Posts

    Nazarundefined

    Hello everyone,

    Just bumping this up—can anyone help with my Y-axis homing process issue? Any guidance would be greatly appreciated!

    Thank you!

  • Ask questions about the official web interface here

    1.5k
    Topics
    12.7k
    Posts

    chrishammundefined

    @Seba7890 Are you using session keys as described on the same page?

  • Feedback for docs.duet3d.com

    99
    Topics
    479
    Posts

    DonStaufferundefined

    @infiniteloop It was specifically how the GCode part of it interacted that I didn't understand. The HRP is explained, and the GCodes are named, but how they interact seems to be a weak point of the docs.

    Thanks you, everyone! It's been very helpful and I think I have it worked out now.

    So here's the end result, in case it helps any future enthusiast to have an example:
    Bed.png
    The measurements I used in this discussion were rounded versions of my real machine to make it easy to talk about; this image contains the real values. Here's the actual geometry and what I settled on for settings. I left M208 X0 Y0 and used the probe as HRP, which simplifies the probing issue, and using the primary nozzle seems like it complicates and confuses things when using the secondary. In theory, my 2 nozzles and probe are supposed to all have the same X coordinate, but I had to fine tune it so the 2 nozzles come out in the same place given the same G0 or G1 command, and in real life they aren't quite in a line.

    Regarding bed leveling, it's my understanding that the probe points need not all be in exactly the same relation to their respective screws as one another - that the differences are compensated for in the math. I did the best I could on each one, but naturally the machine home prevents getting toward the front enough to be close to the front left probe point. and the fans are in the way on the right probe point. My leveling isn't actually all that repeatable, but I'm assuming that's my build material not being held down well enough (PEI 2mm).

  • 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
    781
    Topics
    9.4k
    Posts

    4eIIIuPundefined

    @mrehorstdmd Thank you for the detailed answer, I have seen these photos. Well, then I'll try, try, but honestly I'm already giving up a little... I get either a noisy printer or low rigidity, but all options are combined by ripples.

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

    108
    Topics
    763
    Posts

    OwenDundefined

    @oliof said in I suggest adding a check box to add M501:

    What's missing for me is a way to dump the current configuration with all tweaks into a macro file I could keep around.

    Perhaps an extension of M471 would be a good idea?
    At present you can rename and move a file but it deletes the original.
    Perhaps a "C" parameter to only copy the file?

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

    DueUI
    172
    Topics
    2.5k
    Posts

    dc42undefined

    @cosmowave Duet 3 boards now support notifications via MQTT over WiFi interfaces. In RRF 3.6 that will be extended to Ethernet interfaces. Unfortunately Duet 2 boards have insufficient flash memory and RAM to support MQTT.

  • 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

    390
    Topics
    3.9k
    Posts

    droftartsundefined

    @greggles said in Filament monitor on Duet 0.6:

    I am guessing low signal means tied to ground

    Yes, you may have to experiment with that, as it depends on how the switch is wired. Ideally the microswitch will be 'Normally Closed', ie pin is grounded when filament is present, and only go 'high' (or rather floating) when filament runs out, as it is less susceptible to interference then. If you end up with a switch on a 3-wire PCB (one wire will go to 3.3V), you should still be able to connect it; see https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_endstops

    The Duet 0.6 is less tolerant to wiring errors than newer boards, so check your wiring at least twice before turning it on. You can test it as a normal endstop switch first with M574, before setting it up as a filament runout sensor.

    I also have a Fisher (I used to work for RepRapPro), and it still comes out to test firmware updates and print odd bits and bobs when other printers are broken or busy. It currently has a Duet 2 Maestro in it, but I have plans to update it to a Duet 3 Mini 5+ board. Also got rid of the original extruder, has a Bondtech BMG clone on it now, much more reliable! Also carbon rod arms. I need to redo the side panels though, as the acrylic cracked in a couple of places, and broken around one corner. I've got a pile of 3mm Dibond to make them, though I'll have to get my CNC router running again before I can!

    Let us know how you get on.

    Ian

  • Discuss the smart PCB effector for delta printers here.

    404
    Topics
    4.0k
    Posts

    droftartsundefined

    @gorf32 is the problem when the hot end is hot, or when the hot end heater is actually 'on' (ie heating)? If you try probing with the M558 B parameter set to B1, does that help? If it does, I expect the heater PWM is causing interference. If not, I would think that the heat is causing the Smart Effector PCB to expand, so changing the reading; try adjusting the sensitivity, see https://docs.duet3d.com/en/Duet3D_hardware/Accessories/Smart_Effector#programming-the-sensitivity

    Ian

  • No decsciption available

    229
    Topics
    1.9k
    Posts

    chuijseundefined

    Hello @gwatson90, It's been a while since the last post. I've been looking for the same information lately, as I was thinking of using the same senor on a PEI textured surface. How did your experimentation go using the IR sensor and the textured PEI surface, does it work ?

    Or anyone that has used the DC42 IR probe on Textured PEi surfaces with success or had experience trying it?

    Greetings to all!

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

    669
    Topics
    5.3k
    Posts

    dc42undefined

    @oliof said in BOSSA Program Port in Windows 10 to flash PD:

    @bLiTzJoN you can update PD via RepRapFirmware these days

    That's the case for version 3 and integrated PanelDues, but not for version 2.

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

    197
    Topics
    2.1k
    Posts

    dc42undefined

    @Muhammed the PS_ON pin could be used for this purpose, but you must connect a flyback diode (the right way round!) in parallel with the relay coil, to protect the output from the coil back emf when you turn the relay off.

    Alternatively, use a relay module instead of a bare a relay, then you should be able to drive from one of the pins on the expansion header.

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

    Exerqtorundefined

    Moving this over to a separate topic.

    System info:
    Duet Mini 5+ v1.02 ( 3.6.0-a2+), Duet 1LC v1.2a (3.5.2), standalone, 24v, CoreXY, 3-point bed leveling with individual Z steppers.

    Copied from the topic above to catch up:

    I've been doing roughly 24hours of printing on 3.6.0-a2+3 now without any notable issues, but when I'm about to start print this morning (a print finished in the middle of the night, and the printer has just stood idle since that) it's acting up/crashing into the bed.

    (The printer is a Voron Triden by the way.)

    I start a print from the office and wait for the printer to start homing, hear it homing XY and when it goes of to home Z I hear steppers just turning and turning, so I go out and check on the printer. And it turns out that the rear-center Z stepper is standing still(with the carriage roughtly about where it should be), while both the front Z steppers are still going in a downwards motion about halfway along the Z-axis (I have "WobbleX" on the z-axis).

    I sprint across the room and hit the E-stop and start troubleshooting, first checking out DWC and what it has to say:

    26.7.2024, 09:58:32 Emergency Stop! Reset the controller to continue. Error: Failed to home axes Z 26.7.2024, 09:58:32 Emergency stop, attemping to reconnect... 26.7.2024, 09:58:12 G28 Z Warning: Driver 0.2 warning: phase A may be disconnected, phase B may be disconnected 26.7.2024, 09:55:59 Error: G10: Probe was not triggered during probing move Cancelled printing file 0:/gcodes/Automower/Rim_automower_305_0.2mm_ABS_0.4n_2h14m.gcode, print time was 0h 16m Error: in file macro line 114: G1: insufficient axes homed 26.7.2024, 09:53:33 Warning: Driver 0.2 warning: phase A may be disconnected, phase B may be disconnected 26.7.2024, 09:51:07 Warning: Driver 0.2 warning: phase A may be disconnected, phase B may be disconnected 26.7.2024, 09:49:20 Warning: Driver 0.2 warning: phase A may be disconnected, phase B may be disconnected 26.7.2024, 09:39:45 M32 "0:/gcodes/Automower/Rim_automower_305_0.2mm_ABS_0.4n_2h14m.gcode" File 0:/gcodes/Automower/Rim_automower_305_0.2mm_ABS_0.4n_2h14m.gcode selected for printing

    This all sounds somewhat odd since Driver 0.2 is the one for the rear-center stepper, which don't seem to be doing anything weird.

    Here is a vizual representation of my drive mapping for reference:

    ; (While looking at the printer top down) ; 0.0-----0.1 ; | 0.2 | ; |-------| ; |0.3|0.4| ; ---+--- ; Front

    (0.0 & 0.1 is for the CoreXY motion system)

    I continue troubleshooting:

    I power down the printer and manually reset the two front axis & lock the bed. Then I flip the machine around to check the wiring which all looks good. Put the machine back on it's feet, power up, remove the bed locks and home the printer: all seems fine. Ok? So I jog the printer through full Z motion min-max-min with Paneldue and all seems fine. Not being able to find anything obviously borked I bring the bed up to heat again and attempt to run a tram routine. Tramming routine goes as followng: Home all axis. Coarse tramming pass with 10mm dive height. Fine tramming with 2mm dive height until the deviation is bellow 0.005mm). It runs the coarse pass, and ATTEMPTS tries adjust to 3 z-axis:
    2024-07-26 10:15:06 [warn] Leadscrew adjustments made: -2.315 2.178 1.401, points used 3, (mean, deviation) before (0.660, 1.775) after (-0.000, 0.000)
    It proceeds to the fine pass @ 2mm dive height, but for some reason the z-axis steppers didn't to like they should on the course pass so it ends up scraping the nozzle allong the buildplate rather than hover 2mm above it (I've got Voron TAP, so it's not the biggest issue in the world with a slight "nozzle kiss" thankfully). Again I have no other choice than to slap the E-stop to avoid anything getting destroyed. I check the Z-stepper wiring once again since the steppers didn't move like expected, butI still can't find anything wrong. Recheck I still got full range of motion on the Z axis, which I have: hence rulling out phase/connection issues to the Z-steppers (as far as I can understand). Try once more, and the exact same happens, and that's where I'm at now.

    Like I opened up with saying, I've done multible trams (restarted the printer a couple times and it trams the bed first print after each reboot), without issues during the roughly 24hours of print time I have on it with 3.6.0-a2+2.
    And that this happens with the printer standing idle after a print has finished is somewhat weird (roughly 3.5 hours between the night print finished and i tried starting a new one this monring).

    Status update: I just had time to roll back to 3.5.2 to check if fixes the problem, which it did. So it looks like it's something going on somewhere in regard to Z axis controll in 3.6.0-a2+3 @dc42!

    I haven't got anything else than eventlogging going on at the time so i don't know if it's much if any usefull info one can pick up from that. If you think it might i can supply the entire log from the last couple days.

  • Discuss and contribute to the Duet Software Framework

    115
    Topics
    971
    Posts

    curieosundefined

    @chrishamm Was xscreensaver installed on the older bullseye image? I'll give that a try when I get into work later, thanks!

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

    386
    Topics
    3.1k
    Posts

    dc42undefined

    @petm you could circumvent this limit by configuring up to 64 gpout ports and up to 56 fan ports. You would control the gpout ports using M42 and the fan ports using M106.

    Another possibility with RRF 3.6 on Duet 3 boards would be to use Modbus devices to provide some of the output ports and turn them on/off using M260.1 calls.

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

    932
    Topics
    7.3k
    Posts

    Kioliaundefined

    @oliof Deltas would likely want wildly different IS compensation for Z versus XY since Z is the one axis where everything's going the same direction, but assuming per-axis IS settings become a thing in RRF, there might be a case there!

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

    323
    Topics
    2.1k
    Posts

    the_Kundefined

    I would love to be able to move the emergency stop button to the middle of the screen.

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

    339
    Topics
    3.7k
    Posts

    gloomyandyundefined

    @Arminas A lot of work I know, but try swapping the toolboards over between the two machines? See if the problem moves or not?

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

    98
    Topics
    916
    Posts

    zBeebleundefined

    I need to decide on an SOC or parts for a project. I need one or two USB 3 and an interface for micro-ssd. All of which needs to operate "at speed" ... I suppose the limiting factor would be the micro SSD. But I could also go with an NVME interface instead of SSD.

    So... here's the idea. I want a USB stick to rule them all. I want to be able to present ISOs or images as the USB. I want it to be able to present a restricted copy of what's on the disk. I'm thinking the interface would be a button or two and some LED. Default presentation is a USB that takes power. Cycling through with the button we'd get a text config, all files, and then 10 configured presentations (iso images, empty storage, select files, what have you).

    Nice to have? Bluetooth (you could have a much richer interface on your phone).

    What y'all think?

  • 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

    158
    Topics
    935
    Posts
Unless otherwise noted, all forum content is licensed under CC-BY-SA