So I have done a search and tried everything that I can find anyone has offered as to how to get an M98 to post out. My CD is set to retract to initial height, but my post is stuck in "M99 Land". I am editing a X2 MR2 MpMaster post. A little help?

Ok, so here is a quote from the Manual for the control... "Turn on cutter compensation just before plunging into an individual contour and turn it off immediately after retracting out. Cutter compensation must be turned off before indexing between contours even if the same compensation is required." Using the "plunge after first move" and "retract after last move" check boxes will give me what I need. I was trying to hard code it in, because that is what the old post did (or so I was brought to believe). Upon further review the old post is not even doing what the control requires in the Quote above! Clip from old post... G0 X1.2625 Y-1.56375 G1 X1.2625 Y-1.56375 Z-.375 G41 G1 Y-1.56875 F28.8 G3 X1.3 Y-1.6063 I.0375 J0. If the old post wasn't correct then the users of the new post shouldn't complain, right? What I will do is create a "router" operation defaults file and distribute it with the new posts so that everyone will already have those 2 boxes "checked" by default. Sorry if I wasted anyone's time.

There is an option in the Mach Def to... "Start and end cutter compensation above part (read by post only)" Regardless of how it is set, post output is the same. Is there a way to "hard code" this in to my post so that it will Always initialize and cancel comp above the part? I am editing the most rececnt MPMaster (X2-MR2) I have been looking in the plinout and pcirout sections but am not sure what to do in order to get the G40/41/42 to post before the Z output.

Chris, Thanks... funny, that is exactly what I found that worked... I came back to post that I had figerred her out, and here you are telling me how it to do what I had just done!!! LOL How does that saying go... A day late...? Thanks none the less! Robert Winters "Fix what's Broken, Don't broke what's Fixed!"

Ok, I am a patient man. Thanks for the reply.

:bump:

I am editing the MPMaster for yet another one of our machines... Is there a simple way (say, a switch maybe) to stop the post from outputting "sgfeed"? This post is for a machine that does not have rotary axis, so doesnt need to use anything other than G94's yet is outputting them at every single tool. I know that they wont hurt, but it would save a lot of questions from the users of this post. I commented them out of the tool change commom blocks and the end of the drill cycles, but then stopped to see if any of the Gurus have an idea for an easier edit...? Robert

Ocean Lacky! I love you, man! After seeing your post, I searched for all posts by Brett Thomas and found this... Linky I applied the changes mentioned and I am back in Business! It also explains why it worked on other PC's and not mine as it seems to be a MR2 issue and the other users were using MR1. My only question is how I was able to get coolant a few weeks ago, when I have been using MR2 for over a year, but I guess I will let that slide now that all is working again!

Ok, so I need to retract the statement that it doesn't work for Mastercam Default MD's CD's and posts. It does, I meant to say that it doesn't work for the unedited MpMaster. This may be something with the MpMaster, I am thinking maybe I did download the wrong one, does anyone know what I may need to do to get it to look at the MD rather than itself? Daniel - Check your mail

I have started a new file, created a rectangle, put a simple contour toolpath on it with Coolant ON, and then posted it but No M08 comes out, I have tried it for my customized posts, MD's and CD's as well as the Mastercam Default posts, MD's, CD's. Nothing gives me an M08. 2 weeks ago everything worked just fine.

Daniel, I see what you are saying, I tried it just for kicks. It shows that the coolant is "supposed" to be on, it just doesnt post out the M08, and it is not just this machine def, post processor. It will not spit out the M08 code no matter which Machine, Control, and post I use.

Colin - quote: "The other thing you need to do is make sure that coolant is turned "on" in each individual operation." --- I made sure I tried forcing it to use the tool's step, peck and coolant rather than in just the operation... Didnt work, no M08 Daniel - Yes they are both unchecked, although I did try them both ways. Justin - I hadn't tried this but it doesn't fix the problem either. Quote.. "Also if the programmers are updating older mastercam files that did not use the mpmasterX2 machine def, control def and post the coolant commmands will not post out until you edit your parameters even if they were working before you tried the new post. At least this has been my experience." This is not an updated file, this is on every file including files that I created from scratch to try and work this out. Any other takers?

Hey Connor, where can I get mpsubrep.pst? It mentions it in my mpMaster control def, but it didnt come with it.

Be sure you have a check on the option to ... "Support coolant using coolant value (provides backward compatability for old posts)" It is under the Coolant tab of Machine General parameters for each Machine Definition

