Just guessing that they will be traded. The 3016 isn't a bad machine, but the 4020A(longer "Z" stroke) has had several issues lately, especially after the flood!

Ok guys, I'd rather have Mori or Makino too, but for a light duty aluminum extrusion and drill machine, would you go Fadal or Haas? Looking to replace two vertical Fadals, 4020 and 3016. I've no experience with the Haas, but some seem to like them for the lighter stuff. All programing would be offline, any post issues with the Haas?

I've got two licenses for edit 5 that's still working. I do need to transfer one of them to a new computer and have been having trouble getting hold of Anthony. Maybe he's busy with whatever is changing.

That's him, usually been able to fix any problems I've had with their cutters. We did get one batch of inserts that weren't up to par. Likable trio, but a guys got to go with what works on the job he has.

Cobra, we're running 451 sfm, 117 ipm,.05 dp. in either 15-5 or 17-4, don't remember. Cutter is the 1.5" version of your Iscar, in a 40 taper vertical. Have you talked to James or Matt, they seem to be pretty good with that tool. Matt is the Iscar rep that originally set us up with the tool, but has since moved to turning.

So far so good, changed the active profile to solidworks, the desktop management profile to cad, and disabled the save bitmap. I'll wait till I've got more time to update drivers. That weeks downtime from all the water sure doesn't help with keeping up. Thanks guys

So far we're small enough(11 machines, 1 shift) that I send all programs to the machines. No programs are kept in machine memory after the current run. No program is downloaded from machine to working directory!!! Any changes needed are made in MC and reposted so everything is current. This way I know what they're running and where they got it. As we continue to grow I'm sure there will be changes, but there are no plans for programs to be kept in the machines.

Gunnar, curious as to why the trouble loading nvidias drivers. I haven't tried it yet, but was wondering what you ran into.

Just loaded my new HP nw9440 laptop Fri., XPPro,duocore 2.0 mhz.2gig ram, QuadroFX1500. Getting random crashes, no two at the same place, none with error messages, they just go to the screen that sends crash reports to CNC. I loaded from disks sent by my reseller that are the latest builds. I think there was a file to download from mastercam for XP users when X first came out. Is it still needed? I didn't see anything on the website, but probably overlooked it.

Really like it so far, never ran a laptop and some things seem a bit clumsy yet. Got a wireless mouse going and that helps a bunch. Had a few random crashes with MC, but so far haven't been able to tie anything down.

Checked my new HP nw9440 laptop, Duocore 2.0 MGz, 2 Gig Ram, Quadro FX 1500, Win XP Pro. With settings as it came from factory,(let windows choose what's best for your computer) 9 min. With settings set to Best Performance, 8:45 All in all, quite a change from the 15:30 min on my old desktop! Almost glad it drowned in the flood.

I just got one last week,installed whatever driver was on the cd and haven't gone on the web to update it yet. Works fine so far, but I'm starting to have muscle issues with my arm. Never had problems with the old wired mouse.

Thanks guy. I need the history tree as the second part will require some slight editing of the solid for thicknesses in various places. Guess I could delete those sections and remodel them. I've been importing the fixture since have quite a bit of the operations done in this file and was just going to re-assign geo chains. What I've started so far is to go back to the original file, save as, delete that customer part, import the similar part and start assigning geo to the original operations. The fixture for the second side is where the problem was, I'll just move the second part to orient to that fixture, edit the solid fixture to fit and start reassigning geo. to operations again. Couple hours lost, but not as bad as I had feared.

I've got a fixture built and trying to merge it into a second part file. Getting the no matching opfile error and several solids missing from the fixture. I've modeled it with the wireframe on one level, the solid on another for each different solid. I did a search and see that it is an ongoing problem for the last several years. Didn't see a work around. Anyone found a way to do this?

Glad I don't do any moulds! 15 Min. 30 Sec. P4, 2.8 Ghz, 1Gb Ram,Quadro Fx500,2000pro

Had that on 1 pocket on 1 part. Don't remember the particulars, but managed to find a work around that time. It will give you a start!

The tool path is all set to a plane built from geo. on the face of the fixture. I was just switching back to the default planes for geometry creation for the fixture. Seems to be something about setting them from the bottom menu and then changing from the view manager. I dunno, I can get around it, just wondering what I might be doing wrong.

I'm not sure I'm really doing this right, so that may be the problem. Programing a horizontal, have the part in the front plane. WCS set to top, C and T planes set with geometry to G54(front)through the planes button on the bottom menu. After programming a lot of toolpath, I decide to add some geometry to the side of the fixture. Go to View Manager(right click menu) and move the C and T planes to top(going to check on some stuff before changing to side). When I hit the green check to go back to the main screen all my operations have the dreaded red x. Check the planes through the operation parameters and everything is correct, just needs regenerated. If I change the planes through the button on the bottom menu there is no problem. Do I just not understand the use of the view manager or is there a bug in the system?

I've got nearly as many installs as Surface. I plan on keeping 91 for a while, but how do I take out x, x2sp1 without causing trouble with shared files or configs.?

Be sure to do a side by side installation. That way you can still use what you're using now.

Most of what I've seen here on the board has to do with STL files used as stock for verify. Lathe stock is also causing a bit of trouble. I don't have lathe and rarely ever use STL files, so it's been pretty seamless for me.

I run autosave, but all files are saved to the server. The server is backed up every night to an offsite location, with a back up for each day of the week. You end up with a weeks worth of back ups at all times. More than once I've needed one of those files!

Depends on the program. I have a bunch of programs for our vertical Daewoos that also run on the Horiz. if we hit a schedule snag. As long as there is no rotation of the tombstone we get by with it. Our verticals are split table pallet style machines and I generally run the first side of a part on the 1st table(G54), and the back side of the part on the 2nd table(G55). I don't have to switch planes and have even gotten away with putting a 3rd fixture on the backside of the tombstone by inserting manual insert code commands to rotate the table.

Thanks guys, I'll give it a try. Lost track of this one for awhile.

Guys and Gals I'm trying to setup my post for rigid tapping on a vertical machine center with Fanuc 21i controler. The post is a much modified MP_EZ. I've gotten the M29 and G95 coding through hard statements, but am having trouble getting it to switch back to G94 before the next tool. I tried putting in another hard statement with the G94, but it puts it in after the first hole instead of after subsequent holes are tapped. Also having trouble finding where to get the feed switched to pitch. This is the block for my misc #2 now, just need to find out how to switch back to G94 and feed to pitch. pmisc2$ #Canned Misc #2 Cycle (User Option) pdrlcommonb pbld, n$,"G95", *speed, e$ #added slj 4/12/07 pbld, n$, "M29", e$ pcan1, pbld, n$, *sgdrlref, *sgdrill, pxout, pyout, pfzout, prdrlout, *feed, strcantext, e$ pcom_movea