What are the mi or mr process? are the in the post? thanks

Before i changed toolno = t$ * 100 + tloffno$ to toolno = t$ * 100 + t$ it would post T0900 instead of T09?? the last 2 digits are for the tool length. It would index to tool 9 but would have zero tool length offset toolno = t$ * 100 + t$ works if i want the same tool & length number, but some times i might need T0919 is it possible to use toolno = t$ * 100 + ( Len. offset) ?

on the #tool change mill it was toolno = t$ * 100 + tolffno$ but on my c-axis face drill the Dia offset is 0 and greyed out. i changed it to toolno = t$ * 100 + t$ then it posted T0909 is there any way to get dia offset un-greyed? Thanks

I couldn't figure out the above solution. I put " sg98 " into the canned drill cycle below and i seemed to work. mdrill$ #Canned drill cycle, mill pdrlcommonb pcan1, pbld, n$, *sgdrlref, pgdrlout, sg98, pxout, pyout, pzout, pcout, prdrlout, dwell$, pffr, strcantext, e$ pcom_movea My reseller said - without looking at the entire I can't say if there are anger conflicts but it looks good. what are anger conflicts? When I use canned drill cycle it outputs T0900 when i need T0909 the reseller said I needed to edit a math equation in the post would it be something like- toolno = t$ * 100 + zero Thanks

I have a fanuc 18i control and using- GENERIC FANUC 4X MT_LATHE.pst when i use C axis face drill the post outputs the feed in IPM and I need IPR also my "Dia offset 0" box is greyed in C-axis face drill out so when it post i get T0900 in stead of T0909 X7 mu2 puma TT2500SY fanuc 18i Thanks G0 T0900 G17 M35 M8 G0 G54 Z.25 X3.74 C180. G97 S3834 M33 G83 Z-.343 R.1 F15.34 C60. C300. G80 M9 G28 U0. H0. M35 G28 W0. H0. T0900

Thanks for the help I decided to change to MPFAN post and edit all the changes that i made in my old post ot MPFAN Pete

hello I replaced my, ptap$ #Canned Tap Cycle with ptap$ #Canned Tap Cycle pdrlcommonb result = newfs(17, feed) # Set for tapping Feedrate format if met_tool$, [ if toolismetric, pitch = n_tap_thds$ #Metric NC Code - Metric Tap else, pitch = (1/n_tap_thds$) * 25.4 #Metric NC Code - English Tap ] else, [ if toolismetric, pitch = n_tap_thds$ * (1/25.4) #English NC Code - Metric Tap else, pitch = 1/n_tap_thds$ #English NC Code - English Tap ] pitch = pitch * speed #Force Units Per Minute for regular Tap cycle pbld, n$, sg94, e$ pcan1, pbld, n$, *sgdrlref, *sgdrill, pxout, pyout, pfzout, pcout, prdrlout, *pitch, !feed, strcantext, e$ pcom_movea from MPFAN.pst this is what i got- G99G84Z-.5R.1 this is what i want G99G84Z-.5R.1S713F.0625 here are the errors 15 May 2014 10:27:13 AM - <0> - Report created. 15 May 2014 10:27:13 AM - <2> - Initialize posting log file 15 May 2014 10:27:13 AM - <2> - Using MP run version 16.00 and post components version 16.00 15 May 2014 10:27:13 AM - <2> - Initiate opening the post processor file(s). 15 May 2014 10:27:13 AM - <2> - C:\USERS\PUBLIC\DOCUMENTS\SHARED MCAMX7\MILL\POSTS\MITSUBISHI MELDAS 4 - AXIS HMC.PST 15 May 2014 10:27:13 AM - <2> - The post processor file has been successfully opened. 15 May 2014 10:27:13 AM - <2> - Post version information (input): 15 May 2014 10:27:13 AM - <2> - UPDATEPOST Version 16. was used to modify this file. 15 May 2014 10:27:13 AM - <2> - The file was modified by this product on 05 Sep 2013 13:37:32 15 May 2014 10:27:13 AM - <2> - The post was written to run with Mastercam Version 16. 15 May 2014 10:27:13 AM - <2> - The post product type is Mill. 15 May 2014 10:27:13 AM - <2> - Initialization of pre-defined post variables, strings, postblocks was successful. 15 May 2014 10:27:13 AM - <2> - Search for defined post variables, strings, postblocks was successful. 15 May 2014 10:27:13 AM - <2> - PST LINE (1124) - The formula/boolean failed (general message), , Label has not been defined[12] 15 May 2014 10:27:13 AM - <2> - PST LINE (1124) - The formula/boolean failed (general message) 15 May 2014 10:27:13 AM - <2> - PST LINE (1124) - The post block output type processing has failed!, , Label has not been defined[26] 15 May 2014 10:27:13 AM - <2> - PST LINE (1124) - The post block output type processing has failed!, , Label was expected but was not found[32], Illegal character(s) encountered 15 May 2014 10:27:13 AM - <2> - PST LINE (1125) - The post block output type processing has failed!, , Label has not been defined[15] 15 May 2014 10:27:13 AM - <2> - PST LINE (1125) - The post block output type processing has failed!, , Label was expected but was not found[21], Illegal character(s) encountered 15 May 2014 10:27:13 AM - <2> - PST LINE (1129) - The formula/boolean failed (general message), , Label has not been defined[12] 15 May 2014 10:27:13 AM - <2> - PST LINE (1129) - The formula/boolean failed (general message) 15 May 2014 10:27:13 AM - <2> - PST LINE (1129) - The post block output type processing has failed!, , Label has not been defined[26] 15 May 2014 10:27:13 AM - <2> - PST LINE (1129) - The post block output type processing has failed!, , Label was expected but was not found[32], Illegal character(s) encountered 15 May 2014 10:27:13 AM - <2> - PST LINE (1130) - The post block output type processing has failed!, , Label has not been defined[15] 15 May 2014 10:27:13 AM - <2> - PST LINE (1130) - The post block output type processing has failed!, , Label was expected but was not found[21], Illegal character(s) encountered 15 May 2014 10:27:13 AM - <2> - PST LINE (1132) - The post block output type processing has failed!, , Label has not been defined[7] 15 May 2014 10:27:13 AM - <2> - PST LINE (1132) - The post block output type processing has failed!, , Label was expected but was not found[13], Illegal character(s) encountered 15 May 2014 10:27:13 AM - <2> - PST LINE (1135) - The post block output type processing has failed!, , Label has not been defined[19] 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'dec_seq_right$' was re-initialized from 3. to 0. 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'arcoutput$' was re-initialized from 1. to 0. 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'arcoutputxz$' was re-initialized from 1. to 0. 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'arcoutputyz$' was re-initialized from 1. to 0. 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'larcoutput$' was re-initialized from 1. to 0. 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'larctypexz$' was re-initialized from 1. to 0. 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'larcoutputyz$' was re-initialized from 1. to 0. 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'arccheck$' was re-initialized from 1. to 111. 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'larccheck$' was re-initialized from 1. to 111. 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'rotfeed4$' was re-initialized from 2. to 1. 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'rotfeed5$' was re-initialized from 3. to 1. 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'lrotfeed4$' was re-initialized from 2. to 1. 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'lrotfeed5$' was re-initialized from 0. to 1. 15 May 2014 10:27:13 AM - <2> - CONTROL DEFINITION - Post variable 'peckacel$' was re-initialized from 0. to 1. 15 May 2014 10:27:13 AM - <2> - RUN TIME - PST(1129), NCI(100) - The math calculation/formula has an error 15 May 2014 10:27:13 AM - <2> - Successful completion of posting process!

Mitsubishi Medlas 4-axis HMC.pst

I can't find use_pitch in my post

I couldn't fine the switch " pitch_tap " in my post . is it possible to create a formula ( *feed / *speed ) = ipr

Hello I have a Medlas m3 control (Mitsubishi). On my post i need to output feed in Inches per revolution ptap$ #Canned Tap Cycle pdrlcommonb "M05", e$ pcan1, pbld, n$, *sgdrlref, *sgdrill, pxout, pyout, pfzout, pcout, prdrlout, *feed, *speed, strcantext, e$ pcom_movea I added the ( "m05", e$ ) line to stop the spindle which works but I need to change the feed form F44.57 to F.0625 (3/8-16 tap) G00G90G54X0.Y-8.886B90.S713M03 G43H203Z2.M08T123 M05 G98G84Z.787R1.5375F44.57S713 Thanks Pete X7 mu2

I am using a different machine def for each machine. I would have to rotate drawing 180 deg to machine the same side of a part in the opposite chuck . The problem i just had was on the left chuck machine, I had the stock defined, I had on lathe finish Home position (user defined) d10. z10., boring bar home d14.0 z8.0, Left upper all approaches and retracts at X.1 , machine default home x10. y5.0, and on Control def I had Tool Lathe , get position (home) from machine def. when the boring bar was done it retracted to z-.3512 and then straight up! then when i changed Lathe finish properties to home position -From Machine it retracts to z..03 if i change it back to Lathe finish properties- home position - user defined - it retracts to z.03 still??? I don't trust it at all I could default Lathe finish properties to check Ref Box and default retract x0, then remember to hit "From Machine" inside the Fef point box, which would but in x+.1 or x-.1 depending on left or right chuck. that way if i forgot the boring bars would retract to z0 at least. hope MC fixes this - 5 different places to put home position in- it could be simpler and safer! x7 mu2

I'm trying to get my boring bar to retract before going straight up (home). I have 3 lathes with left chucks and 1 with a right chuck. Have tried defining stock and setting ref points and that works MOST!! of the time. Is there any way to get the right chuck lathe to load a different operation default file automatically? Then I could have the ref point box checked and have approach and retract set to Z.1. every time I open a lathe opp. Then it wouldn't matter if i forgot to define the material or X7 decides it doesn't feel like it want's to retract . Thanks Pete

I found this change dia_mult from 2 to -2 in the post I am still trying to approch the part z first then x any one? Pete