Hi Guys,

i have build a large format printer (10x5x4m) and running on the duet system. I have already printed some huge print.
Now in 4 days time i've started the exact same gcdoe 4 times and the 4th time it did something very weird.
Here is the video for explanation: (problem at 2:38)
https://www.youtube.com/watch?v=Ih0jrkUJZYs

To me it looks like the Y axis just stopped working for a few seconds and then picked up again. I checked all the wiring and the other camera's for blinking lights on the boards and everything looked fine.

It is good to mention i did not turn off power to the printer these 4 days. That should not be an issue as some prints take more then 4 days to finish.
The gcode itself cannot be the problem bc that has done perfect in the past days. Now suddently out of nowhere it dit what is shown in the video.
Recreating the issue while printing would take about 6 hours and alot of $$ in material. so thats not an option.

added is the M122, about 14h later than the pause-print as i was not at the shop when it happened.

Hope someone can help figure this out.

EDIT: found out the Y axis motors are skipping steps on the belt rack system..

Kind Regards,

Sten

Hi Guys, @Aitor @dc42

Same here... Motor brakes do not engage when using M18 or M84. It seems like when you plug the power-cord in, the brakes get the 24V.

That is pretty dangerous in my set up as my Z-axis weighs around 350kg...

Also the M569.7 (configure brakes) does not support 2 brakes. so M569.7 C"out0" works fine, but M569.7 C"out0+out1" does not.
Also putting them in seperate M569.7 commands does not work.

The DWC, 1HCL expansion boards and MB6CH are on v3.4.6

Looking forward to a reply!

@droftarts Hi ian, thank you for your swift response. Here is the m122

Duet 6ch mainboard
4x duet 1xd for the bridge/gantry
1x 1XD for X-axis
1x 1XD for extruder
1x 1HCL for Y-motor (other one on mainboard for now)
firmware: 3.5b4

i am actually printing at the moment and shot the next video for reference, i will make another one when it has a longer perimiter. (dont mind the wobbly hot air tubes)
https://www.dropbox.com/scl/fi/ipg2zb2h06mb7aswqh766/Video-30-03-2025-14-35-05.mov?rlkey=4mfreacwh6p62th9tp045yr8e&st=y9515bpx&dl=0

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5.0-beta.4 (2023-06-08 23:41:30) running on Duet 3 MB6HC v1.02 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TN-6J9D0-3SD6Q-1BB2T
Used output buffers: 3 of 40 (36 max)
=== RTOS ===
Static ram: 155012
Dynamic ram: 120548 of which 204 recycled
Never used RAM 67228, free system stack 136 words
Tasks: NETWORK(1,ready,39.6%,169) ETHERNET(5,nWait,0.2%,314) HEAT(3,nWait,0.0%,353) Move(4,nWait,0.0%,243) CanReceiv(6,nWait,0.1%,771) CanSender(5,nWait,0.0%,330) CanClock(7,delaying,0.0%,349) TMC(4,nWait,8.2%,59) MAIN(1,running,51.8%,444) IDLE(0,ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 01:05:48 ago, cause: software
Last software reset at 2025-03-30 12:28, reason: User, Gcodes spinning, available RAM 68104, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,1
MCU temperature: min 25.0, current 35.1, max 35.6
Supply voltage: min 47.6, current 47.8, max 48.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.2, max 12.5, under voltage events: 0
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/1936/1936, gc cycles 10
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 368, reads 9781, writes 21 timeouts 0
Driver 1: standstill, SG min n/a, mspos 8, reads 9791, writes 11 timeouts 0
Driver 2: standstill, SG min n/a, mspos 8, reads 9791, writes 11 timeouts 0
Driver 3: standstill, SG min n/a, mspos 8, reads 9792, writes 11 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 9792, writes 11 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 9792, writes 11 timeouts 0
Date/time: 2025-03-30 13:34:04
Slowest loop: 130.70ms; fastest: 0.05ms
=== Storage ===
Free file entries: 19
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 7.2ms, write time 67.0ms, max retries 0
=== Move ===
DMs created 125, segments created 6, maxWait 3426434ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00
next step interrupt due in 30425683 ticks, disabled
=== DDARing 0 ===
Scheduled moves 50, completed 47, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 17], CDDA state 3
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is assembling a command in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is doing "M42 P6 S0" in state(s) 0 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x80000003
Queue 0 has 'M42 P4 S0' for move 49
Queue 0 has 'M42 P6 S0' for move 50
Queue 0 has 'M42 P5 S0' for move 50
Queue 0 has 'M42 P4 S0' for move 50
Queue 0 has 'M42 P6 S0' for move 50
Queue 0 has 'M42 P5 S0' for move 50
Queue 0 has 'M42 P4 S0' for move 50
Queue 0 has 'M42 P6 S0' for move 50
Queue 0 has 'M42 P5 S0' for move 50
Queue 0 has 'M42 P4 S0' for move 50
Queue 0 has 'M42 P6 S0' for move 50
Queue 0 has 'M42 P5 S0' for move 50
Queue 0 has 'M42 P4 S0' for move 50
Queue 0 has 'M42 P6 S0' for move 50
Queue 0 has 'M42 P5 S0' for move 50
Queue 0 has 'M42 P4 S0' for move 50
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 20007, received 300264, lost 0, boc 0
Longest wait 1ms for reply type 6041, peak Tx sync delay 281, free buffers 50 (min 46), ts 19744/19743/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 1158.85ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 2 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
= WiFi =
Interface state: disabled
Module is disabled
Failed messages: pending 0, notready 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

