CoreXY setup problems with movement
-
Yes. After homing, using the web interface, I can jog Any of the Axis and they move in the correct direction. I figured if something was backwards, jogging it would show it. Also, when it goes to the next layer, it’s not like it tries to move the 0.2mm that it’s supposed to according to the file, it’s backwards, plus it moves till it hits the end-stop.
-
That sounds really weird. Can you post a few lines of the gcode file you are trying to print, showing the G1 Z move on layer change.
-
Please confirm that you read and understood this bit of my previous reply:
Bear in mind that on a machine with the bed moving in the Z direction, the Z up buttons should move the bed down, and vice versa. This is because +Z means "increase the distance between the bed and the nozzle".
-
That sounds really weird. Can you post a few lines of the gcode file you are trying to print, showing the G1 Z move on layer change.
I will try that if I get a chance tonight after work.
-
Please confirm that you read and understood this bit of my previous reply:
Bear in mind that on a machine with the bed moving in the Z direction, the Z up buttons should move the bed down, and vice versa. This is because +Z means "increase the distance between the bed and the nozzle".
On the Octoprint web interface with ramps setup, UP did make the bed move down.
On the Duet interface, when I hit +10-Z or + 100-Z, it does move the bed down by how much I command. The opposite is true, when I command -10mm-Z it moves the bed up 10mm.
When I home the Z axis, it does move up till it hits the end stop, as it’s supposed to.Could still be something I setup wrong, but I’m sure it will get figured out.
-
Curiouser and curiouser. So moving the head manually moves the Z axis in the correct direction. i.e. a negative move goes toward the nozzle and a positive move goes away from the nozzle. Likewise when you home the bed, it moves towards the nozzle then triggers the switch. But, what you are saying is that when you print, Z moves are reversed. It doesn't make sense.
Unless…...If for some reason the gcode file contains relative Z moves but the Duet is expecting absolute Z moves (as set up by G90 at the start of config.g). Then a relative move of plus 0.3 from say a height of 1.8mm will send it to the absolute position of 0.3mm from home instead of 2.1mm (1.8 plus 0.3).
One quick question. When you move the head manually and do say Z+10 which should move it 10 mm away from the nozzle, is that before or after you have homed the printer? If it's before you've homed it, can you home the printer then try Z+10 again and see if you get the same behaviour? Just wondering if there is something amiss with your homing files that changes anything.
-
Curiouser and curiouser. So moving the head manually moves the Z axis in the correct direction. i.e. a negative move goes toward the nozzle and a positive move goes away from the nozzle. Likewise when you home the bed, it moves towards the nozzle then triggers the switch. But, what you are saying is that when you print, Z moves are reversed. It doesn't make sense.
Unless…...If for some reason the gcode file contains relative Z moves but the Duet is expecting absolute Z moves (as set up by G90 at the start of config.g). Then a relative move of plus 0.3 from say a height of 1.8mm will send it to the absolute position of 0.3mm from home instead of 2.1mm (1.8 plus 0.3).
One quick question. When you move the head manually and do say Z+10 which should move it 10 mm away from the nozzle, is that before or after you have homed the printer? If it's before you've homed it, can you home the printer then try Z+10 again and see if you get the same behaviour? Just wondering if there is something amiss with your homing files that changes anything.
Possibly the G-code file movement is different. I will investigate when I get a chance.
Z+10 works before or after homing.
Another thing is while printing, I added +Z movement from the web control and it did move, but on the next layer, Z moved all the way home, not 0.2mm as per the G-code. -
I think we need to see the GCode file you are trying to print.
-
I think we meed to see the GCode file you are trying to print.
I agree. I will try and get that posted as soon as I can. It has to be something simple, because with this replacement board, everything else was setup nice and quick and it all works.
-
Quick update.
I had the power off during the day while I wa# at work. Decided to verify the homing files for G90 and it was there. Verified the Gcode and it was also there.
I decided to upload the file again and it worked properly. I do have some extruder tweaking to do, but it’s working.I’m going to call it some kind of glitch from the setup and changes I made, and a complete power down cleared it up.
If there ends up being a problem, I’ll dig into it again, but as for now, I can’t fix what isn’t broken.
This weekend, I will try and get it tuned up and see if it pops up again.
