this is a slightly annoying issue that does happen when you have multiple machine groups. Most people that have multiple machine groups do not need them, but there are reasons, like jay said you are actually running a setup on one machine, then the next setup on another. Or, if you require a different stock setup for a second setup on the same machine. But, you should check your WCS and t/c plane when changing machine groups anyway. Anyone using multiple WCS's or multiple T/C Planes should un-check the update T and C planes when changing graphics view in the system config. HTH

if you fmt a variable it is declared. you do not need to declare it seperately, only if you want to assign an initial value to it. all formatted variables are initialized to zero. HTH

Brad, just a note on your post. Since we created the stock to leave functionality has changed from needing to be edited per pass to being a per operation stock to leave. And, on top of that we can have that value added to your radius list at the top of the file. These were major changes that occurred in X2mr2, although the documentation is missing the variable names. Once someone from CNC enlightened me on the variable names it was pretty easy adding the required functionality to the post.

the tool libary is in the general machine parameters. Chris, if you can't get it to convert send it over and I'll take a look at it.

Any resolution on the tool numbering?

you can also save mutliple solids (or surfaces) out as a stl file and use that as the stock. I would only do this if you do not have solids as your stock is now an external file. HTH

I assume you are referring to the fact that you cannot use the default bottom and back planes as t/c planes for indexing. You really have two options: 1. use a template file that has the desired planes already created and then merge your geometry into this file for machining. 2. Import the planes from a file that has the correct planes defined. HTH

manual entry typically isn't the problem, manual entry respects the "enter" key. Look at the file name, operation comments, etc...

If you want to choose your start point you have to let it machine the outer buondary then delete it via the toolpath editor - not a big deal but it is an extra step. Also, there used to be a merge island chook that gave you geometry based on a tool diameter - just what your looking for. But I don't know what happened to it. Anybody else?

Just do a 2d pocket, turn off roughing, uncheck "finish outer boundary". I know people that use this all the time. If you think contour should be enhanced to do this send it in. I use 2d/3d contour to cut vents with a ball end mill all the time that requires it works just like it currently does. And to be honest since it is easily accomplished via pocketing I don't really know that it's neccesary. The only downside of the pocketing toolpath is you can't place your start position exactly where you want it. JM2C

gms1 is almost there. select all backplot click on the toolpath in the graphics area and it will be highlighted in the backplot's operation list (the backplot dialog will need to be expanded to see this list). HTH

+1 on partial tab depth, I don't believe it affects full height tabs, or onion skinning. I set my depth to the depth of my geometry, I then use negative stock to leave to input my "breakthrough". The only reason I use negative stock to leave instead of breakthrough is because breakthrough requires that I open another dialog to check that value.

Unless break through does something I'm not aware of it works the same as setting negative Z stock to leave. My only problem with the breakthrough function is that I have to open another dialog to see what it is set to. I use negative Z stock to leave which I can see at a glance.

any setup sheet that is post based (.set files) will not give you ghosted tool output. The graphical interface setup sheet will.

changing this setting will not keep the post from renumber work offsets if workofs$ = -1 or if you use a transform toolpath operation, even if you use match existing work offsets if one is missing it creates a new one. It just keeps the warning message from coming up. I hear you, I don't like the message either, and if you set all your work offsets manually, and check any transform toolpaths you don't have anything to worry about. I just wanted to point out that there are other things to consider and not everyone should change this setting just because. regards,

I don't know that everyone should run out and change this setting. While the work offset error can get annoying it is there for a reason. If you set this to "none" you can get output that would require multiple offsets without giving you any. You can setup a simple toolpath transform using tool origin only and get code that will cut the same part over, and over, and over instead of cutting an array. And you won't get the warning message to alert you that something is awry. Now, I've always thought that when this setting was set to "transform toolpaths only" (or whatever it says) you should only get the warning on transform ops, not indexing ops. the lock on first WCS functionality works well, and you setup the post to check the values of the tplane origin and output a warning if they change. Personally I just deal with the warning message, unless a post is stricktly used for rotary work. HTH

Unless this is a cycle you will use over and over, many times it is not worth writing a custom cycle. just write out the gcode for one hole manually, then call it as a sub at all locations. This way you can have whatever custom movement you want within a minute or two. It would be beneficial to have a subprogram call as a one of the custom drill cycles so you can just pick locations. HTH

No, but in create ellipse you can choose between spline, arc, or line as the entities to create. in V9 create ellipse created a spline. in V9 create rectangle ellipse created line segments HTH

in psof you will see: comment$ move it to above the safety line output and you will be good to go. later,

I assume your G10 list is a manual entry? And that manual entry is the first op in the ops manager? if so, in the pheader$ postblock put a pound sign in front of comment$. It is setup this way to output the file descriptor before all the rest of the header info. HTH

I have seen the same thing with intellipoint 6.xxx Intellipoint 5.xxx and 4.xxx work just fine.

Heavy, the class of thread is not accounted for in the table, you must use the allowances for that. for example a 1/4-20 will list the major dia as .250" when it should really be .249" (or something like that anyway), you then choose the class of thread to get the actual major dia. Is this the differences you are referring to?

1. they have a thin web so you can cut faster without creating a lot of heat or worse breaking off that little tip on a center drill 2. the whole idea behind a spot drill is that your drill makes initial contact with the center of the drill on the workpiece. So if you are using a 118 degree drill use a 120 degree spot drill. 3. using a center drill will make the the drill contact the workpiece away from the center of rotation, since it is a 120 degree included angle it will contact at the small pilot diameter, causeing chatter which will be bad for accuracy as well as the drill. 4. Using the wrong angled spot drill is worse than using a center drill. If you use a 90 degree spot drill with a 118 degree drill, when the drill comes in it will contact the workpiece at the diameter of the drill which is as bad as it gets for chatter. 5. don't use a 90 degree spot drill just so it puts on a 45 degree chamfer, use the right sot drill for the drill being used. I assume because carbide drills are usually much more rigid, and shorter, I was always told not to spot drill when using them. I don't know if it matters? HTH

instead of output the 1005 or 1008 comment via pcomment2, save it to a custom string and then output the custom string whenever/wherever you would like. HTH

send me the file and I'll take a look at it. later,