not sure what happened to my previous post format. G97S347M03 ----- 347 RPM = 200 CSS @ X2.2 G0X2.2Z.005 G50S3600 G96S200 G1X-.0625F.01 G0Z.105 G97S3600 ---- 3600 RPM = 200 CSS @ X-.0625 (MAX RPM)

The S values on the G97 line is driven by the CSS and MAX RPM speed you set at Mastercam toolpath parameter page. In your example, I think it would be the MAX RPM that you are wanting to adjust. G97S347M03 ----- 347 RMP = 200 CSS @ X2.2<br style="color: rgb(255, 255, 255); font-family: 'Trebuchet MS', Arial; font-size: 14px; line-height: 21px; background-color: rgb(61, 61, 61); ">G0X2.2Z.005<br style="color: rgb(255, 255, 255); font-family: 'Trebuchet MS', Arial; font-size: 14px; line-height: 21px; background-color: rgb(61, 61, 61); ">G50S3600<br style="color: rgb(255, 255, 255); font-family: 'Trebuchet MS', Arial; font-size: 14px; line-height: 21px; background-color: rgb(61, 61, 61); ">G96S200<br style="color: rgb(255, 255, 255); font-family: 'Trebuchet MS', Arial; font-size: 14px; line-height: 21px; background-color: rgb(61, 61, 61); ">G1X-.0625F.01<br style="color: rgb(255, 255, 255); font-family: 'Trebuchet MS', Arial; font-size: 14px; line-height: 21px; background-color: rgb(61, 61, 61); ">G0Z.105<br style="color: rgb(255, 255, 255); font-family: 'Trebuchet MS', Arial; font-size: 14px; line-height: 21px; background-color: rgb(61, 61, 61); ">G97S3600 ---- 3600 RPM = 200 CSS @ X-.0625 (MAX RPM)

The G97 at start and end, will prevent the spindle from having to ramp up/down during the rapid moves to and from home.

new Hurcos will accepts standard Fanuc style cycles, but the "Hurco" style requires incremental drill depths as a positive value.

In regard to the display, it really only applies in regard to the default gViews, and who uses those for anything? When i am working in Mastercam, I am most always in a user defined view by way of dynamic rotation. The orientation of the model on my screen has no relation to Top or Front being the B0 view. No one would look over my shoulder and say "Your HMC files look too much like VMC files". My take on this is that the ONLY difference between a typical HMC and VMC, is the axis of rotation. I can not follow the logic in setting up a machine and post definition, and working in an environment where Y axis moves are really Z, and vise versa, and having to switch them back around in the post. Same thing for Lathe. Instead of working in an environment where X=Z, Y=X, and Y=Z, it would work better if a new GVIEW was made so that you can quickly view the part in the Z/X plane when needed. Helpful tools for rotary programming would be. 1. ability to LOCK the WCS to rotation origin. 2. Have current toolplane clearly represented on screen at its origin. 3. Gviews mapped in respect to current toolplane (quickly look down the spindle / normal to toolplane) 4. A View Manager that does not includes any of the "Default" views, and has quick tool for creating VALID toolplanes for current machine type (rotated about Y or X). 5. Backplot that represent rotary rapid moves. 6. no warning for OFFSET is used in more than one view!!! Most every program I write these days is for a rotary. Most are very simple, but deal with lots of planes and offsets. It seems to me that a few small changes would go a long way in regard to rotary / toolplane stuff. Am I overlooking some simple solutions the these issues?

Translate / Move the geometry into the top view and in position for 1st operation. Use Stock Flip for 2nd operation. I do not recommend using WCS Views for Lathe.

