Our HASP is on the network but my configuration files are saved/accessed right on my PC.

Ever since the switch to 2020 it seems like at least once every week or two I open an instance of Mastercam, whether it's new or a saved file, and my RMB options are set back to default and my hotkeys are totally wiped. Anyone else experiencing this? I've browsed here and mastercam.com but haven't found any threads on the topic.

I'm seeing some funny behavior with Horizontal that I hadn't encountered before and was curious if anyone else is seeing the same stuff?

I just changed the holder and stickout in an already generated horizontal path, went to regenerate and it gives me a fail error. Hit regenerate again and it goes.  I saw it the other day where I had to hit regen about 3 times before it went...I'd say it's happened maybe 4 or 5 times total now, but I also don't use horizontal a ton.

Damnit...I had forgotten. MIN-Z-TPLANE outputs NA for 3D operations. 

Looks good so far. For some reason I had operation/min-z-tplane in mine.

I've got my active reports set up sheet tweaked in pretty nice, but still struggling with one issue.

Say I have one tool cutting at different depths, in different paths, the setup sheet outputs the depth of only the first cutter path of said tool. Is there any way to get it to output the greatest depth out of numerous paths? Or is this a matter of me just getting unlazy and only grabbing that last path instead of selecting all of them?

4 minutes ago, Old_Bear said:

 One hour and I'm there.

Got it. Thanks Old Bear, this has been a very insightful conversation for me.

Correct me if I'm wrong, but it looks to me  that when you drop down into that surface rough menu it's explaining to you what you can get away with...you can do pocket with multi surfaces, or "one surface" with the other paths. If you drop down into surface finish does it use the same verbage? Unless I'm reading into that incorrectly.

That drop down is helpful.

So when he did a multi surface parallel he was using a finish parallel path, I take it?

It's a mold for some sort of concrete block. Based on the pictures he sent me I can imagine he might be able to cobble something together, but it's beside the point. It seems like the more he shows he can do the more complicated work they're putting in his lap, and he's only been using Mastercam since February of this year. I've advised him to try and get them to upgrade to level 3.

Are you saying that with mill level 1 you're able to put down a rough multisurface pocket path and post it out? He claims to have had licensing issues, but I wasn't there to witness it. He's also running 2018.

It almost seems like tribal knowledge or something.

My buddy is working with level 1 and asking questions...he's got a mold to work out of plastic, sent me a picture of it and asked what he should do. I told him if he can get multiple surfaces with legacy paths (confirmed that he can do multiple surfaces with parallel), then try out pocket. Didn't work, not licensed for it. 

He ended up calling his reseller for some support and they also told him that legacy pocket should be capable of multiple surfaces with level 1. He then doubly confirmed that it is not. I told him try multisurface pocket for good measure. No dice. 

Tried searching for this one, but results were watery at best.

Does anyone know what capabilites Mill Level 1 has anymore as far as surfacing goes? I know it used to be that you were limited to one surface at a time, but now it seems like there are certain paths that can handle multiple surfaces...can anyone give me the rundown on what's what at this point in time?

Learning should be front and center after you log in. 

Congrats on retirement. Dicking around with active reports should prove a relaxing way of easing on into your twilight (sarcasm).

Follow Bear's link, after logging in click "learning", then to find the active report tutorial you need to select Mastercam 2018 (or older, from the looks of it). 

17 minutes ago, jeff.D said:

Use the force function.

pcanceldc$       #Cancel canned drill cycle
      result = newfs(three, zinc)
      z$ = initht$
      if cuttype = one, prv_zia = initht$ + (rotdia$/two)
      else, prv_zia = initht$
      pxyzcout
      !zabs, !zinc
      prv_gcode$ = zero
      pcan
      pcan1, pbld, n$, sg80, strcantext, e$
      if (drillcyc$ = 3 | drillcyc$ = 7) & tap_feedtype, pbld, n$, sg94, e$
      result = newfs(15, feed)  #Reset the output format for 'feed'
      pcan2
      result = force(sgcode, sgcode)  #Force gcode output on the next motion line

 

Had to use a variable instead of a string, but this got it where I want it.

Thanks Jeff.

I thought about doing that but my neurosis doesn't allow me to view G80 G0 or just a G0 floating out in space as an acceptable way to program. Would much prefer to keep it on the same block as the first Z movement. 

Been hunting for the Cinci parameters to make that change, but not having any luck so far.

On 12/29/2018 at 8:37 AM, Old_Bear said:

3) Bottom/Bottom/Bottom as has been mentioned, try using Top/Top/Top  also, general rule of thumb, do not use bottom and back planes for positioning on a VMC rotary, create new planes by rotating and existing plane.

I'm just curious why this is rule of thumb?

Thanks.

12 hours ago, jlw™ said:

Is this an Acramatic 2100 Cinci?  You can change that parameter to have it default to G00 after G80.  I haven't touched one in a decade but I'm sure a little Google-Fu will find what you need.

I've got two 2100 Acramatics, plus one 950 and one 900. 

I'll look into this tip, thanks. Would be a huge help.

14 hours ago, nickbe10 said:

What is your "base" post? That is MPMaster, CNC Generic?

That would've helped. I've using Generic Fanuc 3X and Generic Fanuc 4X.

Hey everyone - this one is getting by me. I've got numerous Cinci's that I program and they require a switch back to G0 after a G80. Meaning without a G0 after coming out of a canned cycle they'll just stay in G01. I've been playing with this on and off for a while now, but can't seem to get anywhere. Seems like I need to add something to pzout, but I can't figure out what. Am I on the right track? This seems like it should be a pretty simple fix.

This did it. Thanks Daniel.

Hey guys - I've downloaded Mastercam 2019 HLE off of the Mastercam website. When I try to install it throws an error at the end that says "Some files could not be created. Please close all applications, reboot Windows and restart this installation". 

Closing applications, rebooting windows and restarting the installation yields the same error. Anyone have an idea what might cause this and how to fix it?

Thanks a ton guys, this is very helpful stuff.

https://www.dropbox.com/s/6moenbw2lm7h2ah/5015998.mcam?dl=0

Hey guys, there's my file. I'm struggling a bit here and I'm hoping someone can help me out. This is potentially going to go on one of our HMCs. The flowline toolpath is set up just how I'd prefer to machine it in this case as the machine this part is going on is severely limited on memory. Someone from another forum showed me how to change the filter on the helical style flowline so that it doesn't post out as much code. That could work, but the plunge doesn't leave much scallop to speak of and I think if I get the entry right I should be able to program all three tapered bores in one program. 

Anyways, it's the swept 3D portion of the program that I'm struggling with. The current toolpath almost gets me to where I need to be. The part will have a 2.4375 hole drilled through the center, so what I want to do is use the 2" ball end mill at the edge of that stock, and step it over in .030" increments until it gets to the beginning of the flowline path that starts at 9 o'clock (this is from front view). There's two problems with the swept 3D path -

1). It travels the entire length of the contour on every pass. Is there any path where I can set up my stock, then I can have it plunge along the path of the taper only to where it needs to go based on the remaining stock?

2). The swept 3D path outputs as a ton of very small x movements, whereas the flowline outputs point XYZ to point XYZ. This is really troublesome for the limited memory that I mentioned before.

Thanks everyone for any pointers.