We have 4 seats of MCV9.1 MR0304 and 2 seats of design running on nethasp. At least once a day for some reason, the mastercam server will only release 3 licenses, at which point we have to re-start the MC server. This means someone has to travel the length of the shop at least 2x to get everyone off of MC for the restart..Is anyone experiencing this problem?..suggestions.. thanks.

Has anyone had this happen? When backplotting, (and posting for that matter), the tool dia shows up correctly. In the ops manager however, the tool is completely different.. V9.1 MR0304

This is awful..there must be a patch by now..I am machining a forging and I created a solid representing this forging. I then converted it to an stl file so I could use it for verification and what do I get.. LW has found the STL file not to be closed and watertight. An approximation will be used. How can it not be watertight? it's a solid!! I did a parasolid conversion to test the model and it's fine. I even tried making a surface model from the solid, and then creating an STL, to no avail. I have had my STL tolerance set to .0001 even. Is there a solution out there other than buying verification software?

You're right, it is a very nice post. Thanks for the lead. I am altering as we speak..er write to suit our needs.. Thanks again..

I assume mpmaster is on the installation disk. If not where can I get it? Thanks for the help gentleman. Much appreciated!! I have been and now I am almost.. One other question. I was told by me reseller that the only post that was updated with each release was mpfan. That's why I was using that post. Is there any truth to that statement?

by the way..one_rev is not in this post..

I am using mpfan.pst Using that post I am very close to what I want, however, I have found at the end of each tool via the following line the post outputs A0 pbld, n, protretinc, e This is not desirable. If I # it out the 4th winds up. I need the 4th axis to reset, just not show it in the code. I have frc_cinit set to 1 fyi. After this problem is solved I then need to lock and unlock the 4th. More code please..

Change what to 'one rev' ?

My post is winding up the 4th axis. How do I stop it. Where is this section do I change something? pcoutrev #Rotary axis revolution calculation (Modify for wind-up) cdelta = csav - prv_csav while abs(cdelta) > ctol, #If motion exceeds ctol, add wind-up [ if cdelta > zero, [ rev = rev - one cdelta = cdelta - 360 ] else, [ rev = rev + one cdelta = cdelta + 360 ] ] if cuttype <> one, cabs = rev * 360 + csav else, cabs = sav_rev * 360 + csav !csav

Yes, it is a WCS related event. I have experienced the same thing. My solution has been to always leave the WCS in the initial orientation, op#1 for example, and run all of the following MC9 files from that orientation. You can then run op#1 say and save an STL, then run op#2, load the saved STL from op#1 and proceed as necessary.You will be chasing your tail if you continue redefining stock every time. I have done many circles.. HTH

That would be great!! Where do I put it in the post?..What is the cuttype for rotary axis? Sounds simple, but I know it isn't so, there always seems to be more required, and not being a post expert adds to the mix... I imagine something related to rotary axis would be best since I am using contours for several profiles..

I don't need inverse time on every toolpath in the program I am running. The only way I see to output ipm feeds for a specific path is to turn off inverse time (post setting), then re-post the sections I want at ipm and do the cut and paste thing. which is not desirable for obvious reasons..Any suggestions?

We did try another post and it came out correct.. what now?

I am using the mplfan.pst and the G02/G03's are coming out opposite of what they should be. Any suggestions. The X and Z values are good so that tells me we have the turret spindle orientation correct..I did have to change the dia_mult to -2 to change the sign of X..whazzupp?? thanks in advance

Hey Mike, I have found that if you move the part around that MC verify does not work so good. You then have to xform your stl file, and in most cases you get the wonderful LW has found the model to be not watertight error. I was not a fan of the WCS initially, now I think it's great. In V8 I used to rotate the part for each operation at which point I would have to utilize the STL xform (which worked well in V8). I program almost exclusively for the Mori horizontal in our shop and I always program to part origin. I have had no occasion as of yet to program around centerline. We have a macro in our Mori that calculates to centerline..We probe our location insert it in our G10 line and voila..We are on our way..BTW I worked for your company (ME) from 84-86.. Hope this makes sense..

I used Vericut for a few years...5.2 was the latest version I touched. they don't have it here yet..and believe me, I am pushing for it. Autodiff is a great option. You can export an stl and use if to verify against..You can have multiple models imported for that matter. Just make a solid in MC and export as STL, do the same for your model. when you open Vericut and define your stock, import these files. You can use the default machines (.mch files) and control (.ctl) files to get you going..I can testify to their support as well. I have never had such great support. CGTech is awesome!! Vericut is awesome too. I have full faith in Vericut..I wish I was there to use it with you..

Thanks for the feedback guys..nice to know I'm not the only one with the problem. Russ

We are running Win2K P2.8GHz..The problem is I told the guys in the shop they could run their own config files, so Bob wanted his own. I created a shortcut on the desktop and changed the target accordingly and added bob.cfg and MC starts fine but it boots up with mill9m.cfg not with bob.cfg same thing with brian.cfg..if I rename it to test.cfg it comes up with test.cfg active just like it should... What's up?...

what are the names of your config files? what version are you running? Did you try the names I offered? We are running V9.1 MR0304

Hey.. Can someone try this and let me know if the same thing happens to them? Create a brian.cfg and edit your shortcut target line as follows and tell me what happens. C:Mcam9Mill9.exe brian.cfg If this works like I think it will then try bob.cfg C:Mcam9Mill9.exe brian.cfg Thanks

I have the same settings as you Millman. I went ahead and ran the posted code and it works great!! Thanks for sharing all your info everyone. This is the 1st place I come when I have a question and have always found the answers I need. Thanks again!

I just received the MPMASTER_FADAL post from my reseller. I changed the line below to read as you see and it still outputs A- moves..what's the deal? one_rev : 1 #Limit rotary indexing between 0 and 360? (0 = No, 1 = Yes)

the link is not working for me for some reason..email me the zip file if you wish.. Russ

I am trying to drive the underside of a rib(which has a 10.0 rad) with a 3.0 wheel cutter w/.19 rad. Has anyone else done anything similar to this. I have tried creating a surface and then offsetting it the wall thickness + 1/2 the wheel cutter thickness and MC wants to drive the heel of the cutter on the bottom and I need the nose on the top to drive. I also did as I stated above and tried a 3d path and then offset it radially 1.5 (1/2 the wheel cutter dia) and it's close but still not as exact as I would like it.. A 90 degree head is not an option by the way.. Suggestions please..

set dirs is my startup chook, as for the rest of this computer jargon..Me no understand..TCP/IP..net buie and all that..I can tell you this. We didn't have this problem with V8. Russ