Bar pull on Haas Lathe. There is an unlimited number of ways to do it. Regardless of method (bar-pull, bar-feed, sub spindle), your post will need to be modified for your application. All methods are supported. Below is an example using M97 with an L value to repeat the process for the number of parts per bar. The "Bar-Pull" operation would be the 1st operation in your program. *** Add info below to your toolchange section in PST file. This would be included on all programs that included a Bar Pull operation. if opcode$ = 109, # BAR PULL [ bpull1 = abs(stck_init_z$ - stck_final_z$) l_word = (46 - bpull1) / bpull1 "M97 P999", *l_word, "(SET REPEAT FOR BAR PULL)", e$ "(BAR LENGTH - LEFT OVER / W-VALUE)", e$ "M30", e$ "N999", e$ " ", e$ ] *** Add info below to the "pstc_bar_fd" section of your PST file. This is the sequence for the actual bar pull, and will vary depending on the type of puller you are using. pstck_bar_fd$ #NCI code = 902 available variables: misc_op_z1 = stck_init_z$ + stck_clear$ misc_op_z2 = stck_init_z$ - stck_grip$ misc_op_z3 = stck_final_z$ - stck_grip$ misc_op_z4 = stck_final_z$ + stck_clear$ #~stck_init_z$, ~stck_final_z$, e$ # This is only set-up for a simple bar-pull at START of program # bpull1 = abs(misc_op_z1) + abs(misc_op_z4) bpull1 = abs(stck_init_z$ - stck_final_z$) gcode$ = 0 toolchng = 1 n$, *sgcode, pwcs, "X0", *misc_op_z1, "M5", e$ n$, *misc_op_z2, e$ n$, "M11 (CHUCK OPEN)", e$ n$, "G04 P0.5 (PAUSE)", e$ n$, "G0", *bpull1, "(PART LENGTH + PART-OFF + FACE OFF)", e$ n$, "M10 (CHUCK CLOSE)", e$ n$, "G04 P1. (PAUSE)", e$ n$, "G0", "W.5 (CLEAR)", e$ n$, "G0", "X6. (CLEAR)", e$ !gcode$ bar_pull_flag = 1 toolchng = 0

Yes. The post can be modified to capture and output the X travel extents. if x$ > prv_x$, save it if x$ < prv_x$, save it to other variable. My questions is why does reloading the mmd correct this problem??

Change your work offset to anything other than -1 If offset is left at -1, it will "Auto Increment" on rotations. Correct ?? Or you can use a post that has been modified to override this feature.

Yes. Use the "Update Folder" feature to update both the Part/Geometry files, and the Libraries.

there may be another depth call in pdrill_2 that is causing your trouble. I also show that for this control, you need to consider the reference height in your depth calculations. Below is the drilling post blocks from a post that i setup. I can send you a copy of this if you need a better example. incdrdp = abs(refht$ - depth$) # For Incremental drill depths p_jump # Cancel cycle a move to initht befor going to next hole n$, "G80", e$ n$, psg00, *initht$, e$ n$, *x$, *y$, e$ pdrill$ # Canned Drill Cycle if refht$ <> initht$, n$, *refht$,e$ n$, *sgdrill, *x$, *y$, *incdrdp, *frplunge$,e$ ppeck$ # Canned Peck Drill Cycle if refht$ <> initht$, n$, *refht$,e$ n$, *sgdrill, *x$, *y$, *incdrdp, *peck1$, *frplunge$,e$ pchpbrk$ # Canned Chip Break Cycle if refht$ <> initht$, n$, *refht$,e$ n$, *sgdrill, *x$, *y$, *incdrdp, *peck1$, *frplunge$,e$ ptap$ # Canned Tap Cycle if refht$ <> initht$, n$, *refht$,e$ n$, *sgdrill, *x$, *y$, *incdrdp, *frplunge$,e$ pbore1$ # Canned Bore #1 Cycle pdrill$ pbore2$ # Canned Bore #2 Cycle pdrill$ pmisc1$ # Canned Misc #1 Cycle (Rigid Tapping) n$, "M29",e$ if refht$ <> initht$, n$, *refht$,e$ n$, *sgdrill, *x$, *y$, *incdrdp, *frplunge$,e$ rigid = 1 pmisc2$ # Canned Misc #2 Cycle (User Option) pdrill$ pdrill_2$ # Canned Drill Cycle if refht$ <> initht$, p_jump if refht$ <> initht$, pdrill$ if refht$ = initht$, n$, x$, y$,e$

