"Did you look at the "High feed" option in the operation manager. It is located next to the "G1" post icon. This might be what you are looking for." I checked that out. Looks interesting for perhaps global editing of parameters. But for not for my needs, I just want a simple corner control switch. Being a newer user I'm shocked it has not been in MC for years now, it's a very common requirement for proper milling. -- Bill

Thad, Like I said, I feel it's not appropriate to discuss comparisons (this is a very passionate group...) I will however focus on needs for features I'm used to and would benifit MCX. Jay, Like Gcode said, it should be a switch in the operation. There is no better way to do it. Toolpath edit and At Point are not the best place when you work in a revision changing environment. It's also way more obvious to other programmers who may have to work with someone elses file. What I'm finding is other programmers (in a hurry and lacking patience) just run the tools based on the worst case corner load - which is unfortunate. -- Bill

Gcode, +1... I have 150+ operations with various 4-5" facemills doing 800 sfm at times in cast iron. The machine load is 60-70% on straights, >100% corners. The control alarms at 105%. We load multiple parts unattended over night and weekends. So yes, I need this feature. Slight side note: You mentioned "the so called high end systems" have this feature. I won't say the name of the system I used as it wouldn't be appropriate in this forum but... The one I used actually cost a little less than MCX combined with Solidworks (which is the comparison in features IMHO). So, at that price point I expect to have this kind of toolpath control and more. That all said, there's a workaround for everything . -- Bill

Bruce, Yes, found it. Thanks for the help. That said, I really don't want to set all my programs output to corner slow downs. Just the face mills. I was hoping to do it on an operation by operation decision. It really should be tied to the operation. My previous system had this ability. You would go into the operation and select Corner Control (you could define what was a corner by the angle of the two paths), tell it percentage of the tool dia to slow down and if you wanted it to slow down in steps or all at once. For now, I guess I'll have to break up the geometry and use Change At Point... -- Bill

In MCX - Mill Contour... Where is the setting for "slow down (either percentage or actual values) in corners"? I have a bunch of toolpaths that need to have the facemill slow down in corners. I'm sure it's a simple setting right? Thanks. -- Bill

Roger, "Disable front buffer" option did not fix. Gcode, Turn off unified back/depth buffer did not fix. Then, tried both together - did not fix. Finaly (and as expected) "turn off hardware acceleration" did fix it. Now my backplot works ok but my general display is pretty sucky. We'll see what the next video card brings... -- Bill

When using Backplot, the tool jumps to and from the next position unless I move the screen around. Ex: Backplot / Single step the tool - each time I step forward the tool goes there then jumps back to the previous postion. If I move my spaceball (or rotate with the mouse) the tool then properly moves forward and stays at that postion till the next move. Current setup: Video card - Nvidia Quadro FX 540 w/128mgs MCX mr2 - Intel 3.4 w/ 1gig ram I'm getting another gig of system ram and a new 256mb Nvidia card this week. We'll see if the new card helps. I'd hate to hear the old, "turn off the acceleration" answer... -- Bill

Robert, Heads up on the Vericut Direct chook... I'm working with CGTech right now on some issues with it. 1. Custom tools from MCX don't convert to Vericut well. This is an issue for us since we use extra long holders. Since holders aren't really shown in Vericut, I use custom a custom tool to define a cutter with a holder as one unit in MCX for Accurate collision detection in MCX. For us, It's very important to see the holders. 2. You will end up remodeling all your tools and holders in Vercut since they support complete tool and holder component assemblies. 3. Not a tooling issue specifecly but... if you decide to use multiple toolpath groups under a single Machine Group in MCX, Vericut will convert those all to individual Machine Setups - not a good thing. We are still working on this issue with CGTech and hopefully it can be resolved soon. We use lots of toolpath groups as our programs tend to be large with lots of tools. Typicaly, we group by tools since you can't switch the Operation Manager to list by tools at this time. -- Bill

System integration is the kwy. Perfect example: Mastercam tool libraries... Access database (home made)... Vericut tool libraries... Autocrib software... None of them integrate with each other very well unless you really get under the hood of each and do some coding. All four must be kept current and that sucks. For that reason alone I've been trying to get TDM and a certain compatable cadcam system that could talk to it. When you've got 1000+ holders and 10 times that in tools, the cam system is easily disposed of if it doesn't fit in. With the right cam tools you have: TDM, the cam system, and Vericut all sharing the same exact libraries. The tool crib ties into it as well. -- Bill

The unpredicatable results bring up a thorn in my side with using "max rough depth". In the real world - by default and without a calculation - we want to tell MCX exactly the depth of cut for each pass. This is critical with specialized insert cutters and high speed milling. Another need is alternating depths of cuts for inserted tools. This would reduce premature notching of inserts.

If your company will spring for Vericut, get it. There is no subsitute. The level of detail to which you can interagate the as-machined part is second to none. If you add the MC to Vericut converter it will grab your tools (and holders) to give you ultra accurate simulation of tools & holder collisions. It's very nice to have open will your programming to do quick verifies of say kellering to see exactly how it will turn out. An additional module is Machine Sim which shows the parts being machined using the actual kinimatics of the machine. It's pricey but if you do large parts with clearance issues, it's awesome to have. -- Bill

Scott, "They kept and spent my 401k money as well, I noticed you didn't mention it, did you get paid ?" The issue has left the Dept of Labor and moved to the Dept of Justice. There's a good chance he could get jail time now but it will take time. The "wheels of justice" are sloooowww. "When I was at Simon my level 3 seat with solids was registered,, and your UG seat was as well,,,,what happened to those seats?" I'm still using the same UG seat and Dan's using the MC seat though no maintainance support for either (yet). Morey Simon has cracked versions... I'll email you direct with contact info for your 401k monies. -- Bill

Hi Scott, Yup, it's me. Hope your doing well. We're a little better off here now. At least the checks clear.

I never post here but thought it would be important for the folks here to be warned. There is a job opening on the CNC Concepts website - http://www.cncci.com/ for a company called UDASH Inc. They want a 5ax programmer using Mastercam and or UG. The contact, Morey Simon stole thousands of dollars from the employees of his previous company - Simon Brothers Precision. He also stole our health benefit contributions and payroll taxes. This is all on record with the Cal. Dept of Labor. As one who lost his money, I'm giving you all a heads up to the charactor of this person. Btw, those are cracked versions of Mastercam and UG as well. They've just been reported to the BSA. Ad follows: Location: Chatsworth, CA Company name: UDASH Corp Contact name: Morey Simon Email: [email protected] Submitted: 06/25/2004 Job name: 5 axis CNC programer Help with relocation: No Machines owned: SNK Controls: Fanuc Cam systems owned: MaserCAM / UG Assume all aspects of programming, for a 5 axis aerospace contract manufacturer. Experience necessary. Must be able to hit the ground running. We handle a wide variety of precision machined components. Individual should be very detail oriented and have excellent organizational skills. Submit resume together with expected pay.

Sorry for the posts. I just read the forum guidlines and see I must be a registered MC user to be here. While we do have one seat at our company, I'm not the user. Logging out... -William

>>William, >>Do you do alot of 5axis programming using MC. >>What kind of 5axis machine are you programming. >>LEO No. I do 5ax with UG. It's just that I enjoy the conversation here. Programming is programming. : ) -William

>>Unfortunately, the company I work for is buying unigraphic$<< So Jamman - does this mean you'll havet to use UG in the future? That's pathetic! Maybe if you tell your management that UG programmers make over $25 bucks an hour they'll reconsider. William

First, you're on a Mastercam forum so don't expect a bunch of "buy UG" responses. Also, Masteram will do 90% of the 5ax machining that UG does twice as fast. -William

Just found this on the net: "A machine shop in San Fernando (LA) is looking for a CNC Programmer. Must have a minimum of 5 years experience using Mastercam. Must have experience setting up and operating mold making machines. Starting pay is $20/hr." Just so you all in the midwest don't get excited -the 2001 median home price in Los Angeles is $241,370. (and climbing). Guess that programmer won't be owning a home anytime soon... William

I'm not sure if your single or dual cpu config is decided but a little more info: If your going to keep this system for a while (2-3 yrs), consider the dual setup. No, Mastercam nor Solidworks support SMP yet but I would assume it is in their near future(?) Windows 2K itself also works faster for many tasks on the dual. Along that line, AMD still does not have a dual mobo available. Perhaps there's some news on that? The single Athelon works just fine on with UG. It is not officially supported though. Trust me - it is the graphics cards that really matter here anyways. On the INTEL platform the XEON is the only chip supported on the dual mobo at this time (unless you want to drop back to a pentium III). Don't assume the XEON is really expensive. I see right now you can pick up a Supermicro P4DC6 mobo with two XEON 2.2 w/512k chips for $1,615 on Pricewatch.com. Ram would be extra.(I've got an eye on that setup as well). That would be a SCREAMING workstation. I'm sure I'll be flamed about it's requirement for Rambus ram but it's not much more and works just fine and is reliable. It also requires AGP 4 graphics card (1.5v). Given the fact your talking about UG, Solidworks, & MC on the same box, I'd go the dual route and load it up with ram since you've already made a $30k investment in software why go cheap now. Graphics cards? I like the Elsa Gloria series. Rock solid. -William quote: My deadline to make systems is nearly over yet I'm hesitant about CPU. Will you tell me why anybody doesn't recommend Athlon? Is it because some instabilities with their motherboards? Please tell me what are the problems with it . I hope Bullines and other users can tell me what should I do about CPU. [ 04-22-2002, 02:26 PM: Message edited by: William Grizwald ]

Single procs are fully supported. Given the now low prices of duals though, they are highly "recommended" though by no means required. If you go to the EDS site, there is a list of supported systems - MOST all of which are single cpu. There is also a list of supported graphics cards (which IS the most important issue here). Go to: http://support.ugs.com/online_library/certification/ >If you are going to run UG18 you need a dual >Proc. >this is the only thing UG supports.Not being the >software it self but the company. >they say to only run this on a Daul or they will >not support you. >And they want certian mother boards and Video cards.

Have you looked at the future of the Alpha systems? Fewer software vendors are porting to it anymore. I predict support for the Alpha will die very soon from ALL vendors. I would not base your decisions on a dying (though still fast) processor. Wm