When I output the code using a 12.5dia closed arc the move is broke down to every 1.4173deg. I used the trim break utility; break circles and broke the closed arc into quadrants. The code is still output in 1.4063deg increments, however the code I'm getting is broke down in 11.25deg sections.

I hate to say this but I haven't been able to find a cure for that one. Something I do know, it takes 43 muscles to frown, 17 to smile but only 3 for proper trigger squeeze.

++1 "organized = simplicity" simplicity = efficiency efficiency = speed economy of motion, go slower to go faster, back off from cover to play the angles and reduce your target signature,.....oops wrong game Mike check out the dynamic planes utility in McamX4.

Joel, You will need to go into your machine definition in the machine group properties and make a setting for the A axis properties Open files in the machine group properties, select edit. In the machine definition manger select VMC A axis and right click to open the properties. In the upper left of the A axis component manager you will see "World Coordinate System", change the axis of rotation for the A axis to "Z", green check your way out to accept the changes and repost. By making the changes through the machine group properties it will only affect the part file not the default machine definition

Alan, When you disable hardware Acceleration in McamX it is only disabled for the program. There will be some noticeable difference in the graphics regen primarily when dynamically rotating the part, sometimes Verify will visually look different. I hate to say this but Mcam and ATI cards don't "play well" together (donning Nomex Underwear now...) Do a search on the Forum for ATI graphics cards you see how other users have worked through

Beardog, I should have read that before I hit "send it", if the coolant is turned on in the toolpath it will result in double coolant codes if you're using the X-Style coolant. I you do not have the coolant turned on in the toolpath there will be no M09 output to turn the coolant off "M09" would need to be hard coded as well in the pretract post block There is a scoolant command in the line associated with the G91 G28 Z0. line

Beardog, Go to a postblock in MpMaster called ptlchg_com look for this line of code - pbld, n$, "G43", *tlngno$, pfzout, scoolant, next_tool$, e$ change scoolant to "M08" remember to use the open quotes then close quotes this will hard code the information The one issue is though if you have the coolant turned on in the toolpath you will get double coolant output and you won't get an M09 output to turn the coolant off, you will need toi hard code that as well Possibly a better solution would be to select all the toolpaths in the operations manager and do an edit selected operations / edit common parameters then do a mass edit turning on the coolant

This what I get from a stock Dell Precision M6400 Time to process - 2min 3.8sec laptop/desktop - it's a laptop CPU & speed - Intel Core 2 Duo P8700 2.54 GHz Operation System - Win 7 32bit OS RAM & RAM speed - 4.00GB

Steve, Sounds like you had a hard crash with the file open, the only way to save your bacon with that spituation is to have back-up files active, I have my Mcam back-up files mapped to a personal folder in the C: directory. You can use the key map utility to setup a key stroke assignment for the save function I have mine set to ctrl S

go to the help drop down the toolbars, under the help drop down you will find the Zip to Go utility, click on the utility to launch it, make certain that the check boxes for mill, post processors and toolpath are checked then click on the button in the lower left to create the zip to go file, a zip file will be created in the documents area of your computer with the file name and the file extention .z2g, all the selected files associated with your part file will be in the zip file

typically if you're getting linear code instead of circular interpolation it has more to do with geometry, however you mentioned earlier that you had created an arc and used that for the toolpath geometry if all the settings in the control def are correct, there could be a setting in the post that is forcing linear output a zip to go file is the only way find out what is going on, have you contacted tech support through your reseller?

Marshal, If you need to break the arcs at the control in MDI before you run the code, I would suggest that you set the arc breaks in the control def file to break at 180. Use the drop down to the right of arc break options. Also a good way to make default changes to the control def is to open it through the machine def in the settings drop down. This way as you green check your way out to accept the changes you will be prompted to replace the machine def in the existing part file. If you go directly into the control def you will need to do a machine def replace in the machine group properties to affect the changes in the existing part file.

Marshal, If you are using a contour toolpath try enabling the Arc Filter / Tolerance. Set the filter ratio to 1:1 to start, activate create arcs in XY then set the min and max arc radius

One thing to consider about the display arc center points is that they are not geometry, it only referances the center of an arc. If you have quite a number of arcs defined in the wire geometry it looks like fly scat on the screen. If you need actual points, I have used the "create|point|small arcs" utility. This will allow you to set the max dia of arc you would like Mcam to work with and you can set it to create points for only closed ars or include partial arcs if needed.

Neurosis, Check the tool setting in your control definition. What are your settings in the tool offset registers? If you have it set to "add to tool" the control def will add the in put value for length and dia. If you have this set to "from tool" the values will be pulled from the tool parameterrs in the library.

From GCode "Cool.. " From Ron Branch "One thing I can talk about is a new dynamic bounding box. It will see your part in Aircraft space and give you a bounding box relative to the part not relative to the c-plane. It will also create WCS that is then usable instantly without you having to assign it. One other thing is that it will also tell you the size and weight of the material needed to make the part. It also has stock adjustment on the fly. Details will be coming soon." From Me Industrial Strength Cool

gen I thought I could just leave work offsets alone (left on -1)and mass edit them afterwards. But when I post the program I end up with different work offsets for the different angular positions(cplanes).WCS is left at top. This is not what I want. I want the same work offset throughout the program no matter the cplane. If you're using the mpmaster post, go into the misc values page of the toolpath parameters and set misc integer #9 to one. This will cause the poist to lock on to the first work offset and ignore the the rest of the offset values of the other T/C Planes CJep