3diy
/
klipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: Note g-code output is not intented to be parsed in G-Codes.md 

Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
Kevin O'Connor 2022-03-03 22:20:27 -05:00
parent c31f981575
commit 4a8aece6a7
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/G-Codes.md
View File

@ -42,7 +42,10 @@ Klipper's goal is to support the G-Code commands produced by common
3rd party software (eg, OctoPrint, Printrun, Slic3r, Cura, etc.) in 3rd party software (eg, OctoPrint, Printrun, Slic3r, Cura, etc.) in
their standard configurations. It is not a goal to support every their standard configurations. It is not a goal to support every
possible G-Code command. Instead, Klipper prefers human readable possible G-Code command. Instead, Klipper prefers human readable
["extended G-Code commands"](#additional-commands). ["extended G-Code commands"](#additional-commands). Similarly, the
G-Code terminal output is only intended to be human readable - see the
[API Server document](API_Server.md) if controlling Klipper from
external software.
If one requires a less common G-Code command then it may be possible If one requires a less common G-Code command then it may be possible
to implement it with a custom to implement it with a custom