Common GCode standards
-
I believe it is important that as far as possible, different 3D printer firmwares and CNC firmwares should ascribe a common meaning to each GCode command. Obviously not all firmwares will support all commands, but where they do the meaning should be the same across all firmwares, so that GCode is as far as possible portable between different firmwares.
There have been many cases in the past where firmware developers have ignored this principle. Sadly this seems to be increasing. Therefore I have posted a message at http://forums.reprap.org/read.php?1,820340 arguing for common standards to be used.
If you have a view on this matter, please consider replying to that post.
-
It seems that the initiative got stuck on some unrelated laser power management discussion, Any way to jumpstart the discussion?
-
Perhaps someone else could reply to that thread and get it back on track?
It's disappointing that neither the Marlin nor the Repetier devs have responded to it.
-
Are they even watching that thread?
... If you think I can help, tell me how, I'm out of ideas on how to get it back on track.
-
@dc42 said in Common GCode standards:
Perhaps someone else could reply to that thread and get it back on track?
It's disappointing that neither the Marlin nor the Repetier devs have responded to it.
I'd be happy to name some names, very politely.... who are they?
-
The Repetier developer is very active on the Repetier forums. Might be worth starting a thread there to draw their attention.
-
@danal Scott Lahteine appears to be the main coordinator/developer on Marlin these days.
