The book Andrew just mentioned is what made the macro programming thing make sense for me. It is a very good book. Also the white fanuc books that came with the machines will tell you about all the system variables. Almost anything is possible. Learning on the fanuc controls i have noticed that when your running the program say in single block, that you will see what value the machine is useing for a cerain variable. ex. say this is what you programmed #1=2.54 G1Z-#1F432. when you run this on a fanuc you will see in the program buffer this #1=2.54 G1Z-2.54F432. Mazaks and Yasnaks will look like this #1=2.54 G1Z-#1F432. If you know what value to expect it makes it easier to troubleshoot.

Here is one i made that works really well for us. 177.28 is the top of the block or whatever your using to set the hiegths off of. Get that number by touching a tool off the table, then using that tool to set the height of the setter. This one is for a Fanuc clone so double check the variables but i think they are the same. And you might need to add in a G53Z0 for retracts if M6 doesnt take you home. code: % O9111(TOOL SETTING ALL) (STARTS WITH TOOL IN SPINDLE) (TOUCHES TOOLS OFF IN ORDER) (AUTOMATICALLY GETS NEXT TOOL) (START IN AUTO, HIT CYCLE START) (HIT RESET WHEN DONE) G0G90G80G40G49G17 G56X0Y0(TOOL SETTING POS) #1=#4120(TOOL COUNTER) DO1 M6T#1(TOOL TO SET) #3006=1(JOG TO BLOCK) (BACK TO AUTO CYCLE START) #[11000+#4120]=[#5023-177.728](SETZ Z) #[12000+#4120]=0(SETS WEAR COMP TO 0) M6T[#4120+1] #1=[#1+1](TOOL STEP) END1 M30 %

stck_ht for Z in lathe stck_thck for diameter.

web page Yamazen is our dealer out here in Michigan. The control is a Fanuc clone. and ya they are super fast. the tool changes are pretty cool to see the first couple of times. code: G100G0G90G54.1P1XOYOA0Z50.G43H1D1M3S4000M8 All that happens simultaneously at 2362ipm

I will get some more info tonite for you Chris

We have a bunch of new Brother TS2A's. 30 taper, over 2000ipm rapids, 10000rpm spindles etc. they have g-code and conversational controls. There working out really good for us so far.

dont forget TA,1 to recieve and PU,2 to send from the fadal.

I made our Quest post from the MPLHT42SP.pst from the disk. There are already some Misc.int set up for using M98P1 and M98P2. Mi1 and Mi10 For the P1(main) and P3(live). for the subspindle i dont know yet code: prpm #Output for start spindle speed = speedrpm if posttype = two, pbld, n, *sg97, *spindle_l, *speed, "P1", pgear, e else, pbld, n, *sg97, *spindle_m, *speed, "P3", e

We had that happen when we put on a collet chuck after running a 8inch 3 jaw for a couple years on our Mazak SQT. I think it was the C-axis gain that needed turned down because the wieght difference between the two.

