Hello tjamscad, As mentioned above, we do have a post for this machine. We will send you a follow up e-mail from our generic post address ([email protected]) shortly to the e-mail you provided. Please let me know if you have any questions or did not receive the e-mail for some reason.

Hello, Does the version of your mpmaster have the Productivity Plus support added in? (Look in the revision log for "# IHS 01/10/14 - Added Productivity Plus, cml"). If you are not using the Renishaw probing with this post, you can pound out the line: force_tlchg$ : 0 #first operation marks input SOF as done, ASCII NCI toolchange Gcodes are not altered This should prevent the extra toolchange from occuring between depth cuts and multi-passes.

Hello, In the lathe retract postblock (pl_retract), look for the following line: pcan1, pbld, n$, *sg28ref, "U0.", [if y_axis_mch, "V0."], "W0.", strcantext, e$ and change it to this: pcan1, pbld, n$, *sg28ref, "U0.", strcantext, e$ pbld, n$, *sg28ref, [if y_axis_mch, "V0."], "W0.", e$

Yes, if the variable is missing from the post, you will have to add it. Without this variable being set, the post will not go to the pwrtt$ postblock to pre-read all the tools used.

The B should be tcr$ The W should be tldia$

Is the first tool used a flat endmill? There is an issue with the one string variable declaration. stp09 : "END MILL - FLAT" eventually will be "P9623" <-- There are too many quotation marks and characters outside the quotation marks. Change to something like this: stp09 : "END MILL - FLAT eventually will be P9623" OR stp09 : "END MILL - FLAT" #eventually will be "P9623"

Where are you calling stool_typ from and what post are you working with?

The variables in the string select table must be defined as strings. Try this: #tool type for tool length measurement stp00 : "CENTER DRILL" stp01 : "SPOT DRILL" stp02 : "DRILL" stp03 : "RIGHT HAND TAP" stp04 : "LEFT HAND TAP" stp05 : "REAMER" stp06 : "BORING BAR" stp07 : "COUNTER BAR" stp08 : "COUNTER SINK" stp09 : "END MILL - FLAT" eventually will be "P9623" stp10 : "END MILL - SPHERICAL" stp11 : "CHAMFER MILL" stp12 : "FACE MILL" stp13 : "SLOT MILL" stp14 : "RADIUS MILL" stp15 : "DOVETAIL MILL" stp16 : "TAPERED MILL" stp17 : "LOLLIPOP MILL" stp18 : "BULLNOSE" stype_tool : "" fstrsel stp00 type_tool stype_tool 19 -1 You can also use the variable tool_typ$ if you want so you do not have to read the parameter number.

Hello, You will have to make sure the following variable is enabled in the post for this to work. tooltable$ : 1 #Read for tool table and pwrtt This will allow the post to pre-read all the tools used in the pwrtt$ postblock where you will output from.

You should be able to change the rotation direction in the machine definition to get the opposite angle sign.

