First thing I do for any customer. Everyone has agreed much better to work with Mastercam turning that off. Sorry not seen your issue. I would make sure Windows update has not jacked up your Nivida settings.

Has all the unlock and lock commands for the axis been established? Has the tool been defined correctly on the Control? Is there code need to tell the machine it is turning mode and not milling mode?

Honesty I read this a few times and debated even responding. Both have seen the very problem you are facing along with myself and at some point someone has to decide they are going to rip off the band-aid. Either the company is movimng forward embracing the technology the way it has progressed(sorry I don't like the word evolved) to or die the slow death by a 1000 paper cuts it has been for such along time. Companies embracing the technology shift that has been coming for the last 10 years understand this fact. The shops that are busy and have work are those moving their processes and technology into the forefront. Those lagging and falling behind are just like a tree rotting the inside. That tree looks strong and tall until one day a limb falls off the the true problem starts to show. /that falling limb could be a run of bad parts, lost contract because of late delivery or have not put backup processes or methods in place. Then the next event happens and another limb falls off or the whole trunk collapses and then it gone. Put the safe guards in place and provide the training needed to make the process successful. Then don't look back and provide a process moving forward. Mistakes happen and until everyone is on board make a FAI part of every part run. No matter if they are just running 2-1000 parts. Easy to catch a problem on one part and a lot cheaper than realizing it after running 5-1000 parts. People might complain and gripe, but tell them the cost of scrapping a part is a three times cost loss. The original time, the replacement time and the lost time on the next part. The extra time spent making sure all possible problem have been sorted out until this is working as it should is time well spent.

Peck Tapping?

Not possible on a 4 Axis has to be done on a 5 Axis. Think of the tool always point to the Center of the 4th axis. With that shape will the tool always face to the center of the 4th axis and be able to cut that shape? From what I am seeing it requires a 5 Axis machine to cut it.

I see where you have pulled the value of variables with tabla de valores and then created the process to output them. Problem is are these are back to the Mastercam file before the NCI has been processed. You need to process certain things like you would for output of the NC code. Once you establish what the mathematical difference is then you will be able to map it like you want correctly. xout, yout, zout are all being processed using the MMD to take what you have programmed and converted through that matrix to output the code. You are pulling the raw data from Mastercam that has not really been processed for output like you are doing. The other thing I am seeing is you didn't pull the variables through pwrttparam$ or pparameter$, but pulled them raw. I am not sure or know enough to understand if pulling them from there helps align the output you are looking for, but when ever I have done what you are doing in the past I have always go through and defined everything there first then started working on getting output. It looks like they are pulled without running them through this process. Might try that and see if that is pushing everything through correctly to give the output you are looking for. Here is some of what I got with a post and stuff I added. This goes back 15 years ago so my memory is foggy. # -------------------------------------------------------------------------- # Machine definition and control definition parameter capture: # -------------------------------------------------------------------------- pparameter$ #Information from parameters #"pparameter", ~prmcode$, ~sparameter$, e$ #Brute Force Method for finding Vaules if opcode$=13 | opcode$=14, result = fprm (opcode$) if prmcode$ = 10000, stoper = sparameter$ if stoper=snull, stoper = snullop if prmcode$ = 15552, toolangle = rpar(sparameter$,1) if prmcode$ = 10005, tdia = rpar(sparameter$,1) # Tool Dia Milling if prmcode$ = 10006, tradius = rpar(sparameter$,1) # Tool Corner Radius Milling if prmcode$ = 10010, stock = rpar(sparameter$,1) # Stock to leave in Z Milling if prmcode$ = 10068, stock1 = rpar(sparameter$,1) # Stock to leave in XY Milling if prmcode$ = 10102, lfstockx = rpar(sparameter$,1) # Amount of Stock Left X Turning Finishing if prmcode$ = 10103, lfstockz = rpar(sparameter$,1) # Amount of Stock Left Z Turning Finishing if prmcode$ = 10202, lrstockx = rpar(sparameter$,1) # Amount of Stock Left X Turning Roughing if prmcode$ = 10203, lrstockz = rpar(sparameter$,1) # Amount of Stock Left Z Turning Roughing if prmcode$ = 13343, lrdepth = rpar(sparameter$,1) # Depth of Cut Lathe Roughing if prmcode$ = 10214, lathdir = rpar(sparameter$,1) # Direction 0=ID,1=OD,2=FACE,3=BACK Turning if prmcode$ = 12068, stock2 = rpar(sparameter$,1) # Stock to leave in Z facing Milling if prmcode$ = 10020, clearinc = rpar(sparameter$,1) # param 10020 is clearance now and 10021 indicates abs or inc if prmcode$ = 13359, lgrstockx = rpar(sparameter$,1) # Amount of Stock Left X Turning Groove Roughing if prmcode$ = 13360, lgrstockz = rpar(sparameter$,1) # Amount of Stock Left Z Turning Groove Roughing if prmcode$ = 10366, lgfstockx = rpar(sparameter$,1) # Amount of Stock Left X Turning Groove Finishing if prmcode$ = 10367, lgfstockz = rpar(sparameter$,1) # Amount of Stock Left Z Turning Groove Finsihing if prmcode$ = 10331, lgwidth = rpar(sparameter$,1) # Width of Groove if prmcode$ = 15100, clearflg = rpar(sparameter$,1) if prmcode$ = 15145, metvals = rpar(sparameter$,1) if prmcode$ = 15147, lturret = rpar(sparameter$,1) # Turret Being Used if prmcode$ = 15148, lspindle = rpar(sparameter$,1) # Spindle Being Used if prmcode$ = 15339, clearstrt = rpar(sparameter$,1) if prmcode$ = 15346, comp_type = rpar(sparameter$,1) #Cutter Compensaation Type (Lathe) if prmcode$ = 15347, comp_dir = rpar(sparameter$,1) #Cutter Comp Direction (Lathe and Mill) #if prmcode$ = 15182, miscvalon = rpar(sparameter$,1) if prmcode$ = 20010, sconstplname = ucase(sparameter$) if prmcode$ = 20011, sconstplcomm = ucase(sparameter$) if prmcode$ = 20012, stoolplname = ucase(sparameter$) if prmcode$ = 20013, stoolplcomm = ucase(sparameter$) if prmcode$ = 20014, swcsplname = ucase(sparameter$) if prmcode$ = 20015, swcsplcomm = ucase(sparameter$) if prmcode$ = 20016, smatlname1 = ucase(sparameter$) if prmcode$ = 20017, smatlname2 = ucase(sparameter$) if prmcode$ = 20018, stpgrpname = ucase(sparameter$) if prmcode$ = 20103, stinsert2 = sparameter$ if prmcode$ = 20110, stholder2 = sparameter$ #if prmcode$ = 20100, ltooltype = sparameter$ if prmcode$ = 12025, rotary_axis2 = rpar(sparameter$,1) #Capture the axis of rotation in Multiaxis Drill and Curve 5 Axis if prmcode$ = 15371, axissubdir = rpar(sparameter$,1) if prmcode$ = 12628, [ hst_flg = 1 hststyle = rpar(sparameter$,1) ] if prmcode$ = 20111, shape = rpar(sparameter$,15) if prmcode$ = 20008, head_x = rpar(sparameter$,9) # -------------------------------------------------------------------------- # NCI file pre-read look ahead routines # Build the toolchange buffer, sets cycle and turret flags # -------------------------------------------------------------------------- pwrttparam$ #Information from parameters if opcode$ = 104, result = fprm (opcode$) if prmcode$ = 20007, pilot_dia = rpar(sparameter$, 11) if prmcode$ = 10005, tdia = rpar(sparameter$,1) # Tool Dia Milling if prmcode$ = 10006, tradius = rpar(sparameter$,1) # Tool Corner Radius if prmcode$ = 10010, stock = rpar(sparameter$,1) # Stock to leave in Z Milling if prmcode$ = 10068, stock1 = rpar(sparameter$,1) # Stock to leave in XY Milling if prmcode$ = 10102, lfstockx = rpar(sparameter$,1) # Stock to leave in X Turning Finishing if prmcode$ = 10103, lfstockz = rpar(sparameter$,1) # Stock to leave in Z Turning Finishing if prmcode$ = 10202, lrstockx = rpar(sparameter$,1) # Stock to leave in X Turning Roughing if prmcode$ = 10203, lrstockz = rpar(sparameter$,1) # Stock to leave in Z Turning Roughing if prmcode$ = 13359, lgrstockx = rpar(sparameter$,1) # Amount of Stock Left X Turning Groove Roughing if prmcode$ = 13360, lgrstockz = rpar(sparameter$,1) # Amount of Stock Left Z Turning Groove Roughing if prmcode$ = 10366, lgfstockx = rpar(sparameter$,1) # Amount of Stock Left X Turning Groove Finishing if prmcode$ = 10367, lgfstockz = rpar(sparameter$,1) # Amount of Stock Left Z Turning Groove Finsihing if prmcode$ = 13343, lrdepth = rpar(sparameter$,1) # Depth of Cut Lathe Roughing if prmcode$ = 10331, lgwidth = rpar(sparameter$,1) # Width of Groove if prmcode$ = 10214, lathdir = rpar(sparameter$,1) # Direction 0=ID,1=OD,2=FACE,3=BACK Turning if prmcode$ = 12068, stock2 = rpar(sparameter$,1) # Stock to leave in Z facing if prmcode$ = 15145, metvals = rpar(sparameter$,1) if prmcode$ = 15346, comp_type = rpar(sparameter$,1) # Cutter Compension Type if prmcode$ = 15347, comp_dir = rpar(sparameter$,1) # Compenstion Direction if prmcode$ = 20103, stinsert2 = sparameter$ if prmcode$ = 20110, stholder2 = sparameter$ if prmcode$ = 20004, slot = rpar(sparameter$,16) if prmcode$ = 20006, cut_ability = rpar(sparameter$,8) if prmcode$ = 20007, pilot_dia = rpar(sparameter$,11) if prmcode$ = 12628, [ hst_flg = 1 hststyle = rpar(sparameter$,1) ]

Watch it someone might call you mean for saying such a thing. :0) (0:

Put together a Z2G with a sample part and then maybe someone can help you.

It might come down to the base WCS and the planes in question relationship to back to it. Might have to spin the Plane 180 degrees on Z to get the values you are expecting. NCI is matrix based as much as it is numerical based. Depending on the matrix what you see that doesn't make sense makes perfect since to the post because it is looking to the MMD to decipher the primary axis direction. With a properly configured post that has this setup to output G68.2 or CYCLE800 then we get the correct output when the planes are not sharing the same base point as the WCS. It sounds like that is what you are trying to accomplish is mapping of planes back a WCS that most post that support DWO already have built into them.

Sounds like you need to talk to your reseller to get this sorted out.

In the standard Generic 5 Axis posts for a Trunnion machine you will see this switch in mi9 called Nutating Bias. It should really say Primary Axis for trunnion machines. This is the control in that post.

Agreed, but the post process to address the issue is a dumbing down of the true capability of 5 Axis machining. I can think of only one of our 5 Axis customers using that for their programming process. After we teach them the power and benefits on their machines of using the different workoffsets and planes for programming they all agree extremely beneficially and it is quickly adopted. Again thank you for the videos and effort put to help Mastercam users.

This is where MP.DLL and a Post do their magic in Mastercam. Without access to both going to be hard to get what you need from the raw data. What is it that you are trying to accomplish?

Depending on the post and Machine Definition a couple different ways.

Dylan, thank you for the Video. I wish you would have touched on Work Offsets and setting them before using the linking and relative to process in the video.

No not you many have complained about this enhancement and have asked that the more user friendly method of contrast used by a majority of software companies be added back to the software.

Nope use the Interface and once built it carries all the way through into Vericut. 3D lathe tools are supported also.

Bill the inherit problem with assemblies is there not a process for externally supporting them. Yes it sucks having to build models for your assemblies to then make them holders, but I have found making them this way gives the ability to control their naming. By using the assembly process in Mastercam you have some major disconnects. You cannot mate them like you can in Lathe. 3D lathe for handing 3D tools is the way Mill Should work, but in it current state it is servery lacking in functionality and capability. That said I still build all my 3D lathe tools as models and not as components.

I am with Gcode on this. I never put any of the shanks into my tool definition. I always make them part of the holder definition.

Because it is a possible defect. I have always drawn my chains in situations like this. That way I get lead in and out at each cut. This is the biggest reason I have never used trim and will probably never use it. No intelligence built into the process. It is a dumb brick of a process. Take a look and let me know what you think.

After the latest things Autodesk has done I know of some customers getting away from CAMplete and heading into different CAV directions. Other long time customers being offered it are getting CAMplete with new machine purchases to post NC Cdoe, but will be using other CAV since they offer comparison of the NC code back to the machined models to check for excess and gouges that CAMplete doesn't offer. Do I expect a mass exodus of customers no, but CAMplete like other purchased AD companies isn't what is use to be.

I would use a Circle drawn from the center of the hole in the part and have it intersect the center of the pin. I would then use curve on edge near the one edge closest to the part. Then draw a line between the intersection of the edge back to the center and intersection of the arc to the pin back to the center. Measure the angle between them and I got 1.9486 degrees. Now rotate the part from the center of the hole the 1.9486 degrees. It will get you close, but not perfect. You need to intersect the tangential intersection of the pin with the one edge and on this example I was off .00208 from that perfect intersection. Now you could rotate the part back a little more until almost perfect, but when a best fitting process that adjust according to the tangential intersection would be best. I played with it using dynamic transform and using the adjust function on it to align he rotation process back to the intersection of the edge to the pin. I was able to adjust it backward .01 degrees and get it within .0002" of the tangential intersection. Some work, but that should get you close enough. Here is a screen shot showing the angle. and the file back with my attempt to make it as close as possible. I will remove this after 2 weeks and replaced with a link to my Dropbox account since we are limited to file sizes on this site.

What we have been saying. Machine sim by itself is not good for situations like this or transform operations. With a Post tied to it then much better, but when you get into transform operation all bets are off.

Reach out to Fives and see if someone can assist. https://www.fivesgroup.com/ Getting the correct understanding of the relationship of the W and Z will be very important to programming and running it correctly.

Yes because that logic was not added because it was not needed. Now you are needing this type of logic because you need the ability to pull the value after it was used.