Sorry but FW 1.2.1 is a pain in the ass for corexy users
-
Ok apologies for the rant, I guess i'm becoming a dinosaur and don't like changes but It's a pain the ass. Why the need to set S2 all over the .g files?
Also after a print finishes, I need to home again otherwise I can't jog the print head anywhere. Surely we should know the position once a print finishes.
I do love you guys but not sure why the changes are implemented the way they are for corexy....
-
@totalitarian sorry you are finding it a pain. It was a feature request to stop people damaging their printers and after you have edited the homing files once you should not need to do so again. If you have a M84 in your end gcode then that might be why you need to re-home after a print finishes. Once the motors are turned off the printer cannot with any certainty know where they are so it assumes it is unhomed.
-
M564 H0 is your friend. Just put it somewhere in your config.g
-
@ampex_fhm said in Sorry but FW 1.2.1 is a pain in the ass for corexy users:
M564 H0 is your friend. Just put it somewhere in your config.g
Or that!
-
Thanks, now I understand the reason. I do use M84, is there a way to bypass this feature for M84 as I sometimes need to jog my print head out the way. I always re-home before every print anyway.
-
Your options are:
-
Don't use M84 at the end of a print. The motor current will be reduced to the idle value (default 30% of normal) current after 30 seconds of no movement anyway.
-
Use M564 H0 in config.g to allow axis movement when the printer has not been homed.
-
-
@dc42 said in Sorry but FW 1.2.1 is a pain in the ass for corexy users:
M564 H0
Thanks, i'll go with M564 H0, like I said, i'm a dinosaur
-
Why not just put the "move out of the way" commands in your end script?