Have a look in this area which is used to switch strings based on the cuttype and axis combination #Machining position turret/spindle settings # Switch strings based on turret position top/bottom-left/right and cut type. # Turret position is based on the Mastercam settings (see lathtype). # Strings are re-assigned for output in the routine psw_str_mult. # The string variable sw_string holds the place position value to determine # how to assign the strings. Planes are relative to the view from Mastercam. # Assign the 17 digit string following the alpha columns below: # A - C axis, 1 = axis winds, 2 = axis signed, 3 = indexer # B - Spindle direction, 0 = normal, 1 = reverse # C - Plane 0 arc/comp, 0 = normal, 1 = switch # D - Plane 1 arc/comp, 0 = normal, 1 = switch # E - Plane 2 arc/comp, 0 = normal, 1 = switch # F - Plane 0, 0 = G17, 1 = G19, 2 = G18 # G - Plane 1, 0 = G17, 1 = G19, 2 = G18 # H - Plane 2, 0 = G17, 1 = G19, 2 = G18 # Decimal (required) # I - Plane 0, X axis, 0 = normal, 1 = switch sign from basic # J - Plane 0, Y axis, 0 = normal, 1 = switch sign from basic # K - Plane 0, Z axis, 0 = normal, 1 = switch sign from basic # L - Plane 1, X axis, 0 = normal, 1 = switch sign from basic # M - Plane 1, Y axis, 0 = normal, 1 = switch sign from basic # N - Plane 1, Z axis, 0 = normal, 1 = switch sign from basic # O - Plane 2, X axis, 0 = normal, 1 = switch sign from basic # P - Plane 2, Y axis, 0 = normal, 1 = switch sign from basic # Q - Plane 2, Z axis, 0 = normal, 1 = switch sign from basic use_only_tl : 0 #Use only Top turret/Left spindle settings (below) for #all Mastercam turret/spindle selections #When configuring for multi-spindle/turret set to 0 #Columns- ABCDEFGH.IJKLMNOPQ #Turret/Spindle #Path Type scase_tl_c1 : "10000222.000000000" #Top turret/Left spindle, Turning cut scase_tl_c2 : "10000012.000000000" #Top turret/Left spindle, Right Face cut scase_tl_c_2 : "10110012.000000000" #Top turret/Left spindle, Left Face cut scase_tl_c3 : "10010102.000000000" #Top turret/Left spindle, Cross cut (cuttype = 3) scase_tl_c3r : "10001102.000000000" #Top turret/Left spindle, Reverse Cross cut (cuttype = -3) scase_tl_c4c : "10000222.000000000" #Top turret/Left spindle, Y axis subs. Cycle scase_tl_c4 : "10000122.000000000" #Top turret/Left spindle, Y axis subs. scase_tl_c5 : "10000222.000000000" #Top turret/Left spindle, Multisurf Rotary #Columns- ABCDEFGH.IJKLMNOPQ scase_bl_c1 : "10000222.000000000" #Bottom turret/Left spindle, Turning cut scase_bl_c2 : "10000222.000000000" #Bottom turret/Left spindle, Right Face cut scase_bl_c_2 : "10110222.000000000" #Bottom turret/Left spindle, Left Face cut scase_bl_c3 : "10010222.000000000" #Bottom turret/Left spindle, Cross cut (cuttype = 3) scase_bl_c3r : "10010222.000000000" #Bottom turret/Left spindle, Reverse Cross cut (cuttype = -3) scase_bl_c4c : "10000222.000000000" #Bottom turret/Left spindle, Y axis subs. Cycle scase_bl_c4 : "10000222.000000000" #Bottom turret/Left spindle, Y axis subs. scase_bl_c5 : "10000222.000000000" #Bottom turret/Left spindle, Multisurf Rotary #Columns- ABCDEFGH.IJKLMNOPQ scase_tr_c1 : "10000222.000000000" #Top turret/Right spindle, Turning cut scase_tr_c2 : "10000012.000000000" #Top turret/Right spindle, Right Face cut scase_tr_c_2 : "10110012.000000000" #Top turret/Right spindle, Left Face cut scase_tr_c3 : "10010102.000000000" #Top turret/Right spindle, Cross cut (cuttype = 3) scase_tr_c3r : "10001102.000000000" #Top turret/Right spindle, Reverse Cross cut (cuttype = -3) scase_tr_c4c : "10000222.000000000" #Top turret/Right spindle, Y axis subs. Cycle scase_tr_c4 : "10000222.000000000" #Top turret/Right spindle, Y axis subs. scase_tr_c5 : "10000222.000000000" #Top turret/Right spindle, Multisurf Rotary #Columns- ABCDEFGH.IJKLMNOPQ scase_br_c1 : "10000222.000000000" #Bottom turret/Right spindle, Turning cut scase_br_c2 : "10000222.000000000" #Bottom turret/Right spindle, Right Face cut scase_br_c_2 : "10110222.000000000" #Bottom turret/Right spindle, Left Face cut scase_br_c3 : "10010222.000000000" #Bottom turret/Right spindle, Cross cut (cuttype = 3) scase_br_c3r : "10010222.000000000" #Bottom turret/Right spindle, Reverse Cross cut (cuttype = -3) scase_br_c4c : "10000222.000000000" #Bottom turret/Right spindle, Y axis subs. Cycle scase_br_c4 : "10000222.000000000" #Bottom turret/Right spindle, Y axis subs. scase_br_c5 : "10000222.000000000" #Bottom turret/Right spindle, Multisurf Rotary

