We only got the standard Robodrill with a 14i control, I think it is a 1999. That little bugger just runs, I am not sure how many hours as I am sitting here at home, but I would have no problem recommending that machine, for what it is worth for you Elmo

John, Our machine is about 6 months old, everything is mounted by Methods on 2.5 x 2.5 tubing. Everything seems to be pretty rigid. I have only good things to say about the help I received from both Methods and Renishaw. One of our 1st. issues was that we had the thought when we bought the machine that we could rapid through the beam, decreasing toolbreakge checks from maybe 8 sec. (touch probe) to a couple of seconds with the laser. Renishaw was very helpful . Still toolbreakage is still a 6 sec. cycle. Then I started to play with checking wear and flutes on the cutters, and I did not find it that dependable, plus rather time consuming, I think that a spindle probe is more what I need on that machine. We just got a Haas with a Renishaw spindle probe, and I am playing with that one now, hoping to succeed to the point where I can justify the price for one on the Matsuura. I want to make clear that I am not trying to bash Renishaw, Methods or NC laser probes, the support I have gotten from these guy's have been awesome, but I think that I had this feeling that laser probes was the new sliced bread, James definitely have some good point where applications for a laser probe would be a huge benefit from a standard touch probe, but in our application we would properly have been just as happy with a touch probe and then added a spindle probe. Sorry this is becoming such a long post, I just have to attempt to make it clear that this was no other than my own fault and inexperience. I just do not want Elmo or anyone else to be all amazed that we now are using Reagans Starwars programs in our shops, and thinking that standard touch probes are old days talk. Lars

quote: I also prefer touch for tool breakage detection... Though... when you get down to small diameter tools >.060" , you don't always have a choice because the touch style can actually break these tools. That is very a good point quote: On another note, correct me if I'm wrong please, but don't MOST shops cut their graphite dry?? DOOHHH, I am a idiot , yes of course coolant would not be a problem. quote: laser gives you options for tool checking (broken/worn teeth, tool radius checks, form tool chacks, etc. Personally I have not have much luck with this (With Renishaws help)In cases where I tryed to check numbers of flutes and worn teeth I found it very inrelieble. I most say that our sensors are placed pretty far from each other, and I am sure that have a effect. As always James, damn good point from you

Please do not get fooled by the laser probe though, I have a NC4, and I would rather have had a touch probe. We thought it would be faster to check for broken tools, but that is not true. They have on Renishaws web-page where they are checking with coolant on, that is just a show. Lars

Alright, case solved

Sorry David I have no idea what you can do on that control. I guess you could set it up as a macro in the program where you keep variable #501 = 1 on one machine and zero on the other, and then in your program say something like. IF [#501EQ0]GOTO1 IF [#501EQ1]GOTO2 N1 MXX N2 MXX But that would meen your machine support macro's.

What kind of control is it?, if it is a fanuc it would be pretty easy. Just use parameter 6080 to 6089 to call a custom M code and call a sub program that have that specific code in it. HTH Lars

I am somewhat a Noob myself, but for starters backup your post. Then: Open up your post in a "Programmers File Editor" (Should be in you Mastercam directory), and search for "fastmode" change it to "no", then save it and post out a drill cycle. On the right side of your screen you should see where in your post the different lines gets called out like "pretract", then come back here and post your G-code and the part of your post that is used (like pretract). That would be a start. HTH Lars

All right I finally got it figured out, Wow I feel stupid it took this many attempts LOL Tim, I gave up trying to do multiple locations under one operation, before I ran into this problem, and that is perfectly fine, I can live with that. You got a point about that drl_prm = 9999 would be better if 0 is a output, but since these Renishaw probes got so many different letter variables that will end up being posted as zero’s I think that for at least now I will leave it at zero. Jim, Thanks for the lesson, it makes a whole lot more sense now, and prv_drl_prm1 worked like a charm. Acr1234, I have talked to Rich at Renishaw a couple of times in the past, he is a very helpful guy, thanks for the email, I will take a closer look at when I get the last couple of bugs out of my post. And of course James, John and Ron, thanks for all the support you guy’s always provide on this forum. Thanks Lars

