G-code Program Header Samples - Page 2
Close
Login to Your Account
Page 2 of 2 FirstFirst 12
Results 21 to 29 of 29
  1. #21
    Join Date
    May 2005
    Country
    UNITED STATES
    State/Province
    Pennsylvania
    Posts
    296
    Post Thanks / Like
    Likes (Given)
    241
    Likes (Received)
    8

    Default

    Quote Originally Posted by SeaMoss View Post
    File name of the program matches the part number ? If that's not good enough, a single rem at the top with the part number should do the job ....
    Not even close to good enough for AS9100 Rev D, but such is life for an aerospace shop.

  2. #22
    Join Date
    Jun 2012
    Location
    Michigan
    Posts
    3,491
    Post Thanks / Like
    Likes (Given)
    2859
    Likes (Received)
    2023

    Default

    Code:
    (op1)
    (dec-11-2017)
    (time - 7:58 am)
    ( t1  1-1/2" sandvik r245   d1.5000 )
    ( t2  garr 1/2" 5flute .03r   d0.5000 )
    ( t3  5/16 142 deg spotdrill   d0.3125 )
    ( t4  #1 drill   d0.2280 )
    ( t5  lakeshore 1/2 90 spiral   d0.5000 )
    if[vtlcn eq 1 ]n2
    if[vtlcn ne 1 ]n1
    n1 t1 m6
    n2
    m279(chip auger on)
    (overall retract   z2. )
    (overall depth   z-.5 )
    (overall max - z2.)
    (overall min - z-.5)
    n100 (facemill--)
     (compensation type - computer)
    /m08

  3. #23
    Join Date
    Mar 2017
    Country
    CHINA
    Posts
    1,968
    Post Thanks / Like
    Likes (Given)
    0
    Likes (Received)
    906

    Default

    Quote Originally Posted by roysol View Post
    Not even close to good enough for AS9100 Rev D, but such is life for an aerospace shop.
    Now yer gonna drag aerospace into it ? Not fair !!

    Altho ya know, if matching file and part numbers don't do the job, nothing else is going to either ... what's better, staple a mylar tape to a programmer's left hand and the part print to his right, then swing him from a hook in the freezer until you run the part again ?

  4. #24
    Join Date
    Jun 2006
    Location
    Huntsville Alabama
    Posts
    1,772
    Post Thanks / Like
    Likes (Given)
    1014
    Likes (Received)
    673

    Default

    4.........year..........old.......thread

  5. #25
    Join Date
    May 2009
    Country
    UNITED STATES
    State/Province
    Wyoming
    Posts
    2,835
    Post Thanks / Like
    Likes (Given)
    6084
    Likes (Received)
    4243

    Default

    Quote Originally Posted by Rstewart View Post
    4.........year..........old.......thread
    Yes, but in importance it's timeless. Unless you are programming at the control like in the old days there is no reason not to have as much useful information as possible typed into the header and anywhere else a comment might be required. If you have trainees it is especially helpful to have a parenthetical description after certain lines, like advance parts catcher, part off, stop spindle, turn off coolant, dump parts catcher, advance bar puller, open chuck, switch to inches/minute, pull bar, close chuck, retract puller, switch to inches/rev, home, etc. That helps teach people the correct format for a frequently-used operation. And like Wheelieking sez it never hurts to inject the occasional bit of humor (for a good time call 867-5309).

  6. Likes digger doug liked this post
  7. #26
    Join Date
    May 2004
    Location
    Paradise, Ca
    Posts
    1,973
    Post Thanks / Like
    Likes (Given)
    540
    Likes (Received)
    923

    Default

    Quote Originally Posted by Oldwrench View Post
    (for a good time call 867-5309).
    You spelled "nigh-eee-igh-ehn" wrong.

    I agree with having notes throughout the program but I've always found a huge header in the program as distracting. I prefer any info other than program number & name to be in the setup sheet, where it can be side by side with pictures and other, more lengthy notes if needed.

  8. #27
    Join Date
    Mar 2017
    Country
    CHINA
    Posts
    1,968
    Post Thanks / Like
    Likes (Given)
    0
    Likes (Received)
    906

    Default

    Quote Originally Posted by [email protected] View Post
    I agree with having notes throughout the program but I've always found a huge header in the program as distracting. I prefer any info other than program number & name to be in the setup sheet, where it can be side by side with pictures and other, more lengthy notes if needed.
    Yup. Also prefer this approach. Lay out the setup on a separate page with circles and arrows on the back and any "watch out for !" statements, too.

    But everyone has their own way ...

  9. #28
    Join Date
    Sep 2008
    Country
    UNITED STATES
    State/Province
    Florida
    Posts
    297
    Post Thanks / Like
    Likes (Given)
    25
    Likes (Received)
    75

    Default

    Yes, everyone has their own way. I agree that there's such a thing as too much, but IMHO, at least one line at the top (for part #, drawing rev., and date) is important. I also like to put a short phrase at the beginning of each tool path telling the operator what's going to happen (rough slot, finish pocket) etc. One can get carried away, though...

  10. #29
    Join Date
    May 2009
    Country
    UNITED STATES
    State/Province
    Wyoming
    Posts
    2,835
    Post Thanks / Like
    Likes (Given)
    6084
    Likes (Received)
    4243

    Default

    Quote Originally Posted by [email protected] View Post
    You spelled "nigh-eee-igh-ehn" wrong.
    Well, damn. Good thing we have lots of Haas controls where there's no limit to the number of characters. I'll start spelling everything phonetically and see if anyone notices...


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •