SAIPEM has a good suggestion here. You can't really change the "layout" of how DPRINT outputs, but you can add notes and comments to the outputs so that you can "read" the data instead of just looking at a bunch of numbers and variables.

Its been quite a few years, but I used work at a place where we used several different methods for inspection/qualifying data. Several machines were linked to a PC with software that would allow itself to remain "open" to capture and not close in between transimissions. Basically, its set up for different trigger usage in a DNC type app. Other machines would have a printer hooked directly to it and the data would be instant. Sorry I can't give you the complete layout of this whole structure, but back then, I wasn't paying much attention....

Depending on the machine but most of them peck tap in the same manner of a G73 motion. It doesn't retract completely. In this case, its also controlled by the same parameter as the retract value for G73. If the parameter is set real short (like only a couple thou) then the retract will seemingly be non-existent. Some machines with peck tapping may have a seperate parameter ( or another code added to override/control retract ) to adjust this.

I've used M29 and M135 on Makino (depending on age). M29 works for most Fanucs... but then again theres also M109 (Niigata), M105, .....all Fanuc controls. quote: Somebody here gave me a little lesson some years ago (can't remember who) that G codes are control specific and M codes are machine manufacturer specific. Its 'generally accepted' but not necessarily. There are some G codes specific to machines as well even though the controls are the "same"....

Many of us know that you can nest up to 4 levels (Fanuc) with a M98... This is from the Fanuc manual: " Calls can be nested to a depth of four levels including simple calls (G65) and modal calls (G66). This does not include subprogram calls (M98). " Is this to say that you can go 7 or 8 levels deep? So from the 4th level M98, you can macro call to a sub, then go 3 more levels from there? I'm with James though... KIS or KISS.... The Haas book doesn't say how deep you can nest. At least I've never found it. But with M97 available, why bother unless you have "common" subs for different parts. Mazaks can nest to 8 levels.

Roger, Bruce got the part that he'll need to use multiple offsets. What he was looking for is Dynamic Comp. Mazaks have the ability to set this comp for parts that don't necessarily repeat or rotate exactly on center. In other words, you can program from center, but if your part is off some (due to loading, orientation or otherwise), you can probe, indicate or set the "offcenter" amount and the machine will comp for that in rotation and and position. Cool feature...

Look in your formatted variables of the post. code: fmt Q 2 peck1 #First peck increment (positive) fmt Q 2 shftdrl #Fine bore tool shift fmt R 2 refht_a #Reference height fmt R 2 refht_i #Reference height For peck1, you should have a "Q" there. Or,... check you drill output at G73.... code: pchpbrk #Canned Chip Break Cycle pdrlcommonb pcan1, pbld, n, *sgdrill, *sgdrlref, pxout, pyout, pfzout, pcout, prdrlout, *peck1, *feed, strcantext, e pcom_movea It should be using "peck1" for the string.

quote: ...if someone could tell me where or what lines I need to take out to keep the table and head from moving back and forth... FYI: This is the line that's moving your table and head.... code: G91G1X[#991/25.4]Y[#992/25.4]Z[#993/25.4]F600. In which James' version of warmup skips as well as go through different RPMs. quote: ...and the oper. is forever deleting the warm up prog, makes it easy to just reload 1 prog... As John said, you could shoot him, or... why not just make it a 9000 program. Maybe that will keep the guy from say "accidentaly" deleting the program.

Also look at these: Abbot . . Mid-State . . Stevens . . or Yuasa

I'm not doubting G10s... I use them all the time too. I'm just trying to understand how Fastmill is using them to help out with his post.

quote: Thank you... I will look at that... Not sure if it will help though... No, it won't. I sort of get what you're doing. I'd like to see what the sub looks like and the code it uses though. Not sure if I'm understanding you here though. You're sweeping a position on a stone or fixure then having to handtype that as a G10 offset in each sub? If I'm thinking right, (it is late for me), why not just use multiple work offsets? If you're sweeping each spot anyway.....

