Thad, Unless you also have .ops files in a seperate location you can configure it to go to the same files as your mcx files by changing the routing for ops files to mcx location. When you go to import it is trying to find your ops files and goes to the location you have that set for. I do agree though. that to have the option for either one would be good. To have it give you a choice to import from mcx or ops and to have it go to your default location based on that info.

but the question is were you corrupted then lost or were you lost before you became corrupted?

------------------------------------------------ The secretary's computer that spends 90% of the time writing reports, and other similar activities that's a good candidate for the first OS upgrade victim errrr I mean station. ----------------------------------------------- That's funny James. Last place I worked at had us using 400mhz computers while the secretaries had 1 gig+. We had probs on a daily basis with MC shutting down and everything taking 20+ minutes to regen. After I left they finally put some 1gig+ computers on the floor but only after the secretaries got 2gigs+. These were their hand-me-downs. What makes them think that a word processor needed that much computer compared to what we tried to do every day? go figure

just remember to have your red arrow where you want to paste it to.

Some people use "from tool" because they have large enough carousels to hold most of their tools and these tool #'s will never change. So they create their libraries to match what is in machine. You don't have to renumber tools except for the ones not in dedicated tool pots. Even then you could import your whole directory to begin with and then change to the "add tools sequentially" for any added tools to the program. I wish our carousels held enough so that we could dedicate tool #'s and offsets. I do still dedicate a certain amount of them and bring in my dedicated libray first and then add to it.

Thanks Roger. Will try that sometime today. It is obviously better now than it was. Again, many thanks.

Any time. I'm glad that I can contribute to this forum that has helped me so much.

Here is my tool comment section. ptoolcomment #Comment for tool tnote = t$ toffnote = tloffno$ tlngnote = tlngno$ ";", pstrtool, *tldia$, e$ pstrtool #Comment for tool if strtool$ <> sblank, [ strtool$ = ucase(strtool$) *strtool$, " " ]

Thanks again. That did delete most of the blank lines but I still am getting this. %01 G70 ; PROGRAM NAME - T ; DATE: 11-10-07 TIME: 08:49 N10 G99 T1 L0. R1.5 ;L___________R__________ ; 3" B52 FLY-CUTTER DIA. - 3. N20 G99 T2 L0. R.25 ;L___________R__________ ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 N30 G99 T7 L0. R.25 ;L___________R__________ ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 N40 G99 T3 L0. R.25 ;L___________R__________ ; 1/2"CHAMFER/SPOT E.M. DIA. - .5 N50 G99 T4 L0. R.1953 ;L___________R__________ ; 25/64" PARABOLIC DRILL DIA. - .390625 N60 G99 T5 L0. R.125 ;L___________R__________ ; 1/4" PARABOLIC DRILL DIA. - .25 N70 G99 T6 L0. R.125 ;L___________R__________ ; 1/4" 2 FL CARB '242' E.M. DIA. - .25 N80 G99 T8 L0. R.2 ;L___________R__________ ; .400 DIA. REAMER DIA. - .4 N90 G0 G40 G90 M25 I do expect there to be 2 lines of nothing in between callouts, but some of them are 12. 8 extra. I know it has to do with the amount of ops that tool is doing because the more ops the more spaces. Is there somewhere else that I should be looking.

Thank you. That got rid of the duplicates but now it has spaces where the duplicate comments used to be. So I have large gaps in between data.

I'm having trouble with the way my post is displaying the tool table for a bridgeport/heidehein vmc. The output is correct but it gives me multiple displays of the tools. It seems to display the tool for as many operations that tool does. ex. %01 G70 ; PROGRAM NAME - T ; DATE: 11-10-07 TIME: 06:40 N10 G99 T1 L0. R1.5 ;L___________R__________ ; 3" B52 FLY-CUTTER DIA. - 3. N20 G99 T2 L0. R.25 ;L___________R__________ ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 N30 G99 T7 L0. R.25 ;L___________R__________ ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 ; 1/2" DIA. 2 FLUTE CARB. E.M. DIA. - .5 N40 G99 T3 L0. R.25 ;L___________R__________ ; 1/2"CHAMFER/SPOT E.M. DIA. - .5 ; 1/2"CHAMFER/SPOT E.M. DIA. - .5 I would like to take out all of the duplicates. here is where it calls it in the post. pwrtt$ #Tooltable output if gcode$ = 1001, [ # "%", *sprogname, *smetric, e "%", *progno$, *smetric, e$ " ", e$ "; PROGRAM NAME - ", *sprogname$, e$ "; DATE: ", date$, " TIME: ", time$, e$ ] " ", e$ if t$ > 0, pbld, n$, "G99", *t$, *tool_length, *tlrad$, ";L___________R__________", e$ pbld, ptoolcomment, e$ " ", e$ any help would be much appreciated.

Sorry that is the auto one. I think it only works while your inserting something. The others are under the nc functions drop down menu.

There is an "auto insert spaces" button [x] next to the tool change search buttons. If that doesn't work it is in the drop down for nc functions.

you will also need to make sure you are using the correct file type. Go into setup, file types. and make sure you have the correct file type highlighted. then go to machines and set your tool change and tool load to what you are using. Ex. T for change, M6 for load.

go into your setup page under machine. make sure its looking for the right code for a tool change.

I use 1 file for eveything with the wcs. 1 file uses less memory and the wcs keeps files smaller also because your not having to copy your geometry. Plus this way you can verify all ops without having to save an stl. Again, less memory. Only time I split them is for huge files when the computer starts to bog down.

Ok, so I need to have at least a 10% overlap in the along. Thanks for the help. When you guys said you weren't having probs I kept plugging away at settings and finally got it to work correctly.

Sorry so long for getting back, was at lunch. I've tried alot of dif settings to get it to work. I would like it to be 20% across overlap with 0% along overlap. And then have a 2.0 inch approach and exit distance. When I set it the old way with rapid and 110% along overlap, 20% across, 0 approach and exit it works. But when I just change the rapid to linear it bombs out.

I'm having trouble with a facing op. It is not allowing me to use linear moves between cuts. It keeps giving me a "error creating the facing toolpath". It will work with rapids but not linear. Is anyone else having this prob?

sorry then. I thought it was supposed to be fixed with mr2. Maybe it wasn't until X3.

I think this was covered before and that it was going to be fixed for XP but not for windows 2000. I think it was because , if I remember right, X3 will not support windows 2000. We'll have to switch to XP. Correct me if I'm wrong.

Thanks Kannon for the ref. With understanding now how that worked I can change some other stuff that we had been hand editting for a long time. It really made me aware of how to understand alot more of the post than I did before. And thanks to the others that contributed to the referrenced materials.

Looking back I should probably add the fs2 18 and change the dwell callout to use 18 and change the fs11 back the way it was in case something else was using 11. Again Thanks

I couldn't get that to work so I went to the fs2 11 0.3 0.3 and took out the .'s. It now posts out correctly. Plus if I remember right, the machine wouldn't take a decimal for dwell anyways. I will save the this and try it later if needed. Thanks

Or how about making it to where none of my dwells have decimal points.