I only wish they would come out with a 1000mm or 1250mm horizontal. The 630 is awesome...just not big enough.

FWIW, nextdc$ = 3 is a tapping cycle.

Personally I am a big fan of Mitsubishi's AJX cutter. You should have no problem getting .04 chip per tooth at that depth of cut.

I just gotta vent about the daymn things every now & then. I am the guy who gets to try to fix them when things go wrong. Mechanically, you would be hard pressed to find better machines. At least Matsuura wised up & quit using them on their cublex's. If you ever see a screaming deal on a used cublex you know why. Imagine being on a production run and a drive goes bad that takes 6 weeks to repair. That's the kind of sh!t that causes contracts to be lost....or worse.

I used to like the Siemens controller...but right now if someone tried to give me one of those fvcking 840Di's they put on a matsuura I would laugh at them. What happened there was Yaskawa & Siemens got together and made a nice control. Yaskawa got pissed and left siemens holding the bag. No parts (Yaskawa drives, motors, ect) have been made for them since I don't know when. Yaskawa won't make them, won't support them, won't have anything to do with them. siemens support is questionable already, throw in that hybrid control and you are pretty well fvcked. I got to deal with 4 of the fvcking things. xxxxty part is mechanically the machines are top notch. That controller, now that they have a few years on them, are the most unreliable in our shop. If a drive goes bad, you pray that siemens has one in stock...otherwise its shipped back to Germany for repairs which can take 6 weeks minimum. /end rant I do have a feeling that if it were a "pure" siemens control (drives, motors, ect) I would have a different opinion.

Sorry its happening to you, but I am glad I am not the only one. Identical behavior. our tool libraries reside on out network: P:\Mastercam Machines 2017\Tool Libraries

Tool libraries are on the network also, and I have full permissions at that network location. When I create a tool inside of mcam, (when the crash happens) I would think that it is a local copy until it is saved to the network.

I am not necessarily seeing issues when I am using the standalone tool manager. When inside of mcam, when I create/edit a tool, crash city.

The keyboard is still there...tho is likely different than what you are used to. Example...to create/line/endpoints, one would hit the "Alt" key, then "W", then "E" Or to get to Trim, "Alt", "W", then "T" It is worth your time to install & just check it out. One would be insane to do an upgrade before doing that anyways

A quick search of our network revealed some .ge3 files dating back to 1992 Pretty sure those would be safe to delete....

The tool manager crash issue has forced us to go back to X9. I honestly don't know how people continue to work through things like that. We simply don't have the extra time to waste dealing with crashes.

if you are using the generic 5ax post, look at mi10 I have found that it is important to set it in your control definition.

A few years back I programmed for Okuma's and Doosan's side by side. 500mm machines, 50 taper. Both late model (I believe the Doosan was a 2011 and the Okuma was a 2012) Running the same speeds & feeds, the Doosan's would make a hell of a racket, chatter like crazy, ect compared to the Okuma's. Some I know have had good luck with Doosan's, I just wasn't impressed.

Yes it can be done, and I had to resort to opening another session of mastercam, make the toolpath, save/import the geometry, toolpath as you outlined. However that is a ROYAL PITA compared to just picking the surface & be done. Leaving those paths out of mill-turn is a huge mistake IMO. Blend and Flowline are among the most used surfacing toolpaths for me.

Be glad you aren't using mill-turn. There is no "old school" toolpaths. No flowline, no blend

Yes, I wound up doing the same thing. Undecided if I want it there as a submenu though

I use both. What if you want to know the midpoint of a line? Or a quadrant of an arc? I guess you could make a point and then analyze entity...

Yes, I tried that. Analyze position is not in your screenshot or any list done with the command finder

OK, I found it. Odd that the command finder wouldn't find it. Not being able to customize the "stock" ribbons is totally fvcking stoopid

Did this get removed? is it now analyze entity? I could not find it with the command finder.

The part is a slide for a 1911. Surprisingly, there are more than a few gun mfg's that are using damascus for slides. It does look cool. https://www.google.com/search?q=damascus+slide&tbm=isch&tbo=u&source=univ&sa=X&ved=0ahUKEwiapd-S9KfOAhUB1GMKHd6PAGwQsAQIHQ&biw=1920&bih=916

Anyone ever cut this stuff? Print is calling out for stainless damascus, HRC 40-46 My hopeful SWAG says it is likely similar to H900 17-4 Any thoughts?

This was/is my biggest complaint about the new interface. Depending on if I am driving a lathe or a mill or a mill/turn or even a wire my RMB menu was tied to a workspace. Programming for a lathe....change the workspace, and all of my customization's (mainly toolpaths) are in my RMB menu. New job, mill time? change workspace and now I have all of my most common mill toolpaths right there. I brought this up in the official forum to basically deaf ears.

I am getting some errors when updating some of our older posts (and some of the newer ones also) one that I pretty sure is benign is a message I am getting about the bug3$ switch. So pretty easy to delete that one. Now getting to some of our posts that have been updated through the years & never have received much love (to be fair, they worked fine & didn't need any love) I am running into things that might need a closer look. This error is from a F.A.G.O.R 8025 post plin1$ # First linear movement after SOF, whatno must be set #CNC<<FAIL>>plin1$ # First linear movement after SOF, whatno must be set #CNC<<MSG-ERROR(1217)>> The variable, postblock, or other keyword is no longer supported plin2$ # Second linear movement after SOF, whatno must be set #CNC<<FAIL>>plin2$ # Second linear movement after SOF, whatno must be set #CNC<<MSG-ERROR(1221)>> The variable, postblock, or other keyword is no longer supported plin$ # Linear line movement - at feedrate if startflg = one, pstartpos if rotaxis$ <> zero, protaxis else, plinm,e$ pz$ # Linear movement in Z axis only - at feedrate pzcalc n$, sgcode, pzout, pfr,e$ pcir1$ # First circular movement after SOF, whatno must be set #CNC<<FAIL>>pcir1$ # First circular movement after SOF, whatno must be set #CNC<<MSG-ERROR(1234)>> The variable, postblock, or other keyword is no longer supported pcir2$ # Second circular movement after SOF, whatno must be set #CNC<<FAIL>>pcir2$ # Second circular movement after SOF, whatno must be set #CNC<<MSG-ERROR(1238)>> The variable, postblock, or other keyword is no longer supported So the plin1$ & plin2$ are out to pasture along with pcir1$ and pcir2$ Now I haven't done any testing to see if these errors will affect the output, however they seem to have the potential to cause more of a problem than the bug3$ switch. An yes, these posts are old. Like V8 old. However the machines they run are pretty basic and don't need much. No toolchangers, coolant, ect. Any updates up until 2017 have been flawless. To this day I haven't had to do much with the posts simply because I didn't need to. So are these errors going to be a show stopper? Or should I be good to go?

You couldn't give me an interrapid because of one thing....the dials don't auto-reverse. The needle swings in opposite directions depending on what side of the stylus you are on, so I find myself tapping the stylus with my finger to see if I am plus or minus. Doesn't sound like a big deal, till you get used to using a brown & sharp or other brand thats needle always swings the same direction, making it infinity easier to tell if you are traveling plus or minus.