Mike-T, do you mean >create curve slice< on the create menu. By the way thanks for the analize/database/geometry/toolpats tip I don't know for how long I was trying to figure an easy way to debugg programs from other guys.

Thanks. Alt+A now working.

I just got installed X2MR2 SP1 and I notice that alt+A that I've been using since I think V8 is now gone. I save as I go working about every 3 to 5 minutes and now instead of using the short cut I have to use the mouse which I don't like. Is it only me or more of you guys have the same problem. Is it possible to get this fix?

Thanks jeff that work just fine.

For contour toolpaths, is there a way to have spring passes, just like in the finishing parameters of the pocket toolpath? I know I could use multipasses, but the problem with that is when the tool lead out and then lead back in for every multipass. It could just keep going and then lead out at the end of the spring pass or passes. Also my partners used Gibbs before I got here and they keep saying that Gibbs was able to do that.

Hit send to fast, I meant first time using this post processor. I download this post from this site.

For first I posted a job that includes indexing. My problem is that the degrees are the inverse of what I need i.e. if I need 1.0 the output is 359.0, if I need 89.0 the output is 91.0. Is there a way to correct this in the post or in the machine definition?

thanks, now I just need to persuade our IT guy to install it. May be he will get it installed by march.

Spade have you updated your seat to Mastercam X2 MR2 Service Pack 1, and if so, did this fixed the problem with the operation manager???

I tought I had problems

Where those questions should be located in my post. Do I need to put them right before pheader? then call them in the pheader section?

Thanks guys, so I'll try to avoid the esc key (which is like glued to my fingers).

When I create solids on MC and I swith between toolpats tab to solids tab on the operation manager, eventually I lost the ability to see the toolpaths tree and the solids tree. The only way to recover from this and/or to be able to see my toolpaths and solids is to close and reopen mastercam. Nothing gets lost is just very inconvenient, because I have to do it several times during the day. It also happens after using ctr+O several times, as solid tree gets bigger. I mean the more solids I create or modify the bigger the chance for this to happen. Is there a way to solve this issue?

Reloading machine def worked. Thank you John. You must have invented all these bugs because you know them all. Also I start a new program; same procedure and no problems so far.

some times I can copy the toolpaths but when I click on planes to update to a new WCS then mcam crashes. Then I try to copy one by one toolpath and it work with the fist one then succesfully copy the second one but when I update to a new WCS mcam crashed again. Now I don't know if it is a problem with the copy after function or with WCS manager.

just happened again

First, I create a new WCS. Then I copy all toolpath from a previous group to a new group for the new operation and right after I click on the copy after function mastercam crashes every time. Anybody else having this problem. I'd hate to think that I'm the only lucky one . Maybe another bug to fix for CNC software people.

yes I'm using X style coolant and I don't set my coolant to "with" because I don't like the output, It looks like this: code: G00 G17 G20 G40 G80 G90 N1 T1 M06 (#13 C-DRILL ) (MAX - Z1.) (MIN - Z-.01) M08 G00 G90 G54 X-6.895 Y-3.383 S8000 M03 G43 H1 Z1. T6 Z.171 G94 G99 G81 Z-.01 R.171 F16. X-3.135 on the other hand if I use "after" then it looks like this: code: G00 G17 G20 G40 G80 G90 N1 T1 M06 (#13 C-DRILL ) (MAX - Z1.) (MIN - Z-.01) G00 G90 G54 X-6.895 Y-3.383 S8000 M03 G43 H1 Z1. T6 M08 Z.171 G94 G99 G81 Z-.01 R.171 F16. X-3.135 For what I have read, I can choose to use V9 coolant style. Is this right? and if I choose so, what are the disadvantages compared to version X coolant style?

i don't understand, i already have that code in my post code: phsm1_on #must remain before G43 pbld, n$, "G43", *tlngno$, pfzout, scoolant, next_tool$, e$ phsm2_on #must remain after G43

thank you

Thanks for the help John, it is now working and actually I did not change that mentioned counter from 25 to 24. Anyways this is what I'm getting: code: N1 T1 M06 ( 1/8 SPOTDRILL) (MAX - Z2.) (MIN - Z-.1625) G00 G90 G54 X1.1274 Y-1.246 S2139 M03 G43 H1 Z2. T2 M08 Z-.03 G94 G99 G81 Z-.1625 R-.03 F1.03 X1.35 Y-.8605 X1.5726 Y-1.246 G80 Z2. M09 M05 G91 G28 Z0. M01 How can I get the M08 to output in the G43 line right after the prestaged tool T2?

quote: posted 09-27-2007 07:39 -------------------------------------------------------------------------------- It appears as though the "First coolant off shuts off all coolant options" command has also changed and will also require editing within the post. Similar to the changes above, the line: 17101 all_cool_off #First coolant off command shuts off ALL coolant options will also need to be removed and the parameter table definition needs to have the entity count lowered by 1 (25 to 24). If you use this feature, you will need to set the all_cool_off variable to 1 where it is defined near the top of the post: all_cool_off : 1 #First coolant off command shuts off ALL coolant options Chris I have done everything Chris said but lowering the entity count by 1 (from 25 to 24) I've been looking for the parameter table definition and/or a counter set to 25 but I can't find either one. Please advise

Since we update our mcam to MR2 our mazak post wont post coolant code for any reason. No matter what I do M08 will not come out. This happens only with the mazak post processor which used to work fine untill last week. Does anybody have an idea of what could have happen and how can I fix it. I did a search already and didn't find anything.

I do that all the time use use stub drill and alcohol mixed with air to keep the aluminum from sticking to the tool

it worked thanks