I have drilled many a holes in peek, without the allowance of contaminants down to .016" diameter. Not fun, the cold air gun really helped us, until it gets there, I would typically use a higher reference plane to allow a little more time for chips to come off the drill. When the chips were persistant we would actually have the operator sit there with a soft brush and rub it against the drill on the up movement to remove the chip, of course we had to override the rapid to about 25%. We only moved the brush parallel to the table rather than with the spindle to make sure it didnt get sucked into the hole. Also, PhilCott's method of going .100 deep in each hole before returning to the first hole to allow the material to cool can be really helpful as well.

Here is a weird one... I am in the process of creating/editing new post processors for all of the machines that we have here at our company. All of them will be based on IHS's MPMaster for X2-MR2. I started off with the Haas post since it was one of the easiest. Once it was done I distributed it to some programmers to test it and I started working on one for the Cincinnati. Halfway through testing post output, I noticed that It was not posting out Coolant commands (M07,M08, or M09). I am using the X style coolant commands controlled by pcan, pcan1, and pcan2. First, I went to check the Coolant tab in the machine definition, both check marks were set correctly. Next I disected the post to see if I accidentally deleted or commented out something that I shouldn't have, couldn't find anything. Since the Haas post was proven and guys were already using it, I re-opened the copy from their machine to compare, but NOW it will not post out coolant commmands either! Next I opened up the original unedited MpMaster... still No coolant commands. I went to the machine using the edited MD, CD and post that I had distributed right after I had finished it and it works on that machine fine! Next step, I sent the CD, MD, and post that wasnt working on my machine to a new machine and it posts coolant commands perfectly fine. I have tried flipping every setting to every possible combination between the 2 checkboxes in the coolant page just to try to get it to work, I have also tried all combinations of M08, M07, and M09 with before, with, or after options. Bottom line... I do not think it is the post, as I have the same issue on every post that I use, but the only thing that I would think overwrites the coolant commands in the post, is the Coolant tab in Machine General parameters but that isn't helping. I reiterate... that it was working on my machine at one time. The only major change recently was installing X3 beta 1. After looking at the download page for MpMaster, I see there is a version in which coolant is controlled in the post rather than the MD. I do not remember if I may have accidentally downloaded that one. But like I said Coolant did work at one point so not sure that it is relevant. Any Ideas???

No, I was just going by what Doug Nemeth had said here... http://www.emastercam.com/cgi-bin/ultimate...ic;f=1;t=014556 Robert

So I know that it was logged as a bug way back in X, but have we gotten any where on getting the ability to specify a WCS to create a Layout from a solid? I have been patiently waiting and as of X2 MR2 SP1 it still has not been fixed. Did you guys decide it just was not worth fixing, or is it just a lower priority? Is there any chance it will be fixed by X3? Robert

Scratch that last post, just figgered her out! Robert

Spinner or anyone else that has had this problem, Did you ever figure out the fix for this issue? We are having the exact same problem on one of our users PC's. Robert

Hi David, From the info you hav given, there does not appear to be anything wrong with that code, rather than moving from 0 to 360, it is moving the other direction... 360 to 0. When it gets to 0 it continues counting back from 360, if this is not what you want, you need to set an axis limit in your machine def. From what you said in your post, it sounds like your machine does not have an axis limit so if this code is not what you want, I might be better able to help if you could tell me what it is you expected to see? Robert

If possible, for us single monitor guys... It would be really nice that when the Operations manager was undocked and say floating in the middle of the graphics window, if I were to click on anything that should return me to the GUI that the operations manager would go to the background and the geometry screen would come to the foreground the way that it did in V9. That would be nice so that I could reselect geometry without having to move the operations manager. Otherwise it is useless to have it floating in the middle of the screen, you may as well just leave it on either the left or right side. As for the bugs, I think it is funny that everyone demands new features and better processing speeds but then doesn't realize that granting those requests are what cause more bugs! I dislike bugs as much as the next guy, but understand that sometimes they come with the territory of software enhancements and am willing to give mastercam a grace period to get them fixed in exchange. Now that we are on Maintenance it definitely seems that way more bugs are addressed on a much speedier basis. Just look at a what's new file. There are somewhere around 500 bug fixes per release.

Greg, a quick way to create a plane on the bottom that will give you the correct "A" output is to create a bounding box and then select the appropriate lines to give you the bottom plane with the X axis pointing the same direction as the Top plane. If it isnt creating a new plane, you may be accidentally re-selecting the bottom plane which as we noted earlier will not give you the correct X or Y Values

Noone?

About a week ago, one of our PC's using Mcam 9 started having the following problem, When the user hits the Nesting button in the Xform menu, it takes anywhere from 60-90 seconds for the nesting dialog box to pop up. Some times Mastercam even stops responding before it comes up. It is a new problem that has only been happening since last week, no new programs have been installed, and no settings have been changed (that I know about). Anyone seen this happen before?