![]() ![]() I already saw perfect and fuzzy cuts within the same toolpath on a 10x5 piece of hard wood carefully selected by a luthier.īTW, with which tool do you measure your 24 long slot?Įdit: you were faster than me, wmgeorge. I generally wouldn't expect such precision with a 24 long cut. That's why several posters thought of a tool diameter issue or allowance. Now let's imagine that your spindle can't run faster than 10 000rpm. It's curious you had the same error in X and Y sizes. Based on this mathematical relation, we observe that if we want to increase the feed rate to cut that plywood faster, we will have to increase the spindle rotational speed as well to keep a constant chip load : 2 800 2 x 0,07 x 20 000. the cuts are different, and a g-code comparison will enlighten you the cuts are identical, which demonstrates it's not a software problem Not another tool with the same reference: physically the same tool. Not another board of the same wood, which may react differently. Set the feeds and speeds as well as the depth of cut etc. ![]() Perform all the tests (including V-Carve) as quickly as possible to be sure you have the same conditions (humidity, temperature, …).Īnd when I say the same material and the same tool, I mean exactly the same. The next things we need to add are holes for the adjustable. Cut the same material, with the same tool and measure immediately after cut. So generate *exactly* the same cut with these programs. The question is not "why is the cut too small with V-Carve" but "why is the size not correct while the G-Code is" Bill, pretending V-Carve is the origin of your problem when V-Carve outputs a correct G-code is a dead end. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |