Actually, now if I open any file, and try to choose a machine, it crashes... ugh...

Ok, I've just opened a solidworks part file. I created stock, after selecting a machine.

Then, my stock disappears from the screen, and I can't open Stock, Tools, or edit the Machine Definition. I've saved the file, so I shut down 2017, and reopen it. I open the the file, and the Stock definition is gone, as has the machine group. I try to reselect the machine and Mastercam crashes. It does this for any machine selection.

Anyone encountered this?

I've got a customer with two Mori Seiki MT machines. The newer one has the MSG control, and the older one has the Fanuc control. If they back up the tool offset data (ie, send it back through Cimco DNC Max), the newer machine receives the data fine.

However, the older machine doesn't. The received data looks like this:

`f~x~~~xxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~`~xxx~fxxf~~~~xxxxxf~~f~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~x~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~f~xxx~f~~~fxxx~`~fxf~~f~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~~xxxxx~~~x~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~xxx`~xxf~~~~fxxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~fxxxxxx~~~xxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~xxxxxxxf~~~~fxx~~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~fxxxxxx~~~x`~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~f~xx~xxf~~~xxxxx`~xxf~~f~`~xxxxf~~~~xxxxxf~~~~xxxxxf~~~~~xxxxx~~~xfxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~fx~x~xxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~xxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~x~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~x~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~xxxf~~~~xxxxxf~~~~xxxxxf~~~~xxx
xxf~~~~xxxxxf~~~~xxxxxf~~~~fxx~xxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~~xxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~xxx`~~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~f~xxx`~xf~~~~xxx~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~~xxxxx~~~~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~f~xx~~xxf~~~~`~x~xxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~~xxxxx~~~~xxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~f~xx~xxf~~~~`~x~xxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~~xxxxx~~~~`~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~fxxx~xxf~~~~xxxx~fxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~~xxxxx~~~~fxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~fx~x`~~~xf~~~xfxx~xxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~~xxxxx~~~~xxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~fxxxxxxxfxxf~~~~~x~~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~~xxxxx~~~~~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~f~x~x~f~~~xxxxx~~f~~f~`~xxxxf~~~~xxxxxf~~~~xxxxxf~~~~~xxxxx~~~~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~x~xxxxfxxf~~~
~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~~xxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~x~~x~~xxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~~xxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~fxxxxxfxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~fxxxxx~x~f~~~xxxx~fxf~~f~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~~xxxxx~~~~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xx~~fxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~~xxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xx~xxf~~~fx`~x~`~xxf~~~fxxxxxxx~~f~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~`~xxxxx~~~~`~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~fxfxxxxx~f~~xxxxx~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~`~xxxxx~~~~fxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~`~`~xx~~xf~~~~~~x~xxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~`~xxxxx~~~~xxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xx~xxf~~~fxxxfxxxf~~~x~~x~`~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~`~xxxxx~~~~~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~`~xx~~~xf~~~~~~xx~~xf~~~~xxxxxf~~~~xxxxxf~~~~
xxxxxf~~~~`~xxxxx~~~~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~xxxx~~~~xf~~~xxxx~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~fxxxxxx~~~~xxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~xxxx~~~~xf~~xfxxx~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~`~xxxxx~~~xxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~`~xxxxxf~~x~~x~~~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~`~xxxxx~~~x~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~x`~xfx`~~f~~~~~xx~x~f~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~`~xxxxx~~~x~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~xxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~xxxx~~~f~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~x`~xf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~xfxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~~xxxxxf~~~`~xxxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~fxxxxxx~~~xxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxx~~~x~~xf~~~~xxxxxf
~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~~~~xxxxxf~

when it should look like this:

%
N 11000P         0
P         0
P         0
P
P         0
P         0
P         0
P         0
P         0
P         0
N 11010P0.057
P0.028
P         0
P
P-1.269
P250.377
P-20.000
P         0
P         0
P1.000
N 11020P         0
P         0
P         0
P
P         0
P         0
P         0

Both machines send and receive NC files no problem at all, and the comms settings appear to be identical. It could be a Cimco DNC setting, but I was just curious if anyone here has encountered anything similar?

solidworks users can get HSMworksExpress for free. AAANND it comes with a rebranded version of cimco with backplot.

sorry if this inappropriate to mention on this forum.

I don't think it is inappropriate. Actually, it is a hot tip

_{"C:\Program Files\mcam2017\common\Editors\CIMCOEdit7\CIMCOEdit.exe"}

 

_{Yes it still comes with MC2017}

