G-code explanation

Hi everyone!
I would realize a G-code interpreter. But I have a question. In a G-code line, for example N123 [G-code] *71, what is the utility of number line (N....)? What is the utility of asterisk followed by a number? How is this number calculated?

Quote
calogerom
I would realize a G-code interpreter.

And the point of writing yet another interpreter is ... ?

Quote
calogerom
How is this number calculated?

[github.com]
[reprap.org]

---

Generation 7 Electronics	Teacup Firmware	RepRap DIY

Quote
calogerom
Hi everyone!
I would realize a G-code interpreter. But I have a question. In a G-code line, for example N123 [G-code] *71, what is the utility of number line (N....)? What is the utility of asterisk followed by a number? How is this number calculated?

See [reprap.org].

Edited 1 time(s). Last edit at 12/24/2014 06:30PM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Quote
Traumflug

Quote
calogerom
I would realize a G-code interpreter.

And the point of writing yet another interpreter is ... ?

I like to write my own code. I don't like to copy from others

Quote
Traumflug

Quote
calogerom
How is this number calculated?

[github.com]
[reprap.org]

Thank you for the example!

Quote
Traumflug
And the point of writing yet another interpreter is ... ?

Some people - myself included - enjoy writing code. Among other things, my reprap hobby is a creative outlet for writing some interesting software. I did the same thing myself. I started with a G Code interpreter, realized I could easily have it follow along with an active print and then just started adding buttons and sliders. I started with pronterface, then moved to the printcore portion of pronterface, and then wrote my own interface. Now I have my own host software that is adapted to my workflow and toolchain.

Quote
jbernardis
Some people - myself included - enjoy writing code. Among other things, my reprap hobby is a creative outlet for writing some interesting software. I did the same thing myself. I started with a G Code interpreter, realized I could easily have it follow along with an active print and then just started adding buttons and sliders. I started with pronterface, then moved to the printcore portion of pronterface, and then wrote my own interface. Now I have my own host software that is adapted to my workflow and toolchain.

I would do the same thing. If I have some problem, can I ask you help?

Quote
jbernardis

Quote
Traumflug
And the point of writing yet another interpreter is ... ?

Some people - myself included - enjoy writing code.

That's great, and I see plenty of opportunities more useful than reinventing something which works perfectly already. Top of the head there's e.g. jerk-less and step accurate look-ahead. Or completing support for an arbitrary number of axes in Teacup, if you want something less demanding. The latter also requires some fiddling with the G-code interpreter, FWIW.

---

Generation 7 Electronics	Teacup Firmware	RepRap DIY

Quote
Traumflug
That's great, and I see plenty of opportunities more useful than reinventing something which works perfectly already.

I don't want to get into an argument here, but I just want to point out that the word you chose to use - perfectly - is open to interpretation. To me, pronterface was adequate, but it wasn't perfect. I found myself too many times saying I wish it did this or I wish it worked like that. Once I became familiar with the interfaces, I saw an opportunity to do things my own way.

I'm not against contributing to an open source project, but it's a concept I am just becoming familiar with. You're familiar with the needs in firmware because of your closeness to the teacup project. What you listed there were things I was not even aware of. Let me start investigating teacup. It's a direction I was thinking of moving towards anyway.