I believe that is .04921 inches / thread ( or ipr)

http://www.nachiamerica.com/c-1/Cutting-Tools/Drills/

I have turned the jaws on a 3-jaw then opened the jaws to clamp on ID.

Started w/ Webber 'Prompt' for CAM in '83. Used Autocad for a couple of years after that for CAD Company got a couple of seats of Mastercam and Cadkey around '85-'86 methinks. I've stayed with both since then (albeit Cadkey is now Keycreator) and haven't looked back.

I use custom macro to solve these issues. In a nutshell: 1. Main program calls and changes tools then calls cutting subprogram 2. Cutting subprogram is put into 'While" loop which increments the parts coordinate system (G10L20P__) with each iteration. example (15 PARTS): O1241(mill sub) #21=1 WHILE [#21 LE 15] DO 1 G54.1P#21 | | approach and do cutting | retract for fixture clearance | #21=[#21+1] END 1 | M99 The toolpath group in the operations manager contains only 1 part in 1 fixture. More fixtures due to another operation on the part ? use another toolpath group and repeat.

I'm w/ Matt. Part zero and different offsets for each view. Been doing it that way w/ Mcam since '88 , but now I digress.

I've got a system of macros in our HMCs and VMC's which enables us to write a program for one part only and the system macros will take care of the rest of the parts on the fixture automatically. All the operator has to do is change one variable to go from single-shot mode to complete pallet mode using the exact same code. Really easy to maintain the programs or alter them if needs be. On our verticals we can choose our start part and our finish part so say on a pallet of 20 parts we can make parts 1-20, 3-9, 2-18 10-17, etc or just 1 part. We do what Colin mentions and also list our hole locations (for canned cycles) in only 1 subprogram / feature face. We use a couple of local variables to jump to or skip over hole locations. The hole locations are programmed only once thus making it very easy to maintain or change. This all makes for pretty compact programs. The system macros are applied across the board so , to our operators, a Yasnak, Fanuc, Mazak, Haas, Vertical of Horizontal, look pretty much the same.

Mike, basically that is what I want to do w/ the exception that I have to reach over the high part of the 'V' to the center of the 'V' which will require a cutter diameter of 3" to 4" depending on the diameter of the shank or arbor. Ron, I'll check the link as soon as I get back from the trenches. specv, ditto w/ AB

I need assistance finding a tool to make a 3/32 full radius slot about 7/8 deep and 2.5" long in C1117. I figure I'll need a 4" OD cutter if the bore ID is 1". I would prefer that the cutter uses inserts but will settle w/ solid carbide as the job is a repeating and somewhat high volume job. The feature is a relief groove at the bottom of the 'V' in a V-block. The 'V' and slot used to be cut on the old gang-millers and now that is no longer an option. I am temporarily using a 3/32 ball emill and it is a very slow process. Can anybody point me to any cutting tool manufacturers who might have such an item ? I have looked at Sandvik, Iscar, Seco, Robb Jack, an PH Horn so far w/ little luck. tia

Here is how I did it many moons ago. Notice z_mult ! # -------------------------------------------------------------------------- # Machine Specific Settings # -------------------------------------------------------------------------- #Machine axis switches, initial y_axis_mch : no$ #Machine has Y axis, 0=no, 1=yes old_new_sw : 1 #Switch old (6T), new (0T+) cycle formats, 0=old, 1=new wcs_origin : 0 #Always use the WCS origin for coordinates dia_mult : 2 #Multiplier for output on X axis (Neg. switches sign of X) y_mult : 1 #Multiplier for output on Y axis (Neg. switches sign of Y) z_mult : -1 #Multiplier for output on Z axis (Neg. switches sign of Z) dia_shift : 0 #Shift for output on X axis, radial entry y_shift : 0 #Shift for output on Y axis z_shift : 0 #Shift for output on Z axis map_home : yes$ #Use home positions as enterd or map to machine axis

that is to say ersatz.

True you are. I used offset 99 to be compatible with machines that were using Fanuc Tool Life Management. (sorta an ersatx TLM)

We use macros to automate the indexing and WCS selection for our horizontals and verticals, as well as T-code,H-code and D-code syncronization. It doesn't matter if there is only 1 part on the fixture or 100 parts, change the value of 1 variable and the machine will do either 1 part (great for setup) or multiple parts using the exact same code. Using a standardized tool launching macro, we no longer worry about T,H, and D- code syncronization. Just copy the spindle tools H-offset to an unused location (say 99) and ditto for the D-offset (or use say, 98 or whichever). Then call up the tool, jump to the macro to copy the offsets , G43 the tool w/ H99 and return to the main program.

I would consider using a Chick 4-sided double vise tstone to start with, cuz' it just comes in too handy for all sorts of work. Next I would make your own 4 sided tstones w/ a common bolt-pin pattern. Make them out of aluminum and do your fixturing w/ steel sub-plate mounted to the aforementioned aluminum tstones. A square configuration is OK if you only need to get at two faces of your parts, unless the part is large enough that you can reach 3 faces. My favorite config looks like a + sign when viewed down the centerline of the B-axis. There is plenty of clearance to get to 3 sides of your part + some non-90 degree features as well without the previous part getting in the way of the part you are working on. I find that the more sides you have, the less room and feature reach you have you have. (Tstone sides + feature faces = extended tooling (at best). Consider attempting to finish the part w/ multi-ops on the same tstone, instead of fitting as many parts as you can (1-op) on the tstone. Instant feedback and faster throughput can be gained this way (though a bit longer setup and more available tools are required) my 2 cents,

We are quite happy w/ our Mazak HCN4000's. They were priced just slightly higher than the Haas 400mm, but they are much faster than the Haas, or the Tsugami 300mm.

I'm w/ Doug. Another benefit of the TLO being the actual length of the tool (gage line to tool tip) is that the tool is now transportable between similar shank machine tools even if you have to swap a pull stud to go from , say, a Mazak Cat40 to a Kitamura Cat 40. my .02

How's about pbld, n$, "M98P9000", *tloffno$ e$

toolno is probably formatted w/ a "T". try setting another variable = toolno and formatting it w/ a "P"

?? Place some geometry at your tool change point, Zoom-->Fit, and backplot ??

We bought 2 xtra pallets / machine. The Mazaks are 2 pallet versions, the company didn't want to spring for the multi-pallet versions due to cost and floorspace restrictions, and they are hoping not to have to buy 20-30 more pallets to accommodate our existing Tsugami 300mm fixtures. I'll be taking a much closer look at the HCN4000s next week to see if a modified engine hoist will fit. cp

We have two Mazak HCN4000 horizontals showing up by June 10. Our Tsugami's have 300mm pallets and we can easily transport them between machines w/ a lifting table on wheels and some muscle. I fear that the 400mm pallets are going to be too heavy/clumsy for that approach. Does anyone have a favorite solution to this problem ?? (crane on wheels, etc). Brand names would be appreciated also thanks in advance cp

Our company has just ordered a new NZ-2000-T3Y2 multi-tasker and I need to tool it up. Would you please share your recommendations and advice as to which companies make rotary and/or static tooling (MD Tooling etc)? We are also interested in quick change adaptations,such as Capto. tia cp

Not so sure how to do it on an OSP, but on Fanucs and Yasnaks we interrogate our tool length offsets at the beginning of each program be it Mill or Lathe. seems to me that you want to detect a long tool before you index the turret. in a nutshell: begin loop. Start w/ the system variable to tool 1's offset compare it to the max length if less or equal, continue if more, trip alarm update loop counter variable +1 back to top of loop, this time it will look at tool 2's offset.. etc. We do this to look for decimal place typo's. (operators key in the values from the presetters.) Same idea can be used to determing a safe index position for a lathe/millturn. This time use the loop to determine the longest tool, add a half inch (or so) to that, convert to machine coordinates, store that value in a common variable, then G00Z(variable) for safe index. Applications for macro programming are endless IMHO cp

As I recall, the G28, G30 etc commands are a 2 step function. Go to reference point, but first go thru the point specified by the XYZ sections of the block. normally you can see this happen if you execute the G28 command in single block mode. ex: G91G28X0Y0Z0 says to go 'home' but first go nowhere (G91X0Y0Z0) G90G28X0Y0Z0 says to 'go home' but first go to X0Y0Z0 cuz' of the G90. Methinks the parameter values are trailing zero metric so an english value of -.001 will be represented by a parameter value of -25, -.1 represented as -2500 etc. hope this helps. cp

http://www.abtoolsinc.com/