_{I had to check cause I didn't know.}

_{I've been using the full version for years}

Hah, me too . I've been using the full version for a few years. Cimco Edit Pro is my default editor in Vericut, TopSolid, and Mastercam.

 

 

I know, I know.  Cimco but I can't get the funds for it at the moment.

But it comes free with Mastercam... I guess it still does with 2017?

It has fixed a bunch of other issues as well. One of my customers had a NCBase issue that was a major. Got to hand it to Cimco, they had a patch produced for the customer overnight.

My observations are the same as yours.

 

The machine tool salesmen are soliciting Mastercam with iCam but my customer is questioning adding another software in the mix when they already use Mastercam and Vericut.

 

Thanks for the responses.

I agree with Ben and Matthew, looks like a 4 axis mill, with some special functions. A good post guru should be able to sort the extra functions. The existing combination of Mastercam and Vericut (provided the post for Mastercam is sorted) should be fine. Vericut can handle those functions.

Mazak controls use Mitsubishi mother boards. Despite their entire software runs on Windows, some core CNC resources rely on the Mitsubishi processors.

 

Thank being said, last time I bought a Mazak machine, we had to order a PCI card from them and then install it on a PC and then install the Matrix software in a dedicated PC. Pain to setup, you are tied to one PC since you cannot run the software in a host without the card (We tried RDP) and did I say paaaaaaaainful to setup?

 

I remember we tried to return it to Mazak after a couple of months of attempts...

Hot tip, If you have software licensed to a mac address, and you effectively want a "dongle", buy a USB to Ethernet adapter, and register the mac address of that adaptor to the license. It works a treat for Vericut, and I've used it for Siemens NX and TopSolid. It works legitimately, and when I showed CGTech, they actually thought it was pretty neat, and allowed "dongle usage" on mac address licensed software.

okuma with 200 or 300 control has pretty sweet Collision Avoidance Software. Don't even need to look in the machine window; live simulation will pretty much show what the machine is doing at any moment. I believe it also has some look ahead for upcoming collisions, but Yodoug or gcode would know more.

Okuma Collision Avoidance is good, but it is a pain to set up, and it only runs with Okumas. Also, it doesn't run with TCPC, so for five axis it is about as useful as an ashtray on a motorcycle (unless they'd updated it). We have it on our Multus B400W and our Multus U3000 2SW, but we didn't spec it on our MU500 5 axis. We had Vericut, so we didn't need the CAS.

I agree, whatever machine you go with, get STEP models of the machine as part of the order. I've built Vericut machines/controls for some of my customers, and most of the machine tool dealers ream you after the fact for models.

Flowline. Tried and true.

Hmm, was my answer not good enough?

Analyze -> Curvature will give you what you need.

Thanks Ron. I've used this toolpath a few times, and got good results.

THe ONLY reason I could see using it would be for a nice edge break on the exterior of a part if you did not want to change tools and you were surface machining a top surface that was flat. I never do that either though. I use Chamfer mills or do swept 2D or Flowline...

But roll over edges, does't actually break the edge. It basically pivots the tool at the surface edge, much like roll tool around corner in 2D contour. Really, the function is about as useful as an ashtray on a motorcycle..... Or a bowler hat with sleeves

I'm a 2%er!

 

I could possibly understand dropping the old-school surface paths IF AND ONLY IF the surface high speed paths could be set to not roll over edges.  I have never in my 20 years of programming wanted the path to roll over the outside edges.  The wireframe paths should never be let go though, since they make by far the cleanest output possible.  They're often more work, but it's more than worth it when you need that clean output.

I complained about this a number of times... fell on deaf ears. The only real answer I got was "create a containment boundary" or "use check surfaces". Sometimes that isn't feasible/achievable. Sometimes I just want the surface alone to control the tool. But, again, they didn't listen. Still, we got a nice new interface.... twice...

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.

Flowline has got me out of the !@#$% plenty of times. Sure, it is an old toolpath, but some of those old toolpaths have their place. Even 2D and 3D Swept are useful (And I'm one of those 2% that can do coons patches, including tricky ones).

Maybe Flowline etc being left out of MT is writing on the wall...

Been good here for over 6 months on speed.

So that is how you keep going on Mastercam late into the night... LOL

I have been just using a bounding box, not points then use temporary midpoints to set my centerpoint.

 

Imo they mucked up bounding box.

I get the impression they have a fixed number of functions. Before they introduce a new function, or add to a function, they must first remove an existing function, or reduce its functionality... LOL

It is by design. The option to do it like it use to have been requested until then yes you will have to delete the duplicates.

ARGGHH... *Sigh*... another useful function fubared. Like you Ron, when dealing with with multiple parts in an assembly, it does get old quick.

Vericut can handle it too

I've tried Y output a number of ways, for a Multus B400W. Originally, I used a MR number, but as is always way with MI/MR's, I forgot to set it. This was for a Sandvik Coromant Twin Tool (CNMG/DNMG style)

Since the Multus has a magazine, and the tools are fixed, I just added a function so that if a certain tool was called, it would flag a Y output. Basically a mini tool table inside the post. Worked a charm, and there were no more instances of forgotten settings.

Obviously, it was suitable in this case (due to a magazine with fixed tool numbers), but that was on way of addressing.

I used the full download (ISO) to install. Like you, I always do.

Also, the machine definition was set to a 2017 Tool Library. I always update this when I update the machine/control definitions.

It is a tough one to resolve, as I can't seem to be able to replicate it.

Never seen that before

what OS are you running???

Windows 7. I've noticed it flashes a Tool Manager error, though it happens randomly (ie, I can't easily reproduce the error)

Right now, X9 is more stable than 2017 to me..

I clicked Toolpath -> Contour

Then *POOF*, 2017 shut down.

Then the attached dialog popped up.

Anyone encountered this Compatilbity Assistant before? I've never seen this before at all.

Compatibility Assistant.bmp