I have not had any crashing issues so far, but I do have problems when unchecking the *inch values* box when editing a tool. If I go back to that tool, the box is checked again.

I think I finally got it to work the way I wanted. Thanks for the help guys.

Colin, That got me a little closer, but still no good. Few more things to mention: 1. header is already a variable in my post 2. I have no problems with manual entry in my header(I like it where it is) Before any changes were made to post, I could do either this: () (TOOL COMMENT) () (MANUAL ENTRY) [b]<---NOT correct spot[/b] N730 (OPERATION COMMENT) [b]<---- CORRECT spot[/b] N740 T3 M06 N750 G00 G17 G90 G54 X19.798 Y118.357 S0 M05 or this: (MANUAL ENTRY) [b]<-----CORRECT spot[/b] N730 (OPERATION COMMENT) [b]<----NOT correct spot[/b] () (TOOL COMMENT) () N740 T3 M06 N750 G00 G17 G90 G54 X19.798 Y118.357 S0 M05 After trying your suggestions, the operation comment was in the correct spot, but it was the same operation comment from my first operation for all the operations, and by #ing out comment$, my manual entry will not post out.

I read that thread earlier today when I was searching for my help with this issue. It wasn't exactly what I was hoping to see. I don't have any issues with how manual entry posts in the header. My issue is before/after tool changes. Creating my own string variable has not helped so far either.

Thanks for the reply. Unfortunately, that does not help with my issue. I am looking for a way to separate manual entry code/comments from operation comments. Currently, comment$ is what controls the location of both. Once I have found a way to separate them, I can properly have them output where I want in the code.

Still not able to get this to work. What is: *sav_n3 ?

Any ideas out there?

Trying to separate these. I feel like something is missing here or I am not understanding the portion I quoted here. My post has the same code as listed above but is not posting out correctly.

And yes, as long as the plane is not being used for anything, it can be deleted.

Right click on the name, and the option to rename should appear. You cannot rename the default planes though.

It's per wall. The little picture shows how far away the cutter is from each wall.

Pictures? I don't see it.

Really? When is this going to be possible with operations?

It can be done by using the xform function, but it is not easy unless you know the exact coordinate differences between the two operations.

It won't change there either. It's like it won't stick once I choose what to associate it to. It does let me pick any other .exe file except for cimcoedit.exe

Happened again after upgrading to windows 7 and X7. Still can't figure out why it happens or what to do to fix it.

I've been hoping for a drag and drop (from one file to another) feature for a long time.

Pretty much that. A whole bunch of versions ago I created "big" libraries for different types of material. When I created them, I used the mfg's data and put that into cimco speed and feed to get the base starting numbers and then just modify based upon other circumstances.

Thanks Allan, that worked.

Currently, I have my NC files set to post out to folder based upon which machine the code is needed for. I want to know if there is a way to make the code save to the file/folder that the .mcx file is in...which would be a different file/folder for every different .mcx file. When I look at the mapping options, I do not see that option. Is it named something else or can it even be done?

I concur.

The last 10 or so commands are in icon form on the right side of the screen. At least that is the default.

This works if the next operation is using the same work offset as the previous operation, but not if the tool is moving to a different work offset. I thought this was something that I fixed in the past, but as each new release of mastercam comes out, it is something that reverted back. I can't find the older thread where this was discussed. Does anyone know how to make it break the lines while moving from one work offset to a different one?

Thank you.

Anyone know why the mill.set file does not have information for work offsets? Has anyone added it to theirs? I'm trying to get the setup sheet to post out what work offset is being used for each operation, and I'd also like to make sure it posts out any A, B, or C rotation as well. Any help is appreciated...Thanks.