35 will post out the pound sign (#) in my nc code instead of commenting out the rest of the post block ascii [ 12-03-2003, 03:33 PM: Message edited by: try-on ]

still no luck yet. im using V8 code is coming out G43H1Z.1T2 #1=0 #2=1 G98G81X0.Y0.R.1Z#1F#2 M98P6556Q9901 G80 my blocks: code: pdrlcommonb #Canned Drill Cycle common call, before if sav_dgcode = 81, [ result = newfs (two, zinc) if drillcyc = three, drlgsel = fsg1(-ss) + drillcyc * two else, drlgsel = fsg2(dwell) + drillcyc * two if initht <> refht, drillref = zero else, drillref = one prv_refht_a = c9k prv_refht_i = c9k prv_dwell = zero ] if cuttype = three, sav_dgcode = gcode else, z = depth if cuttype = one, prv_zia = initht + (rotdia/two) else, prv_zia = initht pcom_moveb comment pcan #5 axis must map the true Z, correct Z calculation here if cuttype = three, [ prv_zia = zabs + (-depth) + initht zia = fmtrnd(zabs) zinc = zia - prv_zia ] if absinc = zero, [ no_z = zabs !zabs, !zinc ] else, [ no_z = zinc !zinc, !zabs ] no_f = feed pdrill #Canned Drill Cycle pdrlcommonb pbld, 35, "1=", *no_z, e pbld, 35, "2=", *no_f, e pcan1, pbld, n, *sgdrlref, *sgdrill, pfxout, pfyout, prdrlout, "Z", 35, "1", pcout, "F", 35, "2", dwell, strcantext, e pcom_movea

and for the M98P9000 before the next toolchange try this in your pretract section in you post pretract #End of tool path, "" "" pcan pbld, n, sccomp, *sm05, psub_end_mny, e pbld, n, "M98P9000", e #add it here etc

So far ive had no luck.. here are my fmt's and my pdrill block. Right now no_z is coming out as 0 and no_f is 1. fmt "" 4 no_z #variable z output fmt "" 4 no_f #variable f output pdrill #Canned Drill Cycle pdrlcommonb no_z = z no_f = feed pbld, 35, "1=", *no_z, e pbld, 35, "2=", *no_f, e pcan1, pbld, n, *sgdrlref, *sgdrill, pfxout, pfyout, prdrlout, "Z", 35, "1", pcout, "F", 35, "2", dwell, strcantext, e pcom_movea this is how this is working now. T1M6 G0G90G54X0.Y0.S2139M3 G43H1Z.1T2 #1=0(should be what pzout would be with no "Z") #2=1(should be what *feed would with no "F") G99G81X0.Y0.R.1Z#1F#2 M98P6556Q9901 G80

just in the drill cycles i need the Z and F surpressed. Its for our yasnaks,mazaks,brothers, and fanucs we use this format on all of our machines. Mainly because we use the same sub programs for our locations. ie. spot,drill,tap. If i can get our post to do this then ill just delete all the duplicate subs that you get when you use the subprogram option for drilling. Can mastercam know if it has just created more than one of the same subprograms and then get rid of the extra? [ 12-01-2003, 05:51 PM: Message edited by: try-on ]

good idea millman! sorry about that. Im just modifying the MPmaster I got the idea that doing something like this was even possible from this topic. (Variables as tool numbers)from last week or so. pdrill #Canned Drill Cycle pdrlcommonb pbld, 35, "1=", pzout, e pcan1, pbld, n, *sgdrlref, *sgdrill, pfxout, pfyout, "Z", 35, "1", pcout, prdrlout, dwell, *feed, strcantext, e pcom_movea this will post out like this #1=Z-1.0 G98G81X0Y0Z#1R.1F15. etc I need to strip the Z out of the variable statement.

Am i able to strip the X,Y or Z's from coming out of my code? Does it have something to do with this, (no2str) now ex #1=Z-1.0 need #1=-1.0 thanks

Thanks Jimmy and Dave. I made it like what Jimmy had except changed the one line to what Dave had, with the exception of having to add 9900 to the sub_prg_no thanks

I changed over my post to output local sub calls but dont like the numbering sceme. I would like my subs to start numbering from 9901 and up and not take the main program number into account? As it is now if my main is say O2000 then my subs will be named 11001,11002 etc. psub_call_s #Call to sub level #result = nwadrs(strp, sub_prg_no) sub_prg_no = sub_prg_no + sav_progno + 9000 #Add sub number offset if sav_progno = sub_prg_no, result = mprint(sprgnerror) pbld, n, "M98", *sub_prg_no, e sub_loc_call = sub_prg_no this is what calls it. i have added to and modified this to get my calls right(almost). TIA

wont a monitor from a Commadore 64 just plug right in? sorry

what rekd suggested is what i ended up doing. search for "job setup values in post" on the forum. G65P7 is my bar feed macro and G65P8 is my cutoff macro. I set a Misc Integer to 1 for a bar job and get P7 and P8 automatically were they need to be. when i define my stock the lower left corner is X0 and my part length. Top corner is Bar diameter and Z0 95 percent of the time everything posts out right. i added all this to my posts. # -------------------------------------------------------------------------- # Toolchange / NC output Variable Formats # -------------------------------------------------------------------------- fmt B 12 stck_thck #B for bar dia cutoff G65 fmt Z- 13 stck_ht #Z for G65 bump and cutoff # -------------------------------------------------------------------------- # Start of File and Toolchange Setup # -------------------------------------------------------------------------- pbstop # G65 bump stop "(T0101 FEED STOCK)", e "G65P7", stck_ht, e # thck=x, ht=z mr9=stck_ht mr8=stck_thck pcoff #G65 cutoff "(T0808 CUTOFF)", e "G65P8", mr8 ,"Z-", mr9, "S245", "F.002", e # lsof #Start of file for non-zero tool number, lathe if mi7=1, pbstop ltlchg peof #End of file for non-zero tool ptoolend comment if mi7=1, pcoff #G65 cutoff if m31_loop = zero, n, "M30" if m31_loop = one, n, "M31" mergesub clearsub mergeaux clearaux "%", e

spring semester.

Hey Thad is that Mr.K#$%@#. If so i know how you feel. I think most people i went to class with ended up thinking the software was crap. Ive been using it at work for a few years already. Once everyone found out i sort of knew what was going on it felt like i was actually teaching the class! He did tell us that he just learned it himself so maybe it will be better

i have to ride the bicycles at work all nite to.

i wish they would just go to the old Rotary rapid dial, then you know were your at by feel and keep your eyes in the machine.

[ 09-07-2003, 01:23 AM: Message edited by: try-on ]