and tons of RAM.!!! edit: oops, just saw Jay's referance to RAM +1

if the code is g-code, use .cam if it is conversational, like the Mastercam MX2 post uses, then use .MX2 or .MX3.

Running a tape punch is a communications issue. CIMCO, either the editor in Mastercam or the full blown DNC system, can communicate to a tape punch. The bigger problem is whether the tape for the Mazak is Mazatrol or Gcode. I would bet Mazatrol. Mastercam will not write Mazatrol unless you have the Camiax add-on. Check the 3rd party pages of Mastercam or this web site.

If you don't compress libraries after editing them, you will definetly have problems.

quote: "blank paper space entities" box? On the File Converter's dialog box after you pick the file.

I'd probably go with Project-Blend.

yea, MC did that in V9.1 or V9.0Sp1. Prior to that, it would give you a '0' length dim.

I've got a Dell 8200 with Radion 9000. Works well. I have problems if I run multiple MC's, but otherwise OK. Make sure you download the latest drivers. Are you running XP Pro? That is what I have.

Charles, If I was to write a 5-axis post from scratch for someone, it would cost more than 5K for that one up development. The MC posts are great places to start, and are very close for Fanuc generic.

The mplfan should be pretty close. May need an adjustment to an M code or 2.

Go to 'Rough parameters' - 'Cut depths' and set 'Adjustment to top cut' to a value the same as your max depth of cut. Use a positive number, a negative causes it to cut higher.

From the mplfan post: code: pcssg50 #Output Constant surface speed clamp if css_actv, pbld, n, *sg50, *maxss, e Just change the *sg50 to "G92". If you need the gear(M42) output in this line also do this: if css_actv, pbld, n, "G92", pgear, *maxss, e

gplush, as far as the 'G50 Sxxx' output, maybe it needs to be "G92 Sxxxx" instead. Some controls use g92 instead of G50.

Did you upgrade the W2K to XP or did you do a fresh, full install of XP? You would be much better off with a fresh install. Updating leaves old version files mixed in with XP. Also what GeForce card do you have? Did you put in and update the XP drivers for that card. While trying to upgrade, you should probably upgrade the card. Maybe a GeForce FX5700 or Quadro FX500.

unfortunatly the higher res laptop screens are optimized for that higher-res. I have an Inspirion 8200 with 1600x1200 and it looks like crap at anything lower.

heavy, where is this post from? It is not on the CD. Take a look in the pdrill_2 section. If there is a pcout in there, you can probably remove it. was: code: pdrill_2 #Canned Drill Cycle, additional points pdrlcommonb if tapping = yes, #Flag the we are IN a G84 tapping cycle pcan1, pbld, n, pxout, pyout, pzout, pcout, prdrlout, dwell, strcantext, e else, pcan1, pbld, n, pxout, pyout, pzout, pcout, prdrlout, dwell, feed, strcantext, e pcom_movea changed: code: pdrill_2 #Canned Drill Cycle, additional points pdrlcommonb if tapping = yes, #Flag the we are IN a G84 tapping cycle pcan1, pbld, n, pxout, pyout, pzout, prdrlout, dwell, strcantext, e else, pcan1, pbld, n, pxout, pyout, pzout, prdrlout, dwell, feed, strcantext, e pcom_movea

Paul, careful with the tool setup on the control also. I think I remember something about the page where you set the tool dia. shows it as Radius but need to be Diameter. Or maybe the other way around.

LB, something you can put up on FTP?

quote: some suicide bomber or getting shot on your way to work! And this doesn't happen on you commute in Camarillo ?!?

Yea, the 800FSB should help. Allows for faster RAM usage.

We build all our systems with ASUS

Coming your way Rob.

From the Post PDF Book: code: linarc Category Motion modification Description Breaks arc moves into line segments. Values 0 - No, do not breakup arc motion. 1 - Yes, break up (linearize) arc moves. Code Example: linarc : 1 # Break all arc motion in the post processor pblock # A postblock linarc = zero if cuttype = two, #Polar [ brklinestype = rotary_axis + three linarc = one # Conditionaly break all arc motion ] . Notes: Search the post customization file for all occurrences of linarc to be certain it is not being reset in other postblocks when a global break up of motion is desired.

Darn, where is my Green Lantern De-coder Ring !!!

L-M, from the MpOkuma.pst, code: # -------------------------------------------------------------------------- # General Output Settings # -------------------------------------------------------------------------- sextnc MIN #Set Extension to MIN sub_level : 1 #Enable automatic subprogram support breakarcs : 1 #Break arcs, 0 = no, 1 = quadrants, 2 = 180deg. max arcs arcoutput : 0 #0 = IJK, 1 = R no sign, 2 = R signed neg. over 180 arctype : 2 #Arc center 1=abs, 2=St-Ctr, 3=Ctr-St, 4=unsigned inc. do_full_arc : 0 #Allow full circle output? 0=no, 1=yes helix_arc : 0 #Support helix arc output, 0=no, 1=all planes, 2=XY plane only arccheck : 1 #Check for small arcs, convert to linear Change it to this: code: breakarcs : 2 #Break arcs, 0 = no, 1 = quadrants, 2 = 180deg. max arcs arcoutput : 1 #0 = IJK, 1 = R no sign, 2 = R signed neg. over 180 breakarcs : 2 to get 180 deg max arcs and arcoutput : 1 for the R output