Brad Lisle

Verified Members
  • Content count

    237
  • Joined

  • Last visited

Community Reputation

71 Excellent

1 Follower

About Brad Lisle

  • Rank
    Member
  • Birthday 12/14/1978

Uncategorized

  • Location
    Hillsboro, OR

Recent Profile Visitors

2,022 profile views
  1. Brad Lisle

    Buffer help, I think?

    @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
  2. Brad Lisle

    HOW TO USE CALL OO88?

    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.
  3. Brad Lisle

    Mill-Turn Machine Recommendation

    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.
  4. Brad Lisle

    Helical ramp OD

    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!
  5. Brad Lisle

    Smart Machine Tool

    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)
  6. Brad Lisle

    Helical ramp OD

    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
  7. Brad Lisle

    Best toolholder for 1/8" shank tools?

    These are a great option. I have had great success with the Lyndex SK series holders.
  8. Brad Lisle

    Programming Time

    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.
  9. Brad Lisle

    Help with D## output

    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
  10. Brad Lisle

    Help with D## output

    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.
  11. I have modified my Okuma post logic to output G56 HA if tlngno$ = 10001 | tlngno$ = t$. Further more it will output G56 HB if tlngno$ = 10002 and G56 HC if tlngno$ = 10003. Here is the code ptlen #Tool length offset if tlngno$ = 10001 | tlngno$ = 10002 | tlngno$ = 10003 | tlngno$ = t$, [ if tlngno$ = 10001 | tlngno$ = t$, *sg56, "HA" if tlngno$ = 10002, *sg56, "HB" if tlngno$ = 10003, *sg56, "HC" ] else, *sg56, *tlngno$ !tlngno$ However, I cannot for the life of me get it to work the same for the cutter comp without getting the output on every line pccdia #Cutter Compensation #Force Dxx# if prv_cc_pos$ <> cc_pos$ & cc_pos$, prv_tloffno$ = c9k sccomp #if cc_pos$, tloffno$ if cc_pos$, ptoff ptoff #Tool radial offset if tloffno$ = 10001 | tloffno$ = 10002 | tloffno$ = 10003 | tloffno$ = t$, [ if tloffno$ = 10001 | tloffno$ = t$, "DA" if tloffno$ = 10002, "DB" if tloffno$ = 10003, "DC" ] else, *tloffno$ !tloffno$ Here is the posted code: N1 ( 1/2 FLAT ENDMILL ) G90 G17 G80 G40 G00 G30 P10 G116 T1 G15 H2 G131 F1260. J1 E.002 G00 G94 G90 X-2.4 Y-.1 S5000 M03 T2 G56 HA Z1. M08 G01 Z-1. F30. G41 DA X-2.35 G03 DA X-2.25 Y0. I0. J.1 G01 DA Y1.5 G02 DA X-2. Y1.75 I.25 J0. G01 DA X2. G02 DA X2.25 Y1.5 I0. J-.25 G01 DA Y-1.5 G02 DA X2. Y-1.75 I-.25 J0. G01 DA X-2. G02 DA X-2.25 Y-1.5 I0. J.25 G01 DA Y0. G03 DA X-2.35 Y.1 I-.1 J0. G01 G40 X-2.4 G00 Z1. G130 G131 F1260. J1 E.002 G00 Y-.1 G01 Z-1. G41 DB X-2.35 G03 DB X-2.25 Y0. I0. J.1 G01 DB Y1.5 G02 DB X-2. Y1.75 I.25 J0. G01 DB X2. G02 DB X2.25 Y1.5 I0. J-.25 G01 DB Y-1.5 G02 DB X2. Y-1.75 I-.25 J0. G01 DB X-2. G02 DB X-2.25 Y-1.5 I0. J.25 G01 DB Y0. G03 DB X-2.35 Y.1 I-.1 J0. G01 G40 X-2.4 G00 Z1. M09 M05 G130 G30 P30 M01 N2 ( 1/8 DRILL ) G90 G17 G80 G40 G00 G30 P10 G116 T2 G15 H2 G00 G94 G90 X0. Y0. S6000 M03 T1 G56 HA Z1. M51 G71 Z1. G81 Z-1. R.1 F25. M53 G00 M09 M05 G30 P30 M02 What am I missing? If I do not use the ptoff logic and use the if cc_pos$, tloffno$ line in the pccdia post block it works as expected and only outputs on a single line with the numerical value. I know it is something simple that I am overlooking. Thank you in advance. Brad
  12. new technology brings new problems. The only way I have seen was to break up the y axis movements and command a S speed at each line. You still will not get a true CSS but you can get it closer than a G97. I have heard some talk about this but not sure what will come yet.
  13. Brad Lisle

    Okuma Stock Define for Mill help

    Here is the mill version. The one Orvie posted is for lathes. Stock Graphics for OSP-M.pdf
  14. Brad Lisle

    New Lathe Machine

    I know some of the LT machines are already done in MT. You will want to use MT to get the turret syncs correct, much easier. Where are you located? Either way Gosiger will take good care of you.
  15. Brad Lisle

    New Lathe Machine

    Okuma without a doubt! oh wait... I might be biased

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