Mark, I sent it off to QC to see if they can dulpicate it. I realize it's more of a cosmetic thing that can easily be fixed in a text editor. But I figured that if they give you the option to reset the sequence numbers in subprograms in the Control def., they also probably intended it to work. We'll see. You should send your suggestion to them as well, if you have not already. That could be a pretty big time saver. It seems it could eliminate a lot of back-n-forth positioning. Thanks again for your help...

code: % O0000 (PROGRAM NAME - TEST_TRANS_TP2 ) (DATE=DD-MM-YY - 29-03-06 TIME=HH:MM - 11:54 ) N100 G20 N102 G0 G17 G40 G49 G80 G90 ( 1 INCH COROMILL 390 TOOL - 1028 DIA. OFF. - 1028 LEN. - 1028 DIA. - 1. ) ( ROUGH MILL PROFILE ) N104 T1028 M6 N106 G0 G90 G54 X0. Y6.505 A0. S2139 M3 N108 G43 H1028 Z.25 N110 M98 P0001 ( ROUGH MILL PROFILE ) N112 G90 G55 X0. Y6.505 Z.25 A0. N114 M98 P0001 ( ROUGH MILL PROFILE ) N116 G90 G56 X0. Y6.505 Z.25 A0. N118 M98 P0001 -------blah blah blah------- O0001 N112 Z.1 N114 G1 Z-.25 F6.42 N116 X6. F42.78 N118 G2 X6.505 Y6. R.505 N120 G1 Y0. N122 G2 X6. Y-.505 R.505 N124 G1 X0. N126 G2 X-.505 Y0. R.505 N128 G1 Y6. N130 G2 X0. Y6.505 R.505 N132 G0 Z.25 N134 M99 It doesn't appear to be that Mark. Are you saying that yours sequences correctly?

Mark, I think I understand your request, please correct me if I'm wrong. You would like one sub for each tool regardless of how many "operations" that tool performs in succession. Is that correct?

Rick, If your running Anit-virus/Anti-Spyware programs on the laptop, you could try disabling them (disconnect from the network if your on one first!) and then uninstall/re-install or repair the Mastercam X demo. Good luck.

It appears that Roger's Trick made it into MR1/SP2.

Is anyone else having a problem with sequence numbers not being reset when Transform Toolpath-Translate subs are created? Mine seem to start numbering from the line after the "M98" sub call line in the main. code: % O1000 (PROGRAM NAME - TEST_TRANS_TP ) (DATE=DD-MM-YY - 28-03-06 TIME=HH:MM - 16:24 ) N100 G20 N102 G0 G17 G40 G49 G80 G90 ( 1/2 FLAT ENDMILL TOOL - 1 DIA. OFF. - 1 LEN. - 1 DIA. - .5 ) ( MILL PROFILE ) N104 T1 M6 N106 G0 G90 G54 X0. Y2.25 A0. S3056 M3 N108 G43 H1 Z1. N110 M98 P0001 ( MILL PROFILE ) N112 G90 G55 X0. Y2.25 Z1. A0. N114 M98 P0001 ( MILL PROFILE ) N116 G90 G56 X0. Y2.25 Z1. A0. N118 M98 P0001 ( MILL PROFILE ) N120 G90 G57 X0. Y2.25 Z1. A0. N122 M98 P0001 ( MILL PROFILE ) N124 G90 G58 X0. Y2.25 Z1. A0. N126 M98 P0001 ( MILL PROFILE ) N128 G90 G59 X0. Y2.25 Z1. A0. N130 M98 P0001 N132 M5 N134 G91 G28 Z0. N136 G28 X0. Y0. A0. N138 M01 --------blah blah blah-------- O0001 N112 G91 N114 Z-.9 N116 G1 Z-.35 F12.22 N118 M98 P1001 N120 G1 G91 Z-.25 F12.22 N122 M98 P1001 N124 G0 G91 Z1.5 N126 M99 % I have the "Reset sequence numbers in subprograms" ticked on the Control def. NC Output page. Subs created for depth cuts and hole positions get reset fine. Tested with "Mill Default" Machine/Control Def and MPFAN in Mastercam X MR-1 Mill 3. Can anyone verify this or show me the light? TIA

I opened both the MCX and the STL in Mastercam X MR-1. In the Top view of the Top WCS the STL is positioned towards the Right side. In the MCX your solid (and rect. stock) is positioned towards the Front. Is that normal? I've never used a STL as stock before. From what I can tell the STL file might need to be oriented from the "Left Side". I couldn't access the Highfeed parameters.

Feel better?

