I can't use that option because there are 5 groups of 5 toolpaths that use 5 different planes and the remainder use a separate plane. MasterCAM will properly use the first 3 planes then it changes any toolpaths after to the third plane.

I have a MCAM file that I use as a template. It has all the toolpaths I need to make parts that are similar. The problem I am having is that when I use it to import a group of toolpaths into older programs to update them, MasterCAM won't import more than 2 planes no matter how they are named or whether they exist in the current file. Does anyone have an idea how to get MasterCAM to import more than 2 planes with a group of toolpaths? Sorry, it appears that 3 is the limit

Could Mastercam please hire some programmers that realize designating an Error as Unknown doesn't inspire confidence in the software users. I would rather see some numerical designation so that at least a search for a solution has some relevance. Unknown Error for every anomalous program interaction is a very poor choice on Mastercam's part.

Thank you David, this information is very useful information.

Thank you again Colin, the opcode$ is exactly what I was looking for. Here is what I did to prapidout to achieve my goal. prapidout #Output to NC of linear movement - rapid if sav_mi10=0, [ pcan1, pbld, n$, sgplane, `sgcode, sgabsinc, pccdia, pxout, pyout, pzout, strcantext, e$ #pscool, jaw ] if (sav_mi10=1 & opcode$ = 3), [ ] if (sav_mi10=1 & opcode$ <> 3), [ pcan1, pbld, n$, sgplane, `sgcode, sgabsinc, pccdia, pxout, pyout, pzout, strcantext, e$ #pscool, jaw ] #Modify following line to customize output for high-speed toolpath #tool inspection/change points if rpd_typ$ = 7, pbld, n$, "M00", "(TOOL INSPECTION POINT - POST CUSTOMIZATION REQUIRED)", e$

For future reference, what are the other opcode$ types?

Thank you for your response Colin and I appreciate your concerns. The reason for the bare bones code is that the operators request the code that way. It is running on a single tool machine, so they generally only need locations, but sometimes they need a more complicated group of tool paths, so I cannot remove any of the functionality of the post. I am simply trying to reduce the amount of hand editing prior to the operators receiving the program. Also, the L0 at the end of the drilling line will make the program wait until the next line to start processing according to the information that I have received from the operators.

I need to know what variable is active during the rapid call of the g99 that specifies that the rapid call was from a drill cycle. I have uploaded a copy of the post that I am currently editing. In this post, I use a misc. integer to set a switch to alter the format of the code, so the code doesn't show a g99 even though the box is checked. This is the current code - on the first drill cycle, the "Use clearance only at the start and end of operation" is not checked, and on the second drill cycle, it is checked. % O0000(RAPID TEST 004) (DRILL - CLEARANCE, NO CHECK) G43H290S1069Z2.M8M3 G98G81Z-1.R.1F6.42L0 X0.Y0. Y2. X2. Y0. M0 (DRILL - CLEARANCE, CHECK) G43H290S1069Z2.M8M3 X0.Z.1 ---- I want to remove this line G98G81Z-1.R.1F6.42L0 X0.Y0. Y2. X2. Y0. Z2. M30 % I have noted the line that I want to remove. Here is the section of the post that I think needs altered, but I am not sure which variable is active to denote that this rapid call is from a drill cycle. prapidout #Output to NC of linear movement - rapid if sav_mi10=0, [ pcan1, pbld, n$, sgplane, `sgcode, sgabsinc, pccdia, pxout, pyout, pzout, strcantext, e$ #pscool, jaw ] if (sav_mi10=1 & gcode$ <> 81), ---gcode$ isn't 81 during the first rapid move during a g99 [ pcan1, pbld, n$, sgplane, `sgcode, sgabsinc, pccdia, pxout, pyout, pzout, strcantext, e$ #pscool, jaw ] if (sav_mi10=1 & gcode$ = 81), [ ] SIP 3X GANTRY MILLS_FANUC-Test 004.pst