How about a release date? Well over a year since X4... Dealer guaranteed a new release every year with continues maintenance updates in between...

Where is the example that Ron did? I found a post a while back and bookmarked it to go back and copy some of the custom examples but my link doesn't work and I can't find it through the seaarch?

You have mail...

Happens here often... Restart the computer, delete the extra chains, regen the tollpath then post...

Talked with my gear cutter and he is making me a chart to get you some data...

Very busy day, I will have time in the morning...

I don't have a backlash or tolerance on what we have but I can do some over pin measurements and put togeather a couple gear ratios and measure the backlash...

I have to wire some odd gears (change gears) with profile shift, what is the procedure used to get gear.dll to create the geometry correct? 12 DP 20 PA 2.75 CENTER DISTANCE 22 TEETH (on a 23 PITCH CIRCLE) With standard 43 tooth 23 TEETH (on a 24 PITCH CIRCLE) With standard 42 tooth 24 TEETH (on a 25 PITCH CIRCLE) With standard 41 tooth Many more... We have these hobbed normaly and they work great but I have to create some prototypes to work with and need to wire them...

Has Dynamic mill been fixed when using depth cuts?

I had the same problem with an older TNC 151 post, I think I changed the FR$ to FRPLUNGE$...

Right click - Reverse tool path...

When using depth cuts and finish depth is there a flag to indicate when the rough is complete or the start of the finish? I want to use a flag in the plinout or prapidout similar to rapid type 7 to turn off a feature before starting my finish pass...

I assumed something like that, just going to need a littlet more guidance though. I assume you do the loop with pparameter$, then?

How can I retrieve the misc integers from the entire tool path and not just the current op? I'm trying to add information in the header and need all the misc intergers...

I don't think I can get next to work correctly without doing some type of work around because next_fr doesn't appear to be available?

I did the keep bit to read the buffer... I think I have everything working now with the buffer method but would love to go a step further and try the variable method... ak762, I think what your saying is to save the NCI line to variables like prvx, prvy, etc then run the next line and output prvx and prvy on that line?

I figured out how to get my approach point but do have a question to set my if statements... What variables are used for approach = true and retract = true? Here is what I want: psof$ if approach = true, pwritbuf1 pretract pwritbuf1 peof$ if retract = true, pretract size1 = rbuf(1,0) while rc1 < size1, preadbuf if rc1 = size1, preadlast Still trying to figure out how to get my feedrates backed up a line?

