Issues with a milling post processor..
-
- Posts: 20
- Joined: Mon Feb 22, 2016 9:46 pm
Issues with a milling post processor..
I am having issues with a milling post processor . When doing a pocket it will do the inside part of the pocket but then when it should just move over and cut the outside part it will lift up then try to do the outer cut in mid air.. or say st safe z..This is really a problem when doing letters that are less than double the width of the bit.So you will end up having only the parts milled where it travel it traveled in the one direction.. i have tried everything i can think of and no change.. i am posting an example of the g code ..The first part is fine ..When it switches to the letters is where it messes up
- Attachments
-
- no small.tap
- (40.58 KiB) Downloaded 211 times
-
- no small.tap
- (40.58 KiB) Downloaded 187 times
- Les Newell
- Site Admin
- Posts: 3668
- Joined: Thu May 11, 2006 8:12 pm
-
- Posts: 20
- Joined: Mon Feb 22, 2016 9:46 pm
- Les Newell
- Site Admin
- Posts: 3668
- Joined: Thu May 11, 2006 8:12 pm
The problem is on line 372 in your post:
post.Text (" G01 F1270 z10")
post.Text simply outputs text to the gcode file. That means the post does not know the machine has moved. This is a better solution:
post.ModalText(" G01")
post.ModalNumber (" F", 1270, "0.0###")
post.ModalNumber (" Z", 10 * scale, "0.000")
post.Eol()
Now the post knows exactly what is happening so the generated code will be correct.
post.Text (" G01 F1270 z10")
post.Text simply outputs text to the gcode file. That means the post does not know the machine has moved. This is a better solution:
post.ModalText(" G01")
post.ModalNumber (" F", 1270, "0.0###")
post.ModalNumber (" Z", 10 * scale, "0.000")
post.Eol()
Now the post knows exactly what is happening so the generated code will be correct.
-
- Posts: 20
- Joined: Mon Feb 22, 2016 9:46 pm
-
- Posts: 20
- Joined: Mon Feb 22, 2016 9:46 pm