Thanks Ron. I will try to get a good nights sleep, and give it a shoot in the morning. Lars

acr, According to my manuel 9810 is the macro for movement with protection, I looked through there and I do not have a 9022. I have not had a chance to run the probe at the machine yet, but I am trying to do the leg work before the machine is ready. quote: You probably should set these up just like a drill cycle where the first hole goes to pdrlcst1 and all subsequent holes in the cyle go to pdrlcst1_2. This allows you to have specific output when the first location is called and to have different output when each subsquent hole is output. that way when you hit another 3 point cycle, you can re-initialize the previous output variables or use some type of forced output. Jim, I think this makes sence to me , I am not sure though how I make the post use pdrlcst1 1st and then use pdrlcst1_2 on secondary operation. Is that a setting in the post? Tim, I tryed this code: pdrlcst #Custom drill cycles 8 - 19, additional points (user option) #Use this postblock to customize drilling cycles 8 - 19 #pdrlcommonb ####X-Y-Z Single Surface Measurement Cycle#### #if drillcyc = 9, pcan1, pbld, n, pxout, pyout, pzout, pcout, prdrlout, dwell, # feed, strcantext, e if drillcyc = 9, [ #sub_prg_call = peck1 pdrlcommonb pbld, n, "(X-Y-Z SINGLE MEASUREMENT)", e pbld, n, *sg00, *sgabsinc, e pbld, n, "G65 P9810", pfxout, pfyout, strcantext, "F200.", e pbld, n, "G65 P9810", prdrlout, "F200.", e pbld, n, "G65 P9811", pfzout, *peck1, e pcom_movea ] if drillcyc = 10, [ #sub_prg_call = peck1 pdrlcommonb pbld, n, "(3-POINT BORE MEASUREMENT)", e pbld, n, *sg00, *sgabsinc, e pbld, n, "G65 P9810", pfxout, pfyout, strcantext, "F200.", e pbld, n, "G65 P9810", prdrlout, "F200.", e pbld, n, "G65 P9810", pfzout, e pbld, n, "G65 P9823", drl_prm1, drl_prm2, drl_prm3, drl_prm4, peck1, drl_prm5, drl_prm6, drl_prm7, drl_prm8, drl_prm9, drl_prm10, e drl_prm1=0 drl_prm2=0 drl_prm3=0 drl_prm4=0 drl_prm5=0 drl_prm6=0 drl_prm7=0 drl_prm8=0 drl_prm9=0 drl_prm10=0 pcom_movea ] But it still gives me a N52 with out any varibele letters. Thank you Lars

