Or just uncomment the line in the "prpm" & "prpmnull" post-blocks. result = nwadrs(strp, speed) #Different letter than 'S' for mill spindle?

Rick, The MplMaster post uses variable called speed for the lathe & mill type operations. I added a new variable called speed_m and associated it to output P value in the format. You will need to initialize the variable speed_m, I set that up in the section called spindle variables. In "prpm" I told the post what speed_m would be equal to, in this cause it's "speed_m = speedrpm" In all the mill instances I have set "speed" to be "speed_m". Example from "prpm" else, #Milling mode spindle [ #result = nwadrs(strp, speed) #Different letter than 'S' for mill spindle? if (opcode$ = 3 | opcode$ = 16 | opcode$ = 105) & nextdc$ = 3 & rigid_tap = 1, pbld, n$, *sg97, e$ else, pbld, n$, *spindle_m, *speed_m, e$ #else, pbld, n$, *sg97, *speed, *spindle_m, e$ result = nwadrs(strp, speed_m) #Reset to 'S' for next single speeed output ] I did the same thing for "prpmnull" For "mtap$" I added "speed_m = speedrpm" then changed the instances of "speed" to "speed_m". Hope this is what you're looking for

JW, Don't know what to tell ya because it stays inside the containment in the surf rest rough toolpath I wrote and I can adjust how far I want the tool to stay away from the containment. There are quite a number of variables here, you said that you are using a STL file as well as surfaces to drive the toolpath. It may be setting up a conflict that is overriding the containment. Running - McamX4 MU3 & McamX5 Beta

sorry for the really bad grammar, sometimes my fingers move faster than what I'm thinkin'

Randy, I believe this has more to due with getting the op defaults & the control def on the same page. - first I opened the operation defaults in the machine group properties - with the toolpath operation defaults page open I used the select all operation utility - then right click in the field to open edit selected operations / edit common parameters - I selected to edit the misc values - make certain that he box for automatically set to post values is unchecked - after green checking out of that field use the apply button in the lower right of edit common param set set the change - now edit the control definition, I typical open the control def through the machine def so it will be reloaded into the existing part file - in control topics open misc values - set the initialize toolpath operation to default operation, I also have set misc values on first op checked This what I did to get the misc values defaulted to active

Gibbs, Yes, I typically program everything with Mcam's WCS set to top. I work my way around the part with user defined tool & construction planes. This way I create my stock in the Mcam top view and I never have to move it in verify, it doesn't matter what custom toolplane I have associated to the toolpath. Qst -"Well what about if you want to use the top/front/iso Gview, you can't do that if you don't have custom WCS associated to every face" Ans - That's what dynamic rotation is for, or a Space Pilot and if I tell Mcam to set the Gview = to the toolplane, I'm looking at the part relative to the Z+ direction. The thing is that custom WCS will work but there are a whole bunch of other variables that I have to maintain associations for.

JW, Second tab of the surface restmill parameters, middle right of the page, tool containment, set it to compensate to the inside

Chall, Could be the reason your not finding the fix in your V9 post is because all the "fancy stuff" happens in the .psb file or if it's a Cimco post it would be the cp6 files. Just like Keith was saying, if this is a custom post contacting your reseller is the best place to start. The post developer may be able to update, or they might recommend starting with a new post because of the updates to the McamX4 software.

Scott, Did you try editing the control definition you're using for the Haas in Mcam? Open the control def and go to files in the control topics, delete the default nc file extension and leave the window blank. Save the control def. You will need to reload the machine def in the operations manager for the changes to take effect in the current part file. When you post the code it will be posted without a file extension.

Fretless, You only need one transform op. - Setup the transform to translate, - check the box for "tool plane origin only", - set the method as tool plane, - try grouping the output by operation order, - set it to copy the source operations, - set the work offset numbering to assign new (if you want to use aux work offfsets start with 6) - go to the translate tab - set the translate to "between points" - set the steps to how many work offsets you require - leave the point to point set to zero because you're not changing the origin I like gun control too, I choose to use both hands and hit what I'm aiming at with the first shot

Steve, If you are running the MpMaster post there is a variable that can be activated called output_z, this will output a comment that will give you the Z min-max depth for the overall program and the min-max for the individual toolpaths based at the tool change

