Need help diagnosing bad stepper output signal on Duet 3
-
@Noah said in Need help diagnosing bad stepper output signal on Duet 3:
M350 X16 Y16 Z16 E16:16:16 I1 ; configure microstepping with interpolation
M92 X160.00 Y160.00 Z1600.00 E1600.00:1600.00:873.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z30.00 E30.00:30.00:1800.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z1800.00 E1800.00:1800.00:3000.00 ; set maximum speeds (mm/min)
M201 X1600.00 Y1600.00 Z100.00 E100.00:100.00:2000.00 ; set accelerations (mm/s^2)
M906 X1200 Y1200 Z800 E800:800:950 I30 ; set motor currents (mA) and motor idle factor in per centCan you remove the multiple E values from this section? You only have a single extruder, so there should only be a single E value.
-
Can you send M98 P"config.g" and report the results?
-
The rrf config tool originally gave me that setup
When I manually moved things from
M350 X16 Y16 Z16 E16:16:16 I1 to M350 X16 Y16 Z16:16:16 E16 I1
and so on for all the motor settings the bed would no longer home and the printer wouldn't function so I had to switch everything back -
@Phaedrux said in Need help diagnosing bad stepper output signal on Duet 3:
P"config.g"
M98 P"config.g"
Error: in file macro line 21: M350: array too long, max length = 1
Error: in file macro line 22: M92: array too long, max length = 1
Error: in file macro line 23: M566: array too long, max length = 1
Error: in file macro line 24: M203: array too long, max length = 1
Error: in file macro line 25: M201: array too long, max length = 1
Error: in file macro line 26: M906: array too long, max length = 1
Warning: Macro file config-override.g not found -
I just tried putting back these settings
; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M569 P0.4 S1 ; physical drive 0.4 goes forwards
M569 P0.5 S1 ; physical drive 0.5 goes forwards
M584 X0.0 Y0.1 Z0.2:0.3:0.4 E0.5
M671 X-30.109:146.1:322.309 Y-10.413:317.797:-10.413 S50
M350 X16 Y16 Z16 E16:16:16 I1
M92 X160.00 Y160.00 Z1600.00:1600.00:1600.00 E873.00
M566 X1200.00 Y1200.00 Z30.00:30.00:30.00 E1800.00
M203 X18000.00 Y18000.00 Z1800.00:1800.00:1800.00 E3000.00
M201 X1600.00 Y1600.00 Z100.00:100.00:100.00 E2000.00
M906 X1200 Y1200 Z800:800:800 E950 I30
M84 S30Same result again. The triple Z bed no longer homes or responds to G32
-
If you run M98 P"config.g" again and it gives the same result as before, I think it's because you have multiple factors when you don't need them. If you tell the firmware the Z is 0.2:0.3:0.4 it knows to use one setting for all 3 steppers.
Follow my adventures in 3D Printing, laser cutting and electronics. https://linktr.ee/Rushmere3D
-
@Noah said in Need help diagnosing bad stepper output signal on Duet 3:
M350 X16 Y16 Z16 E16:16:16 I1 to M350 X16 Y16 Z16:16:16 E16 I1
The Z axis only needs a single entry as well. It's only when you have multiple extruder axis that each axis needs to be defined. The other axis with multiple motors all use the same settings since they aren't independent.
So remove the multiple Z values as well.
-
@Rushmere3D JYNX again!
-
@Phaedrux haha
-
ok, haha
thank you so much for dealing with the noob over here. I corrected all of the lines after m671 to show only one value for X,Y,Z,E
I was just copying what the RRF config tool gave me for the multiple E motors since it did not have any option to add extra Z motors.
Z homing and G32 working perfect again, and I only have one data point for motor 5 now
Fingers crossed. -
as soon as the hotend heats up and it will let me send extrude and retract commands, I'll let you know if the ext motor is behaving any differently now
-
Hahahaha Phaedrux & Rushmere You guy are amazing!!!
wish I had asked a little sooner for someone to review my code... I really caused myself a couple of days of grief over here... I have good motor function on all motors now.
Now, I am off to tune my extrusion steps and try a print!|Thank You both soooooo much
Noah
-
Proper config for others refernce
; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M569 P0.4 S1 ; physical drive 0.4 goes forwards
M569 P0.5 S1 ; physical drive 0.5 goes forwards
M584 X0.0 Y0.1 Z0.2:0.3:0.4 E0.5
M671 X-30.109:146.1:322.309 Y-10.413:317.797:-10.413 S50
M350 X16 Y16 Z16 E16 I1
M92 X160.00 Y160.00 Z1600.00 E873.00
M566 X1200.00 Y1200.00 Z30.00 E1800.00
M203 X18000.00 Y18000.00 Z1800.00 E3000.00
M201 X1600.00 Y1600.00 Z100.00 E2000.00
M906 X1200 Y1200 Z800 E950 I30
M84 S30 -
Glad you got it sorted.
-
I still do have the
Error: in file macro line 21: M350: array too long, max length = 1but only for the M350 line
That's strange... what doesn't it like about my M350 X16 Y16 Z16 E16 I1
-
Please upload your actual config.g file
