John: We don't change tools at the beginning of programs. Its always at the end of programs so when the program is executed the spindle starts instead of changing a tool. My old mpmaster post had this feature but anything I've tried with the new version just doesnt work. Terry: That wont work, ive tried and failed miserably with doing that. This is what happens when you remove ptlchg_com: code: % pmachineinfo$ pheader$ :2593 (T) pmachineinfo$ pheader$ (MCX FILE - 60409-101.MCX) pmachineinfo$ pheader$ (PROGRAM - T.65V) pmachineinfo$ pheader$ (DATE - OCT-25-2006) pmachineinfo$ pheader$ (T15 | 1-1/2 FINISHMILL .118 RAD | H13 | D63 | D1.5000) pwrtt$ pwrtt$ (T13 | 1 INCH MITS BXD .06 RAD | H13 | D63 | D1.0000) pwrtt$ pwrtt$ (T4 | 1/4 SPOTDRILL | H14 | D64 | D0.2500) pwrtt$ pwrtt$ Z.415 pzrapid$ prapidout M9 prapid$ p__65:1735 X-34.3878Y2.02M8 prapid$ prapidout It removes the 1st line of the tool and skips a bunch of stuff after that. This is my psof post block code: psof$ #Start of file for non-zero tool number ptravel pwritbuf5 pcuttype toolchng = one if ntools$ = one, [ #skip single tool outputs, stagetool must be on #stagetool = m_one !next_tool$ ] tooltotal = rbuf(4,0) #Reads total tool and null tool changes if toolcountn <= tooltotal, nexttool = rbuf(4,toolcountn) else, nexttool = first_tool$ if tool_table = 2, ppredstck,e$ if tool_table = 3, pmetastck,e$ spaces$=0 if output_z = yes$ & tcnt > 1, [ "(OVERALL MAX - ", *z_tmax, ")", e$ "(OVERALL MIN - ", *z_tmin, ")", e$ ] spaces$=sav_spc if plane$ < 0, plane$ = 0 #pbld, n, *sgcode, *sgplane, *smetric, "G40", "G80", *sgabsinc, e sav_absinc = absinc$ if wcstype <= one, #Work coordinate system [ absinc$ = one pfbld, n$, sgabsinc, "G28", "Z0.", e$ pfbld, n$, "G28", "X0.", "Y0.", e$ pfbld, n$, "G92", *xh$, *yh$, *zh$, e$ absinc$ = sav_absinc ] sav_mi9 = mi9$ sav_workofs = workofs$ if sav_workofs < 0, sav_workofs = 0 ptlchg_com sof=0 That is basic mpmaster psof code there. Im now thinking I need to add something to the ptlchg_com section that checks for beginning of program.

Hey guys, Im trying to remove the tool change at the beginning of my programs when I post out. I've sent the post to my reseller and he was at a loss as how to remove it. Im gonna post here hoping I can get some kind of help to get rid of this because I have to hand edit it out every time I post. code: % pmachineinfo$ pheader$ :2586 (T) pmachineinfo$ pheader$ (MCX FILE - 60405-101.MCX) pmachineinfo$ pheader$ (PROGRAM - T.65V) pmachineinfo$ pheader$ (DATE - OCT-24-2006) pmachineinfo$ pheader$ (T15 | 1-1/2 FINISHMILL .118 RAD | H15 | D65 | D1.5000) pwrtt$ pwrtt$ (T13 | 1 INCH MITS BXD .06 RAD | H16 | D66 | D1.0000) pwrtt$ pwrtt$ (T4 | 1/4 SPOTDRILL | H16 | D66 | D0.2500) pwrtt$ pwrtt$ N15T15M6(1-1/2 FINISHMILL .118 RAD) psof$ ptoolcomm (OKUMA & HOWA 65V) psof$ pcomment2 G0G90G54X-.3524Y-2.5713S984M3T13 psof$ ptlchg_com The N15T15M6 tool line needs to be changed. It needs to stay with the N code and tool comment but the toolchange needs to go. Everything i've tried so far has resulted in some crazy things happening (like tool changes in the middle of code). Im fairly certain I need some kind of if statement in the $psof part of the post but I dont know what it needs to function. This post is a modified mpmaster version x post. I am using mcamx 10.1.3.34 (mp1/sp2) lvl 3

quote: Hey Pete, How about sending Frank or Steve over to load that reseller copy? I second that, only you may have to drive..... a little bit more to load it here

We use 3 flute c-sink tools, 600rpm 10ipm and we use a dwell at the bottom of each. Our c-sink tools have pilots though so that may take out the chatter for us.

Thanks for the answers guys. I wish I could get step files from this guy but I know trying to get that to happen would make me pull the rest of my hair out. I just started using mcamx full time last month so I was trying to distance myself from 9 as much as possible. (weening is tough ) It is a work-around I could use though. Pete: Fair enough, id rather have correct surface data then wireframe geometry.

