[CNCZART]

I've Been Running Mcamx For About 4 Months Now And Most Problems Are Straghtened Out Except One.
When I Post My G71 Canned Cycle I Get No Depth Of Cut.
I'm Using A Converted V9 Post That I Had Tweaked Nicely For My Machines But I Lost The Depth Of Cut When Going To Mcamx
Any Help???

[post_guy]

Here's some information I received on updating lathe posts for X, sounds like exactly what you are encountering... hope it helps:

Important information for updating Lathe posts for X:

The order of positional information in the Lathe NCI lines has changed in X. In earlier versions we output Z X Y and mapped the coordinates in the post, now we output X Y Z (just like in Mill). This change means we have to modify every lathe post to remove the mapping. The update post utility will automagically fix the mapping issue if the logic matches that found in MPLFAN, MPLGEN or MPL_EZ. Here’s what gets changed:

Modifications for Mill Turn posts (X lathe NCI change)

Version 9 (current)

map_home : yes #Use home positions as entered or map to machine axis

pmatrix_su #Setup mapping matrix
hmtx1 = matt(m1)
if cuttype <> one, hmtx1 = mmul(hmtx1, smtx1)
if cuttype = one, mmtx1 = matt(m1)
if cuttype = two, mmtx1 = matt(smtx1)
if cuttype = -2, mmtx1 = matt(bmtx1)
if cuttype = three | cuttype = five, mmtx1 = matt(cmtx1)
if cuttype = four, mmtx1 = matt(amtx1)
if cuttype <> one, mmtx1 = mmul(mmtx1, smtx1)

Version X (required)

map_home : yes #Use home positions as entered or map to machine axis

pmatrix_su #Setup mapping matrix
hmtx1 = matt(m1)
hmtx1 = mmul(hmtx1, smtx1)
if cuttype = one, mmtx1 = matt(m1)
if cuttype = two, mmtx1 = matt(smtx1)
if cuttype = -2, mmtx1 = matt(bmtx1)
if cuttype = three | cuttype = five, mmtx1 = matt(cmtx1)
if cuttype = four, mmtx1 = matt(amtx1)
mmtx1 = mmul(mmtx1, smtx1)

Modification to pmatrix_su for 2X lathe posts (mplgen and mpl_ez based)

pmatrix_su #Setup mapping matrix
# hmtx1 = matt(m1$)
# mmtx1 = matt(m1$)

In some cases, the cuttype variable is prefixed with c1_ so update post can not automatically fix it. You will need to make the following modification manually in these cases:

pmatrix_su #Setup mapping matrix
hmtx1 = matt(m1$)
#if c1_cuttype <> one, hmtx1 = mmul(hmtx1, smtx1) #No longer needed
hmtx1 = mmul(hmtx1, smtx1) #Replaced by this
if c1_cuttype = one, mmtx1 = matt(m1$)
if c1_cuttype = two, mmtx1 = matt(smtx1)
if c1_cuttype = -2,mmtx1 = matt(bmtx1)
if c1_cuttype = 3 | c1_cuttype = 5, mmtx1 = matt(cmtx1)
if c1_cuttype = 4, mmtx1 = matt(amtx1)
#if c1_cuttype <> one, mmtx1 = mmul(mmtx1, smtx1) #No longer needed
mmtx1 = mmul(mmtx1, smtx1) #Replaced by this

The second change in X deals with parameter values read by the posts. In earlier versions of Mastercam parameter values were sometimes reused in several toolpaths with a different meaning for each tool path, this lead to a lot of confusion. So, when we created X we had a developer spend a lot of time going through all of the parameters and had him reassign the shared parameters so each has a unique meaning. That’s not to say that they are no longer shared, just that if a parameter means one thing in one tool path, it will mean the same thing in another (if it is available for that toolpath).

The most common symptom of failure to update the parameter values used is faulty output in canned cycles, although other errors in code generation may also occur.

Unfortunately, there is no way for the update post c-hook to really determine if a number in a post is actually a parameter value or if it is being used for something else so we are forced to go through the posts manually to modify the values if needed.

With this in mind we put together the information contained in the MastercamX_Post_Parameter_Ref.pdf file that is included with the installation in the \mcamx\documents\ folder (you can also launch it from Start/All Programs/MastercamX/Documentation/. This file contains all of the parameters available at the time of release (it has since been updated for MR1/SP2). You can launch the .pdf, search for a parameter and see if it has changed pretty quickly (it usually only takes a few minutes to go through the values in the post). In most cases, the parameters are in lookup tables (especially if the post is MPLFAN or MPLGEN based).

Here is the section from Generic Fanuc 2X Lathe.pst (updated MPLGEN) and Generic Fanuc 4X MT_Lathe.pst (updated MPLFAN):
#--------------------------------------------------------------------------
# Parameter information lookup tables, see pparameter
#--------------------------------------------------------------------------
fprmtbl 1 5 #Rough cut parameters
13343 depthcc #Was 10200
10407 clearcc #Was 10201
10202 xstckcc
10203 zstckcc
10214 directcc

fprmtbl 2 4 #Finish cut parameters
13341 ncutscc #Was 10100
10101 depthcc
10102 xstckcc
10103 zstckcc

fprmtbl 3 5 #Groove cut parameters
13358 stepcc #Was 10301
13138 directcc #Was 10306
13352 dopeckcc #Was 10312
10316 depthcc
13364 clearcc #Was 10320

fprmtbl 104 4 #Thread cut parameters
10811 xmaj_thd #Was 10411
10813 zstrt_thd #Was 10413
10814 zend_thd #Was 10414
10819 face_thd #Was 10419

Chances are you may be able to cut and paste the above section right into your post. If you have any additional values in your parameter tables, look them up in the .pdf file mentioned above to see if they have changed.