quote: I don't have the time or the energy to get into a pissing contest with you. Thank you for your input. WOW! I've been told to shut-up and mind my own business! Sorry...no can do. Seeing as how I teach this stuff, I try to add my input so that others might see how things can be done in a different way. I also do my best to defend Mastercam from bulls**t, which is now the only reason I'm still trying to get through to you. I think I FINALLY see what the problem really is. The print shows the 2-d outside boundary of the top of the pocket (which is at some section in the middle of this .250 corner radius). Apparently it's too difficult to actually DRAW the lower tangency (from which the 2-d toolpath can be easily created using my previously posted methods). Here's how to do it: Create a rectangular surface at Z-.08 bigger than the pocket (I know you're only using Mill level 1, but you CAN create surfaces just not machine them). Create a surface fillet curv/surf selecting the flat surface and the chain of the outside boundary of the pocket. set the radius to .25. Go to the options for the fillet and create only the rails. Do it. Chain the bottom rail for the pocket routine and use -.25 stock to leave. Does this work for you? I've now given EXACT step-by-step instructions for getting this toolpath using 2-d pocketing WITHOUT having to do any "extra calculations". I do apologize that you have to actually do some extra geometry creation, but refer to my previous comment concerning software limitations. If you still don't believe that this will give you the toolpath you're looking for, I'm sorry but I can't do anything else for you (nor do I believe anyone can). Try it anyway, and do it in the same file as the one with "extra calculations and such" that give you a good part. Verify both toolpaths together and see if there is any difference.

quote: If the pocket depth is shallower than the tool's corner radius, then yes. I expect the CAM system to cut the geometry dimensionally correct. If this is what it takes to accomplish that, that's what I expect. This is ASSUMING that the chained geometry is at the TOP of the pocket and that you are using the incremental depth to define the whole depth of the pocket. Not at all the way any of the other toolpaths work in Mastercam. Here's a situation for you (and GibbSCAM if you still have access to that tripe) Pocket depth=.15, Tool nose radius = .25, Islands inside the pocket with height=.063, Multiple depth cuts .03 max cut. (pocket-g.mc9 on the FTP) quote: Workaround? Only "problems" require workarounds. Not true in the least. I can't tell you how many times I just can't seem to get [any] CAM software to cut EXACTLY the way I want. So I have to model my toolpath and chain cutter center with no comp and voila, exactly what I want. All systems have inherent limitations. Workarounds are for those times when you run up against them. quote: Are you sure? Quite. quote: Have you measured it? Many times. quote: This will only work if you have a full 90 degree radius on the edges of the pocket Incorrect. Notice I said the BOTTOM tangency (take a look at the pocket-g.mc9 file). No "extra calculations" required. I've been doing it this way for about 14 years now (since v2.something) and have never had a problem.

quote: gstephens, bring back any memories??????? AAAAAHHHHHHHHHHHH!!!!!!!!!!!!!!!!!!!! quote: They'd probably have to do it the same way huh? Buy a Mazak C-axis lathe (or sub out the job to someone who has one already). They have a REALLY cool function (G1.1) that is used for C-axis threading. X,Z incremental motion through n revolutions of the C-axis (and at 400 RPM no less) too cool. No way to program it in Mastercam though (I wrote a WAY custom post for this one).

quote: MC doesn't account for the corner radius on the tool. I have proven this by milling a pocket that is shallower than the size of the corner radius. In this instance, MC *should* compensate for the diameter of the cutter at that particular depth. Why?? How does Mastercam know whether you want to cut with the eside of the tool or at some (infinite number)point along the corner radius? Are you looking for it to automatically offset based on an incremental depth from the geometry? I guess that would be nice; however, there has been a quite acceptable workaround for a LONG time... just chain the geometry at the tangecy at the bottom of the radius, and give it a NEGATIVE xy stock to leave equal to the corner radius. Works perfectly every time, and won't require an additional type of pocket and contour toolpath. I can just see trying to explain Standard/Open/Facing/Island Facing/PARTIAL CORNER RADIUS options to a bunch of people who have never run CAD/CAM before. JMNSHO Oh BTW, I've put corner rad-g.mc9 on the FTP which runs this fine using surfaces (need level 3) with the appropriate settings. [ 08-26-2002, 01:40 PM: Message edited by: gstephens ]

Hey Bert. Use the motst variable: motst = 4 if Z only motion. if motst <> 4, [ pcan1, pbld, `sgcode, sgabsinc, pxout, pyout, pzout, pcout, feed, strcantext, e ] else, [ pcan1, pbld, `sgcode, sgabsinc, pzout, pcout, *feed, "*V23", strcantext, e prv_feed = -9999 ] Your code looks OK except that you have: else, if... [ . . ] the nested if has to be inside [ ]'s Have fun!

