John, as David said, quote: ..was save some as a parasolid it saves all solids In V9, you could save and write a parasolid file for one solid, or what was in view. This doesn't work in MCX. X saves all solids in the file whether you could see them/select them or not. Some of us think its a bug...

Not sure between the Haas and Fadal but.... What I've done in the past is to make my own blocks for each spindle when using the same angle head between them. Or make a block with both positions and bolt pattern if is has room.

Make sure to create a backup of this post in case theres a problem with the edits. Look in your post for " pdrill_2 " ..... You'll see a call up for feed, delete it. That should get rid of the feedrate on the second line. About the feed rate.... Look in your post for where the "F" is formatted. Something like this: fmt F 15 feed #Feedrate The number 15 outputs only to 2 places. Change that to a 12 (or whichever number will create the 4 place decimal). Now you should get 4 places if needed. Just use the number that the format statement will create a 4 place. fs2 12 0.4 0.4 #Decimal, absolute, 4 place If you don't have one, then you'll need to create one. I wouldn't change an existing line though. Its possible that other things in the post are using the same and you may end up with unwanted code elsewhere. Now, this will affect all feedrates (formatting "F"). If you have an endmill that for some reason feeds at "5.6519" in your cut, thats what will post. If you want to avoid this then make sure to check your feeds in the cut,.... OR..... if you want the post to round off the feed for you, then you'll need to create a new variable in the post for tap feeding.

The Mazak post names the file the same as the program number. If you do not save the file as a program number, it gives you the alarm. To avoid that, look for this in the post: #ppost #Rename the NC file if not the progno name # if snamenc <> snameprg, # [ # result = fclose(sorgncfile) # result = remove(sprgncfile) # result = rename(sorgncfile, sprgncfile) # result = mprint(snameerror) # ] Add the "#" symbols in front of these lines in your post and you won't get the alarm anymore. As for the tap feed, I believe the post is already set for feeding in IPR. Look in your post for "ptap" and you should see something like this: feed = 1 / n_tap_thds

Just like it says.... On the tool parameters page (of the cut operation), you'll see a button that says 'home position...' Check the box then click on it. Input the G92 position there. For G52, I'd say you'll have to create the code in the post to do so. You can use misc integers and or reals to output the the code and the L number. Or, can write a post utlizing the WCS to output for G52 instead.

I'm guessing here because I'm contemplating on doing the same thing. Where does your MMD (machine definition) files reside? In the system default, you can set it to the network, but when you open a machine def. file, theres a setting in there too to search for the tool library associated to it. I'm assuming, each MMD file (if its at each station) has to be set for the network tool library as well. Unless someone else knows otherwise...

Kudos to James....

A coulple things,.... whats the code look like where it crashes? And what do you mean by crash? Is it just gouging or the tool goes thru the part in Z? HMC or VMC? 2D pocket or pocket surfacing? Might need to see the file... and need a little more info. And... Welcome to the Forum.

Like everyone else says..... SCREW EM!! We have a bunch of A55s (including an A55e... 3300 ipm) and program with MC. No problems. I've programmed SNC, A77, A88, the old FNC... all with MC. It's possible that HSM (whether its Cimco, MC or other) may be violent for the machine. But that has little to do with the software and more to do with the programmer using and setting the parameters of the cut... As well as how well the geometry is manipulated or otherwise in certain areas of cuts.

Lars, something like this? . . #NC Program Extension sextnc .NC sextsub .NC sextaux .NC sorgncfile sprgncfile snameprg

Nick, how goes it? Yep, I have always used lock tite as well. And on High speed 40 tapers. Although sometimes I get "out of habit".. The biggest problem I've seen with the "tighten the sh!t out of it" method, is the periodic cracking of the pull stud right below the stud flange on the thread side, in particular to thru coolant studs. I've seen these tools come apart in the machine at full speed. Thank god no personal injuries yet over the years. You want a wake up call??? How about a 50 taper pull stud letting loose at 15K??!!! HELLO!!

