Using G00 I can have separate overrides for rapid and feed. I always run the first part at 25% rapid override but leave my feed at 100%.

There is a file called "MP Documentation Portfolio" that is supposed to have a lot of information in it. You have to get it from your reseller. I believe it is about $50. I haven't seen it yet but it is what others have recommended. This thread http://www.emastercam.com/board/index.php?showtopic=70429 is quite helpful.

For anyone just starting out with post editing check out this old topic. It has a lot of good information in it. http://www.emastercam.com/board/index.php?showtopic=70429

Thanks for the info. I will have to email our reseller to see how much it costs. I checked the post and you were right about the pe and pn being postblocks. The pe postblock had e$ in it and the pn had n$ in it. Neither had anything else in it so I don't know why they didn't just use the e$ and n$.

Yes, I was opening a X6 file. Ideally everyone will load the new machine def when they open an old file but I know it won't happen all the time. I'm hoping it won't hurt anything if they don't.

Thanks Mark, I think it might work now. I ran update folder again on the folder containing my posts with use source folder as destination folder. The old post was given a .pst_vX6 extension and the new one just the .pst extension. X7 is now using the new post and control def like I wanted. Still appears to be using the old machine def but I am not too concealed about that since the only issues we have had in the past were from the control def. When posting out of X6 it is now using the updated post. Is there any chance this could cause a problem or can a post for a new version always be used on an older version? I ran file compare on the old and new post and other then a few minor changes in the formatting section they were identical. Some of our posts use an encrypted .psb file so I was unable to compare the encrypted section.

I don't dare use the migration utility. A lot of people on here have had all kinds of trouble caused by it.

It seems like I spend half of my time when editing a post trying to figure out fairly basic things. Only to forget by the next time. Is there a file somewhere that explains what the common characters in the post are? Things like e$, pbld, n$ Also different posts seem to use to use different characters for the same thing. e$ and pe for end of line pn and n$ for line number Is there any difference?

Every time we update to a new version it has been a real pain. I recently took over taking care of the machine def, control def, and posts. I have everything working ok in X6 and now we are getting ready to switch to X7. My plan this time was to create new X7 versions of each file in the same folder as the old ones and using the same name but with the new X7 file extensions. Since the post doesn't get a new file extension I put the updated version in a sub folder. All the folders are on a network drive. I used update folder in Mastercam to update the files. If I bring in an X6 file it finds the new control def automatically but the machine def and post appear to be the old X6 versions. I then tried renaming the control def so the name is different from the X6 name. Then when I open an X6 file it pops up a box that says the control file being read is from a previous version and it wants me to select a name to create a new one. I don't think it is a good idea to have it making a new one every time I open a X6 file. My thinking is it should be asking what machine def to use so I can select the new machine def and then it will be using the three new files. How is everyone else dealing with this?

You could put the block skip in front of every line of the probing routine.

I've seen it happen in previous versions a few times. If I remember right deleting the tool and then creating a new one fixed it.

Might be a setting in the control definition. In the control def double click on the rotary axis and check the settings under fixed/continuous positioning.

I've even had entities that won't delete when I try to delete everything on the level in the level manager. What worked the last time was changing the number of the level and then selecting delete in the level manager. Restarting Mastercam before trying to delete them has also worked sometimes.

Just read the readme file on the Aladdin hasp monitor and it doesn't list Windows 7. Does it work with Windows 7?

If someone has a seat of Mastercam open when I stop and restart the nethasp would it hurt anything other then forcing them to close Mastercam and restart it?

The post I use has a Misc Integer labeled "Start Solution [0=-Tilt,1=+Tilt]" I just change the 0 to a 1 if I want it to tilt the opposite way.

I am not sure where they should be set. I am still trying to get mine to output correctly. I have been getting the warning rotary limits exceeded error with every setting I've tried so far. I am beginning to think it is something in the post.

I would check the machine definition first. In the machine definition double click on the A axis in the machine configuration and check the travel limits.

I am definitely not a post expert but if your post is similar to mine I think this might work. My post has a section that starts out with the following lines #Select operation note sop00 : "NULL......." # String definition sop01 : "CONTOUR...." # " " sop02 : "CONTOUR...." # " " sop03 : "DRILL/MISC." # " " If your post has a section like this figure out which codes are for a c axis tool path and then in find the section of the post you want to add the M154 and put lines in like this [if opcode$ = 1, "M154"], pe [if opcode$ = 2, "M154"], pe

I have the operations defaults file on a mapped network drive and it was working in X6 before installing updates. After installing updates MU1, MU2, and MU3 I am now getting a referenced file warning when I open a file. In the control definition the operation defaults is set to P:\MASTERCAM\SETTINGS_AND_DEFAULTS\KITAMURA_MILL.DEFAULTS-6 but when I open the file it is looking for %PROJDIR%MASTERCAM\SETTINGS_AND_DEFAULTS\KITAMURA_MILL.DEFAULTS-6. I am not sure but it seems that %PROJDIR% is a variable pointing to the local hard drive. Has anyone with X6 MU3 been able to have the operation defaults on a network drive without this error?

I've seen it happen but not very often other then when someone shuts down the computer with the net hasp. We have had more trouble with not being able to open all of our seats without rebooting the computer with the net hasp. That used to happen about ever month but I haven't noticed it happening for a few months now.

One major drawback of the manual tool changer is the possibility of loading the wrong tool. I did it for the first time on Friday. It could have been bad but the drill I should have loaded was longer then the one I did so it didn't crash. Ours is surprisingly accurate but also drips coolant all over the place. I consider them a nice upgrade over buying a manual lathe but not a replacement for a real CNC lathe. For a prototype shop it might be a good fit but if you are going to run multiple parts you will really begin to hate the manual tool changes.

This method worked for me also. The control definition was on a mapped network drive called P: so I changed the TEMP and TMP environment variables on my Windows 7 pc from %USERPROFILE%\AppData\Local\Temp to a folder I created on the p: drive called p:\misc\ben\temp and now I can edit the control file. I did a google search to find out how to change the environment variable and for Windows 7 this site had good directions http://www.itechtalk...thread3595.html UPDATE: Since I changed the environment variables Mastercam has crashed a few times and an attempt to update some other software failed. I don't know if that is what caused it but when I finish with the control definition edits I will change it back.

I think I understand what you are doing and it sounds like it is for a 4th axis but I am running a 5 axis. I wish Fanuc would just make everything work together.

Thanks, works great once I added the s. I figured it was going to be something simple.