Polar Printer Steps/Degree?
-
OK then position by hand with motors off M84. Then once in position do a G92 X105 Y0 Z0 to set positions.
-
@phospherus ok i will test and update you i really appreciate you help
-
This post is deleted! -
That was with the x axis at 105mm from center of z tower and you did G92 X105 to set position?
And how do you have your slicer setup?
-
@phospherus yes it was however slicer is cura with normal setup as if I slice for any Cartesian printer is there specific setup I just make the plate eclipse and make the origin is center so it is plate with origin
-
I used simplify 3d so can not comment on Cura but In simplify I just leave it as Cartesian because Delta seems to mess things up. My diameter is 240 for bed so I set that for X and Y then do 120 offset to get nozzle in middle.
-
@phospherus I just want to know do you have the same design ? because if yes and working that means something missing in my config and it should work right ? how did you calculate X value can i know the formula ? is it possible to know how do you home your machine ?
As per the polar kinematics documentation homeradius.g and homebed.g should be present however when i rename homex.g and homey.g DWC is giving homex.g or homey.g not found
regards;
-
No my design is not same with the tower in the middle but from what I can see the kinematics should be the same.
-
@phospherus is it possible to tell me which version of reprap firmware are you using because I think there is problem in the version I use because I noticed it behaves correctly sometimes and sometimes not
-
I am using the 3.2.2 stable. I tried version 3.3 beta 2 and Beta 3 and still have issues. 3.2.2 is working for me though.
-
This post is deleted! -
@shadi said in Polar Printer Steps/Degree?:
@phospherus is it possible to tell me which version of reprap firmware are you using because I think there is problem in the version I use because I noticed it behaves correctly sometimes and sometimes not
@shadi I believe this is caused by the same bug that I have just fixed for the issue reported at https://forum.duet3d.com/post/229256. The workaround is the same, i.e. send M669 with a T parameter (e.g. T0.2 to use the default segment length).
