Solved M584 help needed
-
So guys I have a question I have a 6HCMB and I am installing it on a core XY. And I’m running into some issues with M584. I am running dual X and dual Z and a single y. The problem is once I have homed everything X moves fine, but when I tried to move the Y axis the Z motors also move. The M5 84 code that I have entered is this.
M584 X0.0:0.1 Y0.2 Z0.4:0.5 E0.3 
Any thoughts as to why the X axis moves when I am trying to move the Y?
-
Enter M669 from the DWC Console and see what it reports.
These are mine but I had to do some trial-and-error to get the right values for X and Y.
M669 X-1;1;0 Y-1;-1;0 Z0;0;1 ; CoreXY via matrix values (the ; need to be : but posting with them is messed up)
I believe the X and Y values will always be of the form #:#:0 where the #s are either 1 or -1.
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
Do you have M669 K1 in your config already?
-
@phaedrux no
-
-
Then add it near the start of config.g to set the kinematics type to core xy.
-
@phaedrux actually yes I do. Says m669 k1. Nothing after that
-
@phaedrux What should it say after K-1
-
@jlee73 said in M584 help needed:
What should it say after K-1
I don't know what you mean by k-1
Are you sure you have the motors connected to the right drivers?
You can also try the explicit matrix shown by @fcwilt -
@phaedrux the line says m669 k1. Nothing after that
-
Yes, K1 is corexy mode. It doesn't need more after that. And by the looks of your screen shot when you sent M669 by itself it does report that it's in corexy mode. So that seems correct. Which is why I ask if the motors are all connected to the expected drivers.
@jlee73 said in M584 help needed:
The problem is once I have homed everything X moves fine, but when I tried to move the Y axis the Z motors also move.
How much z movement are you seeing exactly?
Can you post your homing files? Your entire config.g would also be good. And for good measure can you send M122 and M98 P"config.g" in the gcode console tab and copy and paste the text here?
-
M98 P"config.g"
Error: in file macro line 14: M540: invalid MAC address
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Debugging enabled for modules:
Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14) Display(15) LinuxInterface(16) CAN(17)
Warning: Macro file config-override.g not found -
; Configuration file for Duet 3 (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Apr 26 2022 14:49:38 GMT-0600 (Mountain Daylight Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Beast" ; set printer name
M669 K1 X1:1:0:0 Y1
0:-1 Z0:0:1:0 ; select CoreXY mode; Network
M551 P"Neiljess18" ; set password
M540 P0.0.0.0 S1 ; set custom MAC address
M552 P192.168.1.129 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable 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 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:0.1
M584 Y0.3
M584 Z0.4:0.5
M584 E0.2 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X400.00 Y400.00 Z3.00 E611.15 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X2500 Y2500 Z2500 E2000 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 X965 Y400 Z300 S0 ; set axis maxima; Endstops
M574 X1 S1 P"io0.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io0.in
M574 Y1 S1 P"io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io1.in
;M574 Z2 S2 ; configure Z-probe endstop for high end on Z; Z-Probe
M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
M558 P9 C"io7.in" 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 X15:215 Y15:195 S20 ; define mesh grid; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950 ; 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 S1.00 ; 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"temp1" Y"thermistor" T100000 B4138 ; 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 S280 ; set temperature limit for heater 1 to 280C; Fans
M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on; 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
G21
M111; Miscellaneous
M501 ; load saved parameters from non-volatile memory
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss -
@phaedrux
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Apr 26 2022 14:49:38 GMT-0600 (Mountain Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-970 Y-405 F1800 ; move quickly to X or Y endstop and stop there (first pass)
G1 H1 X-970 ; home X axis
G1 H1 Y-405 ; home Y axis
G1 X5 Y5 F6000 ; go back a few mm
G1 H1 X-970 F360 ; move slowly to X axis endstop once more (second pass)
G1 H1 Y-405 ; then move slowly to Y axis endstop
G90 ; absolute positioning
G1 X15 Y15 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
@phaedrux
; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Apr 26 2022 14:49:38 GMT-0600 (Mountain Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-970 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000 ; go back a few mm
G1 H1 X-970 F360 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning -
@jlee73 said in M584 help needed:
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-970 Y-405 F1800 ; move quickly to X or Y endstop and stop there (first pass)So as part of your homing files it lowers the Z axis for clearance before moving in XY. Is that what you're seeing? if so, this is normal. If not, please post a video.
-
@phaedrux
; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Apr 26 2022 14:49:38 GMT-0600 (Mountain Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 Y0 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y5 F6000 ; go back a few mm
G1 H1 Y0 F360 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F6000 ; lower Z again
G90 ; absolute positioning -
@phaedrux
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Tue Apr 26 2022 14:49:38 GMT-0600 (Mountain Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X15 Y15 F6000 ; go to first probe point
G30 ; home Z by probing the bed; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
No, once everything is homed on dwc, i then try ti use the move "y" by 1,10 or 50 buttons to move the y which is my hotend. when i do that the x axis also moves it should not move at all.
-
@jlee73 it has nothing to do w Z