quote: I use "magic dust" before posting a program. quote: I always smoke a doob before programing anything important.I refer back to this comment- quote: brain fart when you need to "undo" 15 or 20 minutes worth of bad ideaHowever any time I had tried the "reefer method" it lead to 2 - 3 days of bad ideas, usually starting with trying the "reefer method"

I always setup a file new before making any changes to setting config. I usually try to group my tools by type then by size largest to smallest

step files will work sometimes coming out of Pro-E it depends on the complexity of the part file and how the geom was generated (did the designer/engineer take short cuts?) The best results typically come from the native file type. If you're getting step files from a vendor that are seriously "jacked up" we have used a seat of SWorks to open the step then let SWorks run the diagnostic utility and fix the issues. The usually sldprt opens in Mcam with no missing faces.

Double clicking to open a Mcam file typically leads to trouble. (multiple instances, incorrect file association,...) Don't be lazy, use file open. If the file is located in a folder you visit on a regular basis right click in the field on the left of the file open utility and add the current folder as a short-cut

I typically separate my geom in the levels manager by 2s and toolpath geom by 10s All my shirts hang the same direction in the closet

Tom, Not certain where the NCI path is being stored, that would be a question for folks writing the source code. (they may or may not be willing to share that info) I have seen it before though that I would have multiple toolpaths that shared the exact same nc file name that would post separately. The only way to get it to correct was to - select all, right click in the ops manager, edit selected ops, change nc file name - to reset the nc file path.

quote: would it be a problem if we lost the option for each operation to have a different file name? What if all operations in the toolpath group ALWAYS posted to a single file? I use the nc file name to purposely output files with different file names. If I'm running multiple vices and or manually rotating/moving the part from one fixture to another. I program the part on all sides using different user defined planes -w- work offsets then post the code. Sometimes it's easier to prove the code working with one offset at a time.

Greg, What graphics card are you running? Do you have the latest driver for that card loaded? I have been using the drivers tested and recommended by the SWorks tech support and that has worked out fairly well. http://www.solidworks.com/sw/support/videocardtesting.html How "Big" is the file? I have a solid open with shading set to trans and can pan/zoom & dynamically rotate with no issues. Dell Precision M6400 NVidia Quadro FX2700M

quote: Machsim was available for X4. where? It's a free add-in that you would get from your reseller

Personally I don't change the WCS when doing rotary or multiaxis programing. I leave it set to Mcam TOP. I use custom user defined planes for all my rotational output. Mike you can find dynamic planes in the drop down list below the lower middle of the Mcam graphics area. The dynamic planes utility is right under named views. If you're looking for some quick reading on the use of dynamic planes go to the documentation folder in the McamX4 main directory. Launch the whats new pdf and go to the general system enhancements page. GSE starts with dynamic planes.

Mike, Try using the dynamic planes utility, If you have used the dynamic xform it works the same way in that you orient the X,Y,Z axis' relative to your part. The main thing to be concerned with is the orientation of the axis you're rotating around. example; If you are rotating around the X axis and X positive is pointing to the right, Y & Z have to rotate around X. If I were to change the X positive direction to the left this would be a 5axis move and will result in an axis error when trying to post with a 4axis post

Set the axis type to signed direction, that will make for some serious weirdness in the code, not certain if this will cause smoke to roll out of every orifice of the control panel. I'm fairly certain the Haas VF control wouldn't see the humor. N120 T2 M06 ( TOOL - 2 1/2 FLAT ENDMILL / TOOL DIA. - .5 ) N130 G0 G90 G54 X6.775 Y0. A0. S2650 M3 N140 G43 H2 Z.125 N150 M08 N160 G1 Z-.5 F50. N170 X6.5 F25. N180 A-358.6364 N190 A--357.2727 N200 A---355.9091 N210 A----354.5455 N220 A-----353.1818 N230 A------351.8182 N240 A-------350.4545 N250 A--------349.0909 N260 A---------347.7273

Yeh, I tried that earlier, it sounded like a solution but had no effect. I have a feeling this has more to do with how the NCI is breaking down information and sharing it with the post

+1 on the suggestion for Verification software. There is quite bit that can be done in Mcam with a combination of backplot, verify and dead reckoning visualization, it still can't beat something like Vericut, Camplete,... The next best thing would be the "poor man's" verification, get your self some "cheap material" and run that to prove out the program before doing the money shot.