Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:

Brad Lisle

Verified Members
  • Posts

    242
  • Joined

  • Last visited

1 Follower

About Brad Lisle

  • Birthday 12/14/1978

Profile Information

  • Gender
    Male

Uncategorized

  • Location
    Cornelius, OR

Recent Profile Visitors

2,352 profile views

Brad Lisle's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

77

Reputation

  1. This is the code I like to use for setting up Hi-Cut in my posts. Code below uses mi4$ as a toggle to output on. mr1$-mi3$ are for extended commands within the G131 line. Enjoy, Brad Lisle # -------------------------------------------------------------------------- # G131 Hi-Cut (mi4$) # -------------------------------------------------------------------------- sg130 : "G130" #Hi-CUT output string for G131 cancel sg131 : "G131" #Hi-CUT output string for G131 initiate hicut_on : no$ #flag for hicut on op_changed : no$ #flag for op_id$ change at null tool fmt "F" 2 g131f #'F' Hi-CUT Feedrate Upper Limit (mr1$) fmt "J" 4 g131j #'J' Hi-CUT Machining Mode (mr2$) fmt "E" 2 g131e #'E' Hi-CUT Machining Tolerance (mr3$) phicut_on hicut_on = no$ if mi4$ >= 1, [ phg131_out hicut_on = yes$ ] !hicut_on, !g131f, !g131j, !g131e pnull_hicut #"***", ~op_id$, prv_op_id$, "***", e$ if op_changed, [ if mi4$ >= 1, hicut_on = yes$ else, hicut_on = no$ if (hicut_on = no$ & prv_hicut_on = yes$), [ pbld, n$, sg130, e$ prv_gcode$ = -1 ] else, [ if hicut_on = yes$ & prv_hicut_on = yes$, [ #pbld, n$, sg130, e$ if prv_g131f <> mr1$ | prv_g131j <> mr2$ | prv_g131e <> mr3$, phg131_out prv_gcode$ = -1 ] else, [ if prv_hicut_on = no$ & hicut_on = yes$, [ phg131_out prv_gcode$ = -1 ] ] ] ] !hicut_on, !g131f, !g131j, !g131e phg131_out g131f = mr1$ if g131f <= 0, g131f = 1260 g131j = mr2$ if g131j > 2, g131j = 2 if g131j < 1, g131j = 1 g131e = mr3$ if g131e <= 0, g131e = 0.002 pbld, n$, *sg131, *g131f, *g131j, *g131e, e$ phicut_off if hicut_on, pbld, n$, sg130, e$ psof$ #only if first tool change is in psof$ phicut_on #after toolchange call, before cut moves !mi4$, !mi5$, !mi6$, !mi7$, !op_id$ #at end of post block ptlchg$ phicut_on #after toolchange call, before cut moves !mi4$, !op_id$ #at end of post block ptlchg0$ pnull_hicut #before cut moves !mi4$ #at end of post block pretract phicut_off #after initial retract, before home movement or tool breakage check
  2. @JeremyV, Where are you located? If you are having a hard time getting training from your local Okuma distributor I would highly consider Ron (@crazy^millman) for training. He could help with the machine and MasterCam side of things. He is a great resource as well as a great guy all around. Brad Lisle
  3. Does anyone know how to get the tool cut time? and total cycle time? Thanks, Brad
  4. I can see a couple of issues here. First off you may not be probing on the outer tangency of the sphere, thus the radius measured will not be the true radius of said sphere. By shifting the measured radius you will not be in the true center of the sphere. If the sphere is always a known value, you could probe outside to find center, probe top, then probe outside again to center taking into consideration for the stylus radius. Here is the code: NPRB1 (ASSUMING X0. Y0. Z0. IS CENTER OF SPHERE) (ASSUMING 1.0 SPHERICAL DIAMETER) (ASSUMING 6MM STYLUS TIP) T99 M06 G15 H1 G00 X0. Y0. M05 G56 HA Z2. M09 CALL O9832 (PROBE ON) CALL O9810 PZ=.6 PF=100. (SAFE MOVE) CALL O9814 PD=1. PZ=-.1181 (MEASURE BOSS DIAMETER) VC1=VS75 (LOG MEASURED X POSITION) VC2=VS76 (LOG MEASURED Y POSITION) CALL O9810 PX=VC1 PY=VC2 (MOVE TO TRUE CENTER) CALL O9811 PZ=.5 (MEASURE TOP OF SPHERE) VC3=VS77 (LOG MEASURED Z POSITION) CALL O9810 PX=VC1 PY=VC2 (MOVE TO TRUE CENTER) CALL O9814 PD=1. PZ=-.1181 (MEASURE BOSS DIAMETER) VC4=VS78 (LOG MEASURED DIAMETER) CALL O9810 PZ=2. PF=300. (SAFE RETRACT) CALL O9833 (PROBE OFF) VC5=VC3-[VC4/2] (CALCULATE TO CENTER OF SPHERE) G11 Z=VC5 (PARALLEL SHIFT OF COORDINATE SYSTEM) M01 RUN TOOLS BELOW ... ... G10 (CANCEL G11 SHIFT) (NOTE: RESET WILL ALSO CLEAR THE G11 SHIFT) M30
  5. Please be more specific. Is this for a mill or lathe with milling capabilities? Do you need multiple passes or just a single contour pass? Any other specifics you are looking for this macro to accomplish? Brad
  6. @PcRobotic Would you mind sharing how you got the Z min correct in the tool table? I have been having issues getting the correct output. Almost there and yet still far away. Thank you in advance, Brad
  7. You can have it at the header for each offset you want to use or at each rotation output. Either way works fine as long as you call up the correct work offset numbers. I personally like them at the header. The CALL OO88 is just a calculation tool, therefore there is no mode that needs to be cancel ed. When you change work offsets it will effectively cancel the previous offset. As you can see in Greg's sample code the post is setup to always use the same temporary offset #51 and always references offset #1. Using this format you must have it at every rotation to recalculate every time and it also calls up the temp offset #51 to be active. I have my post setup to program using different work offset numbers for various tool planes. Similar to other posts that do not use "CALL OO88" and outputs a different offset for each rotation. Using this method you only need the CALL OO88 statement only once and it can be anywhere before the offset is called, IE... beginning of program. Just make sure you always call up the active work offsets.
  8. Gosiger has some of the best Applications Engineers and Service Techs on the west coast. There are quite a few great machines to choose from, but service and tech support are key. I'll put my vote in for an Okuma Multus.
  9. Awesome, thank you. I already tried contour and could not find ramp option it only had 2D, 3D or 3D chamfer. I must have selected a bad chain. Got it done finally. It was driving me nuts!
  10. No kidding, That is a 393.7" table with a max swing of 629.9". Can you imagine the distance between columns? I wouldn't trust the rigidity of it with that much spread. Although admittedly I have not seen pictures of it. An FPT Industries Vertigo with a 374.0" (9.5 meter) table only has a max swing of 472.4" (12 meter)
  11. I must have had to much coffee this morning because I cannot think for the life of me. I am trying to do a Helix bore toolpath on an OD. I know I have done this toolpath a few times before but my mind is going a million miles per hour today and I can't get what I want. Simply want to select on an OD arc and tell it to use a highfeed mill to spiral ramp down to a desired Z depth without selecting surfaces. Thank you
  12. These are a great option. I have had great success with the Lyndex SK series holders.
  13. That is the wonderful thing about our industry, every part is it's own unique part and faces it's own unique challenges. I do not see how anyone could come up with a solution that could put an allotted programming time to machine cycle time ratio. This where years of experience in the workshop comes into play. Having quoted a multitude of jobs, a seasoned machinist should be able to tell you estimated programming and cycle times based of the prints fairly quickly. I think being a MASTER OF PERFECTION you would want something a little closer to an experienced estimation rather than a random ratio formula to determine whether your company stays in business or not. Just my 2 cents, take it for what its worth.
  14. Thank you Jeff!!!! I had to remove the * from the tloffno$ at the end of the ptoff block so I would not get redundant D## if using an alternate numerical value offset. Love it. Thanks again
  15. I understand that the *sg56 is redundant I just like to see it so I know it is forced without question. As for the D value if I use if pccdia #Cutter Compensation #Force Dxx# if prv_cc_pos$ <> cc_pos$ & cc_pos$, prv_tloffno$ = c9k sccomp if cc_pos$, tloffno$ The D## only appears at the G41 line as a numerical value. But when I change that block to pccdia #Cutter Compensation #Force Dxx# if prv_cc_pos$ <> cc_pos$ & cc_pos$, prv_tloffno$ = c9k sccomp if cc_pos$, ptoff It puts the D## value on every line, although in the correct format that I'm looking for; DA, DB, DC or a numerical value. I just want to get rid of the redundant D## values, the G56 H## logic works perfect.

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us

×
×
  • Create New...