I just had an issue where I couldn't post to the forum. If you are having that issue, clear to browser cache. That did the trick for me.

I think we saw the last of "Super Machinist" I don't think we were smart enough to understand his unique brand of complex teachings.

Good deal.

I have no idea what your deal is or why you feel the need to insult people. I am only trying to help the OP. I was a spring maker for the first 4 years of my career, so I thought I'd offer my limited knowledge. He can take from it what he wants. As far as 1018 vs 1095, I'm not going to argue with you about it. The fact is there is 5x the amount of carbon in 1095. Calling them the same is BS.

Sorry, I'm not familiar with F@gors automated tool setting cycles. We use Blum lasers on some of our machine, and they use their own macros. I guess I was thinking you were looking for a way to modify the existing G54, G55, ... offsets that were already recorded.

I'm not sure I completely understand, but you can automatically change the Offset table with macro #5263, which is G56, Z axis. And I should mention I don't have a f@gor control. I've never ran one. But in Fanuc it would look something like this. #5261 = [do your calculation here]

1018 is not like 1095. 1018 is more machinable, but not typically used for springs, but that would depend on the function of what you're making. What type of spring are you making? Maybe a little more info might help. I used to make all types many, many years ago. Typically we wouldn't machine much, mostly punched.

Just a thought, when we use the Dprnt, we have to change the COMM Channel to send the data out thru the RS232. Here an example G10L50 N0020R1 G11 Changes to channel 1 BTW - This is on our Makino's. I'm not sure about the Yasnac.

You are truly a king among kings. How could I have doubted you. You're a legend in you own mind. Oh, and after my first year they ask me to be CEO, so bam! I win.

Well that's not really saying much. I've met "lead programmers" that couldn't find the file open menu with a cheat sheet. But since you asked. I started as a general shop helper. Then moved to debur. By the end of my first year I think I was learning manual mills. And by your name, I assume you play guitar?

I think your the guy who comes into our shops claiming to be the best machinist/programmer in town. Then after spending a half a day, you realize how little you know and never show up the next day. You may think I'm exaggerating, but I've literally seen this happen many times. I've been in this trade over 25 years and I've yet to see anyone who can do the things you claim to do after only a years experience. I think you don't want to give anyone your knowledge because there is very little to give.

This is a joke right?

I'm not sure if you ever found an answer to this or not. But don't know Haas real well, but I was pretty good on a Fadal many years ago and it had this function. We used to use it all the time. Anyway, I did some digging on the Haas and I found this. I hope it helps. Operator Checking Questions Ever thought how useful it would be to have your machine ask the operator a question – maybe to ensure the part has been turned over, or which number is to be engraved or any number of other possibilities? The Haas control has a function called Interactive User Input which incorporated into vers. 11.20 and released in 2002 provides the programmer with a new M code, M109 that allows a G-code program to place a short prompt on the screen, get a single character input from the user and store it in a macro variable. The first 15 characters from the comment following the M109 will be displayed as a prompt in the lower left corner of the screen. A macro variable in the range 500 through 599 must be specified by a P code. Note also that due to the look-ahead feature, it is necessary to include a loop in the program following the M109 to check for a non-zero response before continuing. The program can check for any character that can be entered from the keyboard by comparing with the decimal equivalent of the ASCII character. Here are a few common characters: A – 65 a – 97 B – 66 b – 98 C – 67 c – 99 N – 78 n – 110 Y – 89 y – 121 0 – 48 + – 43 1 – 49 – 45 2 – 50 * 42 3 – 51 / 47 The following sample program will ask the user a Yes/No question then wait for him to enter either a Y or an N. All other characters will be ignored. N1 #501= 0. (CLEAR THE VARIABLE) M109 P501 (Sleep 1 min?) N5 IF [ #501 EQ 0. ] GOTO5 (WAIT FOR A KEY) IF [ #501 EQ 89. ] GOTO10 (Y) IF [ #501 EQ 78. ] GOTO20 (N) GOTO1 (KEEP CHECKING) N10 (A Y WAS ENTERED) M95 (00:01) GOTO30 N20 (AN N WAS ENTERED) G04 P1. (DO NOTHING FOR 1 SECOND) N30 (STOP) M30 The following sample program will ask the user to select a number then wait for him to enter a 1, 2 or a 3. All other characters will be ignored. O00234 (SAMPLE PROGRAM) N1 #501= 0. (CLEAR THE VARIABLE) M109 P501 (Pick 1, 2 or 3:) N5 IF [ #501 EQ 0. ] GOTO5 (WAIT FOR A KEY) IF [ #501 EQ 49. ] GOTO10 (1) IF [ #501 EQ 50. ] GOTO20 (2) IF [ #501 EQ 51. ] GOTO30 (3) GOTO1 (KEEP CHECKING) N10 (A 1 WAS ENTERED) M95 (00:01) GOTO30 N20 (A 2 WAS ENTERED) G04 P5. (DO NOTHING FOR 5 SECONDS) N30 (A 3 WAS ENTERED) M30

