Sorry for the delay. Yes email mail to: wire [at] mastercam [dot] com. Roger was able to provide one for me.

I may be totally off base here, but are your tool planes and construction planes correct? Should they be TOP=>FRONT=>FRONT ? I also noticed that your rapid distance is set to .8. and your entry feed distance is set to 1.0. I changed the planes to TOP=>FRONT=>FRONT and changed the rapid distance to 2. and air move distance to 2. and everything looks good. As far as the over-engagement of the tool, check the ramp length. I changed it to 25% and it looks good.

That is good to know. I wish I had checked the forum this morning. This bug just bit me.

I was wondering if I would need to cancel each time. I was hoping to avoid that but I will give it a shot. Thank you.

It is staying in the G81 cycle. As far as the unlocking of the B axis, I haven't found any codes in the manual for unlocking the axis.

I have been plagued with an issue on this machine for some time now. The manual is not very helpful in this case. During a drill cycle and rotating B axis to another location (while still in the cycle) the feed between holes remains at the drilling speed. Is there a way to change this? Am I missing something?

Try this video. It shows the various ways a peel mill toolpath can be chained.

Ron, A different approach would be to use a Seco high feed mill. We use them on our low rigidity machines and/or when somewhat of a long over hang is necessary. I'm not sure which method would give you a higher mmr tho.

I had a similar issue. Any time i selected anything from the menu bar the screen would flash and the dialogue box would never show up. It ended up being the driver for the graphics card. Once I rolled back the driver, everything started working just fine.

We use several of these. It is a most excellent tool.

I highly recommend Helical Carbide endmills. I just finished up a Titanium 6al-4v job where the machine was running 56ipm with a .125 bull endmill, .150 adoc and .007 stepover. I really feel it could have been ran faster.

select "change program #" under the edit selected operations menu.

+1

check the "Retract" box

I checked that. this is on a 2 axis wire burn. everything looked fine. It posted just fine friday. i only posted it again to see if it was just the file i started this morning.

I recently (today) started receiving errors while posting. I posed several programs last week and everything worked fine. I tried posting this morning and I received errors during posting. I have been on X7 since its release (SP2 now and have been running it since it was released). I have not modified my posts. To my knowledge, there has not been any change to my system or posts of mach defs. I even posted the files from last week that posted fine, and now i receive errors on them. I have verified the posted code and so far there hasn't been an issue with the code, but i would rather get this fixed. any ideas how to fix this? 25 Nov 2013 10:11:51 AM - <0> - Report created. 25 Nov 2013 10:11:51 AM - <2> - Initialize posting log file 25 Nov 2013 10:11:51 AM - <2> - Using MP run version 16.00 and post components version 16.00 25 Nov 2013 10:11:51 AM - <2> - Initiate opening the post processor file(s). 25 Nov 2013 10:11:51 AM - <2> - C:\USERS\PUBLIC\DOCUMENTS\SHARED MCAMX7\WIRE\POSTS\MITSUBISHI 90 HA.PST 25 Nov 2013 10:11:51 AM - <2> - The post processor file has been successfully opened. 25 Nov 2013 10:11:51 AM - <2> - Post version information (input): 25 Nov 2013 10:11:51 AM - <2> - UPDATEPOST Version 16. was used to modify this file. 25 Nov 2013 10:11:51 AM - <2> - The file was modified by this product on 11 May 2013 07:22:12 25 Nov 2013 10:11:51 AM - <2> - The post was written to run with Mastercam Version 16. 25 Nov 2013 10:11:51 AM - <2> - The post product type is Wire. 25 Nov 2013 10:11:51 AM - <2> - Initialization of pre-defined post variables, strings, postblocks was successful. 25 Nov 2013 10:11:51 AM - <2> - Search for defined post variables, strings, postblocks was successful. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'max_atol$' was re-initialized from 179. to 179.5 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'trunc_mtol$' was re-initialized from 0. to 1. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'maxnccomment$' was re-initialized from 9999. to 99999. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'maxnccomment$' was re-initialized from 256. to 120. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'dec_seq_left$' was re-initialized from 3. to 4. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'sub_seq_typ$' was re-initialized from 0. to 1. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'tplanemode$' was re-initialized from 2. to 1. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'nobrk$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'nobrkxz$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'nobrkyz$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'lnobrk$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'lnobrkxz$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'lnobrkyz$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'arcoutput$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'arcoutputxz$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'arcoutputyz$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'larcoutput$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'larctypexz$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'larcoutputyz$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'breakarcs$' was re-initialized from 0. to 1. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'breakarcsxz$' was re-initialized from 0. to 1. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'breakarcsyz$' was re-initialized from 0. to 1. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'lbreakarcs$' was re-initialized from 0. to 1. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'lbreakarcsxz$' was re-initialized from 0. to 1. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'lbreakarcsyz$' was re-initialized from 0. to 1. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'helix_arc$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'lhelix_arc$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'do_full_arc$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'do_full_arcxz$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'do_full_arcyz$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'ldo_full_arc$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'ldo_full_arcxz$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'ldo_full_arcyz$' was re-initialized from 1. to 0. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'rotfeed4$' was re-initialized from 2. to 1. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'rotfeed5$' was re-initialized from 3. to 1. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'lrotfeed4$' was re-initialized from 2. to 1. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'lrotfeed5$' was re-initialized from 0. to 1. 25 Nov 2013 10:11:51 AM - <2> - CONTROL DEFINITION - Post variable 'sub_level$' was re-initialized from 0. to 0. 25 Nov 2013 10:11:51 AM - <2> - RUN TIME - Only single-axis rotation is allowed! Angles may be incorrect. 25 Nov 2013 10:11:51 AM - <2> - Successful completion of posting process!

Well, let me first state that the salesman has told us that the machine we have is the first one off the line, and most issues have been dealt with. I am not sure how accurate that statement is. We all know salesmen have been known to embellish a little. The first thing we noticed about this machine was that the rotational travel limits of the machine were less than what was on the brochure and on the quote. Most places might not have been as concerned about that, but it is important to us. Then there was some trouble getting the machine set up. The radiator in the back for the spindle oil, blew out as soon as the machine was turned on. The tech had a lot of trouble getting the machine level. This was initially blamed on our concrete. After pouring a pad under the machine the problem still existed, not sure what he ended up doing to get it level. Mazak is on the floor today regrinding shims on the z axis because it wasn't moving perpendicular to the table. One of the brushes that protects the way covers, broke off. The machine has leaked coolant all over the floor since the tank was filled up. Mazak came in an re-caulked the interior......still hasn't fixed the problem. There are a few other minor issues that the techs are working on right now. Having said all that, Mazak has been here doing what they can to make it right.

We have had one on our shop floor since May. We haven't used it much. In fact mazak has been in numerous times to work on it.

It doesn't work in verify.

I have the same issues in X6 MU3 and X7 SP2. I had the OEM mouse originally and it happened. I currently use a Razer mouse with current drivers and it still happens.

I deal with this everyday. Even after proving that the dynamic toolpaths are better, I still fight the "we've been doing it this way for 30 years" mindset.

My right click menu in the operations manager has about a 5 to 15 second delay. All other right click menus in Mcam x5 x6 x7 (or any other software I use) open instantaneously.

yes! extremely slow. I actually posted a similar question a few months back. It becomes very time consuming when renaming nc files.

I am currently running 6AL-4V parts. i have an .125 dia em with .02 corner rad (Helical endmills ) running 56 ipm .100 depth of cut. I am getting several hours of run time per endmill.

Hit ESC once on X7