Problem with X axis going to side and extruder moving too fast

Phaedrux

Firmware version?

droftarts

@Duncan If nothing has changed on the printer, and these are new print jobs, I'd suspect a change in your slicer settings. Try printing an old job that you know works correctly.

If you have changed something, eg configuration or wiring, look at what you have changed.

Unfortunately, you haven't provided much information, so it's hard to diagnose. For what information to provide, see https://forum.duet3d.com/topic/5909/guide-for-posting-requests-for-help. Ideally, config.g and M122 report, as a minimum.

Ian

Duncan

Sorry for the missing information.

I haven't change anything, even slicer software is the same and old files are working wrong also.

Firmware version is 3.4.0. in a Duet 3 Mainboard 6HC with Toolboard 1LC with the hotend, extruder and 3D-Touch probe connected.

It's a cartesian printer.

Tomorrow I'll go to the place I have the printer and will upload config.cfg and M122 report.

The strange thing for me is that I was printing a lot of huge parts for a couple weeks... I change filament and put an old file again to print and starts failing suddenly.

I think tomorrow I will update firmware, what do you recommend? go for latest stable 3.5.4 or the last 3.6 RC3?

Phaedrux

@Duncan said in Problem with X axis going to side and extruder moving too fast:

go for latest stable 3.5.4 or the last 3.6 RC3?

I'd start with 3.5.4 and see if anything changes for you. 3.6 final won't be too long now.

Duncan

Hello,

this is my config and M122 results.

