Prints coming out mirrored
-
@hwg315 It sounds like you have one of the axes going the wrong direction, and it sounds like the Y axis. Where is the X0 Y0 point? It should be with the nozzle over the front left or the back right of the bed.
Ian
-
@droftarts The origin for the printer is in the back left. Can be confirmed by sending G1 X0 Y0. In Cura, the origin is in the middle of the bed (though I don't have that option checked in machine settings, and turning it on and off seems to have no effect). The thing that confuses me is that I think all my axis are moving in the right directions because they respond to G1 commands as I would expect.
Also - I posted another question a couple of days ago and you answered it. You guys on the forum are the best!
-
@hwg315 If you're homing to the back left, you're using a left-hand coordinate system, and your prints will come out mirrored. 3D printers generally conform to using a right-hand coordinate system.
Looking at the front of the printer. the most common arrangement using a right-hand coordinate system is:
- +X moves the print head to the right
- +Y moves wither the print head away from you (towards the rear of the printer), or the bed towards you (towards the front of the printer)
You can see the arrows in Cura point in this direction, too.
To fix this, you need to change the direction the Y axis moves. You will also need to change your homing files, so that any Y moves go in the opposite direction. You may also need to modify any tool or probe offsets. If you need more help with this, post your config.g and homing files.
I suppose the other thing with this machine is... can't Modix help you?! They should have working configurations for it.
Ian
-
@droftarts I'm not sure if I've got my head around this properly but if the OP is homing to back left, could he not just change his Y end stop assignment to be high end (i.e. Y max). Of course, he'd have to change his Y homing files to travel in the opposite directions to those which he uses now.
Then although he still homes to the back left, the origin would be font left would it not?
-
@deckingman @droftarts Thanks for your reponses, it sounds like I could change the end stop to be in the high positions, and then also change the direction of the Y motors, and ensure that the homing file is properly set up (make sure it moves Y up instead of Y down) then everything would be fixed.
Or....
I could stop screwing around in the config file and just mirror my prints in Cura when it matters. I realize that may sound sacrilegious, but I think simpler may be better in this case.
In response to your comment about Modix, yes, they probably could help us. However, I am a summer intern, and they are on the opposite side of the world so they never respond during working hours so I have been reluctant to reach out. I have also been more of the attitude that I should just work things out myself and rely on open source forums rather than depend on them to fix my problems.
-
@hwg315 If you post your config.g and homing files, it's relatively trivial to fix them for you. You don't need to physically move the endstop; you can configure the endstop position in config.g.
Ian
-
@droftarts How's this? I think I marked all the things that need changing, but let me know - still new to all of this. I'm afraid to use the configurator or to update firmware b/c I made a bunch of changes to GCode manually that I don't think will be maintained.
-
M574 X1 Y1 S1 ; set active high endstops *and make Y1->Y0 here?*
To change to high-end endstop you must change Y1 to Y2.
G1 H1 Y-595 F3000 ; move quickly to Y axis endstop and stop there (first pass) *Make Y positive?*
Yes, you would need to flip the signs on your homing moves. The endstop is at the high end, so the move must be positive. Same is true in homeall.
-
-
@droftarts @Phaedrux Thank you, this fixed the issue. For anyone coming here in the future, you will also need to change the z probe point in homez and homeall, and mesh probing will start in a different corner unless changed.
-
undefined Phaedrux marked this topic as a question
-
undefined Phaedrux has marked this topic as solved