Talk:Torch Table Build: Difference between revisions
(step-nc) |
No edit summary |
||
| Line 1: | Line 1: | ||
G Code is a loose standard. That means if you take some other G Code that you did not write, there is a good chance it will not work. The reason is that each G Code interpreter, be it EMC2, RepRap motherboard, or fancy six axis robotic arm controller were all produced for a specific job which require a specific tool path, on a specific machine. Now if your a computer scientest or programmer, your going "wait a minute, why don't they just make the language more intelligent, add in a required machine descriptor and abstract the tool path away from the user which forces users to hand craft each part they want to make!" Which is a valid point, and I would encourage someone to come up with a better language, because G Code sucks. | G Code is a loose standard. That means if you take some other G Code that you did not write, there is a good chance it will not work. The reason is that each G Code interpreter, be it EMC2, RepRap motherboard, or fancy six axis robotic arm controller were all produced for a specific job which require a specific tool path, on a specific machine. Now if your a computer scientest or programmer, your going "wait a minute, why don't they just make the language more intelligent, add in a required machine descriptor and abstract the tool path away from the user which forces users to hand craft each part they want to make!" Which is a valid point, and I would encourage someone to come up with a better language, because G Code sucks. | ||
----- | |||
I'm a profane, but [http://en.wikipedia.org/wiki/STEP-NC STEP-NC] looks very similar to your description. | I'm a profane, but [http://en.wikipedia.org/wiki/STEP-NC STEP-NC] looks very similar to your description. | ||
----- | |||
This information looks great. The photos are quite good, CAD drawings help a lot, circuits, etc. However, I think this page should be broken up to follow the product development standards. At a minimum, there should be a Torch Table Intro, Torch Table Design, Torch Table BOM, and Torch Table Build Instructions. These should be linked using the OSE Product Template. [[User:Mjn|Mjn]] 07:53, 21 June 2011 (PDT) | |||
Latest revision as of 14:53, 21 June 2011
G Code is a loose standard. That means if you take some other G Code that you did not write, there is a good chance it will not work. The reason is that each G Code interpreter, be it EMC2, RepRap motherboard, or fancy six axis robotic arm controller were all produced for a specific job which require a specific tool path, on a specific machine. Now if your a computer scientest or programmer, your going "wait a minute, why don't they just make the language more intelligent, add in a required machine descriptor and abstract the tool path away from the user which forces users to hand craft each part they want to make!" Which is a valid point, and I would encourage someone to come up with a better language, because G Code sucks.
I'm a profane, but STEP-NC looks very similar to your description.
This information looks great. The photos are quite good, CAD drawings help a lot, circuits, etc. However, I think this page should be broken up to follow the product development standards. At a minimum, there should be a Torch Table Intro, Torch Table Design, Torch Table BOM, and Torch Table Build Instructions. These should be linked using the OSE Product Template. Mjn 07:53, 21 June 2011 (PDT)