Looking for a source for Left Hand Thread repair (Helicoil Inserts / Tap) or any brand. I need a 10-32, and can not seem to find anything. Inserts or wire coils. Anyone know of a source. Thanks

Yes. The res2Vec feature includes a "Trace" mode. The picture is not stored in the file, but is super imposed on the screen while you work. In Mastercam, select Settings->Run User app-> and select Ras2Vec.dll

For the Router product, you must use the RMD machine files. Do not rename or change to a .MD extension. But, you can use the mill post processor files. You will need to use the "Machine Definition Manager", and add the PST file to your control definition.

below is an example of a modified post block for bar pull. The inhouse posts are also a good source of information. This example uses and incremental Z value for the pull length. This makes it very easy to read/modify the program if needed. pstck_bar_fd$ #NCI code = 902 available variables: misc_op_z1 = stck_init_z$ + stck_clear$ misc_op_z2 = stck_init_z$ - stck_grip$ misc_op_z3 = stck_final_z$ - stck_grip$ misc_op_z4 = stck_final_z$ + stck_clear$ # This is only set-up for a simple bar-pull at START of program bpull1 = abs(stck_init_z$ - stck_final_z$) gcode$ = 0 toolchng = 1 n$, *sgcode, pwcs, "X0", *misc_op_z1, "M5", e$ n$, *misc_op_z2, e$ n$, "M11 (CHUCK OPEN)", e$ n$, "G04 P0.5 (PAUSE)", e$ n$, "G0", *bpull1, "(PART LENGTH + PART-OFF + FACE OFF)", e$ n$, "M10 (CHUCK CLOSE)", e$ n$, "G04 P1. (PAUSE)", e$ n$, "G0", "W.5 (CLEAR)", e$ n$, "G0", "X6. (CLEAR)", e$ !gcode$ bar_pull_flag = 1 toolchng = 0

Expand your "BackPlot" menu, and you will find the cycle times. There is a small arrow in the corner that you need to select.

Its hard to go wrong with the "Save As" method. Its just that simple.

"sgcode" is the variable that you need to force output. Add the asterisk modifier as shown below. pcan1, pbld, pn, `sgfeed, *sgplane, sgcode, sgabsinc, pccdia,<br style="color: rgb(255, 255, 255); font-family: 'Trebuchet MS', Arial; font-size: 14px; line-height: 21px; background-color: rgb(61, 61, 61); ">pxout, pyout, pzout, paout, pcout, parc, feed, strcantext, scoolant, pcccomment, pe<br style="color: rgb(255, 255, 255); font-family: 'Trebuchet MS', Arial; font-size: 14px; line-height: 21px; background-color: rgb(61, 61, 61); ">

if the following line exists in your post, check its fetts to be as shown. frc_cinit : 1 #Force C axis reset at toolchange

it is in Text_&_post_files_&_misc To get on the FTP, ftp://mastercam:swis...rcam-cadcam.com

add the following: if mi3$ = 1, n$, "M919", e$ else, n$, "M919 S2", e$

Yes. If tool number is constant, you could key off that and setup post to skip the output anytime that tool number is used.

George, The Cimco Editor is included with Mastercam installation. To setup for use, see Editor selection on "Start / Exit " page of Mastercam configuration settings. Cimco is very good choice for your application.

Mill_Haas_VF.PST is on the FTP, and does include the M97 style for subs.

change the "e" to "f" as shown below. #Format feedrate for lathe thread (E) result = nwadrs(stre, feed) #Format feedrate for lathe thread (F) result = nwadrs(strf, feed)