@sbNielsen @dc42 @T3P3Tony @droftarts Hi guys, i know this topic is pretty old but i'm struggling with the same thing. i also have a (slightly bigger) 3d printer (picture A below) and i am scared to raise the acceleration and jerk settings. One thing i know, right now they are not correct. Even at the slight curves it slows down alot to make the curve and leaves artifacts. (picture B).

The problem is if the accelaration / jerk gets too high in certain situations (when the Z axis has to come to a stop from a going-down movement) if the forces are too high the motors will skip or worse... the whole gantry drops down. The 4 motors on the gantry/bridge are nema42 (32nm) and there is 100kg per side counter-weight on the gantry. That makes sure the likelyhood of this happening less but it has happened to me in the past. Now we have changed the motors to the big 32nm ones but i'm still scared.

So long story short, i dont mind it slowing down a bit, i do mind it stuttering, i must have the values wrong.
i hope somebody can help me / advise me.

info:
i am printing at 85mm/s
i am printing in a 45 degree angle
sliced with cura (already spent alot of time with resolution settings etc.) (using custom post processor for 45degrees)
NOTE: i print in 45 degree angle with a 'normal' printer, this means for a diagonal line / curve i'm moving all 3 axis at the same time.

A: The printer

B: Artifacts

C; config

;!!!DRIVE-MAPPING!!!
M584 X44.0 Y0.0:54.0 Z40.0:41.0:42.0:43.0 E55.0    ;NEW
M92 X22.63 Y113.15 Z113.15 E50 U600   ;NEW		
M350 X16 Y8 Z16 U16 E16 I0   ;NEW

M566 X500.00 Y250.00 Z250.00 E9000		; set maximum instantaneous speed changes JERK (mm/min) 
M203 X10000.00 Y4200.00 Z4200.00 E1000000000	; set maximum speeds (mm/min) ||1500mm/m = 25mm's || 6000 = 100 || 9000 = 150 || 
M201 X250.00 Y75.00 Z75.00  E6000		; set accelerations (mm/s^2)

M906  Y6000  I70              ; set motor currents (mA) and motor idle factor in per cent
M84 S9999999999999999999999                                                  ; Set idle timeout in seconds

;BACKLASH COMPENSATION
M425 X0.25 Y0.25 S10

