I've always thought that was a pretty useful feature that very few other systems give you the capability of doing. Create a horizntal line that has the sam X values of 2 known points where the Y value is say .5 larger than the first point. After you pick the second position and the prompt comes up with some 10 digit number, hit the right arrow key to un-highlight it then type in "+.5" and voila! Pain in the a** otherwise.

2 things... First, I don't think the entries in the dialog boxes on those pages are user editable. I might be wrong, but I think that requires a different compile. Second, in either case, (here we go again) Contact your dealer and tell him/her about your situation. Mastercam is used worldwide and translated into many languages, so your dealer should be able to work out something with a dealer from another country that speaks the same langague as your machinist and get you a copy in that language.

quote: Usually when working with solids I parasolid out and then back in, this gives me a 'dumb solid' but one that requires no regens and no issues when translating ect. also a great way to get the face curves. quote: looks like i will have to get used to doing what you do alan , thanks . Make sure that you REALLY wnt to lose all of your solid operations. As allan said, the message is coming up because Mastercam is trying to delete the geometry that created the solid before the solid itself. Hitting OK is perfectly safe and you will not lose anything of "value". If you want to be absolutely sure and not see the message, use transform-translate-copy, then delete the original solid, then delete the current system group. It looks to be remedied in v9.1 beta. [ 10-07-2002, 04:44 PM: Message edited by: gstephens ]

You have to compare x coordinates throughout the whole chain (really tough to do), and determine whether or not the x value gets smaller then larger over the course of the cut. Somebaod has probably done this for a post at some time (Yasnac?), but since the canned cycle code changed with v8, I'm not sure if anyone has dealt with it since. I'd look into it myself, but I'm swamped at the moment.

quote: What is a 5 1/4" floppy ? It's just like an 8" Floppy only smaller Seriously, do you have access to a 5-1/4" drive? If so, use the cvtold.dll c-hook. If not, find someone that does. [ 09-30-2002, 02:41 PM: Message edited by: gstephens ]

Also remember that the ONLY difference between Format 1 and Format 2 is the canned tap cycle.

quote: Those are really old. If memory serves me correctly, I've not seen values since V5/V6 era. Actually "Values" disappeared with v8.0 when it was FINALLY replaced with "Origin". Hours and hours of typing "0,0,0"...

This may not be an issue anymore, but some of the older posts had problems with multiple depth cuts after v7. The logic that allows the "keep tool down" hosed a bunch of <= v6 posts [1 that was on the v7 CD as well ]. So I would try a couple of programs with multi-passes and depth cuts [contour or pocket - doesn't matter] and CHECK THE OUTPUT CAREFULLY before running an actual part. If you used this post in v7,v8 and it worked fine, disregard the previous ramblings.

The spiral option for flowline was introduced in v8.1, so you won't have that capability with your current version (7.12 is not a correct number - 7.1 or 7.2b/c)

An earlier post said something about demos from other software always doing "Mastercam Bashing". One thing Mastercam can do that others can't is stand on its own merits WITHOUT having to cut down the competition. The biggest thing to me has always been: Mastercam will let the programmer/machinist cut the part the way he/she wants to. Sometimes you have to model the toolpath yourself (I never let Mastercam run an automatic path for me at all until v6), but there's ALWAYS a way. Also, since the people who wrote the software originally were MACHINISTS (not engineers), the parameters tend to ask the questions that the machinist knows should be asked and the toolpaths tend to do what needs to be done to cut the part correctly. Whew!

Henry, the parameters are in the .NCI for each toolpath. Make sure you're resetting the variable at ptlchg0 to catch it.

quote: I want to use the WCS and work offsets stuff for tombstone work You may want to use WCS for tombstone work, but I don't think you REALLY WANT to use WCS for tombstone work. WCS was created for (and in my opinion should ONLY be used for) doing tool plane/rotary/multi-axis motion on a part that can not be moved out of it's orientation to match the machine set up. Even if you use the WCS, you still HAVE to use C-planes/T-planes to acheive the rotations in the posted code. WCS merely will redefine "which end is up."

quote: no controller I know of will allow you to turn cutter comp on an arc move. Fadal is the only one I know of for sure.

I think the problem is probably either: 1. the X and Y need to be in the G8? line. or 2. the R needs the R0=+0.025 format. I think both of those are in the post we've got running at the Fadal plant.

Check out this for the official overview: V9Enhancements.pdf

You can also use the "Create-pattern" to bring in the file. It put all of the geometry on the current construction level. It also allows you you select where in the current file the pattern file's origin is placed.

Actually Ky at Fadal is trying it out. I got the gen5x post configured for the Fadal (and even came across some missing code in the process - Thanks Roger ). It look sgood with drill cycles all set up and everything. D. Contact your reseller and have them give CAD/CAM Consulting (805-375-7676) a call to work out a quote/purchase.

Also, are you using XP Home Edition? I'm running across more and more people with problems in that environment due to memory handling issues.

Biggest issue is simultaneous dual-spindle/dual-turret (coming to a Mastercam near you sometime in the v9.x era - I've seen it ). I'm working on a post right now to handle each spindle/turret individually, but it's on my back burner due to other projects. REALLY involved and gonna be pricey, but as of yet I haven't heard of a good one out there already (I've spoken with the Citzen AE's).

Since you're dealing with metric taps, the value in the tool parameter page is going to make all the difference. For a matric tap, the box is for "pitch", whereas on an english tap the value is "threads" [per inch]. This causes a HUGE problem when posting because the value is sent to the post under the n_tap_thds varible no matter what units are being used. So for metric taps your feedrate should be something like: feed=n_tap_thds to get mm/rev for your output. Make sure you add the appropriate G-code to switch to mm/rev (unless the G84 does it automatically).

Points first, then next closest entity (open chains based on one-way or zig-zag) to the start point. Are all of your chains closed, if not, I'll explain one-way vs. zig-zag in detail (too cumbersome to go into if un-necessary).

quote: Create - Spline - Curves You might also want to Analyze the spline, then go to Edit and reduce the # of control points.

quote: It's nice to have a golden source (the solid) so if I update the model, the toolpaths will regenerate. This is not the case if I export DXF's. This is not the case with solids either, since the edges choosen for the original operation don't necessarily exist in the new model.

quote: Also what are the asterisk's for? (C plane *12)etc. The asterisk shows up when your origin has been shifted from the system world origin (Alt-O).

Charlie...make sure you also get the latest appmch patch as well. Every patch since v9.0 has had some change made to the surface project toolpath.