I had a similar error message in a previous version of mastercam, my problem was that I ran out of disk space while it was calculating the toolpath.

Press AND hold the reset while jogging the axis. This works on some mahcines, but not sure about the xxxxor.

Did you figure it out? BTW the setting that I mentioned was in the Control Definition, Tolerances (Mill), NC precision andor Chordal deviation. I'm pretty sure my setting for the "Choral deviation (used in post)" was set to .0005 (inch) and we changed it to .0002 - this really helped with the facets.

We had a similar problem. There is a setting in the machine definitions (and maybe the post) for tolerance. Ours was set to .0005 (inch) but we changed it to .0002 and the toolpaths came out much smoother and the facets were gone. On the down side the NC files were bigger. I'm on vacation this week so I can't tell you the exactly where the settings are. But check the Machine definitions and look for toolpath tolerances.

Yeah... same problem here with large STL files, very slow loading and rotating views. However I use the trial version of Rhino, to view, shade and rotate the STL file - its really fast for that (and its free.) Edit I think it has 25 or 30 saves before it wont work anymore. But I just use it for a quick view.

quote: Copy-then paste to the Red Arrow of Doom -then delete the old OPs...never fails its a pain but its bullet proof. But what if I need the old ops? (ie semifinish copied to finish)

I have noticed problems only with Surface High Speed Toolpaths. Has anyone had problems with copyingcuttingpasting of other types toolpaths? Just trying to narrow it down. As far as solids... For doing toolpaths, I convert everthing to surfaces as well - saves a lot of time.

quote: Mark thats great and I'm glad that that works for you. That solution/work around will not work for me. How many ops/toolpaths do you typically create per file? The last file was only 20 operations when I first had problems, but I'm up to 32 toolpaths (and growing) as we speak... but some of my files contain 100+ toolpaths.

Below is a link to the problem that I had. My work around was by NOT doing any copyingcuttingpasting of the operations. Which took some time to reslect the geometry and set the parameters, but in the long run, this saved time because I didn’t have to regenerate all the toolpaths multiple times. Topic: Toolpath red Xed

I have had problems with coping and pasting operations. Long story short, it red Xed the original and copied toolpaths when I reopened the file. I emailed it to QC at mastercam and they said it would be fixed in a future release.

Try using surfaces as your boundry. link

What version of Moldplus do you have? I just loaded V9.2.076.7 and have not had a problem running it with X2 MR1 SP1. I got this version from my reseller.

From Mastercam's help file (X2 MR1 SP1) quote: The Mastercam IGES file converter supports IGES Version 5.3 and older.

First off, I sent this to QC at Mastercam and am awaiting a reply. I found a bug and can reproduce it consistently. I have 21 “surface high speed toolpaths” in my file. The first 18 are fine, but when I copied one of them and then removed the CAD (STL) file from the toolpath, the majority of the other toolpaths got red X, even though I did not change anything with them or the STL file. To reproduce the error, remove the CAD file from copied "high speed" toolpath and either regenerate (which may take a long time) or for a quicker check, run RAMSAVER without regenerating and you will see the red X’s. Does anyone else have this issue, or can you reproduce this on your system?

quote: It should just stay put and not move unless I move it and then new toolpaths should follow the arrow. Seems like they tried to complicate it too much by making it move on its own. Sometimes simpler is better. just my 2 cents. Dan +1, That's the way I would like it to work too.

I think this is an interesting toolpath. Also I would think that it could be made associative, MC could save the movements of the mouse as lines, arcs, points, splines...

I always thought is was a bug... One man's bug is another man's feature

For each type of toolpath the filtertolerance button is in a different location. For example; "Surface Rough Pocket" the button is on the "rough parameters" tab. Then click on "total tolerance" you will have an option there to set your tolerance and turn on arcs. (create arcs in XY) You may or may not want this. It is used to make the code smaller for a few of reasons. One reason is to process faster (posting), another reason is so that it can fit in you controlers memory, or faster DNC (drip feed).

Just a thought... Do you have your arc filter turned off? I know that makes the posting slower.

John, you beat me to the punch...

"eMastercam Forum Addicts" might be a better description.

As far as the post processor knowledgebase... I think for version 9 your reseller can get you a pdf file for a nominal fee (possibly free if you ask really nicely ). Version X and up the PDF's came on the instalation CD.

I noticed that some values did not import correctly with the MR1 install with regards to the machine control definitions. NC file extentions was one, as was arc support and Tool offset registers... One thing I noticed was that SP1 and MR1 use there own definitions. For example SP1 has its files in C:mcamxcnc_machines, where as MR1 makes a copy and places the new defs in C:McamX2-MR1cnc_machines. Maybe something got mixed up there?

Thats what I was thinking too.

I did an install of X2 MR1 and kept X2 SP1. I chose the option to migrate the settings from the older version to MR1. However not all of the machine definition control definition parameters were brought over. For example one of the machines does not use arcs so I have that disabled in the definitions. That setting as well as a few others did not come across in MR1 machine control definitions. So just a warning to all you out there to double check your machine control definitions after installing X2 MR1. I opened X2 SP1 and X2 MR1 side by side (dual monitors really pays off some times) and went through each of the paramters in the machine control definitions just to be sure. FYI - I just sent this info to mastercam...