I think buffers are the only way to get this to work? Output needs to look like this: X, Y, Bow, Feedrate Bow is a calculation TAN of sweep/4 but for the next move... Feedrate is the feed and offset of the next move, negative for left positive for right... Here is my current code: code: # ----------------------------------------------- # Buffer Functions # ----------------------------------------------- rc1 : 1 wc1 : 1 size1 : 0 gcode_1 : 0 ccomp_1 : 0 x_1 : 0 y_1 : 0 sweep_1 : 0 fr_1 : 0 fbuf 1 0 6 0 0 # ----------------------------------------------- # POSTLINES # ----------------------------------------------- pfr # Feedrate if fr$ = -1, fr$ = prv_fr$ if fr$ = -2, fr$ = zero quality = fr$ if ccomp$ = 2, neg_feed = 1 if neg_feed = 1, quality = -quality if ccomp$ = 4, neg_feed = 0 *quality !fr$ # ----------------------------------------------- # Buffer Read / Write # ----------------------------------------------- pwritbuf1 # Write buffer number 1 gcode_1 = gcode$ ccomp_1 = ccomp$ x_1 = x$ y_1 = y$ sweep_1 = sweep$ fr_1 = fr$ gcode_1 = wbuf(one,wc1) preadbuf1 # Read buffer number 1 gcode_1 = rbuf(1,rc1) gcode$ = gcode_1 ccomp$ = ccomp_1 x$ = x_1 y$ = y_1 sweep$ = sweep_1 fr$ = fr_1 preadnext # Read buffer number 1 gcode_1 = rbuf(one,rc1) preadbuf size1 = rbuf(one,zero) preadbuf1 preadnext if gcode_1 > one, bow = tan(sweep_1/four) else, bow = zero rc1 = rc1 - 1 if gcode$ = zero, prapidout if gcode$ = one, plinout if gcode$ > one, pcirout preadlast size1 = rbuf(one,zero) preadbuf1 bow = zero if gcode$ = zero, prapidout if gcode$ = one, plinout if gcode$ > one, pcirout # ----------------------------------------------- # Axis linear/circular motion # ----------------------------------------------- prapidout # Linear line movement - at rapid feedrate *x$, *y$, *bow, pfr, e$ plinout # Linear line movement - at feedrate prapidout pcirout # Circular interpolation prapidout # ----------------------------------------------- # POSTLINES, PRE-DEFINED # ----------------------------------------------- pheader$ # File header psof0$ # Start of file for tool zero psof$ psof$ # Start of file for non-zero tool ptlchg0$ # Null tool change ptlchng$ ptlchg$ # Tool change peof0$ # End of file for tool zero peof$ peof$ # End of file for non-zero tool size1 = rbuf(1,0) while rc1 < size1, preadbuf if rc1 = size1, preadlast # ----------------------------------------------- # Axis motion # ----------------------------------------------- prapid$ # Linear line movement - at rapid feedrate pwritbuf1 !x$, !y$ plin$ # Linear line movement - at feedrate prapid$ pcir$ # Circular interpolation prapid$ Now for the problems: 1. If selecting approach or retract positions I can't get them output to the NC code? They are in the NCI... I don't think the buffer is getting them? The code is assembled as such: X, Y, Bow, FeedRate Bow is calculated, Tan of Sweep/4. Bow is output on the line previous to the arc move... FeedRate is negative for left offset and positive for right offset. FeedRate is output on the line previous to the move... 2. I can't get the feedrate for the next move on the line previous, somehow I got it to work for bow but can't get feedrate to work? Is there a way to retrieve next line information from the NCI without using buffers?

Have you tried reverse toolpath? You could use a thread mill path which can be used bottom to top?

Where did you change the hardware acceleration?

any ideas why the feed rate changes to -20 when changing the rpd_typ_v7$ to 0? Feed rates are correct with it set to 1 but then I have the order problem...

Thanks, I'll do that... I have another issue though, the feed rate is now -20 in all drill cycles and never close to the feed rate typed into the tool path? I do not have the post to put a copy on the ftp but it's the mpheid.pst that came with ver 9 and again, this started with X4 install and up dating the post...

That seems to have fixed the problem, THANKS... I couldn't find anything in the post parameter reference to lead me to this? Is there other documentation that would help find these type issues?

We just lost a spindle on one of our new machines and I have to use an older Bridgeport with a Heidenhain TNC 151 control to get some work out this week. We haven,t used this machine much for the last few years so I had to import the post and create the machine and control definition in X4 (V9 post) but it's posting the drill cycles very weird? Using the debugger it's going through the pdrill cycle before the sof section of the post so I get my drill cycle before even getting a tool call, has any one else seen this? Do I need to update through every release? X4 doesn't come with any of the post examples like it did before so I don't have anything newer to compare? Looked on the ftp site but everything Heidenhain is foreign and I don't do foreign lanuages very well...

I'm doing something similar and wanting to know if there is a better way than what I'm doing below: #Misc. string definitions smat_name : "" smat1 : "STEEL inch - 1010 - 200 BHN" smat2 : "STEEL inch - 1030 - 200 BHN" smat3 : "STEEL inch - 303 STAINLESS" smat4 : "STEEL inch - 304 STAINLESS" smat5 : "STEEL inch - 4130 - 300 BHN" smat6 : "STEEL inch - 4140 - 400 BHN" etc... From code: if mr10$ = 0, [ if smat_name = smat1, mr10$ = .58 if smat_name = smat2, mr10$ = .67 if smat_name = smat3, mr10$ = .71 if smat_name = smat4, mr10$ = .79 if smat_name = smat5, mr10$ = .83 if smat_name = smat6, mr10$ = .87 etc... ] This way I can set mr10$ in the toolpath or let it get the multiplier from the post by leaving it at 0. From pparameter$ if prmcode$ = 20016, smat_name = (sparameter$) I wish I could retrieve the variable from User Def 1 in the material?