RRF3.01-RC2 CoreXY Movement differences
-
In RRF2 you had:
M574 X1 Y2 S0 ; Set active low endstops
In RRF3 you have:
M574 X1 S1 P"!xstop" ; configure active-low endstop for low end on X via pin xstop
M574 Y1 S1 P"!ystop" ; configure active-low endstop for low end on Y via pin ystopYou have the Y endstop configured at the high end of the axis in RRF2, but the low end in RRF3.
-
If I make any changes to the M574 settings for X\Y, I'm then unable to home an axis with an
"G32 X\Y
Error: Failed to enable endstops"Using the settings as per my config file, I'm able to home the X\Y axes, but I'm only able to home Z, by leaving the head at the 0,0 position, where normally I would Z home at the bed centre (X150 Y150).
After I've managed to have some form of homing, If I then try any further moves, using DWC, I'm getting weird movements, with the head moving in the X axis, while I've issued a movement in the Y axis only ??
-
@Dr_Ju_Ju It sounds rather like one of you XY motors is moving in the wrong direction or maybe it's not moving at all. Did you change anything else apart from firmware? Did you disturb any of the wiring? Suggest you go back to basics and test motor movement as per this - https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCoreXYPrinter
-
@Dr_Ju_Ju The problem reminds me of this thread, maybe it is worth a read?
-
Nothing has changed physically from the RRF2 system to this RRF3.01 system, all the wiring is correct & working (yes I have tested, I'm an electronics engineer so know what I'm doing), & apart from these weird moving issues, everything else appears to be working ok, i.e. heaters & fans \ lights etc. are all configured(ish) & working with just some minor tweaks needed e.g. PID tuning, speeding things up etc...
If I physically move the head to the 'opposite' motion ends, (motors powered off) then home that axis, it behaves as I would expect, i.e. travels in a straight line to its relative homing end-stop. Which for a CoreXY, in its simplest form, the motors (both), are being driven in the correct direction and working as expected !!
-
@Dr_Ju_Ju Long shot; what version of RRF2 were you on? There was a change in the default direction of one axis a looooong time ago, can’t remember exactly when.
Ian
-
I was on the latest 2.05.1 \ DWC 2.0.7 on Duet Ethernet 1.02 or later
Board ID: 08DGM-95BNL-MGPSJ-6J1F2-3SD6L-9JZHXI'm interested in the new conditional stuff, so went to the latest RC, to at least try & get things going....
Julian
-
@droftarts said in RRF3.01-RC2 CoreXY Movement differences:
@Dr_Ju_Ju Long shot; what version of RRF2 were you on? There was a change in the default direction of one axis a looooong time ago, can’t remember exactly when.
Ian
@droftarts For info, that was RRF 1.19 whereby on a CoreXY, the direction of the Y axis (beta) motor changed.
-
@Dr_Ju_Ju said in RRF3.01-RC2 CoreXY Movement differences:
If I make any changes to the M574 settings for X\Y, I'm then unable to home an axis with an
"G32 X\Y
Error: Failed to enable endstops"Try again, this is working for other people. You need
M584 Y2 not M584 Y1M574 Y2 not M574 Y1. -
@dc42 said in RRF3.01-RC2 CoreXY Movement differences:
M584 Y2 not M584 Y1
Now I'm really confused, Why would I need Y2 in M584, as that setting came from the web configurator, & other examples I've seen ???
Julian
-
Sorry, I meant M574.
-
You commented out the number/maxima and also had the y range backwards vs your old one.
;M208 X0:300 Y300:0 Z0:300 ; Set axis minima:maxima
The y should be Y0:300 not Y300:0.
-
Thank you David, I now have movement as I'd expect'ish, even if the Y axis moves 'negatively', which I suspect will be corrected when I update the axis limits....
Julian
-
Which version of RRF2 were you using before you upgraded to RRF3?
-
David,
@Dr_Ju_Ju said in RRF3.01-RC2 CoreXY Movement differences:
I was on the latest 2.05.1 \ DWC 2.0.7 on Duet Ethernet 1.02 or later
Board ID: 08DGM-95BNL-MGPSJ-6J1F2-3SD6L-9JZHX& yes Nuramori, I was playing with the axis limits to try & get things working in the right direction...