@cncmodeller That's a good tip, I have actually resorted to something similar!
I created a "M2001.g" file in the sys folder and added a M2001 command on each layer change...
The issue is that I am using a custom slicer that I can't easily change myself and that doesn't have this capability (that at least adds ";LAYER: ##" markers at the beginning of a new layer). I was hoping to not have to manually change the gcode file, but thank god for the "change all occurrences" function in VSCode 
Hello Guys,
I want to have the duet execute a script on every new layer without having to add that in the slicer, similar to the "start.g" or "end.g" files.
Is there any tricks to do that already?
I guess as long as there are some kind of layer indicators in the gcode that could be doable?
Hello Guys,
I am currently helping a friend build a Voron 2.4 with a Duet3 6HC + 3HC expansion. We are running RRF 3.3.0.
The machine is mostly done, however we are fighting with the proper setup of the Z-Probe.
The issue is that we cannot get a good Z=0 datum after the start.g routine, we always have to baby-step -0.75mm in order to get to a nice first layer.
The start.g homes X and Y with their endstops, then homes Z with a Z-Probe in the center of the bed. Then we run a G32 that probes next to the four Z axes and aligns the printer gantry to the printbed (following this guide) . after that we do another homing run for Z to establish the right Z=0 datum.
The initial Idea was that we made a mistake when setting up the Z Probe height, so we went ahead and followed the "Test and calibrate a Z probe" guide to make sure our trigger height was set correct, which it was.
We then tried to play around a bit with this value and started to increase it, to trick the duet into coming closer to the true Z=0. Somehow it doesn't matter what we change this value to, it does not reflect to the machine, and I don't understand why.
Anyone has an idea where I am messing up?
config.g:
; Configuration file for Duet 3 (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.5 on Sun Nov 07 2021 21:03:00 GMT+0100 (Mitteleuropäische Normalzeit)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
;M550 P"Duet 3" ; set printer name
M669 K1 ; select CoreXY mode
; A0.0 U1.1
; 20/280 280/280
;
; B0.1 C0.2
; 20/20 280/20
;
; AAAAA FRONT AAAAA
; Drives
M569 P0.4 S0 ; physical drive 0.4 goes forwards B
M569 P0.3 S1 ; physical drive 0.3 goes forwards A
M569 P0.0 S1 ; physical drive 0.1 goes forwards Z1
M569 P0.1 S0 ; physical drive 0.1 goes forwards Z2
M569 P0.2 S1 ; physical drive 0.1 goes forwards Z3
M569 P1.1 S0 ; physical drive 0.1 goes forwards Z4
M569 P0.5 S0 ; physical drive 0.5 goes forwards E
M584 X0.3 Y0.4 Z0.0:0.1:0.2:1.1 E0.5 ; set drive mapping
M671 X20:20:280:280 Y250:00:00:250 S10
M350 X64 Y64 Z64 E64 I1 ; configure microstepping with interpolation
M92 X640.00 Y640.00 Z1200.00 E1746.16 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X60000.00 Y60000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X6000.00 Y6000.00 Z4000.00 E250.00 ; set accelerations (mm/s^2)
M906 X1200 Y1200 Z1200 E400 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
; Axis Limits
M208 X0 Y0 Z-1 S1 ; set axis minima
M208 X300 Y300 Z250 S0 ; set axis maxima
; Endstops
M574 X2 S1 P"io8.in" ; configure switch-type (e.g. microswitch) endstop for high end on X via pin io8.in
M574 Y2 S1 P"io6.in" ; configure switch-type (e.g. microswitch) endstop for high end on Y via pin io6.in
M574 Z1 S2 ; configure Z-probe endstop for low end on Z
; Z-Probe
M558 P5 C"^io4.in" H5 F120 T12000 ; set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y25 Z1.3 ; set Z probe trigger value, offset and trigger height(mehr Z=näher am Bett)
;M557 X15:250 Y15:250 S235 ; define mesh grid
; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" Q10 T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 B0 R0.603 C260.8 D1.69 S1.00 ;V24.3
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1
M308 S1 H63 L-172 ; Thermistor Offset correction
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
; Fans
M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P0 C"HOTEND" S0 H1 T45 ; set fan 0 name and value. Thermostatic control is turned on
M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
M106 P1 C"PARTS" S0 H-1 ; set fan 1 name and value. Thermostatic control is turned off
M950 F2 C"1.out6" Q500 ; create fan 2 on pin 1.out6 and set its frequency
M106 P2 C"CASE" S1 H-1 ; set fan 2 name and value. Thermostatic control is turned off
M950 F3 C"out9" Q500 ; create fan 3 on pin out9 and set its frequency
M106 P3 C"CASE" S1 H-1 ; set fan 3 name and value. Thermostatic control is turned off
; Tools
M563 P0 S"EXTRUDER" D0 H1 F0 ; 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
; Miscellaneous
T0 ; select first tool
bed.g:
; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.3.5 on Sun Nov 07 2021 21:03:00 GMT+0100 (Mitteleuropäische Normalzeit)
M561 ; clear any bed transform
G28 ; home all axes
; Probe the bed at 7 points
G91 ; relative positioning
G1 H2 Z3 F1200 ; lift Z relative to current position
G90 ; absoluet positioning
G30 P0 X20 Y250 H0 Z-99999
G91 ; relative positioning
G1 H2 Z3 F1200 ; lift Z relative to current position
G90 ; absoluet positioning
G30 P1 X20 Y0 H0 Z-99999
G91 ; relative positioning
G1 H2 Z3 F1200 ; lift Z relative to current position
G90 ; absoluet positioning
G30 P2 X280 Y0 H0 Z-99999
G91 ; relative positioning
G1 H2 Z3 F1200 ; lift Z relative to current position
G90 ; absoluet positioning
G30 P3 X280 Y250 H0 Z-99999 S4
homeall.g:
; homeall.g
; called to home all axes
;
; execute homex.g, then homey.g and last homez.g
G91 ; relative positioning
G1 H2 Z25 F1500 ; lift Z relative to current position
G90 ; absoluet positioning
M98 P"homex.g"
M98 P"homey.g"
M98 P"homez.g"
homex.g:
; homex.g
; called to home the X axis
;
G91 ; relative positioning
G1 H1 X305 F3500 ; move quickly to X axis endstop and stop there (first pass)
G1 X-5 F12000 ; go back a few mm
G1 H1 X305 F360 ; move slowly to X axis endstop once more (second pass)
G90 ; absolute positioning
homey.g:
; homey.g
; called to home the Y axis
;
G91 ; relative positioning
G1 H1 Y305 F3500; move quickly to Y axis endstop and stop there (first pass)
G1 Y-5 F12000 ; go back a few mm
G1 H1 Y305 F360 ; move slowly to Y axis endstop once more (second pass)
G90 ; absolute positioning
homez.g:
; homez.g
; called to home the Z axis
;
G90 ; absolute positioning
G1 X150 Y150 F12000 ; go to first probe point
M558 P5 C"^io4.in" F1500 T12000 ; set Z probe type to switch and the dive height + speeds
G30 ; home Z by probing the bed
M558 P5 C"^io4.in" F120 T12000 ; set Z probe type to switch and the dive height + speeds
G30
start.g:
M117 "start.g ausgefuehrt"
M564 S0 ; disable axis limits
G32
G28 Z ; home Z
M564 S1 ; enable axis limits
@phaedrux Yeah, so far I have only been using / configuring single-tool machines. The Extruder tool on 23.0 works fine. but because its on a CAN-extension board the M571 command doesn't work.
The tool is defined to use both drives: M563 P0 D0:1
I have tried to configure the Extruder tool with drives 0.0 and 23.0 and had partial success: If I write M584 E:0.0:23.0 then the output on extrude pin switches, but I don't see any STP/DIR signals on 23.0.
If I write M584 E:23.0:0.0 however, I get no output on extrude pin switches, but I see STP/DIR signals on 23.0...
; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Fri Jul 03 2020 17:01:27 GMT+0200 (Central European Summer Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
;Recommended by 1XD manual
G4 S1 ;wait for expansion boards to start
; RESTART 1XD
;M98 P"0:/sys/COBOD_restart_expansionboards" ; reboot 1XD boards
; Drives
M569 P20.0 S1 ; X forward on 20
M569 P21.0 S1 ; Y forward on 21
M569 P22.0 S1 ; Z forward on 22
M569 P23.0 S0 ; E forward on 23
M569 P24.0 S1 ; U forward on 24
; additional E driver for output on extrude
M569 P0.0 S0
M584 X20.0 Y21.0 Z22.0 E0.0:23.0 R0 ; set drive mapping for linear axes
M584 U24.0 R1 ; set drive mapping for rotational axes
;CONCRETELAB VALUES
M350 X1 Y1 Z1 E1:1 U1 I1 ; Configure microstepping with interpolation
M92 X100 Y100 Z100 E100 U100 ; Set steps per mm
M566 X3000 Y3000 Z100 E3000 U1200 ; Set maximum instantaneous speed changes (mm/min)
M203 X15000 Y15000 Z2500 E50000 U6000 ; Set maximum speeds (mm/min)
M201 X300 Y300 Z100 E1500 U300 ; Set accelerations (mm/s^2)
; Axis Limits
M208 X0 Y0 Z000 E-99999:-99999 U-99999 S1 ; set axis minima
M208 X5000 Y5000 Z3000 E999999:999999 U999999 S0 ; set axis maxima
; Endstops
M574 X0 ; no X endstop
M574 Y0 ; no Y endstop
M574 Z0 ; no Z endstop
M574 E0 ; no E endstop
M574 U0 ; no U endstop
M574 V0 ; no U endstop
; Z-Probe
M558 P8 C"22.io0.in" H20 F750 T15000 R1 ; Set Z probe type to switch and the dive height + speeds
G31 P500 X0 Y-200 Z156 ; Set Z probe trigger value, offset and trigger height
M557 X0:3200 Y0:4200 S500 ; Define probing grid size and spacing
M376 H500 ; define compensation taper
; Heaters
M140 H-1 ; Disable heated bed
; Tools
M563 P0 D0:1 ; 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
; Miscellaneous
T0 ; Select first tool
M302 P1 ; Allow cold extrusion
; Homing outputs
M950 P0 C"20.out1" ; Homing request pin for X
;M950 P1 C"21.out1" ; Homing request pin for Y
;M950 P2 C"22.out1" ; Homing request pin for Z
;M950 P4 C"24.out1" ; Homing request pin for U
;M950 P5 C"25.out1" ; Homing request pin for V
; increase movement queque buffer size
M595 P240 S500
; get current position from PLC
G28
;For saving worklpace coordinate systems to file
M501
; output on extrude
M571 P"0.io0.out" S1 ; enable output on extrude
Reading through the gcode wiki again I noticed that I probably need to define a mixing ratio, as our slicer doesn't output multiple E values...
I have added the corresponding command to the config.g:
; set tool mixing ratio
M567 P0 E1:1
........ and now it finally works!
I have added this block onto the end of the config.g
; SETUP OUTPUT ON EXTRUDE
; additional "virtual" E driver
M569 P0.0 S0
; updated driver mapping
M584 E0.0:23.0 R0
; updated microstepping setting
M350 E1:1
; updated axis limits
M208 E-99999:-99999 S1 ; set axis minima
M208 E999999:999999 S0 ; set axis maxima
; updated Tool definition
M563 P0 D0:1
; set tool mixing rato
M567 P0 E1:1
; enable output on extrude
M571 P"0.io0.out" S1
Thanks for sending me into the right direction @Phaedrux !
I was hoping to get this working by adding a second driver from the 6HC to the E axis without luck. I am now not sure if this is because of some limitation of RRF that I didn't see or if I am implementing this wrong:
; Configuration file for Duet 3 (firmware version 3)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
;Recommended by 1XD manual
G4 S1 ;wait for expansion boards to start
; Drives
M569 P20.0 S1 ; X forward on 20
M569 P21.0 S1 ; Y forward on 21
M569 P22.0 S1 ; Z forward on 22
M569 P23.0 S0 ; E forward on 23
M569 P24.0 S1 ; U forward on 24
M569 P0.0 S0 ; additional axis for OutOnExtrude
M584 X20.0 Y21.0 Z22.0 R0 ; set drive mapping for linear axes
M584 E23.0:0.0 U24.0 R1 ; set drive mapping for rotational axes
[...]
;OMRON VALUES
M350 X1 Y1 Z1 E1 U1 I1 ; Configure microstepping with interpolation
M92 X100 Y100 Z100 E100 U100 ; Set steps per mm
M566 X3000 Y3000 Z100 U1200 E3000 ; Set maximum instantaneous speed changes (mm/min)
M203 X15000 Y15000 Z2500 U6000 E50000 ; Set maximum speeds (mm/min)
M201 X300 Y300 Z100 E1500 U300 ; Set accelerations (mm/s^2)
[...]
;output on extrude
M571 P"0.io3.out" S1 ; enable output on extrude
Is there any workaround or quickfix that you can come up with to control a pin according to extrusion moves? Could I somehow use a driver_Enable signal configured in a certain way?
@dc42 alright, that's good to hear... Any idea when this will be fixed time-wise?
Any idea for a workaround in the meantime?
Could I add a second driver to the extruder axis that is mapped to a driver on the 6HC to make this run? I'll go ahead and give this a try..
Hey @dc42, just wondering if you have managed to fix this?
I couldn't see anything about that in the changelogs..
Hello,
I am trying to set up M571 "output on extrude" on my current machine, however I am a bit stuck.
The output of the pin never changes, whether I am extruding manually or from gcode.
I have tried several ways and different pins all without success
M571 S1 P"0.out8"
M571 S1 P"out8"
M571 S1.0 P"0.out8"
M571 S1 P"0.out7"
M571 P"out7" S1
(you get the idea)
I can successfully invert the output pin with the ! modifier and measure my VIN voltage, but the pin is not changing when the extruder is active.
The extruder is driven by a 1XD board with CAN address 23:
M569 P20.0 S1 ; X forward on 20
M569 P21.0 S1 ; Y forward on 21
M569 P22.0 S0 ; Z forward on 22
M569 P23.0 S0 ; E forward on 23
M569 P24.0 S0 ; U forward on 24
I have figured out that I cannot use the 1XD as output, I get the following error when I try:
M571 P"23.out1" S1
Error: M571: Remote ports are not supported by this command
I suspect that I haven't configures the tool correctly, but I cannot figure out what to change:
M563 P0 D0 ; Define tool 0
If I enter the drive number differently I get an error:
M563 P0 D23.0
Error: M563: bad drive number
Does Anyone have an Idea?
Thanks!
Attached the full config file:
config.g
@Sindarius Hmm.. I don't know about the inner workings of the DWC, but couldn't it be an option in settings to "show E axis control interface"?
Or would @dc42 have to ass something like this through the firmware?
Hey @Sindarius, great work!
We have been looking for a way to clean up the interface for our concrete printers for a while now!
However, we still have an extruder axis that we need to control, do you think it will be possible to activate the CNC DWC with the nice work coordinate system handler and the big DRO also in FFF mode? (Or also show E axes in the jog button overview?)
Thanks a lot!
depending on what board and version you are running, you can do it with this handy extension:
https://forum.duet3d.com/topic/13194/dsf-extension-exec-on-mcode-was-shutdown-sbc
We see the same issue on Duet2 with latest firmware installed, Layer time is not updating.
The gcode we tested definitely worked previously.
@Veti said in Layer chart not updating in 3.2:
how else would it identify the slicer that sliced the g code?
I think if you have lines like ; layer 42 in your gcode the duet uses this as indicator for layer change.
Hello @dc42,
as Kulitorum mentioned, I have changed the Duet3 to a Duet2 Ethernet, with the latest 3.2 RC2 firmware.
I have added signal filtering/averaging options in the PLC and the Machine was running definitely smoother than with the Duet3, but still not satisfactory.
So I went ahead and changed the controller to a Duet2 with firmware 2.05, which is the version that all our previous machines are running, and the velocity curves look a lot better now:
(Red: X velocity, Green: Y velocity, Blue: U velocity, Orange: Extruder Velocity)
But that is only in some areas. Right after, the Duet outputs strange start-and-stop patterns instead of smooth movements:
(Red: X velocity, Green: Y velocity, Blue: U velocity, Orange: Extruder Velocity)
I have connected a scope to this and verified that the Duet is actually sending these waves, it is not an issue that is coming from the PLC.
The gcode file also looks like it has no slicing errors or corruptions that may cause this.
(printed file: 20210107_qatarcommissioning.gcode )
Changing the acceleration or jerk values is also not visibly influencing the movements of the machine.
(config.g with the values that were active during the testprint: config (8).g )
Can we set up a meeting during the day tomorrow to discuss this in person rather than through back and forth in the forum? We can even pay for that by the hour if necessary
@T3P3Tony I only saw dropped CAN packages in the M122 report of the Duet3 setup when I had step/mm values larger than I think 500. I usually had all axes set to 200 step/mm.
On the duet2 the M122 report gives me a hiccup counter over 1000 when it gets to this start-and-stop movement, even reducing all step/mm values to 20 for X/Y/U and 10 for Z/E doesn't help.
Hey @dc42, all boards are now updated to the latest 3.2-RC2 firmware and show the same issues as before:
(Red: X velocity, Green: Y velocity, Blue: U velocity)
The Acceleration and Deceleration S-curve is pretty deformed...
I have also had a closer look at the M122 diagnostics report and found the following:
X (B20): Moves scheduled 266, completed 266, in progress 0, hiccups 518
Y (B21): Moves scheduled 403, completed 403, in progress 0, hiccups 3699
I don't exactly know what that means, but assume that the hiccups counter should be close to 0?
I have unfortunately ordered the wrong logic analyzer and will have to wait until tomorrow for the right one to arrive, so I will upload the results of the trace sometime tomorrow afternoon.
I am very sure that the issue lies somewhere in the duet 3 side of the machine. I am just guessing, but could it be something with the CAN bus speed? Please let me know if you need any more specific info or files and I will upload them here.
I have done some more tests and data traces in my PLC software, and it looks like this "interruption" happens not only when the U axis starts or stops, but when any axis starts or stops the movement:
(pink: Y position, green: U position, blue: X position, orange is the respective velocity)
I'll have access to a logic analyzer sometime later today, then I can make a trace of the actual signals coming out of the duet.
First of all, thanks for the quick responses
@jay_s_uk no, as long as I have the U axis removed from the configuration everything seems fine. If I add the U axis I start to get the issue.
I am connected to a PLC, not an external driver. The input is a NX-EC0142 card:
https://industrial.omron.eu/en/products/NX-EC0142
@dc42 no, it also seems to be occurring if some of the other axes are in standstill. I will do some data logging today to exactly pinpoint when it happens, but for now it looks like the U axis causes some kind of issue. Let me know if you need more info!
Hello Guys,
I have a machine that uses 5 axes, X,Y,Z,E and U.
I used to have a Duet Ethernet with expansion board driving the machine, which worked without issues.
Now I am facing some issues with my upgraded machine:
I have a Duet3 6HC with 5 1XD expansion boards connected, one for each axis. The Step/Direction output is connected to a PLC system.
This is where it gets interesting: While X/Y/Z/E are moving, everything is fine. As soon as also the U axis starts moving, all other axes seem to be stopping for a short period of time (always exactly 30ms) and then continue to move smooth. Once the U axis stops its movement again, the same thing happens again.
If I trace the input signals on my PLC system, I see the the following:
(orange: calculated velocity of X axis, blue: position of X axis)
If I zoom into where the orange acceleration curve drops I can see a "plateau" in the blue position curve. This is also the same for all other currently moving axes:
Looking at the step/direction signals with a scope I see the following just when the short stop happens:
and then afterwards it comes back to nice looking signals:
Initially I thought the issue is because I was using v0.4 1XD expansion boards, so I changed them to v1.0 1XD boards, no change in the printer behavior.
I have tried to remove the E axis from the configuration to see if I am pushing the limits of the CAN bus, but that didn't change anything.
When I remove the U axis from the configuration I see no issues.
I have played around with acceleration and jerk of the U axis, without much success.
I have tried reducing the step/mm values for all 5 axes down to 100 step/mm without any impact.
Here is the relevant parts from my config.g:
; Drives
M569 P20.0 S1 ; X forward on 20
M569 P21.0 S1 ; Y forward on 21
M569 P22.0 S1 ; Z forward on 22
M569 P23.0 S1 ; E forward on 23
M569 P24.0 S1 ; U forward on 24
M584 X20.0 Y21.0 Z22.0 E23.0 U24.0 ; set drive mapping
M92 X100 Y100 Z100 E100 U50 ; Set steps per mm
M566 X200 Y200 Z200 E3000 U3000 ; Set maximum instantaneous speed changes (mm/min)
M203 X60000 Y60000 Z1500 E60000 U36000 ; Set maximum speeds (mm/min)
M201 X300 Y300 Z100 E500 U5000 ; Set accelerations (mm/s^2)
Any ideas what could be going wrong?
Edit:
I have also updated all boards including expansion boards to the latest firmware:
Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.2.0-rc1
Firmware: RepRapFirmware for Duet 3 MB6HC 3.2-RC1 (2020-12-19)
m115 b24
Duet EXP1XD firmware version 3.2-RC1 (2020-12-19)
m115 b23
Duet EXP1XD firmware version 3.2-RC1 (2020-12-19)
m115 b22
Duet EXP1XD firmware version 3.2-RC1 (2020-12-19)
m115 b21
Duet EXP1XD firmware version 3.2-RC1 (2020-12-19)
m115 b20
Duet EXP1XD firmware version 3.2-RC1 (2020-12-19)
Yes, the boards work fine. I can control the axes that are connected to the individual boards even with this error coming up.
I did in fact not have any termination resistor in the boards - I added them on the last one and would you look at that, the error is gone, thanks!
Hello people,
normally on a FFF machine, a 0.25mm difference on the build plate is definitely noticeable, so it makes for a good minimum and maximum of the scale in the heightmap window.
However, I am using the duet to control very very large machines that will map out areas with significantly more differences in height.
When I am trying to look at the heightmap, it is very much distorted:
The attached picture is a heightmap of a small area, 3m x 4m. Once there are more points and the area increases, the entire thing gets even crazier.
What I am suggesting is a configurable scale for the heightmap, changeable somewhere in the settings