MPFAN.pst for X used in example. code: psof$ #Start of file for non-zero tool number pcuttype toolchng = one if ntools$ = one, [ #skip single tool outputs, stagetool must be on stagetool = m_one !next_tool$ ] "%", e$ *progno$, e$ "(PROGRAM NAME - ", sprogname$, ")", e$ "(DATE=DD-MM-YY - ", date$, " TIME=HH:MM - ", time$, ")", e$ pbld, n$, *smetric, e$ pbld, n$, *sgcode, *sgplane, "G40", "G49", "G80", *sgabsinc, e$ pbld, n$, "M08", e$ <---here pbld, n$, "M09", e$ <---and here sav_absinc = absinc$ if mi1$ <= one, #Work coordinate system [ absinc$ = one pfbld, n$, sgabsinc, *sg28ref, "Z0.", e$ pfbld, n$, *sg28ref, "X0.", "Y0.", e$ pfbld, n$, "G92", *xh$, *yh$, *zh$, e$ absinc$ = sav_absinc ] pcom_moveb c_mmlt$ #Multiple tool subprogram call ptoolcomment comment$ pcan if stagetool >= zero, pbld, n$, *t$, "M6", e$ pindex if mi1$ > one, absinc$ = zero pcan1, pbld, n$, *sgcode, *sgabsinc, pwcs, pfxout, pfyout, pfcout, *speed, *spindle, pgear, strcantext, e$ pbld, n$, "G43", *tlngno$, pfzout, scoolant, next_tool$, e$ absinc$ = sav_absinc pcom_movea toolchng = zero c_msng$ #Single tool subprogram call HTH

Lee, that looks like a pretty honest price from what I've seen. I checked newegg.com and mwave.com and your price beat both of them. What card are you currently running? I'd be interested in hearing how it works out for you. Good luck.

I have the Mill Training Tutorial X offered by In House Solutions. It is very well laid out and everything is step-by-step. Large print and plenty of pictures, too. You can find it by clicking the "Books" link at the top of this page. Call your reseller, they maybe able to get it for you if you don't care to shop online. HTH

You have to change it in the local copy of the control def. Expand your machine group in the Operation Manager and click on properties. Click on Edit and change the control def. HTH

On the NC Output page of the control def. The "Enable post debugging information" check box.

Many thanks to eMastercam.com and all the forum members!

How about this; put the # back in the pcancelcc$ post block, and changing the else , sccomp to else, *sccomp in the pccomp section. Does it output a "RL" on the last linear? [ 03-23-2006, 10:21 AM: Message edited by: dwsz71 ]

Mike, did you take the # out of the pcancelcc$ post block? If so, put it back. It was like this: code: pcancelcc$ # Cancel cutter comp. #pn, "R0" Was it not posting correctly before?

Loaded fine for me, try this: 1. Download the drivers, saving the install package to desktop. 2. Uninstall the nvidia display drivers via Add/Remove Programs, then reboot as prompted. 3. Cancel New Hardware Found wizard that comes up on login. 4. Double-click the driver package on the desktop downloaded in step 1. 5. Agree to the License Agreement, Next. 7. Next (to extract to default location). 8. Next again to begin driver install. 6. Click Continue Anyway to the lack of Windows Logo certification. 7. Reboot these steps should get you through. HTH

Did you uninstalled the previous driver first? Do you have admin rights? I'm downloading the 81.67 WHQL driver now. I'll post back with my findings. My card is a Quadro FX 500, but sounds like your having a problem with the driver package, so if there is a problem I should see it too.

Mike, Check out this link. It might help. I've never knurled on a CNC Lathe before. In fact we seldom knurl anything here. Hopefully others more helpful than I can provide more info. Good luck.

I think he meant .016"ipr as a feed along the part after plunging. But if your knurl tool was a 1/4" wide, the width (length) of your knurl, you could just plunge in at .005"ipr. Is that right Randy?

Lee, On the NC Output page in the Control Definition there is a check box to "Enable post file debug information".

quote: I felt I was the one on the "hotseat" with this topic I'm sorry you felt that way Pete. I also agreed the nVidia cards (to be more specific, Quadro FX, not NVS) would probably be more stable. But I can't agree that the Radeon x600 wouldn't work at all with Mastercam X. quote: Anyway, let's put this topic to rest. The horse is beat and has been processed into Elmer's already Now I've only been a member of this forum for about seven months, but it seems to me the thread topic "Video Card", or some other hardware query, is a once-a-week post by some one. Killing this topic seems unlikely due to the lack of published data and a standard for testing. Do you think could you persude Frank to publish some of his testing results of system configurations on the s4a website (mmm... new content )? I understand you guys want to sell custom boxes, and hording information is so popular these days because it might affect sales, but in the spirit of the Mastercam community it would be a very generous gesture. BTW, don't let Frank give you too much sh!t about the GeForce cards, he was endorsing the GeForce 7800GTX when X was released.

quote: In a word: NO! Damn... that's one final word, Pete. quote: The Graphics Processor Unit (GPU) makes all the diference in the world We need someone very clever to come up with, and publish a benchmark that would/could prove this statement. Wouldn't it be nice to know before hand the performance advantage, in Mastercam, of using a $2,600 Quadro FX 4400 vs. $25 MX4000? I think it would. A nVidia based GFX card will probably be more stable. But even the nVidia cards have their share of problems with Mastercam (like turning off the unified back/depth buffer because of ghosting). JM2C

More sticky...