-
Notifications
You must be signed in to change notification settings - Fork 762
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the output of the G-code command #34
Comments
You will contribute these to the documentation? |
I have allready done the M114 (current position) I want to now the "path" to develop a page and get it pushed to GitHub and Its more the git-flow and proper way to work I want to learn. I have a up and running Ruby/Jekyl workspace and have alredy done a minor I have not found any documentation about the format of the output from a Could it be an idea to add the output of a g-code to the documentation. ( I I have also made a configure and setup tool for Marlin called It contains:
Under development:
Its available at GitHub as a VS2015 project. ( Could this be something to look at? MANY REGARDS 2016-08-19 23:07 GMT+02:00 Scott Lahteine notifications@github.com:
|
Have you read all the Github documentation on this subject? I would explain it all at length, but Github have done a very good job of covering this topic. You would also benefit greatly from watching some videos and engaging in some interactive online tutorials to learn the basics of Git branching, merging, rebasing, etc. The first thing you need to do is create forks of Marlin and the Marlin documentation repository under your own Github account. Then, get a copy of Github Desktop, which makes dealing with branches, commits, etc. much easier. |
I have done all in the Github documentation and got it up and running. I I did a copy of the Marlin dokumentation and NOT a fork to my Github Thank you for your suggestions |
You should always fork because then you have a link upstream so you can rebase as primary repository is updated and you can create your own downstream forks to test changes so you don't have to break the |
Honestly the best way to figure this out would be to test sending these commands to a printer and observing the response in host program like Repetier or Pronterface, etc. |
Adding syntax for the response of a G-Code command for each G-Code
Example:
G-Code M105
will create a response like
ok T:195.4 / 195.0 B: 27.8 / 0.0 T0: 195.4 / 195.0 @:29 B@:0
The documentation should contain the explanation of each component of the response.
The text was updated successfully, but these errors were encountered: