quote: My last post was for the poster who ran it in another software with "similar" settings, apples and oranges. Roger, You shouldn't be too quite to judge the other software as I have used both extensively and know were the issues are with both. I thought I would put a few things into perspective regading the timings as because this is really what it is about. My intent was not to throw the SolidCAM curveball in to show how slow or how fast to convert anyone to another CAM system, it is to present perspective.

keep your pants on!

Tempature is everything. Take a look at the PC specs that I tested the bench mark with almost 13min with nothing running compared to 2min on what I consider a mildly OK PC 5 or 6 years ago.

Loaded the the same model and applied the equivilent HSM toolpaths (Not much different the Mastercams HSM) and calculated first time. This is more of a comparision of a Gala Apple to a Fugi Apple.

Well I know this benchmark well by now and I know this is a Mastercam benchmark but I thought I would compare the numbers in SolidCAM2007R11, which also uses Vero's "Machining Stratigist" engine. Note SolidCAM has been using this the Vero core for its HSM longer that what Mastercam has. machining STRATEGIST Mastercam X2 SP1: 12min 21sec Desktop Pentium 4 3.06GHz XP Pro 2GB Ram SolidCAM 2007 R11: 2min Desktop Pentium 4 3.06GHz XP Pro 2GB Ram Note: When I benchmarked the time for SolidCAM I was also running Mastercam,Outlook as well as other various applications. Whats With That!

SolidWorks

quote: Outputting tapping with no M03 on most controls will cause the spindle to run only during the tapping of the hole Doesn't this really only apply to the first hole as there will be stops prior to feed for orientation, and then change of direction to feed out then stop at feed/clearence plane then position for hole two and so on..... I still have the M3 in my post output mind you. quote: (PROG: A) (DATE: 07-24-07) (TIME: 15:02) (NC FILE - Z:OKUMA3A.MIN) (MATERIAL - STEEL INCH - 440 STAINLESS - 400 BHN) (POST NAME - ITD_Okuma) (****TOOL LIST****) (T12| 5/16-18 TAPRH |H12|D12|Dia .3125" ) VTOFD[12 ]=0 (****PROGRAM START****) G90 G15H1 G0 Z30 VMPC2=1 VMPT=0 (PROGRAM MAX: Z1.") (PROGRAM MIN: Z-.5027") N12 M1 (TAP_VENT PINS) (T12| 5/16-18 TAPRH |H12|D12|Dia .3125" ) (OPERATION MAX: Z= 1.") (OPERATION MIN: Z= -.5027") / T12 M6 G0 G90 X-3.1031 Y1.8018 S180 M3 G94 G56 H12 Z1. Z.05 G284 Z-.5027 R.05 F10. S180 M54 X-1.1011 X1.1011 X3.1031 X-3.1031 Y-1.8018 X-1.1011 X1.1011 X3.1031 G0 Z1. G0 Z18. Y18 M30 %

Is it just a matter of odds? You tell me.

This specific instance is a first of this kind for me as well. There are other OP manager issues that have been brought up and indicate that there are issue with the OP Manager and some of it's feature and till this point has been at times bit unpredictable doing certain things that have raised me eye brows. Never a crash though just more of an unconveinence and a PITA. quote: What I don't understand is what could be different from the way I do it to the way it is done by the ones that are crashing? Remember this time it is not an application crash but a machine crash that shouldn't have happened. Imagine doing a semi-finish helical bore and qualifying the tools Dia and depth and then copying the operation removing the stock allowance, regenerating and post. Ready to flawlessy run ...... not in this instance. First thing it does is rapids to datum and plunges. this is not what the parent tool path did. Regen the problematice toolpath again and it solves itself????? I do this type of coping all the time. This is the first problem of this kind. Is there any diffence in the way we do it probably not.

Thin Client?

email sent to QC

Thanks Colin for taking a look.

