Z traveling wrong direction during printing
-
So after coming along a great deal, I finally melted some plastic. The first layer went fantastic then z went the wrong direction.
I have a duet 3 mini 5+ WiFi. CoreXY configuration.
It homes correctly. (Finally)
I used the prusa slicer to make the print.
Should I put my config.g file(below) and the homeall in the slicer startup gcode?
I switched to advanced in the slicer so I could see all the menu items. I did not see any setting that controls the Z direction. Or even the printer configuration itself…
Configuration file for Duet 3 Mini 5+ (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.16 on Fri Aug 11 2023 17:43:56 GMT-0400 (Eastern Daylight Time); General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"CoreXY" ; set printer name
M669 K1 ; select CoreXY mode; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S1 ; enable Telnet; 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 forkwards
M569 P0.3 S1 ; physical drive 0.3 goes forwards
M569 P0.4 S1 ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2:0.3 E0.4 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E409.00 ; set steps per mm
M566 X600.00 Y600.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X3000.00 Y3000.00 Z100.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X300 Y300 Z380 S0 ; set axis maxima; Endstops
M574 X1 S1 P"!io5.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io5.in
M574 Y1 S1 P"!io6.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io6.in; Z-Probe
M950 S0 C"io3.out" ; create servo pin 0 for BLTouch
M558 P9 C"io3.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X150 Y150 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; define mesh grid; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
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 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1
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 S285 ; set temperature limit for heater 1 to 285C; Fans
M950 F0 C"out6" Q500 ; create fan 0 on pin out6 and set its frequency
M106 P0 S1 H1 T45 ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"out5" Q500 ; create fan 1 on pin out5 and set its frequency
M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off; Tools
M563 P0 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; Custom settings are not defined
-
@TOFUATSU You must be homing Z in the wrong direction. Probably you have your X end stop or probe set to the low end of the axis when it should be the high end or vice versa.
-
Post your homeall.g and homez.g
After homing are you able to jog the z axis correctly? As in Z+ makes the nozzle and bed farther apart? Z- makes it closer together?
-
@Phaedrux
Yes it goes correctly when I manually move it.However, this is a coreXY machine and I feel like the z motors should be set to run backwards. I have them set to run forwards.
It weird, I am switching out a duet 2 wifi that I accidentally fried switching to a CRTouch. Other than that it’s all the same everything.
I tried to reverse everything, motors and the z commands in all the home.g files, but it homed the wrong way.
Would switch the poles on the motor work?
-
switching the motor wiring is the same effect as changing the direction of rotation in the config.
You shouldn't change the homing file. Your Z moves need to follow Z- moves bed and nozzle closer together and Z+ moves them farther away. That's just the way it is. The only thing you have control over is where the endstops are located, either high end or low end of travel and how that is set in the config, and finally the direction of rotation of the motors. You can flip that one way or the other so that the Z- and Z+ travel in the expected direction.
-
Post your homing files.
-
@Phaedrux ;
I just ran this with successhomez.g
; Called to home the Z axis
;
G91 ; Relative positioning
G1 H2 Z10 F10000 ; Lift Z relative to current position
M280 P0 S10 ; Extend the probe pin
G90 ; Use absolute positioning
G1 X143 Y155 F6000 ; Go to the probe point
G30 ; Home the Z axis by probing the bed
G91 ; Use relative positioning
G1 Z5 F100 ; lift Z relative to current position
G90 ; absolute positioning
M280 P0 S90 ; Retract probe pin
; -
@Phaedrux said in Z traveling wrong direction during printing:
switching the motor wiring is the same effect as changing the direction of rotation in the config.
You shouldn't change the homing file. Your Z moves need to follow Z- moves bed and nozzle closer together and Z+ moves them farther away. That's just the way it is. The only thing you have control over is where the endstops are located, either high end or low end of travel and how that is set in the config, and finally the direction of rotation of the motors. You can flip that one way or the other so that the Z- and Z+ travel in the expected direction.
This is how mine is going. -Z moves the bed up, toward the nozzle. +Z moves it down.
Gonna try a different slicer
-
Can you share the gcode file you're printing?
-
@Phaedrux it seems that I have some setting in the prusa slicer messed up. The Cura sliced it and it travels correctly
