Quantcast
Channel: Reprap Forum - CoreXY Machines
Viewing all articles
Browse latest Browse all 550

Struggling with X & Y motion in my Duet-powered CoreXY [SOLVED] (7 replies)

$
0
0
I'm getting close to completing my new CoreXY printer (G&C Printer) and this morning powered it up for the first time.

All seems fine apart from the X and Y motion, which is giving me a headache. No matter what I do with the M569 commands in the Duet's config.g file, I can't get them to move properly. Here are the relevant lines in the config.g file:
; Movement section

M569 P0 S0							; 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
M569 P4 S1							; Drive 4 goes forwards
Ignore all the bits about "Drive n goes forwards" - I'll retype those when it works.

In this current configuration, the carriage will move correctly in the Y axis, but the X axis is reversed. Changing the M569 instruction to fix this is not so simple, as in CoreXY both motors work together to move in a straight line in either axis. This means that changing the direction of 1 motor just changes the error. I've tried reading all the documentation about M569, but that's not particularly helpful when considering CoreXY. I've had to assume that P0 is the X motor, and P1 the Y motor. P2 seems to affect the Z motor, and that's working properly.

I've looked at Filipe's (the designer's) config.g file, and that's only slightly different - he had P0 S1 and P1 S0, but that just changed the error around for me. The result was that the carriage moved correctly in the X axis, but was reversed in the Y. I've also tried P0 S0/P1 S0 and P0 S1/P1 S1, but that just made it worse.

Maybe the CoreXY code needs "reverse X axis" and "reverse Y axis" commands! (or maybe these already exist and I've missed them in the G code lists)

Can anyone offer some guidance in the meantime?

Viewing all articles
Browse latest Browse all 550

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>