Gcode, I'm aware that this has been dissussed numerous times....I'm always invoved. quote: If you drag and drop OPs you're going to get bit. So what you are saying is that if I use a feature in Mastercam that has been around since what V7 that I will produce code that will crash the machine. Stop and think about it! The feature worked great in previous to X versions (How long has X been around, not to mention the lengthy development and Beta testing). Should we all go back to version 9 because similar features in X don't seem to be predictable enough. quote: Yes, its a pain and its not fully Windows compliant, but it works and it doesn't crash your machine. Thats not even V9 or CNC software compliant. If it dosen't work and is not going to work get rid of the option. This has been a long enough standing problem for CNC software to either fix the problem or get rid of the feature.

Ron, You can disagree all you want. I am a long time user of Mastercam as well its Solids option. Trust me I realize that this is not Solidworks or the like it was never intended to compete, it was intended to complement the use of people already using solids and to be offered to small shops as a basic turn key modeling/programming investment. All that is fine. What I have issues with are features that that don't either work as advertised or features that are more a hinderence as opposed to a feature that should work well and not give you more grief. If you'd like to talk about processing power and it being the root of all my problems, I admit the PCs that I am running are not the most current or top of the line out there but they are repectably good machines with my laptop being the best of the lot. I would gladly drop 8 or so grand on a new system if CNC would tell me that that would fix alot of the pending issues with all the quirks and short commings that seem to be ever present regardless of release. I have recently compared functionality up against competeing CAM Products to do with Solids and find for the most part these systems working quite fluid whether this be creating or working with solids, creating toolpaths on solids that more associative to its features as well as the parent model. Mastercam has a lot of great feature and has been benchmark for alot of feature for other CAM products in the industry. When it comes to solids this is more a selling feature than a productive tool.

Ron, You sound like a salesman. All that Ron is saying is true in respect to the advantages of solids. Keep in mind that Solid Modeling in Mastercam is limited, toolpaths on solids makes the whole process slower (alot of momentary hangs on simple prismatic operations).....

quote: I don't understand what you mean by *and if so in what?* Are you importing from a Solid Modeler, are you or will you be modeling in Mastercam exclusively. Yada Yada Yada

Do you design in solids already and if so in what?

High all I've been pointing out (complaining) issues with the Operations Manager in a couple of threads. As the file size has grown the OP Manager seems to become instable regarding its group structure as well as showing problems while using/dragging "Copy/Move Before/After" feature. As stated by a number of users "I found if you don't use that feature and you copy and paste or just recreate the Operation everything works fine." What kind of BS solution is that. I loaded a folder on the the Forum FTP in "/Mastercam_forum/MCX2_Files/C_Crash", The folder contains a MCX, Screen Shot and a Code file that I captured and saved in the moment right after I found going some where that it wasn't supposed to. Plunging to z-0.875 into hardened 420......I caught it, but of course I'm not impressed. As you take a look at the files the operation in question is #61 and it is the finishing path which is a drag after copy of operation #60. All that was changed in oiperation #61 is the stock in X & Y was set to 0...regen....post...run. The code then instucting the machine to plunge at X0Y0 to Z-0.875 then directly go to the start point of bore 1 as it was supposed to do from the get go originally. Now if that isn't enough I had the present of mind to save code, capture the screen shot and save the MCX file in that state. Here is the kicker Operation #61 being clean an not in need of regeneration, I decided to regenerate and post the code....plunging into solid was gone and the code was as it should be. Please take a look and let me know what you think. CNC you can get a hold of me at [email protected] or better yet at 604-946-1622.

quote: Only with simple straight forward parts, certain types of features WILL get lost. 1000+ The direct translator feature is more of a selling feature than a useful tool.

Yes

Well you can start casing you tail with all the things that will cost money to speed up your system, this one is here ready and waiting as soon as Vista is adopted, or you could just buy mor RAM. My Dell M90 was purchase with 2GB of Ram as opposed to 4GB for the reason that 2x2GB Dimms was going to cost me 2 grand now I can get it from crutial for 350 and I don't have to screw around with alternates and just RAM disk what I need.

Doesn't Ready boost in Vista do the same thing amd all you need is a USB memory stick. Link Microsoft

Sweet. Thanks Craig

Good Deal!

Yor new machine is pretty heavy, what was the approx. cost on that one?