CoreXY only one motor moves at time
I just run the reprap configurator to set my printer in coreXY mode but it dont work as expected.
When i try to move with this command :
G1 X10 F5000 S2
Only one motor moves.
If i use "G1 X10 F5000 S2", the other motor moves, but still only one.
I tried both command "M667 S1" and "M669 K1" but none of them do what i want.
I an probably doing something wrong but what ?
Here is my config.g :
; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
; generated by RepRapFirmware Configuration Tool v2 on Wed Jul 10 2019 22:12:37 GMT+0200 (heure d’été d’Europe centrale)
; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
;M667 S1 ; Select CoreXY mode
M550 P"Hyper Cube La Muerte" ; Set machine name
M552 S1 ; Enable network
M587 S"HUIT-FILLES" P"Muahahahaha!!!" ; Configure access point. You can delete this line once connected
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet
M569 P0 S1 ; Physical drive 0 goes forwards
M569 P1 S1 ; Physical drive 1 goes forwards
M569 P2 S1 ; Physical drive 2 goes forwards
M569 P3 S1 ; Physical drive 3 goes forwards
M350 X256 Y256 Z256 E256 I0 ; Configure microstepping without interpolation
M92 X1280.00 Y1280.00 Z25600.00 E13395.20 ; Set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E3000.00 ; Set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; Set accelerations (mm/s^2)
M906 X1000.00 Y1000.00 Z1000.00 E800.00 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 Z300 S0 ; Set axis maxima
M574 X1 Y1 Z1 S3 ; Set endstops controlled by motor load detection
M915 X Y S5 R2
M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; Set Z probe trigger value, offset and trigger height
M557 X100:200 Y100:200 S20 ; Define mesh grid
M307 H0 B0 S1.00 ; Disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B3950 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S150 ; Set temperature limit for heater 0 to 150C
M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C
M106 P0 S0 I0 F500 H T45 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
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
; Automatic saving after power loss is not enabled
; Custom settings are not configured
M501 ; Load saved parameters from non-volatile memory
DocTrucker last edited by DocTrucker
It's been deprediated. Use M669
Edit: Sorry, just seen you were trying that. Reading on!
DocTrucker last edited by DocTrucker
What firmware version are you runming? Assuming at least 2.03? Is firmware version 1.21 mentioned in the config file just something from the configurator?
It from configurator.
I use 2.01 Beta 1
I try 2.03 tonight.
DocTrucker last edited by
It's been a while since I played with a Core XY, but the documentation says the following about M667:
This command is deprecated in RRF 2.03 and later. Use M669 instead.
I'm not sure if it is a polite request to not use it or saying M667 won't work on 2.03 or later. Likewise without checking the release notes I'm not sure when M669 was enabled.
The documentation is very light on how to use the motor movement coefficients, how to get the matrix, and what are the default values.
When configured with M669 K1 what does a plain M669 command over the duet web control g code panel return?
@donpi It's doing exactly what it's supposed to do. The S2 and S1 parameters are for testing the direction of each individual motor. Once you have established that the axes move in the correct directions, just use the G1 Xnnn Fnnn commands.
Not sure, I can't try until tonight ( cause I'am at work )
But if it is the case, I tell you.
gtj0 last edited by
I'm just as stupid. I changed over to a CoreXY setup yesterday and spent quite a bit of time trying to figure out what the issue was. The documentation for the S/H parameter isn't exactly clear.
@deckingman You are great!
Everything is ok for now