Hello, If you are using mplmaster, you will have to change the string address for "cout_a" and "cabs" in "pfcout" and "pcout" as shown below. Original: pfcout #Force C axis output if spindle_no$ = 0, #main [ result = nwadrs(strc,cout_a) result = nwadrs(strh,cout_i) if millcc & g112address = 0, result = nwadrs(stry, cabs) if millcc & g112address = 1, result = nwadrs(strc, cabs) ] else, #sub [ result = nwadrs(stra,cout_a) <-------------------------------------------HERE if millcc & g112address = 0, result = nwadrs(stry, cabs) if millcc & g112address = 1, result = nwadrs(stra, cabs) <-------------------------------------------HERE ] Modified: pfcout #Force C axis output if spindle_no$ = 0, #main [ result = nwadrs(strc,cout_a) result = nwadrs(strh,cout_i) if millcc & g112address = 0, result = nwadrs(stry, cabs) if millcc & g112address = 1, result = nwadrs(strc, cabs) ] else, #sub [ result = nwadrs(strc,cout_a) <-------------------------------------------HERE if millcc & g112address = 0, result = nwadrs(stry, cabs) if millcc & g112address = 1, result = nwadrs(strc, cabs) <-------------------------------------------HERE ] HTH

Look for the variable omitseq$ in the post and make sure it is set to 1.

If you send the MCX file you are working with into [email protected], one of the developers will be able to look into this request for you.

I think the problem with line 449 is the "ah". This is not a Mastercam pre-defined variable and therefore needs to be initialized or calculated. Also, you cannont force out a postblock, you can only force out variables or strings. Normally we will use two different postblocks for this type of situation and call the desired one: Eg: n, *sgcode, pabs, pwcs, *xabs, *yabs, pfaout, *speed, *spdlon, prange, pcan, e Instead of: n, *sgcode, pabs, pwcs, *xabs, *yabs, *paout, *speed, *spdlon, prange, pcan, e Then have: paout # Calculate Output variables (Output only if it changes) aabs !xs, !aabs pfaout # Calculate Output variables (Force output) *aabs !xs, !aabs

You will also want to make sure that you import all or some of the pages from the settings for the other post location if you had made any changes from the default control definition settings. This is required because when you add a new post, it will automatically set everything to the default settings. Common changes are arc types, stage tooling, and NC file extensions. Also, make sure you reload the files into the MCX file before posting or the changes will not take effect.

Hello, We have Makino wire EDM posts available. If you contact your local Mastercam reseller, they will be able to get a quote for you on this post.

Hi Wes, Yes, we can normally open up those parts of the post for you to edit yourself. I just checked the Integrex posts of yours we have on file and it appears that the Mark III and e-series versions you have should have those sections available. The Mark IV seems to be the only one that has those parts locked up. If you send a request into [email protected], we will be able to send you a new copy with the sections you would like available. - Stephen

Do you have "allow 360 degree arcs" selected for all planes? This has to be enabled or the moves will still be broken up. The moves are genereated in the NCI file and the post does not modify them at all.

As some members have mentioned, we do have good posts for the Integrex machines. Our posts will support both upper and lower turrets as well as simultaneous 5-axis toolpaths and polar conversion with C-axis toolpaths. We are also able to completly customize the post to your needs to produce edit free code. We also have many Mori Seiki posts available in our library.