What is a .dat file and how can I creat one?

zoey, best way that I have found is to make sure that you have your tool identified correctly in your tool parameters page. Then use "computer" for your offset. I don't have any probs with chamfers doing it this way.

But they aren't un-ghosting that I know of. They are still ghosted after posting.

Alot of times when I transform - rotate toolpaths and have "copy source ops" and "disable posting in selected source operations" checked, it still posts the original ops. Does anybody else have this problem? It doesn't happen all the time. Seems like it's finicky (sp) on when it does and when it doesn't.

Thanks. Will give it a try again.

I'm with JP here. Import a step (.stp) file instead.

I was with toolman184, but after reading this I am going to have to learn how to use the stl files. I tried once but the stl didn't look anything like it was supposed to when I brought it back up. So I haven't tried it since. What is the proper way to save these, and how do you use them if it needs to be rotated for other ops?

When I have this problem it is usually after importing an Autocad file. Don't know how to get rid of them. I don't get them though if I import a Step file.

Neurosis, I used to run smartcam that could do the same thing in chaining. Prob is is that the other programmers would not check to see which line they were grabbing and parts would get scrapped because of it. If you have a tapered wall - which all molds do - and the programmer picked the top of one side of a pocket and the bottom of the other side the pocket/part would be scrap. This way of chaining is by far safer and less confusing. When I first started there - before I became programmer - I would spend 4-6 hours a day trying to figure out where the programmers went wrong and it was the top/bottom geometry thing in their chaining. Then I would get yelled at about what I did all night (night shift). I would leave a book for the programmers about what was wrong.

Instead of the stepover amount, leave more stock on walls instead.

Cool Mike-T. Neurosis, try using a step file or a sat file instead of an iges file. They are better models to use than iges - less mistakes with model.

Thanks nils and thad. Will give it a try when I get a chance.

ah. so it's a windows thing.

I have specific folders for customers and then specific folders for each job all on a server. It doesn't always go to the folder that I need it to. and then I'm having to go thru all the folders to get to the one I need. After I've posted one pgm for a specific folder it will go to that folder for the second one but rarely the first.

Thanks John. I had tried alot of things but nothing worked. It looked like you should be able to add shortcuts there. It would simplify things if you could.

When you post a pgm and the "save as" page comes up, is there a way to add a folder to the shortcuts on the left. I have tried to drag one to the area but it didn't take.

Do you have the same geometry at a dif depth under the top one. I find when I have this prob it is picking the bottom geometry.

bump

sorry , I had a value wrong in my example. the n150 was wrong in what it needed to output. my bad.

