Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.
Use your display name or email address to sign in:
So I've just started back into the most recent version of Mastercam after using VISI for a number of years. So here's my current stumbling block it appears that when I post a G-code program that things are working properly. The control see's the program it even shows that the comp is on the correct side (right in this case) and displays a tool path that looks about right. BUT when the tool comes in to make a cut (only a finish pass in this case) the displayed x value is much smaller than the programmed one and indeed it will cut on the small side >.< Anyone have any suggestions? I've tried flipping the comp to the other side going through touch off and tool definition a number of times all with the same results. Here's the code in question:
eMastercam - your online source for all things Mastercam.
Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.
ProtoTRAK SX3 Lathe post issues in X8
in Post Processor Development Forum
Posted · Edited by JParis
readability
So I've just started back into the most recent version of Mastercam after using VISI for a number of years. So here's my current stumbling block it appears that when I post a G-code program that things are working properly. The control see's the program it even shows that the comp is on the correct side (right in this case) and displays a tool path that looks about right. BUT when the tool comes in to make a cut (only a finish pass in this case) the displayed x value is much smaller than the programmed one and indeed it will cut on the small side >.< Anyone have any suggestions? I've tried flipping the comp to the other side going through touch off and tool definition a number of times all with the same results. Here's the code in question: