G-code Program Header Samples
Close
Login to Your Account
Page 1 of 2 12 LastLast
Results 1 to 20 of 29
  1. #1
    Join Date
    Mar 2011
    Location
    Clearwater FLA
    Posts
    1,115
    Post Thanks / Like
    Likes (Given)
    76
    Likes (Received)
    213

    Default G-code Program Header Samples

    Ok guys,

    What I am looking for are some sample NC file headers, I want to see what you guys like the operators to see in the program. Here is an example of a post I created with what I have in the header.

    Code:
    (BEGIN PREDATOR NC HEADER)
    (MACH_FILE=HAAS - 3XVMILL.MCH)
    (MTOOL T1 S4 D.25 H5. A118. C0. DIAM_OFFSET 1 = .125)
    (MTOOL T2 S1 D.5 H5. A0. C0. DIAM_OFFSET 2 = .25)
    (MTOOL T3 S1 D.5 H4. A0. C0. DIAM_OFFSET 3 = .25)
    (MTOOL T4 S1 D.25 H5. A0. C0. DIAM_OFFSET 4 = .125)
    (MTOOL T5 S2 D.25 H2.5 A0. C.125 DIAM_OFFSET 5 = .125)
    (MTOOL T6 S7 D.078 H5. A90. C0. DIAM_OFFSET 6 = .039)
    (SBOX X-2.95 Y-2.95 Z-1.975 L5.9 W5.9 H1.975)
    (END PREDATOR NC HEADER)
    
    %
    O100
    (PROGRAM NUMBER)
    
    (FIRST MACHINE SETUP - Machine Setup - 1)
    
    (PROGRAM NAME -  SAMPLE02.NC)
    (POST -  FANUC 0M)
    (DATE - MON. 10/28/2013)
    (TIME - 11:44AM)
    (MATERIAL ALUM  6  x 6 x 2  THICK  MOUNTED ON HIRSHMANN TOOLING BLOCK)
    (SET ZERO TOP CENTER OF BLOCK)
    (T5 ON OP 10 USES H15  THIS Z OFFSET IS -.008 DEEPER THEN H5)
    
    G90 G80 G40 G20 G17
    G00 G91 G28 Z0.
    G91 G28 X0. Y0.
    
    (OP1 DRILLING PEN HOLES )
    
    N0001 T01 M06
    S1500 M03
    G4 X3.
    G90 G54 X2.3 Y-2.3
    G43 H01 Z.25 M08
    G83 G98 X2.3 Y-2.3 Z-1.1549 R.1 Q.05 F7.
    X-2.3
    G80
    
    (OP 2 DRILLING CARD HOLDER CORNERS)
    
    S1500
    G00 X1.5829 Y-1.7011
    G83 G98 X1.5829 Y-1.7011 Z-.89 R.1 Q.05 F7.
    X1.7325 Y-1.55
    Y-1.95
    X-1.7325
    Y-1.55
    G80
    M09
    M05
    G00 G91 G28 Z0.
    M01
    In my example I am using the tool list variable to post the necessary header for predator to simulate the tool and stock. I assume that have the tool description, size offsets and LOC would be more important for production shops and figure some of you could post up some samples for me to review.


    Side Bar:


    In the V26 software that we are currently rolling out we did add setup sheets, but I know many shops prefer to have the program notes in the header so there is only 1 file to "manage" for the program notes...

    But for those that want to take a look at our XLM setup sheets here are a few screen shots of the different templates that come pre loaded with the V26.

    setup_sheet.jpg

    setup_sheet_2.jpg

    setup_sheet_3.jpg

  2. #2
    Join Date
    Oct 2006
    Location
    Boston,Mass.
    Posts
    1,973
    Post Thanks / Like
    Likes (Given)
    69
    Likes (Received)
    163

    Default

    (Programmed By.___________)
    (Programmed Proven By________)
    (Program Proven Date_______)

  3. Likes Oldwrench liked this post
  4. #3
    Join Date
    Mar 2006
    Country
    UNITED STATES
    State/Province
    Tennessee
    Posts
    2,003
    Post Thanks / Like
    Likes (Given)
    249
    Likes (Received)
    363

    Default

    Part #
    Rev #
    Fixture bin #

  5. Likes Oldwrench liked this post
  6. #4
    Join Date
    Aug 2005
    Location
    Bremerton, Wa
    Posts
    2,595
    Post Thanks / Like
    Likes (Given)
    66
    Likes (Received)
    68

    Default

    Waaaaaaaaay to many rem statements

  7. #5
    Join Date
    Apr 2010
    Country
    UNITED STATES
    State/Province
    Wisconsin
    Posts
    5,432
    Post Thanks / Like
    Likes (Given)
    4000
    Likes (Received)
    3202

    Default

    I don't use'm. Negligible value for onesy/twosey program files that only I run.

  8. #6
    Join Date
    Mar 2013
    Country
    UNITED STATES
    State/Province
    New York
    Posts
    3,745
    Post Thanks / Like
    Likes (Given)
    2711
    Likes (Received)
    2377

    Default

    part name
    part number w/ rev and assy #
    file location
    customer name
    Engineer
    programmer name
    set-up name
    date

  9. #7
    Join Date
    Jun 2011
    Location
    Ashland, Oregon
    Posts
    28
    Post Thanks / Like
    Likes (Given)
    1
    Likes (Received)
    0

    Default

    Abbreviated company name, part #
    Full company name, part # , rev #
    Machine
    Programed date , programmer initials
    Proved date , initials
    Cycle time
    Material (meaning raw blank size if extruded, eg. 6061 ALU 1" x 1 1/4")
    Cut size
    (any specific variables : like bar feeder setting for the lathe)
    Origin locations of work offsets.
    Tool List


    Basically a setup sheet minus pictures. (i'm still working on ascii art for that)

  10. #8
    westk Guest

    Default

    position #
    program 1 of 1
    machine center
    part #
    rev #
    Derivative
    program version #
    Mat size
    mat type
    grain with what dim
    program info
    setup info
    5 along x
    2 along y
    x0=
    y0=
    z0=
    programmer name

  11. #9
    Join Date
    Mar 2009
    Country
    UNITED STATES
    State/Province
    Washington
    Posts
    8,374
    Post Thanks / Like
    Likes (Given)
    5773
    Likes (Received)
    10138

    Default

    Why don't you guys make a set up sheet and leave nine miles of crap out of the program?

  12. Likes mbpp, Edster, AARONT, Billetgrip, jrmach and 1 others liked this post
  13. #10
    Join Date
    Mar 2011
    Location
    Clearwater FLA
    Posts
    1,115
    Post Thanks / Like
    Likes (Given)
    76
    Likes (Received)
    213

    Default

    John,

    I think for some shops having all the information about the program, in the program makes it easier to keep track of. Having to manage the NC file and the setup sheet takes a little more work, than just having the information in the header of the NC file.

    Which leads me to a different point.

    Do you guys take pictures of setup? Maybe store that with the setup sheet and nc code?

  14. Likes Oldwrench liked this post
  15. #11
    Join Date
    Mar 2009
    Country
    UNITED STATES
    State/Province
    Washington
    Posts
    8,374
    Post Thanks / Like
    Likes (Given)
    5773
    Likes (Received)
    10138

    Default

    Quote Originally Posted by aldepoalo View Post
    John,

    I think for some shops having all the information about the program, in the program makes it easier to keep track of. Having to manage the NC file and the setup sheet takes a little more work, than just having the information in the header of the NC file.

    Which leads me to a different point.

    Do you guys take pictures of setup? Maybe store that with the setup sheet and nc code?
    Yeah I hear ya.

    I guess I find it easier to just make a set up sheet than to type a bunch of crap into the program.

  16. #12
    Join Date
    Mar 2013
    Country
    UNITED STATES
    State/Province
    New York
    Posts
    3,745
    Post Thanks / Like
    Likes (Given)
    2711
    Likes (Received)
    2377

    Default

    Quote Originally Posted by aldepoalo View Post
    John,

    I think for some shops having all the information about the program, in the program makes it easier to keep track of. Having to manage the NC file and the setup sheet takes a little more work, than just having the information in the header of the NC file.

    Which leads me to a different point.

    Do you guys take pictures of setup? Maybe store that with the setup sheet and nc code?

    at my old shop, they kept a program header template on the network that we saved our files to. A few guys would take pictures of the setups, and labeled the pick up locations and their corresponding WCS. all this was done and saved only after a program was proved out.

    this was for production...waste of time at the prototype level.

  17. #13
    Join Date
    Jun 2011
    Location
    Ashland, Oregon
    Posts
    28
    Post Thanks / Like
    Likes (Given)
    1
    Likes (Received)
    0

    Default

    9 miles of crap, although troublesome to input, have helped when access to our network drive wasn't available. We used to keep paper setup sheets at the machine for each job that was common to that machine. But papers being lost, or multiple copies, made it a challenge to keep things straight. So we've made an effort to keep the electronic copies up to date so the next guy who comes in looking for it doesn't have to guess about what's current. I've also started to take pictures of setups, tooling if there are clearance issues, and occasionally a video. All this is kept on the network in the job folder. Also for a few of us, a gentle reminder of origins and notes is all we need to remember the specifics of the job if it's a repeater. The setup sheets will also keep information of any finish work required for that part. They are like instruction books for dummies, although they always come out with a bigger, better dummy.

  18. #14
    Join Date
    Dec 2012
    Location
    WI, USA
    Posts
    206
    Post Thanks / Like
    Likes (Given)
    67
    Likes (Received)
    9

    Default

    Customer - Part Name
    Part number
    Drawing Rev number
    Material
    ()
    Machine it's programmed for, which op it is, and program number
    ()
    Short description of set-up on machine (Using 30" x40" tombstone,
    bolt fixture to tombstone orientated, etc., etc.)
    ()
    Brief loading instructions, if necessary, and what way the part/program
    is orientated
    ()
    Programmed Positions at B0:
    B0 is .....
    X0 is ....
    (Ref: X-bump(s) is X.....)
    Y0 is ...
    (Ref: Y-bump(s) is Y .... )
    Z0 is ...
    (Ref: Z-bump(s) is Z....)
    ()

    I have found that taking the short amount of time it takes to add this information has been way more beneficial than detrimental. I try to give the most pertinent information in the most concise way. I think of what I'd like to see if I was setting up a job, and/or post the most needed information. What's the material? You know right where to look. Any special instructions? What did we mount these fixtures to again? I'll probably hear crap for this but I also have descriptive tool list/process sheets and set-up sheets that go into further detail, and a picture is worth a thousand words, so I take pictures of set-ups, for some loading instructions, pictures of fixtures, etc. To have this information available in multiple places has the tendency to save time and frustration. It's not a perfect world; sometimes you have the program readout and don't have the set-up sheet handy.... anyway, thorough documentation and instruction is one of the best ways to get the most out of people (productivity) while minimizing mistakes (quality).

  19. Likes CNC Hacker liked this post
  20. #15
    Join Date
    Jan 2013
    Location
    Gilbert, AZ
    Posts
    4,677
    Post Thanks / Like
    Likes (Given)
    5500
    Likes (Received)
    5732

    Default

    We are pretty in-formal at B&A! LOL

    %
    O00017
    (I AM KNOWN TO PUT ALL KINDS OF CRAZY SHIT HERE, IT KEEPS THE ATMOSPHERE LAID BACK, AND THE MORAL HIGH)
    (LIKE: BATSHIT FLAVORED MONKEY NARDSICKLES )
    (STOCK = 1.25"x4.5"x10.050" )
    (X,Y "0" = TYPICAL ORIGIN )
    (Z "0" = TOP OF STOCK -.025" )
    ( T1 = .375 SPOT DRILL )
    ( T2 = .250 DRILL )
    ( T3 = "Q" DRILL )
    ( T4 = 1.0 TWISTY CHIP SPITTER OUT'ER )
    ( T10 = .375 2FL BALL MILL )
    ( T12 = BIG DADDY )
    ( T17 = .5 2FL .750min. LOC )
    ( T24 = .375 2FL 90' CHAMFER )
    N17 G00 G91 G28 Z0 M05 G80
    T17 M6 ( .5 2FL CARB EM. 0.5 DIA. )
    (SOMETIMES I EVEN PUT HIDDEN MESSAGES IN RANDOM SPOTS JUST TO SEE HOW LONG IT TAKES TOMMY TO FIND THEM)
    T12
    G90 G54 X-0.6281 Y1.1308 S12000 M3
    G43 H17 Z1.725 /M8
    Z0.825
    G1 G17 Z0.5 F50.0
    X-0.25
    G41 D17 X-0.2131 Y1.1782
    G3 X-0.2 Y1.2369 I-0.1244 J0.0586
    G1 Y1.6554
    G2 X0.175 Y2.0304 I0.375 J0. F75.0
    G1 X1.4826 F50.0
    G2 X1.7983 Y1.9608 I0. J-0.75 F75.0
    G3 X3.0409 Y2.0725 I0.5247 J1.1307 F50.0
    G2 X3.9728 Y1.9071 I0.3839 J-0.5448 F75.0
    G3 X6.0272 Y1.9071 I1.0272 J0.7114 F50.0
    G2 X6.9591 Y2.0725 I0.5479 J-0.3795 F75.0
    G3 X8.2017 Y1.9608 I0.7179 J1.019 F50.0
    G2 X8.5174 Y2.0304 I0.3157 J-0.6803 F75.0
    G1 X9.825 F50.0
    (HE USUALLY COMES IN LAUGHING HYSTERICALLY, OR THROWS SOMETHING AT ME)


    Sorry for not being very serious. But, at least I was honest.

  21. Likes aldepoalo, Billetgrip, Oldwrench liked this post
  22. #16
    Join Date
    Jun 2012
    Location
    Michigan
    Posts
    3,706
    Post Thanks / Like
    Likes (Given)
    3212
    Likes (Received)
    2142

    Default

    All I need is the part number and a tool list.
    The rest of the info is on our job sheet router.

  23. Likes Edster liked this post
  24. #17
    Join Date
    Apr 2001
    Location
    Nottingham, England
    Posts
    1,668
    Post Thanks / Like
    Likes (Given)
    78
    Likes (Received)
    154

    Default

    We have one called Chinese.nc

    It's the local take away menu so we can phone an order thru without leaving the machine.

  25. Likes CNC Hacker, Mtndew, Edster, roysol, Oldwrench liked this post
  26. #18
    Join Date
    Jun 2012
    Location
    Michigan
    Posts
    3,706
    Post Thanks / Like
    Likes (Given)
    3212
    Likes (Received)
    2142

    Default

    Quote Originally Posted by john stevenson View Post
    we have one called chinese.nc

    it's the local take away menu so we can phone an order thru without leaving the machine.
    genius!!!!!

  27. Likes Oldwrench liked this post
  28. #19
    Join Date
    May 2015
    Country
    UNITED STATES
    State/Province
    Ohio
    Posts
    3
    Post Thanks / Like
    Likes (Given)
    2
    Likes (Received)
    3

    Default

    Quote Originally Posted by John Welden View Post
    Yeah I hear ya.

    I guess I find it easier to just make a set up sheet than to type a bunch of crap into the program.
    ISO standards require that a program has to be traceable to a part. So if there is no header on the program or the crap as you called it how can you prove that it is the correct program?

  29. Likes roysol, Oldwrench liked this post
  30. #20
    Join Date
    Mar 2017
    Country
    CHINA
    Posts
    1,813
    Post Thanks / Like
    Likes (Given)
    0
    Likes (Received)
    1127

    Default

    Quote Originally Posted by heavenlykid View Post
    ISO standards require that a program has to be traceable to a part. So if there is no header on the program or the crap as you called it how can you prove that it is the correct program?
    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 ....


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
  •