I posted this in business practices, but didn't get any responses, hopefully this section has more traffic and I get more luck.
Simple question, what is the difference between a setup sheet and a gcode header?
Printable View
I posted this in business practices, but didn't get any responses, hopefully this section has more traffic and I get more luck.
Simple question, what is the difference between a setup sheet and a gcode header?
A setup sheet is a document with information about the project and machining operations.
https://www.cnccookbook.com/art-setup-sheet/
The G-Code header is the block of codes at the beginning of a g-code program that sets the required modes on the machine.
I see, thanks Gerry.
I think I get it now. A gcode header basically points to the correct setup sheet.
I actually read another article on cnccookbooks that confused me:
https://www.cnccookbook.com/g-code-b...ucture-blocks/
But reviewing it again:
"– Program file name.
– Program author
– Version date
– Modification history–a line for each version telling what changed, who made the changes, and the date.
– Machine and control the program is intended for
– Units: inches or mm
– Setup information: What stock material is expected, what size, etc.?
– Work Coordinates: What’s expected by way of work coordinates? Where is Part Zero?
– Customer info: Job shops will want information about what customer and job # the program is part of."
There isn't as much overlap as I remembered after all. I think it's the stock material, work coordinates/where is part zero lines that really threw me off.
I guess it could, but it doesn't have to contain any information that's in the setup sheet.Quote:
A gcode header basically points to the correct setup sheet.
A setup sheet is basically an instruction sheet for machining your part.
You can add comments to the g-code with the same info, but it's not required.
Yep gocha. I just like Bob's way of putting it "A CAD File, CAM File, G-Code File, and a Setup Sheet might be all we need to fully document a program if there’s enough meat captured by the Setup Sheet." So going off this, I just wanted to make sure each component complemented each other, didn't contain redundant information and all 4 components were generated.