quote: Where and how did you define those varaibles. Ron, I must admit that I just through them in there with out any verily order. code: # Start of probing coustom cycle-Lars -05-10-2007 #Contaning # 1) X-Y-Z Single surface measurement # 2) 3-Point bore measurement # 3) Feature-to-Feature #Variabelse in Mastercam #--------------------------------------- #Peck1 = H (Tolerance +/- #drl_prm1 #Costum Drill Parameter 1 - A #drl_prm2 #Costum Drill Parameter 1 - B #drl_prm3 #Costum Drill Parameter 1 - C #drl_prm4 #Costum Drill Parameter 1 - D #drl_prm5 #Costum Drill Parameter 1 - M #drl_prm6 #Costum Drill Parameter 1 - S #drl_prm7 #Costum Drill Parameter 1 - T #drl_prm8 #Costum Drill Parameter 1 - U #drl_prm9 #Costum Drill Parameter 1 - V #drl_prm10 #Costum Drill Parameter 1 - W #--------------------------------------- fmt A 2 drl_prm1 fmt B 2 drl_prm2 fmt C 2 drl_prm3 fmt D 2 drl_prm4 fmt M 2 drl_prm5 fmt S 2 drl_prm6 fmt T 2 drl_prm7 fmt U 2 drl_prm8 fmt V 2 drl_prm9 fmt W 2 drl_prm10 fmt L 2 mlars #pdrlcst #Custom drill cycles 8 - 19 (user option) #Use this postblock to customize drilling cycles 8 - 19 #pdrlcommonb #if drillcyc = 8, pcan1, pbld, n, *sgdrlref, *sgdrill, pxout, pyout, pfzout, pcout, # prdrlout, dwell, *feed, strcantext, e #if drillcyc = 8, #[ #sub_prg_call = peck1 #pcan1, pbld, n, *sg00, *sgabsinc, pfxout, pfyout, strcantext, e #pbld, n, "M98", *sub_prg_call, e #] #else, "CUSTOMIZABLE DRILL CYCLE ", pfxout, pfyout, pfzout, pfcout, e #pcom_movea pdrlcst_2 #Custom drill cycles 8 - 19, additional points (user option) #Use this postblock to customize drilling cycles 8 - 19 pdrlcommonb #if drillcyc = 8, pcan1, pbld, n, pxout, pyout, pzout, pcout, prdrlout, dwell, # feed, strcantext, e if drillcyc = 9, pbld, n, "(X-Y-Z SINGLE MEASUREMENT) [ #sub_prg_call = peck1 pbld, n, *sg00, *sgabsinc, e pbld, n, "G65 P9810", pfxout, pfyout, strcantext, "F200.", e pbld, n, "G65 P9810", prdrlout, "F200.", e pbld, n, "G65 P9811", pfzout, *peck1, e pcom_movea ] pdrlcst #Custom drill cycles 8 - 19, additional points (user option) #Use this postblock to customize drilling cycles 8 - 19 #pdrlcommonb ####X-Y-Z Single Surface Measurement Cycle#### #if drillcyc = 9, pcan1, pbld, n, pxout, pyout, pzout, pcout, prdrlout, dwell, # feed, strcantext, e if drillcyc = 9, [ #sub_prg_call = peck1 pdrlcommonb pbld, n, "(X-Y-Z SINGLE MEASUREMENT)", e pbld, n, *sg00, *sgabsinc, e pbld, n, "G65 P9810", pfxout, pfyout, strcantext, "F200.", e pbld, n, "G65 P9810", prdrlout, "F200.", e pbld, n, "G65 P9811", pfzout, *peck1, e pcom_movea ] if drillcyc = 10, [ #sub_prg_call = peck1 pdrlcommonb pbld, n, "(3-POINT BORE MEASUREMENT)", e pbld, n, *sg00, *sgabsinc, e pbld, n, "G65 P9810", pfxout, pfyout, strcantext, "F200.", e pbld, n, "G65 P9810", prdrlout, "F200.", e pbld, n, "G65 P9810", pfzout, e pbld, n, "G65 P9823", drl_prm1, drl_prm2, drl_prm3, drl_prm4, peck1, drl_prm5, drl_prm6, drl_prm7, drl_prm8, drl_prm9, drl_prm10, e pcom_movea ] pcanceldc #Cancel canned drill cycle result = newfs (three, zinc) z = initht if cuttype = one, prv_zia = initht + (rotdia/two) else, prv_zia = initht pxyzcout !zabs, !zinc prv_gcode = zero if cool_zmove = yes & (nextop=1003 | (nextop=1011 & t<>abs(nexttool))), coolant = zero pcan if drillcyc <> 8, pcan1, pbld, n, "G65 P9810", pfzout, "F200.", e if use_pitch & tapflg = 1, pbld, n, "G94", e pcan2 tapflg = 0 # ------------------------------ James, That is the 1st. time in all these years I have ever seen you use that Graemlins. Thanks guy's for always be so helpfull. Lars