quote: Metal Flake Did you try blanking?? This doesn't work either... I'm with David, I think its a bug....

Murlin.... Metal wrote... quote: I have 5 or so solids all on different layers and I just want to export one of them. I've been trying this with parasolid and can't get it to work. It works for other formats, just not parasolid it seems....

And I recant..... I've never tried it with parasolid file. I can get it to work with other formats like a .stp file for example. Seems though that parasolid converting takes all of the solids regardless of whats selected. I think its a bug. You can though, 'save some' as a MCX file, then save that single solid as a .x_t file. It's an extra step though.

What did you use as a select for the solid when saving? If you have your solids on different levels, and you only want to save a solid on one level, click on level and highlight the level number, then ok. It should only save the one solid. It works on mine....

I haven't played with this much in X yet but... In V9, I have posts that will do that. In order for it to work though, I had to create a new feed variable, then give it the math to scale it as according to the rpm. This post works in X (although I still have some changes to make for X because some of the "lingo" doesn't work anymore). It seems that X is the same way. You'll have to create the math in a post you use to scale the feed as according to the max rpm. Unless someone knows different for X....

quote: Oh, and there is no way not to use them. And they are not going away... IMHO, this is a bummer. I have up to this point, have had very little if any problems moving programs from machine to machine, control to control. In this shop we have a dozen + types of controls and a half a dozen or so machine makes or all types (HMC, VMC, Lathes, Multi-Centers etc.). I understand its use, capabilities and future progression. Believe me, I will use it (besides the fact I have to). However, I don't necessarily think it should be forced. Many places don't have a need (or feel that they need) full blown verifiers and don't even have machines beyond 2-1/2 axis coupled with MAYBE a 4th table. As far as program/machine compatability goes, good posts should already handle that. I have posts (as well as many others here) that will change the necessary codes, scale feed rates to different rpms, give an error messages for comp types etc. Oh well,.... back to the game....

Checked the Verisurf site as well. Doesn't look like its out yet.... just V9.

quote: Heard he is a manager somewhere in Asia (Singapore?) for a company that used to be his main customer I doubt its AMAT,..... StorageTek ??? I'll have to pay a visit to his brother. Did you get the macro yet? Brett has the right idea with a while/do loop. It's not built into any posts I have now, I think I'll write one though.....

Forgot to add.... the longhand for MC output will still have a G0 in the retract so you'll have to edit it out in the NC. edit: looks like macro then!!! I wonder if CMS will sell the building? He owned it outright plus another few acres next to it. I hear Perry is now working for a company based out of China.

Mark, write a drill macro (or have one written) to do what you need. I'd do it but I gotta get out to the floor. Also in V9 (since I'm not sure about X yet), you can change the output in the post setting for "usecanned" to no and it will generate code in long hand instead of a canned cycle. Haven't played with that much so I'm not sure if it will do the job for you. Also, do a search too. I seem to recall someone posting a macro program to do just that some time ago.

This stuff is soft, soft, soft. It's probably easier to to view these links on commercially available "pure aluminum". 1100-O Aluminum or 3105 Aluminum

VERY COOL!!!

You have to map it to the 10-key on the right. Go to 'Setting > keymapping' and assign the numbers to views if you want. You can even add it to the maplist so that you can use either the 10key on the right or the numbers on the keyboard.

quote: You'll be superised how much it's still the same. quote: Hit them in sequence. It's a single finger pick just like before. Create Arc was C A in V9. Not too much different. Mike, You are correct to a certain extent. Physically, its not "that much different". You have one extra step is all. Mentally though, is another story. I don't have to "think" much when I'm designing or programming. My fingers for the most part know exactly what key to push to do what I'm thinking. It just goes there (if that makes sense). When I open a door, I don't "think" about turning the handle. My hand just does it. When I open a beer, I don't "think" about having to twist the cap, my hand just does it. Its that extra step (or steps), however so little, thats causing a bunch of grief in the short time that I've been using it. I've got some serious stutter issues happening now. I'm about ready to tie my left hand to the back of my chair until I get used to all of this...