MLS: Your way worked to a point. It only imported some of the geometry?! /boggle Chris: Edge curves isnt an option on iges translations, but every option is checked on. I normally don't run the EA manager so no it wasn't turned on. I did turn it on for ***** and giggles and imported the same file and still no geometry besides the surfaces. I'm at a loss, until I can get some kind of answer as to what im missing I'll have to keep re-creating all my geometry

Im having some issues with converting files into mcamx. I can open an .iges file into mcam 9 and it has the splines, lines, and arcs on the surfaces. When I open the same file in mcamx all of the lines, arcs and splines are gone. I keep thinking im missing some setting in the config but I have every option checked on. What the heck am I missing?? It does the same thing when I try and import a Rhino 3d file and its driving me nuts having to recreate all this geometry. Using version 10.1.3.34 (mr1/sp2)

Thanks for the couple replies guys. My next question was gonna be how well does X handle operation importing. Looks like it hasn't changed

I've had this problem for so long I figure now that I have some time I will try and correct it. When I am programming a part I usually end up with 50~100 operations. Some use the same tool, some don't and sometimes due to process change I delete a tool from the list because it isnt being used anymore. The programs I make usually have an opposite. So I use mirror toolpaths as well. When I save my operations to an .op9 file, I export the geometry with the toolpaths and compress the library. Now comes the problem. When I try to import the toolpaths into my next part in the family my tool data gets lost on some tools. The toolpath and geometry (sometimes I dont import the geometry) import fine but on *some* tools they just dont import. Sometimes the operation that is imported will have a completely different tool in the tool list or the tool doesn't exist and was never imported with the toolpath and geometry. I've also tried to import toolpaths/geo/tools from an .mc9 file directly and the same problem pops up. The difference with importing operations directly from an .mc9 file is not only does it screw up my imported file it ALSO screws up the file I imported the data from I've tried everything I could possibly think of. I have exported each operation seperately and compressed the library for each operation. I have reinstalled mcam 9 I have tried all the disable/enable tool checking options and nothing seems to work and I am at a loss. The killer part is it doesn't do this on all the operations I import. Sooo anyone have a suggestion to try and fix this? This is for the lastest version of Mastercam 9

Wow thanks a bunch Roger. I will be sure to get this is in the post pronto.

Ouch.. I guess I'll have to try and setup a peck2 routine for it. I do have to use it *occasionally*, the majority of the time its straight rigid tapping but I would still like to have it setup now so I dont have to go back and get it. Thanks Charlie

Ive done a search and set up my post for rigid peck tapping. Problem is, the post always outputs the Q no matter if I have a peck set or not. I know there is a simple way to make it only show the Q command when I have it set in the operations page, I just cant find it. I tried putting a * in front of peck1$, it just isnt working and it keeps putting out Q0. if I dont enter anything in the peck field. ptap$ #Canned Tap Cycle pdrlcommonb #RH/LH based on spindle direction if use_pitch, pbld, n$, "G95", e$ if use_pitch = 0, [ n$, *sm05, e$ n$, "M29", *speed, e$ pcan1, pbld, n$, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout, *peck1$, prdrlout, *feed, strcantext, e$ ] This is my tapping cycle. The * added in front of peck1$ isnt working. Any ideas?

Im starting to work with mcamx but I do not like the mastercam editor. I tried to configure X to use Cimcoedit from version 9. (Pointed the settings editor to the cimcoedit folder in my mcam9 install) Now, whenever I post a program the system hangs and I have to hard reboot to get it to stop. Looking at the task manager I see cimco editor in the process list along with winlogon.exe and my system resources are pegged to max. Any ideas why this is happening Im using mcamX mr1 10.1.3.34 build date 1-6-2006 and no I do not have maintenance.

it doesnt have the toolpaths that you made dave

got it thanks a bunch

Dave is it possible to send me the file by email? The FTP site is down

I cant seem to access it. Is it down for maintenance?

Thanks for the help guys I appreciate it. Sorry I didnt respond Kannon I had left work right after I posted. Now if only the FTP site was up....

I uploaded a file Helppocket.zip to the mc9 directory on the ftp site. I tried this awhile ago with little success so I was wondering if I could get some help with this. I need to cut the pocket in the center of this part. The outside profile is already made so it takes a little of the work away. Im having a problem getting a surface toolpath to work in this with a 1/2 ballnose. I tried to use a parallel surface path but for some reason it stays away from the side walls about .03". Basically, I dont really know what toolpath to select to cut this and was wondering if I could get some help with this. Thanks in advance. I am using mcam 9.1mr0105.

quote: Toolpath Editor Based on user requests for editing capabilities similar to Version 9, the toolpath editor has been brought into Mastercam X. To access the function, right-click on the operation you wish to edit in the Toolpath Manager and choose Toolpath Editor. The functionality is the same as Version 9. No improvements?

I was very curious if open pockets were improved/fixed for X. Guess its not

I have only edited the right click menu to add a couple items (Done/Enter). Updated a couple posts. I havent had time to play with it yet so ive only used it sparingly for a couple weeks. edit: I did set my default editor to Cimco. I Doubt that has anything to do with this.

I have the same thing as Thad. I never had a demo or beta of X.

Yes! Thats what I was looking for Paul thanks a bunch