Thank you all for contributing in this post! :)

As I suspected there's many expressions used for this. I think I'll stay with "stickout" then!

Hi.

Me and a colleague (we're from Norway in Europe) got into a discussion about what's the correct term for what I call "tool-stickout length".

What do the native English speaking folks here say? Is there a formal term and an informal one for this? 

Also, does one use other names for what I call "work piece stickout" or "boring-bar stickout" etc..?

Any other terms for this?

On 6/27/2017 at 3:31 PM, Roger Peterson said:

There's really only one right answer, put the entire "shared mcam2018" on the network and point both pc's Mastercam to use it.  if you do this updating from version to version is as simple as running the migration wizard. 

 

Any other configuration requires re-linking to posts, tool libraries, etc..  While not necessarily a problem it is time consuming and in the case of re-linking posts can have terrible effects if done correctly.

 

below is a pdf file that goes through the process of sharing files over the network.  The pdf is for 2017 but the process is identical for 2018

 

HTH

Mastercam 2017 Sharing Files Over The Network.pdf

Hi Roger!

We're looking into this solution in our shop. I downloaded the pdf you provided here, but the link to the Prototek Engineering sharefile is not available anymore.

Is this a program you wrote just to make the process easier, or do we need it to reverse-engineer something in Mastercam to make this solution work at all?

I'm thinking about doing it like this:

- Move entire "shared Mastercam" folder to desired network location

- Relink path in Configuration > Files > Shared Data Folder 

After this I will mirror the whole installation of Mastercam on my computer, and push it to all the computers in our shop.

In my head this is a viable solution. What do you think?

On 10/4/2018 at 3:13 AM, jlw™ said:

This is my thought exactly.  Why can't we do this in X?

I though about this recently as well!

Best answer I came up with is that setup lenght on a similar tool for X-axis cutting would be hard to set because you would need an Y-axis offset for the tool,

and usually you can't probe a tool in Y-axis direction..

Does this make sense?

Anyway.. I am struggling to make G96 work with Y-axis cutting on a Mazak Nexus 350 MY with 640T version of Mazatrol.

Does anyone have a solution for this?

Right now the spindle is going straight up to my defined "G50 Sxxx" speed when moving to X0 to start Y-axis cutting..

I read somewhere that G96 Sxxx P2 M03 could make the machine use Y-axis as reference for the G96, but nothing happened.