; !!!Axis Limits!!!
M208 X0 Y0 Z0 U0 S1                                     ; set axis minima
M208 X3500 Y9000 Z1800 U9999999999 S0                                  ; set axis maxima

@dc42 Good Morning, Thank you for your reply.

The GND connection between X11 and the 1XD worked, a day later i had another issue with another 1XD but this time outputting step/dir signals.
I think the whole problem is/was that i had the machine turned on for 11 days straight and there must be too much static (pellets conveying to the extruder have alot of static (the hopper and conveyer tubes are grounded).

For the 1XD with the The step/dir signal problem, the signal was irregular and 'missed steps' all of a sudden, it became worse and worse. I unplugged power to the board and plugged it back in, it was working fine right away. So last night i turned off the machine and turned it on this morning. Now everything works fine for the past 2 hours.

Do you think this is a grounding issue? with static buildup in the whole machine being the issue?

@dc42 Thank you for the reply, i dont use X10, but instead use X11 (page 62). i have pins 11 and 9 jumped, for other reasons and indeed step and dir on 6,7,8,12
X10 is where the cable to the PC goes into for configuration, i do not have a break out board for that. only for X11 and X12

Could a fix be wiring it as a single ended connection? only wiring the step- and dir- to the 1XD

EDIT: it has always worked in the current config,
EDIT: i have the Compax3S150 i10T10

@droftarts Thank you for your reply, i am using the PARKER COMPACT X3 servo driver, it is a huge beast with a very in depth documentation. (linked below)
I guess i have to find out why the driver is suddently emitting 5v through the step and direction. There is no option for that in the configuration and i didnt change anything

Documentation:
https://download.variodrive.nl/Parker/Compax3/manuals/C3I10T10_eng.pdf

Somehow after a while the 1XD connected to my servo driver for the extruder killed itself, looking at the wiring i was afraid it shorted itself. i fixed the wiring and put a new one on. Today that one gave up out of nowhere, first the out0 worked but the step+dir didnt. after a restart there was just the blue LED and nothing else.

So i disconnected it, grabbed a spare board and put back the connectors. while plugging in the step+dir i saw the red 5v LED come on. As that could be a red flag i turned to the PC and googled why servo drives emmit 5v signal on the step+dir. I found out this was normal bc they are internally pulled up. So to be sure i turned off the servo. connected and powered the 1XD, then turned on the servo. as soon as i turn on the servo the board goes back to only the blue LED. no response anymore.

So my questions are... can i fix the boards? and Is this normal or is the 5v from the servo a problem?
i measure 5v between step+ and step-, same goes for dir+ and dir-

Everything worked fine yesterday....

Kind Regards,

Hi Guys,

I'm looking for a way to send notifications from the Duet. To a mail server or some service i dont care.
Ive seen articles on this forum dating back from 2018 and 2019 but nothing since. Is this feature implemented and i missed it?

I need a sensor, lets say endstop. when triggered to send out a message to email, or service to eventually make alarm go off.
i dont care about status updates so much but if we could tap into that from the outside would be nice too.

i would love to hear suggestions, idea's or a solution.
Thanks in advance!

@droftarts Thank you for the reply, that answers my question!

Hi Guys,

I have a Large scale printer where i use 4x Nema42 motors on the Z axis. These beast have their own drivers controlled with step and direction via 4x 1XD.
Now i want to run these in Closed Loop mode via the Duet system. My question is; can i run the duet encoder on the 1HCL and run the step and direction on the 1XD or does the motor need to be connected to the 1HCL as well?

.
PS: if someone knows a closed loop motor + driver combo capable of 25+ Nm of torque (Nema34 or 42) let me know!

PS2: does anyone know if i can remove the back plate of the motor safely or is this holding something back?

PS2: if someone knows a closed loop motor + driver combo capable of 25+ Nm of torque (Nema34 or 42) let me know!

@T3P3Tony Thank you! i think this is the way, i didnt think about the Deamon file. i'm going to try it out and update this thread!