I just found a bug in MX7, that is still present in MX8 beta that I wanted to share with everyone before you get bit like I did. I will submit this tomorrow. When using a boundary box on a surface high speed tool path, it is violating my boundary when my transition is set to smooth. the violation has a direct correlation to the step over distance. I will attach some picture to try and show what's going on. I hope I explained everything well enough. Ray Capture1.pdf Capture2.pdf Capture3.pdf

I don't understand. We have a Prototrak SMX and it reads G18 just fine. We also use .GCD all the time. Perhaps this was an option that you didn't purchase or maybe you're not reading in the GCD code properly. I'm not the one who runs the machine, but I think you have to OPEN AS: G Code .GCD I hope this helps

Can you post a zip2go file. What version MC are you running? Maybe for some reason your 'Z' is be truncated on the G2, G3 lines to a 2 place decimal, but not on the linear moves.

Try to project all of your geometry to the same Z plane. The re-do the operation. BTW - I don't think this is a post issue. MasterCam is probably doing exactly what it should do. You contour must not lie perfectly on the cutting plane.

I only wish that the operation manager menu icons could be customizable. That would solve the problem. I hate when I hit verify when I wanted to hit backplot, and I have to wait for the verify window to open. All while my fingers are crossed hoping that MC doesn't crash, and trying to remember the last time I saved.

Yes you can. Instead of using depth cuts, go to cut parameters and change contour type to 'ramp' Then for what your describing you probably want to use plunge

Aaron, I sent you a message.

Yes, we rotate about the Y. On the substitute Operation, its greyed out, but it is rotating about the Y as well, but the axis that it is being substituted is -X-. I did however try to switch that, and the result was not correct.

So a co-worker of my asked me to look into this. He is trying to do an axis substitution which he says he has done many times prior to MX7. But for some reason when he does this Mastercam X7 position the -B- axis 90 degrees off. I do not normally use axis substitution, so I have no idea why this is off. I was wondering if someone out there can confirm that this is a bug or possibly that we may be using this wrong. In my sample file I have two operations. The first is using Axis substitution, and if you post it, you can see that the -B- axis starts the cut at about 97 degrees. The second operation, I used curve 5th axis. This is the method I would normally use. And when you post this one the -B- positions correctly at about B7. degrees to start the cut. Note that we program our horizontals using the top plane as -B- zero, not the front plane. So this may not post out correctly your horizontal post. Any help would be appreciated. thanks Ray 29694_test_output.txt 29694_TEST_SUBMITT.MCX-7

There are a few softwares out there that say they can convert STL's into solid, but we've tried a few and had little success with complicated STL's. But simple STL's work OK The few we've tried are, Vericut, Spaceclaim, and currently we are trying Syscode.