x moves with z - crazy
-
hey
I had a short ground in driver 3 of my z axis.
After I fixed this problem, everything is alright, BUT when I move z axis, the x axis is also moving. Is that a normal problem after a short ground?I switched the shorted driver to a driver on the expansion board - but same problem.
When I move x, z axis is not moving..
Is my Duet broken?R.G.
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Aug 02 2021 16:15:35 GMT+0200 (MitteleuropƤische Sommerzeit) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Duet 3" ; set printer name M552 S1 P192.168.2.108 ; Wifi G4 S4 ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S0 ; physical drive 0.2 goes forwards M569 P1.2 S0 ; physical drive 0.2 goes forwards M569 P0.4 S0 ; physical drive 0.2 goes forwards M569 P0.5 S0 ; physical drive 0.2 goes forwards M569 P121.0 S1 ; physical drive 121.0 goes forwards M569 P122.0 S1 ; physical drive 122.0 goes forwards M569 P123.0 S1 ; physical drive 123.0 goes forwards M584 M584 X1.1 Y0.0:0.1 Z0.2:1.2:0.4:0.5 E121.0:122.0:123.0 ; set drive mapping M350 X16 Y16 Z16 E16:16:16 I1 ; configure microstepping with interpolation M92 X160.00 Y160.00 Z640.00 E409.00:409.00:409.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E3000.00:3000.00:3000.00 ; set maximum instantaneous speed changes (mm/min) M203 X12000.00 Y12000.00 Z6000.00 E6000.00:6000.00:6000.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z300.00 E250.00:250.00:250.00 ; set accelerations (mm/s^2) M906 X1300 Y1300 Z2500 E1000:1000:1000 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X-10 Y-10 Z10 S1 ; set axis minima M208 X1030 Y1030 Z1030 S0 ; set axis maxima ; Endstops M574 X2 S1 P"^io3.in" ; configure active-high endstop for high end on X via pin ^io3.in M574 Y2 S1 P"^io1.in" ; configure active-high endstop for high end on Y via pin ^io1.in M574 Z1 S1 P"^io2.in" ; configure active-high endstop for low end on Z via pin ^io2.in ; Z-Probe M558 P0 H-5 F300 T300 ; disable Z probe but set dive height, probe speed and travel speed M556 S50 X0 Y0 Z70 ; set orthogonal axis compensation parameters M557 X10:10 Y10:10 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 B0 R0.243 C586.2 D33.87 S1.00 V0 ; disable 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"121.temp0" Y"thermistor" T100000 B4138 ; configure sensor 1 as PT1000 on pin 121.temp0 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 S250 ; set temperature limit for heater 1 to 250C M308 S2 P"122.temp0" Y"pt1000" R2200 ; configure sensor 2 as PT1000 on pin 122.temp0 M950 H2 C"122.out0" T2 ; create nozzle heater output on 122.out0 and map it to sensor 2 M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H2 S250 ; set temperature limit for heater 2 to 250C M308 S3 P"123.temp0" Y"pt1000" R2200 ; configure sensor 3 as PT1000 on pin 123.temp0 M950 H3 C"123.out0" T3 ; create nozzle heater output on 123.out0 and map it to sensor 3 M307 H3 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H3 S250 ; set temperature limit for heater 3 to 250C ; Fans M950 F0 C"121.out1" Q500 ; create fan 0 on pin 121.out1 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"121.out2" Q500 ; create fan 1 on pin 121.out2 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"122.out1" Q500 ; create fan 2 on pin 122.out1 and set its frequency M106 P2 S1 H-1 ; set fan 2 value. Thermostatic control is turned off M950 F3 C"122.out2" Q500 ; create fan 3 on pin 122.out2 and set its frequency M106 P3 S1 H2 T45 ; set fan 3 value. Thermostatic control is turned on M950 F4 C"123.out1" Q500 ; create fan 4 on pin 123.out1 and set its frequency M106 P4 S1 H-1 ; set fan 4 value. Thermostatic control is turned off M950 F5 C"123.out2" Q500 ; create fan 5 on pin 123.out2 and set its frequency M106 P5 S1 H3 T45 ; set fan 5 value. Thermostatic control is turned on M950 F6 C"out4" Q500 ; create fan 6 on pin out4 and set its frequency M106 P6 S1 H-1 ; set fan 6 value. Thermostatic control is turned off M950 F7 C"out5" Q500 ; create fan 7 on pin out5 and set its frequency M106 P7 S1 H T45 ; set fan 7 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 ; define tool 0 G10 P0 X30 Y28.25 Z45 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P1 D1 H2 F2 ; define tool 1 G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C M563 P2 D2 H3 F4 ; define tool 2 G10 P2 X0 Y0 Z0 ; set tool 2 axis offsets G10 P2 R0 S0 ; set initial tool 2 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss -
@barbarossa-cologne
Switching drivers -- same problem
-
@barbarossa-cologne
M584 M584 X1.1 Y0.0:0.1 Z0.2:1.2:0.4:0.5 E121.0:122.0:123.0 ; set drive mappingTwo M584 commands on the same line. Not saying that's it, but who know what it's doing.
-
@kb58 The code listing suggests that it was generated by the configuration app. I've read several threads where someone's used the results and it didn't work as expected. I suggest going through that code line by line, using the Gcode Directory, https://duet3d.dozuki.com/Wiki/Gcode#main and double checking all the M commands and whether their parameters make sense on your setup.
-
@kb58
Before I had the short ground, everything was fine. I try with changing the m584...
Would be to easy
Same problem with one m584 command..
Thank you -
It's crazy because the x driver is in a different board. And it doesn't care on which driver.
Y is working completely fine (and not moving when z moves). -
@barbarossa-cologne this behaviour is caused by the M556 command in your config.g file.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 do you mean in row 44?
What is wrong there / just delete them ?
It's curios because this behaviour first shows up after short ground..
Hopefully it's the reason -
@barbarossa-cologne the M556 line says that you have axis skew and that you want to compensate for it, by moving X too when Z changes. It's unusual to use skew compensation, and in any case the amount of compensation specified in your M566 command is much too large to be reasonable. I suggest you delete that line.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 ok thanks for this information. It's made by the config tool and I'm not a professional, yet. Sry
Nice to have such a good support -
@barbarossa-cologne said in x moves with z - crazy:
It's made by the config tool
You would have had to check the box to enable it in the tool
"Enable Orthogonal Axis Compensation"