I have a Bridgeport Interact 1 with a Heidenhain TNC151 control. I am having probs in regard to drilling planes that are not at Z0. I need to drill holes with these Mastercam parameters set in peck drilling cycle clearance 1. abs retract .1 inc top of stock -.19 abs depth -.5 abs I am running the control in ISO (gcode) mode. We have hundreds of pgm's made this way so conversational is not an option. the code is coming out like this N140 Z1. M8 N150 Z-.09 N160 G83 P01 .09 P02 -.5 P03- .157 P04 0. P05 120 N170 G79 this doesn't work at all. it alarms out. it should look like this. N140 Z1. M8 N150 Z-.09 N160 G83 P01 -.1 P02 -.31 P03- .157 P04 0. P05 120 N170 G79 This is what my post looks like # -------------------------------------------------------------------------- # Drilling # -------------------------------------------------------------------------- pdrill0$ #Pre-process before drill call sav_dgcode = gcode$ #Capture gcode for 5 axis drill pdrlcommonb #Canned Drill Cycle common call, before if sav_dgcode = 81, [ result = newfs (two, zinc) if drillcyc$ = three, drlgsel = fsg1(-ss$) + drillcyc$ * two else, drlgsel = fsg2(dwell$) + drillcyc$ * two if initht$ <> refht$, drillref = zero else, drillref = one prv_refht_a = c9k prv_refht_i = c9k prv_dwell$ = zero ] if cuttype = three, sav_dgcode = gcode$ else, z$ = depth$ if cuttype = one, prv_zia = initht$ + (rotdia$/two) else, prv_zia = initht$ pcom_moveb feed = fr_pos$ comment$ pcan #5 axis must map the true Z, correct Z calculation here if cuttype = three, [ prv_zia = zabs + (-depth$) + initht$ zia = fmtrnd(zabs) zinc = zia - prv_zia ] prdrlout #R drill position if cuttype = one, refht_a = refht$ + (rotdia$ / two) else, refht_a = refht$* -1 refht_i = refht$ - initht$ if cuttype = three, refht_a = w$ if absinc$ = zero, refht_a, !refht_i else, refht_i, !refht_a pdrill$ #Canned Drill Cycle feed = feed * 10 pdrlcommonb pcan1, pbld, n$, *sgdrill, pxout, pyout, pfzout, pcout, prdrlout, dwell$, *feed, strcantext, e$ pcom_movea ppeck$ #Canned Peck Drill Cycle pdrlcommonb result = nwadrs(sp01,refht_a) result = nwadrs(sp01,refht_i) result = nwadrs(sp02,zabs) result = nwadrs(sp02,zinc) result = nwadrs(sp03,peck1$) result = nwadrs(sp04,dwell$) result = nwadrs(sp05,feed) feed = feed * 10 pcan1, pbld, n$, *sgdrill, pxout, pyout, prdrlout, pfzout, pcout, *peck1$, *dwell$, *feed, strcantext, e$ pcom_movea pchpbrk$ #Canned Chip Break Cycle pdrlcommonb feed = feed * 10 pcan1, pbld, n$, *sgdrill, pxout, pyout, pfzout, pcout, prdrlout, *peck1$, *feed, strcantext, e$ pcom_movea ptap$ #Canned Tap Cycle pdrlcommonb result = nwadrs(sp01,refht_a) result = nwadrs(sp01,refht_i) result = nwadrs(sp02,zabs) result = nwadrs(sp02,zinc) result = nwadrs(sp06,dwell$) result = nwadrs(sp04,feed) feed = feed * 10 pcan1, pbld, n$, *sgdrill, pxout, pyout, prdrlout, pfzout, pcout, *dwell$, *feed, strcantext, e$ pcom_movea pbore1$ #Canned Bore #1 Cycle pdrlcommonb feed = feed * 10 pcan1, pbld, n$, *sgdrill, pxout, pyout, pfzout, pcout, prdrlout, dwell$, *feed, strcantext, e$ pcom_movea pbore2$ #Canned Bore #2 Cycle pdrlcommonb feed = feed * 10 pcan1, pbld, n$, *sgdrill, pxout, pyout, pfzout, pcout, prdrlout, *feed, strcantext, e$ pcom_movea pmisc1$ #Canned Misc #1 Cycle pdrlcommonb feed = feed * 10 pcan1, pbld, n$, *sgdrill, pxout, pyout, pfzout, pcout, prdrlout, shftdrl$, dwell$, *feed, strcantext, e$ pcom_movea pmisc2$ #Canned Misc #2 Cycle (User Option) pdrill$ pdrill_2$ #Canned Drill Cycle, additional points pdrlcommonb n$, "G79",e$ feed = feed * 10 pcan1, pbld, n$, pxout, pyout, pzout, pcout, prdrlout, dwell$, feed, strcantext, e$ pcom_movea ppeck_2$ #Canned Peck Drill Cycle pdrill_2$ pchpbrk_2$ #Canned Chip Break Cycle pdrill_2$ ptap_2$ #Canned Tap Cycle pdrill_2$ pbore1_2$ #Canned Bore #1 Cycle pdrill_2$ pbore2_2$ #Canned Bore #2 Cycle pdrill_2$ pmisc1_2$ #Canned Misc #1 Cycle pdrill_2$ pmisc2_2$ #Canned Misc #2 Cycle pdrill_2$ pdrlcst$ #Custom drill cycles 8 - 19 (user option) #Use this postblock to customize drilling cycles 8 - 19 pdrlcommonb "CUSTOMIZABLE DRILL CYCLE ", pfxout, pfyout, pfzout, pfcout, e$ pcom_movea pdrlcst_2$ #Custom drill cycles 8 - 19, additional points (user option) #Use this postblock to customize drilling cycles 8 - 19 pdrlcommonb "CUSTOMIZABLE DRILL CYCLE ", pfxout, pfyout, pfzout, pfcout, e$ pcom_movea pcanceldc$ #Cancel canned drill cycle result = newfs (three, zinc) z$ = initht$ if cuttype = one, prv_zia = initht$ + (rotdia$/two) else, prv_zia = initht$ pxyzcout !zabs, !zinc prv_gcode$ = zero pbld, n$, "G79", e$ result = nwadrs(strz,zabs) result = nwadrs(strz,zinc) result = nwadrs(strp,dwell$) result = nwadrs(strf,feed) can someone help me with this. I know that it has to do with the top of surface plane and how eveything is calculated from there. In the past we have always drilled from z0 to fix this but we've had holes that needed to be drilled from -1. and that's alot of wasted time. It didn't help that I just now had the chance to experiment with the control and figure out what the correct output needed to be. I never touched this machine until now. editted [ 12-19-2007, 12:43 PM: Message edited by: doyleg ]

oh yea. by the way. if you use g92, your g54 is offset the amount in the offset from the g92 position, not home. so I would zero out all work offsets if your using g92.

with the o-m control. make sure there isn't a value in the no.0 shift. this is a shift co-ordinate that will shift every work offset the amount that is in it. It will be the workoffset in upper left corner of your work offset page.

CAN YOU DIG IT !!!!!!! great work. Been wanting this drag and drop for awhile.

if you can't get the right code to output, see what the axis callouts are and rotate your toolpath with transform toolpath. i was able to do this until my post was fixed to give me the correct output.

if the tolerance isn't too bad we use an electronic edge finder. if its tight, I still do the old trusty way. I sweep a known bore gauge, then pick up the side of the part and offset half of the bore gauges dia.