Unintentional axis movement

kerembyl

Hello,

In some cases Y axis is moving certain amount unintentionally. I use three-point manual bed leveling and nozzle travels 3 points respectively.

Here the coordinates of those points are:
[“X30 Y30”, “X270 Y30", “X170 Y300”]

First move: G1 X30 Y30 (No problem)
Second move: G1 X270 Y30 (X goes to 270 and Y supposed to stay still but it moves anyway. It moves approximately 3-4 milimeters in positive direction.)

All movements are done in absolute cartesian coordinate system.
Hardware: Duet2 Wifi
Firmware: 2.03beta3

What would cause this?

Thanks in advance.

My configuration:

; General preferences

M111 S0 ; Debugging off
G21 ; Work in millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X330 Y330 Z330 S0 ; Set axis maxima

; Endstops
M574 S0 ; Define active low and unused microswitches
M574 X1 Y1 Z0 S1 ; Define active high microswitches
M558 P5 X0 Y0 Z1 H10 F120 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
G31 X0 Y0 Z0 P10
M557 X30:310 Y0:250 S50 ; Define mesh grid
M581 E0 S0 T3 C0
M581 E0 S1 T4 C0
G29 S2

; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S1 ; Drive 1 goes forwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X256 Y256 Z256 E256 I0 ; Configure microstepping without interpolation
M92 X1280 Y1280 Z10240 E2544 ; Set steps per mm
M566 X900 Y900 Z10 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X18000 Y18000 Z1000 E1200 ; Set maximum speeds (mm/min)
M201 X1500 Y1500 Z100 E2000 ; Set accelerations (mm/s^2)
M906 X1700 Y1700 Z1800 E800 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Heaters
M143 S380 ; Set maximum heater temperature to 380C
M305 P0 T100000 B4623 C9.264103e-8 R4193 ; Set thermistor + ADC parameters for heater 0
; There are two types of thermistors in the field on P1. Setting it via hw_version check
M305 P2 T100000 B4623 C9.264103e-8 R4193
M307 H3 A-1 C-1 D-1
M141 H2

; Tools
M563 P0 D0 H1 ; 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

; Network
M550 Pmachina ; Set machine name
M551 Ppass ; Set password
M552 S0 ; Enable network
M586 P0 S1 ; Enable HTTP
M586 P1 S1 R21 T0 ; Enable FTP
M586 P2 S0 ; Disable Telnet

; Fans
M106 P0 S1 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H2 T50 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H2 T50 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 S0

; Custom settings are not configured
M501

Veti

lets start of with the first thing. there is a M208 before the M584

See
https://duet3d.dozuki.com/Wiki/Gcode#Section_M584_Set_drive_mapping

Order dependence

M584 must come earlier in config.g than any M350 and M906 commands. If it creates new axes, it must also be earlier than any M92, M201, M203, M208, M350, M566, M574 , M667 and M669 commands.

Veti

@kerembyl said in Unintentional axis movement:

M501 ; Check config override file

also it makes sense that this should be the last command in your config. not one of the first.

kerembyl

@veti said in Unintentional axis movement:

M584 must come earlier in config.g than any M350 and M906 commands. If it creates new axes, it must also be earlier than any M92, M201, M203, M208, M350, M566, M574 , M667 and M669 commands.

I fixed the things you mentioned, problem is still there. Thank you for correction though.

Veti

if you move back to G1 X30 Y30. does it return to the same place as the original G1 X30 Y30 ?

droftarts

Is any axis compensation applied? I'm thinking more of the M556 orthogonality type. Possibly in homeall.g or bed.g?

Ian

kerembyl

@droftarts neither both of them have M556. There is no axis compensation.

@Veti Error is not consistent so i could not experiment that.

Veti

can you post a picture of your printer?

kerembyl

@veti If you tell me what exactly do you want to see i can help you better. Because product is commercial and under development.

Veti

is the movement for x and y independent?

what do the u and v axis do?

kerembyl

@veti In order to prevent confusion because of U and V axis, i edited first post and submitted simpler config file. This belongs to another device which runs on same hardware and firmware and problem still exists. What i mean is it is not relevant to creating additional axes.

X and Y axes are independent for sure. They are driven by seperate stepper with no mapping applied to each other.

Veti

does the y stepper motor actually move when doing the move from 30 to 270?

kerembyl

@veti yes from x30 to x270 it moves.

Veti

and you ruled out any mechanical issue? like moving the head manually when the duet is off to see if the movement happens as well?

without axis compensation there should be no movement on the y motor.
can you also post the config-overwrite

kerembyl

I ruled out all mechanical issues, all of our devices have this problem.

config-overwrite.g contains only PID and BL Touch parameters.

Oddly enough, this is not happening while printing. Because dimensions are true.

; Heater model parameters
M307 H0 A90.0 C700.0 D10.0 S1.00 B1
M307 H1 A435.6 C268.1 D12.2 S0.27 B0
M307 H2 A340.0 C140.0 D5.5 S1.00 B0
M307 H4 A340.0 C140.0 D5.5 S1.00 B0
M307 H5 A340.0 C140.0 D5.5 S1.00 B0
M307 H6 A340.0 C140.0 D5.5 S1.00 B0
M307 H7 A340.0 C140.0 D5.5 S1.00 B0
; Z probe parameters
G31 T1 P10 X0.0 Y0.0 Z1.50
G31 T3 P500 X0.0 Y0.0 Z0.70
G31 T4 P500 X0.0 Y0.0 Z0.00

MrsDelish

This movement only happens when you probe your bed? If that is the case there is probably a probe offset(G31) in Y set somewhere, since the i.e:
G30 X100 Y100 uses position of probe(nominal tool holder position & probe offset) , where as
G1 X100 Y100 uses active tool position(nominal tool holder position & tool offset).
Check your config.g, homeX/Z/Y.g and Bed.g for any G31 with a XY value or G10 tool offset in XY.

Veti

i dont see anything in the config that would explain that.
just to rule out any firmware problem please update to the stable 2.03

kerembyl

@mrsdelish It also happens on a device which employs manual bed leveling. (without probe)

kerembyl

@dc42 Do you have any idea about that?

dc42

@kerembyl said in Unintentional axis movement:

Firmware: 2.03beta3

Beta versions of firmware are not supported once a later beta or (as in this case) the corresponding full release has been published. So you should upgrade to 2.03 (final release) or 2.04RC1 and test again.