James I did this: code: [ #sub_prg_call = peck1 pdrlcommonb pbld, n, "(3-POINT BORE MEASUREMENT)", e pbld, n, *sg00, *sgabsinc, e pbld, n, "G65 P9810", pfxout, pfyout, strcantext, "F200.", e pbld, n, "G65 P9810", prdrlout, "F200.", e pbld, n, "G65 P9810", pfzout, e pbld, n, "G65 P9823", !drl_prm1, !drl_prm2, !drl_prm3, !drl_prm4, !peck1, !drl_prm5, !drl_prm6, !drl_prm7, !drl_prm8, !drl_prm9, !drl_prm10, e pcom_movea ] And ended up with this : code: % pheader O0000 (NAME ME1) pheader (DATE - 14-05-07 TIME - 11:14) pheader (Machine: Renishaw Probe) pheader (Programmer: Lars Christensen) pheader N10 G00 G17 G20 G40 G49 G80 G90 psof (TOOL PROBETOOL - 41) psof ptoolcomm N12 G53 Z0. psof ptlchg_com N14 T41 M06 psof ptlchg_com N16 G65 P9832 psof ptlchg_com N18 G00 G90 G54 psof ptlchg_com N20 G65 P9810 X10. Y0. F200. psof ptlchg_com N22 G43 H41 Z10. psof ptlchg_com N24 G65 P9810 Z2. F200. psof ptlchg_com N26 (3-POINT BORE MEASUREMENT) pdrlcst p__70:1925 N28 G00 G90 pdrlcst p__70:1925 N30 G65 P9810 X10. Y0. F200. pdrlcst p__70:1925 N32 G65 P9810 Z.1 F200. pdrlcst p__70:1925 N34 G65 P9810 Z-.25 pdrlcst p__70:1925 N36 G65 P9823 pdrlcst p__70:1925 N38 G65 P9810 Z2. F200. pcanceldc N40 G65 P9810 X5. F200. ptlchg0 prapidout N42 (3-POINT BORE MEASUREMENT) pdrlcst p__70:1925 N44 G00 G90 pdrlcst p__70:1925 N46 G65 P9810 X5. Y0. F200. pdrlcst p__70:1925 N48 G65 P9810 Z.1 F200. pdrlcst p__70:1925 N50 G65 P9810 Z-.25 pdrlcst p__70:1925 Now I am missing the letter varibelse in both N36 and N52 Oops, I forgot to say this is for version 8 not version X if that matters , sorry Thank you Lars

Very cool PERRY, this is what makes this forum great. Thank you Lars

John you are a got damn genuis, here I have been thinking about this all weekend at home, LOL, thanks man. Now how about this one: code: % pheader O0000 (NAME ME1) pheader (DATE - 14-05-07 TIME - 10:35) pheader (Machine: Renishaw Probe) pheader (Programmer: Lars Christensen) pheader N10 G00 G17 G20 G40 G49 G80 G90 psof (TOOL PROBETOOL - 41) psof ptoolcomm N12 G53 Z0. psof ptlchg_com N14 T41 M06 psof ptlchg_com N16 G65 P9832 psof ptlchg_com N18 G00 G90 G54 psof ptlchg_com N20 G65 P9810 X10. Y0. F200. psof ptlchg_com N22 G43 H41 Z10. psof ptlchg_com N24 G65 P9810 Z2. F200. psof ptlchg_com N26 (3-POINT BORE MEASUREMENT) pdrlcst p__70:1925 N28 G00 G90 pdrlcst p__70:1925 N30 G65 P9810 X10. Y0. F200. pdrlcst p__70:1925 N32 G65 P9810 Z.1 F200. pdrlcst p__70:1925 N34 G65 P9810 Z-.25 pdrlcst p__70:1925 N36 G65 P9823 B120. C120. D1. pdrlcst p__70:1925 N38 G65 P9810 Z2. F200. pcanceldc N40 G65 P9810 X5. F200. ptlchg0 prapidout N42 (3-POINT BORE MEASUREMENT) pdrlcst p__70:1925 N44 G00 G90 pdrlcst p__70:1925 N46 G65 P9810 X5. Y0. F200. pdrlcst p__70:1925 N48 G65 P9810 Z.1 F200. pdrlcst p__70:1925 N50 G65 P9810 Z-.25 pdrlcst p__70:1925 N52 G65 P9823 pdrlcst p__70:1925 N54 G65 P9810 Z2. F200. pcanceldc N56 G65 P9833 peof pretract N58 G53 X0. Y0. peof N60 G90 peof N62 M30 peof % I do not get the B C and D value in line N52 as I have in line N36. Second hole location is created by taking the first hole location operation and copy it in operation manager and pick a new point. Thank you Lars

I have started to modify a MPmaster post for our 1st. Renishaw spindle probe, but I am running into a little headache when I come to the macro calls in my costum drill parameters, and am hoping someone can help me. This is what I got: code: [ #sub_prg_call = peck1 pdrlcommonb pbld, n, "(3-POINT BORE MEASUREMENT)", e pbld, n, *sg00, *sgabsinc, e pbld, n, "G65 P9810", pfxout, pfyout, strcantext, "F200.", e pbld, n, "G65 P9810", prdrlout, "F200.", e pbld, n, "G65 P9810", pfzout, e pbld, n, "G65 P9823", *drl_prm1, *drl_prm2, *drl_prm3, *drl_prm4, *peck1, *drl_prm5, *drl_prm6, *drl_prm7, *drl_prm8, *drl_prm9, *drl_prm10, e pcom_movea ] so I have set up all the drl_prm's for there respective macro letters, but sometimes you want the output to look like this: G65 P9823 A2. B2. C100 H.01 Other times you want it to look like this: G65 P9823 A2. C100 Z5. But what I get now is all the varibelse that are not used as zeros, like this: G65 P9823 A2. B0. C100 H0. Z5. Q0. K0. Do I make any sence?, I understand why they are reading zero, what I do not understand is how to write a "IF" statement that will not post drl_prm1 if it is reading zero in the costum drill parameter page in Mastercam. Thank you Lars

Techniks collet holders ER25 and 32 are rated up to 18000 rpm, they also makes a nice system when you want to use there collet chucks with through coolant tools, you just have to buy another nut amd a small washer, I have had good luck with techniks, I am running 3 machines with 1000 psi. Lars

You should be able to contact your local reseller.

Or maybe just call the machine builder and they can email you the macro, should not be a big problem. HTH Lars

I do not know how much this is going to help you, but I had to machine this stuff a couple of years ago, and started this thread. Link Good luck

Glad everything worked out for you. Do not be afraid to ask questions, that is what makes this forum so great.

edmBosto, I agree with everyone that you properly want to wait doing more testing til you get your guides replaced, you also might want to run a simple program like the one I posted where you do not use all those variables and sub programs, that way you can determine if is a machine issue or NC code. Your Z3 and Z4 should be in the 0.300 range. quote: The Z3 (after doing a mach. Z taper at 2.500 from upper cup to table) was within .0004 of the .814 height of block + .015 Shim + .7000 H91=1.529 for Z3 setting The actual Z3 when I ran the program was 1.5286. This do not seems right, these numbers added up, I believe your 0.3000 range from your Ztaper calibration should be in there. Keep us posted. Lars

I will not be back til tommorow, but maybe this will help you on your way. code: % (EDMBOSTO ) (DATE - 11-01-07 TIME - 09:24 ) (Machine: Mitsubishi FA) (Programmer: Lars Christensen) N100 G90 N102 Z1 = 0.81400 N104 Z2 = 0.40700 N110 Z5 = 0.00000 N112 G92 X0. Y0. N114 G00 X0. Y0. N116 M20 N118 M78 N120 M80 M82 M84 N122 E1231 F.120 N124 M90 N126 G88 N128 A-.25 N130 G01 G41 H1=0.00375 Y.15 N132 G03 X-.15 Y0. I0. J-.15 N134 X.15 I.15 J0. N136 X0. Y.15 I-.15 J0. N138 A0. N140 G01 G40 Y.12 N142 E1232 F.200 N144 M90 N146 G88 N148 A.25 N150 G01 G42 H1=0.00275 Y.15 N152 G02 X.15 Y0. I0. J-.15 N154 X-.15 I-.15 J0. N156 X0. Y.15 I.15 J0. N158 A0. N160 G01 G40 Y.12 N162 M21 N164 G00 X0. Y0. N166 M02 %

A Epack should not change your Z1 and Z4, I have no idea why these would change on you. Can you post your code here or email it to me.

I verily think it is prefrence, we use G92 but we do not use multiple setups, however if we did on a regular basis I would. For my case I never use G54 unless I am programing for our production, I always use G110, that way no one screws up my work cordinate, I have found that so many people are so focused on G54, that if I have a setup where I have used G54 and they need to jump into the machine , they start shaking when you tell them they have to pick another work cordinate. Sorry for rampling. Lars