gcode wrote: quote: Legally it probably is a pirated seat, but I can't see any court in the land convicting anyone of piracy in those conditions. Leagally it is a "pirated" seat, in that it is un-licensed. The license is ONLY good for the original owner unless CNC approves the transfer (Does antbody actually ever read the license agreements they agree to? ). Software is such a weird thing. Somebody earlier asked about accounting and assets. Yes it is considered an asset for tax/accounting purposes because if the company is sold as a WHOLE it will be transferred, however it is not sellable on its own. As far a a court "convicting" someone of piracy...that would imply that it was a criminal offense. Currently the cases are almost always civil issues (which is why it is so difficult and costly to stop piracy). OK...enough ranting (for now )

You probably have to change that question number in the mill.set file as well.

Actually CNC Software has to approve the transfer BEFORE it happens, so you want to contact your reseller FIRST, then get the OK, then aquire the software, then pay the license transfer fee. Only after all of this has been done will you be a legal licensee.

The A feedrate is in degrees/minute that's why they look so high. Below is how to get rid of the wind-up. Be VERY careful if you do this as your rotary may not like the "shortest distance method of programming. Save your existing post (and .txt file) with a DIFFERENT filename to be sure not to lose it. Find "pcoutrev" in the post and add the line shown below: pcoutrev #Rotary axis revolution . . . rev = 0 #<---Insert this line if cuttype <> one, cabs = rev * 360 + csav else, cabs = sav_rev * 360 + csav If this doesn't work for you, you'll need to contact your dealer post customization.

If the chain is closed, you'll end up not cutting the whole contour.

Is there any control that allows you to turn comp on in an arc move? As far as I know only the Fadal will do this.

ctol is usually associated with wind-up of a rotary axis. If I remember right it's the max value for a single rotary axis move in degrees. It also determines which direction your table rotates when doing a rapid move.

You might also want to check out the Verisurf link at the bottom of this page.

Use "T" in operations manager to toggle selected paths on/off.

My favorite 2 are... "I've cut the darn thing 3 times and it's still too short!" and... "Always keep letter punches around so you can mark any extra holes with: "O", "I", "L"

You need to run nhasp and change the settings to nethasp and local. Also you need to make sure you have the nethasp server installed and running on your computer for others to see it.

I saw it Saturday! Oh yeah, and I've got tickets for Friday at Grauman's Chinese Theater also (It's DIGITAL there this time! Woo Hoo!). [ 05-13-2002, 06:08 PM: Message edited by: gstephens ]

Kathy, I just installed the new Nethasp server and had to go through a few things to get it to work. You need to run the Lmsetup.exe and remove the license manager completely then re-install it. After that it worked fine.

You can do the same thing, it's just a little more involved to get it done. You have to set your c-plane, the go to the view manager, then right click on the system plane with the same number as your current c-plane, then copy the selected plane and give it a new name.

OK so...Is the booth shutting down at 1:00pm on Tuesday? It looks like there won't be anybody left to show anything! How about ordering a few pizzas and having the meet at the booth itself? (does Papa John's deliver inside the convention center?)

Mastercam itself doesn't seem to have Long File Name problems, but some of the c-hooks and editors don't always like them (leftover code from the v5 days). I've found that using spaces in the DIRECTORY names can be an issue. File names seem to be fine. Unmapped network paths (servermastercammc8filesfile.mc8) seem to be OK now, but I still try to avoid them as well (Mastercam does still have an occasional network timeout issue though). I always try to use an _ instead of a space in my paths and will probably continue to do so until the v10 rewrite.

What do you mean by "debug info"? Are you getting things like psof, pheader, etc. after the code on the same line? Which version are you using? If v9 are you talking about the .err file? Post a copy of a few lines of the output you're talking about and maybe that'll help us help you.

CorelDraw 10 has the best raster to vector (tracing) function I've ever seen. There are more smoothing and fitting options than most other software. The bset thing about it is the ability to set the tracing so that a spline is created with each pixel being a control point. Corel can output a DXF as well, so you can bring that data into Mastercam. I usually create new splines from the existing curves, then use "remove control points" from the analyze edit box to smooth them. Also, running a toolpath on it, filtering to a looser tolerance, then backplotting while saving geometry seems to clean things up alot too.

Only in chaining can you mask to the current c-plane. Chain-options-plane mask.

Mastercam's raster to vector and engraving add-ins included an .ai translator. Opens them up right in Mastercam.