Anyway, I'm going to update now and test

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.2 (2022-09-13 15:17:43) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: 08DJM-9P63L-DJ3S0-7JTD4-3S86P-9AJM9
Used output buffers: 10 of 40 (18 max)
=== RTOS ===
Static ram: 152664
Dynamic ram: 95956 of which 0 recycled
Never used RAM 102052, free system stack 200 words
Tasks: NETWORK(ready,28.8%,252) ETHERNET(notifyWait,0.0%,453) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,8.4%,91) MAIN(running,62.2%,1101) IDLE(ready,0.6%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:03:07 ago, cause: power up
Last software reset at 2025-05-13 12:46, reason: User, GCodes spinning, available RAM 102052, slot 2
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,0
Step timer max interval 128
MCU temperature: min 19.0, current 34.4, max 34.5
Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 4, reads 56545, writes 14 timeouts 0
Driver 1: standstill, SG min 0, mspos 4, reads 56545, writes 14 timeouts 0
Driver 2: standstill, SG min 0, mspos 4, reads 56545, writes 14 timeouts 0
Driver 3: standstill, SG min 0, mspos 4, reads 56546, writes 14 timeouts 0
Driver 4: standstill, SG min 0, mspos 4, reads 56546, writes 14 timeouts 0
Driver 5: standstill, SG min 0, mspos 4, reads 56546, writes 14 timeouts 0
Date/time: 2025-05-15 07:30:27
Slowest loop: 2.37ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 0.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by 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 idle 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 idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0 sensor: no filament
=== CAN ===
Messages queued 1701, received 3843, lost 0, boc 0
Longest wait 2ms for reply type 6026, peak Tx sync delay 6, free buffers 50 (min 49), ts 939/938/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 3.99ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
= Ethernet =
State: active
Error counts: 0 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== Multicast handler ===
Responder is inactive, messages processed 0[config.g](/assets/uploads/files/1747287143373-config.g)

Duncan

Hello again,

I updated to 3.5.4, it seems to be all working but I'm trying to make the mesh for the bed with the tool and when I hit the option to start the mesh with G29

The printer moves really slow... like 0,5mm/sec, and I can't find where is the problem, because normal moves are ok, homing is ok and when I use G30 is also ok...

My new config.g is this:

; Configuration file for RepRapFirmware on Duet 3 Main Board 6HC
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.5.12 on Thu May 15 2025 08:40:59 GMT+0200 (hora de verano de Europa central)

; General
G90 ; absolute coordinates
M83 ; relative extruder moves
M550 P"BIGC3D" ; set hostname

; Accessories
M575 P1 S0 B57600 ; configure PanelDue support

; Network
M552 P0.0.0.0 S1 ; configure Ethernet adapter
M586 P0 S1 ; configure HTTP

; Wait a moment for the CAN expansion boards to become available
G4 S2

; Smart Drivers
M569 P0.0 S0 D2 ; driver 0.0 goes backwards (Y axis)
M569 P0.1 S0 D2 ; driver 0.1 goes backwards (Z axis)
M569 P0.2 S0 D2 ; driver 0.2 goes backwards (Z axis)
M569 P0.3 S0 D2 ; driver 0.3 goes backwards (X axis)
M569 P0.4 S0 D2 ; driver 0.4 goes backwards (Z axis)
M569 P0.5 S0 D2 ; driver 0.5 goes backwards (Z axis)
M569 P20.0 S1 D2 ; driver 121.0 goes forwards (extruder 0)

; Motor Idle Current Reduction
M906 I30 ; set motor current idle factor
M84 S30 ; set motor current idle timeout

; Axes
M584 X0.3 Y0.0 Z0.1:0.2:0.4:0.5 ; set axis mapping
M350 X32 Y32 Z32 I1 ; configure microstepping with interpolation
M906 X2800 Y4000 Z2800 ; set axis driver currents
M92 X213.883 Y213.883 Z1280 ; configure steps per mm
M208 X0:1100 Y0:1100 Z0:1000 ; set minimum and maximum axis limits
M566 X900 Y900 Z12 ; set maximum instantaneous speed changes (mm/min)
M203 X20000 Y20000 Z1000 ; set maximum speeds (mm/min)
M201 X1000 Y1000 Z200 ; set accelerations (mm/s^2)

; Extruders
M584 E20.0 ; set extruder mapping
M350 E16 I1 ; configure microstepping with interpolation
M906 E1000 ; set extruder driver currents
M92 E561.6 ; configure steps per mm
M566 E120 ; set maximum instantaneous speed changes (mm/min)
M203 E1200 ; set maximum speeds (mm/min)
M201 E250 ; set accelerations (mm/s^2)

; Kinematics
M669 K0 ; configure Cartesian kinematics
M671 X1115:1115:-15:-15 Y1360:-260:-260:1360 S0.5	; J- configuramos la posición de los husillos respecto el origen (0,0) de la cama (no de los finales de carrera)

; Probes
M558 K0 P9 C"20.io0.in" H5 F480 T100 ; configure BLTouch probe via slot #0
G31 P500 X-20 Y40 Z0.7 ; set Z probe trigger value, offset and trigger height
M950 S0 C"20.io0.out" ; create servo #0 for BLtouch

; Endstops
M574 X1 P"io2.in" S1 ; configure X axis endstop
M574 Y1 P"io1.in" S1 ; configure Y axis endstop
M574 Z1 P"io3.in+io4.in+io5.in+io6.in" S1 ; configure Z axis endstop

; Mesh Bed Compensation
M557 X50:1050 Y50:1050 S50:50 ; define grid for mesh bed compensation

; Sensors
M308 S0 P"temp3" Y"thermistor" T100000 B4725 ;C7.06e-8 ; configure sensor #0
M308 S1 P"20.temp0" Y"pt1000" ; configure sensor #1

; Heaters
M950 H0 C"out0" T0 ; create heater #0
M143 H0 P0 T0 C0 S120 A0 ; configure heater monitor #0 for heater #0
;M307 H0 R2.43 D5.5 E1.35 K0.56 B1 ; configure model of heater #0
M307 H0 A340 C2745.9 D25 S1.00 B0                               ; enable bang-bang mode for the bed heater and set PWM limit - OLD FIRMWARE 3.4.3
M950 H1 C"20.out0" T1 ; create heater #1
M143 H1 P0 T1 C0 S290 A0 ; configure heater monitor #0 for heater #1
;M307 H1 R2.43 D5.5 E1.35 K0.56 B0 S100 ; configure model of heater #1
M307 H1 R4.221 K0.860:0.000 D1.42 E1.35 S1.00 B0 V22.7 ;after PID configuration tool calibration

; Heated beds
M140 P0 H0 ; configure heated bed #0

; Fans
M950 F0 C"20.out2" ; create fan #0
M106 P0 S0 B0.1 H1 T50 ; configure fan #0
M950 F1 C"20.out1" ; create fan #1
M106 P1 S0 L0 X1 B0.1 ; configure fan #1

; Tools
M563 P0 S"toolzero" D0 H1 F0 ; create tool #0
M568 P0 X0 Y0 Z0 ; set custom offsets for tool #0
M568 P0 R0 S0 ; set initial tool #0 active and standby temperatures to 0C

; Miscellaneous
M564 H0
M302 P1

dc42

@Duncan slow movement is usually caused by the slice rinserting M201 and/or M203 commands into the GCode file. Configure your slicer not to do this. It is totally unnecessary for slicers to insert these commands because there are other parameters and commands to set speeds and accelerations for one particular print.

Duncan

@dc42 thank you, I located my mistake... the speed in M558 was T100 by default and I didn't change it... I put 10000 and now it's doing the mesh leveling.

After that I will try to print again my old files and see if the problem I was creating this thread about it's still existing or not.

Thank you!

Duncan

Hello,

I still have the problem, after update, change SD... no idea what's the problem... still going to the right and extruder moving so fast while it goes and return to print...

droftarts

@Duncan I'd think that some Gcode is being sent from somewhere, if the job is interrupted with this strange movement, but then returns to where it was after the interruption, without losing position.

I think you have a PanelDue connected? Try disconnecting that, and see if the printer runs correctly. It's possible the cable between the Duet and PanelDue is picking up interference, or something is pressing on the screen of the PanelDue and triggering a macro. What firmware version are you running on the PanelDue? Check the 'Setup' screen on the PanelDue.

Ian

Duncan

@droftarts Hello!
My paneldue was in 3.4.0, just updated to latest firmware.

I updated also Orca Slicer and I'm doing again the gcode files.

Also I recheck all wires and try to avoid any interferences between data and power...

So let's try again.

Thank you!

Duncan

Hello!
Last part was printed ok, so I put another one this morning and hope nothing fails again...

It's very strange because I really don't know what is or was the real problem...

Because of the updates I notice that the Tool 0 is not activated on power up and I have to press the "toolzero" in browser...

My last config.g is on my previous post... the line to activate the T0 is

M568 P0 R0 S0 ; set initial tool #0 active and standby temperatures to 0C

I also tried with the old line on my previous config.g

G10 P0 R0 S0 ; set initial tool #0 active and standby temperatures to 0C

But problem is the same... any ideas?

fcwilt

@Duncan

To activate tool zero you need a T0 command - you can put it after the other tool commands in config.g if you want.

Frederick