Do you really need G10s? (since I'm not seeing any in your sample program). If you have subs for everything, is that to say that you have constant patterns that repeat for different sized parts? To me it sounds more like you need to get involved with nesting routines/patterns for MC.

+1 Mark..... I use the custom G codes too... really cleans up the program.

I don't see why not. As far as linear coding, all that should be needed is to set the post (and control def) to not output arcs. The sequence (if I remember right) also has a setting in control def. Only thing is you may have to modify the post to be able to output higher values than 4 digits for the sequence number. Some controls will also use decimal values for numbers ( like "N1132.4435" ). This allows for more number combinations and ability to "tag" your sequences for easier searching. Not sure if this can apply to that type of machine though, haven't programmed one of those yet. HTH

Amen Hardmill.

quote: psycho, have u got all the machine defs done for down there Yeah, right..... Time is against me. We're busier than hell. I'm the only one familiar enough with MC to do this... so as of yet, I haven't released it for use in the shop. I have several of them done and quite a few more to go.

Murlin, since CAD systems are actually in "units" of measure and not specifically inches or metric, you can just draw the part at its face value in the "inch" system. The only time its gonna be an issue is when you tool it. Either have a metric tool library set up, or convert the inch tools for metric values and set up a library. I used to program a metric machine but I used the same "inch MasterCam" to program. Now in X, I think you can freely switch between inch and metric after you choose a MD. In the Properties you can choose different tool libraries, operation defaults files etc. If you set metric files, I think this should work real easy for you. I haven't played with this yet to try though.

+1 Robk for the Mitsubishi AJX. Use them here also. Not familiar with the material though. Sounds like tough stuff and given the machine being used I'd try the high feed cutters. But at 4" deep, I may look into plunge mills to plow it out.

Well, not knowing what material you're working with other than its a forging, I'm inclined to think that you may be using the wrong machine for the app. The 300VTC is more geared for high speed machining of large work pieces. If you need a machine to "plow" large and/or deep cavities, this particular model may not do it. Better off with a FJV or V series. Follow Hardmill's advice on this one for this particular machine and change the process/methods. I think you have a good machine, just need a different approach.

quote: I don't know what that means, LOL!!!! Sounds like you're beginning to pick up a little "Janglish" or "Jenglish" (Japanese version of English). It only gets better.... Yeah right Anyway, as I said, be real careful with the parameters. You can tighten up the bell too much (where its similar to linear) or loosen it too much where either way, undesirable results. Back up your parameters and make suttle changes until you're familar with the parameter controls. And with each change, back them up as a different file until you're through. Another tip is to run the machine for a while after a change before making another change. This way, in the "in between time", you can run normal part programs and make sure that what you've changed doesn't cause a mishap/problem with some other stuff during machining. Once you're familar with it and have enough time behind you doing this, then you'll have a general idea for setting a "default" set to adjust other machines from. But never assume anything. Even if the models are the same. I've had them where the servos were tuned so differently (same machines, same model etc.) that a "default" didn't quite work the way I wanted. good luck and let the chips fly!!

Coming in late on this one... ( had an operator do a major "oops" and have been wrenching on machines all week) ..... anyway.... James and David are right on. As well as Lars about parameters. I don't recall the exact difference in seek time and block read (or look ahead) but its something along the lines as described. 3D (as mentioned) will see a big difference. In normal 2D stuff, you won't see a big difference until you really start pushing feedrates. G8 on many machines will have certain limits set, from there G5 can take over. For example: In G8, a machine may not be able to process (or is limited to) feedrates under 900 or 1000 IPM. Beyond that you would need the G5 option. Now in most cases, G8 won't sustain accuracy to within preset limits beyond 600 or maybe 700 IPM if you're lucky. I roughing, this may not be a problem. You can however tweak the servos to increase this window. But I would only do this if you were ABSOLUTELY comfortable at this. You can easily "lose" your machine if you make a few wrong adjustments and your 'slower' feed stuff as well as accuracy in finishing will sacrifice. Lars' comment is an example of poor parameter settings (unless the machine ain't bolted down). I've had machines in G8 that shook at the head so bad, like a jack hammer on steroids, that I thought it was gonna flip like a turtle. Obviously made adjustments to that one..

Hmmm .... Half of us are "one page" and the other half is on another page of this book. Theepres is looking to do internal subbing, NOT external (like M98 or M198). The answer for FANUC (as some have mentioned here) is NO. There are some work arounds but not quite as effective. I use a lot of "While/Do"s like James mentioned. You can use "GOTO" but as he also mentioned, this causes the control to seek the file from the top. If the program is long and/or the control is slow, this will actually "pause" the machine until it finds it. Another way is to use "M99P???" with a counter set in variable, but this has the same effect as a GOTO when its used in the "main body" of the program. Haas has M97, Mazaks M98H?? .. Yep, Fanuc needs to add this to their stuff.

James.... quote: ( G54) G90 G10 L2 P1 X00.0000 Y00.0000 Z00.000 B000.000 ( G55) G90 G10 L2 P2 X00.0000 Y00.0000 Z00.000 B000.000 ( G56) G90 G10 L2 P3 X00.0000 Y00.0000 Z00.000 B000.000 ( G56) G90 G10 L2 P4 X00.0000 Y00.0000 Z00.000 B000.000 ( G57) G90 G10 L2 P5 X00.0000 Y00.0000 Z00.000 B000.000 ( G58) G90 G10 L2 P6 X00.0000 Y00.0000 Z00.000 B000.000 ( G59) G90 G10 L2 P7 X00.0000 Y00.0000 Z00.000 B000.000 G11 should be: ( G54) G90 G10 L2 P1 X00.0000 Y00.0000 Z00.000 B000.000 ( G55) G90 G10 L2 P2 X00.0000 Y00.0000 Z00.000 B000.000 ( G56) G90 G10 L2 P3 X00.0000 Y00.0000 Z00.000 B000.000 ( G57) G90 G10 L2 P4 X00.0000 Y00.0000 Z00.000 B000.000 ( G58) G90 G10 L2 P5 X00.0000 Y00.0000 Z00.000 B000.000 ( G59) G90 G10 L2 P6 X00.0000 Y00.0000 Z00.000 B000.000 G11 Must still be early eh?!!

I think you're describing a "Corner Rounder" ? If I understand your tool it sounds like a 5mm corner rounder with a 1/4" pilot? For these types of tools, I usually program the tool as a 1/4" tool ( or whatever the pilot diameter is). To climb cut (provided its not a left handed tool), "Comp Left". For Z depth, you can set the tool at the back end (or 'top') of the 5mm radius and call that zero (therefore programming at Z0), or set it at the bottom of the tip and program Z to the top of the radius. Just sneak up on it by keeping the Z a little short and running plus (+) comp at first until you like the result. This is all provided we are talking about the same tool type.....

First of all, what material are you cutting? and what type of cutting are you doing (pocketing, slotting, contour, 3D something?)? About the tool, if you just plug it in and run the same rates, with the 4flute you cut the FPT in half. This can cause some chatter since your chip load is alot lighter now. Some other issue,... did the helix angles change? Chip clearance may be an issue now as well since the end gash ( from a 2fl to a 4fl) is alot tighter. This can be a problem (particularly in slotting or pocketing) in say Aluminum and such.