Weird, I've never had the major diameter value lit up. It's always been ghosted out, and I never even saw it there. *shrugs*

This thread rocks. I've been programming CNC mills for 10 years and have learned more from this thread than I have in a long time. You "old timers" are crazy. I don't even know what a jig bore is, never seen an od/id grinder, saw my first blanchard grinder a couple years ago, practically never touch manual mills or lathes. I think I have cut threads on a lathe twice, never grind tools, can't sharpen a drill unless it's with a darex or drill doctor. Actually I'm embarrassed to even post this, but had to give credit to the guys that really know what they're doing

And for multiple passes I just copy the operation with different Allowance(overcut) values.

quote: I tried the thread milling option and got linerized code with that too.Doesn't that mean that your post processor has the following set to zero? code: helix_arc : 2 #Support helix arc output, 0=no, 1=all planes, 2=XY plane only

Thanks everyone for your replies. I'm going to look into programming from top view. Seems easier to post the same file to a horizontal or vertical as needs dictate. Thanks again, I appreciate all of the responses.

Terry can you elaborate please? Do you draw the part like on a vertical, normal WCS top up? And then when you want to run it on a horizontal create a new WCS with front up and make all of the toolpaths reference that wcs? How come the post processors for horizontals don't use the same plane as verticals?

I'm trying to figure out the best way to write my programs(new shop with horizontals & verticals), and was wondering if you guys have 2 different files for the same part so it can be ran on horizontals & verticals, or if there is someway to make the same file work on both. It appears the proper way to program for a horizontal is front view, but vertical is top view. How come they aren't both top view? Thanks in advance for any help, it's kinda confusing.

Ok, I have no idea what I'm doing, but it seems to have worked. Under #Rotary/Index variables I added this: code: clampstate : 0 #Pallet change switch And then under #General G and M Code String select tables I added this: code: # Table lock and unlock codes sclamp M78 #Pallet clamp sunclamp M79 #Pallet unclamp And finally under ptlchg0 I added this: code: if indx_out <> prv_indx_out, [ clampstate = 1 *sunclamp, e ] if cuttype = zero, ppos_cax_lin if indx_out = prv_indx_out & clampstate = 1, [ clampstate = 0 *sclamp, e ] It seems to have worked, and I only barely understand why!

Ack~! Sorry for not responding guys, I keep forgetting email notification doesn't happen automatically. Thanks for all of the replies though. It was a one time deal so to make it work I just did a search and replace of all of the Z values to -.015" from 4.935". I'm going to check into the incremental suggestion though.

The generic HAAS post. The machine I am using is an OKK, but I don't have a post for it.

Good morning everyone, I was hoping someone could help me out with some post issues I am having. I am trying to get clamp/unclamp code to work correctly and this is what I have so far: code: psof #Start of file for non-zero tool number pcuttype toolchng = one if ntools = one, ~~~~~~~~~~~~~~~~~~~~~ pbld, n, "G0G40G80G90G49Z0", *speed, e if stagetool >= zero, pbld, n, *t, "M206", ptoolcomment, e comment if rot_on_x & cuttype = zero, pbld, n, *sunlock, e pindex if rot_on_x & cuttype = zero, pbld, n, *slock, e if mi1 > one, absinc = zero pcan1, pbld, n, *sgcode, pwcs, pfxout, pfyout, ~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~ ptlchg0 #Call from NCI null tool change (tool number repeats) pcuttype pcom_moveb ~~~~~~~~~~~~~~~~~~~~~ if rot_on_x & cuttype = 0, pbld, n, *sunlock, e if cuttype = zero, ppos_cax_lin if rot_on_x & cuttype = 0, pbld, n, *slock, e ~~~~~~~~~~~~~~~~~~~~~ The problem I am having is that it puts the clamp/unclamp at every null tool change(ie g80) even when there is no pallet rotation. Example: code: G98G81R.1Z-.13F10. Y.593 X-2.Y2. X-3.625 G80 (CLEARANCE MOVE B270) M79 M78 X-2.Z5. (CLEARANCE MOVE B0) G54X-6.Y2. Z5. M79 B0 M78 (C'DRILL C'BORES B0) M79 M78 X-10.625Y3.625Z.1 G98G81R.1Z-.31F10. Y.375 G80 (C'DRILL 1/8NPT B0) M79 M78 X-10.Y2. Thank you in advance for any and all replies.

Good morning everyone, I am having problems wrapping an engraving on a cylinder and was hoping someone could help me out. I have a 4th axis(aligned with "X") with a 9.9" diameter cylinder on it. My datum is the right edge in "X", centered in "Y", and the top of the part is "Z". I have text at X-7.875 Y1.1 Z0. On the tool parameter page I have the rotary box checked with "Axis Substitution", "Substitute Y Axis", "CW" and 9.9" diameter. The problem is since my axis rotates on Z0 when I backplot the engraving is happening 4.95" above the part. How do I change the rotation so it happens based on Z-4.95"? Thanks in advance for any and all replies. edit: Forgot to mention 9.1 MR0304

tag

Thanks for the suggestion Dave, unfortunately my file already has that code (revision log goes to 03/15/04)

Anyone else have any thoughts?

Seriously though, if you drew a clock, and wanted to go from 12:00 to 1:00(positive direction), since you can't move the little hand(your coordinate system)you have to move the clock(your part)counterclockwise. Just like X+ moves the table in a negative direction

Thanks for the suggestion, unfortunately I have 250MB allocated to each of the database and toopath, so I don't think that's the problem.

If you mean as opposed to when posting the actual .nc file then yes, the setup sheet is the only error.

Greetings all, I am having a problem with my setup sheet (modified mill2.set) and was wondering if someone would be willing to assist me. The problem seems to be when I have multiple toolpath groups. Errors are detected during posting (view code) and the end result is the "Z" depths are messed up(I believe only in the final toolpath group). code: Combined Mill and Lathe Post Processor Version 9.19 © Copyright 1992-2004 CNC Software, Inc. Processing file with MILL... Cannot read record 66 in buffer 1 buffer is too small. Postblock label ptlchg Any thoughts? Thanks in advance for any and all replies. Version 9.1 MR0304